Bug report #20556

processing doesn't output a shapefile's encoding

Added by Tobias Wendorff almost 2 years ago. Updated over 1 year ago.

Status:Feedback
Priority:Normal
Assignee:-
Category:Processing/Core
Affected QGIS version:3.5(master) Regression?:No
Operating System:Microsoft Windows (any) Easy fix?:No
Pull Request or Patch supplied:No Resolution:
Crashes QGIS or corrupts data:No Copied to github as #:28376

Description

The tools in "processing", like "split vector layer" don't write any information about encoding of shapefiles.
Postprocessing the files is very hard because you either have to know where they come from and which charset they might be in.


Related issues

Related to QGIS Application - Bug report #20614: Problem with encoding when using GRASS (v.generalize) thr... Closed 2018-11-23

History

#1 Updated by Tobias Wendorff almost 2 years ago

  • Subject changed from processing doesn't output encoding for shapefiles to processing doesn't tell about shapefile's encoding

#2 Updated by Tobias Wendorff almost 2 years ago

  • Subject changed from processing doesn't tell about shapefile's encoding to processing doesn't tell output shapefile's encoding

#3 Updated by Tobias Wendorff almost 2 years ago

  • Subject changed from processing doesn't tell output shapefile's encoding to processing doesn't output a shapefile's encoding

#4 Updated by Giovanni Manghi almost 2 years ago

  • Category changed from Unknown to Processing/Core
  • Status changed from Open to Feedback

If I'm not wrong this is change compared to 2.18, correct?

#5 Updated by Alexander Bruy over 1 year ago

  • Related to Bug report #20614: Problem with encoding when using GRASS (v.generalize) through QGIS added

#6 Updated by Giovanni Manghi over 1 year ago

Just made a test on 3.6 and seems good to me. Please check again.

Also available in: Atom PDF