You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As someone on Discord suggested, the current implementation can cause problems for people from GB, Australia, or Canada, where some words might be spelt differently than in the US. Then Aspell will detect things that shouldn't be detected.
I just found the option --extra-dicts with which we can support US English and GB English, etc., at the same time.
But it does not let us switch languages. So we can't say English and German, for example.
With aspell -a --lang=en_US --extra-dicts=en_GB it accepts both spellings of initialise, whereas just one would always throw a mistake:
We could either add this as default flags in the Aspell class or add it as a config value as was suggested in #45
The text was updated successfully, but these errors were encountered:
If we allow the value to be configurable you can put in any Aspell local you want. If they are not from the same language, there will be an exception but that way you could put en_US and en_GB or just de_DE 🤔
I am german myself and all projects I have seen so far use English. Just sometimes single german words when working with different APIs.
As someone on Discord suggested, the current implementation can cause problems for people from GB, Australia, or Canada, where some words might be spelt differently than in the US. Then Aspell will detect things that shouldn't be detected.
I just found the option
--extra-dicts
with which we can support US English and GB English, etc., at the same time.But it does not let us switch languages. So we can't say English and German, for example.
With
aspell -a --lang=en_US --extra-dicts=en_GB
it accepts both spellings of initialise, whereas just one would always throw a mistake:We could either add this as default flags in the
Aspell
class or add it as a config value as was suggested in #45The text was updated successfully, but these errors were encountered: