Thai characters not displaying correctly in the query results window of Map Display in GRASS 7.0.0beta3 Windows

[richardc]

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.

Query results of one point in Map Display:

geonames_th@asiapopthai:

Category: 78127 Layer: 1 Key_column: cat Database: C:\Users\rcooper\grassdata7\chula_4326\asiapopthai\sqlite\sqlite.db Type: Point Driver: sqlite Table: geonames_th Attributes:

name: Ban_Dong_Samphan countrycode: TH geonameid: 7680691 gtopo30: 198 featurecode: PPL longitude: 102.96903 cat: 78127 admin1code: 76 modification: 2012-01-21 timezone: Asia/Bangkok featureclass: P latitude: 17.7022 asciiname: Ban_Dong_Samphan alternatename: Ban_Dong_Samphan,ban_dng_samphanth,บ้านดงสัมพันธ์ population: 0

Id: 78127

Attribute table: alternatename field: Ban Dong Samphan,ban dng samphanth,บ้านดงสัมพันธ์

[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.

[marisn]

Replying to 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

[wenzeslaus]

Replying to marisn:

Replying to 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.