-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
3.2.1
-
None
-
Not sure; I am a user, not admin
Write some text into the Rich Text editor and then select a space between two words. Choose Insert -> Symbol and then use mdash. It renders correctly. Save the page and look at what you get and it changes to a series of hyphens. Edit again and look at Wiki Code. Same thing happens with a space between the words and the mdash but it changes to three hyphens. The correct use of the mdash is to use it without spaces.
I looked in the database and there is an issue already reported for this and labeled fixed. It's CONF-501 and it's 6 years old. Perhaps this is a regressed bug?
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CONFSERVER-20077] mdash from Insert Symbol incorrectly rendered
Like the man says, emdashes should not need to be surrounded by spaces. This problem appears to be a bad interaction between the use of dashes in Wiki markup as enclosing symbols for strikethrough and use of repeated dashes for endash and emdash. The syntax not deterministically parseable, so instead can we have a macro or something that always renders as an emdash in Wiki markup? Or just don't translate a literal "—" into the three-dash equivalent?
Olin Sibert
added a comment - - edited Like the man says, emdashes should not need to be surrounded by spaces. This problem appears to be a bad interaction between the use of dashes in Wiki markup as enclosing symbols for strikethrough and use of repeated dashes for endash and emdash. The syntax not deterministically parseable, so instead can we have a macro or something that always renders as an emdash in Wiki markup? Or just don't translate a literal "—" into the three-dash equivalent? 
Hi davidledgerwood
Thanks for taking the time to raise this issue. This has been on our backlog now for 4 years now with very little movement in that time. Rather than leave this issue here I'm going to close it out as won't fix I believe that it better reflects that the status.
If the problem is raised again in the future we will re-address it.
Regards
Steve Haffenden
Confluence Bugmaster
Atlassian