Re: [GRASS GIS] #3925: winGRASS 7.8.1dev: 'charmap' codec can't decode byte 0x9d - issue in vector attribute data handling (e.g. opening attribute table, v.report, etc)

#3925: winGRASS 7.8.1dev: 'charmap' codec can't decode byte 0x9d - issue in vector
attribute data handling (e.g. opening attribute table, v.report, etc)
----------------------+------------------------------------
  Reporter:  hellik   |      Owner:  grass-dev@…
      Type:  defect   |     Status:  new
  Priority:  blocker  |  Milestone:  7.8.3
 Component:  Vector   |    Version:  git-releasebranch78
Resolution:           |   Keywords:  python3, py3, wingrass
       CPU:  x86-64   |   Platform:  MSWindows
----------------------+------------------------------------

Comment (by mmetz):

 Replying to [comment:5 hellik]:
 > Replying to [comment:4 hellik]:
 > > v.db.select output of the geonames data:
 > >
 > > [...]
 > >
 > > v.db.select seems to work, but some encoding issues also there, e.g.
 **Weiße Ries|Weisse Ries**

 This was apparently running v.db.select on the command line, not in the
 GRASS python console.
 >
 > starting v.db.select pops up the same encoding error:
 >
 > {{{
 > Exception in thread Thread-20:
 > Traceback (most recent call last):
 >   File "C:\OSGEO4~1\apps\Python37\lib\threading.py", line
 > 917, in _bootstrap_inner
 >     self.run()
 >   File "C:\OSGEO4~1\apps\grass\grass78\gui\wxpython\core\gco
 > nsole.py", line 162, in run
 > in position 840: character maps to <undefined>
 > [...]
 > }}}

 This was apparently running v.db.select using the GUI.

 Maybe the decoding must be adjusted according to the input.

 If input is the output of a GRASS db query, the same encoding needs to be
 used that is used in the GRASS db.

 If input is provided by the user, the system's

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/3925#comment:12>
GRASS GIS <https://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/grass-dev