From: Sean E. <sea...@gm...> - 2004-11-29 04:09:01
|
Gaim is now frozen for 1.0.4. I doubt there are many string changes from 1.0.3, but translators should beware. We'll release our next stable version on Thursday. |
From: Kevin M S. <ke...@si...> - 2004-11-29 04:42:06
|
Sean Egan wrote: > Gaim is now frozen for 1.0.4. > > I doubt there are many string changes from 1.0.3, but translators should beware. > > We'll release our next stable version on Thursday. > Our ChangeLog in CVS implies we are going to 1.1.0. We should verify which version number we're actually releasing. Kevin |
From: Sean E. <sea...@gm...> - 2004-11-29 17:11:27
|
On Sun, 28 Nov 2004 23:41:02 -0500, Kevin M Stange <ke...@si...> wrote: > Our ChangeLog in CVS implies we are going to 1.1.0. We should verify > which version number we're actually releasing. so it does. The next release will be 1.1.0 -s. |
From: Danilo S. <ds...@gm...> - 2004-11-29 11:01:12
|
=D0=94=D0=B0=D0=BD=D0=B0=D1=81 =D1=83 5:08, Sean Egan =D0=BD=D0=B0=D0=BF=D0= =B8=D1=81=D0=B0: > Gaim is now frozen for 1.0.4. > > I doubt there are many string changes from 1.0.3, but translators should = beware. Updated Serbian translations are available on: http://kvota.net/~danilo/gaim-sr.po.gz http://kvota.net/~danilo/gaim-sr@Latn.po.gz > We'll release our next stable version on Thursday. I've came across some missing ngettext calls (most probably they have been sitting there for a while already): #: plugins/chkmail.c:136 #, c-format msgid "%s (%d new/%d total)" #: src/conversation.c:2203 #, c-format msgid "(+%d more)" #: src/gtkdialogs.c:759 #, c-format msgid "" "You are about to remove the contact containing %s and %d other buddies fro= m " "your buddy list. Do you want to continue?" #: src/protocols/yahoo/yahoo_filexfer.c:169 #, c-format msgid "" "Gaim cannot send files over Yahoo! that are bigger than %d megabytes (%d " "bytes)." The first is a bit tricky, since we'd need two ngettext calls on different variables, and this is commonly solved through a couple of steps:=20 char *new =3D g_strdup_printf(ngettext("%d new", "%d new", newmsgs), newmsg= s); char *total =3D g_strdup_printf(ngettext("%d total", "%d total", msgs), msg= s); /* Translators: second and third %s are equivalents of "%d new" and "%d total" in your language. */ char *result =3D g_strdup_printf(_("%s (%s/%s)"), text, new, total); The similar should be applied to last one (%d megabytes, %d bytes), except that I'd do it a bit differently: char *strbytes =3D g_strdup_printf(ngettext("%d bytes", "%d bytes", bytes),= bytes); /* Translators: %s is replaced with the equivalent of "%d bytes". */ char *result =3D g_strdup_printf( ngettext("Gaim cannot send files over Yahoo! that are bigger than %d mega= byte (%s).", "Gaim cannot send files over Yahoo! that are bigger than %d mega= bytes (%s).", megabytes), megabytes, strbytes); (The difference between these two cases is that here "%d megabytes" can affect other part of sentence as well.) Of course, appropriate freeing calls should be issues as well. Others are trivial. Cheers, Danilo |
From: Tim R. <om...@ho...> - 2004-11-29 23:41:31
|
Danilo Segan wrote: >#: src/protocols/yahoo/yahoo_filexfer.c:169 >#, c-format >msgid "" >"Gaim cannot send files over Yahoo! that are bigger than %d megabytes (%d " >"bytes)." > > > I didn't use ngettext here because the value will never be one. I've only used %d's at all in case it changes again, so I can change it without needing to retranslate, and I'm not sure what the exact value is yet actually, but it's at least 10 megabytes. But I seriously doubt it will ever be one again. So I don't *think* this needs to be changed, but I don't pretend to be an expert on i18n issues either. --Tim |
From: Sean E. <sea...@gm...> - 2004-11-30 00:13:33
|
On Mon, 29 Nov 2004 17:41:21 -0600, Tim Ringenbach <om...@ho...> wrote: > I didn't use ngettext here because the value will never be one. I've > only used %d's at all in case it changes again, so I can change it > without needing to retranslate, and I'm not sure what the exact value is > yet actually, but it's at least 10 megabytes. But I seriously doubt it > will ever be one again. Some languages have more than just "one" and "more than one." (a special case for "two" is the most common). I doubt that any language has a special case for 10, though. I'm not positive, but it probably doesn't hurt to be safe. |
From: Javier <jf...@co...> - 2004-11-29 14:47:20
|
On Sun, Nov 28, 2004 at 11:08:53PM -0500, Sean Egan wrote: > Gaim is now frozen for 1.0.4. >=20 > I doubt there are many string changes from 1.0.3, but translators should = beware. >=20 > We'll release our next stable version on Thursday. Attached is an update of the spanish translation. Best regards Javier |
From: Javier <jf...@co...> - 2004-12-01 20:50:05
Attachments:
gaim.es.po.gz
|
On Mon, Nov 29, 2004 at 03:45:37PM +0100, Javier Fernández-Sanguino Peña wrote: > On Sun, Nov 28, 2004 at 11:08:53PM -0500, Sean Egan wrote: > > Gaim is now frozen for 1.0.4. > > > > I doubt there are many string changes from 1.0.3, but translators should beware. > > > > We'll release our next stable version on Thursday. > > Attached is an update of the spanish translation. Attached *now* is the update. Sorry for the previous message. Regards Javier |
From: Ethan B. <ebl...@cs...> - 2004-11-30 00:23:39
|
Sean Egan spake unto us the following wisdom: > On Mon, 29 Nov 2004 17:41:21 -0600, Tim Ringenbach <om...@ho...> w= rote: > > I didn't use ngettext here because the value will never be one. I've > > only used %d's at all in case it changes again, so I can change it > > without needing to retranslate, and I'm not sure what the exact value is > > yet actually, but it's at least 10 megabytes. But I seriously doubt it > > will ever be one again. >=20 > Some languages have more than just "one" and "more than one." (a > special case for "two" is the most common). >=20 > I doubt that any language has a special case for 10, though. I'm not > positive, but it probably doesn't hurt to be safe. For what it's worth, Russian has different cases for 1, 2-4, and 5+. That doesn't make it to 10, but... Ethan --=20 The laws that forbid the carrying of arms are laws [that have no remedy for evils]. They disarm only those who are neither inclined nor determined to commit crimes. -- Cesare Beccaria, "On Crimes and Punishments", 1764 |
From: Tim R. <ma...@us...> - 2004-11-30 01:13:58
|
Ethan Blanton wrote: >Sean Egan spake unto us the following wisdom: > > >>Some languages have more than just "one" and "more than one." (a >>special case for "two" is the most common). >> >>I doubt that any language has a special case for 10, though. I'm not >>positive, but it probably doesn't hurt to be safe. >> >> > >For what it's worth, Russian has different cases for 1, 2-4, and 5+. >That doesn't make it to 10, but... > > Oops, I was thinking it was just for "one" and "more than one" for some reason. Really, I should figure out what exactly the limit is (it's if (0 && overlimit) error; in cvs oldstatus, if anyone [already running it] wants to find out for me) now. So, is this (and the others) something we should change now, or after the release when the freeze is thawed? --Tim |
From: Danilo S. <ds...@gm...> - 2004-11-30 12:06:45
|
=D0=94=D0=B0=D0=BD=D0=B0=D1=81 =D1=83 1:23, Ethan Blanton =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0: > Sean Egan spake unto us the following wisdom: >> On Mon, 29 Nov 2004 17:41:21 -0600, Tim Ringenbach <om...@ho...> = wrote: >> > I didn't use ngettext here because the value will never be one. I've >> > only used %d's at all in case it changes again, so I can change it >> > without needing to retranslate, and I'm not sure what the exact value = is >> > yet actually, but it's at least 10 megabytes. But I seriously doubt it >> > will ever be one again. >>=20 >> Some languages have more than just "one" and "more than one." (a >> special case for "two" is the most common). >>=20 >> I doubt that any language has a special case for 10, though. I'm not >> positive, but it probably doesn't hurt to be safe. > > For what it's worth, Russian has different cases for 1, 2-4, and 5+. > That doesn't make it to 10, but... To clear things up a bit, since I think Russian is exactly the same as Serbian here. Serbian has three forms: 1. numbers ending with 1, but not with 11 (eg. 1, 21, 101, 371, ...) 2. numbers ending with 2, 3, 4 but not with 12, 13, 14 (2, 34, 103) 3. all other numbers (5, 11, 14, 25, 257, ...) So you can grasp it easier, the simplest explanation here is that plural forms go with the word flow, taking into account that one and two/three/four are exceptions. We read something like "twenty and=20 one cat" (instead of English "twenty-one cats"), so "one" affects the following word, not entire number. "Eleven", otoh, is not special (since it's not "ten and one" :). Thus, if this value is going to change, it's easier for you to use ngettext here no matter whether it's static or not. Alternative would be to put the current value in a translators' comment which will appear in a PO file (just put the regular C comment in the line above this string; something like /* translators: %d is 10 */ would do =E2=80=94 otherwise, a guideline for them how to find out this value, even if it means looking into source code, would be appropriate). Cheers, Danilo |