I am searching for some best practices for using lupdate, lrelease and linguist for a large project. Our project consists of some 300 Visual Studio projects (no qmake .pro files), which we would like to combine in a single .qm file per language. At the moment, the total number of strings is about 15.000.
There are some issues I have to address. The first on is the collection of the strings (lupdate). As we are not using qmake, I would have to feed the path(s) into lupdate. I could add the top-level directory, but this will include any strings in test and demo programs, which we do not want to include in translations. On the other hand, I may list all the files in a listfile to be used with lupdate, but this requires keeping the list file up to date. My first approach was to run lupdate separately for each project, updating the .ts files only partially. However, I cannot tell lupdate NOT to mark entries as obsolete. A second issue is concurrent translations that may lead to merge conflicts in SVN. Of course, this (and the above) problem can be solved by using one .ts file per project. However, with this approach the translators for one language will be faced with 300 files to be translated and the overall number of .ts files will reach the thousands. Does anyone out there has some experience in i18n with large projects and can share some hints or best practices? Best Regards / Mit freundlichen Grüßen Rainer Wiesenfarth -- Software Engineer | Trimble Imaging Division Rotebühlstraße 81 | 70178 Stuttgart | Germany Office +49 711 22881 0 | Fax +49 711 22881 11 http://www.trimble.com/geospatial/ | http://www.inpho.de/ Trimble Germany GmbH, Am Prime Parc 11, 65479 Raunheim Eingetragen beim Amtsgericht Darmstadt unter HRB 83893, Geschäftsführer: Dr. Frank Heimberg, Hans-Jürgen Gebauer
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
