Re: Updated (Lyx/Latex) -> (ps/pdf/html) script
> In my distro epstopdf is part of tetex. The philosophy apparently > being that it is needed when running pdflatex instead of LaTeX on a > document prepared with eps graphics. As far as I understand it, epstopdf comes together with pdflatex, it was written by the same people. So anyone who has the pdftex package should have epstopdf. And most recent versions of tetex (I don't know starting when) do include the pdftex family. Same with latex2html, I think. In summary, recent installations of tetex come with latex2html, pdflatex, epstopdf, latex and dvips. So besides lyx and perl, tetex should provide everything needed to run lyxport. I'm open to corrections if I'm mistaken in any of this. Best regards, Fernando.
Updated (Lyx/Latex) -> (ps/pdf/html) script
Hi All, I have updated/documented quite a bit my Perl script to automate producing PostScript, PDF and HTML from a Latex or Lyx source file. I've tested it a fair bit and it seems to be working well (famous last words), to the point where I've replaced the normal calls to pdflatex and latex2html with it in my Converters dialog. Its whole purpose is to work around the quirks of pdflatex and latex2html to be a bit more robust and convenient. There is now full documentation and an installation makefile, so it should be usable by non-coders. I know it still chokes on very complex files (Thomas...) but some of those problems seem to be things that kill latex2html or pdflatex themselves. I've put up a bare bones web page for it at http://www-hep.colorado.edu/~fperez/lyxport I post this to both lists b/c I think it may be useful to others, and it can certainly use more testing and bugfixing by more brains than mine. All comments and suggestions are welcome, as well as code with improvements. Jean-Marc, you are welcome to include the latest version from the web page in lyx/contrib if you find it good enough for general use. The code is GPL. Cheers, Fernando PS: Please cc your replies to me or to lyx-users, as I'm not subscribed to lyx-devel (though I read the archives).
Nasty core dump with Lyx 1.1.6fix1
Hi all, I'm only subscribed to lyx-users, but I think this is more relevant here (please keep this fact in mind if you reply). I found an ugly coredump with 1.1.6f1: if I have a simple lyx file with an included eps figure (in a float, it so happens), and try to export to latex with lyx --export latex file.lyx all goes well. However, if I use lyx -dbg --export latex file.lyx I get a nice coredump. I tried -dbg any to see how far it got, and this is the last lyx says before going belly up: Building macros [0] MathErr: Attempt to submetric a subparagraph. LyXLex::EatLine read char: `S' LyXLex::EatLine read char: `t' LyXLex::EatLine read char: `a' LyXLex::EatLine read char: `n' LyXLex::EatLine read char: `d' LyXLex::EatLine read char: `a' LyXLex::EatLine read char: `r' LyXLex::EatLine read char: `d' LyXLex::EatLine read char: ` ' lyx: SIGSEGV signal caught Sorry, you have found a bug in LyX. If possible, please read 'Known bugs' under the Help menu and then send us a full bug report. Thanks! Bye. Abort The MathErr line is the only unusual line of the tons of output. I can submit an example file if it's needed. It would be nice if this bug could be fixed, as it now breaks a script of mine which needs to run lyx with -dbg on for other reasons. Even nicer (it would simplify my script) would be if lyx could report on stdout any .tex files it creates when called with --export latex. Let me clarify: if I run "lyx --export latex file.lyx" but includes , lyx will correctly create and . However, it will only report on stdout that it made , and no mention will be made of . In order to find that out, you need to parse the output of "lyx -dbg latex --export latex file.lyx" and look for lines that begin with "writefile:". This is what I'm doing now, but it would be much simpler if lyx could simply report all the files it made, even included files. Anyway, just wanted to let you know of the coredump, and drop my little extra request. Keep up the good work! Regards, Fernando.
