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? No, it won't. We need to get rid of that file. PS: I can't find it. Shouldn't we have at least one in qttranslations? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
