Re: export to odt and HTML (Word)
On 07/18/2012 11:22 PM, Jack Tanner wrote: On my LyX 2.0.4, Windows, export to odt and HTML (Word) is very broken. For example, at times I get this in messages: 23:14:21.748: C:\Users\lunacy\AppData\Local\Temp\lyx_tmpdir.Hp8096\lyx_tmpbuf3t4ht my-doc.tex -cooxtpipes -coo -ewin32/tex4ht.env 23:14:21.751: --- error --- Illegal storage address but then I also get: 23:14:21.772: Successful export to format: odt 23:18:42.401: Automatic save done. Naturally, the export fails, i.e., neither the temp dir nor the actual doc dir contain an exported file. 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.) LyX must think the export worked because tex4ht is returning the code for success. That's the only way we know what's happened. Richard
Re: export to odt and HTML (Word)
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/
Re: export to odt and HTML (Word)
On 07/21/2012 12:50 PM, Jack Tanner wrote: 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/ Have you talked to John (another philosopher!) about the LaTeX issues? I'm sure he'd be interested in fixing them. Richard
Re: export to odt and HTML (Word)
On Saturday, July 21, 2012 2:28:06 PM, Richard Heck wrote: Have you talked to John (another philosopher!) about the LaTeX issues? I'm sure he'd be interested in fixing them. I didn't, but only because I found this message, which makes it look like he knows about the issues already: https://groups.google.com/d/topic/pandoc-discuss/_NrHzZoDRd4/discussion
Re: export to odt and HTML (Word)
On 07/18/2012 11:22 PM, Jack Tanner wrote: On my LyX 2.0.4, Windows, export to odt and HTML (Word) is very broken. For example, at times I get this in messages: 23:14:21.748: C:\Users\lunacy\AppData\Local\Temp\lyx_tmpdir.Hp8096\lyx_tmpbuf3>t4ht my-doc.tex "-cooxtpipes -coo" -ewin32/tex4ht.env 23:14:21.751: --- error --- Illegal storage address but then I also get: 23:14:21.772: Successful export to format: odt 23:18:42.401: Automatic save done. Naturally, the export fails, i.e., neither the temp dir nor the actual doc dir contain an exported file. 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.) LyX must think the export worked because tex4ht is returning the code for "success". That's the only way we know what's happened. Richard
Re: export to odt and HTML (Word)
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/
Re: export to odt and HTML (Word)
On 07/21/2012 12:50 PM, Jack Tanner wrote: 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/ Have you talked to John (another philosopher!) about the LaTeX issues? I'm sure he'd be interested in fixing them. Richard
Re: export to odt and HTML (Word)
On Saturday, July 21, 2012 2:28:06 PM, Richard Heck wrote: Have you talked to John (another philosopher!) about the LaTeX issues? I'm sure he'd be interested in fixing them. I didn't, but only because I found this message, which makes it look like he knows about the issues already: https://groups.google.com/d/topic/pandoc-discuss/_NrHzZoDRd4/discussion
export to odt and HTML (Word)
On my LyX 2.0.4, Windows, export to odt and HTML (Word) is very broken. For example, at times I get this in messages: 23:14:21.748: C:\Users\lunacy\AppData\Local\Temp\lyx_tmpdir.Hp8096\lyx_tmpbuf3t4ht my-doc.tex -cooxtpipes -coo -ewin32/tex4ht.env 23:14:21.751: --- error --- Illegal storage address but then I also get: 23:14:21.772: Successful export to format: odt 23:18:42.401: Automatic save done. Naturally, the export fails, i.e., neither the temp dir nor the actual doc dir contain an exported file.
export to odt and HTML (Word)
On my LyX 2.0.4, Windows, export to odt and HTML (Word) is very broken. For example, at times I get this in messages: 23:14:21.748: C:\Users\lunacy\AppData\Local\Temp\lyx_tmpdir.Hp8096\lyx_tmpbuf3>t4ht my-doc.tex "-cooxtpipes -coo" -ewin32/tex4ht.env 23:14:21.751: --- error --- Illegal storage address but then I also get: 23:14:21.772: Successful export to format: odt 23:18:42.401: Automatic save done. Naturally, the export fails, i.e., neither the temp dir nor the actual doc dir contain an exported file.
