多年前項目伊始是，命名叫"GTK+ AOL Instant Messenger".AOL自然不樂意，於是Mark Spencer將項目更名為Gaim。這下AOL滿意了，因為沒認聽過這個名字，用戶也不多。
A few years later AOL trademarked "AIM," and started referring to their IM services using that name. They complained. The issue was brought up on Slashdot, and the Gaim 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. The public thought the issue had gone away then. It sorta did, in that AOL stopped responding to Gaim's legal support for a while.
幾年之後AOL為AIM申請了專利，並且開始對是用這個名字的IM服務說事。還發起了訴訟。這個話題當年Slashdot討論過，也有人一度向Gaim的開發人員提供法律支持。法律支持認為在持續同AOL的對話最終下定結論前可以保持信息，事態也如法律支持所料。公眾認為這個話題已經過去。可以說AOL一度對Gaim的法律支持不再回應。
Our legal support has changed several times, and each group of lawyers have recommended silence & secrecy. Around the time of Gaim's first 2.0.0 beta, AOL came back into our lives in a very strong way, this time threatening to sue Sean.
我們的法律支持幾度換人，並且每批律師都建議沉默和保密。在Gaim2.0.0的第一個beta前後，AOL卷土重來，這次威脅要告的是Sean。
This represents a clear pattern. AOL received more pushback than they expected, and would sort of let things stand for a while. Then they would threaten a different Gaim developer. Each time a new Gaim developer was threatened, we had to look at new legal support, to prevent a conflict of interest.
事情已經明了。當年AOL得到了比預期要多的阻力，所以把事情擱置一段時間。然後他們換一名開發人員威脅要起訴。每次一位新的Gaim開發人員被威脅，我們得求助於新的法律支持,以避免利益沖突。
This process could not go on forever. As a result we ended up forming the Instant Messaging Freedom Corporation, 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.
事情不能永遠拖延下去。於是我們以建立Instant Messaging Freedom Corporation的形式終結，以為Gaim承擔法律責任。我們責令我們的法律支持著手同AOL達成一個永久的和解，以讓這個話題在我們有生之年永遠不再提及。
Getting a settlement with AOL has taken FAR FAR longer than we would have ever guessed. On legal advice, 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 advice, we have also kept this information closely controlled.
同AOL比我們猜的要遠困難得多。依照法律上的建議，我們在和解過程中避免了任何非beta版本的發布，以表示我們的誠意，並且要防止AOL單方面放棄和解。再一次，法律支持建議，我們還要保持這個消息不被宣揚。
At long last, I am pleased to announce that we have a signed settlement and can release our new version. There is one catch however: we have had to change the project's name.
最終，我很高興宣布我們簽署了和解並且可以發不我們新的版本了。不過有一個條件：我們不得不更換項目的名字。
After a long, and unfortunately secret debate (as we could not say why we were looking at a name change, we ended up just doing this ourselves), 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, see http://en.wikipedia.org/wiki/Pidgin.
在長時間，很不幸是秘密的爭論(我們說不好為什麼要選擇更換名稱，於是我們只是單方面這樣做了)之後。我們將Gaim更名為Pidgin，libgaim (作為2.0.0beta6)更名為libpurple，以及gaim-text改名為Finch。Pidpin這個發音也尤其特定的意義。參見：
Since>en.wikipedia.org/wiki/Pidgin.
Since so much is changing between the name and the nature of the 2.0.0 release itself, we decided to go ahead with something we have talked about doing for a while now. We have set up 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.
因為2.0.0發布的名稱和本身都改變得太多，我們打算一不做二不休。我們在DVLabs的贊助下建立了自己的服務器。於是我們的新主頁現在成了www.pidgin.im和developer.pidgin.im 我們，至少是現在，會堅持使用SF的鏡像系統來發布。然而，錯誤報告系統不會再在SF上使用，郵件列表也將移動到其他某個地方。同樣，我們選擇了monotone作為我們的版本控制系統，放棄了SF的cvs和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, the legal process has concluded, allowing us to make a formal announcement now, instead of months from now.
大概是上周，一次SF基礎設施的升級導致一個老版的gaim-cabal列表變得完全公開。而我們的原本的打算是停止這個列表，並且在和解簽署後在公布這個列表的存檔。幸運的是，法律過程已經有了結論，我們現在可以發布正式的聲明，而不是幾個月之後。
I, and all of pidgin's development team have deeply hated the need to keep some portion of our work, decision making and discussion secret for a time. I sincerely apologize that as a result of this need, you all have had no chance to help us with it, and to provide feedback.
我以及所有的Pidgin的開發小組成員一度憎惡把我們的工作分幾個部分，秘密的討論和決策。我們對由此沒有給大家提供援助和反饋的機會表示嚴正的歉意。
Now that the settlement is signed, we hope to have the final Pidgin 2.0.0 release late this week or early next.
現在和解已經簽署，我們希望本周末和下周初就可以發布Pidgin2.0.0了。
We are going to release it with a 2.0.0 version number, and an API compatibility layer for plugin authors. The project has not changed; this is our 2.0.0 release, not some new program that requires new version numbering.
我們希望以2.0.0的版本號發不，並且為插件作者提供一個API兼容層。項目沒有改變，這是我們的2.0.0發布，不像某個新的程序，需要新的版本號。
