On 10 November 2013 at 21:13, Nigel Delaney wrote:
| Thanks Dirk. I'll confess I am mostly trying to follow the practices
| outlined in the writing R-extensions manual and books by Chambers and
| Gentleman, but have found some conflicting advice on the internet in
| various places, and am also t
On 10 November 2013 at 16:32, Nigel Delaney wrote:
| I had a quick question I was hoping someone might be able to answer, as my
journey through the source code so far has not been very profitable. I have a
command line program that embeds R, and the program works just fine when run
from the com
Hi,
I had a quick question I was hoping someone might be able to answer, as my
journey through the source code so far has not been very profitable. I have a
command line program that embeds R, and the program works just fine when run
from the command line. However, when I run the program as a j
On 13-11-10 2: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
encoding break UTF-8 on Windows, because the native encoding is often
Latin1 or some other
Here is a quick (and largely untested, apart from the toy example) hack that
should read and write UTF-8 encoded CSV files on Window. It is *not* the best
solution, which should use proper C-level code. But it could help a bit in your
case.
Best,
Philippe Grosjean
read.tableUTF8 <- function (
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
>>> encoding break UTF-8 on Window
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
>> encoding break UTF-8 on Windows, because the native encoding is often
>> Latin1 or some other encoding that doesn't cover all the cha
On 13-11-10 7:31 AM, Sverre Stausland wrote:
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 ne
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
On 13-11-09 6:58 PM, Ben Bolker wrote:
Duncan Murdoch gmail.com> writes:
On 13-11-09 12:07 PM, Sverre Stausland wrote:
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:
Th
To continue this discussion with constructive propositions, here is a page that
provides useful tracks for using UTF-8 on Windows:
http://www.utf8everywhere.org (second half of the page).
On 10 Nov 2013, at 00:58, Ben Bolker wrote:
> Duncan Murdoch gmail.com> writes:
>
>>
>> On 13-11-09 12:
11 matches
Mail list logo
