2012/9/18 Justin B Rye <jbr@edlug.org.uk>: > If you have already sent an [ITT] message, and somebody else then > sends another [ITT] for the same file... Fixed. > So if Alice and Bob happen to send colliding ITTs more or less > simultaneously, they then *each* need to send an immediate "reminder" > to the list as well, reiterating their claim? This sounds like an > annoying rule. It's the behavior on the french localisation mailing list. It's not a general rule and does not apply to other localisation team. I removed it and I'll keep it in the french file. > I would again suggest a subtler tweak: underline the function of ITTs > as a way of "reserving" tasks. > > Sent to register a claim on a translation that you plan to work on; > used to avoid double work. Fixed. > Trying to whittle it down to one clear example: > > Used to put a translation on hold when there's a danger that > any work done now may be wasted, for example when problems > have been found that require changes in the original text. Pasted in the new version of the file. > David Prevot writes: > Changing the <ul> <li> stuff in <dd> > <dt> makes it harder to read the initial diff, but since the page is > only translated in French for the moment, that's not a big deal. > I added David Prévot's patch too. Using a definition term (dt tag) seems more logical to me than an unordered list (ul). I applied your patch too. David and Justin, thanks for your reviews! -- Imprimez ce message en A2 et en couleur au moins 500 fois! Brûlez des arbres!! -- envoyé depuis ma centrale à charbon Stéphane
#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> must be one of the following:
TAF, MAJ, ITT, RFR, LCFC, BTS#<bug number>, DONE, or HOLD.
</p>
<dl>
<dt>
<tt>TAF</tt> (<i>Travail À Faire</i>)
</dt>
<dd>
Sent by a <strong>coordinator</strong> (not by a random list member) to
indicate that there is a document that needs to be worked on.
</dd>
<dt>
<tt>MAJ</tt> (<i>Mise À Jour</i>)
</dt>
<dd>
Sent by a <strong>coordinator</strong> (not by a random list member) to
indicate that there is a document that needs to be updated
and that the work is reserved for the previous translator.
</dd>
<dt>
<tt>ITT</tt> (Intent To Translate)
</dt>
<dd>
Sent to register a claim on a translation; used to
avoid double work.<br />
</dd>
<dt>
<tt>RFR</tt> (Request For Review)
</dt>
<dd>
An initial draft translation is attached. Others on the list are
requested to check it for errors and send a reply (possibly
off-list if they found no flaws).<br />
Further RFRs may follow if substantial changes have been made.
</dd>
<dt>
<tt>ITR</tt> (Intent To Review)
</dt>
<dd>
Used to avoid LCFCs being sent when there are reviews pending.<br />
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.)<br />
The mail body should contain an indication of when to expect the
review.<br />
Note that ITR pseudo-URLs are ignored by the spider.<br />
</dd>
<dt>
<tt>LCFC</tt> (Last Chance For Comment)
</dt>
<dd>
Indicates that translation is finished, with changes from the
review process incorporated, and that it will be sent to the
appropriate place.<br />
Can be sent when there are no ITRs, and discussion following the
last RFR has ended for a few days.<br />
Should not be sent before there has been at least one review.
</dd>
<dt>
<tt>BTS#<bug number></tt> (Bug Tracking System)
</dt>
<dd>
Used to register a bug number once you have submitted the
translation to the BTS.<br />
The spider will regularly check if an open bug report has been
fixed or closed.
</dd>
<dt>
<tt>DONE</tt>
</dt>
<dd>
Used to close a thread once the translation has been dealt with;
useful if it has not been sent to the BTS.
</dd>
<dt>
<tt>HOLD</tt>
</dt>
<dd>
Used to put a translation on hold when there's a danger that
any work done now may be wasted, for example when problems
have been found that require changes in the original text.
</dd>
</dl>
<p>
The <i>type</i> can be anything indicating the type of the document, such as
po-debconf, debian-installer, po, po4a, or wml.
</p>
<p>
<i>package</i> is the name of the package that 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
to uniquely identify the document, such as the path to the file.
It's usually a name like <i>lc</i>.po where <i>lc</i> is the language code
(e.g.: <i>de</i> for German, or <i>pt_BR</i> 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 since it's used
on these web pages to track the status of translations,
it's strongly recommended to follow the scheme given below.
</p>
<ul>
<li><code>debian-installer://package-name/path-in-sourcepackage/lc.po</code> (for the installer)</li>
<li><code>ddp://document/filename.po</tt> (for Debian documentation)</li>
<li><code>xml://installation-guide/lang/path-in-sourcepackage/file.xml</tt> (for the installation guide)</li>
<li><code>po://package-name/path-in-sourcepackage/lc.po</code> (for classical po file)</li>
<li><code>po-debconf://package-name/lc.po</code> (for installer configuration interface)</li>
<li><code>po4a://package-name/path-in-sourcepackage/lc.po</code> (for documentation converted to po format)</li>
<li><code>wml://path_under_language_name_in_CVS</code> (for web site pages)</li>
</ul>
<p>
The BTS state is somewhat special; it registers a bug number so the
l10n-bot can track the status of the translation once submitted to
the BTS by checking whether any of the open bug reports have been
closed. Thus for instance the debian-l10n-spanish list might use:
</p>
<div class="center"><code>[BTS#123456] po-debconf://cups/es.po</code></div>
<p>
If you intend to translate a lot of packages, you can ITT them all
at once. An example (for the debian-l10n-danish list):
</p>
<div class="center"><code>[ITT] po-debconf://{cups,courier,apache2}/da.po</code></div>
<p>
So put the packages between braces and separate them with commas. No
extra spaces!
</p>
Attachment:
modif_3.pseudo-urls.wml.diff
Description: Binary data