That might also be reporting something that can be felt like a brittle
aspect of R when embedded.
I am very tempted to ask why enforcing LC_NUMERIC to "C" for the
whole process while this only concerns numerical values written into
"data" files. I am understanding that at least postscript/pdf file
You start from a false premise, and it seems that you are reporting a
serious bug in Rpy to the wrong list:
Note that R expects to be run with the locale category `LC_NUMERIC' set
to its default value of C, and so should not be embedded into an
application which changes that.
('Writing R
Thanks for the quick answer.
The documentation for Sys.setlocale mentions the possibility of warning
when LC_NUMERIC is set.
After checking it is looking like setting LC_NUMERIC from Sys.setlocale
does issue a warning, but there is does not seem to be a warning when
LC_NUMERIC is set in the paren
On Fri, 14 Nov 2008, laurent wrote:
Dear list,
A problem with creating pdf or postscript plots from an embedded R, and
in an environment where a locale is defined, was recently reported on
the rpy (Python->R interface) mailing list.
The problem appears to be that whenever the locale defines ',
Dear list,
A problem with creating pdf or postscript plots from an embedded R, and
in an environment where a locale is defined, was recently reported on
the rpy (Python->R interface) mailing list.
The problem appears to be that whenever the locale defines ',' as a
separator for the decimal part o
