<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>C, else D, else B, never A</p>
<p id="reply-intro">On 2024-11-15 17:01, Albert Astals Cid wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Right now docs need to be generated manually by translators/team coordinators <br />and commited to the docs/ folder.<br /><br />This is something we don't communicate a lot and I'm sure some teams don't do <br />that, not your fault.<br /><br />Also it's relatively "easy" to commit broken docs that will break the <br />application compilation (again not your fault again, the tooling is a bit <br />fragile).<br /><br />One of the things we were discussing with Luigi is to automate the docs <br />compilation process.<br /><br />Everyone likes automation, so that's a good thing, BUT there is a "problem", <br />which is why we offloaded the compilation to humans in the first place.<br /><br />The problem is that our current system, a particular documentation needs to be <br />translated to 100% to be properly converted into an usable doc.<br /><br />The easy solution is to remove a doc once it stops compiling, but that doesn't <br />seem very optimal/fair because a single sentence would cause the doc to be <br />removed and my understanding is that it's better to have a doc somewhat old <br />doc translated than one with 0% translated.<br /><br />The other easy solution is never to remove a doc even if it fails to compile, <br />this can cause that the documentation gets SUPER OLD and then maybe it's not <br />better to have a SUPER OLD translated documentation compared to a non <br />translated documentation.<br /><br />The middle ground (which is what we do with GUI messages) is to always <br />generate the docs and if a particular string is missing use the English <br />version of the string, this way we always have the newest documentation, as <br />much translated as possible.<br /><br />The middle ground of the middle group is fill missing translations with <br />English but only if the translated percentage is bigger than say 75%<br /><br />I think collectively want to move towards an automated system so we should <br />adopt one of the 4 solutions described above (or if you have another magically <br />perfect solution we have not thought about please say so).<br /><br />PLEASE VOTE:<br /><br />Which automatic solution do you prefer?<br /><br />A) Remove translated documentation once they are not 100% translated<br /><br />B) Keep previously 100% translated documentation once current version is not <br />100% translated<br /><br />C) Use English text for non translated strings when generating translated <br />documentation <br /><br />D) Use English text for non translated strings when generating translated <br />documentation but only if translated strings are > 75%, otherwise remove the <br />translated documentation and use the English one.<br /><br />I think I would vote for C, but I'm not really a translator nowadays so I'm <br />not sure my vote counts.<br /><br />Cheers,<br /> Albert<br /><br /><br /></div>
</blockquote>
<p><br /></p>
</body></html>