cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Heinicke (JIRA) <j...@apache.org>
Subject [jira] Closed: (COCOON-2063) NekoHTMLTransformer needs to set the default-encoding of the current system to work properly with UTF-8
Date Thu, 08 May 2008 05:38:57 GMT

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

Jörg Heinicke closed COCOON-2063.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2-dev (Current SVN)
                   2.1.12-dev (Current SVN)

As Vadim mentioned at http://marc.info/?l=xml-cocoon-dev&m=120905050708311&w=4 the
NekoHTMLTransformer had an issue with converting String to byte[] using OS' default encoding
rather than keeping the string - and so had the NekoHTMLGenerator when reading a request parameter
value. These both issues are fixed in SVN and maybe caused the symptoms you saw. Closing the
issue for now. Feel free to reopen it if problem still persists.

> NekoHTMLTransformer needs to set the default-encoding of the current system to work properly
with UTF-8
> -------------------------------------------------------------------------------------------------------
>
>                 Key: COCOON-2063
>                 URL: https://issues.apache.org/jira/browse/COCOON-2063
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: HTML
>    Affects Versions: 2.1.11, 2.2
>            Reporter: Alexander Klimetschek
>            Assignee: Jörg Heinicke
>            Priority: Minor
>             Fix For: 2.1.12-dev (Current SVN), 2.2-dev (Current SVN)
>
>         Attachments: NekoHTMLGenerator_BRANCH2_1_X.patch, nekohtmltransformer-encoding.patch
>
>
> The NekoHTMLTransformer uses the cyberneko HTMLConfiguration for tidying html. Unfortunately
it does not use the system's current encoding as default, instead you have to set a property
to set your encoding. But this varies from one OS to another, so the best solution is to set
this property automatically in the NekoHTMLTransformer depending on what Java uses as defaultCharset:
>             config.setProperty("http://cyberneko.org/html/properties/default-encoding",
Charset.defaultCharset().name());

-- 
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