Re: Terminal Server Client



mån 2003-04-28 klockan 17.37 skrev Erick Woods:
> I've thought about it in the past, but have so for avoided cvs.  There are
> also other issues, but I'll not get into them.  It shouldn't be that much
> more difficult to go to my site, grab the pot and translate it, is it?

Perhaps not "difficult", but a great waste of time better spent on
actual translating.

The GNOME Translation Project is several hundred individual translators,
organized into sixtysomething language teams (more than fifty last time
I counted, but that was a long time ago and we've had some new since
then).
Many of these translators translate (and regularly update!) from tens
even up to hundreds of different pieces of software inside the GNOME
project. The reason this is even remotely possible is because we have a
common status page (see
http://developer.gnome.org/projects/gtp/status/gnome-2.2/) monitoring
the current translation status for all these modules, and updated
several times a day, and last but not least a common cvs where all
translations can be immediately accessed in an identical way, and
instantly committed.

The status page doesn't support "external" projects outside of GNOME
cvs, and to be honest I don't see any immediate need for that. GNOME
translation wouldn't be possible as we know it today if each and every
translator would be required to figure out a homepage for every or even
some pot or po files of any of the pieces of software, retrieve those,
and mail updates and *hope* for them to arrive or get applied in a
timely manner by some software maintainer in the other end.

I don't see how this would even be remotely comparable. Let alone since
this is only the translator aspect and the benefits of common
testing/contributions hasn't even been discussed. Comments?


Christian




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