[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: encoding for PostScript output

From: Klaus Straubinger
Subject: Re: encoding for PostScript output
Date: Tue, 7 Dec 2004 13:16:50 +0100 (CET)

Hello Werner,

>> DESCRIPTION OF INCORRECT BEHAVIOUR: Requesting PostScript output for
>> a file with input characters « (guillemotleft) or » (guillemotright)
>> leads to a mapping of these characters to the wrong output
>> characters.
> Example file, please.  I can't reproduce that.  Selecting PS output
> automatically loads the file `latin1.tmac' which sets up the proper
> input encoding.

Essential for reproducing the problem seem to be the locale settings.
As can be seen in the example file, it is in the ISO-8859-1 encoding,
and the error occurs only if groff is called in an ISO-8859-1 locale,
in my case with LANG=de_DE.ISO-8859-1. The error can also be seen when
putting the file into UTF-8 encoding and running groff in the
de_DE.UTF-8 locale.

As far as I understand latin1.tmac, it redefines the special characters
if they are not already available. But this purpose gets defeated when
using a file encoded according to the locale groff is running in
because then the characters are already defined.

By the way, if the text in the file starts with a guillemet character,
troff core dumps, but that is another bug, isn't it?


Attachment: test.ms
Description: test file

reply via email to

[Prev in Thread] Current Thread [Next in Thread]