#2082 closed defect (fixed)
Description lists are unescapable
Reported by: | Christian Boos | Owned by: | Christian Boos |
---|---|---|---|
Priority: | normal | Milestone: | 0.10 |
Component: | wiki system | Version: | 0.9b1 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
Once a "::" is seen in an indented line, it's always recognized as a description list separator, and there's no way to escape it.
In a bulleted list, it's OK, therefore I can write the following:
- neither with
"!::"
(rendered as "!::") - nor with the code block syntax
{{{
::}}}
(rendered as::
) - nor with backticks
`::`
(rendered as::
).
But if I repeat the above 3 lines, this time without the bullet:
neither with
"!::"
(rendered as "!::") nor with the code block syntax{{{
::}}}
(rendered as::
) nor with backticks`::`
(rendered as::
).
The ::
turns each line in a description term, ignoring any form
of escape.
Attachments (0)
Change History (9)
comment:1 by , 19 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 19 years ago
Description: | modified (diff) |
---|---|
Milestone: | → 0.9.4 |
comment:7 by , 13 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Hi there,
Seems to still exists on up-to-date versions of Trac. Tested on online demo of 0.12. According to my understanding, following code should display items (desc1, desc2, desc3) in monospace font + no wiki processing of the two :
. This is not what happen.
Example below
{{{desc1::}}}:: blahblabla {{{desc2::}}}:: blahblabla {{{desc3::}}}:: blahblabla
renders as:
- {{{desc1
- blahblabla
- {{{desc2
- blahblabla
- {{{desc3
- blahblabla
follow-up: 9 comment:8 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Re-closing ticket assigned to milestone:0.10. Please create a new ticket for the issue.
comment:9 by , 9 years ago
Replying to Ryan J Ollos:
Re-closing ticket assigned to milestone:0.10. Please create a new ticket for the issue.
⇒ #12214
Ok, I guess since I wrote the DL stuff I'll take this one.