R-hub has a debian-clang-devel platform now, with the same ISO-8859-15
locale, so you can easily reproduce this with
rhub::check(, platform = "debian-clang-devel")
To fix it, it is probably better to reproduce it locally, either via
rhub::local_check_linux(, image = "rhub/debian-clang-devel")
I think in R you can use
❯ l10n_info()
$MBCS
[1] TRUE
$`UTF-8`
[1] TRUE
$`Latin-1`
[1] FALSE
G.
On Thu, Apr 11, 2019 at 9:20 AM David Gohel wrote:
>
> Yes, it seems so.
>
> Thanks Gabor, if possible, a docker for that case would be welcome.
>
> I think I solved my issues. I set the locale in
Yes, it seems so.
Thanks Gabor, if possible, a docker for that case would be welcome.
I think I solved my issues. I set the locale in my cpp code:
setlocale(LC_NUMERIC, "C");
In the R code, I am testing if the locale is set to UTF-8 with the following
code but I am not sure this is the
I just got the CRAN ultimatum about a package of mine failing in that
locale, so yes, it definitely seems intentional.
Gabor
On Wed, Apr 10, 2019 at 3:33 PM Gábor Csárdi wrote:
>
> If the charset choice is intentional, then we can add a builder/docker
> image for this on R-hub.
>
> It would
If the charset choice is intentional, then we can add a builder/docker
image for this on R-hub.
It would certainly make sense to have a builder with an unusual charset.
Gabor
On Wed, Apr 10, 2019 at 11:43 AM David Gohel wrote:
>
> Dear all,
>
> Among the CRAN machines used by Check,
Dear all,
Among the CRAN machines used by Check, "r-devel-linux-x86_64-debian-clang" has
been upgraded from UTF-8 to ISO8859-15.
# using R Under development (unstable) (2019-04-07 r76333)
# using platform: x86_64-pc-linux-gnu (64-bit)
# using session charset: ISO8859-15
I realized that while
