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: Vincent v. A. <adr...@gn...> - 2006-03-27 11:31:36
|
Op Mon, 27 Mar 2006 13:18:15 +0200 (CEST) schreef Bjoern Voigt <bj...@cs...>: > Hello all! >=20 > > > (2) explain the user that this is a Jabber server comment > > >=20 > > > (something like: _("Jabber server comment: ") + > > > instructions) > >=20 > > (2) is superior to (1). I've just committed something like that. > > We'll see how people like that. >=20 > Ok, I tested my committed change and think, it's ok. >=20 While it is better than (1), it's not ideal. > > > (3) don't use the server comment, only use Gaim's own comment > >=20 > > I don't like this; it throws away useful data. >=20 As Bjoern explains below, the information might not be that useful. > My question to Jabber experts is: How useful are these search > comments for Gaim? >=20 > The example comment from users.jabber.org was: >=20 > | Find a contact by entering the search criteria in the given > | fields. Note: Each field supports wild card searches (%) >=20 > The search fields (First Name, Last Name, Nickname and E-Mail) are > hard-coded in Gaim (see src/protocols/jabber/buddy.c). It's > relatively clear that the user has to fill one or more of this > fields to search. >=20 > The only interesting information is, that wild card searches (with > "%") are possible. =20 >=20 > There is not much documentation about JUD (Jabber User Directory). >=20 > Look at this README file from > http://modzer0.cs.uaf.edu/wiki/index.php/Jabber/JUD: <snipped pasted text> >=20 > If I read the README right the search instruction section is only > needed for customized searches (here with age and colour).=20 >=20 > What's with the following situation: An example Jabber User > Directory allows a search for additional fields like age and says > this in it's search comment field. Then the user wonders about the > missing field "Age:". >=20 > Greetings, Bj=F6rn 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. Kind regards, Vincent van Adrighem |
From: Bjoern V. <bj...@cs...> - 2006-03-27 11:18:50
|
Hello all! > > (2) explain the user that this is a Jabber server comment > >=20 > > (something like: _("Jabber server comment: ") + instructions) >=20 > (2) is superior to (1). I've just committed something like that. We'll > see how people like that. Ok, I tested my committed change and think, it's ok. > > (3) don't use the server comment, only use Gaim's own comment >=20 > I don't like this; it throws away useful data. My question to Jabber experts is: How useful are these search comments for Gaim? The example comment from users.jabber.org was: | Find a contact by entering the search criteria in the given | fields. Note: Each field supports wild card searches (%) The search fields (First Name, Last Name, Nickname and E-Mail) are hard-coded in Gaim (see src/protocols/jabber/buddy.c). It's relatively clear that the user has to fill one or more of this fields to search. The only interesting information is, that wild card searches (with "%") are possible. =20 There is not much documentation about JUD (Jabber User Directory). Look at this README file from http://modzer0.cs.uaf.edu/wiki/index.php/Jabber/JUD: | JUD - Jabber User Directory | --------------------------- | http://jud.jabberstudio.org/ |=20 | This is the ANSI C implementation of a simple JUD (Jabber User Directory= ). | There are other implementations that handle a large user base better, | see the website above for links. |=20 | Unpack it into your jabberd 1.4.x server folder, and type 'make' to | build the jud.so. |=20 | Then add the following to your jabber.xml configuration file: |=20 | <service id=3D"jud"> | <host>jud.localhost</host> | <load><jud>./jud/jud.so</jud></load> | <jud xmlns=3D"jabber:config:jud"> | <vCard> | <FN>Local User Directory</FN> | <DESC>This service provides a simple user directory service.</DESC= > | <URL>http://jud.jabberstudio.org/</URL> | </vCard> | =20 | <!-- Enable full user listing retrieval by browsing to | 'jud.localhost/users' with your Jabber client. | Definitely not suitable for large user bases. | <userbrowse/> --> |=20 | <!-- You only need this section if you want customized | instructions or database fields | <register> | <instructions>Fill in the fields to register</instructions> | <name/> | <age/> | <colour/> | </register> --> |=20 | <!-- You only need this section if you want to customize | the search dialog | <search> | <instructions>Enter values to search</instructions> | <age/> | <colour/> | </search> --> |=20 | </jud> | </service> If I read the README right the search instruction section is only needed for customized searches (here with age and colour).=20 What's with the following situation: An example Jabber User Directory allows a search for additional fields like age and says this in it's search comment field. Then the user wonders about the missing field "Age:". Greetings, Bj=F6rn |
From: Etan R. <de...@ed...> - 2006-03-26 18:57:20
|
On Sun, 26 Mar 2006, Richard Laager wrote: > On Sun, 2006-03-26 at 14:21 +0200, Bjoern Voigt wrote: >> How should we deal with the original English text message? >> >> I see some possible solutions: >> >> (1) leave it as is >> >> (2) explain the user that this is a Jabber server comment >> >> (something like: _("Jabber server comment: ") + instructions) > > (2) is superior to (1). I've just committed something like that. We'll > see how people like that. > >> (3) don't use the server comment, only use Gaim's own comment > > I don't like this; it throws away useful data. > >> (4) write a dummy translation string for this message > >> This only makes sense, if the server search comment is more or less >> a standard comment. > > I think this might be okay for a couple really popular default strings, > but it's also something that could quickly get out of control. Also, > where do you draw the line? > >> (5) inform the Jabber maintainers about the problem > > This would probably require some sort of language negotiation between > the client and the server and the server would need to have lots of > strings configured. Unless someone who knows more about Jabber than me > thinks it's futile, I'd say it's worth mentioning, but I doubt it'll get > us anywhere, at least in the short term. > > Richard This "problem" of server messages not being translated into the correct localized language, and what to do about that came up on one of the jabber mailing lists somewhat recently. I don't recall if any sort of outcome was reached though. If I find time I'll go look for it, other people should of course feel free to find it before I get a chance. As to (5) there are a large number of jabber servers, with a large number of maintainers. Getting them to agree on any single string for instructions is not likely to be easy (since they likely have much different features and presentations for things). Which isn't to say you shouldn't try to talk to some of them, just that I'm not sure how useful any talking will be. (Especially since I can't really see how they are going to solve the problem.) -Etan |
From: Richard L. <rl...@wi...> - 2006-03-26 17:46:22
|
On Sun, 2006-03-26 at 14:21 +0200, Bjoern Voigt wrote: > How should we deal with the original English text message? > > I see some possible solutions: > > (1) leave it as is > > (2) explain the user that this is a Jabber server comment > > (something like: _("Jabber server comment: ") + instructions) (2) is superior to (1). I've just committed something like that. We'll see how people like that. > (3) don't use the server comment, only use Gaim's own comment I don't like this; it throws away useful data. > (4) write a dummy translation string for this message > This only makes sense, if the server search comment is more or less > a standard comment. I think this might be okay for a couple really popular default strings, but it's also something that could quickly get out of control. Also, where do you draw the line? > (5) inform the Jabber maintainers about the problem This would probably require some sort of language negotiation between the client and the server and the server would need to have lots of strings configured. Unless someone who knows more about Jabber than me thinks it's futile, I'd say it's worth mentioning, but I doubt it'll get us anywhere, at least in the short term. Richard |
From: Bjoern V. <bj...@cs...> - 2006-03-26 12:23:52
|
Sorry, here is the screen shot. |
From: Bjoern V. <bj...@cs...> - 2006-03-26 12:22:02
|
Hello! I found that the search comment for Jabber user search is not translatable. Please take a look at the attached screen shot. I made this screen shot using the following steps: * Jabber account at jabber.org * search in "Accounts -> (my jabber account> -> Search for Users..." * "Select a user directory to search": users.jabber.org (default) * "Search Directory" There is an English comment "Find a contact [...] wild card searches (%)". The code comes from src/protocols/jabber/buddy.c: user_search_fields_result_cb() [...] if((instnode =3D xmlnode_get_child(query, "instructions"))) =09=09instructions =3D xmlnode_get_data(instnode); else =09=09instructions =3D g_strdup(_("Fill in one or more fields to search " =09=09=09=09=09"for any matching Jabber users.")); [...] The English text is not part of Gaim and not part of the Jabber daemon (searched in jabberd-2.0s10). My Internet search resulted in the fact that the English text is part of a Jabber configuration file: http://support.jabber.com/troubleshooting/know_base/jud_setup.html How should we deal with the original English text message? I see some possible solutions: (1) leave it as is (2) explain the user that this is a Jabber server comment (something like: _("Jabber server comment: ") + instructions) (3) don't use the server comment, only use Gaim's own comment (4) write a dummy translation string for this message (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. (5) inform the Jabber maintainers about the problem I would prefer (2), may be in combination with (4) but let's discuss it. The missing i18n markers in the search results dialog are already reported in=20 http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1458542&group_= id=3D235&atid=3D713922 Greetings, Bj=F6rn |
From: Mark D. <ma...@ki...> - 2006-03-21 00:58:07
|
We Gaim developers have been doing a little talking, and we've decided to come out of string freeze for a little while in order to make some changes. Why? Mostly because we want Gaim 2.0.0 to be really good. Over the past few weeks we've found some places where changing/adding strings would make the release better. And we feel those improvements are enough to justify delaying Gaim 2.0.0 a little more, and ruffling our translators feathers a bit. When? As of now we are no longer in a string freeze. We'll release beta 3 later this week (probably Thursday night, EST). When we feel we're really ready to release Gaim 2.0.0 final, we'll enter another string freeze that will last for 1 to 2 weeks. The number of changed strings between now and then should be relatively minor. My guess is around 25. So it looks like I was a bit premature in rushing into the first string freeze. Sorry to all the translators! I hope the added overhead has not cost too much of your time. If you haven't sent in an updated translation yet, feel free to do so whenever it's convenient for you. But keep in mind that the strings in CVS HEAD are a moving target (albeit a small one) until we string freeze again. Thanks for your patience! -Mark |
From: Clytie S. <cl...@ri...> - 2006-03-17 07:51:07
|
Hello again :) On 16/03/2006, at 10:47 PM, Vincent van Adrighem wrote: >> >> I see some familiar names on this list. <waves happily> > > <waves back> Hi, and welcome again. :) Thanks, Vincent. :) >> >> The stats page [1] only gives me a beautiful blank. :( >> >> So I have no idea what the status of our Vietnamese translation is. > > The page you're referring to is an XML file, I've been told. Not every > browser can handle that directly. Epiphany/Galeon (Firefox?) can > handle that. :( It certainly looks as though OmniWeb doesn't like it. I can look at =20 the source, though. It looks as though Vietnamese is currently at =20 about 54%. Not good. I'll follow this up with Qu=C3=BD. Maybe he no = longer =20 has enough time to translate this file. We might be able to fit it in =20= elsewhere. > > You can also just download the cvs yourself. > Take a look at [2] for instructions. After downloading the cvs, a > simple "intltool-update <language>" in the gaim/po directory will > give you an updated translation. CVS I can do. ;) > Thanks, Vincent, that was really helpful. :) 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: Erdal R. <erd...@gm...> - 2006-03-16 12:24:16
|
SGksCgo+IFRoZSBwYWdlIHlvdSdyZSByZWZlcnJpbmcgdG8gaXMgYW4gWE1MIGZpbGUsIEkndmUg YmVlbiB0b2xkLiBOb3QgZXZlcnkKPiBicm93c2VyIGNhbiBoYW5kbGUgdGhhdCBkaXJlY3RseS4g RXBpcGhhbnkvR2FsZW9uIChGaXJlZm94PykgY2FuCj4gaGFuZGxlIHRoYXQuCgpXaGF0IGEgY29v bCBtZXRob2QhIEkgd2lsbCB1c2UgdGhhdCBYTUwgZm9yIG93biBzdGF0aXN0aWMgcGFnZXMgaW4g dGhlCmZ1dHVyZS4gVGhhbmtzIGZvciB0aGUgaGludC4KCkVyZGFsCg== |
From: Vincent v. A. <adr...@gn...> - 2006-03-16 12:18:12
|
Op Thu, 16 Mar 2006 22:14:06 +1030 schreef Clytie Siddall <cl...@ri...>: > Hello all :) >=20 > I see some familiar names on this list. <waves happily> <waves back> Hi, and welcome again. :) > Sorry if I'm not up-to-date: after translating Gaim last year and =20 > finding that somehow I had translated "a too-new file", I handed > over the Vietnamese translation to Quy (at his request) quite some > time ago, and haven't been able to keep up with the list. >=20 > Today, I am trying to get some information prepared for a =20 > localization conference in Hanoi: a list of our current projects. >=20 > I couldn't find an i18n link at the Gaim site at all. Do you have > a translation project page, some basic information for translators? >=20 > One of the aims of my (online) information is to gather some =20 > volunteer effort to work on these projects, but I need to give the =20 > people somewhere to look. >=20 > The stats page [1] only gives me a beautiful blank. :( >=20 > So I have no idea what the status of our Vietnamese translation is. The page you're referring to is an XML file, I've been told. Not every browser can handle that directly. Epiphany/Galeon (Firefox?) can handle that.=20 You can also just download the cvs yourself. Take a look at [2] for instructions. After downloading the cvs, a simple "intltool-update <language>" in the gaim/po directory will give you an updated translation. Kind regards, Vincent van Adrighem [2]http://gaim.sourceforge.net/downloads.php |
From: Erdal R. <erd...@gm...> - 2006-03-16 12:16:10
|
SGksCgp0cnkgaHR0cDovL2dhaW0uc291cmNlZm9yZ2UubmV0L2kxOG4vCgpSZWdhcmRzLApFcmRh bAoKMjAwNi8zLzE2LCBDbHl0aWUgU2lkZGFsbCA8Y2x5dGllQHJpdmVybGFuZC5uZXQuYXU+Ogo+ IEhlbGxvIGFsbCA6KQo+Cj4gSSBzZWUgc29tZSBmYW1pbGlhciBuYW1lcyBvbiB0aGlzIGxpc3Qu IDx3YXZlcyBoYXBwaWx5Pgo+Cj4gU29ycnkgaWYgSSdtIG5vdCB1cC10by1kYXRlOiBhZnRlciB0 cmFuc2xhdGluZyBHYWltIGxhc3QgeWVhciBhbmQKPiBmaW5kaW5nIHRoYXQgc29tZWhvdyBJIGhh ZCB0cmFuc2xhdGVkICJhIHRvby1uZXcgZmlsZSIsIEkgaGFuZGVkIG92ZXIKPiB0aGUgVmlldG5h bWVzZSB0cmFuc2xhdGlvbiB0byBRdXkgKGF0IGhpcyByZXF1ZXN0KSBxdWl0ZSBzb21lIHRpbWUK PiBhZ28sIGFuZCBoYXZlbid0IGJlZW4gYWJsZSB0byBrZWVwIHVwIHdpdGggdGhlIGxpc3QuCj4K PiBUb2RheSwgSSBhbSB0cnlpbmcgdG8gZ2V0IHNvbWUgaW5mb3JtYXRpb24gcHJlcGFyZWQgZm9y IGEKPiBsb2NhbGl6YXRpb24gY29uZmVyZW5jZSBpbiBIYW5vaTogYSBsaXN0IG9mIG91ciBjdXJy ZW50IHByb2plY3RzLgo+Cj4gSSBjb3VsZG4ndCBmaW5kIGFuIGkxOG4gbGluayBhdCB0aGUgR2Fp bSBzaXRlIGF0IGFsbC4gRG8geW91IGhhdmUgYQo+IHRyYW5zbGF0aW9uIHByb2plY3QgcGFnZSwg c29tZSBiYXNpYyBpbmZvcm1hdGlvbiBmb3IgdHJhbnNsYXRvcnM/Cj4KPiBPbmUgb2YgdGhlIGFp bXMgb2YgbXkgKG9ubGluZSkgaW5mb3JtYXRpb24gaXMgdG8gZ2F0aGVyIHNvbWUKPiB2b2x1bnRl ZXIgZWZmb3J0IHRvIHdvcmsgb24gdGhlc2UgcHJvamVjdHMsIGJ1dCBJIG5lZWQgdG8gZ2l2ZSB0 aGUKPiBwZW9wbGUgc29tZXdoZXJlIHRvIGxvb2suCj4KPiBUaGUgc3RhdHMgcGFnZSBbMV0gb25s eSBnaXZlcyBtZSBhIGJlYXV0aWZ1bCBibGFuay4gOigKPgo+IFNvIEkgaGF2ZSBubyBpZGVhIHdo YXQgdGhlIHN0YXR1cyBvZiBvdXIgVmlldG5hbWVzZSB0cmFuc2xhdGlvbiBpcy4KPgo+IFRoZSBv bmx5IGluZm9ybWF0aW9uIGFib3V0IHRyYW5zbGF0aW5nIEdhaW0gSSd2ZSBiZWVuIGFibGUgdG8g aW5jbHVkZQo+IGhhcyBiZWVuIHRoZSBob21lcGFnZSBhbmQgdGhpcyBtYWlsaW5nIGxpc3QuCj4K PiBUaGFua3lvdSBmb3IgYW55IGhlbHAgeW91IGNhbiBnaXZlIHdpdGggdGhpcy4gOikKPgo+IGZy b20gQ2x5dGllICh2aS1WTiwgVmlldG5hbWVzZSBmcmVlLXNvZnR3YXJlIHRyYW5zbGF0aW9uIHRl YW0gLyBuaMOzbQo+IFZp4buHdCBow7NhIHBo4bqnbiBt4buBbSB04buxIGRvKQo+IGh0dHA6Ly9n cm91cHMtYmV0YS5nb29nbGUuY29tL2dyb3VwL3ZpLVZOCj4KPiBbMV0gaHR0cDovL2dhaW0uc291 cmNlZm9yZ2UubmV0L2kxOG4vCj4KPgo+Cj4KPgo= |
From: Clytie S. <cl...@ri...> - 2006-03-16 11:44:19
|
Hello all :) I see some familiar names on this list. <waves happily> Sorry if I'm not up-to-date: after translating Gaim last year and =20 finding that somehow I had translated "a too-new file", I handed over =20= the Vietnamese translation to Quy (at his request) quite some time =20 ago, and haven't been able to keep up with the list. Today, I am trying to get some information prepared for a =20 localization conference in Hanoi: a list of our current projects. I couldn't find an i18n link at the Gaim site at all. Do you have a =20 translation project page, some basic information for translators? One of the aims of my (online) information is to gather some =20 volunteer effort to work on these projects, but I need to give the =20 people somewhere to look. The stats page [1] only gives me a beautiful blank. :( So I have no idea what the status of our Vietnamese translation is. The only information about translating Gaim I've been able to include =20= has been the homepage and this mailing list. Thankyou for any help you can give with this. :) 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 [1] http://gaim.sourceforge.net/i18n/ |
From: Luke S. <lsc...@us...> - 2006-03-13 15:13:00
|
----- Forwarded message from "SourceForge.net" <no...@so...> ----- Date: Mon, 13 Mar 2006 01:50:25 -0800 From: "SourceForge.net" <no...@so...> To: no...@so... Subject: [Gaim-bugs] [ gaim-Bugs-1448734 ] German Translation for not availiable Bugs item #1448734, was opened at 2006-03-13 10:50 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100235&aid=1448734&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 Resolution: None Priority: 5 Submitted By: Windseeker (windseeker) Assigned to: Nobody/Anonymous (nobody) Summary: German Translation for not availiable Initial Comment: Hi! At the moment, the status "not availiable" is translated to german with "nicht erreichbar". This is kind of wrong, because it means "not reachable " what makes users think it is a technical problem reaching the (online and availiable) user. The correct and mostly used translaton would be "nicht verfügbar". Best regards, Daniel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100235&aid=1448734&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-bugs mailing list Gai...@li... https://lists.sourceforge.net/lists/listinfo/gaim-bugs ----- End forwarded message ----- |
From: Mark D. <ma...@ki...> - 2006-03-09 03:04:20
|
On Tue, 7 Mar 2006 17:31:13 -0500, Luke Schierer wrote > Mark currently wants to release gaim on the 9th. While there is some > doubt that this will actually happen, It does create a tenative > cut-off for updates at around noon gmt-5 on the 9th. Please let me > know if this is unreasonable. > > looking at gaim.sf.net/i18n, we are doing well. > > am, az, bg, bn, bs, en_AU, en_CA, et, gu, hi, it, ka, ko, ku, mk, > my_MM, nb, nn, pa, pl, sk, sq, sr and sr@Latn, ta, te, > uk, xh, and zh_CN are all below 75% translated, not counting fuzzy > translations. This is 29 of our 54 translations, but even many of > these are 70-71% translated. > > luke FYI we've pushed the release back to March 16th, at the earliest. So you've got at least another week, but it's always good not to wait until the last minute! Thanks, Mark |
From: Luke S. <lsc...@us...> - 2006-03-07 22:31:45
|
Mark currently wants to release gaim on the 9th. While there is some doubt that this will actually happen, It does create a tenative cut-off for updates at around noon gmt-5 on the 9th. Please let me know if this is unreasonable. looking at gaim.sf.net/i18n, we are doing well. am, az, bg, bn, bs, en_AU, en_CA, et, gu, hi, it, ka, ko, ku, mk, my_MM, nb, nn, pa, pl, sk, sq, sr and sr@Latn, ta, te, uk, xh, and zh_CN are all below 75% translated, not counting fuzzy translations. This is 29 of our 54 translations, but even many of these are 70-71% translated. luke |
From: Stu T. <st...@no...> - 2006-03-03 21:53:08
|
On Fri, 2006-03-03 at 22:33 +0100, Bjoern Voigt wrote: > $ cvs log -r 1.398 src/protocols/msn/msn.c > revision 1.398 > date: 2006/03/03 14:05:43; author: nosnilmot; state: Exp; lines: +148 -46 > Working parsing for the new MSN profiles. Much of this is #if 0'd out as it > adds new strings - someone should remind me to undo that when we've thawed. ... wishful thinking, hey? > The code is #if 0'd. But gettext also searches for new strings in "if > 0"-regions. Therefore we still see much untranslated and fuzzy strings. Sorry about that, I thought gettext was clever like that. > What is the best solution for this problem within a "non-strict" string > freeze? I don't think the introduction of this many not absolutely necessary strings is fair on you guys even during a "non-strict" string freeze. > My suggestions > > 1. If all of us have enough time until release, we can translate the > new strings. nosnilmot can active the new code then. > 2. We can change the _() markers to P_() markers in the new code like > in the imported GTK+ files. I've done something similar to 2 now. Let me know if I've caused any other problems. Regards, Stu. |
From: Bjoern V. <bj...@cs...> - 2006-03-03 21:33:12
|
Hello! I saw 34 new strings which where introduced with a patch to=20 src/protocols/msn/msn.c $ cvs log -r 1.398 src/protocols/msn/msn.c revision 1.398 date: 2006/03/03 14:05:43; author: nosnilmot; state: Exp; lines: +148 = -46 Working parsing for the new MSN profiles. Much of this is #if 0'd out as = it adds new strings - someone should remind me to undo that when we've thawe= d. The code is #if 0'd. But gettext also searches for new strings in "if=20 0"-regions. Therefore we still see much untranslated and fuzzy strings. What is the best solution for this problem within a "non-strict" string=20 freeze? My suggestions 1. If all of us have enough time until release, we can translate the new strings. nosnilmot can active the new code then. 2. We can change the _() markers to P_() markers in the new code like in the imported GTK+ files. I think, the second solution is better within string freeze but I'm not=20 sure. Greetings, Bj=F6rn |
From: Richard L. <rl...@wi...> - 2006-03-03 00:42:40
|
On Thu, 2006-03-02 at 23:22 +0100, Bjoern Voigt wrote: > I agree with Danilo that we do not need the "property description" > i18n > strings in the imported GTK+ files. > > My attached patch changes the _() markers to P_() markers in > gtkcellview.c and gtkcombobox.c. The file already had P_() markers. > The > files gtkcelllayout.c and gtkcellviewmenuitem.c do not have i18n > strings. Committed. Richard |
From: Bjoern V. <bj...@cs...> - 2006-03-02 22:22:33
|
Hello! I agree with Danilo that we do not need the "property description" i18n=20 strings in the imported GTK+ files. My attached patch changes the _() markers to P_() markers in=20 gtkcellview.c and gtkcombobox.c. The file already had P_() markers. The=20 files gtkcelllayout.c and gtkcellviewmenuitem.c do not have i18n strings.= Could someone commit the patch? The patch disables 33 unnecessary i18n strings. Greetings, Bj=C3=B6rn =D0=94=D0=B0=D0=BD=D0=B8=D0=BB=D0=BE =D0=A8=D0=B5=D0=B3=D0=B0=D0=BD wrote= : > =D0=88=D1=83=D1=87=D0=B5 =D1=83 0:51, Bjoern Voigt =D0=BD=D0=B0=D0=BF=D0= =B8=D1=81=D0=B0: > > > Now my questions? > > > > 1) Do we really need to translate the i18n strings in the imported GT= K+ > > files? > > > > I think no, because > > - the strings are never (or nearly never, may be on errors) visib= le > > to the user > > - only users with an old GTK+ setup (<=3D2.6.0) will use this imp= orted > > files > > > > 2) If we decide that it's not useful to translate the i18n strings in= > > the imported files, it's easy to disable the strings. The file > > gtkexpander.c for instance has it disabled. > > "Property descriptions" can freely be disabled, IMHO. They are not > useful, and are only visible in a prospective "GObject class browser", > and I am not sure that such a thing exists. They will not be seen by > users. This is the main reason we split this in Gnome (so translators > know that they don't need to translate this for full Gnome support). > > All strings marked with P_ are such "property descriptions". Other > strings are actually useful |
From: Richard L. <rl...@wi...> - 2006-03-02 16:18:09
|
On Thu, 2006-03-02 at 16:52 +0330, Elnaz Sarbar wrote: <=D8=B1=D9=88=D8=B2 =DA=86=D9=87=D8=A7=D8=B1=D8=B4=D9=86=D8=A8=D9=87=D8=8C= 2006-03-01 =D8=B3=D8=A7=D8=B9=D8=AA 15:18 -0600=D8=8C Richard Laager =D9= =86=D9=88=D8=B4=D8=AA: <It's no big deal :) but it would be really better if they are > translatable. Given the differences in opinion, I've marked these for translation again. That way the individual translators can make the decision. Richard |
From: Elnaz S. <el...@fa...> - 2006-03-02 13:27:59
|
=D8=B1=D9=88=D8=B2 =DA=86=D9=87=D8=A7=D8=B1=D8=B4=D9=86=D8=A8=D9=87=D8=8C= 2006-03-01 =D8=B3=D8=A7=D8=B9=D8=AA 15:18 -0600=D8=8C Richard Laager =D9= =86=D9=88=D8=B4=D8=AA: > On Wed, 2006-03-01 at 21:51 +0100, =D0=94=D0=B0=D0=BD=D0=B8=D0=BB=D0=BE= =D0=A8=D0=B5=D0=B3=D0=B0=D0=BD wrote: > > =D0=94=D0=B0=D0=BD=D0=B0=D1=81 =D1=83 8:18, Richard Laager =D0=BD=D0=B0= =D0=BF=D0=B8=D1=81=D0=B0: > > > >=20 > I don't really know much about languages, especially not Serbian.... Is > this a problem? I can add the translation markers back if you need them. Hi, Most of GNOME Persian translators prefer to transcribe names as much as possible. Our language is written in Arabic script which looks much different from Latin script and is right-to-left. It looks much more nicer when names are transcribed. It's no big deal :) but it would be really better if they are translatable. Cheers, Elnaz |
From: <da...@gn...> - 2006-03-01 21:40:47
|
Today at 22:18, Richard Laager wrote: > I don't really know much about languages, especially not Serbian.... Is > this a problem? I can add the translation markers back if you need them. It's not a big problem. It's pretty much similar for all non-Latin-script based languages: there are different opinions among translators themselves. I've been a witness of some arguments about the same stuff on gnome-cyr list (Russian GNOME translation list). It's about what is more important: advertising a foreign product as foreign, or advertising it as what it does. And there are sometimes puns in the name which are best translated if translator is aware of them (think of "[Netscape] Navigator", "[Internet] Explorer", "Konqueror", "Galeon", perhaps even "Epiphany"?). For instance, all of the translators (three of us so far) who worked on Gaim Serbian translations seem to support transcription at least ("Trillian" in "Trillian Encryption" is transcribed as "=D0=A2=D1=80=D0=B8= =D0=BB=D0=B8=D1=98=D0=B0=D0=BD"). However, some names of the programs are simply impossible to leave untranslated (imagine things like "Best Instant Messenger" or "Gnome System Tools" :). > It's not a huge deal at the moment, since the plugin isn't compiled by > default, but if I manage to find the time to work on it again, it will > be once it's cleaned up a bit. Sure, it's not a big deal, but just take it into consideration. Cheers, Danilo |
From: Richard L. <rl...@wi...> - 2006-03-01 21:18:39
|
On Wed, 2006-03-01 at 21:51 +0100, =D0=94=D0=B0=D0=BD=D0=B8=D0=BB=D0=BE =D0= =A8=D0=B5=D0=B3=D0=B0=D0=BD wrote: > =D0=94=D0=B0=D0=BD=D0=B0=D1=81 =D1=83 8:18, Richard Laager =D0=BD=D0=B0= =D0=BF=D0=B8=D1=81=D0=B0: >=20 > > On Wed, 2006-03-01 at 07:57 +0100, Emil Nowak wrote: > >> Hello, > >> When I was updating my translation I found that in /plugins/log_read= er there > >> are names of other Instatnt Messaging programes and they are marked = for > >> translation. There is Fire, Adium, Trillian.=20 > >> Those names shouldn't be translated, so I suggest to remove gettext = functions > >> from here, to make sure no one accidentally translates it. > > > > Done. > > > > Thanks for bringing this to our attention. >=20 > Are you sure those programs' names are not translated in themselves as > well? I know that people generally have differing ideas on this, and=20 > making them translatable satisfies both worlds (i.e. those who don't > want to translate them just copy them over). I thought of this. I did some checking, and I don't see them translated anywhere on their respective sites. The text around the names is translated, but not the names. > For Serbian, most of them would be at least transcribed to Cyrillic > (one would not lose any of the meaning, yet they would be readable to > everyone). I don't really know much about languages, especially not Serbian.... Is this a problem? I can add the translation markers back if you need them. It's not a huge deal at the moment, since the plugin isn't compiled by default, but if I manage to find the time to work on it again, it will be once it's cleaned up a bit. Richard |
From: <da...@gn...>
) - 2006-03-01 20:47:13
|
=D0=94=D0=B0=D0=BD=D0=B0=D1=81 =D1=83 8:18, Richard Laager =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0: > On Wed, 2006-03-01 at 07:57 +0100, Emil Nowak wrote: >> Hello, >> When I was updating my translation I found that in /plugins/log_reader t= here >> are names of other Instatnt Messaging programes and they are marked for >> translation. There is Fire, Adium, Trillian.=20 >> Those names shouldn't be translated, so I suggest to remove gettext func= tions >> from here, to make sure no one accidentally translates it. > > Done. > > Thanks for bringing this to our attention. Are you sure those programs' names are not translated in themselves as well? I know that people generally have differing ideas on this, and=20 making them translatable satisfies both worlds (i.e. those who don't want to translate them just copy them over). For Serbian, most of them would be at least transcribed to Cyrillic (one would not lose any of the meaning, yet they would be readable to everyone). Anyway, just my 2c ;) Cheers, Danilo |
From: Ethan B. <ebl...@cs...> - 2006-03-01 12:29:24
|
Emil Nowak spake unto us the following wisdom: > and another thing. > In > #: ../src/gtkconv.c:364 > we have msgid: "me is using Gaim v%s." > If someone translates first word ("me") from this, then=20 > /devug version > command will not work - at least in jabber conferences.=20 > So it may be good, to put warning for translators, or split this string i= nto > translatable, and non-translatable parts. This string, like the debug logs, should not be translatable at all. I am marking it as such, thanks for catching this. 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 |