> Wouldn't the obvious thing be to not use an r string here?
"Obvious" in terms of keeping RCMD CHECK happy, certainly, but it'd be
antithetical to clear code--- the string I included in the post would become
incomprehensible to the maintainer (me).
IME raw strings in R are under-appreciated
I'd prefer a change that said that R and NAMESPACE files must contain
UTF-8, rather than an exception for raw strings. ASCII is a subset, so
any package that is currently compliant would still be compliant.
Duncan Murdoch
On 2025-11-29 5:55 a.m., Mark Bravington wrote:
Hi--- My package 'lyxp
Wouldn't the obvious thing be to not use an r string here? Using r strings does
not imply the use of non-ascii characters (AFAIK they are intended for regex
patterns), and using regular strings does not imply you cannot use Unicode
(with \u).
At some point I would think that accepting Unico
Hi--- My package 'lyxport' has R code with several raw strings (see ?Quotes)
which contain UTF-8 characters (FWIW: in order to deal with wacky legacy Latex
characters). For example, one of the strings is:
converto <- r"--{
Ä \"A ä \"a Á \'A á \'a Ȧ \.A ȧ \.a Ā \=A
ā
