On Tue, Nov 21, 2023 at 08:25:57PM -0500, Alexander Dunlap wrote:
> I am so sorry, I tried it again and I can no longer reproduce either :-(
This is actually positive outcome :) The fix is now in debian and hopefully
in CTAN once I find some more time.
Pavel
--
lyx-devel mailing list
lyx-devel@l
I am so sorry, I tried it again and I can no longer reproduce either :-(
I will try to think of if there was anything I was doing differently earlier.
On Tue, Nov 21, 2023, at 5:08 PM, Pavel Sanda wrote:
> On Tue, Nov 21, 2023 at 10:26:06AM -0500, Alexander Dunlap wrote:
> > I tried the same PDF i
On Tue, Nov 21, 2023 at 10:26:06AM -0500, Alexander Dunlap wrote:
> I tried the same PDF in all three scenarios.
Ok, you challenged me to test this on both TL 2022 (debian based) and TL 2023
(installed locally for a standalone user).
Everything worked in both TL 2022 & 2023.
Could you give me ex
I tried the same PDF in all three scenarios.
On Tue, Nov 21, 2023, at 10:06 AM, Pavel Sanda wrote:
> On Tue, Nov 21, 2023 at 08:48:40AM -0500, Alexander Dunlap wrote:
> > None of these tests give me any error messages. However, when I test it with
> > the absolute path, the output I get is differe
On Tue, Nov 21, 2023 at 08:48:40AM -0500, Alexander Dunlap wrote:
> 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 page
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. How
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
Yes that is right, sorry for not reading carefully. :-)
On Mon, Nov 20, 2023, at 10:30 AM, Pavel Sanda wrote:
> On Mon, Nov 20, 2023 at 10:08:23AM -0500, Alexander Dunlap wrote:
> > By "the behavior you describe" I also meant what happens when I apply the
> > fix. :-)
>
> I didn't describe behav
On Mon, Nov 20, 2023 at 10:08:23AM -0500, Alexander Dunlap wrote:
> By "the behavior you describe" I also meant what happens when I apply the
> fix. :-)
I didn't describe behaviour of the step 2, but I'll interpret this exchange, as
"the patch works" :)
Pavel
--
lyx-devel mailing list
lyx-devel
By "the behavior you describe" I also meant what happens when I apply the fix.
:-)
On Mon, Nov 20, 2023, at 10:02 AM, Pavel Sanda wrote:
> On Mon, Nov 20, 2023 at 09:46:32AM -0500, Alexander Dunlap wrote:
> > I have texlive 2023 and I can reproduce the behavior you describe exactly.
>
> And the
On Mon, Nov 20, 2023 at 09:46:32AM -0500, Alexander Dunlap wrote:
> I have texlive 2023 and I can reproduce the behavior you describe exactly.
And the fix works? :)
As a root do something like:
cd /usr/share/texlive/texmf-dist/scripts/pfarrei/
cat /path/to/patch/pf.patch | patch -p0
And as a u
I have texlive 2023 and I can reproduce the behavior you describe exactly.
Alex
On Mon, Nov 20, 2023, at 9:39 AM, Pavel Sanda wrote:
> Hi,
>
> somewhat offtopic: could anyone running TL 2023 (or at least 2022) check for
> me the following two things:
>
> 1) a5toa4 does not work, try by running
Hi,
somewhat offtopic: could anyone running TL 2023 (or at least 2022) check for me
the following two things:
1) a5toa4 does not work, try by running:
$ a5toa4 $some_file_of_yours.pdf
it fails with something like:
/usr/share/texlive/texmf-dist/scripts/pfarrei/pfarrei.tlu:114:
pfarrei.xR
13 matches
Mail list logo
