You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the future, we'll need our apps available in languages other than English. i18n is really hard to retrofit into an app, so we need to plan for it upfront, and continuously confirm it's working.
HGTV should be made available in at least one other language as a test case, as it contains very little UI text and should be easy to translate. The tasks:
Use a framework like Babel to manage translation strings (Baseframe uses it).
Ensure server-side translation for text originating in Python code or Jinja2 templates by using the _() and __() wrappers (Python) and {% trans %} tag (Jinja2) wherever UI text appears.
Use format_* and ngettext wherever numbers or singular/plural-based text appears.
Pick an i18n framework for JavaScript and figure out how to do client-side translations (this should be solved in Baseframe and used here).
Commission a translation into at least one other language that the dev team can understand.
The text was updated successfully, but these errors were encountered:
In the future, we'll need our apps available in languages other than English. i18n is really hard to retrofit into an app, so we need to plan for it upfront, and continuously confirm it's working.
HGTV should be made available in at least one other language as a test case, as it contains very little UI text and should be easy to translate. The tasks:
_()
and__()
wrappers (Python) and{% trans %}
tag (Jinja2) wherever UI text appears.format_*
andngettext
wherever numbers or singular/plural-based text appears.The text was updated successfully, but these errors were encountered: