bug#44578: AW: bug#44578: AW: bug#44578: Investigating current preview problem

2022-01-12 Thread Bruckmann, Tobias 
Dear all,

is there still something that Hugo or me could provide? I am not sure
whether there are open points that we could support. In that case, please
let us know.

Thanks and best wishes,
Tobias

-Ursprüngliche Nachricht-
Von: Tassilo Horn  
Gesendet: Samstag, 8. Januar 2022 11:47
An: reinhard.kotu...@web.de
Cc: Ikumi Keita ; d...@gnu.org; Bruckmann, Tobias
; hugo.rag...@insa-cvl.fr;
44...@debbugs.gnu.org; bug-auctex@gnu.org
Betreff: Re: bug#44578: AW: bug#44578: Investigating current preview problem

Reinhard Kotucha  writes:

Hi Reinhard,

>  > > I replaced "use_any_eps_file_here" with "tiger" and saved the 
> file  > > under the name "xyz.tex". And I created symbolic link of 
> tiger.eps in  > > the current directory (in my case, /tmp/): ln -s  > 
> > 
> /usr/local/texlive/2021/texmf-dist/doc/generic/pstricks/images/tiger.e
> ps
>  > > .
>  >
>  > Unfortunately, my TeXLive doesn't have a tiger. ;-)
>
> It has.  But the doc tree isn't searched by kpathsea.
> Hence the "ln -s /usr//tiger.eps ." above.

Ok, let me state it this way: my distro's texlive packages don't seem to
install the doc tree.

Bye,
Tassilo


smime.p7s
Description: S/MIME cryptographic signature
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex

bug#44578: AW: bug#44578: AW: bug#44578: Investigating current preview problem

2022-01-07 Thread Bruckmann, Tobias 
Dear Tassilo,

as far as I understood, the principle is that \psfragfig calls an external
process to perform an "encapsulated" LaTeX->PS->PDF run, applied on a
synthetical LaTeX document that contains the *.eps file. It replaces all
expressions found in the *.eps file (say, a letter "a"), by the
corresponding expression given by psfrag (say, a proper math symbol a):

\psfrag{a}[cc][cc][1.3]{$a$}

Now whether the figure environment contains this line, or the user provides
a separate file, exactly named as the corresponding *.eps file, that
contains all replacements for that *.eps figure.

So, to make psfragfig working, I always thought that -shell-escape is
absolutely needed!

I am not sure whether this was your question, but if I can help, please let
me know.

Best wishes,
Tobias

-Ursprüngliche Nachricht-
Von: Tassilo Horn  
Gesendet: Freitag, 7. Januar 2022 12:52
An: Ikumi Keita 
Cc: Bruckmann, Tobias ; 44...@debbugs.gnu.org;
d...@gnu.org; hugo.rag...@insa-cvl.fr
Betreff: Re: bug#44578: AW: bug#44578: Investigating current preview problem

Ikumi Keita  writes:

>> You are right.  With a test-example EPS which comes with TeXLive, it 
>> again compiles well for me:
>
>>
>> \psfragfig[mode=errorstop,width=0.9\textwidth]{/usr/share/texmf-dist/
>> tex/latex/mwe/example-image}
>
> It seems that the usage of "example-image" is the source of trouble. 
> In that case, I find in the log that "example-image.tex" is read in, 
> not "example-image.eps".

Ah, indeed, both exist.  But I specified example-image.eps at the first try
and then it complained that example-image.eps.eps did not exist.

So it seems that depending on if -shell-escape is used, \psfragfig either
expects/prefers an eps or a tex file?

Bye,
Tassilo


smime.p7s
Description: S/MIME cryptographic signature
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex

bug#44578: AW: bug#44578: Investigating current preview problem

2022-01-07 Thread Bruckmann, Tobias 
I can confirm that I observe the same behavior as Hugo and that the error is
still appearing with the newest version of preview.sty (as downloaded from
AUCTeX yesterday).

