Skip to content

Changed double hyphens in TCW20 to em-dashes #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 29, 2025
Merged

Conversation

bleekere
Copy link
Contributor

This PR addresses #16

@trishaoconnor
Copy link
Contributor

These changes look good to me. Merging this to dev as they are straight-forward updates.

@trishaoconnor trishaoconnor merged commit 50ed615 into master Jan 29, 2025
1 check passed
@trishaoconnor trishaoconnor deleted the bleekere-16 branch January 29, 2025 12:03
Copy link
Contributor

@trishaoconnor trishaoconnor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for spotting this. Great work in bringing the TCWs in line with the Guidelines.

@bansp
Copy link
Member

bansp commented Jan 29, 2025

Just wondering, with a view to future practice: if the original was:

space+hyphen+hyphen+space

isn't it more natural, and perhaps closer to the author's intention, for the result to be

space+ndash+space

rather than

mdash

?

@ebeshero
Copy link
Member

We have been following a general rule that applies the en dash in ranges, as in 0–9, and the longer em dash for emphatic/dramatic separation to make an idea stand out, as in this particular edit. Here’s an explanation: https://www.grammarly.com/blog/punctuation-capitalization/dash/

I did find some discussion of an alternate approach preferred by some British English writers to set the en dash with spaces around it as you suggest. But we are following this other way to make our style consistent when we are providing guidance and information. After some discussion, though, we are not always following the em dash rule in the Guidelines examples if we are representing a different usage in a source document.

@bansp
Copy link
Member

bansp commented Jan 29, 2025

Thanks for the explanation, I was hoping that both styles were on an equal footing. Oh well, I'll try to bear that sad rule in mind ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants