[GRASS-dev] [GRASS GIS] #2021: encoding information in locale gets lost

GRASS GIS trac at osgeo.org
Thu Jun 11 00:51:26 PDT 2015


#2021: encoding information in locale gets lost
--------------------------+-----------------------------
  Reporter:  mlennert     |      Owner:  grass-dev@…
      Type:  defect       |     Status:  reopened
  Priority:  normal       |  Milestone:  7.0.1
 Component:  Startup      |    Version:  svn-trunk
Resolution:               |   Keywords:  locale encoding
       CPU:  Unspecified  |   Platform:  Linux
--------------------------+-----------------------------

Comment (by marisn):

 Hm. Probably set_language should be moved to some place to kick-in only if
 a GUI session is started.

 Rant:
 The architectural problem lies in the fact that GRASS is not a monolithic
 app as i.e. QGIS. GUI's can be started from CLI and there are CLI apps too
 (and, of course, "native" widgets like "open file"!). Thus setting a
 language in wxgui tries to cover all potential aspects to ensure a
 constant user experience.
 The problem areas are: lack of target locale on particular system (only
 GRASS messages will be translated); incorrect default encoding (i.e. for
 Latvian language Python is certain that Win-1257 is the best thing on my
 UTF-8 Linux box and then hell breaks loose!); enforcing language on
 everything (cal; "OK" and "Cancel" buttons; all GRASS module output as it
 might be piped back to GUI; did I forgot something?
 As one can see - it is easy to mess something up and "quick fixes" need to
 ensure covering most of aspects as it is too easy to make things worse.
 (just check my own commits for language switching and you will see that it
 is true ;) )

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



More information about the grass-dev mailing list