I think there are two use cases where keeping the entity references through
the transformation is a valid user requirement:
Yes but usually (or often or sometimes) the way to achieve that is not
to stop there expansion, but just to expand them, collapse them and then
fold them up at the end.
our NAG DTD which has a lot of (as in several thousand) entities each
entity is of the form:
<!ENTITY whatever '<start-entity xid="whatever"/> ..... <end-entity
xid="whatever"/>">
when transforming,
sometimes you let entities expand, sometimes
you change &whatever; to [[[[amp]]]]whatever; to suppress expansion and
sometimes
you want to let it expand, then do the transformation, then replace
wheaver is (now) between <start-entity xid="whatever"/> .....
<end-entity xid="whatever"/> replace it by &whatever; and make that the
new definition of the entity (and worry about what to do if different
instances of the entity reference got transformed to different things.
There's no universal right answer, so it's hard to sell (or even give
away:-) an "improved" identity transformation that "fixes" the problem.
David
________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.
This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs.
________________________________________________________________________
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--