[Rd] Versioning Rtools ARP entries

2023-03-13 Thread Daniel Possenriede
Hi, If I am not mistaken, all Rtools 4.2 (and 4.3) revisions have the same ARP [1] entries, i.e. all report version 4.2.0.1 (or 4.3.0.1). This makes it difficult to determine the installed version (is it possible to determine the installed revision?) and impossible for tools like winget [2] to upd

Re: [Rd] Bug Report: read.table with UTF-8 encoded file imports infinity symbol as Integer 8

2019-02-08 Thread Daniel Possenriede
indows API to use > Unicode and have all strings in UTF-8 in R, we would still have problems > when interfacing with packages that assume strings are in current native > encoding (without checking), so this problem won't be easy to fix. > > Best, > Tomas > > On 2/7/19 3:10

Re: [Rd] Bug Report: read.table with UTF-8 encoded file imports infinity symbol as Integer 8

2019-02-07 Thread Daniel Possenriede
There seems to be something odd with "∞" on Windows (and not only with read.table) In native encoding (cp-1252 in my case), "∞" gets converted to "8" x <- "∞" Encoding(x) #> [1] "unknown" print(x) #> [1] "8" charToRaw(x) #> [1] 38 "∞" is indeed "8" identical(x, "8") #> [1] TRUE Everything seem

Re: [Rd] special latin1 do not print as glyphs in current devel on windows

2017-09-14 Thread Daniel Possenriede
This is a follow-up on my initial posts regarding character encodings on Windows (https://stat.ethz.ch/pipermail/r-devel/2017-August/074728.html) and Patrick Perry's reply (https://stat.ethz.ch/pipermail/r-devel/2017-August/074830.html) in particular (thank you for the links and the bug report!

Re: [Rd] special latin1 do not print as glyphs in current devel on windows

2017-08-01 Thread Daniel Possenriede
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 her

Re: [Rd] special latin1 do not print as glyphs in current devel on windows

2017-08-01 Thread Daniel Possenriede
Sorry, I should have included my console output, obviously. So here we go: Wrong UTF-8 escapes with using print in v3.5.0 devel: # R Under development (unstable) (2017-07-30 r73000) -- "Unsuffered Consequences" # Platform: x86_64-w64-mingw32/x64 (64-bit) > x <- c("€", "–", "‰") > Encoding(x) [1]

Re: [Rd] special latin1 do not print as glyphs in current devel on windows

2017-08-01 Thread Daniel Possenriede
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 la

[Rd] special latin1 do not print as glyphs in current devel on windows

2017-07-31 Thread Daniel Possenriede
Sorry, if I am spamming/not using the right list, but I think I might be onto a regression in current devel. Namely, special (non-ASCII) characters with latin1 encoding do not get printed as glyphs with R 3.5.0 devel but were with R 3.4.1. This output is from # R version 3.4.1 (2017-06-30) -- "S