Description: in format cell higri calendar in calc is good but persian calendar don't correct in calc it just replace month number with month name Steps to Reproduce: 1.insert now() function in cell 2.right click and select format cell 3.select persian Actual Results: ۱۷ آبان ۲۰۲۱ Expected Results: ۲۵ مرداد ۱۴۰۰ Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: "آبان" is 8th month but now is 5th month
Created attachment 174338 [details] format cell
persian- jalali - or solar calendar https://en.wikipedia.org/wiki/Solar_Hijri_calendar
First, it should be said that the sample data for Persian in the 'Format Cell' dialog is wrong. Esfand is the last month of the Jalali calendar for each year, and it is either 29, or 30 (leap year). Thus, '۳۱ اسفند' which means '31 Esfand' is wrong in the first place. Other than that, choosing Persian in "Format Cell > Numbers" leads to a whole set of different wrong results. Either ###, or using the name of the 2nd month of Jalali instead of 2nd month of Gregorian calendar, or displaying the date from Gregorian calendar with Persian numerals. It should be noted that currently the Jalali calendar is not implemented in LibreOffice. This problem is reproducible with: LibreOffice 3.5.0rc3 Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735 OS: Linux 5.13; UI render: default; VCL: gen Version: 7.3.0.3 / LibreOffice Community Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3 CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 237a5e5121a6f12981eb6e4c5a138fc8cfa1c3cf CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Dear HM, 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
The problem is still reproducible with the latest LO 25.8 dev master: Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 3c9fdd9aeb74d76ef7f1c0581582439c8a135532 CPU threads: 12; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: CL threaded