similar to: Writing escaped unicode

Duncan Murdoch <murdoch.duncan at gmail.com> writes: > users of other languages may want to have messages and variable names > in their native language, and ASCII might not be enough for that. Allowing for messages in non-ASCII encodings would probably be a good idea, but I think allowing non-ASCII variable names is dangerous. -- Regards, Bj?rn-Helge Mevik

Hi, In the R console, I have the following: > runif(10) Error in runif(10) : '.Random.seed' is not an integer vector but of type 'list' > Can someone advise me of the solution of the problem? Mei-Yuan Chen Department of Finance NCHU, aiwan

Dear all, Is there a quick and easy way of converting utf characters to the \uxxxx form (necessary e.g. for packages)? I mean something working like this: > utf2uxxxx("õäöü") [1] "\u00f5\u00e4\u00f6\u00fc" It is easy to program but perhaps someone already has implemented this. (I couldn't find anything useful from searches incl RSiteSearch). Thanks in advance, Kenn

Sorry, I should have been more clear -- if I write the contents of that script to a file called 'encoding.R' and source that, then I see the reported behavior. Here's something standalone that you should hopefully be able to copy + paste into RGui to reproduce: code <- ' x <- 1 print(list()) save(x, file = tempfile()) output <- encodeString("apple")

Fixed in R-devel and R-patched, Tomas On 07/18/2018 12:03 PM, Tomas Kalibera wrote: > Thanks, I can now reproduce and it is a bug that is easy to fix, I > will do so shortly. > > Fyi it can be reproduced simply by running these two lines in Rgui: > > list() > encodeString("apple") > > Best > Tomas > > On 07/17/2018 05:16 PM, Kevin Ushey wrote:

What is the inverse of encodeString? For example, \u1 is some Unicode symbol. If I do s <- encodeString("\u1") then s will be the string "\001". But anything I do with s, will not return the Unicode that corresponds to \u1: cat(s, "\n") # prints \001 cat("\u1", "\n") # prints y with umlaut Alberto Monteiro

Given the following R script: x <- 1 print(list()) save(x, file = tempfile()) output <- encodeString("apple") print(output) If I source this script from RGui on Windows, I see the output: > source("encoding.R") list() [1] "\002??apple\003??" That is, it's as though R has injected what looks like byte order marks around the

I have some comment text taken from a SAS data file. It is stored in two vectors and is difficult to read. I would like to simply concatentate the individual entries and end up with a character vector that give me one line of text per comment. I cannot see how to do this, yet it must be very easy. I have played around with cat() and print with no success. Would someone kindly point out where I

I'm writing a script which puts together a bunch of graphs and outputs them to a graphics device. One of the things I want to add is ANOVA summaries but I'm having trouble with formatting them for graphics. I do this: anova_summary <- summary(aov(concentration~inhibition*genotype, data =drug_data)) print(anova_summary) The printout to the R console is in the format I want but if I

In what way is this a bug in R? It looks like a bug in the package, and as Defn.h is not part of R's API any packge using it is `at risk' (and cannot be installed in a binary-only installation, or even an installed version of R). In particular, Defn,.h depends on config.h, and it seems you installed a binary version of R and used separate sources. I would suggest building R from

Hello, Peter, I tried it out: iconv(names(attributes(spss[,'Y6'])[[1]][14]), "UTF-8", "LATIN1", sub='byte') yielded [1] "<c4>rzte Chirurgie" and c4 corresponds in most encodings to ?. What can I do next? I wonder whether there is a more comfortable way then to change the occurences of <..> by the adequate character. Regards, Matthias

Thanks, I can now reproduce and it is a bug that is easy to fix, I will do so shortly. Fyi it can be reproduced simply by running these two lines in Rgui: list() encodeString("apple") Best Tomas On 07/17/2018 05:16 PM, Kevin Ushey wrote: > Sorry, I should have been more clear -- if I write the contents of > that script to a file called 'encoding.R' and source that,

Greetings, R-Helpers: I am trying to build a package on WinXP, something that I have done before, but infrequently, and have recently updated both the Rtools and the version of R being used. My test case fails after successfully creating the compiled html files with this error message: . . . Created c:\DOCUME~1\CHARLE~1\LOCALS~1\Temp\Rbuild142865646\March18\chm\March18.chm, 41,494

Colleagues, I am using R to assemble RTF documents (which are plain text). I need to embed a JPEG graphic that was created with R. I presume that the steps need to be: a. read the file into R b. convert the object to HEX format c. write the converted object to a textfile. If I read the file into R using readLines, I get the following (only the first 5 lines shown): > >

This is a little off topic, but maybe someone can help. I have a Win2K laptop that's part of a corporate domain. When I bring it home and add it to my home LAN, it refuses to access any SMB machine (including a Samba server, Win98 or Win95 box) complaining that "There are currently no logon servers available to service the logon request." Is there any way to fix this easily? I

Hi I've imported an spss-file using read.spss. One variable has value like '?rzte'. I thought this is UTF-8 encoded, but it is not (as the results of iconv and utf8ToInt suggest). Is there any way to find out how these spss-values are encoded? Regards, Matthias

In both R and JSON (and many other languages), unicode characters can be escaped using a backslash followed by a lowercase "u" and a 4 digit hex code. However when deparsing a character vector in R on Windows, the non-latin characters get escaped as "<U+" followed by their 4 digit hex code and ">": > x <- "I like \u5BFF\u53F8" > cat(x) I like

I'm trying to use the biological female and male signs in R2.5.1 under Windows XP. I can access and insert these symbols using word-processors. In general these should be available as \u2640 and \u2642 but I can't make them happen in R using (say) text(5,5, "\u2640") message "invalid \uxxxx sequence" I've replaced Arial with Arial unicode MS in Rdevga and

On Fri, Dec 12, 2014 at 06:01:22AM -0500, Duncan Murdoch wrote: > On 12/12/2014, 4:12 AM, Bj??rn-Helge Mevik wrote: > > Duncan Murdoch <murdoch.duncan at gmail.com> writes: > > > >> users of other languages may want to have messages and variable names > >> in their native language, and ASCII might not be enough for that. > > > > Allowing for

Dear R-users, Just like other users (as seen from previous posts on the list), I would like to use female and male signs in plots. I found B. Ripley's post about using Unicode characters. However, it doesn't works for me. > text(locator(1),"\u2640") produces the following error: Error: invalid \uxxxx sequence But I can specify other Unicode characters as long I