[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/server .symlinks translations/cvs_savannah....
|
From: |
Alex Muntada |
|
Subject: |
www/server .symlinks translations/cvs_savannah.... |
|
Date: |
Mon, 04 Jun 2007 18:40:20 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Alex Muntada <alex_muntada> 07/06/04 18:40:20
Modified files:
server : .symlinks
Removed files:
server/translations: cvs_savannah.html draft-procedures.txt
todo.txt trans-coordinator.html
trans-standards.html trans-team-member.html
Log message:
Moved all translations stuff to standards place.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/.symlinks?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/server/translations/cvs_savannah.html?cvsroot=www&r1=1.8&r2=0
http://web.cvs.savannah.gnu.org/viewcvs/www/server/translations/draft-procedures.txt?cvsroot=www&r1=1.1&r2=0
http://web.cvs.savannah.gnu.org/viewcvs/www/server/translations/todo.txt?cvsroot=www&r1=1.4&r2=0
http://web.cvs.savannah.gnu.org/viewcvs/www/server/translations/trans-coordinator.html?cvsroot=www&r1=1.8&r2=0
http://web.cvs.savannah.gnu.org/viewcvs/www/server/translations/trans-standards.html?cvsroot=www&r1=1.4&r2=0
http://web.cvs.savannah.gnu.org/viewcvs/www/server/translations/trans-team-member.html?cvsroot=www&r1=1.3&r2=0
Patches:
Index: .symlinks
===================================================================
RCS file: /web/www/www/server/.symlinks,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- .symlinks 9 Feb 2006 04:25:19 -0000 1.10
+++ .symlinks 4 Jun 2007 18:40:02 -0000 1.11
@@ -8,3 +8,4 @@
whatsnew.html whatsnew.es.html
new-software.tmp.html new-software.html
takeaction.html takeaction.xhtml
+standards/translations translations
Index: translations/cvs_savannah.html
===================================================================
RCS file: translations/cvs_savannah.html
diff -N translations/cvs_savannah.html
--- translations/cvs_savannah.html 10 Dec 2006 23:23:23 -0000 1.8
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,255 +0,0 @@
-<?xml version="1.0" encoding="utf-8" ?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
-<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
-
-<head>
-<title>Getting CVS Access On Savannah - GNU Project - Free Software Foundation
(FSF)</title>
-<meta http-equiv="content-type" content="text/html; charset=utf-8" />
-<link rel="stylesheet" type="text/css" href="/gnu.css" />
-<link rev="made" href="mailto:address@hidden"; />
-</head>
-
-<!-- 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 -->
-
-<body>
-
-<p><a href="#translations">Translations</a> of this page</p>
-
-<h3>Getting CVS Access On Savannah</h3>
-
-<p>
-<a href="/graphics/agnuhead.html"><img src="/graphics/gnu-head-sm.jpg"
- alt=" [image of the Head of a GNU] "
- width="129" height="122" /></a>
-</p>
-
-<hr />
-
-<h4>Table of Contents</h4>
-
-<ul>
- <li><a href="#Step0"
- id="TOCStep0">Step 0: Anonymous CVS</a></li>
- <li><a href="#Step1"
- id="TOCStep1">Step 1: Savannah</a></li>
- <li><a href="#Step2"
- id="TOCStep2">Step 2: SSH</a></li>
- <li><a href="#Step3"
- id="TOCStep3">Step 3: CVS</a></li>
-</ul>
-
-<hr />
-
-<h3><a href="#TOCStep0"
- id="Step0">Step 0: Anonymous CVS</a></h3>
-
-<p>
-Before you get an account in Savannah and start working
-as a member of a translation team, you can try the anonymous
-CVS access to get a fresh copy of the HTML files under
-<a href="/home.html">www.gnu.org</a>:
-</p>
-
-<pre>
-
- cvs -z3 -d:pserver:address@hidden:/web/www co www/philosophy
-
-</pre>
-
-<p>
-But, in order to get full CVS write access, you'll have to
-finish the remaining steps below.
-</p>
-
-<hr />
-
-<h3><a href="#TOCStep1"
- id="Step1">Step 1: Savannah</a></h3>
-
-<p>
-Start by going to <a
-href="http://savannah.gnu.org/";>http://savannah.gnu.org/</a>
-and clicking on <b>New User via SSL</b> (third link on the left bar).
-</p>
-
-<p>
-Type in your desired login name, password (twice), full/real name,
-and email address, then click on <b>Register</b>. After a few seconds
-you'll see a message like this:
-</p>
-
-<pre>
-Savannah: New Account Registration Confirmation
-Congratulations. You have registered on Savannah.
-Your new username is: your_user_name
-You are now being sent a confirmation email to verify your email address.
-Visiting the link sent to you in this email will activate your account.
-
-</pre>
-
-<p>
-Check your email and use the provided link to activate your new account.
-The link should look something like:</p>
-
-<pre>
-
-https://savannah.gnu.org/account/verify.php?confirm_hash=some_hex_number
-
-</pre>
-
-<p>
-This will take you to a Savannah Account Verification page where you'll have
-to type in the login and password you've chosen, then click on <b>Login</b>.
-</p>
-
-<p>If everything went OK you'll be greeted with the following message:</p>
-
-<pre>
-
-Welcome to Savannah
-
-You are now a registered user on Savannah.
-
-As a registered user, you can participate fully in the activities on the site.
-You may now post messages to the project message forums, post bugs for software
-in Savannah, sign on as a project developer, or even start your own project.
-
-You should take some time to read through the site documentation so that you
-may take full advantage of Savannah.
-
-Enjoy the site.
-
---the Savannah team.
-
-</pre>
-
-<hr />
-
-<h3><a href="#TOCStep2"
- id="Step2">Step 2: SSH</a></h3>
-
-<p>
-You are ready now for the next step, setting your ssh environment.
-Click on the first link under Savannah group of links,
-<b>User Docs (FAQ)</b> to learn how to <a
-href="https://savannah.gnu.org/faq/?group_id=5802&question=User_Account_-_How_do_I_configure_my_SSH_access.txt";>configure
the SSH access</a>.</p>
-
-<hr />
-
-<h3><a href="#TOCStep3"
- id="Step3">Step 3: CVS</a></h3>
-
-<p>
-CVS will let you get and maintain a synchronized copy of the content of
-<a href="/home.html">www.gnu.org</a> on your own computer.</p>
-
-<p>
-First make sure you have cvs installed. If you don't have it, you can
-get it from <a href="http://www.cvshome.org/";>CVS HOME</a>.
-For now, I'll assume you already have cvs installed somewhere.
-</p>
-
-<p>
-Create a new directory and change directory there, then issue the
-following command (replace with your own login):</p>
-
-<pre>
-
- cvs -z3 address@hidden:/web/www co www/philosophy
-
-</pre>
-
-<p>
-You might have to also type in you passphrase. If you want to avoid typing
-in the passphrase for each cvs command, use the <code>ssh-agent</code>
-program to handle the authentication process for you.</p>
-
-<p>
-That's it. Replace <code>philosophy</code> with another directory name to
-retrieve its content.</p>
-
-<p>
-Congratulations, you now have <code>read</code> access from www.gnu.ors's
-CVS repository. For <code>write</code> access, ask the <a
-href="mailto:address@hidden";>translation teams coordinator</a>
-for permission.</p>
-
-<hr />
-
-<!-- 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 class="translations">
-<p><a id="translations"></a>
-<b>Translations of this page</b>:<br />
-
-<!-- Please keep this list alphabetical, and in the original -->
-<!-- language if possible, otherwise default to English -->
-<!-- If you do not have it English, please comment what the -->
-<!-- English is. If you add a new language here, please -->
-<!-- advise address@hidden and add it to -->
-<!-- - in /home/www/bin/nightly-vars either TAGSLANG or WEBLANG -->
-<!-- - in /home/www/html/server/standards/README.translations.html -->
-<!-- one of the lists under the section "Translations Underway" -->
-<!-- - if there is a translation team, you also have to add an alias -->
-<!-- to mail.gnu.org:/com/mailer/aliases -->
-<!-- Please also check you have the 2 letter language code right versus -->
-<!-- http://www.w3.org/WAI/ER/IG/ert/iso639.htm -->
-[
- <a href="/server/translations/cvs_savannah.html">English</a>
-]
-</p>
-</div>
-
-
-
-<div class="copyright">
-<p>
-Return to the <a href="/home.html">GNU Project home page</a>.
-</p>
-
-<p>
-Please send FSF & GNU inquiries to
-
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
-There are also <a href="/home.html#ContactInfo">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>
-Please see the
-<a href="/server/standards/README.translations.html">Translations
-README</a> for information on coordinating and submitting
-translations of this article.
-</p>
-
-<p>
-Copyright (C) 2002, 2005 Free Software Foundation, Inc.,
-51 Franklin St, Fifth Floor, Boston, MA 02110, USA
-<br />
-Verbatim copying and distribution of this entire article is
-permitted worldwide without royalty in any medium provided
-this notice is preserved.
-</p>
-
-<p>
-Updated:
-<!-- timestamp start -->
-$Date: 2006/12/10 23:23:23 $ $Author: alex_muntada $
-<!-- timestamp end -->
-</p>
-</div>
-
-</body>
-</html>
Index: translations/draft-procedures.txt
===================================================================
RCS file: translations/draft-procedures.txt
diff -N translations/draft-procedures.txt
--- translations/draft-procedures.txt 5 Mar 2007 22:55:07 -0000 1.1
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,100 +0,0 @@
-[These are *draft* procedures, to be amended by the web-translators
-team and pending discussion/ideas/corrections with the team leaders.]
-
-Finding a Translation Team
-==========================
-
-The existing translation teams are listed at README.translations as
-"Translations underway". The list includes details about the project
-page and the team leader. In case your language is not listed there,
-it means that
-
- * There is no team established and no pages translated
- * Some pages were translated by occasional contributors, but no
- team has been formed
- * The page is not updated with the current team information
-
-In all cases, if you can't find a team for your language, please
-contact us at <address@hidden>.
-
-
-Joining an Existing Team
-========================
-
-First, register an account at Savannah, if you don't already have
-one. When you login, go to "My groups [link]" and fill in the name of
-the project in the field "Request for inclusion"; then complete the
-form and submit it. That way, we will be able to see the date when
-you sent your request and take necessary steps in case the team leader
-is inactive. It is certainly fine to have private exchange by mail,
-Jabber or IRC with the team leader in parallel to your request for
-inclusion to the project. Most probably you'll want to learn more
-about the established translation process and on the other hand, the
-leader might want to inform you about the project's internal
-procedures.
-
-If you don't hear from the team leader in two weeks, inform us about
-it at <address@hidden>.
-
-
-Create a New Team
-=================
-
-If there is no team for your language, you might consider establishing
-one. This is a very important activity and has always been a priority
-for the GNU Project. As a team leader you will have certain
-responsibilities. The first thing to do is to read
-README.translations and all the guidelines/extra information linked
-from that page. Checkout the www.gnu.org CVS repository [link] to get
-an idea about the HUGE amount of work that has do be done. Don't
-despair -- one by one, that job can be accomplished, exactly in the
-same way the GNU operating system was developed.
-
-Let us know at <address@hidden> that you intend to start a
-new team and send us the questionnaire [link]. Be fair and answer to
-the questions with your own words, as you feel or think on the topic.
-Do not answer with links to gnu.org articles -- we are quite familiar
-with them. The purpose of the questionnaire is to enable us to make a
-judgement (albeit vague) about your motivation and dedication, and
-understanding of some core values of the Free Software Movement.
-
-We will reply with comments or directions. Register an account at
-Savannah and apply for a new "www.gnu.org" translation project. The
-project name should be "www-$LANGCODE" [FIXME: with or without dash?],
-i.e. for Swedish that would be "www-sv". We maintain a list of
-articles that are of high priority [link] to translate -- it is a very
-good idea to start with them. Until you are granted CVS write access,
-send all translations as html attachments to us [FIXME: include general
-guidelines about editing the HTML code, etc., perhaps would fit in the
-next section].
-
-Responsibilities of the team leader [FIXME, FIXME harder, FIXME a lot]
------------------------------------
-
-Recommendations for the team's organization [FIXME -- to be extended]
--------------------------------------------
-
-Do not work alone -- we require translations to be made by teams for
-several specific reasons. As a beginning, find at least one person to
-proof-read your translations before you submit them. This activity is
-as important as the translating process -- often you will make errors
-or your wording will be unclear or ambiguous. Others spot such issues
-much easier than you (and vice versa).
-
-
-Becoming a team leader
-======================
-
-[FIXME: To be discussed further, and we'll base it on the outcome and
-lessons learnt from the current Norwegian case, which will be the
-"guinea pig" for this procedure, as it seems.]
-
-
-Granting write CVS access
-=========================
-
-You have to submit your first several translations to
-<address@hidden>. You will probably receive advices and
-recommendations. When we feel that you are doing well, you will be
-granted write access. Be careful -- you will have the right to edit
-the whole "www" tree and basically the web pages of every project.
Index: translations/todo.txt
===================================================================
RCS file: translations/todo.txt
diff -N translations/todo.txt
--- translations/todo.txt 11 Mar 2007 23:20:51 -0000 1.4
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,54 +0,0 @@
-* teams:
- [ ] track translation team inactivity
- - File bugs for issues reported to web-translators [yavor]
- - Generate status reports from team leaders' reports and bugs
- handling [yavor]
- [ ] get reports by team leader
- - We have to decide about the frequency and format, perhaps
- make a recommended template [yavor]
-
-* procedures:
- Draft procedures to be discussed with the team leaders before they
- become official, see draft-procedures.txt [yavor]
- [ ] finding a translation team
- [ ] joining an existing team
- [ ] create a new team
- [ ] becoming a team leader
- [ ] granting write CVS access
- [ ] requirements to publish a translation (e.g. number of reviews needed)
-
-* resources:
- [ ] mailing lists
- [ ] savannah projects
- [ ] cvs repos
- [ ] mail aliases
- [ ] rt queue
-
-* pending tasks (some of them listed as bugs or tasks in trans-coord):
- [ ] update /server/translations
- [ ] update or move /server/standards translation related content
- [ ] important languages w/o teams
- - Probably keep a list at /server/takeaction [yavor]
- [ ] recruit more volunteers as web-translators staff
- - We're currently 4 people for ~20 teams (many of them inactive,
- though). In case the revamping of the coordination process is
- followed by an influx of more teams and more activity, we'll
- have to think about recruitment. For now, we need more
- translators :-) [yavor]
- [ ] update web-translators-?? mail aliases
- [ ] announce translation priorities page (www, trans-coord and rms)
-
-* ideas:
- [ ] priority translations page (usually requested by rms)
- [ ] evaluate new leaders
- - Questionnaire [yavor]
- [ ] request team project planning
- - This is a bit touchy area, better to discuss on the ML [yavor]
- [x] create a page with translation priorities
- [ ] Regarding /software: communicate with the GNU maintainers and
- maintain a list of packages where we have blanket permission to
- commit translations without specific approval. To make
- translators' life easier, maintain a list of such packages.
- Encourage team leaders to give warm welcome to such occasional
- contributors (translators of /software) and eventually recruit
- them as regular team members. [yavor]
Index: translations/trans-coordinator.html
===================================================================
RCS file: translations/trans-coordinator.html
diff -N translations/trans-coordinator.html
--- translations/trans-coordinator.html 9 Jun 2005 17:35:36 -0000 1.8
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,128 +0,0 @@
-<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">
-<HTML>
-<HEAD>
-<TITLE>Translation Coordinators - GNU Project - Free Software Foundation
(FSF)</TITLE>
-<LINK REV="made" HREF="mailto:address@hidden";>
-</HEAD>
-<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#1F00FF" ALINK="#FF0000"
VLINK="#9900DD">
-<H3>Coordinating a Translation Team</H3>
-<A HREF="/graphics/agnuhead.html"><IMG SRC="/graphics/gnu-head-sm.jpg"
- ALT=" [image of the Head of a GNU] "
- WIDTH="129" HEIGHT="122"></A>
-
-[
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
- <A HREF="trans-coordinator.html">English</A>
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
-]
-
-<P>
-<!-- Replace this list with the page's contents. -->
-<H4>Table of Contents</H4>
-<UL>
- <LI><A HREF="#trans_teams" NAME="TOCtrans_teams">About the GNU translation
teams</A>
- <LI><A HREF="#tasks" NAME="TOCtasks">Tasks</A>
- <LI><A HREF="#tips" NAME="TOCtips">Tips</a>
- <LI><A HREF="#cvs" NAME="TOCcvs">CVS</a>
- <LI><A HREF="#privacy" NAME="TOCPrivacy">Privacy policy</a>
- <LI><A HREF="#other" NAME="TOCother">Other texts to read</a>
-</UL>
-
-<P>
-<HR>
-<P>
-<H4><A HREF="#TOCtrans_teams" NAME="trans_teams">About the GNU translations
teams</A></H4>
-<P>
-This page is a short description of the role played by the GNU Translation
Team Coordinator.
-<P>
-<H4><A HREF="#TOCtasks" NAME="tasks">Tasks</A></H4>
-<P>
-The following is a list of the tasks a coordinator of a traslation team should
perform:
-<P>
-<ul>
-<li>1. Contact constantly, at least once a month, the Web Translations Manager
<address@hidden> to let hir (her or him) know
-about the development of the team. Important information to provide the
web-translators is : Number of old and new volunteers and number of pages
-translated since the last contact.</li>
-<li>2. Provide first help to newcoming volunteers willing to join the team.
Ask them to read the <a
-href="/server/standards/README.translations.html">general translation
directives</a>, and inform hir about the role to be played inside
-the team, as well of any internal rules.</li>
-<li>3. Keep a record of the in-progress translations on the team. This can be
done in any way the coordinator find easier: Either
-writing a web page and uploading it to the web server, or a local record on
hir machine.
-<li>4. Make sure that every page is reviewed at least by two volunteers not
involved in the original translation, when possible.</li>
-<li>5. Upload the pages to the web server using CVS.
-<li>6. Monitor the changes on the server to keep the translations current.</li>
-</ul>
-<H4><A HREF="#TOCtips" NAME="tips">Tips</A></H4>
-<p>
-<b>Start easy</b>. The first pages to translate should be those with few
paragraphs. Do this until you get more
-fluent with the translation process.
-<p>
-<b>Do not translate the GNU Flashes</b>. This section of the GNU Home page
changes too often to keep it current. Include the GNU Flashes
-only if your team is big enough to keep pace of this changes
-(> 15 volunteers).
-<p>
-<b>Do not translate the <a href="/boilerplate.html">boilerplate</a></b> or any
other page which is intended to be read primarily by the GNU
-volunteers, like the <a
href="/server/standards/README.translations.html">general translation
directives</a> or this page. It's useless.
-<H4><A HREF="#TOCcvs" NAME="cvs">CVS</A></H4>
-https://savannah.gnu.org/cvs/?group_id=23
-
-<H4><A HREF="#TOCPrivay" NAME="privacy">Privacy</A></H4>
-
-We are very serious about the privacy. The coordinator of a translation team
may choose to include either (or
-none) of these data into the
<code>/server/standards/README.translations.html</code> file.
-<br><br>
-<ul>
-<li>Coordinator complete name or an alternative alias.
-<li>Email email address (either at GNU.org or a private address).
-<li>Group email address. address@hidden
-<li>Group web URL, when available. This address should be preferably at the
GNU.org web site. Remember not to link
-any site where propietary software is announced, advertised or promoted.
-</ul>
-<br><br>
-<H4><A HREF="#TOCother" NAME="other">Other texts to read</A></H4>
-
-<HR>
-
-Note : Do not translate this page. <br>
-[
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
- <A HREF="trans-coordinator.html">English</A>
-<!-- | A HREF="/boilerplate.LG.html" LANGUAGE /A -->
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
-]
-
-<P>
-Return to <A HREF="/home.html">GNU's home page</A>.
-<P>
-
-Please send FSF & GNU inquiries & questions to
-
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>.
-There are also <A HREF="/home.html#ContactInfo">other ways to
-contact</A> the FSF.
-<P>
-
-Please send comments on these web pages to
-
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>,
-send other questions to
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>.
-<P>
-Copyright (C) 2001 Free Software Foundation, Inc.,
-51 Franklin St, Fifth Floor, Boston, MA 02110, USA
-<P>
-Verbatim copying and distribution of this entire article is
-permitted in any medium, provided this notice is preserved.
-<P>
-Updated:
-<!-- timestamp start -->
-$Date: 2005/06/09 17:35:36 $ $Author: alex_muntada $
-<!-- timestamp end -->
-<HR>
-</BODY>
-</HTML>
-
Index: translations/trans-standards.html
===================================================================
RCS file: translations/trans-standards.html
diff -N translations/trans-standards.html
--- translations/trans-standards.html 5 May 2005 19:37:20 -0000 1.4
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,108 +0,0 @@
-<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">
-<HTML>
-<HEAD>
-<TITLE>Translation Coordinators - GNU Project - Free Software Foundation
(FSF)</TITLE>
-<LINK REV="made" HREF="mailto:address@hidden";>
-</HEAD>
-<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#1F00FF" ALINK="#FF0000"
VLINK="#9900DD">
-<H3>Coordinating a Translation Team</H3>
-<A HREF="/graphics/agnuhead.html"><IMG SRC="/graphics/gnu-head-sm.jpg"
- ALT=" [image of the Head of a GNU] "
- WIDTH="129" HEIGHT="122"></A>
-
-[
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
- <A HREF="trans-coordinator.html">English</A>
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
-]
-
-<P>
-<!-- Replace this list with the page's contents. -->
-<H4>Table of Contents</H4>
-<UL>
- <LI><A HREF="#footers" NAME="TOCfooters">Footers in every GNU Translated
page</A>
- <LI><A HREF="#privacy" NAME="TOCprivacy">Translators Privacy</A>
-</UL>
-
-<P>
-<HR>
-<P>
-<H4><A HREF="#TOCfooters" NAME="footers">Footers in every GNU Translated
page</A></H4>
-<P>
-The following is an example of how the footer of every translation must be
written.
-<br><br><hr width="60%">
-<ul><code>
-<P>
-Return to <A HREF="/home.html">GNU's home page</A>.
-<P>
-FSF & GNU inquiries & questions to
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>.
-Other <A HREF="/home.html#ContactInfo">ways to contact</A> the FSF.
-<P>
-Comments on these web pages to
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>,
-send other questions to
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>.
-<P>
-Translation <A HREF="/server/standards/README.Language-translation.LG.html">
-<EM>Language translation team</EM></A>
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>
-<P>
-Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002 Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110, USA
-<P>
-Verbatim copying and distribution of this entire article is
-permitted in any medium, provided this notice is preserved.
-</code></ul>
-<hr width="60%"><br><br>
-Notes about the footer:
-<br><br>
-<ul>
-<li> The "Return to GNU's home page" link should point to the same language.
(for example, home.it.html). </li>
-<li> "Language translation team" link must always point to the page under
/server/translations/translations.<i>lang_code</i>.html, where
-<i>lang_code</i> is the ISO 639 two-letter code.</li>
-<li> The "address@hidden" link is a <code>mailto:</code> to the group address,
<code>web-translators-LG</code>. In no case other adresses
-should be inserted here.
-</ul>
-<BR><BR>
-
-<H4><A HREF="#TOCprivacy" NAME="privacy">Translators privacy</A></H4>
-
-<p>The translator may choose, at his own discretion, to include hir name
and/or email address at the end of
-a translated page. Be advised that, due to the popularity of the GNU web site,
including an email address may
-increase the rate of spam received by that account.</p>
-
-<HR>
-
-<P>
-Return to <A HREF="/home.html">GNU's home page</A>.
-<P>
-
-Please send FSF & GNU inquiries & questions to
-
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>.
-There are also <A HREF="/home.html#ContactInfo">other ways to
-contact</A> the FSF.
-<P>
-
-Please send comments on these web pages to
-
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>,
-send other questions to
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>.
-<P>
-Copyright (C) 2001 Free Software Foundation, Inc.,
-51 Franklin St, Fifth Floor, Boston, MA 02110, USA
-<P>
-Verbatim copying and distribution of this entire article is
-permitted in any medium, provided this notice is preserved.
-<P>
-Updated:
-<!-- timestamp start -->
-$Date: 2005/05/05 19:37:20 $ $Author: novalis $
-<!-- timestamp end -->
-<HR>
-</BODY>
-</HTML>
-
Index: translations/trans-team-member.html
===================================================================
RCS file: translations/trans-team-member.html
diff -N translations/trans-team-member.html
--- translations/trans-team-member.html 5 May 2005 19:37:20 -0000 1.3
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,124 +0,0 @@
-<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">
-<HTML>
-<HEAD>
-<TITLE>Translation Team Member - GNU Project - Free Software Foundation
(FSF)</TITLE>
-<LINK REV="made" HREF="mailto:address@hidden";>
-</HEAD>
-<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#1F00FF" ALINK="#FF0000"
VLINK="#9900DD">
-<H3>Being a member of a Translation Team</H3>
-<A HREF="/graphics/agnuhead.html"><IMG SRC="/graphics/gnu-head-sm.jpg"
- ALT=" [image of the Head of a GNU] "
- WIDTH="129" HEIGHT="122"></A>
-
-[
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
- <A HREF="trans-coordinator.html">English</A>
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
-]
-
-<P>
-<!-- Replace this list with the page's contents. -->
-<H4>Table of Contents</H4>
-<UL>
- <LI><A HREF="#joining_a_team" NAME="TOCjoining_a_team">Joining a GNU
translation team</A>
- <LI><A HREF="#preparation" NAME="TOCtasks">Preparation</A>
- <LI><A HREF="#team_member" NAME="TOCteam_member">Tasks of a team member</a>
- <LI><A HREF="#privacy" NAME="TOCPrivacy">Privacy policy</a>
-</UL>
-
-<P>
-<HR>
-<P>
-<H4><A HREF="#TOCjoining_a_team" NAME="joining_a_team">Joining a GNU
Translations team</A></H4>
-<P>
-This page is intended for those volunteers that approach the GNU willing to
join the translation efforts.
-<P>
-<H4><A HREF="#TOCpreparation" NAME="preparation">Preparation</A></H4>
-<P>
-The following is a list of the tasks a new volunteer must perform.
-<P>
-<ul>
-<li>1. Read the <A
HREF="/server/standards/README.translations.html#TranslationsUnderway">Translations
Underway section of
-the README.translations page</A> to see if your language appears there.
-<li>2. If there's already a team for the language you are willing to translate
to, contact the team coordinator and wait a
-reasonable time for an answer. (see note)
-<li>3. The team coordinator will assign you a page to translate or review,
depending on the current team needs.
-<li>4. <b>Have fun</b>. This is a volunteer job and having fun along is not
only desirable, but encouraged. Please keep a
-good team climate.
-</ul>
-<p><i>Note: If no answer is ever received from the team coordinator, contact
the Web Translations Manager
-<address@hidden> and let hir now about it. </i></p>
-
-<p>Other suggestions:</p>
-<ul>
-<li>It might be useful for you to read the <A
HREF="trans-coordinator.html">Coordinators guidelines</a> as well.
-<li>Try to recruit other team members. Let others know about your work at the
GNU and they may be interested.
-</ul>
-
-<H4><A HREF="#TOCteam_member" NAME="team_member"></A></H4>
-<p>Once you have joined the team of your choice, the tasks for any team member
are as follows:
-<ul>
-<li><b>Continuous contact</b>. Be in contact with your team coordinator, at
least once a month. Let hir know about your
-current work status and availability.
-<li><b>Plan your leaves</b>. If you know you will not be available for a long
period of time (say, more than a couple of
-weeks), let the coordinator know about this situation. He/she may be counting
on you for a certain job.
-<li><b>Translate as directed</b>. Do not translate anything before asking the
coordinator. This certain page may be
-already translated and is waiting to be uploaded or somebody else can still be
working on it, either translating or
-reviewing.
-</ul>
-
-
-<H4><A HREF="#TOCPrivacy" NAME="privacy">Privacy</A></H4>
-
-<p>We are very serious about your privacy. You may choose to add your name
and/or email to a translated or reviewed page;
-but you can also add nothing and remain anonymous. Only your coordinator knows
who made what translation and nobody else.
-We keep no public records of it. </p>
-
-<p>Be aware that, due to the high traffic in the GNU web pages, we are
constantly scanned by spam robots. Including your
-email address on the translated page may increase your spam levels
significantly.</p>
-
-<hr>
-
-Note : Do not translate this page. <br>
-[
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
- <A HREF="trans-coordinator.html">English</A>
-<!-- | A HREF="/boilerplate.LG.html" LANGUAGE /A -->
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
-]
-
-<P>
-Return to <A HREF="/home.html">GNU's home page</A>.
-<P>
-
-Please send FSF & GNU inquiries & questions to
-
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>.
-There are also <A HREF="/home.html#ContactInfo">other ways to
-contact</A> the FSF.
-<P>
-
-Please send comments on these web pages to
-
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>,
-send other questions to
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>.
-<P>
-Copyright (C) 2001 Free Software Foundation, Inc.,
-51 Franklin St, Fifth Floor, Boston, MA 02110, USA
-<P>
-Verbatim copying and distribution of this entire article is
-permitted in any medium, provided this notice is preserved.
-<P>
-Updated:
-<!-- timestamp start -->
-$Date: 2005/05/05 19:37:20 $ $Author: novalis $
-<!-- timestamp end -->
-<HR>
-</BODY>
-</HTML>
-
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/server .symlinks translations/cvs_savannah....,
Alex Muntada <=