You can subscribe to this list here.
2005 |
Jan
|
Feb
(1) |
Mar
(70) |
Apr
(43) |
May
(57) |
Jun
(84) |
Jul
(22) |
Aug
(20) |
Sep
(17) |
Oct
(8) |
Nov
(1) |
Dec
(9) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(12) |
Feb
(58) |
Mar
(34) |
Apr
(65) |
May
(16) |
Jun
(6) |
Jul
(4) |
Aug
|
Sep
|
Oct
(23) |
Nov
(18) |
Dec
|
2007 |
Jan
(16) |
Feb
(6) |
Mar
(2) |
Apr
(22) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Bjoern V. <bj...@cs...> - 2006-04-24 10:43:45
|
Hello translators! I found some i18n strings in Gaim which I don't like for different=20 reasons. Of course I can write a patch which changes these strings. But=20 I think it's better to change the strings after a voting from other=20 translators. Here are the strings which I don't like: #: ../src/gtkdialogs.c:100 msgid "hacker and designated driver [lazy bum]" msgstr "" I think it's abusive to call the retired developer Syd Logan a "lazy=20 bum". I think this not a humorous designation. The direct German=20 translation "Hacker und selbsternannter F=FChrer [fauler Arsch]" sounds=20 very bad. So I refuse to translate it directly anyway. Does anyone know, what Syd Logan did for the Gaim project? #: ../plugins/psychic.c:60 msgid "You feel a disturbance in the force..." msgstr "" This message is not bad language but it does not describe what's going=20 on. I asked the developer (Christopher O'Brien) about what his string=20 mean. He told me, that it means: "If a buddy begins to type a message to = you a conversation window appears (with this message)". Unfortunately he = does not want to change his string. So I need your votes. #: ../src/gtkaccount.c:1297 msgid "you can see the butterflies mating" msgstr "" This may be a funny message. But also it does say nothing. It has=20 something to do with the proxy port option in the account dialogs. But I = don't know the exact meaning. Greetings, Bj=F6rn |
From: Shalom C. <scr...@gm...> - 2006-04-24 09:33:27
|
This is purely a point of pride, but I wanted to know - who do I talk to about getting credit for the translation? It's still being credited to Pavel... </hurt ego> |
From: Ethan B. <ebl...@cs...> - 2006-04-18 14:05:10
|
Shalom Craimer spake unto us the following wisdom: > I think I might have gotten a mite confused - we're no longer in a string > freeze? Will there be one before release? Correct, we opened strings up again after releasing beta 3. The freeze was inteded to hold until 2.0.0 was released, but it was premature. There will be another freeze for 2.0.0, but hopefully it won't contain a lot of changes from the 2.0.0b3 freeze. 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: Shalom C. <scr...@gm...> - 2006-04-18 13:33:40
|
I think I might have gotten a mite confused - we're no longer in a string freeze? Will there be one before release? -=3D Shalom |
From: Bjoern V. <bj...@cs...> - 2006-04-11 16:15:11
|
Hello Richard! Richard Laager <rl...@wi...> wrote: > I reworked this a little bit. I didn't know where to pull those > variables from. If you'd like them, please provide a patch. Now the error dialog in the attached patch has everything what we want (a title, a generic message and a detailed message with an error code). Greetings, Bj=F6rn |
From: Richard L. <rl...@wi...> - 2006-04-10 23:45:22
|
On Tue, 2006-04-11 at 00:06 +0200, Bjoern Voigt wrote: > Something like: "Could not query \"%s\" (error code: %d). You either > entered an invalid Jabber user directory or the directory could not be > contacted in the moment." I reworked this a little bit. I didn't know where to pull those variables from. If you'd like them, please provide a patch. Thanks, Richard |
From: Richard L. <rl...@wi...> - 2006-04-10 23:42:46
|
On Mon, 2006-04-10 at 23:31 +0200, Bjoern Voigt wrote: > Ok, the patch is attached (file jabber-user-dir-comments2-i18n.patch). Committed. Thanks. Richard |
From: Bjoern V. <bj...@cs...> - 2006-04-10 21:31:20
|
Richard Laager <rl...@wi...> wrote: > > What happens, if tmp is NULL? >=20 > Some systems will display "Server Instructions: (null)". Some systems > will crash. Yes, this should be checked. >=20 > Can you create a patch that addresses these concerns. If so, I'll apply > it unless someone objects. Ok, the patch is attached (file jabber-user-dir-comments2-i18n.patch). Greetings, Bj=F6rn |
From: Richard L. <rl...@wi...> - 2006-04-10 20:57:47
|
On Mon, 2006-04-10 at 22:44 +0200, Bjoern Voigt wrote: > Richard Laager <rl...@wi...> wrote: > > > We could take advantage of the fact that gettext doesn't honor #if 0... > > > > #if 0 > > /* This is for gettext only. */ > > > static const char * jabber_user_dir_comments [] = { > > > /* current comment from Jabber User Directory users.jabber.org */ > > > N_("Find a contact by entering the search criteria in the given fields. " > > > "Note: Each field supports wild card searches (%)"), > > > NULL > > > }; > > #endif > > Ok. This is clever. > > I forget to write about another problem in the existing code: > > if((instnode = xmlnode_get_child(query, "instructions"))) > { > char *tmp = xmlnode_get_data(instnode); > instructions = g_strdup_printf(_("Server Instructions: %s"), tmp); > g_free(tmp); > } > > What happens, if tmp is NULL? Some systems will display "Server Instructions: (null)". Some systems will crash. Yes, this should be checked. Can you create a patch that addresses these concerns. If so, I'll apply it unless someone objects. Richard |
From: Bjoern V. <bj...@cs...> - 2006-04-10 20:45:14
|
Richard Laager <rl...@wi...> wrote: > We could take advantage of the fact that gettext doesn't honor #if 0... >=20 > #if 0 > /* This is for gettext only. */ > > static const char * jabber_user_dir_comments [] =3D { > > =09/* current comment from Jabber User Directory users.jabber.org */ > > =09N_("Find a contact by entering the search criteria in the given fiel= ds. " > > =09 "Note: Each field supports wild card searches (%)"), > > =09NULL > > }; > #endif Ok. This is clever.=20 I forget to write about another problem in the existing code: if((instnode =3D xmlnode_get_child(query, "instructions"))) { char *tmp =3D xmlnode_get_data(instnode); instructions =3D g_strdup_printf(_("Server Instru= ctions: %s"), tmp); g_free(tmp); } What happens, if tmp is NULL? I looked into xmlnode_get_data(). This function can return NULL. And probably a modified JUD can return such an XML-node without data. I think, the code is more safe with an test for tmp!=3DNULL. The problem exists both in the existing and in the patched code. Greetings, Bj=F6rn |
From: Richard L. <rl...@wi...> - 2006-04-10 20:08:37
|
On Mon, 2006-04-10 at 22:03 +0200, Bjoern Voigt wrote: > I used the for-loop because otherwise it's not possible to print the > debugging message, if a new JUD search comment comes. With gettext alone > it's not possible to see I don't like the debugging message, and neither does Etan. We could take advantage of the fact that gettext doesn't honor #if 0... #if 0 /* This is for gettext only. */ > static const char * jabber_user_dir_comments [] = { > /* current comment from Jabber User Directory users.jabber.org */ > N_("Find a contact by entering the search criteria in the given fields. " > "Note: Each field supports wild card searches (%)"), > NULL > }; #endif Richard |
From: Bjoern V. <bj...@cs...> - 2006-04-10 19:37:53
|
Hello Richard! I wrote some code which translates known Jabber User Directory (JUD) search comments. Currently there is only one comment in the list (the comment from users.jabber.org). users.jabber.org is the standard JUD server for Gaim and it is the most important JUD in Jabber networks. (I didn't find any other working public JUD server). Could you please commit my patch? I tested it and didn't found problems with it. Greetings, Bj=F6rn |
From: Duarte H. <dua...@gm...> - 2006-04-09 23:39:38
|
SGksIEknbSB0aGUgcHRfUFQgdHJhbnNsYXRvciwgYW5kIHdhcyBhd2F5IGxhc3Qgd2VlaywgdGhh dCdzIHdoeSBJCmhhZG4ndCByZXNwb25kZWQuCgpJIHBvc3RlZCBteSB0aG91Z2h0cyBvbiB0aGUg dHJhbnNsYXRpb25zIHRyYWNrZXIgbm93LgoKQ2hlZXJzLApEdWFydGUgSGVucmlxdWVzCg== |
From: <mau...@gm...> - 2006-04-07 10:57:56
|
SSd2ZSB0cmFuc2xhdGVkIHRoaXMgYXMgIk5lZ290aWF0aW5nIiAoIk5lZ29jaWFuZG8iKSwgYnV0 IHRoaXMgaXMgYW4KYWx0ZXJuYXRpdmUgSSB3aWxsIGNvbnNpZGVyLiBJIHdpbGwgYXNrIHNvbWUg dXNlcnMgdG8gc2VlIGlmIGl0IG1ha2VzCnRoaW5ncyBjbGVhcmVyLiBUaGFua3MuCgotLQpNYXVy w61jaW8KCk9uIDQvNy8wNiwgQ2x5dGllIFNpZGRhbGwgPGNseXRpZUByaXZlcmxhbmQubmV0LmF1 PiB3cm90ZToKPgo+IEkndmUgZm91bmQgdGhlIHNhZmVzdCB0aGluZyB0byBkbywgd2hlbiB0cmFu c2xhdGluZyB0aGlzIHBocmFzZSwgaXMKPiB0byB1c2Ugd2hhdGV2ZXIgbWVhbnMgInNoYWtpbmcg aGFuZHMiIGluIG5vcm1hbCBkYWlseSB1c2UuIChJbiBteQo+IGxhbmd1YWdlLCBpdCBsaXRlcmFs bHkgbWVhbnMgImNhdGNoIHRoZSBoYW5kIjogYuG6r3QgdGF5LikKPgo+IFdvdWxkIHRoaXMgd29y ayBmb3IgeW91ciBsYW5ndWFnZT8gSXQncyBhIHJlYXNvbmFibHkgdW5pdmVyc2FsCj4gY29uY2Vw dDogZXZlbiBpZiB5b3UgZG9uJ3QgYWN0dWFsbHkgInNoYWtlIiB0aGUgaGFuZHMsIHdlIGFsbCBj bGFzcAo+IGhhbmRzIGluIGZyaWVuZHNoaXAgaW4gb25lIHdheSBvciBhbm90aGVyLgo= |
From: Clytie S. <cl...@ri...> - 2006-04-07 05:37:47
|
On 07/04/2006, at 10:12 AM, Maur=C3=ADcio Collares wrote: > Bacalhauzada makes no sense in Brazilian Portuguese either, but after > I got a few complaints about this in an earlier version of Gaim, I > asked a friend who said this is some sort of slang in pt_PT. I don't > know if this is true. I've found the safest thing to do, when translating this phrase, is =20 to use whatever means "shaking hands" in normal daily use. (In my =20 language, it literally means "catch the hand": b=E1=BA=AFt tay.) Would this work for your language? It's a reasonably universal =20 concept: even if you don't actually "shake" the hands, we all clasp =20 hands in friendship in one way or another. from Clytie (vi-VN, Vietnamese free-software translation team / nh=C3=B3m = =20 Vi=E1=BB=87t h=C3=B3a ph=E1=BA=A7n m=E1=BB=81m t=E1=BB=B1 do) http://groups-beta.google.com/group/vi-VN |
From: <mau...@gm...> - 2006-04-07 00:42:16
|
Hopefully, this was not present on 1.5.0, pt_BR (please warn me if I'm wrong). It *was* present on an earlier version, due to a confusion related to a patch I sent during the freeze (it was not checked in by accident). Bacalhauzada makes no sense in Brazilian Portuguese either, but after I got a few complaints about this in an earlier version of Gaim, I asked a friend who said this is some sort of slang in pt_PT. I don't know if this is true. -- Maur=EDcio On 4/6/06, Stephen Eilert <spe...@gm...> wrote: > As I recall, that was also present on 1.5.0, pt_BR. The translation must = be > handled differently from pt_PT as well. |
From: Stephen E. <spe...@gm...> - 2006-04-06 16:08:58
|
QXMgSSByZWNhbGwsIHRoYXQgd2FzIGFsc28gcHJlc2VudCBvbiAxLjUuMCwgcHRfQlIuIFRoZSB0 cmFuc2xhdGlvbiBtdXN0IGJlCmhhbmRsZWQgZGlmZmVyZW50bHkgZnJvbSBwdF9QVCBhcyB3ZWxs LgoKClN0ZXBoZW4KCk9uIDQvNi8wNiwgTHVrZSBTY2hpZXJlciA8bHNjaGllcmVAdXNlcnMuc2Yu bmV0PiB3cm90ZToKPgo+IC0tLS0tIEZvcndhcmRlZCBtZXNzYWdlIGZyb20gIlNvdXJjZUZvcmdl Lm5ldCIgPG5vcmVwbHlAc291cmNlZm9yZ2UubmV0Pgo+IC0tLS0tCj4KPiBEYXRlOiBXZWQsIDA1 IEFwciAyMDA2IDE4OjUwOjM1IC0wNzAwCj4gRnJvbTogIlNvdXJjZUZvcmdlLm5ldCIgPG5vcmVw bHlAc291cmNlZm9yZ2UubmV0Pgo+IFRvOiBub3JlcGx5QHNvdXJjZWZvcmdlLm5ldAo+IFN1Ympl Y3Q6IFtHYWltLXRyYW5zbGF0aW9uc10gWyBnYWltLVRyYW5zbGF0aW9ucy0xNDY1Mzk5IF0gUHRf UFQKPiB0cmFuc2xhdGlvbiBvZiAiSGFuZHNoYWtpbmciCj4KPiBUcmFuc2xhdGlvbnMgaXRlbSAj MTQ2NTM5OSwgd2FzIG9wZW5lZCBhdCAyMDA2LTA0LTA1IDE4OjA2Cj4gTWVzc2FnZSBnZW5lcmF0 ZWQgZm9yIGNoYW5nZSAoQ29tbWVudCBhZGRlZCkgbWFkZSBieSBybGFhZ2VyCj4gWW91IGNhbiBy ZXNwb25kIGJ5IHZpc2l0aW5nOgo+Cj4gaHR0cHM6Ly9zb3VyY2Vmb3JnZS5uZXQvdHJhY2tlci8/ ZnVuYz1kZXRhaWwmYXRpZD03MTM5MjImYWlkPTE0NjUzOTkmZ3JvdXBfaWQ9MjM1Cj4KPiBQbGVh c2Ugbm90ZSB0aGF0IHRoaXMgbWVzc2FnZSB3aWxsIGNvbnRhaW4gYSBmdWxsIGNvcHkgb2YgdGhl IGNvbW1lbnQKPiB0aHJlYWQsCj4gaW5jbHVkaW5nIHRoZSBpbml0aWFsIGlzc3VlIHN1Ym1pc3Np b24sIGZvciB0aGlzIHJlcXVlc3QsCj4gbm90IGp1c3QgdGhlIGxhdGVzdCB1cGRhdGUuCj4gPkNh dGVnb3J5OiBOb25lCj4gR3JvdXA6IE5vbmUKPiBTdGF0dXM6IE9wZW4KPiBQcmlvcml0eTogNQo+ IFN1Ym1pdHRlZCBCeTogV2F0ZXJTZXZlblViICh3YXRlcnNldmVudWIpCj4gPkFzc2lnbmVkIHRv OiBMdWtlIFNjaGllcmVyIChsc2NoaWVyZSkKPiBTdW1tYXJ5OiBQdF9QVCB0cmFuc2xhdGlvbiBv ZiAiSGFuZHNoYWtpbmciCj4KPiBJbml0aWFsIENvbW1lbnQ6Cj4gQ3VycmVudCB0cmFuc2xhdGlv biBvZiAiSGFuZHNoYWtpbmciIGluIFBvcnR1Z3Vlc2UKPiAoUG9ydHVnYWwsIEludGVybmF0aW9u YWwpIGlzICJCYWNhbGhhdXphZGEiLiBUaGF0Cj4gZG9lc24ndCBtYWtlIHNlbnNlLiBQbGVhc2Ug dHJhbnNsYXRlIHRvIHNvbWV0aGluZyBsaWtlCj4gIkEgbmVnb2NpYXIiLgo+Cj4gRmlsZSBwdC5w bzoKPgo+ICM6IC4uL3NyYy9wcm90b2NvbHMvbXNuL3Nlc3Npb24uYzozNTAKPiAuLi9zcmMvcHJv dG9jb2xzL21zbi9zZXNzaW9uLmM6MzUyCj4gbXNnaWQgIkhhbmRzaGFraW5nIgo+IG1zZ3N0ciAi QmFjYWxoYXV6YWRhIiBzaG91bGQgYmUKPgo+IG1zZ3N0ciAiQSBuZWdvY2lhciIKPgo+IFRoYW5r IHlvdS4KPgo+IFJ1aSBBei4KPiBhc3Ryb25vbXlAbWFpbC5wdAo+Cj4gLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQo+ Cj4gPkNvbW1lbnQgQnk6IFJpY2hhcmQgTGFhZ2VyIChybGFhZ2VyKQo+IERhdGU6IDIwMDYtMDQt MDUgMjA6NTAKPgo+IE1lc3NhZ2U6Cj4gTG9nZ2VkIEluOiBZRVMKPiB1c2VyX2lkPTE1NjQ4Nwo+ Cj4gSW4gZ2VuZXJhbCwgd2UgYWNjZXB0IHdoYXRldmVyIHRoZSB0cmFuc2xhdG9ycyBwcm92aWRl IHVzLgo+IEhhdmUgeW91IG1lbnRpb25lZCB0aGlzIHRvIHRoZSB0cmFuc2xhdG9yKHMpIGZvciB0 aGF0Cj4gbGFuZ3VhZ2U/IFRoZXkncmUgbGlzdGVkIGluIHRoZSBhYm91dCBib3ggKEhlbHAgLT4g QWJvdXQpLgo+Cj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQo+Cj4gWW91IGNhbiByZXNwb25kIGJ5IHZpc2l0aW5n Ogo+Cj4gaHR0cHM6Ly9zb3VyY2Vmb3JnZS5uZXQvdHJhY2tlci8/ZnVuYz1kZXRhaWwmYXRpZD03 MTM5MjImYWlkPTE0NjUzOTkmZ3JvdXBfaWQ9MjM1Cj4KPgo+IC0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KPiBUaGlzIFNGLk5ldCBlbWFpbCBp cyBzcG9uc29yZWQgYnkgeFBNTCwgYSBncm91bmRicmVha2luZyBzY3JpcHRpbmcKPiBsYW5ndWFn ZQo+IHRoYXQgZXh0ZW5kcyBhcHBsaWNhdGlvbnMgaW50byB3ZWIgYW5kIG1vYmlsZSBtZWRpYS4g QXR0ZW5kIHRoZSBsaXZlCj4gd2ViY2FzdAo+IGFuZCBqb2luIHRoZSBwcmltZSBkZXZlbG9wZXIg Z3JvdXAgYnJlYWtpbmcgaW50byB0aGlzIG5ldyBjb2RpbmcKPiB0ZXJyaXRvcnkhCj4gaHR0cDov L3NlbC5hcy11cy5mYWxrYWcubmV0L3NlbD9jbWQ9bG5rJmtpZD0xMTA5NDQmYmlkPTI0MTcyMCZk YXQ9MTIxNjQyCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X18KPiBHYWltLXRyYW5zbGF0aW9ucyBtYWlsaW5nIGxpc3QKPiBHYWltLXRyYW5zbGF0aW9uc0Bs aXN0cy5zb3VyY2Vmb3JnZS5uZXQKPiBodHRwczovL2xpc3RzLnNvdXJjZWZvcmdlLm5ldC9saXN0 cy9saXN0aW5mby9nYWltLXRyYW5zbGF0aW9ucwo+Cj4KPiAtLS0tLSBFbmQgZm9yd2FyZGVkIG1l c3NhZ2UgLS0tLS0KPgo+Cj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLQo+IFRoaXMgU0YuTmV0IGVtYWlsIGlzIHNwb25zb3JlZCBieSB4UE1M LCBhIGdyb3VuZGJyZWFraW5nIHNjcmlwdGluZwo+IGxhbmd1YWdlCj4gdGhhdCBleHRlbmRzIGFw cGxpY2F0aW9ucyBpbnRvIHdlYiBhbmQgbW9iaWxlIG1lZGlhLiBBdHRlbmQgdGhlIGxpdmUKPiB3 ZWJjYXN0Cj4gYW5kIGpvaW4gdGhlIHByaW1lIGRldmVsb3BlciBncm91cCBicmVha2luZyBpbnRv IHRoaXMgbmV3IGNvZGluZwo+IHRlcnJpdG9yeSEKPiBodHRwOi8vc2VsLmFzLXVzLmZhbGthZy5u ZXQvc2VsP2NtZD1sbmsma2lkPTExMDk0NCZiaWQ9MjQxNzIwJmRhdD0xMjE2NDIKPiBfX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IEdhaW0taTE4biBtYWls aW5nIGxpc3QKPiBHYWltLWkxOG5AbGlzdHMuc291cmNlZm9yZ2UubmV0Cj4gaHR0cHM6Ly9saXN0 cy5zb3VyY2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vZ2FpbS1pMThuCj4K |
From: Luke S. <lsc...@us...> - 2006-04-06 14:53:28
|
----- Forwarded message from "SourceForge.net" <no...@so...> ----- Date: Wed, 05 Apr 2006 18:50:35 -0700 From: "SourceForge.net" <no...@so...> To: no...@so... Subject: [Gaim-translations] [ gaim-Translations-1465399 ] Pt_PT translation of "Handshaking" Translations item #1465399, was opened at 2006-04-05 18:06 Message generated for change (Comment added) made by rlaager You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=713922&aid=1465399&group_id=235 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: None Group: None Status: Open Priority: 5 Submitted By: WaterSevenUb (watersevenub) >Assigned to: Luke Schierer (lschiere) Summary: Pt_PT translation of "Handshaking" Initial Comment: Current translation of "Handshaking" in Portuguese (Portugal, International) is "Bacalhauzada". That doesn't make sense. Please translate to something like "A negociar". File pt.po: #: ../src/protocols/msn/session.c:350 ../src/protocols/msn/session.c:352 msgid "Handshaking" msgstr "Bacalhauzada" should be msgstr "A negociar" Thank you. Rui Az. ast...@ma... ---------------------------------------------------------------------- >Comment By: Richard Laager (rlaager) Date: 2006-04-05 20:50 Message: Logged In: YES user_id=156487 In general, we accept whatever the translators provide us. Have you mentioned this to the translator(s) for that language? They're listed in the about box (Help -> About). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=713922&aid=1465399&group_id=235 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Gaim-translations mailing list Gai...@li... https://lists.sourceforge.net/lists/listinfo/gaim-translations ----- End forwarded message ----- |
From: Bjoern V. <bj...@cs...> - 2006-04-05 10:46:15
|
Hello! I wanted to write some code, which tries to translate the user search comment from users.jabber.org. Nearly all Jabber services seam to use users.jabber.org as a user directory. Unfortunately Gaim does not find the JUD (Jabber User Directory) users.jabber.org at all since some days. So I can not test my patch any more. jabber: Sending (ssl): <iq type='get' id='gaim44faa493' to='users.jabber.org'><query xmlns='jabber:iq:search'/></iq> jabber: Recv (ssl)(236): <iq from='users.jabber.org' to='MY-...@ja.../Gaim' type='error' id='gaim44faa493'><query xmlns='jabber:iq:search'/><error code='404' type='cancel'><remote-server-not-found xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq> Is this a Gaim bug or is the JUD at users.jabber.org really down? "ping users.jabber.org" works. Greetings, Björn |
From: Etan R. <de...@ed...> - 2006-03-30 03:45:39
|
On Tue, 28 Mar 2006, Bjoern Voigt wrote: <snip> > Also we can look for a list of "standard" Jabber server comments and > translate them. Translating server messages in gaim sounds like a really bad idea to me=20 (especially in light of a recent thread which had complaints about the=20 amount of translatable strings in gaim =3D). > Can someone give me a good list of Jabber User Directories? (I only know > users.jabber.org). It's not much work to query all this servers for > their User search comments using Gaim. I believe there are working JUDs in C, python, and perl. You should be=20 able to find out about them on jabberstudio.org (though that site was=20 better back before the break in), and by using google. <snip> > Greetings, Bj=F6rn =09-Etan |
From: Vincent v. A. <adr...@gn...> - 2006-03-29 10:03:18
|
Op Tue, 28 Mar 2006 23:02:52 +0200 (CEST) schreef Bjoern Voigt <bj...@cs...>: > Hello! >=20 <snip> >=20 > Can someone give me a good list of Jabber User Directories? (I only > know users.jabber.org). It's not much work to query all this > servers for their User search comments using Gaim.=20 >=20 <snip> >=20 > Greetings, Bj=F6rn Hi again, I don't think many JUDs are in use. I searched around a bit, and all services I found point to jabber.org for the JUD. That would make sense too. Having a central JUD instead of having dozens of 'em makes finding someone a lot easier. Maybe gmail has its own JUD, but I didn't find it. Kind regards, Vincent van Adrighem |
From: Bjoern V. <bj...@cs...> - 2006-03-28 21:03:34
|
Hello! Vincent van Adrighem <adr...@gn...> wrote: > This simple translation problem is slowly turning into a fundamental > problem, eh? Hmmm, just thinking out loud here: Would it be possible > to pipe the server message through gettext? We could then, for > example, translate the three most used messages. And when they change, > they will be English again, but the user might be able to do something > with the info. that, in combination with some hiding, would be a > (albeit very hackish) workable situation, right? I repeat, just > thinking out loud. Yes, this is possible. I tried to explain it in my first mail in this thread: | (4) write a dummy translation string for this message |=20 | (something like=20 | | char *server_comment_dummy=3DN_("Find a contact [...] wild " | "card searches (%)"); | if(instructions =3D=3D=3D server_comment_dummy)=20 | instructions2=3D_(server_comment_dummy); | else | instructions2=3Dinstructions; | | of course this is pseudo code, not C) | | This only makes sense, if the server search comment is more or less | a standard comment. Also we can look for a list of "standard" Jabber server comments and translate them. Can someone give me a good list of Jabber User Directories? (I only know users.jabber.org). It's not much work to query all this servers for their User search comments using Gaim.=20 Gettext automatically selects the original language (in most projects this is English) if it doesn't find the translation of the string in the catalog. Gettext needs to do this because often translations are more or less incomplete (look at http://gaim.sf.net/i18n for example) and programs normally should not crash on an incomplete string. (A little i18n story: I recently visited a bug tracking system with a browser with German language preference. The web-site crashed with a Java exception. The web-master told me, that a missing translation caused the Java exception. gettext() silently ignores missing translations, Java's standard localization method throws an exception which _can_ crash the whole application if not handled.) So in German locale gettext("Hello World") is "Hallo Welt" if the German translator has translated "Hello World". Otherwise gettext("Hello World") returns "Hello World". Greetings, Bj=F6rn |
From: Vincent v. A. <adr...@gn...> - 2006-03-28 19:06:40
|
Op Tue, 28 Mar 2006 13:29:13 -0500 (EST) schreef Etan Reisner <de...@ed...>: > On Mon, 27 Mar 2006, Vincent van Adrighem wrote: >=20 > <snip> >=20 > > Good point. The situation of hardcoded fields and custom messages > > is bogus anyway. We can remove/hide it safely and insert our own > > message, if needed. We could insert a "click here for server info" > > kind of widget. Perhaps that triangle flip open widget at the > > bottom of the window, with this text in it, or maybe a tooltip of > > somesort....I don't know, just thinking aloud. But a casual user > > should not need it anyway. The "use % for wildcard" text should > > stay though. Many will otherwise try to use > > * as a wildcard. >=20 > You can't just remove server messages, they do have meaning or they=20 > wouldn't be there. Hiding the message is doable, though not really=20 > optimal. The problem here is with the message not being translated. It's of no use anyway to most people in non-english countries, so we might as well hide it. Imagine the message being in Japanese. Or worse, in a language you sortof understand, but not quite. You'd want it gone, right? The idea is to hide information that's more confusing than informative, but keep it there in case the user wants to know more. > How exactly do you propose to keep part of server information? > Keeping in mind that different servers have different instructions > and different semantics. Some servers clearly use % as a wildcard, > others might use * or & or anything else you can imagine. I'm sorry about the fuzzyness of my reply. I didn't mean keeping part of the message. I meant replacing the server message with a fixed message explaning the "% is a wildcard" thing. But as you explain in your text here, that would be no solution. Maybe a "% or * might be a wildcard" line... > As Nathan pointed out, servers need to send information, the > information needs to come from the server, this isn't going to > stop, it's only going to increase as more jabber servers exist and > more features exist. And the information is going to vary between > different servers and possibly even between different versions of > the same server. Different versions of gibberish don't make no useful message. That's what I was trying to make clear. We have a problem where people can't read English text. That is why we translate in the first place. The ideal solution would be to get into the development process of all jabber server software and translate it there. Then we could use the xml:lang stuff nathan writes about. But that's only a long term solution. Not a 2006 solution. This simple translation problem is slowly turning into a fundamental problem, eh? Hmmm, just thinking out loud here: Would it be possible to pipe the server message through gettext? We could then, for example, translate the three most used messages. And when they change, they will be English again, but the user might be able to do something with the info. that, in combination with some hiding, would be a (albeit very hackish) workable situation, right? I repeat, just thinking out loud. Kind regards, Vincent van Adrighem |
From: Etan R. <de...@ed...> - 2006-03-28 18:29:51
|
On Mon, 27 Mar 2006, Vincent van Adrighem wrote: <snip> > Good point. The situation of hardcoded fields and custom messages is > bogus anyway. We can remove/hide it safely and insert our own > message, if needed. We could insert a "click here for server info" > kind of widget. Perhaps that triangle flip open widget at the bottom > of the window, with this text in it, or maybe a tooltip of > somesort....I don't know, just thinking aloud. But a casual user > should not need it anyway. The "use % for wildcard" text should stay > though. Many will otherwise try to use > * as a wildcard. You can't just remove server messages, they do have meaning or they wouldn't be there. Hiding the message is doable, though not really optimal. How exactly do you propose to keep part of server information? Keeping in mind that different servers have different instructions and different semantics. Some servers clearly use % as a wildcard, others might use * or & or anything else you can imagine. As Nathan pointed out, servers need to send information, the information needs to come from the server, this isn't going to stop, it's only going to increase as more jabber servers exist and more features exist. And the information is going to vary between different servers and possibly even between different versions of the same server. > Kind regards, > Vincent van Adrighem -Etan |
From: Nathan W. <fac...@fa...> - 2006-03-27 13:47:21
|
Very few Jabber implementations use the hardcoded field names anymore. Most use the x:data implementation, which means that the instructions, and all field names and field types come from the server. There is a provision in some parts of XMPP/Jabber for the server to send multiple things with an xml:lang attribute, so we could start paying attention to that. Apart from that, it's pretty damn difficult to translate sanely. User search, chat room configuration, and a whole slew of other things are done this way, and it is the preferred way of getting information from the user. The list will only grow. Sorry to be the bearer of bad news. -Nathan |