Created attachment 120656 [details] First test case: text-only; all words "gubergren" manually formatted as italic Searching for italic format does not work. First test case: 1. The attached document 'Lorem Ipsum, italic manually.odt' contains a simple Lorem Ipsum created on LO 3.5.7.2 without any styles. The only change made is that I searched for the word "gubergren" and *manually* formatted all of them italic. 2. Searching for all italic formats (via Edit> Find&Replace...; More Options> Format> Font: Style = Italic; Find All) results in the message "Search key not found." Expected result is to find all appearances of the word "gubergren" and having them selected. The same behavior is seen when opening the document on LO 5.0.0.5. I remember seeing the expected behavior with some version prior to 3.5.7.2 but cannot recall which exactly. Ditto for an analogous document where a few words are selected at random and manually formatted as italic. So the behavior does not seem to be related to the way the words were selected. The searching does produce the expected result if the option "Including Styles" is activated. This should not be the case, however, as the whole document uses paragraph style "Default" and the italic formatting is applied manually. Second test case: 1. The attached file 'OpenOffice.odt' is similar to the above in the way that no styles used but only some selected words were manually formatted as italic. 2. Searching for all italic formats (via Edit> Find&Replace...; More Options> Format> Font: Style = Italic; Find All) results in a very peculiar selection of text. It is hard to describe precisely but to me it seems that every paragraph *containing* any italic letters is selected; *some* of the italic words are selected as well, others are not. Expected result is to have all italic words selected but none else. The same behavior is seen when opening the document on LO 5.0.0.5. I remember seeing the expected behavior with some version prior to 3.5.7.2 but cannot recall which exactly. Comment: I am astonished that no one else has noticed this behavior and raised a bug about it. However, I have thoroughly tested these cases with different installations and am confident about it being relevant in general.
Created attachment 120658 [details] Test case 2: text-only; no styles; some words manually formatted as italic
Confirmed. I guess there was some glitch with saving those documents in 3.5. Win 7 Pro 64-bit, Version: 5.0.3.2 (x64) Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75 Locale: fi-FI (fi_FI) Version: 5.1.0.0.alpha1+ Build ID: f6bc5b79c31225c02e9500d0ced4bd26f998f82b Threads 4; Ver: Windows 6.1; Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2015-11-24_01:07:47 Locale: fi-FI (fi_FI)
Thanks! What exactly do you mean by "I guess there was some glitch with saving those documents in 3.5."?
(In reply to sm8ps from comment #3) > Thanks! What exactly do you mean by "I guess there was some glitch with > saving those documents in 3.5."? I mean only documents coming from 3.5 (or specifically your documents?) are affected. That's why this should be seen as low priority. When using documents created with 5, the format find all works perfectly.
Your comment makes perfect sense now, Beluga. Thanks for pointing this out! In fact, the idea simply did not cross my mind to check with a similar document *created* on LO 5. So this issue really is of low priority.
Comment on attachment 120656 [details] First test case: text-only; all words "gubergren" manually formatted as italic more specifically: Search for format breaks seems not to work either. Edit / find & replace / other options format / text flow Breaks / This submenue seems to be inactive / not selectable. I couldn't find a way to search for the manually inserted (page-) breaks otherwise. As a testcase a attach "LoremIpsum_break-hh.odt" (created with Writer 5.0.5.2 pasting unformatted text from attachment "Lorem Ipsum, italic manually.odt" and inserting a manual break prior to Duis autem, to start page 4. Is there a display option to show manual breaks (not just by beginning a new page but to indicate a forced new page)?
Created attachment 123901 [details] testcase search manual page break
** 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.2.7 or 5.3.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-20170522
*** Bug 111977 has been marked as a duplicate of this bug. ***
** 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
I tried first Test case using Version: 6.1.3.2 (x64) Build-ID: 86daf60bf00efa86ad547e59e09d6bb77c699acb CPU-Threads: 4; BS: Windows 6.1; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group threaded I found the error persists but I also found means to get correct behaviour: I marked all of the text and chose to assign a different font. The test case file uses font Linux Libertine # which is not part of Writer 6.1! I chose font Linux Libertine G or Linux Libertine Display G and the problem was gone. May be the observed dependancy "only documents affected created with some old version" is actually that the font Linux Libertine was only available in that version. However even if this explaines behaviour I think behaviour is not correct. The display process correctly displays italic (Test: step char by char through text and observe the font attribute shown in the top bar) - only search fails to detect this correctly
I retested also Test case 2 using Version: 6.1.3.2 (x64) Build-ID: 86daf60bf00efa86ad547e59e09d6bb77c699acb CPU-Threads: 4; BS: Windows 6.1; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group threaded ========= I found the error persists. find and replace when searching for Format italic marks very arbitrary parts of the text. To find out if this is a problem of the document I did the same search for italic using the extension "Alternate search&Replace" V1.4.2. Alternate search and replace tells me it is searching for [:::CharPosture::] to find italic text and properly marks all the italic text portions and nothing else! ========= It can be done correctly -> it should be done correctly also by standard find&replace!
I was looking around in the current version if I can find a way to search for manual page break. Unfortunately this is not true, only "Alternate serch&replace" is offering that. If extension "Alternate search&replace (Altsearch)" was a regular part of the distribution I couldn't complain... It does what I want!
*** Bug 127725 has been marked as a duplicate of this bug. ***
The variation of this bug (I reported as https://bugs.documentfoundation.org/show_bug.cgi?id=127725) persists in LO 6.2.7.1 on Ubuntu 19.04..
I reproduced in older LO 5.0. Selecting Italic would also show Normal in Find. Seems fixed in 6.3, good in master 7.1+. So I set WFM. Please test yourself.
*** Bug 103400 has been marked as a duplicate of this bug. ***
*** Bug 105725 has been marked as a duplicate of this bug. ***
More changes in Lo 6.3, from crashing, selecting Normal and other to Italic. This is the final. Bibisect in Linux. commit 2f564bd1391be29762cd3d7a2d7db4c71dbae653 Date: Thu Aug 29 11:05:26 2019 +0200 source 0417dd10991b0e92b5163167ddba59f1ffe6d73d prev source 482a97009a729e6198a4eae07869913f90a90c3c author Caolán McNamara <caolanm@redhat.com> 2019-08-19 16:30:23 +0100 committer Michael Stahl <Michael.Stahl@cib.de> 2019-08-29 10:26:00 +0200 commit 0417dd10991b0e92b5163167ddba59f1ffe6d73d (patch) tree ab371be674d6eb07568dba2def3523892b06baa1 parent 482a97009a729e6198a4eae07869913f90a90c3c (diff) Related: tdf#127029 true was substituted for FALSE presumably accidentally by... commit 6ed0bcdd5bc07692fc81406942509eb9c30d3904 Date: Tue Oct 5 07:57:51 2010 -0500 Description is different so I'll mark Fixed, not duplicate.
*** Bug 126338 has been marked as a duplicate of this bug. ***
*** Bug 122197 has been marked as a duplicate of this bug. ***