[CA | CN | DE | EN | FR | JA | ES | KO | PT | ZH]

Welcome to another issue of the Brave GNU World — hopefully not too many readers were affected by pyDDR fever and have blamed their sore muscles on the column.

欢迎来到又一期的《勇敢 GNU 世界》 — 希望没有太多读者感染到「pyDDR 热」，并且向这专栏抱怨著他们酸痛的肌肉。

给自由软件用的驱动程序（Drivers）

One particular situation is probably among the most difficult ones for many users of Free Software operating systems, especially when pure users are concerned. Assembling and installing the new hardware was quickly done, but the included drivers are only for Windows.

可能在对「许多自由软件操作系统使用者的许多困难点」上的一个特别的情形，特别是纯使用者所关切的是：组合（Assembling）和安装（installing）新硬件时很快就完成了，但包含的驱动程序〔却〕只有给 Windows 〔使用〕。

Unless you've spent significant time on internet research before buying hardware, so you could make an informed decision which hardware to buy, now precious hours are lost trying to locate the right driver. In especially unfortunate cases you will even come to realize that this particular piece of hardware is not supported at all. Outdated information, unmaintained links and discontinued development of some drivers make the situation worse.

除非在购买硬件之前，你已经花了许多时间在互联网上搜寻〈这样子你可以作出被告知有关於哪个硬件可以买〔的信息〕的决定〉，〔否则〕现在先前的几个小时已经在试著找出正确的驱动程序中浪费掉了。在特别不幸的例子中，你甚至将会最后了解到：这个特殊的硬件根本就不被支持。某些驱动程序的过时信息、没有维护的链接以及不再持续的开发，〔都〕使得这情况〔变得〕更差。

Strictly speaking, this is the fault of hardware vendors that are often not caring about selling their hardware outside the Windows monopoly and don't take customers outside that monopoly seriously.

严格地说，这是硬件卖方的错〈他们经常对於将硬件卖到 Windows 垄断〔范围〕外不在乎，而且对 Windows 垄断〔范围〕外的顾客并不当真〉。

In fact often not every hardware vendor would even have to develop each and every driver themselves. Often there are volunteers to help developing drivers in their own interest. But in many cases, these developers only receive very limited support. Even worse. Some hardware vendors actively try to defend themselves against this attempt at increasing their market potential.

事实上，经常也并不是每一个硬件的卖方，都能够自行开发每一份驱动程序。经常会有使用者基於他们自己的兴趣来开发驱动程序。但是许多的状况中，这些开发者只有获得非常有限的支持。更糟的是：一些硬件卖方积极地护卫著他们自己，免受这个「可以增加他们的市场利基（potential）」的试图的侵扰。

Of course there are also more and more exceptions to that rule, some hardware vendors are beginning to understand the potential of the Free Software market and either try to provide drivers themselves or further their development. Right now these are more or less exceptions confirming the rule, however. But drivers written and distributed exclusively by hardware vendors are really only the second best solution.

当然，对於那个法则而言，已经有愈来愈多的例外了：一些硬件卖方开始了解到自由软件市场〔可以带来〕的可能性，并且开始自己提供驱动程序，或是更进一步他们的开发。然而，就目前来说，这些或多或少〔都只是再次〕确认这法则的例外〔罢了〕。但是由硬件卖方独占性地编写以及散布驱动程序，真的只是次佳的解决方案〔而已〕。

Better would be a platform on which vendors develop and maintain drivers together with interested companies and volunteers. This will not only help keeping drivers maintained even years after the production has been discontinued, it also becomes possible to use synergies.

较好〔的方式〕是有一个平台（platform），可以使卖方与有兴趣的公司和志愿者，一起开发以及维护驱动程序。这将不只帮助了「驱动程序即使在这项产品不再延续后的数年后，〔仍然〕受到维护」，「使用合成〔效果〕（synergies）【译注：指的是独立的个别的效果，经由互动或合作而产生全新或进一步的效果】」也成为可能。

Many boards by different hardware vendors use identical chipsets. So a lot of multiple work could be avoided. Also developing drivers for multiple operating systems or allowing porting to a new hard- or software-platform — creating a new sales market — would be possible.

许多由不同硬件卖方〔所做出〕的电路板（boards）使用了相同的晶片组（chipsets）。所以大量的重覆（multiple）工作可以被避免。同时，为多重操作系统开发驱动程序，或是允许移殖（porting）到一个新的硬件或软件平台 — 因而创造出一个新的销售市场 — 也将成为可能。

