Page MenuHomePhabricator

Make translations more modular so third-party libraries can translate their strings
ClosedPublic

Authored by epriestley on Feb 11 2015, 8:00 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Dec 13, 8:40 PM
Unknown Object (File)
Fri, Dec 13, 4:38 PM
Unknown Object (File)
Thu, Dec 12, 3:10 PM
Unknown Object (File)
Fri, Dec 6, 5:56 PM
Unknown Object (File)
Wed, Dec 4, 7:36 PM
Unknown Object (File)
Tue, Dec 3, 10:25 PM
Unknown Object (File)
Tue, Dec 3, 6:33 PM
Unknown Object (File)
Sat, Nov 30, 7:36 AM
Subscribers

Details

Summary

Ref T7152. Ref T1139. This is a little far afield, but I need to translate some "%s thing(s)" strings into English in Instances to complete the invite workflow.

This isn't currently possible because translations are not modular enough: a library can not translate only its own strings.

To fix this:

  • Define PhutilLocale, which provides a target translation language, like "English (US)".
  • Provide PhutilTranslation, which provides some strings in a target language. Libraries can subclass PhutilTranslation to supplement strings.
  • Rework PhutilTranslator to be aware of locales.
  • I also formalized test translations, silly translations, and de-hacked up the "ALL CAPS" translation. The sex/plural rules are still hard-coded for now.
Test Plan

See next two diffs.

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Make translations more modular so third-party libraries can translate their strings.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
btrahan edited edge metadata.
This revision is now accepted and ready to land.Feb 11 2015, 8:28 PM
This revision was automatically updated to reflect the committed changes.