#2453: Thai characters not displaying correctly in the query results window of Map
Display in GRASS 7.0.0beta3 Windows
-------------------------------------------+--------------------------------
Reporter: richardc | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Default | Version: svn-releasebranch70
Keywords: Map Display, Asian characters | Platform: MSWindows 7
Cpu: x86-32 |
-------------------------------------------+--------------------------------
Reference: http://osgeo-org.1560.x6.nabble.com/v-in-geonames-not-
importing-txt-file-in-GRASS-7-0-0beta3-Windows-td5166832.html
In the Map Display, Thai characters (from TH.txt geonames download) are
not displaying correctly in the query results window (pls see below).
However, Thai characters are correctly displayed in the imported file's
attribute table.
#2453: Thai characters not displaying correctly in the query results window of Map
Display in GRASS 7.0.0beta3 Windows
-------------------------------------------+--------------------------------
Reporter: richardc | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Default | Version: svn-releasebranch70
Keywords: Map Display, Asian characters | Platform: MSWindows 7
Cpu: x86-32 |
-------------------------------------------+--------------------------------
Comment(by annakrat):
It would be good to get first resolved ticket #2431 because it simplifies
reading data from v.what. I think attribute table manager assumes utf8
unless you specify encoding in settings. I don't think we have currently
any better solution for attributes encoding, especially combining data
with different encodings.
#2453: Thai characters not displaying correctly in the query results window of Map
Display in GRASS 7.0.0beta3 Windows
-------------------------------------------+--------------------------------
Reporter: richardc | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Default | Version: svn-releasebranch70
Keywords: Map Display, Asian characters | Platform: MSWindows 7
Cpu: x86-32 |
-------------------------------------------+--------------------------------
Comment(by marisn):
Replying to [comment:1 annakrat]:
> It would be good to get first resolved ticket #2431 because it
simplifies reading data from v.what. I think attribute table manager
assumes utf8 unless you specify encoding in settings. I don't think we
have currently any better solution for attributes encoding, especially
combining data with different encodings.
DB encoding issues will have to be solved one day. The correct option
would be add a encoding metadata to dblink. Still it needs some design
decisions (should it be enforced?). Unfortunately I had no time to work on
it this year and it is too large change for 7.0. http://lists.osgeo.org/pipermail/grass-dev/2014-April/068160.html
#2453: Thai characters not displaying correctly in the query results window of Map
Display in GRASS 7.0.0beta3 Windows
-------------------------------------------+--------------------------------
Reporter: richardc | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Default | Version: svn-releasebranch70
Keywords: Map Display, Asian characters | Platform: MSWindows 7
Cpu: x86-32 |
-------------------------------------------+--------------------------------
Comment(by wenzeslaus):
Replying to [comment:2 marisn]:
> Replying to [comment:1 annakrat]:
> > It would be good to get first resolved ticket #2431 because it
simplifies reading data from v.what. I think attribute table manager
assumes utf8 unless you specify encoding in settings. I don't think we
have currently any better solution for attributes encoding, especially
combining data with different encodings.
>
> DB encoding issues will have to be solved one day. The correct option
would be add a encoding metadata to dblink. Still it needs some design
decisions (should it be enforced?). Unfortunately I had no time to work on
it this year and it is too large change for 7.0.
> http://lists.osgeo.org/pipermail/grass-dev/2014-April/068160.html
Sounds reasonable to me. According to your current understanding, do you
think that the change could be done in backwards compatible manner?
Because if not, it would have to wait to 8.0.