The minimum example I use is

\documentclass[12pt,a4paper]{article}
\usepackage[margin=2cm,a4paper]{geometry}
\usepackage{hyperref}
\title{psfrag in pdflatex }
\usepackage{graphicx}
\usepackage{pstool}
\usepackage{bookmark}
\begin{document}
Test
\begin{figure}[h!]
\centering
 \psfragfig[mode=errorstop,width=0.9\textwidth]{use_any_eps_file_here}
\caption{The EPS image with psfragfig}
\end{figure}
\end{document}

Note, I read frequently that TeXLive compiles very well. I use MikTex,
latest updates applied. Maybe Hugo also uses MikTex?
Is it possible that one of those distributions uses legacy packages?

Thanks a lot for your support!
Tobias

-Ursprüngliche Nachricht-
Von: Tassilo Horn  
Gesendet: Freitag, 7. Januar 2022 06:54
An: Hugo Raguet 
Cc: 44...@debbugs.gnu.org; d...@gnu.org; Bruckmann, Tobias
; bug-auctex@gnu.org
Betreff: Re: bug#44578: Investigating current preview problem

Hugo Raguet  writes:

>> I've attached it; could you and Tobias please give it a try.
>
> Unfortunately, it does not fix my problem ; for instance, the minimum 
> example on the above referenced thread fails with the exact same 
> problem as before if I do not apply Ulrike Fisher's workaround.

FWIW, I have the same "problem" as David.  The example document from TeX
StackExchange compiles just fine for me (after adding %%%
TeX-command-extra-options: "--shell-escape" to the local variables) using
TeXLive 2021.  The compile log suggests that the preview style is not
loaded.

So then I've put a \usepackage{preview} before loading pstricks and tried
both with the TeXLive preview version and the current AUCTeX version and
still both compiled fine and gave the same output.

Maybe you could give the exact latex command that fails for you on this
document?

Bye,
Tassilo


smime.p7s
Description: S/MIME cryptographic signature
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex

bug#45894: AW: Future of EPS (was Re: bug#45894: Bug report for preview-latex)

2021-09-03 Thread Bruckmann, Tobias 
Dear Ikumi,

thanks a lot, especially for the detailed description of possible
approaches.

As many figures are scientific plots, e.g. generated in MATLAB, containing
axes definitions and multiple textual informations, that would be hard to
realize...

Thanks anyways! I will try to test TikZ export functions available in MATLAB
and Inkscape.

Best wishes,
Tobias