Hardware vendors willing to enter such a process would see a much increased usability for their hardware in combination with a higher customer retention based upon the knowledge that support will not be suddenly discontinued in 1-2 years. Not to mention that the potential market would grow.

愿意进入这样一个过程（process）的硬件卖方，将会看到他们的硬件增快得多的使用性，这是由於〔硬件〕与「奠基於支持将不会在一二年内突然地不再延续的认识，因而有著较高的顾客向心力（retention）」〔所造成〕的混合效果。更不用提到潜在的市场将会成长了。

The entry portal for such a system would have to be a database, which allows searching for products of vendors in order to know about the existing drivers and their status. So users would directly find out whether drivers exist and whether they are for instance stable, only suited for developers, orphaned and/or outdated.

针对一个这样子的系统的进入点（entry portal）将会需要一个资料库，来允许搜寻卖方的产品，以知道关於现有的驱动程序以及它们的状态。因此使用者才能直接地发现驱动程序是否存在？以及它们是否〔只是某些〕状况下稳定？只适合给开发者、已经成了孤儿以及／或过时了。

Florian Duraffourg from France calls to build such a database.

来自法国的 Florian Duraffourg 徵求〔志愿者〕来建立起这样一个资料库。

给自由软件驱动程序使用的资料库

Based on PHP, HTML and MySQL, Florian Duraffourg is aiming at creating a driver database [5] specifically for GNU/Linux and GNU/HURD. Anyone looking for a driver should then be able to find out whether a driver exists and which status it has.

Florian Duraffourg 基於 PHP 、 HTML 和 MySQL ，将目标放在创作出一个特别针对 GNU/Linux 和 GNU/HURD 的驱动程序资料库（driver database） [5] 。任何正在寻找一支驱动程序的人应该到时候就可以知道是否有这一支驱动程序存在，以及它的状态为何了。

By means of a simple Web-access, this would also allow checking directly before buying hardware in a store to see how well it is supported. Florian also considers allowing direct server access, so accessing the database would become possible without HTML and browser; for instance with a simple client program on a wireless device like a PDA or mobile telephone.

经由简单的网络存取（Web-access），这也允许了〔人们〕在商店里购买硬件之前，直接检查看看它被支持的程度如何。 Florian 也考虑了允许直接的伺服器存取，这样一来即使没有了 HTML 和浏览器，存取资料库也将成为可能；举例来说：在像是 PDA 或行动电话一般的无线装置上，提供一支客户端程序。

Thoughts and plans around this program are still under development, so Florian still doesn't have a final domain or dedicated server. Among his considerations was also to mirror all drivers on a dedicated FTP server to slow linkrot and loss of information.

围绕著这支程序的想法和打算仍然处在发展〔阶段〕，所以 Florian 仍然还没有最终的域名（domain）或一台专属的伺服器。在他的考虑中也有：镜射在一台专属 FTP 伺服器上的所有驱动程序以减缓信息的失效链接（linkrot）以及漏失〔的程度〕。

Right now his biggest concern is finding volunteers that would like to contribute to development, designing the web site, translating documents into different languages and assembling the driver database.

目前，他最大的关切点在於寻找愿意贡献开发、设计网站、翻译文档到不同语言、以及组装起驱动程序资料库的志愿者。

This seems like an extremely useful project and I hope that many volunteers will join the effort. Also some hardware vendors will hopefully recognize their chance and support this project directly.

这看起来似乎是个极为有用的工程，因此我希望能有许多志愿者加入这份努力。也希望有一些硬件卖方能够认识到它们〔由此可以获得〕的机会，并且直接地支持这个工程。

Those interested in finding business models around Free Software should also have come to realize that another very interesting opportunity has presented itself in this field.

那些有兴趣找出环绕著自由软件商业模型〔的人〕，应该也会渐渐了解到：另一个非常有趣的机会已经在这个领域中将它自己展示出来。

Should a store or mail order business strategically orient itself towards hardware supported by Free Software like GNU/Linux, this added value would certainly be worth a lot to many people.

商家或是邮购公司是否会策略性地将自己导入到被像是 GNU/Linux 一般的自由软件所支持的硬件？〔考虑到〕这附加价值肯定会对许多人〔来说〕非常值得。

Customers would know that they could shop as much as they wanted without having to worry about lack of support. As a kind of additional service they could even get a CD with the right drivers for the hardware they just bought.

