I agree this is important, and it should probably be introduced much earlier on in the examples and then all the following examples should be doing it all the time. There may be examples in the writing extensions docs that should have it added as well.

The problem is afaik we don't actually have a documented right way to localize extensions yet - to pull the internationalized strings from the source files into po files to be translated, translate them, and then use the translated strings in CKAN.

I think there needs to be a new chapter in the docs, _Internationalizing and localizing extensions and themes_, that goes through all the steps in one place. Once we have that, the examples in the extensions and theming docs should be internationalized and should just point people to the _Internationalizing and localizing_ docs for details.

For now, I think I'd like to leave this as it is, and work on all this in a separate pull request.