Translating Gramps - Revision history

Romjerome at 16:41, 4 May 2013

2013-05-04T16:41:27Z

Romjerome: /* Translating wiki manual */

2013-04-21T10:33:43Z

‎Translating wiki manual

Patsyblefebre: Gramps

2013-02-04T05:52:43Z

Gramps

Patsyblefebre: Patsyblefebre moved page Translating GRAMPS to Translating Gramps: lowercase

2013-01-17T08:13:59Z

Patsyblefebre moved page Translating GRAMPS to Translating Gramps: lowercase

Patsyblefebre: Gramps

2013-01-17T00:08:45Z

Gramps

Patsyblefebre: /* Getting started */ Translating the Gramps User manual

2012-12-30T01:04:08Z

‎Getting started: Translating the Gramps User manual

Romjerome: /* Translating man pages */

2012-12-13T11:26:18Z

‎Translating man pages

Romjerome: /* Translating man pages */

2012-12-13T11:25:45Z

‎Translating man pages

Romjerome: /* Translating man pages */

2012-12-13T11:11:55Z

‎Translating man pages

Romjerome: /* Installing your translation */

2012-11-16T06:25:29Z

‎Installing your translation

@@ Line 207: / Line 207: @@
 in the <code>po</code> directory. This assumes that you have already succesfully configured the source. Note, this command ignores <code>--no-wrap</code> option, so not practical for SVN diffs.
-{{man warn|Environment change|For trunk, see [[Translation_environment4|new environment]].}}
+{{man warn|Environment change|For gramps 4.0 and trunk, see [[Translation_environment4|new environment]].}}
 ===Testing your update===
@@ Line 232: / Line 232: @@
 ===Installing your translation===
-{{man warn|Environment change|For trunk, see [[Translation_environment4|new environment]].}}
+{{man warn|Environment change|For gramps 4.0 and trunk, see [[Translation_environment4|new environment]].}}
 You want to use the new translation immediately, and systemwide?
@@ Line 430: / Line 430: @@
 ==Translating man pages==
