Skip to content

Should rust-uchardet depend on rust-encoding? #1

@emk

Description

@emk

It looks like encoding is rapidly becoming the encoding library of choice, and uchardet would be much more useful if it could actually transcode data directly. We have several choices:

  1. Keep uchardet as a strictly low-level library, and create a new library which depends on both it and encoding.
  2. Depend on encoding, and let the linker decide whether or not to pull in all of encoding.
  3. Depend on encoding, and create a second internal library that provides the low-level API without pulling in everything.

I'm leaning towards (2), with the option of splitting out (3) at a latter date if somebody asks for it. But I'm open to suggestions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions