string freeze break request: initscripts

[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

[Domingo Becker]

2007/9/4, Bill Nottingham <notting(a)redhat.com&gt;:
>  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. 
No problem for spanish locale.

>  It would have been done before the string freeze, except I was on
>  vacation. 
It sounds understandable.  :-)

Regards

DomingoBecker (es)

[Lauri Nurmi]

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

[Igor Pires Soares]

Em Ter, 2007-09-04 às 16:39 -0400, Bill Nottingham escreveu:
>  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. 
No problem for Brazilian Portuguese Team. We still have some time before
the Translation Freeze.

[Ankit Patel]

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
>     
-- 
Regards,
Ankit Patel

[Bill Nottingham]

Ankitkumar Rameshchandra Patel (ankit(a)redhat.com) said: 
>  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. 
Committed now.

Bill

[Ankit Patel]

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&...

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.

-- 
Regards
Ankit Patel

[Diego Búrigo Zacarão]

>  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&...
>
>  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.
>
>  
We are looking at this problem.
I have noted many modules non-update in our new system and I believe that
problem is in the script of update.
Dimitris and me have talked about that in #fedora-admin to receive some logs
and we expect to fix it soon.

Regards

-- 
Diego Búrigo Zacarão
Linux User #402589
USE SOFTWARE LIVRE

[Ankit Patel]

Diego Búrigo Zacarão ??????:
>      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 <http://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&...
>     
> <http://i18n.redhat.com/cgi-bin/i18n-status?page=status&locale=gu&...
>
>      But, it's completely different status showing on
>      translate.fedoraproject.org <http://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.
>
>
>  We are looking at this problem.
>  I have noted many modules non-update in our new system and I believe 
>  that problem is in the script of update.
>  Dimitris and me have talked about that in #fedora-admin to receive 
>  some logs and we expect to fix it soon.
>
>  Regards
>
>  -- 
>  Diego Búrigo Zacarão
>  Linux User #402589
>  USE SOFTWARE LIVRE  
As long as the infrastructure people know it & working on
the fix, i am 
happy. Thanks for the update! :)

-- 
Regards
Ankit Patel