Using different translation workflow


For the first time, we have a GNOME Git hosted module that choose to use
a different translation tool than

On one side, I would say that freedom is the key, so every module
maintainer should choose the tool which suited him the best.
On the other side, this could lead to fragmentation. If GNOME
translation teams have to use several different platform for their work,
there is clearly an overhead implied. Considering various comments on
the bug #608627, coordinators don't like this situation.

So the question is, should we make it an explicit requirement to use as the main translation platform for a module to be
hosted in GNOME Git?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]