Translating the Gramps User manual - Revision history

Patsyblefebre: /* Screenshots */ 40

2013-02-13T03:31:21Z

‎Screenshots: 40

Patsyblefebre: Gramps

2013-01-26T00:12:38Z

Gramps

Romjerome: /* Screenshots */

2013-01-03T11:04:14Z

‎Screenshots

Patsyblefebre: /* Getting started */ User manual

2012-12-30T01:26:22Z

‎Getting started: User manual

Patsyblefebre: /* Getting started */ update instructions

2012-12-30T01:25:58Z

‎Getting started: update instructions

Patsyblefebre: Patsyblefebre moved page Translating the manual to Translating the Gramps User manual: more meaning full title

2012-12-30T00:53:57Z

Patsyblefebre moved page Translating the manual to Translating the Gramps User manual: more meaning full title

Patsyblefebre: User manual

2012-12-30T00:53:03Z

User manual

Patsyblefebre: /* Links to wiki manual */ update samples

2012-12-29T23:53:33Z

‎Links to wiki manual: update samples

Patsyblefebre: /* Links to wiki manual */ old link gone moved to http://svn.code.sf.net/p/gramps/code/trunk/gramps/gui/display.py

2012-12-29T23:52:03Z

‎Links to wiki manual: old link gone moved to http://svn.code.sf.net/p/gramps/code/trunk/gramps/gui/display.py

Patsyblefebre: /* Screenshots */ Screenshots

2012-12-29T23:25:52Z

‎Screenshots: Screenshots

@@ Line 17: / Line 17: @@
 ** If it's too much trouble for you, just let us know and perhaps somebody else will do it for you. Fortunately, one does not have to speak the language to make screenshots :-)
 ** For maintenance, it could be more easy to follow a naming scheme :
-*** filename-''{gramps version number}-{locale}''.png <pre>Mainwin-33-fr.png</pre>
+*** filename-''{gramps version number}-{locale}''.png <pre>Mainwin-40-fr.png</pre>
-*** filename_''{gramps version number}_{locale}''.png <pre>Mainwin_33_fr.png</pre>
+*** filename_''{gramps version number}_{locale}''.png <pre>Mainwin_40_fr.png</pre>
 *[[Screenshots]]

@@ Line 1: / Line 1: @@
 {{languages}}
-An explanation of how you can translate the [[User manual|GRAMPS User manual]]. This manual is also available from within GRAMPS using the {{man key press|F1}} key (which opens this manual in a browser window), or from the help menu.
+An explanation of how you can translate the [[User manual|Gramps User manual]]. This manual is also available from within Gramps using the {{man key press|F1}} key (which opens this manual in a browser window), or from the help menu.
 ==Getting started==
