Bug report #15332
No UTF 8 encoding under processing geoalgorithms
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: |  Victor Olaya | ||
| Category: | Processing/QGIS | ||
| Affected QGIS version: | 2.16.0 | Regression?: | No |
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | fixed/implemented |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 23264 |
Description
attribute table entries in UTF 8 encoding aren`t preserved when executing a geoalgorithm under processing in QGIS
History
#1
Updated by Anita Graser over 8 years ago
Confirmed.
When testing with GDAL/OGR algorithms, the following warning is displayed
Warning 1: One or several characters couldn't be converted correctly from UTF-8 to ISO-8859-1. This warning will not be emitted anymore.
Seems like Processing is trying to produce output in System default encoding rather than preserve the input encoding.
#2
Updated by Alexander Bruy over 8 years ago
- Operating System deleted (
Windows)
When executing ogr2ogr from command line directly, encoding also lost, so I think this is not a Processing issue.
BTW, works fine with native algs.
#3
Updated by Giovanni Manghi almost 8 years ago
- Priority changed from High to Normal
- Status changed from Open to Feedback
ogr based algs have (on purpose) an optional parameter "additional creation options" that can be used to add, for example
-lco ENCODING=UTF-8
and that will take care of encoding of outputs.
QGIS native algs works as expected.
SAGA and GRASS algs are breaking encoding, and that's already reported also in other tickets.
Could we close this?
#4
Updated by Christian Metzger almost 8 years ago
Hello, yes I can confirm that the utf 8 encoding will be preserved when executing qgis algs. The ticket can be closed.
Thank you very much!
#5
Updated by Giovanni Manghi almost 8 years ago
- Status changed from Feedback to Closed
- Resolution set to fixed/implemented