Bug report #14704
Encoding problems with Processing toolbox
|Affected QGIS version:||2.18.4||Regression?:||Yes|
|Operating System:||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:||fixed/implemented|
|Crashes QGIS or corrupts data:||Yes||Copied to github as #:||22665|
Some qgis algs create outputs where the attribute tables have encoding issues. Examples are buffer and dissolve. Maybe others are also affected (an example that works as expected in "voronoi polygons").
Sample data attached.
I'm using QGIS 2.14.1 on Windows 10 through OSGeo4W setup.
I noticed that if I process a vector layer (i.e. UTF-8 encoded geojson) with QGIS algorithm (i.e. crop, Voronoi, etc) through Processing toolbox, result layer has attribute table with question marks instead expected characters. While if I run the same algorithm through QGIS menu, result layer is correctly encoded.
I noticed also that this affects GDAL/OGR algorithms, besides QGIS algorithms, while not SAGA algorithms.
For reference I open a question first here: http://gis.stackexchange.com/questions/190137/qgis-algoritms-have-encoding-problems
#7 Updated by Giovanni Manghi almost 4 years ago
- Operating System deleted (
- Affected QGIS version changed from 2.14.1 to 2.18.4
- OS version deleted (
- File portugal_continental_3763_1.zip added
Saber Razmjooei wrote:
In my case, the problem was with path.
The bug is present in 2.18 and 2.14.
Tested on 2.18.4 on Windows special chars in paths seems to be not an issue for QGIS algs. They are an issue for GDAL/OGR ones (will file a different ticket).
Encoding problems in outputs do not seem to be a problem with GDAL/OGR algs or with all QGIS algs, but certainly a few QGIS algs are affected, like dissolve and buffer (and maybe others).
#14 Updated by Giovanni Manghi almost 4 years ago
- Status changed from Feedback to Closed
- Resolution set to fixed/implemented
Alexander Bruy wrote:
Can't reproduce with latest 2.18 using attached sample data and native buffer and dissolve algorithms.
confirmed, if some other tool is affected please reopen this one.