<br><div><span class="gmail_quote">2007/4/20, Dimitris Glezos <<a href="mailto:dimitris@glezos.com">dimitris@glezos.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
O/H Diego Búrigo Zacarão έγραψε:<br>> Hello, all..<br>><br>> I have some doubts about translation credits and I hope that someone can<br>> explain it to me.<br>><br>> 1 - About msgid "translator-credits" in all PO files. I suppose we must
<br>> put one translator per line, in the form of:<br>> NAME <EMAIL>, YEAR. (right?)<br>> So, where that will appear? I have checked some modules GUI like<br>> system-config-* and I did't see it anywhere.
<br><br>I'm glad you brought this up Diego. We've discussed it in the past (also in<br>FOSDEM with some other translators) and everyone agrees that it is a good thing<br>to give credit to Authors and Translators. FWIW, all GNOME apps have this in the
<br>"Help -> About" menu.<br><br>Concerning Fedora applications we need to:<br><br> 1. Open bug reports for apps that don't give credits to translators (and<br>authors) as a part of their GUI.<br><br> 2. Some apps don't even have a "translator-credits" msgid in their POT, so
<br>mention this in those bug reports as well.<br><br>We need a volunteer to do this. Diego, how about giving it a try? :)</blockquote><div><br>I will see if L10N brazilian team can do something around it.<br>Igor Soares, what about it?
<br><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Someone from us could even grab the source of some apps and produce patches on
<br>the bug reports; the chances to achieve what we want increase dramatically.<br><br>> 2 - The same problem above happen on CVS Docs. We have the msgid<br>> "translator-credits" in PO files, but it is't displayed on pages
<br>> published at <a href="http://docs.fedoraproject.org">docs.fedoraproject.org</a> <<a href="http://docs.fedoraproject.org">http://docs.fedoraproject.org</a>>.<br>> However we have some confused things here, because some modules, like
<br>> mirror-tutorial <<a href="http://docs.fedoraproject.org/mirror/">http://docs.fedoraproject.org/mirror/</a>>, shows names of<br>> translators as author, cause they were added in rpm-info.xml in<br>> <colophon> tag. But, in other modules, like install-guide
<br>> <<a href="http://docs.fedoraproject.org/install-guide/fc6/">http://docs.fedoraproject.org/install-guide/fc6/</a>>, this does't happened.<br>> Then... What's the right thing to do?<br><br>The right thing to do is have translators in "translator-credits" and create a
<br>"colophon" section that prints out this string. We have two choices here, the<br>way I see it:<br><br> 1. List all translators in all languages' documents. To do this, the author<br>should maintain a list of the translators in the POT file itself (see:
<br>release-notes).</blockquote><div><br>I think we must have all translators in all language's docs, because some translations of languages can be based in another language. It's very common between "portuguese" and "brazilian portuguese", cause they no have many diferences.
<br><br>A separate section for Contributor Credits as Paul have said, it's very interesting. I guess it the best way to improve it. But I suppose that it is not necessary put all contributor credits names in POT/PO to be translated. Just put in
rpm-info.xml (or any another file) it's enough.<br>My name must be write "Diego Búrigo Zacarão" in any language. No?<br><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2. Each localized document lists its own translators. The msgid in the POT is<br>empty and each language fills in the PO its own translators.<br></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Once we decide, we need to open bug reports for all affected docs (so that we
<br>know what's fixed and what's not yet) and someone in the `cvsdocs` group could<br>go ahead right away and fix it.<br><br>-d<br><br><br>--<br>Dimitris Glezos<br>Jabber ID: <a href="mailto:glezos@jabber.org">glezos@jabber.org
</a>, GPG: 0xA5A04C3B<br><a href="http://dimitris.glezos.com/">http://dimitris.glezos.com/</a><br><br>"He who gives up functionality for ease of use<br>loses both and deserves neither." (Anonymous)<br>--<br><br>
</blockquote></div><br>Best Regards<br clear="all"><br>-- <br>Diego Búrigo Zacarão<br>Linux User #402589<br>USE SOFTWARE LIVRE