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

Problems with recognition of dictionary files #585

Open
allefeld opened this issue Aug 23, 2024 · 0 comments
Open

Problems with recognition of dictionary files #585

allefeld opened this issue Aug 23, 2024 · 0 comments

Comments

@allefeld
Copy link

Under several circumstances, additional non-functional entries appear in the list of spelling languages.

– I copied several dictionaries for use with Spell Right from the hunspell_dictionaries collection maintained by Chromium, and I ran into a problem with the Oxford spelling dictionary, en_GB_oxendict.

If ~/.config/Code/Dictionaries (Linux) contains en_GB_oxendict.dic and en_GB_oxendict.aff, I get two entries in the language list, "en_GB_oxendict" + "en_GB_oxe", and neither of them works.

As a workaround, I invented the country "OX" and renamed the files to en_OX.dic and en_OX.aff, and now I get one language entry "en_OX", and it does work.

But it would be great if the extension could deal with such file names of the form language_country_variant automatically.

– The Chromium collection also contains files with extension .dic_delta, which are word lists which may be added to the .dic file.

If such a file is present in ~/.config/Code/Dictionaries, it is displayed as an additional language entry, which however does not work.

Merging the delta into the .dic file manually is not very hard (concatenate, sort, update number of words), but it would be more convenient if it could be automatically treated as an additional list of valid words.

If not, it should be ignored and not lead to an entry in the language list.

– For some reason, my ~/.config/Code/Dictionaries already contained a file en-US-10-1.bdic, maybe from another extension. This, too, leads to an entry in the language list which doesn't work. I believe files in this binary format are not supported by the extension, which is not a problem, but they should be ignored.

Thanks!

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

No branches or pull requests

1 participant