Description: The user-defined dictionary fails to add a trailing period for an abbreviation that has it in the ODT document from which the dictionary is being compiled. Steps to Reproduce: 1. In Writer, have a document with text open. Include some abbreviations that have periods and that are not in LO's dictionaries. Examples (relevant to English (USA)): M.D. F.A.C.S. 2. Press F7, for Spelling. 3. When spell-check encounters one of these abbreviations and you can specify how to handle it, click Add to Dictionary. 4. Click the Options... button. 5. For the user-defined dictionaries, leave as preselected Standard [All] and click the Edit... button. 6. Examine entries for abbreviations you added. 7. If the trailing period is missing, you may want to select each one and then click Delete. Examples: M.D F.A.C.S Actual Results: Even though the string under consideration because it's not already in the dictionary and you have a choice of how to handle it is red when the surrounding text is black and the red string includes the trailing period, the trailing period is not being copied into the user-defined dictionary. Expected Results: Inclusion of the entire red string, including a trailing period. An alternative expectation is that the trailing period would not be red, but would be black, but periods are small and so that would be a subtle and counterintuitive signal to the user, easily missed. Reproducible: Always User Profile Reset: Yes Additional Info: Apparently, entries can have periods in the middle but not trailing. In a few cases, abbreviations properly have periods in the middle but not trailing, but that's unusual. The period that ends a sentence when the sentence ends with an unknown abbreviation that uses periods can confuse the dialog, by making the sentence-ending period red even though the period won't be accepted for the custom dictionary. The problem persists in version 6.3.4.2.0+ (build ID 6.3.4.2-2.fc31). I'm not prepared to install a newer or unstable verion. I don't have an OpenGL setting.
I confirm it with Version: 6.3.5.2 (x64) Build-ID: dd0751754f11728f69b42ee2af66670068624673 CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: threaded and user-defined dictionary
Dear Nick Levinson, 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 bug was still recently present, including in Safe Mode. The only difference in applying STR to this test is that the desired user dictionary was not preselected, and that's only because I had created an additional dictionary, which was preselected, so I selected the desired dictionary and found the new entries that lacked trailing periods. Before the latest update per Fedora Linux: LO: From Help > About: Version: 7.2.5.2.0+ Build ID: 20(Build:2) CPU threads: 2; OS: Linux 5.16; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded I'm not prepared to install another LO version.