mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joonas Koivunen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (VYSPER-4) Handle non UTF-8 encoded streams
Date Fri, 14 Sep 2012 10:49:07 GMT

    [ https://issues.apache.org/jira/browse/VYSPER-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455714#comment-13455714

Joonas Koivunen commented on VYSPER-4:

This is rather old issue, and apparently it has remained dormant as XMPP only allows UTF8.
However vysper's "nbxml" project is usable far beyond vysper itself, and I'd like to move
in and provide this functionality (most likely as a optional "feature" of the parser, so that
vysper code does not need modification). Basically I'd like to look into supporting ISO-8859-1
through <?xml version="1.0" encoding="iso-8859-1"?> PIs. If there are no objections
I'll be posting a patch hopefully soon.

I haven't read the latest sources (currently git svn cloning the vysper repo, will be mirroring
it at least a bit to github) but as I understood, PI's are currently ignored by the xml tokenizer,
and thus are unhandled completly. So, I'll be looking at the tokenizer first.
> Handle non UTF-8 encoded streams
> --------------------------------
>                 Key: VYSPER-4
>                 URL: https://issues.apache.org/jira/browse/VYSPER-4
>             Project: VYSPER
>          Issue Type: Bug
>          Components: connection handshake, transport
>            Reporter: Bernd Fondermann
> currently, UTF-8 encoding is hardcoded in stream parser, regardless what the initiating
party is providing

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

View raw message