2013/8/9 Andrej N. Gritsenko <email@example.com>
Julius22 has written on Friday, 9 August, at 12:40:
>> Compiling it is very simple (example for French translation):
>> rm -f fr.gmo && msgfmt -o fr.gmo fr.po
>> Installing of that translation is also simple. In case of libfm on
>> Linux for French translation:
>> sudo install -m 0644 fr.gmo /usr/share/locale/fr/LC_MESSAGES/libfm.mo
>> Different OS may have it in different paths though but the language
>> and the package are always present in the path, you should replace
>> existing file for testing it.
>I'm glad you precised it because I thought I had to compile and install Yes, exactly what I meant. You just replace translation which was
>the whole software. So, if I understood you well, you only need to
>compile and install the translation files?
installed with your existing software and that software starts to use it
on next launch (in case of pcmanfm it is required to kill existing one
because pcmanfm uses single-instance approach).
I´m sorry but not so simple. Libfm pootle files are from master branch. This means that if we compile it some strings will not appear correct. Some strings in master branch are not the same in stable release.
> I now have another noob question. After having made some translation Until you press the button "Commit to VCS", your translation is
>work with Pootle, do you need to use the "Commit all to VCS" button of
>the project you worked in in order that your work is saved and taken
>into account? Or don't you need to do anything special?
visible only on Pootle server, and when you press that button it is
submitting into sources, so if you want that translation to be used, you
should always press it after work is done.
Correct. You should always do this. If not, other people work could be compromised.