197 2003-04-19 00:34:01 +0000 Use I18N::Charset to support IANA Aliases. 2010-01-19 16:40:16 +0000 1 1 1 Unclassified Validator check 0.6.1 Other other REOPENED http://www.w3.org/mid/3E1DD04E.8040204@assoft.com P2 normal --- 1 link link ot www-validator-cvs oldest_to_newest 446 0 link 2003-04-19 00:34:01 +0000 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. 499 1 link 2003-05-24 07:47:46 +0000 Targetting 0.7.0. 2201 2 link 2004-09-01 13:05:08 +0000 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. 2251 3 bjoern 2004-09-06 21:15:37 +0000 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. 2306 4 link 2004-09-09 18:25:58 +0000 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. 23714 5 ot 2009-02-13 15:13:13 +0000 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?