james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] Updated: (MIME4J-118) MIME stream parser handles non-ASCII fields incorrectly
Date Thu, 19 Feb 2009 17:06:01 GMT

     [ https://issues.apache.org/jira/browse/MIME4J-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Oleg Kalnichevski updated MIME4J-118:
-------------------------------------

    Attachment: mime4j-118-field.patch

Markus,

Let's try a different approach to the problem. The new patch changes representation of a MIME
field in the API by replacing name/value/raw tuple with Field interface. If you like this
patch better, I'll look into changing the representation of raw field content from String
to ByteArrayBuffer or similar immutable class. As a next step I would look into resolving
MIME4J-116.

Oleg

> MIME stream parser handles non-ASCII fields incorrectly
> -------------------------------------------------------
>
>                 Key: MIME4J-118
>                 URL: https://issues.apache.org/jira/browse/MIME4J-118
>             Project: JAMES Mime4j
>          Issue Type: Bug
>            Reporter: Oleg Kalnichevski
>            Assignee: Oleg Kalnichevski
>             Fix For: 0.6
>
>         Attachments: mime4j-118-field.patch, mime4j-118.patch
>
>
> Presently MIME stream parser handles non-ASCII fields incorrectly. Binary field content
gets converted to its textual representation too early in the parsing process using simple
byte to char cast. The decision about appropriate char encoding should be left up to individual
ContentHandler implementations.
> Oleg

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message