[CN | DE | EN | FR | IT | JA | ES | KO | PT | ZH]
Welcome back to the Brave GNU World. Firstly I'd like to apologize to all of you who were disappointed to not find the Brave GNU World in its usual place when going through the magazine(s) or web. Directly before the column needed to be written I broke my clavicle. This put typing way beyond my capabilities.
欢迎回到《勇敢 GNU 世界》。首先我想要向你们各位，失望地没有在杂志或网络上通常的地方找到《勇敢 GNU 世界》的人说声抱歉。就在这个专栏要被写成之前，我摔断了我的锁骨。这使得打字超出了我的能力。【译注：为求优译，中英文并陈将持续到译文被发表之后四周左右；在此期间，请不吝于提供对于本文翻译的意见。】
After this extremely unvoluntary pause things should continue as usual with a good mix of different subjects.
〔即使〕在这个极端的非自愿中断〔发生〕之后，事情还是得一如往常，以「好的不同主题的混合」继续〔进行〕。
Gnuzza （密码学聊天：CryptChat）
Still in beta-testing,but already being used is Gnuzza (ChryptChat) by Timo Schulz. The project began when a friend of his was asking him for a secure chat program that would work on GNU/Linux and Windows. So Timo began writing one and July 2001 version 0.0.3 of Gnuzza was published under the terms of the GNU General Public License (GPL) as Free Software.
仍然在 beta 测试中，但是已经在使用的是由 Timo Schulz 所完成的 Gnuzza （密码学聊天）。 [5] 这工程开始于他的一位朋友问他是否有一个，可以在 GNU/Linux 和 Windows 上工作的安全聊天程序。所以 Timo 就开始撰写一个，并且在二○○一年七月， Gnuzza 的 0.0.3 版就在 GNU General Public License (GPL) 的条款下发行为自由软件了。
Gnuzza is a "peer to peer" (p2p) chat progam with strong cryptography,so it allows two people to chat via keyboard while preserving their privacy. Also they can mail each other files through the encrypted channel.
Gnuzza 是一个「一对一（peer to peer；简写为p2p）」，且具有强密码学的聊天程序，因此它允许两个人经由键盘聊天的同时，也保存他们的隐私权。他们也可以经由这个加密的渠道互相寄送档案。
Based on the GNU cryptography library libgcrypt,[6] Gnuzza supports Diffie Hellman key exchange (1024 up to 4096 bit) as well as the symmetrical algorithmy 3DES,BlowFish,Twofish,CAST5 and Rijndael. Gnuzza default is to use asymmetrical encryption,though,since this makes commonly known passwords unnecessary. Authentification of users is easily done through OpenPGP compliant keys in this case.
以 GNU 密码学程序库（library） libgcrypt [6] 作为基础， Gnuzza 支援 Diffie Hellman 键交换（key exchange）（从 1024 到最多 4096 个位元）以及对称算法 3DES 、 BlowFish 、 Twofish 、 CAST5 和 Rijndael。虽然如此， Gnuzza 的预设（default）是使用非对称加密法，因为这会让通常已知的通行码（passwords）变得没有必要。使用者的认证（Authentification）在这样的状况下，可以经由 OpenPGP 所认可的键而简单地完成。
Gnuzza has been written in ANSI C with a ncurses user interface,which makes it fast and resource friendly. It runs on GNU/Linux,on which the required libraries are installation standard for most distribution,and Windows,for which dependency on DLLs has been minimized.
Gnuzza 是以 ANSI C 所写成，同时具有一个 ncurses 使用者介面，这使得它很快并且资源友善。它在 GNU/Linux （所需要的程序库对大部份的散布件都是安装的标准）以及 Windows （对于 DLLs 的依赖已经降到最低）上执行。
Owing to ncurses the program has a text-based user interface,but some users would probably prefer a truly graphical user interface. For these Timo is considering a GTK+/GNOME/KDE GUI - but he does not have any experience with GTK+ and is therefore looking for volunteers to take care of this part of the project.
由于〔采用〕 ncurses ，这程序有一个以文字作为基础（text-based）的使用者介面，但是一些使用者也许会更喜欢一个真正的图形使用者介面。由于这些〔原因〕， Timo 正在考虑一个 GTK+/GNOME/KDE 的 GUI - 但他并没有任何 GTK+ 的经验，因此正在寻找志愿者来处理工程的这个部份。
Besides the aforementioned,tracing down and eliminating bugs is in the focus of his interest. Should you be wondering now whether you should give it a try,it should be pointed out that thanks to thoroughly considered default settings,knowledge about cryptography is only required for the advanced functionality. So if you are not afraid of beta software,you should not find it difficult to use Gnuzza.
除了前面所提及的之外，追查并且排除臭虫〔也〕是他所关注的焦点。如果你现在疑惑着是否应该试试它一下，〔在这里〕应该指出的是，感谢这些认真考虑过的预设设定（default settings），有关密码学的知识只有在进阶的功能时才有必要。所以如果你并不害怕 beta 〔测试中版本〕的软件，你应该不会发现使用 Gnuzza 很困难〔才是〕。
A word of warning for those intending to use it on Windows,however: Don't put too much trust into the security of the application,because every chain is only as strong as its weakest link. So it could happen that data is transmitted into the Gnuzza client on Windows securely only to be passed on by the operating system itself to a third party.
然而，奉劝一句给那些打算在 Windows 上使用它的人：不要太过于信任这个应用〔程序〕的安全〔机制〕，因为每一个链条（chain）的强度就和它最弱的链接（link）相同。所以可能会发生：传送到 Gnuzza 在 Windows 上的代理程序（client）的资料，就被作业系统本身传递到第三者（third party）了。
Or to put it plainly: Building steel doors into cardboard houses is only of limited use.
或者更清楚地说：在硬纸板房屋上建造钢板门只有有限的用途而已。
GNU Aspell （GNU 拼字检查器）
Among the applications that are generally useful for most users are certainly automatic spell checkers. GNU Aspell [7] is such a program and since August 2002 it is part of the GNU Project.
在所有的应用〔程序〕中，对大部份的使用者都能一般地有用的，无疑是自动拼字检查器（automatic spell checkers）。 GNU Aspell [7] 就是这样的一个程序，它并且从二○○二年八月开始成为 GNU 工程的一部份。
Until the Aspell project was started,there was only one spell checking program that was Free Software: International Ispell. [8] Naturally,Ispell turned out to be rather widespread on most Unix machines and was also the standard spell checker for the GNU System. Unfortunately,the intelligence of suggestions made by Ispell was noticeably below those made by proprietary spell checkers.
直到 Aspell 工程开始之前，只有一个拼字检查程序是自由软件： International Ispell 。 [8] 自然地， Ispell 结果在大部份的 Unix 机器上变得更加广布，而且也成为 GNU 系统的标准拼字检查器。不幸的是，由 Ispell 所作出的知识〔产权〕建议，明显地比那些由私权拼字检查器所作出的还要糟糕。
For this reason and based on the "Lawrence Philips' Metaphone Algorithm," which allows approximating the English pronounciation of a written word,Kevin Atkinson began working on Aspell in 1998. It was first released in September 1998 under the name Kspell,but since the KDE spell checking project was also called Kspell,he changed the name to Aspell.
为了这个原因，并且根据允许一个接近书写字英语发音的「Lawrence Philip 的 Metaphone 算法」， Kevin Atkinson 在一九九八年开始致力于 Aspell 。它在一九九八年以 Kspell 这个名称第一次被发行，但是因为 KDE 的拼字检查工程也称作为 Kspell ，他就将名称改为 Aspell 。
During the next years,Kevin dedicated a lot of his time to the rather intensive development of Aspell. Concepts were tried,overhauled and sometimes discarded. He for instance sought to create one generic interface for all spell checkers present on the system called Pspell. Unfortunately it complicated rather than simplified life of everyone involved. Therefore Pspell hs vanished into Aspell since version 0.5.
- Therefore Pspell hs vanished + Therefore Pspell has vanished
在下一年， Kevin 付出了许多他的时间给 Aspell 更加密集的开发〔过程〕。〔许多〕观念都被测试、整理以及有时候被舍弃。例如他寻求创造一个称为 Pspell 的原生介面（generic interface），给目前存在系统内的所有拼字检查器〔使用〕。不幸的是，它把所有牵扯进来的每一个人的生活弄得更加复杂而不是简单。因此 Pspell 从 Aspell 0.5 版之后就消失了。
Something else he put a lot of effort in were generating better word lists based on the ones provided with Ispell. Very carefully he separated the English lists into British,American and Canadian spelling. The results of that work are also published separately. [9]
他付出了很大努力的其他事情还有，根据 Ispell 所提供的那个，制作出更好的字汇列表（word list）。他很仔细地将英文列表分为英国、美国和加拿大的拼法（spelling）。那项工作的结果也被个别地加以公开。 [9]
After the August 2002 release of GNU Aspell 0.5,Aspell is now seeking to replace Ispell especially on GNU/Linux distributions. Given its pretty impressive track record,it seems like this will merely be a matter of time.
在二○○二年八月发行 GNU Aspell 0.5 之后， Aspell 现在正寻求特别是在 GNU/Linux 散布件上替换掉 Ispell 。由于它相当令人印象深刻的追踪记录（track record），看起来这将只是时间问题而已。
GNU Aspell cannot only be used directly as a spell checking program with nice ncurses user interface,it also allows being linked by other programs as a library. And the suggestions made by GNU Aspell are significantly better than those of Ispell or those by Netscape 4.0 or Microsoft Word 97. To quantify this,Kevin developed a test environment that is available along with the results it created on the GNU Aspell web page. [7]
GNU Aspell 不只可以极佳的 ncurses 使用者介面，而作为拼字检查程序被使用，它也允许被其他程序作为程序库而被连结。同时 GNU Aspell 所作出的建议也比那些由 Ispell 或 Netscape 4.0 或 Microsoft Word 97 所作出的更好。 Kevin 为了将这〔更好的情形〕定量地表示而开发了一个测试环境，〔这环境〕与它所作出的结果都可以在 GNU Aspell 网页 [7] 上取得。
It appears that those tests were only made for the English language,however,even if word lists for other languages exist. For these languages it would probably be useful to find native speakers who would be willing to come up with similar tests. But even if you are just a normal user you can improve the results,because GNU Aspell learns from the mistakes users make.
然而，那些测试好像只有为英语文而作〔的部份〕，即使字汇列表也存在有其他的语文。对于这些语文，找一些想要提供类似测试的以它们作为母语的使用者可能比较有用。但即使你只是个一般的使用者，你〔也〕可以改进这些〔作出的建议〕结果，因为 GNU Aspell 会从使用者〔修正〕的错误中学习。
Whether used as a program or linked to as a library,GNU Aspell is multi-process aware. Personal dictionaries of a user are available to all Aspell process of that user and changes are automatically being propagated between the GNU Aspell processes. Any user can have several personal dictionaries,though.
不管是作为一个程序使用或作为程序库连接， GNU Aspell 都可察觉多进程〔的使用〕（multi-process aware）。一个使用者的个人字典可以为那个使用者的所有 Aspell 进程所取得，而且〔任何〕改变都会自动地在〔所有〕的 GNU Aspell 进程间互相增殖（propagated）。尽管如此，任何一个使用者都可以拥有数个个人字典。
In order to keep the memory usage acceptable with all these extended capabilities,all GNU Aspell running on one system share the general/common dictionaries. The price GNU Aspell still had to pay for its extended features are a higher memory profile than Ispell.
为了保持这个记忆的使用（memory usage）对于所有的扩充功能（extended capabilities）都是可以接受的，所有在一个系统内执行的 GNU Aspell 〔都〕分享一般／通常的字典。 GNU Aspell 为了它的扩充功能仍旧必须要付出的代价是，比起 Ispell 而言较高的记忆体〔使用量〕侧写（memory profile）。
This might also be caused by the circumstance that Ispell supports the so-called "Affix Compression" and GNU Aspell currently does not. Affix compression works because many words consist of one base word combined with different affixes. So the final word is built by one base word with an infix,prefix or postfix.
这也可能是由于 Ispell 支援所谓的「字缀压缩（Affix Compression）」，而 GNU Aspell 目前并没有〔支援〕的情况所造成。字缀压缩之所以有用，是因为许多字是由一个字根（base word）与不同的词缀（affixes）组合而成。所以最后〔组合而成〕的字是由一个字根和一个字中（infix）、字首（prefix）或字尾（postfix）所建构出。【译注：字根的概念相当于中文的部首（radical）；词缀则是如偏旁之类的中文字构成元素。】
Word lists with affix compression contain the base word with possible affixes. The English words "alarm alarms alarmed alarming" might for instance be compressed to "alarm/SDG". Especially for languages with massive affixation (like German,for example) this might make quite some difference.
具有字缀压缩的字汇列表包含有字根及其可能的字缀。以英文字「alarm alarms alarmed alarming」为例，可能会被压缩成「alarm/SDG」。这特别是对具有大量词缀的语文（举例来说，像是德文），可能会造成相当大的〔记忆体侧写〕差异。
Although GNU Aspell is geared towards multi-process enviroments,developers should note that it should not be considered "Thread Safe" yet. Achieving this is currently quite high on the priority list.
虽然 GNU Aspell 已经搭上了多进程环境（multi-process enviroments），但开发者应该注意：还不应该认为它已经是「线程安全（Thread Safe）」的了。实现这个〔目标〕目前在列表中具有很高的优先。
Other items are work on the manual,adaptation to the GNU coding standards,completion of UTF-8 support,support for dynamically loadable filters and writing a C++ interface. Also customizing the ispell.el EMACS module is yet to be done.
其他的项目有：在使用手册上的工作、调整到《GNU 源码撰写标准》、完成 UTF-8 的支援、支援动态载入过滤器以及撰写一个 C++ 介面。还有客户化 ispell.el EMACS 模组〔的工作〕也还没完成。
And finally Kevin Atkinson plans to import the affix compression code written by Kevin Hendricks for the OpenOffice lingucomponent into GNU Aspell.
最后 Kevin Atkinson 计划着要引入由 Kevin Hendricks 为了 OpenOffice 语文元件（lingucomponent）所撰写的词缀压缩码（affix compression code）到 GNU Aspell 中。
But even if there is still quite some work going on with GNU Aspell,this should not discourage anyone from using it already,because since version 0.50.2,GNU Aspell certainly is up to par with other spell checkers currently being used. Although Kevin did not feel he should name it version 1.0 yet,which is rather typical for Free Software developers.
但是就算 GNU Aspell 还有相当多的工作需要进行，这〔消息〕应该不会让任何人泄气，因而不现在就使用它，因为从 0.50.2 版开始， GNU Aspell 无疑地〔已经〕与目前使用中的其他拼字检查器具有相同等级。虽然 Kevin 还不觉得他应该将它命名为 1.0 版 -- 但那是其他自由软件开发者很典型地〔在这种品质下〕会做的。
It should be noted that Kevin Atkinson essentially did all the work on GNU Aspell himself. But he would certainly appreciate help and if you are looking for an interesting project that will be around and used by many users for a long time to make your name immortal,this is certainly a good possibility.
值得一提的是， Kevin Atkinson 在本质上由他自己做了在 GNU Aspell 上的所有工作。但他肯定会感谢帮忙，而且如果你正在寻找一个可以在很长的时间被许多人围绕和使用的有趣工程，并使得你的名字永垂不朽，这无疑是一个很好的可能。
Experienced readers of the Brave GNU World will have noticed that so far no word about the license status of GNU Aspell has been said,although it should be clear that GNU Aspell is Free Software,since it is part of the GNU Project.
经验老到的《勇敢 GNU 世界》读者应该已经注意到到目前为止，都还没有谈到有关 GNU Aspell 的许可证状态，虽然因为 GNU Aspell 是 GNU 工程的一部份，所以很清楚地〔知道它〕是自由软件。
GNU Aspell has originally been released by Kevin Atkinson himself under the GNU Lesser General Public License (LGPL). In order to secure the legal maintainability and therefore the long-term survival of his project,Kevin assigned his rights to the Free Software Foundation North America,making it the fiduciary for his interests.
GNU Aspell 一开始是由 Kevin Atkinson 他自己在 GNU Lesser General Public License (LGPL) 下发行。为了保证法律维护的安全，并且使他的工程可以因此获得长期的生存。 Kevin 将他的权利转让给北美自由软件基金会，使它（指基金会）成为他的利益的受托者。
Despite the fact that the FSF North America would consider it more useful to release GNU Aspell under the GNU General Public License (GPL),it continues to release GNU Aspell under the GNU Lesser General Public License because Kevin considered this very important to him.
尽管北美自由软件基金会认为将 GNU Aspell 在 GNU General Public License (GPL) 下发行会更有用处， GNU Aspell 仍将会在 GNU Lesser General Public License 下发行，因为 Kevin 认为这对他来说非常重要。
There quite a bit of reasoning behind these different positions that is not only interesting but also important,so I would like to try and shed some light on them.
有些相当量的论理在这些不同立场（positions）后面，〔这些论理〕不只有趣而且也很重要，所以我想要试着阐明它们。
要用 GPL 还是 LGPL ？
Kevin Atkinson wants to see GNU Aspell become the de-facto spell checker for GNU/Linux and other Free operating systems. Especially in projects such as OpenOffice and Mozilla he would like to see adaption of GNU Aspell.
Kevin Atkinson 想要看到 GNU Aspell 成为给 GNU/Linux 和其他的自由作业系统的 那 事实上的拼字检查器。特别是在像是 OpenOffice 和 Mozilla 这样的工程中，他想要看到 GNU Aspell 为〔它们〕所适用。
Since there are also proprietary spin-offs of OpenOffice and Mozilla,he is afraid that the projects won't use GNU Aspell at all if it was licensed under the GNU GPL.
因为 OpenOffice 和 Mozilla 还有私权的副产品存在，他害怕如果 GNU Aspell 是以 GNU GPL 作为许可，这些工程将根本不会使用它。
Of course the proprietary spin-offs could use GNU Aspell through an external program execution. This might be less effective,but it is a possible alternative.
私权的副产品当然可以经由一个外部程序的执行而使用 GNU Aspell 。这可能会〔导致〕较没有效能，但它是一个可行的替代方式。
So Kevins position is largely based on his wish to see GNU Aspell spread as much as possible and the fear that including GNU Aspell under the GNU General Public License would create too many problems for projects with proprietary spin-offs.
所以 Kevin 的立场很大一部份是根据他想要看到 GNU Aspell 在可能的范围内散播地愈多愈好的意愿，以及害怕将 GNU Aspell 包括在 GNU General Public License 下，将会产生给具有私权副产品的工程〔使用时〕的过多问题。
Undoubtedly it would be very good if GNU Aspell was widely adopted by many people since it would bring all these users freedom in their spell checking. But there is also another side to the issue.
毫无疑问地，如果 GNU Aspell 可以被许多人由于「它会给所有这些使用者在他们的拼字检查上带来自由」的缘故而广泛地采用是很好的。但这个议题还有另外一面。
One of the fundamental understandings on which the GNU General Public License is built is that there will always be people who are willing to profit even at someone elses expense. And you can not rely on the goodness at heart of companies and managers alone.
GNU General Public License 所以被建立的其中一个基本的认识是，总是会有人们即使是在以某个其他人作为代价的状况下，仍将乐意地〔不顾他人死活地〕获利。因此你不能单独地依赖公司和管理者内心的善良。【译注：俗话说「杀头的生意有人做，赔本的生意没人干。」】
Or shortly: Those who do not defend their freedom are bound to lose it!
简而言之：那些不捍卫着他们的自由的人必然会失去它！
The GNU Lesser General Public License (LGPL) is a modification of the GPL,purposefully limiting the protection of freedom in one significant aspect: It allows to link the code with proprietary applications.
GNU Lesser General Public License (LGPL) 是一种 GPL 的修订，目的是以限制「自由的保护」以达成一种有意义的形势（aspect）：它允许将〔在它之下发行的程序〕码与私权应用〔程序〕进行连接。
In the past this has often been useful or even necessary and central components such as the GNU C library have been published under the LGPL.
在过去，这通常是有用甚至是必要的，而且像是 GNU C 程序库之类的中心元件〔都〕是以 LGPL 公开的。
Free Software offers a new paradigm for software with many advantages. Fast and "predatory" profits sought by some companies are not one of its properties; the rewards and advantages of Free Software are more in the mid- to long-term.
自由软件提供了一个具有许多优点的新的软件典型（paradigm）。一些公司所追求的迅速以及「弱肉强食（predatory）」并不是它的特性；自由软件的回报和优点比起中长期〔所能给予〕的还要更多。
By burning large amounts of money,proprietary software can sometimes create problems for Free Software in the short term to push Free Software out of or ban it from an area in order to protect or gain a monopoly. This may then be very hard to undo later.
经由投入大笔的资金，私权软件有时候可以在短期内对自由软件造成问题，经由将自由软件推开或是禁止它〔涉足）到某个领域，以保护或获得垄断〔地位〕。这也许接下来在稍后要扳回一程（to undo）会非常困难。
When people choose their software based on short-term,technical features because they have not understood that software always has a macro-economical,cultural,social and ethical component,that danger increases. Because someone not understanding the bigger gestalt will switch back to proprietary software as quickly as he or she tried Free Software.
当人们还没有了解到软件总是有一个总体经济的（macro-economical）、文化的、社会的和道德的组成，并因而基于短期的技术功能来选择他们的软件时，那危险就增大。因为一个不了解这较大形态〔的「整体」概念〕的人，将会如同他或她嚐试自由软件般地快速，切回（switch back）〔使用〕私权软件。
Within the Free Software scene,we're seeing that some people are more involved with the Free Software mentality and others heading more towards Open Source. This shows that even within the classic scene of Free Software this understanding is not yet fully developed. Outside of this group things look even worse.
在自由软件的活动领域内，我们正看到一些人与自由软件的精神更加契合（more involved），而其他人则朝着开放源码〔的方向前进〕。这表示即使在传统的自由软件活动领域内，这个理解也还没有完全地发展。在这群组（group）之外事情看起来甚至更糟。
As long as the understanding of these questions is not common knowledge,Free Software is facing a problem: Proprietary software can exploit unprotected or too weakly protected Free Software almost totally,whereas the opposite is clearly not true.
只要〔对于〕这些问题的理解还不是一般知识，自由软件就面临到一个问题：私权软件可以几乎完全地，不正当地利用未受保护的或过弱保护的自由软件，同时反过来说则很清楚地并不成立。
Unsatisfactory protection of Free Software creates an imbalance favoring proprietary software. This at least makes it harder for Free Software to gain also a short-term,technical advantage over proprietary software.
自由软件的不符合要求的保护（Unsatisfactory protection）创造了一个赞同私权软件的不均衡状态。这样至少会使得自由软件更难取得短期的，超越私权软件的技术优势。
As already mentioned,Free Software is a new paradigm,it creates a new market with new rules and mechanisms. Every market has its rules and it is important for all participants to uphold and protect these rules in order to protect the individual and the market as a whole.
如同〔先前〕已经提到过的，自由软件是一个新的典型，它创造了一个具有新的规则和机制（mechanisms）的新市场。每一个市场〔都〕有着它（自己〕规则，而且所有的参与者高举并保护这些规则，以保护作为一个整体的〔参与〕个体和市场是重要的。
The market of Free Software is still being built and in a somewhat early phase. The majority of participants has not yet fully understood the rules and mechanisms,although most of them abide them.
自由软件市场仍然在建构中，并且是处于某种程度的早期阶段。参与者的大多数还没有完全了解这些规则和机制，虽然他们大多忍受它们。
Considering what has been said before,it is not surprising that the GNU General Public License with its strong protection of freedom has become the predominating license,under which more than 50% of all Free Software is published.
考虑到先前已经说过的，具有对自由强保护（strong protection）的 GNU General Public License 成为占主导地位的许可证并不让人惊讶，在它之下有超过全部自由软件的百分之五十被公开。
To me this seems like it is the natural consequence of the mechanisms at work and it is also strong evidence that the GPL hasn't taken over the market,it rather created it. This means that the market of Free Software has shaped itself largely because of and around the GNU General Public License.
对我来说这看起来像是，它是作用中的机制的自然结果，并且它也是 GPL 并没有接管这个有一点是它所创造的市场的有力证据。这表示自由软件市场由于以及围绕着 GNU General Public License 而很大〔程度〕地形塑了它本身。
To prevent misunderstandings I'd like to emphasize that this does not mean the GPL is the only acceptable license. Other licenses like the LGPL or licenses with even fever protection like the BSD style licenses are also a part of Free Software and can at times even be the most useful choice.
为了避免误解，我想要强调这并不表示 GPL 是唯一可以接受的许可证。其他的许可证像是 LGPL ，或是甚至更加保护的许可证像是 BSD 风格的许可证，也都是自由软件的一部份，甚至〔它们〕在有时候可以成为最有用的选择。
The question whether weak protection is the best choice for GNU Aspell is what started this article. From the perspective of the FSF,things look different than they do for the author.
正是哪一种弱保护（weak protection）是 GNU Aspell 的最佳选择的问题开始了这篇文章。从 FSF 的观点来看，事情看起来和作者所见的并不相同。
Thanks to Ispell,Free Software already has a widely established spell checker that may have its weaknesses,but it was able to fill the gap for many years with a non-protective license.
感谢 Ispell 〔所留下的好的和坏的影响〕，自由软件已经有了一个可能具有它的弱点的广泛建立的拼字检查器，但是如果以一个非保护性的许可证〔发行的话〕，它可以将这个缺口填满。
Building upon this,GNU Aspell could now give every Free Software package dealing with text a significant technical advantage over similar proprietary products in order to balance the short-term power relationship in favor of Free Software.
依此作为基础而建构出， GNU Aspell 现在可以给予每一个自由软件包处理文字〔的能力〕，其方式并且比类似的私权产品具有重大的技术优势。这是为了平衡短期内有利于自由软件的有力关系。
Also it would increase the incentive to release projects based upon GNU Aspell as Free Software.
它也会增加将工程以 GNU Aspell 为基础而发行为自由软件的动机。
In reference to the projects OpenOffice and Mozilla,the possible problems of which were a major reason for Kevin to prefer the LGPL,it should be noted that there seems to be no striking reason to release the commercial versions as proprietary software.
就有关 OpenOffice 和 Mozilla 工程〔而言〕，其可能〔造成〕的问题是 Kevin 选择 LGPL 的一个主要原因，值得注意的是，似乎并没有显着的理由〔让我们相信〕，发行商业软件非得一定是要作为私权软件〔才可行〕。
Especially with OpenOffice the major reasons for people to buy the proprietary StarOffice seems to be the apparently very good handbook,the support and the liability. None of these depends on StarOffice being proprietary,they wouldn't change if it was released as Free Software.
特别是对 OpenOffice 来说，人们购买私权的 StarOffice 的主要原因似乎是显然〔做得〕相当好的手册、〔良好的〕支援（售后服务）和容易〔上手使用〕。这些〔原因〕中没有一个是由于 StarOffice 是私权的〔软件的原因〕，即使它是以自由软件来发行，它们也不会改变。
If somebody thinks they really have to create a proprietary version of one of these projects,of course they could. But we as the Free Software community should as ourselves why we would want to give them GNU Aspell to produce better proprietary software.
如果有人认为他们真的必须创造出一个这些工程中，其中一个的私权版本，当然他们是可以〔这么做〕的。但是我们作为自由软件社团就应该依照我们自身〔的想法和目标〕，为什么我们会想要给他们 GNU Aspell 去做出一个更好的私权软件呢。
Enough of this topic,I hope I've at least managed to shed some light from different angles on this sometimes pretty complex topic.
对这个题目应该是足够了，我希望我已经至少从不同的角度设法阐明了这个有时候相当复杂的题目。
If you are interested in reading more about these questions or would like to see it covered from a different angle,reading the article by Richard Stallman on the GNU web page is recommended. [10]
如果你有兴趣阅读更多有关这些问题，或是想从不同的角度来掌握它时，〔那么〕建议〔你〕阅读在 GNU 网页上，由理查德．斯多尔曼所撰写的文章。 [10]
Gnutemberg！ 自由文档资料库（GFDD）
Simo Sorc,the Italian translator of the Brave GNU World,recommended the "Gnutemberg! Free Documentation Database" (GFDD) project [11] from Italy.
Simo Sorc ，《勇敢 GNU 世界》的意大利语文翻译，从意大利建议了「Gnutemberg！ 自由文档资料库（GFDD）」工程。 [11]
Being part of the "Gnutemberg!" project,[12] GFDD aims to create and maintain a database of Free Documentation. In order to ensure its freedom,only documents published under a FSF approved Free Documentation License [13] are being added to the database.
身为「Gnutemberg！」工程的一部份， [12] GFDD 将目标放在创造并且维护一个『自由文档』的资料库。为了确保它的自由，只有在 FSF 所认可的 Free Documentation License [13] 下所出版的文档才会被加入到这个资料库。
The technical implementation is done in PHP and Postgresql,based upon the "Dublin Core Metadata Element Set" abd tge "Open Source Metadata Framework." [14] Naturally,all code is being published as Free Software under the GNU General Public License.
技术上的实作是以 PHP 和 Postgresql 所完成，奠基于「都柏林核心诠释资料元素集（Dublin Core Metadata Element Set）」和「开源诠释资料架构（Open Source Metadata Framework）」。 [14] 自然地，所有的代码都在 GNU General Public License 下被公开为自由软件。
A user can publish documentation or translate it and with a search engine it is possible to search for fields like author,publication date,title,language,translations,ISBN No.,pages,price or other notes.
使用者可以公开文档或是翻译它，同时〔因为〕具有一个搜寻引擎，〔所以〕可以搜寻像是作者、出版日期、标题、语文、翻译、 ISBN 号码、页数、价钱或其他可供记录的栏位。
The project is being maintained by Gaetano Paolone,Marco Presi,Simone Merli,Marco Milanesi,Alceste Scalas and Donato Molino,but they are still looking for help on both the technical and the content side.
这工程现在是由 Gaetano Paolone 、 Marco Presi 、 Simone Merli 、 Marco Milanesi 、 Alceste Scalas 和 Donato Molino 所维护，但是他们还在寻找技术和内容两方面的帮忙。
Sice documentation is an incredibly important and much too often neglected area,I hope that they will find many volunteers.
Sice documentation is an Since documentation is an
由于文档是个极为重要且太过经常地被忽视的领域，我希望他们将可以找到许多志愿者。
下回见
That should be enough for this month; unless other catastrophes happen,the next column will arrive next month.
这个月应该足够了；除非还有其他的灾难发生，〔不然〕下个专栏将会在下个月份出现。
Of course I cannot close the column without having asked for lots of Feedback,information,ideas,questions or hints about potentially interesting projects by mail. [1]
当然，我不能在没有经由邮件询问许多有关的具有潜力的有趣工程的反馈、信息、想法、问题或提示的情形下，结束这个专栏。 [1] 【译注：请以英文或德文撰写邮件，其他的语言无法被了解；或以中文送到本文翻译。】
原文链接：/postgresql/197470.html