field with encoded string (e.g. chinese) doesn't display correctly on screen #1780
Assignees
Labels
Comments
lixun910
added a commit
to lixun910/geoda
that referenced
this issue
Dec 9, 2018
lixun910
added a commit
to lixun910/geoda
that referenced
this issue
Dec 9, 2018
|
This is a report from a Chinese scholar. |
lixun910
added a commit
to lixun910/geoda
that referenced
this issue
Dec 9, 2018
lixun910
added a commit
to lixun910/geoda
that referenced
this issue
Dec 9, 2018
lixun910
added a commit
to lixun910/geoda
that referenced
this issue
Dec 10, 2018
1 GDAL/OGR after 1.9.0 can read encoding information (if coded) from DBF file via LDID byte (Language Driver ID), and then automatically recode strings to UTF-8 2. This will cause reading some encoded DBF file (e.g. Chinese GB2312) in GeoDa directly as UTF-8 strings, and this will mislead the user with missing encoding information. 3. By set GDAL/OGR flags SHAP_ENCODING and ENCODING to "", GeoDa can then read DBF with original encoding and then user can choose correct encoding type via menu Table->Encodings. 4. A option "Select encoding" is added when load datasource for merging, in which user won't have Table->Encodings menu for the to-be-merged data.
lixun910
added a commit
to lixun910/geoda
that referenced
this issue
Dec 10, 2018
lixun910
added a commit
to lixun910/geoda
that referenced
this issue
Dec 11, 2018
|
GeoDa 1.12.1.179 (macOS Mojave, 10.14.1). Same problem.
|
|
Please use v181 which is temporary at http://geodacenter.github.io/download_nightly.html <http://geodacenter.github.io/download_nightly.html>
Thanks
… On Dec 11, 2018, at 10:01 PM, Ashitacarl ***@***.***> wrote:
GeoDa 1.12.1.179 (macOS Mojave, 10.14.1).
Same problem.
<https://user-images.githubusercontent.com/45187310/49848019-a7fc8280-fd98-11e8-92d4-fe2fd29e985c.png>
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <#1780 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACT8T26IqM6ozcIdsJyWyK2LH0LRVzFsks5u4I2vgaJpZM4ZJ7dV>.
|
|
And you also need to use Table->Encoding to select proper encoding (e.g. Chinese Simplified GB2312)
… On Dec 11, 2018, at 10:02 PM, Xun Li ***@***.***> wrote:
Please use v181 which is temporary at http://geodacenter.github.io/download_nightly.html <http://geodacenter.github.io/download_nightly.html>
Thanks
> On Dec 11, 2018, at 10:01 PM, Ashitacarl ***@***.*** ***@***.***>> wrote:
>
> GeoDa 1.12.1.179 (macOS Mojave, 10.14.1).
>
> Same problem.
>
> <https://user-images.githubusercontent.com/45187310/49848019-a7fc8280-fd98-11e8-92d4-fe2fd29e985c.png>
> —
> You are receiving this because you were assigned.
> Reply to this email directly, view it on GitHub <#1780 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACT8T26IqM6ozcIdsJyWyK2LH0LRVzFsks5u4I2vgaJpZM4ZJ7dV>.
>
|
|
Don't know why, but seems still not working properly... |
|
@Ashitacarl sorry, this version is not up-to-date, please try to download again |
|
GeoDa 1.12.1.181 (macOS Mojave, 10.14.1). Fix verified.
|
|
Great. Thanks.
…On Tue, Dec 11, 2018 at 10:53 PM Ashitacarl ***@***.***> wrote:
GeoDa 1.12.1.181 (macOS Mojave, 10.14.1).
Fix verified.
[image: 1780-3]
<https://user-images.githubusercontent.com/45187310/49849577-dc277180-fd9f-11e8-8feb-97998b493788.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1780 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACT8T-GiviNupes8-oj05_MJ1rBO2Cfqks5u4JnOgaJpZM4ZJ7dV>
.
|
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This also causes an issue when merge datasource with encoded strings. For example, when a chinese city name is used as key to merge.
The text was updated successfully, but these errors were encountered: