Opened 13 years ago
Closed 8 years ago
#10454 closed defect (fixed)
Whitespaces are killed in `backtick ` quotes
Reported by: | anonymous | Owned by: | Christian Boos |
---|---|---|---|
Priority: | normal | Milestone: | 1.3.2 |
Component: | wiki system | Version: | 0.12 |
Severity: | normal | Keywords: | css |
Cc: | Branch: | ||
Release Notes: |
Respect spacing within inline code style in the wiki |
||
API Changes: | |||
Internal Changes: |
Description
This is the same case as in Ticket #3925 but still not fixed for backquotes.
Trac-Wiki says:
{{{...}}} and `...` commands not only select a monospace font, but also treat their content as verbatim text, meaning that no further wiki processing is done on this text.
But this is only true for {{{
as in
three spaces between words
If I do the same thing with backticks like three spaces between words
or with curly braces inline as in three spaces between words
Trac helpfully collates the whitespaces.
If I do the same thing with backticks like `three spaces between words` or with curly braces inline as in {{{three spaces between words}}} Trac helpfully collates the whitespaces.
Defect present on 0.11.7 and 0.12.3dev
Attachments (0)
Change History (7)
comment:1 by , 13 years ago
Keywords: | css added |
---|---|
Milestone: | → next-major-0.1X |
comment:2 by , 9 years ago
Version: | 0.12 → 1.1dev |
---|
The original poster cites WikiFormatting#FontStyles
Issue still present in Trac 1.1. However, it may be better to accept this as a feature: the backticks are mostly used for code, and code rarely contains double spaces. Also, indentation is preserved:
three spaces between words
That way the user has a choice for when double spaces should collapse into a single space or not, ie {{{ ... }}}
vs backticks. Therefore, rather than changing code, we could change the documentation for this idiosyncratic feature.
comment:3 by , 9 years ago
Version: | 1.1dev → 0.12 |
---|
comment:4 by , 9 years ago
Milestone: | next-major-releases → next-dev-1.3.x |
---|---|
Owner: | set to |
Status: | new → assigned |
If there's no argument against code, tt { white-space: pre-wrap }
, I'll do that change on trunk once we start 1.3.x.
comment:7 by , 8 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
IIRC the change was intentional, so that we get wrapping.
Now that CSS 2.1 support is the norm, we could add:
tt, code, kbd, samp { white-space: pre-wrap }
.