W3C home > Mailing lists > Public > www-validator@w3.org > November 2001

Re: Sixteen Bit Fonts

From: V.I.X <vixcc@yahoo.com>
Date: Mon, 19 Nov 2001 17:26:45 -0800 (PST)
Message-ID: <20011120012645.22951.qmail@web21101.mail.yahoo.com>
To: Martin Duerst <duerst@w3.org>, SherLok Merfy <brewhaha@freenet.edmonton.ab.ca>, Terje Bless <link@tss.no>
Cc: www-validator@w3.org
Lynx does support UTF-8.

--- Martin Duerst <duerst@w3.org> wrote:
> Hello SherLok,
> 
> Moving to UTF-8 as the core encoding in the validator was
> very helpful to do decent internationalization. Before that,
> many actually correct pages (but e.g. in some Asian encodings)
> were labeled as invalid, and on the other side, many mistakes
> with character encodings went unnoticed.
> 
> That we don't convert back from UTF-8 is part lazyness, and
> part an effort to move forward with internationalization.
> In the age of XML, a browser that doesn't support UTF-8 is
> quite a bit outdated. It's a pity that Lynx doesn't deal
> with UTF-8 yet; maybe you can do something about that.
> 
> [Please note that when supporting UTF-8, there is no need
> to display all characters. Displaying question marks or
> boxes for those characters than cannot be displayed is
> perfectly okay. Please also note that if you are working
> on some kind of Unix, there is terminal software that supports
> UTF-8.]
> 
> Regards,  Martin.
> 
> At 04:50 01/11/16 -0500, SherLok Merfy wrote:
> >On Thu, 29 Mar 2001, Terje Bless wrote:
> >
> > > On 12.03.01 at 17:45, '' <brewhaha@home.ecn.ab.ca> wrote:
> > >
> > > >   The validator seems to be insisting that I receive UTF-8, and Lynx
> > > >doesn't support it (can't support it without terminal software), so it
> > > >asks me to download documents from the validator (AltaVista's dijital
> > > >translator is just as arrogant). I hav iso-8859-1 selected in Lynx as my
> > > >preferred character set (font). The validator doesn't ask for that
> > > >information before delivering text/html;charset=utf-8.
> > >
> > > Yeah, we should probably check for preferred (or supported) client charset
> > > and convert it before returning results. Not sure how critical that is
> > > since UTF-8 is a superset of US-ASCII (IIRC) and most UAs can deal with it,
> > > but heeding client preferences is obviously preferable in this case.
> >
> >I'd appreciate it. No conversion is necessary for English.
> 


=====
--------------------------------------------
"People are of three types: those who know 
how to count, and those who don't..."
tAke a bReak! gEt eNtertained!!!
@ http://sallini.com/
----------------

__________________________________________________
Do You Yahoo!?
Find the one for you at Yahoo! Personals
http://personals.yahoo.com
Received on Monday, 19 November 2001 20:26:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:14:00 GMT