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

Welcome to another issue of the Brave GNU World. Since word processing is certainly among the most common users' needs, the following feature has been moved to the top. Hopefully this will also give especially "beginners" new perspectives.

歡迎再次來到《勇敢 GNU 世界》。由於「文書處理（word processing）」 肯定對於一般使用者來說最為需要，因此下述的專輯已經被擺到上頭。 希望這也將給予特別是「新手」一些新的觀點。 【為求優譯，中英文並陳將持續到下一期被發表之後； 在此期間，請不吝於提供對於本文翻譯的意見。】

preview-latex - 介紹

The history of TeX and therefore also LaTeX [5] goes back to Donald E. Knuth, undoubtedly one of the most important heads of computer science. Because of its capabilities and properties, LaTeX turned out to be the favorite solution for people in science and the computer area.

TeX 以及接著的 LaTeX [5] 的歷史可以追溯到 Donald E. Knuth， 【高德納 先生，目前是 Stanford 大學電腦科學系名譽教授， 《The Art of Computer Programming》這本經典演算法書籍的作者。】 這位無疑是電腦科學界最重要的巨頭之一。 由於它的能力（capabilities）和特性（properties）， LaTeX 最終成為在科學界和電腦界中最受歡迎的解決方案。

A major advantage of LaTeX is to allow an author to concentrate on the content without having to worry about details of display with every word. But also when it comes to typesetting mathematical equations of any complexity, LaTeX is still unrivaled.

LaTeX 一個最重要的優點在於：允許作者專注於〔寫作的〕內容， 而不擔心每一個字〔應該如何〕顯示的細節。 並且當遇到排版任何複雜程度的數學式子時，仍無人可與 LaTeX 匹敵。

This becomes possible because LaTeX offers a kind of "Programming language for documents" in which texts are being written.

這之所以成為可能， 是因為 LaTeX 提供了一種「給文件使用的程式語言」； 而文字（texts）則是由這種語言撰寫而成的。

Especially for people not so deeply entrenched in computers this can provide a significant barrier, which is why so-called WYSIWYG ("What You See Is What You Get") programs have become the predominant choice for them. This paradigm also offers some advantages for documents massively relying on graphics and all widely-used office packages today are following it.

特別是對於那些並沒有深刻使用電腦習慣的人而言， 這會變成一種重大的障礙，這也就是為什麼所謂的 WYSIWYG（所見即所得「What You See Is What You Get」） 程式成為他們主要選擇的原因。 這個典型（paradigm）也提供了對於大量依賴圖形（graphics） 的文件一些優點，並且今天所有廣泛使用的辦公室軟體套件都依循著它。

In order to combine both paradigms and get the advantages from both worlds, some programs offer WYSIWYG input on a LaTeX basis. Examples are LxX [6] or TeXmacs, [8] which was introduced in issue #30 of the Brave GNU World. [7]

為了結合兩種典型並且從兩個世界中取出優點， 一些程式在 LaTeX 的基礎上提供了 WYSIWYG 的輸入。 例子有 LxX [6] 或 TeXmacs [8]， 在《勇敢 GNU 世界》-〈第 30 期〉中有介紹到它。 [7]

Like the office packages, these have to introduce another layer between user and LaTeX document, which makes it harder or even impossible to access all of the LaTeX functionality. Also this also often requires an intermediate format, which makes the long-term maintenance of a document more difficult.

就像辦公室軟體套件一樣，這些〔程式〕引入了介於使用者和 LaTeX 文件間的一層中介，使得它變得較難甚至不可能存取（access） 所有的 LaTeX 功能（functionality）。 同時這通常也需要一種中介格式（intermediate format）， 使得一份文件的長期維護變得更加困難。

Also it tends to hide one advantage of LaTeX, which contradicts the WYSIWYG paradigm. Because of the design as programming language, it is possible to include notes, comments and instructions in LaTeX document, which are invisible in the output, but can be incredibly useful for further development and maintenance of a document.

它也傾向於將 LaTeX 一個優點隱藏起來；而這優點反對 WYSIWYG 典型。 因為設計成一種程式語言，在 LaTeX 文件中有可能加入筆記、註解和指令 （instructions），它們在輸出中是不可見（invisible）的， 但是對於文件的進一步發展和維護卻是不可思議的有用。

preview-latex - 這計畫

In order to make life with LaTeX more comfortable for beginners and professional users without having to go without any of the advantages of LaTeX, David Kastrup began the preview-latex [9] project.

為了讓和 LaTeX 在一起的生涯對於新手和專業使用者都更舒適些， 並且不需要犧牲掉任何 LaTeX 的優點，David Kastrup 開始了 preview-latex [9] 計畫。

preview-latex is a package for the editors GNU Emacs and Xemacs, which allows embedding WYSIWYG feedback into the AUC-TeX mode.

preview-latex 是一個給 GNU Emacs 和 Xemacs 編輯器使用的軟體套件， 並且允許進入到 AUC-TeX 模式的嵌入式 WYSIWYG 反饋（feedback）中。

As the largest part of working with a document is still writing it, this can be done in Emacs, a very mighty tool with many additional features. At the same time more complex elements like mathematical equations, non-latin texts, chess and go boards, musical score sheets, graphics and so on can be visualized directly in the editor.

由於在文件上的大部份工作仍是在撰寫它〔這程式語言〕， 因此可以在 Emacs 這個擁有許多額外功能的強而有力的工具中完成。 在此同時，較為複雜的元件（elements）像是數學式子、非拉丁文字、 棋盤（chess and go boards）、樂譜（musical score sheets）和圖形…… 等等，也可以直接地在編輯器中視覺化地顯示。

Since preview-latex does not require or make modifications in the LaTeX code, the full power of LaTeX can be used. Also in cases where different authors work on the same document, the use of preview-latex in one place does not influence the others.

因為 preview-latex 並不需要，或者要對 LaTeX 碼作出修改， LaTeX 的全部實力得以發揮。而在不同的作者編輯同一份文件的情形時， 在一處使用 preview-latex 的行為並不會影響到其他人。

The project was originally "scratch your own itch" only, when it began during the PhD thesis of David Kastrup, who - after publishing it as Free Software under the GNU General Public License (GPL) - quickly discovered that there was remarkable interest in his project.

這個計畫起初只是用來「搔自己的癢」，那是在 David Kastrup 撰寫博士論文時 - 在將它以 GNU General Public License (GPL) 公開為自由軟體之後 - 他很快地發現到這在他的計畫中有相當的好處。

In short time, six more developers were found, among which Alan Shutko, Jan-Åke Larsson and Nick Alcock should be highlighted. Alan Shutko created and maintains the Autoconf-Support. Jan-Åke Larsson has contributed massively to the documentation, did the RPM packaging and is currently working on a rendering daemon to speed up the display. And Nick Alcock is the man behind the XEmacs port and helped with a lot of debugging.

在很短的時間內，他就找到了六個開發人員，其中特別值得強調的人員有 Alan Shutko 、 Jan-Åke Larsson 和 Nick Alcock。 Alan Shutko 創造並維護了 Autoconf-支援。 Jan-Åke Larsson 對於文件貢獻了許多，進行 RPM 封包， 現在並且致力於一個表現引擎（rendering daemon）以加快顯示速度。 Nick Alcock 則是躲在 XEmacs 實作品（port）後的那個人， 他也幫忙大量的調試除錯工作。

Not surprisingly, preview-latex is written mostly in TeX-Macros, some PostScript and a lot of glue code in Emacs-LISP. For speed, future elements will be employing C, as well.

不讓人驚訝的是，preview-latex 主要是以 TeX-Macros 、 一些 PostScript 和許多以 Emacs-LISP 寫的黏著碼（glue code） 所撰寫而成的。為了速度，未來的元件也將會採用 C 語言。

In the eyes of David Kastrup, one of the main advantages of preview-latex is being unobtrusive. It only becomes active on request and because of the intuitive user interface, most people never seem to read the documentation. Also it has already seen a lot of optimization and the response time is acceptable even for fairly large documents on mediocre hardware.

在 David Kastrup 的眼中，preview-latex 的一個主要優點在於： 它守本份（unobtrusive）。它只有在被要求時才會作用， 而且由於直覺的使用者介面，大部份的使用者絕對不會覺得好像在閱讀文件。 它看起來也好像已經作了許多最佳化（optimization）， 即使在普通的硬體上編輯相當大的文件，回應時間也是可以接受的。

Larger graphical parts still create some problems, however, since they do not feel comfortable to handle in either GNU Emacs or Xemacs.

