2014-09-15 15:35 GMT-03:00 Johan Brichau <jo...@inceptive.be>: > On 15 Sep 2014, at 19:31, Stephan Eggermont <step...@stack.nl> wrote: >> The main problems I have with external tools is the lack of translation >> context and the >> slow feedback cycle. That is killing for translation speed and quality. > I can understand that in-app tools work well for developers but when you > start working with translators (humans) that are not developers (and > certainly not Smalltalkers), you want to export the translation work. Now, > Gettext is certainly not the walhalla, but I see a lot of things to do in-app > before even getting to the level of those external tools.
+1 We used a Gettext like (custom dev) approach in the past, and it was the analyst and expert users who did the translations and customizations (regional dialects). It involved 3 languages and several dialects of Spanish. Some specific terms are different in different countries and/or each corporation has a different jargon which THEY WANT to see on the screen/reports. It worked very well. And because the files were plain text it was even easier to integrate different modifications to the master file using standard tools like git/diff. Regards!
