Note that not only LINGUAS file is a pain to add new languages... Makefile
file for documentation is even more difficult to parse as it's not always
in the same way, and it's needed to add a new language for documentation.
This case should be also considered
Cheers!
2018-09-06 10:00 GMT+02:00
>
> Of course, if there is any problem with a translation commit you can
> always ask this list and we will help you ;-)
Right, the goal is to not break on pre-merge though. But since this seems
quite rare to happen... it's probably not a big deal.
To add more weigh into this, recently I also had
>
> Damned Lies ald my script does such tests, but the case we have had with
> GIMP headers has not been detected... maybe test tools don't consider it a
> wrong line, when they should
>
Interesting... what kind of tests are passed? We had an issue with Nautilus
one year ago or so with a
2018-09-04 9:45 GMT+02:00 Carlos Soriano :
> Thanks for the answers!
>
> > LINGUAS is often a variable inside a Mafefile or a configure.ac file
> Indeed. One option for that is to have one or two people from i18n have
> access to some projects to fix that.
>
> > Note that there are more and more
2018-09-04 9:45 GMT+02:00 Carlos Soriano :
> Yeah... on the other hand I think most of FOSS projects do it this way
> nowadays, at least in things like GitHub, etc. Another thing to consider is
> that translationa can break the code, maybe a good option is that
> translations need to pass CI
I use gtxml and msgfmt for checking PO files, but I disabled the gtxml
check temporary because it returned false positives in the
"translator-credits" line, but it detects wrong tags in documentation that
might cause a crash when compiling the module.
Of course, if there is any problem with a
Also, it would be good to know if merge requests would be appropriate for
this, instead of pure git access.
On Tue, 4 Sep 2018 at 09:16, Carlos Soriano wrote:
> Hello all,
>
> Recently we had a bit of scramble with the release notes and some
> translators not having git access to it.
>
> If I
Hello all,
Recently we had a bit of scramble with the release notes and some
translators not having git access to it.
If I remember correctly translators are encouraged to not push directly and
use Dammed Lies instead, if I remember correctly doing otherwise is
unsupported.
However, some
Hi Carlos,
Yes, translators are encouraged to use Damned Lies instead of accesing Git
directly, but some translators (me, for example) might use an automated
script (1) to push a bunch of translations instead of doing it one by one
in Damned Lies, which implies so much click-work to upload and
Thanks for the answers!
> LINGUAS is often a variable inside a Mafefile or a configure.ac file
Indeed. One option for that is to have one or two people from i18n have
access to some projects to fix that.
> Note that there are more and more modules also using LINGUAS files for
docs, so this issue
Hi engagement team,
we have set the GUADEC dates and location and I would appreciate if
someone could volunteer to (or help) write announcements, publish them
and also publicise via social media.
We would like to announce towards end of this week. If you're
interested, ping me directly!
Thanks
11 matches
Mail list logo
