[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1003255: marked as done (Using pst-all makes dvipdf emit a transparency-related warning even if transparency not used)



Your message dated Mon, 8 Aug 2022 08:05:42 +0900
with message-id <YvBFRicuOjhQn7cd@bulldog>
and subject line Re: Bug#1003255: No
has caused the Debian Bug report #1003255,
regarding Using pst-all makes dvipdf emit a transparency-related warning even if transparency not used
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1003255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003255
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-pstricks
Version: 2021.20211217-1

Let's construct mwe.tex containing

\documentclass{article}
\usepackage{pstricks}
\begin{document}
test
\end{document}

and run

latex mwe && dvipdf mwe

or

latex mwe && dvips mwe && ps2pdf mwe.ps

This prints

%%%% WARNING: Transparency operations ignored - need to use -dALLOWPSTRANSPARENCY

on a tty. Of course, one can do as the message says and add the corresponding command-line option. Still, I feel that the transparency stuff shouldn't even be in the Postscript file unless it is really used. So could pstricks be a bit more economical and not issue the transparency-related commands by default (or, equivalently, issue them only if opacity and the like is really used in the user's LaTeX input)? Alternatively or in addition, could ghostscript be a little less fussy about transparency and make ALLOWPSTRANSPARENCY default?

Bug report: https://tex.stackexchange.com/questions/629314 . The PStricks maintainers have been informed, too, just in case they don't have an update for this issue yet.

Thank you in advance,
Peter

--- End Message ---
--- Begin Message ---
On Sun, 07 Aug 2022, Peter Müller wrote:
> It's not the presence or absence of any such check that makes it into a bug.
> It's the resulting behavior that has a bug.

As mentioned in the policy of the TeX Debian Maintainers, we don't fix
or work on bugs that relate to up-upstream, that is not directly related
to TeX Live and its packaging.

It is up to you to get your preferred changes into TeX Live, from where
they will find their way into Debian.

Up-Upstream bugs are closed.

Have a nice day

Norbert

--
PREINING Norbert                              https://www.preining.info
Mercari Inc.     +     IFMGA Guide     +     TU Wien     +     TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

--- End Message ---

Reply to: