Skip to content

Fix Persian future-time wording and locale metadata - #461

Open
AliEmami81 wants to merge 1 commit into
python-humanize:mainfrom
AliEmami81:fix-persian-future-time
Open

AliEmami81 wants to merge 1 commit into
python-humanize:mainfrom
AliEmami81:fix-persian-future-time

Conversation

@AliEmami81

Copy link
Copy Markdown

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 as 3 ثانیه تا به اکنون.

This changes the future template to %s دیگر, producing 3 ثانیه دیگر (in three seconds), and corrects the Persian catalog's copied German language metadata. Past and present wording is preserved.

Validation:

  • Added five regression cases covering past, present, and future timestamps with an explicit reference time. Before the translation change, both future cases failed and the other three passed.
  • Recompiled translation catalogs locally using polib; the upstream CI uses its existing gettext compilation step.
  • Internationalisation suite: 121 passed, 2 skipped (gettext command-line tools are unavailable locally).
  • Full non-benchmark suite: 844 passed, 2 skipped.
  • Ruff and Black checks on the changed test file.

This contribution was prepared with AI assistance and checked against the Persian wording and executable regression tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant