Hi Stefano, tex4ht works with LuaLaTeX, but no htlualatex script is provided by default. There are some conflicts between tex4ht and babel, but these errors don't affect output, only compilation is stoped. To workaround problems with babel, making local copy of html4.4ht file and converting it to utf8 encoding should help. Note that polyglossia doesn't work, because it loads fontspec and opentype fonts (or, more precisely, fonts without tfm table) don't work with tex4ht dvi to xml converter.
Regarding direct conversion conversion from LuaLaTeX to xml without need to use dvi processing, it is possible. I created simple demo, or proof of concept [1]. Not all things supported by tex4ht works, but as you can see, fontspec works without the need of patching. PS. Note that make4ht [2] is not the same thing as mk4ht, it is simple build tool which enables configuration of commands used for conversion of images, post-processig generated files etc. Best regards, Michal [1] https://github.com/michal-h21/lua4ht [2] https://github.com/michal-h21/make4ht 2014-03-01 21:00 GMT+01:00 stefano franchi <[email protected]>: > > > > On Sat, Mar 1, 2014 at 12:23 PM, Michal Hoftich <[email protected]> > wrote: >> >> Hi, >> >> you can use tex4ht for this. It uses LaTeX by default, but it can be >> configured to use lualatex instead. See [1] for htlualatex script, other >> option is to use make4ht [2] with `-l` option. >> > > Hi Michal, > > I use mk4ht often but my impression was that htlatex does not really work > with LuaTeX. It does work with XeTeX, though, and that's what I've been > using. > > > The problem with htlatex, besides its current state of suspended animation, > is that it really uses a roundabout way to produce its output, having first > to go through (la|xe|lua)TeX processing to produce a customized DVI file and > then process the DVI to produce its final output. > > I am thinking that the first part of htlatex process essentially duplicates > (Lua)TeX functionalities, and it would be easier, perhaps, to intervene in > LuaTeX itself and "redirect" the output to XML instead of DVI|pdf. The > existence of a XML module for context seems to validate this option (big > differences between Context and LaTex notwithstanding), but I admit I have > no knowledge whatsoever of LuaTeX internals and only a cursory one of > Context. > > Any thought? > > > Stefano > > -- > __________________________________________________ > Stefano Franchi > Associate Research Professor > Department of Hispanic Studies Ph: +1 (979) 845-2125 > Texas A&M University Fax: +1 (979) 845-6421 > College Station, Texas, USA > > [email protected] > http://stefano.cleinias.org
