LISTSERV mailing list manager LISTSERV 15.5

Help for XML-L Archives

XML-L Archives

XML-L Archives


Next Message | Previous Message
Next in Topic | Previous in Topic
Next by Same Author | Previous by Same Author
Chronologically | Most Recent First
Proportional Font | Monospaced Font


Join or Leave XML-L
Reply | Post New Message
Search Archives

Subject: Re: special characters
From: Richard Lander <[log in to unmask]>
Reply-To:Richard Lander <[log in to unmask]>
Date:Thu, 25 Mar 1999 10:06:36 -0500

text/plain (41 lines)

 Why is it that characters such as a grave need to be reprented by character
references? They are part of the ASCII set, are they not? Or is there a
subset of ASCII that is defined as 'main' and the rest as 'others' that need
to be specially represented?

I used UTF-8 encoding because I thought I was doing something wrong. I
started without any encoding but did not get the results I wanted. I tried
UTF-16 too but it didn't work at all because, I assume, my file was not a
UTF-16 file but plain ASCII text.



----- Original Message -----
From: Chris Maden <[log in to unmask]>
To: <[log in to unmask]>
Sent: Thursday, March 25, 1999 9:08 AM
Subject: Re: special characters

> [JR Gardner]
> > Would a UTF-16 declaration solve that?
> Not if the content isn't UTF-16.  From the original mail, I recall
> that it was ISO 8859-1, but I may be mis-remembering.  UTF-16 doesn't
> need a declaration.
> Character sets, encodings, and the interactions between them are
> confusing.  If you're using a text editor and don't know your
> character sets, use only US-ASCII characters, with entity or numeric
> character references to any other characters.  Since US-ASCII is a
> strict subset of UTF-8, you don't need an encoding declaration.
> -Chris
> --
> <!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN"
> "<URL> <TEL>+1.617.499.7487
> <USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek>

Back to: Top of Message | Previous Page | Main XML-L Page



CataList Email List Search Powered by the LISTSERV Email List Manager