search for: uxxxx

...creased file by 50,957 bytes. preparing package March18 for lazy loading Loading required package: rcom Loading required package: RODBC Loading required package: RColorBrewer Loading required package: survival Loading required package: splines Error in parse(n = -1, file = file) : invalid \uxxxx sequence Calls: <Anonymous> -> code2LazyLoadDB -> sys.source -> parse Execution halted make: *** [lazyload] Error 1 *** Installation of March18 failed *** Removing 'C:/DOCUME~1/CHARLE~1/LOCALS~1/Temp/Rinst142800030/March18' While I can clearly read that the pro...

While preparing a function that contained non-ASCII characters for inclusion into a package, I replaced all non-ASCII characters with UTF-8 escape sequences (using \uxxxx) in order to make the package portable (and adhere to "R CMD check"). What I didn't expect: when one uses UTF-8 escape sequences in function arguments, one needs to use UTF-8 escape sequences when calling the function, too - even when working in a UTF-8 locale. Is this an intended...

...g 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 I've tried various setlocale options with no success (the Murrell/Ripley examples (Rnews 6/2) do work of course ... so I feel I should be able to do this myself, but after several hours it is time to ask for help)....

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...

...rmat. For those that do not (for example those lacking a powerful enough @code{iconv}), it is likely that they work in Latin-1, the old @R{} assumption. Then the parser can return a -UTF-8-encoded string if it encounters a @samp{\uxxx} escape for a +UTF-8-encoded string if it encounters a @samp{\uxxxx} escape for a Unicode point that cannot be represented in the current charset. (This needs MBCS support, and was only enabled at footnote{See define @code{USE_UTF8_IF_POSSIBLE} in file @file{src/main/gram.c}.} on -Windows.) This is enabled for all platforms, and a @samp{\uxxx} or +Windows.) T...

...e 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 don't exceed 00FF, so this works > text(locator(1),"\u00FF") or > text(locator(1),"\u00E6") and also without preceeding 00 > text(locator(1),"\uE6") Can someone give me a hint? I'm us...

Hello, My nt admin made a group for my samba server called Share_Dfsroot_pvcs-cdw_C and added me as a member. I made a nested group on my side with net rpc group add ntcdw -L -Uxxxxx I then added the Share_Dfsroot... with net rpc group addmem ntcdw "DOMAIN+Share_Dfsroot..." -Uxxxxx net rpc group members ntcdw -Uxxxx shows: DOMAIN\Share_Dfsroot... so all looks good. I then created on unix side a group called ntcdw and then tried to associate ntcdw (ntgroup...

Hi We have configured 2 PDC Samba (v3.0.33, sambapdc1 and sambapdc2) servers using LDAP (389 DS v1.2.5) as its database backend. If I run "net rpc user -UXXXX" from theses servers I get all groups in LDAP. These servers are working fine for a long time. Now I have configured a file server (not logon server, sambafs1), as a member of the domain served by those servers (this with v3.3.8). I have configured the LDAP client, so I can do "getent pa...

I'd like to write unicode strings using the "\u" escape syntax. According to the documentation, print.default or encodeString will escape unicode using the \u convention. In practice, I can't make it work. > b="Unicode character: \ufffd" > print.default(b) [1] "Unicode character: ?" > encodeString(b) [1] "Unicode character: ?" I want to

...n chosen as a good fit for infinity in Windows. In my scenario, the conversion is invoked by RGui before returning the input to the main R loop, even before the input gets to the parser. In principle, we could change this particular conversion in RGui to avoid the substitution. RGui uses "\uxxxx" escapes to pass characters that cannot be represented, this is why e.g. the Cyrillic Zhe \u0436 worked, so we could tell Windows not to do the substitution and pass "\u221e" for Infinity, and then the string after being processed by the parser will be represented in UTF-8 inside...

...c) > y <- parse(text=src)[[1]] > identical(x, y) [1] TRUE However this is suboptimal because it introduces a big performance overhead for large text. Several things are unclear to me: - Why does deparse() use a different escape notation than parse? Is there a way to make deparse output \uXXXX for unicode instead? - Why does deparse on windows escape this in the first place, and not keep the actual character when the locale supports it? > sessionInfo() R version 3.1.1 (2014-07-10) Platform: x86_64-w64-mingw32/x64 (64-bit) locale: [1] LC_COLLATE=English_United States.1252 [2] LC_CT...

