On 15 Sep 2014, at 19:31, Stephan Eggermont <stephan@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. Also, there is translation context exported to Gettext (but this does not help actually) and whenever a translator changes the file, we immediately read it again in the app, so I donât really understand the slow feedback cycle issue. There are other tools btw: - http://translate-toolkit.readthedocs.org/en/latest/index.html - http://www.arizona-software.ch/ilocalize/ Iâm all for an approach where Pharo explicitly caters for multiple possible translators, where Gettext would just be one possible option. This is more or less what exists today, except that itâs ad-hoc and deserves a cleaned implementation and design. Gettext and other translators can plugin to the Locale and Translator class hierarchies that are there. Johan