Maybe instead of doing system calls to xmllint one could record the file list into some file (maybe the .fls file produced by the -recorder option is OK for that), and then one would do something like this to make the syntax checking.
awk '/^OUTPUT.*\.xml$/ { $1 =""; print}' record_file.fls | xargs xmllint We should anyway have some test target in the root makefile. That could be part of it. V. Le sam. 6 juin 2020 à 00:29, Michal Hoftich <michal....@gmail.com> a écrit : > > Hi Karl > > > 1) I wonder if we really care. But I guess it is good to check that > > what's generated is valid. > > > > I don't think we really care, as it validates only the generated HTML > documentation for literate sources. Personally, I never check that :) > > > 2) In which case, I wonder if there is any feasible way to combine calls > > to reduce the number of invocations and amount of output. xmllint > > supposedly takes more than one file. > > > > Unfortunately from a quick look it is invoked from tex4ht.env[-unix] and > > it is only set up to do one file. Michal, have you roamed around in this > > area at all? Any ideas? --thanks, karl. > > It is called by xhlatex script. It seems to pass -cvalidate option to > t4ht, which then calls a validation tool defined in tex4ht.env on each > output HTML file. I think we should just get rid of it and use just > ordinary htlatex. > > Best, > Michal