[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #63589] spelling mistakes found by codespell
From: |
Dave |
Subject: |
[bug #63589] spelling mistakes found by codespell |
Date: |
Tue, 7 Feb 2023 22:55:41 -0500 (EST) |
Follow-up Comment #23, bug #63589 (project groff):
[comment #19 comment #19:]
> Mmmm. "shareable" but not "browseable"?
English has little consistency about whether to keep a silent e before adding
-able. Occasionally pronunciation will demand retaining the e ("noticeable"
losing the "e" would change the "c" from soft to hard), but absent such a
consideration, it's hard to discern a rule.
merriam-webster.com lists "shareable" and "sharable," "livable" and
"liveable," "smokable" and "smokeable," "tamable" and "tameable," and
"movable" and "moveable" as valid options. For some, it denotes one or the
other as less common, but obviously still common enough to meet whatever
threshold is required to make it into a major dictionary.
Other words aren't as flexible. "Dyeable" and "handleable" require retaining
the e. But "reputable," "arguable," "advisable," "refutable," and, yes,
"browsable" (if you believe Merriam-Webster) are wrong if you keep the e. So
is "breathable," even though "breathe," not "breath," is the root.
English! Barely us(e)able but still lov(e)able.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63589>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [bug #63589] spelling mistakes found by codespell, (continued)
- [bug #63589] spelling mistakes found by codespell, G. Branden Robinson, 2023/02/04
- [bug #63589] spelling mistakes found by codespell, G. Branden Robinson, 2023/02/04
- [bug #63589] spelling mistakes found by codespell, G. Branden Robinson, 2023/02/04
- [bug #63589] spelling mistakes found by codespell, G. Branden Robinson, 2023/02/04
- [bug #63589] spelling mistakes found by codespell, G. Branden Robinson, 2023/02/04
- [bug #63589] spelling mistakes found by codespell, G. Branden Robinson, 2023/02/04
- [bug #63589] spelling mistakes found by codespell, G. Branden Robinson, 2023/02/04
- [bug #63589] spelling mistakes found by codespell, G. Branden Robinson, 2023/02/04
- [bug #63589] spelling mistakes found by codespell, G. Branden Robinson, 2023/02/04
- [bug #63589] spelling mistakes found by codespell, G. Branden Robinson, 2023/02/05
- [bug #63589] spelling mistakes found by codespell,
Dave <=