On Thu, Apr 06, 2023 at 11:14:01AM +0300, Eli Zaretskii wrote: > > The alternative is, of course, bringing HTML up to par feature-wise > > (wrt. indices etc), but that'd be on the other end of the extreme, where > > instead of being too easy to parse and lacking important information, > > it'd be oververbose with and difficult to parse (not that such a thing > > should not be done too, so that folks using ordinary browsers can enjoy > > documentation, and so that projects can provide more accessible > > documentation by the merit of more people having HTML than Info > > viewers). > > > > WDYT folks? > > Gavin will tell, but AFAIU our plan is to develop js as the means > towards the goals you mentioned. That will allow using HTML browsers > to read Texinfo documentation without losing the functionalities of > the Info readers we value. HTML rendering reflows as integral part of > its workings, so that problem is not an issue if this plan succeeds. Progress on this issue is described in the TODO.HTML file in the Texinfo repository. https://git.savannah.gnu.org/cgit/texinfo.git/tree/TODO.HTML In short, the main avenue of progress appears to be the documentation browser using the embedded WebkitGTK browser.
