Menu

#1557 Migration from texi2html to texi2any

Accepted
nobody
None
Build
2016-02-03
2011-03-11
Anonymous
No

Originally created by: *anonymous

Originally created by: Carl.D.S...@gmail.com

texi2html version 5.0 has been released (June 2010).

We should see if it will allow us to simplify our texi2html.init file

See issue 1000 for a related issue.

Related

Issues: #1000
Issues: #1081

Discussion

  • Google Importer

    Google Importer - 2011-03-11

    Originally posted by: pnorcks@gmail.com

    Huh, that's interesting.  I never saw an announcement about that, but it's clearly in the release directory at savannah...

    However, texi2html is now integrated with texinfo, and all major developments are probably happening there.

    See http://lists.gnu.org/archive/html/texinfo-commits/

    Labels: Priority-Low

     
  • Google Importer

    Google Importer - 2013-05-28

    Originally posted by: lemzw...@googlemail.com

    It is good for us that texi2html is frozen; this probably means that our setup works just fine.  On the other hand, texi2html is no longer compiled or installed by default in texinfo 5; you must explicitly enable compilation by modifying `configure.ac'.

    We have to bite the bullet and do a transition to texi2any in the near future.

     
  • Google Importer

    Google Importer - 2015-02-16

    Originally posted by: fedel...@gmail.com

    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.

     
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.