I've noticed that translations of intro paragraph in "Fedora Live Images" do not appear in translated docs, although they do exist.
Anyone else seeing this?
Regards, Miloš
W dniu 29.05.2010 17:32, Miloš Komarčević pisze:
I've noticed that translations of intro paragraph in "Fedora Live Images" do not appear in translated docs, although they do exist.
Anyone else seeing this?
This is a known issue. We were using Publican 1.6.2 to build PO files and now we are using Publican 1.99 to publish them. This is causing some troubles with missing translations etc. I think Publican's developers are aware of this situation.
On 05/30/2010 05:10 AM, Piotr Drąg wrote:
W dniu 29.05.2010 17:32, Miloš Komarčević pisze:
I've noticed that translations of intro paragraph in "Fedora Live Images" do not appear in translated docs, although they do exist.
Anyone else seeing this?
This is a known issue. We were using Publican 1.6.2 to build PO files and now we are using Publican 1.99 to publish them. This is causing some troubles with missing translations etc. I think Publican's developers are aware of this situation.
Piotr's explanation is correct; and there are similar examples of unmatched strings scattered through many docs.
The solution is to refresh the POT and PO files of these docs using Publican 1.6.3 (currently released version) or 1.99 (same codebase as 1.6.3 but with the web publishing components included). We would not have made these changes at this time, except that 1.6.2 had some severe translation problems of its own. This process is certain to create many fuzzies, and probably break a few strings entirely. Running this process prior to GA when many teams were still working would have been far too disruptive.
Now that we're past GA, I'm happy to run this so that teams can eliminate these problems. I could either:
* refresh docs individually, as soon as any language team requests it
* just refresh any doc where there has been no translation activity after GA
Which would you guys prefer?
Cheers Rudi
написане Sun, 30 May 2010 00:17:33 +0300, Ruediger Landmann r.landmann@redhat.com:
On 05/30/2010 05:10 AM, Piotr Drąg wrote:
W dniu 29.05.2010 17:32, Miloš Komarčević pisze:
I've noticed that translations of intro paragraph in "Fedora Live Images" do not appear in translated docs, although they do exist.
Anyone else seeing this?
This is a known issue. We were using Publican 1.6.2 to build PO files and now we are using Publican 1.99 to publish them. This is causing some troubles with missing translations etc. I think Publican's developers are aware of this situation.
Piotr's explanation is correct; and there are similar examples of unmatched strings scattered through many docs.
The solution is to refresh the POT and PO files of these docs using Publican 1.6.3 (currently released version) or 1.99 (same codebase as 1.6.3 but with the web publishing components included). We would not have made these changes at this time, except that 1.6.2 had some severe translation problems of its own. This process is certain to create many fuzzies, and probably break a few strings entirely. Running this process prior to GA when many teams were still working would have been far too disruptive.
Now that we're past GA, I'm happy to run this so that teams can eliminate these problems. I could either:
refresh docs individually, as soon as any language team requests it
just refresh any doc where there has been no translation activity
after GA
Which would you guys prefer?
Cheers Rudi
Hi!
I would like the second option for Ukrainian. And please enable the submission for Jargon Buster. ;)
Thanks for your hard work.
Best regards, Yuri
On Sat, May 29, 2010 at 10:17 PM, Ruediger Landmann r.landmann@redhat.com wrote:
Now that we're past GA, I'm happy to run this so that teams can eliminate these problems. I could either:
refresh docs individually, as soon as any language team requests it
just refresh any doc where there has been no translation activity
after GA
Which would you guys prefer?
I don't really understand the implications of either option since I'll go through my translations anyway (only have 3 docs), so feel free to refresh all?
Milos
W dniu 29.05.2010 23:17, Ruediger Landmann pisze:
Now that we're past GA, I'm happy to run this so that teams can eliminate these problems. I could either:
refresh docs individually, as soon as any language team requests it
just refresh any doc where there has been no translation activity
after GA
Which would you guys prefer?
I'm fine with rebuilding Polish translations, so I could start updating them ASAP. I would even do it by myself, including publishing, but I'm getting "Permission denied (publickey)" errors when cloning repos. I'm a member of docs-writers group, so it's kind of weird.