fix(locale): force Gregorian date formatting - #652
Open
KristjanESPERANTO wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While working on PR #649, I noticed that
prettifyValue()could format Gregorian dates using a locale's default calendar. For example, Farsi could formatMar 06-Jul 15as6 اسفند (Esfand)-15 تیر (Tir)instead of6 مارس (March)-15 ژوئیه (July).EsfandandTirare months in the Persian calendar, not the Gregorian months March and July, so this mixed up two calendar systems.The output now explicitly uses the Gregorian calendar while preserving localized names and formatting. The tests also introduce
addPrettifyValueForLocale, so locale-specific regression tests always run independently of the selected test locale.