Right, thanks for the tip.
For future reference: if you want to avoid this warning, but still use
examples with unicode, you can put the unicode text data in
inst/extdata/file_with_unicode.txt and then in your example code you can
read it via
readLines(system.file("extdata", "file_with_unicode.tx
On 9/25/19 7:59 PM, Toby Hocking wrote:
> Hi Tomas thanks for the explanation. Does that mean that there is no
> known fix? i.e. it is OK to re-submit a new version of my package
> without fixing these WARNINGS?
One way to fix would be to remove non-ASCII characters from the
examples. I see \u4
Hi Tomas thanks for the explanation. Does that mean that there is no known
fix? i.e. it is OK to re-submit a new version of my package without fixing
these WARNINGS?
On Tue, Sep 24, 2019 at 1:38 AM Tomas Kalibera
wrote:
> On 9/24/19 1:57 AM, Toby Hocking wrote:
> > Hi all,
> >
> > is there a kno
On 9/24/19 1:57 AM, Toby Hocking wrote:
Hi all,
is there a known fix for this WARNING which I am getting on solaris for my
newly submitted nc package?
https://www.r-project.org/nosvn/R.check/r-patched-solaris-x86/nc-00check.html
It seems that deparse() came across some non-printable characters
Hi all,
is there a known fix for this WARNING which I am getting on solaris for my
newly submitted nc package?
https://www.r-project.org/nosvn/R.check/r-patched-solaris-x86/nc-00check.html
A quick google search for "it is not known that wchar_t is Unicode on this
platform cran" shows that many ot
