1. What is expected to happen in Writer via the Terminal:
cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1002985/+attachment/3158838/+files/example.odt && lowriter --nologo example.odt
save the attached document in .doc format (97/2000/XP/2003), close, reopen and the endnote looks the same as it did in .odt.
2. What happens instead is the the endnote number is decoupled from the endnote text.
Still happening LO 4.3.1RC1 OSX 10.9.4
OS -> ALL
Endnote is decoupled indeed.
** 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 (220.127.116.11 or later)
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)
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-09-03
I just tested this with:
Build ID: 40m0(Build:2)
On Ubuntu 15.04.
Saved as docx and it opened fine in Libre Office.
Would be good to test whether it works in Word, but I don't have that :)
Guessing this one is fixed.
Footnotes looked pretty good too :)
I've tested saving the file as .doc and .docx and it opens fine in Libre Office, but not in Word 2010.
In Word there is still a big gap between the endnote number and the text.
Also, the character for the endnote changes from a '1' to roman numeral 'i' when opening .doc in Word (this doesn't happen for .docx)
Endnote character changing is bug 40101
A carriage return was added each time the document was saved and re-opened. That was fixed in LO 6.0 for bug 108448.
Johnny Gill: this bug report is about .doc, not .docx right? So comment 3 doesn't really apply?
Iwan: It seemed that I needed to modify the document to notice the extra carriage return being added. A simple load and save didn't trigger it. So in my testing I always changed the page size before saving.
Comment 4: Yes, there is still a big gap (a tab) added to the footnote. There are other bug reports relating to that, so not worrying about that in this report.
Comment 4: Yes, the endnote character shows up as i instead of 1 in MSWord. In LibreOffice, that is defined in Tools - Footnotes and Endnotes. The default is roman numberals for endnotes. See bug 40101 and bug 40049.
Interestingly, MSWord2013 cannot see the first page (with "Affects the World") but only the endnote page. This is true all the way back to LO 3.6. However, Word 2003 opens it up fine, so we won't worry about MSWord's bug.
Closing because the "decoupled" problem has been resolved in LO 6.0.
*** This bug has been marked as a duplicate of bug 108448 ***