But, this is already dealt with in 2.5.1 patched ...
On Sat, 30 Jun 2007, Petr Savicky wrote:
> On Wed, Jun 27, 2007 at 04:20:39PM +0100, Prof Brian Ripley wrote:
>> But you can't really avoid it if you want to test non-ASCII
>> features: for example, you cannot test Latin-1 graphics in a C local
On Wed, Jun 27, 2007 at 04:20:39PM +0100, Prof Brian Ripley wrote:
> But you can't really avoid it if you want to test non-ASCII
> features: for example, you cannot test Latin-1 graphics in a C locale.
>
> It was intended that the postscript device opened for testing graphics was
> opened with en
On Wed, 27 Jun 2007, Peter Dalgaard wrote:
> Prof Brian Ripley wrote:
>> But R 2.5.0 does the same, and as far as I know R has done so for many
>> past versions.
>>
>> You are asking the impossible: outputting Latin-1 in a Latin-2
>> environment. Remember that postscript() does not handle UTF-8,
Prof Brian Ripley wrote:
> But R 2.5.0 does the same, and as far as I know R has done so for many
> past versions.
>
> You are asking the impossible: outputting Latin-1 in a Latin-2
> environment. Remember that postscript() does not handle UTF-8, and so
> uses whatever it thinks the local 8-bit
But R 2.5.0 does the same, and as far as I know R has done so for many
past versions.
You are asking the impossible: outputting Latin-1 in a Latin-2
environment. Remember that postscript() does not handle UTF-8, and so
uses whatever it thinks the local 8-bit encoding is, in your case
either
configure and make run OK, but make check failed
for R version 2.5.1 RC (2007-06-26 r42068) on graphics with error:
> ## The following two examples use latin1 characters: these may not
> ## appear correctly (or be omitted entirely).
> plot(1:10, 1:10, main = "text(...) examples\n
