Description: I need to number chapters and subheadings in chapters in my thesis in a right-to-left language (Persian). The outline numbering works as expected in LTR but when I switch the text direction, the order of heading numbers will not change. For example, 1.2.3 in LTR would refer to subheading 3 of subheading 2 of chapter one. In RTL I expect it to show on the right side of the page in the reversed order, ie., ۳.۲.۱. Steps to Reproduce: 1. define outline numberings for heading 1, heading 2, etc. 2. modify heading styles text direction to RTL 3. apply the styles to the heading titles Actual Results: outline numberings appeared in the wrong direction. Expected Results: in RTL language chapter number should appear on the right side, then outline number for heading 2, the heading 3, etc. Reproducible: Always User Profile Reset: Yes, many times. Additional Info: Just that this is very urgent. If this cannot be resolved soon, I may have to switch to MS Office which I have resisted many years. Or I will have to enter outline numberings manually. I have searched for this problem. Some people had mentioned the same issue in other places since maybe 2012 and some had suggested that this cannot be solved and a bug report/feature request must be filed. I was unable to solve it too and did not find a bug filed for it, and hence the report. User-Agent: Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2486.0 Safari/537.36 Edge/13.10586
شما می توانید یک فایل پیوستی را همین جا بگذارید تا من مشکل را گزارش کنم با تشکر
یا اگر نیاز به تغییر در جایی بود به فارسی توضیح دهید تا آن را به تیم لایبر آفیس اطلاع بدم
Created attachment 128797 [details] examples of what happens of what must happen
سلام لطفا فایل پیوستی را ملاحظه بفرمایید. اینجا در واقع دو ایراد وجود دارد. یکی را قبلا توضیح دادم و دیگری را در این فایل اضافه کردم. داخل فایل مثال زده‌ام. خیلی متشکرم.
در مورد علامت اعشار امیدوارم مساله در مورد شماره‌ی فصل‌ها و زیر فصل‌ها و ترکیب‌هایی مانند «(... ۲۱۳). بببب» که توضیح دادم حل شود و تاثیری روی رفتار لیبره آفیس با اعداد اعشار خالص مثل ۱.۲ نداشته باشد.
سلام، فایل پیوستی رو مشاهده کنید
Created attachment 128887 [details] Description about problem
بعد از مشاهده فایل پیوستی فونت گفته شده را از لینک زیر دانلود و نصب کن http://www.uplooder.net/files/8ea4a8c14a84a3ccc34344cb4aeec6d0/fonts.zip.html
این مشکلاتی که شما در فایل پیوستی مثال زده اید به احتمال زیاد در نسخه 5.3 رفع خواهند شد به هر حال باید با مشکلات کنار اومد
Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists in 5.3. Change to RESOLVED FIXED, if the problem went away.
Hi, Finally got to check the reported issue in 5.3. The issue has not went away. This is an obviously missing feature in LibreOffice. There should be an easy way of changing the alignment of outline numberings to right-to-left when typing in an RTL language. In RTL documents it's preferred that chapter numbers appear on the right, then following by other outline levels.
Hello, Is anyone paying attention here?
Confirmed in Version: 5.4.0.0.alpha0+ Build ID: d3676ceeec55a41337ce5e6bc596f4f100d0638e CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk2; Locale: ca-ES (ca_ES.UTF-8); Calc: group and Version: 4.3.0.0.alpha1+ Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
Any news on this bug?
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Hi, I have checked and the bug still is present in the most recent version of LibreOffice. Info from Help>About: Version: 6.1.0.3 Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: en-US (en_US); Calc: group threaded
Dear Nima Az, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Nima Az, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Repro: Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: bfbae5ddd52cf80af94b250b9de349f0340dbe34 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: threaded