On 12/23/05, ะะณะพั ะะธะปะตัะธั grejigl-gnomeprevod@yahoo.ca wrote:
And two further clarify, there will be two locale's, sr and sr@Latn.
Regards, Igor
Sarah Wang sarahs@redhat.com wrote: Just to clarify, do you mean to add "sr" locale (sr.po) to all fedora packages?
Dear Sarah,
we already have translated sr.po files for all the packages and they are tied to the "Serbian" language on the status page (some are not being built and shipped though, but that's already in bugzilla). So that's all perfectly fine.
As Igor said, we need another set of sr@Latn.po files created for all the packages and the current Serbian translators added to their ACL as we need to support both scripts concurrently. Not sure if we need a separate status page for these since they're always generated by a script and will hopefully always have identical status. Can the CVS be set up so that when a translator "takes" a module on the "Serbian" page both of these locales get locked? If, on the other hand, you find it necessary to create another language page, you can label it "Serbian (Latin)" in the list. (I don't know how GNOME handles this, but I couldn't see two separate "languages" on their status page, while they support both locales; maybe you can check how they did it in their CVS?)
I hope that clears things a bit, please feel free to ask us more questions until we get this is completely clarified.
Thanks a lot for your help and time, Milos
Hi Sarah,
On 12/23/05, Miloš Komarčević kmilos@gmail.com wrote:
On 12/23/05, ะะณะพั ะะธะปะตัะธั grejigl-gnomeprevod@yahoo.ca wrote:
And two further clarify, there will be two locale's, sr and sr@Latn.
Regards, Igor
Sarah Wang sarahs@redhat.com wrote: Just to clarify, do you mean to add "sr" locale (sr.po) to all fedora packages?
As Igor said, we need another set of sr@Latn.po files created for all the packages and the current Serbian translators added to their ACL as we need to support both scripts concurrently. Not sure if we need a separate status page for these since they're always generated by a script and will hopefully always have identical status. Can the CVS be set up so that when a translator "takes" a module on the "Serbian" page both of these locales get locked? If, on the other hand, you find it necessary to create another language page, you can label it "Serbian (Latin)" in the list. (I don't know how GNOME handles this, but I couldn't see two separate "languages" on their status page, while they support both locales; maybe you can check how they did it in their CVS?)
Did you have any new ideas how to get this new sr@Latn locale into the CVS? I'm just asking because test2 freeze date is coming up soon and we would like to get these in...
Thanks, Milos
Milos,
I'm not sure how this can be done. The set of po files can certainly be added to CVS, but I'm not sure how the status page will handle this, and how the new locale can be enabled in anaconda.
Bernd/Jeremy, any ideas?
Sarah
On Thu, 2006-01-05 at 20:04 +0000, Miloš Komarčević wrote:
Hi Sarah, Did you have any new ideas how to get this new sr@Latn locale into the CVS? I'm just asking because test2 freeze date is coming up soon and we would like to get these in...
Thanks, Milos
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-trans-list
On 1/6/06, Sarah Wang sarahs@redhat.com wrote:
Milos,
I'm not sure how this can be done. The set of po files can certainly be added to CVS, but I'm not sure how the status page will handle this, and how the new locale can be enabled in anaconda.
We've managed to convince Jeremy and this has already been added to anaconda:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=175611
As for the status page, we can either create a new "Serbian (Latin)" locale page and track it independently if we must, or not track it at all (if the setup permits that) because status should be identical as files are automatically generated by a script by us. GNOME and KDE sort of do it that way, would it help to check how they did it?
In any case, if you could create the sr@Latn.po files in the CVS and add the same people that have access to sr to the ACL it would be a huge step forward as it would enable us to commit these and packagers to ship them.
Thanks, Milos
Milos,
The files sr@Latin.po are added in all packages. Please note, they are just empty file placeholders, you need to replace them (or merge your translation into them). I've also added new locale Serbian (Latin) in the status page locale list, hopefully it would show up within 24 hours.
Sarah
On Fri, 2006-01-06 at 10:33 +0000, Miloš Komarčević wrote:
On 1/6/06, Sarah Wang sarahs@redhat.com wrote:
Milos,
I'm not sure how this can be done. The set of po files can certainly be added to CVS, but I'm not sure how the status page will handle this, and how the new locale can be enabled in anaconda.
We've managed to convince Jeremy and this has already been added to anaconda:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=175611
As for the status page, we can either create a new "Serbian (Latin)" locale page and track it independently if we must, or not track it at all (if the setup permits that) because status should be identical as files are automatically generated by a script by us. GNOME and KDE sort of do it that way, would it help to check how they did it?
In any case, if you could create the sr@Latn.po files in the CVS and add the same people that have access to sr to the ACL it would be a huge step forward as it would enable us to commit these and packagers to ship them.
Thanks, Milos
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-trans-list
Dear Sarah,
On 1/9/06, Sarah Wang sarahs@redhat.com wrote:
Milos,
The files sr@Latin.po are added in all packages. Please note, they are just empty file placeholders, you need to replace them (or merge your translation into them). I've also added new locale Serbian (Latin) in the status page locale list, hopefully it would show up within 24 hours.
Thank you very much for making this possible for us. However, the correct ISO identifier for the latin script is @Latn, not @Latin, so this will have to be corrected in CVS asap before I can commit! (No need to change the full description on the status page and anaconda chooser though.)
Thanks again, Milos
Sorry about this mistake! The correction has been made both in CVS and the status page.
Sarah On Mon, 2006-01-09 at 09:16 +0000, Miloš Komarčević wrote:
Dear Sarah,
On 1/9/06, Sarah Wang sarahs@redhat.com wrote:
Milos,
The files sr@Latin.po are added in all packages. Please note, they are just empty file placeholders, you need to replace them (or merge your translation into them). I've also added new locale Serbian (Latin) in the status page locale list, hopefully it would show up within 24 hours.
Thank you very much for making this possible for us. However, the correct ISO identifier for the latin script is @Latn, not @Latin, so this will have to be corrected in CVS asap before I can commit! (No need to change the full description on the status page and anaconda chooser though.)
Thanks again, Milos
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-trans-list
On 1/10/06, Sarah Wang sarahs@redhat.com wrote:
Sorry about this mistake! The correction has been made both in CVS and the status page.
Great! Thanks again!
I guess I can't commit until the status page is up to enable file ACL locking?
Best regards, Milo
Milo,
I have enabled your access for this locale. Who else need to be able to commit in this locale?
Sarah
On Tue, 2006-01-10 at 00:36 +0000, Miloš Komarčević wrote:
On 1/10/06, Sarah Wang sarahs@redhat.com wrote:
Sorry about this mistake! The correction has been made both in CVS and the status page.
Great! Thanks again!
I guess I can't commit until the status page is up to enable file ACL locking?
Best regards, Milo
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-trans-list
On 1/10/06, Sarah Wang sarahs@redhat.com wrote:
I have enabled your access for this locale.
Still can't commit, I get the folowing error in TortoiseCVS:
Testing sr@Latn.po... /usr/bin/i18n-access: Invalid filename.
Usage: i18n-access [filenames]
**** Access allowed: kmilos is in ACL for anaconda/po. cvs server: Pre-commit check failed cvs [server aborted]: correct above errors first!
You mnetioned before some 24hr wait before things get synced, is that still the case?
Who else need to be able to commit in this locale?
The same people who have access to the "sr" locale so we always update them hand in hand. I don't know their CVS usernames, but let me know if you can't find them and I'll get them to email you.
Thanks, Milos
It doesn't look like an access issue. Looks like "@" symbol is causing problem in the pre-commit check script. Need to defer this to the script author.
I've enabled sr@Latn locale access for all current sr committers.
Sarah
On Tue, 2006-01-10 at 10:51 +0000, Miloš Komarčević wrote:
On 1/10/06, Sarah Wang sarahs@redhat.com wrote:
I have enabled your access for this locale.
Still can't commit, I get the folowing error in TortoiseCVS:
Testing sr@Latn.po... /usr/bin/i18n-access: Invalid filename.
Usage: i18n-access [filenames]
**** Access allowed: kmilos is in ACL for anaconda/po. cvs server: Pre-commit check failed cvs [server aborted]: correct above errors first!
You mnetioned before some 24hr wait before things get synced, is that still the case?
Who else need to be able to commit in this locale?
The same people who have access to the "sr" locale so we always update them hand in hand. I don't know their CVS usernames, but let me know if you can't find them and I'll get them to email you.
Thanks, Milos
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-trans-list
On 1/10/06, Sarah Wang sarahs@redhat.com wrote:
It doesn't look like an access issue. Looks like "@" symbol is causing problem in the pre-commit check script. Need to defer this to the script author.
Ah, ok. I would be interested to keep an eye on this if there is a bugzilla entry, otherwise, please keep us updated and let us know if we can be of any help.
I've enabled sr@Latn locale access for all current sr committers.
Thanks, Milos
Miloš Komarčević wrote:
On 1/10/06, Sarah Wang sarahs@redhat.com wrote:
It doesn't look like an access issue. Looks like "@" symbol is causing problem in the pre-commit check script. Need to defer this to the script author.
Ah, ok. I would be interested to keep an eye on this if there is a bugzilla entry, otherwise, please keep us updated and let us know if we can be of any help.
This should be fixed now.
I've enabled sr@Latn locale access for all current sr committers.
I'd undo the sr@Latn as locale thing. All commits of sr@Latn are treated the same as commits to sr, it's namely a different filename.
Bernd
On 1/11/06, Bernd Groh bgroh@redhat.com wrote:
Miloš Komarčević wrote:
On 1/10/06, Sarah Wang sarahs@redhat.com wrote:
It doesn't look like an access issue. Looks like "@" symbol is causing problem in the pre-commit check script. Need to defer this to the script author.
Ah, ok. I would be interested to keep an eye on this if there is a bugzilla entry, otherwise, please keep us updated and let us know if we can be of any help.
This should be fixed now.
Ok, looks like something is fixed, but now I get this error, even after reserving anaconda on the "sr" status page:
Testing sr@Latn.po... [sr@Latn.po] is not in your locale. **** Access allowed: kmilos is in ACL for anaconda/po. cvs server: Pre-commit check failed cvs [server aborted]: correct above errors first!
Presumably to do with what zou mention below?
I've enabled sr@Latn locale access for all current sr committers.
I'd undo the sr@Latn as locale thing. All commits of sr@Latn are treated the same as commits to sr, it's namely a different filename.
I guess that's what I was asking about earlier. There's really no need to track them separately as we'll be committing them in sync. Can something like that be set up?
Thanks, Milos
P.S. The status page for "Serbian(Latin)" gives me an internal server error...
Miloš Komarčević wrote:
On 1/11/06, Bernd Groh bgroh@redhat.com wrote:
Miloš Komarčević wrote:
On 1/10/06, Sarah Wang sarahs@redhat.com wrote:
It doesn't look like an access issue. Looks like "@" symbol is causing problem in the pre-commit check script. Need to defer this to the script author.
Ah, ok. I would be interested to keep an eye on this if there is a bugzilla entry, otherwise, please keep us updated and let us know if we can be of any help.
This should be fixed now.
Ok, looks like something is fixed, but now I get this error, even after reserving anaconda on the "sr" status page:
Testing sr@Latn.po... [sr@Latn.po] is not in your locale. **** Access allowed: kmilos is in ACL for anaconda/po. cvs server: Pre-commit check failed cvs [server aborted]: correct above errors first!
Presumably to do with what zou mention below?
Goes to show that people should actually test things. :)
Try again now!
I've enabled sr@Latn locale access for all current sr committers.
I'd undo the sr@Latn as locale thing. All commits of sr@Latn are treated the same as commits to sr, it's namely a different filename.
I guess that's what I was asking about earlier. There's really no need to track them separately as we'll be committing them in sync. Can something like that be set up?
Thanks, Milos
P.S. The status page for "Serbian(Latin)" gives me an internal server error...
I guess I simply didn't think ahead and understood '@' as tainted data. This requires a fix, and has been added to my queue.
Cheers, Bernd
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-trans-list
On 1/11/06, Bernd Groh bgroh@redhat.com wrote:
Goes to show that people should actually test things. :)
Try again now!
Bernd,
Thanks a bunch, just managed to commit a bunch of stuff!
Oddly enough, just one module wass giving me trouble. I guess the problem is that on that one I was trying to commit both updated sr and sr@Latn at the same time, but it wouldn't have it:
Testing sr@.po... Testing sr@Latn.po... [sr@Latn.po] is not a valid translation file, etc...
Looks like it concatenated them together?
In any case, managed to do it in separate commits...
Thanks, Milos
Miloš,
Miloš Komarčević wrote:
On 1/11/06, Bernd Groh bgroh@redhat.com wrote:
Goes to show that people should actually test things. :)
Try again now!
Bernd,
Thanks a bunch, just managed to commit a bunch of stuff!
Oddly enough, just one module wass giving me trouble. I guess the problem is that on that one I was trying to commit both updated sr and sr@Latn at the same time, but it wouldn't have it:
Testing sr@.po... Testing sr@Latn.po... [sr@Latn.po] is not a valid translation file, etc...
Looks like it concatenated them together?
In any case, managed to do it in separate commits...
Hmmm, let me think about it. Glad you could commit though.
Cheers, Bernd
-
Bernd Groh -
Miloš Komarčević -
Sarah Wang