Re: GTK+ translations
- From: Claude Paroz <claude 2xlibre net>
- To: Matthias Clasen <matthias clasen gmail com>
- Cc: GNOME i18n list <gnome-i18n gnome org>
- Subject: Re: GTK+ translations
- Date: Fri, 19 Apr 2013 23:46:13 +0200
Le vendredi 19 avril 2013 à 16:01 -0400, Matthias Clasen a écrit :
There seems to be some confusion around GTK+ translations.
To clarify: GTK+ is not using intltool. Please don't put any type
annotations in POTFILES.in. That breaks the build. We handle
extracting strings from ui files differently. The correct way to get
an updated pot for GTK+ is as follows:
make
make -C po gtk30.pot
Matthias,
That new method to generate the pot file is problematic for GNOME
translations.
Until now, no GNOME modules require to be built to be able to generate
the pot file. And this has always been a rule we stick with whenever
some new module wanted to use the GNOME i18n infrastructure.
That sort of design change is not something that should be taken
lightly. I think that requiring building a module to obtain the pot file
is bad for translators in general. It is then much more difficult for
translators to update translations themselves (almost impossible for the
majority of them).
Even at an infrastructure level, you surely know that building big
modules like GTK+ is often a challenge. And if then other modules begin
to use the same procedure, this will be a nightmare to maintain in the
i18n point of view.
I'd like to ask the GNOME community to reconsider that change and do all
what's possible to keep the legacy way of generating translations. I'm
not particularly attached to intltool, so if we find another tool that
does a better job, why not. But let's try all possible solution that do
not require to build the modules themselves.
Thanks for hearing us (me?).
Claude
--
www.2xlibre.net
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]