...;U", x, fixed = TRUE) x <- gsub("\u009c", "\\\'u", x, fixed = TRUE) x } This function works fine for me if I source from a file, but if I try to include it into a package, the package cannot be installed: "Error in parse(n = -1, file = file) : invalid \uxxxx sequence (line 835)" (1) Why is there a difference between sourcing and package installation? (2) How can I fix this? (3) Perhaps there is a more reasonable way for doing this? I am using R_2.7.1. Hardware: Model Name: MacBook Model Identifier: MacBook2,1 Processor Name: Intel C...

...a "Windows Unicode" application (uses UTF16-LE) but it needs to convert the input to native encoding before passing it to R, which is based on locales. However, that string is passed by R to the parser, which Rgui takes advantage of and converts non-representable characters to their \uxxxx escapes which are understood by the parser. Using this trick, Unicode characters can get to the parser from Rgui (but of course then still in risk of conversion later when the program runs). Rgui only escapes characters that cannot be represented, unfortunately, the standard C99 API for that im...

I have Asterisk deliver all voice mail to users as email attachments. I found by accident that there is a limit of 99 messages in your INBOX in Asterisk. The 100th attempt to record a voice mail causes the system to play your greeting and then never record the 100th message and silently disconnect the caller. So...is it safe to simply use the UNIX find command to delete any files in the

Hello, There is a long-lasting problem with processing UTF-8 source code in R on Windows OS. As Windows do not have "UTF-8" locale and R passes source code through OS before executing it, some characters are "simplified" by the OS before processing, leading to undesirable changes. Minimalistic example: Let's type "?" (LATIN SMALL LETTER R WITH CARON) in RGui

...sing cache on failed catalog err: Could not retrieve catalog; skipping run I took a closer look and found the following error message at my "postgresql.log". 2012-03-15 11:15:01 CET FEHLER: ungültiges Unicode-Escape bei Zeichen 184 2012-03-15 11:15:01 CET TIPP: Unicode-Escapes müssen \uXXXX oder \UXXXXXXXX sein. 2012-03-15 11:15:01 CET ANWEISUNG: INSERT INTO "param_values" ("created_at", "line", "resource_id", "updated_at", "value", "param_name_id") VALUES(''2012-03-15 11:15:01.040833'', NULL, 154,...

...od fit for > infinity in Windows. In my scenario, the conversion is invoked by RGui > before returning the input to the main R loop, even before the input > gets to the parser. In principle, we could change this particular > conversion in RGui to avoid the substitution. RGui uses "\uxxxx" escapes > to pass characters that cannot be represented, this is why e.g. the > Cyrillic Zhe \u0436 worked, so we could tell Windows not to do the > substitution and pass "\u221e" for Infinity, and then the string after > being processed by the parser will be represented...

...pplication (uses UTF16-LE) but it needs to >> convert the input to native encoding before passing it to R, which is >> based on locales. However, that string is passed by R to the parser, >> which Rgui takes advantage of and converts non-representable characters >> to their \uxxxx escapes which are understood by the parser. Using this >> trick, Unicode characters can get to the parser from Rgui (but of course >> then still in risk of conversion later when the program runs). Rgui only >> escapes characters that cannot be represented, unfortunately, the >&...

...ed, LF and CR) should be used in code files. Other characters are accepted in comments, but then the comments may not be readable in e.g. a UTF-8 locale. Non-ASCII characters in object names will normally fail when the package is installed. Any byte will be allowed in a quoted character string but \uxxxx escapes should be used for non-ASCII characters. However, non-ASCII character strings may not be usable in some locales and may display incorrectly in others." Since comments are dropped by parse(), their actual content does not matter, and the rest of the code should be in ASCII. (*) It cou...

Consider: x <- list(`a b` = 1) x$a<tab> (i.e., press the 'tab' key after typing 'x$a') The auto-complete mechanism will fill the buffer like so: x$a b This is not particularly helpful because this is now a syntax error. It seems to me there's a simple fix -- in utils:::specialCompletions(), we can wrap the result of utils:::specialOpCompletionsHelper() with