fix -j and -g problems

[arsalanyavari]

fix the #11, #33 and #36 issues

[fzerorubigd]

The leap check function has two parts. The first is using the official data to simply get the leap status based on a table can be found here
If you want to change the leap year function, then you have to provide a test for all the years in the doc and the result should be based on the doc. the range out of that can't be tested, and we can ignore the test for them.

[arsalanyavari]

I have added the file sources/test_kit/jalali/leap_range.c to the project and hardcoded the mentioned leap years in it. From now on, after the make, you can check the leap years using ./sources/test_kit/jalali/leap_range.

The logic of the new jalali_is_jleap() function has passed all these tests as well.

[fzerorubigd]

I tried several times to get to this one and merge it. but it changes everything in one single PR and every time I get to it, I decide to simply ignore it since it is too much.
while the title is to fix a flag, it changes everything. For that reason alone I am not comfortable merging this one.

[arsalanyavari]

Thanks for your response.
This bug is also caused by an error in calculating the leap years. Therefore the pull request to fix it requires all the changes we have made.

Also, the commit messages are telling, and this pull request is made up of several commits.

Feel free to ask about any of our changes and we'll happily respond.

[fzerorubigd]

Hello, Based on your friends reaction in mastadon, i feel like asking for fix is not an option. BUT if you want and you don't feel like i am wasting your time, please fix the leap year issue first in a different pr. Just the leap year issue. Thanks

…

On Fri, Sep 26, 2025, 8:33 PM Amir Arsalan Yavari ***@***.***> wrote: *arsalanyavari* left a comment (persiancal/jcal#37) <#37 (comment)> Thanks for your response. This bug is also caused by an error in calculating the leap years. Therefore the pull request to fix it requires all the changes we have made. Also, the commit messages are telling, and this pull request is made up of several commits. Feel free to ask about any of our changes and we'll happily respond. — Reply to this email directly, view it on GitHub <#37 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHEJ43OHJKEEENKH5HWD2D3UWBHDAVCNFSM6AAAAAB4JWYDXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMZZHE3DOMZUGY> . You are receiving this because you commented.Message ID: ***@***.***>