Howto:Change the language of reports - Revision history

Patsyblefebre: Gramps

2013-01-23T22:57:21Z

Gramps

Patsyblefebre: /* Run Gramps in a different language */ Gramps

2013-01-20T01:20:39Z

‎Run Gramps in a different language: Gramps

Patsyblefebre: Gramps

2013-01-20T01:18:37Z

Gramps

Bmcage: /* Run GRAMPS in a different language */

2012-12-31T15:14:22Z

‎Run GRAMPS in a different language

Bmcage: /* Run GRAMPS in a different language */

2012-12-31T15:13:53Z

‎Run GRAMPS in a different language

Bmcage: /* Run GRAMPS in a different language */

2012-12-31T15:12:30Z

‎Run GRAMPS in a different language

Bmcage: /* Run GRAMPS in a different language */

2012-12-31T15:11:52Z

‎Run GRAMPS in a different language

BACbKA: XML version

2012-04-06T13:02:48Z

XML version

Daleathan: /* Automatically translate names and places */

2011-11-03T02:47:48Z

‎Automatically translate names and places

Daleathan at 02:44, 3 November 2011

2011-11-03T02:44:31Z

@@ Line 6: / Line 6: @@
 If you have an international family, chances are you want to produce reports in the language used by your distant family members.
-Gramps is supported in [[GRAMPS_translations|many languages]]. You can produce reports in all these languages, by running Gramps in this language and making the report.
+Gramps is supported in [[Gramps_translations|many languages]]. You can produce reports in all these languages, by running Gramps in this language and making the report.
 == Run Gramps in a different language==
@@ Line 153: / Line 153: @@
   	$(GUNZIP) < $< | $(XSLT) --stringparam living '[LIVING]' $(TRANSLATEXSL) - | $(GZIP) > $@
 * Create a new database in gramps, and import the resulting en.Smith.gramps into it. Review the database, and now produce, using the language translated into, all the reports, export into GEDCOM, etc.
-* GRAMPS XML version is hardcoded in the XSL -- make sure it matches yours. "zcat *.gramps|head" will give you the GRAMPS XML format version used in that GRAMPS file. The script works has been tested either 1.3.0 (Gramps v3.2) or 1.4.0 GRAMPS XML (Gramps v3.3).
+* GRAMPS XML version is hardcoded in the XSL -- make sure it matches yours. "zcat *.gramps|head" will give you the GRAMPS XML format version used in that Gramps file. The script works has been tested either 1.3.0 (Gramps v3.2) or 1.4.0 GRAMPS XML (Gramps v3.3).
 [[Category:Tutorials|Change the language of reports]]
 [[Category:Documentation]]
 [[Category:Translators/Categories]]

@@ Line 12: / Line 12: @@
 First, let us learn how to run gramps from a terminal or console (the so called CLI-Command Line Interface, which you find typically in the System Menu of your task bar).
-This can be done by typing <code>gramps</code>, as GRAMPS typically is installed in the directory <code>/usr/bin</code>. You can also start Gramps with <code>/usr/bin/gramps</code>, although this might be different on other distributions.
+This can be done by typing <code>gramps</code>, as Gramps typically is installed in the directory <code>/usr/bin</code>. You can also start Gramps with <code>/usr/bin/gramps</code>, although this might be different on other distributions.
 This command calls up Gramps with the default locale setting of your PC, that is, the language in which you installed your linux OS. If other locales are installed on your system, calling up Gramps in this language can be done. To check if there are other installed locales, use:

@@ Line 6: / Line 6: @@
 If you have an international family, chances are you want to produce reports in the language used by your distant family members.
-GRAMPS is supported in [[GRAMPS_translations|many languages]]. You can produce reports in all these languages, by running GRAMPS in this language and making the report.
+Gramps is supported in [[GRAMPS_translations|many languages]]. You can produce reports in all these languages, by running Gramps in this language and making the report.
-== Run GRAMPS in a different language==
+== Run Gramps in a different language==
 First, let us learn how to run gramps from a terminal or console (the so called CLI-Command Line Interface, which you find typically in the System Menu of your task bar).
