search for: u044f

..." # - words.1[214] should be "????????", as in corpus.file[14] # but it is "????????????????" # 2 entering Unicode characters into R: I want to search for, # say, "???". So I try to define it as follows, # but this doesn't work: (x123<-"\u0434\u043b\u044F") # I can define each individual character (x1<-"\u0434"); (x2<-"\u043b"); (x3<-"\u044F") # and each pair of character (x12<-"\u0434\u043b") (x13<-"\u0434\u044F") (x23<-"\u043b\u044F") # but not all three ... the...

...could be wrong) is that when you source a file, it first gets translated to your native locale and then parsed. When you parse a character vector, it does not get translated. In your locale, every "?" character (U+044F) gets replaced by the byte "\xFF": > iconv("\u044f", "UTF-8", "Windows-1251") [1] "\xff" I suspect that particular value causes trouble for the R parser, which uses a stack of previously-seen characters (include/Defn.h): LibExtern char R_ParseContext[PARSE_CONTEXT_SIZE] INI_as(""); And at various...

Hello, I do not have an account on R Bugzilla, so I will post my bug report here. I want to report a very old bug in base R *source()* function. It relates to sourcing some R scripts in UTF-8 encoding on Windows machines. For some reason if the UTF-8 script is containing cyrillic letter *"?"*, the script execution is interrupted directly on this letter (btw the same scripts are sourcing