Hey Ruediger,<div><br></div><div>I just want to say to you that I have not forgoten your translation requirement. I keep it in my mind.</div><div><br></div><div>Kind regards</div><div>Christian Ponce<br><br><div class="gmail_quote">
2010/5/15 Ruediger Landmann <span dir="ltr"><<a href="mailto:r.landmann@redhat.com">r.landmann@redhat.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi all --<br>
<br>
Just a note that Publican 1.6.3 will be in the repos shortly. This is a<br>
major bugfix release with fixes for around 20 issues including quite a<br>
few that specifically impact localization:<br>
<br>
580360 - Publican does not allow programlisting/screen in entry<br>
581397 - Updating zero-length PO files causes Publican to create<br>
corrupted PO files<br>
581773 - a manual page reference should not break a paragraph for<br>
translations / PO files<br>
582255 - <indexterm> is not translatable when outside of <para><br>
582649 - Some translated strings are not used, problem with non-breaking<br>
space?<br>
582680 - <indexterm> should be standalone in a translation<br>
583224 - <keyword> should be translatable<br>
<br>
The net effect of these fixes is that Publican now presents some strings<br>
to translators that it did not present before (such as <keyword>,<br>
<indexterm>, and the contents of <screen> and <programlisting>), and<br>
divides some strings in PO files differently from how it did before (for<br>
example, not breaking English strings into three separate strings around<br>
<refentrytitle>). These changes should make life easier for translators<br>
in future, and allow them to produce more complete translations.<br>
<br>
As we approach the final push towards Fedora 13, it's really important<br>
that Docs team members keep the POT (and therefore PO) files stable for<br>
translators -- we don't want to shift the goalposts.<br>
<br>
Therefore, do NOT use Publican 1.6.3 to refresh POT files for documents<br>
already in translation. If you do so, it is very likely that you will<br>
break existing translations.<br>
<br>
If you do need to update or change POT files for an existing document<br>
(which at this stage should require permission from the Localization<br>
Team anyway) make sure that you use Publican 1.6.2.<br>
<br>
However, if you need to generate or refresh PO files for some reason<br>
(for example, to add a new language for a document), it's fine to use<br>
1.6.3: the changes in Publican only affect XML-to-POT, not POT-to-PO.<br>
<br>
Cheers<br>
Rudi<br>
<font color="#888888"><br>
--<br>
trans mailing list<br>
<a href="mailto:trans@lists.fedoraproject.org">trans@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/trans" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/trans</a><br>
</font></blockquote></div><br><br clear="all"><br>-- <br>...la mala-copa no es un estado, es un estilo de vida.<br>
</div>