james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clément Denis (JIRA) <mime4j-...@james.apache.org>
Subject [jira] [Created] (MIME4J-230) Provide a way to override the default charset for mime parts without specified charset or no Content-Type header
Date Tue, 21 May 2013 13:39:15 GMT
Clément Denis created MIME4J-230:
------------------------------------

             Summary: Provide a way to override the default charset for mime parts without
specified charset or no Content-Type header
                 Key: MIME4J-230
                 URL: https://issues.apache.org/jira/browse/MIME4J-230
             Project: James Mime4j
          Issue Type: Improvement
          Components: parser (core)
    Affects Versions: 0.7.2
            Reporter: Clément Denis


When the charset or the Content-Type header is missing from a part in a multipart message,
the charset defaults to us-ascii, as it should according to RFC 2046/5.1.

For some applications (especially those dealing with non-US mime messages), this default results
in broken encoding most of the time.

The default charset is hardcoded in DefaultBodyDescriptor, and cannot be easily customized.
There should be a way to define this default charset.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message