-Ursprüngliche Nachricht-
Von: Ikumi Keita  
Gesendet: Freitag, 3. September 2021 10:20
An: Bruckmann, Tobias 
Cc: 45...@debbugs.gnu.org; 44...@debbugs.gnu.org
Betreff: Re: Future of EPS (was Re: bug#45894: Bug report for preview-latex)

>>>>> "Bruckmann, Tobias"  writes:
> Are you aware of any approach to do these LaTeX text replacements in 
> PDF graphics already today?

How about exporting figures _without_ texts and _adding_ annotation with
TikZ, as done in the attached example? In this way, no "text replacements"
are necessary.

Or is it too painful to adjust the position of the texts at LaTeX level, not
at the time of creation of figure?

Regards,
Ikumi Keita



smime.p7s
Description: S/MIME cryptographic signature
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex

bug#44578: AW: Future of EPS (was Re: bug#45894: Bug report for preview-latex)

2021-09-02 Thread Bruckmann, Tobias 
Dear Ikumi,

first, I would like to thank you for taking the time to reflect the
situation and to give me some insight.

I would be perfectly fine with a purely PDF-based toolchain, and as I use
Inkscape as a graphics editor, that would be no problem. My only requirement
is the ability to replace text in graphics by LaTeX expressions, which is
why I use pstool.

(Well, to be honest, as I am in the middle of preparing a larger document
and as dozens of graphics are already prepared for pstool replacements, I
would be in favor of finalizing this single project using the pstool
approach...)

Are you aware of any approach to do these LaTeX text replacements in PDF
graphics already today?

I will try the TikZ format in between.

Thanks,
Tobias

-Ursprüngliche Nachricht-
Von: Ikumi Keita  
Gesendet: Donnerstag, 2. September 2021 09:01
An: Bruckmann, Tobias 
Cc: 45...@debbugs.gnu.org; 44...@debbugs.gnu.org
Betreff: Future of EPS (was Re: bug#45894: Bug report for preview-latex)

Dear Tobias,

>>>>> "Bruckmann, Tobias"  writes:
> 6 months ago we had the conversation below, and as Mr. Kastrup decided 
> not to care for the issue without getting paid, I wanted to ask 
> whether this bug is still on the list of the auctex team.

This bug is registered in Bug Tracker of AUCTeX:
https://debbugs.gnu.org/cgi/pkgreport.cgi?which=pkg=auctex

So perhaps someone might pick it up and try to resolve it in future;
However, I think that hope is very weak. In my view, the (La)TeX ecosystem
is moving rapidly towards PDF centric realm with respect to the graphic
format and EPS is already considered (implicitly) as semi-obsolete. In a
decade, EPS would be totally obsolete as (La)TeX graphic format.

You wrote
> - Most scientific works use vector EPS graphics.
before. If your tool supports only EPS as the format for outputs, my
recommendation is to ask the developer to update it to support other format.
If I remember correctly, many scientific tools which consider
interoperability with LaTeX recently supports TikZ code as export format. Is
it difficult to do so for your tool?

> The combination of pstool and pdfLaTeX seems to be the most promising 
> approach to me to join these points in one toolchain.

For the reason described above, I don't think it's promising, at least for
usage with (La)TeX.

> So there's no pathway and this toolchain is dead forever?

The answer depends whether the developer of your tool adheres to EPS or not,
I think.

Regards,
Ikumi Keita


smime.p7s
Description: S/MIME cryptographic signature
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex

bug#45894: AW: AW: AW: bug#45894: Bug report for preview-latex

2021-09-01 Thread Bruckmann, Tobias 
Dear Ikumi,

6 months ago we had the conversation below, and as Mr. Kastrup decided not
to care for the issue without getting paid, I wanted to ask whether this bug
is still on the list of the auctex team.

I had some conversation here
https://tex.stackexchange.com/questions/587774/proper-toolchain-for-pdflatex
-and-psfrag-including-hyperref where also Ulrike Fischer commented. She also
created a separate burg report here
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=44578

It seems the only proper solution is a fix in the preview package.

Thanks for a short comment,
Tobias

-Ursprüngliche Nachricht-
Von: Bruckmann, Tobias 
Gesendet: Montag, 1. März 2021 10:14
An: 'David Kastrup' 
Cc: Ikumi Keita ; 45...@debbugs.gnu.org;
44...@debbugs.gnu.org
Betreff: AW: AW: AW: bug#45894: Bug report for preview-latex

> -Ursprüngliche Nachricht-
> Von: David Kastrup 
> Gesendet: Donnerstag, 25. Februar 2021 14:10
> An: Bruckmann, Tobias 
> Cc: Ikumi Keita ; 45...@debbugs.gnu.org;
> 44...@debbugs.gnu.org
> Betreff: Re: AW: AW: bug#45894: Bug report for preview-latex
> 
> "Bruckmann, Tobias"  writes:
> 
> > Dear David,
> >
> > this is a good question. I didn't want to push
> 
> Not?
> 
No. I just asked whether there is a chance that this gets a fix. You
mentioned that you are not seeing a chance to fix it due to conflicts
between Hyperref and LaTeX internals, and I wanted to know if this means the
toolchain I described is dead, despite its relevance for scientific authors.
If you confirm this, I will have to change my toolchain. Or look for other
people who stumble across the same issue and who are maybe able to fix it. 

> > but just point out the relevance of the issue, believing that you feel
> > a personal appreciation (and/or certain responsibility) for a code you
> > officially maintain.
> >
> > If I had the expertise to fix the code on my own, I would not have
> > spent the time to find and bother you, but better invest it to produce
> > the solution and propose it to you.
> >
> > If you ask for money - that could be a problem. I have no idea on the
> > time needed to find the problem, to fix and to test it. Hiring a
> > professional is probably beyond my budget as I am just an academics.
> > As such, I am volunteering as well in multiple matters, trying to
> > improve things - so I think when it comes to projects driven by
> > enthusiastism, I share your engagement, but I don't think that a
> > spirit of needing individual payments will lead to a better future for
> > open source projects.
> 
> I thought so.  I've invested decades of my time in Free Software, living
below
> minimum wage, with the obvious consequences for my personal future.  All
> that buys you is people thinking they are entitled to it and argue you
should do
> more for them.
> 
> There are times when this motivational framework does not work all that
well
> for me.

I understand. But look, Free Software in its core concept was always driven
by enthusiasts who enjoy spending their leisure time in creating software
together. I agree, this implies that no one can push you. Now you join
the project and try to enforce a business model. I know how it feels if a
business plan fails, but you cannot blame the Free Software model, driven by
people doing things for themselves and others because of ... fun.

Note, I did not ask a company to implement an extra software feature for me,
but I asked the voluntary maintainers to give a comment on chances for a bug
fix. 

Don't get me wrong, but on my side it feels like you turned the Free
Software maintainer position into a sales platform for your service.
Establishing a functionality in Free Software, letting people rely on it and
then(!) ask for money for bugfixes does not feel fair for me: If you intend
to make money
with software (which is absolutely reasonable), then create a product, put a
price tag on it and advertise. Then customers might buy it for a price they
know in advance, and the sum of their payments will pay your bills. This is
what commercial programmers do.

If you decide to create and advertise commercial LaTeX packages,
I totally might be amongst your customers if they simplify my work. 

LaTeX
would probably take advantage from such entrepreneur initiatives, just like
Linux. But - please - don’t change the rules during the game...

Tobias

> 
> --
> David Kastrup


smime.p7s
Description: S/MIME cryptographic signature
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex

bug#45894: AW: AW: AW: bug#45894: Bug report for preview-latex

2021-03-01 Thread Bruckmann, Tobias 
> -Ursprüngliche Nachricht-
> Von: David Kastrup 
> Gesendet: Donnerstag, 25. Februar 2021 14:10
> An: Bruckmann, Tobias 
> Cc: Ikumi Keita ; 45...@debbugs.gnu.org;
> 44...@debbugs.gnu.org
> Betreff: Re: AW: AW: bug#45894: Bug report for preview-latex
> 
> "Bruckmann, Tobias"  writes:
> 
> > Dear David,
> >
> > this is a good question. I didn't want to push
> 
> Not?
> 
No. I just asked whether there is a chance that this gets a fix. You
mentioned that you are not seeing a chance to fix it due to conflicts
between Hyperref and LaTeX internals, and I wanted to know if this means the
toolchain I described is dead, despite its relevance for scientific authors.
If you confirm this, I will have to change my toolchain. Or look for other
people who stumble across the same issue and who are maybe able to fix it. 

> > but just point out the relevance of the issue, believing that you feel
> > a personal appreciation (and/or certain responsibility) for a code you
> > officially maintain.
> >
> > If I had the expertise to fix the code on my own, I would not have
> > spent the time to find and bother you, but better invest it to produce
> > the solution and propose it to you.
> >
> > If you ask for money - that could be a problem. I have no idea on the
> > time needed to find the problem, to fix and to test it. Hiring a
> > professional is probably beyond my budget as I am just an academics.
> > As such, I am volunteering as well in multiple matters, trying to
> > improve things - so I think when it comes to projects driven by
> > enthusiastism, I share your engagement, but I don't think that a
> > spirit of needing individual payments will lead to a better future for
> > open source projects.
> 
> I thought so.  I've invested decades of my time in Free Software, living
below
> minimum wage, with the obvious consequences for my personal future.  All
> that buys you is people thinking they are entitled to it and argue you
should do
> more for them.
> 
> There are times when this motivational framework does not work all that
well
> for me.

I understand. But look, Free Software in its core concept was always driven
by enthusiasts who enjoy spending their leisure time in creating software
together. I agree, this implies that no one can push you. Now you join
the project and try to enforce a business model. I know how it feels if a
business plan fails, but you cannot blame the Free Software model, driven by
people doing things for themselves and others because of ... fun.

Note, I did not ask a company to implement an extra software feature for me,
but I asked the voluntary maintainers to give a comment on chances for a bug
fix. 

Don't get me wrong, but on my side it feels like you turned the Free
Software maintainer position into a sales platform for your service.
Establishing a functionality in Free Software, letting people rely on it and
then(!) ask for money for bugfixes does not feel fair for me: If you intend
to make money
with software (which is absolutely reasonable), then create a product, put a
price tag on it and advertise. Then customers might buy it for a price they
know in advance, and the sum of their payments will pay your bills. This is
what commercial programmers do.

If you decide to create and advertise commercial LaTeX packages,
I totally might be amongst your customers if they simplify my work. 

LaTeX
would probably take advantage from such entrepreneur initiatives, just like
Linux. But - please - don’t change the rules during the game...

Tobias

> 
> --
> David Kastrup


smime.p7s
Description: S/MIME cryptographic signature
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex

bug#44578: AW: AW: bug#45894: Bug report for preview-latex

2021-02-24 Thread Bruckmann, Tobias 
Dear David,

this is a good question. I didn't want to push but just point out the relevance 
of the issue, believing that you feel a personal appreciation (and/or certain 
responsibility) for a code you officially maintain.

If I had the expertise to fix the code on my own, I would not have spent the 
time to find and bother you, but better invest it to produce the solution and 
propose it to you.

If you ask for money - that could be a problem. I have no idea on the time 
needed to find the problem, to fix and to test it. Hiring a professional is 
probably beyond my budget as I am just an academics. As such, I am volunteering 
as well in multiple matters, trying to improve things - so I think when it 
comes to projects driven by enthusiastism, I share your engagement, but I don't 
think that a spirit of needing individual payments will lead to a better future 
for open source projects. If this was the way to go, I'd better buy a 
commercial text processor I can afford and stick with it.

But I am in the weaker position and already spent lots of time in a LaTeX-based 
thesis, so please let me know a price, and I have to see...

Thanks and best wishes,
Tobias


Von: David Kastrup 
Gesendet: Donnerstag, 25. Februar 2021 00:58
An: Bruckmann, Tobias
Cc: Ikumi Keita; 45...@debbugs.gnu.org; 44...@debbugs.gnu.org
Betreff: Re: AW: AW: bug#45894: Bug report for preview-latex 

"Bruckmann, Tobias"  writes: 

> Hi Ikumi, David 
> 
> this is a bad situation. I am quite surprised I am the first (and only?) one 
> to stumble across this: 
> - Most scientific works use vector EPS graphics. psfrag is extremely popular 
> in this field. 
> - Most works are published in PDF 
> - You can't get around hyperref 
> 
> The combination of pstool and pdfLaTeX seems to be the most promising 
> approach to me to join these points in one toolchain. Living with an old 
> version might work for some months, but this can't be the future. 
> 
> So there's no pathway and this toolchain is dead forever? 
> 
> Thanks for your appreciated comment, 

So what are you willing to invest to avert the catastrophe?  In terms of 
procuring code or paying for the time of those who do? 

-- 
David Kastrup 


smime.p7s
Description: S/MIME Cryptographic Signature
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex

bug#45894: AW: AW: bug#45894: Bug report for preview-latex

2021-02-15 Thread Bruckmann, Tobias 
Hi Ikumi, David

this is a bad situation. I am quite surprised I am the first (and only?) one
to stumble across this:
- Most scientific works use vector EPS graphics. psfrag is extremely popular
in this field.
- Most works are published in PDF
- You can't get around hyperref

The combination of pstool and pdfLaTeX seems to be the most promising
approach to me to join these points in one toolchain. Living with an old
version might work for some months, but this can't be the future.

So there's no pathway and this toolchain is dead forever?

Thanks for your appreciated comment,
Tobias

-Ursprüngliche Nachricht-
Von: Ikumi Keita  
Gesendet: Sonntag, 14. Februar 2021 20:32
An: Bruckmann, Tobias 
Cc: d...@gnu.org; 45...@debbugs.gnu.org; 44...@debbugs.gnu.org
Betreff: Re: AW: bug#45894: Bug report for preview-latex

Hi Tobias,

>>>>> "Bruckmann, Tobias"  writes:
> I am not sure whether the status of my bug report:
> Is there any chance this will be resolved, or is it only of minor
relevance?

I'm sorry to say this, but I can't help. It requires mature knowledge about
TeX programming and Postscript language to deal with this issue. I have
neither one.

As I told before, I'd just recomend to keep an old TeX distribution
separately to typeset your documents. That's only workaround I can think of.

Best regards,
Ikumi Keita


smime.p7s
Description: S/MIME cryptographic signature
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex

bug#44578: AW: bug#45894: Bug report for preview-latex

2021-02-14 Thread Bruckmann, Tobias 
Dear all,

I am not sure whether the status of my bug report:
Is there any chance this will be resolved, or is it only of minor relevance?

I would be grateful for any quick comment...

Thanks and best wishes,
Tobias

-Ursprüngliche Nachricht-
Von: Bruckmann, Tobias 
Gesendet: Sonntag, 17. Januar 2021 13:47
An: 'Ikumi Keita' ; d...@gnu.org
Cc: 45...@debbugs.gnu.org; 44...@debbugs.gnu.org
Betreff: AW: bug#45894: Bug report for preview-latex

Thanks! 
Please let me know in case I can support the clarification of the bug.

-Ursprüngliche Nachricht-
Von: Ikumi Keita  
Gesendet: Sonntag, 17. Januar 2021 06:58
An: d...@gnu.org
Cc: Bruckmann, Tobias ; 45...@debbugs.gnu.org;
44...@debbugs.gnu.org
Betreff: Re: bug#45894: Bug report for preview-latex

Hi David,

Could you please take care of bug#44578[1], reported by Ulrike Fischer?
It seems that that bug is responsible for bug#45894, skimming over the
correspondence between Tobias and Ulrike[2].

In addition, the following simple document fails at preview-latex when
TeX-PDF-mode is nil and preview-image-type is `png', although I'm not sure
whether this is related or not. (The two math fragments "\(a\)" and "\(b\)"
both don't render as images but instead "Do not enter" signs appear beside
them.)

In summary, it seems that latex+dvips+gs has low compatibility with
preview.sty by recent changes in LaTeX core.

Best regards,
Ikumi Keita

--
\documentclass{article}
\usepackage{tikz}

\begin{document}

\begin{itemize}
\item \(a\)
\item \(b\)
\end{itemize}

% pdflatex+pdf2dsc+gs OK
% latex+dvipngOK
% latex+dvips+gs  NG

\end{document}

%%% Local Variables:
%%% mode: latex
%%% TeX-master: t
%%% End:
--

[1] https://debbugs.gnu.org/44578
[2]
https://tex.stackexchange.com/questions/570404/pdflatex-fails-on-pstool-when
-hyperref-is-included

>>>>> "Bruckmann, Tobias"  writes:
> Dear Sir or Madam,
> I reported a bug on github, and the maintainers advised me to inform 
> the authors of preview-latex:

>  <https://github.com/latex3/hyperref/issues/166> pdfLaTeX fails on 
> pstool when hyperref is included · Issue #166 · latex3/hyperref 
> (github.com). The original bug report, a minimum example and all 
> needed files are posted there.

> I would be absolutely willing to support the clarification of the issue.
> Please inform me how to formally submit the bug report.

> Thanks and best wishes,

> Tobias Bruckmann


smime.p7s
Description: S/MIME cryptographic signature
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex

bug#44578: AW: AW: bug#45894: Bug report for preview-latex

2021-01-23 Thread Bruckmann, Tobias 
Dear all,

is there anything I can do from user side? I am no programmer, but let me
know in case I can help.

Will there be some bug tracking to follow any debugging process?

Thanks and best wishes,
Tobias

-Ursprüngliche Nachricht-
Von: David Kastrup  
Gesendet: Sonntag, 17. Januar 2021 13:59
An: Bruckmann, Tobias 
Cc: Ikumi Keita ; 45...@debbugs.gnu.org;
44...@debbugs.gnu.org
Betreff: Re: AW: bug#45894: Bug report for preview-latex


Frankly, I have a problem seeing a sensible fix for "Hyperref chose to mess
with LaTeX internals in its own exclusive way incompatible with anybody else
trying to change behavior, even when done in the exactly same manner, but
will likely change doing this to a different way soon".


"Bruckmann, Tobias"  writes:

> Thanks! 
> Please let me know in case I can support the clarification of the bug.
>
> -Ursprüngliche Nachricht-
> Von: Ikumi Keita 
> Gesendet: Sonntag, 17. Januar 2021 06:58
> An: d...@gnu.org
> Cc: Bruckmann, Tobias ; 
> 45...@debbugs.gnu.org; 44...@debbugs.gnu.org
> Betreff: Re: bug#45894: Bug report for preview-latex
>
> Hi David,
>
> Could you please take care of bug#44578[1], reported by Ulrike Fischer?
> It seems that that bug is responsible for bug#45894, skimming over the 
> correspondence between Tobias and Ulrike[2].
>
> In addition, the following simple document fails at preview-latex when 
> TeX-PDF-mode is nil and preview-image-type is `png', although I'm not 
> sure whether this is related or not. (The two math fragments "\(a\)" and
"\(b\)"
> both don't render as images but instead "Do not enter" signs appear 
> beside
> them.)
>
> In summary, it seems that latex+dvips+gs has low compatibility with 
> preview.sty by recent changes in LaTeX core.
>
> Best regards,
> Ikumi Keita
>
> --
> \documentclass{article}
> \usepackage{tikz}
>
> \begin{document}
>
> \begin{itemize}
> \item \(a\)
> \item \(b\)
> \end{itemize}
>
> % pdflatex+pdf2dsc+gs OK
> % latex+dvipngOK
> % latex+dvips+gs  NG
>
> \end{document}
>
> %%% Local Variables:
> %%% mode: latex
> %%% TeX-master: t
> %%% End:
> ------
>
> [1] https://debbugs.gnu.org/44578
> [2]
> https://tex.stackexchange.com/questions/570404/pdflatex-fails-on-pstoo
> l-when
> -hyperref-is-included
>
>>>>>> "Bruckmann, Tobias"  writes:
>> Dear Sir or Madam,
>> I reported a bug on github, and the maintainers advised me to inform 
>> the authors of preview-latex:
>
>>  <https://github.com/latex3/hyperref/issues/166> pdfLaTeX fails on 
>> pstool when hyperref is included · Issue #166 · latex3/hyperref 
>> (github.com). The original bug report, a minimum example and all 
>> needed files are posted there.
>
>> I would be absolutely willing to support the clarification of the issue.
>> Please inform me how to formally submit the bug report.
>
>> Thanks and best wishes,
>
>> Tobias Bruckmann
>

--
David Kastrup


smime.p7s
Description: S/MIME cryptographic signature
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex

bug#45894: AW: bug#45894: Bug report for preview-latex

2021-01-17 Thread Bruckmann, Tobias 
Thanks! 
Please let me know in case I can support the clarification of the bug.

-Ursprüngliche Nachricht-
Von: Ikumi Keita  
Gesendet: Sonntag, 17. Januar 2021 06:58
An: d...@gnu.org
Cc: Bruckmann, Tobias ; 45...@debbugs.gnu.org;
44...@debbugs.gnu.org
Betreff: Re: bug#45894: Bug report for preview-latex

Hi David,

Could you please take care of bug#44578[1], reported by Ulrike Fischer?
It seems that that bug is responsible for bug#45894, skimming over the
correspondence between Tobias and Ulrike[2].

In addition, the following simple document fails at preview-latex when
TeX-PDF-mode is nil and preview-image-type is `png', although I'm not sure
whether this is related or not. (The two math fragments "\(a\)" and "\(b\)"
both don't render as images but instead "Do not enter" signs appear beside
them.)

In summary, it seems that latex+dvips+gs has low compatibility with
preview.sty by recent changes in LaTeX core.

Best regards,
Ikumi Keita

--
\documentclass{article}
\usepackage{tikz}

\begin{document}

\begin{itemize}
\item \(a\)
\item \(b\)
\end{itemize}

% pdflatex+pdf2dsc+gs OK
% latex+dvipngOK
% latex+dvips+gs  NG

\end{document}

%%% Local Variables:
%%% mode: latex
%%% TeX-master: t
%%% End:
--

[1] https://debbugs.gnu.org/44578
[2]
https://tex.stackexchange.com/questions/570404/pdflatex-fails-on-pstool-when
-hyperref-is-included

>>>>> "Bruckmann, Tobias"  writes:
> Dear Sir or Madam,
> I reported a bug on github, and the maintainers advised me to inform 
> the authors of preview-latex:

>  <https://github.com/latex3/hyperref/issues/166> pdfLaTeX fails on 
> pstool when hyperref is included · Issue #166 · latex3/hyperref 
> (github.com). The original bug report, a minimum example and all 
> needed files are posted there.

> I would be absolutely willing to support the clarification of the issue.
> Please inform me how to formally submit the bug report.

> Thanks and best wishes,

> Tobias Bruckmann


smime.p7s
Description: S/MIME cryptographic signature
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex

bug#45894: Bug report for preview-latex

2021-01-15 Thread Bruckmann, Tobias 
Dear Sir or Madam,

 

I reported a bug on github, and the maintainers advised me to inform the
authors of preview-latex:

  pdfLaTeX fails on pstool
when hyperref is included · Issue #166 · latex3/hyperref (github.com). The
original bug report, a minimum example and all needed files are posted
there.

 

I would be absolutely willing to support the clarification of the issue.
Please inform me how to formally submit the bug report.

 

Thanks and best wishes,

Tobias Bruckmann

 

 



 

Dr.-Ing. Tobias Bruckmann
Universität Duisburg-Essen, Campus Duisburg
Fakultät für Ingenieurwissenschaften
Abteilung Maschinenbau und Verfahrenstechnik
Lehrstuhl für Mechatronik
Lotharstraße 1, MD 334
47057 Duisburg

 

Mobil: +49 (0) 170 / 639 2859

Tel.: +49 (0) 203 / 379 - 1908
Fax: +49 (0) 203 / 379 – 4494
E-Mail:  
mailto:tobias.bruckm...@uni-due.de
Internet:  
http://www.uni-due.de/mechatronik

 

 



smime.p7s
Description: S/MIME cryptographic signature
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex