Quite often, because users don't know about the hiphenation tool, they force the hiphenation manually. As result, the spelling checker correclty flags the wrong hyphenation, identifying as a false compounds. The problem is that in the suggested corrections, it creates several compounds that does not exist. This flaw only happens when we have the terms written in lower letters. With capital letters, the suggestions are correct. This must happen in the other languages too. Someone (László?) will have to download VERO to check this flaw, as I can't check in other languages. Examples: en-contradas subse-quente convo-cado nú-mero ofi-cial contra-ditório as-sinatura ce-lebração an-tecipados pe-nalidades di-reito EN-CONTRADAS SUBSE-QUENTE CONVO-CADO NÚ-MERO OFI-CIAL CONTRA-DITÓRIO AS-SINATURA CE-LEBRAÇÃO AN-TECIPADOS PE-NALIDADES DI-REITO To download VERO as extension (pt-BR spell checker), please go to the VERO extension page in pt-br portal: http://tinyurl.com/6msbv3j
Reproducible with LO 4.3.4.1, English and German, but if I write the words in capitals I get no correction suggestions. Steps done: 1. Open WRITER and assure that the page format is A4 with all margins = 2.00 cm (FORMAT -> PAGE -> tab PAGE) and the selected font is "Liberation Serif" with font size = 12 2. Write an English and German sample text, I used the following: This is a large house with a very nice garden around. In the garden there are trees which are beautiful. This is a large house with a very nice garden around. In the garden there are trees which are BEAUTIFUL. Das ist ein Haus mit einem sehr schönen Garten. In dem Garten finden sich Bäume, die wunderschön sind. Das ist ein Haus mit einem sehr schönen Garten. In dem Garten finden sich Bäume, die WUNDERSCHÖN sind. 3. Select the first two paragraphs and go to TOOLS -> LANGUAGE -> FOR SELECTION -> English (UK) or (USA) 4. Select the last two paragraphs and go to TOOLS -> LANGUAGE -> FOR SELECTION -> German (GERMANY) 5. Add a minus to have a manual hyphenation: "beautiful" -> "beauti-ful", "BEAUTIFUL" -> "BEAU-TIFUL", "wunderschön" -> "wun-derschön", "WUNDERSCHÖN" -> "WUN-DERSCHÖN" Interim Results: LO marks "beauti-ful" and "wun-derschön" a wrong (they are underlined) 6. Go to TOOLS -> SPELLING AND GRAMMAR Result: LO suggests the following non-existing "corrections": beauti-ful: beaut-ful, beauts-ful, beauty-ful, beau-ful, beatitude-ful, beating-ful BEAU-TIFUL: no correction wun-derschön: wund-derschön, wen-derschön, nun-derschön, tun-derschön, Sun-derschön, Run-derschön, Tun-derschön WUN-DERSCHÖN: no correction After choosing one of these suggestions, LO marks them also as wrong. -> Bug LO marks "wun-derschön" as wrong, but not "wunder-schön". Actually of course both are correct in this case. I suppose that if we add a minus to hyphenate a word manually, LO doesn't recognize it as a hypenation, but sees them a compound words and then checks every word part itself. In German: "derschön" does not exist as a word and is therefore also not possible as a compound word. -> Bug -> Enhancement Request: I would like to suggest that it would also be possible to make a manual hypenation with a minus. LO should then check if this word with a minus is at a line break and if yes then LO should check it as "one" word (also possible correction suggestions). If this word with a minus is not at a line break then LO should check it as compound words and all words separatly. But I am not sure, maybe such an enhancement has also drawbacks? Maybe it would otherwise be possible to add a shortcut and/or an icon in the toolbar to add a manual hypenation.
** 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.0.4 or later) 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 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
Reproducible with LO 5.1.0.1, Win 8.1 For BEAU-TIFUL and WUN-DERSCHÖN it shows as one alternative the correct correstions.
** 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.6 or 5.2.3 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-20170103
Still reproducible. Version: 6.0.6.2 (x64) Build-ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77 CPU-Threads: 8; BS: Windows 10.0; UI-Render: Standard; Gebietsschema: de-AT (de_AT); Calc: group
Dear Olivier Hallot, 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
Tested wunderschön; working pretty ok Version: 7.0.0.2 Build ID: c01aa64b6c3d89ebe5fe69c28c7adb24eb85249c CPU threads: 4; OS: Mac OS X 10.12.6; UI render: default; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded
Dear Olivier Hallot, 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
The issue now is related only when the hyphen follows an accented letter. In the words above, only nú-mero generates a list of inexistent words, but, offers número as good option. At the moment, I consider this issue as Work for me. Version: 7.3.5.2 / LibreOffice Community Build ID: 184fe81b8c8c30d8b5082578aee2fed2ea847c01 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: pt-BR Calc: threaded