Bug 116088 - Export to XHTML issue with numbering in multi-columns sections
Summary: Export to XHTML issue with numbering in multi-columns sections
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
Version:
(earliest affected)
3.6.7.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:html
Depends on:
Blocks: (X)HTML-Export
  Show dependency treegraph
 
Reported: 2018-02-28 14:30 UTC by Philippe Laugier
Modified: 2023-04-10 03:17 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Example file (31.31 KB, application/vnd.oasis.opendocument.text)
2018-02-28 14:30 UTC, Philippe Laugier
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Laugier 2018-02-28 14:30:29 UTC
Created attachment 140221 [details]
Example file

The export to XHTML seems to have an issue with paragraph numbers that are used in sections having multiple columns.

I attached a small ODT example here.
Using export to XHTML you get a nice HTML file but the original chapters 1.1.1 and 1.1.2 in the ODT are 0.0.1 and 0.02 in the HTML
Comment 1 Buovjaga 2018-03-09 17:58:02 UTC
Reproduced.

Btw., issue for multi-column support is bug 107790

Arch Linux 64-bit
Version 3.6.7.2 (Build ID: e183d5b)

Arch Linux 64-bit
Version: 6.1.0.0.alpha0+
Build ID: b8fe96f1da2c42c04a8094ca8c57d49763b7bded
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on March 8th 2018
Comment 2 QA Administrators 2019-03-10 03:21:25 UTC Comment hidden (obsolete)
Comment 3 Philippe Laugier 2019-03-18 06:38:40 UTC
Hi, 

The bug is still present in:
Version: 6.2.1.2
Build ID: 7bcb35dc3024a62dea0caee87020152d1ee96e71
CPU threads: 4; OS: Linux 4.18; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded
Comment 4 QA Administrators 2021-04-09 03:46:50 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2023-04-10 03:17:54 UTC
Dear Philippe Laugier,

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