[R-pkg-devel] Check Flavor r-devel-linux-x86_64-debian-clang charset

[David Gohel]

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 reading an error that appeared few days ago on a package 
I maintain:
https://cran.r-project.org/web/checks/check_results_fpeek.html 
<https://cran.r-project.org/web/checks/check_results_fpeek.html>

My question is not how to fix my error but about the setting. 

Does anyone know why and if that setting will stay as is?


Kind regards,
David Gohel


[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] Check Flavor r-devel-linux-x86_64-debian-clang charset

[David Gohel]

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 best solution: 

# Only when not windows
has_locale <- Sys.which("locale") != ""
is_utf_8 <- has_locale && (system(command = "locale charmap", intern = 
TRUE) == "UTF-8")

If someone has an advice, it will be welcomed :)



David Gohel



> Le 11 avr. 2019 à 10:04, Gábor Csárdi  a écrit :
> 
> 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 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, "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 reading an error that appeared few days ago on a 
>>> package I maintain:
>>> https://cran.r-project.org/web/checks/check_results_fpeek.html 
>>> <https://cran.r-project.org/web/checks/check_results_fpeek.html>
>>> 
>>> My question is not how to fix my error but about the setting.
>>> 
>>> Does anyone know why and if that setting will stay as is?
>>> 
>>> 
>>> Kind regards,
>>> David Gohel
>>> 
>>> 
>>>[[alternative HTML version deleted]]
>>> 
>>> __
>>> R-package-devel@r-project.org mailing list
>>> https://stat.ethz.ch/mailman/listinfo/r-package-devel


[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] Check Flavor r-devel-linux-x86_64-debian-clang charset

[David Gohel]

Thank you!

> Le 11 avr. 2019 à 10:36, Gábor Csárdi  a écrit :
> 
> 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 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 best solution:
>> 
>># Only when not windows
>>has_locale <- Sys.which("locale") != ""
>>    is_utf_8 <- has_locale && (system(command = "locale charmap", intern = 
>> TRUE) == "UTF-8")
>> 
>> If someone has an advice, it will be welcomed :)
>> 
>> 
>> 
>> David Gohel
>> 
>> 
>> 
>> Le 11 avr. 2019 à 10:04, Gábor Csárdi  a écrit :
>> 
>> 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 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, "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 reading an error that appeared few days ago on a 
>> package I maintain:
>> https://cran.r-project.org/web/checks/check_results_fpeek.html 
>> <https://cran.r-project.org/web/checks/check_results_fpeek.html>
>> 
>> My question is not how to fix my error but about the setting.
>> 
>> Does anyone know why and if that setting will stay as is?
>> 
>> 
>> Kind regards,
>> David Gohel
>> 
>> 
>>   [[alternative HTML version deleted]]
>> 
>> __
>> R-package-devel@r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-package-devel
>> 
>> 

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] Including fonts in an rmarkdown vignette

[David Gohel]

David

If you are ok to use one of the fonts available on google font, you could use 
package gfonts (in Suggests):
https://cran.r-project.org/web/packages/gfonts/vignettes/gfonts.html 


As it will be « inline », your document size could inflate (I guess it could be 
an issue with CRAN) - if only one font, size should be ok.

Otherwise, you also could add a css chunk to import the font from a public 
server - if no internet connexion, nothing will break.

David


> Le 3 juin 2020 à 08:46, Maëlle SALMON via R-package-devel 
>  a écrit :
> 
> Hi,
> 
> I've recently seen an example of a package that provides its own fonts for a 
> vignette. See links in 
> https://blog.r-hub.io/2020/06/03/vignettes/#pretty-vignettes 
> 
> 
> In that same post I link to a workaround I saw on this list 
> https://www.mail-archive.com/r-package-devel@r-project.org/msg02921.html for 
> changing the vignette format based on the versions of dependencies. Maybe 
> something similar is possible for fonts (I have no idea).
> 
> Maëlle.
> 
> Den tisdag 2 juni 2020 20:14:24 CEST, David Hugh-Jones 
>  skrev: 
> 
> 
> 
> 
> 
> Hi,
> 
> I'd like to build a rmarkdown vignette with my own choice of fonts – I'm
> pernickety about look and feel.
> 
> R CMD check will rebuild vignettes in the vignettes/ directory, and if
> relevant fonts aren't on the build machine, it'll give a warning.
> 
> Here are the options I can think of:
> * build vignettes on my machine and put them in inst/doc. Don't mention the
> specific fonts in the Rmd file in vignettes/. So the file built by "R CMD
> check" won't look quite like the pre-built version.  This might work, but
> it seems against open source principle.
> * put font files in vignettes/ and refer to them in the rmarkdown file. I'm
> not sure how to do this.
> * limit myself to the fonts preinstalled on win-builder or CRAN machines.
> I'm not sure what these are
> 
> Has anyone got any advice or examples?
> 
> Cheers,
> David
> 
> [[alternative HTML version deleted]]
> 
> __
> R-package-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel
> 
> __
> R-package-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel


[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] gcc-san check warns for non-portable flags

[David Gohel]

I had the same this week.

Yes, you should answer these are false negative results.

KR,
David

De : R-package-devel  de la part de 
Pepijn de Vries 
Date : vendredi, 10 janvier 2025 � 18:00
� : Ivan Krylov via R-package-devel 
Objet : [R-pkg-devel] gcc-san check warns for non-portable flags
Dear fellow package developers,

There were multiple issues with a package I maintain: @CRAN: 
 @source: 
. As far as I can tell all 
issues listed @CRAN were fixed in the latest version (available from GitHub and 
R-Universe). However, when submitting to CRAN, the special gcc san check 
complains about non-portable flags (see below).

I cannot reproduce this warning myself. As far as I can tell, I don't set these 
flags myself (neither in the configure script nor in makevars.in). I suspect 
that these flags are set by the machine that performs the checks. How do I pass 
this check? Or should I report it to CRAN as a false negative result?

Many thanks for your help.

Kind regards,

Pepijn

> Flavor: r-devel-windows-x86_64, r-devel-linux-x86_64-debian-special-clang-san
> Check: *, Result: OK
>
> Flavor: r-devel-linux-x86_64-debian-special-gcc-san
> Check: compilation flags used, Result: WARNING
>  Compilation used the following non-portable flag(s):
> '-Wno-deprecated-declarations' '-Wno-ignored-attributes'
> '-Wno-stringop-truncation'
>   including flag(s) suppressing warnings

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel