Comment #7 on issue 1557 by [email protected]: Migration from texi2html to
texi2any
https://code.google.com/p/lilypond/issues/detail?id=1557
I think I was too optimistic. IIUC texinfo does not allow to use gettext
*to translate content*. See this thread:
http://lists.gnu.org/archive/html/help-texinfo/2013-08/msg00002.html
It's a pity, because I just realized how it would be helpful while checking
an out-of-date italian manual I'm maintaining (it's a gnome app, which uses
mallard to build the documentation from xml - http://projectmallard.org/).
We often receive bug reports about wrong sentences in translated manuals
not maintained anymore. gettext is smart enough to build a translated
manual in a way that it contains also new paragraphs (in english); and
perhaps it can also replace out-of-date (fuzzy) paragraphs with original
english.
Any translated manual is "frozen" after a release and always available at
doc/vX.YZ/. If I quit the italian translation of lilypond documentation
(and nobody replaced me), I'd be happy to see the new versions of italian
doc half english and half italian but without any old or wrong information.
I think that this is something it's worth considering when
updating/changing our tools.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
