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

RE: use cases for d-o-e

Subject: RE: use cases for d-o-e
From: "KIENLE, STEVEN C [IT/0200]" <steven.c.kienle@xxxxxxxxxxxxx>
Date: Thu, 10 Jan 2002 14:38:03 -0500
RE:  use cases for d-o-e
FWIW, I agree.  I've always thought that XSLT should be able to produce
human readable entities in the output.  So far I have been able to live
without it. Only I learned the hex equivalent to &nbsp;.  But even so, I
still feel that XSLT should be able to produce an entity of any sort in the
output.  Perhaps an <xsl:entity name=".."/> type of element.  I mean, you
can create processing instructions, elements, attributes and comments; why
leave entities out of the mix?


-----Original Message-----
From: naha@xxxxxxxxxx [mailto:naha@xxxxxxxxxx]
Sent: Thursday, January 10, 2002 2:22 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx; David Carlisle
Subject: Re:  use cases for d-o-e

Quoting David Carlisle <davidc@xxxxxxxxx>:

One of the reasons for adopting an XML notation is so that such
intermediate documents are human-readable.

I'm curious why the XML infoset didn't provide for unexpanded entity
references.  Aside from being parsed and serialized, the only other
operation they'd need to support is name().

 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.