On 01/10/2014 03:12 AM, Ludovic Courtès via RT wrote:
 >>
 >> (0) when a new (or corrected) translation is committed to www, www
 >> translators send updates to TP, and they merge it to their PO files;
 >>
 >> (1) when a new translation is submitted to TP, the translators send
 >> a copy to the respective www.gnu.org translation team (or
 >> web-translators@gnu.org if that team doesn't maintain blurb
 >> translation for some reason); of course, TP translators should know
 >> what strings are blurbs.
 >
 > Sounds good.
 >
 > What would it take exactly to inform the TP folks of the process?

Discuss with coordinator@translationproject.org, I think; they may add
their own adjustments to the procedure before actually announcing it
to the translators.

 >> However, there is a technical problem: www translations are in HTML,
 >> while guix uses plain text. it's easy to transform plain text to HTML;
 >> the reverse conversion seems missing.
 >
 > Seems to me that the only difference in the translated strings is that
 > the www ones have something like this at the end:
 >
 >   <small>(<a href="/manual/manual.html#pkg_3dldf\">doc</a>)</small>
 >
 > Would it be possible somehow to remote that link from the translatable
 > strings?

But they are translatable; what may make sense is separating them
to their own msgids (also, "This package is looking for a maintainer.").

GNUN has a means to do it when the strings can't come, say, in separate
paragraphs, <span class="gnun-split"></span>, like on the home page [0],
so this could be implemented like in the attachment.

Then, there are also <tt>s (which may "translate" into something
different, like <code> or <em>) and a few other substitutions [1].
I wonder whether it would be easier if guix used HTML in PO files and
converted it to plain text when needed; this way, no exact reverse
conversion would be necessary.

[0] https://www.gnu.org/home.en.html
[1] http://cvs.savannah.gnu.org/viewvc/gnumaint/gm-generate.pl?root=womb&view=markup