Re: modernizing html output

2019-01-01 Thread Per Bothner
On 1/1/19 1:49 PM, Gavin Smith wrote: Thanks for working on this. What else needs to be changed so that the output is valid for HTML 5? It's worth clarifying that all of the changes in my patch produce valid HTML 4: Using 'id' attributes on arbitrary elements is part of HTML 4, and I believe i

can we remove generated files from git?

2019-01-01 Thread Per Bothner
These files seem to be always out of date: po/*.po po_document/*.po tp/Texinfo/XS/gnulib/m4/*m4 This makes 'git status' and 'git diff' a pain. Can we remove them from the git repository, and add them to .gitignore ? There may be other generated files, but they don't change as soon as

Re: modernizing html output

2019-01-01 Thread Gavin Smith
On Tue, Jan 01, 2019 at 02:10:11PM -0800, Per Bothner wrote: > On 1/1/19 1:49 PM, Gavin Smith wrote: > >Thanks for working on this. What else needs to be changed so that the > >output is valid for HTML 5? I assume that the DOCTYPE declaration would > >need to be changed - currently it is > > > >

Re: modernizing html output

2019-01-01 Thread Per Bothner
On 1/1/19 1:49 PM, Gavin Smith wrote: PS Texinfo is using git now for its development. In https://www.gnu.org/software/texinfo/ the link for "The development source tree." is a (broken) link to the svn tree. Also, the links in the following paragraph ("The NEWS file listing ...") go to svn.sav

Re: modernizing html output

2019-01-01 Thread Per Bothner
On 1/1/19 1:49 PM, Gavin Smith wrote: Thanks for working on this. What else needs to be changed so that the output is valid for HTML 5? I assume that the DOCTYPE declaration would need to be changed - currently it is http://www.w3.org/TR/html4/loose.dtd";> The recommendation seems to be just

Re: modernizing html output

2019-01-01 Thread Gavin Smith
On Mon, Dec 31, 2018 at 01:14:28PM -0800, Per Bothner wrote: > See this old thread: > https://lists.gnu.org/archive/html/bug-texinfo/2016-02/msg00056.html > > Attached is a simple patch to generate better-structured html. > > It wraps all nodes (anything processed by _convert_heading_command) in

Re: Order of command line options handed over to texi2any when running texinfo-js

2019-01-01 Thread Gavin Smith
On Tue, Jan 01, 2019 at 06:55:20PM +0100, Stefan Husmann wrote: > Okay, so I tried > > [haawda@frege lispintro]$ texinfo-js -I ../emacs emacs-lisp-intro.texi > texinfo-js: unknown option --I > > Why two hyphens? Glad to see somebody is trying this system! The extra hyphen was an error and has b

Order of command line options handed over to texi2any when running texinfo-js

2019-01-01 Thread Stefan Husmann
Hello list members, I was trying to genarate html out put of the Emacs Lisp Introduction using the sources coming with Gnu Emacs from git master. The source file emacs-lisp-intro.texi uses some files by @including them, which are not in the same directory, but at ../emacs. I tried to run [haaw