forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [JIRA] Commented: (FOR-241) forrest undoes entity resolution
Date Thu, 24 Feb 2005 06:46:42 GMT
The following comment has been added to this issue:

     Author: David Crossley
    Created: Thu, 24 Feb 2005 12:46 AM
I have done some investigation. The issue only happens on the link/@href and a/@href and img/@src
attributes. Other attributes are okay, e.g. link/@title and img/@alt

In 0.7-dev, request http://localhost:8888/body-dreams.html ... View-source shows that the
a/@href attributes have been mangled. Now in the main/webapp/sitemap.xmap go to the <map:resource
name="skinit"> at line 208. Replace the html serializer with an xml serializer. View-source
for body-dreams.html shows that the entities are intact. So it is the html serializer on the
internal pipeline that "fixes" the href attributes.

Using today's cocoon-trunk and their "Hello world" sample, adding an <a> element, shows
that there is no such problem.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: FOR-241
    Summary: forrest undoes entity resolution
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Forrest
             Core operations
   Fix Fors:

   Reporter: Diwaker Gupta

    Created: Mon, 2 Aug 2004 9:00 PM
    Updated: Thu, 24 Feb 2005 12:46 AM

If I have a url like this inside the XML source:

validate-xdocs fails because it wants the literal & to be typed out as
&amp; instead. So I correct it to become:;type=1

However, the generated HTML has the entity resolution UNDONE!:

This HTML fails validation as 4.01 transitional.

David Crossley adds:
There is a demonstration of the problem in the document
The ampersand in the link element text is properly handled but
the ampersand in the link href attribute is not.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message