You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Create a new charset abstraction that allows the same sort of registration as with mime types
Set up some sane defaults. This will require some research, and the answer might be "none".
Expose this functionality in the middlware/cli APIs and as a property on the ecstatic module
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: