Vinnie Boston wrote:
Hi, I'm trying to figure out the current state of OpenDocument export on LyX
1.5.1. There is a good deal of info out there, but it seem this is changing
fairly rapidly, so not sure whether what I've found is current or not.
Yes, things are somewhat unsettled.
So, what is the current state of .odt export in LyX, particularly from
WinXP?
Unfortunately, no-one who's been working on this in on XP, so far as I know, and the various conversations I've had with people on XP haven't really produced a stable set of problems, let alone solutions. There seem to be some problems with htlatex itself on Windows generally, and we have no control over that. What we can do, from within LyX, is run the external script and then move the file to where the user will expect it to be. And that is all we do.

You can do this manually and thereby get a better sense for where the problem must be. There are two ways to do it, both of which you should try. (i) Export to LaTeX. Run oolatex or htlatex, as you wish, manually on the exported file. See if you get an odt. If this works, you can export that way. You will want to run LaTeX itself first, to generate some other files (aux, etc) that htlatex needs to produce a really final document. If this doesn't work, then try moving the exported file to a directory with no funny characters, like spaces, in the pathname, say, c:/ itself. And then try doing it again. (ii) While running LyX, try exporting. We know this will fail. Then go find LyX's temporary directory (this should be listed in the Paths dialog), find the LaTeX file LyX exported behind your back (this is probably in a subdirectory of LyX's tempdir), and try running htlatex there. It may be that this fails, even if it worked before. If so, it might have to do with spaces, or other characters, in file or path names that are upsetting htlatex. If it does work, then I'm very unsure why it's not working from within LyX.

Finally, let me know the results. Maybe we can make sense of them.

Richard

Reply via email to