[qmc2-devel] Italian translation
Brought to you by:
prianthefist,
renereucher
|
From: R. R. <ren...@ba...> - 2012-03-02 18:03:21
|
Hi Stefano! Your sf.net account should now be allowed to do commits in the SVN repository. Please do all updates against the "trunk". A general "rule": when using an editor for any manual editing, please choose one that produces POSIX-like line endings (and not WinDOS-like "^M"'s). I prefer 'vi', but that's a matter of taste, of course :)! Not counting the documentation, the steps to translate QMC2 basically consist of 2 things: translation of the application with Qt Linguist (> 3220 meanhwile, I'm sorry!) and the translation of the external "emulator configuration templates" (XML files) with either Marcelo Bossoni's Java translation tool or manually (I'd prefer Marcelo's tool, if I were you...). Anyway, I would suggest to start with the application translation via Qt Linguist... You'll find the Italian (completely unfinished) translation source in 'data/lng/qmc2_it.ts'. All you have to do is open this file in Qt Linguist and start translating :)... 'lrelease' will be called whenever necessary through make (there's also a "make lang", BTW). You should produce the compiled translation (data/lng/qmc2_it.qm) before you "svn commit" your changes, but if you miss that, it'll be updated by me on the next commit :). The required minimum Qt version is 4.7, BTW, but I'd recommend to use 4.8, if possible. As the Italian translation will surely take a bit of time to complete, we should do the following in order to avoid SVN merge-conflicts during this period: - I will refrain from running 'lupdate' as long as possible. - When I *must* run it, I will post a message here asking you to "commit your changes" so I can run 'lupdate' safely afterwards. Regarding template translation... well, let's talk about it in detail when you're ready to go :)! You'll find the XML files in 'data/opt/<emulator>/template.xml'. Basic idea is that every <section> and every <option> can have a translation of its <description>: Example: <section name="search_paths"> <description lang="us" text="Search paths"/> <description lang="de" text="Suchpfade"/> ... <option name="crosshairpath" type="directory" default="crosshair"> <description lang="us" text="Path to crosshair files"/> <description lang="de" text="Suchpfad für Fadenkreuz-Dateien"/> ... </option> </section> Have fun, René |