16,602
edits
Changes
m
→Installing your translation
make --prefix=/usr install #as root !
This should install your translations to <code>''/usr/share/locale/xx{lang}/LC_MESSAGES/gramps.mo</code>'', with xx {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!
==== Running trunk with your translation ====
The i18n data are often under <code>''../share/locale</code> '' according to the default prefix.
So you can use:
python setup.py install #as root !
This will install the .mo files under <code>''../share/locale/xx/LC_MESSAGES</code>'', according to the default prefix set.
or
python setup.py build
python setup.py install --root=/home/jolejoe/gramps-trunk --prefix="/home/jolejoe/gramps4" --enable-packager-mode #as simple user !
This will install Gramps and translations under your <code>''/home/...</code> '' directory.
===== $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 as of February 2009:
* when you type <code>makepython build</code> in the source tree root (/home/user/trunk e.g.) all the trunk/po/*.po files are compiled into trunk/pobuild/mo/{lang}/*.gmo mo files.* when you type <code>make python install</code> inside the /home/user/trunk/po directory, these .gmo mo files are copied to /usr/local{prefix}/share/locale/xx{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)
