You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Author Name: Tobias Wendorff (Tobias Wendorff)
Original Redmine Issue: 18782
Redmine category:data_source_manager
QGIS parses shapefiles with or without a CPG file to UTF-8 by default.
You can override this manually, but this often leads to trouble because staff is not always aware of this problem.
I've often seen statt loading ISO-8859-1 coded DBFs in QGIS. QGIS parses it as UTF-8 and when edits are done, things get messed up.
This results in ISO-8859-1 (loaded as UTF-8) and UTF-8 mixed entries, which get saved as UTF-8.
Is it possible to add some kind of dialog with asks for the charset, if no CPG file is available? Perhaps with a small preview window of characters making trouble. A dialog windows, like it's used for SRS/CRS ... even Microsoft Excel has such a dialog window :)
Related issue(s): #21264 (relates)
Redmine related issue(s): 13203
The text was updated successfully, but these errors were encountered:
Author Name: Tobias Wendorff (Tobias Wendorff)
Original Redmine Issue: 18782
Redmine category:data_source_manager
QGIS parses shapefiles with or without a CPG file to UTF-8 by default.
You can override this manually, but this often leads to trouble because staff is not always aware of this problem.
I've often seen statt loading ISO-8859-1 coded DBFs in QGIS. QGIS parses it as UTF-8 and when edits are done, things get messed up.
This results in ISO-8859-1 (loaded as UTF-8) and UTF-8 mixed entries, which get saved as UTF-8.
Is it possible to add some kind of dialog with asks for the charset, if no CPG file is available? Perhaps with a small preview window of characters making trouble. A dialog windows, like it's used for SRS/CRS ... even Microsoft Excel has such a dialog window :)
Related issue(s): #21264 (relates)
Redmine related issue(s): 13203
The text was updated successfully, but these errors were encountered: