Page MenuHomePhabricator

Integrate with translatewiki.net for "static" message translation
Closed, ResolvedPublic

Description

  • Generate .po translation files from Django
  • Register project at TWN
  • Work with TWN on any integration steps needed to get messages into and back from TWN

Note: Dynamic content translations (T259838) are out of scope at this point.

Event Timeline

bd808 triaged this task as Medium priority.Oct 6 2020, 10:33 PM

I think we are going to eventually need to register with TWN as 3 related projects:

  • one for the Django .po files localizing the API and other backend messages.
  • one for the Vue-i18n .json files localizing the frontend UI
  • one for dynamic content translations in toolinfo records and associated annotations

I believe this splitting will be needed in order for TWN to manage it's import/export tasks for the translation strings.

Change 637824 had a related patch set uploaded (by BryanDavis; owner: Bryan Davis):
[wikimedia/toolhub@main] l10n: Add initial Django locale config

https://gerrit.wikimedia.org/r/637824

Change 637824 merged by jenkins-bot:
[wikimedia/toolhub@main] l10n: Add initial Django locale config

https://gerrit.wikimedia.org/r/637824

Change 641578 had a related patch set uploaded (by Srishakatux; owner: Srishakatux):
[wikimedia/toolhub@main] Internationalization support

https://gerrit.wikimedia.org/r/641578

Change 641578 merged by jenkins-bot:
[wikimedia/toolhub@main] Internationalization support

https://gerrit.wikimedia.org/r/641578

Change 643569 had a related patch set uploaded (by Srishakatux; owner: Srishakatux):
[wikimedia/toolhub@main] RTL support

https://gerrit.wikimedia.org/r/643569

Change 643569 merged by jenkins-bot:
[wikimedia/toolhub@main] Basic RTL support

https://gerrit.wikimedia.org/r/643569

Change 644613 had a related patch set uploaded (by BryanDavis; owner: Bryan Davis):
[wikimedia/toolhub@main] i18n: Add banana-checker and make translation files comply

https://gerrit.wikimedia.org/r/644613

Change 644613 merged by jenkins-bot:
[wikimedia/toolhub@main] i18n: Add banana-checker and make translation files comply

https://gerrit.wikimedia.org/r/644613

I think we are going to eventually need to register with TWN as 3 related projects:

  • one for the Django .po files localizing the API and other backend messages.
  • one for the Vue-i18n .json files localizing the frontend UI
  • one for dynamic content translations in toolinfo records and associated annotations

I believe this splitting will be needed in order for TWN to manage it's import/export tasks for the translation strings.

After reading a bit more about TWN setup, I believe that we actually will need 3 "message groups" for the Toolhub project and not 3 projects. Having multiple collections of messages connected to a project seems to be a well supported feature on the TWN side of things.

bd808 moved this task from Backlog to In Progress on the Toolhub board.