Description: Currently, if Footnote numbering is set to restart on each page or chapter, the Exported HTML restarts its numbering to match the document, even though all of the footnotes become a single series at the end of the document. Instead of apparently random numbering restarts, the HTML footnotes should number sequentially to the end of the file. the Ebooks have the same issue for footnote numbers that restart each page. Steps to Reproduce: 1.Create a document and use tools-footnotes to restart numbering on each page. 2.Export as HTML and EPub. 3.Check how the footnotes now have numbering restarts that are unrelated to pages. Actual Results: Peculiar endnote numbering restarts Expected Results: Converted Footnotes should be numbered sequentially to the end of the file for HTML and the end of each chapter for ebooks. Reproducible: Always User Profile Reset: No Additional Info: The Export conversion keeps track of all the footnotes sequentially, so it should be easy enough to display their numbers sequentially too.
(In reply to Bruce Armstrong from comment #0) > Steps to Reproduce: > 1.Create a document and use tools-footnotes to restart numbering on each > page. Please attach such 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)
Dear Bruce Armstrong, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Bruce Armstrong, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp