michal-h21 / tex4ht-doc Goto Github PK

I tried to compile the doc on my computer but the compilation fail to build the html file

Output written on tex4ht_process.dvi (2 pages, 15888 bytes).
Transcript written on tex4ht_process.log.
dvisvgm -c 1.5 --exact --font-format=woff,ah tex4ht_process.dvi
pre-processing DVI file (format version 2)
processing page 1
  graphic size: 527.504752pt x 149.292204pt (185.396717mm x 52.470209mm)
  output written to tex4ht_process-1.svg
1 of 2 pages converted in 0.306787 seconds
make[1]: Leaving directory '/home/bertrand/src/tex4ht-doc/images/tex4ht_process'
make4ht -usm draft -c config -l -d out -f html5+common_domfilters -e build.mk4  tex4ht-doc.tex
[STATUS]  make4ht: Conversion started
[STATUS]  make4ht: Input file: tex4ht-doc.tex
...ve/texmf-dist/scripts/make4ht/make4ht-errorlogparser.lua:5: attempt to index a nil value (local 'filename')
make: *** [Makefile:31: tex4ht-doc.html] Error 1

Have you an idea?

Some info about my config:

• Debian 11
• make4ht version v0.3b
• Lualatex Version 1.10.0 (TeX Live 2019/Debian)

Thanks!

PS : readme file is not displayed as (parsed) markdown on Github, maybe it should be renamed README.md?

Hi Michael,
Thanks very much for creating this repository; I'm 'watching' it, and have forked it as well. I certainly hope to contribute to the project as time goes on.

I wondered what kind of work flow you'd like to use for the project. Specifically, I wondered what you think about having a develop branch to which pull requests are submitted, so that master always contains the most up to date version? I've seen this approach to be quite effective on other projects, but perhaps it wouldn't be appropriate here?

Best
Chris (cmhughes)