BrowseAtWork.com:   [ UP ]   [Manage cookies]

Guide to Translating www.gnu.org Web Pages

Most important: Do NOT translate the raw HTML source.

If you want to submit a translation or help translation efforts, please contact the relevant existing team below. If there is no team established for your language, please write to <web-translators@gnu.org> after reading the manuals.

[image of the typing GNU]

General Guide

  • Before doing anything, please read
  • 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 <web-translators@gnu.org>, and ask if you can start a new team for your language.

Language Codes

  • ISO 639 gives the two-letter language codes in its 2nd column. If a two-letter language code is not assigned, 3-letter (ISO 639-2) can be used. 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).

Translating the home page

  • The translated homepage must include the full list of translations via SSI.
    The required SSI tag looks like this: 
                <!--#include file="translations.include" -->
  • If you provide a new home page translation you must update the translations.include file. The file is stored in the GNU webservers root directory.

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 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

Keeping Translations Current

  • For all translations to be kept current, you should subscribe to the www-commits mailing list. 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. You may also use make report TEAM=LANG if you have GNUN installed.

Translations Underway

The language code is followed by the name of the language, and the name and e-mail address of the translation team leader.

Translation Teams:

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. It is best to notify the team leader of your language that you volunteer, because we always contact them first. If there is no team and you are willing to help with this, please contact <web-translators@gnu.org>.

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 web-translators-es@gnu.org is the forwarding address for your translations team: 
  <link rev="translated" href="mailto:web-translators-es@gnu.org" />

Check out other Free Software Foundation campaigns

Translations of this page