Uploaded image for project: 'Forrest (Retired)'
  1. Forrest (Retired)
  2. FOR-448

Faulty treatment of a-Elements in html-pipeline

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.7, 0.8
    • 0.8
    • Core operations
    • None
    • 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

      Attachments

        1. html-to-document.xml.diff
          2 kB
          Jim Dixon
        2. anchorerrortestfiles.zip
          3 kB
          David Crossley

        Activity

          People

            Unassigned Unassigned
            f.soethe Ferdinand Soethe
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: