translation tooling: fix script to not include Kirigami strings

Not sure when it started doing that - we don't want those in our
translations, I believe.

Also, we appear to suddenly get problems with too many numerus lines
unless the existing translation is deleted, first. Very strange.

Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
This commit is contained in:
Dirk Hohndel 2020-03-10 14:06:18 -07:00
parent ca75177f0c
commit 1b2db4e058

View file

@ -19,6 +19,10 @@ pushd $SRC
git status | grep "Changes not staged for commit" 2>/dev/null && echo "tree not clean" && exit 1
git status | grep "Changes to be committed" 2>/dev/null && echo "tree not clean" && exit 1
# now remove the translations and remove access to the kirigami sources
chmod 000 mobile-widgets/qml/kirigami
rm translations/subsurface_source.ts
# enable creating the translation strings
sed -i.bak 's/# qt5_create_translation/ qt5_create_translation/ ; s/# add_custom_target(translations_update/ add_custom_target(translations_update/' translations/CMakeLists.txt
@ -45,6 +49,9 @@ git add translations/subsurface_source.ts
git commit -s -m "Update translation source strings"
git reset --hard
# now enable access to kirigami again
chmod 755 mobile-widgets/qml/kirigami
# this really depends on my filesystem layout
# push sources to Transifex
if [[ "$NOPUSH" != "1" ]] ; then