ti, 2007-09-04 kello 16:39 -0400, Bill Nottingham kirjoitti:

I'd like to update the translations in initscripts:

A fully translated checkout will go from: mk.po: 785 translated messages. to: mk.po: 726 translated messages, 97 fuzzy translations, 34 untranslated messages.

Why we're changing now: Unfortunately, updating the initscripts list of translatable strings is a manual process that first requires installing every package that has a translatable file - this is a constantly changing set. It would have been done before the string freeze, except I was on vacation.

Impact of not doing it: Some initscripts will not be translated.

Yay/nay?

Any action or non-action that leads to some strings not being translated is the same as breaking the string freeze. The purpose of string freeze is not to keep the .pot files intact for some unknown reason, but to keep the strings of the application intact so that a translation team knows the 100% (or whatever percentage) they have reached will not suddenly decrease without a warning.

Now, the translation teams are interested in maintaining the percentage of translation they have reached, and new translatable strings appearing during string freeze is not desirable. However, it is even less desirable to add new _untranslatable_ strings, because that way the translators are not even given a chance to keep their translations up-to-date.

So, in my opinion it does not make sense to even consider an approach where new untranslatable strings are added in order to avoid breaking the string freeze. There are only two options: Either no strings are added/modified, and the string freeze stays, or strings are added and the string freeze is broken.

-LN

Hi,

I haven't seen any updates in the CVS repository yet. Can you please let's know whether you commited the changes to the CVS server or not.

Bill Nottingham લખ્યું:

I'd like to update the translations in initscripts:

A fully translated checkout will go from: mk.po: 785 translated messages. to: mk.po: 726 translated messages, 97 fuzzy translations, 34 untranslated messages.

Why we're changing now: Unfortunately, updating the initscripts list of translatable strings is a manual process that first requires installing every package that has a translatable file - this is a constantly changing set. It would have been done before the string freeze, except I was on vacation.

Impact of not doing it: Some initscripts will not be translated.

Yay/nay?

Bill

Bill Nottingham લખ્યું:

I'd like to update the translations in initscripts:

A fully translated checkout will go from: mk.po: 785 translated messages. to: mk.po: 726 translated messages, 97 fuzzy translations, 34 untranslated messages.

Why we're changing now: Unfortunately, updating the initscripts list of translatable strings is a manual process that first requires installing every package that has a translatable file - this is a constantly changing set. It would have been done before the string freeze, except I was on vacation.

Impact of not doing it: Some initscripts will not be translated.

Yay/nay?

Bill

Hi,

Here is the question for Dimtris now.

As per above information the new updated status of the translation should be "726 translated messages, 97 fuzzy translations, 34 untranslated messages.", which is correctly showing on i18n.redhat.com status page (i am putting Gujarati [gu] language status link here for the reference): http://i18n.redhat.com/cgi-bin/i18n-status?page=status&locale=gu&bra...

But, it's completely different status showing on translate.fedoraproject.org status page for this particular package: http://translate.fedoraproject.org/languages/gu/fedora-8

I just noticed that status for some other packages also differs.

Why is that so? Before some other people get confused between the status difference, please look at the issue.