Am 27.08.2018 um 21:42 schrieb Allin Cottrell:
And here's what I find:
If <UTF8_filename> contains accented characters that are in my
Windows' locale codepage (for example c-cedilla), and <TO_ENCODING> is
just "" (empty string to indicate current locale), the second
invocation of file.info() works OK, though not surprsingly the first
one fails (actually, produces a bunch of NAs).
So this case might be caught in
functions like gretl.loadmat which is
offered to R by gretl, right?
Or actually I guess I might mean the string gretl.dotdir, really.
If <UTF8_filename> contains out-of-codepage characters (I tried
Greek), conversion to "" fails. Not surprising. In addition, iconv()
with to="UTF16" fails. It seems to me this last is an R bug. The
function iconvlist() shows that UTF16 is a valid target.
Aha, interesting. I was puzzled by some of the failures in this area.
Where are R bugs reported, anyway? It turns out it's not only hard to
google for "R" stuff, but also for R bugs, because that's actually an R
package of that name...
One more thought, maybe "UTF-16LE" on little-endian machines?
But I suspect R suffers from the problem that gretl had before 2018b,
namely that you can't access files that have out-of-codepage names
(and whose names must therefore be given in UTF16).
Sounds plausible -- way to go, gretl!
thanks,
sven