www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/server/standards README.translations.html


From: Richard M. Stallman
Subject: www/server/standards README.translations.html
Date: Sun, 01 Jul 2012 15:15:58 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     Richard M. Stallman <rms>       12/07/01 15:15:58

Modified files:
        server/standards: README.translations.html 

Log message:
        Add recommendations about audience and clarity.  Some rearrangement.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.translations.html?cvsroot=www&r1=1.203&r2=1.204

Patches:
Index: README.translations.html
===================================================================
RCS file: /web/www/www/server/standards/README.translations.html,v
retrieving revision 1.203
retrieving revision 1.204
diff -u -b -r1.203 -r1.204
--- README.translations.html    10 Jun 2012 08:09:41 -0000      1.203
+++ README.translations.html    1 Jul 2012 15:15:46 -0000       1.204
@@ -105,11 +105,44 @@
 
 <p>Here are our specific goals for our translated pages.</p>
 
+<h4 id="clarity">Clarity</h4>
+
+With few exceptions, the pages we translate are addressed to the
+general public.  Before working on a page, please look at the original
+and ask yourself whether it is addressed to programmers or to the
+general public.  Then aim your translation at the same audience.
+
+In pages meant for the general public, please avoid words that are not
+found in common dictionaries, except for our special terms such as
+"GNU" and "copyleft" (see the list below).
+
 <h4 id="accuracy">Accuracy</h4>
 
 <p>In order to produce a translation which is accurate and faithful to 
-the original, you need to be familiar with the basic concepts of the GNU 
-Project and the specific terminology used in gnu.org:</p>
+the original, you need to be familiar with the basic concepts of the
+GNU Project and the specific terminology used in gnu.org.
+</p>
+
+<p>
+Please study the <a href="/philosophy"> philosophy </a> of the free
+software movement, so that you can present it properly and clearly.
+The following articles will be particularly helpful:
+</p>
+
+<ul>
+  <li><a href="/philosophy/free-sw.html">What is Free Software?</a></li>
+  <li><a href="/philosophy/categories.html">Categories of Free and 
+    Nonfree Software</a></li>
+
+  <li><a href="/philosophy/words-to-avoid.html">Words to Avoid</a></li>
+  <li><a href="/gnu/why-gnu-linux.html">What's in a Name?</a></li>
+  <li><a href="/philosophy/open-source-misses-the-point.html">Open 
+    Source Misses the Point of Free Software</a></li>
+</ul>
+
+<p>
+These terms and files need special attention:
+</p>
 
 <ul>
   <li><p><strong>Copyleft</strong>. This is a term that can be difficult to 
@@ -185,21 +218,24 @@
     conceived, use the following format (this is an example for Swedish): 
     &ldquo;GNU's Not Unix (<span xml:lang="sv" lang="sv">
     GNU &auml;r inte Unix</span>)&rdquo;.</p></li>
+</ul>
 
-  <li><p>You can learn more about specific terms and the GNU philosophy by 
-    reading some articles such as the following, among others that you may 
-    find useful:</p>
-    <ul>
-      <li><a href="/philosophy/free-sw.html">What is Free Software?</a></li>
-      <li><a href="/philosophy/categories.html">Categories of Free and 
-        Nonfree Software</a></li>
+<p>Before installing or before submitting your translation for 
+installation in gnu.org:</p>
 
-      <li><a href="/philosophy/words-to-avoid.html">Words to Avoid</a></li>
-      <li><a href="/gnu/why-gnu-linux.html">What's in a Name?</a></li>
-      <li><a href="/philosophy/open-source-misses-the-point.html">Open 
-        Source Misses the Point of Free Software</a></li>
-    </ul>
-  </li>
+<ul>
+  <li>Have your translation reviewed by as many members of your team as 
+      possible. Peer review is crucial for the quality of the translation 
+      process. Too many errors are just missed (especially if they are 
+      obvious) when the translator does a final review of her own 
+      translation. One common technique to performing such reviews is to 
+      send the translation to the team's mailing list: members comment on
+      specific parts, quoting them appropriately. The result is better 
+      quality of the translation, since more people looked at it.</li>
+
+  <li>If there is no team established for your language, show your 
+      translations to friends who are not experts on free software or GNU, 
+      to see if they understand the translation clearly.</li>
 </ul>
 
 <h4 id="what">What to Translate</h4>
@@ -546,7 +582,7 @@
 
 <p>Updated:
 <!-- timestamp start -->
-$Date: 2012/06/10 08:09:41 $
+$Date: 2012/07/01 15:15:46 $
 <!-- timestamp end -->
 </p>
 </div>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]