Commit Graph

5 Commits

Author SHA1 Message Date
JosJuice e526b39956 update-translated-strings.sh: Disable fuzzy matching
This doesn't really matter in practice, because I always sync with
Transifex before running updated-translated-strings.sh, and then
there can't be any fuzzy matches. But we might as well disable fuzzy
matching explicitly, becase the results can be quite odd.
This should make the script a bit faster too.
2019-04-14 15:19:29 +02:00
JosJuice 0db63cefc0 Use dirname $0 in localization scripts 2017-08-04 19:09:12 +02:00
JosJuice ee4195547a Handle update-translated-strings.sh being run from a different directory
update-source-strings.sh was already solving the same problem
in the same way.
2017-08-04 10:39:08 +02:00
JosJuice cd0abb1445 Simplify update-translated-strings.sh 2017-08-01 14:19:46 +02:00
JosJuice 6425fa28ab Split gettextize script into two
When building DolphinWX using cmake, msgmerge will run on the
.po files, updating the formatting of them if they aren't
already in the exact format that msgmerge uses. This means that
running msgmerge on all the .po files is necessary before
committing any updates to the .po files, because otherwise
unstaged changes are going to appear whenever anyone tries to
build that commit using cmake. The translation syncing scripts
that were used by delroth and Parlane did so by invoking `cmake`
and then `make translations`, but that isn't a good solution
for people who sync translations on Windows (i.e. me).

This commit uncomments some existing code for running msgmerge
on all the .po files, and places that code in a new script. Now,
translation syncing scripts just have to call that script before
committing, instead of using msgmerge directly or using cmake.

I'm not sure why the script was called gettextize to begin with.
gettextize is the name of a gettext executable that doesn't seem
to be related to what our gettextize script did.
2017-08-01 13:33:07 +02:00