[GRASS-dev] Re: [GRASS GIS] #1349: Ps.map supports only english

GRASS GIS trac at osgeo.org
Wed Apr 20 05:12:50 EDT 2011


#1349: Ps.map supports only english
-------------------------+--------------------------------------------------
 Reporter:  annakrat     |       Owner:  grass-dev@…              
     Type:  enhancement  |      Status:  new                      
 Priority:  minor        |   Milestone:  6.5.0                    
Component:  Ps.map       |     Version:  unspecified              
 Keywords:  encoding     |    Platform:  Unspecified              
      Cpu:  Unspecified  |  
-------------------------+--------------------------------------------------

Comment(by mlennert):

 Replying to [comment:1 hamish]:
 > Replying to [ticket:1349 annakrat]:
 > > Postscript file generated by ps.map uses Latin1 and as a result
 > > I can't use czech language properly. I have no experience with
 > > postscript, so would it be possible to change it to utf8?
 >
 > from the help page:
 > {{{
 > For users wanting to use special characters (such as accented char-
 > acters) it is important to note that ps.map uses ISO-8859-1  encod-
 > ing.   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-8859-1 encoding, for example  by  using  the  iconv
 > utility:
 > iconv -f UTF-8 -t ISO_8859-1 utf_file > iso_file
 > }}}
 >
 > from the mailing list archive:
 >    http://thread.gmane.org/gmane.comp.gis.grass.devel/15881

 The problem is that


 {{{
 iconv -f UTF-8 -t ISO_8859-1 utf_file > iso_file
 }}}

 will not work if the utf_file contains special caracters which are defined
 in ISO-8859-2.

 I don't know how/if Postscript handles UTF-8. a2ps and enscript can create
 Postscript files from text encoded in ISO-8859-2, but they cannot
 transform UTF-8 text into Postscript files.

 This seems to be a more structural issue than just the iconv conversion. I
 don't know how other projects handle this issue.

 Moritz

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1349#comment:2>
GRASS GIS <http://grass.osgeo.org>



More information about the grass-dev mailing list