Le 06. 09. 18 à 10:00, Carlos Soriano a écrit :
...
Also, another thing I'm taking into account here is that there is a
strong desire by some maintainers to prevent any commit to go directly
to master by using GitLab's protected branches feature (not because of
translators, but generally). This
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 Ca
>
> 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
Þann þri 4.sep 2018 19:15, skrifaði Daniel Mustieles García via gnome-i18n:
Ok so just to clear things and not to start a flame-war, I just want to use
my script to commit a bunch of translations, only that. If i have to commit
20 PO files with just one string modified throught DL I will simply
Ok so just to clear things and not to start a flame-war, I just want to use
my script to commit a bunch of translations, only that. If i have to commit
20 PO files with just one string modified throught DL I will simply ignore
them because all the click-work needed to do it it's not worth for me.
Just some notes from Serbian translation team. It is nice to have a
tool such as Damned Lies and we would love if it can grow to a point
that all the translation can be done through a web interface (like
transifex for example).
On the other hand, DL functionality is very limited, especially when
d
On Tue, Sep 4, 2018 at 8:10 PM Daniel Mustieles García <
daniel.mustie...@gmail.com> wrote:
> El mar., 4 sept. 2018 17:50, Alexandre Franke
> escribió:
>
>> On Tue, Sep 4, 2018 at 9:30 AM Daniel Mustieles García via gnome-i18n <
>> gnome-i18n@gnome.org> wrote:
>> Damned lies has an API and your s
El mar., 4 sept. 2018 17:50, Alexandre Franke escribió:
> On Tue, Sep 4, 2018 at 9:30 AM Daniel Mustieles García via gnome-i18n <
> gnome-i18n@gnome.org> wrote:
>
>> Yes, translators are encouraged to use Damned Lies instead of accesing
>> Git directly, but some translators (me, for example) migh
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 before
On Tue, Sep 4, 2018 at 9:30 AM Daniel Mustieles García via gnome-i18n <
gnome-i18n@gnome.org> wrote:
> 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 i
On Tue, Sep 4, 2018 at 9:30 AM Claude Paroz wrote:
> However, there are some cases where Damned Lies is not yet able to push
> *new* translations.
>
Another case that you forgot about and which I also forgot about so far
when replying to this topic is figures. We don’t have a way to upload
image
Claude,
Em ter, 4 de set de 2018 às 04:30, Claude Paroz escreveu:
>
> Note that there are more and more modules also using LINGUAS files for
> docs, so this issue should be less important in the future. If the
> release-notes build could be changed to use a LINGUAS file, it would be
> great too.
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 tran
>
> 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 translatio
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 m
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 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 com
Le 04. 09. 18 à 09:16, Carlos Soriano a écrit :
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 d
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 re
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 transla
20 matches
Mail list logo