Hallo, wenn ich ein einfaches Dokument mit Zeilennummerierung in docx abspeichere, merkt sich der Writer den Beginn einer neuen Zeilennummerierung beim erneuten Öffnen nicht. Ergebnis ist, dass bei jedem Öffnen der Neubeginn der Zeilennummerierungen erneut eingestellt werden muss. Der Fehler tritt nicht beim Abspeichern in odt auf. Andere Formate wurden nicht überprüft. Vielen Dank für's Nachschauen! Beste Grüße!
Please attach an example odt file that shows this behavior when saved as docx. I tried to create a simple example, but both paragraph numbering and line numbering restarts correctly in docx, in a fresh master version: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d8dbf35c48698e49c527d740853ce4edc4f1afa9 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: hu-HU (hu_HU.UTF-8); UI: en-US Calc: threaded
Created attachment 189654 [details] docx-file with not working paragraph numbering
Created attachment 189655 [details] odt-file with working paragraph numbering
Hello, you'll find two examples attached. In the docx-file I defined the first row with the "NZZ" as a new paragraph. When I reopened it, the start of the paragraph numbering was gone. In the odt-file everything works as expected. Thanks for your time and help! Best regards Hendrik PS: First I save the file as docx and then created the odt-file from the docx-file.
Created attachment 189665 [details] Page level line numbering settings in Word 2016 and Writer Thanks, now I can confirm the issue. Most of the problem is that in Word the line numbering does not have the same Restart at this paragraph option, as in Writer. So there is no option in the docx model to map this Writer-setting to.
Dear hendrik.gaspar, 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