----- Original Message -----
From: "JeeBee" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, March 02, 2006 4:06 AM
Subject: Re: newly downloaded font problem
Thanks Helge and Paul.
I would prefer some construct like
\require{my_file.foo}
or \dependency{my_file.foo}
That does absolutely nothing but making lyx copy this file
to the temp directory as well.
If that would be possible ...
I tried copying all related (even a bit too much) to my ~/.tex/fonts dir.
(it does find style files there without problem)
Also to ~/.tex/fonts/tfm and ~/.tex/fonts/vf.
But apparantly it is not looking there because I get the same error.
Also to ~/.tex now without success.
It just does not seem to work before I copy
those file to lyx temp dir in /tmp
I am going to share some thoughts with you on this subject.
I use Windows more than Linux so may use that terminology
but both Miktex and TeTex have the same important functions.
You present a fairly thorough report but you leave out texhash
or equivalently in Windows Miktex Options->Refresh Now
which refreshes the filename database (fndb) which keeps track
of new packages installed and fonts. The files must be put in the
approximately right directory and the next step is to run texhash.
So if you are doing that it should be in your report so people
don't wonder about itsince failing to run texhash is a frequent
cause of a newly installed font not working. The common place
to install (new) fonts is in /texmf... or /localtexmf.... and then
run Miktex Options Refresh Now or texhash.
But I think you can add or have more than those two tex root
directories. It is safer not to have spaces in your path or filenames.
I think you could create an additional tex root directory /usr/local/
My_LyX_Project, place fonts there and have them read into the fndb.
Then they become available for general use. I think localtexmf is fndb1,
texmf is fndb2 a new tex root is fndb3.
In Miktex if you add a new root directory the database refresh is run
automatically, you can change which directory is considered local,
and the order in which they are read. There is a nice GUI. I think
Linux has inittex or texconfig to do this. Also I'm not sure that you
can get away without emulating some of inner tex directory structure
of /texmf. But I'm sure it can be made to work, but to what advantage?
I don't think there is much you can do inside a document to determine
which files are copied to the tmp directory. For instance in LyX137
if you had jpeg and eps images to be included, you could run dvipdfm
to make a .pdf output file. Files with a *.bb suffix (I think bounding box)
were created and copied to tmp. In LyX140 this got broken and either
the *.bbs are not copied or not named properly. Anyway if you manually copy
the *.bb files to the tmp directory then you can run dvipdfm and
make a pdf file output. This is an inner LyX mechanism not under control
like the contents of a document or the functioning of the Latex backend
unless you are a developer and fix the LyX (C++?) code.
Are you sure you ran texhash or Miktex Options, update of database?
Stephen
