Similar to bug 79276, auto correct and spell check should work when a language variant's files are not present but the primary language files are. A user tweeted < https://twitter.com/raju_thorat/status/507034090088853504 > that he has english-US installed, but as his default language for documents set to english-India, he is unable to use the english spellcheck as there isnt a check mark next to it < https://pbs.twimg.com/media/BwlY0PwCUAIsPMy.png >. I can confirm this behaviour happens in Linux Mint 17 with 4.3.1 (only USA has check mark) and Ubuntu 14.04 with 4.2.5 (only AU, CA, SA, UK, and USA have check marks).
Jay: I'll let you edit the title of the bugtracker since something's lacking :) Andras: I thought about doing about the same as this: http://cgit.freedesktop.org/libreoffice/core/commit/?id=a4f411ba62d4fd7fd4a61d1c9d326488d5e84ff5 but in the case of English, I'd rename en-US/acor_en-US to en/acor_en since English US would be the default. More generally, should we follow a general rule that would be one "generic variant" for each language? Eg: ja-JP/acor_ja-JP.dat would be renamed to ja/acor_ja (Still, there would be some cases to decide like: - acor_zh-CN - acor_zh-TW ) Any idea?
(In reply to comment #1) > Jay: I'll let you edit the title of the bugtracker since something's lacking > :) :D > Andras: I thought about doing about the same as this: > http://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=a4f411ba62d4fd7fd4a61d1c9d326488d5e84ff5 > but in the case of English, I'd rename en-US/acor_en-US to en/acor_en since > English US would be the default. Please dont forget dictionaries files as well, as that was the main reason of the bug. :) /share/extensions/dict-en/
Argh! Again I confused autocorrect and dictionaries :-( Forget my last comments then :-(
(In reply to comment #1) > Jay: I'll let you edit the title of the bugtracker since something's lacking > :) > > Andras: I thought about doing about the same as this: > http://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=a4f411ba62d4fd7fd4a61d1c9d326488d5e84ff5 > but in the case of English, I'd rename en-US/acor_en-US to en/acor_en since > English US would be the default. currently default autocorrect english datasets include: en-AU (Australia) en-US (United States) en-GB (Great Britain) en-ZA (South Africa) other English variants that do not have a specific autocorrect set are: Belize, Canada, Caribbean, Ghana, India, Ireland, Jamaica, Malawi, Namibia, New Zealand, Philippines, Trinidad, Zimbabwe as far as I know, most of those variants belong to Commonwealth countries so they derive from English GB root languages rather than English US. so my suggestion would be to clone the "acor_en-GB.dat" file and rename it to "acor_en.dat" and use that generic .dat file to pupulate the other languages. in other words we should have: en-AU (Australia) en-US (United States) en-GB (Great Britain) en-ZA (South Africa) en (Generic clone of en-GB) then if in second phase we found that some countries would have a better match with en-US, we could clone this as well and rename it to the proper locale. for example if you think English (Canada) is more similar to en-US rather than en-UK we should clone en-US and rename it as en-CA
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
This is still relevant today. Portuguese variants still lack this mechanism. - Angola Portuguese (pt-AN) and Mozambique (pt-MZ) Portuguese are closer to European Portuguese and they lack all writing aids. - European Portuguese (pt-PT) lacks the bundled Lightproof grammar checker available for Brazilian Portuguese. Though there are slight grammar differences, having it linked would be appreciated. - Brazilian Portuguese (pt-BR) lacks a bundled thesaurus, that exists on the European Portuguese version.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This bug is untouched yet. I am using Version: 6.0.7.3 in Ubuntu 18.04 yet I can not do spell check if I set language to English India I can not do spell correction or set language from spelling dialog box.
(In reply to Dr Anirban Mitra from comment #8) > This bug is untouched yet. I am using Version: 6.0.7.3 in Ubuntu 18.04 yet I > can not do spell check if I set language to English India I can not do spell > correction or set language from spelling dialog box. 6.0 and 6.1 are EOL. Please give a try to a recent LO version. (last one is 6.2.5). You can find it on LO ppa (see https://launchpad.net/~libreoffice/+archive/ubuntu/ppa)
Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
In my opinion, it should be each Native Language Community's decision to pick a fallback dictionary for their language, case-by-case, instead of using blanket solutions for them and risking inappropriate decisions (especially when an area's language history is tied with colonialism). I assume that we don't have that fallback mechanism implemented just yet, and that technical aspect could be the focus of this report. Once it has been implemented, we could have NLCs decide for themselves what sensible fallback should be used for their language (if any), until a proper dictionary (and grammar checker, and autocorrect list) is used. Sophie, what's your opinion?
(In reply to Stéphane Guillou (stragu) from comment #11) > In my opinion, it should be each Native Language Community's decision to > pick a fallback dictionary for their language, case-by-case, instead of > using blanket solutions for them and risking inappropriate decisions > (especially when an area's language history is tied with colonialism). > > I assume that we don't have that fallback mechanism implemented just yet, > and that technical aspect could be the focus of this report. > > Once it has been implemented, we could have NLCs decide for themselves what > sensible fallback should be used for their language (if any), until a proper > dictionary (and grammar checker, and autocorrect list) is used. > > Sophie, what's your opinion? Yes agreed, asking l10n teams what is their needs once the fallback is implemented would be the best approach.
spspinz, you maked this as "fixed" but there isn't any target or related commit. Was that a mistake?
I think I mixed it up with another bug I was reading at the time, my mistake and sincere apologies. Thank you for pointing it out! :) SPinz
*** Bug 156194 has been marked as a duplicate of this bug. ***
My dupe bug 156194 is about thesaurus files specifically (the request to fall back onto per-language files when per-language-variant/per-locale files are missing).