Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Message-ID: <11530266.1156402203493.JavaMail.jira@brutus>
Date: Wed, 23 Aug 2006 23:50:03 -0700 (PDT)
From: "David Crossley (JIRA)" <jira@apache.org>
To: dev@forrest.apache.org
Subject: [jira] Updated: (FOR-448) Faulty treatment of a-Elements in
 html-pipeline
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/FOR-448?page=all ]

David Crossley updated FOR-448:
-------------------------------

    Attachment: anchorerrortestfiles.zip

The attachment was retrieved from our old issue tracker.
Contributed:  24/Feb/05 Ferdinand Soethe

> Faulty treatment of a-Elements in html-pipeline
> -----------------------------------------------
>
>                 Key: FOR-448
>                 URL: http://issues.apache.org/jira/browse/FOR-448
>             Project: Forrest
>          Issue Type: Bug
>          Components: Core operations
>    Affects Versions: 0.7
>         Environment: Windows XP SP2
>            Reporter: Ferdinand Soethe
>         Attachments: anchorerrortestfiles.zip
>
>
> 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  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira