Requirement for multilingual interfaces

• One should be able to activate (not develop) multilingual projects in Map Fish?.
• Every module should be multilingual-compliant (activated or not, but it should be possible, just to activate a language and to add the translated strings
• Search module and attributes display should be able to gather different table attributes: name_fr, name_en
• Language switching should keep the state of the application
• Translated elements should be stored in UTF8 format to avoid encodings problem

Using technology

• Using the lib i18n Open Layers? (for Mapfish pages).
• Babel is recommended when using pylon for server side translate (http://babel.edgewall.org).
• For the template, we can use Mako (http://www.makotemplates.org/docs/usage.html#usage_common_babel). With this solution, it is possible to translate pages without mapfish (static html).

Skill

• We can generate the Open Layers? translations files (lang.js) with Babel.
• Use the permalink logic to generate lang links (lang links update is triggered: either on same events as permalink [toomuch], or when the lang link is clicked [best])