Details Ticket 5195


Comment | Reply | Take | Open


Serial Number 5195
Subject ps.map sets encoding to iso-8859-1
Area grass6
Queue grass
Requestors mlennert@club.worldonline.be
Owner none
Status resolved
Last User Contact Fri Oct 13 00:57:41 2006 (2 yr ago)
Current Priority 30
Final Priority 70
Due No date assigned
Last Action Wed Nov 15 15:29:07 2006 (2 yr ago)
Created Mon Oct 9 16:29:30 2006 (2 yr ago)

Transaction History Ticket 5195


Mon, Oct 9 2006 16:29:30    Request created by guest  
Subject: ps.map sets encoding to iso-8859-1

Platform: GNU/Linux/x86
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: cvs_head_20060921

On line 92 of ps/ps.map/prolog.ps the encoding is set to ISOLatin1Encoding.
If I understand correctly (and some testing confirms this) this means that the
instructions file for ps.map has to be encoded in iso-8859-1 (or similar) to
work, i.e. to be able to print accented characters. If you are in a UTF-8 environment,
ps.map creates a ps file which doesn't show correct accented characters be it
in iso or in utf.

Is there any reason why ps.map hardcodes the encoding ? Is it possible to automatically
use the users encoding ?

Moritz
Tue, Oct 10 2006 05:45:58    Mail sent by glynn@gclements.plus.com  
Return-Path <glynn@gclements.plus.com>
Delivered-To grass-bugs@lists.intevation.de
From Glynn Clements <glynn@gclements.plus.com>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Transfer-Encoding 7bit
Message-ID <17707.5998.511987.172468@cerise.gclements.plus.com>
Date Tue, 10 Oct 2006 04:45:50 +0100
To Request Tracker <grass-bugs@intevation.de>
Cc grass-dev@grass.itc.it
Subject Re: [GRASS-dev] [bug #5195] (grass) ps.map sets encoding to iso-8859-1
In-Reply-To <20061009142930.818711006B8@lists.intevation.de>
References <20061009142930.818711006B8@lists.intevation.de>
X-Mailer VM 7.07 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Request Tracker wrote:

> this bug's URL: http://intevation.de/rt/webrt?serial_num=5195
> -------------------------------------------------------------------------
> 
> Subject: ps.map sets encoding to iso-8859-1
> 
> Platform: GNU/Linux/x86
> grass obtained from: CVS
> grass binary for platform: Compiled from Sources
> GRASS Version: cvs_head_20060921
> 
> On line 92 of ps/ps.map/prolog.ps the encoding is set to ISOLatin1Encoding.
> 
> If I understand correctly (and some testing confirms this) this
> means that the instructions file for ps.map has to be encoded in
> iso-8859-1 (or similar) to work, i.e. to be able to print accented
> characters. If you are in a UTF-8 environment, ps.map creates a ps
> file which doesn't show correct accented characters be it in iso or
> in utf.
> 
> Is there any reason why ps.map hardcodes the encoding ? Is it
> possible to automatically use the users encoding ?

The reason why we force the font's encoding to ISOLatin1Encoding is
that the default encoding for most Latin fonts is StandardEncoding,
which (contrary to its name) is a completely non-standard encoding
which (AFAICT) is not used by anything except PostScript.

The value of the Encoding property is an array of 256 glyph names, so
you can use any unibyte encoding (e.g. ISO-646-*, ISO-8859-*,
windows-12?? etc).

If you want to support more complex encodings, you need to use
CID-keyed fonts. Apart from being rather complex, CID-keyed fonts may
not be supported by PostScript printers sold outside of South-East
Asia.

In short, allowing the encoding to be changed to other unibyte
encodings is simple enough. Anything else will require a willing
volunteer (i.e. not me), and will need to be implemented in such a way
that users don't end up accidentally producing documents which show up
fine in (recent versions of) Ghostscript but which will be rejected by
every PostScript printer on this half of the planet.

-- 
Glynn Clements <glynn@gclements.plus.com>


Tue, Oct 10 2006 07:03:40    Mail sent by hamish_nospam@yahoo.com  
Return-Path <hamish_nospam@yahoo.com>
Delivered-To grass-bugs@lists.intevation.de
Date Tue, 10 Oct 2006 18:03:29 +1300
From Hamish <hamish_nospam@yahoo.com>
To grass-dev@grass.itc.it
Cc grass-bugs@intevation.de
Subject Re: [GRASS-dev] [bug #5195] (grass) ps.map sets encoding to iso-8859-1
Message-Id <20061010180329.50a9e027.hamish_nospam@yahoo.com>
In-Reply-To <17707.5998.511987.172468@cerise.gclements.plus.com>
References <20061009142930.818711006B8@lists.intevation.de> <17707.5998.511987.172468@cerise.gclements.plus.com>
X-Mailer Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu)
X-Face M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk!HT&BB 8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
Mime-Version 1.0
Content-Type text/plain; charset=US-ASCII
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-2.3 tagged_above=-999 required=3 tests=[BAYES_00=-5, FORGED_YAHOO_RCVD=2.7]
X-Spam-Level
> Request Tracker wrote:
> > this bug's URL: http://intevation.de/rt/webrt?serial_num=5195
> > -------------------------------------------------------------------
> >
> > Subject: ps.map sets encoding to iso-8859-1
..
> > On line 92 of ps/ps.map/prolog.ps the encoding is set to
> > ISOLatin1Encoding.
> > 
> > If I understand correctly (and some testing confirms this) this
> > means that the instructions file for ps.map has to be encoded in
> > iso-8859-1 (or similar) to work, i.e. to be able to print accented
> > characters. If you are in a UTF-8 environment, ps.map creates a ps
> > file which doesn't show correct accented characters be it in iso or
> > in utf.
> > 
> > Is there any reason why ps.map hardcodes the encoding ? Is it
> > possible to automatically use the users encoding ?


FWIW, if all you want is accents, ps.map should be able to pass through
the standard ascii extended chars.  e.g. I use the (c), ^2, degree
symbols a lot. gnome-terminal doesn't like them, but they are fine
passed from an input file. Alternately direct insertion using rxvt+vi on
the output PostScript file can get the job done. If you try this & have
many to do, I suggest leaving some breadcrumbs for the search&replace to
find.


Hamish


Tue, Oct 10 2006 09:53:12    Mail sent by mlennert@club.worldonline.be  
Return-Path <mlennert@club.worldonline.be>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <452B5177.2090602@club.worldonline.be>
Date Tue, 10 Oct 2006 09:53:27 +0200
From Moritz Lennert <mlennert@club.worldonline.be>
User-Agent Thunderbird 1.5.0.7 (X11/20060915)
MIME-Version 1.0
To Glynn Clements via RT <grass-bugs@intevation.de>, Hamish <hamish_nospam@yahoo.com>
Cc Grass Developers List <grass-dev@grass.itc.it>
Subject Re: [bug #5195] (grass) ps.map sets encoding to iso-8859-1
References <20061010034558.408E21006A0@lists.intevation.de>
In-Reply-To <20061010034558.408E21006A0@lists.intevation.de>
Content-Type text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Glynn Clements via RT wrote:
> Request Tracker wrote:
> 
>> this bug's URL: http://intevation.de/rt/webrt?serial_num=5195
>> -------------------------------------------------------------------------
>>
>> Subject: ps.map sets encoding to iso-8859-1
>>
>> Platform: GNU/Linux/x86
>> grass obtained from: CVS
>> grass binary for platform: Compiled from Sources
>> GRASS Version: cvs_head_20060921
>>
>> On line 92 of ps/ps.map/prolog.ps the encoding is set to ISOLatin1Encoding.
>>
>> If I understand correctly (and some testing confirms this) this
>> means that the instructions file for ps.map has to be encoded in
>> iso-8859-1 (or similar) to work, i.e. to be able to print accented
>> characters. If you are in a UTF-8 environment, ps.map creates a ps
>> file which doesn't show correct accented characters be it in iso or
>> in utf.
>>
>> Is there any reason why ps.map hardcodes the encoding ? Is it
>> possible to automatically use the users encoding ?
> 
> The reason why we force the font's encoding to ISOLatin1Encoding is
> that the default encoding for most Latin fonts is StandardEncoding,
> which (contrary to its name) is a completely non-standard encoding
> which (AFAICT) is not used by anything except PostScript.
> 
> The value of the Encoding property is an array of 256 glyph names, so
> you can use any unibyte encoding (e.g. ISO-646-*, ISO-8859-*,
> windows-12?? etc).
> 
> If you want to support more complex encodings, you need to use
> CID-keyed fonts. Apart from being rather complex, CID-keyed fonts may
> not be supported by PostScript printers sold outside of South-East
> Asia.


Does UTF-8 count as 'complex encoding' ? Most GNU/Linux distributions 
come with UTF-8 as default system encoding nowadays and so users will 
have that problem.

> 
> In short, allowing the encoding to be changed to other unibyte
> encodings is simple enough. Anything else will require a willing
> volunteer (i.e. not me), and will need to be implemented in such a way
> that users don't end up accidentally producing documents which show up
> fine in (recent versions of) Ghostscript but which will be rejected by
> every PostScript printer on this half of the planet.


Hamish wrote:
> FWIW, if all you want is accents, ps.map should be able to pass through
> the standard ascii extended chars.  e.g. I use the (c), ^2, degree
> symbols a lot. gnome-terminal doesn't like them, but they are fine
> passed from an input file. 

We haven't been able to get accents in ps.map if the instructions file 
containing the accents was utf-8 encoded.

> Alternately direct insertion using rxvt+vi on
> the output PostScript file can get the job done. If you try this & have
> many to do, I suggest leaving some breadcrumbs for the search&replace to
> find.

Yes, manually it is no problem (see below), but that is quite a hassle. 
IMO accents should be easily available in GRASS.

If I did understand correctly what happened during my testing, even in a 
UTF-8 environment it is enough that the ps.map instruction file was 
encoded using a unibyte encoding, i.e.

iconv -f ISO_8859-15 -t UTF-8 test.psmap.iso > test.psmap.utf8

LC_ALL=iso-8859-15

ps.map in=test.psmap.iso out=map.ps
accents are there.

ps.map in=test.psmap.utf8 out=map.ps
garbled accents


LC_ALL=UTF-8

ps.map in=test.psmap.iso out=map.ps
accents are there

ps.map in=test.psmap.utf8 out=map.ps
garbled accents

So, maybe we should at least add a hint to the ps.map man page that 
utf-8-based users who want non-ascii characters should translate their 
utf-8 instruction files to unibyte before using them.

I imagine there is no way of automatically identifying the encoding of a 
file ?

Moritz


Tue, Oct 10 2006 10:26:22    Mail sent by hamish_nospam@yahoo.com  
Return-Path <hamish_nospam@yahoo.com>
Delivered-To grass-bugs@lists.intevation.de
Date Tue, 10 Oct 2006 21:25:52 +1300
From Hamish <hamish_nospam@yahoo.com>
To Moritz Lennert <mlennert@club.worldonline.be>
Cc grass-bugs@intevation.de, grass-dev@grass.itc.it
Subject Re: [bug #5195] (grass) ps.map sets encoding to iso-8859-1
Message-Id <20061010212552.4057d702.hamish_nospam@yahoo.com>
In-Reply-To <452B5177.2090602@club.worldonline.be>
References <20061010034558.408E21006A0@lists.intevation.de> <452B5177.2090602@club.worldonline.be>
X-Mailer Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu)
X-Face M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk!HT&BB 8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
Mime-Version 1.0
Content-Type text/plain; charset=US-ASCII
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-2.3 tagged_above=-999 required=3 tests=[BAYES_00=-5, FORGED_YAHOO_RCVD=2.7]
X-Spam-Level
Moritz Lennert wrote:
> So, maybe we should at least add a hint to the ps.map man page that 
> utf-8-based users who want non-ascii characters should translate their 
> utf-8 instruction files to unibyte before using them.

yes that would be good, with an example.

> I imagine there is no way of automatically identifying the encoding of a 
> file ?

file $filename


Hamish


Tue, Oct 10 2006 10:31:52    Mail sent by mlennert@club.worldonline.be  
Return-Path <mlennert@club.worldonline.be>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <452B5A8F.6030400@club.worldonline.be>
Date Tue, 10 Oct 2006 10:32:15 +0200
From Moritz Lennert <mlennert@club.worldonline.be>
User-Agent Thunderbird 1.5.0.7 (X11/20060915)
MIME-Version 1.0
To Hamish <hamish_nospam@yahoo.com>
Cc grass-bugs@intevation.de, grass-dev@grass.itc.it
Subject Re: [bug #5195] (grass) ps.map sets encoding to iso-8859-1
References <20061010034558.408E21006A0@lists.intevation.de> <452B5177.2090602@club.worldonline.be> <20061010212552.4057d702.hamish_nospam@yahoo.com>
In-Reply-To <20061010212552.4057d702.hamish_nospam@yahoo.com>
Content-Type text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Hamish wrote:
> Moritz Lennert wrote:
>> So, maybe we should at least add a hint to the ps.map man page that 
>> utf-8-based users who want non-ascii characters should translate their 
>> utf-8 instruction files to unibyte before using them.
> 
> yes that would be good, with an example.
> 
>> I imagine there is no way of automatically identifying the encoding of a 
>> file ?
> 
> file $filename

Could this be integrated into ps.map (i.e. is there a C equivalent) ? 
Would this be a good idea ?

Moritz


Tue, Oct 10 2006 14:50:10    Mail sent by glynn@gclements.plus.com  
Return-Path <glynn@gclements.plus.com>
Delivered-To grass-bugs@lists.intevation.de
From Glynn Clements <glynn@gclements.plus.com>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Transfer-Encoding 7bit
Message-ID <17707.38653.353951.900162@cerise.gclements.plus.com>
Date Tue, 10 Oct 2006 13:50:05 +0100
To Moritz Lennert <mlennert@club.worldonline.be>
Cc Glynn Clements via RT <grass-bugs@intevation.de>, Hamish <hamish_nospam@yahoo.com>, Grass Developers List <grass-dev@grass.itc.it>
Subject Re: [GRASS-dev] Re: [bug #5195] (grass) ps.map sets encoding to iso-8859-1
In-Reply-To <452B5177.2090602@club.worldonline.be>
References <20061010034558.408E21006A0@lists.intevation.de> <452B5177.2090602@club.worldonline.be>
X-Mailer VM 7.07 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Moritz Lennert wrote:

> >> this bug's URL: http://intevation.de/rt/webrt?serial_num=5195
> >> -------------------------------------------------------------------------
> >>
> >> Subject: ps.map sets encoding to iso-8859-1
> >>
> >> Platform: GNU/Linux/x86
> >> grass obtained from: CVS
> >> grass binary for platform: Compiled from Sources
> >> GRASS Version: cvs_head_20060921
> >>
> >> On line 92 of ps/ps.map/prolog.ps the encoding is set to ISOLatin1Encoding.
> >>
> >> If I understand correctly (and some testing confirms this) this
> >> means that the instructions file for ps.map has to be encoded in
> >> iso-8859-1 (or similar) to work, i.e. to be able to print accented
> >> characters. If you are in a UTF-8 environment, ps.map creates a ps
> >> file which doesn't show correct accented characters be it in iso or
> >> in utf.
> >>
> >> Is there any reason why ps.map hardcodes the encoding ? Is it
> >> possible to automatically use the users encoding ?
> > 
> > The reason why we force the font's encoding to ISOLatin1Encoding is
> > that the default encoding for most Latin fonts is StandardEncoding,
> > which (contrary to its name) is a completely non-standard encoding
> > which (AFAICT) is not used by anything except PostScript.
> > 
> > The value of the Encoding property is an array of 256 glyph names, so
> > you can use any unibyte encoding (e.g. ISO-646-*, ISO-8859-*,
> > windows-12?? etc).
> > 
> > If you want to support more complex encodings, you need to use
> > CID-keyed fonts. Apart from being rather complex, CID-keyed fonts may
> > not be supported by PostScript printers sold outside of South-East
> > Asia.
> 
> Does UTF-8 count as 'complex encoding' ?

Anything which isn't a unibyte encoding (where each byte maps to a
specific character) counts as a complex encoding. That includes UTF-8.

> Most GNU/Linux distributions 
> come with UTF-8 as default system encoding nowadays and so users will 
> have that problem.

The default locale's encoding doesn't matter. What matters is the
encoding of the text in the ps.map input file.

If they have text in UTF-8, they'll need to convert it to ISO-8859-1
first. If you have text outside of the ISO-8859-1 repertoire, you lose
regardless of what ps.map does, because your printer probably doesn't
have those glyphs.

About the only thing which ps.map can do here is to convert UTF-8 to
ISO-8859-1. But then it would need some way to determine that the text
is in UTF-8 (if it assumes it, users would first have to convert any
ISO-8859-1 text to UTF-8 just so that ps.map can convert it back to
ISO-8859-1).

> I imagine there is no way of automatically identifying the encoding of a 
> file ?

Correct. At least, not reliably. You can use various heuristics; e.g. 
bytes \x80-\x9F aren't valid in any ISO-8859-* encodings, certain
combinations aren't valid in UTF-8 etc.

But it's entirely possible to create a text file which is perfectly
valid in multiple encodings. E.g. if you have an ISO-8859-* file which
is almost entirely ASCII but with a small number of isolated non-ASCII
characters, it's almost impossible for a program to determine exactly
which ISO-8859-* encoding it's meant to be.

-- 
Glynn Clements <glynn@gclements.plus.com>


Tue, Oct 10 2006 15:03:22    Mail sent by glynn@gclements.plus.com  
Return-Path <glynn@gclements.plus.com>
Delivered-To grass-bugs@lists.intevation.de
From Glynn Clements <glynn@gclements.plus.com>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Transfer-Encoding 7bit
Message-ID <17707.39446.26137.432265@cerise.gclements.plus.com>
Date Tue, 10 Oct 2006 14:03:18 +0100
To Moritz Lennert <mlennert@club.worldonline.be>
Cc Hamish <hamish_nospam@yahoo.com>, grass-bugs@intevation.de, grass-dev@grass.itc.it
Subject Re: [GRASS-dev] Re: [bug #5195] (grass) ps.map sets encoding to iso-8859-1
In-Reply-To <452B5A8F.6030400@club.worldonline.be>
References <20061010034558.408E21006A0@lists.intevation.de> <452B5177.2090602@club.worldonline.be> <20061010212552.4057d702.hamish_nospam@yahoo.com> <452B5A8F.6030400@club.worldonline.be>
X-Mailer VM 7.07 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Moritz Lennert wrote:

> >> So, maybe we should at least add a hint to the ps.map man page that 
> >> utf-8-based users who want non-ascii characters should translate their 
> >> utf-8 instruction files to unibyte before using them.
> > 
> > yes that would be good, with an example.
> > 
> >> I imagine there is no way of automatically identifying the encoding of a
> >> file ?
> > 
> > file $filename
> 
> Could this be integrated into ps.map (i.e. is there a C equivalent) ? 
> Would this be a good idea ?

I'm not sure whether it's precise enough to be useful. E.g. it won't
attempt to distinguish different ISO-8859-* encodings (it just reports
"ISO-8859 text"). Also, it can occasionally misidentify ISO-8859-* as
UTF-8; AFAICT, anything which is text, isn't ASCII, and is legal as
UTF-8 is assumed to be UTF-8, even if it is also legal as ISO-8859-*.

-- 
Glynn Clements <glynn@gclements.plus.com>


Tue, Oct 10 2006 15:34:47    Mail sent by mlennert@club.worldonline.be  
Return-Path <mlennert@club.worldonline.be>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <452BA18C.3090102@club.worldonline.be>
Date Tue, 10 Oct 2006 15:35:08 +0200
From Moritz Lennert <mlennert@club.worldonline.be>
User-Agent Thunderbird 1.5.0.7 (X11/20060927)
MIME-Version 1.0
To Glynn Clements <glynn@gclements.plus.com>
Cc Glynn Clements via RT <grass-bugs@intevation.de>, Hamish <hamish_nospam@yahoo.com>, Grass Developers List <grass-dev@grass.itc.it>
Subject Re: [GRASS-dev] Re: [bug #5195] (grass) ps.map sets encoding to iso-8859-1
References <20061010034558.408E21006A0@lists.intevation.de> <452B5177.2090602@club.worldonline.be> <17707.38653.353951.900162@cerise.gclements.plus.com>
In-Reply-To <17707.38653.353951.900162@cerise.gclements.plus.com>
Content-Type multipart/mixed; boundary="------------020607020707050706080906"
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
This is a multi-part message in MIME format.
--------------020607020707050706080906
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Glynn Clements wrote:
> Moritz Lennert wrote:

>> Most GNU/Linux distributions 
>> come with UTF-8 as default system encoding nowadays and so users will 
>> have that problem.
> 
> The default locale's encoding doesn't matter. What matters is the
> encoding of the text in the ps.map input file.

Yes, but I would assume that in most cases (i.e. in those where people 
don't even think about encoding issues) files will be encoded in the 
locale's encoding.

> 
> If they have text in UTF-8, they'll need to convert it to ISO-8859-1
> first. If you have text outside of the ISO-8859-1 repertoire, you lose
> regardless of what ps.map does, because your printer probably doesn't
> have those glyphs.
> 
> About the only thing which ps.map can do here is to convert UTF-8 to
> ISO-8859-1. But then it would need some way to determine that the text
> is in UTF-8 (if it assumes it, users would first have to convert any
> ISO-8859-1 text to UTF-8 just so that ps.map can convert it back to
> ISO-8859-1).

This is obviously no solution.

> 
>> I imagine there is no way of automatically identifying the encoding of a 
>> file ?
> 
> Correct. At least, not reliably. You can use various heuristics; e.g. 
> bytes \x80-\x9F aren't valid in any ISO-8859-* encodings, certain
> combinations aren't valid in UTF-8 etc.
> 
> But it's entirely possible to create a text file which is perfectly
> valid in multiple encodings. E.g. if you have an ISO-8859-* file which
> is almost entirely ASCII but with a small number of isolated non-ASCII
> characters, it's almost impossible for a program to determine exactly
> which ISO-8859-* encoding it's meant to be.

Ok, so the only thing to do seems to be a note in the man page.

Does the attached patch look alright ?

Moritz

--------------020607020707050706080906
Content-Type: text/plain;
 name="ps_map_description.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="ps_map_description.diff"

Index: ps/ps.map/description.html
===================================================================
RCS file: /grassrepository/grass6/ps/ps.map/description.html,v
retrieving revision 1.45
diff -u -r1.45 description.html
--- ps/ps.map/description.html	19 Jul 2006 10:08:31 -0000	1.45
+++ ps/ps.map/description.html	10 Oct 2006 13:31:33 -0000
@@ -20,7 +20,9 @@
 This program has two distinct modes of operation.  The command-line
 mode requires the user to prepare a file of mapping instructions prior
 to running <EM>ps.map</EM> that describes the various spatial and textual
-information to be printed.
+information to be printed. For users wanting to use special characters (such
as accented characters) it is important to not that ps.map uses ISO-Latin1 encoding.
This means that your instructions file will have to be encoded in this encoding.
If you normally work in a different encoding environment (such as UTF-8), you
have to transform your file to the ISO-latin1 encoding, for example by using
<EM>iconv</EM>:
+
+<EM>iconv -f UTF-8 -t ISO_8859-1 utf_file > iso_file</EM>
 
 The interactive mode (i.e., no command-line arguments) will prompt the
 user for items to be mapped and does not require the user

--------------020607020707050706080906--


Tue, Oct 10 2006 19:17:50    Mail sent by tutey@o2.pl  
Return-Path <tutey@o2.pl>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <452BD5BC.9010907@o2.pl>
Date Tue, 10 Oct 2006 19:17:48 +0200
From Maciej Sieczka <tutey@o2.pl>
User-Agent Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version 1.0
To Glynn Clements <glynn@gclements.plus.com>
Cc Moritz Lennert <mlennert@club.worldonline.be>, Glynn Clements via RT <grass-bugs@intevation.de>, Hamish <hamish_nospam@yahoo.com>, Grass Developers List <grass-dev@grass.itc.it>
Subject Re: [GRASS-dev] Re: [bug #5195] (grass) ps.map sets encoding to iso-8859-1
References <20061010034558.408E21006A0@lists.intevation.de> <452B5177.2090602@club.worldonline.be> <17707.38653.353951.900162@cerise.gclements.plus.com>
In-Reply-To <17707.38653.353951.900162@cerise.gclements.plus.com>
Content-Type text/plain; charset=ISO-8859-2
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Glynn Clements wrote:
> Moritz Lennert wrote:

>> Most GNU/Linux distributions 
>> come with UTF-8 as default system encoding nowadays and so users will 
>> have that problem.

> The default locale's encoding doesn't matter. What matters is the
> encoding of the text in the ps.map input file.

Technically that's right, but the problem is that eg. in Ubuntu, where
default encoding is UTF-8, the new text files I create are by default
in UTF-8. Unless the user knows what the ISO-8859-whatever and
UTF-whatever are, he's in trouble. I understand we currently just have
to assume he must know that tough, and that's it's not GRASS problem
problem if he doesn't.

>> I imagine there is no way of automatically identifying the encoding of a 
>> file ?

> Correct. At least, not reliably. You can use various heuristics; e.g. 
> bytes \x80-\x9F aren't valid in any ISO-8859-* encodings, certain
> combinations aren't valid in UTF-8 etc.

ENCA [1] is a nice example of such a software. It never failed for me
for ISO-8859-1/2 <-> UTF-8 automatic conversions.

Maciek

[1] http://freshmeat.net/projects/enca/


Wed, Oct 11 2006 04:09:47    Mail sent by hamish_nospam@yahoo.com  
Return-Path <hamish_nospam@yahoo.com>
Delivered-To grass-bugs@lists.intevation.de
Date Wed, 11 Oct 2006 15:09:27 +1300
From Hamish <hamish_nospam@yahoo.com>
To Moritz Lennert <mlennert@club.worldonline.be>
Cc grass-bugs@intevation.de, grass-dev@grass.itc.it
Subject Re: [GRASS-dev] Re: [bug #5195] (grass) ps.map sets encoding to iso-8859-1
Message-Id <20061011150927.1db6f561.hamish_nospam@yahoo.com>
In-Reply-To <452BA18C.3090102@club.worldonline.be>
References <20061010034558.408E21006A0@lists.intevation.de> <452B5177.2090602@club.worldonline.be> <17707.38653.353951.900162@cerise.gclements.plus.com> <452BA18C.3090102@club.worldonline.be>
X-Mailer Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu)
X-Face M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk!HT&BB 8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
Mime-Version 1.0
Content-Type text/plain; charset=US-ASCII
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-2.3 tagged_above=-999 required=3 tests=[BAYES_00=-5, FORGED_YAHOO_RCVD=2.7]
X-Spam-Level
> Ok, so the only thing to do seems to be a note in the man page.
> 
> Does the attached patch look alright ?

Index: ps/ps.map/description.html
===================================================================
RCS file: /grassrepository/grass6/ps/ps.map/description.html,v
retrieving revision 1.45
diff -u -r1.45 description.html
--- ps/ps.map/description.html	19 Jul 2006 10:08:31 -0000	1.45
+++ ps/ps.map/description.html	10 Oct 2006 13:31:33 -0000
@@ -20,7 +20,9 @@
 This program has two distinct modes of operation.  The command-line
 mode requires the user to prepare a file of mapping instructions prior
 to running <EM>ps.map</EM> that describes the various spatial and textual
-information to be printed.
+information to be printed. For users wanting to use special characters (such
as accented characters) it is important to not that ps.map uses ISO-Latin1 encoding.
This means that your instructions file will have to be encoded in this encoding.
If you normally work in a different encoding environment (such as UTF-8), you
have to transform your file to the ISO-latin1 encoding, for example by using
<EM>iconv</EM>:
+
+<EM>iconv -f UTF-8 -t ISO_8859-1 utf_file > iso_file</EM>
 
 The interactive mode (i.e., no command-line arguments) will prompt the
 user for items to be mapped and does not require the user


It reads well. A few suggestions:

- this probably belongs in the NOTES section, not the DESCRIPTION
section of the help page.

- typo: "it is important to not that"   s/not/note/

- please break lines before the 80th column

- "code" examples should be html-ized as follows:
    (also in the above you forgot <BR> or <P> to separate the line)

<div class="code"><pre>
iconv -f UTF-8 -t ISO_8859-1 utf_file.txt > iso_file.txt
</pre></div>



Hamish


Wed, Oct 11 2006 06:55:26    Mail sent by glynn@gclements.plus.com  
Return-Path <glynn@gclements.plus.com>
Delivered-To grass-bugs@lists.intevation.de
From Glynn Clements <glynn@gclements.plus.com>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Transfer-Encoding 7bit
Message-ID <17708.31029.185856.159305@cerise.gclements.plus.com>
Date Wed, 11 Oct 2006 05:55:17 +0100
To Moritz Lennert <mlennert@club.worldonline.be>
Cc Glynn Clements via RT <grass-bugs@intevation.de>, Hamish <hamish_nospam@yahoo.com>, Grass Developers List <grass-dev@grass.itc.it>
Subject Re: [GRASS-dev] Re: [bug #5195] (grass) ps.map sets encoding to iso-8859-1
In-Reply-To <452BA18C.3090102@club.worldonline.be>
References <20061010034558.408E21006A0@lists.intevation.de> <452B5177.2090602@club.worldonline.be> <17707.38653.353951.900162@cerise.gclements.plus.com> <452BA18C.3090102@club.worldonline.be>
X-Mailer VM 7.07 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-2.74 tagged_above=-999 required=3 tests=[BAYES_00=-5, LONGWORDS=2.26]
X-Spam-Level
Moritz Lennert wrote:

> >> Most GNU/Linux distributions 
> >> come with UTF-8 as default system encoding nowadays and so users will 
> >> have that problem.
> > 
> > The default locale's encoding doesn't matter. What matters is the
> > encoding of the text in the ps.map input file.
> 
> Yes, but I would assume that in most cases (i.e. in those where people 
> don't even think about encoding issues) files will be encoded in the 
> locale's encoding.

Not necessarily.

If they get the data from an external source (email, web page), the
file will probably be in whatever format the file's creator chose. 
Programs which save some data to text files typically just save the
bytes as they found them.

If they created the data themselves, it's likely to be in the default
encoding of their preferred text editor, which isn't necessarily the
same as the locale's encoding.

> >> I imagine there is no way of automatically identifying the encoding of a
> >> file ?
> > 
> > Correct. At least, not reliably. You can use various heuristics; e.g. 
> > bytes \x80-\x9F aren't valid in any ISO-8859-* encodings, certain
> > combinations aren't valid in UTF-8 etc.
> > 
> > But it's entirely possible to create a text file which is perfectly
> > valid in multiple encodings. E.g. if you have an ISO-8859-* file which
> > is almost entirely ASCII but with a small number of isolated non-ASCII
> > characters, it's almost impossible for a program to determine exactly
> > which ISO-8859-* encoding it's meant to be.
> 
> Ok, so the only thing to do seems to be a note in the man page.
> 
> Does the attached patch look alright ?

> +information to be printed. For users wanting to use special
> characters (such as accented characters) it is important to not that
> ps.map uses ISO-Latin1 encoding.

Technically, the encoding is ISO-8859-1. "ISO Latin 1" refers to the
repertoire (the set of characters) rather than the byte-sequences used
to encode them.

Other than that, it seems okay.

One error I noticed in the ps.map manpage; in the description of the
"text" command, it says:

        wrong??   font:  cyrilc  gothgbt gothgrt gothitt greekc greekcs greekp
greeks italicc italiccs italict romanc  romancs  romand  romans  romant
       scriptc scripts (The default font is romans);

Yep, that's definitely wrong. Valid arguments to the "font" option are
whatever fonts your printer (or Ghostscript, etc) supports. Safe
choices, present in all PostScript implementations, are:

	Times-Roman
	Times-Italic
	Times-Bold
	Times-BoldItalic
	Helvetica
	Helvetica-Oblique
	Helvetica-Bold
	Helvetica-BoldOblique
	Courier
	Courier-Oblique
	Courier-Bold
	Courier-BoldOblique

The default is Helvetica.

-- 
Glynn Clements <glynn@gclements.plus.com>


Wed, Oct 11 2006 17:28:42    Mail sent by mlennert@club.worldonline.be  
Return-Path <mlennert@club.worldonline.be>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <452D0DC0.6050600@club.worldonline.be>
Date Wed, 11 Oct 2006 17:29:04 +0200
From Moritz Lennert <mlennert@club.worldonline.be>
User-Agent Thunderbird 1.5.0.7 (X11/20060927)
MIME-Version 1.0
To Maciej Sieczka <tutey@o2.pl>
Cc Glynn Clements <glynn@gclements.plus.com>, Glynn Clements via RT <grass-bugs@intevation.de>, Hamish <hamish_nospam@yahoo.com>, Grass Developers List <grass-dev@grass.itc.it>
Subject Re: [GRASS-dev] Re: [bug #5195] (grass) ps.map sets encoding to iso-8859-1
References <20061010034558.408E21006A0@lists.intevation.de> <452B5177.2090602@club.worldonline.be> <17707.38653.353951.900162@cerise.gclements.plus.com> <452BD5BC.9010907@o2.pl>
In-Reply-To <452BD5BC.9010907@o2.pl>
Content-Type text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Maciej Sieczka wrote:
> 
> ENCA [1] is a nice example of such a software. It never failed for me
> for ISO-8859-1/2 <-> UTF-8 automatic conversions.
> 

mlennert@geog-pc40:~$ enca test.psmap.utf8
enca: Cannot determine (or understand) your language preferences.
Please use `-L language', or `-L none' if your language is not supported
(only a few multibyte encodings can be recognized then).
Run `enca --list languages' to get a list of supported languages.

mlennert@geog-pc40:~$ enca --list languages
belarussian: CP1251 IBM866 ISO-8859-5 KOI8-UNI maccyr IBM855
   bulgarian: CP1251 ISO-8859-5 IBM855 maccyr ECMA-113
       czech: ISO-8859-2 CP1250 IBM852 KEYBCS2 macce KOI-8_CS_2 CORK
    estonian: ISO-8859-4 CP1257 IBM775 ISO-8859-13 macce baltic
    croatian: CP1250 ISO-8859-2 IBM852 macce CORK
   hungarian: ISO-8859-2 CP1250 IBM852 macce CORK
  lithuanian: CP1257 ISO-8859-4 IBM775 ISO-8859-13 macce baltic
     latvian: CP1257 ISO-8859-4 IBM775 ISO-8859-13 macce baltic
      polish: ISO-8859-2 CP1250 IBM852 macce ISO-8859-13 ISO-8859-16 
baltic CORK
     russian: KOI8-R CP1251 ISO-8859-5 IBM866 maccyr
      slovak: CP1250 ISO-8859-2 IBM852 KEYBCS2 macce KOI-8_CS_2 CORK
     slovene: ISO-8859-2 CP1250 IBM852 macce CORK
   ukrainian: CP1251 IBM855 ISO-8859-5 CP1125 KOI8-U maccyr
     chinese: GBK BIG5 HZ
        none:

So this seems a bit limited for general use in GRASS...and shows how 
complicated it is to do it for just a few languages.

Moritz


Thu, Oct 12 2006 09:55:34    Mail sent by mlennert@club.worldonline.be  
Return-Path <mlennert@club.worldonline.be>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <452DF504.8030705@club.worldonline.be>
Date Thu, 12 Oct 2006 09:55:48 +0200
From Moritz Lennert <mlennert@club.worldonline.be>
User-Agent Thunderbird 1.5.0.7 (X11/20060927)
MIME-Version 1.0
To Glynn Clements <glynn@gclements.plus.com>
Cc Glynn Clements via RT <grass-bugs@intevation.de>, Hamish <hamish_nospam@yahoo.com>, Grass Developers List <grass-dev@grass.itc.it>, Maciej Sieczka <tutey@o2.pl>
Subject Re: [GRASS-dev] Re: [bug #5195] (grass) ps.map sets encoding to iso-8859-1
References <20061010034558.408E21006A0@lists.intevation.de> <452B5177.2090602@club.worldonline.be> <17707.38653.353951.900162@cerise.gclements.plus.com> <452BA18C.3090102@club.worldonline.be> <17708.31029.185856.159305@cerise.gclements.plus.com>
In-Reply-To <17708.31029.185856.159305@cerise.gclements.plus.com>
Content-Type text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-2.74 tagged_above=-999 required=3 tests=[BAYES_00=-5, LONGWORDS=2.26]
X-Spam-Level
Glynn Clements wrote:
> Moritz Lennert wrote:
> 
>>>> Most GNU/Linux distributions 
>>>> come with UTF-8 as default system encoding nowadays and so users will 
>>>> have that problem.
>>> The default locale's encoding doesn't matter. What matters is the
>>> encoding of the text in the ps.map input file.
>> Yes, but I would assume that in most cases (i.e. in those where people 
>> don't even think about encoding issues) files will be encoded in the 
>> locale's encoding.
> 
> Not necessarily.
> 
> If they get the data from an external source (email, web page), the
> file will probably be in whatever format the file's creator chose. 
> Programs which save some data to text files typically just save the
> bytes as they found them.
> 
> If they created the data themselves, it's likely to be in the default
> encoding of their preferred text editor, which isn't necessarily the
> same as the locale's encoding.
> 
>>>> I imagine there is no way of automatically identifying the encoding of a
>>>> file ?
>>> Correct. At least, not reliably. You can use various heuristics; e.g. 
>>> bytes \x80-\x9F aren't valid in any ISO-8859-* encodings, certain
>>> combinations aren't valid in UTF-8 etc.
>>>
>>> But it's entirely possible to create a text file which is perfectly
>>> valid in multiple encodings. E.g. if you have an ISO-8859-* file which
>>> is almost entirely ASCII but with a small number of isolated non-ASCII
>>> characters, it's almost impossible for a program to determine exactly
>>> which ISO-8859-* encoding it's meant to be.
>> Ok, so the only thing to do seems to be a note in the man page.
>>
>> Does the attached patch look alright ?
> 
>> +information to be printed. For users wanting to use special
>> characters (such as accented characters) it is important to not that
>> ps.map uses ISO-Latin1 encoding.
> 
> Technically, the encoding is ISO-8859-1. "ISO Latin 1" refers to the
> repertoire (the set of characters) rather than the byte-sequences used
> to encode them.
> 
> Other than that, it seems okay.
> 
> One error I noticed in the ps.map manpage; in the description of the
> "text" command, it says:
> 
>         wrong??   font:  cyrilc  gothgbt gothgrt gothitt greekc greekcs greekp
>        greeks italicc italiccs italict romanc  romancs  romand  romans  romant
>        scriptc scripts (The default font is romans);
> 
> Yep, that's definitely wrong. Valid arguments to the "font" option are
> whatever fonts your printer (or Ghostscript, etc) supports. Safe
> choices, present in all PostScript implementations, are:
> 
> 	Times-Roman
> 	Times-Italic
> 	Times-Bold
> 	Times-BoldItalic
> 	Helvetica
> 	Helvetica-Oblique
> 	Helvetica-Bold
> 	Helvetica-BoldOblique
> 	Courier
> 	Courier-Oblique
> 	Courier-Bold
> 	Courier-BoldOblique
> 
> The default is Helvetica.

Just committed changes to description.html including corrections from 
Hamish Glynn and above information about fonts.

Bug can be closed (but we probably should think about how to handle this 
more elegantly in the future).

Moritz


Fri, Oct 13 2006 00:57:41    Mail sent by hamish_nospam@yahoo.com  
Return-Path <hamish_nospam@yahoo.com>
Delivered-To grass-bugs@lists.intevation.de
Date Fri, 13 Oct 2006 11:57:08 +1300
From Hamish <hamish_nospam@yahoo.com>
To Moritz Lennert <mlennert@club.worldonline.be>
Cc grass-bugs@intevation.de, grass-dev@grass.itc.it
Subject Re: [GRASS-dev] Re: [bug #5195] (grass) ps.map sets encoding to iso-8859-1
Message-Id <20061013115708.4ea9a654.hamish_nospam@yahoo.com>
In-Reply-To <452DF504.8030705@club.worldonline.be>
References <20061010034558.408E21006A0@lists.intevation.de> <452B5177.2090602@club.worldonline.be> <17707.38653.353951.900162@cerise.gclements.plus.com> <452BA18C.3090102@club.worldonline.be> <17708.31029.185856.159305@cerise.gclements.plus.com> <452DF504.8030705@club.worldonline.be>
X-Mailer Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu)
X-Face M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk!HT&BB 8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
Mime-Version 1.0
Content-Type text/plain; charset=US-ASCII
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-2.3 tagged_above=-999 required=3 tests=[BAYES_00=-5, FORGED_YAHOO_RCVD=2.7]
X-Spam-Level
> Just committed changes to description.html including corrections from 
> Hamish Glynn and above information about fonts.

Hi,

the explaination of the encoding situation is now easy to understand,
thanks.


Your patch didn't apply cleanly as I had made a change recently:
  http://grass.itc.it/pipermail/grass-commit/2006-October/024639.html

please check that there were not conflicts during the merge before
committing changes to CVS.

ie. before making changes always do
  cvs up description.html

and before commiting always do
  cvs diff description.html

and then watch out for error messages.


Now fixed in CVS.



thanks,
Hamish


Fri, Oct 13 2006 00:58:18    Status changed to resolved by hbowman  
Fri, Oct 13 2006 01:13:29    Mail sent by mlennert@club.worldonline.be  
Return-Path <mlennert@club.worldonline.be>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <452ECC30.9030304@club.worldonline.be>
Date Fri, 13 Oct 2006 01:13:52 +0200
From Moritz Lennert <mlennert@club.worldonline.be>
User-Agent Thunderbird 1.5.0.7 (X11/20060927)
MIME-Version 1.0
To Hamish via RT <grass-bugs@intevation.de>
Subject Re: [bug #5195] (grass) ps.map sets encoding to
References <20061012225741.6DEF31005A8@lists.intevation.de>
In-Reply-To <20061012225741.6DEF31005A8@lists.intevation.de>
Content-Type text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Hamish via RT wrote:
>> Just committed changes to description.html including corrections from 
>> Hamish Glynn and above information about fonts.
> 
> Hi,
> 
> the explaination of the encoding situation is now easy to understand,
> thanks.
> 
> 
> Your patch didn't apply cleanly as I had made a change recently:
>   http://grass.itc.it/pipermail/grass-commit/2006-October/024639.html
> 
> please check that there were not conflicts during the merge before
> committing changes to CVS.
> 
> ie. before making changes always do
>   cvs up description.html

I normally do, but must have forgotten about it this time.

Sorry.

> 
> and before commiting always do
>   cvs diff description.html
> 
> and then watch out for error messages.
> 
> 
> Now fixed in CVS.

Thanks.

Moritz

> 
> 
> 
> thanks,
> Hamish
> 
> 
> --- Headers Follow ---
> 
>>From hamish_nospam@yahoo.com  Fri Oct 13 00:57:41 2006
> Return-Path: <hamish_nospam@yahoo.com>
> Delivered-To: grass-bugs@lists.intevation.de
> Received: from kolab.intevation.de (aktaia [212.95.126.10])
> 	by lists.intevation.de (Postfix) with ESMTP id 4C0BA1005A3
> 	for <grass-bugs@lists.intevation.de>; Fri, 13 Oct 2006 00:57:41 +0200 (CEST)
> Received: from localhost (localhost.localdomain [127.0.0.1])
> 	by kolab.intevation.de (Postfix) with ESMTP id 32E091A4881
> 	for <grass-bugs@lists.intevation.de>; Fri, 13 Oct 2006 00:57:41 +0200 (CEST)
> Received: from localhost (localhost.localdomain [127.0.0.1])
> 	by kolab.intevation.de (Postfix) with ESMTP id 188B81AE3B5
> 	for <grass-bugs@lists.intevation.de>; Fri, 13 Oct 2006 00:57:41 +0200 (CEST)
> Received: from mailhub1.otago.ac.nz (mailhub1.otago.ac.nz [139.80.64.218])
> 	by kolab.intevation.de (Postfix) with ESMTP id 978AB1A4881
> 	for <grass-bugs@intevation.de>; Fri, 13 Oct 2006 00:57:34 +0200 (CEST)
> Received: from galadriel.otago.ac.nz (galadriel.otago.ac.nz [139.80.64.213])
> 	by mailhub1.otago.ac.nz (8.13.6/8.13.6) with ESMTP id k9CMv9uZ010838;
> 	Fri, 13 Oct 2006 11:57:09 +1300
> Received: from taihua.otago.ac.nz ([139.80.35.27] helo=taihua)
> 	by galadriel.otago.ac.nz with smtp (Exim 4.50)
> 	id 1GY9UB-0005R1-Md; Fri, 13 Oct 2006 11:57:08 +1300
> Date: Fri, 13 Oct 2006 11:57:08 +1300
> From: Hamish <hamish_nospam@yahoo.com>
> To: Moritz Lennert <mlennert@club.worldonline.be>
> Cc: grass-bugs@intevation.de, grass-dev@grass.itc.it
> Subject: Re: [GRASS-dev] Re: [bug #5195] (grass) ps.map sets encoding to
>  iso-8859-1
> Message-Id: <20061013115708.4ea9a654.hamish_nospam@yahoo.com>
> In-Reply-To: <452DF504.8030705@club.worldonline.be>
> References: <20061010034558.408E21006A0@lists.intevation.de>
> 	<452B5177.2090602@club.worldonline.be>
> 	<17707.38653.353951.900162@cerise.gclements.plus.com>
> 	<452BA18C.3090102@club.worldonline.be>
> 	<17708.31029.185856.159305@cerise.gclements.plus.com>
> 	<452DF504.8030705@club.worldonline.be>
> X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu)
> X-Face: M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk!HT&BB
>  8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
> Mime-Version: 1.0
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: 7bit
> X-Virus-Scanned: by amavisd-new at intevation.de
> X-Spam-Status: No, hits=-2.3 tagged_above=-999 required=3 tests=[BAYES_00=-5,
>  FORGED_YAHOO_RCVD=2.7]
> X-Spam-Level: 
> 
> -------------------------------------------- Managed by Request Tracker


Fri, Oct 13 2006 01:13:30    Status changed to open by _rt_system  
Wed, Nov 15 2006 15:29:07    Status changed to resolved by msieczka  
Comment | Reply | Take | Open

You are currently authenticated as guest.
[Show Configuration] [Login as another user]

Users Guide - Mail Commands - Homepage of RequestTracker 1.0.7 - list any request