Created attachment 144315 [details] Screengrab of broken text rendering. See the attached screenshot. Although the original DOCX file contains spaces and renders just fine, LO seems to have removed the spacing and renders with 0 or negative character spacing. Unfortunately, the document contains copyrighted content and I was unable to create a minimal testcase. Please let me know how to proceed. Version: 6.2.0.0.alpha0+ Build ID: f05b0a6aaf8af5d78f9cad8bb953228cb0ce09f1 CPU threads: 8; OS: Mac OS X 10.11.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-08-20_00:51:25 Locale: en-US (en.UTF-8); Calc: threaded
@Jens : from the screenshot, it seems to be a font display/fallback issue. Which particular font is being used in the document at that place ? If you can provide a sample Writer document with any content and using that font, then we might be able to confirm, but the font really needs to be freely accessible. Is the font supplied by default with the OS ?
The fonts in use here are Times New Roman (9pt) and Arial (9pt) both of which are installed by default on my system and available. It doesn’t seem to be a font display/fallback issue because the dropping of space characters and 0-char spacing seems to happen randomly all over the document and even sometimes mid-sentence. What’s odd is the fact that space characters seem to disappear!
It seems that the document is in compatibility mode. Saving as current DOCX without compatibility mode seems to resolve this issue… what’s the difference here?
Please attach a sample document, as this makes it easier for us to verify the bug. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
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 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-20190321
The document contains protected content. I have reached out to you regarding this issue, but have not received a response.
(In reply to Jens Troeger from comment #6) > The document contains protected content. I have reached out to you regarding > this issue, but have not received a response. How did you reach us? by email? to which email address did you send it ?
Dear Jens Troeger, 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 Jens Troeger, 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