Repository navigation
Fix Persian future-time wording and locale metadata - #461
Open
AliEmami81 wants to merge 1 commit into
Open
AliEmami81 wants to merge 1 commit into
AliEmami81 wants to merge 1 commit into
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.
Persian future timestamps currently use
%s تا به اکنون, which reads as a duration up to the present rather than a future time. For example, a timestamp three seconds ahead renders as3 ثانیه تا به اکنون.This changes the future template to
%s دیگر, producing3 ثانیه دیگر(in three seconds), and corrects the Persian catalog's copied German language metadata. Past and present wording is preserved.Validation:
This contribution was prepared with AI assistance and checked against the Persian wording and executable regression tests.