Created attachment 70304 [details] test case for demonstrating problems with saving list Problem: when I change list to bullets list and save, it becomes numbered Steps to reproduce: 0. Open attachment in Writer 1. Select all items of numbered list and change to Bullets using button "Bullets On/Off" on toolbar or by press Shift-F12. List becomes bulletted. 2. Save 3. File->Reload Expected: list remains bulletted Actually: list becomes numbered Reproduced in 3.4.2 on Windows XP 32 bit and in 3.6.3 on RFR 17 64 bit Observation: msWord 2007 opens list as numbered. Therefore I guess that problem appears during saving. Calligra Words and Ocular also opens as numbered. Workaround: use Format->Bullets and numbering for changing format of list
reproducible with LO 4.0.2.2 (Win7 Home, 64bit)
still reproducible with LO 4.1.1.2 (Win7 Pro, 64bit)
Reproducible with LO 4.4.0.3, 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.0.5 or 5.1.0) 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: 2016-02-21
** 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.5 or 5.3.0 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-20170306
Still reproducible with attached document in: Version: 6.2.0.0.alpha0+ (x64) Build ID: 8b1501d80dc9d3f42c351c6e026fa737e116cae5 CPU threads: 2; OS: Windows 6.1; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-09-22_23:19:22 Locale: bs-BA (bs_BA); Calc: threaded Also in:LO 3.3.0 and OOo 3.3.0. Tested in new document in all versions saving bulleted list seems OK.
Repro 6.4+
repro 7.2+. A named list (L1) becomes an automatic list (right?) when changing to bullets. So it seems like export doesn't really recognize that change. I was not able to reproduce this with a brand new document either (comment 6)
On a brand new document, the definition of the list is saving into content.xml. With this document, there is an L1 list style in styles.xml, and then when you change to bullet, it is saving that bullet list as a conflicting L1 in content.xml.
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/46dc9f3bbac67e9240adc44ab017f905482ef786 tdf#57317 odf export: avoid autolist conflict with NumberingStyles It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.