Hrvoje Niksic <[EMAIL PROTECTED]> writes:
> The strategy of re-releasing the whole package shares many of the
> flaws with the "strings freeze" strategy. Specifically, I would be
> tempted to include bug fixes and string changes into such a
> re-released package.
Would be okay with me. Just increase the version number (reserve the
first 3 numbers for programming realated issue and the 4th number for
translations):
1.7 The "normal" forthcoming release.
Then
1.7.0.1 Only translations added
or
1.7.1 Release with bug fixes (and with new translations)
If it was needed to release 1.7.1 and further translations will arrive,
release
1.7.1.1 That's the bug fix release with new translations.
> Unbundling translations has the additional benefit that people who
> don't care about translations (*gasp*) never need to deal with them.
We'll go this way sooner or later; IMO, the time doesn't have come.
> I really cannot understand how an additional TAR file would be an
> irritation to *everyone*. The programmers, the translators, and the
> users would never even notice it!
Might be part of the problem. programmers just get familiar with "how
it works"; maybe, they are not fond of the idea to maintain additional
tar files. At the moment it's guaranteed it just works (widely
supported by automake, autoconf and gettext plus the "robot").
> Compare that to the current situation where all of Wget's translations
> except the Croatian one are *guaranteed* to be incomplete!
Not necessarily. Interested parties can have a look at
www.iro.umontreal.ca and fetch updated files.
> Francois Pinard has dismissed my idea out of hand. Sometimes I get
> the feeling that the Translation Project is extremely closed to new
> ideas.
No, not at all. But it's a lot of work to arrange all the
infrastructure for all the i18n/l10n business. At the moment we (Martin
v. L�wis and me, with background support by Fran�ois) are trying to get
the whole project fly again: we've to test gettext, support the teams,
support new translators who want to establish a new team, sort out
copyright issues, add new software packages, keeping track of changing
email addresses and "web" and FTP references, update/fix the robot
software. Then we'll have to update the texts of Fran�ois' website and
we've to work out a scheme to hand out more work to the so called "team
leaders" (that's a big permission/security problem).
If this is done we can start to change the workflow. Of course, we can
start now to collect all ideas and to assign priorities.
> Several years ago when I decided to not bundle gettext with Wget, it
> was considered almost unthinkable. Today it is becoming an
> established practice.
;) For Linux this might work...
> Sometimes I wish the TP people would listen to suggestions with a more
> attentive ear.
Be assured, we do. Of course, Fran�ois also did listen. Actually, he
collected and sorted all the different mails (proposals, support
requests, etc.); all things are in a pretty good condition as handed out
by Fran�ois. Now we're trying to cut down the backlog. I'm sure this
will not take too long.
I guess I can start to think seriously about improvement proposals the
next month. This doesn't mean the improvement will come true 2 months
later ;)
Hope this helps for the moment.
--
work : [EMAIL PROTECTED] | ,__o
: http://www.suse.de/~ke/ | _-\_<,
home : [EMAIL PROTECTED] | (*)/'(*)
