Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <708500861.1203328834952.JavaMail.jira@brutus>
Date: Mon, 18 Feb 2008 02:00:34 -0800 (PST)
From: "Joerg Schaible (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Commented: (CONFIGURATION-164) Charset detection
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CONFIGURATION-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569833#action_12569833 ] 

Joerg Schaible commented on CONFIGURATION-164:
----------------------------------------------

That algorithm seems bloated for our use case, since it also tries to extract the encoding from the HTML settings/page. We might as alternative use a simpler approach like it is done in the XmlHeaderAwareReader in XStream, which is based on the JDK's PushBackInputStream and implemented similar to a normal InputStreamReader.

> Charset detection
> -----------------
>
>                 Key: CONFIGURATION-164
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-164
>             Project: Commons Configuration
>          Issue Type: New Feature
>    Affects Versions: Nightly Builds
>            Reporter: Emmanuel Bourg
>            Priority: Minor
>             Fix For: 2.x
>
>
> Detecting automatically the charset of the file based configurations would be a
> nice addition. When the file has no byte order mark defining the charset, we
> might apply a detection algorithm similar to the one implemented in Mozilla.
> There is at least one Java library providing this feature, jchardet :
> http://sourceforge.net/projects/jchardet

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