Re: Translations, GNOME and KDE

[Jeff Waugh <jdub perkypants org>]

<quote who="Jordi Mallach">

> In my experience (I have been translating GNOME since 1.3/pre2.0), the 2.4
> release process was quite negative in the i18n front. The final list of
> modules was announced way too late, adding a zillion new strings to our
> modules. Some teams can't cope with that workload, and in consequence,
> they don't reach 90% (the established limit to consider stuff as
> "supported").

As I said in an earlier answer, you guys have so much opportunity and time
to make your needs known. It's great that we're getting the feedback now,
but we're going to have to deal with these things better than reacting to
crises as they come up. [ Not that this is a crisis, but you know what I
mean. ;-) ]

> Another issue is if translations are ever released, yes. There's a list of
> modules in the status pages that haven't done a release in years, and
> despite this, the teams allocate time to translate them, because they show
> up in the status pages. Also, once GNOME 2.x.0 is released, you count on
> tarballs being made for 2.x.1, but many times this only happens if there
> are non-i18n bugfixes to be made on the given module. If the package is
> Good(tm), it's easy that you won't see another version, so your
> translation won't be used by anyone until GNOME 2.(x+1).0 where, surprise,
> it might have rotten again.

Arsekicking *has* to come from the i18n team on this front. You guys know
what's going on, so have to urge maintainers to release, or make sure the
release team is informed enough to do the arse kicking for you. :-)

Thanks,

- Jeff

-- 
Come to gnome.conf.au 2004!   http://www.gnome.org/~jdub/2004/gnome.conf.au/
 
                              Perl - The Movie
                        Starring 'Weird' Al Yankovic