Thanks Emmanuele. That's lots of good information to take the first step. I
try to gather some information and do as you suggested.
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n
Dear Fòram, and all,
Am Mo., 22. Juni 2020 um 16:39 Uhr schrieb Fòram na Gàidhlig
:
> IMO the optimum workflow would be to pull weblate translations with a
> scheduled GitLab CI job and let the CI commit them into a branch when
> they're green. The master branch should be protected and nobody
On Mon, 22 Jun 2020 at 16:58, mousavi.ar...@gmail.com <
mousavi.ar...@gmail.com> wrote:
> On Mon, Jun 22, 2020 at 4:43 PM Emmanuele Bassi wrote:
> >
> > On Mon, 22 Jun 2020 at 16:32, mousavi.arash--- via gnome-i18n <
> gnome-i18n@gnome.org> wrote:
> >>
> >> Hey,
> >>
> >> This has been discussed
On Mon, Jun 22, 2020 at 4:43 PM Emmanuele Bassi wrote:
>
> On Mon, 22 Jun 2020 at 16:32, mousavi.arash--- via gnome-i18n
> wrote:
>>
>> Hey,
>>
>> This has been discussed and resurfaced every once in a while. I think
>> the main issue is that the GNOME's L10N decision makers have no
>> interest
On Mon, 22 Jun 2020 at 16:32, mousavi.arash--- via gnome-i18n <
gnome-i18n@gnome.org> wrote:
> Hey,
>
> This has been discussed and resurfaced every once in a while. I think
> the main issue is that the GNOME's L10N decision makers have no
> interest in going this path and regular members also
Hey,
This has been discussed and resurfaced every once in a while. I think
the main issue is that the GNOME's L10N decision makers have no
interest in going this path and regular members also have no power or
knowledge to do it or don't know where to start. As a contributor for
many years, I
Hi Kukuh,
What I found is https://docs.weblate.org/en/weblate-3.10/workflows.html
IMHO the Weblate's translation workflow is simpler than DL's.
While DL operates on PO file level, Weblate operates on individual messages,
which effectively makes several stages from DL workflow unnecessary.
Speaking about Weblate, please consider back to this thread [1].
My question still not answered yet [2].
[1] https://mail.gnome.org/archives/gnome-i18n/2020-June/msg00016.html
[2] https://mail.gnome.org/archives/gnome-i18n/2020-June/msg00036.html
Regards
On Mon, Jun 22, 2020 at 9:39 PM Fòram na
I think WebLate would be a good pick. It has a glossary function too,
which teams will find handy to help with terminology consistency. And
you can download the files to translate too, in a long list of formats
of your choice. And it has some QA checks too, like punctuation, printf
placeholders
Hello,
I am coming from another thread and second the adoption of Weblate.
If someone prefers to work directly on PO files, those can be
downloaded, translated and uploaded back to Weblate. It has checks for
PO files.
It has teams, permissions, terminology, translation memory, machine
Hey Daniel,
First of all, I want to say that I see your POV, and you cannot change the
whole thing by yourself and I'm glad you are pushing to address these
translators' pain points in your time. I do agree on the technical side
with Emannuelle, but I also understand it's not something that will
Again this is David against Goliat, and I'm tired of fighting...
I have no skills to improve DL, I only developed a script and made it
available to everyone who wants use/read/whatever with it. If if can be a
start point to improve DL great! but I'm not going to keep fighting against
something
On Mon, 22 Jun 2020 at 11:44, Daniel Mustieles García <
daniel.mustie...@gmail.com> wrote:
> Hi Emmanuele,
>
> Just a quick question: which is the difference between commiting directly
> into Git and commiting through DL?
>
DL can, at least, centralise the place where tests are executed to
Hi Emmanuele,
Just a quick question: which is the difference between commiting directly
into Git and commiting through DL? PO file checks are the same (or should
be), so commiting directly is not more dangerous than using DL. the same
checks DL makes into a PO file are done in my script, for
Hi;
to be brutally honest, as a maintainer I don't want any translator to
commit directly to Git—unless it's done to a separate branch and/or through
merge requests.
Translators do not build the projects they translate, and they don't (or
cannot) know when they break things. The only way
Some time ago I talked about this with +Carlos Soriano
. I asked him about the possibility of creating a user's group in Gitlab,
formed by some team coordinators, which will have commit rights to be able
to commit a bunch of translations due to the heavy clickwork must be done
in DL. Still
16 matches
Mail list logo
