-
Bug
-
Resolution: Fixed
-
Medium
-
2.5.7, 2.5.8, 2.6-dr1, 2.6.0
-
None
The monospace macro/markup doesn't get properly rendered when there are certain characters surrounding the {{ or }}.
Text is not rendered in monospaced font in these cases:
{anchor:baz}{{foobar}}(1)
[sd]{{foobar}}(1)
!http://wikis.sun.com/images/icons/plus.gif!{{foobar}}(1)
{{ foobar}}
{{foobar }}
{{ foobar }}
This bugs makes it difficult or impossible to use Confluence for technical documentation.
Look at http://confluence.atlassian.com/display/TEST/Monospace+Bug for examples
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
[CONFSERVER-9889] Monospace text {{ }} is not rendered when next to macros, links or images
Todd Day
added a comment - This is also a problem
{{enum}}s
The trailing s prevents the macro from working.
Todd Day
added a comment - This is also a problem
{{enum}}s
The trailing s prevents the macro from working.
Kristina Chodorow
added a comment - I'm using Confluence 3.0, where it also occurs. I'm trying to render monospaced JSON with some fields in italics, which, due to this bug, is completely impossible at the moment.
Please fix this soon!
Kristina Chodorow
added a comment - I'm using Confluence 3.0, where it also occurs. I'm trying to render monospaced JSON with some fields in italics, which, due to this bug, is completely impossible at the moment.
Please fix this soon! 
Stefan Hansel
added a comment - I was just helped by atlassian with a similar problem (with bold-style).
A small macro is able to solve most of this problems (unfortunately doesn't work in richt-text-edit, so is just a small workaround
. Please see the attached screenshot.
Just use another name and <tt>$body</tt> instead of <b>$body</b>.
Stefan Hansel
added a comment - I was just helped by atlassian with a similar problem (with bold-style).
A small macro is able to solve most of this problems (unfortunately doesn't work in richt-text-edit, so is just a small workaround . Please see the attached screenshot.
Just use another name and <tt>$body</tt> instead of <b>$body</b>. 
Antranig Basman
added a comment - This issue is very important to me. I can't see any reason that text like "Each of these {{InlineEdit}}s must be configured" is considered invalid. I would like to have, for example, monospaced text which can be followed by normal text without an intervening space. Right now, the above markup simply becomes "unclosed" and corrupts the rest of the text.
Antranig Basman
added a comment - This issue is very important to me. I can't see any reason that text like "Each of these {{InlineEdit}}s must be configured" is considered invalid. I would like to have, for example, monospaced text which can be followed by normal text without an intervening space. Right now, the above markup simply becomes "unclosed" and corrupts the rest of the text. The same behaviour is still observable with Confluence 2.9.2
Additionally it is impossible to begin or end monospaced text with curly braces like:
{{\{text\}}}
while
{{.\{text\}.}}
works fine. For some reason even the first example does work in this Jira instance...
As a workaround you can put empty color-macros at the beginning and/or end:
{{{color:red}{color}\{text\} {color:red}{color}}}
Ron Koerner
added a comment - - edited The same behaviour is still observable with Confluence 2.9.2
Additionally it is impossible to begin or end monospaced text with curly braces like:
{{\{text\}}}
while
{{.\{text\}.}}
works fine. For some reason even the first example does work in this Jira instance...
As a workaround you can put empty color-macros at the beginning and/or end:
{{{color:red}{color}\{text\} {color:red}{color}}}
Several of the original and most annoying limitations of monospace markup raised by this issue have been fixed in recent versions of Confluence. The first three lines in the description now work correctly.
Monospace markup currently requires a letter as the first and last characters inside the braces, and a word break or punctuation character immediately outside the braces.
I'm going to close this issue as fixed and I've raised
CONF-22236to cover the remaining limitations. Please move your vote/watch to that issue if you're still concerned about these limitations.CONF-22236also has some workarounds that you can use in your documents until we resolve that issue.