消费者将会知道他们可以买来愈多他们想要的〔东西〕，而不必担心缺乏支持。作为一种额外的服务，他们甚至可以拿到一张有著他们刚刚购买的硬件的驱动程序 CD 。

And due to customer retention they would be likely to buy their other hardware that is often uncritical in terms of being supported, like hard disks, cases, CPUs, memory from that company. So by supporting the project above even the sales-oriented businesses could gain substantial additional value.

同时，由於顾客向心力〔使然〕，他们〔也比较〕可能购买那公司的其它硬件〈那些以被支持的角度来看经常并不重要的〉，像是硬碟、〔主机〕外壳、 CPUs 、记忆体…。所以经由支持上述的工程，甚至销售导向的事业体也可以获取大量的附加价值。

libQGLViewer （3D 阅览程序库）

The libQGLViewer [6] project by Gilles Debunne has created a 3D viewer library that makes development of 3D applications easier and faster.

由 Gilles Debunne 所完成的 libQGLViewer [6] 工程已经创作出了一个 3D 阅览程序库（viewer library），它使得开发 3D 应用程序〔得以〕更简单，也更快速。

According to Gilles, it was a major problem for development of 3D applications that tools like a moving camera, snapshots, simple coordinate systems — although classical and well-known — are rarely part of 3D standard libraries. Even GLUT is using a much lower abstraction level.

根据 Gilles ，开发 3D 应用程序的一个主要问题在於：像是移动摄影机（moving camera）、快照（snapshots）、简易座标系统（simple coordinate systems） — 虽然经典且〔为人所〕熟知 — 都很少是 3D 标准程序库的一部份。即便是 GLUT 也是使用一个较为低阶的抽象层。

In comparison, libQGLViewer provides camera and objects, which can be freely moved with the mouse within a 3D scenario. Also saving snapshots in different formats including vector-based EPS is possible.

比较之下， libQGLViewer 提供了摄影机和物件，它们都可以在 3D 场景（scenario）中，以鼠标任意地移动。同时，以不同格式储存快照〈其中包括以向量为基础的 EPS〉也是可能的。

The project is based on the QGLWidget class of the Qt library and solely for the purpose of showing the refresh rate it is still using GLUT. This dependency will disappear with the move to Qt 3.1, however. The libQGLViewer itself was — like the Qt library — written in C++.

这工程是奠基於 Qt 程序库中的 QGLWidget 类别（class），它也仍然使用 GLUT ，不过这单单只是为了显示更新率（refresh rate）〔而已〕。然而，这个相依性（dependency）将会在转移到 Qt 3.1 之后消失。 libQGLViewer 它本身 — 如同 Qt 程序库 — 是以 C++ 编写而成的。

The author is working in a graphics laboratory in which everyone was creating their own 3D viewer in the past. Each solution had its strengths, but none was complete. This is what Gilles sought to change. Also he is teaching students and sought to allow them to get creative more easily without having to spend much time on the infrastructure.

作者正在致力於一个图形制造厂（graphics laboratory），有了它〔之后〕，未来每一个人都可以创作出他们自己的 3D 阅览器。〔以前〕每一个解决方案都有著它的强处，但却没有一个是完整的。这就是 Gilles 寻求著要改变的〔地方〕。他也教授学生，并且试图允许他们可以更容易地发挥创意（to get creative），而不用必须花费许多时间在基础建设上。

Therefore Gilles began developing this project. Originally he estimated it to be a weeks worth of work, but in the end it turned out to be a full-time project for a whole year. By now he considers the project to be finished, only the documentation could still need some polishing by a native English speaker. Also some feedback for the installation routine would be welcome.

因此 Gilles 开始了开发这项工程。一开始他估计它是个值上几个星期的工作，但最后它却变成了整整一年的全时工程。现在他认为工程将要结束了，只差了文档仍然需要位英语母语者的一些修饰。关於安装常式（routine）的一些反馈也是欢迎的。

Declaring the project finished was a conscious decision, by the way. His declared goal was to keep the viewer as general as possible without focussing on specific applications. Gilles is convinced to have reached that limit, so he decided to not add any more substantial new features.

顺道一提，宣布工程结束是个有意识的决定。他所宣布的目标在於，保持阅览器尽可能地一般化，而不是聚焦在特定的应用上。 Gilles 相信〔它〕已经达到了极限，所以他决定不再增加任何实质的新功能特色了。

