Model data in many languages is pretty well managed by our versioning system, but what about templates, error messages and locales (dates, etc) ?
We created our own phrase --> translation mechanism but it is really SLOW (too many db calls). Therefore, we are looking for some other tool.
Our ideas are to use Gettext for all internal translations and to expand zafu for templates.
Zafu templates are already rendered once per language, so it is easy to create a totally customized template for a language (just create a version in the desired language for the template). But what happens if you just need to translate the word “documents” ?
One idea would be to create a zafu tag to import translations <z:translate with='myphrases.yml'>...</z:translate>, the translations being globally available in the translate scope through <z:trans>documents</z:trans>.
The “myphrases.yml” would be a yaml TextDocument. Either with all languages like this :
en:
documents: "documents"
clic_here: "please clic here"
fr:
documents: "documents"
clic_here: "veuillez cliquer ici"
or with one version for each language :
documents: "documents"
clic_here: "please clic here"
Gaspard Bucher