| Summary: | Cell with Arabic (only?) text that starts with LTR character is rendered incorrectly | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | J. R. Schmid <jrs+documentfoundation> |
| Component: | Calc | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED INSUFFICIENTDATA | ||
| Severity: | normal | CC: | xiscofauli |
| Priority: | medium | ||
| Version: | 5.2.5.1 release | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Attachments: |
Screenshot of example document showing correct (cell A1) alongside broken (cell A2) Arabic rendering
Document capable of showing correct vs. broken Arabic rendering if doubleclicking either cell A1 or A2 Screenshot of example document showing correct (cell A1) alongside broken (cell A2) Arabic rendering Document capable of showing correct vs. broken Arabic rendering if doubleclicking either cell A1 or A2 How it looks in LibreOffice 6.5 master |
||
|
Description
J. R. Schmid
2019-09-24 13:00:08 UTC
Created attachment 154436 [details]
Screenshot of example document showing correct (cell A1) alongside broken (cell A2) Arabic rendering
Created attachment 154437 [details]
Document capable of showing correct vs. broken Arabic rendering if doubleclicking either cell A1 or A2
Created attachment 154441 [details]
Screenshot of example document showing correct (cell A1) alongside broken (cell A2) Arabic rendering
Created attachment 154442 [details]
Document capable of showing correct vs. broken Arabic rendering if doubleclicking either cell A1 or A2
Created attachment 156491 [details]
How it looks in LibreOffice 6.5 master
it looks fine Version: 6.5.0.0.alpha0+ Build ID: b9d6ea1dd7541c4bd866571f9e3f0aa894687c07 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ? You can install it alongside the standard version. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build Dear J. R. Schmid, 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 J. R. Schmid, 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 |