According to its author, the most important advantages of the project are its clean, portable and carefully design API, also the library comes with complete documentation and a great amount of commented examples. This makes it possible to generate a simple 3D viewer within one minute and 10 lines of code.

根据它的作者，这工程最重要的优势在於它的清楚（clean）、可移殖性（portable）和仔细设计的应用程序介面（API），程序库也附有完整的文档，以及相当大量的注解过的例子。这使得它有可能可以在一分钟内，以十行程序码来制作出一个简单的 3D 阅览器。

Gilles also sought to emphasize what the libQGLViewer is not. It does not do 3D rendering, because its sole purpose is to provide the viewer — the "draw()" method remains the responsibility of the user and a lot of possibilities exist to generate the scenario. libQGLViewer then allows the user to enter these scenarios and move within them.

Gilles 也试图强调 libQGLViewer 不是什么。它并不做 3D 描绘（rendering），因为它唯一的目的在於提供阅览器 — "draw()" 方法（method）仍然是使用者的责任，而且制作出场景也还存在著许多可能性。 libQGLViewer 接著允许使用者进入这些场景，然后在它们之中移动。

The libQGLViewer is published as Free Software under the GNU General Public License (GPL). Apparently there were numerous requests to switch to the Lesser General Public License (LGPL) in order to also allow proprietary applications. For personal and political reasons Gilles decided to keep publishing the libQGLViewer under the GPL, however.

libQGLViewer 是在 GNU General Public License (GPL) 下作为自由软件而公开。显然地有许多切换到 Lesser General Public License (LGPL) 的要求，以为了〔使它〕也允许私权应用程序〔得以使用〕。然而基於个人以及政治因素， Gilles 决定了保持在 GPL 下公开 libQGLViewer 〔的作法〕。

Also he found the generally available information about licenses, possible change of licenses and multi-licensing to be incomplete and sometimes confusing. He is probaby not the only person feeling that way, so it might be useful to write a little introduction into the background.

他也发现了关於许可证、许可证的可能改变、以及「不完全，并且有时候〔造成〕混淆的多许可（multi-licensing）」的一般可以取得的信息。他可能并不是唯一那样子感觉到的人，因此写一点进入背景的介绍可能会是有用的。

介绍版权（Copyright）

In order to be able to understand the licenses, it helps to understand the background on which they are built. Licenses like the GNU General Public License (GPL) are Copyright-licenses, or Authorship right ("Droit d'Auteur") licenses. Even though the terms Copyright and Droit d'Auteur are almost the same for most practical purposes, some historic differences exist.

为了可以了解许可证，知道用来构建它们的背景会有帮助。像是 GNU General Public License (GPL) 的许可证是版权许可证（Copyright-licenses），或是「作者权（Authorship right ； Droit d'Auteur）许可证」【事实上 Authorship right 就语意上也可以翻译为著作权，但是因为目前我们已经把著作权视为作者权（著作人格权）和版权（著作财产权）的合称，因此还是避免采用这一个术语以免造成困扰】。即使版权和作者权对於大部份的实用目的而言几乎是一样的，〔它们之间〕仍然存在历史差异。

In order to understand these, one has to know that Copyright is an invention of the Gutenberg age, a result of inventing the printing press around 1476. Originally being a pure monopoly for publishers it wasn't intended to give authors any rights in their works. Only 1710 first authors can purchase rights in their own works.

为了了解这些，〔我们〕必须知道版权是 Gutenberg 时代的一项发明，〔是〕一个在大约一四七六年发明了印刷术（printing press）〔之后〕的结果【中国则更早了六百年】。一开始的状况是出版者的纯粹垄断〔情形〕，它〔当时〕也不是为了要给予作者关於他们作品的任何权利。只有到了一七一○年才第一次有作者购买了他们自己的作品的权利。

The idea of a fundamental right of the author in his or her work — the core of todays Droit d'Auteur — has been propagated mostly by German and French philosophers in the time before the French revolution and has first been implemented as a major achievement of the French revolution.

「作者拥有他或她的作品的基本权利（a fundamental right）」的想法 — 那是作者权的核心 — 在法国大革命前，已经在大部份的德国和法国哲学家中普及了，并且作为法国大革命的一项主要成就而首次地被加以实现（implemented）。

This established the Droit d'Auteur as a new legal tradition in order to replace the old, publisher-monopoly oriented system. Today, essentially the continental European countries are following the Droit d'Auteur tradition while the angloamerican area is still following the Copyright tradition.

