search for: yeby3zcb

...eds to figure out how many characters there are in those bytes in order to add the appropriate CR with the right width. The default is 8 bit, so you get 0D 0A in current versions of R, regardless of the encoding. There are ways to declare UTF-16LE (see https://msdn.microsoft.com/en-us/library/yeby3zcb.aspx, or Google "Windows fopen" if that moves), but no other wide encoding. That's what I'm putting in place if you ask for UTF-16LE or UCS-2LE. So far I'm not planning to handle UTF-16BE or UTF-32, because doing those would mean R would have to handle the translation of...

On 30/04/2017 12:23 PM, Duncan Murdoch wrote: > No, I don't think anyone is working on this. > > There's a fairly simple workaround for the UTF-16 and UTF-32 iconv > issues: don't attempt to produce character vectors, produce raw vectors > instead. (The "toRaw" argument to iconv() asks for this.) Raw vectors > can contain embedded nulls. Character vectors