Created attachment 96252 [details] test file Hi, I observe that existing styles are corrupted when loading styles by "Styles and Formating > Load Styles > From file" Case 1: To repeat: - Open the attached file - it contains both a bulleted and a numbered list - load styles from the same file by "Styles and Formating > Load Styles > From file" (Check Overwrite). Two of three bulleted items loose their bullets, all numbered items loose the numbers. Styles of these items do not change, so I think that the styles themselves were broken. Case 2: - Create a new document from the default template (may be empty) - Open the attached file and check style OOoHeading2 of the green heading - its Outline & numbering > Outline level is "Level 2" - load styles from the new file by "Styles and Formating > Load Styles > From file - check now the style OOoHeading2 of the green heading - its Outline & numbering > Outline level has changed to "Body text". The same happens with other OOoHeading styles. In this case, since the new file does not contain the OOoheading2 style I would expect that this style it remains unchanged after loading style from there. The problem is present in LO40, LO41, LO42 and Apache OO 3.4 and AOO 4.0 -- milos
Hello Milos, *, thanks for reporting this bug :) I can confirm your bug with LO Version: 4.1.5.3 Build-ID: 1c1366bba2ba2b554cd2ca4d87c06da81c05d24 (with Germanophone lang- as well as helppack), Version: 4.1.6.1 Build ID: a59ce81388f477fc89db57f0c27f222f31884eb, Version: 4.2.3.3 Build-ID: 882f8a0a489bc99a9e60c7905a60226254cb6ff0, Version: 4.2.4.1 Build ID: d4c441391e20647b3d2e8dde4d20aa868e77e515 (the last three parallel installed, following the instructions from https://wiki.documentfoundation.org/Installing_in_parallel, and with Germanophone lang- as well as helppack) and LO Version: 4.3.0.0.alpha1+ Build ID: 58fdcd262bf3476b6917c71e76ca6e49d0978c5f TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2014-04-20_23:10:06 (also parallel installed, but this one with en_US lang- as well as helppack) on Debian Testing i686 ... :( As I can reproduce it on an older version of LO 4.2.2.1, I will change the version adequately. And as I am using a 32 bit system, I will also change the platform entry to all ... ;) HTH Thomas.
** 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 (4.4.3 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 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-06-08
Hi, the bug according to Case 1 is still present in 4.4.3.2 and 5.0.0.0 I cannot however confirm Case 2 - "Level 2" remains there even for older versions LO 4.0 4.2 and 4.4. So, this information was probably not correct when reporting the bug) The bug is present in OOo33 -- milos
** 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.5 or 5.2.1 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-20160920
Hi, I confirm Case 1 in Version: 5.3.0.0.alpha0+ but I cannot repeat the problem described in Case 2. Additional comments to Case 1: The problem occurs only if Numbering is unchecked in the Load Styles dialog. If it is checked, no problem occurs. However, according to the help, numbering styles should be loaded if "Numbering" is checked, so the styles should not change if not checked. There seems to be a similar problem also with the Text checkbox. Works if checked. If unchecked (nothing checked except Overwrite), I expect that nothing changes on style loadin. However, the whole file is loaded, even the text. Milos
*** Bug 107820 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
Seems fixed IMHO Case 1: Can't repro. I followed the instructions, applied the style and nothing happened. There was quite some bug fixing with bullets and numberings in the last releases, so maybe it's fixed. Case 2: Can't repro. I imported the style OOoHeading2 into the new file and its outline level is 2. The reporter himself and another forum member could not reproduce case 2 after the original posting - Maybe it was fixed shortly after creating the report? Version: 7.0.0.0.beta1+ (x64) Build ID: 94c217984e456196047ce41096d4a6f05bf66382 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: threaded
Cannot repro Case 1 and Case 2 (or in positive terms, using Load Styles results in the expected behavior in relation to the two cases). Tested with: Version: 7.2.0.0.alpha0+ (x64) Build ID: 4041c68ea59181f1c4774c356809066d2051db41 CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Vulkan; VCL: win Locale: da-DK (en_DK); UI: en-US Calc: threaded Based on this test and the test in comment 8, closing as WORKSFORME (if there are still problems, then reopen and gives steps to show the problem)