Title: Message Title
|
|
|
|
I have investigated it in deep. At first, this is XMLUI "bug" only. Because it is not bug, it is a feature. The general solution and also my simple workaround are described bellow.
To sum up - working with XML correctly needs to follow rules, especially to follow some defined XML schema. The DRI document has own schema too. This schema does not define well known HTML entities like nbsp and all such entities is escaped (I say "amped") during any XML transformation/processing.
In our case: Introductory text is processed via the SimpleHTMLFragment aspect, where is transformed (using standard XML processing tools) and put into the DRI document. And according to the DRI schema all unknown entities are escaped ("amped"). And will be escaped during any XML operation on any DRI document, so to take care of such entities ad hoc (e.g. in the SimpleHTMLFragment) does not help because the pipeline in XMLUI consists of many steps working with a DRI document.
The general solution is to define all (or usual) HTML entities. So they will be valid in all DRI documents. The question is if this goes against the DRI purpose (because we do not need any HTML entity in a DRI document for the pipeline process itself). Another question is what is "the simple HTML" allowed in the Introductory text.
The simple workaround is to switch the escaped entities back during the final XSLT (DRI -> HTML) transformation. I have written two simple templates which do the work. Both of them are recursive - the first handles (copies) XHTML and calls the second which handles the entities. They are quite general - the input (as a parameter) could be any XML document/fragment and output is the same XML with the entities unescaped ("unamped"). So having th Introductory text as an input leads to what you want. Jordan Piščanc has already tested them and can confirm they work.
The templates can be dowloaded (together with simple use example) here:
https://kic-internal.ics.muni.cz/~krejvl/xslt-xmlui-dspace-entities/
Anyone can try to call for example:
xsltproc unespace-ent.xsl test.xml
|
|
|
|
|
|
|
The trouble is that the ampersand "&" character is always translated
into XML "&" in XMLUI in case this ampersand is stored in any "HTML"
form (like introductory text for community/collection). This behaviour
could be quite embarassing - assume we want to have a well-formed XHTML so
there is for example:
<i>Hewlet&Packard</i>:
<a href=""
|
|
|
|
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
