Created attachment 110086 [details] Simple DOCX with TOC When you save a file with a TOC as a RTF, the resulting file will have a duplicated TOC. Steps to reproduce. 1) Open attachment 110084 [details] in Writer 4.2+ 2) Save as RTF 3) Open in Word or OneDrive 4) Compare the original with the exported It doesn't matter if the original is a DOC, DOCX, or RTF. The exported RTF file will have a corrupted TOC when opened in Word.
Created attachment 110087 [details] RTF with TOC round trip
Created attachment 110088 [details] Simple RTF with TOC
I don't see the same problem with XP however I do see a problem: Open your toc.rtf document in Word 2007 Click on the ToC and this takes us to the correct place Update ToC and save Now open toc.rtf in LO4.2.0.4 Click on the ToC and this takes us to the correct place Close Now open toc.rtf in LO4.4.0.0 beta1 Click on the ToC and I get a message: "HYPERLINK#_Toc404771503" is not an absolute URL that can be passed to an external application to open it. Same problem on Fedora 21 with 4.4.0.0 beta and with 4.3.3.2 Could someone pls advise whether I should open a new report for the problem I see or can this be generic problem with ToC in RTF docs? Starting around 4.2.7?
@Tim Lloyd I also ran into the 'The "HYPERLINK#_Tocxxx" is not an absolute URL' ERROR and filed it as Bug 86750.
Hi Luke, I reproduce with LO 4.2.7.0.0+ Build ID: 92216be6ce13990b8ea6b6264c656d2bc1746401 TinderBox: Win-x86@42, Branch:libreoffice-4-2, Time: 2014-07-14_16:21:42 & Windiows 7 Home Premium I set Status to NEW. Have a nice day, Jacques
Adding Michael and Miklos since they both recently worked on RTF TOC issues. You guys have done some amazing work. Thanks!
** 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.6 or 5.2.3 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-20170103
Verified FIXED in 5.4.0.0.alpha0+ (x64) Build ID: bf80bbb7b75febc2769d6b64e6981224982f8fe2