Hans-Christoph Steiner wrote on Fri, 01 May 2020 10:08 +0200: > Translations are no different. What we're proposing for this website > is something that is achievable with the small level of contributor > time that is available. We can definitely deliver something that is > useful without being a maintenance burden using established software > and patterns. It will not be perfect, and it would not be able to > provide the specific feature you describe.
Okay. Thanks for clarifying this. > I know of no translation workflow software that will provide this > specific feature that you are asking for. I know that people can do it > manually, but that's a lot more work. po4a is a great tool, its written > in perl, and the maintainers welcome contributions, if anyone wants to > implement such a feature. IIRC, there was at least one translation toolkit that presents translators with one paragraph at a time, and then, if a paragraph's translation was missing, the English version would be used, exactly as in the git-reset(1) usage output I posted upthread. (I don't remember its name, but in any case that was years ago.) Such a design would involve zero ongoing overhead and address the out-of-datedness concern, though I grant it has not only upsides but also downsides. I don't have anything to add. The concern is clear, I hope, as are the existing ways to address it. Beyond this point, I defer to the list. Thanks for the information! Daniel