add locale support for name specifiers#92
Merged
Merged
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
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.
WithLocale(Locale)to localize name specifiers%A %a %B %b %h %p; numeric specifiers unaffectedLocaleis an interface built viaNewLocale(...)functional options; English default derived from stdlibtime, empty entries fall back to EnglishStrftimeper context; a future%OB/%Obcan be added as an optional interface without breaking the APINote: this ships no actual localizations — the library carries no per-language name data. It provides the escape hatch so users can supply their own names (or implement
Localethemselves, backed by a map / computed values / an external dataset).Closes #64