Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: update Calendar Localization Issues in nepaliCalenderdata.ts and calendarLocalisations.ts #42

Merged
merged 7 commits into from
Jun 24, 2024

Conversation

rc-poudel
Copy link
Contributor

This pull request addresses two issues related to calendar localization:

nepaliCalenderdata.ts file for the year 2081
Current:
2081: [17, 31, 31, 32, 32, 31, 30, 30, 30, 29, 30, 30, 30]

Corrected:
2081: [17, 31, 32, 31, 32, 31, 30, 30, 30, 29, 30, 30, 30]

Issue in calendarLocalisations.ts:
Add 32 to the ne-NP numbers array.

error screenshot
Screenshot

solved screenshot
Screenshot 2024-06-24 at 07 44 01

Let me know if there are any questions or further adjustments needed.

Copy link
Collaborator

@kabaros kabaros left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @rc-poudel - One thing that came up during discussion with the Temporal team around Nepali calendar (and this kind of updates) is that they asked us to add a ticket for Nepali calendar to be added to the Unicode CLDR - they believe this should be straight forward for implementers (browsers, OS etc..) to follow on and implement.

Here is the disucssion - would you be interested in adding a ticket for Nepali as described, and following up on it? or recommend someone who could? (I can add the ticket, but I am not expert on the calendar itself so won't be able to answer calendar-specific questions). It would be great to see Nepali calendar natively supported by browsers at some point.

@kabaros kabaros changed the title Fix Calendar Localization Issues in nepaliCalenderdata.ts and calendarLocalisations.ts fix: update Calendar Localization Issues in nepaliCalenderdata.ts and calendarLocalisations.ts Jun 24, 2024
@kabaros
Copy link
Collaborator

kabaros commented Jun 24, 2024

@rc-poudel are you able to fix the conflicts in this PR (I htink just need to remove the change to package.json) and also update the commit message to follow our expected format, i.e. squash the commits and change the title to something like fix: update calendar data for year 2080 in nepali calendar (same for the PR title)

@rc-poudel
Copy link
Contributor Author

I have updated and fixing the conflicts on package.json

Please review and let me know if any further changes are needed.

as you know, our Nepali calendar system is different and needs a separate field for manipulation. I use the above package for display in the Capture app in DHIS2. If I have any new updates, I will let you know soon.

@kabaros
Copy link
Collaborator

kabaros commented Jun 24, 2024

@rc-poudel the build is still failing - all commits in the branch needs to follow the correct format .. it's probably easier to sqaush all commits into with the correct format. Happy to jump on a call to help you with this if necessary mozafar(at)dhis2.org

image

@rc-poudel rc-poudel force-pushed the amakomaya branch 2 times, most recently from 2bbfc08 to c34decf Compare June 24, 2024 11:32
@rc-poudel rc-poudel reopened this Jun 24, 2024
@kabaros kabaros merged commit f172662 into dhis2:main Jun 24, 2024
2 of 4 checks passed
@dhis2-bot
Copy link
Contributor

🎉 This PR is included in version 1.2.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants