Windows Notepad prefixes UTF-8 files with a Byte Order Mark (\UFEFF).
Per https://en.wikipedia.org/wiki/Byte_order_mark, this is permitted in
UTF-8, but not required.
I suppose that there are other Windows programs which do likewise (in
addition to Excel and Notepad).
"The Unicode Standard permits
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
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 wrote:
>
> This doesn't seem to be happening on MacOS, neither in Terminal nor RStudio,
> (R 3.5.1, R-devel, R-patched). So prob
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 2019, at 11:17 , David Byrne wrote:
>
> Bug
> Using read.table(file, encoding="UTF-8") to import a UTF-8 encoded
> file containing the infin
Bug
Using read.table(file, encoding="UTF-8") to import a UTF-8 encoded
file containing the infinity symbol (' ∞ ') results in the infinity
symbol imported as the number 8. Other Unicode characters seem
unaffected, example, Zhe: ж
Expected Behavior:
The imported data.frame should represent the infi
Doesn't Rtools provide everything needed to build R packages and R on
Windows - including gcc?
Am Sa., 2. Feb. 2019 um 22:29 Uhr schrieb Abs Spurdle :
> Creating an .exe file isn't necessarily difficult.
> The main problems are that you have to write and compile the C (or other)
> files.
> Otherw
