Re: Encoding designation in non-HTML sites

Ah... so my message did go through. Bad morning with the mailer...

Actually, most of the Javascript sites are probably in
Latin-1................

XML files are typically in UTF-16 (my brain is *definitely* going), but
smart folks who expect to live through trading files tag the files as (and
then store them in) UTF-8. That's so that your Windows PC and your Sun
server can both read the files reliably without having to look at the Byte
Order Mark.

Sorry if my recreation of this message seems timesome... ;-)

Addison

----- Original Message -----
From: Suzanne Topping <stopping@rochester.rr.com>
To: <www-international@w3.org>
Sent: Tuesday, April 11, 2000 10:14 AM
Subject: Re: Encoding designation in non-HTML sites


>
> ----- Original Message -----
> From: <addison@globalsight.com>
>
> >In the end, a "Javascript page" is still in HTML and can have a META tag
> just like normal >HTML. Most such pages, however, either indicate the
> encoding in the http header (which >is a much better place for it) or
don't
> bother to indicate the encoding at all (which is bad, >but not a
surprise).
>
> This must have been the handling for the (multiple) sites that I looked
> at... surprizing.
>
> >XML files are, by default, Unicode encoded (UTF-8, I believe), unless
> tagged otherwise.
>
> That's right, I knew this... sheesh, the brain is starting to go.
>
> As a point of interest, what I was looking for was an UTF-8 encoded site,
> and I couldn't find one! I came across an interesting assortment of stuff
> (such as the Java sites with no encoding specification), but no Unicode
> sites.
>
> Oh well... proof that it remains more the future than the present.
>
>

Received on Tuesday, 11 April 2000 14:58:12 UTC