similar to: iconv documentation error

You seem confused about Latin-1: those characters are not in Latin-1. (MicroSoft code pages are a proprietary encoding, some code pages such as CP1252 being extensions to Latin-1.) You have not given the 'at a minimum information' asked for in the posting guide so we have no way to reproduce this, and without showing us the output on your system, we have no idea what you saw. [As a

On 23.02.2016 11:37, Martin Maechler wrote: >>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>>> on Mon, 22 Feb 2016 18:45:59 +0100 writes: > > > Dear R developers > > I think I have found a bug that can be reproduced with two lines of code > > and I am very thankful to get your first assessment or feed-back

Excellent analysis, thank you both for the quick reply! Is there anything I can do to get the bug fixed in the next version of R (e. g. filing a bug report at https://bugs.r-project.org/bugzilla3/)? On Tue, 2016-02-23 at 14:06 +0200, Mikko Korpela wrote: > On 23.02.2016 11:37, Martin Maechler wrote: > >>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >

Hello there, I have a windows box (spanish locale, charset cp1252) which is backup to a linux server via rsync. Until now I've had problems with file names containing non us-ascii characters. Since the new stable version of rsync with support for iconv I've upgraded rsync on my linux (Debian) to 3.0.0 and also on my windows (cygwin, compiled from source). It works quite right, getting

Upon further inspection, I think these are at least two problems. First the issue with printing latin1/cp1252 characters in the "80" to "9F" code range. x <- c("?", "?", "?") Encoding(x) print(x) I assume that these are Unicode escapes!? (Given that Encoding(x) shows "latin1" I'd rather expect latin1/cp1252 escapes here, but

Thank you!. My apologies again for not including the console output in my message before. I sent another e-mail with the output in the meantime, so it should be a bit clearer now, what I am seeing. In case I missed something, please let me know. Yes, I am using latin1 and cp1252 interchangebly here, mostly because Encoding() is reporting the encoding as "latin1". You presumed correctly

>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>> on Mon, 22 Feb 2016 18:45:59 +0100 writes: > Dear R developers > I think I have found a bug that can be reproduced with two lines of code > and I am very thankful to get your first assessment or feed-back on my > report. > If this is the wrong mailing list or I

R-devel community: I have encountered some unexpected behavior using iconv, which may be the source of errors I am getting when connecting to a UTF-16 -encoded SQL Server database. A simple example is below. When researching this problem, I found r-devel reports of the same problem in threads from June 2010 and February, 2016, and that bug #16738 was posted to Bugzilla as a result. However, I

On 23/02/2016 7:06 AM, Mikko Korpela wrote: > On 23.02.2016 11:37, Martin Maechler wrote: >>>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>>>> on Mon, 22 Feb 2016 18:45:59 +0100 writes: >> >> > Dear R developers >> > I think I have found a bug that can be reproduced with two lines of code

>>>>> Uwe Ligges <ligges at statistik.tu-dortmund.de> >>>>> on Wed, 28 Jun 2017 18:45:59 +0200 writes: > On 27.06.2017 17:36, Martin Maechler wrote: >> This is a continuation of the R-devel thread with subject >> "suggestion to fix packageDescription() for Windows users" : >> >> As I said there, a

8. You have join to this mail a text file with the few characters that don't = match. On Swat, it's easier. = I use Swat from my win98 box. When I write a share comment with some chara= cters, there are not translated properly inside smb.conf file. = When I read my smb.conf file, I noticed that for example a cp1252 characte= r like (0xC1) has been changed onto an ISO8859-15 character

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 can't, because internally, R is using 8 bit C strings, and the

Hello, I am trying to convert french characters into latin ones using inconv but I face some problems. Here is what I am doing in ruby console: >> $KCODE = ''u'' => "u" >> @x = ''x éèçà x'' => "x éèçà x" >> Iconv.new(''US-ASCII//TRANSLIT'', ''utf-8'').iconv @x => "x ???? x"

Hello, I am trying to get rsync-3.0.0pre10 --iconv option working between two linux hosts in local network. The client host is running Fedora Core 4 (kernel 2.6.17) and is using iso8859-1 character set. LANG=en_US The daemon host is running Centos 5 (kernel 2.6.18) and is using utf-8 character set. LANG=en_US.UTF-8 Rsync is transferring files properly without --iconv switch: fc4: (connected

Hi Yihui, list.files() returns file names converted to native encoding by Windows, so one needs to use only characters representable in current native encoding for file names. If one wants to be safe, it makes sense to be much stricter than that (only ASCII, and only a subset of it, there is a number of recommendations that can be found online). Using more than that is asking for trouble.

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

If I execute the code from the "?write.table" examples section x <- data.frame(a = I("a \" quote"), b = pi) # (ommited code) write.csv(x, file = "foo.csv", fileEncoding = "UTF-16LE") the resulting CSV file has a size of 6 bytes which is too short (truncated): """,3 The problem seems to be the iconv function:

Hi Tomas, Sorry for the false alarm! I did some further testing, and you were right. There was no regression. I suspected it was a regression because the user who reported the issue said his code worked in R 3.6 but not 4.0. I should have tested it more carefully by myself. After I tested it again with the German locale and Chinese locale, respectively, I found that the code worked for both

Hi, I'm having problem using rsync from an Ubuntu server to a Windows machine using cygwin and rsync. It works whenever I have a share name that doesn't include a special character like ?, ? or ?. My full command is: "rsync -avz -e 'ssh -p specialport' user at windowsmachine:/cygdrive/c/?test --iconv=CP1252,utf-8 (Also tride ISO8859-1 and utf-8)" I thought that iconv

Hi all, I hope that there is someone that can help me out here. I am trying to load() a workspace on os x (R 2.11.0) that was saved in windows XP (R 2.9). In that workspace, there's a data.frame with names that contain swedish characters. These characters become garbled, which is a major problem. >From the R windows FAQ, I read: "Note though that character data in a workspace will be