Replies: 3 comments 6 replies
-
I then found out the root cause is likely to be the fact hunspell has different license for en_GB than the others So, I assume you tried to mitigate the issue of having an en_GB with a more restrictive license, by creating a dictionary focused on en_GB from another sources. |
Beta Was this translation helpful? Give feedback.
-
What I don't get is where the old files comes from. I feel like it should be mentioned I'm working on documenting where to add words, and the fact I don't have an idea from where this "old file" comes is a kind of issue to me. I mean you say its license is MIT, but where does this file comes from. Thanks |
Beta Was this translation helpful? Give feedback.
-
The intent of en_GB-MIT is to have a MIT license of the en-GB dictionary. CSpell cannot ship dictionaries with a GPL like license. The original en-GB word list was created years ago from a mixed set of sources, some of them my own. It did not use the en-GB Hunspell file in the beginning. That was added later not realizing that it contained a GPL license. When the issue was raised, an attempt at splitting out the words into two different lists was made. But I didn't have the time to finish it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I found out that these two dictionaries exist.
I'm using a discussion, so we can easily dig into each details
Beta Was this translation helpful? Give feedback.
All reactions