Re: How to revert to upstream translations
On 07/14/2010 04:24 PM, Åsmund Skjæveland wrote: > A specific case is the Norwegian Nynorsk (nn) translation of Rhythmbox, > which was not previously translated upstream. I have updated the > Launchpad translation (changing many of the existing translations) and > committed the PO file both upstream and back to Launchpad. So the next > time Rhythmbox is imported into Launchpad from upstream, it should get > my new translation, which is also already in Launchpad. Correct. > Currently, my updated translation is marked as 'Changed in Launchpad', > since as far as LP knows, there is no upstream translation. Will LP > detect the new upstream translation and give them precedence > automatically, or will the LP translations (which currently are > identical to upstream) take precedence? It should use the "Packaged" ones, since they are the same as the ones currently in Launchpad. But this only works for the Ubuntu release where the new package has been imported into (most likely Maverick), since older Ubuntu releases carry the older package versions, where the upstream translations didn't include Nynorsk. > Since Rhythmbox has ~1k strings, clicking 'packaged' in LP on every one > is not “simply” :) Shouldn't be necessary, Launchpad should switch those automatically to "Packaged". But in case it doesn't, just file a question on https://answers.launchpad.net/rosetta/ and ask the Launchpad Translations team to switch all translations on this template to "Packaged". 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
Arne Goetje wrote: > Sorry, Milo, I need to correct you here. :) > > On 07/13/2010 08:38 PM, Milo Casagrande wrote: >> 2010/7/13 Åsmund Skjæveland: >>> Sorry if this is a repeat, this one never came back to me. >> I think it's the first time I see this message, so this should be the >> first one! ;-) >> >>> 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, it should do so. If it's not working that could be a problem. > > No. (see below) > Although, if you do that in the development release of Ubuntu and a new > version of that package gets uploaded later and carries the same string, > Launchpad may flip over to the "Packaged" one... I wouldn't rely on > that, though. > >>> 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? >> The "Current..." one is the actual translation for that string, be it >> upstream or of your team. > > The "Current" one is the string which is currently exported into the > langpacks. > >>> I assume "Packaged" is the last string that was included in a >>> langpack. >> Exactly. Packaged is the string that was shipped with the last >> langpack, it doesn't mean that that string is upstream though. > > No, "Packaged" means that that string came with the ubuntu package of > that application and got imported into Launchpad from there. > This means, that the "Packaged" translation can be > a) the one which the upstream project (of the same version) uses > b) the one which the Debian translators contributed, which then got > put into the package by the Debian package maintainer > c) a former translation on Launchpad, which got exported manually by > the ubuntu package maintainer and put into that package before uploading > it into the archive. > > The only way to make sure the string really comes from the upstream > project is to compare it with the translations in the upstream project. > :) Usually, it's a) though. (It may also be that upstream used to use > that string, but has changed it in the meantime. In that case upstream > will probably have a higher version number of the software than we ship > in Ubuntu.) > > If the Ubuntu translation team chooses the "Packaged" string in > Launchpad, it means the string in the next (and further) language pack > will be the one which comes with the ubuntu package. Further package > upgrades may therefore change that string. > > If the "Current" and "Packaged" strings are not the same in Launchpad, > it means that string has been entered manually in Launchpad before. > > So, in order to "revert" the translation to what comes with the package, > simply set the string to "Packaged". The next language-pack update will > then carry that change. A specific case is the Norwegian Nynorsk (nn) translation of Rhythmbox, which was not previously translated upstream. I have updated the Launchpad translation (changing many of the existing translations) and committed the PO file both upstream and back to Launchpad. So the next time Rhythmbox is imported into Launchpad from upstream, it should get my new translation, which is also already in Launchpad. Currently, my updated translation is marked as 'Changed in Launchpad', since as far as LP knows, there is no upstream translation. Will LP detect the new upstream translation and give them precedence automatically, or will the LP translations (which currently are identical to upstream) take precedence? Since Rhythmbox has ~1k strings, clicking 'packaged' in LP on every one is not “simply” :) > For Maverick (the current development release), these language pack > updates will go into the archive automatically until the final release. > For stable releases, these updates will go into the PPA and you (your > team) will need to request us to copy the language pack update over into > the archive manually once you have tested it and you are satisfied. > > In case the "Current" and "Packaged" strings are both not preferred and > the upstream project carries the preferred string in the meantime, the > best way would be: > 1. check if the package version the the current ubuntu development > release is the same like upstream -> if yes, the proper translation > should get imported into Launchpad for Maverick. It should be listed as > a suggestion for stable Ubuntu releases then (may be only after Maverick > was opened for translations, I'm not sure about that). > If this is the case, just choose that suggestion for stable ubuntu releases. > 2. If it doesn't show up as suggestion in stable ubuntu releases, > enter the string manually. > >> You can find more info on translation precedence in La
Re: How to revert to upstream translations
2010/7/14 Arne Goetje : > Sorry, Milo, I need to correct you here. :) No worries at all, thanks for the clarification! That means I always got it wrong! :) (and it also clarifies me some of the "strange" behaviors I thought it had!) Are these information written somewhere in our wiki pages? If not, I think they should really be. Ciao. -- Milo Casagrande -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: How to revert to upstream translations
Sorry, Milo, I need to correct you here. :) On 07/13/2010 08:38 PM, Milo Casagrande wrote: > 2010/7/13 Åsmund Skjæveland: >> Sorry if this is a repeat, this one never came back to me. > > I think it's the first time I see this message, so this should be the > first one! ;-) > >> 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, it should do so. If it's not working that could be a problem. No. (see below) Although, if you do that in the development release of Ubuntu and a new version of that package gets uploaded later and carries the same string, Launchpad may flip over to the "Packaged" one... I wouldn't rely on that, though. >> 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? > > The "Current..." one is the actual translation for that string, be it > upstream or of your team. The "Current" one is the string which is currently exported into the langpacks. >> I assume "Packaged" is the last string that was included in a >> langpack. > > Exactly. Packaged is the string that was shipped with the last > langpack, it doesn't mean that that string is upstream though. No, "Packaged" means that that string came with the ubuntu package of that application and got imported into Launchpad from there. This means, that the "Packaged" translation can be a) the one which the upstream project (of the same version) uses b) the one which the Debian translators contributed, which then got put into the package by the Debian package maintainer c) a former translation on Launchpad, which got exported manually by the ubuntu package maintainer and put into that package before uploading it into the archive. The only way to make sure the string really comes from the upstream project is to compare it with the translations in the upstream project. :) Usually, it's a) though. (It may also be that upstream used to use that string, but has changed it in the meantime. In that case upstream will probably have a higher version number of the software than we ship in Ubuntu.) If the Ubuntu translation team chooses the "Packaged" string in Launchpad, it means the string in the next (and further) language pack will be the one which comes with the ubuntu package. Further package upgrades may therefore change that string. If the "Current" and "Packaged" strings are not the same in Launchpad, it means that string has been entered manually in Launchpad before. So, in order to "revert" the translation to what comes with the package, simply set the string to "Packaged". The next language-pack update will then carry that change. For Maverick (the current development release), these language pack updates will go into the archive automatically until the final release. For stable releases, these updates will go into the PPA and you (your team) will need to request us to copy the language pack update over into the archive manually once you have tested it and you are satisfied. In case the "Current" and "Packaged" strings are both not preferred and the upstream project carries the preferred string in the meantime, the best way would be: 1. check if the package version the the current ubuntu development release is the same like upstream -> if yes, the proper translation should get imported into Launchpad for Maverick. It should be listed as a suggestion for stable Ubuntu releases then (may be only after Maverick was opened for translations, I'm not sure about that). If this is the case, just choose that suggestion for stable ubuntu releases. 2. If it doesn't show up as suggestion in stable ubuntu releases, enter the string manually. > You can find more info on translation precedence in Launchpad here: > https://wiki.ubuntu.com/Translations/KnowledgeBase/TranslationsPrecedence > > Hope it can be of some help. > > Ciao. > 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
2010/7/13 Åsmund Skjæveland : > Sorry if this is a repeat, this one never came back to me. I think it's the first time I see this message, so this should be the first one! ;-) > 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, it should do so. If it's not working that could be a problem. > 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? The "Current..." one is the actual translation for that string, be it upstream or of your team. > I assume "Packaged" is the last string that was included in a > langpack. Exactly. Packaged is the string that was shipped with the last langpack, it doesn't mean that that string is upstream though. You can find more info on translation precedence in Launchpad here: https://wiki.ubuntu.com/Translations/KnowledgeBase/TranslationsPrecedence Hope it can be of some help. Ciao. -- Milo Casagrande -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
How to revert to upstream translations
Sorry if this is a repeat, this one never came back to me. -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: How to revert to upstream translations
Le mardi 20 janvier 2009 à 10:11 +0100, henn...@ubuntu.com a écrit : > - I am currently working on two implementations that will help with > these issues: > https://blueprints.launchpad.net/rosetta/+spec/link-to-style-guide > https://blueprints.edge.launchpad.net/rosetta/+spec/export-changed-in-launchpad > Both are scheduled to be in the new release next week. Thanks, I think this is a step in the right direction! At least contributors will easily find where they need to go to get informations. Exporting translations towards upstream is really nice too, but generally ours are of poor quality because many different people worked on the same domain and they are often unexperienced. But it can help new projects to get translated. -- 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 Milo, У уто, 20. 01 2009. у 02:42 -0700, Milo Casagrande пише: > Following on what you said on the previous mail, probably the "Packaged" > term could lead to some misunderstanding. IMHO, probably, we are more > accustomed to "usptream" and "downstream" kind of terms. > > Just a suggestion: would it be possible to change that definition to > "Upstream" instead of "Packaged" and with the glossary blueprint [1] we > discussed at UDS insert the term "Upstream" in the glossary and link it? > Or at least, if changing the term is not feasible, would it be possible > to link "Packaged" using the glossary thing? Not really. "Upstream" is a confusing term, especially when used in the Launchpad context (Launchpad uses "upstream" to also indicate projects which are directly hosted in Launchpad). Apart from that, it's not even correct (Ubuntu package might not exactly match upstream). We've thought about how to best name this, and never came up with the better name. The other best alternative we came up with was "Imported", but we figured that was going to confuse more people if displayed in the UI (i.e. was that stuff that was imported that I uploaded, or imported from the package/upstream). Cheers, Danilo -- 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 20/01/09 10:42, Milo Casagrande wrote: > Just a suggestion: would it be possible to change that definition to > "Upstream" instead of "Packaged" and with the glossary blueprint [1] we > discussed at UDS insert the term "Upstream" in the glossary and link it? > Or at least, if changing the term is not feasible, would it be possible > to link "Packaged" using the glossary thing? > Well, as was explained somewhere else in the thread, "packaged" is not always the same as "upstream" because it is referring to the Ubuntu package which may have been patched (English strings changed or added) in relation to upstream. I think explaining the term is the better option here. Henning -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: How to revert to upstream translations
> Original Message > Subject: Re: How to revert to upstream translations > From: henn...@ubuntu.com > Date: Tue, January 20, 2009 10:28 am > > Sorry, I had sorted my mails incorrectly and missed the fact that others > from the team had already replied. Please excuse the extra noise if I > repeated things that had already been said. Repetita juvant! :) Following on what you said on the previous mail, probably the "Packaged" term could lead to some misunderstanding. IMHO, probably, we are more accustomed to "usptream" and "downstream" kind of terms. Just a suggestion: would it be possible to change that definition to "Upstream" instead of "Packaged" and with the glossary blueprint [1] we discussed at UDS insert the term "Upstream" in the glossary and link it? Or at least, if changing the term is not feasible, would it be possible to link "Packaged" using the glossary thing? Cheers. [1] https://lists.ubuntu.com/archives/ubuntu-translators/2008-December/001997.html -- Milo Casagrande -- 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 20/01/09 10:11, henn...@ubuntu.com wrote: > Thank you Milo for pointing that out in this context. Danilo gave some > good examples on how things work now and I hope all read it. > > As for the current thread, let me add a few clarifications: > Sorry, I had sorted my mails incorrectly and missed the fact that others from the team had already replied. Please excuse the extra noise if I repeated things that had already been said. Henning -- 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 18/01/09 21:45, Milo Casagrande wrote: > I just quote from last Danilo message regarding this aspect: > > > The original thread is here: > > https://lists.ubuntu.com/archives/ubuntu-translators/2008-December/001994.html > Thank you Milo for pointing that out in this context. Danilo gave some good examples on how things work now and I hope all read it. As for the current thread, let me add a few clarifications: - "Packaged" means "imported from upstream" and has nothing to do with language packs. I hope that this misunderstanding is not too common. If you select a "packaged" version of a translation, you are reverting it to the translation that was provided from upstream. - As Danilo describes, translations imported from upstream only overwrite those made in Launchpad if this is the first translation upstream provides (as of December). In the case of updated translations from upstream, they do *not* overwrite changes made in Launchpad. The intended use is to be able to override upstream translations for Ubuntu or to quickly fix errors in the upstream translation. We assume, as Danilo describes, that the overridden translations are discussed with the upstream project and that fixes are provided back to upstream so that on the next import from upstream those messages match the ones made in Launchpad. - Please re-think the phrase "Launchpad does this, Launchpad does that". Launchpad is a tool, the translations are done by dedicated translators, they are the "doers" and they are trying their best. I know at least for the German team (and I guess that others are the same) that they have a policy not to touch upstream translations unless there is a good reason for that. Translators wanting to translate an application into a new language are pointed to the upstream project to do that work. Also, translations are not "open" for Ubuntu, meaning that not anybody can change translations from upstream, they need approval from regular team members first who watch that their policies are met. - I am currently working on two implementations that will help with these issues: https://blueprints.launchpad.net/rosetta/+spec/link-to-style-guide https://blueprints.edge.launchpad.net/rosetta/+spec/export-changed-in-launchpad Both are scheduled to be in the new release next week. Henning -- 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 Mon, Jan 19, 2009 at 10:05 AM, Danilo Šegan wrote: > Case 1 has been correctly tracked for a long time (i.e. forever, or at > least since I've been around: i.e. if you revert to the packaged > translation by using the same string, Launchpad would continue to prefer > updates from the package). > > Case 2 has been made automatic recently (December 2008). Thanks for clarifying this Danilo. 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
У пон, 19. 01 2009. у 08:00 -0500, Og Maciel пише: > On Mon, Jan 19, 2009 at 6:06 AM, Danilo Šegan wrote: > >> 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. > > > > Actually, this has been in for over a year. Looking at [1], I'd say > > exactly since 2007-06-08, and 1.1.6 release (June 2007). > > Right, but the real problem happens when someone decides to change > something that came from upstream (case 1) OR adds a new translation > for a string that had none (case 2). The next time Rosetta imports > translations from upstream, it will no longer track these two cases, Case 1 has been correctly tracked for a long time (i.e. forever, or at least since I've been around: i.e. if you revert to the packaged translation by using the same string, Launchpad would continue to prefer updates from the package). Case 2 has been made automatic recently (December 2008). What I talked about was UI that helped detect both cases which has been around for a little less time. Cheers, Danilo -- 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 Mon, Jan 19, 2009 at 6:06 AM, Danilo Šegan wrote: >> 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. > > Actually, this has been in for over a year. Looking at [1], I'd say > exactly since 2007-06-08, and 1.1.6 release (June 2007). Right, but the real problem happens when someone decides to change something that came from upstream (case 1) OR adds a new translation for a string that had none (case 2). The next time Rosetta imports translations from upstream, it will no longer track these two cases, giving the translation done via Rosetta higher "priority", right? If this is still the case, the problem is not always because Rosetta translators *rather* use their own translations, but because they may not know any better. I assume that if they all knew that they would be overriding the upstream work, they would either fix it upstream (the optimal solution imnsho) or send in a patch. 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
Hi Dominique, У нед, 18. 01 2009. у 20:44 +0100, Dominique Pelle пише: > 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? That's how it works today. > I've done translations upstream, which have been reviewed and I'd > be a bit disappointed if they were badly altered in Ubuntu. Some were unintentionally altered in the past. That should happen no more. "Changed in Launchpad" filter on individual translate pages (and a count of "Changed" on overview pages) can help you find any translations that have been altered in this way. If you want to revert them, use the "Packaged" one (that's the one that is most likely from upstream). Cheers, Danilo -- 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 Og, others, У нед, 18. 01 2009. у 15:10 -0500, Og Maciel пише: > 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. Actually, this has been in for over a year. Looking at [1], I'd say exactly since 2007-06-08, and 1.1.6 release (June 2007). And to confirm Milo's statement, yes, that's exactly how this will work. "Packaged" is whatever is coming from an Ubuntu package (i.e. for most purposes when there are no significant patches in Ubuntu, the same as "upstream"), not what was in the last language pack. Cheers, Danilo [1] https://bugs.launchpad.net/rosetta/+bug/32471 -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: How to revert to upstream translations
Milo Casagrande wrote:
> 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.
Thanks Milo for bringing this quote in. To be clear:
1. If the currently selected translation for a message in Launchpad is
the one that was last imported from upstream, then that message will
"track" upstream. So if a later import from upstream changes the
translation, Launchpad will also use that new translation. This has
always(1) been the case.
2. If the Ubuntu translation team has chosen to diverge from the
upstream translation, then the translation in Launchpad overrides the
upstream translation. It continues doing so until either the Ubuntu
translation or upstream decides to use the same text as the other.
That's why translation teams should do this only if the upstream
translation is buggy, or requires an Ubuntu-specific translation
different from the upstream one. Launchpad/Rosetta has no way of
guessing the team's reasons. For the "buggy" case, of course the
translation team would do well to report to upstream.
3. The situation Danilo is referring to is this one: upstream does not
translate a particular message, but Launchpad does. Then, upstream does
add a translation of its own for that message, and the new translation
is imported. In this case Launchpad does guess the reason why it had a
different translation than upstream: because upstream didn't have one.
And so it switches to tracking the upstream translation in this case.
It's this last part that's new(2).
Jeroen
(1) Well, I happen to know it wasn't the case during the late
Pleistocean, for example, but grant me some artistic license here.
(2) To put this in perspective: the late Pleistocean is very old. This
feature came more sort of late 2008-ish.
--
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
