[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Using Entity References in XSL Templates

Subject: RE: Using Entity References in XSL Templates
From: Arjun Ray <aray@xxxxxx>
Date: Mon, 24 Jan 2000 06:28:31 -0500 (EST)
arjun ray

On Fri, 21 Jan 2000, Mike Brown wrote:

> HTML 4 uses numeric entities ...

Please note that _character reference_ and _entity reference_ are distinct
categories.  In particular, the former is not an "entity" at all. 

> ... to refer exclusively to code positions in the document's character
> set, while named entities refer to character positions in either
> ISO-8859-1 or UCS, depending on which entity you're referring to.

Not quite.  In the entity declarations, the entities are defined in terms
of character references.  That's OK, because the connection between
ISO-8859-1/UCS and the document character set is determined by the SGML

> In HTML, &nbsp; is always ISO-8859-1 character number 160, i.e. a
> non-breaking space ... but &#160; is simply character number 160 in the
> character set of the document encoding, 

Oops.  Not at all.  Absolutely not.  The encoding has absolutely nothing,
repeat **NOTHING** to do with this.  The I18n spec is required reading:


(It's the job of the "entity manager" to transcode from the encoding to
the document character set.)

These references may be helpful also:



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.