Re: Character Data

• Mail folder: html-archive
• Next message: Corprew Reed: "Re: Character Data"
• Previous message: Murray Maloney: "Re: Character Data"
• Maybe in reply to: Daniel W. Connolly: "Re: Character Data "

Date: Thu, 22 Sep 94 15:41:50 EDT
Message-id: <9409221940.AA02474@ulua.hal.com>
Reply-To: connolly@hal.com
Originator: html-wg@oclc.org
Sender: html-wg@oclc.org
Precedence: bulk
From: "Daniel W. Connolly" <connolly@hal.com>
To: Multiple recipients of list <html-wg@oclc.org>
Subject: Re: Character Data 
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: HTML Working Group (Private)

In message <9409221414.aa01254@dali.scocan.sco.COM>, Murray Maloney writes:
>> 
>> In message <9409221044.aa00721@dali.scocan.sco.COM>, Murray Maloney writes:
>> ><P>
>> >Because certain special characters are subject to interpretation 
>> >and special processing, information providers and 
>> >browser implementors should follow 
>> ><A HREF="#spclchars"> these guidelines </A>
>> 
>> This paragraph is misleading. In HTML 2.0, there are no characters
>> that are "subject to interpretation and special processing."
>> There's just ISO8859-1 -- a bunch of character glyphs, two or
>> three control characters, and the rest are not used.
>
>As the later text states, at least space and hyphen may be
>interpreted or processed differently in different contexts
>or by specific processing engines -- like H&J.  I think that
>it is imprudent not to make this potential clear from the outset.

Ok. I thought you were talking about SDATA style behaviour
where entities get mapped to different things on different
systems.

Never mind.


Dan