Re: Validation: The Holy Grail

Both of them pass cyrillic text through ok. Interesting that
validator.w3.org transcodes it from windows-1251 to UTF-8. And
valet.webthing.com retains original windows-1251. But none of them seems to
exhibit it explicitly as meta and evidently use HTTP headers.

Regards,
Sergey


----- Original Message -----
From: "Nick Kew" <nick@webthing.com>
To: "Ushakov, Sergey N" <ushakov@int.com.ru>
Cc: <www-validator@w3.org>
Sent: Wednesday, November 21, 2001 3:13 AM
Subject: Re: Validation: The Holy Grail


>
> On Wed, 21 Nov 2001, Ushakov, Sergey N wrote:
>
> > Nick, now it's better :)   Now I also can see the ???? ???? :)   Though
my
> > system is cyrillic-enabled...
>
> What do you see when you use the established validators (like Page Valet
> or validator.w3.org) to validate your page?
>
>
> > I see the the validation result page comes in UTF-8 while the original
page
> > was in windows-1251.
> > Seems something goes wrong while converting between charsets...
> >
> > Can you consider retaining the original charset in the validation
result?
>
> I'm not sure.  The potential trouble with that is that the validator
> will produce output that is not valid as [charsetX], where charsetX
> is whatever a user's page is.
>
> Thinking aloud ..
>
> If I filter the *output* through iconv, I have two problems.
> Firstly, if iconv doesn't recognise your charset, I can't do it.
> Secondly, the XSLT module I'm using to transform the output
> has to be handled with care: if I start feeding it different
> encodings, I don't know how far it will cope.
>
> > Or maybe I can be of any help for handling cyrillics?
>
> Thank you.  I may try a couple of different ideas for dealing
> with it, and ask what you see for each one.  But I need to
> think about this a bit first.
>
> --
> Nick Kew
>
> Site Valet - the essential service for anyone with a website.
> <URL:http://valet.webthing.com/>

Received on Tuesday, 20 November 2001 20:59:53 UTC