Recompile for translation update under gettext?
Moderator: Forum Moderators
Recompile for translation update under gettext?
Have I understood it correctly when I infer that you have to recompile to update a translation under gettext?
-
- Inactive Developer
- Posts: 173
- Joined: January 15th, 2004, 5:09 pm
- Location: Zaragoza, Spain
- Contact:
Definitely not, after you have changed the sv.po you only need to generate the .gmo by running:
from the main directory. Then copy the sv.gmo to the place where Wesnoth .mo files reside (renamed as sv.mo).
That should work. I'm really pleased to see that you're trying again.
Best regards.
Code: Select all
make -C po sv.gmo
That should work. I'm really pleased to see that you're trying again.
Best regards.
Re: Recompile for translation update under gettext?
No, you only have to "compile" the new version of the po file you just updated. You can do that by running "make update-po" in the po directory. That will refresh the wesnoth.pot files in case the source files have changed, resync all *.po files, and rebuild all *.gmo files from them, including yours.sanna wrote:Have I understood it correctly when I infer that you have to recompile to update a translation under gettext?
Then "make install" will put the gmo files in the right place, so that the next wesnoth run will see them.
gettextization
french l10n team member
french l10n team member
-
- Inactive Developer
- Posts: 173
- Joined: January 15th, 2004, 5:09 pm
- Location: Zaragoza, Spain
- Contact:
That command basically runs:
First it deletes the previous gmo and then run the msgfmt program to generate the .gmo from the .po.
The .po file (as you know) is an UTF-8 ASCII file with the translations and all the non-translated strings.
The .mo file is a binary version of the .po file, which is smaller and faster, and because of that is used when the program runs instead of the .po.
Code: Select all
rm -f sv.gmo && /usr/bin/msgfmt -c --statistics -o sv.gmo sv.po
The .po file (as you know) is an UTF-8 ASCII file with the translations and all the non-translated strings.
The .mo file is a binary version of the .po file, which is smaller and faster, and because of that is used when the program runs instead of the .po.
Well, I'm not REALLY translating again, just trying to get the version yeti compiled working with 0.8.3isaac wrote:I'm really pleased to see that you're trying again.

Oh deary me, where might that be on mac?isaac wrote:Then copy the sv.gmo to the place where Wesnoth .mo files reside (renamed as sv.mo).
Hm, maybe we should install by default the compiled catalogs under $datadir, to make things easier. People willing to install them in a central place can always override the defaults.sanna wrote:Well, I'm not REALLY translating again, just trying to get the version yeti compiled working with 0.8.3isaac wrote:I'm really pleased to see that you're trying again.Frankly, I want something like poedit on mac!
Oh deary me, where might that be on mac?isaac wrote:Then copy the sv.gmo to the place where Wesnoth .mo files reside (renamed as sv.mo).
gettextization
french l10n team member
french l10n team member