Bug 51907

Summary: Bad display of imported html
Product: LibreOffice Reporter: Vasileios Anagnostopoulos <fithis2001>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: major CC: mike.hall
Priority: medium    
Version: 3.6.0.0.beta3   
Hardware: x86 (IA32)   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: The html file I mentioned

Description Vasileios Anagnostopoulos 2012-07-09 13:08:03 UTC
Created attachment 64018 [details]
The html file I mentioned

I had a file (actually the template of Journal Of Optical Commpunications) and had imported in Google docs. I exported it as html and tried to view in Libreoffice.

While qupzilla 1.2.0 and MS Office 2010 displayed it almost the same, Libreoffice was very very bad at displaying it. Especially the format and location of tables drew my attention.

The same template is also available from the journal in .doc but the import in Libreoffice is also very bad but this is not my main problem. (I like standards compatible behavior).
Comment 1 mike.hall 2012-12-02 12:03:06 UTC
I'm unconvinced this is a bug, so changed the status to NEEDINFO, see below for the background.

1) After looking at the html in detail, there are various minor problems. In general the defaults take care of the fact that the html has some errors. However, the html includes some layout oddities, eg the first character of the introduction does not seem to be correctly coded. The display of the html document in Firefox, Internet Explorer and in Libre Office all show the character 'T' in what is obviously the wrong position, but it is what I would expect from the html. This is almost certainly caused by a restriction or error in the Google Docs export, ie nothing to do with Libre Office.

2) This was originally a Word template. I don't understand the reason for converting it to html, especially not from Google Docs which clearly doesn't support 'round tripping' for .doc documents, eg the option to 'double click to edit' is not supported by the export. For papers submitted to a journal you are better to keep the format as close as possible to the one you need to use for submission to the journal. Conversions to and from html are very likely to cause problems, whatever software you use, and unless you have a reason for displaying the document as a web page, there seems no benefit. 

3) If you still believe that there are Libre Office errors, please can you create a minimum example of html code that demonstrates the incorrect layout in Libre Office but not elsewhere so that a developer could focus on the essence of the problem.

4) If the .doc version does not work properly in Libre Office, please submit a separate bug report.
Comment 2 QA Administrators 2013-09-24 01:47:53 UTC
Dear Bug Submitter,

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 INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/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
Comment 3 QA Administrators 2013-10-25 15:09:06 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO