CVSROOT: /web/www
Module name: www
Changes by: Yavor Doganov <yavor> 11/11/06 00:34:02
Modified files:
philosophy : no-word-attachments.it.html
papadopoulos-response.it.html
philosophy/po : papadopoulos-response.it.po
Added files:
philosophy/po : no-word-attachments.it-en.html
papadopoulos-response.it-en.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/no-word-attachments.it.html?cvsroot=www&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/papadopoulos-response.it.html?cvsroot=www&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/papadopoulos-response.it.po?cvsroot=www&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/no-word-attachments.it-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/papadopoulos-response.it-en.html?cvsroot=www&rev=1.1
Patches:
Index: no-word-attachments.it.html
===================================================================
RCS file: /web/www/www/philosophy/no-word-attachments.it.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- no-word-attachments.it.html 5 Nov 2011 16:30:49 -0000 1.9
+++ no-word-attachments.it.html 6 Nov 2011 00:33:37 -0000 1.10
@@ -209,7 +209,7 @@
<em>Ã anche probabile che il tuo computer abbia qualche programma per
convertire al formato PDF. Seleziona File, poi Stampa (Print). Dal menu a
tendina seleziona la voce Crea Documento PDF (o qualche altra voce simile,
-dipende dal programma che utilizzi). </p>
+dipende dal programma che utilizzi).</em></p>
<p>
<em>Per maggiori informazioni su questo argomento si veda
@@ -322,7 +322,7 @@
<!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2011/11/05 16:30:49 $
+$Date: 2011/11/06 00:33:37 $
<!-- timestamp end -->
</p>
Index: papadopoulos-response.it.html
===================================================================
RCS file: /web/www/www/philosophy/papadopoulos-response.it.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- papadopoulos-response.it.html 5 Nov 2011 00:33:46 -0000 1.4
+++ papadopoulos-response.it.html 6 Nov 2011 00:33:37 -0000 1.5
@@ -40,7 +40,7 @@
scrivere documenti .doc.
</p><p>
Purtroppo, sembra che Microsoft a volte riesca nei suoi intenti. La mia
-applicazione non-Microsoft non è stata in grado di aprire il documento.doc
+applicazione non-Microsoft non è stata in grado di aprire il documento .doc
che mi hai inviato. Di conseguenza non possiamo scambiarci informazioni
finché non accada uno dei due eventi che seguono:
</p><p>
@@ -72,10 +72,10 @@
che il documento venga interpretato correttamente. Credo che non si possa
attribuire loro la colpa.
</p><p>
-PPPS: Per conoscere altre ragioni per cui no si deve scegliere il formato
+PPPS: Per conoscere altre ragioni per cui non si deve scegliere il formato
.doc per scambiare informazioni elettronicamente, ti invito a leggere <a
href="/philosophy/no-word-attachments.it.html">
-http://www.gnu.org/philosophy/no-word-attachments.it.html</a>. Ã forse un
+http://www.gnu.org/philosophy/no-word-attachments.it.html</a>. Forse è un
po' lungo, ma sicuramente chiarisce i compromessi che tu, in quanto
mittente, ed io, in quanto destinatario, stiamo facendo quando ci scambiamo
documenti Microsoft Word.
@@ -117,11 +117,13 @@
Tradotto originariamente da Matteo HCE Valsasna. Modifiche successive di
Paola Blason e Giorgio V. Felchero, Giovanni Biscuolo, Claudio Iannotta,
Andrea Pescetti, Dora Scilipoti.</div>
+
+
<p>
<!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2011/11/05 00:33:46 $
+$Date: 2011/11/06 00:33:37 $
<!-- timestamp end -->
</p>
@@ -148,6 +150,7 @@
<!-- Please use W3C normative character entities. -->
<!-- -->
<!-- <gnun>
+
<ul class="translations-list"> -->
<!-- Greek -->
<!-- <li><a
href="/philosophy/papadopoulos-response.el.html">Ελληνικά</a> [el]</li>
-->
@@ -163,7 +166,8 @@
<!-- <li><a
href="/philosophy/papadopoulos-response.pl.html">polski</a> [pl]</li> -->
<!-- Russian -->
<!-- <li><a
href="/philosophy/papadopoulos-response.ru.html">русский</a> [ru]</li>
-->
-<!-- </ul></gnun> -->
+<!-- </ul>
+</gnun> -->
<!-- </div>
-->
</div>
Index: po/papadopoulos-response.it.po
===================================================================
RCS file: /web/www/www/philosophy/po/papadopoulos-response.it.po,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
Index: po/no-word-attachments.it-en.html
===================================================================
RCS file: po/no-word-attachments.it-en.html
diff -N po/no-word-attachments.it-en.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/no-word-attachments.it-en.html 6 Nov 2011 00:33:47 -0000 1.1
@@ -0,0 +1,358 @@
+<!--#include virtual="/server/header.html" -->
+
+<title>We Can Put an End to Word Attachments - GNU Project - Free Software
Foundation (FSF)</title>
+<meta http-equiv="keywords" content="GNU, FSF, Free Software Foundation,
Linux, general, public, license, gpl, general public license, freedom,
software, power, rights, word, attachment, word attachment, microsoft" />
+<meta http-equiv="description" content="This essay explains why Microsoft Word
attachments to email are bad, and describes what you can do to help stop this
practice." />
+
+<!--#include virtual="/server/banner.html" -->
+<!--#include virtual="/philosophy/po/no-word-attachments.translist" -->
+
+<h2>We Can Put an End to Word Attachments</h2>
+
+<p>by <strong>Richard M. Stallman</strong>
+</p>
+
+<p>
+Don't you just hate receiving Word documents in email messages? Word
+attachments are annoying, but, worse than that, they impede people from
+switching to free software. Maybe we can stop this practice with a
+simple collective effort. All we have to do is ask each person who
+sends us a Word file to reconsider that way of doing things.</p>
+
+<p>
+Most computer users use Microsoft Word. That is unfortunate for them,
+since Word is proprietary software, denying its users the freedom to
+study, change, copy, and redistribute it. And because Microsoft
+changes the Word file format with each release, its users are locked
+into a system that compels them to buy each upgrade whether they want
+a change or not. They may even find, several years from now, that the
+Word documents they are writing this year can no longer be read with
+the version of Word they use then.</p>
+
+<p>
+But it hurts us, too, when they assume we use Word and send us (or
+demand that we send them) documents in Word format. Some people
+publish or post documents in Word format. Some organizations will
+only accept files in Word format: I heard from someone that he was
+unable to apply for a job because resumes had to be Word files. Even
+governments sometimes impose Word format on the public, which is truly
+outrageous.</p>
+
+<p>
+For us users of free operating systems, receiving Word documents is an
+inconvenience or an obstacle. But the worst impact of sending Word
+format is on people who might switch to free systems: they hesitate
+because they feel they must have Word available to read the Word files
+they receive. The practice of using the secret Word format for
+interchange impedes the growth of our community and the spread of
+freedom. While we notice the occasional annoyance of receiving a Word
+document, this steady and persistent harm to our community usually
+doesn't come to our attention. But it is happening all the time.</p>
+
+<p>
+Many GNU users who receive Word documents try to find ways to handle
+them. You can manage to find the somewhat obfuscated ASCII text in
+the file by skimming through it. Free software today can read most
+Word documents, but not all—the format is secret and has not been
+entirely decoded. Even worse, Microsoft can change it at any time.</p>
+
+<p>
+Worst of all, it has already done so. Microsoft Office 2007 uses by
+default a format based on the patented OOXML format. (This is the one
+that Microsoft got declared an “open standard” by
+political manipulation and packing standards committees.) The actual
+format is not entirely OOXML, and it is not entirely documented.
+Microsoft offers a gratis patent license for OOXML on terms which do
+not allow free implementations. We are thus beginning to receive Word
+files in a format that free programs are not even allowed to read.</p>
+
+<p>
+When you receive a Word file, if you think of that as an isolated
+event, it is natural to try to cope by finding a way to read it.
+Considered as an instance of a pernicious systematic practice, it
+calls for a different approach. Managing to read the file is treating
+a symptom of an epidemic disease; what we really want to do is stop
+the disease from spreading. That means we must convince people not to
+send or post Word documents.</p>
+
+<p>
+I therefore make a practice of responding to Word attachments with a
+polite message explaining why the practice of sending Word files is a
+bad thing, and asking the person to resend the material in a nonsecret
+format. This is a lot less work than trying to read the somewhat
+obfuscated ASCII text in the Word file. And I find that people
+usually understand the issue, and many say they will not send Word
+files to others any more.</p>
+
+<p>
+If we all do this, we will have a much larger effect. People who
+disregard one polite request may change their practice when they
+receive multiple polite requests from various people. We may be able
+to give <em>Don't send Word format!</em> the status of netiquette,
+if we start systematically raising the issue with everyone who sends
+us Word files.</p>
+
+<p>
+To make this effort efficient, you will probably want to develop a
+canned reply that you can quickly send each time it is necessary.
+I've included two examples: the version I have been using recently,
+followed by a new version that teaches a Word user how to convert to
+other useful formats. They are followed by several suggestions sent
+by other people.</p>
+
+<p>
+You can use these replies verbatim if you like, or you can personalize
+them or write your own. By all means construct a reply that fits your
+ideas and your personality—if the replies are personal and not
+all alike, that will make the campaign more effective.</p>
+
+<p>
+These replies are meant for individuals who send Word files. When you
+encounter an organization that imposes use of Word format, that calls
+for a different sort of reply; there you can raise issues of fairness
+that would not apply to an individual's actions.</p>
+
+<p>
+Some recruiters ask for resumes in Word format. Ludicrously, some
+recruiters do this even when looking for someone for a free software
+job. (Anyone using those recruiters for free software jobs is not
+likely to get a competent employee.) To help change this practice,
+you can put a link to this page into your resume, next to links to
+other formats of the resume. Anyone hunting for a Word version of the
+resume will probably read this page.</p>
+
+<p>
+This page talks about Word attachments, since they are by far the most
+common case. However, the same issues apply with other proprietary
+formats, such as PowerPoint and Excel. Please feel free to adapt the
+replies to cover those as well, if you wish.</p>
+
+<p>
+With our numbers, simply by asking, we can make a difference.</p>
+
+<hr />
+
+<p>
+<em>You sent the attachment in Microsoft Word format, a secret
+proprietary format, so I cannot read it. If you send me the plain
+text, HTML, or PDF, then I could read it.</em></p>
+
+<p>
+<em>Sending people documents in Word format has bad effects, because that
+practice puts pressure on them to use Microsoft software. In effect,
+you become a buttress of the Microsoft monopoly. This specific
+problem is a major obstacle to the broader adoption of GNU/Linux.
+Would you please reconsider the use of Word format for communication
+with other people?</em></p>
+
+<hr />
+
+<p>
+<em>You sent the attachment in Microsoft Word format, a secret
+proprietary format, so it is hard for me to read. If you send me
+plain text, HTML, or PDF, then I will read it.</em></p>
+
+<p>
+<em>Distributing documents in Word format is bad for you and for others.
+You can't be sure what they will look like if someone views them
+with a different version of Word; they may not work at all.</em></p>
+
+<p>
+<em>Receiving Word documents is bad for you because they can carry
+viruses (see http://en.wikipedia.org/wiki/Macro_virus_(computing)).
+Sending Word documents is bad for you because a Word document normally
+includes hidden information about the author, enabling those in the
+know to pry into the author's activities (maybe yours). Text that you
+think you deleted may still be embarrassingly present. See
+http://news.bbc.co.uk/2/hi/technology/3154479.stm for more
+info.</em></p>
+
+<p>
+<em>But above all, sending people Word documents puts pressure on them to
+use Microsoft software and helps to deny them any other choice. In
+effect, you become a buttress of the Microsoft monopoly. This
+pressure is a major obstacle to the broader adoption of free software.
+Would you please switch to a different way of sending files to other
+people, instead of Word format?</em></p>
+
+<p>
+<em>To convert the file to HTML using Word is simple. Open the
+document, click on File, then Save As, and in the Save As Type strip
+box at the bottom of the box, choose HTML Document or Web Page. Then
+choose Save. You can then attach the new HTML document instead of
+your Word document. Note that Word changes in inconsistent
+ways—if you see slightly different menu item names, please try
+them.</em></p>
+
+<p>
+<em>To convert to plain text is almost the same—instead of HTML
+Document, choose Text Only or Text Document as the Save As
+Type.</em></p>
+
+<p>
+<em>Your computer may also have a program to convert to PDF format.
+Select File, then Print. Scroll through available printers and select
+the PDF converter. Click on the Print button and enter a name for the
+PDF file when requested.</em></p>
+
+<p>
+<em>See http://www.gnu.org/philosophy/no-word-attachments.html for more
+about this issue.</em></p>
+
+<hr />
+
+<p>
+Here's another approach, suggested by Bob Chassell. It requires that
+you edit it for the specific example, and it presumes you have a way
+to extract the contents and see how long they are.</p>
+
+<hr />
+
+<p>
+<em>I am puzzled. Why did you choose to send me 876,377 bytes in your
+recent message when the content is only 27,133 bytes?</em></p>
+
+<p>
+<em>You sent me five files in the non-standard, bloated .doc format that
+is Microsoft's secret, rather than in the international, public, and
+more efficient format of plain text.</em></p>
+
+<p>
+<em>Microsoft can (and did recently in Kenya and Brazil) have local
+police enforce laws that prohibit students from studying the code,
+prohibit entrepeneurs starting new companies, and prohibit
+professionals offering their services. Please don't give them your
+support.</em></p>
+
+<hr />
+
+<p>
+John D. Ramsdell suggests people discourage the use of proprietary
+attachments by making a small statement in their <kbd>.signature</kbd>
+file:</p>
+
+<hr />
+
+<p>
+<em>Please avoid sending me Word or PowerPoint attachments.<br />
+See http://www.gnu.org/philosophy/no-word-attachments.html</em></p>
+
+<hr />
+
+<p>
+<a href="/philosophy/papadopoulos-response.html">Here is a response
+letter</a> by Alexandros Papadopoulos to an email message with a Word
+attachment.</p>
+
+<hr />
+
+<p>
+Kevin Cole of the Gallaudet University in Washington,
+DC, <a href="/philosophy/kevin-cole-response.html">sends out this
+automatic reply message</a> whenever he receives a word
+attachment. (I think it is
+better to send the responses by hand, and make it clear that you have
+done so, because people will receive them better.)</p>
+<hr />
+
+<p>
+Father Martin Sylvester
+offers <a href="/philosophy/sylvester-response.html">a more lengthy
+response</a> that adds the concept that it is a discourtesy to send
+Word attachments to a recipient when you don't know that they can read
+them.</p>
+
+</div>
+
+<!--#include virtual="/server/footer.html" -->
+
+<div id="footer">
+<p>
+Please send FSF & GNU inquiries to
+<a href="mailto:g...@gnu.org";><g...@gnu.org></a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.
+<br />
+Please send broken links and other corrections or suggestions to
+<a href="mailto:webmast...@gnu.org";><webmast...@gnu.org></a>.
+</p>
+
+<p>
+Please see the
+<a href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting
+translations of this article.
+</p>
+
+<p>
+Copyright © 2002, 2007 Richard M. Stallman
+<br />
+This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.
+</p>
+
+<p>
+Updated:
+<!-- timestamp start -->
+$Date: 2011/11/06 00:33:47 $
+<!-- timestamp end -->
+</p>
+</div>
+
+<!-- <div id="translations"> -->
+<!-- <h4>Translations of this page</h4> -->
+<!-- -->
+<!-- Please keep this list alphabetical by language code. -->
+<!-- Comment what the language is for each type, i.e. de is German. -->
+<!-- Write the language name in its own language (Deutsch) in the text. -->
+<!-- If you add a new language here, please -->
+<!-- advise web-translat...@gnu.org and add it to -->
+<!-- - /home/www/html/server/standards/README.translations.html -->
+<!-- - one of the lists under the section "Translations Underway" -->
+<!-- - if there is a translation team, you also have to add an alias -->
+<!-- to mail.gnu.org:/com/mailer/aliases -->
+<!-- Please also check you have the language code right; see: -->
+<!-- http://www.loc.gov/standards/iso639-2/php/code_list.php -->
+<!-- If the 2-letter ISO 639-1 code is not available, -->
+<!-- use the 3-letter ISO 639-2. -->
+<!-- Please use W3C normative character entities. -->
+<!-- -->
+<!-- <ul class="translations-list"> -->
+<!-- Bosnian -->
+<!-- <li><a
href="/philosophy/no-word-attachments.bs.html">bosanski</a> [bs]</li> -->
+<!-- Czech -->
+<!-- <li><a
href="/philosophy/no-word-attachments.cs.html">Česky</a> [cs]</li>
-->
+<!-- Danish -->
+<!-- <li><a
href="/philosophy/no-word-attachments.da.html">dansk</a> [da]</li> -->
+<!-- German -->
+<!-- <li><a
href="/philosophy/no-word-attachments.de.html">Deutsch</a> [de]</li> -->
+<!-- English -->
+<!-- <li><a
href="/philosophy/no-word-attachments.html">English</a> [en]</li> -->
+<!-- Spanish -->
+<!-- <li><a
href="/philosophy/no-word-attachments.es.html">español</a> [es]</li>
-->
+<!-- Farsi (Persian) -->
+<!-- <li><a
href="/philosophy/no-word-attachments.fa.html">فارسی</a> [fa]</li>
-->
+<!-- French -->
+<!-- <li><a
href="/philosophy/no-word-attachments.fr.html">français</a> [fr]</li>
-->
+<!-- Hebrew -->
+<!-- <li><a
href="/philosophy/no-word-attachments.he.html">עברית</a> [he]</li>
-->
+<!-- Italian -->
+<!-- <li><a
href="/philosophy/no-word-attachments.it.html">italiano</a> [it]</li> -->
+<!-- Dutch -->
+<!-- <li><a
href="/philosophy/no-word-attachments.nl.html">Nederlands</a> [nl]</li> -->
+<!-- Norwegian (bokmål) -->
+<!-- <li><a href="/philosophy/no-word-attachments.nb.html">norsk
(bokmål)</a> [nb]</li> -->
+<!-- Polish -->
+<!-- <li><a
href="/philosophy/no-word-attachments.pl.html">polski</a> [pl]</li> -->
+<!-- Brazilian Portugese -->
+<!-- <li><a href="/philosophy/no-word-attachments.pt-br.html">português
do Brasil</a> [pt-br]</li> -->
+<!-- Romanian -->
+<!-- <li><a
href="/philosophy/no-word-attachments.ro.html">română</a> [ro]</li>
-->
+<!-- Russian -->
+<!-- <li><a
href="/philosophy/no-word-attachments.ru.html">русский</a> [ru]</li>
-->
+<!-- </ul> -->
+<!-- </div> -->
+</div>
+</body>
+</html>
Index: po/papadopoulos-response.it-en.html
===================================================================
RCS file: po/papadopoulos-response.it-en.html
diff -N po/papadopoulos-response.it-en.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/papadopoulos-response.it-en.html 6 Nov 2011 00:33:48 -0000 1.1
@@ -0,0 +1,138 @@
+<!--#include virtual="/server/header.html" -->
+<title>A Response Letter to the Word Attachments</title>
+<meta http-equiv="Keywords"
+ content="GNU, FSF, Free Software Foundation, Linux, general, public, license,
gpl, general public license, freedom, software, power, rights, word,
attachment, word attachment, microsoft" />
+ <meta http-equiv="Description" content="This essay explains why Microsoft
Word attachments to email are bad, and describes what you can do to help stop
this practice." />
+<!--#include virtual="/server/banner.html" -->
+<!--#include virtual="/philosophy/po/papadopoulos-response.translist" -->
+<h2>A Response Letter to the Word Attachments</h2>
+
+<p>From: Alexandros Papadopoulos</p>
+<p>
+I'm sorry, but I was unable to read the Microsoft Word document you sent
+me. Microsoft has been steadily changing the .doc format over the
+releases of Microsoft Word (4.0, 95, 97, 2000, and now XP). Microsoft
+has also intentionally refused to release the specification of the .doc
+format to the community, making Microsoft Word the only application
+that can reliably open this format. There is the Microsoft
+Word Viewer application, but it only runs on Microsoft Windows
+operating systems and does not allow one to edit the document.
+</p><p>
+The development team that designed the software I choose to use
+(OpenOffice.org), has tried hard to figure out how the .doc format is
+created and interpreted, in order to make it available to more people.
+They believe that all people should be able to exchange information
+electronically, and .doc is one of the most common formats. So, they
+tried to make OpenOffice.org, the main competitor to Microsoft's own
+Office suite, as compatible as possible with Microsoft's own formats.
+But Microsoft did not like this, because it would mean that people that
+have not bought Microsoft Windows and Microsoft Office would be able to
+read and write .doc documents.
+</p><p>
+Unfortunately, it seems that Microsoft is sometimes successful. My
+non-Microsoft application was unable to open the .doc document you sent
+me. As a result, we cannot exchange information, until one of the
+following happens:
+</p><p>
+[0] The information intended to be read/processed by me is converted to
+an open format that people who don't use Microsoft Windows and Microsoft
+Office are able to process.
+</p><p>
+[1] I purchase and install Microsoft Windows, Microsoft Word, and by
+deduction all other Microsoft applications necessary to do my work.
+</p><p>
+Because it will be a cold day in hell before I do the latter, I would
+suggest we find a different way of exchanging information
+electronically.
+</p><p>
+--A
+</p><p>
+PS: I hope you realize that I have nothing against you as a person. I
+just can't use the document you sent me, and I tried to explain why the
+implicit assumption that I would be able to read it, was mistaken.
+</p><p>
+PPS: When I tried to open the document you sent to me, my word processor
+crashed, obviously unable to properly interpret the .doc format. My
+word processor was handling 4 other documents at the time. Two of them
+were assignments, and all changes I had not saved were lost. On
+aggregate, about two hours of my work were lost because the
+OpenOffice.org developers were unable to overcome the barriers Microsoft
+put in place, and render the document properly. I believe they are the
+last to blame for this failure.
+</p><p>
+PPPS: For further reasons why .doc should not be the format of choice
+when exchanging information electronically, I invite you to read
+<a href="/philosophy/no-word-attachments.html">
+http://www.gnu.org/philosophy/no-word-attachments.html</a>. It may be
+long, but it certainly exposes the compromises both you, as the
+sender, and I, as the receiver, are making by exchanging Microsoft
+Word documents.
+</p>
+
+</div>
+
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+
+<p>
+Please send FSF & GNU inquiries to
+<a href="mailto:g...@gnu.org";><em>g...@gnu.org</em></a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.
+<br />
+Please send broken links and other corrections or suggestions to
+<a href="mailto:webmast...@gnu.org";><em>webmast...@gnu.org</em></a>.
+</p>
+
+<p>
+Please see the
+<a href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting
+translations of this article.
+</p>
+
+<p>
+Last updated:
+<!-- timestamp start -->
+$Date: 2011/11/06 00:33:48 $
+<!-- timestamp end -->
+</p>
+</div>
+
+<!-- <div id="translations"> -->
+<!-- <h4>Translations of this page</h4> -->
+<!-- -->
+<!-- Please keep this list alphabetical. -->
+<!-- Comment what the language is for each type, i.e. de is German. -->
+<!-- Write the language name in its own language (Deutsch) in the text. -->
+<!-- If you add a new language here, please -->
+<!-- advise web-translat...@gnu.org and add it to -->
+<!-- - /home/www/bin/nightly-vars either TAGSLANG or WEBLANG -->
+<!-- - /home/www/html/server/standards/README.translations.html -->
+<!-- - one of the lists under the section "Translations Underway" -->
+<!-- - if there is a translation team, you also have to add an alias -->
+<!-- to mail.gnu.org:/com/mailer/aliases -->
+<!-- Please also check you have the 2 letter language code right, cf. -->
+<!-- <URL:http://www.w3.org/WAI/ER/IG/ert/iso639.htm> -->
+<!-- Please use W3C normative character entities. -->
+<!-- -->
+<!-- <ul class="translations-list"> -->
+<!-- Greek -->
+<!-- <li><a
href="/philosophy/papadopoulos-response.el.html">Ελληνικά</a> [el]</li>
-->
+<!-- English -->
+<!-- <li><a
href="/philosophy/papadopoulos-response.html">English</a> [en]</li> -->
+<!-- Spanish -->
+<!-- <li><a
href="/philosophy/papadopoulos-response.es.html">Español</a> [es]</li>
-->
+<!-- French -->
+<!-- <li><a
href="/philosophy/papadopoulos-response.fr.html">Français</a> [fr]</li>
-->
+<!-- Italian -->
+<!-- <li><a
href="/philosophy/papadopoulos-response.it.html">Italiano</a> [it]</li> -->
+<!-- Polish -->
+<!-- <li><a
href="/philosophy/papadopoulos-response.pl.html">polski</a> [pl]</li> -->
+<!-- Russian -->
+<!-- <li><a
href="/philosophy/papadopoulos-response.ru.html">русский</a> [ru]</li>
-->
+<!-- </ul> -->
+<!-- </div> -->
+</div>
+</body>
+</html>
