maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Siveton (JIRA)" <>
Subject [jira] Closed: (DOXIA-134) Apt parser issues
Date Tue, 12 May 2009 11:08:45 GMT


Vincent Siveton closed DOXIA-134.

         Assignee: Vincent Siveton
       Resolution: Fixed
    Fix Version/s:     (was: 1.2)

I fixed the issues about multiline and linebreak in table cells in [r773851|]

> Apt parser issues
> -----------------
>                 Key: DOXIA-134
>                 URL:
>             Project: Maven Doxia
>          Issue Type: Bug
>          Components: Module - Apt
>    Affects Versions: 1.0-alpha-8
>            Reporter: Lukas Theussl
>            Assignee: Vincent Siveton
>             Fix For: 1.1.1
>         Attachments: actual.txt, DOXIA-134-headerCell.patch, expected.txt
> I did the following experiment: using the SinkTestDocument that I attached at DOXIA-101
I generated two text documents, one by dumping the model directly into a text sink, the other
by piping it through the current apt sink, parsing the result with the apt parser and dumping
it into the same text sink as before. The results should be the same since the second chain
corresponds to the 'identity transformation', ie piping a document through a parser and sink
should give you the original document. I attach the two text files for comparison, here are
the differences:
> # the parser swallows newlines between text elements
> # a paragraph within a list item is swallowed
> # verbatim text within a definition list item is not processed correctly
> # the closing of a definition list is not processed correctly
> # table header cells are not recognized and newlines within table cells are not processed
> Point 1 is not severe by itself because newlines are not significant in apt source documents,
however, two newlines are, so I am not sure if it doesn't have consequences (eg within table
> Point 5 has partially been fixed by the patch Vincent attached at DOXIA-50.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message