Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on Should we render double hyphen as an em dash?

Post

Should we render double hyphen as an em dash?

+2
−2

Some places render "--" (double hyphen) as "—" (em dash).

Currently Codidact does not -- so these are left as double hyphens in both the edit preview and a rendered post (like that).

Would it be useful for Codidact to automatically render double hyphen as an em dash? Are there settings in which that would be a problem? When explaining command line flags such as --verbose I'd expect the double hyphens to be inside a code block. Would only rendering as an em dash outside of code blocks be sufficient to avoid problems?

I'm not sure if this is feasible yet. I just wanted to judge community interest in the idea first.

Workaround

In the meantime, if you want your post to contain an em dash, you can use "&mdash;" which renders correctly as "—". Putting it inside a code block allows displaying the raw text as &mdash; rather than —.

Note that it's "mdash" rather than "emdash" - &emdash; won't work.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Word is horrible with this - don't do it here! (3 comments)
Word is horrible with this - don't do it here!
manassehkatz‭ wrote over 1 year ago

Which reminds me of my problems with Microsoft Word. I need to find out how to turn that off. One of the reasons it is a problem with Word is if you convert to a PDF it stays an mdash and then if you copy/paste to put it in plain text somewhere (I do this routinely) now it is a non-ASCII character. As already noted elsewhere, this is especially a problem with -- as part of command-line parameter notation.

trichoplax‭ wrote over 1 year ago

The answer explaining why we shouldn't do this has plenty of upvotes (including mine) so I'm pretty sure we're safe from this happening. I have been thoroughly convinced that my suggestion is a bad idea...

Which reminds me of my problems with Microsoft Word. I need to find out how to turn that off.

Why not ask that question on PowerUsers?