Patrick De Visschere writes:
>
> I normally use pathnames relative to the current directory and since . is
> automatically included in the TEXINPUTS prefix, this should still work I
> guess without making any modifications. But it doesn't.
> The problematic paths start with ../ and it looks there
On 27 Sep, 2011, at 11:11 PM, Richard Heck wrote:
> On 09/27/2011 04:47 PM, Patrick De Visschere wrote:
>> Hello,
>>
>> Including a .pdf file with \includegraphics and with a relative pathname like
>>
>> \includegraphics{../path/to/file/starting/from/parent/directory/some_file.pdf}
>>
>> resul
On Sep 27, 2011, at 5:11 PM, Richard Heck wrote:
On 09/27/2011 04:47 PM, Patrick De Visschere wrote:
Hello,
Including a .pdf file with \includegraphics and with a relative
pathname like
\includegraphics{../path/to/file/starting/from/parent/directory/
some_file.pdf}
results in a "file n
On Sep 27, 2011, at 4:47 PM, Patrick De Visschere wrote:
Hello,
Including a .pdf file with \includegraphics and with a relative
pathname like
\includegraphics{../path/to/file/starting/from/parent/directory/
some_file.pdf}
results in a "file not found" error from the pdftex.def package.
On 09/27/2011 04:47 PM, Patrick De Visschere wrote:
> Hello,
>
> Including a .pdf file with \includegraphics and with a relative pathname like
>
> \includegraphics{../path/to/file/starting/from/parent/directory/some_file.pdf}
>
> results in a "file not found" error from the pdftex.def package.
>
>
Hello,
Including a .pdf file with \includegraphics and with a relative pathname like
\includegraphics{../path/to/file/starting/from/parent/directory/some_file.pdf}
results in a "file not found" error from the pdftex.def package.
When exporting as .tex and processing with e.g. TeXShop there is n
