From: D. M. M. <mic...@ro...> - 2009-11-13 04:44:06
|
I have completed a string audit in the course of finishing the Spanish translation. (This translation is in need of a review by a native speaker. I think I have done an admirable job for a gringo, but I'm sure it needs refinement and proof reading.) User-visible strings are officially frozen as of three... two... one... NOW! Developers should make NO CHANGES to user-visible strings that are not ABSOLUTELY UNAVOIDABLE. (This includes restructuring the source tree by moving files around, as this impacts translation contexts.) By extension, we have a soft feature freeze, because it is difficult to add, remove, or modify features without changing strings. However, many minor issues remain to be sorted out, and there is some leeway here. All of this is sort of a dry run for the alpha we're about to release, so that hopefully by the time the final release date gets here (14 February 2010 or whenever it's ready, whichever comes first) we will have worked through all the problems with this new system. I have started a revised set of instructions for translators. It is not yet complete, but watch this space over the next few days: http://rosegardenmusic.com/wiki/translator:add_or_update_translation I've modified the reporting tool to produce interesting feedback. Instead of looking at "Untranslated" strings, we will judge the level of completion by the number of "unfinished" strings instead. With Qt and Qt Linguist, if no translation is required (eg. a string like "%1 %2") then no translation is recorded, and this string remains "untranslated" even after being marked as "finished." However, the list of "unfinished" strings may very well include some huge number that are, in fact, translated, and merely need to be reviewed and approved. ------------------------------------------------------------------------------ TRANSLATION STATUS REPORT FOR THE ROSEGARDEN PROJECT ------------------------------------------------------------------------------ rosegarden.ts contains 4037 messages Language Total Translated Untranslated Unfinished Obsolete Status -------- ----- ---------- ------------ ---------- -------- ------- en 4037 20 4002 0 0 [%%%%%] en_GB 4037 101 3920 0 0 [%%%%%] en_US 4037 20 4002 0 0 [%%%%%] es 4037 3917 72 0 0 [%%%%%] fi 4037 4242 94 85 363 [%%%%-] de 4037 4209 128 187 366 [%%%%-] cs 4037 4042 242 300 302 [%%%%-] fr 4037 3274 1000 2288 301 [%%---] ru 4037 2972 1259 2594 269 [%----] it 4037 2861 1377 3846 252 [-----] ca 4037 2555 1650 4037 223 [-----] cy 4037 1945 2266 4037 205 [-----] et 4037 1973 2203 4037 156 [-----] eu 4037 2629 1576 4037 220 [-----] id 4037 1630 2503 4037 127 [-----] ja 4037 2809 1425 4037 249 [-----] nl 4037 2826 1417 4037 253 [-----] pl 4037 2724 1496 4037 236 [-----] sv 4037 2831 1405 4037 251 [-----] zh_CN 4037 2384 1835 4037 211 [-----] Total: total strings that are note obsolete Translated: strings that have been translated Untranslated: strings that have no translation (may be finished) Unfinished: strings that have not been marked as finished (may or may not have a translation) Obsolete: strings were translated, but these translations are no longer used in the source (frequently happens after someone edits a text to make a correction) Report produced on Thu, 12 Nov 2009 22:59:03 -0500 -- D. Michael McIntyre |
From: Alexandre P. <ale...@gm...> - 2009-11-13 07:23:54
|
On Fri, Nov 13, 2009 at 7:40 AM, D. Michael McIntyre wrote: > ru 4037 2972 1259 2594 269 [%----] Bloody hellfire, that's a lot of work ahead. February 14 sounds like a kind of relief as a deadline :) Thanks for being kinds to us, Michael :) Alexandre |
From: D. M. M. <mic...@ro...> - 2009-11-13 15:53:13
|
On Friday 13 November 2009, Alexandre Prokoudine wrote: > Bloody hellfire, that's a lot of work ahead. February 14 sounds like a > kind of relief as a deadline :) It was a lot of work indeed, but it's not as bad as it looks on the surface. Remember that you really only have 1259 (yeah, only! :) ) new strings to translate, and most of the 2594 you will just have to look at and hit Ctrl+Enter to mark as finished. > Thanks for being kinds to us, Michael :) You're welcome, Alexandre and everyone else. I know this is going to be the longest and most difficult job of translation anyone ever faces at Rosegarden, and it's important to give everyone plenty of time. -- D. Michael McIntyre |
From: oota <ri...@us...> - 2009-11-16 14:21:21
|
On Thu, Nov 12, 2009 at 11:40:52PM -0500, D. Michael McIntyre wrote: > I have started a revised set of instructions for translators. It is not yet > complete, but watch this space over the next few days: > ------------------------------------------------------------------------------ > TRANSLATION STATUS REPORT FOR THE ROSEGARDEN PROJECT > ------------------------------------------------------------------------------ > ja 4037 2809 1425 4037 249 [-----] OK. for translation qt4's new i18n system,I had changed my linux environment from TURBOLINUX to OpenSUSE 11.2 because OpenSUSE 11.2 has qt-4.5.3 . I began to translate ja.ts file with qt4 linquest,but it did'nt work! It caught SEGFALUT! So anyone know how to translate .ts file without linquest? Any other tool exsit? (Of course, .ts file written with XML. So any editor (like emacs)can handle .ts file. But editing .ts file directly is very danger than specific tool , I think.) oota |
From: D. M. M. <mic...@ro...> - 2009-11-16 16:17:38
|
On Monday 16 November 2009, oota wrote: > I began to translate ja.ts file with qt4 linquest,but it did'nt work! > It caught SEGFALUT! > > So anyone know how to translate .ts file without linquest? > Any other tool exsit? This is unfortunate. :( I see no good answer to this one, but it looks like you may be able to get the job done using ts2po (from a package called "translate-toolkit" on my system) and editing the .po file with the new KDE translation tool lokalize (and possibly other tools that use po files, but trusty old KBabel no longer exists) then converting it back with po2ts I would not want to have to do that myself if I could avoid it, although it's probably better than editing all the translations in a text editor. When I tried lokalize on the converted .po file, it did not load the source code to show the translation context, and that meant none of the // TRANSLATOR comments were visible. We have a lot of translator comments, and a lot of strings that may be difficult to translate correctly without them. (B the note versus B the keyboard shortcut, for example.) If I were in your situation, I would try to fix Qt Linguist if at all possible. Does your version of Linguist segfault on any other .ts file, or just ja.ts? If it is broken in general, perhaps the OpenSuSE maintainers might be of some assistance sorting out why your package seems to be broken. I'm not familiar with OpenSuSE or how they do things though. Another possibility worth attempting if you have time is to download a Qt source tarball and compile it yourself to /usr/local, and try using the linguist from that installation. Earlier in development, I had Qt 4.4.3 from distro packages installed to /usr along with Qt 4.5.0 from source in /usr/local and I was able to run everything successfully. The only problem I had with this arrangement was when I tried to compile software other than Rosegarden in this environment. I had no runtime problems. Qt takes hours to compile, but it is not difficult to get it to go. Hopefully you won't really have to resort to that. Anyway, good luck with this, and I regret that you are experiencing such problems! This is bad! -- D. Michael McIntyre |
From: Alexandre P. <ale...@gm...> - 2009-11-16 18:28:00
|
On 11/16/09, oota wrote: > So anyone know how to translate .ts file without linquest? > Any other tool exsit? Virtaal can handle it. http://translate.sourceforge.net/wiki/virtaal/index Alexandre |
From: oota <ri...@us...> - 2009-12-15 10:31:36
|
On Mon, Nov 16, 2009 at 10:25:45PM +0900, oota wrote: > > for translation qt4's new i18n system,I had changed my linux environment > from TURBOLINUX to OpenSUSE 11.2 because OpenSUSE 11.2 has qt-4.5.3 . > I began to translate ja.ts file with qt4 linquest,but it did'nt work! > It caught SEGFALUT! I change base system OpenSUSE 11.2 to Ubuntsu 9.10. It has qt-4.5.2 and linguist worked. I try to translate some message,and upload it (No. 2914692). Would anyone check this translation is correct or not? If ok,then I will translate it sequentially. oota |
From: D. M. M. <mic...@ro...> - 2009-12-16 00:50:25
|
On Tuesday 15 December 2009, oota wrote: > I try to translate some message,and upload it (No. 2914692). > Would anyone check this translation is correct or not? > If ok,then I will translate it sequentially. It looks fine to me. Committed revision 11464. -- D. Michael McIntyre |