Created attachment 116637 [details]
.odt test case to save as .doc
tested under Win8.1 x64
load attached 2 pages .odt file and save it as .doc then reload the output.
page numbers are shown as "1" and "2" in source .odt
and as "11" and "22" in .doc output, if you add a new page it is shown as "33"
this "doubling" of page numbers is present in all LibO releases (tested up to 3.3.3) and in OOo as well, so it's an inherited bug.
it also persists in LibO 22.214.171.124 and recent 5.1 master daily builds
Confirmed with v126.96.36.199 under windows 7 x64.
Also better test it with docx. Then the doc extend to 10 or 11 pages with strikes through text and randomly places bulletpoints, all hidden now. So you might have another fileopen bug here.
the .docx issue is already known and reported at Bug 89991
I cannot reproduce it when I create a simple test file, so must be specific for this document?
And the document is weird too.
When I place the cursor in the footer, just in front of the number field, and do a Backspace to remove a Tab, at the first paragraph on the second page a bullet is added :D
I'm not the author of that document... it's a stripped version of another attachment probably from Bug 89991
anyway this bug is probably "document specific"
still reproducible under Win8.1 x64 using LibO 188.8.131.52.alpha0+
Build ID: 05618e74c77658da76f467a1ab328cb310a19e84
CPU Threads: 4; OS Version: Windows 6.29; UI Render: GL;
TinderBox: Win-x86@42, Branch:master, Time: 2016-02-20_23:42:27
Locale: it-IT (it_IT)
still present in 184.108.40.206.alpha0+
Build ID: 4c70a1a6666a079872b8f1966bd398e924dc1d1a
CPU Threads: 8; OS Version: Windows 6.1; UI Render: default;
TinderBox: Win-x86@42, Branch:master, Time: 2016-09-22_06:54:24
Locale: it-IT (it_IT); Calc: CL
Build ID: acb43c0b8efbfb841e7b40603d75a8432eb21f21
CPU threads: 4; OS: Windows 6.3; UI render: default;
TinderBox: Win-x86@42, Branch:master, Time: 2018-01-08_23:05:27
Locale: it-IT (it_IT); Calc: group threaded
** 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!
the same in Version: 220.127.116.11.alpha0+
Build ID: 65f6a4088ad5d51a3225905aa6e2fa175f3eab49
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-02-03_17:11:18
Locale: nl-NL (nl_NL.UTF-8); UI-Language: en-US