Le mercredi 22 mars 2017 11:02:09 CET, vous avez écrit : > Jean-Noël Avila <jn.avila@xxxxxxx> writes: > >> I am wondering if Documentation/po part should be a separate > >> repository, with a dedicated i18n/l10n coordinator. Would it make > >> it easier for (1) those who write code and doc without knowing other > >> languages, (2) those who update .pot and coordinate the l10n effort > >> for the documentation and (3) those who translate them if we keep > >> them in a single repository? > > > > This is one of the points raised in the first RFC mail. Splitting this > > part would help a lot manage the translations with their own workflow, > > would not clutter the main repo with files not really needed for > > packaging and would simplify dealing with the interaction with crowd > > translation websites which can directly push translation content to a > > git repo. > > As I was in favor of splitting it out, I was trying to gauge what > the downside of doing so would be, especially for those who are > doing the translation work (it is obvious that it would help > developers who are not translators, as nothing will change for them > if we keep this new thing as a separate project). There's one big downside of this splitting. The gitman-l10n project would not be autonomous without the specific cloning at the particular place in the git project. po4a needs the original asciidoc files to perform the transclusion of the translated content into the structure of the documents. The setup that you are proposing would rule out simple CI checks and would make it complicated for the translators to set up their working copy and check the resulting man pages. As I see it, there's the need for the Documentation folder to be contained in both project (while remaining the property of the git project). So I would think the other way around: for those interested in translated the documentation, some script would allow to checkout the git project inside the gitman-l10n project (like a kind of library). This would be mainly transparent for the git developers. > I'd prefer to start with the "optional gitman-l10n repository is > checked out at Documentation/po only by convention" approach, before > committing to bind it as a submodule. Once we got comfortable with > cooperating between these two projects, we do want to bind them > using the submodule mechanism, but not before. Obviously, my proposition would not allow to evolve towards such a setup, but is it really needed anyway ?