然而較大的圖形部份還是會造成一些問題， 因為它們在 GNU Emacs 或 Xemacs 中〔使用〕並不感到舒適。

Therefore the project is still looking for volunteers to help improving things also from the side of the Emacs editors. Especially on Windows and Macintosh, there is still some work to do for the GNU Emacs.

因此這個計畫仍然在尋找志願者來幫忙改進事物， 其中也包括 Emacs 編輯器那一側的。 特別是在 Windows 和 Macintosh 平台上， GNU Emacs 在那兒還有一些工作需要完成。

Technically adept people will certainly find many ways of getting involved. I do hope that some of the "normal" users might have gotten curious and will take a look at preview-latex without being discouraged by some initial difficulties.

科技專家必然可以找出許多方式來參與。我真誠地希望可以有一些「正常」 的使用者，會有點好奇心並且沒有因為一開始的困難而氣餒地看一眼 preview-latex。

If you are interested in a more complete and verbose overview of the field of text processing, I'd recommend taking a look at a document [10] written by David Kastrup during his work on preview-latex.

如果你對於文書處理領域的一個更完整而詳細的概觀有興趣的話， 我建議你看一下由 David Kastrup 在他致力於 preview-latex 時所撰寫的文件。 [10]

Lire - 日誌檔管理

It is tradition on Unix systems that all proceedings and activities in the system of services like web server, mail server, name server, databases and many more are written into logfiles. This protocol of activities allows system administrators to monitor their systems closely.

在 Unix 系統中這是個傳統；在系統中服務的所有行為（proceedings） 和活動（activities）像是網站伺服器、郵件伺服器、名稱伺服器、 資料庫和許多其他，都將資訊寫入日誌檔（logfiles）中。 這個活動的協定（protocol of activities） 允許系統管理者可以仔細地監視他們系統。

But the logfiles can quickly become fairly large, which makes handling them hard. Although they are usually in ASCII format, a file size of several megabytes can not really be completely grasped by a human being.

但是日誌檔可以很快地就變得太大了，使得處理它們很困難。 雖然它們通常是使用 ASCII 格式，但是一個具有數 megabytes 的檔案， 一個人實在也無法完全地掌握。

On top of this, data only becomes information when approached with a certain question. But a significant part of the data will be irrelevant to the question, so in practice this means that information is usually buried under irrelevant data and therefore almost inaccessible.

其中最主要的問題是：資料只有在當著手於某個特定問題時才會變成資訊。 但是有很大一部份的資料將會與問題毫無干係，因此在實用上這代表： 資訊通常被湮沒在不相干的資料中，因而幾乎是無法取得的。

This problem has occured in many places for several years now and has triggered the development of programs to aid people in the analysis of logfiles.

這個問題在許多地方出現已經有些年了， 並因此觸發了用來輔助人們分析日誌檔的程式的開發。

So on April 6th, 2000, several computer scientists of Dutch companies got together to discuss the tedious task of log analysis. It became apparent that each of their companies creates solutions that are merely duplicating efforts already completed in other companies.

因此在二○○○年四月六日，幾個荷蘭公司的電腦科學家聚在一塊， 討論日誌分析這個冗長乏味的苦差事。很明顯的， 他們公司中的任一間都創造出了在其他公司中早已完成的解決方案 -- 這都成了〔做了白工的〕重複努力。

In order to end this multiplication of work, the LogReport team began writing a program as Free Software under the GNU General Public License (GPL), which should accomplish these tasks reliably in a professional environment. Almost two years later, Lire 1.0 [11] was published.

為了終結這種工作上的重複，LogReport 小組開始撰寫採用 GNU General Public License (GPL) 而作為自由軟體的程式， 這應該可以將這些任務可靠地實現在專業環境中。 將近兩年之後 Lire 1.0 [11] 就被公開了。

Like the "Electric Monks" of Douglas Adams, which free humans from the boring task of believing, it is the goal of Lire to free people from the tedious task of logfile reading. Hence the name, because the French word "lire" means "reading."

就像「電子修道士」Douglas Adams 以他的信念使在無聊差事中的人們得以獲得自由一樣，Lire 的目標在於： 使在閱讀日誌檔這個冗長乏味的苦差事中的人們得以獲得自由。 因此之故，作為名字的這個法文單字「lire」，指的是「reading」。

