A cell in sheet that contains mixed Latin and Persian characters render just LTR and changing the cell to RTL does not effect on rendering. If I add Right-to-Left mark at the beginning of cell value, it renders text correctly. Note that there is no problem with Calc 6.2.8.2 on the same machine/os.
Thank you for reporting the bug. 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.) I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Created attachment 156630 [details] Sample ODS file Sample file that have bad render. The A1 cell must render RTL but it renders LTR. Use RTL/LTR button does not change it! if I add a RTL render mark character before the text, the text render will be ok.
Created attachment 156631 [details] Bad render screen shot A1 cell with bad render
Created attachment 156632 [details] Correct Render Cell A1 with correct render
(In reply to Xisco Faulí from comment #1) > Thank you for reporting the bug. 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.) > > I have set the bug's status to 'NEEDINFO'. Please change it back to > 'UNCONFIRMED' once the requested document is provided. I attached 3 file: 1. sample ODS file 2. Screenshot when render is not correct 3. Screenshot when render is correct (by add Right-to-left mark character at the begging of cell content
You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone else confirms it.
(In reply to Sadeq N Yazdi from comment #4) > Created attachment 156632 [details] > Correct Render > > Cell A1 with correct render For me it looks like this. Tested both with gtk3 and kf5 backends. Maybe try with 6.4.x. Arch Linux 64-bit Version: 7.0.0.0.alpha0+ Build ID: 23ddc3811d4d1890e4024f4e0f6bb5129a694fdc CPU threads: 8; OS: Linux 5.6; UI render: default; VCL: kf5; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 30 April 2020 Arch Linux 64-bit Version: 6.4.3.2 Build ID: 6.4.3-1 CPU threads: 8; OS: Linux 5.6; UI render: default; VCL: kf5; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded
Dear Sadeq N Yazdi, 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 Sadeq N Yazdi, 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