这建立起了「作者权作为一项新的法律传统（legal tradition）」，以用来取代旧的〔传统〕，也就是「出版者垄断导向的体系」。今天，实质上欧洲大陆国家遵循著作者权传统， 而盎格鲁美洲地区【北美，包括美国和加拿大】仍然遵循著版权传统。

To create common international ground, there have been harmonizing processes and agreements that are commonly referred to by the cities of Berne and Stockholm in which they have come to pass in. Because of this, most issues are practically not different despite the very different basis. With one exception.

为了创造出「共同国际基点」（common international ground）【即，在两种不同体系之间建立起可以沟通互动的渠道】，〔因此〕在牵涉到的城市〈Berne 和 Stockholm〉〔之间〕有了调和的过程（harmonizing processes），和已经批准的协定（agreements）。因为这样，〔使得〕在非常不同的根基（basis）之外，大部份的〔相关〕议题在实用上并无不同。〔但〕有一个例外。

Contrary to Copyright, Droit d'Auteur knows a personality right of the author, which — like other human rights — is inalienable. Independent of what any contract says, the personality rights of the author can never be limited. In fact, a contract that is (seemingly or for real) trying to do this runs a risk of being declared invalid in court.

与版权相反的是，作者权认知作者的人格权（personality right） — 就像其它人权 — 是不可让渡的（inalienable）。独立於任何合约上所说〔的条款〕，作者的人格权永远不能受到限制。事实上，一份（似乎或是真的）试图这样做的合约，就是冒了在法庭上被宣布为无效的风险。【这应该以法律体系层次的角度来看，命令违反法律者无效；法律违反宪法者无效；甚至宪法违反基本人权者也是无效的。当然，许可证是属於合约的层次，是以法律作为基础的。】

Only the so-called exploitation rights are transferrable. There are single and exclusive exploitation rights; the proprietor of the exclusive exploitation rights can provide an unlimited amount of single exploitation rights and defend his rights in court. So the exclusive exploitation rights are for most practical purposes similar to the angloamerican Copyright.

只有所谓的利用权（exploitation rights）【现行所谓的著作财产权】是可以移转的。利用权有单一（single）以及独占（exclusive），独占利用权的所有人（proprietor）可以提供不限数量的单一利用权，并在法庭上捍卫他的权利。所以就大部份的实用目的〔来说〕，独占利用权相似於盎格鲁美洲的版权。

自由软件授权（Licensing）

So based upon these exclusive exploitation rights and/or the Copyright the owner of these rights can choose the license under which the software is distributed. In the case of Free Software that means choosing a Free Software license. [7]

所以根据这些独占利用权以及／或版权，这些权利的拥有者可以选择软件要在哪一个许可证下散布。以自由软件的例子来看，那表示选择一份自由软件许可证 [7] 。

As the owner of the exlusive exploitation rights/Copyright can issue an unlimited amount of single exploitation rights (and therefore licenses), it is of cause always possible to issue the same software under several licenses. Whether these licenses are Free Software licenses or proprietary makes no legal difference.

由於独占利用权／版权的拥有者可以发出（issue）不限数量的单一利用权（也因此「〔作出〕授权〔动作〕」），当然总是有可能「在数个不同许可证下」发出相同软件〔的授权〕。这些许可证是自由软件或是私权的许可证在法律上并无不同。

Should the exclusive exploitation rights be with several people, because a piece of software has several authors and they have not chosen to combine their rights with one fiduciary, for instance, of cause all of these authors must agree with the licensing.

当独占利用权属於数个人时〈举例来说：因为一个软件片段有著数位作者，而他们还没有选择要组合起他们的权利予单一的受托者〉，当然所有的作者都必须同意授权〔的条件〕。

So the license is given by means of the exclusive exploitation rights — which are more or less the same as the anglo-american Copyright — as a single exploitation right.

所以许可证是以独占利用权的方式 — 或多或少与盎格鲁美洲版权相同 — 以单一利用权来〔加以〕给出。

It should be understood that only the owner of the exclusive exploitation rights can also defend the license in court. Also relicensing may become practically impossible if a large number of authors has been working on a project.

应该要了解的是，也只有独占利用权的拥有者可以在法庭上捍卫许可证。另外，如果有很大数量的作者在一个工程中〔一起〕工作，再授权（relicensing）或许会变得不可能〔实行〕。

