Writeup and general estimates for work to internationalize KARL

[Paul Everitt]

Tom has gotten inquiries about a French version of KARL. To better inform him for scheduling and planning, he needs a summary of the work involved, impact, and enough of an educated guess on effort.

I provided some initial feedback, but it is better to get an architect's statement on this.

I'll put this in M49, which I'm currently thinking covers October. If you're booked and can't get it done by then, lemme know and I'll reschedule.

[Tres Seaver (tseaver)]

There are actually two pieces of the puzzle here:

- Internationlization (i18n) of KARL is the task of preparing the KARL software
  to allow translations to be applied wherever code or templates contain
  in-language text. This effort requires visiting each and every KARL
  template, adding the appropriate 'i18n:' markup, as well as updating any
  Python code which emits text (e.g., status / error messages). The end-
  product is the internationalized templates and code, *plus* the 'karl.pot'
  file which serves as the starting point for creating a translation. The
  initial 'karl.pot' file should be able to be generated via a tool from the
  internationalized source files.

- Localization (l10n) of KARL to a particular language involves using the
  'karl.pot' file to create a translation file appropriate for that language.

In order to test the i18n portion, we should plan to produce a trivial
l10n (one not requiring expert translation skills), such as targeting
'en_TX' or some such trivial "translation".

[Paul Everitt (paul-agendaless)]

I'm going to count this one as done.