Bug 63780 - FILESAVE: FILEEXPORT: OpenDocument file saved as XHTML results in incorrect formatting in XHTML file
Summary: FILESAVE: FILEEXPORT: OpenDocument file saved as XHTML results in incorrect f...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.0.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-21 16:12 UTC by Tom Williams
Modified: 2015-05-19 13:58 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
The original OpenDocument document used for saving in (X)HTML format. (24.61 KB, application/vnd.oasis.opendocument.text)
2013-04-21 16:12 UTC, Tom Williams 		Details
The original OpenDocument document used for saving in (X)HTML format (24.61 KB, application/vnd.oasis.opendocument.text)
2013-04-21 16:14 UTC, Tom Williams 		Details
Screen shot of OpenDocument document exported to XHTML (124.36 KB, image/png)
2013-04-21 16:21 UTC, Tom Williams 		Details
Screen shot of OpenDocument document saved as HTML (67.78 KB, image/png)
2013-04-21 16:21 UTC, Tom Williams 		Details
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Williams 2013-04-21 16:12:44 UTC 
Created attachment 78297 [details]
The original OpenDocument document used for saving in (X)HTML format.

When saving an OpenDocument document with various formatting elements as a HTML file, the generated HTML file contains incorrectly formatted content.  I understand not all OpenDocument formatting will be preserved when exporting to HTML, but I expect the generated HTML file to at least contain be legible content.

Steps to reproduce:

1.  Open the attached OpenDocument file
2.  Use the "Save As" function to save as a HTML file
3.  Use the "Export" function to export to an  XHTML file
4.  Open the HTML and XHTML files in a web browser and see the results

The HTML file should be misformatted but the content should still be legible.  The XHTML file should contain some text which overlays some other text, making that text illegible.

I will attach screen shots of the generated HTML files and the OpenDocument file I started with to this bug report.
Comment 1 Tom Williams 2013-04-21 16:14:03 UTC 
Created attachment 78298 [details]
The original OpenDocument document used for saving in (X)HTML format
Comment 2 Tom Williams 2013-04-21 16:21:12 UTC 
Created attachment 78299 [details]
Screen shot of OpenDocument document exported to XHTML

This was generated in Opera 12.15 on Ubuntu 12.10 Linux.
Comment 3 Tom Williams 2013-04-21 16:21:56 UTC 
Created attachment 78300 [details]
Screen shot of OpenDocument document saved as HTML

This was generated in Opera 12.15 on Ubuntu 12.10 Linux.
Comment 4 Thomas van der Meulen [retired] 2013-04-21 17:35:31 UTC 
Thank you for your bug report, 
I can reproduce this bug running LibreOffice 4.0.3.1 and master 4.1.0.0.alpha0+
Build ID: cf3e8cf92190baddf601283855070a36fc89125


wen I save the document in Master I get this error: 
Warning saving the document Katie Wright CV:
Write Error.
Document could not be completely saved.

os: mac osx 10.8.3
Comment 5 Tom Williams 2014-04-27 04:09:27 UTC 
I'm able to reproduce this in LibreOffice Writer 4.2.3.3 on Ubuntu 14.04 Linux (64-bit).
Comment 6 Gordo 2015-05-18 16:25:32 UTC 
Could not reproduce.

Exported original file to html.
Exported html file to xhtml.
Exported original file to xhtml.
Result:
No overlapping of text.

How the xhtml file looks is affected by where the anchors for the frames are.  Some of the frames are anchored to text that comes are the frame.

Firefox 38.0.1
Windows Vista 64
Version: 4.4.3.2
Build ID: 88805f81e9fe61362df02b9941de8e38a9b5fd16

Changed to RESOLVED WORKSFORME.
Comment 7 Tom Williams 2015-05-19 13:58:16 UTC 
I just tried this using Writer 4.4.3.2 on Windows XP and the XHTML file was exported without text overlay or overlap.

I confirm this is fixed.