I comprehend your concern for quality. But now I have no clear info
about documentation changes. I would have to study git changelogs or do
other frustration work. It has impact on documentation translation
completeness and quality too.
I translate Gnome (which uses own tools for work with documentation
po/pot) and I don't see any problem with quality. Documentation
translator is usually the same as UI translator so he has knowledge
about application.
I thing the limit to translation quality is translator at first,
using .po is the matter in question.
Guillaume Lelarge píše v Pá 24. 09. 2010 v 12:22 +0200:
> Le 24/09/2010 12:06, Marek Černocký a écrit :
> > It would be nice to choice format the gettext (or similar tool) know
> > about. It's very difficult to track changes in the current documentation
> > for translators.
> >
>
> Gettext really doesn't work for documentation. It's much harder to know
> the context of each sentence. I'm translating the PostgreSQL manuel
> since 7.4.7 IIRC, and I'm completely against using a .po toolchain for
> the french translation. It could help to make it quicker and simpler to
> update, but it would quickly degrade the quality of the translation. Of
> course, this is only my opinion, and I know some that don't agree with
> me on this.
>
>