Using different translation workflow
- From: Claude Paroz <claude 2xlibre net>
- To: GNOME Infrastructure <gnome-infrastructure gnome org>
- Subject: Using different translation workflow
- Date: Tue, 23 Feb 2010 08:31:58 +0100
Hi,
For the first time, we have a GNOME Git hosted module that choose to use
a different translation tool than l10n.gnome.org.
https://bugzilla.gnome.org/show_bug.cgi?id=608627
http://mail.gnome.org/archives/gnome-i18n/2010-February/msg00153.html
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
l10n.gnome.org as the main translation platform for a module to be
hosted in GNOME Git?
Claude
--
www.2xlibre.net
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]