[haiku-commits] Re: r41046 - in haiku/trunk/data/catalogs: preferences/network servers/print

  • From: "Jonas Sundström" <jonas@xxxxxxxxxxx>
  • To: "haiku-commits@xxxxxxxxxxxxx" <haiku-commits@xxxxxxxxxxxxx>
  • Date: Sun, 20 Mar 2011 17:50:17 +0100

Adrien Destugues <pulkomandy@xxxxxxxxxxxxxxxxx> wrote:
> Le 20/03/2011 14:55, Jonas Sundström a écrit :
> > 2. Instead of the committer downloading the tarball just in time
> > for the commit, the langauge manager gets it and attaches it to the
> > commit-request. Attachments would need to be allowed on [haiku-
> > i18n]
> > or a new list made for this purpose. [haiku-i18n-commit-request]
> > maybe.
> >
> A trac ticket once every now and then will be enough once we get past
> the current phase of localizing stuff. Then, it will just be
> maintenance
> of the strings. For now the commit rate is pretty high because there
> is
> ongoing work to catch up the delay between writing apps and
> translating
> them.

It's exactly then that the issue I'm talking about is the most
visible. I'm language manager for Swedish. We stay close to 100%
translation a lot of the time, but the strings are a moving target.
HTA never stays 100% green for very long, due to changes in the
code. Also the translators work all the time, try strings, try names,
discuss, change strings. This work essentially -removes- strings
until the manager approves them. This work is on-going. Completion
does not mean things slow down or go silent.

If I commit a set of catkeys where the state is less than 100%
whereas the set in SVN were 100%, that is a step back. And that's
something I think a proper workflow can avoid. The language should
sign off on a definite set of catkeys, in the form of a tarball,
since that's the only means of snapshotting HTA currently.


Other related posts: