Den 3 Sep 2014 kl. 6:11 PM skrev Thiago Macieira: > On Wednesday 03 September 2014 07:16:22 Saether Jan-Arve wrote: >> We could do that, but I don't see the problem in providing the translation >> file. Shawn already mentioned many good reasons for why translating the >> "engineering English" to "end user English" (whatever that is) is a good >> thing. (Note - you don't need to provide translations for everything) > > The problem is actually shipping and loading such a file. > > Imagine an application that is only run in English (no L10n) and for which > the > source code has proper, English messages. Will it occur to the developers > that > they have to provide the en_US translation file from Qt?
It doesn't necessarily occur to an English speaker to identify translatable strings and wrap them in tr(), either. It is some work already to try to support localization, so we are talking about people who are aware enough to think about supporting it. But if we were using enum keys instead of string-string lookup, it would be more efficient and would also encourage separation of content from the means of displaying it. _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
