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?

Parent

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 moderator attention?
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! (2 comments)
Post
+7
−0

For the reasons you already alluded to, rendering -- as em-dash by default is dangerous, see discussions on a Similarly Engineered site. This is particularly true in question titles since they don't support formatting options.

I think that at least in communities where verbatim reproduction can be paramount for correctly stating questions and answers, automatic conversions should be avoided as much as possible. This is true all the more since

  • a new user will often not know how to protect -- using code tags, making questions prone to misinterpretation (considering that a majority of questions likely come from "first-time" visitors)
  • an inclined user who wants "typographically" fancy appearance can still explicitly enter e.g. an em-dash using the workardound you already mentioned, or by unicode code-point, i.e. Alt+0151
History
Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

Questioners won't always know to use backticks (2 comments)
Questioners won't always know to use backticks
trichoplax‭ wrote 10 months ago

The post you link to discusses questions, rather than answers, which makes me realize what I was overlooking:

An answerer will generally put -- inside a code block or inline code, so it won't get converted, but someone asking a question is less likely to know to do this, so we can't rely on it.

I was leaning in favour of automatically converting to em dash, but you've changed my mind with this.

AdminBee‭ wrote 10 months ago · edited 10 months ago

Yes, I think this summarizes the key issue rather nicely. I have edited the answer to highlight that aspect more prominently (so that future readers have it all "at a glance").