-This can be done by typing <code>gramps</code>, as GRAMPS typically is installed in the directory <code>/usr/bin</code>. You can also start GRAMPS with <code>/usr/bin/gramps</code>, although this might be different on other distributions.
+This can be done by typing <code>gramps</code>, as GRAMPS typically is installed in the directory <code>/usr/bin</code>. You can also start Gramps with <code>/usr/bin/gramps</code>, although this might be different on other distributions.
-This command calls up GRAMPS with the default locale setting of your PC, that is, the language in which you installed your linux OS. If other locales are installed on your system, calling up GRAMPS in this language can be done. To check if there are other installed locales, use:
+This command calls up Gramps with the default locale setting of your PC, that is, the language in which you installed your linux OS. If other locales are installed on your system, calling up Gramps in this language can be done. To check if there are other installed locales, use:
   locale -a
@@ Line 39: / Line 39: @@
 ===Add KDE Menu Item===
-[[Image:gramps_locale_add_kde_menu_item.png|800px|Add locale GRAMPS KDE menu item]]
+[[Image:gramps_locale_add_kde_menu_item.png|800px|Add locale Gramps KDE menu item]]
 *Right Click on <code>'K'</code> -> select <code>'Menu Editor'</code>
 *Click on <code>'Office'</code>
-*Click on <code>'New Item', Enter <code>'GRAMPS Genealogy System (nl)'</code>
+*Click on <code>'New Item', Enter <code>'Gramps Genealogy System (nl)'</code>
 In each of the fields enter:
-*Description: <code>GRAMPS NL Locale</code>
+*Description: <code>Gramps NL Locale</code>
 *Comment: <code>Manage genealogical information, perform genealogical research and analysis</code>
 *Command: <code>LANG=nl_BE.UTF-8; /usr/bin/gramps</code>
 Change LANG to whatever you wanted as described in the previous section.
-Leave all other options as default.  To add the GRAMPS icon, click on the icon beside Name and Description fields
+Leave all other options as default.  To add the Gramps icon, click on the icon beside Name and Description fields
 *Select <code>'Other icons'</code> -> Click on <code>'Browse'</code>
@@ Line 60: / Line 60: @@
 In the KDE Menu Editor select <code>'Save'</code> and close the window.
-To Launch the locale version of GRAMPS click on K->APPLICATIONS -> OFFICE -> GRAMPS NL Locale
+To Launch the locale version of Gramps click on K->APPLICATIONS -> OFFICE -> Gramps NL Locale
@@ Line 86: / Line 86: @@
 ==What about dates and calendars==
-Dates and calendars depend on your locale,<!-- not your language setting. So here the variable of importance is locale.CODESET, so the locale must be installed and be the default. --> so changing the LANG variable will run GRAMPS with the date and calendar appropriate to the locale (if implemented).
+Dates and calendars depend on your locale,<!-- not your language setting. So here the variable of importance is locale.CODESET, so the locale must be installed and be the default. --> so changing the LANG variable will run Gramps with the date and calendar appropriate to the locale (if implemented).
 ==How to install a locale==
@@ Line 111: / Line 111: @@
 == Run the report==
-Having started GRAMPS in another language, all reports you make will also be in this language. Of course, things you typed in yourself are not translated.
+Having started Gramps in another language, all reports you make will also be in this language. Of course, things you typed in yourself are not translated.
 ===Tips for international use===
@@ Line 117: / Line 117: @@
 * for places: use the actual placename, for example München and not Munich. You could add an alternate location to the place with the translated name. (Or wait until the [[GEPS_006:_Better_Place_handling|better place handling]] feature is fully implemented and available).
 * for notes: use the languages the people who are most interested in this section will want it in. This version enables multiple notes, so you are able to make different notes, one per language, with the possibility to use filters to determine what appears
-* for descriptions: Try to use built-in description names as much as possible, as those are translated. Eg, try to avoid custom events, and use the builtin events of GRAMPS as much as possible.
+* for descriptions: Try to use built-in description names as much as possible, as those are translated. Eg, try to avoid custom events, and use the builtin events of Gramps as much as possible.
 ===Automatically translate names and places===
