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

+

The languages supported need to be added to [[Template:Languages]], [[Template:Languages/table]] 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 the Maintainer should translate==

+

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

+

The list of pages which group translation strings and must be translated:

−

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.

+

*[[GRAMPS:Main_page_templates]]: Translation of text strings on the main page

*[[GRAMPS:Community_templates]]: Translation of the Gramps community portal

+

*[[GRAMPS:Side_bar_translation]]: Translation of the text strings of the sidebar. '''Note''': although the sidebar will be translated, it will link to the english root page. This is a technical limitation of the sidebar!

+

List of pages you should definitely consider to translate:

+

*[[GRAMPS:About]]: The about box

+

*[[Installation]]: How to install Gramps

+

*[[Contact]]: How to contact Gramps

+

+

==What NOT to translate==

In details:

In details:

−

#The developers section is english only. Development of GRAMPS is in english.

+

#The developers section is english only. Development of Gramps is in english.

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

#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 <nowiki>{{languages|pagename}}</nowiki> template to the content. Instead, add it to the noinclude section of the template: <pre><nowiki><noinclude>{{languages|pagename}}</noinclude></nowiki></pre>

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

+

+

==What Users can translate==

+

Anything they like of the articles. Do follow the guidelines in the next section, How?, though.

+

+

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.

+

==How?==

==How?==

Line 25:

Line 54:

## You make the page <nowiki>[[GRAMPS:About/nl]]</nowiki> with content: <pre>#REDIRECT [[nl:GRAMPS:Info]]</pre>

## You make the page <nowiki>[[GRAMPS:About/nl]]</nowiki> with content: <pre>#REDIRECT [[nl:GRAMPS:Info]]</pre>

## In the page <nowiki>[[GRAMPS:About]]</nowiki>, you add at the bottom <pre>{{languages}}</pre>

## In the page <nowiki>[[GRAMPS:About]]</nowiki>, you add at the bottom <pre>{{languages}}</pre>

−

## 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: <pre>{{languages|GRAMPS:About|GRAMPS:Info}}</pre>

+

## 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: <pre>{{languages|GRAMPS:About|GRAMPS:Info}}</pre>

## If you want to link to translated pages, you can use the standard wiki syntax: <nowiki>[[link here/nl|text]]</nowiki>, 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 <pre>{{call_lang|link here|nl|text}}</pre> If the required translation exists, it is returned, otherwise the english root page is returned

## If you want to link to translated pages, you can use the standard wiki syntax: <nowiki>[[link here/nl|text]]</nowiki>, 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 <pre>{{call_lang|link here|nl|text}}</pre> If the required translation exists, it is returned, otherwise the english root page is returned

Line 32:

Line 61:

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

What the Maintainer should translate

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, ...).

The list of pages which group translation strings and must be translated:

GRAMPS:Side_bar_translation: Translation of the text strings of the sidebar. Note: although the sidebar will be translated, it will link to the english root page. This is a technical limitation of the sidebar!

What NOT to translate

In details:

The developers section is english only. Development of Gramps is in english.

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>

What Users can translate

Anything they like of the articles. Do follow the guidelines in the next section, How?, though.

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.

How?

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

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.

In the case no english page exists for the page you want to make, first add an english page with content

{{stub}}{{languages|pagename}}

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.

You make the page [[GRAMPS:About/nl]] with content:

#REDIRECT [[nl:GRAMPS:Info]]

In the page [[GRAMPS:About]], you add at the bottom

{{languages}}

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

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.