for each function thoroughly and
carefully.
Tomas
On Thu, Apr 11, 2019 at 9:54 AM Tomas Kalibera wrote:
>
> On 4/11/19 9:10 AM, Tomáš Bořil wrote:
> > Or, if this cannot be done easily, please, disable the "utf-8" value
> > in source(..., ) function on Windows R.
>
;best fit" on Windows
and some characters in string literals may be automatically changed.
Because, at this state, the UTF-8 encoding of R source files on
Windows is a fake Unicode as it can handle only 256 different ANSI
characters in reality.
Thanks,
Tomas
On Thu, Apr 11, 2019 at 8:53 AM
For me, this would be a perfect solution.
I.e., do not use the “best” fit and leave it to user’s competence:
a) in some functions, utf-8 works
b) in others -> error is thrown (e.g., incomplete string, NA, etc.)
=> user has to change the code with his/her intentional “best fit string
literal
>> executing the function. Instead of that, I have to explicitly type
>> "\U00159" throughout my code.
On Wed, Apr 10, 2019 at 5:29 PM Tomas Kalibera wrote:
>
> On 4/10/19 3:02 PM, Tomáš Bořil wrote:
> > The thing is, I would rather prefer R (in that rare occas
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
