Description: The file contains the following string sí̱/si̱i̱ In the 'Find' field, I enter si. In the options, I mark 'Whole words only' and 'Diacritic-sensitive'. 'Find next' stops at both of the above occurrences. This means that neither of the two options does what the user expects. Steps to Reproduce: 1. The file contains words containing diacritics and words adjacent to special characters. 2. In the 'Find and replace' dialogue box, mark 'whole words only'. 3. Enter a search string in the Find field and press Next. Actual Results: 'Whole words only' finds the string if adjacent to non-ascii characters, too. 'Diacritic-sensitive' considers a non-ASCII string as a find for an ASCII string. It apparently only considers ANSI characters and ignores other diacritics. Expected Results: In the example, 'Find next' should stop at neither of the two examples. Reproducible: Always User Profile Reset: Yes Additional Info: Apparently the implementation has a very simple notion both of word boundary and of diacritic. Both should be refined.
Christian, thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it)
Created attachment 178447 [details] test file for find-and-replace options Try the find-and-replace options as explained in the attachment.
Steps: 1. Open attachment 178447 [details] 2. Edit -> Find and Replace 3. Test 1: Insert "word" in Find-field and select "Whole words only" 4. Find next => "word" in second paragraph is found 5. Test 2: Insert "a" in Find-field and select "Diacritic sensitive" 6. Find next => "á" (5th paragraph) and every "a" is found Christian, do you get the same result? Does this cover your description of actual an expected result in comment 0? Pleae also have a look at bug 146521. Tested with Version: 7.3.0.3 (x64) / LibreOffice Community Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL
Yes, this is what I meant. In Test 2, not only is the ä found, but also the following a's with diacritics. My impression (i.e, without having executed a complete and systematic test) is that diacritics are recognized as such if they are part of one (complex) character, but are not seen if they are added upon or below a simple character as "non-spacing diacritic".
(In reply to Christian Lehmann from comment #4) > Yes, this is what I meant. In Test 2, not only is the ä found, but also the > following a's with diacritics. Very strange: In my initial test, "ä" "a̱" are not found. But now they are included in the search result. So let's change status to NEW.
Dear Christian Lehmann, 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 persists unchanged in Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 60(Build:1) CPU threads: 12; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded