>>>>> "Alexander" == Alexander Wollmann <[EMAIL PROTECTED]> writes:
Alexander> On 22-Oct-99 Lars Gullik Bj�nnes wrote:
>> Bruce Momjian <[EMAIL PROTECTED]> writes:
>>
>> | So I go an include the pstex_t file using Insert/Include file,
>> and I | click on the Input radio button and put the filename in.
>>
>> Ok...can you have a look at the latex log file Edit->LaTeX Log
>>
>> And see if some missing/not found files are mentioned.
>>
>> Lgb
Alexander> I had the same problem here, the solution was to use an
Alexander> absolute filename:
Alexander> look in the .pstex_t file and find the line
Alexander> \special{psfile=foo.pstex} ; or something like this...
Alexander> then edit the filename, and give the full path to the file
Alexander> e.g.
Alexander> \special{psfile=/home/blabla/foo.pstex}
I think this is exactly the problem. Currently xfig gives you two
choices:
- generating code for a 10 years old latex using \special. This causes
problems to us. This works if you give absolute filenames or do not
use a temp directory.
- generating code for a 5 years old latex using \psfig (when -DEPSF is
defined in the relevant makefile before compiling xfig). This works
if you add \usepackage{epsfig} in the preamble.
I guess people do not see the same behaviour because all builds of
xfig do not produce the same result.
It would really be nice if xfig was upgraded to produce real latex
(whichout this ugly \SetFigFont too).
JMarc
