[OS X TeX] FontForge and TeX i-Package update
Gerben.Wierda at rna.nl
Mon Mar 21 11:37:58 EST 2005
> Le 21 mars 05, à 16:49, Gerben Wierda a écrit :
>> This looks like a fontforge bug. It should not try to open an X11
>> if it is just running a script. I'll investigate.
> Could this be a bug inside convert.pe? The man page for fontforge says:
>> -script file
>> Execute the script named file. Does not open the X
>> This must be the first argument passed to fontforge.
>> Any other
>> arguments are handled by the scriptfile itself. Any
>> other com-
>> mand line arguments will be passed to the script. The
>> contains a command interpreter which allows access to
>> most but
>> not all of its interactive features. If a scriptfile
>> is exe-
>> cutable, and if its first line contains the string
>> then the argument -script may be omitted. This means
>> that font-
>> forge can be used as an interpreter.
> However the first line of convert.pe does not contain the string
> "fontforge", but "pfaedit":
> Not sure this is the correct explanation, though.
It isn't ;-)
It says pfaedit because the script also works with versions of fontforge
form before the renaming from pfaedit to fontforge. My fontforge
installation mintains pfaedit as a symlink to fontforge, just to be
friendly. It does mean that my script does not work with a hand-installed
fontforge, unless you create the symlink yourself. But requests for help
following from that possible scenario (currently 0) I can handle...
This was not a bug at all. When I read the problem report I assumed it was
a problem with the TeX i-Package and reacted accordingly. But it had to do
with starting fontforge from the shell.
So, there is no bug and I reacted too soon.
--------------------- 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 Post: <mailto:MacOSX-TeX at email.esm.psu.edu>
More information about the MacOSX-TeX