Skip to content

Support for getting encoding from .cpg files #247

Closed

Description

@karimbahgat

Describe the feature request

Non-standard but commonly accepted cpg file that specifies which text encoding to use. Would make for more robust handling of files and special cases. Main problem is figuring out which strings are used to represent encodings, appears to be non-standard.

May want to support both read and write support for this.

Contributions

  • I am interested in implementing the described feature request and submit as a PR.

Activity

  1. JamesParrott commented on Oct 18, 2022

    @JamesParrott
    Collaborator

    I'm not familiar with arc, but from googling, .cpg files do seem to be nothing more than one line text files. However their very nature does invite the following questions:

    Are the .cpg files themselves encoded in utf-8, or what?
    Or do all the encoding strings to be supported only use ascii characters, so it shouldn't matter if it's not utf-16?

  2. karimbahgat commented on Jan 10, 2023

    @karimbahgat
    CollaboratorAuthor

    Not sure at the moment, I suspect using ascii or utf8 would be a safe assumption and work in most cases. I haven't looked very hard though. Let me know if you find out, or want to submit a PR :)

  3. JamesParrott commented on Jul 25, 2026

    @JamesParrott
    Collaborator

    Completed by #441, released in 3.1.6.

    Tested with the latin1 shapefile (and anecdotally with a UTF16 shapefile from QGIS). Round trip tests to be added later (possibly with support for optionally writing .cpg files).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions