Re: shift_jis,iso-8859-1(B

At 13:33 03/08/27 +0200, Terje Bless wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Bjoern Hoehrmann <derhoermi@gmx.net> wrote:
>
> >Same in their meta, on http://members.aol.com one can find
> >
> >  <meta http-equiv='Content-Type'
> >        content='text/html; charset=Shift_JIS,ISO-8859-1'>
> >
> >I've now seen such constructs about half a dozen of times. As the comma
> >is not allowed in charset named, could the validator have a special case
> >for them with a more user friendly error message?
>
>Yeah, we should detect this specifically. I've logged it as Bug #299 $Bc`G
(B
><http://www.w3.org/Bugs/Public/show_bug.cgi?id=299> $Bc`G
(Band will try to look at
>it for the next major revision (I'll need to rip out the current code and
>replace it to do this sanely I think).

I don't think you need to rip out the code. There is already
a mechanism built in to allow to say "don't use this 'charset',
use this other one". See the end of the 'charset.cfg' file at
http://dev.w3.org/cvsweb/validator/htdocs/config/charset.cfg.

Adding a line like:

shift_jis,iso-8859-1            X    shift_jis or iso-8859-1

will do the job. See sub transcode for the code. It will print out
Shift_JIS,ISO-8859-1 undefined; replace by shift_jis or iso-8859-1.

Regards,    Martin.