The program is written in Perl and Bash, massively employing XML and it works in four steps. First, logfiles are normalized into a "Destilled Log Format" (DLF) in preparation of the second step, where they are being analyzed by generic tools which can be used across services. The output format of those tools is XML, which in the fourth step can then be translated into one of the final logfile formats.

這個程式是以 Perl 和 Bash 撰寫而成，大量地採用 XML 並且以四個步驟進行工作。首先，logfiles 被正規化（normalized） 為「Destilled Log Format（DLF）」以作為第二步的準備， 接下來它們由可以跨服務的原生工具（generic tools）進行分析。 這些工具的輸出格式為 XML，然後在第四步驟中， 它可以被轉譯為最終的日誌檔格式。

Currently, Lire has input filters for 29 different services, still counting. A new service can simply be added by writing a converter into the DLF format.

目前，Lire 擁有二十九種不同服務的輸入過濾器，並且還在增加中。 新的服務只要撰寫一個到 DLF 格式的轉換器（converter） 就可以被加入。

A special advantage of Lire is that it does allow to compare different implementations of the same service, like the MTAs exim and postfix.

Lire 的一個特別的優點是， 它確實地允許相同服務的不同實作品間的比較， 像是 MTAs exim 和 postfix。

The project has already proven itself to perform well in companies with logfiles of severalfor tasks like performance measuring, system maintenance, problem solution and marketing, so it can be considered stable.

這個計畫已經自我證明了它的工作效能： 在公司內部，數 gigabytes 的日誌檔任務，像是效率量測、系統維護、 問題解決方案和行銷，因此它可以被認為是穩定的。

Accordingly to Josh Koenig, who filled out the Brave GNU World questionnaire, the biggest weakness is currently the API, which isn't easily understood or well-documented. Besides a user-friendly GUI, this is a major concern of further development.

根據 Josh Koenig 這個填來《勇敢 GNU 世界》標準問題的人， 目前最大的弱點是在 API，它們不太容易理解也沒有很好地加以文檔化。 因此除了一個對使用者友善的 GUI 之外， 這是未來開發的主要關心的事。

Help on these areas as well as filters for new services are very welcome. Also the group seeks help making Lire popular especially in medium to large size companies.

十分歡迎針對這些項次以及過濾器的幫忙。 同時這群組也尋求可以使 Lire 在特別是中大型企業受到歡迎的幫忙。

The hard core of the LogReport development team consists of Joost van Baal, Francis Lacoste, Egon Willighagen, Josh Koenig and Wessel Dankers, although many developers from different countries around the world have contributed. The project is being maintained by the LogReport Foundation, a charitable association in the Netherlands.

LogReport 開發小組最堅實的核心人員包括： Joost van Baal 、 Francis Lacoste 、 Egon Willighagen 、 Josh Koenig 和 Wessel Dankers ， 雖然有許多來自世界上不同國家的開發人員也作出了貢獻。 這個計畫是由 LogReport 基金會所維護，它是一所荷蘭的慈善機構。

And besides being technically useful, this project also offers a very nice example for one of the most important economic advantages of Free Software, the prevention of repetition of work.

除了在科技上有用之外，這個計畫也提供了 「避免重複工作-自由軟體最重要的經濟優點之一」 的一個非常好的例子。

GNU 源碼語法標示（GNU Source Highlight）

GNU Source Highlight [12] by Lorenzo Bettini takes a source code and creates syntax-highlighted output in HTML or XHTML. It has evolved out of the tools java2html and cpp2html, which were introduced in issue #21 of the Brave GNU World and have dissolved into GNU Source Highlight.

由 Lorenzo Bettini 所完成的 GNU 源碼語法標示 [12] 取得一份源碼，並且以 HTML 或 XHTML 格式製作出具有語法〔顏色〕 標示的輸出。它是由 java2html 和 cpp2html 進化而來 -- 在《勇敢 GNU 世界》-〈第 21 期〉有介紹， [13] 這兩個工具已經溶解到 GNU 源碼語法標示，並成為它的一部份。

Currently input filters exist for Java, C/C++, Prolog, Perl, PHP3, Python, Flex and ChangeLog. Filters for other languages can be added, however.

目前存在的輸入過濾器有 Java 、 C/C++ 、 Prolog 、 Perl 、 PHP3 、 Python 、 Flex 和 ChangeLog。不過給其他語言使用的過濾器可以被加上就是了。

