forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [JIRA] Commented: (FOR-448) Faulty treatment of a-Elements in html-pipeline
Date Fri, 25 Feb 2005 08:33:42 GMT
The following comment has been added to this issue:

     Author: Ferdinand Soethe
    Created: Fri, 25 Feb 2005 2:33 AM
       Body:
Forget to add:

The problems are already there when I request index.xml, so as Ross suggested it is likely
an html2document.xsl issue.

Ferdinand
---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-448?page=comments#action_12094

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-448

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-448
    Summary: Faulty treatment of a-Elements in html-pipeline
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Forrest
 Components: 
             Core operations
   Versions:
             0.7

   Assignee: 
   Reporter: Ferdinand Soethe

    Created: Thu, 24 Feb 2005 12:25 PM
    Updated: Fri, 25 Feb 2005 2:33 AM
Environment: Windows XP SP2

Description:
After noticing that anchor elements in html-files got lost in the Forrest default pipeline,
I did some test with a sample document (before and after are included) and found that named
anchors either get completely lost or messed up pretty bad. Even text within them is sometimes
lost.

The lines refer to original and translated file.

Original     Translated   Looks   Function
  line          line
------------------------------------------
   16            157       ok       gone     
   <a> element is completely lost
   
   
   22            162       bad       ok      
   
   there are now 2 <a> elements
   <a name="anchor2"></a>Anchor 2<a href="#anchor1">Anchor 2</a>
   and unfortunately twice the text!
   
   29            166       ok       gone
   <a> element is completely lost
   
   35            171       bad      gone
   <a> element and text within it is completely lost!
   
   42            176       ok       gone 
   <a> element is completely lost
   
   49            181       ok       gone
   <a> element is completely lost  


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message