Ticket #10678 (closed enhancement: fixed)
spelling fixes from Debian - message, suppressed, included, occurrences
| Reported by: | sven | Owned by: | lasgouttes |
|---|---|---|---|
| Priority: | normal | Milestone: | 2.3.0 |
| Component: | general | Version: | 2.2.3 |
| Severity: | normal | Keywords: | |
| Cc: | skostysh, rgheck |
Description
Hi,
this is a patch for several misspellings we carry against 2.2.x currently.
There already a few more for which neither Nick nor I created a patch so far.
Would be cool if someone could merge this one as a starting point.
Attachments
Change History
comment:1 Changed 7 years ago by sven
In case someone cares, you can see the remaining spelling issues lintian knows about here:
https://lintian.debian.org/full/pkg-lyx-devel@lists.alioth.debian.org.html#lyx
comment:2 Changed 6 years ago by spitz
- Status changed from new to fixedinmaster
- Milestone changed from 2.2.x to 2.3.0
Thanks, I committed the patch at [b498646b2eb8/lyxgit] (master) and [64007533a76/lyxgit] (2.3.x) and also fixed those other listed errors I could find (except for collapsable/collapsible, which is a major change).
If there are remaining errors, please report.
comment:3 Changed 6 years ago by lasgouttes
We should do something once and for all about collapsable. Probably in 1.4 now.
comment:4 Changed 6 years ago by spitz
- Cc rgheck added
The collapsable/collapsible case seems to be ambivalent. Apparently, collapsable is a possible spelling. I have seen the statement that collapsable and collapsible are homonymous forms in many dictionaries and English usage guides, both of British and American origin, and back to the early 20th century (try a Google Books query on "collapsable collapsible").
On the other hand, some sources suggest that the "collapsable" alternative is meanwhile considered a "historic form", since "collapsible" is increasingly considered the more (or only) correct spelling. At least some modern dictionaries only have that form, and many spell checkers (including the one that currently checks my input in firefox) flag the -able form wrong.
So it's not really a spelling correction, but rather an orientation towards recent standardization processes (says the linguist in me).
comment:5 Changed 6 years ago by rgheck
Neither Oxford nor Merriam-Webster list "collapsable" at all, so far as I can see. One does see both listed in other places, but these are the UK authority, and at least one major US authority, so probably we should go with "collapsible".
It's an exception to the rule listed here. Probably that is the source of the confusion.
For what it's worth, the philosopher in me agrees with the linguist in Jürgen.
comment:6 Changed 6 years ago by spitz
OK, I propose we do the big change after 2.3.0 is released (I would wait for the release since the renaming will make cherry-picking more difficult).
OTOH, we could change the spelling in the docs already now (and for 2.3.x).
comment:7 follow-ups: ↓ 8 ↓ 9 Changed 6 years ago by rgheck
- Cc skostysh added
My main question would be to what extent this will affect our translators. If not so much, then I'd prefer we go ahead and do it now in 2.3.x, but that is presumably Scott's call.
comment:8 in reply to: ↑ 7 Changed 6 years ago by skostysh
Replying to rgheck:
My main question would be to what extent this will affect our translators. If not so much, then I'd prefer we go ahead and do it now in 2.3.x, but that is presumably Scott's call.
Fine with me.
comment:9 in reply to: ↑ 7 Changed 6 years ago by spitz
Replying to rgheck:
My main question would be to what extent this will affect our translators. If not so much, then I'd prefer we go ahead and do it now in 2.3.x, but that is presumably Scott's call.
What do you mean by "it"? The whole renaming or only the docs? I have just had a look at the manuals and, interestingly enough, "collapsable" does not occur but for the mention of the color (which would be part of the whole renaming).
comment:10 Changed 6 years ago by rgheck
Sorry, that was unclear.
It sounds as if there is not much to do in the docs.
In the source, if we did it before 2.3.0, then, as you say, it would make cherry-picking later commits from master easier. I guess there is some risk to doing it, but it seems very unlikely that it would actually cause problems.
comment:11 Changed 6 years ago by spitz
I also think the actual risk is low. Scott?
comment:12 Changed 6 years ago by skostysh
Go ahead for 2.3.0. Thanks.
comment:13 Changed 6 years ago by spitz
I have split the changes into four parts and committed to master:
- [648ddd25e/lyxgit] (comments/docs)
- [c466baaa5/lyxgit] (internals)
- [69d237cd7/lyxgit] (i7n)
- [434533187/lyxgit] (layouts)
comment:14 Changed 6 years ago by spitz
2.3.x at:
- [e040ccb0e86/lyxgit] (comments/docs)
- [a59301eaff5/lyxgit] (internals)
- [a71778de94d/lyxgit] (i7n)
- [9ae4b659dc8/lyxgit] (layouts)
comment:16 Changed 6 years ago by rgheck
- Status changed from fixed to closed
- Resolution set to fixed
LyX 2.3.0 is released.
comment:17 Changed 5 years ago by racoon
I just saw a number of error messages that stemmed from my using "collapsable" in user defined layouts. So I had to adjust them manually. Isn't that a format change which some converter should have taken care of?