Closed raveit65 closed 4 years ago
@raveit65 @mate-desktop/core-team
I think msgfmt -c
does the checks to prevent unexpected behavior caused by erroneous translation
I think we can work in the classical way, without transifex, doing PRs with translations.
I think msgfmt -c does the checks to prevent unexpected behavior caused by erroneous translation
Yes, msgfmt -c
is the same like msgfmt -v --check-format --check-header --check-domain
,
and --check-format
gives us the fatal error.
With msgfmt -v --check-header --check-domain
the bad formatted string will simply ignored and not translated.
This is the same behaviour before we switched to gettext
.
I think we can work in the classical way, without transifex, doing PRs with translations.
Sadly, i don't have any spare time left to review tons of PRs in tons of languages.
I remember that pology can remove conflicting translations or mark them as draft/fuzzy, or something similar.
@raveit65 you can use the macro AM_XGETTEXT_OPTION in configure.ac file for adding options to xgettext.
msguniq can remove dulicated entries
I was able to fix similar issue for mate-power-manager with Lithuanian languge. https://github.com/mate-desktop/mate-power-manager/commit/809da871ffcd82732384ee8f164588b4008938e2 https://www.transifex.com/mate/MATE/translate/#lt/1-24--mate-power-manager/194076476?q=text%3A'%25i+minute' Here singular and plural forms are selectable. I will try it later for marco.
Expected behaviour
No trouble with translations
For the 1.24.1 release i had to fix 4 languages at transifex, see git history. Building always failed like this.
The problem is the
-c
option ofmsgfmt
See help:In result:
So we need to change
msgfmt
option somewhere in package, but i didn't find something in /po/Makevars. It is not acceptable that i have to fix at transifex simple formatting issues by translators with nearly every new tarball. Especially when i don't understand the languages.