Created attachment 122579 [details] the odt document to be exported and the resulting html The page numbers in the Table of Contents (ToC) are getting lost during XHTML export of a LO writer document. ToC before export (writer2html.odt): Table of Contents Heading1............................1 Heading2............................1 Heading21........................1 Heading22........................2 ToC after export via "File->Export->All Formats->XHTML (.html;.xhtml)" (writer2html.html): Table of Contents Heading1 Heading2 Heading21 Heading22 This HTML ToC export is realized by the XSL template „createIndexBodyTable“. There is also a EasyHack related to this template, the task is to improve the ToC formatting for the HTML export: https://bugs.documentfoundation.org/show_bug.cgi?id=89290
Reproduced. Win 7 Pro 64-bit, Version: 5.1.0.3 (x64) Build ID: 5e3e00a007d9b3b6efb6797a8b8e57b51ab1f737 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Locale: fi-FI (fi_FI)
Regarding this bug report it is the other way around: The output of the HTML export is just one page and therefore page numbers are meaningless. So the bug report should not be titled “missing page numbers ….” as in this bug report, it should be titled “not removed page numbers...”. The page numbers are correctly removed from LO Writer documents but not from AOO Writer documents. So also the associated EasyHack makes no sense anymore: https://bugs.documentfoundation.org/show_bug.cgi?id=89290
So the goal of this easy hack is to remove page numbers when exporting Open Office Writer documents via "File->Export->All Formats->XHTML"? I agree with Martin considering page numbers meaningless, but the purpose of this easy hack is not clear for me.
(In reply to Gian Domenico Ceccarini from comment #3) > So the goal of this easy hack is to remove page numbers when exporting Open > Office Writer documents via "File->Export->All Formats->XHTML"? > > I agree with Martin considering page numbers meaningless, but the purpose of > this easy hack is not clear for me. Please be aware, this is not a easyhack, and thus considered more complicated. The purpose of the bug is quite clear, the XHTML export, should not have page numbers. This is by the way not for openoffice (or AOO) documents but for LO documents.
** 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! Warm Regards, QA Team MassPing-UntouchedBug
Dear Martin Nathansen, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Compiler problems maybe come in this time? It is really possible for everyone to always keep started these things, What is the important part for these messages and what we people demand the most for changing https://aussiessayreviews.com/assignmenthelper-com-au-review/ and it is be really possible to keep maintain.
I agree that this bug report should be closed as "not a bug". Page numbers should not appear as a HTML page is not paginated. Instead, a new but report should be opened (if it doesn't exist already) about how "Save As > HTML" shows page numbers in the TOC, and the bottom of the page shows "Page x of x". XHTML export does not show either. Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: 6b09276d157abada74e1a4989700139167207778 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-05-14_04:32:30 Calc: threaded
(In reply to stragu from comment #8) > I agree that this bug report should be closed as "not a bug". Page numbers > should not appear as a HTML page is not paginated. A funny footnote, but these days page numbers make sense in some contexts thanks to CSS paged media: https://developer.mozilla.org/en-US/docs/Web/CSS/Paged_Media https://print-css.rocks/ Not in web browsers, though (except with a JavaScript polyfill).
Related: Bug 142725 - Page numbers not removed from ToC when saved to HTML https://bugs.documentfoundation.org/show_bug.cgi?id=142725
Dear Martin Nathansen, 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