Skip to content

Conversation

@ilkka
Copy link

@ilkka ilkka commented Nov 27, 2025

The format string should be written using the tokens derived from English, i.e. "yyyy" for years. The example leads one to believe that tokens derived from the user's current language could be used. Fix Finnish and Ukrainian because those are the two that I could spot that make this error.

Screenshots

Testing strategy

Type of change

  • ✅ Bug fix (non-breaking change that fixes an issue)

The format string should be written using the tokens derived from
English, i.e. "yyyy" for years. The example leads one to believe that
tokens derived from the user's current language could be used. Fix
Finnish and Ukrainian because those are the two that I could spot that
make this error.
@ilkka ilkka force-pushed the dont-translate-format-string-tokens branch from 6a9c14c to afb7be6 Compare November 27, 2025 07:34
@phoerious
Copy link
Member

phoerious commented Nov 27, 2025

Translations are fixed on Transifex. This is something that should be done there or the source translation needs to be updated to contain a placeholder that is an untranslatable string. Personally, I wouldn't mind localising the pattern, as not everyone is able to read English date formats. Though I do see that this might cause problems if the language uses a different alphabet.

@phoerious phoerious closed this Nov 27, 2025
@ilkka
Copy link
Author

ilkka commented Nov 27, 2025

Okay, it's just that these example patterns just don't work.

@ilkka ilkka deleted the dont-translate-format-string-tokens branch November 27, 2025 18:25
@droidmonkey
Copy link
Member

droidmonkey commented Nov 27, 2025

Dealing with localized pattern matching is a nightmare, no thanks. I made the changes in transifex.

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.

3 participants