The project itself was written in C++ and is stable according to Lorenzo Bettini. He is now working on a new output format (LaTeX) and would like to write a better description language for programming languages in order to replace Flex, which is currently used for this purpose.

這計畫本身是以 C++ 寫成的，根據 Lorenzo Bettini 它也已經穩定。 他現在正致力於一個新的輸出格式（LaTeX）， 並且打算撰寫一個更好的描述語言（description language） 以替換掉 Flex ，這是目前使用來作為這個目的〔的語言〕。

Most of the support he received for this project was in terms of filters for different programming languages written by other developers. John Millaway for instance wrote the filters for Flex and ChangeLog, Christian W. Zuckschwedt and Josh Hiloni contributed the XHTML output and Martin Gebert wrote the Python filter. Alain Barbet wrote the filters for PHP3 and Perl.

這個計畫他大部份獲得的支援是： 由其他開發者所撰寫的針對不同程式語言的過濾器。 舉例來說，John Millaway 撰寫了 Flex 和 ChangeLog 的過濾器； Christian W. Zuckschwedt 和 Josh Hiloni 貢獻了到 XHTML 的輸出； Martin Gebert 撰寫了 Python 的過濾器； Alain Barbet 撰寫了給 PHP3 和 Perl 的過濾器。

The major weakness of the project at the moment is that references of functions can currently not be mapped to their definitions, as only lexical analysis is being performed. Fixing this and writing more filters would therefore be good ways of supporting the project.

這個計畫此刻最主要的弱點在於： 函數的參照（references of functions）目前可能會不被映射到 （mapped to）它們的定義，而只有字彙分析被執行。 因而「修正這個問題」以及「撰寫更多過濾器」 將會是支援這個計畫的好方式。

Naturally, developers using GNU Source Highlight as commandline tool or interactive CGI in the web are the classical user group of the project. But there are also users who do appreciate a good graphical user interface.

自然地，以命令列（commandline）或是在網路上的互動式 CGI 來使用 GNU 源碼語法標示的開發人員，是這個計畫的典型使用者群組。 但是也有使用者會比較欣賞一個好的圖形使用者介面。

Ksrc2html - 給 GNU 源碼語法標示使用的 GUI

Ksrc2html [14] by Martin Gebert is a graphical user interface for GNU Source Highlight; also available under the GNU General Public License (GPL), which makes it Free Software. As the name suggests, Ksrc2html is based upon C++, Qt and KDE 2, an update to KDE 3 is planned.

由 Martin Gebert 所完成的 Ksrc2html [14] 是一個給 GNU 源碼語法標示使用的圖形使用者介面； 也可以在使它成為自由軟體的 GNU General Public License (GPL) 下取得。 正如它的名稱所暗示的： Ksrc2html 奠基於 C++ 、 Qt 和 KDE 2 ， 不過也計劃要更新到 KDE 3 。

Ksrc2html allows a formatting preview in order to allow better control over the parameters. Also settings for colors and font types can be made interactively and saved for later usage.

Ksrc2html 提供格式的預覽，以允許可以更好地控制參數 （parameters）。同時對於顏色和字形字體的設定也能夠互動地完成， 並且可以儲存起來作為以後的用途。

Thanks to Xavier Outhier, who took care of the French translation, Ksrc2html is currently localizable for German and French.

感謝 Xavier Outhier 照應了它的法文翻譯， Ksrc2html 目前已經對德文和法文完成區域化（localizable for） 的工作了。

Martin considers the project to be stable, although he does plan to expand the dialog for colors and font types in a way that will allow automatic adjustment for different programming languages.

Martin 認為這計畫已經穩定了，雖然他確實計劃要 「以一種允許給不同程式語言自動調整的方式」， 擴充顏色和字形字體的對話框。

Also he would like it to be known that help with the KDE 3 port would be quite welcome.

同時他也想讓大家知道：特別歡迎對於 KDE 3 實作品的幫忙。

自由軟體在亞洲

As the Asian readers will probably be happy to read, on July 10th, 2002, the "Free Software Initiative Japan" (FSIJ) [15] was founded. It seeks to further Free Software in Japan and create the basis for a future FSF Japan or FSF Asia.

