Bug report #21949

Processing OGR based tools: encoding changed in outputs

Added by Bernd Vogelgesang over 5 years ago. Updated over 5 years ago.

Status:Open
Priority:High
Assignee:-
Category:Processing/OGR
Affected QGIS version:3.6.2 Regression?:Yes
Operating System:Linux Mint Easy fix?:No
Pull Request or Patch supplied:No Resolution:
Crashes QGIS or corrupts data:No Copied to github as #:29764

Description

When trying to buffer a point dataset with the GDAL buffer vector function, the attributes get obviously encoded to sth else than the original UTF-8.
All special characters become a ? on black rhombic background. When manually setting the resulting layer to windows1252, the special characters are visible again.
This seems to apply to other GDAL/OGR functions besides buffer as well.

Besides that I would like to second Tobias's feature request #21279 to change the output format from ESRI shapefile to GPKG, cause shape format (dbase) might cripple any GPKG-based workflow. And as GPKG is UTF-8 by default, the encoding issues would/could/should be gone as well, I hope.

QGIS 3.6.2 on Linux Mint

History

#1 Updated by Jürgen Fischer over 5 years ago

  • Description updated (diff)

#2 Updated by Giovanni Manghi over 5 years ago

  • Crashes QGIS or corrupts data changed from Yes to No
  • Priority changed from Normal to High

Confirmed also here (same OS and same QGIS version). I also think this wasn't an issue in the past. Note: applying manually ISO8859-1 also "works".

#3 Updated by Giovanni Manghi over 5 years ago

  • Subject changed from OGR processing: Encoding changed from UTF-8 to windows1252 to Processing OGR based tools: encoding changed in outputs

Also available in: Atom PDF