www/server/standards/translations details.html

[Alex Muntada]

CVSROOT:        /web/www
Module name:    www
Changes by:     Alex Muntada <alex_muntada>     07/06/04 19:46:54

Added files:
        server/standards/translations: details.html 

Log message:
        First draft published.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/translations/details.html?cvsroot=www&rev=1.1

Patches:
Index: details.html
===================================================================
RCS file: details.html
diff -N details.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ details.html        4 Jun 2007 19:46:46 -0000       1.1
@@ -0,0 +1,218 @@
+<!--#include virtual="/server/header.html" -->
+<title>Web Translation Details - GNU Project - Free Software Foundation 
(FSF)</title>
+<!--#include virtual="/server/banner.html" -->
+<h1>Web Translation Details</h1>
+
+<p>This is a detailed description of translation processes for
+<a href="/">the GNU website</a>, so everyone can quickly get
+the picture of how things are done and the amount of work that
+is needed to get them done.
+</p>
+
+<!-- ---------------------------------------------------------------- -->
+
+<h2>Introduction</h2>
+<p>The GNU website has thousands of documents, most of them
+philosophical articles and technical documents which need
+to be translated to get them available to a broader audience,
+so everybody around the globe can benefit from them.
+Dealing with the task of translating a website this large
+is a hard job, and too often people volunteering translations
+get frustrated or loose interest in keeping up with that work.
+</p>
+
+
+<h2>Web Translators</h2>
+<p>Translators should work on translating web pages according
+to the <a href="/server/standards/">GNU Web Standards</a>
+designed by webmasters and sysadmins at GNU.  Among many other
+things, this means that the following guidelines should be
+strictly performed:</p>
+
+<ol>
+<li><strong>Don't mess with the original HTML layout.</strong>
+Usually, GNU webmasters spend a lot of time designing
+the web pages and not keeping the HTML from translations
+as close as possible to the original is troublesome.</li>
+<li><strong>Don't use visual editors,
+use plaintext editors instead.</strong>
+Otherwise, it's very difficult to be sure that previous
+guideline is achieved.  Moreover, visual editors used
+often add extra HTML tags and sometimes they refer to
+non-free software.</li>
+</ol>
+
+<p>Please, see also
+<a href="trans-team-member.html">how to join a web translation team</a>.
+
+<h2>Web Translation Teams</h2>
+<p>Each language present on the GNU website should have
+a team, however some translations were volunteered by
+people who didn't want to take charge of a team; hence,
+the lack of teams for some languages present.  Teams
+provide the context for a group of people with common
+objectives, i.e. translating the GNU website into a
+known language to all team members.  Each team has at
+least one leader (or admin) that will be the team
+contact and translation coordinator, thus having a few
+extra rights and responsibilities.</p>
+
+<h3>Savannah</h3>
+<p>Every translation team should have a project in
+<a href="http://savannah.gnu.org/";>Savannah</a>.  For
+historical reasons those team names may vary a lot (e.g.
+<a href="https://savannah.gnu.org/p/spanish";>spanish</a>,
+<a href="https://savannah.gnu.org/p/www-bg";>www-bg</a>,
+<a href="https://savannah.gnu.org/p/elwebtrans";>elwebtrans</a>,
+etc.)  Plus, there are some teams that use their own
+resources outside from Savannah; althought there's no
+obligation to use Savannah for team work, the need
+for a Savannah project for each language is obvious:
+it's a standard way to find information for translation
+teams and their contacts.</p>
+
+<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, home pages, mailing lists, etc.  How each uses
+these resources it's up to the team itself.</p>
+
+<h3>Mailing lists</h3>
+<p>Mailing lists usually are linked to existing Savannah
+projects, but the software used to manage them
+(<a href="/software/mailman/">Mailman</a>)
+isn't part of Savannah, which means that there are lists
+that aren't linked to any specific project, though may be
+related to some.</p>
+
+<h3>Aliases</h3>
+<p>On the other side, people with an account in GNU servers
+usually can update existing team aliases (e.g. web-translators-fr).
+However, this isn't recommended unless you know exactly
+what to do.  Web translation managers have more experience
+on this and will take care of updating aliases at leader's
+request.</p>
+
+<h3>Team Leaders</h3>
+<p>People in charge of a translation team are team leaders
+and Savannah project admins.  Usually, they're the only
+people from their team with write CVS access to the GNU website,
+and are listed as team contacts in
+<a href="/server/standards/README.translations.html">translations README</a>.
+Please, see also
+<a href="trans-coordinator.html">how to coordinate a translation team</a>.
+</p>
+
+<h2>Web Translation Managers</h2>
+<p>Translation managers are those people coordinating
+translation coordinators (team leaders) and dealing with
+all sort of requests or issues related to GNU website
+translation, while trying to improve the translation
+procedures and coodinating with GNU webmasters, too.</p>
+
+<h3>Request Tracker (RT)</h3>
+<p><a href="http://www.bestpractical.com/rt/";>Request Tracker</a>
+is a ticketing system that helps managing translation
+requests and issues to translation managers.  It's the
+successor of former web-trans mailing list and was setup
+more or less like its brother queue webmasters primarily
+to deal with the huge amount of spam that web-trans was
+receiving.  Sometimes, tickets are moved from other RT
+queues to web-translators and occasionally tickets from
+web-translators are moved into other queues.</p>
+
+<p>There's the web-translators-staff group in RT that
+lists RT users with right in web-translators queue,
+web-translators-admin group for people in RT that can
+change web-translators config.  Finally, there's a
+custom field specific to web-translators queue that
+helps tagging which language each ticket is related to.
+This custom field can only be managed by people in
+web-translators-admin group, but anyone in group
+web-translators-staff can use it to tag tickets.</p>
+
+<h3>Savannah</h3>
+
+<ol>
+<li><a href="https://savannah.gnu.org/p/www";>www</a></li>
+<li><a href="https://savannah.gnu.org/p/trans-coord";>trans-coord</a></li>
+<li>specific translation team projects</li>
+<li>Savannah administration</li>
+</ol>
+
+<h3>Mailing Lists</h3>
+<p>There are a few mailing lists that every translation
+manager should be subscribed to:</p>
+
+<ol>
+<li>www-discuss (member)</li>
+<li>www-commits (admin)</li>
+<li>trans-coord-discuss (member+admin)</li>
+<li>trans-coord-news (admin)</li>
+</ol>
+
+<p>Some of them, will need that some translation managers
+become their admins too (as noted above).</p>
+
+<h3>Aliases</h3>
+<p>Translation managers should know how to update, create
+or remove aliases from GNU servers per request of translation
+team leaders.  An account in GNU servers is a prerequisite.</p>
+
+<h3>To Do</h3>
+Some tasks <a href="todo.txt">to do</a> were recorded.
+Need more work.
+
+<h3>Draft Procedures</h3>
+Some common <a href="draft-procedures.txt">procedures</a>
+were drafted.  Need more work.
+
+
+<!-- ---------------------------------------------------------------- -->
+
+<!-- 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-min.html" -->
+<div id="footer">
+
+<p>
+Please send FSF &amp; GNU inquiries to 
+<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+There are also <a href="/contact/">other ways to contact</a> 
+the FSF.
+<br />
+Please send broken links and other corrections (or suggestions) to
+<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+</p>
+
+<p>
+Copyright &copy; 2007 Free Software Foundation, Inc.,
+</p>
+<address>51 Franklin St, Fifth Floor, Boston, MA 02110, USA</address>
+<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>
+
+<p>
+Updated:
+<!-- timestamp start -->
+$Date: 2007/06/04 19:46:46 $
+<!-- timestamp end -->
+</p>
+</div>
+
+<div id="translations">
+<h4>Translations of this page</h4>
+<p>This page does not need any translation.
+It's for webmaster and translator eyes only.  ;)</p>
+</div>
+</div>
+
+</body>
+</html>