© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
4. Patch the Mahara Launchpad -> po file -> langpack toolchain, so that it builds this particular string into a js file instead of a php file. I think given our current limited facility at manipulating that toolchain, though, this might well be the hardest method.
5. Manage this one language string outside of the langpack infrastructure. File gerrit patches in order to update this language string. The challenge here, is that because this string is not in a Mahara lang file, translators will not be prompted to translate it in the Launchpad translation interface. Perhaps we could add it to a langpack just as a placeholder, in order to trigger that prompt? This would be a really slipshod way of doing things, though.