-{{man warn|Environment change|For trunk, see [[Translation_environment4#Translating_man_pages|new environment]].}}
+{{man warn|Environment change|For gramps 4.0 and trunk, see [[Translation_environment4#Translating_man_pages|new environment]].}}
 You can also translated the man pages into your own language.

@@ Line 506: / Line 506: @@
 Note that reports/tools link to a section in the page with the same name as the report name in Gramps.
-*You should be able to edit directly on wiki or using tools like [http://translate.sourceforge.net/wiki/toolkit/txt2po txt2po] or [http://po4a.alioth.debian.org/ po4a]. Also previous gettext file for the manual and [http://en.wikipedia.org/wiki/Translation_memory Translation Memory] may help you to upgrade deprecated/old gettext files.
+*You should be able to edit directly on wiki or using tools like [http://translate.sourceforge.net/wiki/toolkit/txt2po txt2po] or [http://po4a.alioth.debian.org/ po4a]. Also previous gettext file for the manual and [http://en.wikipedia.org/wiki/Translation_memory Translation Memory] may help you to upgrade deprecated/old gettext files. eg, store existing entries from ''/usr/share/locale''.
 ==Language specific pages==

← Older revision		Revision as of 05:52, 4 February 2013
Line 1:		Line 1:
−	{{languages\|Translating ~~GRAMPS~~}}	+	{{languages\|Translating Gramps}}

	Tips for translators of the Gramps program.		Tips for translators of the Gramps program.

@@ Line 1: / Line 1: @@
 {{languages|Translating GRAMPS}}
-Tips for translators of the GRAMPS program.
+Tips for translators of the Gramps program.
 The page [[Coding_for_translation|coding for translation]] may also be of interest to translators.
@@ Line 65: / Line 65: @@
 # If possible, try the translation before sending
-Translating GRAMPS into a new language means translating English strings used in the GRAMPS interface. To put it shortly, this amounts to
+Translating Gramps into a new language means translating English strings used in the Gramps interface. To put it shortly, this amounts to
 # obtaining the gramps.pot file with the strings to be translated,
 # translating the strings in the template, and
@@ Line 72: / Line 72: @@
 ===Obtaining gramps.pot===
-* Download <code>gramps.pot</code> from GRAMPS SVN repository, see [[Brief_introduction_to_SVN| the introduction to SVN]].
+* Download <code>gramps.pot</code> from Gramps SVN repository, see [[Brief_introduction_to_SVN| the introduction to SVN]].
 * Look for <code>gramps.pot</code> in the directory <code>gramps{{stable_branch}}/po</code> or if you looking for the trunk version look for <code>gramps.pot</code> in the directory <code>trunk/po</code>.
@@ Line 78: / Line 78: @@
 * Copy <code>gramps.pot</code> to the file named <code>lang.po</code>, according to the language you are translating into (<code>fr.po</code> for French, <code>ru.po</code> for Russian, etc.)
 * Use [http://gtranslator.sourceforge.net GTtranslator] (GNOME, windows), [http://i18n.kde.org/tools/ KBabel] (KDE), [http://userbase.kde.org/Lokalize Lokalize] (KDE, windows), Emacs po-mode, [http://translate.sourceforge.net/wiki/pootling/index pootling] (GNU/Linux, windows), [http://www.poedit.net/ poedit] (GNU/Linux, OSX, windows), or any similar tool designed for translating <code>.po</code> files. If you do not like any of these tools, you can use any text editor to translate messages. If using vim, properly setting the "langmap" option will significantly speed up your work.
-* Even though GRAMPS uses UNICODE (UTF-8) for its character set, you may use your native character set for your translation. Just make sure you specify the character set you are using in the <code>Content-Type</code> line in the <code>.po</code> file. GRAMPS will handle the conversion to UNICODE.
+* Even though GRAMPS uses UNICODE (UTF-8) for its character set, you may use your native character set for your translation. Just make sure you specify the character set you are using in the <code>Content-Type</code> line in the <code>.po</code> file. Gramps will handle the conversion to UNICODE.
 * If there are non ASCII characters in the original English string, try to preserve them by copying them, if applicable.
 ===Context===
-As an extension to standard gettext, strings in GRAMPS can have a context prefix. This prefix should '''not''' be translated, and just be deleted in the translation. More info and an example [[#Translation context|further down]].
+As an extension to standard gettext, strings in Gramps can have a context prefix. This prefix should '''not''' be translated, and just be deleted in the translation. More info and an example [[#Translation context|further down]].
 As a special context, you will see the manual context, eg :
@@ Line 186: / Line 186: @@
 ===Updating your translation===
-If you have submitted a translation, it may well be that after some weeks/months, new strings are added to GRAMPS, implying you need to update your translation file.
+If you have submitted a translation, it may well be that after some weeks/months, new strings are added to Gramps, implying you need to update your translation file.
-Assuming you have obtained originally the GRAMPS source tree as explained in [[Brief introduction to SVN]]. Now:
+Assuming you have obtained originally the Gramps source tree as explained in [[Brief introduction to SVN]]. Now:
-* Update your gramps tree from SVN. This can be done by executing the command <pre>svn up</pre> from the root GRAMPS svn directory. This will download an updated <code>gramps.pot</code> file.
+* Update your gramps tree from SVN. This can be done by executing the command <pre>svn up</pre> from the root Gramps svn directory. This will download an updated <code>gramps.pot</code> file.
 * Use your outdated translation to translate the strings that did not change:<pre>msgmerge lang.po gramps.pot -o newlang.po</pre> or <pre>msgmerge --no-wrap lang.po gramps.pot -o newlang.po</pre> where <code>lang</code> is your language code.  The <code>--no-wrap</code> option will prevent changes due to automatic word wrapping, use it if your previous po file was constructed like that.  The <code>--no-wrap</code> options allows for more readable SVN diffs.
 * Check fuzzy messages and translate all untranslated messages in <code>newlang.po</code>. When you are sure everything is right, rename <code>newlang.po</code> as <code>lang.po</code> and check it into SVN as you did with the original file.
@@ Line 243: / Line 243: @@
 This should install your translations to ''/usr/share/locale/{lang}/LC_MESSAGES/gramps.mo'', with {lang} being your language. You could of course copy your files manually to that dir with the gramps.mo name.
-Make sure you only install from within the po directory, or you will install the development version of GRAMPS, which is not supported and for testing only!
+Make sure you only install from within the po directory, or you will install the development version of Gramps, which is not supported and for testing only!
 ==== Running trunk with your translation ====
@@ Line 267: / Line 267: @@
 ===== $GRAMPSI18N (for your locale) =====
-Actually you don't even need to install the files in order to test them. This is useful because you can develop GRAMPS without needing superuser privileges. Bear in mind the GRAMPS i18n process goes something like this when you use trunk:
+Actually you don't even need to install the files in order to test them. This is useful because you can develop Gramps without needing superuser privileges. Bear in mind the Gramps i18n process goes something like this when you use trunk:
 * when you type <code>python build</code> in the source tree root (/home/user/trunk e.g.) all the trunk/po/*.po files are compiled into trunk/build/mo/{lang}/*.mo files.
 * when you type <code>python install</code> inside the /home/user/trunk/po directory, these .mo files are copied to {prefix}/share/locale/{lang}/LC_MESSAGES as gramps.mo files.
-But you can change the place where GRAMPS looks for these files by altering the environment variable $GRAMPSI18N. So you could also for instance do something like this and avoid the <code>python setup install</code> step: (if you are using csh or tcsh the syntax would be a little different)
+But you can change the place where Gramps looks for these files by altering the environment variable $GRAMPSI18N. So you could also for instance do something like this and avoid the <code>python setup install</code> step: (if you are using csh or tcsh the syntax would be a little different)
    [user@localhost /home/user/trunk]$ mkdir -p po/en_GB/LC_MESSAGES
@@ Line 489: / Line 489: @@
 ==Translating wiki manual==
-To have the link working in GRAMPS, you need to have or edit the GrampsDisplay.py file to contain your language.
+To have the link working in Gramps, you need to have or edit the GrampsDisplay.py file to contain your language.
 On line 30 of that file, you see:
@@ Line 504: / Line 504: @@
 *Every 'manual|...' entry in the gramp.pot file refers to a section in the manual, so make sure to use good section headings so this does not change too much over time.
-Note that reports/tools link to a section in the page with the same name as the report name in GRAMPS.
+Note that reports/tools link to a section in the page with the same name as the report name in Gramps.
 *You should be able to edit directly on wiki or using tools like [http://translate.sourceforge.net/wiki/toolkit/txt2po txt2po] or [http://po4a.alioth.debian.org/ po4a]. Also previous gettext file for the manual and [http://en.wikipedia.org/wiki/Translation_memory Translation Memory] may help you to upgrade deprecated/old gettext files.
@@ Line 517: / Line 517: @@
 ==Translating addon plugins==
-* See [[Addons_development#Get_translators_to_translate_your_addon_into_multiple_languages|3rd-party addon for GRAMPS]].
+* See [[Addons_development#Get_translators_to_translate_your_addon_into_multiple_languages|3rd-party addon for Gramps]].

@@ Line 69: / Line 69: @@
 # translating the strings in the template, and
 # getting the translated file uploaded into gramps SVN repository.
-Another avenue of translation is translating the documentation. This is a different and lengthy process and it is decribed in our [[Translating the manual]] page. Here we will concentrate on the interface translation only.
+Another avenue of translation is translating the documentation. This is a different and lengthy process and it is decribed in our [[Translating the Gramps User manual]] page. Here we will concentrate on the interface translation only.
 ===Obtaining gramps.pot===

@@ Line 430: / Line 430: @@
 ==Translating man pages==
-{{man warn|Environment change|For trunk, see [[Translation_environment4|new environment]].}}
+{{man warn|Environment change|For trunk, see [[Translation_environment4|new environment#Translating_man_pages]].}}
 You can also translated the man pages into your own language.
@@ Line 469: / Line 469: @@
 You could also in the config file of subversion ( HOMEDIR/.subversion/config) enable the auto-prop feature (enable-auto-props = yes) and uncomment the relevant lines in the [auto-props] section.
-All changes must be committed and do not forget to change the ChangeLog file.
+All changes must be committed.
 You should see no errors when you run the <code>

← Older revision		Revision as of 11:11, 13 December 2012
Line 429:		Line 429:

	==Translating man pages==		==Translating man pages==
		+
		+	{{man warn\|Environment change\|For trunk, see [[Translation_environment4\|new environment]].}}
		+
	You can also translated the man pages into your own language.		You can also translated the man pages into your own language.

@@ Line 241: / Line 241: @@
   make --prefix=/usr install     #as root !
-This should install your translations to <code>/usr/share/locale/xx/LC_MESSAGES/gramps.mo</code>, with xx being your language. You could of course copy your files manually to that dir with the gramps.mo name.
+This should install your translations to ''/usr/share/locale/{lang}/LC_MESSAGES/gramps.mo'', with {lang} being your language. You could of course copy your files manually to that dir with the gramps.mo name.
 Make sure you only install from within the po directory, or you will install the development version of GRAMPS, which is not supported and for testing only!