similar to: invalid \uxxxx sequence while trying to create a package

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

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

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

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

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

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

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

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

I can reproduce this behavior on my Windows 10 system in RGui (cp1252): when I paste the Unicode infinity symbol into the console, it is treated as number 8. This is caused by Windows "best fit" default behavior in conversion of unicode characters to characters in the current native encoding: at some point in the past, 8 has been chosen as a good fit for infinity in Windows. In my

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

On 4/10/19 6:32 PM, Jeroen Ooms wrote: > On Wed, Apr 10, 2019 at 5:45 PM Duncan Murdoch <murdoch.duncan at gmail.com> wrote: >> On 10/04/2019 10:29 a.m., Yihui Xie wrote: >>> Since it is "technically easy" to disable the best fit conversion and >>> the best fit is rarely good, how about providing an option for >>> code/package authors to disable

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

Dear list, I am trying to replace Unicode notation of German and Spanish special characters (as read in by read.csv from excel spreadsheets) by character strings that can be interpreted by LaTeX. E.g.: uni2latex <- function(x){ x <- gsub("&", "et", x, fixed = TRUE) # Deutsch x <- gsub("\u0080", "\\\"A", x, fixed = TRUE) x

I am developping a package (pgirmess) that since long does not go through CRAN MacOSX checks, just because I have this command in one of the examples. text(mydata[,3],mydata[,4],paste(round(dirs,0),"?"),cex=0.7) It makes: <ERROR: re-encoding failure from encoding 'latin1'> text(mydata[,3],mydata[,4],paste(round(dirs,0),"+ + + + cleanEx() +

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

Hello, i have a problem with stored configs since the migration from "sqlite" to "postgresql". dho@appelbaum:~$ sudo puppetd --test --verbose info: Retrieving plugin info: Loading facts in disks info: Loading facts in users info: Loading facts in mountpoints info: Loading facts in disks info: Loading facts in users info: Loading facts in mountpoints err: Could not retrieve

Or, if this cannot be done easily, please, disable the "utf-8" value in source(..., ) function on Windows R. source(..., encoding = "utf-8") -> error: "utf-8" does not work right on Windows. -> (or, at least) warning: "utf-8" is handled by "best fit" on Windows and some characters in string literals may be automatically changed. Because, at

SUGGESTION: Would it make sense if install.packages() and friends always use an "ascii"(*) encoding when parse():ing R package source code files? I believe this should be safe, because R code files should be in ASCII [http://en.wikipedia.org/wiki/ASCII] and only in source-code comments you may use other characters. This is from Section 'Package subdirectories' in 'Writing R

On Mon, 1 Jan 2024 01:09:47 -0600 cha charle via samba <samba at lists.samba.org> wrote: > Hi, > I have setup Samba in Raspberry Pi, and am able to connect to > "PiShare" (/home/charles/share) without any problems; however, > somehow I can't connect to "entertainment" (/media/usb-drive/music), > which is on an external usb hard drive. I have tried

It is using NTFS.Thanks. On Mon, Jan 1, 2024 at 2:39?AM Rowland Penny via samba < samba at lists.samba.org> wrote: > On Mon, 1 Jan 2024 01:09:47 -0600 > cha charle via samba <samba at lists.samba.org> wrote: > > > Hi, > > I have setup Samba in Raspberry Pi, and am able to connect to > > "PiShare" (/home/charles/share) without any problems;