Displaying 10 results from an estimated 10 matches for "possenriede".
2017 Sep 14
2
special latin1 do not print as glyphs in current devel on windows
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!). My initial
posts were quite chaotic (and partly wrong), so I am trying to clear
things up a
2017 Sep 14
0
special latin1 do not print as glyphs in current devel on windows
...else localeCP = 0;
/* Not 100% correct, but CP1252 is a superset */
known_to_be_latin1 = latin1locale = (localeCP == 1252);
}
#endif
The "1252" should be "28591"; see
https://msdn.microsoft.com/en-us/library/windows/desktop/dd317756(v=vs.85).aspx
.
> Daniel Possenriede <mailto:possenriede at gmail.com>
> September 14, 2017 at 3:40 AM
> 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....
2019 Feb 08
3
Bug Report: read.table with UTF-8 encoded file imports infinity symbol as Integer 8
...inciple all calls to Windows 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 PM, Daniel Possenriede wrote:
> 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...
2019 Feb 07
3
Bug Report: read.table with UTF-8 encoded file imports infinity symbol as Integer 8
I can confirm that it doesn't happen on Ubuntu 18.04.1 so Peter is
most likely correct; it looks like its Windows specific.
On Thu, 7 Feb 2019 at 12:55, peter dalgaard <pdalgd at gmail.com> wrote:
>
> This doesn't seem to be happening on MacOS, neither in Terminal nor RStudio, (R 3.5.1, R-devel, R-patched). So probably Windows specific.
>
> -pd
>
> > On 7 Feb
2017 Aug 01
0
special latin1 do not print as glyphs in current devel on windows
...output on your system, we have no idea what you saw.
[As a convenience to Windows users, R does in some cases assume that
they are using Latin-1 encodings. If they use extensions to Latin-1 then
there are no guarantees that code written for strict Latin-1 will work.]
On 01/08/2017 10:19, Daniel Possenriede wrote:
> 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)
>
&...
2023 Mar 13
1
Versioning Rtools ARP entries
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 update Rtools to the latest revision, AFAICT.
Would it be possible to track the version in the
2017 Aug 01
2
special latin1 do not print as glyphs in current devel on windows
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 here, mostly because
Encoding() is reporting the encoding as "latin1". You presumed correctly
2017 Aug 01
3
special latin1 do not print as glyphs in current devel on windows
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 latin1/cp1252 escapes here, but
2019 Feb 08
0
Bug Report: read.table with UTF-8 encoded file imports infinity symbol as Integer 8
...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 PM, Daniel Possenriede wrote:
> > 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)
> > #> [...
2019 Feb 07
0
Bug Report: read.table with UTF-8 encoded file imports infinity symbol as Integer 8
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