By UTF-18 I meant UTF-16, obviously.
On Sun, Nov 10, 2013 at 8:41 PM, Sverre Stausland
wrote:
> With respect to your comment (sorry, the e-mail you wrote that in
> didn't get to my inbox):
>
>>> I don't think so. In general, functions that convert to the native
g that doesn't cover all the characters in
>> UTF-8.
As I understand it, the native encoding in Windows is UTF-18, not Latin1:
http://msdn.microsoft.com/en-us/library/dd374081.aspx
And UTF-18 is a superset of UTF-8, isn't it?
Sverre
On Sun, Nov 10, 2013 at 1:49 PM, Duncan M
My e-mail was intended as a typical "feature request", and I couldn't
find any more suitable place for that than the r-devel mailing list. I
am not a programmer, so I don't have the skills to write this into R's
source code myself.
The incentive is nevertheless clear enough. I believe a software
p
As recently discussed on Stack Overflow, R for Mac OS and Ubuntu (so
probably all Unix systems) can correctly write files with UTF-8
encoding, but R for Windows cannot:
http://stackoverflow.com/questions/19877676/write-utf-8-files-from-r
I strongly suggest that R for Windows should support this f
