On Thursday, September 22, 2022 9:04:53 AM MST Andres Salomon wrote: > FYI, chromium's documentation about this stuff is here: > > https://chromium.googlesource.com/chromium/deps/hunspell_dictionaries/+/refs > /heads/main/README.chromium
Thanks for that link. > It appears that the dictionary files are versioned, and those versions > are matched in chromium's source code: > > https://chromium.googlesource.com/chromium/src/+/refs/heads/main/components/ > spellcheck/common/spellcheck_common.cc My understanding from reading this documentation is that the versioning of the dictionaries is to facilitate automatic updating of the dictionary files. If we could coax Chromium to use a system-wide directory, that would no longer be an issue because updates would be handled by apt-get. > My understanding is that .config/chromium/Dictionaries isn't the source > of dictionaries; when you add a language to chromium, a .bdic file for > that (already installed) language doesn't show up there unless you > first add the language in the "Preferred languages" chromium config > screen, and then go into the spelling config screen and manually select > that language under "Use spell check for". My testing indicates that, when you add a new language under the languages Chromium config screen, it then adds an entry to the spelling config screen. If you turn that entry on (disabled by default), Chromium downloads the appropriate .bdic to ~/.config/chromium/Dictionaries from some central repository hard coded into Chromium's code. This would explain why simply dropping a .bdic into that directory is not enough to enable it as an option in Chromium. Given how this is structured, I am not sure how easy it would be to convince Chromium to use a system-wide directory for the .bdic storage. -- Soren Stoutner so...@stoutner.com
signature.asc
Description: This is a digitally signed message part.
