[
https://jira.duraspace.org/browse/DS-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23614#comment-23614
]
Scott Phillips commented on DS-1092:
------------------------------------
This is an interesting problem. I added that bit about escaping the & so
that it would be easier for everyone when adding text to the introduction. I
might add, that I work for "Texas A&M University" so that character comes up a
lot around here :). I think a better place to fix this problem would be in the
Java code where it places that text into the SAX pipeline and add a special
check to see to prevent the & from being escaped if it is followed by "amp;".
> XHTML/XML entities (ampersand) encoded bad in XMLUI
> ---------------------------------------------------
>
> Key: DS-1092
> URL: https://jira.duraspace.org/browse/DS-1092
> Project: DSpace
> Issue Type: Bug
> Components: XMLUI
> Affects Versions: 1.8.0
> Reporter: Jordan Piščanc
> Priority: Major
>
> 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="http://linkwithparams.org/?param1&param2";>linkwithparams</a>
>
> The result in XMLUI is then:
>
> <i>Hewlet&amp;Packard</i>
> <a href="http://linkwithparams.org/?param1&amp;param2";>linkwithparams</a>
>
> The first line cause only wrong diplayed text while the link on the second
> line is malfunctional (the params are corrupted).
> Another example where entities like   are not displayed correctly:
> JSPUI:
> http://demo.dspace.org/jspui/handle/123456789/8456
> display correct..
> But
> XMLUI:
> http://demo.dspace.org/xmlui/handle/123456789/8456
> is not displayed correctly :(
>
>
> Why the classic   are not displayed correctly within XMLUI??
>
> I read some topics here:
>
> http://web.archiveorange.com/archive/v/hxciqlvx4589UJszcXvi
> http://www.mail-archive.com/[email protected]/msg12678.html
>
> I think that ther is something complained with the trasformation and one XSLT
> in the pipeline of Cocoon where the main collection or comunity is
> generated... where the XSLT's feature 'Disable-ouput-escaping' is not
> correctly used?!
>
> I tried for example to modify
>
> collection-view.xsl
>
> <xsl:if
> test="string-length(dim:field[@element='description'][not(@qualifier)])>0">
> <p class="intro-text">
> <xsl:copy-of
> select="dim:field[@element='description'][not(@qualifier)]/node()"
> disable-output-escaping ="yes" />
> </p>
> </xsl:if>
>
> but disable-output-escaping is not permitted in xsl:copy-of
>
> other solutions??
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Learn Windows Azure Live! Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for
developers. It will provide a great way to learn Windows Azure and what it
provides. You can attend the event by watching it streamed LIVE online.
Learn more at http://p.sf.net/sfu/ms-windowsazure
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
