Clash between pgf and transparent packagesEnumerate and itemize undefined + captions not workingClash among packages?Unexpected clash between babel and pgf spyInterference between onslide and setbeamercoveredtransparentLatex already defined clash between cls file and multiple packagesPermanent “Undefined Control Sequence?”conflict between mathabx and other packagesTransparent text: what alternatives to the transparent package?torn paper problem compileIncompatibility between PGF and PStricks
Passing multiple files through stdin (over ssh)
Were Alexander the Great and Hephaestion lovers?
Where Mongol herds graze
How can this tool find out registered domains from an IP?
Should an arbiter claim draw at a K+R vs K+R endgame?
Grover algorithm for a database search: where is the quantum advantage?
Winning Strategy for the Magician and his Apprentice
How to hide an urban landmark?
System.StringException: Unexpected end of expression
Is it possible to have a wealthy country without middle class?
What ways have you found to get edits from non-LaTeX users?
What to do when surprise and a high initiative roll conflict with the narrative?
Logarithm of exponential
Prime Sieve and brute force
Share calendar details request from manager's manager
How come the nude protesters were not arrested?
Is it possible to 'live off the sea'
Is it a problem if <h4>, <h5> and <h6> are smaller than regular text?
What is the highest possible permanent AC at character creation?
Déjà vu, again?
Why didn't Voldemort recognize that Dumbledore was affected by his curse?
Someone whose aspirations exceed abilities or means
Did Milano or Benatar approve or comment on their namesake MCU ships?
Determining fair price for profitable mobile app business
Clash between pgf and transparent packages
Enumerate and itemize undefined + captions not workingClash among packages?Unexpected clash between babel and pgf spyInterference between onslide and setbeamercoveredtransparentLatex already defined clash between cls file and multiple packagesPermanent “Undefined Control Sequence?”conflict between mathabx and other packagesTransparent text: what alternatives to the transparent package?torn paper problem compileIncompatibility between PGF and PStricks
I get an error with the following MWE when using pdflatex
.
documentclassarticle
usepackagepgfkeys, pgfcalendar
usepackagetransparent
begindocument
hello world
enddocument
! Undefined control sequence.
pgfutil@addpdfresource@extgs ...urce@extgs@plain
#1
I can trace it back to input pgfutil-common.tex
so it is not really pgfcalendar
and seems like a general clash with pgf. Is this a bug? If so is it known and is there a work around. If not, which side is it on so I can report it.
tikz-pgf errors incompatibility transparency
add a comment |
I get an error with the following MWE when using pdflatex
.
documentclassarticle
usepackagepgfkeys, pgfcalendar
usepackagetransparent
begindocument
hello world
enddocument
! Undefined control sequence.
pgfutil@addpdfresource@extgs ...urce@extgs@plain
#1
I can trace it back to input pgfutil-common.tex
so it is not really pgfcalendar
and seems like a general clash with pgf. Is this a bug? If so is it known and is there a work around. If not, which side is it on so I can report it.
tikz-pgf errors incompatibility transparency
add a comment |
I get an error with the following MWE when using pdflatex
.
documentclassarticle
usepackagepgfkeys, pgfcalendar
usepackagetransparent
begindocument
hello world
enddocument
! Undefined control sequence.
pgfutil@addpdfresource@extgs ...urce@extgs@plain
#1
I can trace it back to input pgfutil-common.tex
so it is not really pgfcalendar
and seems like a general clash with pgf. Is this a bug? If so is it known and is there a work around. If not, which side is it on so I can report it.
tikz-pgf errors incompatibility transparency
I get an error with the following MWE when using pdflatex
.
documentclassarticle
usepackagepgfkeys, pgfcalendar
usepackagetransparent
begindocument
hello world
enddocument
! Undefined control sequence.
pgfutil@addpdfresource@extgs ...urce@extgs@plain
#1
I can trace it back to input pgfutil-common.tex
so it is not really pgfcalendar
and seems like a general clash with pgf. Is this a bug? If so is it known and is there a work around. If not, which side is it on so I can report it.
tikz-pgf errors incompatibility transparency
tikz-pgf errors incompatibility transparency
edited May 30 at 2:06
Phelype Oleinik
29k64894
29k64894
asked May 30 at 0:36
StrongBadStrongBad
13.4k650107
13.4k650107
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I dare say the fault on in PGF's side, sorry if I'm wrong.
The pgfutil@addpdfresource@extgs
which shows in the error message seems to be a generic macro which, with the current settings, expands to pgf@sys@addpdfresource@extgs@plain
. The latter, however, is undefined. Searching the files for that macro, I found it in driver-specific definition code like pgfsys-pdftex.def
and the like, which seems like it's not being loaded.
I was going to say that loading pgfsys-pdftex.def
(or pgfsys-luatex.def
or pgfsys-dvipdfmx.def
) manually solves the problem, however loading the driver code when one is using only pgfrcs
(loaded by pgfcalendar
, which causes the error) doesn't make much sense, so perhaps the way to go is to un-define pgfutil@addpdfresource@extgs
, so that transparent
's code won't try to use it:
documentclassarticle
usepackagepgfkeys, pgfcalendar
makeatletter
AtBeginDocument%
@ifundefinedpgf@sys@addpdfresource@extgs@plain%
letpgfutil@addpdfresource@extgsSomethingProbablyUndefined
makeatother
usepackagetransparent
begindocument
hello transparent0.3world
enddocument
Another way around, instead of loading the driver code manually, would be to load pgfsys
(and graphicx
, without which pgfsys
apparently doesn't work):
usepackagegraphicx
usepackagepgfkeys, pgfsys, pgfcalendar
2
No it is not the fault of pgf but of the compability code in transparent: it tries to detect pgf to coordinate the pdf resources but the test is not quite correct if only a subpart of pgf is loaded. As we are currently working on the management of pdfresources this will stay until a real solution is there. See also github.com/ho-tex/oberdiek/issues/62
– Ulrike Fischer
May 30 at 9:50
@UlrikeFischer so that would be it is known and I should just load more of pgf until things get fixed?
– StrongBad
May 30 at 10:45
I think it's strange for pgf to define the genericpgfutil@addpdfresource@extgs
in terms of a driver-specific macro which is undefined, but this is just my opinion. However the issue appeared after an update intransparent.sty
, so...
– Phelype Oleinik
May 30 at 10:51
@PhelypeOleinik yes it is a bit strange, but it is an internal pgf command and it is not pgf's fault if transparent uses such an internal command wrongly.
– Ulrike Fischer
May 30 at 11:27
2
As I wrote we are currently working in the pdfresources management and try to setup things so that tricks as transparent has to use now to coordinate the resources with pgf is no longer needed. This will mean changes in both packages so I don't see much sense to do some intermediate repairs now.
– Ulrike Fischer
May 30 at 12:02
|
show 1 more comment
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "85"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f493285%2fclash-between-pgf-and-transparent-packages%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I dare say the fault on in PGF's side, sorry if I'm wrong.
The pgfutil@addpdfresource@extgs
which shows in the error message seems to be a generic macro which, with the current settings, expands to pgf@sys@addpdfresource@extgs@plain
. The latter, however, is undefined. Searching the files for that macro, I found it in driver-specific definition code like pgfsys-pdftex.def
and the like, which seems like it's not being loaded.
I was going to say that loading pgfsys-pdftex.def
(or pgfsys-luatex.def
or pgfsys-dvipdfmx.def
) manually solves the problem, however loading the driver code when one is using only pgfrcs
(loaded by pgfcalendar
, which causes the error) doesn't make much sense, so perhaps the way to go is to un-define pgfutil@addpdfresource@extgs
, so that transparent
's code won't try to use it:
documentclassarticle
usepackagepgfkeys, pgfcalendar
makeatletter
AtBeginDocument%
@ifundefinedpgf@sys@addpdfresource@extgs@plain%
letpgfutil@addpdfresource@extgsSomethingProbablyUndefined
makeatother
usepackagetransparent
begindocument
hello transparent0.3world
enddocument
Another way around, instead of loading the driver code manually, would be to load pgfsys
(and graphicx
, without which pgfsys
apparently doesn't work):
usepackagegraphicx
usepackagepgfkeys, pgfsys, pgfcalendar
2
No it is not the fault of pgf but of the compability code in transparent: it tries to detect pgf to coordinate the pdf resources but the test is not quite correct if only a subpart of pgf is loaded. As we are currently working on the management of pdfresources this will stay until a real solution is there. See also github.com/ho-tex/oberdiek/issues/62
– Ulrike Fischer
May 30 at 9:50
@UlrikeFischer so that would be it is known and I should just load more of pgf until things get fixed?
– StrongBad
May 30 at 10:45
I think it's strange for pgf to define the genericpgfutil@addpdfresource@extgs
in terms of a driver-specific macro which is undefined, but this is just my opinion. However the issue appeared after an update intransparent.sty
, so...
– Phelype Oleinik
May 30 at 10:51
@PhelypeOleinik yes it is a bit strange, but it is an internal pgf command and it is not pgf's fault if transparent uses such an internal command wrongly.
– Ulrike Fischer
May 30 at 11:27
2
As I wrote we are currently working in the pdfresources management and try to setup things so that tricks as transparent has to use now to coordinate the resources with pgf is no longer needed. This will mean changes in both packages so I don't see much sense to do some intermediate repairs now.
– Ulrike Fischer
May 30 at 12:02
|
show 1 more comment
I dare say the fault on in PGF's side, sorry if I'm wrong.
The pgfutil@addpdfresource@extgs
which shows in the error message seems to be a generic macro which, with the current settings, expands to pgf@sys@addpdfresource@extgs@plain
. The latter, however, is undefined. Searching the files for that macro, I found it in driver-specific definition code like pgfsys-pdftex.def
and the like, which seems like it's not being loaded.
I was going to say that loading pgfsys-pdftex.def
(or pgfsys-luatex.def
or pgfsys-dvipdfmx.def
) manually solves the problem, however loading the driver code when one is using only pgfrcs
(loaded by pgfcalendar
, which causes the error) doesn't make much sense, so perhaps the way to go is to un-define pgfutil@addpdfresource@extgs
, so that transparent
's code won't try to use it:
documentclassarticle
usepackagepgfkeys, pgfcalendar
makeatletter
AtBeginDocument%
@ifundefinedpgf@sys@addpdfresource@extgs@plain%
letpgfutil@addpdfresource@extgsSomethingProbablyUndefined
makeatother
usepackagetransparent
begindocument
hello transparent0.3world
enddocument
Another way around, instead of loading the driver code manually, would be to load pgfsys
(and graphicx
, without which pgfsys
apparently doesn't work):
usepackagegraphicx
usepackagepgfkeys, pgfsys, pgfcalendar
2
No it is not the fault of pgf but of the compability code in transparent: it tries to detect pgf to coordinate the pdf resources but the test is not quite correct if only a subpart of pgf is loaded. As we are currently working on the management of pdfresources this will stay until a real solution is there. See also github.com/ho-tex/oberdiek/issues/62
– Ulrike Fischer
May 30 at 9:50
@UlrikeFischer so that would be it is known and I should just load more of pgf until things get fixed?
– StrongBad
May 30 at 10:45
I think it's strange for pgf to define the genericpgfutil@addpdfresource@extgs
in terms of a driver-specific macro which is undefined, but this is just my opinion. However the issue appeared after an update intransparent.sty
, so...
– Phelype Oleinik
May 30 at 10:51
@PhelypeOleinik yes it is a bit strange, but it is an internal pgf command and it is not pgf's fault if transparent uses such an internal command wrongly.
– Ulrike Fischer
May 30 at 11:27
2
As I wrote we are currently working in the pdfresources management and try to setup things so that tricks as transparent has to use now to coordinate the resources with pgf is no longer needed. This will mean changes in both packages so I don't see much sense to do some intermediate repairs now.
– Ulrike Fischer
May 30 at 12:02
|
show 1 more comment
I dare say the fault on in PGF's side, sorry if I'm wrong.
The pgfutil@addpdfresource@extgs
which shows in the error message seems to be a generic macro which, with the current settings, expands to pgf@sys@addpdfresource@extgs@plain
. The latter, however, is undefined. Searching the files for that macro, I found it in driver-specific definition code like pgfsys-pdftex.def
and the like, which seems like it's not being loaded.
I was going to say that loading pgfsys-pdftex.def
(or pgfsys-luatex.def
or pgfsys-dvipdfmx.def
) manually solves the problem, however loading the driver code when one is using only pgfrcs
(loaded by pgfcalendar
, which causes the error) doesn't make much sense, so perhaps the way to go is to un-define pgfutil@addpdfresource@extgs
, so that transparent
's code won't try to use it:
documentclassarticle
usepackagepgfkeys, pgfcalendar
makeatletter
AtBeginDocument%
@ifundefinedpgf@sys@addpdfresource@extgs@plain%
letpgfutil@addpdfresource@extgsSomethingProbablyUndefined
makeatother
usepackagetransparent
begindocument
hello transparent0.3world
enddocument
Another way around, instead of loading the driver code manually, would be to load pgfsys
(and graphicx
, without which pgfsys
apparently doesn't work):
usepackagegraphicx
usepackagepgfkeys, pgfsys, pgfcalendar
I dare say the fault on in PGF's side, sorry if I'm wrong.
The pgfutil@addpdfresource@extgs
which shows in the error message seems to be a generic macro which, with the current settings, expands to pgf@sys@addpdfresource@extgs@plain
. The latter, however, is undefined. Searching the files for that macro, I found it in driver-specific definition code like pgfsys-pdftex.def
and the like, which seems like it's not being loaded.
I was going to say that loading pgfsys-pdftex.def
(or pgfsys-luatex.def
or pgfsys-dvipdfmx.def
) manually solves the problem, however loading the driver code when one is using only pgfrcs
(loaded by pgfcalendar
, which causes the error) doesn't make much sense, so perhaps the way to go is to un-define pgfutil@addpdfresource@extgs
, so that transparent
's code won't try to use it:
documentclassarticle
usepackagepgfkeys, pgfcalendar
makeatletter
AtBeginDocument%
@ifundefinedpgf@sys@addpdfresource@extgs@plain%
letpgfutil@addpdfresource@extgsSomethingProbablyUndefined
makeatother
usepackagetransparent
begindocument
hello transparent0.3world
enddocument
Another way around, instead of loading the driver code manually, would be to load pgfsys
(and graphicx
, without which pgfsys
apparently doesn't work):
usepackagegraphicx
usepackagepgfkeys, pgfsys, pgfcalendar
edited May 30 at 2:35
answered May 30 at 1:36
Phelype OleinikPhelype Oleinik
29k64894
29k64894
2
No it is not the fault of pgf but of the compability code in transparent: it tries to detect pgf to coordinate the pdf resources but the test is not quite correct if only a subpart of pgf is loaded. As we are currently working on the management of pdfresources this will stay until a real solution is there. See also github.com/ho-tex/oberdiek/issues/62
– Ulrike Fischer
May 30 at 9:50
@UlrikeFischer so that would be it is known and I should just load more of pgf until things get fixed?
– StrongBad
May 30 at 10:45
I think it's strange for pgf to define the genericpgfutil@addpdfresource@extgs
in terms of a driver-specific macro which is undefined, but this is just my opinion. However the issue appeared after an update intransparent.sty
, so...
– Phelype Oleinik
May 30 at 10:51
@PhelypeOleinik yes it is a bit strange, but it is an internal pgf command and it is not pgf's fault if transparent uses such an internal command wrongly.
– Ulrike Fischer
May 30 at 11:27
2
As I wrote we are currently working in the pdfresources management and try to setup things so that tricks as transparent has to use now to coordinate the resources with pgf is no longer needed. This will mean changes in both packages so I don't see much sense to do some intermediate repairs now.
– Ulrike Fischer
May 30 at 12:02
|
show 1 more comment
2
No it is not the fault of pgf but of the compability code in transparent: it tries to detect pgf to coordinate the pdf resources but the test is not quite correct if only a subpart of pgf is loaded. As we are currently working on the management of pdfresources this will stay until a real solution is there. See also github.com/ho-tex/oberdiek/issues/62
– Ulrike Fischer
May 30 at 9:50
@UlrikeFischer so that would be it is known and I should just load more of pgf until things get fixed?
– StrongBad
May 30 at 10:45
I think it's strange for pgf to define the genericpgfutil@addpdfresource@extgs
in terms of a driver-specific macro which is undefined, but this is just my opinion. However the issue appeared after an update intransparent.sty
, so...
– Phelype Oleinik
May 30 at 10:51
@PhelypeOleinik yes it is a bit strange, but it is an internal pgf command and it is not pgf's fault if transparent uses such an internal command wrongly.
– Ulrike Fischer
May 30 at 11:27
2
As I wrote we are currently working in the pdfresources management and try to setup things so that tricks as transparent has to use now to coordinate the resources with pgf is no longer needed. This will mean changes in both packages so I don't see much sense to do some intermediate repairs now.
– Ulrike Fischer
May 30 at 12:02
2
2
No it is not the fault of pgf but of the compability code in transparent: it tries to detect pgf to coordinate the pdf resources but the test is not quite correct if only a subpart of pgf is loaded. As we are currently working on the management of pdfresources this will stay until a real solution is there. See also github.com/ho-tex/oberdiek/issues/62
– Ulrike Fischer
May 30 at 9:50
No it is not the fault of pgf but of the compability code in transparent: it tries to detect pgf to coordinate the pdf resources but the test is not quite correct if only a subpart of pgf is loaded. As we are currently working on the management of pdfresources this will stay until a real solution is there. See also github.com/ho-tex/oberdiek/issues/62
– Ulrike Fischer
May 30 at 9:50
@UlrikeFischer so that would be it is known and I should just load more of pgf until things get fixed?
– StrongBad
May 30 at 10:45
@UlrikeFischer so that would be it is known and I should just load more of pgf until things get fixed?
– StrongBad
May 30 at 10:45
I think it's strange for pgf to define the generic
pgfutil@addpdfresource@extgs
in terms of a driver-specific macro which is undefined, but this is just my opinion. However the issue appeared after an update in transparent.sty
, so...– Phelype Oleinik
May 30 at 10:51
I think it's strange for pgf to define the generic
pgfutil@addpdfresource@extgs
in terms of a driver-specific macro which is undefined, but this is just my opinion. However the issue appeared after an update in transparent.sty
, so...– Phelype Oleinik
May 30 at 10:51
@PhelypeOleinik yes it is a bit strange, but it is an internal pgf command and it is not pgf's fault if transparent uses such an internal command wrongly.
– Ulrike Fischer
May 30 at 11:27
@PhelypeOleinik yes it is a bit strange, but it is an internal pgf command and it is not pgf's fault if transparent uses such an internal command wrongly.
– Ulrike Fischer
May 30 at 11:27
2
2
As I wrote we are currently working in the pdfresources management and try to setup things so that tricks as transparent has to use now to coordinate the resources with pgf is no longer needed. This will mean changes in both packages so I don't see much sense to do some intermediate repairs now.
– Ulrike Fischer
May 30 at 12:02
As I wrote we are currently working in the pdfresources management and try to setup things so that tricks as transparent has to use now to coordinate the resources with pgf is no longer needed. This will mean changes in both packages so I don't see much sense to do some intermediate repairs now.
– Ulrike Fischer
May 30 at 12:02
|
show 1 more comment
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f493285%2fclash-between-pgf-and-transparent-packages%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown