Skip to content

Does the current charset detector actually even work? #244

@jfhbrook

Description

@jfhbrook

I have reasons to believe that the charset library that's intended to guess at charsets for content-types is actually just trying to parse them out of the existing content-type mimetype string, and so is effectively a noop.

I figure the way to fix this is:

  1. Create a new charset abstraction that allows the same sort of registration as with mime types
  2. Set up some sane defaults. This will require some research, and the answer might be "none".
  3. Expose this functionality in the middlware/cli APIs and as a property on the ecstatic module

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