On Saturday, July 21, 2012 9:57:22 AM, Richard Heck wrote:
These look like bugs in the tex4ht package you're using to do the export. tex4ht is known to be problematic on Windows. (It's a bit flaky sometimes on other platforms, too.)
I've now spent about 12 hours trying to get tex4ht to work. I've tried it in MiKTeX 2.9, in TexLive under Cygwin, and under CentOS.
My verdict is that tex4ht is awfully, awfully broken. For one, the file tex4ht.env comes with at least two sets of hard-coded paths that cannot possibly work on any system other than the developer's. Then there's the piece of the xtpipes infrastructure that generates invalid XML that it later tries to parse and fails...
I got better results with pandoc for conversion from LyX-exported TeX to docx. It's fast and robust. However, pandoc has poor support for input from TeX tables. It seems like if LyX could export either to pandoc-enhanced markdown or to pandoc's native format, we'd have pretty good support for conversion from LyX to a bunch of useful formats. See http://johnmacfarlane.net/pandoc/