Re: libgnomeui.po - msgfmt test failure.
On 2006-04-13T07:58:36+0300, [EMAIL PROTECTED] wrote: > msgfmt -cv libgnomeui.po -o /dev/null > > th output is: > > libgnomeui.po:17:7: parse error > msgfmt: found 1 fatal error Which version of msgfmt you are using? For me the attached file works fine: $ msgfmt -cv libgnomeui.po 344 translated messages. $ LANG=C msgfmt --version msgfmt (GNU gettext-tools) 0.14.5 Copyright (C) 1995-1998, 2000-2005 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by Ulrich Drepper. -- Tommi Vainikainen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Request for freeze break -- feature & string freeze for 2.14.x cycle
On 13/04/2006, at 2:08 AM, Elijah Newren wrote: Alternative ideas welcome. I know this really, really sucks, and I should be publicly whipped, If you're really volunteering, this could be a good fund-raiser for Gnome. I don't think we've had a public whipping for ages. :D from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gnome-applets branched
Don't forget to include all the possible and fictional towns, villages and hamlets on Moon, Mars, Venus and Io in gnome-applets-locations. Plans for 2.18 - the planets and starports of our Local group of Galaxy. Oh yes - we earn for the klingonese. Kind regards: al_shopov ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
gnome-applets branched
gnome-applets has been branched for active development towards GNOME 2.16. --d -- Davyd Madeley http://www.davyd.id.au/ 08B0 341A 0B9B 08BB 2118 C060 2EDD BB4F 5191 6CDA ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gnome-applets branched
Plans! Plans! On 4/13/06, Davyd Madeley <[EMAIL PROTECTED]> wrote: > gnome-applets has been branched for active development towards GNOME > 2.16. > > --d > > -- > Davyd Madeley > > http://www.davyd.id.au/ > 08B0 341A 0B9B 08BB 2118 C060 2EDD BB4F 5191 6CDA > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: How can I join the Esperanto translation team ?
On 4/11/06, Raphael Higino <[EMAIL PROTECTED]> wrote: > On 4/11/06, Clytie Siddall <[EMAIL PROTECTED]> wrote: > > However, if you want to risk the duplication angle (which is less > > likely if the team has not been active), you can start translating/ > > updating files and asking people here to commit them for you (send a > > mail with a link to the completed files). > > I'd like someone to correct me if I'm wrong, but AFAIK Guillaume can > risk duplicating work but he can't have his Esperanto translations > uploaded until the problem with the current official coordinator has > been solved. > > That's because if Esperanto coordinator and team are still active, > they must have their own QA process, which while Guillaume's > translations must be very welcome, they'd most likely want to apply it > to them. > > More experienced guys, am I right? Yes, you're entirely right. It's always the coordinator for the affected language who has to approve what translations for that language can go in. And until the coordinator is officially changed, the coordinator remains the same. Of course, Clytie is also right -- in situations like this, it is probably a very safe bet that the team coordinatorship will somehow change eventually, and that the new translations will probably be approved by the new coordinator. As a consequence, you could try to start translating right away in order to save some time in situations like this, and if you're not afraid of the theoretical danger of wasted work. However, new Esperanto translations must not be *committed* until the coordinatorship issue has been officially resolved. And there is still some days left for that. Christian ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Request for freeze break -- feature & string freeze for 2.14.x cycle
On 4/13/06, Vincent Untz <[EMAIL PROTECTED]> wrote: > Just wondering before giving an approval: what are the plans in the > future wrt to this? Do you plan to keep this option? Or do you think we > can have a better solution? I believe this patch is the better solution to the strict focus patches that have been around for years and by demand found their way into Debian, Ubuntu, and RHEL despite their kludgy nature. Those other patches existed because there were complaints that "Sometimes windows take focus when I don't want them to!". The "solution" in those other patches was to just never focus new windows. Period. (Why anyone would think that the run application dialog shouldn't be focused when the user presses Alt+F2 is beyond me. Or the open file dialog when the user pressed Ctrl+O in some app. Or a variety of other cases. But, it appears that some users never do those things and thus didn't mind such a kludge) Focus-stealing-prevention didn't mitigate demand for this "dont-focus-new-windows" feature either, surprisingly. The strict focus option introduced by this patch puts some rationale behind the use cases for why users wouldn't want to focus new windows (besides focus stealing prevention stuff) and only takes effect in those cases instead of kludging it in everywhere. By doing that, it became useful to a wider group of people (e.g. me) and I have reports from others that wanted the "don't-focus-new-windows" behavior that it solved their problem. Since this option solves a very common complaint (one of only two options I've ever found that had sufficient complaints/requests in order to get multiple major distros to patch in a kludgy option for it), and it has a decent usability rationale (even if for a niche set of users), I think it should stay. I've applied it to HEAD and it will be an option in 2.16 and beyond. I'd take an even better solution if one existed, but I really doubt one does at this point. > I believe it only affects the terminal, but there are mentions of other > apps in the bug, so I'm a bit lost here. Was it because users were still > using an old metacity with the first buggy version of the strict mode? That's one of the reasons. Another big reason is that users are unable to distinguish between the new behavior in 2.14.0 and the old focus stealing prevention bugs being tracked in #149028 (which isn't surprising -- most users are literally unable to distinguish between the very different concepts of focusing and raising, and the different focus-new-window behaviors is a far more subtle difference). There's possibly one more reason too: the combination of the fact that users in general have a difficult time expressing themselves coherently, and the fact that they were using the terminal to launch other apps. ;) Hope that helps, Elijah ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Request for freeze break -- feature & string freeze for 2.14.x cycle
On 4/12/06, Kjartan Maraas <[EMAIL PROTECTED]> wrote: > ons, 12,.04.2006 kl. 10.38 -0600, skrev Elijah Newren: > > Hi, > > > > Yeah, I suck. I know alarm bells are going off and this looks pretty > > bad. However, the focus behavior for programs launched from a > > terminal unfortunately appears to be really badly hated (yes, this > > only affects users using a terminal). Ubuntu has already patched it > > out (though I'm getting lots of strange bug reports about Ubuntu and > > focus which people report go away with our tarballs, making me think > > there's something amiss in their patches), and the bug is marked as an > > FC5-updates blocker. So, I'm guessing they'll take the patch (or hack > > something else together) even if this isn't approved. I'm not aware > > of the situation in other distros but those are the big two shipping > > with 2.14 right now that I know of. > > > > So, I'd like to apply Ron Yorston's patch in bug 326159 to make a > > focus_new_windows option, which simultaneously changes the default > > behavior back to what it was in 2.12. (I don't feel reverting the > > default without adding the option isn't a good idea; there's no need > > to punch the users in the face who have been requesting 'strict' focus > > options for years and finally saw this bug fixed...it'd just be too > > cruel) > > > > Alternative ideas welcome. I know this really, really sucks, and I > > should be publicly whipped, but it seemed to be worth bringing up for > > your consideration as I think not taking this is going to cause more > > pain and bugs than breaking the freeze. > > > 1/2 from me. I agree with the suckiness of the timing and all, but I > think it's worth it. After talking with Elijah a bit off-list, yes, I'd like to see this go in- 2/2. Luis ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Request for freeze break -- feature & string freeze for 2.14.x cycle
On 4/12/06, Christian Rose <[EMAIL PROTECTED]> wrote: > You have your string freeze approval from me. From looking at the > patch (http://bugzilla.gnome.org/attachment.cgi?id=61971) attached to > the bug report (http://bugzilla.gnome.org/show_bug.cgi?id=326159), it > seems the only new strings that the patch adds is the two messages for > a new GConf key in metacity. Furthermore, this sounds (from your > description) like a serious problem that bothers the distros. Thanks. And yes, the strings basically will only appear to users of gconf-editor that happen to look at this particular key. > As always, once you have had all approvals necessary and committed the > patch, please let translators know so they know when it's time to > update their metacity translations. Also, if you plan to do a new bug > fix release soon, please let the translators know so they know how > much time they have to fix the translations. With the three necessary approvals from you, Kjartan, and Luis, I have now committed the patch to the gnome-2-14 branch. I'd like to make a bug fix release soon. I would do it now, especially since the strings are extremely unlikely to be seen by users, but I don't want to cause any problems for translators. Would making a release about this time tomorrow be okay or are there any translators that would like more time? Thanks everyone, Elijah > > > Thanks, > Christian > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Request for freeze break -- feature & string freeze for 2.14.x cycle
On 4/13/06, Elijah Newren <[EMAIL PROTECTED]> wrote: > With the three necessary approvals from you, Kjartan, and Luis, I have > now committed the patch to the gnome-2-14 branch. I'd like to make a > bug fix release soon. I would do it now, especially since the strings > are extremely unlikely to be seen by users, but I don't want to cause > any problems for translators. Would making a release about this time > tomorrow be okay or are there any translators that would like more > time? Would you please wait a couple more hours, say, 3 or 4? Thanks in advance. -- Raphael Higino ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Request for freeze break -- feature & string freeze for 2.14.x cycle
On 4/13/06, Raphael Higino <[EMAIL PROTECTED]> wrote: > On 4/13/06, Elijah Newren <[EMAIL PROTECTED]> wrote: > > With the three necessary approvals from you, Kjartan, and Luis, I have > > now committed the patch to the gnome-2-14 branch. I'd like to make a > > bug fix release soon. I would do it now, especially since the strings > > are extremely unlikely to be seen by users, but I don't want to cause > > any problems for translators. Would making a release about this time > > tomorrow be okay or are there any translators that would like more > > time? > > Would you please wait a couple more hours, say, 3 or 4? Sure. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Weekly translation status for Gnome 2.14
Translation status changes from 2006-04-06 to 2006-04-13. Total message count has changed from 33917 to 33889. Average change during this period was 0.183%. Top 5 movers of the week: * Dzongkha (up 4.4%, now supported) * Breton (up 2.46%, unsupported) * Georgian (up 2.41%, partially supported) * Korean (up 1.77%, supported) * Polish (up 0.93%, supported) Supported languages (more than 80% strings translated). 1. Dutch (nl)100.00% up 0.13% Lithuanian (lt) 100.00% up 0.14% Spanish (es) 100.00% up 0.13% Vietnamese (vi) 100.00% up 0.13% Welsh (cy)100.00% up 0.14% Bulgarian (bg)100.00% up 0.13% 7. Finnish (fi) 99.99% up 0.13% 8. Gujarati (gu) 100.00% up 0.13% 9. Swedish (sv) 99.99% up 0.12% Albanian (sq) 99.99% up 0.14% German (de)99.99% up 0.14% Greek (el) 99.99% up 0.13% Japanese (ja) 99.99% up 0.15% 14. Catalan (ca) 99.98% up 0.11% Galician (gl) 99.98% up 0.11% 16. Brazilian Portuguese (pt_BR) 99.97% up 0.11% Punjabi (pa) 99.97% up 0.11% Hungarian (hu) 99.97% up 0.11% 19. Portuguese (pt)99.96% up 0.11% 20. Serbian (sr) 99.95% up 0.11% Ukrainian (uk) 99.95% up 0.11% 22. Norwegian Bookmal (nb) 99.94% up 0.12% 23. Russian (ru) 99.93% up 0.11% 24. Czech (cs) 99.80% up 0.32% 25. Italian (it) 99.31% up 0.11% 26. Canadian English (en_CA) 99.23% up 0.11% 27. Chinese Simplified (zh_CN) 98.97% up 0.11% 28. Macedonian (mk)98.96% up 0.30% 29. Chinese Traditional (zh_TW)98.70% up 0.12% 30. Romanian (ro) 97.09% up 0.12% 31. Dzongkha (dz) 96.87% up 4.40% 32. French (fr)96.35% up 0.42% 33. Korean (ko)96.08% up 1.77% 34. Danish (da)95.42% up 0.08% 35. Hindi (hi) 94.10% up 0.11% 36. Polish (pl)91.23% up 0.93% 37. Turkish (tr) 91.14% up 0.11% 38. British English (en_GB)87.43% up 0.08% 39. Indonesian (id)87.36% up 0.07% 40. Basque (eu)84.49% up 0.10% 41. Estonian (et) 84.39% up 0.23% 42. Chinese (Hong Kong) (zh_HK)83.38% up 0.07% 43. Nepali (ne)82.75% up 0.07% 44. Thai (th) 81.04% up 0.08% 45. Bengali (bn) 80.32% up 0.07% Partially supported languages (between 50% and 80%). 46. Persian (fa) 76.55% up 0.07% 47. Norwegian Nynorsk (nn) 74.59% up 0.06% 48. Croatian (hr) 67.35% up 0.06% 49. Tamil (ta) 66.64% up 0.06% 50. Hebrew (he)63.58% up 0.39% 51. Belarusian (be)63.52% up 0.28% 52. Slovak (sk)63.30% up 0.05% 53. Georgian (ka) 58.64% up 2.41% 54. Arabic (ar)58.48% up 0.06% 55. Azerbaijani (az) 58.38% up 0.06% 56. Xhosa (xh) 56.29% up 0.06% 57. Malay (ms) 51.15% up 0.07% Unsupported languages (less than 50%). 58. Bosnian (bs) 47.25% up 0.05% 59. Mongolian (mn) 47.15% up 0.05% 60. Telugu (te)40.16% up 0.07% 61. Slovenian (sl) 33.20% up 0.03% 62. Latvian (lv) 29.41% down 1.52% 63. Kirghiz (ky) 24.18% up 0.02% 64. Wallon (wa)20.40% up 0.01% 65. Irish Gaelic (ga) 16.33% up 0.01% 66. Icelandic (is) 16.04% up 0.01% 67. Oriya (or) 15.47% up 0.01% 68. Afrikaans (af) 14.63% up 0.01% 69. Malayalam (ml) 14.02% up 0.01% 70. Northern Sotho (nso) 13.89% up 0.01% 71. Breton (br)13.56% up 2.46% 72. Kurdish (ku) 12.86% up 0.02% 73. Armenian (hy) 11.73%no change 74. Serbian Jekavian ([EMAIL PROTECTED]) 11.52% up 0.01% 75. Amharic (am) 11.00%no change 76. Zulu (zu)
Weekly translation status for Gnome 2.12
Translation status changes from 2006-04-06 to 2006-04-13. Total message count is stable at 32910. Average change during this period was 0.000%. Top 5 movers of the week: * Afrikaans (down 0%, now unsupported) * Oriya (down 0%, unsupported) * Icelandic (down 0%, unsupported) * Irish Gaelic (down 0%, unsupported) * Wallon (down 0%, unsupported) Supported languages (more than 80% strings translated). 1. Catalan (ca) 99.99%no change 2. Bulgarian (bg)100.00%no change Dzongkha (dz) 100.00%no change 4. Punjabi (pa) 99.99%no change 5. Finnish (fi) 99.98%no change Canadian English (en_CA) 99.98%no change Hungarian (hu) 99.98%no change 8. Spanish (es) 99.91%no change Galician (gl) 99.91%no change 10. Dutch (nl) 99.90%no change 11. Lithuanian (lt)99.88%no change 12. Japanese (ja) 99.86%no change Ukrainian (uk) 99.86%no change Norwegian Bookmal (nb) 99.86%no change 15. Romanian (ro) 99.85%no change 16. Vietnamese (vi)99.84%no change Chinese Traditional (zh_TW)99.84%no change Macedonian (mk)99.84%no change 19. German (de)99.82%no change Albanian (sq) 99.82%no change 21. Czech (cs) 99.79%no change 22. Brazilian Portuguese (pt_BR) 99.76%no change 23. Greek (el) 99.75%no change Portuguese (pt)99.75%no change Serbian (sr) 99.75%no change 26. Russian (ru) 99.70%no change 27. French (fr)99.63%no change 28. Hindi (hi) 99.61%no change 29. Turkish (tr) 99.55%no change 30. Gujarati (gu) 99.38%no change 31. Chinese Simplified (zh_CN) 99.18%no change 32. Korean (ko)97.30%no change 33. Polish (pl)96.79%no change 34. Danish (da)96.47%no change 35. Swedish (sv) 94.53%no change 36. British English (en_GB)94.31%no change 37. Indonesian (id)93.83%no change 38. Welsh (cy) 93.37%no change 39. Nepali (ne)90.40%no change 40. Italian (it) 86.00%no change 41. Basque (eu)85.88%no change 42. Bengali (bn) 83.43%no change 43. Persian (fa) 82.02%no change 44. Estonian (et) 81.69%no change Partially supported languages (between 50% and 80%). 45. Norwegian Nynorsk (nn) 77.99%no change 46. Croatian (hr) 73.18%no change 47. Tamil (ta) 73.17%no change 48. Hebrew (he)67.10%no change 49. Slovak (sk)65.90%no change 50. Arabic (ar)64.58%no change 51. Azerbaijani (az) 64.11%no change 52. Xhosa (xh) 62.93%no change 53. Thai (th) 62.81%no change 54. Malay (ms) 56.71%no change 55. Bosnian (bs) 51.96%no change 56. Mongolian (mn) 51.94%no change 57. Belarusian (be)50.84%no change Unsupported languages (less than 50%). 58. Telugu (te)42.26%no change 59. Slovenian (sl) 36.92%no change 60. Latvian (lv) 32.18%no change 61. Chinese (Hong Kong) (zh_HK)24.83%no change 62. Wallon (wa)22.60%no change 63. Irish Gaelic (ga) 18.07%no change 64. Icelandic (is) 17.72%no change 65. Afrikaans (af) 16.44%no change 66. Oriya (or) 16.17%no change 67. Malayalam (ml) 15.77%no change 68. Northern Sotho (nso) 15.32%no change 69. Serbian Jekavian ([EMAIL PROTECTED]) 12.37%no change 70. Amharic (am) 12.28%no change 71. Armenian (hy) 11.74%no change 72. Zulu (zu) 11.07%no change 73. Turkmen (tk)9.84%no change 74. Limburgish (li) 9.61%no change 75. Kinyarwanda (rw)8.83%no change 76. Marathi (mr)8.74%
Kbabel & 2 .po file sources
Hello AllI'm interested if Kbabel has a feature to open 2 same module's files with differentlanguages? The main reason is to have 2 well known languages sources to makea better translation. Can you tell me if it is possible ? :)Thank YouVladimer Sichinava-- E 'l naufragar m'è dolce in questo mare... ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Kbabel & 2 .po file sources
I would suggest that you also send your question to a KDE user list, simply because they may be better prepared and experienced to answer questions on KBabel. If you get an answer - please forward it here, so that the translators using KBabel will learn something new. Kind regards: al_shopov Vladimer Sichinava написа: Hello All I'm interested if Kbabel has a feature to open 2 same module's files with different languages? The main reason is to have 2 well known languages sources to make a better translation. Can you tell me if it is possible ? :) Thank You Vladimer Sichinava -- E 'l naufragar m'è dolce in questo mare... ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Kbabel & 2 .po file sources
--- Vladimer Sichinava <[EMAIL PROTECTED]> wrote: > I'm interested if Kbabel has a feature to open 2 same module's files > with different languages? The main reason is to have 2 well known > languages sources to make a better translation. How do you mean "open"? In separate windows? That is, of course, possible, but I suspect that you mean something else. Regards, Gora __ Yahoo! India Matrimony: Find your partner now. Go to http://yahoo.shaadi.com ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
