Difference between revisions of "Gramps:Language policy"

From Gramps
Jump to: navigation, search
m (Protected "GRAMPS:Language policy": language policy [edit=sysop:move=sysop])
Line 32: Line 32:
 
==More Info==
 
==More Info==
 
For more info, see the documentation in [[Template:Languages]],  [[Template:Call lang]].
 
For more info, see the documentation in [[Template:Languages]],  [[Template:Call lang]].
 +
 +
 +
==Examples==
 +
* Compare [[GRAMPS:About]] and [[Nl:GRAMPS:Info]] which uses redirect to a different pagename.
 +
* Compare [[Template:Main_page/genealogy_links]] and [[Template:Main_page/genealogy_links/nl]] which uses the call_lang template to do fallback to english language on non-translated pages.

Revision as of 18:01, 4 March 2007

This page describes the current multi-lingual policy on GRAMPS wiki.

Which Languages?

In theory, all languages for which a person can be found to maintain the translation, can have the GRAMPS main page translated. You can then translate articles on a opt-in basis. Are supported today:

Dutch
Maintainer: B. Malengier. Contact him by mailing bm AT the domain cage dot ugent dot be, or via the devel mailing list.

The languages supported need to be added to Template:Languages and GRAMPS:Main_page_templates/page by a system administrator

The task of a maintainer is to translate the Main page via GRAMPS:Main_page_templates as well as the main portals. He also has to respond to user questions about the language, and investigate misuse in his language (profanities, flame-wars, ...)

What NOT to translate

It is actually very easy, you only need to know the original language (English) and be able to copy/paste with perhaps the extra complication of using a template for links instead of normal wiki links.

In details:

  1. The developers section is english only. Development of GRAMPS is in english.
  2. Mark-up Templates. Templates for markup, eg pretty tables, boxes, should be written language independent, with if necessary a language parameter which is passed to content specific templates that can be translated.

Note that Content templates can be translated, but do not include the {{languages|pagename}} template to the content. Instead, add it to the noinclude section of the template:

<noinclude>{{languages|pagename}}</noinclude>

How?

  1. If you want to translate page [[GRAMPS:Language policy]] in a language with language code zz, you create a page [[GRAMPS:Language policy/zz]]. The root name af the article must be the english name. So e.g. Bonjour would be Goodday/fr. However you can use redirection to give French users a fr:Bonjour page
  2. Next, you add at the bottom of the page the template {{languages|GRAMPS:Language policy}}. This same template must be added to the root page as well as all translated pages.
  3. In the case no english page exists for the page you want to make, first add an english page with content
    {{stub}}{{languages|pagename}}
  4. You can redirect people to a page with localized title. This is helpfull for searching pages in non-english, or for inclusion of the pages in Help:Categories. Eg, you want to translate [[GRAMPS:About]] in Dutch.
    1. You make the page [[GRAMPS:About/nl]] with content:
      #REDIRECT [[nl:GRAMPS:Info]]
    2. In the page [[GRAMPS:About]], you add at the bottom
      {{languages}}
    3. You create the page nl:GRAMPS:Info, with as content the translated English page, and at the bottom you call the languages script, with as first parameter the english root page, and second parameter the true dutch name:
      {{languages|GRAMPS:About|GRAMPS:Info}}
    4. If you want to link to translated pages, you can use the standard wiki syntax: [[link here/nl|text]], but this is off course only possible if the nl page already exists. You can also use the following handy template: Template:Call_lang, which works as
      {{call_lang|link here|nl|text}}
      If the required translation exists, it is returned, otherwise the english root page is returned

Note: It actually suffices in the English page to add {{languages}}. If the translated page does not make use of redirects, that also suffices in the translated page. However, when using redirect, you must add as parameter the correct english pagename. Therefore, it is better to just always add it, so you never forget.

More Info

For more info, see the documentation in Template:Languages, Template:Call lang.


Examples