Created attachment 161072 [details] Screen shot of the end of the document. When reading MS Word created DOCX files with a bookmark which is defined at the very end of the file, it is not read. See attachment. This works correctly if the file is saved as a .DOC file. DOCX and DOC files were created with MS Office 2010. If there are any characters after the bookmark or any blank paragraphs then the bookmark is correctly read. For the fault to show it must be after the very last character in the document. The attachment is shown with punctuation characters turned on and the bookmark is defined immediately in front of the final closing paragraph marker.
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Created attachment 161129 [details] Sample document showing the bookmark error (.DOCX format) This sample document was created using MS Word 2010 and then saved as a DOCX file format. The document attempts to show the page number of the end of document bookmark but fails.
Created attachment 161130 [details] Sample document showing the bookmark works (.DOC format) This is the same sample document as previous attachment (161129) but has been saved in the .DOC format. Here the bookmark page number is correctly shown as page 1 (in red).
Two versions of the same sample document provided. Both created using MS Word 2010 on 64 bit Windows 10. The docx version shows the error (in red) when attempting to reference the page number of the end of document bookmark. The bookmark is created after the final sentence of the document - this is critical creating it any earlier in the document or with a blank paragraph after it does not show the fault. The doc version of the same file shows the expected document where the page number of the end of document bookmark is shown as 1 (again in red). This version loads correctly.
Created attachment 161134 [details] Comparison MSO 2010 and LibreOffice 7.0 master
Reproduced in Version: 7.0.0.0.alpha1+ Build ID: 8209c2569f5726f9ed29f75d30efdccb94f98fe5 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Also reproduced in Version: 5.2.0.0.alpha0+ Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53 Threads 4; Ver: 4.19; Render: default; and Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
@NISZ Team, I thought you might be interested in this issue
Dear Phil Walter, 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
This has just been tested on the latest version of Libra Office and I can confirm that the bug is no longer present. Well done to the team for fixing this. Version: 7.3.3.2 (x64) / LibreOffice Community Build ID: d1d0ea68f081ee2800a922cac8f79445e4603348 CPU threads: 8; OS: Windows 10.0 Build 22000; UI render: Skia/Vulkan; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded