From: Luke S. <lsc...@us...> - 2007-04-07 13:57:40
|
Dear translators, Many years ago, when this project was first started, it was called "GTK+ AOL Instant Messenger." AOL naturally complained, and Mark Spencer changed the name to "Gaim." AOL was appeased, and no one really ever heard of it because there were very few users back then. A few years passed, AOL trademarked "AIM," and started refering to their IM services under that name. They complained. The issue was brought up on Slashdot, and the developers at the time got some legal support. That legal support advised that the ongoing discussions with AOL be kept confidential until fully settled, and so it remained. Everyone thought the issue went away then. It sorta did, in that AOL stopped responding to the legal support for a while. Our legal support has changed several times, and each group of lawyers have recommended silence & secrecy. Around the time of the first 2.0.0 beta, AOL came back into our lives in a very strong way, this time threatening to sue Sean. This represents a clear pattern. AOL received more pushback than they expected, and would sort of let things stand for a while. They they woudl threaten a different Gaim developer. Each time a new Gaim developer was threatened, we had to look at new legal support. This process could not go on forever. As a result we ended up forming the Instant Messaging Freedom Coporation, and making it legally responsible for Gaim. We also had our new legal support work to create a real settlement with AOL that would get this issue dismissed from our lives forever. Getting a settlement with AOL has taken FAR FAR longer than we would have ever guessed. On legal advise, we have refrained from any non-beta release during this process as a show of good faith, and to keep AOL from giving up on it. Again, on legal advise, we have also kept this information closely embargoed. At long last, I am pleased to announce, that we have a signed settlement, and can again release. There is one catch however, we have had to change the project's name. After long, and unfortunately secret (as we could not say why we were looking at a name change, we ended up just doing this ourselves), debate, we settled on the name "Pidgin" for gaim itself, "libpurple" for libgaim (which, as of 2.0.0 beta6, exists), and "finch" for gaim-text. Yes, the spelling of "Pidgin" is intentional. Since between the name, and the nature of the 2.0.0 release itself, so much is changing, we decided to go ahead with something we have talked about doing for a while now anyway. We have gotten our own server, kindly donated by DVLabs. As a result our new home will be www.pidgin.im and developer.pidgin.im We, at least for now, will still be using SF's mirroring system for releases. However, the bug tracking will no longer be on SF, and we will be migrating the mailing lists at some point soon. Also, we have chosen to go with monotone for our revision control, rather than the SF cvs or svn. In the last week or so, an upgrade to SF's infrastructure caused an old version of the gaim-cabal list to become briefly public. It has always been our intention to end-of-life this list and make its archives public once the settlement was signed. Fortunately, very few people took notice of the lapse, and equally fortunately, the legal process has concluded, allowing us to make a formal announcement now, instead of months from now. I, and all of pidgin's development team have deaply hated the need to keep some portion of our work, decision making and discussion secret for a time. I sincerely appologize that as a result of this need, you all have had no chance to help us with it, and to provide feedback. I also regret that this will create additional work for you. Now that the settlement is signed, we are looking at making our public announcement sometime this weekend or early this coming week. We hope to have the final pidgin 2.0.0 release late this week or early next. I know we have announced a string freeze several times, and only poorly kept the source actually frozen. Hopefully you now see why there were several false attempts at releasing (delays in the legal process), and why it has been hard to honor the string freeze (no sure notion of when exactly we would be able to release, whether in weeks or in months). This will be the last string change before the final release. Ethan tells me that for some languages this will be more than a search and replace operation, or I would just sed the po files and change the name myself. Nathan is working on getting a new copy of the i18n page up at www.pidgin.im. We are closing the SF tracker (I believe there are one or two translation updates still in it. I will grab those shortly), so new updates should go to developer.pidgin.im, just create a ticket for them. You may need to gzip your po file to be able to upload it. luke luke ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Gaim-packagers mailing list Gai...@li... https://lists.sourceforge.net/lists/listinfo/gaim-packagers ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Gaim-packagers mailing list Gai...@li... https://lists.sourceforge.net/lists/listinfo/gaim-packagers |
From: Luke S. <lsc...@us...> - 2007-04-07 15:32:48
|
On Sat, Apr 07, 2007 at 11:52:52AM -0300, Maurício Collares wrote: > I have one question, though. Is the monotone server available now, or > is SourceForge's svn the main repository at this moment? I translate > by downloading the repository files, running update-intltool and then > updating the po file (as opposed to grabbing the po in /i18n/); > getting this wrong would result in (lots of) useless work. > It is available now. luke |
From: Mark D. <ma...@ki...> - 2007-04-07 15:39:43
|
On Sat, 7 Apr 2007 11:32:38 -0400, Luke Schierer wrote > On Sat, Apr 07, 2007 at 11:52:52AM -0300, Maurício Collares wrote: > > I have one question, though. Is the monotone server available now, or > > is SourceForge's svn the main repository at this moment? I translate > > by downloading the repository files, running update-intltool and then > > updating the po file (as opposed to grabbing the po in /i18n/); > > getting this wrong would result in (lots of) useless work. > > > > It is available now. There's some info on using the repository at http://developer.pidgin.im/wiki/UsingPidginMonotone -Mark |
From: Nathan W. <fac...@fa...> - 2007-04-07 16:02:51
|
Luke Schierer wrote: <snip> > Nathan is working on getting a new copy of the i18n page up at > www.pidgin.im. We are closing the SF tracker (I believe there are one > or two translation updates still in it. I will grab those shortly), so > new updates should go to developer.pidgin.im, just create a ticket for > them. You may need to gzip your po file to be able to upload it. http://pidgin.im/l10n/ Happy translating! -Nathan |
From: Nathan W. <fac...@fa...> - 2007-04-07 22:29:08
|
Nathan Walp wrote: > Luke Schierer wrote: > <snip> >> Nathan is working on getting a new copy of the i18n page up at >> www.pidgin.im. We are closing the SF tracker (I believe there are one >> or two translation updates still in it. I will grab those shortly), so >> new updates should go to developer.pidgin.im, just create a ticket for >> them. You may need to gzip your po file to be able to upload it. > > http://pidgin.im/l10n/ > > Happy translating! > > -Nathan > http://developer.pidgin.im/ticket/56 Can I assume that fixing this is worth breaking the string freeze, since no good translation can really happen with it like it is? I want an OK from a translator or two before I go ahead and commit. -Nathan |
From: Nathan W. <fac...@fa...> - 2007-04-07 22:51:02
|
Bjoern Voigt wrote: > Nathan Walp wrote: >> http://developer.pidgin.im/ticket/56 >> Can I assume that fixing this is worth breaking the string freeze, since >> no good translation can really happen with it like it is? I want an OK >> from a translator or two before I go ahead and commit. >> > For me it's ok. But do we really currently have a string freeze? I have > more than 76 fuzzy strings and more than 7 new strings since switching > from Gaim (trunk) to Pidgin. I would prefer to delay the string freeze > for some days because some more i18n problems may be found in the next days. > I have committed the change to mtn, and started the update script for the l10n stats page, so a new .pot file should be there in the next hour or so (I forget how long it takes that script to run these days). We're certainly trying to act like we're in string freeze, but I don't consider it a hard freeze if we have to break it to make the lives of you translators easier somehow. I know we're asking a lot from you guys on pretty short notice :-/ -Nathan |
From: <mau...@gm...> - 2007-04-07 22:56:17
|
I, too, have no problem with the change. I can't access the monotone server, though. mauricioc@mauricioc:~/monotone$ monotone -d db.mtn db init mauricioc@mauricioc:~/monotone$ monotone -d db.mtn pull pidgin.im im.pidgin= .* monotone: setting default server to pidgin.im monotone: setting default branch include pattern to 'im.pidgin.*' monotone: setting default branch exclude pattern to '' monotone: doing anonymous pull; use -kKEYNAME if you need authentication monotone: connecting to pidgin.im monotone: network error: failed to connect: Connection timed out Am I doing something wrong? -- Thanks, Maur=EDcio On 4/7/07, Nathan Walp <fac...@fa...> wrote: |
From: Nathan W. <fac...@fa...> - 2007-04-07 22:59:17
|
Maurício Collares wrote: > I, too, have no problem with the change. I can't access the monotone > server, though. > > mauricioc@mauricioc:~/monotone$ monotone -d db.mtn db init > mauricioc@mauricioc:~/monotone$ monotone -d db.mtn pull pidgin.im > im.pidgin.* > monotone: setting default server to pidgin.im > monotone: setting default branch include pattern to 'im.pidgin.*' > monotone: setting default branch exclude pattern to '' > monotone: doing anonymous pull; use -kKEYNAME if you need authentication > monotone: connecting to pidgin.im > monotone: network error: failed to connect: Connection timed out > > Am I doing something wrong? I don't believe you're doing anything wrong. Perhaps you have some sort of firewall disallowing that port? It works for me, that's about all I can say. Ethan Blanton is our resident monotone expert. -Nathan |
From: <mau...@gm...> - 2007-04-07 23:00:28
|
Okay, just found out. Wikipedia says: "Monotone version 0.26 introduced major changes to the internal database structures, including a new structure known by Monotone developers as a roster[1]. Monotone databases created with version 0.26 can not exchange revisions with older Monotone databases. The older databases must first be upgraded to the new format. The new netsync protocol is incompatible with earlier versions of Monotone." Ubuntu Edgy, however, has: mauricioc@mauricioc:~/monotone$ monotone --version monotone 0.24 (base revision: d59847072bb689e952ab21db7f9fababdb80a19f) I will update monotone, then. Sorry for bothering. On 4/7/07, Maur=EDcio Collares <mau...@gm...> wrote: |
From: <mau...@gm...> - 2007-04-07 23:24:46
|
For Ubuntu Edgy people: I just installed these packages from Debian: http://www.backports.org/debian/pool/main/m/monotone/monotone_0.28-1~bpo.1_= i386.deb http://http.us.debian.org/debian/pool/main/b/boost/libboost-date-time1.32.0= _1.32.0-6_i386.deb http://http.us.debian.org/debian/pool/main/b/boost/libboost-regex1.32.0_1.3= 2.0-6_i386.deb http://http.us.debian.org/debian/pool/main/b/boost/libboost-filesystem1.32.= 0_1.32.0-6_i386.deb And things seem to work fine now. Ubuntu Feisty has monotone 0.31, but the package requires a newer libc6 then what I have. This could save some time. By the way, the binary name is now mtn as expected, which suggests they changed the name in order to explicit the incompatibility. Again, sorry for bothering, but this might be useful to someone. -- Thanks, Maur=EDcio On 4/7/07, Maur=EDcio Collares <mau...@gm...> wrote: |
From: Bjoern V. <bj...@cs...> - 2007-04-07 23:02:43
|
Maurício Collares wrote: > I, too, have no problem with the change. I can't access the monotone > server, though. > > mauricioc@mauricioc:~/monotone$ monotone -d db.mtn db init > mauricioc@mauricioc:~/monotone$ monotone -d db.mtn pull pidgin.im > im.pidgin.* > monotone: setting default server to pidgin.im > monotone: setting default branch include pattern to 'im.pidgin.*' > monotone: setting default branch exclude pattern to '' > monotone: doing anonymous pull; use -kKEYNAME if you need authentication > monotone: connecting to pidgin.im > monotone: network error: failed to connect: Connection timed out > > Am I doing something wrong? May be your firewall blocks the Monotone port (port 4691)? I'm also new to Monoton, but there is some info: http://monotone.ca/monotone.html#Basic-Network-Service Greetings, Björn |
From: Bjoern V. <bj...@cs...> - 2007-04-07 22:44:58
|
Nathan Walp wrote: > http://developer.pidgin.im/ticket/56 > Can I assume that fixing this is worth breaking the string freeze, since > no good translation can really happen with it like it is? I want an OK > from a translator or two before I go ahead and commit. > For me it's ok. But do we really currently have a string freeze? I have more than 76 fuzzy strings and more than 7 new strings since switching from Gaim (trunk) to Pidgin. I would prefer to delay the string freeze for some days because some more i18n problems may be found in the next days. Greetings, Björn |
From: Timo J. <tim...@hu...> - 2007-04-08 12:20:52
|
Luke Schierer kirjoitti: > This will be the last string change before the final release. Ethan > tells me that for some languages this will be more than a search and > replace operation, or I would just sed the po files and change the name > myself. Unfortunately it looks like some string changes have been made that make it impossible to translate those strings anymore in a correct way. I noticed these: "Welcome to " - two of these "About " "distributed with " - in the end of the long Pidgin description, also starts with empty space but there the non-conjugated "Pidgin" fits in at least in my language "You are using " "_Force (traditional " "Options specific to Windows " "Provides options specific to Windows " All of the above are probably attaching "Pidgin" after the string, which breaks the translations in many languages as the translator is not given the possibility to conjugate the word Pidgin in the way that would fit the string. I tried to work around the problems but it's usually simply quite impossible without the translation sounding very stupid. I guess the idea was to keep some more parts of the translations not bound to the program name, but could these listed ones be reverted so that they include the "Pidgin" in the English translatable string? There were some others similar to these, too, but I'd guess they are translatable still in every language - the difference is that in those above there some extra word like "to", "about", "with" etc., which in many languages are done by conjugating the words. Not sure why, but some items seem not to be translated at all in the UI now, including "Welcome to Pidgin!", and "You have no accounts enabled..." and the About Pidgin dialog including the title and the first paragraph describing Pidgin. I'm currently using the snapshot linked to at http://developer.pidgin.im/, with (again) fully translated fi.po file. -Timo |
From: Bjoern V. <bj...@cs...> - 2007-04-08 12:35:45
|
Timo Jyrinki wrote: > Luke Schierer kirjoitti: > >> This will be the last string change before the final release. Ethan >> tells me that for some languages this will be more than a search and >> replace operation, or I would just sed the po files and change the name >> myself. >> > > Unfortunately it looks like some string changes have been made that make > it impossible to translate those strings anymore in a correct way. I > noticed these: > > "Welcome to " - two of these > "About " > "distributed with " - in the end of the long Pidgin description, also > starts with empty space but there the non-conjugated "Pidgin" fits in at > least in my language > "You are using " > "_Force (traditional " > "Options specific to Windows " > "Provides options specific to Windows " > Yes, there is a ticket for this issue: http://developer.pidgin.im/ticket/56 The ticket should be reopened because the issue is only partially fixed. See http://developer.pidgin.im/ticket/56#comment:7 Greetings, Björn Greetings, Björn |
From: Ambrose LI <ac...@ad...> - 2007-04-09 03:56:04
|
Hi, the Chinese (traditional) translation team has not had the time to look at the latest strings yet. We wish to have a few days' time to assess the situation. Thank you. -- cheers, -ambrose don't believe everything you read in Wikipedia... |
From: Javier <jf...@co...> - 2007-04-08 10:00:34
|
On Sat, Apr 07, 2007 at 09:57:34AM -0400, Luke Schierer wrote: > Nathan is working on getting a new copy of the i18n page up at > www.pidgin.im. We are closing the SF tracker (I believe there are one > or two translation updates still in it. I will grab those shortly), so > new updates should go to developer.pidgin.im, just create a ticket for > them. You may need to gzip your po file to be able to upload it. I guess the webpage up at http://pidgin.im/ still nees to be updated: - second item in the menu is still "What is Gaim" - bug report link on the menu (http://pidgin.im/bug.php) still redirects to SF I guess translators have to send our new translations using the new ticketing system (http://developer.pidgin.im/report), right? I'm not a very expert trac user, could you please clarify how we should open up new tickets? I think the steps are: - Create an account in trac - Login to that account - Go to "New ticket" (top menu, item farthest to the right) (at http://developer.pidgin.im/simpleticket) - Add description mark 'I have files to attach' and upload the translation Is this correct? Regards Javier |