Edgewall Software
Modify

Opened 13 years ago

Last modified 17 months ago

#8140 new enhancement

nested lists with multiple paragraphs should work properly

Reported by: jhammel@… Owned by:
Priority: high Milestone: topic-wikiengine
Component: wiki system Version: 0.12dev
Severity: normal Keywords: lists
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description

When you need to nest list with multiple paragraphs, the markup rendered is not what is expected. With the source input

 * lists can be used to denote all sorts of things
   
   '''Examples:'''
    - listing tickets
    - listing other things that need doing
    - laundry lists

 * this is another list item

 * and so is this

the markup rendered is

<ul><li>lists can be used to denote all sorts of things
</li></ul><p>
   
</p>
<blockquote>
<blockquote>

<p>
<strong>Examples:</strong>
</p>
</blockquote>
</blockquote>
<ul><li>listing tickets
</li><li>listing other things that need doing
</li><li>laundry lists
</li></ul><ul><li>this is another list item
</li></ul><ul><li>and so is this
</li></ul>

The markup desired is more like:

<ul><li>lists can be used to denote all sorts of things

<p>
<strong>Examples:</strong>
</p>

<ul><li>listing tickets
</li><li>listing other things that need doing
</li><li>laundry lists
</li></ul></ul>
<ul><li>this is another list item
</li></ul><ul><li>and so is this
</li></ul>

This can be worked around with the [[BR]] tag:

* lists can be used to denote all sorts of things[[BR]]'''Examples:'''
    - listing tickets
    - listing other things that need doing
    - laundry lists

 * this is another list item

 * and so is this

But this is non-semantic

Attachments (0)

Change History (8)

comment:1 by Christian Boos, 13 years ago

Component: renderingwiki system
Milestone: experimental
Owner: set to Christian Boos

In the current WikiEngine, empty lines are paragraph separators and they end a list. So even:

 * one
 
 * two

will currently create two lists.

In this situation, we could indeed try to keep those items in the same list.

comment:2 by anonymous, 11 years ago

In this situation, we could indeed try to keep those items in the same list.

Yes, especially in the case of ordered lists:

 1. one

 1. one

should be numbered 1. and 2., not 1. and 1.:

  1. one
  1. one

comment:3 by Christian Boos, 11 years ago

Keywords: lists added
Milestone: experimental0.13

comment:4 by Christian Boos, 11 years ago

Priority: normalhigh

comment:5 by Christian Boos, 11 years ago

Milestone: 0.130.14-wikiengine

comment:6 by Ryan J Ollos, 6 years ago

Owner: Christian Boos removed

comment:7 by anonymous, 6 years ago

There is a workaround described in the GHC wiki, namely:

Formatting list items with multiple paragraphs

TracWiki recognizes list items by their indentation and the asterisk preceding the first line. However if a second paragraph is started after an empty line, TracWiki will not consider it part of the list item despite the use of indentation. The "proper" way to do it is to separate the second and subsequent paragraphs by line break macros. For example:

 * A list item paragraph consists of a leading asterisk
   and indented text lines.
   [[br]][[br]]
   Using line breaks we can start another paragraph.
   [[br]][[br]]
   And another

How the above renders:

  • A list item paragraph consists of a leading asterisk and indented text lines.

    Using line breaks we can start another paragraph.

    And another

comment:8 by Christian Boos, 6 years ago

Right, that's a good workaround. You can also use \\ as an easier to type alternative to [[br]].

Wiki text Rendered
 * A list item paragraph consists of a leading asterisk
   and indented text lines.
   \\\\
   Using line breaks we can start another paragraph.
   \\\\
   And another
  • A list item paragraph consists of a leading asterisk and indented text lines.

    Using line breaks we can start another paragraph.

    And another

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.