Bug report #15332
No UTF 8 encoding under processing geoalgorithms
|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|
attribute table entries in UTF 8 encoding aren`t preserved when executing a geoalgorithm under processing in QGIS
#1 Updated by Anita Graser about 4 years ago
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.
#3 Updated by Giovanni Manghi over 3 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
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?