This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 197 - Use I18N::Charset to support IANA Aliases.
Summary: Use I18N::Charset to support IANA Aliases.
Status: REOPENED
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.6.1
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: Terje Bless
QA Contact: qa-dev tracking
URL: http://www.w3.org/mid/3E1DD04E.804020...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-19 00:34 UTC by Terje Bless
Modified: 2010-01-19 16:40 UTC (History)
1 user (show)

See Also:

Attachments

Description Terje Bless 2003-04-19 00:34:01 UTC 
Validator should probably use I18N::Charset  or some similar method to enable
support for the character encoding name aliases found in the IANA registration
database.
Comment 1 Terje Bless 2003-05-24 07:47:46 UTC 
Targetting 0.7.0.
Comment 2 Terje Bless 2004-09-01 13:05:08 UTC 
Hmmm. Or import the database and use the new config facility?

Nominating for 0.7.0, but may have to bump it. Not sure how to deal with it yet.
Comment 3 Bj 2004-09-06 21:15:37 UTC 
We would implement this using Encode::Alias I think. Once we use Encode.pm. 
Which won't be 0.7.0 as far as I understand.
Comment 4 Terje Bless 2004-09-09 18:25:58 UTC 
Actually I think Encode::Alias and I18N::Charset would complement eachother,
but in either case it makes sense to do this when we look at Encode.pm.

Since that doesn't look to be for 0.7.0, I'm retargetting this bug.
Comment 5 Olivier Thereaux 2009-02-13 15:13:13 UTC 
We've had Encode::Alias functional for a while and there's been no complaint about unrecognized charset aliases. Any specific reason why we should be looking at I18N::Charset too?