[GRASS-dev] Re: [GRASS GIS] #882: i18n enabled winGRASS: properties dialog not opening

[GRASS GIS]

#882: i18n enabled　winGRASS: properties dialog not opening
----------------------+-----------------------------------------------------
  Reporter:  neteler  |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect   |      Status:  new                      
  Priority:  blocker  |   Milestone:  6.4.0                    
 Component:  wxGUI    |     Version:  svn-releasebranch64      
Resolution:           |    Keywords:  wingrass                 
  Platform:  All      |         Cpu:  x86-32                   
----------------------+-----------------------------------------------------
Changes (by neteler):

  * keywords:  => wingrass
  * platform:  MSWindows XP => All

Comment:

 Replying to [comment:7 glynn]:
 > Replying to [comment:5 neteler]:
 > > On a Japanese Linux box, the current encoding is:
 > {{{
 > r.cost --interface-description
 > <?xml version="1.0" encoding="EUC-JP"?>
 > }}}
 > >
 > > but should be UTF8.
 >
 > What do you mean by "should be"?

 OK: s/should be/IMHO/

 > Are the descriptions encoded in EUC-JP or in UTF-8?

 The grass*_ja.po files are in UTF8.

 > First and foremost, the encoding specified in the header must be the
 encoding which is actually used for the data.

 That's why I assumed a mismatch (both for Win and Linux, but in different
 ways).

 > The strings to which `opt->label` and `opt->description` point will be
 in the locale's encoding, as that's how `dgettext()` works, and that's how
 they need to be encoded so that the --help output displays correctly on
 the user's terminal. `G__usage_xml()` doesn't recode the data; it just
 copies the strings into the output.
 >
 > If you want the --interface-description output to always use UTF-8, then
 `G__usage_xml()` will need to recode any localised strings with `iconv()`.
 >
 > There shouldn't be any problem with encoding=EUC-JP, but encoding=CP932
 may be problematic as "CP932" isn't an IANA-registered encoding (the IANA
 name is "Windows-31J"), so it may not be recognised by XML parsers.

 I did not have success with encoding=EUC-JP while the .po files are in
 UTF8. Same of course for encoding=CP932.

 > [http://www.iana.org/assignments/character-sets IANA-registered
 encodings]

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/882#comment:8>
GRASS GIS <http://grass.osgeo.org>