For this reason — as presented in Brave GNU World issue #48 [8] — the FSF Europe has published the Fiduciary Licence Agreement (FLA) [9] in February 2003.

为了这个理由 — 如同在《勇敢 GNU 世界》第四十八期中的陈述 [8] — 欧洲 FSF 已经在二○○三年二月出版了〈信托许可同意书〉（Fiduciary Licence Agreement ； FLA） [9] 。

关於 FLA 的问题

In reaction to the publication of the FLA, some questions were raise that should maybe be briefly addressed here.

反应了 FLA 的出版，一些或许应该要简短地在此说明的问题被提了出来。

One question raised a few times was whether the FLA should replace the GPL. That is of course not the case, because the GPL is one Copyright based license granted by means of the exclusive exploitation rights, while the FLA is dealing with transfer of exclusive exploitation rights, which is one level before the license.

一个提出了数次的问题是 FLA 是否应该〔用来〕取代 GPL 。那当然不是这样，因为 GPL 是一份基於版权，并以独占利用权的方式所授与的许可证，而 FLA 是在处理独占利用权移转〔的问题〕〈那是在「作出授权」的前一个层次〉。

Another question was with reference to the keeping the possibility open for the assigning party to do dual-licensing, since the FLA is retransferring an unlimited amount of single exploitation rights back to the author. The question raised was whether it would be possible to then enforce these licenses in court as the author is no longer holder of the exclusive exploitation rights.

另一个问题是有关於「〔是否要〕保持让渡团体（assigning party）做出双授权（dual-licensing）的可能性为开放〔的状态〕」，因为 FLA 再次地将「不限数量的单一利用权」移转给回作者。提出的问题是它是否有可能接著在法庭中强制〔执行〕这些许可证，因为作者已经不再是独占利用权的握有者（holder）了。

If you imagine this case, author A would assign her rights to the FSF Europe and give a single, proprietary license to company B with the contract clause of not passing this license and software on to third parties. Now company C is selling software in which the software of author A is obviously used in a proprietary way. What does this mean?

如果你想像这个例子，甲作者让渡了她的权利给欧洲 FSF ，并且给了一份单一、私权的授权给乙公司，合约中的条款有：不可转让此授权以及软件到第三团体。现在丙公司贩卖显然是甲作者以私权方式使用的软件。这表示什么？

There are two logical possibilities. Normally the software would be published under the GNU General Public License by the FSF Europe, so the first possibility would be that company C has violated the GPL by using the software proprietary. Of course the FSF Europe would investigate that. Only when company C provides written evidence that they did not take the GPL version, but rather the proprietary version of company B, they will be cleared of that suspicion.

有两种逻辑上的可能性。正常来说，软件会由欧洲 FSF 在 GNU General Public License 下公开，所以第一个可能性会是丙公司由於使用了软件私权而违反了 GPL 。欧洲 FSF 当然会调查那〔情形〕。只有当丙公司提供了〔指明了〕他们并没有拿了 GPL 版本的书面证据（written evidence），他们才能洗清那项质疑。

In that case, company B has violated its contract with author A, however. And the author of course still has the right to take legal steps against contract violation. So the author can take legal steps and cut the chain of transferral of rights in the transferral to company B.

然而如果是那样的话，乙公司就已经违反了它与甲作者的合约。作者当然仍然有权采取法律程序来对付合约违反〔情事〕。所以作者可以采取法律程序，并且切断转移到（transferral to）乙公司的转移链。

Of course I need to state explicitly that this will in doubt always require intensive checking by an accredited and fully trained lawyer, which I am not. But I do hope that I was successful in making the overall picture clearer to non-lawyers without upsetting the experts in legal issues with oversimplifying matters in their eyes.

当然我需要明确地声明将会受到质疑的这个〔状况〕，需要一位合格并受完整训练的律师的彻底检查，而我并不是。但我真的希望我〔已经〕成功地使整个的图像，对於不是律师的人〔变得〕较为清楚，〔同时〕没有使法律议题的专家，由於在他们眼光中过度简化的内容而感到不悦。

结语

Enough for this issue. As usual I am hoping for numerous suggestions, questions, comments and of course information about interesting projects and new developments to the usual address. [1]

本期足够了。如同往常，我希望能有许多关於有趣工程和新发展的建议、问题、意见、当然还有信息，〔寄〕送到往常的〔邮件〕地址 [1] 。