亞洲的讀者也許會很高興地閱讀到，在二○○二年七月十日， 「Free Software Initiative Japan（FSIJ）」 [15] 成立了。 它致力於在日本推廣自由軟體，並且創立作為未來 FSF Japan 或 FSF Asia 的基本組織。

Chairman of the FSIJ is Prof. Masayuki Ida, who was acting as the "Vice President Japan" of the Free Software Foundation North America for a long time and with whom the members of the Free Software Foundation Europe led intensive discussions during his trip through Europe last year.

FSIJ 的主席是 Masayuki Ida 教授，他擔任北美自由軟體基金會 「日本副總裁」很長了一段時間，並且在他去年的歐洲訪問期間， 與歐洲自由軟體基金會的成員們進行了密集的討論。

In order to provide an impulse for Free Software in Japan, the FSIJ organized the "Free Software Symposium 2002" in Tokyo on October 22nd and 23rd. Being the first event of its kind in Asia, speakers from China, Thailand, Japan, Singapore, Germany, Italy and the USA were invited to provide an interesting conference programme.

為了提供給在日本的自由軟體基金會一個推動力，FSIJ 組織了十月卄二日、卄三日在東京舉辦的 「二○○二年自由軟體研討會（Free Software Symposium 2002 ）」。 由於這是在亞洲這類型事件第一次出現的場合， 來自中國、泰國、日本、新加坡、德國、義大利和美國的演講者都被邀請， 並提供有趣的會議節目。

Besides the more technically oriented presentations about Debian, the HURD project or RedFlag Linux, the Chinese GNU/Linux distribution, there were also speeches about the larger issues of Free Software and the situations in Asia and Europe.

除了較為技術導向的關於 「Debian 、 HURD 計畫或 RedFlag Linux 、中文 GNU/Linux 散佈件」 的展示外，也有關於自由軟體以及其在亞洲和歐洲的狀況的演講。

The round table on the evening of October 22nd discussed the issues of better international cooperation for internationalization of programs and documentation as well as the possibility of a solution oriented database for Free Software. Even though these issues would certainly not be solved in two hours, some practical ideas were found that are now being pursued by mail.

十月卄二日晚上舉行的圓桌會議討論了對於 「程式與文件的國際化」的更好的國際合作的議題， 以及給自由軟體使用的解決方案導向資料庫（solution oriented database） 的可能性。即使這些議題肯定無法在兩個小時之內獲得解決， 卻也找到一些實用的想法 -- 現在正以郵件尋求解決。

All in all this was an important step forward for Free Software in Asia, which also intensified the dialog between the asian countries. Building upon it, it is considered to hold a followup-event sometime around February or March 2003 in Thailand.

全部這些，都是自由軟體在亞洲的重要一步， 並強化了亞洲國家間的對話。以這為基礎，目前已經考慮要接續著舉辦 -- 約二○○三年二月或三月份左右於泰國。

Maybe it will be possible to establish these events as a permanent institution wandering from country to country in Asia. In any case it is very good to see that Free Software is also on the rise in Asia.

也許將有可能將這些事件建立為一種永久的「在亞洲國家間輪流舉辦的」 慣例。不管怎樣，看到自由軟體也在亞洲掘起總是非常好的。

Asian readers of the Brave GNU World who would like to get involved should probably get in touch with the FSIJ or GNU China [16].

想要參與的《勇敢 GNU 世界》的亞洲讀者，也許應該和 FSIJ 或 GNU China [16] 聯繫。

直到下一次之前

Enough Brave GNU World for this month. Although the repetition might cause some to read over it, as every month I am asking for questions, ideas, comments and mails about interesting projects.

這個月的《勇敢 GNU 世界》已經足夠了。 雖然這一再的重複也許會使得一些讀者跳過這裡， 但每個月我還是請求各位寄來有關各種計畫的問題、想法、意見和郵件。

And despite the danger to be buried under more mail, I'd like to ask you a concrete question. In reference to Douglas Adams, I'd like to hear what is the most important question to you that Free Software provides the answer to. Like everything else, please send your questions to the usual address. [1].

即便有可能會被更多的郵件所湮沒，我還是請求你寄來具體的問題。 關於 Douglas Adams，我想要聽聽看對你而言，自由軟體應該回答的 「什麼是最重要的問題」。如同其他，請將你的問題送到平常的位址 [1]。 【請以英文或德文撰寫郵件，其他的語言無法被了解； 或以中文送到本文翻譯。】