Description: I used "soffice --headless --convert-to pdf test.docx" for a docx file convert to pdf. Looks good but some style display error. For example: docx display some text just one row, but pdf show 2 rows. docx display text style: ABCDEFG pdf display text style: ABCDE FG ENV: server for docx to pdf: centos 7.6 + libreoffice6.3 mac wps office Steps to Reproduce: You can download my example include docx file and pdf files. "https://gofile.io/?c=wyXKZo" or "https://easyupload.io/i4611q" About step: 1.Create a docx through wps or office with some content like my text.docx 2.Upload docx to centos system for convert to pdf 3.download pdf check display style Actual Results: PDF text display two row. Expected Results: PDF text display one row is corrent. Reproducible: Always User Profile Reset: No Additional Info: My example, you can download from any one link. "https://gofile.io/?c=wyXKZo" or "https://easyupload.io/i4611q"
Created attachment 157274 [details] sample file
Hello aven, Could you please attach a screenshot showing how it looks in MSO Word ?
Dear aven, 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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/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 MassPing-NeedInfo-Ping
Dear aven, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA 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 our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp