Re: HTML - i18n / NCR & charsets

Drazen Kacar (Drazen.Kacar@public.srce.hr)
Wed, 27 Nov 1996 06:03:08 +0100 (MET)


From: Drazen.Kacar@public.srce.hr (Drazen Kacar)
Message-Id: <199611270503.GAA15596@jagor.srce.hr>
Subject: Re: HTML - i18n / NCR & charsets
In-Reply-To: <v0300780aaec1659ae557@[205.149.180.135]> from Walter Ian Kaye at "Nov 26, 96 07:42:16 pm"
To: walter@natural-innovations.com (Walter Ian Kaye)
Date: Wed, 27 Nov 1996 06:03:08 +0100 (MET)
Cc: www-html@w3.org

Walter Ian Kaye wrote:
> 
> Not sure what "existing practice" is, or is expected to be, but if a person
> is using a certain charset specified via HTTP (or <meta http-equiv=...>),
> then why would numeric charrefs be needed in the first place? The only
> possible reason would be to include characters in Latin-1 or Unicode, since
> the page would already have all characters in the specified charset available.
> Thus, usage of NCRs for a non-Unicode/Latin1 charset makes no sense, and any
> such pages deserve to break. :-)

But you didn't consider cheesy little editors (I don't mean Emacs).
They will do it for you. On Windows, in particular. When you're not using
Latin 1, they will assume you do, because, what else could you be using?

And they will insert entities, tons of them. Some of them will be in the
128-159 range. These will be numeric, others will be simbolic.

Thus, usage of HTML editors makes no sense, and their authors deserve to
break a leg. >:)

-- 
Life is a sexually transmitted disease.

dave@fly.cc.fer.hr
dave@zemris.fer.hr