Re: [Rd] Small encoding question

2008-02-14 Thread Prof Brian Ripley
Have you set R_ENCODING_LOCALES? That's how you tell R what locale to use for latin1 and UTF-8 when checking. Details in R-exts.texi. As it works for me in 'C' on Leopard with R-devel without setting this, I can't reproduce the problem to check if setting works. For l10n_info, it is asking

Re: [Rd] Small encoding question

2008-02-14 Thread Simon Urbanek
I think I found the cause, but fixing it may be more complicated (other than a hot fix for this particular case). What it boils down to is that the code for .check_package_code_syntax is trying to change the locale in a manner that doesn't work. In addition to that, the output of l10n_info()

Re: [Rd] Small encoding question

2008-02-14 Thread Prof Brian Ripley
On Thu, 14 Feb 2008, Simon Urbanek wrote: On Feb 14, 2008, at 2:45 PM, Kurt Hornik wrote: Vincent Goulet writes: Dear developeRs, Compilation of the latest version (0.9-5) of my actuar package fails with r-release MacOS_X ix86 on CRAN; see http://www.R-project.org/nosvn/R.check

Re: [Rd] Small encoding question

2008-02-14 Thread Simon Urbanek
On Feb 14, 2008, at 2:45 PM, Kurt Hornik wrote: >> Vincent Goulet writes: > >> Dear developeRs, >> Compilation of the latest version (0.9-5) of my actuar package fails >> with r-release MacOS_X ix86 on CRAN; see > >> >> http://www.R-project.org/nosvn/R.check/r-release-macosx-ix86/actuar

Re: [Rd] Small encoding question

2008-02-14 Thread Kurt Hornik
> Vincent Goulet writes: > Dear developeRs, > Compilation of the latest version (0.9-5) of my actuar package fails > with r-release MacOS_X ix86 on CRAN; see > > http://www.R-project.org/nosvn/R.check/r-release-macosx-ix86/actuar-00check.html > All errors come from accented letters

[Rd] Small encoding question

2008-02-14 Thread Vincent Goulet
Dear developeRs, Compilation of the latest version (0.9-5) of my actuar package fails with r-release MacOS_X ix86 on CRAN; see http://www.R-project.org/nosvn/R.check/r-release-macosx-ix86/actuar-00check.html All errors come from accented letters in comments in latin-1 encoded files