Re: translating [was Re: Intolerable CVS behaviour]

[Karl Eichwalder <ke suse de>]

Miguel de Icaza <miguel ximian com> writes:

> > Not bad.  Nevertheless, be prepare weird things will easily happen this
> > way: es.po from gnome-libs will be checked in as es.po for gnome-core...
> > What about branches?

> you bring up good points.

Thanks :)

Concerning branches: the web interface has to hide them, of course.  Our
targeted web interface user is only interested in doing the translation
for either the next package release, or for GNOME 1.4, or for GNOME 2.0,
etc.

To prevent confusion about es.po != es.po the web based check out should
adjust the file name accordingly:

    gtrans --get gnumeric --lang es --version current-gnome

should default to 'gnumeric.es.po' (or something); of course, you'll
have to define what's the meaning of "current-gnome" and some such
symbolic version terms.

> Good point.  We could have an authentication mechanism plus an ACL
> mechanism (so that German translations are not accidentally checked in
> as spanish translations).

;) Hopefully, beta tests will sort out thoses nitty gritties.

Almer "S." Tigelaar <almer gnome org> writes:

> I have no problems with it if it becomes additional. That way we can
> also see how the web-based system works in practice. But enforcing it
> seems unlogical at this point.

Yes, that's the point.  I'm pretty sure some new translators joining the
teams will love a web based interface; "old" translators will stay with
the CVS interface.  And some flux might happen.

I'm looking forward (please, try to avoid Perl as much as possible;
Python has nice offerings, too).

-- 
Linux Frechet 2.2.18 #1 Fri Jan 19 22:10:35 GMT 2001 i686 unknown
  8:53am  up 3 days,  1:32,  6 users,  load average: 0.00, 0.01, 0.00
                                             work    :      ke suse de
Karl Eichwalder                              home    : keichwa gmx net