[Web-trans] Re: Translation Coordination Status

[Praveen Kamat]

--- Alex Muntada <address@hidden> wrote:

> To summarize:
> 
> * <address@hidden>:
> If you like the idea of asking for a new RT queue, I
> will ask
> sysadmin, request them to change the
> web-translator-manager
> alias and add spam filters to web-trans too.

Yes, I agree. We definitely need a  separate RT queue
for translation coordination to help track and manage
the requests as also admin privileges to the web-trans
mailing list.  

> * <address@hidden>:
> One of you (Dwayne or Praveen) who are already
> developers on the
> trans-coord project should ask savannah-hackers for
> admin rights
> (if no response is sent in 1 week, resend the
> request CC to rms).

Will do. But it is my understanding that the mailing
lists creation feature within the savannah projects is
 still inactive.
 
Attached is the updated 
<http://www.gnu.org/server/standards/README.translations.html>
page based on the responses I received so far. I have
opted to remove the inactive team lead contacts in the
'Translations Underway' section in an effort to
accurately reflect the current situation. Please
review and publish if it looks ok to you. 

Thanks
Praveen
GNU/FSF Translation Coordinator 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Guide to Translating www.gnu.org Web Pages

[ English
| Indonesian

]

---

Table of Contents

• General Guide
• Two-letter Language Codes
• What to Translate
• Linking Other Documents
• Translations into Other Languages
• Filenames
• Tools to Help Translators
• Keeping Translations Current
• Translations Underway
• Final Notes

---

General Guide

• Before doing anything, read both
  • the Guidelines for GNU Web Site Volunteers,
  • the FSF HTML Style Sheet, http://www.gnu.org/server/fsf-html-style-sheet.html
• After reading this page, refer to the Translations Underway list, and check if there is already a team formed for the language you want to translate to. If not, contact address@hidden, and ask if you can start a new team for your language.

Two-letter Language Codes

• RFC 1766 describes what two-letter language codes are allowed. ISO 639 gives the two-letter language codes in it's 2nd column. Later versions of RFC 1766 and ISO 639 may exist.
• If ISO 639 does not have a code, do some research and find out the right one to use. ISO 3166 gives the codes for countries. Language and country codes do not have to be the same. It is a mistake to assume a country code can be substituted for a language code - unless you verify it against a standard.

What to Translate

• Documents should be converted together with their "glue pages", such as home.html and philosophy/philosophy.html.
• Don't translate anything under these directories:

  /software/

  We leave that area up to each maintainer. But if you want to help a maintainer do translations, ask hir (him or her).

  /brave-gnu-world/

  Here's how to help translate Brave GNU World.

  When translating "GNU's Not Unix," please ensure that the translation remains recursive. If a recursive translation cannot be conceived, use the following format: "GNU's Not Unix" (GNU �r inte Unix).

Linking Other Documents

• All links are relative to the web server root, meaning that they should link to, for example, /software/software.html and not just software.html.
• Link should be made pointing to a translated page if it exists, else made pointing to the English original. You should NOT make links that depend upon content negotiation. One reason is that they will fail on mirror servers that do not do content negotiation.

Translations into Other Languages

• The top and bottom of all translations (including the English original) should contain links to other translations of the document when such exists. See the http://www.gnu.org/boilerplate.html for an example on how to do this.

Filenames

• Translations should be named PAGENAME.LG.html where LG is the two-letter language code. For example, a German translation of home.html should be named home.de.html.
• There exists a symlink index.html pointing to some other file other.html. Create a symlink named index.LG.html pointing to the correct translation other.LG.html.

Tools to Help Translators

• A file TAGS.LG in directory ~www/html/ lists all the HTML files translated into language LG. These files allow one to search or query replace all of the HTML files for a language code LG. See these instructions for more information.

Keeping Translations Current

• For all translations to be kept current, you should ask the Translations Manager, <address@hidden> to subscribe you to the diffmon-web mailinglist. Then you will get sent one email for each page that is modified in cvs (for the www module). The traffic is around 4-5 mails per day, more on weekends. It's suggested that you save all such email and burst through them about once a week to make sure the translations are current.

Translations Underway

The two-letter language code is followed by the name of the language,
and the name and e-mail address of the translation team leader. 
Translation Teams:

• ?? - This place is reserved for your name, when you form a translation team for another language.
• !! - Contact the Translations Coordinator at <address@hidden> if you would like to form a Translation Team and be listed as the translation team lead for your language.
• az - Azeri (Igrar  Huseynov <address@hidden>)
  
• bs - Bosnian 
• ca - Catalan (Alex Muntada <address@hidden>)
• cn - Simplified Chinese (Chao-Hong Liu <address@hidden>)
• zh - Traditional Chinese (Chao-Hong Liu <address@hidden>)
• cs - Czech
• de - German (Eckart Störmer Eckart Störmer)
• eo - Esperanto
• es - Spanish
• fr - French
• gl - Galician
• he - Hebrew (Ofer Waldman (a.k.a. the duke) <the_duke at intermail dot co dot il>, Hebrew translation team)
• hr - Croatian
• hu - Hungarian
• id - Indonesian (Rahmat M. Samik-Ibrahim,Indonesian translation team)
• it - Italian (Giorgio V. Felchero and Paola Blason <address@hidden>, Italian translation team)
• ja - Japanese (Masayuki Hatta <address@hidden>)
• ko - Korean
• nl - Dutch (Gerrit Rensink <address@hidden>)
• no - Norwegian
• pl - Polish (Wojciech Kotwica <address@hidden>)
• pt - Portuguese (Fernando Lozano <address@hidden>, Portuguese translation team)
• ro - Romanian
• ru - Russian (Dmitry Rutsky <balto AT bk DOT ru>)
• sl - Slovenian
• sr - Serbian
• sv - Swedish (Pål Brattberg <address@hidden>)
• tr - Turkish
• uk - Ukrainian (Evgenyi Sudyr <address@hidden>)
  

Note that

• en - English

is a special case. The bulk of the site is written in English, which is
the de-facto language of the GNU Project. We occasionally need original
documents written in other languages translated into English. If you
can
help with this, please contact <address@hidden>.

Final Notes

If you translate a page for www.gnu.org, please insert the following tag, in the <HEAD>...</HEAD> (or <head> for xhtml) section. Where address@hidden is the forwarding address for your translations team:

<link rev="translated" href-"mailto:address@hidden" />

---

[ English | Indonesian ]

Return to the GNU Project home page.

Please send FSF & GNU inquiries to address@hidden. There are also other ways to contact the FSF.
Please send broken links and other corrections (or suggestions) to address@hidden.

Please see the Translations README for information on coordinating and submitting translations of this article.

Copyright (C) 1999, 2004 Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA
Verbatim copying and distribution of this entire article is permitted worldwide without royalty in any medium provided this notice is preserved.

Updated: $Date: 2004/10/16 15:09:31 $ $Author: kamatp $