Like with [[Translation_environment22#Files_and_directory|previous environment]], we need to list files with translation strings for retrieving messages and generating a 'po/gramps.pot' file.

+

Like with [[Translation_environment22#Files_and_directory|previous environment]], we need to list files with translation strings for retrieving messages and generating a 'po/gramps.pot' file. Process is now only using ''gettext'' and ''python''.

−

* gettext, intltool and 'POTFILES.in' file

+

* gettext, 'POTFILES.in' and 'POTFILES.skip' files

If you want a script to take your translatable strings into account, you must add your source file path in the file : <code>po/POTFILES.in</code>. For this report example, you should add:

If you want a script to take your translatable strings into account, you must add your source file path in the file : <code>po/POTFILES.in</code>. For this report example, you should add:

Line 48:

Line 52:

...

...

−

See [[Translation_environment22]].

+

==Translating man pages==

−

* xgettext and 'po/gramps' file

+

You can also translated the man pages into your own language.

−

If you want a script to take your translatable strings into account, you must add your source file path in the file : <code>po/gramps</code>. For this report example, you should add:

+

For the development (trunk) version you can find the required starting files under the directory /data/man.

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.