7 | | I'm working on qgis, and it uses Qt with QStrings. They are unicode, and when |
8 | | using a non-unicode library one can chose between mystring.latin1(), |
9 | | mystring.ascii(), mystring.utf8() msytring.unicode() and mystring.local8Bit() |
10 | | for converting from unicode. So far, filenames use .local8Bit(), but attributes |
11 | | use .ascii(). I'm thinking I might change it to .local(Bit() too. |
12 | | The ideal(?) soultion would be if we could set the encoding to utf-8 for |
13 | | instance, and also note that in the .dbf header somewhere. Reverse on reading. |
| 4 | I'm working on qgis, and it uses Qt with QStrings. They are unicode, and when using a non-unicode library one can chose between mystring.latin1(), mystring.ascii(), mystring.utf8() msytring.unicode() and mystring.local8Bit() for converting from unicode. So far, filenames use .local8Bit(), but attributes |
| 5 | use .ascii(). |
| 6 | |
| 7 | I'm thinking I might change it to .local(Bit() too. |
| 8 | The ideal(?) soultion would be if we could set the encoding to utf-8 for instance, and also note that in the .dbf header somewhere. Reverse on reading. |