Re: Bug Report (sublists in pp2latex)
[email protected] Tue, 19 Mar 2002 11:20:46 +0100
| Newsgroups | perl.perlpoint |
|---|---|
| Message-ID | <[email protected]> |
---MOQ10165332464433c289f29cf76f35460f87871cbd58 Content-Type: text/plain Content-Transfer-Encoding: 7bit (see attached text) Regard, Lorenz ---MOQ10165332464433c289f29cf76f35460f87871cbd58 Content-Type: text/plain; name="repl.txt" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="repl.txt" To: [email protected] Re: Bug Report Hello Robert, thank you for your bug report. Yes, you are completely right, the implementation of the shift paragraphs > and < is not correct. It works for simple lists, but you get into trouble with nested lists, especially if the last list item is not on top level, for example a list like * Item 1 of outer list * Item 2 of outer list o item one of inner list o item two of inner list (and that's it!) In HTML this woud be implemented as <ul> <li> Item 1 of outer list <li> Item 2 of outer list <ul> <li> item one of inner list <li> item two of inner list (and that's it!) </ul> </ul> The problem is, as you pointed out, that the parser does not allow a < (shift back) at the end of a list. Sublists cannot be placed at the end of a list. At least one item should come after the sublist. In pp2html I tried to keep track of the level and to rewind the indentation level by adding an appropriate number of </ul>. In pp2latex the implementation is totally buggy (it just ignores sublists). It think that the parser should be changed so that the following PerlPoint code would be correct: =Background *Blah *Blah *A Sublist > *Foo *Bar < Some thing else The first *Blah starts a (toplevel) list. The > starts a second level list (and does not terminate the toplevel list) The < should terminate the second level list and the "Something else" (which is a normal text paragraph) terminates the toplevel list. Probably the Parser should implement a stack of lists. Another problem is the continuation of numbered lists, which may be interrupted by an example (verbatim) block. I will discuss this further with Jochen, who knows the details about the parser. Hopefully we will soon come up with a solution. Reards, Lorenz ---MOQ10165332464433c289f29cf76f35460f87871cbd58--