[OS X TeX] LaTeXit and output drivers
Peter_Dyballa at Web.DE
Thu Jul 26 17:33:01 EDT 2007
Am 26.07.2007 um 18:26 schrieb Alan Munn:
> I'm trying to get LaTeXit to work with xetex, but I need to use the
> xdvipdfmx output driver.
Why do you try this?
> Is there a way to get LaTeXit to do that?
I'd recommend to use a shell script. I did not look into the source
of LaTeXiT, but I think the "paths" in the preferences are not
allowed to have "add-ons." And there is one problem: LaTeXiT uses a
complicated way to invoke the TeX programme:
<programme> -file-line-error -interaction nonstopmode <file>
So it's necessary to update the engine file a bit! This line does the
job for me:
xelatex -output-driver=xdvipdfmx $*
This line will fail when the file's name contains a space or such!
But this, too, can be caught:
set xelatex_args = ""
set file_name = ""
foreach element ($*)
case -file-line-error: # the well-known
case -interaction: # switches can be
case nonstopmode: # handled the same
set xelatex_args="$xelatex_args $element"
default: # the "uncertain" stuff
set file_name="$file_name $element" # bad: initially
it's " file name"!
set better_name=`echo "$file_name" | sed 's/^ //'` # " file name" ->
xelatex -output-driver=xdvipdfmx $xelatex_args "$better_name"
I think this will work in TeXShop as well.
> I also tried pointing the xelatex command to the appropriate
> TeXShop engine, but that didn't work either.
How did you try? What was the error message? Have you already made
the preamble XeLaTeX compatible?
There is no worse tyranny than to force a man to pay for what he does
not want merely because you think it would be good for him.
-- Robert Heinlein
------------------------- Helpful Info -------------------------
Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
TeX FAQ: http://www.tex.ac.uk/faq
List Archive: http://tug.org/pipermail/macostex-archives/
List Reminders & Etiquette: http://www.esm.psu.edu/mac-tex/list/
More information about the MacOSX-TeX