Re: Update: translation errors with msgids and msgstrs
Milo Casagrande wrote: > Everything fixed for Italian. Thanks :) > Just a couple of notes/questions: > > - we found some strings in KDE packages with plural forms that we > suppose are c-format, but the *msgid* string is using something like > "1%" (in the singular) for saying "one percent" and the plural has a "% > n". Now, I don't know how KDE internals work, but shouldn't it be "1%%" > if it's a c-format string? The translation already there is correct > since it basically translate to "one percent" without the % sign. But, > since KDE looks like is using a "different" version of gettext, I really > don't know... yes, it should be "1%%", otherwise it will be treated as a space padded format string (e.g. "1% of", would be interpreted as "1%of", where "%o" would be treated as format string). Since the plural uses "%n", the entry should be marked as c-format string, IMHO. Otherwise the %n replacement won't work. > - what kind of test was used to give all those errors even with > no-c-format strings? Were no-c-format strings treated as c-format? We forced msgfmt to treat all strings as c-format strings in order to catch those which really do have c-formats inside but were not tagged as such. Cheers Arne -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: How to revert to upstream translations
Hi,
Il giorno dom, 18/01/2009 alle 20.44 +0100, Dominique Pelle ha scritto:
> I do hope that strings from upstream have higher priority
> than strings in Rosetta. I would find it quite wrong if Rosetta
> replaced without good reasons translations that have been
> done carefully upstream.
>
> Shouldn't Rosetta only add strings when translations are missing
> upstream? Or in some rare cases maybe correct incorrect strings
> from upstream?
I just quote from last Danilo message regarding this aspect:
> Launchpad Translations has changed the translation precedence policy
> with the December release: now upstream ("packaged") translations will
> be given more priority in specific cases. Yet, Launchpad Translations
> keeps the ability to override any specific upstream translation if so
> is
> desired.
>
> This mostly concerns Ubuntu and it's upstreams (packages), though it
> will have a small effect on projects hosting their translations in
> Launchpad as well. If you understand better with examples, just look
> at
> the "examples" section below.
The original thread is here:
https://lists.ubuntu.com/archives/ubuntu-translators/2008-December/001994.html
Cheers.
--
Milo Casagrande
signature.asc
Description: Questa è una parte del messaggio firmata digitalmente
--
ubuntu-translators mailing list
ubuntu-translators@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: How to revert to upstream translations
On Sun, Jan 18, 2009 at 2:31 PM, Milo Casagrande wrote: > Il giorno dom, 18/01/2009 alle 19.54 +0100, Åsmund Skjæveland ha > scritto: >> Some strings in Launchpad have better translations upstream than in >> Launchpad. If I replace the Launchpad translation with the upstream >> string, will Launchpad automatically detect that the upstream >> translation takes over? > > Yes... For the record, this is new to the translation process via Rosetta, and as far as I know will be used for the very first time. How well it will be used is still to be seen. I am however hoping for the best. Cheers, -- Og B. Maciel omac...@foresightlinux.org ogmac...@gnome.org ogmac...@ubuntu.com GPG Keys: D5CFC202 http://www.ogmaciel.com (en_US) http://blog.ogmaciel.com (pt_BR) -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: How to revert to upstream translations
> Some strings in Launchpad have better translations upstream than in > Launchpad. If I replace the Launchpad translation with the upstream > string, will Launchpad automatically detect that the upstream > translation takes over? > > In the translation page, Launchpad shows three strings labeled English, > Current Norwegian Nynorsk, and Packaged. Is the string labeled "Current > Norwegian Nynorsk" the upstream string, or the most recent Launchpad > string? I assume "Packaged" is the last string that was included in a > langpack. I do hope that strings from upstream have higher priority than strings in Rosetta. I would find it quite wrong if Rosetta replaced without good reasons translations that have been done carefully upstream. Shouldn't Rosetta only add strings when translations are missing upstream? Or in some rare cases maybe correct incorrect strings from upstream? I've done translations upstream, which have been reviewed and I'd be a bit disappointed if they were badly altered in Ubuntu. Regards -- Dominique http://dominiko.livejournal.com -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: How to revert to upstream translations
Il giorno dom, 18/01/2009 alle 19.54 +0100, Åsmund Skjæveland ha scritto: > Some strings in Launchpad have better translations upstream than in > Launchpad. If I replace the Launchpad translation with the upstream > string, will Launchpad automatically detect that the upstream > translation takes over? Yes... > In the translation page, Launchpad shows three strings labeled English, > Current Norwegian Nynorsk, and Packaged. Is the string labeled "Current > Norwegian Nynorsk" the upstream string, or the most recent Launchpad > string? I assume "Packaged" is the last string that was included in a > langpack. Yes, usually "Packaged" is the last packaged upstream string, the "Current..." is the translation in use now, the one that will be shipped in the next langpack, and usually a string that has been changed inside Launchpad. This string will not became a "Packaged" string with the creation of a new langpack though, the "Packaged" will always be the upstream string. (That's how I understood the all thing, maybe Danilo could say something more.) Cheers. -- Milo Casagrande signature.asc Description: Questa è una parte del messaggio firmata digitalmente -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
How to revert to upstream translations
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Some strings in Launchpad have better translations upstream than in Launchpad. If I replace the Launchpad translation with the upstream string, will Launchpad automatically detect that the upstream translation takes over? In the translation page, Launchpad shows three strings labeled English, Current Norwegian Nynorsk, and Packaged. Is the string labeled "Current Norwegian Nynorsk" the upstream string, or the most recent Launchpad string? I assume "Packaged" is the last string that was included in a langpack. - -- Åsmund Skjæveland -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAklzetYACgkQKeJUaVS5dc6xfACggS0VENla0YNJZ8ArJ4+EpUxl omgAoJ1Rb9GO7QGyH1VCxx0EcajWXhjR =HVYd -END PGP SIGNATURE- -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Update: translation errors with msgids and msgstrs
Il giorno sab, 17/01/2009 alle 01.26 +0800, Arne Goetje ha scritto: > Dear translators, > > for your convenience, here is the list of affected msgids, sorted by > release and language code: > > http://people.ubuntu.com/~arne/langpack_errors/ > > Please note, that these lists may contain false positives. Everything fixed for Italian. Just a couple of notes/questions: - we found some strings in KDE packages with plural forms that we suppose are c-format, but the *msgid* string is using something like "1%" (in the singular) for saying "one percent" and the plural has a "% n". Now, I don't know how KDE internals work, but shouldn't it be "1%%" if it's a c-format string? The translation already there is correct since it basically translate to "one percent" without the % sign. But, since KDE looks like is using a "different" version of gettext, I really don't know... - what kind of test was used to give all those errors even with no-c-format strings? Were no-c-format strings treated as c-format? Cheers. -- Milo Casagrande signature.asc Description: Questa è una parte del messaggio firmata digitalmente -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Some details of what happened (was: Re: HEADS-UP! URGENT! Major problem with translations for Hardy and Intrepid.)
Hi all, 2009/1/18 Milo Casagrande : > Il giorno dom, 18/01/2009 alle 07.39 +0200, Adi Roiban ha scritto: >> Below is the report based on Base pack: 2009-01-06 00:14:56 EET , but I >> would add a cron job to update such a page once every 2 weeks. >> http://l10n.ubuntu.tla.ro/rosetta-hardy-build/ > > It's great, but there are a lot of false positive in there (at least as > I see them and for my own language) like: > > Last-Translator > Project-Id-Version > Language-Team > > (There's also an error like "1 translated message".) > I believe that's this bug -> https://bugs.edge.launchpad.net/rosetta/+bug/128324 Now regarding the issue at hand: first of all, I must say I share all of Milan's concerns on his message [1], but as I believe most of his points have now been understood, I will stop here. Seeing that this also concerns translation packages updates, and that Arne asked for suggestions, here's my simple suggestion: devise and publish a schedule for language pack updates on each release cycle. It does not have to be more than a wiki page with this information. The way it is today is less than optimal and it does not use the advantages of langpacks at all. We never know when or how the langpacks will be released, and it usually boils down to an announcement that they will be released in a couple of days, which does not give us time to apply corrections or to set our translation aims at all. Having a plan for langpack updates would allow us to a) devise a better way, or at least a schedule for testing them before release b) think of a way to provide some sort of automatic testing in the way Adi is suggesting and has already started implementing for the ubuntu-docs. As for the current issue, I have created a page to help better tracking its status for all teams -> https://wiki.ubuntu.com/TranslatingUbuntu/LangPackSecurityIssues. Please feel free to add information about the status of this for your teams. Regards, David. [1] https://lists.ubuntu.com/archives/ubuntu-translators/2009-January/002043.html -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Some details of what happened (was: Re: HEADS-UP! URGENT! Major problem with translations for Hardy and Intrepid.)
Il giorno dom, 18/01/2009 alle 07.39 +0200, Adi Roiban ha scritto: > Below is the report based on Base pack: 2009-01-06 00:14:56 EET , but I > would add a cron job to update such a page once every 2 weeks. > http://l10n.ubuntu.tla.ro/rosetta-hardy-build/ It's great, but there are a lot of false positive in there (at least as I see them and for my own language) like: Last-Translator Project-Id-Version Language-Team (There's also an error like "1 translated message".) Those aren't things you can change directly in Launchpad and that upstream teams usually should deal with. We can check with them though, but it's not always that easy, since, if you don't have the Last-Translator or Language-Team field set, you have to go by trial and error. Anyway, that would be a great addition to our resources! -- Milo Casagrande signature.asc Description: Questa è una parte del messaggio firmata digitalmente -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Update: translation errors with msgids and msgstrs
Le Friday 16 January 2009 18:26:18 Arne Goetje, vous avez écrit : > Dear translators, > > for your convenience, here is the list of affected msgids, sorted by > release and language code: > > http://people.ubuntu.com/~arne/langpack_errors/ Everything is fixed for French. -- Bruno -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
