Page MenuHomePhabricator

Make all interface messages translatable
Closed, ResolvedPublicBUG REPORT

Description

There are still lots of interface messages that are hardcoded in English (e.g. the home page). These should be moved to the i18n files, and so made translatable on TranslateWiki.

This task will involve finding all the English messages, moving them to i18n/en.json, and accessing them via e.g. the Twig msg function {{ msg('msg-name-here'). The i18n/qqq.json file will also need to be updated to include the new messages. Make sure to run composer test and npm run test before submitting a pull request.

Event Timeline

Frostly triaged this task as High priority.
Frostly added a project: User-Frostly.
Frostly moved this task from Backlog to In progress on the User-Frostly board.
Frostly lowered the priority of this task from High to Medium.Oct 1 2023, 8:01 PM
Frostly moved this task from In progress to Backlog on the User-Frostly board.
PMenon-WMF subscribed.

Hi @Frostly, removing you from this task because it has been stale for a while. Feel free to re-assign it to yourself and give us an update if you are still working on it!

I have opened PR #77 on GitHub.
I have a question, for the text Index Pages:, is it okay to do {{ msg('index-pages') }}: [1] as index-pages already exists and is also used somewhere else and this way we can avoid double translation of same thing. But for languages that are written in right to left, is what I am concern about.

[1]: https://github.com/AS1100K/wscontest/blob/2b85ca9dcc4f1f69d7cd34beba140dccd15942eb/templates/contests_edit.html.twig#L44C15-L44C91

Thanks for the PR!

I have a question, for the text Index Pages:, is it okay to do {{ msg('index-pages') }}: [1] as index-pages already exists and is also used somewhere else and this way we can avoid double translation of same thing.

No, it's best to not re-use messages, and in this case they're also not the same because one needs the colon and one doesn't (different languages may use a different character for that purpose, so it needs to be included in the message).

Done and released in 2.5.3.

Thanks @AS1100K!