[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
trans-coord/manual/web-trans index.html web-tra...
|
From: |
Yavor Doganov |
|
Subject: |
trans-coord/manual/web-trans index.html web-tra... |
|
Date: |
Mon, 30 Jan 2012 16:11:55 +0000 |
CVSROOT: /web/trans-coord
Module name: trans-coord
Changes by: Yavor Doganov <yavor> 12/01/30 16:11:54
Modified files:
manual/web-trans: index.html web-trans.dvi.gz web-trans.html
web-trans.html.gz web-trans.html_node.tar.gz
web-trans.info.tar.gz web-trans.pdf
web-trans.ps.gz web-trans.texi.tar.gz
web-trans.txt web-trans.txt.gz
manual/web-trans/html_node: CSS.html Capitalization.html
Co_002dleaders.html Commits.html
Copying-This-Manual.html
Introduction.html Joining.html
Leaders.html Leaving-A-Team.html
Mailing-Lists.html Managing.html
Members.html Migrating.html
New-Team.html Priorities.html
RTL.html Reports.html Review.html
SSI.html Savannah-Bugs.html
Savannah-Homepage.html
Savannah-Mailing-Lists.html
Savannah-Members.html
Savannah-News.html
Savannah-Patch.html
Savannah-Projects.html
Savannah-Support.html
Savannah-Tasks.html
Savannah-VCS.html Savannah.html
Stepping-Down.html
Submitting-as-PO.html
Submitting-as-Plain-Text.html
Submitting.html Summary.html
Terminology.html Tracking-Tasks.html
Translation-Managers.html
Translation-Tips.html
Unreviewed-Translations.html
index.html topbanner.html
Added files:
manual/web-trans/html_node: Distribution-Terms.html
Log message:
Update to gnun-0.5.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/index.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.dvi.gz?cvsroot=trans-coord&rev=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.html.gz?cvsroot=trans-coord&rev=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.html_node.tar.gz?cvsroot=trans-coord&rev=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.info.tar.gz?cvsroot=trans-coord&rev=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.pdf?cvsroot=trans-coord&rev=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.ps.gz?cvsroot=trans-coord&rev=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.texi.tar.gz?cvsroot=trans-coord&rev=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.txt?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/web-trans.txt.gz?cvsroot=trans-coord&rev=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/CSS.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Capitalization.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Co_002dleaders.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Commits.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Copying-This-Manual.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Introduction.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Joining.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Leaders.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Leaving-A-Team.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Mailing-Lists.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Managing.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Members.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Migrating.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/New-Team.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Priorities.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/RTL.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Reports.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Review.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/SSI.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Bugs.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Homepage.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Mailing-Lists.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Members.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-News.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Patch.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Projects.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Support.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-Tasks.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah-VCS.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Savannah.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Stepping-Down.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Submitting-as-PO.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Submitting-as-Plain-Text.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Submitting.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Summary.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Terminology.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Tracking-Tasks.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Translation-Managers.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Translation-Tips.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Unreviewed-Translations.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/index.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/topbanner.html?cvsroot=trans-coord&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/trans-coord/manual/web-trans/html_node/Distribution-Terms.html?cvsroot=trans-coord&rev=1.1
Patches:
Index: index.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/index.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- index.html 11 Nov 2009 14:50:41 -0000 1.4
+++ index.html 30 Jan 2012 16:11:48 -0000 1.5
@@ -3,42 +3,36 @@
<!--#include virtual="/server/banner.html" -->
<h2>GNU Web Translators Manual</h2>
-<!-- This document is in XML, and xhtml 1.0 -->
-<!-- Please make sure to properly nest your tags -->
-<!-- and ensure that your final document validates -->
-<!-- consistent with W3C xhtml 1.0 and CSS standards -->
-<!-- See validator.w3.org -->
-
<address>Free Software Foundation</address>
-<address>last updated November 11, 2009</address>
+<address>last updated January 30, 2012</address>
<p>This manual (web-trans) is available in the following formats:</p>
<ul>
<li><a href="web-trans.html">HTML
- (128K bytes)</a> - entirely on one web page.</li>
+ (132K bytes)</a> - entirely on one web page.</li>
<li><a href="html_node/index.html">HTML</a> - with one web page per
node.</li>
<li><a href="web-trans.html.gz">HTML compressed
- (36K gzipped characters)</a> - entirely on
+ (40K gzipped characters)</a> - entirely on
one web page.</li>
<li><a href="web-trans.html_node.tar.gz">HTML compressed
(44K gzipped tar file)</a> -
with one web page per node.</li>
<li><a href="web-trans.info.tar.gz">Info document
- (32K bytes gzipped tar file)</a>.</li>
+ (36K bytes gzipped tar file)</a>.</li>
<li><a href="web-trans.txt">ASCII text
- (96K bytes)</a>.</li>
+ (100K bytes)</a>.</li>
<li><a href="web-trans.txt.gz">ASCII text compressed
- (32K bytes gzipped)</a>.</li>
+ (36K bytes gzipped)</a>.</li>
<li><a href="web-trans.dvi.gz">TeX dvi file
- (56K bytes gzipped)</a>.</li>
+ (60K bytes gzipped)</a>.</li>
<li><a href="web-trans.ps.gz">PostScript file
- (160K bytes gzipped)</a>.</li>
+ (264K bytes gzipped)</a>.</li>
<li><a href="web-trans.pdf">PDF file
- (252K bytes)</a>.</li>
+ (348K bytes)</a>.</li>
<li><a href="web-trans.texi.tar.gz">Texinfo source
- (60K bytes gzipped tar file).</a></li>
+ (68K bytes gzipped tar file).</a></li>
</ul>
<p>You can <a href="http://shop.fsf.org/";>buy printed copies of
@@ -48,29 +42,28 @@
<p>(This page generated by the <a
href="http://savannah.gnu.org/cgi-bin/viewcvs/~checkout~/texinfo/texinfo/util/gendocs.sh";>gendocs.sh
script</a>.)</p>
-<!-- If needed, change the copyright block at the bottom. In general, -->
-<!-- all pages on the GNU web server should have the section about -->
-<!-- verbatim copying. Please do NOT remove this without talking -->
-<!-- with the webmasters first. -->
-<!-- Please make sure the copyright date is consistent with the document -->
-<!-- and that it is like this "2001, 2002" not this "2001-2002." -->
+<!-- If needed, change the copyright block at the bottom. In general,
+ all pages on the GNU web server should have the section about
+ verbatim copying. Please do NOT remove this without talking
+ with the webmasters first.
+ Please make sure the copyright date is consistent with the document
+ and that it is like this: "2001, 2002", not this: "2001-2002". -->
</div><!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.html" -->
<div id="footer">
-<p>
-Please send FSF & GNU inquiries to
+<p>Please send general FSF & GNU inquiries to
<a href="mailto:address@hidden";><address@hidden></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:address@hidden";><address@hidden></a>.
-</p>
+<a href="mailto:address@hidden";><address@hidden></a>.</p>
-<p>Copyright © 2009 Free Software Foundation, Inc.</p>
+<p>Copyright © 2012 Free Software Foundation, Inc.</p>
-<p>Verbatim copying and distribution of this entire article is
-permitted in any medium, provided this notice is preserved.</p>
+<p>Verbatim copying and distribution of this entire article are
+permitted worldwide, without royalty, in any medium, provided this
+notice, and the copyright notice, are preserved.</p>
</div>
</div>
Index: web-trans.dvi.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.dvi.gz,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
Binary files /tmp/cvsrctQlg and /tmp/cvsgU2gWC differ
Index: web-trans.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- web-trans.html 11 Nov 2009 14:50:42 -0000 1.4
+++ web-trans.html 30 Jan 2012 16:11:48 -0000 1.5
@@ -8,11 +8,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -91,7 +91,8 @@
</li></ul>
<li><a href="#Priorities">5.4 What To Translate</a>
<li><a href="#Capitalization">5.5 When To CAPITALIZE</a>
-<li><a href="#Terminology">5.6 Language-specific Terminology</a>
+<li><a href="#Distribution-Terms">5.6 Distribution Terms</a>
+<li><a href="#Terminology">5.7 Language-specific Terminology</a>
</li></ul>
<li><a name="toc_Summary" href="#Summary">6 Overview Of The Translation
Process</a>
<ul>
@@ -114,21 +115,21 @@
<h2 class="unnumbered">GNU Web Translators Manual</h2>
-<p>This manual is a guide for the <acronym>GNU</acronym> Web Translators.<br>
-Last updated on 10.11.2009, for <acronym>GNU</acronym>nited Nations
-version 0.4.
+<p>This manual is a guide for the GNU Web Translators.<br> Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
<pre class="sp">
</pre>
-Copyright © 2009 Free Software Foundation, Inc.
+Copyright © 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
<blockquote>
Permission is granted to copy, distribute and/or modify this document
-under the terms of the <acronym>GNU</acronym> Free Documentation License,
-Version 1.3 or any later version published by the Free Software
-Foundation; with no Invariant Sections, no Front-Cover Texts, and no
-Back-Cover Texts. A copy of the license is included in the section
-entitled “<acronym>GNU</acronym> Free Documentation License.”
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled “GNU Free
+Documentation License.”
</blockquote>
<ul class="menu">
@@ -157,10 +158,10 @@
<p>This manual is an attempt to describe in detail the process of
translating www.gnu.org articles—how to join a team, or start a new
one, the responsibilities of the team members and leaders, as well as
-some peculiarities of the <acronym>GNU</acronym> Project's website when it
comes
-to localization.
+some peculiarities of the GNU Project's website when it comes to
+localization.
- <p>The <acronym>GNU</acronym> website contains hundreds of documents, most
of them
+ <p>The GNU website contains hundreds of documents, most of them
philosophical articles (essays) and technical documents which need to be
translated to make them available to a broader audience. This is
especially important for the philosophy-related materials, as many
@@ -168,19 +169,20 @@
read such articles in their native language. Dealing with the task of
translating a website this large is a hard job, and too often people
volunteering as translators get frustrated or lose interest in keeping
-up with that work. Reading this manual, and the related
<acronym>GNUN</acronym>
-manual (see <a href="gnun.html#Top">GNUnited Nations</a>), is just the tip of
the iceberg. This is not meant to
-discourage any potential volunteer; rather, we prefer to be honest and
-to give preliminary estimation of the work/responsibility involved—if
-you feel you are not in a position to help you may move on to a smaller
-project before going through all procedures.
-
- <p>It is important to realize that being a <acronym>GNU</acronym> Web
Translator is
-a hard job at all levels, but your help is much appreciated and is
-invaluable contribution to the society. While there are many people who
-contribute to our community by writing free software (and their number
-is constantly increasing), the ones actively engaged in teaching others
-to appreciate and defend their freedom are only a few. Consequently and
+up with that work. Reading this manual, and the related GNUN manual
+(see <a href="gnun.html#Top">GNUnited Nations</a>), is
+just the tip of the iceberg. This is not meant to discourage any
+potential volunteer; rather, we prefer to be honest and to give
+preliminary estimation of the work/responsibility involved—if you feel
+you are not in a position to help you may move on to a smaller project
+before going through all procedures.
+
+ <p>It is important to realize that being a GNU Web Translator is a hard job
+at all levels, but your help is much appreciated and is invaluable
+contribution to the society. While there are many people who contribute
+to our community by writing free software (and their number is
+constantly increasing), the ones actively engaged in teaching others to
+appreciate and defend their freedom are only a few. Consequently and
rather unfortunately, there are not so many volunteers willing to
maintain on the long term translations of the various essays that
describe the fundamental values of the free software movement.
@@ -189,16 +191,16 @@
language teams. Each team has one or more co-ordinators, who are
responsible for the respective team. The co-ordinators participate in
the Savannah ‘<samp><span class="samp">trans-coord</span></samp>’
organizational project, which is managed
-by the <acronym>GNU</acronym> Web Translation Managers. The manual is
organized
-in chapters that follow the organizational structure of the whole
+by the GNU Web Translation Managers. The manual is organized in
+chapters that follow the organizational structure of the whole
translation project.
<p>If you wish to join a translation team or contribute a translation or
-two, see <a href="#Members">Members</a>. If your intention is to form a
translation
-team, see <a href="#Leaders">Leaders</a>. The chapter about the
‘<samp><span class="samp">trans-coord</span></samp>’
-administrators (a.k.a. <dfn><acronym>GNU</acronym> Translation Managers</dfn>)
-describes all the responsibilities and procedures involved in performing
-this duty. See <a href="#Translation-Managers">Translation Managers</a>.
+two, see <a href="#Members">Members</a>. If your intention is to form a
translation team,
+see <a href="#Leaders">Leaders</a>. The chapter about the ‘<samp><span
class="samp">trans-coord</span></samp>’
+administrators (a.k.a. <dfn>GNU Translation Managers</dfn>) describes all the
+responsibilities and procedures involved in performing this duty.
+See <a href="#Translation-Managers">Translation Managers</a>.
<div class="node">
<a name="Members"></a>
@@ -256,11 +258,11 @@
next chapter, see <a href="#Leaders">Leaders</a>.
<p>Contacting the team is best done via Savannah—each translation team
-has its own project, named ‘<samp><span
class="samp">www-</span><var>lang</var></samp>’, with the project page
-being
+has its own project, named ‘<samp><span
class="samp">www-</span><var>lang</var></samp>’, with the project
+page being
<<code>https://savannah.gnu.org/projects/www-</code><var>lang</var>>.
-Usually teams have mailing lists, either on Savannah or on some external
-site. Some teams have homepages,
+Usually teams have mailing lists, typically in the form
+<a href="mailto:www-<var>lang</var>address@hidden">www-<var>lang</var>-<small
class="dots">...</small>@gnu.org</a>. Some teams have homepages,
<<code>http://gnu.org/server/standards/translations/</code><var>lang</var>>
with additional contact details and procedures for team members.
@@ -317,7 +319,7 @@
<h4 class="subsection">2.2.1 How To Submit a Translation in PO Format</h4>
-<p>All translations<a rel="footnote" href="#fn-1"
name="fnd-1"><sup>1</sup></a> are maintained via <acronym>GNUN</acronym> (see
+<p>All translations<a rel="footnote" href="#fn-1"
name="fnd-1"><sup>1</sup></a> are maintained via GNUN (see
<a
href="http://www.gnu.org/software/gnun/";>http://www.gnu.org/software/gnun/</a>),
which significantly eases
maintenance and avoids the unpleasant situation where a translation is
lagging behind the original. See <a
href="gnun.html#Advantages">Advantages</a>.
@@ -351,8 +353,8 @@
your message. The web-translators will review (to the best of their
ability) the translation and will install it in the repository.
- <li>In order <acronym>GNUN</acronym> to be able to generate (and
subsequently update)
-a gettextized translation, the language should have the server templates
+ <li>In order GNUN to be able to generate (and subsequently update) a
+gettextized translation, the language should have the server templates
available as PO files. These templates are short, and translating them
shouldn't take much time. If the language code is present in the
<code>TEMPLATE_LINGUAS</code> variable at <samp><span
class="file">server/gnun/gnun.mk</span></samp>, then you
@@ -364,6 +366,9 @@
submit them in the usual way, together with the translation of the
essay.
+ <p>Additional templates are defined via the <var>extra-templates</var>
variable
+in <samp><span class="file">server/gnun/gnun.mk</span></samp>.
+
<p>If you don't want to translate the templates for whatever
reason—do
not worry, the web-translators will install empty templates (which means
the English strings will be used).
@@ -390,9 +395,9 @@
<p>If you feel the procedure described in the previous section is too
burdensome and unfeasible for you to follow, you can still submit a
translation in plain text. It will be manually converted to PO file by
-the <acronym>GNU</acronym> Web Translation Managers, which can be tricky
-sometimes, and naturally, means more work for them and slower processing
-of your request.
+the GNU Web Translation Managers, which can be tricky sometimes, and
+naturally, means more work for them and slower processing of your
+request.
<p>You should <em>never</em> translate the HTML markup—i.e. <em>do
not</em>
use the “View Source” functionality of your browser to translate
the
@@ -535,7 +540,7 @@
<p>Examine the layout and structure of the repository. Basically, it is
mapped to the URL locations, more or less. Take a look at the most
important materials to translate under <samp><span
class="file">/philosophy</span></samp>, <samp><span
class="file">/gnu</span></samp>,
-<samp><span class="file">/ditros</span></samp>, <samp><span
class="file">/copyleft</span></samp> and <samp><span
class="file">/licenses</span></samp> directories just
+<samp><span class="file">/distros</span></samp>, <samp><span
class="file">/copyleft</span></samp> and <samp><span
class="file">/licenses</span></samp> directories just
to get a rough estimate about the amount of work involved. If you are
still not scared and determined to go on further, excellent.
@@ -543,9 +548,9 @@
translatable articles has a <samp><span class="file">/po</span></samp>
sub-directory, which is where the
new canonical source format of the translations is stored.
- <li>Assuming you have already read the <acronym>GNUN</acronym> manual
entirely (as
-recommended in the beginning of this section), check if your language
-code is present in the variable <code>TEMPLATE_LINGUAS</code> at
+ <li>Assuming you have already read the GNUN manual entirely (as
recommended
+in the beginning of this section), check if your language code is
+present in the variable <code>TEMPLATE_LINGUAS</code> at
<samp><span class="file">server/gnun/gnun.mk</span></samp>. If it is not, the
first thing to do is to
translate and submit to <a href="mailto:address@hidden";>address@hidden</a> the
following
files (all in the <samp><span class="file">server/po/</span></samp> directory):
@@ -636,8 +641,8 @@
</ul>
<p>You'll have to request subscription to ‘<samp><span
class="samp">www-discuss</span></samp>’
-yourself—this list is managed by the <acronym>GNU</acronym> Webmasters,
but all
-team leaders are required to subscribe in order to receive important
+yourself—this list is managed by the GNU Webmasters, but all team
+leaders are required to subscribe in order to receive important
site-wide announcements.
</ol>
@@ -881,8 +886,8 @@
<p>If you wish to volunteer as webmaster and help with generic webmaster
work and RT tickets, that is perfectly fine—please follow the
-established (by the <acronym>GNU</acronym> Webmasters) procedure. If you are
-approved, you can modify such pages wearing your “webmaster's hat”.
+established (by the GNU Webmasters) procedure. If you are approved, you
+can modify such pages wearing your “webmaster's hat”.
<p>If a particular page has issues with the markup which create problems
for your language, please inform <a
href="mailto:address@hidden";>address@hidden</a>.
@@ -962,24 +967,29 @@
Savannah project for each language is obvious: it's a standard way to
find information for translation teams and their contacts.
- <p>Using external hosting facilities is sometimes justified—for
example,
-some languages have a single mailing list for all free software-related
-translations, where all translators co-operate. Others have already
-established repositories and/or bug tracking systems where usual
-contributors already have access. Some team members prefer to work
-within the established infrastructure of a broad translation team (for
-whatever reason), and this is entirely acceptable. However, it is
-important to remember that regardless of the technical resources which a
-team decides to use, the responsibility of the team co-ordinator remains
-the same.
+ <p>Using external hosting facilities may seem justified sometimes. Some
+teams may have already established repositories and/or bug tracking
+systems where usual contributors already have access. Some team
+members prefer to work within the established infrastructure of a
+broad translation team (for whatever reason), but this is discouraged.
+It is required that every team has a mailing list at Savannah
+(see <a href="#Savannah-Mailing-Lists">Savannah Mailing Lists</a>), because it
is easier to pass its
+management to the new co-ordinator when the old one steps down, and it
+helps to keep the archives at one place for future members of the
+team. Likewise, it is better to use Savannah for the team's
+repository and bugs/tasks, but this is not mandatory.
+
+ <p>However, it is important to remember that regardless of the technical
+resources which a team decides to use, the responsibility of the team
+co-ordinator remains the same.
<p>Those teams that are using Savannah have a broad variety of tools at
hand: team membership management, documents, trackers (bugs, tasks and
support), alerts, CVS (and any other VCS that Savannah supports), home
-pages, mailing lists, etc. How each team uses these resources is up to
-the team itself, but it often turns out to choose Savannah for nearly
-all of the team activities, as it requires almost zero work; the
-Savannah Hackers are happy to support us.
+pages, etc. How each team uses these resources is up to the team
+itself, but it often turns out to choose Savannah for nearly all of
+the team activities, as it requires almost zero work; the Savannah
+Hackers are happy to support us.
<p>Whatever you (in your capacity as a team leader) decide, please do it
with caution: some organizational decisions may become ineffective as
@@ -1186,15 +1196,21 @@
<h5 class="subsubsection">3.2.3.8 Managing Mailing Lists</h5>
-<p>You can create new mailing lists via the Savannah interface. However,
+<p>Every team should have a mailing list on lists.gnu.org and use it for
+internal communications. All active translators should be on the
+list. The list owner should be the co-ordinator of the team. The
+name of the list should begin with ‘<samp><span
class="samp">www-</span><var>lang</var><span
class="samp">-</span></samp>’.
+
+ <p>The list will make it possible for the GNU project to contact the team
+when the co-ordinator disappears; its archive will also give access to
+the history for new translators.
+
+ <p>You can create new mailing lists via the Savannah interface. However,
this should be done after some thought. If the project membership is
low (<= 10 members), there is no need to create more than one mailing
-list. If there is a general translation list common for all translators
-of the language (i.e. GNOME, GNUstep, KDE, and free software in
-general), there is no reason at all to create a list at Savannah.
+list.
- <p>You can redirect all messages generated by the trackers to any list
-(including those that are not on GNU servers).
+ <p>You can redirect all messages generated by the trackers to any list.
<div class="node">
<a name="Savannah-VCS"></a>
@@ -1398,7 +1414,8 @@
<li><a accesskey="3" href="#CSS">CSS</a>: General advice how
to use CSS.
<li><a accesskey="4" href="#Priorities">Priorities</a>: What to
translate as a priority.
<li><a accesskey="5" href="#Capitalization">Capitalization</a>: To
CAPITALIZE or not?
-<li><a accesskey="6" href="#Terminology">Terminology</a>: Dealing
with terminology issues.
+<li><a accesskey="6" href="#Distribution-Terms">Distribution Terms</a>:
Translating distribution terms.
+<li><a accesskey="7" href="#Terminology">Terminology</a>: Dealing
with terminology issues.
</ul>
<div class="node">
@@ -1412,10 +1429,11 @@
<h3 class="section">5.1 Migration To The New Style</h3>
<p>Migration to the new style should be straightforward, and this is one of
-the problems <acronym>GNUN</acronym> set out to solve. If you have to migrate
-old-style translations, see <a href="gnun.html#Migrating">Migrating</a>. If
the old translation is HTML 2.0 (or 3.2), you still have to
-take care about the inner markup. Overall, it is substantially easier
-than doing all of it manually.
+the problems GNUN set out to solve. If you have to migrate old-style
+translations, see <a href="gnun.html#Migrating">Migrating</a>.
+If the old translation is HTML 2.0 (or 3.2), you still have to take care
+about the inner markup. Overall, it is substantially easier than doing
+all of it manually.
<p>Subsequent migrations to newer (X)HTML standards and newer look and feel
of the website are supposed to happen semi-automatically, although this
@@ -1432,11 +1450,11 @@
<h3 class="section">5.2 Summary of SSI <code>#include</code>s</h3>
-<p>The GNU Project's website uses <acronym>SSI</acronym> (Server Side
Includes) to
-manage some common parts that are the same in many of the articles.
-With the help of <acronym>GNUN</acronym> their handling should be behind the
-scenes, but for some of them manual intervention is needed. Here is a
-(possibly incomplete) list of the <code>#include</code>'s used:
+<p>The GNU Project's website uses SSI (Server Side Includes) to manage some
+common parts that are the same in many of the articles. With the help
+of GNUN their handling should be behind the scenes, but for some of them
+manual intervention is needed. Here is a (possibly incomplete) list of
+the <code>#include</code>'s used:
<dl>
<dt><samp><span class="file">server/banner.html</span></samp><dd>This file
contains only <code>#include</code> directives, so the
@@ -1454,13 +1472,13 @@
file.
<br><dt><samp><span
class="file">server/footer-text.html</span></samp><dd>This is a very short file
currently containing the “back to top” link.
-Also translatable via <acronym>GNUN</acronym>.
+Also translatable via GNUN.
<br><dt><samp><span class="file">server/header.html</span></samp><dd>The
declaration that is included in literally every file. It is
maintained manually, as it does not make much sense to put it under
-<acronym>GNUN</acronym>'s control (there are no translatable strings).
Remember
-to specify the proper <code>xml:lang</code> and <code>lang</code> attributes,
and
-for RTL languages, the <code>dir</code> attribute. For example, the file
+GNUN's control (there are no translatable strings). Remember to specify
+the proper <code>xml:lang</code> and <code>lang</code> attributes, and for RTL
+languages, the <code>dir</code> attribute. For example, the file
<samp><span class="file">header.ar.html</span></samp> should contain this line:
<pre class="example"> <html
xmlns="http://www.w3.org/1999/xhtml"; xml:lang="ar" lang="ar"
@@ -1474,6 +1492,18 @@
declared in the <code><meta></code> element at
<samp><span class="file">server/head-include-1.</span><var>lang</var><span
class="file">.html</span></samp>, so browsers will obey it.
+ <p>The encoding should be UTF-8. This is required because the English
text
+in the articles serves as a replacement of the translation when the latter
+is not complete, and because all translated pages share automatically
+generated lists of translations.
+
+ <br><dt><samp><span
class="file">server/html5-header.html</span></samp><dd>This file is included in
newer pages using some entities introduced
+in HTML5 draft. We have to distinguish those pages since some features
+of HTML4 were rejected in HTML5, and our old pages don't validate
+as HTML5.
+
+ <br><dt><samp><span
class="file">server/html5-head-include-1.html</span></samp><dd>Likewise, this
file replaces head-include-1.html for HTML5 pages.
+
<br><dt><samp><span
class="file">server/head-include-2.html</span></samp><dd>Imports the standard
CSS, which can be overriden. See <a href="#CSS">CSS</a>.
<br><dt><samp><span class="file">server/footer.html</span></samp><dd>This
is a very short and simple file (at least at the time of writing),
@@ -1481,6 +1511,15 @@
manually, so just add <var>lang</var> to the filename, in order the localized
<samp><span class="file">footer-text.</span><var>lang</var><span
class="file">.html</span></samp> to be included.
+ <br><dt><samp><span
class="file">server/outdated.html</span></samp><dd>This file is automatically
included in outdated translations. It
+contains respective message with links to the English file and
+to a generated difference of the current revision of the English
+file against the most recent revision that has a complete translation.
+It is only included in articles affected by “grace period” because
+in those cases the outdated passages are replaced with English text,
+and it is evident without any notices that there is no complete
+and up to date translation.
+
<br><dt><samp><span
class="file">translations.include</span></samp><dd>The list of translations for
the homepage (and only the homepage). It
is maintained manually; in order the link to a translation to appear on
all of the homepages, it has to be present here.
@@ -1501,8 +1540,8 @@
HTML version of the license without the gnu.org style; 2) to prevent
strings sneaking in the <samp><span class="file">.pot</span></samp> files, as
licenses have only
unofficial translations, hosted elsewhere. Nothing special should be
-done about these SSI directives; the files generated by <acronym>GNUN</acronym>
-include them verbatim as they should not be translated.
+done about these SSI directives; the files generated by GNUN include
+them verbatim as they should not be translated.
<br><dt><samp><span
class="file">server/sidebar*.html</span></samp><dd>These files are
deprecated—they are remnants from an older design that
lived shortly in the middle between the old classic design and the
@@ -1511,17 +1550,29 @@
<samp><span class="command">grep</span></samp> to check this.
</dl>
- <p>The files <samp><span class="file">header.html</span></samp>,
<samp><span class="file">head-include-1.html</span></samp>,
-<samp><span class="file">head-include-2.html</span></samp>, <samp><span
class="file">banner.html</span></samp>,
-<samp><span class="file">body-include-1.html</span></samp>, <samp><span
class="file">body-include-2.html</span></samp>,
-<samp><span class="file">footer.html</span></samp> and <samp><span
class="file">footer-text.html</span></samp> in the <samp><span
class="file">server</span></samp>
-sub-directory are what webmasters call “the server templates”.
These
-files are included in almost every article, translated or not. They are
-somewhat important, as an error made in translating them propagates
-everywhere. The server templates, the homepages, and whatsnew
-(a.k.a. “GNU News”) are being rebuilt by <acronym>GNUN</acronym>
whenever there
-is a change in the original English files; the <code>GRACE</code> variable has
-no effect for them. See <a href="gnun.html#Runtime-Variables">Runtime
Variables</a>.
+ <p>The files
+
+<!-- Use @itemize to avoid `underfull \hbox' warnings from TeX. -->
+ <ul>
+<li><samp><span class="file">header.html</span></samp>
+<li><samp><span class="file">head-include-1.html</span></samp>
+<li><samp><span class="file">html5-header.html</span></samp>
+<li><samp><span class="file">html5-head-include-1.html</span></samp>
+<li><samp><span class="file">head-include-2.html</span></samp>
+<li><samp><span class="file">banner.html</span></samp>
+<li><samp><span class="file">body-include-1.html</span></samp>
+<li><samp><span class="file">body-include-2.html</span></samp>
+<li><samp><span class="file">footer.html</span></samp>
+<li><samp><span class="file">footer-text.html</span></samp>
+</ul>
+
+ <p>in the <samp><span class="file">server</span></samp> sub-directory are
what webmasters call “the
+server templates”. These files are included in almost every article,
+translated or not. They are somewhat important, as an error made in
+translating them propagates everywhere. The server templates, the
+homepages, and whatsnew (a.k.a. “GNU News”) are being rebuilt by
+GNUN whenever there is a change in the original English files; the
+<code>GRACE</code> variable has no effect for them. See <a
href="gnun.html#Runtime-Variables">Runtime Variables</a>.
<div class="node">
<a name="CSS"></a>
@@ -1569,6 +1620,14 @@
include the license notice from the <samp><span
class="file">style.css</span></samp>, with a short
comment.
+ <p>If using the default CSS style for translations does not give the
+expected good results, or there are other problems (significant or not)
+that obstruct reading and/or worsen the look from aesthetic point of
+view, please write to <a href="mailto:address@hidden";>address@hidden</a> with
a description of
+the issue. If there are several unrelated problems, send separate
+messages with appropriate explanation (which may include a demonstration
+of the bug, such as a screenshot).
+
<ul class="menu">
<li><a accesskey="1" href="#topbanner">topbanner</a>: How to
localize the topbanner image.
<li><a accesskey="2" href="#RTL">RTL</a>: Special notes about
RTL languages.
@@ -1641,11 +1700,10 @@
style="..."></code>. In such situations, it is quite possible that the
general language-specific CSS does not help, and the translation of this
specific article does not look correct. Please write to
-<a href="mailto:address@hidden";>address@hidden</a>; if you have a working
solution
-that works for both cases—so much the better. For general issues that
-affect your language and require a general solution, write to
-<a href="mailto:address@hidden";>address@hidden</a> or <a
href="mailto:address@hidden";>address@hidden</a>, precisely
-describing the problem.
+<a href="mailto:address@hidden";>address@hidden</a>; if you have a working
solution that works
+for both cases—so much the better. For general issues that affect
+your language and require a general solution, write to
+<a href="mailto:address@hidden";>address@hidden</a> as well, precisely
describing the problem.
<div class="node">
<a name="Priorities"></a>
@@ -1661,25 +1719,42 @@
<p>The article
<a
href="http://www.gnu.org/server/standards/translations/priorities.html";>http://www.gnu.org/server/standards/translations/priorities.html</a>
lists the most important essays to translate. In general, articles in
-the directories <samp><span class="file">philosophy</span></samp>, <samp><span
class="file">gnu</span></samp>, <samp><span class="file">copyleft</span></samp>
and
-<samp><span class="file">licenses</span></samp> are important. The others may
be deferred for a time
-when a team completes most of the important translations, or they can be
-translated as a “rest”–in translators' parlance this means
doing
-something in between which is typically easier to handle.
+the directories <samp><span class="file">philosophy</span></samp>, <samp><span
class="file">gnu</span></samp>, <samp><span class="file">distros</span></samp>,
+<samp><span class="file">copyleft</span></samp> and <samp><span
class="file">licenses</span></samp> are important. The others may be
+deferred for a time when a team completes most of the important
+translations, or they can be translated as a “rest”–in
translators'
+parlance this means doing something in between which is typically easier
+to handle.
+
+ <p>It is very important to keep existing translations up-to-date with the
+respective English originals. This task should be higher priority than
+translating new articles. GNUN's <code>report</code> rule can help you to
+identify precisely which articles need updating; see <a
href="gnun.html#report">report</a>. There is a monthly cronjob which
+sends a verbose output to each team—by default, the address(es) used
+is the Savannah account(s) of the admin(s) of the specific translation
+project. If you want them changed, please write to
+<a href="mailto:address@hidden";>address@hidden</a>.
+
+ <p>It is strongly recommended translation teams to attempt to recruit
+native English speakers in order to improve their translation process.
+Translators sometimes misunderstand English idioms and expressions, and
+as a result, they translate them incorrectly or in ways that are
+suboptimal and confusing. These errors are trivial to discover for the
+native English speaker.
<p><em>Do not</em> translate articles under these directories:
<dl>
<dt><samp><span class="file">software/</span><var>pkg</var><span
class="file">/</span></samp><dd>These pages are maintained by the respective
<var>pkg</var> maintainers.
-<acronym>GNUN</acronym> does not support them for the time being, as they
reside
-in separate repositories. The procedures for contributing translations
-of such articles are not yet settled.
+GNUN does not support them for the time being, as they reside in
+separate repositories. The procedures for contributing translations of
+such articles are not yet settled.
<br><dt><samp><span class="file">brave-gnu-world</span></samp><dd>The
Brave GNU World initiative has been abandoned long time ago, and
-it's in a separate repository—thus not supported by the automatic
-<acronym>GNUN</acronym> build job.
+it's in a separate repository—thus not supported by the automatic GNUN
+build job.
- <br><dt><samp><span class="file">home.shtml</span></samp><dd>There is not
problem to translate this page, but don't make the mistake
+ <br><dt><samp><span class="file">home.html</span></samp><dd>There is not
problem to translate this page, but don't make the mistake
to pick it up as your first translation. It is modified often,
sometimes intensively, and only active team members should take that
road.
@@ -1694,7 +1769,7 @@
<div class="node">
<a name="Capitalization"></a>
<p><hr>
-Next: <a rel="next" accesskey="n" href="#Terminology">Terminology</a>,
+Next: <a rel="next" accesskey="n" href="#Distribution-Terms">Distribution
Terms</a>,
Previous: <a rel="previous" accesskey="p"
href="#Priorities">Priorities</a>,
Up: <a rel="up" accesskey="u" href="#Translation-Tips">Translation
Tips</a>
@@ -1702,10 +1777,12 @@
<h3 class="section">5.5 When To CAPITALIZE</h3>
-<p>The English language has strict rules for capitalization of titles,
-chapters, acronym expansions and the like. They do not make sense for
-many other languages, but unfortunately, many translators
-<em>erroneously duplicate</em> the capitalization in their translation.
+<p>The English language has some rules for capitalization of titles,
+chapters, acronym expansions and the like. These rules are neither
+strict nor uniform, although the gnu.org website strives to apply them
+consistently. They do not make sense for many other languages, but
+unfortunately, many translators <em>erroneously duplicate</em> the
+capitalization in their translation.
<p>Examples for common (and correct) English capitalization is the title of
the article “Why Software Should Be Free” or “Free Software
@@ -1722,14 +1799,74 @@
them as ‘<samp><span class="samp">français</span></samp>’
or ‘<samp><span class="samp">português</span></samp>’,
respectively.
<div class="node">
-<a name="Terminology"></a>
+<a name="Distribution-Terms"></a>
<p><hr>
+Next: <a rel="next" accesskey="n" href="#Terminology">Terminology</a>,
Previous: <a rel="previous" accesskey="p"
href="#Capitalization">Capitalization</a>,
Up: <a rel="up" accesskey="u" href="#Translation-Tips">Translation
Tips</a>
</div>
-<h3 class="section">5.6 Language-specific Terminology</h3>
+<h3 class="section">5.6 Distribution Terms</h3>
+
+<p>Most www.gnu.org articles are released under the terms of
+the Creative Commons Attribution-NoDerivs 3.0 United States license.
+The exact HTML for English pages to use is:
+
+<pre class="example"> 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>.
+</pre>
+ <p>Pages in other languages should translate this notice, and should link
+to a translated version of the Creative Commons license “deed” if
it's
+available. Creative Commons provides standard text for this in all the
+languages they support, and we should use that wording whenever
+possible. To do that, follow these steps:
+
+ <ul>
+<li>Check at the bottom of the English deed page to see the list of
+languages they support. Follow the link the language that you want a
+translation for, if available.
+
+ <li>Follow the “Use this license for your own work” link near
the bottom
+of the translated deed page—it's in distinct yellow text.
+
+ <li>The textarea on that page provides standard HTML. Note that we're not
+using the graphic, just the text.
+
+ </ul>
+
+ <p>For example, here's the text they provide for German:
+
+<pre class="example"> Dieses Werk bzw. Inhalt steht unter einer <a
rel="license"
+
href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.de">Creative
+ Commons Namensnennung-Keine Bearbeitung 3.0 Vereinigte Staaten von
+ Amerika Lizenz</a>.
+</pre>
+ <p>Note that the link in this text is changed to point directly to the
+German language deed. We should always link to a copy of the license
+deed that's in the same language as the page itself.
+
+ <p>Pages in languages that aren't supported by CC should prepare their own
+translation, use it consistently throughout pages translated to that
+language, and link to the English language deed.
+
+ <p>Note that translations should <em>not</em> change the jurisdiction of the
+license; they should <em>always</em> link to the CC BY-ND 3.0 <em>United
+States</em> license, and <em>not</em> a different port like CC BY-ND 3.0
+Japan. This is because there are substantive differences between the way
+different ports handle moral rights issues, and we prefer the specific
+terms that are in the United States license.
+
+<div class="node">
+<a name="Terminology"></a>
+<p><hr>
+Previous: <a rel="previous" accesskey="p"
href="#Distribution-Terms">Distribution Terms</a>,
+Up: <a rel="up" accesskey="u" href="#Translation-Tips">Translation
Tips</a>
+
+</div>
+
+<h3 class="section">5.7 Language-specific Terminology</h3>
<p>This is a very important topic, not yet covered by this manual.
@@ -1780,8 +1917,8 @@
participants in the process.
<dl>
-<dt><a href="mailto:address@hidden";>address@hidden</a><dd>The basic discussion
list of the <acronym>GNU</acronym> Webmasters. All team
-leaders are required to subscribe.
+<dt><a href="mailto:address@hidden";>address@hidden</a><dd>The basic discussion
list of the GNU Webmasters. All team leaders are
+required to subscribe.
<p>This is a private mailing list.
@@ -1793,37 +1930,42 @@
<p>This is a public mailing list, so everyone can subscribe and review the
archives. The ‘<samp><span class="samp">www</span></samp>’ CVS
repository is also public.
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>The main
discussion list for the <acronym>GNU</acronym> Web Translators. Team
-leaders must subscribe, as errors from <acronym>GNUN</acronym> are mailed
here.
-Team members are welcome to join as well, provided they are already
-members of ‘<samp><span
class="samp">www-</span><var>lang</var></samp>’. If they want to
subscribe with a
-different email address, a verification from the team leader is
-required.
+ <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>The main
discussion list for the GNU Web Translators. Team leaders must
+subscribe, as errors from GNUN are mailed here. Team members are
+welcome to join as well, provided they are already members of
+‘<samp><span class="samp">www-</span><var>lang</var></samp>’. If
they want to subscribe with a different email
+address, a verification from the team leader is required.
<p>This is a private mailing list, although there is no absolute reason
for
that. It may become public in the future.
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>This is a
list for notifications about gnunews and <acronym>GNU</acronym>nited
-Nations releases. It is not mandatory to subscribe to it, although the
-traffic is very low. If you want to track only <acronym>GNUN</acronym> release
-announcements, subscribe to the ‘<samp><span
class="samp">gnun</span></samp>’ topic via Mailman's user
-interface. Likewise, if you want to recieve only <dfn>What's New</dfn>
-updates, subscribe to the ‘<samp><span
class="samp">whatsnew</span></samp>’ topic. In the near future,
-there will be automatic announcements for newly available English
-articles and translations.
+ <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>This is a
list for notifications about gnunews and GNUnited Nations
+releases. It is not mandatory to subscribe to it, although the traffic
+is very low. If you want to track only GNUN release announcements,
+subscribe to the ‘<samp><span class="samp">gnun</span></samp>’
topic via Mailman's user interface.
+Likewise, if you want to recieve only <dfn>What's New</dfn> updates,
+subscribe to the ‘<samp><span class="samp">whatsnew</span></samp>’
topic.
+
+ <p>Automatic announcements for new gnu.org translations (provided they're
+handled by GNUN) are also delivered here. There are separate
+‘<samp><var>lang</var><span class="samp">-ann</span></samp>’
topics for every GNUN-aware language, so it is a
+good idea to advertise this capability widely among your local
+community. For example, if a reader wants to be informed only about new
+Spanish translations, she can just subscribe to the ‘<samp><span
class="samp">es-ann</span></samp>’
+mailing list topic.
<p>This is a public mailing list.
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>All
development of <acronym>GNUN</acronym> happens here. Commits to the
-‘<samp><span class="samp">trans-coord</span></samp>’ repository
are also sent to this list.
+ <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>All
development of GNUN happens here. Commits to the ‘<samp><span
class="samp">trans-coord</span></samp>’
+repository are also sent to this list.
<p>This is a public list, and <a
href="mailto:address@hidden";>address@hidden</a> is an alias.
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>All build
logs from the various <acronym>GNUN</acronym> automatic builds are sent
-to this list, so it is not a very pleasant thing to be subscribed,
-especially if you are not interested in <acronym>GNUN</acronym>'s internals.
-However, everyone can use the web archives to check the log why a
-particular article was not built at expected.
+ <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>All build
logs from the various GNUN automatic builds are sent to this
+list, so it is not a very pleasant thing to be subscribed, especially if
+you are not interested in GNUN's internals. However, everyone can use
+the web archives to check the log why a particular article was not built
+at expected.
<p>This is a public list.
</dl>
@@ -1857,8 +1999,7 @@
to be members, as bugs reported to <a
href="mailto:address@hidden";>address@hidden</a> are
often redirected to the ‘<samp><span
class="samp">trans-coord</span></samp>’ ‘<samp><span
class="samp">Bugs</span></samp>’ tracker.
- <p>The admins of this project are the <acronym>GNU</acronym> Web
Translation
-Managers.
+ <p>The admins of this project are the GNU Web Translation Managers.
<br><dt>‘<samp><span
class="samp">www-</span><var>lang</var></samp>’<dd>All translation team
leaders of the language <var>lang</var> should be
members of the project ‘<samp><span
class="samp">www-</span><var>lang</var></samp>’. The admins of the
project
Index: web-trans.html.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.html.gz,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
Binary files /tmp/cvsmSrBKh and /tmp/cvsGn1ioE differ
Index: web-trans.html_node.tar.gz
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/web-trans.html_node.tar.gz,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
Binary files /tmp/cvs9E9zqi and /tmp/cvsK0jm5E differ
Index: web-trans.info.tar.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.info.tar.gz,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
Binary files /tmp/cvsVHj0pl and /tmp/cvstIfP5H differ
Index: web-trans.pdf
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.pdf,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
Binary files /tmp/cvsfVsqyl and /tmp/cvs12oGhI differ
Index: web-trans.ps.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.ps.gz,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
Binary files /tmp/cvs7WfQNn and /tmp/cvsyj0JzK differ
Index: web-trans.texi.tar.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.texi.tar.gz,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
Binary files /tmp/cvsChvYEm and /tmp/cvsonFqsJ differ
Index: web-trans.txt
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.txt,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- web-trans.txt 11 Nov 2009 14:50:43 -0000 1.4
+++ web-trans.txt 30 Jan 2012 16:11:49 -0000 1.5
@@ -38,7 +38,8 @@
5.3.2 Specific Issues Related to RTL
5.4 What To Translate
5.5 When To CAPITALIZE
- 5.6 Language-specific Terminology
+ 5.6 Distribution Terms
+ 5.7 Language-specific Terminology
6 Overview Of The Translation Process
6.1 Related Mailing Lists
6.2 Savannah Projects Membership
@@ -49,9 +50,9 @@
**************************
This manual is a guide for the GNU Web Translators.
-Last updated on 10.11.2009, for GNUnited Nations version 0.4.
+Last updated on 30.01.2012, for GNUnited Nations version 0.5.
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -87,10 +88,10 @@
It is important to realize that being a GNU Web Translator is a hard
job at all levels, but your help is much appreciated and is invaluable
-contribution to the society. While there are many people who
-contribute to our community by writing free software (and their number
-is constantly increasing), the ones actively engaged in teaching others
-to appreciate and defend their freedom are only a few. Consequently and
+contribution to the society. While there are many people who contribute
+to our community by writing free software (and their number is
+constantly increasing), the ones actively engaged in teaching others to
+appreciate and defend their freedom are only a few. Consequently and
rather unfortunately, there are not so many volunteers willing to
maintain on the long term translations of the various essays that
describe the fundamental values of the free software movement.
@@ -145,9 +146,10 @@
Contacting the team is best done via Savannah--each translation team
has its own project, named `www-LANG', with the project page being
<https://savannah.gnu.org/projects/www-LANG>. Usually teams have
-mailing lists, either on Savannah or on some external site. Some teams
-have homepages, <http://gnu.org/server/standards/translations/LANG>
-with additional contact details and procedures for team members.
+mailing lists, typically in the form <address@hidden>. Some
+teams have homepages,
+<http://gnu.org/server/standards/translations/LANG> with additional
+contact details and procedures for team members.
You could also write directly to the team leader via the Savannah
interface--that way you request will be recorded by Savannah and can be
@@ -229,6 +231,9 @@
`server/po/footer-text.LANG.po'--you can translate and submit them
in the usual way, together with the translation of the essay.
+ Additional templates are defined via the EXTRA-TEMPLATES variable
+ in `server/gnun/gnun.mk'.
+
If you don't want to translate the templates for whatever
reason--do not worry, the web-translators will install empty
templates (which means the English strings will be used).
@@ -366,7 +371,7 @@
Examine the layout and structure of the repository. Basically, it
is mapped to the URL locations, more or less. Take a look at the
most important materials to translate under `/philosophy', `/gnu',
- `/ditros', `/copyleft' and `/licenses' directories just to get a
+ `/distros', `/copyleft' and `/licenses' directories just to get a
rough estimate about the amount of work involved. If you are
still not scared and determined to go on further, excellent.
@@ -660,8 +665,8 @@
If you wish to volunteer as webmaster and help with generic webmaster
work and RT tickets, that is perfectly fine--please follow the
-established (by the GNU Webmasters) procedure. If you are approved,
-you can modify such pages wearing your "webmaster's hat".
+established (by the GNU Webmasters) procedure. If you are approved, you
+can modify such pages wearing your "webmaster's hat".
If a particular page has issues with the markup which create problems
for your language, please inform <address@hidden>. For
@@ -738,24 +743,29 @@
Savannah project for each language is obvious: it's a standard way to
find information for translation teams and their contacts.
- Using external hosting facilities is sometimes justified--for
-example, some languages have a single mailing list for all free
-software-related translations, where all translators co-operate.
-Others have already established repositories and/or bug tracking
+ Using external hosting facilities may seem justified sometimes. Some
+teams may have already established repositories and/or bug tracking
systems where usual contributors already have access. Some team
members prefer to work within the established infrastructure of a broad
-translation team (for whatever reason), and this is entirely
-acceptable. However, it is important to remember that regardless of
-the technical resources which a team decides to use, the responsibility
-of the team co-ordinator remains the same.
+translation team (for whatever reason), but this is discouraged. It is
+required that every team has a mailing list at Savannah (*note Savannah
+Mailing Lists::), because it is easier to pass its management to the
+new co-ordinator when the old one steps down, and it helps to keep the
+archives at one place for future members of the team. Likewise, it is
+better to use Savannah for the team's repository and bugs/tasks, but
+this is not mandatory.
+
+ However, it is important to remember that regardless of the technical
+resources which a team decides to use, the responsibility of the team
+co-ordinator remains the same.
Those teams that are using Savannah have a broad variety of tools at
hand: team membership management, documents, trackers (bugs, tasks and
support), alerts, CVS (and any other VCS that Savannah supports), home
-pages, mailing lists, etc. How each team uses these resources is up to
-the team itself, but it often turns out to choose Savannah for nearly
-all of the team activities, as it requires almost zero work; the
-Savannah Hackers are happy to support us.
+pages, etc. How each team uses these resources is up to the team
+itself, but it often turns out to choose Savannah for nearly all of the
+team activities, as it requires almost zero work; the Savannah Hackers
+are happy to support us.
Whatever you (in your capacity as a team leader) decide, please do it
with caution: some organizational decisions may become ineffective as
@@ -884,15 +894,21 @@
3.2.3.8 Managing Mailing Lists
..............................
-You can create new mailing lists via the Savannah interface. However,
-this should be done after some thought. If the project membership is
-low (<= 10 members), there is no need to create more than one mailing
-list. If there is a general translation list common for all translators
-of the language (i.e. GNOME, GNUstep, KDE, and free software in
-general), there is no reason at all to create a list at Savannah.
+Every team should have a mailing list on lists.gnu.org and use it for
+internal communications. All active translators should be on the list.
+The list owner should be the co-ordinator of the team. The name of the
+list should begin with `www-LANG-'.
+
+ The list will make it possible for the GNU project to contact the
+team when the co-ordinator disappears; its archive will also give
+access to the history for new translators.
+
+ You can create new mailing lists via the Savannah interface.
+However, this should be done after some thought. If the project
+membership is low (<= 10 members), there is no need to create more than
+one mailing list.
- You can redirect all messages generated by the trackers to any list
-(including those that are not on GNU servers).
+ You can redirect all messages generated by the trackers to any list.
3.2.3.9 Version Control Systems
...............................
@@ -1055,11 +1071,11 @@
5.2 Summary of SSI `#include's
==============================
-The GNU Project's website uses SSI (Server Side Includes) to manage
-some common parts that are the same in many of the articles. With the
-help of GNUN their handling should be behind the scenes, but for some
-of them manual intervention is needed. Here is a (possibly incomplete)
-list of the `#include''s used:
+The GNU Project's website uses SSI (Server Side Includes) to manage some
+common parts that are the same in many of the articles. With the help
+of GNUN their handling should be behind the scenes, but for some of them
+manual intervention is needed. Here is a (possibly incomplete) list of
+the `#include''s used:
`server/banner.html'
This file contains only `#include' directives, so the
@@ -1101,6 +1117,21 @@
encoding declared in the `<meta>' element at
`server/head-include-1.LANG.html', so browsers will obey it.
+ The encoding should be UTF-8. This is required because the
+ English text in the articles serves as a replacement of the
+ translation when the latter is not complete, and because all
+ translated pages share automatically generated lists of
+ translations.
+
+`server/html5-header.html'
+ This file is included in newer pages using some entities introduced
+ in HTML5 draft. We have to distinguish those pages since some
+ features of HTML4 were rejected in HTML5, and our old pages don't
+ validate as HTML5.
+
+`server/html5-head-include-1.html'
+ Likewise, this file replaces head-include-1.html for HTML5 pages.
+
`server/head-include-2.html'
Imports the standard CSS, which can be overriden. *Note CSS::.
@@ -1110,6 +1141,16 @@
maintained manually, so just add LANG to the filename, in order
the localized `footer-text.LANG.html' to be included.
+`server/outdated.html'
+ This file is automatically included in outdated translations. It
+ contains respective message with links to the English file and to
+ a generated difference of the current revision of the English file
+ against the most recent revision that has a complete translation.
+ It is only included in articles affected by "grace period" because
+ in those cases the outdated passages are replaced with English
+ text, and it is evident without any notices that there is no
+ complete and up to date translation.
+
`translations.include'
The list of translations for the homepage (and only the homepage).
It is maintained manually; in order the link to a translation to
@@ -1149,16 +1190,36 @@
migrated and none of them includes such files, you should delete
them. You can use `grep' to check this.
- The files `header.html', `head-include-1.html',
-`head-include-2.html', `banner.html', `body-include-1.html',
-`body-include-2.html', `footer.html' and `footer-text.html' in the
-`server' sub-directory are what webmasters call "the server templates".
-These files are included in almost every article, translated or not.
-They are somewhat important, as an error made in translating them
-propagates everywhere. The server templates, the homepages, and
-whatsnew (a.k.a. "GNU News") are being rebuilt by GNUN whenever there
-is a change in the original English files; the `GRACE' variable has no
-effect for them. *Note Runtime Variables: (gnun)Runtime Variables.
+ The files
+
+ - `header.html'
+
+ - `head-include-1.html'
+
+ - `html5-header.html'
+
+ - `html5-head-include-1.html'
+
+ - `head-include-2.html'
+
+ - `banner.html'
+
+ - `body-include-1.html'
+
+ - `body-include-2.html'
+
+ - `footer.html'
+
+ - `footer-text.html'
+
+ in the `server' sub-directory are what webmasters call "the server
+templates". These files are included in almost every article,
+translated or not. They are somewhat important, as an error made in
+translating them propagates everywhere. The server templates, the
+homepages, and whatsnew (a.k.a. "GNU News") are being rebuilt by GNUN
+whenever there is a change in the original English files; the `GRACE'
+variable has no effect for them. *Note Runtime Variables:
+(gnun)Runtime Variables.
5.3 How To Use Custom CSS
=========================
@@ -1196,6 +1257,14 @@
When creating your own `style.LANG.css', don't forget to include the
license notice from the `style.css', with a short comment.
+ If using the default CSS style for translations does not give the
+expected good results, or there are other problems (significant or not)
+that obstruct reading and/or worsen the look from aesthetic point of
+view, please write to <address@hidden> with a description of the
+issue. If there are several unrelated problems, send separate messages
+with appropriate explanation (which may include a demonstration of the
+bug, such as a screenshot).
+
5.3.1 Localizing The `topbanner' Image
--------------------------------------
@@ -1247,11 +1316,10 @@
such situations, it is quite possible that the general
language-specific CSS does not help, and the translation of this
specific article does not look correct. Please write to
-<address@hidden>; if you have a working solution that
-works for both cases--so much the better. For general issues that
-affect your language and require a general solution, write to
-<address@hidden> or <address@hidden>, precisely describing the
-problem.
+<address@hidden>; if you have a working solution that works for
+both cases--so much the better. For general issues that affect your
+language and require a general solution, write to <address@hidden>
+as well, precisely describing the problem.
5.4 What To Translate
=====================
@@ -1259,11 +1327,27 @@
The article
`http://www.gnu.org/server/standards/translations/priorities.html'
lists the most important essays to translate. In general, articles in
-the directories `philosophy', `gnu', `copyleft' and `licenses' are
-important. The others may be deferred for a time when a team completes
-most of the important translations, or they can be translated as a
-"rest"-in translators' parlance this means doing something in between
-which is typically easier to handle.
+the directories `philosophy', `gnu', `distros', `copyleft' and
+`licenses' are important. The others may be deferred for a time when a
+team completes most of the important translations, or they can be
+translated as a "rest"-in translators' parlance this means doing
+something in between which is typically easier to handle.
+
+ It is very important to keep existing translations up-to-date with
+the respective English originals. This task should be higher priority
+than translating new articles. GNUN's `report' rule can help you to
+identify precisely which articles need updating; *note report:
+(gnun)report. There is a monthly cronjob which sends a verbose output
+to each team--by default, the address(es) used is the Savannah
+account(s) of the admin(s) of the specific translation project. If you
+want them changed, please write to <address@hidden>.
+
+ It is strongly recommended translation teams to attempt to recruit
+native English speakers in order to improve their translation process.
+Translators sometimes misunderstand English idioms and expressions, and
+as a result, they translate them incorrectly or in ways that are
+suboptimal and confusing. These errors are trivial to discover for the
+native English speaker.
_Do not_ translate articles under these directories:
@@ -1278,7 +1362,7 @@
and it's in a separate repository--thus not supported by the
automatic GNUN build job.
-`home.shtml'
+`home.html'
There is not problem to translate this page, but don't make the
mistake to pick it up as your first translation. It is modified
often, sometimes intensively, and only active team members should
@@ -1294,10 +1378,12 @@
5.5 When To CAPITALIZE
======================
-The English language has strict rules for capitalization of titles,
-chapters, acronym expansions and the like. They do not make sense for
-many other languages, but unfortunately, many translators _erroneously
-duplicate_ the capitalization in their translation.
+The English language has some rules for capitalization of titles,
+chapters, acronym expansions and the like. These rules are neither
+strict nor uniform, although the gnu.org website strives to apply them
+consistently. They do not make sense for many other languages, but
+unfortunately, many translators _erroneously duplicate_ the
+capitalization in their translation.
Examples for common (and correct) English capitalization is the
title of the article "Why Software Should Be Free" or "Free Software
@@ -1313,7 +1399,57 @@
`Franc,ais' or `Portugue^s'--write them as `franc,ais' or `portugue^s',
respectively.
-5.6 Language-specific Terminology
+5.6 Distribution Terms
+======================
+
+Most www.gnu.org articles are released under the terms of the Creative
+Commons Attribution-NoDerivs 3.0 United States license. The exact HTML
+for English pages to use is:
+
+ 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>.
+
+ Pages in other languages should translate this notice, and should
+link to a translated version of the Creative Commons license "deed" if
+it's available. Creative Commons provides standard text for this in
+all the languages they support, and we should use that wording whenever
+possible. To do that, follow these steps:
+
+ * Check at the bottom of the English deed page to see the list of
+ languages they support. Follow the link the language that you
+ want a translation for, if available.
+
+ * Follow the "Use this license for your own work" link near the
+ bottom of the translated deed page--it's in distinct yellow text.
+
+ * The textarea on that page provides standard HTML. Note that we're
+ not using the graphic, just the text.
+
+
+ For example, here's the text they provide for German:
+
+ Dieses Werk bzw. Inhalt steht unter einer <a rel="license"
+ href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.de";>Creative
+ Commons Namensnennung-Keine Bearbeitung 3.0 Vereinigte Staaten von
+ Amerika Lizenz</a>.
+
+ Note that the link in this text is changed to point directly to the
+German language deed. We should always link to a copy of the license
+deed that's in the same language as the page itself.
+
+ Pages in languages that aren't supported by CC should prepare their
+own translation, use it consistently throughout pages translated to that
+language, and link to the English language deed.
+
+ Note that translations should _not_ change the jurisdiction of the
+license; they should _always_ link to the CC BY-ND 3.0 _United States_
+license, and _not_ a different port like CC BY-ND 3.0 Japan. This is
+because there are substantive differences between the way different
+ports handle moral rights issues, and we prefer the specific terms that
+are in the United States license.
+
+5.7 Language-specific Terminology
=================================
This is a very important topic, not yet covered by this manual.
@@ -1370,20 +1506,26 @@
reason for that. It may become public in the future.
<address@hidden>
- This is a list for notifications about gnunews and GNUnited
- Nations releases. It is not mandatory to subscribe to it,
- although the traffic is very low. If you want to track only GNUN
- release announcements, subscribe to the `gnun' topic via Mailman's
- user interface. Likewise, if you want to recieve only "What's New"
- updates, subscribe to the `whatsnew' topic. In the near future,
- there will be automatic announcements for newly available English
- articles and translations.
+ This is a list for notifications about gnunews and GNUnited Nations
+ releases. It is not mandatory to subscribe to it, although the
+ traffic is very low. If you want to track only GNUN release
+ announcements, subscribe to the `gnun' topic via Mailman's user
+ interface. Likewise, if you want to recieve only "What's New"
+ updates, subscribe to the `whatsnew' topic.
+
+ Automatic announcements for new gnu.org translations (provided
+ they're handled by GNUN) are also delivered here. There are
+ separate `LANG-ann' topics for every GNUN-aware language, so it is
+ a good idea to advertise this capability widely among your local
+ community. For example, if a reader wants to be informed only
+ about new Spanish translations, she can just subscribe to the
+ `es-ann' mailing list topic.
This is a public mailing list.
<address@hidden>
- All development of GNUN happens here. Commits to the
- `trans-coord' repository are also sent to this list.
+ All development of GNUN happens here. Commits to the `trans-coord'
+ repository are also sent to this list.
This is a public list, and <address@hidden> is an alias.
Index: web-trans.txt.gz
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/web-trans.txt.gz,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
Binary files /tmp/cvsaT45Aq and /tmp/cvsRkOirN differ
Index: html_node/CSS.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/CSS.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/CSS.html 11 Nov 2009 14:50:43 -0000 1.4
+++ html_node/CSS.html 30 Jan 2012 16:11:51 -0000 1.5
@@ -11,11 +11,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -84,6 +84,14 @@
include the license notice from the <samp><span
class="file">style.css</span></samp>, with a short
comment.
+ <p>If using the default CSS style for translations does not give the
+expected good results, or there are other problems (significant or not)
+that obstruct reading and/or worsen the look from aesthetic point of
+view, please write to <a href="mailto:address@hidden";>address@hidden</a> with
a description of
+the issue. If there are several unrelated problems, send separate
+messages with appropriate explanation (which may include a demonstration
+of the bug, such as a screenshot).
+
<ul class="menu">
<li><a accesskey="1" href="topbanner.html#topbanner">topbanner</a>:
How to localize the topbanner image.
<li><a accesskey="2" href="RTL.html#RTL">RTL</a>: Special
notes about RTL languages.
Index: html_node/Capitalization.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Capitalization.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Capitalization.html 11 Nov 2009 14:50:43 -0000 1.4
+++ html_node/Capitalization.html 30 Jan 2012 16:11:51 -0000 1.5
@@ -7,15 +7,15 @@
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Translation-Tips.html#Translation-Tips"
title="Translation Tips">
<link rel="prev" href="Priorities.html#Priorities" title="Priorities">
-<link rel="next" href="Terminology.html#Terminology" title="Terminology">
+<link rel="next" href="Distribution-Terms.html#Distribution-Terms"
title="Distribution Terms">
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -41,7 +41,7 @@
<div class="node">
<a name="Capitalization"></a>
<p>
-Next: <a rel="next" accesskey="n"
href="Terminology.html#Terminology">Terminology</a>,
+Next: <a rel="next" accesskey="n"
href="Distribution-Terms.html#Distribution-Terms">Distribution Terms</a>,
Previous: <a rel="previous" accesskey="p"
href="Priorities.html#Priorities">Priorities</a>,
Up: <a rel="up" accesskey="u"
href="Translation-Tips.html#Translation-Tips">Translation Tips</a>
<hr>
@@ -49,10 +49,12 @@
<h3 class="section">5.5 When To CAPITALIZE</h3>
-<p>The English language has strict rules for capitalization of titles,
-chapters, acronym expansions and the like. They do not make sense for
-many other languages, but unfortunately, many translators
-<em>erroneously duplicate</em> the capitalization in their translation.
+<p>The English language has some rules for capitalization of titles,
+chapters, acronym expansions and the like. These rules are neither
+strict nor uniform, although the gnu.org website strives to apply them
+consistently. They do not make sense for many other languages, but
+unfortunately, many translators <em>erroneously duplicate</em> the
+capitalization in their translation.
<p>Examples for common (and correct) English capitalization is the title of
the article “Why Software Should Be Free” or “Free Software
Index: html_node/Co_002dleaders.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Co_002dleaders.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Co_002dleaders.html 11 Nov 2009 14:50:43 -0000 1.4
+++ html_node/Co_002dleaders.html 30 Jan 2012 16:11:51 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Commits.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/Commits.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Commits.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Commits.html 30 Jan 2012 16:11:51 -0000 1.5
@@ -11,11 +11,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -60,8 +60,8 @@
<p>If you wish to volunteer as webmaster and help with generic webmaster
work and RT tickets, that is perfectly fine—please follow the
-established (by the <acronym>GNU</acronym> Webmasters) procedure. If you are
-approved, you can modify such pages wearing your “webmaster's hat”.
+established (by the GNU Webmasters) procedure. If you are approved, you
+can modify such pages wearing your “webmaster's hat”.
<p>If a particular page has issues with the markup which create problems
for your language, please inform <a
href="mailto:address@hidden";>address@hidden</a>.
Index: html_node/Copying-This-Manual.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Copying-This-Manual.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Copying-This-Manual.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Copying-This-Manual.html 30 Jan 2012 16:11:52 -0000 1.5
@@ -9,11 +9,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Introduction.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Introduction.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Introduction.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Introduction.html 30 Jan 2012 16:11:52 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -51,10 +51,10 @@
<p>This manual is an attempt to describe in detail the process of
translating www.gnu.org articles—how to join a team, or start a new
one, the responsibilities of the team members and leaders, as well as
-some peculiarities of the <acronym>GNU</acronym> Project's website when it
comes
-to localization.
+some peculiarities of the GNU Project's website when it comes to
+localization.
- <p>The <acronym>GNU</acronym> website contains hundreds of documents, most
of them
+ <p>The GNU website contains hundreds of documents, most of them
philosophical articles (essays) and technical documents which need to be
translated to make them available to a broader audience. This is
especially important for the philosophy-related materials, as many
@@ -62,19 +62,20 @@
read such articles in their native language. Dealing with the task of
translating a website this large is a hard job, and too often people
volunteering as translators get frustrated or lose interest in keeping
-up with that work. Reading this manual, and the related
<acronym>GNUN</acronym>
-manual (see <a href="../gnun/index.html#Top">GNUnited Nations</a>), is just
the tip of the iceberg. This is not meant to
-discourage any potential volunteer; rather, we prefer to be honest and
-to give preliminary estimation of the work/responsibility involved—if
-you feel you are not in a position to help you may move on to a smaller
-project before going through all procedures.
-
- <p>It is important to realize that being a <acronym>GNU</acronym> Web
Translator is
-a hard job at all levels, but your help is much appreciated and is
-invaluable contribution to the society. While there are many people who
-contribute to our community by writing free software (and their number
-is constantly increasing), the ones actively engaged in teaching others
-to appreciate and defend their freedom are only a few. Consequently and
+up with that work. Reading this manual, and the related GNUN manual
+(see <a href="../gnun/index.html#Top">GNUnited Nations</a>), is
+just the tip of the iceberg. This is not meant to discourage any
+potential volunteer; rather, we prefer to be honest and to give
+preliminary estimation of the work/responsibility involved—if you feel
+you are not in a position to help you may move on to a smaller project
+before going through all procedures.
+
+ <p>It is important to realize that being a GNU Web Translator is a hard job
+at all levels, but your help is much appreciated and is invaluable
+contribution to the society. While there are many people who contribute
+to our community by writing free software (and their number is
+constantly increasing), the ones actively engaged in teaching others to
+appreciate and defend their freedom are only a few. Consequently and
rather unfortunately, there are not so many volunteers willing to
maintain on the long term translations of the various essays that
describe the fundamental values of the free software movement.
@@ -83,16 +84,16 @@
language teams. Each team has one or more co-ordinators, who are
responsible for the respective team. The co-ordinators participate in
the Savannah ‘<samp><span class="samp">trans-coord</span></samp>’
organizational project, which is managed
-by the <acronym>GNU</acronym> Web Translation Managers. The manual is
organized
-in chapters that follow the organizational structure of the whole
+by the GNU Web Translation Managers. The manual is organized in
+chapters that follow the organizational structure of the whole
translation project.
<p>If you wish to join a translation team or contribute a translation or
-two, see <a href="Members.html#Members">Members</a>. If your intention is to
form a translation
-team, see <a href="Leaders.html#Leaders">Leaders</a>. The chapter about the
‘<samp><span class="samp">trans-coord</span></samp>’
-administrators (a.k.a. <dfn><acronym>GNU</acronym> Translation Managers</dfn>)
-describes all the responsibilities and procedures involved in performing
-this duty. See <a
href="Translation-Managers.html#Translation-Managers">Translation Managers</a>.
+two, see <a href="Members.html#Members">Members</a>. If your intention is to
form a translation team,
+see <a href="Leaders.html#Leaders">Leaders</a>. The chapter about the
‘<samp><span class="samp">trans-coord</span></samp>’
+administrators (a.k.a. <dfn>GNU Translation Managers</dfn>) describes all the
+responsibilities and procedures involved in performing this duty.
+See <a href="Translation-Managers.html#Translation-Managers">Translation
Managers</a>.
</body></html>
Index: html_node/Joining.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/Joining.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Joining.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Joining.html 30 Jan 2012 16:11:52 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -70,11 +70,11 @@
next chapter, see <a href="Leaders.html#Leaders">Leaders</a>.
<p>Contacting the team is best done via Savannah—each translation team
-has its own project, named ‘<samp><span
class="samp">www-</span><var>lang</var></samp>’, with the project page
-being
+has its own project, named ‘<samp><span
class="samp">www-</span><var>lang</var></samp>’, with the project
+page being
<<code>https://savannah.gnu.org/projects/www-</code><var>lang</var>>.
-Usually teams have mailing lists, either on Savannah or on some external
-site. Some teams have homepages,
+Usually teams have mailing lists, typically in the form
+<a href="mailto:www-<var>lang</var>address@hidden">www-<var>lang</var>-<small
class="dots">...</small>@gnu.org</a>. Some teams have homepages,
<<code>http://gnu.org/server/standards/translations/</code><var>lang</var>>
with additional contact details and procedures for team members.
Index: html_node/Leaders.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/Leaders.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Leaders.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Leaders.html 30 Jan 2012 16:11:52 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Leaving-A-Team.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Leaving-A-Team.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Leaving-A-Team.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Leaving-A-Team.html 30 Jan 2012 16:11:52 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Mailing-Lists.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Mailing-Lists.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Mailing-Lists.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Mailing-Lists.html 30 Jan 2012 16:11:52 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -52,8 +52,8 @@
participants in the process.
<dl>
-<dt><a href="mailto:address@hidden";>address@hidden</a><dd>The basic discussion
list of the <acronym>GNU</acronym> Webmasters. All team
-leaders are required to subscribe.
+<dt><a href="mailto:address@hidden";>address@hidden</a><dd>The basic discussion
list of the GNU Webmasters. All team leaders are
+required to subscribe.
<p>This is a private mailing list.
@@ -65,37 +65,42 @@
<p>This is a public mailing list, so everyone can subscribe and review the
archives. The ‘<samp><span class="samp">www</span></samp>’ CVS
repository is also public.
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>The main
discussion list for the <acronym>GNU</acronym> Web Translators. Team
-leaders must subscribe, as errors from <acronym>GNUN</acronym> are mailed
here.
-Team members are welcome to join as well, provided they are already
-members of ‘<samp><span
class="samp">www-</span><var>lang</var></samp>’. If they want to
subscribe with a
-different email address, a verification from the team leader is
-required.
+ <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>The main
discussion list for the GNU Web Translators. Team leaders must
+subscribe, as errors from GNUN are mailed here. Team members are
+welcome to join as well, provided they are already members of
+‘<samp><span class="samp">www-</span><var>lang</var></samp>’. If
they want to subscribe with a different email
+address, a verification from the team leader is required.
<p>This is a private mailing list, although there is no absolute reason
for
that. It may become public in the future.
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>This is a
list for notifications about gnunews and <acronym>GNU</acronym>nited
-Nations releases. It is not mandatory to subscribe to it, although the
-traffic is very low. If you want to track only <acronym>GNUN</acronym> release
-announcements, subscribe to the ‘<samp><span
class="samp">gnun</span></samp>’ topic via Mailman's user
-interface. Likewise, if you want to recieve only <dfn>What's New</dfn>
-updates, subscribe to the ‘<samp><span
class="samp">whatsnew</span></samp>’ topic. In the near future,
-there will be automatic announcements for newly available English
-articles and translations.
+ <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>This is a
list for notifications about gnunews and GNUnited Nations
+releases. It is not mandatory to subscribe to it, although the traffic
+is very low. If you want to track only GNUN release announcements,
+subscribe to the ‘<samp><span class="samp">gnun</span></samp>’
topic via Mailman's user interface.
+Likewise, if you want to recieve only <dfn>What's New</dfn> updates,
+subscribe to the ‘<samp><span class="samp">whatsnew</span></samp>’
topic.
+
+ <p>Automatic announcements for new gnu.org translations (provided they're
+handled by GNUN) are also delivered here. There are separate
+‘<samp><var>lang</var><span class="samp">-ann</span></samp>’
topics for every GNUN-aware language, so it is a
+good idea to advertise this capability widely among your local
+community. For example, if a reader wants to be informed only about new
+Spanish translations, she can just subscribe to the ‘<samp><span
class="samp">es-ann</span></samp>’
+mailing list topic.
<p>This is a public mailing list.
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>All
development of <acronym>GNUN</acronym> happens here. Commits to the
-‘<samp><span class="samp">trans-coord</span></samp>’ repository
are also sent to this list.
+ <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>All
development of GNUN happens here. Commits to the ‘<samp><span
class="samp">trans-coord</span></samp>’
+repository are also sent to this list.
<p>This is a public list, and <a
href="mailto:address@hidden";>address@hidden</a> is an alias.
- <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>All build
logs from the various <acronym>GNUN</acronym> automatic builds are sent
-to this list, so it is not a very pleasant thing to be subscribed,
-especially if you are not interested in <acronym>GNUN</acronym>'s internals.
-However, everyone can use the web archives to check the log why a
-particular article was not built at expected.
+ <br><dt><a href="mailto:address@hidden";>address@hidden</a><dd>All build
logs from the various GNUN automatic builds are sent to this
+list, so it is not a very pleasant thing to be subscribed, especially if
+you are not interested in GNUN's internals. However, everyone can use
+the web archives to check the log why a particular article was not built
+at expected.
<p>This is a public list.
</dl>
Index: html_node/Managing.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Managing.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Managing.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Managing.html 30 Jan 2012 16:11:52 -0000 1.5
@@ -11,11 +11,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Members.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/Members.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Members.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Members.html 30 Jan 2012 16:11:52 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Migrating.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Migrating.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Migrating.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Migrating.html 30 Jan 2012 16:11:52 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -48,10 +48,11 @@
<h3 class="section">5.1 Migration To The New Style</h3>
<p>Migration to the new style should be straightforward, and this is one of
-the problems <acronym>GNUN</acronym> set out to solve. If you have to migrate
-old-style translations, see <a
href="../gnun/Migrating.html#Migrating">Migrating</a>. If the old translation
is HTML 2.0 (or 3.2), you still have to
-take care about the inner markup. Overall, it is substantially easier
-than doing all of it manually.
+the problems GNUN set out to solve. If you have to migrate old-style
+translations, see <a href="../gnun/Migrating.html#Migrating">Migrating</a>.
+If the old translation is HTML 2.0 (or 3.2), you still have to take care
+about the inner markup. Overall, it is substantially easier than doing
+all of it manually.
<p>Subsequent migrations to newer (X)HTML standards and newer look and feel
of the website are supposed to happen semi-automatically, although this
Index: html_node/New-Team.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/New-Team.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/New-Team.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/New-Team.html 30 Jan 2012 16:11:52 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -78,7 +78,7 @@
<p>Examine the layout and structure of the repository. Basically, it is
mapped to the URL locations, more or less. Take a look at the most
important materials to translate under <samp><span
class="file">/philosophy</span></samp>, <samp><span
class="file">/gnu</span></samp>,
-<samp><span class="file">/ditros</span></samp>, <samp><span
class="file">/copyleft</span></samp> and <samp><span
class="file">/licenses</span></samp> directories just
+<samp><span class="file">/distros</span></samp>, <samp><span
class="file">/copyleft</span></samp> and <samp><span
class="file">/licenses</span></samp> directories just
to get a rough estimate about the amount of work involved. If you are
still not scared and determined to go on further, excellent.
@@ -86,9 +86,9 @@
translatable articles has a <samp><span class="file">/po</span></samp>
sub-directory, which is where the
new canonical source format of the translations is stored.
- <li>Assuming you have already read the <acronym>GNUN</acronym> manual
entirely (as
-recommended in the beginning of this section), check if your language
-code is present in the variable <code>TEMPLATE_LINGUAS</code> at
+ <li>Assuming you have already read the GNUN manual entirely (as
recommended
+in the beginning of this section), check if your language code is
+present in the variable <code>TEMPLATE_LINGUAS</code> at
<samp><span class="file">server/gnun/gnun.mk</span></samp>. If it is not, the
first thing to do is to
translate and submit to <a href="mailto:address@hidden";>address@hidden</a> the
following
files (all in the <samp><span class="file">server/po/</span></samp> directory):
@@ -179,8 +179,8 @@
</ul>
<p>You'll have to request subscription to ‘<samp><span
class="samp">www-discuss</span></samp>’
-yourself—this list is managed by the <acronym>GNU</acronym> Webmasters,
but all
-team leaders are required to subscribe in order to receive important
+yourself—this list is managed by the GNU Webmasters, but all team
+leaders are required to subscribe in order to receive important
site-wide announcements.
</ol>
Index: html_node/Priorities.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Priorities.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Priorities.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Priorities.html 30 Jan 2012 16:11:52 -0000 1.5
@@ -11,11 +11,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -52,25 +52,42 @@
<p>The article
<a
href="http://www.gnu.org/server/standards/translations/priorities.html";>http://www.gnu.org/server/standards/translations/priorities.html</a>
lists the most important essays to translate. In general, articles in
-the directories <samp><span class="file">philosophy</span></samp>, <samp><span
class="file">gnu</span></samp>, <samp><span class="file">copyleft</span></samp>
and
-<samp><span class="file">licenses</span></samp> are important. The others may
be deferred for a time
-when a team completes most of the important translations, or they can be
-translated as a “rest”–in translators' parlance this means
doing
-something in between which is typically easier to handle.
+the directories <samp><span class="file">philosophy</span></samp>, <samp><span
class="file">gnu</span></samp>, <samp><span class="file">distros</span></samp>,
+<samp><span class="file">copyleft</span></samp> and <samp><span
class="file">licenses</span></samp> are important. The others may be
+deferred for a time when a team completes most of the important
+translations, or they can be translated as a “rest”–in
translators'
+parlance this means doing something in between which is typically easier
+to handle.
+
+ <p>It is very important to keep existing translations up-to-date with the
+respective English originals. This task should be higher priority than
+translating new articles. GNUN's <code>report</code> rule can help you to
+identify precisely which articles need updating; see <a
href="../gnun/report.html#report">report</a>. There is a monthly cronjob which
+sends a verbose output to each team—by default, the address(es) used
+is the Savannah account(s) of the admin(s) of the specific translation
+project. If you want them changed, please write to
+<a href="mailto:address@hidden";>address@hidden</a>.
+
+ <p>It is strongly recommended translation teams to attempt to recruit
+native English speakers in order to improve their translation process.
+Translators sometimes misunderstand English idioms and expressions, and
+as a result, they translate them incorrectly or in ways that are
+suboptimal and confusing. These errors are trivial to discover for the
+native English speaker.
<p><em>Do not</em> translate articles under these directories:
<dl>
<dt><samp><span class="file">software/</span><var>pkg</var><span
class="file">/</span></samp><dd>These pages are maintained by the respective
<var>pkg</var> maintainers.
-<acronym>GNUN</acronym> does not support them for the time being, as they
reside
-in separate repositories. The procedures for contributing translations
-of such articles are not yet settled.
+GNUN does not support them for the time being, as they reside in
+separate repositories. The procedures for contributing translations of
+such articles are not yet settled.
<br><dt><samp><span class="file">brave-gnu-world</span></samp><dd>The
Brave GNU World initiative has been abandoned long time ago, and
-it's in a separate repository—thus not supported by the automatic
-<acronym>GNUN</acronym> build job.
+it's in a separate repository—thus not supported by the automatic GNUN
+build job.
- <br><dt><samp><span class="file">home.shtml</span></samp><dd>There is not
problem to translate this page, but don't make the mistake
+ <br><dt><samp><span class="file">home.html</span></samp><dd>There is not
problem to translate this page, but don't make the mistake
to pick it up as your first translation. It is modified often,
sometimes intensively, and only active team members should take that
road.
Index: html_node/RTL.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/RTL.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/RTL.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/RTL.html 30 Jan 2012 16:11:52 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -65,11 +65,10 @@
style="..."></code>. In such situations, it is quite possible that the
general language-specific CSS does not help, and the translation of this
specific article does not look correct. Please write to
-<a href="mailto:address@hidden";>address@hidden</a>; if you have a working
solution
-that works for both cases—so much the better. For general issues that
-affect your language and require a general solution, write to
-<a href="mailto:address@hidden";>address@hidden</a> or <a
href="mailto:address@hidden";>address@hidden</a>, precisely
-describing the problem.
+<a href="mailto:address@hidden";>address@hidden</a>; if you have a working
solution that works
+for both cases—so much the better. For general issues that affect
+your language and require a general solution, write to
+<a href="mailto:address@hidden";>address@hidden</a> as well, precisely
describing the problem.
</body></html>
Index: html_node/Reports.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/Reports.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Reports.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Reports.html 30 Jan 2012 16:11:52 -0000 1.5
@@ -11,11 +11,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Review.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/Review.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Review.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Review.html 30 Jan 2012 16:11:52 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/SSI.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/SSI.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/SSI.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/SSI.html 30 Jan 2012 16:11:53 -0000 1.5
@@ -11,11 +11,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -49,11 +49,11 @@
<h3 class="section">5.2 Summary of SSI <code>#include</code>s</h3>
-<p>The GNU Project's website uses <acronym>SSI</acronym> (Server Side
Includes) to
-manage some common parts that are the same in many of the articles.
-With the help of <acronym>GNUN</acronym> their handling should be behind the
-scenes, but for some of them manual intervention is needed. Here is a
-(possibly incomplete) list of the <code>#include</code>'s used:
+<p>The GNU Project's website uses SSI (Server Side Includes) to manage some
+common parts that are the same in many of the articles. With the help
+of GNUN their handling should be behind the scenes, but for some of them
+manual intervention is needed. Here is a (possibly incomplete) list of
+the <code>#include</code>'s used:
<dl>
<dt><samp><span class="file">server/banner.html</span></samp><dd>This file
contains only <code>#include</code> directives, so the
@@ -71,13 +71,13 @@
file.
<br><dt><samp><span
class="file">server/footer-text.html</span></samp><dd>This is a very short file
currently containing the “back to top” link.
-Also translatable via <acronym>GNUN</acronym>.
+Also translatable via GNUN.
<br><dt><samp><span class="file">server/header.html</span></samp><dd>The
declaration that is included in literally every file. It is
maintained manually, as it does not make much sense to put it under
-<acronym>GNUN</acronym>'s control (there are no translatable strings).
Remember
-to specify the proper <code>xml:lang</code> and <code>lang</code> attributes,
and
-for RTL languages, the <code>dir</code> attribute. For example, the file
+GNUN's control (there are no translatable strings). Remember to specify
+the proper <code>xml:lang</code> and <code>lang</code> attributes, and for RTL
+languages, the <code>dir</code> attribute. For example, the file
<samp><span class="file">header.ar.html</span></samp> should contain this line:
<pre class="example"> <html
xmlns="http://www.w3.org/1999/xhtml"; xml:lang="ar" lang="ar"
@@ -91,6 +91,18 @@
declared in the <code><meta></code> element at
<samp><span class="file">server/head-include-1.</span><var>lang</var><span
class="file">.html</span></samp>, so browsers will obey it.
+ <p>The encoding should be UTF-8. This is required because the English
text
+in the articles serves as a replacement of the translation when the latter
+is not complete, and because all translated pages share automatically
+generated lists of translations.
+
+ <br><dt><samp><span
class="file">server/html5-header.html</span></samp><dd>This file is included in
newer pages using some entities introduced
+in HTML5 draft. We have to distinguish those pages since some features
+of HTML4 were rejected in HTML5, and our old pages don't validate
+as HTML5.
+
+ <br><dt><samp><span
class="file">server/html5-head-include-1.html</span></samp><dd>Likewise, this
file replaces head-include-1.html for HTML5 pages.
+
<br><dt><samp><span
class="file">server/head-include-2.html</span></samp><dd>Imports the standard
CSS, which can be overriden. See <a href="CSS.html#CSS">CSS</a>.
<br><dt><samp><span class="file">server/footer.html</span></samp><dd>This
is a very short and simple file (at least at the time of writing),
@@ -98,6 +110,15 @@
manually, so just add <var>lang</var> to the filename, in order the localized
<samp><span class="file">footer-text.</span><var>lang</var><span
class="file">.html</span></samp> to be included.
+ <br><dt><samp><span
class="file">server/outdated.html</span></samp><dd>This file is automatically
included in outdated translations. It
+contains respective message with links to the English file and
+to a generated difference of the current revision of the English
+file against the most recent revision that has a complete translation.
+It is only included in articles affected by “grace period” because
+in those cases the outdated passages are replaced with English text,
+and it is evident without any notices that there is no complete
+and up to date translation.
+
<br><dt><samp><span
class="file">translations.include</span></samp><dd>The list of translations for
the homepage (and only the homepage). It
is maintained manually; in order the link to a translation to appear on
all of the homepages, it has to be present here.
@@ -118,8 +139,8 @@
HTML version of the license without the gnu.org style; 2) to prevent
strings sneaking in the <samp><span class="file">.pot</span></samp> files, as
licenses have only
unofficial translations, hosted elsewhere. Nothing special should be
-done about these SSI directives; the files generated by <acronym>GNUN</acronym>
-include them verbatim as they should not be translated.
+done about these SSI directives; the files generated by GNUN include
+them verbatim as they should not be translated.
<br><dt><samp><span
class="file">server/sidebar*.html</span></samp><dd>These files are
deprecated—they are remnants from an older design that
lived shortly in the middle between the old classic design and the
@@ -128,17 +149,29 @@
<samp><span class="command">grep</span></samp> to check this.
</dl>
- <p>The files <samp><span class="file">header.html</span></samp>,
<samp><span class="file">head-include-1.html</span></samp>,
-<samp><span class="file">head-include-2.html</span></samp>, <samp><span
class="file">banner.html</span></samp>,
-<samp><span class="file">body-include-1.html</span></samp>, <samp><span
class="file">body-include-2.html</span></samp>,
-<samp><span class="file">footer.html</span></samp> and <samp><span
class="file">footer-text.html</span></samp> in the <samp><span
class="file">server</span></samp>
-sub-directory are what webmasters call “the server templates”.
These
-files are included in almost every article, translated or not. They are
-somewhat important, as an error made in translating them propagates
-everywhere. The server templates, the homepages, and whatsnew
-(a.k.a. “GNU News”) are being rebuilt by <acronym>GNUN</acronym>
whenever there
-is a change in the original English files; the <code>GRACE</code> variable has
-no effect for them. See <a
href="../gnun/Runtime-Variables.html#Runtime-Variables">Runtime Variables</a>.
+ <p>The files
+
+<!-- Use @itemize to avoid `underfull \hbox' warnings from TeX. -->
+ <ul>
+<li><samp><span class="file">header.html</span></samp>
+<li><samp><span class="file">head-include-1.html</span></samp>
+<li><samp><span class="file">html5-header.html</span></samp>
+<li><samp><span class="file">html5-head-include-1.html</span></samp>
+<li><samp><span class="file">head-include-2.html</span></samp>
+<li><samp><span class="file">banner.html</span></samp>
+<li><samp><span class="file">body-include-1.html</span></samp>
+<li><samp><span class="file">body-include-2.html</span></samp>
+<li><samp><span class="file">footer.html</span></samp>
+<li><samp><span class="file">footer-text.html</span></samp>
+</ul>
+
+ <p>in the <samp><span class="file">server</span></samp> sub-directory are
what webmasters call “the
+server templates”. These files are included in almost every article,
+translated or not. They are somewhat important, as an error made in
+translating them propagates everywhere. The server templates, the
+homepages, and whatsnew (a.k.a. “GNU News”) are being rebuilt by
+GNUN whenever there is a change in the original English files; the
+<code>GRACE</code> variable has no effect for them. See <a
href="../gnun/Runtime-Variables.html#Runtime-Variables">Runtime Variables</a>.
</body></html>
Index: html_node/Savannah-Bugs.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-Bugs.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Savannah-Bugs.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Savannah-Bugs.html 30 Jan 2012 16:11:53 -0000 1.5
@@ -11,11 +11,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Savannah-Homepage.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-Homepage.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Savannah-Homepage.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Savannah-Homepage.html 30 Jan 2012 16:11:53 -0000 1.5
@@ -11,11 +11,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Savannah-Mailing-Lists.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-Mailing-Lists.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Savannah-Mailing-Lists.html 11 Nov 2009 14:50:44 -0000
1.4
+++ html_node/Savannah-Mailing-Lists.html 30 Jan 2012 16:11:53 -0000
1.5
@@ -11,11 +11,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -49,15 +49,21 @@
<h5 class="subsubsection">3.2.3.8 Managing Mailing Lists</h5>
-<p>You can create new mailing lists via the Savannah interface. However,
+<p>Every team should have a mailing list on lists.gnu.org and use it for
+internal communications. All active translators should be on the
+list. The list owner should be the co-ordinator of the team. The
+name of the list should begin with ‘<samp><span
class="samp">www-</span><var>lang</var><span
class="samp">-</span></samp>’.
+
+ <p>The list will make it possible for the GNU project to contact the team
+when the co-ordinator disappears; its archive will also give access to
+the history for new translators.
+
+ <p>You can create new mailing lists via the Savannah interface. However,
this should be done after some thought. If the project membership is
low (<= 10 members), there is no need to create more than one mailing
-list. If there is a general translation list common for all translators
-of the language (i.e. GNOME, GNUstep, KDE, and free software in
-general), there is no reason at all to create a list at Savannah.
+list.
- <p>You can redirect all messages generated by the trackers to any list
-(including those that are not on GNU servers).
+ <p>You can redirect all messages generated by the trackers to any list.
</body></html>
Index: html_node/Savannah-Members.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-Members.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Savannah-Members.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Savannah-Members.html 30 Jan 2012 16:11:53 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Savannah-News.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-News.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Savannah-News.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Savannah-News.html 30 Jan 2012 16:11:53 -0000 1.5
@@ -11,11 +11,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Savannah-Patch.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-Patch.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Savannah-Patch.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Savannah-Patch.html 30 Jan 2012 16:11:53 -0000 1.5
@@ -11,11 +11,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Savannah-Projects.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-Projects.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Savannah-Projects.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Savannah-Projects.html 30 Jan 2012 16:11:53 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -66,8 +66,7 @@
to be members, as bugs reported to <a
href="mailto:address@hidden";>address@hidden</a> are
often redirected to the ‘<samp><span
class="samp">trans-coord</span></samp>’ ‘<samp><span
class="samp">Bugs</span></samp>’ tracker.
- <p>The admins of this project are the <acronym>GNU</acronym> Web
Translation
-Managers.
+ <p>The admins of this project are the GNU Web Translation Managers.
<br><dt>‘<samp><span
class="samp">www-</span><var>lang</var></samp>’<dd>All translation team
leaders of the language <var>lang</var> should be
members of the project ‘<samp><span
class="samp">www-</span><var>lang</var></samp>’. The admins of the
project
Index: html_node/Savannah-Support.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-Support.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Savannah-Support.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Savannah-Support.html 30 Jan 2012 16:11:53 -0000 1.5
@@ -11,11 +11,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Savannah-Tasks.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-Tasks.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Savannah-Tasks.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Savannah-Tasks.html 30 Jan 2012 16:11:53 -0000 1.5
@@ -11,11 +11,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Savannah-VCS.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah-VCS.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Savannah-VCS.html 11 Nov 2009 14:50:44 -0000 1.4
+++ html_node/Savannah-VCS.html 30 Jan 2012 16:11:53 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Savannah.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Savannah.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Savannah.html 11 Nov 2009 14:50:45 -0000 1.4
+++ html_node/Savannah.html 30 Jan 2012 16:11:53 -0000 1.5
@@ -11,11 +11,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -55,24 +55,29 @@
Savannah project for each language is obvious: it's a standard way to
find information for translation teams and their contacts.
- <p>Using external hosting facilities is sometimes justified—for
example,
-some languages have a single mailing list for all free software-related
-translations, where all translators co-operate. Others have already
-established repositories and/or bug tracking systems where usual
-contributors already have access. Some team members prefer to work
-within the established infrastructure of a broad translation team (for
-whatever reason), and this is entirely acceptable. However, it is
-important to remember that regardless of the technical resources which a
-team decides to use, the responsibility of the team co-ordinator remains
-the same.
+ <p>Using external hosting facilities may seem justified sometimes. Some
+teams may have already established repositories and/or bug tracking
+systems where usual contributors already have access. Some team
+members prefer to work within the established infrastructure of a
+broad translation team (for whatever reason), but this is discouraged.
+It is required that every team has a mailing list at Savannah
+(see <a href="Savannah-Mailing-Lists.html#Savannah-Mailing-Lists">Savannah
Mailing Lists</a>), because it is easier to pass its
+management to the new co-ordinator when the old one steps down, and it
+helps to keep the archives at one place for future members of the
+team. Likewise, it is better to use Savannah for the team's
+repository and bugs/tasks, but this is not mandatory.
+
+ <p>However, it is important to remember that regardless of the technical
+resources which a team decides to use, the responsibility of the team
+co-ordinator remains the same.
<p>Those teams that are using Savannah have a broad variety of tools at
hand: team membership management, documents, trackers (bugs, tasks and
support), alerts, CVS (and any other VCS that Savannah supports), home
-pages, mailing lists, etc. How each team uses these resources is up to
-the team itself, but it often turns out to choose Savannah for nearly
-all of the team activities, as it requires almost zero work; the
-Savannah Hackers are happy to support us.
+pages, etc. How each team uses these resources is up to the team
+itself, but it often turns out to choose Savannah for nearly all of
+the team activities, as it requires almost zero work; the Savannah
+Hackers are happy to support us.
<p>Whatever you (in your capacity as a team leader) decide, please do it
with caution: some organizational decisions may become ineffective as
Index: html_node/Stepping-Down.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Stepping-Down.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Stepping-Down.html 11 Nov 2009 14:50:45 -0000 1.4
+++ html_node/Stepping-Down.html 30 Jan 2012 16:11:53 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Submitting-as-PO.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Submitting-as-PO.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Submitting-as-PO.html 11 Nov 2009 14:50:45 -0000 1.4
+++ html_node/Submitting-as-PO.html 30 Jan 2012 16:11:53 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -47,7 +47,7 @@
<h4 class="subsection">2.2.1 How To Submit a Translation in PO Format</h4>
-<p>All translations<a rel="footnote" href="#fn-1"
name="fnd-1"><sup>1</sup></a> are maintained via <acronym>GNUN</acronym> (see
+<p>All translations<a rel="footnote" href="#fn-1"
name="fnd-1"><sup>1</sup></a> are maintained via GNUN (see
<a
href="http://www.gnu.org/software/gnun/";>http://www.gnu.org/software/gnun/</a>),
which significantly eases
maintenance and avoids the unpleasant situation where a translation is
lagging behind the original. See <a
href="../gnun/Advantages.html#Advantages">Advantages</a>.
@@ -81,8 +81,8 @@
your message. The web-translators will review (to the best of their
ability) the translation and will install it in the repository.
- <li>In order <acronym>GNUN</acronym> to be able to generate (and
subsequently update)
-a gettextized translation, the language should have the server templates
+ <li>In order GNUN to be able to generate (and subsequently update) a
+gettextized translation, the language should have the server templates
available as PO files. These templates are short, and translating them
shouldn't take much time. If the language code is present in the
<code>TEMPLATE_LINGUAS</code> variable at <samp><span
class="file">server/gnun/gnun.mk</span></samp>, then you
@@ -94,6 +94,9 @@
submit them in the usual way, together with the translation of the
essay.
+ <p>Additional templates are defined via the <var>extra-templates</var>
variable
+in <samp><span class="file">server/gnun/gnun.mk</span></samp>.
+
<p>If you don't want to translate the templates for whatever
reason—do
not worry, the web-translators will install empty templates (which means
the English strings will be used).
Index: html_node/Submitting-as-Plain-Text.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Submitting-as-Plain-Text.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Submitting-as-Plain-Text.html 11 Nov 2009 14:50:45 -0000
1.4
+++ html_node/Submitting-as-Plain-Text.html 30 Jan 2012 16:11:53 -0000
1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -50,9 +50,9 @@
<p>If you feel the procedure described in the previous section is too
burdensome and unfeasible for you to follow, you can still submit a
translation in plain text. It will be manually converted to PO file by
-the <acronym>GNU</acronym> Web Translation Managers, which can be tricky
-sometimes, and naturally, means more work for them and slower processing
-of your request.
+the GNU Web Translation Managers, which can be tricky sometimes, and
+naturally, means more work for them and slower processing of your
+request.
<p>You should <em>never</em> translate the HTML markup—i.e. <em>do
not</em>
use the “View Source” functionality of your browser to translate
the
Index: html_node/Submitting.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Submitting.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Submitting.html 11 Nov 2009 14:50:45 -0000 1.4
+++ html_node/Submitting.html 30 Jan 2012 16:11:53 -0000 1.5
@@ -11,11 +11,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Summary.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/Summary.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Summary.html 11 Nov 2009 14:50:45 -0000 1.4
+++ html_node/Summary.html 30 Jan 2012 16:11:53 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Terminology.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Terminology.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Terminology.html 11 Nov 2009 14:50:45 -0000 1.4
+++ html_node/Terminology.html 30 Jan 2012 16:11:54 -0000 1.5
@@ -6,15 +6,15 @@
<meta name="generator" content="makeinfo 4.13">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Translation-Tips.html#Translation-Tips"
title="Translation Tips">
-<link rel="prev" href="Capitalization.html#Capitalization"
title="Capitalization">
+<link rel="prev" href="Distribution-Terms.html#Distribution-Terms"
title="Distribution Terms">
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -40,12 +40,12 @@
<div class="node">
<a name="Terminology"></a>
<p>
-Previous: <a rel="previous" accesskey="p"
href="Capitalization.html#Capitalization">Capitalization</a>,
+Previous: <a rel="previous" accesskey="p"
href="Distribution-Terms.html#Distribution-Terms">Distribution Terms</a>,
Up: <a rel="up" accesskey="u"
href="Translation-Tips.html#Translation-Tips">Translation Tips</a>
<hr>
</div>
-<h3 class="section">5.6 Language-specific Terminology</h3>
+<h3 class="section">5.7 Language-specific Terminology</h3>
<p>This is a very important topic, not yet covered by this manual.
Index: html_node/Tracking-Tasks.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Tracking-Tasks.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Tracking-Tasks.html 11 Nov 2009 14:50:45 -0000 1.4
+++ html_node/Tracking-Tasks.html 30 Jan 2012 16:11:54 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Translation-Managers.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Translation-Managers.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Translation-Managers.html 11 Nov 2009 14:50:45 -0000 1.4
+++ html_node/Translation-Managers.html 30 Jan 2012 16:11:54 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Translation-Tips.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Translation-Tips.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Translation-Tips.html 11 Nov 2009 14:50:45 -0000 1.4
+++ html_node/Translation-Tips.html 30 Jan 2012 16:11:54 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -64,7 +64,8 @@
<li><a accesskey="3" href="CSS.html#CSS">CSS</a>: General
advice how to use CSS.
<li><a accesskey="4" href="Priorities.html#Priorities">Priorities</a>:
What to translate as a priority.
<li><a accesskey="5"
href="Capitalization.html#Capitalization">Capitalization</a>: To
CAPITALIZE or not?
-<li><a accesskey="6" href="Terminology.html#Terminology">Terminology</a>:
Dealing with terminology issues.
+<li><a accesskey="6"
href="Distribution-Terms.html#Distribution-Terms">Distribution Terms</a>:
Translating distribution terms.
+<li><a accesskey="7" href="Terminology.html#Terminology">Terminology</a>:
Dealing with terminology issues.
</ul>
</body></html>
Index: html_node/Unreviewed-Translations.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/Unreviewed-Translations.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/Unreviewed-Translations.html 11 Nov 2009 14:50:45 -0000
1.4
+++ html_node/Unreviewed-Translations.html 30 Jan 2012 16:11:54 -0000
1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/index.html
===================================================================
RCS file: /web/trans-coord/trans-coord/manual/web-trans/html_node/index.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/index.html 11 Nov 2009 14:50:45 -0000 1.4
+++ html_node/index.html 30 Jan 2012 16:11:54 -0000 1.5
@@ -8,11 +8,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
@@ -91,7 +91,8 @@
</li></ul>
<li><a href="Priorities.html#Priorities">5.4 What To Translate</a>
<li><a href="Capitalization.html#Capitalization">5.5 When To CAPITALIZE</a>
-<li><a href="Terminology.html#Terminology">5.6 Language-specific
Terminology</a>
+<li><a href="Distribution-Terms.html#Distribution-Terms">5.6 Distribution
Terms</a>
+<li><a href="Terminology.html#Terminology">5.7 Language-specific
Terminology</a>
</li></ul>
<li><a name="toc_Summary" href="Summary.html#Summary">6 Overview Of The
Translation Process</a>
<ul>
@@ -114,21 +115,21 @@
<h2 class="unnumbered">GNU Web Translators Manual</h2>
-<p>This manual is a guide for the <acronym>GNU</acronym> Web Translators.<br>
-Last updated on 10.11.2009, for <acronym>GNU</acronym>nited Nations
-version 0.4.
+<p>This manual is a guide for the GNU Web Translators.<br> Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
<pre class="sp">
</pre>
-Copyright © 2009 Free Software Foundation, Inc.
+Copyright © 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
<blockquote>
Permission is granted to copy, distribute and/or modify this document
-under the terms of the <acronym>GNU</acronym> Free Documentation License,
-Version 1.3 or any later version published by the Free Software
-Foundation; with no Invariant Sections, no Front-Cover Texts, and no
-Back-Cover Texts. A copy of the license is included in the section
-entitled “<acronym>GNU</acronym> Free Documentation License.”
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled “GNU Free
+Documentation License.”
</blockquote>
<ul class="menu">
Index: html_node/topbanner.html
===================================================================
RCS file:
/web/trans-coord/trans-coord/manual/web-trans/html_node/topbanner.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- html_node/topbanner.html 11 Nov 2009 14:50:45 -0000 1.4
+++ html_node/topbanner.html 30 Jan 2012 16:11:54 -0000 1.5
@@ -10,11 +10,11 @@
<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
<!--
This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
-Last updated on 10.11.2009, for GNUnited Nations
-version 0.4.
-
- Copyright (C) 2009 Free Software Foundation, Inc.
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Index: html_node/Distribution-Terms.html
===================================================================
RCS file: html_node/Distribution-Terms.html
diff -N html_node/Distribution-Terms.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ html_node/Distribution-Terms.html 30 Jan 2012 16:11:52 -0000 1.1
@@ -0,0 +1,102 @@
+<html lang="en">
+<head>
+<title>Distribution Terms - GNU Web Translators Manual</title>
+<meta http-equiv="Content-Type" content="text/html">
+<meta name="description" content="GNU Web Translators Manual">
+<meta name="generator" content="makeinfo 4.13">
+<link title="Top" rel="start" href="index.html#Top">
+<link rel="up" href="Translation-Tips.html#Translation-Tips"
title="Translation Tips">
+<link rel="prev" href="Capitalization.html#Capitalization"
title="Capitalization">
+<link rel="next" href="Terminology.html#Terminology" title="Terminology">
+<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
+<!--
+This manual is a guide for the GNU Web Translators.
+Last updated on
+30.01.2012, for GNUnited Nations version 0.5.
+
+ Copyright (C) 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
+
+ Permission is granted to copy, distribute and/or modify this
+ document under the terms of the GNU Free Documentation License,
+ Version 1.3 or any later version published by the Free Software
+ Foundation; with no Invariant Sections, no Front-Cover Texts, and
+ no Back-Cover Texts. A copy of the license is included in the
+ section entitled ``GNU Free Documentation License.''
+ -->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"><!--
+ pre.display { font-family:inherit }
+ pre.format { font-family:inherit }
+ pre.smalldisplay { font-family:inherit; font-size:smaller }
+ pre.smallformat { font-family:inherit; font-size:smaller }
+ pre.smallexample { font-size:smaller }
+ pre.smalllisp { font-size:smaller }
+ span.sc { font-variant:small-caps }
+ span.roman { font-family:serif; font-weight:normal; }
+ span.sansserif { font-family:sans-serif; font-weight:normal; }
+--></style>
+</head>
+<body>
+<div class="node">
+<a name="Distribution-Terms"></a>
+<p>
+Next: <a rel="next" accesskey="n"
href="Terminology.html#Terminology">Terminology</a>,
+Previous: <a rel="previous" accesskey="p"
href="Capitalization.html#Capitalization">Capitalization</a>,
+Up: <a rel="up" accesskey="u"
href="Translation-Tips.html#Translation-Tips">Translation Tips</a>
+<hr>
+</div>
+
+<h3 class="section">5.6 Distribution Terms</h3>
+
+<p>Most www.gnu.org articles are released under the terms of
+the Creative Commons Attribution-NoDerivs 3.0 United States license.
+The exact HTML for English pages to use is:
+
+<pre class="example"> 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>.
+</pre>
+ <p>Pages in other languages should translate this notice, and should link
+to a translated version of the Creative Commons license “deed” if
it's
+available. Creative Commons provides standard text for this in all the
+languages they support, and we should use that wording whenever
+possible. To do that, follow these steps:
+
+ <ul>
+<li>Check at the bottom of the English deed page to see the list of
+languages they support. Follow the link the language that you want a
+translation for, if available.
+
+ <li>Follow the “Use this license for your own work” link near
the bottom
+of the translated deed page—it's in distinct yellow text.
+
+ <li>The textarea on that page provides standard HTML. Note that we're not
+using the graphic, just the text.
+
+ </ul>
+
+ <p>For example, here's the text they provide for German:
+
+<pre class="example"> Dieses Werk bzw. Inhalt steht unter einer <a
rel="license"
+
href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.de">Creative
+ Commons Namensnennung-Keine Bearbeitung 3.0 Vereinigte Staaten von
+ Amerika Lizenz</a>.
+</pre>
+ <p>Note that the link in this text is changed to point directly to the
+German language deed. We should always link to a copy of the license
+deed that's in the same language as the page itself.
+
+ <p>Pages in languages that aren't supported by CC should prepare their own
+translation, use it consistently throughout pages translated to that
+language, and link to the English language deed.
+
+ <p>Note that translations should <em>not</em> change the jurisdiction of the
+license; they should <em>always</em> link to the CC BY-ND 3.0 <em>United
+States</em> license, and <em>not</em> a different port like CC BY-ND 3.0
+Japan. This is because there are substantive differences between the way
+different ports handle moral rights issues, and we prefer the specific
+terms that are in the United States license.
+
+ </body></html>
+
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- trans-coord/manual/web-trans index.html web-tra...,
Yavor Doganov <=