[OS X TeX] MacOSX-TeX Digest #1523 - 10/13/05
André Valentin
Andre.J.Valentin at wanadoo.fr
Fri Oct 14 08:24:35 CEST 2005
MacOSX-TeX Digest #1523 - Thursday, October 13, 2005
latexdb & texshop
by "Ingo Reich" <ireich at mac.com>
Re: [OS X TeX] RTF via GUI?
by "Jason Davies" <ucgajpd at ucl.ac.uk>
Re: [OS X TeX] latexdb & texshop
by "Herbert Schulz" <herbs at wideopenwest.com>
Re: [OS X TeX] latexdb & texshop
by "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Re: [OS X TeX] New TeX i-Packages release
by "Franck Pastor" <pastor at fusl.ac.be>
Re: [OS X TeX] New TeX i-Packages release
by "Franck Pastor" <pastor at fusl.ac.be>
Re: [OS X TeX] latexdb & texshop
by "Ingo Reich" <ireich at mac.com>
Re: [OS X TeX] New TeX i-Packages release
by "Gerben Wierda" <Gerben.Wierda at rna.nl>
Re: [OS X TeX] New TeX i-Packages release
by "Gerben Wierda" <Gerben.Wierda at rna.nl>
Re: [OS X TeX] New TeX i-Packages release
by "Gerben Wierda" <Gerben.Wierda at rna.nl>
Re: [OS X TeX] latexdb & texshop
by "Peter Dyballa" <Peter_Dyballa at Web.DE>
Re: [OS X TeX] New TeX i-Packages release
by "Peter Dyballa" <Peter_Dyballa at Web.DE>
Re: [OS X TeX] New TeX i-Packages release
by "Peter Dyballa" <Peter_Dyballa at Web.DE>
Re: [OS X TeX] New TeX i-Packages release
by "Peter Dyballa" <Peter_Dyballa at Web.DE>
Re: [OS X TeX] RTF via GUI?
by "Peter Dyballa" <Peter_Dyballa at Web.DE>
Re: [OS X TeX] altpdflatex - back compatibility please
by "Joachim Kock" <jkock at start.no>
Re: [OS X TeX] altpdflatex - back compatibility please
by "Bruno Voisin" <bvoisin at mac.com>
Re: [OS X TeX] latexdb & texshop
by "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Re: [OS X TeX] latexdb & texshop
by "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Re: [OS X TeX] latexdb & texshop
by "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Re: [OS X TeX] altpdflatex - back compatibility please
by "Morten Høgholm" <morten.hoegholm at gmail.com>
Re: [OS X TeX] latexdb & texshop
by "Ingo Reich" <ireich at mac.com>
Re: [OS X TeX] altpdflatex - back compatibility please
by "Gerben Wierda" <Gerben.Wierda at rna.nl>
Re: [OS X TeX] latexdb & texshop
by "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Re: [OS X TeX] altpdflatex - back compatibility please
by "Fernando Pereira" <fcnpereira at mac.com>
Re: [OS X TeX] latexdb & texshop
by "Ingo Reich" <ireich at mac.com>
Re: [OS X TeX] latexdb & texshop
by "Herbert Schulz" <herbs at wideopenwest.com>
Re: [OS X TeX] Re: Maarten's Bugs for MacTeX Distribution
by "Chris Goedde" <cgoedde at condor.depaul.edu>
Re: [OS X TeX] latexdb & texshop
by "Ingo Reich" <ireich at mac.com>
Re: [OS X TeX] latexdb & texshop
by "Ingo Reich" <ireich at mac.com>
Re: [OS X TeX] latexdb & texshop
by "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Re: [OS X TeX] latexdb & texshop
by "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Re: [OS X TeX] latexdb & texshop
by "Herbert Schulz" <herbs at wideopenwest.com>
Re: [OS X TeX] altpdflatex - back compatibility please
by "Richard Koch" <koch at math.uoregon.edu>
Re: [OS X TeX] latexdb & texshop
by "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Re: [OS X TeX] latexdb & texshop
by "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Flashmode and pdftex
by "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Re: [OS X TeX] latexdb & texshop
by "Ingo Reich" <ireich at mac.com>
Re: [OS X TeX] latexdb & texshop
by "Peter Dyballa" <Peter_Dyballa at Web.DE>
Re: [OS X TeX] latexdb & texshop
by "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Re: [OS X TeX] latexdb & texshop
by "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Re: [OS X TeX] latexdb & texshop
by "Peter Dyballa" <Peter_Dyballa at Web.DE>
Re: [OS X TeX] latexdb & texshop
by "Peter Dyballa" <Peter_Dyballa at Web.DE>
----------------------------------------------------------------------
Subject: latexdb & texshop
From: "Ingo Reich" <ireich at mac.com>
Date: Thu, 13 Oct 2005 01:12:51 +0200
Hi,
I'd like to use latexdb from within texshop. (latexdb is a script
based on python that enables one to connect to mySQL-databases from
within a latex-file: http://privat.hgesser.com/software/latexdb/). I
tried to adapt one of Claus Gerhardts Scripts and came up with the
one below. The applescript works properly the first time it is
called, the second time ii is called however texshop complains that
it can't locate the file example.tex (in German: "Der Ort des
Dokuments 'example.tex' konnte nicht festgestellt werden"), and it
wants me to "save as ...". Any ideas what's going wrong here? Thanks,
Ingo
%%%%%%%% begin %%%%%%%
--Applescript
set scriptPath to (do shell script "dirname " & "~/Library/TeXShop/
Scripts/ex")
set scriptPath to scriptPath & "/setname.scpt"
set scriptName to POSIX file scriptPath as alias
set scriptLiB to (load script scriptName)
tell scriptLib
set frontName to setname(#NAMEPATH#,#TEXPATH#)
end tell
set fileName to #NAMEPATH#
set n to (number of characters of contents of fileName)
set fileNamequoted to quoted form of fileName
set baseName to do shell script "basename " & fileNamequoted
set m to (number of characters of contents of baseName)
set dirName to quoted form of (characters 1 thru (n - m - 1) of
fileName as string)
set texName to baseName & ".tex"
set shellScript to "cd " & dirName & ";"
set shellScript to shellScript & "~/Library/TeXShop/bin/latexdbi " &
baseName
do shell script shellScript
tell application "TeXShop"
activate
open POSIX file #DVIPATH#
end tell
%%%%%%%%% end %%%%%%%%%%
where "latexdbi" is the following binary script:
%%%%%%%% begin %%%%%%%%%%
#!/bin/tcsh
# latexdbi
set path= ($path /usr/local/bin /usr/local/teTeX/bin/powerpc-apple-
darwin-current)
latexdb "$1.tex"
%%%%%%%%% end %%%%%%%%%%
----------------------------------------------------------------------
Subject: Re: [OS X TeX] RTF via GUI?
From: "Jason Davies" <ucgajpd at ucl.ac.uk>
Date: Thu, 13 Oct 2005 01:23:39 +0100
>
> Good Luck,
>
thanks for all the advice. I'll try the engine when I'm feeling brave
and have time to make every mistake:-)
if I do get it working, do others want it?
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Herbert Schulz" <herbs at wideopenwest.com>
Date: Wed, 12 Oct 2005 19:31:38 -0500
On Oct 12, 2005, at 6:12 PM, Ingo Reich wrote:
> Hi,
> I'd like to use latexdb from within texshop. (latexdb is a script
> based on python that enables one to connect to mySQL-databases from
> within a latex-file: http://privat.hgesser.com/software/latexdb/).
> I tried to adapt one of Claus Gerhardts Scripts and came up with
> the one below. The applescript works properly the first time it is
> called, the second time ii is called however texshop complains that
> it can't locate the file example.tex (in German: "Der Ort des
> Dokuments 'example.tex' konnte nicht festgestellt werden"), and it
> wants me to "save as ...". Any ideas what's going wrong here? Thanks,
> Ingo
> ...
>
Howdy,
Is there some reason you don't just define a new TeXShop engine file?
Go to ~/Library/TeXShop/Engines/. Duplicate one of the .engine files
there and rename it latexdb.engine; this saves you from making the
file executable later. Open the latexdb.engine file in TeXShop and
replace the contents with
#!/bin/bash
latexdb "$1"
and save it. This ``engine'' is executed in the directory with the
source file.
To use it just select the latexdb engine in the drop down menu on the
toolbar at the top of the source file (it that isn't there Ctl-Click
on the toolbar and choose to configure it). To make it the default
engine add the line
%!TEX TS-program = latexdb
at, or near, the top of the file. Then Cmd-T will automatically
execute the latexdb engine for typesetting.
Good Luck,
Herb Schulz
(herbs at wideopenwest.com)
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Date: Thu, 13 Oct 2005 02:30:37 +0200
The command in the shell script should be
> latexdb "$1"
>
Claus
On Oct 13, 2005, at 1:12, Ingo Reich wrote:
> Hi,
> I'd like to use latexdb from within texshop. (latexdb is a script
> based on python that enables one to connect to mySQL-databases from
> within a latex-file: http://privat.hgesser.com/software/latexdb/).
> I tried to adapt one of Claus Gerhardts Scripts and came up with
> the one below. The applescript works properly the first time it is
> called, the second time ii is called however texshop complains that
> it can't locate the file example.tex (in German: "Der Ort des
> Dokuments 'example.tex' konnte nicht festgestellt werden"), and it
> wants me to "save as ...". Any ideas what's going wrong here? Thanks,
> Ingo
>
>
>
> %%%%%%%% begin %%%%%%%
> --Applescript
>
> set scriptPath to (do shell script "dirname " & "~/Library/TeXShop/
> Scripts/ex")
> set scriptPath to scriptPath & "/setname.scpt"
> set scriptName to POSIX file scriptPath as alias
> set scriptLiB to (load script scriptName)
> tell scriptLib
> set frontName to setname(#NAMEPATH#,#TEXPATH#)
> end tell
>
> set fileName to #NAMEPATH#
> set n to (number of characters of contents of fileName)
> set fileNamequoted to quoted form of fileName
> set baseName to do shell script "basename " & fileNamequoted
> set m to (number of characters of contents of baseName)
> set dirName to quoted form of (characters 1 thru (n - m - 1) of
> fileName as string)
> set texName to baseName & ".tex"
>
> set shellScript to "cd " & dirName & ";"
> set shellScript to shellScript & "~/Library/TeXShop/bin/latexdbi "
> & baseName
> do shell script shellScript
>
> tell application "TeXShop"
> activate
> open POSIX file #DVIPATH#
> end tell
> %%%%%%%%% end %%%%%%%%%%
>
>
> where "latexdbi" is the following binary script:
>
> %%%%%%%% begin %%%%%%%%%%
> #!/bin/tcsh
> # latexdbi
>
> set path= ($path /usr/local/bin /usr/local/teTeX/bin/powerpc-
> apple-darwin-current)
>
> latexdb "$1.tex"
>
> %%%%%%%%% end %%%%%%%%%%
>
> ------------------------- Info --------------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
> & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Archive: http://tug.org/pipermail/macostex-archives/
>
>
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] New TeX i-Packages release
From: "Franck Pastor" <pastor at fusl.ac.be>
Date: Thu, 13 Oct 2005 07:28:23 +0200
Le 12-oct.-05 à 21:42, Gerben Wierda a écrit :
>
> In terms of the command line, the following behaviours (using
> TL2005 stuff), (example: map file handling):
>
> System wide (this is how the TeX i-Package does it).
>
> 1. Install the map file in texmf.local (~/Library/texmf is ignored)
> 2. Run:
> sudo -H -u root updmap-sys --enable Map foo.map
>
>
> Personal:
> 1. Install the map file in ~/Library/texmf
> 2. Run:
> updmap --enable Map foo.map
>
>
Wouldn't it be better to have an updmap.cfg file in the ~/Library/
texmf/web2c directory in that case ? A copy of the updmap.cfg file
that lies in /usr/local/teTeX/share/texmf.local/web2c, for example...
>
> Compatible with TL2004 (written in texmf.local but ~/Library/texmf
> is *not* ignored):
>
> 1. Install in ~/Library/texmf of texmf.local
> 2. Run:
> sudo updmap-sys --enable Map foo.map
>
> G
> ------------------------- Info --------------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
> & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Archive: http://tug.org/pipermail/macostex-archives/
>
>
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] New TeX i-Packages release
From: "Franck Pastor" <pastor at fusl.ac.be>
Date: Thu, 13 Oct 2005 07:37:42 +0200
Le 13-oct.-05 à 07:28, Franck Pastor a écrit :
>
> Le 12-oct.-05 à 21:42, Gerben Wierda a écrit :
>
>
>
>>
>> In terms of the command line, the following behaviours (using
>> TL2005 stuff), (example: map file handling):
>>
>> System wide (this is how the TeX i-Package does it).
>>
>> 1. Install the map file in texmf.local (~/Library/texmf is ignored)
>> 2. Run:
>> sudo -H -u root updmap-sys --enable Map foo.map
>>
>>
>> Personal:
>> 1. Install the map file in ~/Library/texmf
>> 2. Run:
>> updmap --enable Map foo.map
>>
>>
>>
>
> Wouldn't it be better to have an updmap.cfg file in the ~/Library/
> texmf/web2c directory in that case ? A copy of the updmap.cfg file
> that lies in /usr/local/teTeX/share/texmf.local/web2c, for example...
>
>
More precisely, I meant : in the "personal" case. The files
"updmap.cfg" that lie in the texmf.local or texmf.tetex are
unreadable by the user if he's not "root". Hence the idea to put a
copy of /usr/local/teTeX/share/texmf.local/web2c/updmap.cfg in your
personal setting, ~/Library/texmf/web2c/, before running the "updmap
--enable Map foo.map" command.
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Ingo Reich" <ireich at mac.com>
Date: Thu, 13 Oct 2005 07:46:31 +0200
Herb,
last night I tried (almost: tcsh) exactly what you suggested, and it
didn't work at all; this morning I retried (bash), and it does work
on the first run. To be more precise: it does work as long as I don't
have to save my file before calling latexdb; if I need to save
changes in the file, texshop still complains the way I mentioned in
my last mail.
Another question: Since latexdb only generates a dvi-file, not a
pdf-file, I tried to extend the script as follows:
#!/bin/bash
latexdb "$1"
dvipdfm "$1"
But now dvipdfm looks for "example.tex.dvi" instead of "example.dvi",
and gets stuck.
Sorry for being so ignorant.
Ingo
P.S. to Claus: I did try it both ways, i.e. with and without the
extension .tex, but the problem persisted.
Am 13.10.2005 um 02:31 schrieb Herbert Schulz:
>
> On Oct 12, 2005, at 6:12 PM, Ingo Reich wrote:
>
>
>
>> Hi,
>> I'd like to use latexdb from within texshop. (latexdb is a script
>> based on python that enables one to connect to mySQL-databases
>> from within a latex-file: http://privat.hgesser.com/software/
>> latexdb/). I tried to adapt one of Claus Gerhardts Scripts and
>> came up with the one below. The applescript works properly the
>> first time it is called, the second time ii is called however
>> texshop complains that it can't locate the file example.tex (in
>> German: "Der Ort des Dokuments 'example.tex' konnte nicht
>> festgestellt werden"), and it wants me to "save as ...". Any ideas
>> what's going wrong here? Thanks,
>> Ingo
>> ...
>>
>>
>
> Howdy,
>
> Is there some reason you don't just define a new TeXShop engine
> file? Go to ~/Library/TeXShop/Engines/. Duplicate one of
> the .engine files there and rename it latexdb.engine; this saves
> you from making the file executable later. Open the latexdb.engine
> file in TeXShop and replace the contents with
>
> #!/bin/bash
> latexdb "$1"
>
> and save it. This ``engine'' is executed in the directory with the
> source file.
>
> To use it just select the latexdb engine in the drop down menu on
> the toolbar at the top of the source file (it that isn't there Ctl-
> Click on the toolbar and choose to configure it). To make it the
> default engine add the line
>
> %!TEX TS-program = latexdb
>
> at, or near, the top of the file. Then Cmd-T will automatically
> execute the latexdb engine for typesetting.
>
> Good Luck,
>
> Herb Schulz
> (herbs at wideopenwest.com)
>
>
> ------------------------- Info --------------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
> & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Archive: http://tug.org/pipermail/macostex-archives/
>
>
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] New TeX i-Packages release
From: "Gerben Wierda" <Gerben.Wierda at rna.nl>
Date: Thu, 13 Oct 2005 07:46:45 +0200
Remove them unless you need special or personalized versions. If you
want personal stuff: use the command line and the fmtutil command.
System wide, use "sudo -H -u root fmtutil-sys"
G
On Oct 13, 2005, at 01:09, Claus Gerhardt wrote:
> What happens with the personal formats (.fmt) that reside in
> ~/Library/texmf/web2c and what are the recommended (or possible)
> procedures in this case.
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] New TeX i-Packages release
From: "Gerben Wierda" <Gerben.Wierda at rna.nl>
Date: Thu, 13 Oct 2005 09:17:41 +0200 (CEST)
>
> Le 12-oct.-05 à 21:42, Gerben Wierda a écrit :
>
>
>>
>> In terms of the command line, the following behaviours (using
>> TL2005 stuff), (example: map file handling):
>>
>> System wide (this is how the TeX i-Package does it).
>>
>> 1. Install the map file in texmf.local (~/Library/texmf is ignored)
>> 2. Run:
>> sudo -H -u root updmap-sys --enable Map foo.map
>>
>>
>> Personal:
>> 1. Install the map file in ~/Library/texmf
>> 2. Run:
>> updmap --enable Map foo.map
>>
>>
>
> Wouldn't it be better to have an updmap.cfg file in the ~/Library/
> texmf/web2c directory in that case ? A copy of the updmap.cfg file
> that lies in /usr/local/teTeX/share/texmf.local/web2c, for example...
>
That happens automatically if the file does not exist yet.
G
----------------------------------------------------------------------
Subject: Re: [OS X TeX] New TeX i-Packages release
From: "Gerben Wierda" <Gerben.Wierda at rna.nl>
Date: Thu, 13 Oct 2005 09:21:07 +0200 (CEST)
>
> Le 13-oct.-05 à 07:28, Franck Pastor a écrit :
>
>
>>
>> Le 12-oct.-05 à 21:42, Gerben Wierda a écrit :
>>
>>
>>
>>>
>>> In terms of the command line, the following behaviours (using
>>> TL2005 stuff), (example: map file handling):
>>>
>>> System wide (this is how the TeX i-Package does it).
>>>
>>> 1. Install the map file in texmf.local (~/Library/texmf is ignored)
>>> 2. Run:
>>> sudo -H -u root updmap-sys --enable Map foo.map
>>>
>>>
>>> Personal:
>>> 1. Install the map file in ~/Library/texmf
>>> 2. Run:
>>> updmap --enable Map foo.map
>>>
>>>
>>>
>>
>> Wouldn't it be better to have an updmap.cfg file in the ~/Library/
>> texmf/web2c directory in that case ? A copy of the updmap.cfg file
>> that lies in /usr/local/teTeX/share/texmf.local/web2c, for example...
>>
>>
> More precisely, I meant : in the "personal" case. The files
> "updmap.cfg" that lie in the texmf.local or texmf.tetex are
> unreadable by the user if he's not "root".
>
They are readable. They are not writable.
> Hence the idea to put a
> copy of /usr/local/teTeX/share/texmf.local/web2c/updmap.cfg in your
> personal setting, ~/Library/texmf/web2c/, before running the "updmap
> --enable Map foo.map" command.
>
This happens automatically. --enable takes the current config file and
changes and saves it. If there is no config file in your personal texmf
tree yet, it uses whatever is current as input. That should be the
one in
texmf.local. This is true for updmap, texconfig and fmtutil.
As soon as you have a personal configuration, using the i-Package for
configuration does not work anymore because it restricts itself to the
system-wide configuration.
G
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Peter Dyballa" <Peter_Dyballa at Web.DE>
Date: Thu, 13 Oct 2005 10:44:54 +0200
Am 13.10.2005 um 07:46 schrieb Ingo Reich:
> #!/bin/bash
> latexdb "$1"
> dvipdfm "$1"
>
> But now dvipdfm looks for "example.tex.dvi" instead of "example.dvi",
> and gets stuck.
>
>
As Claus already emphasised: "$1" has a value of "name.tex." So you
should better try:
Name = `basename "$1" .tex`
latexdb "$Name" # if .tex is necessary make it $1 again
dvipdfm "$Name"
(dvipdfm "`basename \"$1\" .tex`" would worm too in bash)
And maybe here's too an explanation why TeXShop stops to work: you are
only handling the filename without its path component. In the beginning
TeXShop might have open ~/Library/texmf/unerledigte Arbeit/Dings.tex
and then this turns into Dings.tex. I may look as puzzled as TeXShop
then ...
My AppleScript understanding is obviously very limited. Particularly I
wonder how things like #NAMEPATH#, #TEXPATH#, and #DVIPATH# can appear
from inside a Were-Rabbit's silk-hat. I too feel that the sequence of
statements in the script isn't well elaborated and could need some new
order and comments.
--
Mit friedvollen Grüßen
Pete === -Q
==<__/% >>
_____________(_)____ at _____________________________
----------------------------------------------------------------------
Subject: Re: [OS X TeX] New TeX i-Packages release
From: "Peter Dyballa" <Peter_Dyballa at Web.DE>
Date: Thu, 13 Oct 2005 10:53:03 +0200
Am 12.10.2005 um 03:58 schrieb Axel E. Retif:
> Does this mean that in command line we still _have_ to make a
> distinction between updmap and updmap-sys?
>
>
In TeX Live 2005: yes, of course! And it makes a difference whether you
invoke 'sudo -H utility-sys ...' or 'sudo utility-sys ...' ...
--
Greetings
Pete
When you meet a master swordsman,
show him your sword.
When you meet a man who is not a poet,
do not show him your poem.
-- Rinzai, ninth century Zen master
----------------------------------------------------------------------
Subject: Re: [OS X TeX] New TeX i-Packages release
From: "Peter Dyballa" <Peter_Dyballa at Web.DE>
Date: Thu, 13 Oct 2005 10:55:46 +0200
Am 13.10.2005 um 01:09 schrieb Claus Gerhardt:
> What happens with the personal formats (.fmt) that reside in
> ~/Library/texmf/web2c and what are the recommended (or possible)
> procedures in this case.
>
>
fmtutil without -sys.
--
Mit friedvollen Grüßen
Pete
Behold the warranty ... the bold print giveth and the fine print taketh
away.
----------------------------------------------------------------------
Subject: Re: [OS X TeX] New TeX i-Packages release
From: "Peter Dyballa" <Peter_Dyballa at Web.DE>
Date: Thu, 13 Oct 2005 10:58:13 +0200
Am 13.10.2005 um 07:28 schrieb Franck Pastor:
> Wouldn't it be better to have an updmap.cfg file in the
> ~/Library/texmf/web2c directory in that case ? A copy of the
> updmap.cfg file that lies in /usr/local/teTeX/share/texmf.local/web2c,
> for example...
>
You don't need a private copy because updmap uses the system-wide
updmap.cfg file.
Although I wonder whether it can work to habe less fonts MAPped for
private use than the system dictates ... Having more works!
--
Greetings
Pete
There's no place like ~
(UNIX Guru)
----------------------------------------------------------------------
Subject: Re: [OS X TeX] RTF via GUI?
From: "Peter Dyballa" <Peter_Dyballa at Web.DE>
Date: Thu, 13 Oct 2005 11:23:21 +0200
Am 13.10.2005 um 02:23 schrieb Jason Davies:
> if I do get it working, do others want it?
>
>
Just make it public in this list! Someone will need and use it. Sooner
or later ...
(Although I've found that only simple documents can be converted. Usual
cosmetics are lost. Many RTF viewers failed. In the end there might be
a more precise copy of your (La)TeX design when going a detour over
HTML or PDF or with Perl?)
--
Greetings
Pete
It's not the valleys in life I dread so much as the dips.
-- Garfield
----------------------------------------------------------------------
Subject: Re: [OS X TeX] altpdflatex - back compatibility please
From: "Joachim Kock" <jkock at start.no>
Date: Thu, 13 Oct 2005 11:47:51 +0200 (CEST)
Dear Gerben,
thanks a lot for looking into this, and thanks in general for your good
work with the tetex distribution.
> The altpdftex->simpdftex change has been made because altpdftex
> needs a
> separate command file for every type of format (altpdftex,
> altpdflatex,
> etc.) and this clutters your binary directory and is also
> problematic to
> maintain: if you enable or disable formats (via fmtutil, texconfig
> or the
> i-Package configure phase) the required extra altpdf* links are not
> automatically created.
>
I understand that although these scripts are extremely useful, the
original
design was not thought-through enough, and perhaps you did not
imagine how
popular and wide-spread the scripts would be.
However, the problem that new-format versions of the script are not
generated automatically is not a problem that ever broke any
functionality.
If altpdfsmartlatex never existed, then neither did anyone ever
expect it
to exist. Cluttering the bin/ directory shouldn't really be a
problem for
anyone, at least not a problem compared to the advantage and noble
concern
of back compatibility.
> When we were dicussing adding this, the result was that altpdf*
> would be
> replaced by a single command with an argument. That needs to to be
> maintained and it is cleaner.
>
I agree that the simpdftex design is much better. But there is
nothing to
maintain: just freeze the old alt* scripts as they are and keep them, in
respect of people using them. That's extremely simple and should not
be a
problem for anyone. (You might freeze them together with a warning,
in the
style of the latex 2.09 compatibility.) If some day the scripts break,
too bad, but before that happens we will probably have had another
couple
of years of transition, and the problem would be much smaller.
> So, last year, simpdftex was introduced and altpdf*tex were retained
> because of backward compatibility. The frontend designers were
> informed
> that the change had taken place and they were requested to change
> their
> frontends to use simpdftex instead of altpdf*tex. It was then said
> that
> altpdf*tex would be retired later.
>
But why retire them at all as long as they work?
> The problem we are seeing now is that the front end designers (busy
> bees
> as they are) forgot about it and I did not remind them periodically).
>
This is not a question of frontend developers being busy bees: the
question
is that the frontend is supposed to work with existing tetex
distributions
(and not just the newest ones). TeXShop and other frontends should
not be
forced to require the user to have a less-than-one-year-old tetex
installation!
Perhaps you forget how stable a thing tex (and gwtex) is. For 90
percent
of the tex users, there is no reason to upgrade, and there may be
many old
installations around. Certainly on this list, people are very
advanced tex
users and we are all very thankful for the constant development and
improvements, and the new bells and whistles, but the average user (not
subscribed to this list) may not need more than standard OT1 encoded CM
fonts, and a few AMS packages. This has been working perfectly well
ever
since your first distribution back in the previous millenium.
By removing those scripts, the frontend writer wishing to use the
scripts
is forced to either formally require a new version of tetex (gwtex) or
write complicated instructions in the manual or 'readme', explaining
that
in certain distributions you have to do one thing, and in other
distributions you have to do some other thing, and it is akward to
describe
precisely what versions because there are so many components involved
and
it is not clear which version number you should refer to or where the
user
can find this information.
> Re-introducing a back compatibility script would defeat the object
> of the
> transition completely so I am not going to do it.
>
Sorry for being stupid, but how does the error message work? Isn't it a
script? Why does this error script not defeat the objective of the
transition? Why is it better to have an error script (breaking existing
functionality) than having the current symlinks?
I don't see any problem with the population of the bin/ directory.
Nobody
ever opens this directory anyway -- we are not talking a polished OSX
folder where the presence of more than six items would be intimidating!
Compare with some other famous transitions: you can still write
\documentstyle{article} in your source file and it will work. You can
still say latex in the command line and it will invoke pdflatex with the
appropriate parameters... Do these tricks defeat the objective of the
transitions?
> Backwards compatibility is not truly lost. You can still compile all
> your old documents, the only thing that has changed is that the
> convenience script for running tex, dvips and distiller has been
> renamed
> and changed its command line interface. In my book, backwards
> compatibility is not lost of you still can get the same results
> even if
> you have to do different things to get those results.
>
Which book? And which edition? :-)
> But it is of course possible to disagree on the interpretation of
> backward compatibility.
>
The transitions I mentioned above represent different views on backward
compatibility than yours. But of course they were also more important
transitions...
Cheers,
Joachim.
------------------------------------------------------------------------
-
Start.no tilbyr nå raskere bredbånd til lavere pris.
Sjekk http://www.start.no/bredband/ for mer informasjon
----------------------------------------------------------------------
Subject: Re: [OS X TeX] altpdflatex - back compatibility please
From: "Bruno Voisin" <bvoisin at mac.com>
Date: Thu, 13 Oct 2005 11:53:07 +0200
Le 13 oct. 05 à 11:47, Joachim Kock a écrit :
> TeXShop and other frontends should not be
> forced to require the user to have a less-than-one-year-old tetex
> installation!
>
That's the world we live in, however!
Bruno Voisin
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Date: Thu, 13 Oct 2005 12:02:31 +0200
Ingo,
Try the following script and convince yourself that the required
subscripts or subroutines are all available.
Claus
%%%%%%%% begin %%%%%%%
--Applescript
tell application "TeXShop"
get path of document of window 1
set fileName to result
end tell
set scriptPath to (do shell script "dirname " & "~/Library/
Flashmode/Subroutines/ex")
set scriptPath to scriptPath & "/setnamets.scpt"
set scriptName to POSIX file scriptPath as alias
set scriptLiB to (load script scriptName)
tell scriptLiB
set {baseName, texName, pdfName, namePath, dirName,
dirNameunquoted, logName, logPath, rtfName} to setnamets(fileName)
end tell
set shellScript to "cd " & dirName & ";"
set shellScript to shellScript & "~/Library/TeXShop/bin/latexdbi " &
texname
do shell script shellScript
set shellScript to "cd " & dirName & ";"
set shellScript to shellScript & "~/Library/TeXShop/bin/dvipdfc " &
basename
do shell script shellScript
(*
set pdfName to quotedform of pdfName
set thePDF to POSIX file pdfName as alias
*)
tell document texName of application "TeXShop"
activate
refreshpdf
end tell
%%%%%%%%% end %%%%%%%%%%
-- Save the subroutine setnamets.scpt in ~/Library/TeXShop/Scripts
on setnamets(x)
set n to (number of characters of contents of x)
set fileNamequoted to quoted form of x
set windowName to do shell script "basename " & fileNamequoted
set m to (number of characters of contents of windowName)
set dirName to quoted form of (characters 1 thru (n - m - 1) of
x as string)
set dirNameunquoted to (characters 1 thru (n - m - 1) of x as
string)
set theText to contents of windowName as string
set n to (number of characters of contents of theText)
set i to n as number
repeat while i > 0
if character i of theText is equal to "." then
set m to i
exit repeat
else
set i to (i - 1)
end if
end repeat
set baseName to (characters 1 thru (m - 1) of theText as string)
set texName to baseName & ".tex"
set namePath to dirNameunquoted & "/" & baseName as string
set pdfName to namePath & ".pdf" as string
set rtfName to namePath & ".rtf" as string
set logPath to namePath & ".log" as string
set logName to baseName & ".log" as string
try
tell application "TeXShop"
save document texName
end tell
end try
return {baseName, texName, pdfName, namePath, dirName,
dirNameunquoted, logName, logPath, rtfName} as list
end setnamets
On Oct 13, 2005, at 2:30, Claus Gerhardt wrote:
> The command in the shell script should be
>
>
>
>> latexdb "$1"
>>
>>
>
>
> Claus
>
>
> On Oct 13, 2005, at 1:12, Ingo Reich wrote:
>
>
>
>> Hi,
>> I'd like to use latexdb from within texshop. (latexdb is a script
>> based on python that enables one to connect to mySQL-databases
>> from within a latex-file: http://privat.hgesser.com/software/
>> latexdb/). I tried to adapt one of Claus Gerhardts Scripts and
>> came up with the one below. The applescript works properly the
>> first time it is called, the second time ii is called however
>> texshop complains that it can't locate the file example.tex (in
>> German: "Der Ort des Dokuments 'example.tex' konnte nicht
>> festgestellt werden"), and it wants me to "save as ...". Any ideas
>> what's going wrong here? Thanks,
>> Ingo
>>
>>
>>
>> %%%%%%%% begin %%%%%%%
>> --Applescript
>>
>> set scriptPath to (do shell script "dirname " & "~/Library/TeXShop/
>> Scripts/ex")
>> set scriptPath to scriptPath & "/setname.scpt"
>> set scriptName to POSIX file scriptPath as alias
>> set scriptLiB to (load script scriptName)
>> tell scriptLib
>> set frontName to setname(#NAMEPATH#,#TEXPATH#)
>> end tell
>>
>> set fileName to #NAMEPATH#
>> set n to (number of characters of contents of fileName)
>> set fileNamequoted to quoted form of fileName
>> set baseName to do shell script "basename " & fileNamequoted
>> set m to (number of characters of contents of baseName)
>> set dirName to quoted form of (characters 1 thru (n - m - 1) of
>> fileName as string)
>> set texName to baseName & ".tex"
>>
>> set shellScript to "cd " & dirName & ";"
>> set shellScript to shellScript & "~/Library/TeXShop/bin/latexdbi
>> " & baseName
>> do shell script shellScript
>>
>> tell application "TeXShop"
>> activate
>> open POSIX file #DVIPATH#
>> end tell
>> %%%%%%%%% end %%%%%%%%%%
>>
>>
>> where "latexdbi" is the following binary script:
>>
>> %%%%%%%% begin %%%%%%%%%%
>> #!/bin/tcsh
>> # latexdbi
>>
>> set path= ($path /usr/local/bin /usr/local/teTeX/bin/powerpc-
>> apple-darwin-current)
>>
>> latexdb "$1.tex"
>>
>> %%%%%%%%% end %%%%%%%%%%
>>
>> ------------------------- Info --------------------------
>> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
>> & FAQ: http://latex.yauh.de/faq/
>> TeX FAQ: http://www.tex.ac.uk/faq
>> List Archive: http://tug.org/pipermail/macostex-archives/
>>
>>
>>
>>
>
> ------------------------- Info --------------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
> & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Archive: http://tug.org/pipermail/macostex-archives/
>
>
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Date: Thu, 13 Oct 2005 12:06:36 +0200
Sorry there were two typos in the basic Applescript.
Claus
--Applescript
tell application "TeXShop"
get path of document of window 1
set fileName to result
end tell
set scriptPath to (do shell script "dirname " & "~/Library/
Flashmode/Subroutines/ex")
set scriptPath to scriptPath & "/setnamets.scpt"
set scriptName to POSIX file scriptPath as alias
set scriptLiB to (load script scriptName)
tell scriptLiB
set {baseName, texName, pdfName, namePath, dirName,
dirNameunquoted, logName, logPath, rtfName} to setnamets(fileName)
end tell
set shellScript to "cd " & dirName & ";"
set shellScript to shellScript & "~/Library/TeXShop/bin/latexdbi " &
texName
do shell script shellScript
set shellScript to "cd " & dirName & ";"
set shellScript to shellScript & "~/Library/TeXShop/bin/dvipdfc " &
baseName
do shell script shellScript
(*
set pdfName to quotedform of pdfName
set thePDF to POSIX file pdfName as alias
*)
tell document texName of application "TeXShop"
activate
refreshpdf
end tell
%%%%%%%%% end %%%%%%%%%%
On Oct 13, 2005, at 12:02, Claus Gerhardt wrote:
> Ingo,
>
> Try the following script and convince yourself that the required
> subscripts or subroutines are all available.
>
> Claus
>
> %%%%%%%% begin %%%%%%%
> --Applescript
>
> tell application "TeXShop"
> get path of document of window 1
> set fileName to result
> end tell
> set scriptPath to (do shell script "dirname " & "~/Library/
> Flashmode/Subroutines/ex")
> set scriptPath to scriptPath & "/setnamets.scpt"
> set scriptName to POSIX file scriptPath as alias
> set scriptLiB to (load script scriptName)
> tell scriptLiB
> set {baseName, texName, pdfName, namePath, dirName,
> dirNameunquoted, logName, logPath, rtfName} to setnamets(fileName)
> end tell
>
>
>
> set shellScript to "cd " & dirName & ";"
> set shellScript to shellScript & "~/Library/TeXShop/bin/latexdbi "
> & texname
> do shell script shellScript
>
> set shellScript to "cd " & dirName & ";"
> set shellScript to shellScript & "~/Library/TeXShop/bin/dvipdfc "
> & basename
> do shell script shellScript
> (*
> set pdfName to quotedform of pdfName
>
> set thePDF to POSIX file pdfName as alias
> *)
> tell document texName of application "TeXShop"
> activate
> refreshpdf
> end tell
>
>
> %%%%%%%%% end %%%%%%%%%%
>
> -- Save the subroutine setnamets.scpt in ~/Library/TeXShop/Scripts
>
> on setnamets(x)
> set n to (number of characters of contents of x)
> set fileNamequoted to quoted form of x
> set windowName to do shell script "basename " & fileNamequoted
> set m to (number of characters of contents of windowName)
> set dirName to quoted form of (characters 1 thru (n - m - 1) of
> x as string)
> set dirNameunquoted to (characters 1 thru (n - m - 1) of x as
> string)
> set theText to contents of windowName as string
>
> set n to (number of characters of contents of theText)
> set i to n as number
>
> repeat while i > 0
> if character i of theText is equal to "." then
> set m to i
> exit repeat
> else
> set i to (i - 1)
> end if
> end repeat
>
> set baseName to (characters 1 thru (m - 1) of theText as string)
> set texName to baseName & ".tex"
> set namePath to dirNameunquoted & "/" & baseName as string
> set pdfName to namePath & ".pdf" as string
> set rtfName to namePath & ".rtf" as string
> set logPath to namePath & ".log" as string
> set logName to baseName & ".log" as string
>
> try
> tell application "TeXShop"
> save document texName
> end tell
> end try
> return {baseName, texName, pdfName, namePath, dirName,
> dirNameunquoted, logName, logPath, rtfName} as list
> end setnamets
>
>
> On Oct 13, 2005, at 2:30, Claus Gerhardt wrote:
>
>
>
>> The command in the shell script should be
>>
>>
>>
>>
>>> latexdb "$1"
>>>
>>>
>>>
>>
>>
>> Claus
>>
>>
>> On Oct 13, 2005, at 1:12, Ingo Reich wrote:
>>
>>
>>
>>
>>> Hi,
>>> I'd like to use latexdb from within texshop. (latexdb is a script
>>> based on python that enables one to connect to mySQL-databases
>>> from within a latex-file: http://privat.hgesser.com/software/
>>> latexdb/). I tried to adapt one of Claus Gerhardts Scripts and
>>> came up with the one below. The applescript works properly the
>>> first time it is called, the second time ii is called however
>>> texshop complains that it can't locate the file example.tex (in
>>> German: "Der Ort des Dokuments 'example.tex' konnte nicht
>>> festgestellt werden"), and it wants me to "save as ...". Any
>>> ideas what's going wrong here? Thanks,
>>> Ingo
>>>
>>>
>>>
>>> %%%%%%%% begin %%%%%%%
>>> --Applescript
>>>
>>> set scriptPath to (do shell script "dirname " & "~/Library/
>>> TeXShop/Scripts/ex")
>>> set scriptPath to scriptPath & "/setname.scpt"
>>> set scriptName to POSIX file scriptPath as alias
>>> set scriptLiB to (load script scriptName)
>>> tell scriptLib
>>> set frontName to setname(#NAMEPATH#,#TEXPATH#)
>>> end tell
>>>
>>> set fileName to #NAMEPATH#
>>> set n to (number of characters of contents of fileName)
>>> set fileNamequoted to quoted form of fileName
>>> set baseName to do shell script "basename " & fileNamequoted
>>> set m to (number of characters of contents of baseName)
>>> set dirName to quoted form of (characters 1 thru (n - m - 1) of
>>> fileName as string)
>>> set texName to baseName & ".tex"
>>>
>>> set shellScript to "cd " & dirName & ";"
>>> set shellScript to shellScript & "~/Library/TeXShop/bin/latexdbi
>>> " & baseName
>>> do shell script shellScript
>>>
>>> tell application "TeXShop"
>>> activate
>>> open POSIX file #DVIPATH#
>>> end tell
>>> %%%%%%%%% end %%%%%%%%%%
>>>
>>>
>>> where "latexdbi" is the following binary script:
>>>
>>> %%%%%%%% begin %%%%%%%%%%
>>> #!/bin/tcsh
>>> # latexdbi
>>>
>>> set path= ($path /usr/local/bin /usr/local/teTeX/bin/powerpc-
>>> apple-darwin-current)
>>>
>>> latexdb "$1.tex"
>>>
>>> %%%%%%%%% end %%%%%%%%%%
>>>
>>> ------------------------- Info --------------------------
>>> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
>>> & FAQ: http://latex.yauh.de/faq/
>>> TeX FAQ: http://www.tex.ac.uk/faq
>>> List Archive: http://tug.org/pipermail/macostex-archives/
>>>
>>>
>>>
>>>
>>>
>>
>> ------------------------- Info --------------------------
>> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
>> & FAQ: http://latex.yauh.de/faq/
>> TeX FAQ: http://www.tex.ac.uk/faq
>> List Archive: http://tug.org/pipermail/macostex-archives/
>>
>>
>>
>>
>
> ------------------------- Info --------------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
> & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Archive: http://tug.org/pipermail/macostex-archives/
>
>
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Date: Thu, 13 Oct 2005 12:18:36 +0200
The path for the subroutine was wrong, unless Ingo, like most people,
has installed Flashmode.
Claus
--Applescript
tell application "TeXShop"
get path of document of window 1
set fileName to result
end tell
set scriptPath to (do shell script "dirname " & "~/Library/
TeXShop/Scripts/ex")
set scriptPath to scriptPath & "/setnamets.scpt"
set scriptName to POSIX file scriptPath as alias
set scriptLiB to (load script scriptName)
tell scriptLiB
set {baseName, texName, pdfName, namePath, dirName,
dirNameunquoted, logName, logPath, rtfName} to setnamets(fileName)
end tell
set shellScript to "cd " & dirName & ";"
set shellScript to shellScript & "~/Library/TeXShop/bin/latexdbi " &
texName
do shell script shellScript
set shellScript to "cd " & dirName & ";"
set shellScript to shellScript & "~/Library/TeXShop/bin/dvipdfc " &
baseName
do shell script shellScript
(*
set pdfName to quotedform of pdfName
set thePDF to POSIX file pdfName as alias
*)
tell document texName of application "TeXShop"
activate
refreshpdf
end tell
%%%%%%%%% end %%%%%%%%%%
On Oct 13, 2005, at 12:06, Claus Gerhardt wrote:
> Sorry there were two typos in the basic Applescript.
>
> Claus
>
> --Applescript
>
> tell application "TeXShop"
> get path of document of window 1
> set fileName to result
> end tell
> set scriptPath to (do shell script "dirname " & "~/Library/
> Flashmode/Subroutines/ex")
> set scriptPath to scriptPath & "/setnamets.scpt"
> set scriptName to POSIX file scriptPath as alias
> set scriptLiB to (load script scriptName)
> tell scriptLiB
> set {baseName, texName, pdfName, namePath, dirName,
> dirNameunquoted, logName, logPath, rtfName} to setnamets(fileName)
> end tell
>
>
>
> set shellScript to "cd " & dirName & ";"
> set shellScript to shellScript & "~/Library/TeXShop/bin/latexdbi "
> & texName
> do shell script shellScript
>
> set shellScript to "cd " & dirName & ";"
> set shellScript to shellScript & "~/Library/TeXShop/bin/dvipdfc "
> & baseName
> do shell script shellScript
> (*
> set pdfName to quotedform of pdfName
>
> set thePDF to POSIX file pdfName as alias
> *)
> tell document texName of application "TeXShop"
> activate
> refreshpdf
> end tell
>
>
> %%%%%%%%% end %%%%%%%%%%
>
> On Oct 13, 2005, at 12:02, Claus Gerhardt wrote:
>
>
>
>> Ingo,
>>
>> Try the following script and convince yourself that the required
>> subscripts or subroutines are all available.
>>
>> Claus
>>
>> %%%%%%%% begin %%%%%%%
>> --Applescript
>>
>> tell application "TeXShop"
>> get path of document of window 1
>> set fileName to result
>> end tell
>> set scriptPath to (do shell script "dirname " & "~/Library/
>> Flashmode/Subroutines/ex")
>> set scriptPath to scriptPath & "/setnamets.scpt"
>> set scriptName to POSIX file scriptPath as alias
>> set scriptLiB to (load script scriptName)
>> tell scriptLiB
>> set {baseName, texName, pdfName, namePath, dirName,
>> dirNameunquoted, logName, logPath, rtfName} to setnamets(fileName)
>> end tell
>>
>>
>>
>> set shellScript to "cd " & dirName & ";"
>> set shellScript to shellScript & "~/Library/TeXShop/bin/latexdbi
>> " & texname
>> do shell script shellScript
>>
>> set shellScript to "cd " & dirName & ";"
>> set shellScript to shellScript & "~/Library/TeXShop/bin/dvipdfc "
>> & basename
>> do shell script shellScript
>> (*
>> set pdfName to quotedform of pdfName
>>
>> set thePDF to POSIX file pdfName as alias
>> *)
>> tell document texName of application "TeXShop"
>> activate
>> refreshpdf
>> end tell
>>
>>
>> %%%%%%%%% end %%%%%%%%%%
>>
>> -- Save the subroutine setnamets.scpt in ~/Library/TeXShop/Scripts
>>
>> on setnamets(x)
>> set n to (number of characters of contents of x)
>> set fileNamequoted to quoted form of x
>> set windowName to do shell script "basename " & fileNamequoted
>> set m to (number of characters of contents of windowName)
>> set dirName to quoted form of (characters 1 thru (n - m - 1)
>> of x as string)
>> set dirNameunquoted to (characters 1 thru (n - m - 1) of x as
>> string)
>> set theText to contents of windowName as string
>>
>> set n to (number of characters of contents of theText)
>> set i to n as number
>>
>> repeat while i > 0
>> if character i of theText is equal to "." then
>> set m to i
>> exit repeat
>> else
>> set i to (i - 1)
>> end if
>> end repeat
>>
>> set baseName to (characters 1 thru (m - 1) of theText as string)
>> set texName to baseName & ".tex"
>> set namePath to dirNameunquoted & "/" & baseName as string
>> set pdfName to namePath & ".pdf" as string
>> set rtfName to namePath & ".rtf" as string
>> set logPath to namePath & ".log" as string
>> set logName to baseName & ".log" as string
>>
>> try
>> tell application "TeXShop"
>> save document texName
>> end tell
>> end try
>> return {baseName, texName, pdfName, namePath, dirName,
>> dirNameunquoted, logName, logPath, rtfName} as list
>> end setnamets
>>
>>
>> On Oct 13, 2005, at 2:30, Claus Gerhardt wrote:
>>
>>
>>
>>
>>> The command in the shell script should be
>>>
>>>
>>>
>>>
>>>
>>>> latexdb "$1"
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> Claus
>>>
>>>
>>> On Oct 13, 2005, at 1:12, Ingo Reich wrote:
>>>
>>>
>>>
>>>
>>>
>>>> Hi,
>>>> I'd like to use latexdb from within texshop. (latexdb is a
>>>> script based on python that enables one to connect to mySQL-
>>>> databases from within a latex-file: http://privat.hgesser.com/
>>>> software/latexdb/). I tried to adapt one of Claus Gerhardts
>>>> Scripts and came up with the one below. The applescript works
>>>> properly the first time it is called, the second time ii is
>>>> called however texshop complains that it can't locate the file
>>>> example.tex (in German: "Der Ort des Dokuments 'example.tex'
>>>> konnte nicht festgestellt werden"), and it wants me to "save
>>>> as ...". Any ideas what's going wrong here? Thanks,
>>>> Ingo
>>>>
>>>>
>>>>
>>>> %%%%%%%% begin %%%%%%%
>>>> --Applescript
>>>>
>>>> set scriptPath to (do shell script "dirname " & "~/Library/
>>>> TeXShop/Scripts/ex")
>>>> set scriptPath to scriptPath & "/setname.scpt"
>>>> set scriptName to POSIX file scriptPath as alias
>>>> set scriptLiB to (load script scriptName)
>>>> tell scriptLib
>>>> set frontName to setname(#NAMEPATH#,#TEXPATH#)
>>>> end tell
>>>>
>>>> set fileName to #NAMEPATH#
>>>> set n to (number of characters of contents of fileName)
>>>> set fileNamequoted to quoted form of fileName
>>>> set baseName to do shell script "basename " & fileNamequoted
>>>> set m to (number of characters of contents of baseName)
>>>> set dirName to quoted form of (characters 1 thru (n - m - 1) of
>>>> fileName as string)
>>>> set texName to baseName & ".tex"
>>>>
>>>> set shellScript to "cd " & dirName & ";"
>>>> set shellScript to shellScript & "~/Library/TeXShop/bin/
>>>> latexdbi " & baseName
>>>> do shell script shellScript
>>>>
>>>> tell application "TeXShop"
>>>> activate
>>>> open POSIX file #DVIPATH#
>>>> end tell
>>>> %%%%%%%%% end %%%%%%%%%%
>>>>
>>>>
>>>> where "latexdbi" is the following binary script:
>>>>
>>>> %%%%%%%% begin %%%%%%%%%%
>>>> #!/bin/tcsh
>>>> # latexdbi
>>>>
>>>> set path= ($path /usr/local/bin /usr/local/teTeX/bin/powerpc-
>>>> apple-darwin-current)
>>>>
>>>> latexdb "$1.tex"
>>>>
>>>> %%%%%%%%% end %%%%%%%%%%
>>>>
>>>> ------------------------- Info --------------------------
>>>> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
>>>> & FAQ: http://latex.yauh.de/faq/
>>>> TeX FAQ: http://www.tex.ac.uk/faq
>>>> List Archive: http://tug.org/pipermail/macostex-archives/
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>> ------------------------- Info --------------------------
>>> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
>>> & FAQ: http://latex.yauh.de/faq/
>>> TeX FAQ: http://www.tex.ac.uk/faq
>>> List Archive: http://tug.org/pipermail/macostex-archives/
>>>
>>>
>>>
>>>
>>>
>>
>> ------------------------- Info --------------------------
>> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
>> & FAQ: http://latex.yauh.de/faq/
>> TeX FAQ: http://www.tex.ac.uk/faq
>> List Archive: http://tug.org/pipermail/macostex-archives/
>>
>>
>>
>>
>
> ------------------------- Info --------------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
> & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Archive: http://tug.org/pipermail/macostex-archives/
>
>
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] altpdflatex - back compatibility please
From: "Morten Høgholm" <morten.hoegholm at gmail.com>
Date: Thu, 13 Oct 2005 13:59:27 +0200
On Thu, 13 Oct 2005 11:53:07 +0200, Bruno Voisin <bvoisin at mac.com>
wrote:
> Le 13 oct. 05 à 11:47, Joachim Kock a écrit :
>
>
>> TeXShop and other frontends should not be
>> forced to require the user to have a less-than-one-year-old tetex
>> installation!
>>
>
> That's the world we live in, however!
>
I agree. Users who are able to get a less than one year old TeXshop are
probably also capable of checking for updated packages in the i-
Installer
or running fink selfupdate.
--
Morten
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Ingo Reich" <ireich at mac.com>
Date: Thu, 13 Oct 2005 14:04:14 +0200
Claus, thanks for your kind help. The script works great, but texshop
still complains when I try to save the file after running latexdb.
The problem however seems not to relate to texshop since I got a
similar warning message when I tried to edit the source file in
alphax. It rather seems that latexdb changes some property of the tex-
file such that either the editor can't locate the file (texshop) or
it states that the file has been changed (alphax). The only way to
deal with that problem at the moment is: 1. edit file, 2. save file,
3. run your script, 4. close file, 5. open file, 6. edit file, 7.
save file etc. pp. -- not very concenient; probably a bug in latexdb.
Ingo
----------------------------------------------------------------------
Subject: Re: [OS X TeX] altpdflatex - back compatibility please
From: "Gerben Wierda" <Gerben.Wierda at rna.nl>
Date: Thu, 13 Oct 2005 14:19:02 +0200 (CEST)
Thanks for thinking along.
> Perhaps you forget how stable a thing tex (and gwtex) is. For 90
> percent
> of the tex users, there is no reason to upgrade, and there may be
> many old
> installations around. Certainly on this list, people are very
> advanced
> tex
> users and we are all very thankful for the constant development and
> improvements, and the new bells and whistles, but the average user
> (not
> subscribed to this list) may not need more than standard OT1
> encoded CM
> fonts, and a few AMS packages. This has been working perfectly
> well ever
> since your first distribution back in the previous millenium.
>
Yes, it has been a while, hasn't it? Anyway, the old stuff still works.
And people can still install TL2003 or TL2004 based TeX from me, but
these
now come with simpdftex instead of altpdftex.
> By removing those scripts, the frontend writer wishing to use the
> scripts
> is forced to either formally require a new version of tetex (gwtex) or
> write complicated instructions in the manual or 'readme',
> explaining that
> in certain distributions you have to do one thing, and in other
> distributions you have to do some other thing, and it is akward to
> describe
> precisely what versions because there are so many components
> involved and
> it is not clear which version number you should refer to or where
> the user
> can find this information.
>
simpdftex has been available for 1.5 years or so. So most people now
have
it. Those that do not can either stay with their old version
frontend, use
a newer frontend with an older TeX (and set their prefs), or update
TeX as
well as the frontend.
>> Re-introducing a back compatibility script would defeat the object of
>> the
>> transition completely so I am not going to do it.
>>
>
> Sorry for being stupid, but how does the error message work? Isn't
> it a
> script? Why does this error script not defeat the objective of the
> transition? Why is it better to have an error script (breaking
> existing
> functionality) than having the current symlinks?
>
I though it was unfriendly not to offer a warning so I have made the
transition as smooth as possible. First step: introduce simpdftex, one
year later (now) change altpdf*tex into a warning, next year, the
warning
goes away. I could have dropped the alt* stuff now but that would have
been harsh.
> I don't see any problem with the population of the bin/ directory.
> Nobody
> ever opens this directory anyway -- we are not talking a polished OSX
> folder where the presence of more than six items would be
> intimidating!
>
Computer scientists often go for elegance because they know that in the
long term they will be defeated by complexity if they don't.
Note: last year or the year before, TeX4ht had the same kind of
transition. No warning scripts just bang from multiple scripts to one
with
a different syntax.
> Compare with some other famous transitions: you can still write
> \documentstyle{article} in your source file and it will work. You can
> still say latex in the command line and it will invoke pdflatex
> with the
> appropriate parameters... Do these tricks defeat the objective of the
> transitions?
>
But some stuff stops working. Currently I get help requests for people
using old ways of detecting PDFTeX vs TeX (which do not work anymore
with
TL2005). And the changes in fmtutil and friends make up the bulk of
support requests. Changing engine preferences seems to be easy enough.
>> Backwards compatibility is not truly lost. You can still compile all
>> your old documents, the only thing that has changed is that the
>> convenience script for running tex, dvips and distiller has been
>> renamed
>> and changed its command line interface. In my book, backwards
>> compatibility is not lost of you still can get the same results
>> even if
>> you have to do different things to get those results.
>>
>
> Which book? And which edition? :-)
>
Ha, yes, you've got me there. I should spend time on writing my book
instead of maintaining and supporting a TeX redistribution. If I ever
finish it, you will all buy 100 copies for friends, family, work etc.,
right?
Tell you what: I could reintroduce the altpdf* scripts to run the
simpdftex instead but after a warning and a delay of 20 seconds. It
would
work, but it would be nasty enough to make people make the move.
I had to seriously rewrite my TeX i-Package scripts because it has to
handle a different mode of TeX configuration tools (the -sys tools) as
well as the older method (for e.g. TL2003 which I also support). I tried
to argue with Thoams Esser for a different approach, but I was too late.
He had already committed himself to the move a while back.
The frontend writers could check if simpdftex is available and otherwise
use altpdftex. That adds to their complexity, but hey, have you ever
read
the perl code of the configuration phase of the TeX i-Package? There you
can see what I have to do to remain compatible with 3 versions of TeX
on 2
hardware platforms, among other things.
If users do not upgrade TeX and they do not upgrade their frontend,
there
is no problem. If they upgrade their frontend, it is the frontend
designer
who decides what he supports and how. The same thing happens to me, look
in my TeX i-Package code and you'll still see support for old TeX
distribution layouts long since gone (texmf.macosx) and people having
upgraded over th elast years have generally not noticed what work was
done
in the background. Fonrtend designers can handle the changes in their
environment (that is in this case my TeX distribution) however they want
or not of course.
Anyway, thanks for thinking along. Shall I introduce the seriously
slowed
down nagging altpdf*tex scripts? I kind of think the idea is
humurous, but
maybe my sense of humour is broken.
G
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Date: Thu, 13 Oct 2005 14:30:47 +0200
Latexdb creates two additional files ending in ....tex.pre
and ....tex.debug, which probably are causing the trouble. Let me
suggest as possible solution:
Change your latexdbi shell script to
#!/bin/tcsh
# latexdbi
set path= ($path /usr/local/bin /usr/local/teTeX/bin/powerpc-apple-
darwin-current)
latexdb "$1"
rm -f "$1.pre"
rm -f "$1.debug"
Claus
On Oct 13, 2005, at 14:04, Ingo Reich wrote:
> Claus, thanks for your kind help. The script works great, but
> texshop still complains when I try to save the file after running
> latexdb. The problem however seems not to relate to texshop since I
> got a similar warning message when I tried to edit the source file
> in alphax. It rather seems that latexdb changes some property of
> the tex-file such that either the editor can't locate the file
> (texshop) or it states that the file has been changed (alphax). The
> only way to deal with that problem at the moment is: 1. edit file,
> 2. save file, 3. run your script, 4. close file, 5. open file, 6.
> edit file, 7. save file etc. pp. -- not very concenient; probably a
> bug in latexdb.
> Ingo
>
> ------------------------- Info --------------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
> & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Archive: http://tug.org/pipermail/macostex-archives/
>
>
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] altpdflatex - back compatibility please
From: "Fernando Pereira" <fcnpereira at mac.com>
Date: Thu, 13 Oct 2005 09:00:51 -0400
On Oct 13, 2005, at 5:47 AM, Joachim Kock wrote:
> By removing those scripts, the frontend writer wishing to use the
> scripts
> is forced to either formally require a new version of tetex (gwtex) or
> write complicated instructions in the manual or 'readme',
> explaining that
> in certain distributions you have to do one thing, and in other
> distributions you have to do some other thing, and it is akward to
> describe
> precisely what versions because there are so many components
> involved and
> it is not clear which version number you should refer to or where
> the user
> can find this information.
>
I understand your concern, but I think this is being blown way out of
proportion. The error message printed by the new alt*tex scripts is
pretty self explanatory, and it takes just a couple of minutes to
tell TeXShop to use simpdftex as the error message says. I see only
three potential issues with this:
1) people don't read the message carefully
2) people don't know how to act on the message
3) front-ends get confused
I teach intro CS, and I see 1) all the time, especially regarding
problem statements in assignments. My reaction to that is, part of
growing up is learning to take attention to one's surroundings. My
reaction to 2) is, that's what the documentation for the various
front-ends is for. RTFM works much of the time. Not to be
cantankerous, but using software is a two-way street. The software
writer should try to do the best they can within their resource
limits, but the user also has a responsibility to be aware that they
are using a complicated machine with many parts. We like to pretend
that everything should be transparent in software, but that's a
dangerous delusion.
As for 3), it would be quite easy for a front-end to check for the
existence of simpdftex and if it is not available, try alt*tex. Among
all configurations complexities, this one seems pretty trivial.
-- F
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Ingo Reich" <ireich at mac.com>
Date: Thu, 13 Oct 2005 15:04:00 +0200
it cleans up my folder, but doesn't help with the original problem :-(
Sorry to have already stolen so much of your time.
Ingo
Am 13.10.2005 um 14:30 schrieb Claus Gerhardt:
> Latexdb creates two additional files ending in ....tex.pre
> and ....tex.debug, which probably are causing the trouble. Let me
> suggest as possible solution:
>
> Change your latexdbi shell script to
>
> #!/bin/tcsh
> # latexdbi
>
> set path= ($path /usr/local/bin /usr/local/teTeX/bin/powerpc-
> apple-darwin-current)
>
> latexdb "$1"
> rm -f "$1.pre"
> rm -f "$1.debug"
>
> Claus
>
> On Oct 13, 2005, at 14:04, Ingo Reich wrote:
>
>
>
>> Claus, thanks for your kind help. The script works great, but
>> texshop still complains when I try to save the file after running
>> latexdb. The problem however seems not to relate to texshop since
>> I got a similar warning message when I tried to edit the source
>> file in alphax. It rather seems that latexdb changes some property
>> of the tex-file such that either the editor can't locate the file
>> (texshop) or it states that the file has been changed (alphax).
>> The only way to deal with that problem at the moment is: 1. edit
>> file, 2. save file, 3. run your script, 4. close file, 5. open
>> file, 6. edit file, 7. save file etc. pp. -- not very concenient;
>> probably a bug in latexdb.
>> Ingo
>>
>> ------------------------- Info --------------------------
>> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
>> & FAQ: http://latex.yauh.de/faq/
>> TeX FAQ: http://www.tex.ac.uk/faq
>> List Archive: http://tug.org/pipermail/macostex-archives/
>>
>>
>>
>>
>
> ------------------------- Info --------------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
> & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Archive: http://tug.org/pipermail/macostex-archives/
>
>
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Herbert Schulz" <herbs at wideopenwest.com>
Date: Thu, 13 Oct 2005 08:33:53 -0500
On Oct 13, 2005, at 12:46 AM, Ingo Reich wrote:
> Herb,
> last night I tried (almost: tcsh) exactly what you suggested, and
> it didn't work at all; this morning I retried (bash), and it does
> work on the first run. To be more precise: it does work as long as
> I don't have to save my file before calling latexdb; if I need to
> save changes in the file, texshop still complains the way I
> mentioned in my last mail.
>
> Another question: Since latexdb only generates a dvi-file, not a
> pdf-file, I tried to extend the script as follows:
>
> #!/bin/bash
> latexdb "$1"
> dvipdfm "$1"
>
> But now dvipdfm looks for "example.tex.dvi" instead of
> "example.dvi", and gets stuck.
> Sorry for being so ignorant.
> Ingo
>
> P.S. to Claus: I did try it both ways, i.e. with and without the
> extension .tex, but the problem persisted.
>
>
Howdy,
The $1 is the full name, with the .tex; e.g., fname.tex. To get the
base name you need to use `basename "$1" .tex` so a simple addition
to get it right is:
#!/bin/bash
basefname=$(basename "$1" .tex)
latexdb "$1"
dvipdfm "${basefname}"
In terms of your other problem... What is the output of latexdb? Does
it change the .tex file?
Good Luck,
Herb Schulz
(herbs at wideopenwest.com)
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Re: Maarten's Bugs for MacTeX Distribution
From: "Chris Goedde" <cgoedde at condor.depaul.edu>
Date: Thu, 13 Oct 2005 09:18:33 -0500
On Oct 10, 2005, at 4:04 PM, Richard Koch wrote:
> When we originally made the MacTeX package, we talked about requiring
> at least
> system 10.3. The long list of bugs Maarten discovered on 10.2 suggests
> that we
> should revisit this decision and probably require 10.3.
>
>
I think that supporting only (current OS version) + (previous OS
version) is completely reasonable, so I would approve of dropping
support for 10.2 at this time.
Chris
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Ingo Reich" <ireich at mac.com>
Date: Thu, 13 Oct 2005 15:59:32 +0200
Am 13.10.2005 um 15:33 schrieb Herbert Schulz:
>
> On Oct 13, 2005, at 12:46 AM, Ingo Reich wrote:
>
>
>
>> Herb,
>> last night I tried (almost: tcsh) exactly what you suggested, and
>> it didn't work at all; this morning I retried (bash), and it does
>> work on the first run. To be more precise: it does work as long as
>> I don't have to save my file before calling latexdb; if I need to
>> save changes in the file, texshop still complains the way I
>> mentioned in my last mail.
>>
>> Another question: Since latexdb only generates a dvi-file, not a
>> pdf-file, I tried to extend the script as follows:
>>
>> #!/bin/bash
>> latexdb "$1"
>> dvipdfm "$1"
>>
>> But now dvipdfm looks for "example.tex.dvi" instead of
>> "example.dvi", and gets stuck.
>> Sorry for being so ignorant.
>> Ingo
>>
>> P.S. to Claus: I did try it both ways, i.e. with and without the
>> extension .tex, but the problem persisted.
>>
>>
>>
>
> Howdy,
>
> The $1 is the full name, with the .tex; e.g., fname.tex. To get the
> base name you need to use `basename "$1" .tex` so a simple addition
> to get it right is:
>
> #!/bin/bash
> basefname=$(basename "$1" .tex)
> latexdb "$1"
> dvipdfm "${basefname}"
>
> In terms of your other problem... What is the output of latexdb?
> Does it change the .tex file?
>
> Good Luck,
>
> Herb Schulz
> (herbs at wideopenwest.com)
>
>
>
Hi Herb, I can't see that the file is in any way different than
before, so probably it doesn't. But, as Claus pointed out, running
latexdb on example.tex generates additional files with tex endings:
"example.tex.1", "example.tex.pre.1" and "example.tex.texdb.1";
during its run it also generates a then removed file called
"example.backup" which suggests that latexdb does in fact not only
read example.tex. What it does exactly, however, is completely
obscure to me. Ingo
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Ingo Reich" <ireich at mac.com>
Date: Thu, 13 Oct 2005 16:35:18 +0200
Am 13.10.2005 um 15:59 schrieb Ingo Reich:
> Am 13.10.2005 um 15:33 schrieb Herbert Schulz:
>
>
>
>>
>> On Oct 13, 2005, at 12:46 AM, Ingo Reich wrote:
>>
>>
>>
>>
>>> Herb,
>>> last night I tried (almost: tcsh) exactly what you suggested, and
>>> it didn't work at all; this morning I retried (bash), and it does
>>> work on the first run. To be more precise: it does work as long
>>> as I don't have to save my file before calling latexdb; if I need
>>> to save changes in the file, texshop still complains the way I
>>> mentioned in my last mail.
>>>
>>> Another question: Since latexdb only generates a dvi-file, not
>>> a pdf-file, I tried to extend the script as follows:
>>>
>>> #!/bin/bash
>>> latexdb "$1"
>>> dvipdfm "$1"
>>>
>>> But now dvipdfm looks for "example.tex.dvi" instead of
>>> "example.dvi", and gets stuck.
>>> Sorry for being so ignorant.
>>> Ingo
>>>
>>> P.S. to Claus: I did try it both ways, i.e. with and without the
>>> extension .tex, but the problem persisted.
>>>
>>>
>>>
>>>
>>
>> Howdy,
>>
>> The $1 is the full name, with the .tex; e.g., fname.tex. To get
>> the base name you need to use `basename "$1" .tex` so a simple
>> addition to get it right is:
>>
>> #!/bin/bash
>> basefname=$(basename "$1" .tex)
>> latexdb "$1"
>> dvipdfm "${basefname}"
>>
>> In terms of your other problem... What is the output of latexdb?
>> Does it change the .tex file?
>>
>> Good Luck,
>>
>> Herb Schulz
>> (herbs at wideopenwest.com)
>>
>>
>>
>>
>
> Hi Herb, I can't see that the file is in any way different than
> before, so probably it doesn't. But, as Claus pointed out, running
> latexdb on example.tex generates additional files with tex endings:
> "example.tex.1", "example.tex.pre.1" and "example.tex.texdb.1";
> during its run it also generates a then removed file called
> "example.backup" which suggests that latexdb does in fact not only
> read example.tex. What it does exactly, however, is completely
> obscure to me. Ingo
>
>
Sorry, it's "example.tex.backup". latexdb just failed to compile
because I made some mistake with the name of the mySQL table, and the
file then didn't get deleted -- and the file "example.tex" has been
changed (part of it has been removed). So probably latexdb renames
the original file as "example.tex.backup" and writes a new file
"example.tex" which is identical to "example.tex.backup" if (and only
if?) everything compiles correctly.
Ingo
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Date: Thu, 13 Oct 2005 16:49:21 +0200
Apparently latexdb creates more files with the wrong endings then is
mentioned in its tutorial. Try to remove all files with offending
endings by adding appropiate commands in latexdbi.
Claus
On Oct 13, 2005, at 15:04, Ingo Reich wrote:
> it cleans up my folder, but doesn't help with the original problem :-(
> Sorry to have already stolen so much of your time.
> Ingo
>
>
> Am 13.10.2005 um 14:30 schrieb Claus Gerhardt:
>
>
>
>> Latexdb creates two additional files ending in ....tex.pre
>> and ....tex.debug, which probably are causing the trouble. Let me
>> suggest as possible solution:
>>
>> Change your latexdbi shell script to
>>
>> #!/bin/tcsh
>> # latexdbi
>>
>> set path= ($path /usr/local/bin /usr/local/teTeX/bin/powerpc-
>> apple-darwin-current)
>>
>> latexdb "$1"
>> rm -f "$1.pre"
>> rm -f "$1.debug"
>>
>> Claus
>>
>> On Oct 13, 2005, at 14:04, Ingo Reich wrote:
>>
>>
>>
>>
>>> Claus, thanks for your kind help. The script works great, but
>>> texshop still complains when I try to save the file after running
>>> latexdb. The problem however seems not to relate to texshop since
>>> I got a similar warning message when I tried to edit the source
>>> file in alphax. It rather seems that latexdb changes some
>>> property of the tex-file such that either the editor can't locate
>>> the file (texshop) or it states that the file has been changed
>>> (alphax). The only way to deal with that problem at the moment
>>> is: 1. edit file, 2. save file, 3. run your script, 4. close
>>> file, 5. open file, 6. edit file, 7. save file etc. pp. -- not
>>> very concenient; probably a bug in latexdb.
>>> Ingo
>>>
>>> ------------------------- Info --------------------------
>>> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
>>> & FAQ: http://latex.yauh.de/faq/
>>> TeX FAQ: http://www.tex.ac.uk/faq
>>> List Archive: http://tug.org/pipermail/macostex-archives/
>>>
>>>
>>>
>>>
>>>
>>
>> ------------------------- Info --------------------------
>> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
>> & FAQ: http://latex.yauh.de/faq/
>> TeX FAQ: http://www.tex.ac.uk/faq
>> List Archive: http://tug.org/pipermail/macostex-archives/
>>
>>
>>
>>
>
> ------------------------- Info --------------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
> & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Archive: http://tug.org/pipermail/macostex-archives/
>
>
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Date: Thu, 13 Oct 2005 16:55:08 +0200
I think your present directory is cluttered with too many
example.tex's. Cretae a new file example-ingo.tex and run latexdb
only once to see which additional files are created. Then tell the
shell script to remove all files with offending endings,
i.e., .tex.whatever.
Claus
On Oct 13, 2005, at 15:59, Ingo Reich wrote:
> Am 13.10.2005 um 15:33 schrieb Herbert Schulz:
>
>
>
>>
>> On Oct 13, 2005, at 12:46 AM, Ingo Reich wrote:
>>
>>
>>
>>
>>> Herb,
>>> last night I tried (almost: tcsh) exactly what you suggested, and
>>> it didn't work at all; this morning I retried (bash), and it does
>>> work on the first run. To be more precise: it does work as long
>>> as I don't have to save my file before calling latexdb; if I need
>>> to save changes in the file, texshop still complains the way I
>>> mentioned in my last mail.
>>>
>>> Another question: Since latexdb only generates a dvi-file, not
>>> a pdf-file, I tried to extend the script as follows:
>>>
>>> #!/bin/bash
>>> latexdb "$1"
>>> dvipdfm "$1"
>>>
>>> But now dvipdfm looks for "example.tex.dvi" instead of
>>> "example.dvi", and gets stuck.
>>> Sorry for being so ignorant.
>>> Ingo
>>>
>>> P.S. to Claus: I did try it both ways, i.e. with and without the
>>> extension .tex, but the problem persisted.
>>>
>>>
>>>
>>>
>>
>> Howdy,
>>
>> The $1 is the full name, with the .tex; e.g., fname.tex. To get
>> the base name you need to use `basename "$1" .tex` so a simple
>> addition to get it right is:
>>
>> #!/bin/bash
>> basefname=$(basename "$1" .tex)
>> latexdb "$1"
>> dvipdfm "${basefname}"
>>
>> In terms of your other problem... What is the output of latexdb?
>> Does it change the .tex file?
>>
>> Good Luck,
>>
>> Herb Schulz
>> (herbs at wideopenwest.com)
>>
>>
>>
>>
>
> Hi Herb, I can't see that the file is in any way different than
> before, so probably it doesn't. But, as Claus pointed out, running
> latexdb on example.tex generates additional files with tex endings:
> "example.tex.1", "example.tex.pre.1" and "example.tex.texdb.1";
> during its run it also generates a then removed file called
> "example.backup" which suggests that latexdb does in fact not only
> read example.tex. What it does exactly, however, is completely
> obscure to me. Ingo
>
>
>
>
>
> ------------------------- Info --------------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
> & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Archive: http://tug.org/pipermail/macostex-archives/
>
>
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Herbert Schulz" <herbs at wideopenwest.com>
Date: Thu, 13 Oct 2005 10:16:38 -0500
On Oct 13, 2005, at 9:35 AM, Ingo Reich wrote:
>
> Sorry, it's "example.tex.backup". latexdb just failed to compile
> because I made some mistake with the name of the mySQL table, and
> the file then didn't get deleted -- and the file "example.tex" has
> been changed (part of it has been removed). So probably latexdb
> renames the original file as "example.tex.backup" and writes a new
> file "example.tex" which is identical to "example.tex.backup" if
> (and only if?) everything compiles correctly.
> Ingo
>
>
Howdy,
Then it sounds as though TeXShop doesn't know that the original file
has changed. Wow, that is definitely a bad practice!
Good Luck,
Herb Schulz
(herbs at wideopenwest.com)
----------------------------------------------------------------------
Subject: Re: [OS X TeX] altpdflatex - back compatibility please
From: "Richard Koch" <koch at math.uoregon.edu>
Date: Thu, 13 Oct 2005 08:38:44 -0700
Folks,
It is probably stupid of me to comment here because I haven't yet
released
TeXShop 2.04 and 1.41 (I'm concentrating on the MacTeX installer).
Joachim Kock makes a good point about making sure software works
for users who don't upgrade. He wrote
> By removing those scripts, the frontend writer wishing to use the
> scripts
> is forced to either formally require a new version of tetex (gwtex) or
> write complicated instructions in the manual or 'readme',
> explaining that
> in certain distributions you have to do one thing, and in other
> distributions you have to do some other thing, and it is akward to
> describe
> precisely what versions because there are so many components
> involved and
> it is not clear which version number you should refer to or where
> the user
> can find this information.
>
Actually, the upcoming TeXShops work like this:
When the user typesets using the script specified in TeXShop's
tex + dvi + distiller preference, the program checks to see if
this preference is
altpdftex ***. If it is, then TeXShop checks to see if simpdftex
is available in
the TeX binary directory. And if so, TeXShop changes altpdftex to
simpdftex tex in the preference, keeping any other flags that
were present.
So this should work automatically. I'll try to get this version
released fairly soon.
Dick
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Date: Thu, 13 Oct 2005 17:43:10 +0200
The additional files created by latexdb are not the cause of the
trouble with saving the original, but as Ingo has already hinted
latexdb must change the name of original to .backup.
The only remedy I can think of, except of course rewriting latexdb,
is the following Applescript
Claus
--Applescript
tell application "TeXShop"
get path of document of window 1
set fileName to result
end tell
set scriptPath to (do shell script "dirname " & "~/Library/
TeXShop/Scripts/ex")
set scriptPath to scriptPath & "/setnamets.scpt"
set scriptName to POSIX file scriptPath as alias
set scriptLiB to (load script scriptName)
tell scriptLiB
set {baseName, texName, pdfName, namePath, dirName,
dirNameunquoted, logName, logPath, rtfName} to setnamets(fileName)
end tell
set theFile to POSIX file fileName as string
tell application "TeXShop"
close document texName
end tell
set shellScript to "cd " & dirName & ";"
set shellScript to shellScript & "~/Library/TeXShop/bin/latexdbi " &
texName
do shell script shellScript
set shellScript to "cd " & dirName & ";"
set shellScript to shellScript & "~/Library/TeXShop/bin/dvipdfc " &
baseName
do shell script shellScript
(*
set pdfName to quotedform of pdfName
set thePDF to POSIX file pdfName as alias
*)
tell application "TeXShop"
open theFile
end tell
tell document texName of application "TeXShop"
activate
refreshpdf
end tell
On Oct 13, 2005, at 15:04, Ingo Reich wrote:
> it cleans up my folder, but doesn't help with the original problem :-(
> Sorry to have already stolen so much of your time.
> Ingo
>
>
> Am 13.10.2005 um 14:30 schrieb Claus Gerhardt:
>
>
>
>
>> Latexdb creates two additional files ending in ....tex.pre
>> and ....tex.debug, which probably are causing the trouble. Let me
>> suggest as possible solution:
>>
>> Change your latexdbi shell script to
>>
>> #!/bin/tcsh
>> # latexdbi
>>
>> set path= ($path /usr/local/bin /usr/local/teTeX/bin/powerpc-
>> apple-darwin-current)
>>
>> latexdb "$1"
>> rm -f "$1.pre"
>> rm -f "$1.debug"
>>
>> Claus
>>
>> On Oct 13, 2005, at 14:04, Ingo Reich wrote:
>>
>>
>>
>>
>>
>>> Claus, thanks for your kind help. The script works great, but
>>> texshop still complains when I try to save the file after running
>>> latexdb. The problem however seems not to relate to texshop since
>>> I got a similar warning message when I tried to edit the source
>>> file in alphax. It rather seems that latexdb changes some
>>> property of the tex-file such that either the editor can't locate
>>> the file (texshop) or it states that the file has been changed
>>> (alphax). The only way to deal with that problem at the moment
>>> is: 1. edit file, 2. save file, 3. run your script, 4. close
>>> file, 5. open file, 6. edit file, 7. save file etc. pp. -- not
>>> very concenient; probably a bug in latexdb.
>>> Ingo
>>>
>>> ------------------------- Info --------------------------
>>> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
>>> & FAQ: http://latex.yauh.de/faq/
>>> TeX FAQ: http://www.tex.ac.uk/faq
>>> List Archive: http://tug.org/pipermail/macostex-archives/
>>>
>>>
>>>
>>>
>>>
>>>
>>
>> ------------------------- Info --------------------------
>> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
>> & FAQ: http://latex.yauh.de/faq/
>> TeX FAQ: http://www.tex.ac.uk/faq
>> List Archive: http://tug.org/pipermail/macostex-archives/
>>
>>
>>
>>
>>
>
> ------------------------- Info --------------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
> & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Archive: http://tug.org/pipermail/macostex-archives/
>
>
>
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Date: Thu, 13 Oct 2005 18:03:00 +0200
The additional files created by latexdb are not the cause of the
trouble with saving the original, but as Ingo has already hinted
latexdb must change the name of original to .backup.
The only remedy I can think of, except of course rewriting latexdb,
is the following Applescript
Claus
--Applescript
tell application "TeXShop"
get path of document of window 1
set fileName to result
end tell
set scriptPath to (do shell script "dirname " & "~/Library/
TeXShop/Scripts/ex")
set scriptPath to scriptPath & "/setnamets.scpt"
set scriptName to POSIX file scriptPath as alias
set scriptLiB to (load script scriptName)
tell scriptLiB
set {baseName, texName, pdfName, namePath, dirName,
dirNameunquoted, logName, logPath, rtfName} to setnamets(fileName)
end tell
set theFile to POSIX file fileName as string
tell application "TeXShop"
close document texName
end tell
set shellScript to "cd " & dirName & ";"
set shellScript to shellScript & "~/Library/TeXShop/bin/latexdbi " &
texName
do shell script shellScript
set shellScript to "cd " & dirName & ";"
set shellScript to shellScript & "~/Library/TeXShop/bin/dvipdfc " &
baseName
do shell script shellScript
(*
set pdfName to quotedform of pdfName
set thePDF to POSIX file pdfName as alias
*)
tell application "TeXShop"
open theFile
end tell
tell document texName of application "TeXShop"
activate
refreshpdf
end tell
On Oct 13, 2005, at 15:04, Ingo Reich wrote:
> it cleans up my folder, but doesn't help with the original problem :-(
> Sorry to have already stolen so much of your time.
> Ingo
>
>
> Am 13.10.2005 um 14:30 schrieb Claus Gerhardt:
>
>
>
>
>
>> Latexdb creates two additional files ending in ....tex.pre
>> and ....tex.debug, which probably are causing the trouble. Let me
>> suggest as possible solution:
>>
>> Change your latexdbi shell script to
>>
>> #!/bin/tcsh
>> # latexdbi
>>
>> set path= ($path /usr/local/bin /usr/local/teTeX/bin/powerpc-
>> apple-darwin-current)
>>
>> latexdb "$1"
>> rm -f "$1.pre"
>> rm -f "$1.debug"
>>
>> Claus
>>
>> On Oct 13, 2005, at 14:04, Ingo Reich wrote:
>>
>>
>>
>>
>>
>>
>>> Claus, thanks for your kind help. The script works great, but
>>> texshop still complains when I try to save the file after running
>>> latexdb. The problem however seems not to relate to texshop since
>>> I got a similar warning message when I tried to edit the source
>>> file in alphax. It rather seems that latexdb changes some
>>> property of the tex-file such that either the editor can't locate
>>> the file (texshop) or it states that the file has been changed
>>> (alphax). The only way to deal with that problem at the moment
>>> is: 1. edit file, 2. save file, 3. run your script, 4. close
>>> file, 5. open file, 6. edit file, 7. save file etc. pp. -- not
>>> very concenient; probably a bug in latexdb.
>>> Ingo
>>>
>>> ------------------------- Info --------------------------
>>> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
>>> & FAQ: http://latex.yauh.de/faq/
>>> TeX FAQ: http://www.tex.ac.uk/faq
>>> List Archive: http://tug.org/pipermail/macostex-archives/
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>> ------------------------- Info --------------------------
>> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
>> & FAQ: http://latex.yauh.de/faq/
>> TeX FAQ: http://www.tex.ac.uk/faq
>> List Archive: http://tug.org/pipermail/macostex-archives/
>>
>>
>>
>>
>>
>>
>
> ------------------------- Info --------------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
> & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Archive: http://tug.org/pipermail/macostex-archives/
>
>
>
>
>
----------------------------------------------------------------------
Subject: Flashmode and pdftex
From: "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Date: Thu, 13 Oct 2005 20:22:59 +0200
I just noticed that Flashmode also works with pdftex instead of
pdflatex. If you want to use it with pdftex, simply replace in one of
the shell scripts, e.g., flashmode-ts-1, the line
pdflatex --shell-escape "$1"
by
pdftex --shell-escape "$1"
Claus
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Ingo Reich" <ireich at mac.com>
Date: Thu, 13 Oct 2005 22:13:49 +0200
Thanks to Claus, Herb and Peter for spending their time to solve my
problem.
Everything works fine now. Ingo
Am 13.10.2005 um 18:03 schrieb Claus Gerhardt:
> The additional files created by latexdb are not the cause of the
> trouble with saving the original, but as Ingo has already hinted
> latexdb must change the name of original to .backup.
>
> The only remedy I can think of, except of course rewriting latexdb,
> is the following Applescript
>
> Claus
>
>
> --Applescript
>
> tell application "TeXShop"
> get path of document of window 1
> set fileName to result
> end tell
> set scriptPath to (do shell script "dirname " & "~/Library/
> TeXShop/Scripts/ex")
> set scriptPath to scriptPath & "/setnamets.scpt"
> set scriptName to POSIX file scriptPath as alias
> set scriptLiB to (load script scriptName)
> tell scriptLiB
> set {baseName, texName, pdfName, namePath, dirName,
> dirNameunquoted, logName, logPath, rtfName} to setnamets(fileName)
> end tell
>
> set theFile to POSIX file fileName as string
> tell application "TeXShop"
> close document texName
> end tell
>
> set shellScript to "cd " & dirName & ";"
> set shellScript to shellScript & "~/Library/TeXShop/bin/latexdbi "
> & texName
> do shell script shellScript
>
> set shellScript to "cd " & dirName & ";"
> set shellScript to shellScript & "~/Library/TeXShop/bin/dvipdfc "
> & baseName
> do shell script shellScript
> (*
> set pdfName to quotedform of pdfName
>
> set thePDF to POSIX file pdfName as alias
> *)
> tell application "TeXShop"
> open theFile
> end tell
>
> tell document texName of application "TeXShop"
> activate
> refreshpdf
> end tell
>
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Peter Dyballa" <Peter_Dyballa at Web.DE>
Date: Thu, 13 Oct 2005 22:59:15 +0200
Am 13.10.2005 um 17:16 schrieb Herbert Schulz:
> Then it sounds as though TeXShop doesn't know that the original file
> has changed. Wow, that is definitely a bad practice!
>
>
Bad practice by whom or by what?
To me it's TeXShop that's incorrectly working. All editors I know
become aware of a change in the file they've loaded before for editing.
And TeXShop notices this with PDF files already. Why is it failing with
a TeX file?!
I think it's a necessary enhancement to sense whether the TeX input
file has changed.
I am CC'ing my answer to Richard Koch. Could be he's not aware of this
and not paying attention to this thread because of other work.
Approximately 1h ago I opened a TeX file in TeXShop 1.40 on Panther
(Mac OS X 10.3.9). Then, in Terminal, I attached twice with 'cat >>
file' comments to the file -- TeXShop takes no notice!
--
Greetings
Pete
Make it simple, as simple as possible but no simpler. (Albert Einstein)
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Date: Thu, 13 Oct 2005 23:21:18 +0200
I think you misunderstood what happened: The open file has been
renamed by the shell script and TS isn't aware of it. Even if it
were, like BBEdit, e.g., this wouldn't be much helpful, because
subsequent typesettings and reruns of the shell script would result
in very awkward and long filenames.
In my opinion the script latexdb is simply badly written in this
respect. If you want to backup a file, then you should produce a copy
with a different name and not rename the original and give the copy
the old name.
Claus
On Oct 13, 2005, at 22:59, Peter Dyballa wrote:
>
> Am 13.10.2005 um 17:16 schrieb Herbert Schulz:
>
>
>
>> Then it sounds as though TeXShop doesn't know that the original
>> file has changed. Wow, that is definitely a bad practice!
>>
>>
>>
>
> Bad practice by whom or by what?
>
> To me it's TeXShop that's incorrectly working. All editors I know
> become aware of a change in the file they've loaded before for
> editing. And TeXShop notices this with PDF files already. Why is it
> failing with a TeX file?!
>
> I think it's a necessary enhancement to sense whether the TeX input
> file has changed.
>
>
> I am CC'ing my answer to Richard Koch. Could be he's not aware of
> this and not paying attention to this thread because of other work.
> Approximately 1h ago I opened a TeX file in TeXShop 1.40 on Panther
> (Mac OS X 10.3.9). Then, in Terminal, I attached twice with 'cat >>
> file' comments to the file -- TeXShop takes no notice!
>
> --
> Greetings
>
> Pete
>
> Make it simple, as simple as possible but no simpler. (Albert
> Einstein)
>
> ------------------------- Info --------------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
> & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Archive: http://tug.org/pipermail/macostex-archives/
>
>
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Claus Gerhardt" <gerhardt at math.uni-heidelberg.de>
Date: Thu, 13 Oct 2005 23:39:26 +0200
TS knows when the input file has changed otherwise Flashmode wouldn't
work with TS, it only doesn't display the change automatically. There
is an Applescript command
tell document "fileName" of application "TeXShop"
refreshtext
end tell
for this.
Claus
On Oct 13, 2005, at 22:59, Peter Dyballa wrote:
> I think it's a necessary enhancement to sense whether the TeX input
> file has changed.
>
>
> I am CC'ing my answer to Richard Koch. Could be he's not aware of
> this and not paying attention to this thread because of other work.
> Approximately 1h ago I opened a TeX file in TeXShop 1.40 on Panther
> (Mac OS X 10.3.9). Then, in Terminal, I attached twice with 'cat >>
> file' comments to the file -- TeXShop takes no notice!
>
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Peter Dyballa" <Peter_Dyballa at Web.DE>
Date: Fri, 14 Oct 2005 00:04:09 +0200
Am 13.10.2005 um 23:21 schrieb Claus Gerhardt:
> In my opinion the script latexdb is simply badly written in this
> respect.
>
Yes, that's my impression too from what I've read. Beside this specific
problem TeXShop should notice when the TeX source changes, as other
editors do. GNU Emacs allows to update the old contents with the new
one or to edit the old and save it finally under a different name. Or
to save the old contents without any alteration under a new name.
--
Mit friedvollen Grüßen
Pete
When you meet a master swordsman,
show him your sword.
When you meet a man who is not a poet,
do not show him your poem.
-- Rinzai, ninth century Zen master
----------------------------------------------------------------------
Subject: Re: [OS X TeX] latexdb & texshop
From: "Peter Dyballa" <Peter_Dyballa at Web.DE>
Date: Fri, 14 Oct 2005 00:16:00 +0200
Am 13.10.2005 um 23:39 schrieb Claus Gerhardt:
> TS knows when the input file has changed otherwise Flashmode wouldn't
> work with TS, it only doesn't display the change automatically. There
> is an Applescript command
>
> tell document "fileName" of application "TeXShop"
> refreshtext
> end tell
>
> for this.
>
>
This seems to be like the refresh button in some Internet browser. And
the browser too does not notice when a remote file has changed.
I doubt that you're right! When I do 'cat >> file' and then make
TeXShop compile, it compiles that version it loaded, maybe, days
before!
If TexShop notices a change in the TeX source it could at least raise a
flag or change a modeline -- or ask, as after having edited, whether it
should save first before compiling!
--
Mit friedvollen Grüßen
Pete
"I wouldn't recommend sex, drugs or insanity for everyone, but they've
always worked for me."
-- Hunter S. Thompson
----------------------------------------------------------------------
End of MacOSX-TeX Digest
------------------------- Info --------------------------
Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
& FAQ: http://latex.yauh.de/faq/
TeX FAQ: http://www.tex.ac.uk/faq
List Archive: http://tug.org/pipermail/macostex-archives/
------------------------- Info --------------------------
Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
& FAQ: http://latex.yauh.de/faq/
TeX FAQ: http://www.tex.ac.uk/faq
List Archive: http://tug.org/pipermail/macostex-archives/
More information about the macostex-archives
mailing list