Hi, Thanks Justin for your review and explanations. I started back from your last version. Most of your assumptions were right about the intent, I just reply to the things I changed from your proposal. Le 11/08/2012 04:46, Justin B Rye a écrit : > David Prévot wrote: >> <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>Indicates that the translation is finished, with changes from the > review process incorporated, and that it will be sent to the > appropriate place.</li> Your file added back the “changes […] have been” form, I guess it was not intentional, so I pushed back your inline version (“with […]”). >> <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> > > That "e.g." is hardly an example - it's just a paraphrase of the > general description. Or possibly even a contradiction; the first > version implies there's no work to be done, the second implies there's > work to be done but it would be wasted effort. Maybe: > > <li>Used to put a translation on hold, when the original version has > changed or is about to change and any work done on updates now is > likely to be wasted.</li> There are actually other use for HOLD, like tagging a translated file handled elsewhere (installation-guide can be handle in PO file, but the current French translators prefers to edit directly the XML, so it's tagged to avoid someone begins to translate the PO file), or if the PO files are not supposed to be translated (lintian ships PO files for its test suite). They are not worth mentioning in the page (documenting every corner case would make the page huge for no good reason), but that was the purpose of the “e.g.”. Not sure how to word it to let the readers assume they could use “HOLD” for something else though. http://www.debian.org/international/l10n/po/fr The proposed version was also problematic: “when the original version has changed *or* is about to change”: if “the original version has changed”, the translation should be updated, but if it “is about to change”, we should wait. A good example is if a new template has been introduced in the archive, but a review is in progress on d-l10-english. I went on with: Used to put a translation on hold, when the original version has changed and is about to change again, so any work done on updates now is likely to be wasted. maybe “Used for example to put […]” could do the trick? >> <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> > > What "following rules"? And what does "page status of this section" > mean? Maybe something like: > > In principle it's just an identifier, but since it's used to track page > status it's strongly recommended to follow the scheme given below. I meant the status pages from http://www.debian.org/international/l10n (where this web page will be introduced), like the French one about PO files that contains some HOLD examples. I've reworded it this way, hope I didn't introduced too much flaws: In principle it's just an identifier, but since it's used to track the translation status in the web pages of this section, it's strongly recommended to follow the scheme given below. > Oh, and... it says that the state should be one of a given list, but > that list doesn't mention MAJ, ITR, or HOLD. So shouldn't those all > have the same note about being ignored by the spider? Actually, I added MAJ and HOLD to the list, since they're recognized by the spider. Thanks in advance for your other reviews. 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> must be one of the following:
TAF, MAJ, ITT, RFR, LCFC, BTS#<bug number>, DONE, or HOLD.
</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>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).</li>
<li>Further RFRs may follow if substantial changes have been made.</li>
</ul>
</li>
<li>ITR (Intent To Review)
<ul>
<li>Used to avoid LCFCs being sent when there are reviews pending.</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>The mail body should contain an indication of when to expect the
review.</li>
<li>Note that ITR pseudo-URLs are ignored by the spider.</li>
</ul>
</li>
<li>LCFC (Last Chance For Comment)
<ul>
<li>Indicates that translation is finished, with changes from the
review process incorporated, and that it will be sent to the
appropriate place.</li>
<li>Can be sent when there are no ITRs, 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 have submitted the
translation to the BTS.</li>
<li>The spider will regularly 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 dealt with;
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 and is about to change again, so any work done on updates
now is likely to be wasted.</li>
</ul>
</li>
</ul>
<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.: 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 since it's used to
track the translation status in the web pages of this section,
it's strongly recommended to follow the scheme given below.
</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 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:
signature.asc
Description: OpenPGP digital signature