Created attachment 82584 [details] This is the testcase Hi, My input is docx file that I created through libreoffice 4.0.4.2 version. If I export xhtml using libreoffice user interface then the xhtml output is well generated but if I use command line xhtml export method then it goes to worst xhtml output. My command is : /opt/libreoffice4.0/program/soffice --headless --invisible --convert-to xhtml:"XHTML Writer File" INPUTFILE --outdir OUTPUTDIR If I wrong please suggest me the right way to execute this command. Can anybody tell me how to match my xhtml exported output with my command line xhtml exported file. I want the same output like that I got through the libreoffice user interface. All headers are converted into <h file instead of <h1 , <h2 , <h3 .... in command line output. And I am also intrested to know, what is the backgroud process in libreoffice user interface and if I choose a command line xhtml export method. Regards, Anirudha
I used file >> "Export" option in libreOfiice then selected file type "XHTML 1.1 + MathML 2.0". And command: /opt/libreoffice4.0/program/soffice --headless --invisible --convert-to xhtml:"XHTML Writer File" INPUTFILE --outdir OUTPUTDIR suggest the right way using command line.
Strange, I get the same results from menu and also the the command line. The generated files are byte-to-byte exactly the same. Well, there is one difference. If I use File/Export menu, it produces file name with the suffix .html. If I use the command line, it uses file suffix .xhtml. Is it possible that your XHTML/HTML viewer handle the generated files different way according to the suffix, please? Another potential difference is that I do not see "XHTML 1.1 + MathML 2.0" in File/Export. There is only "XHTML (.html,.xhtml). Do you really see "XHTML 1.1 + MathML 2.0" in the export dialog, please? Finally, it is not caused by the suffix. Could you please attach both generated documents? It might help to understand what happens there. Also, does it print any warning or error messages on the console, please?
I lower the severity a bit. I understand that it is a blocker for you and we need to solve it. On the other hand, it affects only very limited group of users, so it can't block the release with many other useful fixes and improvements. We could provide the fix in any of the frequent bugfix releases.
Dear Bug Submitter, Please read the entire message before proceeding. 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
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