[ 
https://jira.duraspace.org/browse/DS-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bram Luyten (@mire) updated DS-1092:
------------------------------------

    Status: More Details Needed  (was: Received)

changing status to needs more detail since I wasn't able to reproduce this in 
3.1
                
> 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&amp;Packard</i>:
>  <a href="http://linkwithparams.org/?param1&amp;param2";>linkwithparams</a>
>  
>  The result in XMLUI is then:
>  
>  <i>Hewlet&amp;amp;Packard</i>
> <a href="http://linkwithparams.org/?param1&amp;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 &nbsp; &#160; 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 &nbsp; &#160; 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)])&gt;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
For more information on JIRA, see: http://www.atlassian.com/software/jira

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to