Ken
> >What I did find, however, was that if I put
> >the replacement string in a variable and then invoked that I got what I
> >wanted.
>
> Not sure what you are saying there, but whatever it is I'm guessing
> you are going beyond the bounds of the XPath data model.
It seems that variables are not parsed. If you ask to send the contents of a
variable to the output stream it will appear exactly as defined, without any
of the replacements taking place (hopefully)
> > > What is the use case for entity renaming?
> >
> >Two main ones:
> >
> >1) Entity reference retention ( -> rather than  )
> >2) Localization/easier comprehension for people with limited English
(&et;
> >or ∧ rather than &)
>
> I'm quite sure both of those are covered in XSLT 2 character
> maps. Both of them are mapping a Unicode character into an entity
> reference ... not preserving input entities nor creating an entity
> for a string of characters.
1) is most definitely not. You can't preserve entities by mapping  
back to
2) you can do now I think it through a bit further. But you could not
replace &et; with &.
Martin
-- DSDL members discussion list To unsubscribe, please send a message with the command "unsubscribe" to dsdl-discuss-request@dsdl.org (mailto:dsdl-discuss-request@dsdl.org?Subject=unsubscribe)Received on Tue Dec 13 20:35:45 2005
This archive was generated by hypermail 2.1.8 : Wed Dec 14 2005 - 04:48:02 UTC