On Jan 13, 2007, at 12:26 PM, [EMAIL PROTECTED] wrote:
The following documents (the rest of the data from this thread) how
I got the PDF and DVI viewers and PDF and HTML exports all working
on Mac OSX 10.4.8 (just as I have them in my Slackware Linux setup)
-- with much thanks to Jens Noeckel's help.
----------------------------------------------------------------------
----
On Wed, 10 Jan 2007, Jens Noeckel wrote:
On Jan 10, 2007, at 11:00 AM, [EMAIL PROTECTED] wrote:
On Sun, 7 Jan 2007, Jens Noeckel wrote:
2 of the 3 pdf conversions work. On viewing or exporting with
dvipdfm, I get the following error:
... error running dvipdfmx -p letter -o 'newfile1.pdf'
'newfile1.dvi'
dvipdfmx exists. So is the command line wrong?
I've always had simply dvipdfm as the driver (had not installed
dvipdfmx at all because I didn't need it). Now I tried that using
fink and got the same error as you.
The error was, as you suggested, that I was using the dvipdfmx
command but didn't actually have it installed -- only dvipdfm from
fink. So I installed dvipdfmx and it uninstalled other things which
caused some of the viewers to stop working.
So I uninstalled dvipdfmx and took the 'x' off of the command line
leaving dvipdfm to do the work, and viola! -- all three pdf viewers
and exports now work. thanks!
Also, it seems that I have to have X11 running to use the DVI. So
do I need to start X11 before running the DVI viewer? And which?
And should I remove the other X11?
I wouldn't worry about it. The X11's can coexist, as far as I
know. But you're right, there is a "bug" in open-x11 which doesn't
let it automatically start X11.app, as I had intended (it works if
you provide an argument to open-x11). Another thing I never
noticed, because I have X11 running all the time, anyway...
So the better way to do this is: replace "open-x11" by "open -a
X11" in the line I sent you earlier, i.e., open -a X11 && export
DISPLAY=:0.0 && /sw/bin/xdvik
Yes, adding the -a works for opening X11 automatically. So the DVI
viewer is all smooth and nice now too! :-)
And oops -- to bring this up to the functionality I depend on in
linux on the Mac, I mostly need to be able to export to html as
well as pdf.
For that, I would suggest doing a "fink install tex4ht" (I don't
think you can get tth from fink, but tex4ht is extremely good in
my opinion; there's also "hevea"). You may have to run Reconfigure
in LyX after the installation.
I guess I assumed that I got a new html export when I upgraded to
1.4.3 in slackware. But I've been using TTH for years now which I
installed a couple years back. So I guess that wasn't part of the
upgrade then. But it sure does work seamlessly in LyX 1.4.3 on
linux if it's from that old install. The exported files retain
the important parts of the lyx formatting I need and require
little or no modification thereafter.
I had trouble with tex4ht -- I guess because it's converting from
DVI and I couldn't figure out the command line. I may re-
investigate this later.
So I went to TTH's website and downloaded the latest source. http://
hutchinson.belmont.ma.us/tth
Then I installed all the Xcode stuff from OSX, and the OSX gcc.
Then tth compilied quite simply. I moved the executable to /usr/
local/bin. And then I replicated the command line my linux setup
has for the html export in preferences - converters - LaTeX (plain)
-> HTML:
tth -t -e2 -L$$b <$$i >$$o
And it works beautifully as it does in linux. :-)
As for importing from Word, I'm not sure I'll need this but I'm
using a package I got some years ago -- wv. Command line in MS Word
-> LaTeX exports is wvCleanLatex $$i $$o The package is wv. Though
the one I have is old and I suspect there are better options.
And here one more stupid question from a long-time LyX user:
what's a "wiki"? <:-O I've seen it and probably should know what
it is. Is it an acronym?
See
http://en.wikipedia.org/wiki/Wiki
Boy was THAT ever a complete definition! Thanks for bringing me out
of the dark on this one too!
And thanks much for all the other help!
jamie faunt
Jamie,
good to know the setup is basically working now. For HTML export, all
I can say is that I only do that from the command line (since LyX to
me is simply an editor, not a swiss army knife), and tex4ht works
fine for me. Just in case you want to revisit it later:
One thing that could be a problem is if tex4ht encounters a figure
whose conversion is faulty - then it is unable to complete the
process and you get a message like what you reported.
To be on the safe side, the latex file that gets passed to htlatex
should have the figures included in eps, png or jpg format. I prefer
to have my own bitmap versions of the figures already prepared, but
you can also use an eps file and leave the conversion to bitmap up to
t4ht (if you don't care about details of the compression and color
map etc).
Jens
