Transcluded Search groups that are entered in Replace (i.e. $1) lose their formatting such as italics. To reproduce this: 1. Type "aitalicsb" in a new document, and make word "italics" between "a" and "b" in italics. 2. CTRL+H Find and Replace > Check "Regular Expressions" 3. Search: a(.+)b 4. Replace: A$1D 5. Click replace. Expected result: AitalicsB, with the word "italics" in italics as before Actual result : AitalicsB, with the word "italics" no longer italics. AltSearch has the same problem, which may be resolved when this is fixed.
Thank you!
Could not reproduce with Version: 4.2.2.1 Build ID: 3be8cda0bddd8e430d8cda1ebfd581265cca5a0f Ubuntu 13.10 - Closing as works for me, please reopen if you still reproduce with the latest version - Sophie
Created attachment 95510 [details] transclusion bug demo
I'll have to check it again on my Linux, but here is my platform: Version: 4.2.0.4 Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71 on XP
From what I can see this was never confirmed by QA team - moving to UNCONFIRMED to get their confirmation.
I just produced this error again on this platform: Version: 4.2.2.1 Build ID: 3be8cda0bddd8e430d8cda1ebfd581265cca5a0f on Windows XP SP3 32 bit. Let's see what QA says or if anyone else can confirm.
Reproducible with LO 4.3.3.2, Win 8.1. You need to press the Replace button two times (after the first time everything is still ok). After the second time the italics format gets lost.
** 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
** 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
Seems to be one of the problems of 'exchanging' content where LibreOffice in reality deletes content and then inserts new content. This results in losing formatting/style definitions.
@nissimnanach I believe your report is a duplicate of bug 62603. The problem is not regex, but that the font attributes of the first matched character is applied to the entire replace string. See bug 62603, comment 24 If you think your case is not a duplicate of bug 62063, then please REOPEN, with an explanation of what is different. *** This bug has been marked as a duplicate of bug 62603 ***