Jean-Noël AVILA <jn.av...@free.fr> writes: >> ... Doesn't that workflow apply equally well for the >> documentation l10n? > > Theoretically, this workflow should apply to the documentation, so that a > version of the documentation can be cut at each release of git. I still have > to convince po4a not to update the *.pot and *.po files each time it is run, > while at the same time allow translators to produce the output file for > proofreading.
Ahh, OK, that does sound like a meaningful difference that may make the workflow we use for in-code strings not applicable for the documentation l10n project. As I said already, I am not married to the "gitman-l10n at Documentation/po" approach at all, and if the layout you brought up to turn the containment relationship the other way around works better, that is perfectly fine by me. Thanks.
