On Sat, Jun 13, 2009 at 9:52 AM, Diego Schulz<dsch...@gmail.com> wrote: > On Fri, Jun 12, 2009 at 2:14 PM, Daniel > Molkentin<daniel.molken...@nokia.com> wrote: >> Hi translators, >> >> today we committed the final round of string changes (mostly capitalization >> fixes and new tips) to the 1.2 branch. Since we would like to release soon >> (tm), please send in your translation updates until monday, if possible. >> Integrating them later will be harder if not impossible. >> >> As we have not yet ported back all changes to the master branch, it is vital >> to do any translations on the 1.2 branch. Also note that the latest changes >> will have a 12 hour delay, starting now, before they show up on the public >> repository. >> >> Attached is a small readme for translators that describes how to translate >> Qt Creator. It will show up in the repository soon, too. >> >> I am sorry that this comes on such short notice. Next time we will have a >> longer string freeze period, promised! If you need help, please ask. >> >> Have a nice weekend! >> >> Cheers, >> Daniel >> -- >> Daniel Molkentin, Software Engineer, >> Nokia Qt Software, www.qtsoftware.com >> Rudower Chaussee 13, DE-12489 Berlin >> >> How To add translations to Qt Creator >> ===================================== >> >> - Coordinate over the mailing list to avoid duplicate work. >> >> - Add your language to the LANGUAGES line in translations.pro. >> Don't qualify it with a country unless it is reasonable to expect >> country-specific variants. >> Skip this step if updating an existing translation, obviously. >> >> - Run "make ts". This will complain if you are not building against >> Qt 4.6 (or the master branch which will become it). >> >> If your Qt version is too old, you may create a template by running >> lconvert --drop-translations qtcreator_de.ts -o qtcreator_<yours>.ts >> and adjusting the language attribute in the new .ts file. The downside >> of this method is obviously that you will not be translating the newest >> Creator sources (unless qtcreator_de.ts was completely up-to-date). >> Of course, this method is not applicable if you are updating an existing >> translation. >> >> You may also request an up-to-date template from us. >> >> The remaining steps do *not* require Qt 4.6 in any case. >> >> - Fire up linguist and do the translation. >> >> - Check in the modified .pro file and _only_ your .ts file. >> >> - Make a merge request on gitorious. >> >> - .qm files are generated as part of the regular build. >> > > > I'm working on the spanish translation. I think the hardest part is > already done, installed Qt 4.6 (finally!) and now I can easily get an > updated template to work on. > The only pending obstacle I'm facing now, is to fully understand how > to manipulate the Git repositories as I need, and get the updated > translation (*and* the changes I pulled from the official repository) > pushed in a public repository. Clearly it's not a brain-dead easy task > to do it right, requires some understanding and not-so-basic skills on > Git operation, at least until you discover the hard way (checkout -f, > say bye to your past 3 hours work) that there were "other ways not so > complicated" :) > > Cheers, > > diego >
Spanish translation done, merge request pending. diego _______________________________________________ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