-From Gramps version 3.2, GRAMPS doesn't support language tagging of alternative names --- whether for a person or a location. That is, you can add multiple alternative names, each in a different language, but still only one of them will be the primary one --- and will be the one picked up for a report. Nevertheless, when exporting to a relative not speaking your language, or when preparing a report for a part of your family having different language preferences than yourself, you need to change the primary language, but only in a temporary manner --- so that you still continue maintaining your own DB in your preferred language.
+From Gramps version 3.2, Gramps doesn't support language tagging of alternative names --- whether for a person or a location. That is, you can add multiple alternative names, each in a different language, but still only one of them will be the primary one --- and will be the one picked up for a report. Nevertheless, when exporting to a relative not speaking your language, or when preparing a report for a part of your family having different language preferences than yourself, you need to change the primary language, but only in a temporary manner --- so that you still continue maintaining your own DB in your preferred language.
-Luckily, the simplicity of the GRAMPS XML format allows the use of a small XSL stylesheet, fed by a local translation table of the names you want translated, which you can use for this purpose. Here's how you can easily do it on Linux:
+Luckily, the simplicity of the Gramps XML format allows the use of a small XSL stylesheet, fed by a local translation table of the names you want translated, which you can use for this purpose. Here's how you can easily do it on Linux:
 * Ensure your administrator installs the "xsltproc" package.
-* Export your GRAMPS DB (without media) in the .gramps format (i.e., GZipped GRAMPS XML). Save it (let's call it Smith.gramps). Ensure you enable the required censorship on the database (such as restrict the data on living people, etc.)
+* Export your Gramps DB (without media) in the .gramps format (i.e., GZipped GRAMPS XML). Save it (let's call it Smith.gramps). Ensure you enable the required censorship on the database (such as restrict the data on living people, etc.)
 * Store the translation XSL ([http://www.tarunz.org/~vassilii/pub/gramps-translate/gramps-translate.xsl gramps-translate-names.xsl]) near the Smith.gramps. Look at the XSL source for advanced parameters allowing you to customize the translation.
 * Create the translation dictionary ([http://www.tarunz.org/~vassilii/pub/gramps-translate/t.xml t.xml]) near it as well:

@@ Line 18: / Line 18: @@
 For example, if the locale ''nl_BE'' is installed with encoding ''nl_BE.UTF-8'', you can start it with:
-  LANG=nl_BE.UTF-8
+  LANG=nl_BE.UTF-8 /usr/bin/gramps
- /usr/bin/gramps
 Once you get the locale working and to make things handy going forward, you can create an alias.  Open the file <code>.bashrc</code> (this file is located in your home directory) in a text editor.  At the bottom of the file add the following:

@@ Line 29: / Line 29: @@
 If you want to run Gramps in a locale you did not install, things will only work partially. You first need to set a fallback which is installed, or Gramps will never start. For example, if you have nl_BE.UTF-8 installed, and want to run in Swedish, you can do:
-  LC_ALL=C.UTF-8 LANG="sv" python3 gramps
+  LC_ALL=nl_BE.UTF-8 LANG="sv" python3 gramps
-This assumes the Gramps translations are installed globally. If this is not the case, you need to give Gramps the directory where the translations will be found. A translation is called ''gramps.mo'', you can find it in linux with the ''locate'' command. For example, if you have Swedish in directory /home/me/gramps/mo/sv/gramps.mo, you can direct Gramps there using:
+Gramps '''requires''' an UTF-8 locale to work correctly in most cases.
   GRAMPSI18N=/home/me/gramps/mo LC_ALL=C.UTF-8 LANG="sv" python3 gramps

@@ Line 9: / Line 9: @@
 == Run GRAMPS in a different language==
-=== Version 4.0+ ===
 First, let us learn how to run gramps from a terminal or console (the so called CLI-Command Line Interface, which you find typically in the System Menu of your task bar).
@@ Line 35: / Line 35: @@
 Alternatively you can add a new item to the menu of GNOME or KDE, so this command needs not to be entered in a terminal, but can be called from the menu.
 ===Add KDE Menu Item===

@@ Line 1: / Line 1: @@
 {{languages|Howto:_Change_the_language_of_reports}}
-This howto explains how you can produce reports in a language different from the language you installed your operating system in.
+Explanation of how you can produce reports in a language different from the language you installed your operating system in.
 ==Introduction==
 If you have an international family, chances are you want to produce reports in the language used by your distant family members.
@@ Line 8: / Line 9: @@
 == Run GRAMPS in a different language==
 First, let us learn how to run gramps from a terminal or console (the so called CLI-Command Line Interface, which you find typically in the System Menu of your task bar).