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
I would have expected the following locale tag combinations to be accepted and triggering the spelling checker:
crk
crk-Cans
crk-CA
crk-US
crk-Cans-CA
crk-Cans-US
Of these, only the following tags are recognised:
crk-CA
crk-Cans
That is, all combinations ending in US are unrecognised, and the -Cans- ones are only recognised without the country part. This seems a bit inconsistent, and will make it hard for end users to know what to type in order to trigger the spelling checker.
I don't know whether any of this is related to the fact that the crk locale code has been added erroneously to LO - as crk-CN instead of -CA (China vs Canada), but given that crk-CA is accepted, I would assume not.
The text was updated successfully, but these errors were encountered:
According to https://bugs.documentfoundation.org/show_bug.cgi?id=73973 the correct BCP-47 codes have been added to LO since version 5.2.0, and the corresponding language entries have been available as «Cree, Plains, Latin» and «Cree, Plains, Syllabics». But when setting the text language to any of those, the speller is not triggered, even though both variants are found in the dictionary search path.
I have tried to add the following entries to VoikkoHandlePool.py, but it did not help:
I have the following zhfst files installed and recognised by voikkospell:
These are aksi recognised by LO-Voikko in Preferences > Language prefs > Voikko.
In the file pythonpath/VoikkoHandlePool.py the following entries are found for crk:
I would have expected the following locale tag combinations to be accepted and triggering the spelling checker:
Of these, only the following tags are recognised:
That is, all combinations ending in US are unrecognised, and the -Cans- ones are only recognised without the country part. This seems a bit inconsistent, and will make it hard for end users to know what to type in order to trigger the spelling checker.
I don't know whether any of this is related to the fact that the crk locale code has been added erroneously to LO - as crk-CN instead of -CA (China vs Canada), but given that crk-CA is accepted, I would assume not.
The text was updated successfully, but these errors were encountered: