Hi, Le 10/08/2012 13:59, Christian PERRIER a écrit : > Quoting David Prévot (da...@tilapin.org): > >> I'd rather propose to host it in the main website [4], so it can even be >> translated, and will proceed soon if no one stops me. […] > Nobody will stop you..:)
Here we go! Thanks in advance for your reviews of the soon to come page
that will replace the l10n.d.o one [1] (I just fixed some typos and
adapted it a bit). It's published on my test server [2], do not hesitate
to propose huge modifications, or to rewrite it completely if you're in
a good mood ;).
1: http://l10n.debian.org/coordination/01static/pseudo-urls.html
2: http://www.tilapin.org/debian/international/l10n/pseudo-urls
Regards
David
#use wml::debian::template title="Coordination of l10n teams"
<h1>Pseudo-URLs</h1>
<p>
The program that listens to debian-l10n-* lists understands pseudo-URLs in the
subject header.
The pseudo-URLs need to have the following form.
</p>
<div class="center"><code>[<state>] <type>://<package>/<file></code></div>
<p>
The <i>state</i> can be one of the following: TAF, ITT, RFR, LCFC,
BTS#<bug number> or DONE.
</p>
<ul>
<li>TAF (<i>Travail à Faire</i>)
<ul>
<li>Sent to indicate that there is a document that needs to be worked
on.</li>
</ul>
</li>
<li>MAJ (<i>Mise à Jour</i>)
<ul>
<li>Sent to indicate that there is a document that needs to be updated
and that the work is reserved for the previous translator.</li>
</ul>
</li>
<li>ITT (Intent To Translate)
<ul>
<li>Sent to indicate that you plan to work on the translation, used to
avoid double work.</li>
</ul>
</li>
<li>RFR (Request For Review)
<ul>
<li>Initial translation is done and, attached to the mail, others on
the list can then go over it to check for errors.</li>
<li>Possibly followed by other RFR when substantial changes have been
made.</li>
<li>NOTE: send a reply, eventually off-list if you checked it and found
no flaws.</li>
</ul>
</li>
<li>ITR (Intent To Review)
<ul>
<li>Used to avoid LCFC's being sent when there are pending reviews
out.</li>
<li>Mainly used when you expect your review not to be ready for several
days (because the translation is big, or you don't have any time
before the weekend, etc.)</li>
<li>Mail body should contain an indication of when to expect the
review.</li>
<li><b>NOTE</b>: Not parsed by the spider.</li>
</ul>
</li>
<li>LCFC (Last Chance For Comment)
<ul>
<li>Indicates that translation is done, change from the review process
have been incorporated, and translation will be send to the
appropriate place.</li>
<li>Can be sent when there are no ITR's, and discussion following the
last RFR has ended for a few days.</li>
<li>Should not be sent before there has been at least one review.</li>
</ul>
</li>
<li>BTS#<bug number> (Bug Tracking System)
<ul>
<li>Used to register a bug number once you submitted the translation to
the BTS.</li>
<li>Regularly the spider will check if an open bug report has been
fixed or closed.</li>
</ul>
</li>
<li>DONE
<ul>
<li>Used to close a thread once the translation has been taken into
account, useful if it has not been sent to the BTS.</li>
</ul>
</li>
<li>HOLD
<ul>
<li>Used to put a translation on hold, when the original version has
changed but there is no need to update the translation, e.g. you
know other modifications will be done soon on the original and
you don't want someone to update the translation too quickly.</li>
</ul>
</li>
</ul>
<p>
The <i>type</i> can be anything indicating the type of the document, e.g.:
po-debconf, debian-installer, po, po4a, or wml.
</p>
<p>
<i>package</i> is the name of the package where the document comes from.
Please use <i>www.debian.org</i> or nothing for the WML files of the
Debian web site.
</p>
<p>
<i>file</i> is the filename of the document, it can contain other information
such as the path to the file so no other
document in the same package should be referred the same.
It's usually a name like <i>lc</i>.po where <i>lc</i> is the language code
(e.g.: de for German, or pt_BR for Brazilian Portuguese).
</p>
<p>
The structure of <i>file</i> depends on the chosen type, and of course the
language.
In principle it's just an identifier, but it's strongly recommended to follow
the following rules, since it's used to update page status of this section.
</p>
<ul>
<li><code>po-debconf://package-name/lc.po</code></li>
<li><code>po://package-name/path-in-sourcepackage/lc.po</code></li>
<li><code>debian-installer://package-name/path-in-sourcepackage/lc.po</code></li>
<li><code>wml://path_under_language_name_in_CVS</code></li>
<li><code>po4a://package-name/path-in-sourcepackage/lc.po</code></li>
</ul>
<p>
The state BTS is somewhat special, it used to register a bug number so the
l10n-bot can track the status of the translation once submitted to
the BTS: it will check if any of the open bug reports have been
closed. An example of this command is (for the debian-l10n-spanish list):
</p>
<div class="center"><code>[BTS#123456] po-debconf://cupsys/es.po</code></div>
<p>
If you have the intent to translate a lot of packages, you can ITT them all
at ones. An example (for the debian-l10n-danish list):
</p>
<div class="center"><code>[ITT] po-debconf://{cupsys,courier,apache2}/da.po</code></div>
<p>
So put the packages between curly braces and separate them with comma's. No
extra spaces!
</p>
signature.asc
Description: OpenPGP digital signature
