Skip to content
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

Correct spelling mistake. #5831

Merged
merged 2 commits into from
Nov 15, 2018
Merged

Correct spelling mistake. #5831

merged 2 commits into from
Nov 15, 2018

Conversation

bakert
Copy link
Contributor

@bakert bakert commented Nov 12, 2018

Very simple fix of typo in fonts.md.

It's "Non-existent" not "Non-existant".

"Nonexistent" (no hyphen) is also the most common current usage so switched to that form.

It's "Non-existent" not "Non-existant".

"Nonexistent" (no hyphen) is also the most common current usage so switched
to that form.
@benmccann
Copy link
Contributor

Google says 10.3m results for "nonexistent" and 20m for "non-existent", so I'm not sure that the non-hyphenated version really is more common

@bakert
Copy link
Contributor Author

bakert commented Nov 13, 2018

Maybe "common" isn't the right word. It is the nature of hyphens to atrophy and die as a formulation becomes more common. (See e-mail versus email.) For me the worm has turned on nonexistent so I prefer to go with what I see as a near-inevitable (not nearinevitable!) future. Merriam-Webster has it without a hyphen.

All that said the Times of London is still using the hyphen (at least in 2016) and I am 100% happy to return the hyphen if you prefer. I mostly just wanted to correct the spelling (it's "non-existant" in the source right now not "non-existent"). So if you prefer the hyphen I can return it. LMK.

@benmccann
Copy link
Contributor

I personally would prefer Non-Existent. Partially because I don't see the need to change something that's fine now, but mostly because it's just the way I'm used to seeing it. In any case I know I'm being a bit nit picky :-)

Thank you for fixing the typo!!

simonbrunel
simonbrunel previously approved these changes Nov 14, 2018
Copy link
Member

@simonbrunel simonbrunel left a comment

Choose a reason for hiding this comment

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

I'm fine with both, though, translation tools I use return Nonexistent (WR, Linguee). If that makes debate, we could also change the title for Missing Fonts which is IMO more straightforward to understand for non native English.

@bakert
Copy link
Contributor Author

bakert commented Nov 14, 2018

The Gordian Knot is cut! "Missing Fonts" pushed. Thanks!

@simonbrunel simonbrunel added this to the Version 2.8 milestone Nov 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants