ed. As long
>>>> as you are using UTF-8 strings representable in the current encoding, so
>>>> that they can be converted to native encoding and back without problems,
>>>> you are fine, R will do the conversions as needed. The troubles come when
>>>>
for real).
>>>> Specifically with
>>>> "mathotString", you might try creating an example
>>>> that does not include
>>>> any package (just calls to parse with encoding
>>>>
gt;>>> If you find behavior re encodings in released versions of R that
>>>> contradicts the current documentation, please report with a minimal
>>>> reproducible example, such cases should be fixed (even though sometimes
>>>> the "fix" would be
s in native encoding the
>>> most straightforward way of loading this literal strings
>>> would be in UTF-8.
>>
>> You mean the memory representation? For that there would be R
>> In
supports parsing and loading a package
>> encoded with UTF-8 and it supports having UTF-8 strings in memory next to
>> strings in native encoding the most straightforward way of loading this
>> literal strings would be in UTF-8.
>>
>> You mean the memory
specially if you are working with
> characters representable in the current encoding, there should be
> no problem.
>
> It depends on if I now understand ?parse correctly in that it should
> have the strings in a package that is parsed with the specified
sentable in the current encoding, there should be no problem.
>
It depends on if I now understand ?parse correctly in that it should have
the strings in a package that is parsed with the specified encoding in that
encoding or not. As I wondered above.
> I would love to use the new versi
ecome
stable.
Best
Tomas
> Cheers,
> Joris
>
>
> Best,
> Tomas
>
> [1]
>
> https://developer.r-project.org/Blog/public/2020/07/30/windows/utf-8-build-of-r-and-cran-packages/index.html
>
> >
> > Cheers,
> > Joris
>
> &g
o be stored in memory. But it just seems
> logical to me that if R already supports parsing and loading a package
> encoded with UTF-8 and it supports having UTF-8 strings in memory next to
> strings in native encoding the most straightforward way of loading this
> literal strings would be in UTF-8.
>
>
> Cheers,
> > Joris
>
> >
> >
> > On Wed, 16 Dec 2020 at 20:15, David Bosak wrote:
> >
> >> Joris:
> >>
> >>
> >>
> >> I’ve fought with encoding problems on Windows a lot. Here are some
> >> general suggesti
a more specific problem, please describe and we can try to
help.
David
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
Windows 10
*From: *jo...@jorisgoosen.nl
*Sent: *Wednesday, December 16, 2020 1:52 PM
*To: *r-package-devel@r-project.org
*Subject: *[R-pkg-devel]
;3. This post:
>https://kevinushey.github.io/blog/2018/02/21/string-encoding-and-r/
>
>
>
> If you have a more specific problem, please describe and we can try to
> help.
>
>
>
> David
>
>
>
> Sent from Mail <https://go.microsoft.com/fwl
Hello All,
Some context, I am one of the programmers of a software pkg (
https://jasp-stats.org/) that uses an embedded instance of R to do
statistics. And make that a bit easier for people who are intimidated by R
or like to have something more GUI oriented.
We have been working on translating
13 matches
Mail list logo