-Translating GRAMPS' documentation into a new language is a long, tedious, and boring process, just like with any complex text :-)
+Translating Gramps' documentation into a new language is a long, tedious, and boring process, just like with any complex text :-)
-Since GRAMPS version 3.0 the documentation was moved completely to this wiki. So for translation you don't need to use or even install any fancy applications to help us. You can use your browser and start immediately. Just go to the [[User manual]] page, select the current manual and then click on your language. You should could keep the english manual open to check if there is a help page missing.
+Since Gramps version 3.0 the documentation was moved completely to this wiki. So for translation you don't need to use or even install any fancy applications to help us. You can use your browser and start immediately. Just go to the [[User manual]] page, select the current manual and then click on your language. You should could keep the english manual open to check if there is a help page missing.
 The general [[Help:Contents|wiki help page]] will help you editing wiki pages. This wiki uses the [http://www.mediawiki.org/ MediaWiki] software, which is the same that is used by [http://en.wikipedia.org/wiki/Wikipedia Wikipedia], so it could feel familiar.
@@ Line 24: / Line 24: @@
 ==Links to wiki manual==
-To have your recently translated manual available from within GRAMPS. You need to activate the manual by editing the following file: '''[http://svn.code.sf.net/p/gramps/code/trunk/gramps/gui/display.py display.py]''' to contain your language code, you may also contact the developers of Gramps by opening a ''Feature request'' for the new language on the [[Using_the_bug_tracker |Bug tracker]].
+To have your recently translated manual available from within Gramps. You need to activate the manual by editing the following file: '''[http://svn.code.sf.net/p/gramps/code/trunk/gramps/gui/display.py display.py]''' to contain your language code, you may also contact the developers of Gramps by opening a ''Feature request'' for the new language on the [[Using_the_bug_tracker |Bug tracker]].
 On line 32 of that file, you see:
@@ Line 45: / Line 45: @@
 *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#mediawiki txt2po].

@@ Line 14: / Line 14: @@
 * Figures: localized screenshots are nice in the localized manual
 ** If you can provide figures on your own this is great. Upload them to this wiki with the following naming convention: <code>figure_name_zz.png</code> (<code>zz</code> is your language code). If the figure is language independent just call it <code>figure_name.png</code>.
-** A command to take screenshots that works for me, is by using imagemagick (should be installed with every linux distribution, if not, get it): <pre>import -quality 100 -trim -delay 200 -resize 500 -density 100x100 -frame -channel RGB -depth 8 screenshot.png </pre>This creates a fully compressed (<code>-quality 100), timed screenshot after 2 seconds (<code>-delay 200</code>) of size 500 pixels wide (<code>-resize 500</code>), with resolution 100 (<code>-density 100x100</code>), with the window frame attached (<code>-frame</code>) in RGB mode (<code>-channel RGB</code>) and bbp 24 (<code>-depth 8</code>). This creates images of 5 inches wide, which fit nicely on a book page, as well as on a HTML page.
+** A command to take screenshots that works for me, is by using imagemagick (should be installed with every linux distribution, if not, get it): <pre>import -quality 100 -trim -delay 200 -resize 500 -density 100x100 -frame -channel RGB -depth 8 screenshot.png </pre>This creates a fully compressed (<code>-quality 100</code>), timed screenshot after 2 seconds (<code>-delay 200</code>) of size 500 pixels wide (<code>-resize 500</code>), with resolution 100 (<code>-density 100x100</code>), with the window frame attached (<code>-frame</code>) in RGB mode (<code>-channel RGB</code>) and bbp 24 (<code>-depth 8</code>). This creates images of 5 inches wide, which fit nicely on a book page, as well as on a HTML page.
 ** If it's too much trouble for you, just let us know and perhaps somebody else will do it for you. Fortunately, one does not have to speak the language to make screenshots :-)
 ** For maintenance, it could be more easy to follow a naming scheme :

@@ Line 6: / Line 6: @@
 Translating GRAMPS' documentation into a new language is a long, tedious, and boring process, just like with any complex text :-)
-Since GRAMPS version 3.0 the documentation was moved completely to this wiki. So for translation you don't need to use or even install any fancy applications to help us. You can use your browser and start immediately. Just go to the [[User Manual]] page, select the current manual and then click on your language. You should could keep the english manual open to check if there is a help page missing.
+Since GRAMPS version 3.0 the documentation was moved completely to this wiki. So for translation you don't need to use or even install any fancy applications to help us. You can use your browser and start immediately. Just go to the [[User manual]] page, select the current manual and then click on your language. You should could keep the english manual open to check if there is a help page missing.
 The general [[Help:Contents|wiki help page]] will help you editing wiki pages. This wiki uses the [http://www.mediawiki.org/ MediaWiki] software, which is the same that is used by [http://en.wikipedia.org/wiki/Wikipedia Wikipedia], so it could feel familiar.

@@ Line 6: / Line 6: @@
 Translating GRAMPS' documentation into a new language is a long, tedious, and boring process, just like with any complex text :-)
-Since GRAMPS version 3.0 the documentation was moved completely to this wiki. So for translation you don't need to use or even install any fancy applications to help us. You can use your browser and start immediately. Just go to the [[Gramps 3.3 Wiki Manual|User Manual]] page, click on your language. You should could keep the english manual open to check if there is a help page missing.
+Since GRAMPS version 3.0 the documentation was moved completely to this wiki. So for translation you don't need to use or even install any fancy applications to help us. You can use your browser and start immediately. Just go to the [[User Manual]] page, select the current manual and then click on your language. You should could keep the english manual open to check if there is a help page missing.
 The general [[Help:Contents|wiki help page]] will help you editing wiki pages. This wiki uses the [http://www.mediawiki.org/ MediaWiki] software, which is the same that is used by [http://en.wikipedia.org/wiki/Wikipedia Wikipedia], so it could feel familiar.

@@ Line 28: / Line 28: @@
 On line 32 of that file, you see:
- MANUALS = {
+<pre>
      'nl' : '/nl',
-−
+}
 This maps a language code to the extension used on the wiki, so to add french, change this to:
- MANUALS = {
+<pre>
      'nl' : '/nl',
-     'fr':  '/fr',
+     'fr' : '/fr',
-−
+}
 *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.