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
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 vec
---------------
--------
-Original Message-----
From: Duncan Murdoch [mailto:murdoch.dun...@gmail.com]
Sent: Tuesday, 2 May 2017 04:22
To: Jack Kelley ; r-devel@r-project.org
Subject: Re: [Rd] Any progress on write.csv fileEncoding for UTF-16 and
UTF-32 ?
On 30/04/2017
Correction to my previous post: Not just the final CR+LF...
Change
EXAMPLE: Using UTF-32 for exaggeration (note also that 3 nul bytes are
missing in the final CR+LF):
to
EXAMPLE: Using UTF-32 for exaggeration (note also that 3 nul bytes are
missing in *each* CR+LF):
-- Jack Kelley
__
adBin (csv, "raw", 1000))
}), .Names = names (EOL))
}), .Names = ENCODING)
print (csv)
print (CSV)
--------------------------------
------------
-Original Message-
From: Duncan Murdoch [mailto:murdoch.dun...@gmail.com]
Sent: Tuesday, 2
df, csv, fileEncoding = encoding, row.names = FALSE,
eol = EOL [EOL.name]
)
list (csv = csv, raw = readBin (csv, "raw", 1000))
}), .Names = names (EOL))
}), .Names = ENCODING)
print (csv)
print (CSV)
--------------------------------
------------
-Original
