None of these tests give me any error messages. However, when I test it with
the absolute path, the output I get is different. I ran it on a two-page PDF
and with relative paths the resulting PDF is a single page with both pages side
by side, in a file called ORIGINALFILENAME-sidebyside.pdf. However, when I run
it with an absolute path, I get a PDF (in the same filename) with only the text
"width=!,height=!,pages=-,nup=2x1"
Alex
On Tue, Nov 21, 2023, at 6:00 AM, Pavel Sanda wrote:
> On Mon, Nov 20, 2023 at 10:34:48AM -0500, Alexander Dunlap wrote:
> > Yes that is right, sorry for not reading carefully. :-)
>
> Alas, the former fix breaks with path specifications.
>
> The path searching mechanism of pdflatex (when -output-directory is used)
> is willing to consider current directory for path like "../../a/b/file"
> but is unwilling to consider current directory when only "file" is provided.
> Weird.
>
> Alexander, would you mind testing for me 2nd version of the patch?
> You need to unwind the last patch ("-R" for patch or just delete the
> simple change manually) and then apply the current one.
>
> 3 scenarios to be tested:
> 1. a5toa4 local_file.pdf
> 2. a5toa4 some_relative_path/file.pdf
> 3. a5toa4 /absolute_path/file.odf
>
> Works here with TL 2020, but I worry what other changes on searching
> mechanisms of -output-directory awaits in the future TLs.
> Pavel
>
> --
> lyx-devel mailing list
> lyx-devel@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-devel
>
>
> *Attachments:*
> • pf2.patch
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
