Conflict between tufte-book, adforn, and pdfx











up vote
2
down vote

favorite












When I try to use the tufte-book class with the adforn and pdfx packages, I am getting a problem with symbol substitutions. For example:



documentclass{tufte-book}
usepackage{adforn}
usepackage[x-1a]{pdfx}

begin{document}
textcopyright
end{document}


Generates:



Failure



If I do any one of (a) use the article class instead (b) leave out adforn (c) leave out pdfx, I get the proper symbol:



Success



I haven't a clue how to start diagnosing this. I could probably work around by creating my own copyright symbol, but I worry that other symbols in my large document might also be wrong. Any suggestions? Can others duplicate this?



I am using pdflatex with MiKtex on Windows.



Edit: this compiles for me without errors. Here is my logfile, I didn't see anything relevant.










share|improve this question




















  • 2




    Do you need the call of pdfx? Without it the compiles without error messages. With pdfx I gert error messages. Do you get some? Add them to your question please. BTW: Welcome to TeX.SE!
    – Kurt
    Dec 2 at 20:08












  • I don't get any errors, no. I can try to attach my log file though. I didn't see any relevant warnings. Thanks for the welcome, I have gotten much use previous answers on the site!
    – Cass Sackett
    Dec 2 at 21:03










  • The printer I am preparing this for requires pdf/X compliance. If there is a better way to achieve that I would be happy to hear.
    – Cass Sackett
    Dec 2 at 21:11






  • 2




    Well, you are using an older version pdfTeX, Version 3.14159265-2.6-1.40.18 (MiKTeX 2.9.6300 64-bit) (preloaded format=pdflatex 2017.5.9), the current version is pdfTeX, Version 3.14159265-2.6-1.40.19 (MiKTeX 2.9.6880 64-bit) (preloaded format=pdflatex 2018.12.1). to get the code compiled i have to change the order of pdfx and adforn and still receives an error message ! LaTeX Error: Option clash for package xcolor.
    – Kurt
    Dec 2 at 21:30

















up vote
2
down vote

favorite












When I try to use the tufte-book class with the adforn and pdfx packages, I am getting a problem with symbol substitutions. For example:



documentclass{tufte-book}
usepackage{adforn}
usepackage[x-1a]{pdfx}

begin{document}
textcopyright
end{document}


Generates:



Failure



If I do any one of (a) use the article class instead (b) leave out adforn (c) leave out pdfx, I get the proper symbol:



Success



I haven't a clue how to start diagnosing this. I could probably work around by creating my own copyright symbol, but I worry that other symbols in my large document might also be wrong. Any suggestions? Can others duplicate this?



I am using pdflatex with MiKtex on Windows.



Edit: this compiles for me without errors. Here is my logfile, I didn't see anything relevant.










share|improve this question




















  • 2




    Do you need the call of pdfx? Without it the compiles without error messages. With pdfx I gert error messages. Do you get some? Add them to your question please. BTW: Welcome to TeX.SE!
    – Kurt
    Dec 2 at 20:08












  • I don't get any errors, no. I can try to attach my log file though. I didn't see any relevant warnings. Thanks for the welcome, I have gotten much use previous answers on the site!
    – Cass Sackett
    Dec 2 at 21:03










  • The printer I am preparing this for requires pdf/X compliance. If there is a better way to achieve that I would be happy to hear.
    – Cass Sackett
    Dec 2 at 21:11






  • 2




    Well, you are using an older version pdfTeX, Version 3.14159265-2.6-1.40.18 (MiKTeX 2.9.6300 64-bit) (preloaded format=pdflatex 2017.5.9), the current version is pdfTeX, Version 3.14159265-2.6-1.40.19 (MiKTeX 2.9.6880 64-bit) (preloaded format=pdflatex 2018.12.1). to get the code compiled i have to change the order of pdfx and adforn and still receives an error message ! LaTeX Error: Option clash for package xcolor.
    – Kurt
    Dec 2 at 21:30















up vote
2
down vote

favorite









up vote
2
down vote

favorite











When I try to use the tufte-book class with the adforn and pdfx packages, I am getting a problem with symbol substitutions. For example:



documentclass{tufte-book}
usepackage{adforn}
usepackage[x-1a]{pdfx}

begin{document}
textcopyright
end{document}


Generates:



Failure



If I do any one of (a) use the article class instead (b) leave out adforn (c) leave out pdfx, I get the proper symbol:



Success



I haven't a clue how to start diagnosing this. I could probably work around by creating my own copyright symbol, but I worry that other symbols in my large document might also be wrong. Any suggestions? Can others duplicate this?



I am using pdflatex with MiKtex on Windows.



Edit: this compiles for me without errors. Here is my logfile, I didn't see anything relevant.










share|improve this question















When I try to use the tufte-book class with the adforn and pdfx packages, I am getting a problem with symbol substitutions. For example:



documentclass{tufte-book}
usepackage{adforn}
usepackage[x-1a]{pdfx}

begin{document}
textcopyright
end{document}


Generates:



Failure



If I do any one of (a) use the article class instead (b) leave out adforn (c) leave out pdfx, I get the proper symbol:



Success



I haven't a clue how to start diagnosing this. I could probably work around by creating my own copyright symbol, but I worry that other symbols in my large document might also be wrong. Any suggestions? Can others duplicate this?



I am using pdflatex with MiKtex on Windows.



Edit: this compiles for me without errors. Here is my logfile, I didn't see anything relevant.







tufte pdfx






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 2 at 21:08

























asked Dec 2 at 19:56









Cass Sackett

133




133








  • 2




    Do you need the call of pdfx? Without it the compiles without error messages. With pdfx I gert error messages. Do you get some? Add them to your question please. BTW: Welcome to TeX.SE!
    – Kurt
    Dec 2 at 20:08












  • I don't get any errors, no. I can try to attach my log file though. I didn't see any relevant warnings. Thanks for the welcome, I have gotten much use previous answers on the site!
    – Cass Sackett
    Dec 2 at 21:03










  • The printer I am preparing this for requires pdf/X compliance. If there is a better way to achieve that I would be happy to hear.
    – Cass Sackett
    Dec 2 at 21:11






  • 2




    Well, you are using an older version pdfTeX, Version 3.14159265-2.6-1.40.18 (MiKTeX 2.9.6300 64-bit) (preloaded format=pdflatex 2017.5.9), the current version is pdfTeX, Version 3.14159265-2.6-1.40.19 (MiKTeX 2.9.6880 64-bit) (preloaded format=pdflatex 2018.12.1). to get the code compiled i have to change the order of pdfx and adforn and still receives an error message ! LaTeX Error: Option clash for package xcolor.
    – Kurt
    Dec 2 at 21:30
















  • 2




    Do you need the call of pdfx? Without it the compiles without error messages. With pdfx I gert error messages. Do you get some? Add them to your question please. BTW: Welcome to TeX.SE!
    – Kurt
    Dec 2 at 20:08












  • I don't get any errors, no. I can try to attach my log file though. I didn't see any relevant warnings. Thanks for the welcome, I have gotten much use previous answers on the site!
    – Cass Sackett
    Dec 2 at 21:03










  • The printer I am preparing this for requires pdf/X compliance. If there is a better way to achieve that I would be happy to hear.
    – Cass Sackett
    Dec 2 at 21:11






  • 2




    Well, you are using an older version pdfTeX, Version 3.14159265-2.6-1.40.18 (MiKTeX 2.9.6300 64-bit) (preloaded format=pdflatex 2017.5.9), the current version is pdfTeX, Version 3.14159265-2.6-1.40.19 (MiKTeX 2.9.6880 64-bit) (preloaded format=pdflatex 2018.12.1). to get the code compiled i have to change the order of pdfx and adforn and still receives an error message ! LaTeX Error: Option clash for package xcolor.
    – Kurt
    Dec 2 at 21:30










2




2




Do you need the call of pdfx? Without it the compiles without error messages. With pdfx I gert error messages. Do you get some? Add them to your question please. BTW: Welcome to TeX.SE!
– Kurt
Dec 2 at 20:08






Do you need the call of pdfx? Without it the compiles without error messages. With pdfx I gert error messages. Do you get some? Add them to your question please. BTW: Welcome to TeX.SE!
– Kurt
Dec 2 at 20:08














I don't get any errors, no. I can try to attach my log file though. I didn't see any relevant warnings. Thanks for the welcome, I have gotten much use previous answers on the site!
– Cass Sackett
Dec 2 at 21:03




I don't get any errors, no. I can try to attach my log file though. I didn't see any relevant warnings. Thanks for the welcome, I have gotten much use previous answers on the site!
– Cass Sackett
Dec 2 at 21:03












The printer I am preparing this for requires pdf/X compliance. If there is a better way to achieve that I would be happy to hear.
– Cass Sackett
Dec 2 at 21:11




The printer I am preparing this for requires pdf/X compliance. If there is a better way to achieve that I would be happy to hear.
– Cass Sackett
Dec 2 at 21:11




2




2




Well, you are using an older version pdfTeX, Version 3.14159265-2.6-1.40.18 (MiKTeX 2.9.6300 64-bit) (preloaded format=pdflatex 2017.5.9), the current version is pdfTeX, Version 3.14159265-2.6-1.40.19 (MiKTeX 2.9.6880 64-bit) (preloaded format=pdflatex 2018.12.1). to get the code compiled i have to change the order of pdfx and adforn and still receives an error message ! LaTeX Error: Option clash for package xcolor.
– Kurt
Dec 2 at 21:30






Well, you are using an older version pdfTeX, Version 3.14159265-2.6-1.40.18 (MiKTeX 2.9.6300 64-bit) (preloaded format=pdflatex 2017.5.9), the current version is pdfTeX, Version 3.14159265-2.6-1.40.19 (MiKTeX 2.9.6880 64-bit) (preloaded format=pdflatex 2018.12.1). to get the code compiled i have to change the order of pdfx and adforn and still receives an error message ! LaTeX Error: Option clash for package xcolor.
– Kurt
Dec 2 at 21:30












1 Answer
1






active

oldest

votes

















up vote
3
down vote



accepted










The problem is common with tufte classes: they load hyperref too early. With pdfx, it is this package that should load it.



There is another small problem about tufte-book loading xcolor with options and pdfx doing the same with different options.



PassOptionsToPackage{cmyk,hyperref}{xcolor}
documentclass[nohyper]{tufte-book}
usepackage{adforn}
usepackage[x-1a]{pdfx}

begin{document}

textcopyright

end{document}


If you want to use the same hyperref setup as tufte-book, add



hypersetup{
pdfborder = {0 0 0},
bookmarksdepth = section,
citecolor = DarkGreen,
linkcolor = DarkBlue,
urlcolor = DarkGreen,
}


before begin{document}.



Why does the issue show when adforn is loaded? It's a bug of adforn explained in https://tex.stackexchange.com/a/394388/4427. It causes the U fontencoding to be current when pdfx is loaded, so for reasons too long to be explained, L8U ends up being assigned as the default encoding for textcopyright and many other commands, which is wrong because this encoding is only for internal use.



The fix I add below might be sufficient, but it's best to use nohyper anyways.



PassOptionsToPackage{cmyk,hyperref}{xcolor}
documentclass[nohyper]{tufte-book}
usepackage{adforn}
fontencoding{T1}selectfont % work around the adforn bug

usepackage[x-1a]{pdfx}

hypersetup{
pdfborder = {0 0 0},
bookmarksdepth = section,
citecolor = DarkGreen,
linkcolor = DarkBlue,
urlcolor = DarkGreen,
}

begin{document}

textcopyright

end{document}





share|improve this answer























  • Or maybe not. I don't know how I generated it.
    – cfr
    Dec 3 at 1:36










  • Thank you, this seemed to work! Though now there are other problems from pdfx, but perhaps I can sort them out.
    – Cass Sackett
    Dec 3 at 1:47












  • When I try to compile the example in the question, I get an error, which is fine, and then it hangs on loading the MPS to PDF converter.
    – cfr
    Dec 3 at 1:52










  • Sounds like I should be thankful this thing compiles for me at all!
    – Cass Sackett
    Dec 3 at 1:54










  • For future reference: the nohyper option seemed to cause a lot of trouble (on my real doc, not the test), but just including your adforn fix resolved the character problem
    – Cass Sackett
    Dec 3 at 1:56











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',
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f462849%2fconflict-between-tufte-book-adforn-and-pdfx%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








up vote
3
down vote



accepted










The problem is common with tufte classes: they load hyperref too early. With pdfx, it is this package that should load it.



There is another small problem about tufte-book loading xcolor with options and pdfx doing the same with different options.



PassOptionsToPackage{cmyk,hyperref}{xcolor}
documentclass[nohyper]{tufte-book}
usepackage{adforn}
usepackage[x-1a]{pdfx}

begin{document}

textcopyright

end{document}


If you want to use the same hyperref setup as tufte-book, add



hypersetup{
pdfborder = {0 0 0},
bookmarksdepth = section,
citecolor = DarkGreen,
linkcolor = DarkBlue,
urlcolor = DarkGreen,
}


before begin{document}.



Why does the issue show when adforn is loaded? It's a bug of adforn explained in https://tex.stackexchange.com/a/394388/4427. It causes the U fontencoding to be current when pdfx is loaded, so for reasons too long to be explained, L8U ends up being assigned as the default encoding for textcopyright and many other commands, which is wrong because this encoding is only for internal use.



The fix I add below might be sufficient, but it's best to use nohyper anyways.



PassOptionsToPackage{cmyk,hyperref}{xcolor}
documentclass[nohyper]{tufte-book}
usepackage{adforn}
fontencoding{T1}selectfont % work around the adforn bug

usepackage[x-1a]{pdfx}

hypersetup{
pdfborder = {0 0 0},
bookmarksdepth = section,
citecolor = DarkGreen,
linkcolor = DarkBlue,
urlcolor = DarkGreen,
}

begin{document}

textcopyright

end{document}





share|improve this answer























  • Or maybe not. I don't know how I generated it.
    – cfr
    Dec 3 at 1:36










  • Thank you, this seemed to work! Though now there are other problems from pdfx, but perhaps I can sort them out.
    – Cass Sackett
    Dec 3 at 1:47












  • When I try to compile the example in the question, I get an error, which is fine, and then it hangs on loading the MPS to PDF converter.
    – cfr
    Dec 3 at 1:52










  • Sounds like I should be thankful this thing compiles for me at all!
    – Cass Sackett
    Dec 3 at 1:54










  • For future reference: the nohyper option seemed to cause a lot of trouble (on my real doc, not the test), but just including your adforn fix resolved the character problem
    – Cass Sackett
    Dec 3 at 1:56















up vote
3
down vote



accepted










The problem is common with tufte classes: they load hyperref too early. With pdfx, it is this package that should load it.



There is another small problem about tufte-book loading xcolor with options and pdfx doing the same with different options.



PassOptionsToPackage{cmyk,hyperref}{xcolor}
documentclass[nohyper]{tufte-book}
usepackage{adforn}
usepackage[x-1a]{pdfx}

begin{document}

textcopyright

end{document}


If you want to use the same hyperref setup as tufte-book, add



hypersetup{
pdfborder = {0 0 0},
bookmarksdepth = section,
citecolor = DarkGreen,
linkcolor = DarkBlue,
urlcolor = DarkGreen,
}


before begin{document}.



Why does the issue show when adforn is loaded? It's a bug of adforn explained in https://tex.stackexchange.com/a/394388/4427. It causes the U fontencoding to be current when pdfx is loaded, so for reasons too long to be explained, L8U ends up being assigned as the default encoding for textcopyright and many other commands, which is wrong because this encoding is only for internal use.



The fix I add below might be sufficient, but it's best to use nohyper anyways.



PassOptionsToPackage{cmyk,hyperref}{xcolor}
documentclass[nohyper]{tufte-book}
usepackage{adforn}
fontencoding{T1}selectfont % work around the adforn bug

usepackage[x-1a]{pdfx}

hypersetup{
pdfborder = {0 0 0},
bookmarksdepth = section,
citecolor = DarkGreen,
linkcolor = DarkBlue,
urlcolor = DarkGreen,
}

begin{document}

textcopyright

end{document}





share|improve this answer























  • Or maybe not. I don't know how I generated it.
    – cfr
    Dec 3 at 1:36










  • Thank you, this seemed to work! Though now there are other problems from pdfx, but perhaps I can sort them out.
    – Cass Sackett
    Dec 3 at 1:47












  • When I try to compile the example in the question, I get an error, which is fine, and then it hangs on loading the MPS to PDF converter.
    – cfr
    Dec 3 at 1:52










  • Sounds like I should be thankful this thing compiles for me at all!
    – Cass Sackett
    Dec 3 at 1:54










  • For future reference: the nohyper option seemed to cause a lot of trouble (on my real doc, not the test), but just including your adforn fix resolved the character problem
    – Cass Sackett
    Dec 3 at 1:56













up vote
3
down vote



accepted







up vote
3
down vote



accepted






The problem is common with tufte classes: they load hyperref too early. With pdfx, it is this package that should load it.



There is another small problem about tufte-book loading xcolor with options and pdfx doing the same with different options.



PassOptionsToPackage{cmyk,hyperref}{xcolor}
documentclass[nohyper]{tufte-book}
usepackage{adforn}
usepackage[x-1a]{pdfx}

begin{document}

textcopyright

end{document}


If you want to use the same hyperref setup as tufte-book, add



hypersetup{
pdfborder = {0 0 0},
bookmarksdepth = section,
citecolor = DarkGreen,
linkcolor = DarkBlue,
urlcolor = DarkGreen,
}


before begin{document}.



Why does the issue show when adforn is loaded? It's a bug of adforn explained in https://tex.stackexchange.com/a/394388/4427. It causes the U fontencoding to be current when pdfx is loaded, so for reasons too long to be explained, L8U ends up being assigned as the default encoding for textcopyright and many other commands, which is wrong because this encoding is only for internal use.



The fix I add below might be sufficient, but it's best to use nohyper anyways.



PassOptionsToPackage{cmyk,hyperref}{xcolor}
documentclass[nohyper]{tufte-book}
usepackage{adforn}
fontencoding{T1}selectfont % work around the adforn bug

usepackage[x-1a]{pdfx}

hypersetup{
pdfborder = {0 0 0},
bookmarksdepth = section,
citecolor = DarkGreen,
linkcolor = DarkBlue,
urlcolor = DarkGreen,
}

begin{document}

textcopyright

end{document}





share|improve this answer














The problem is common with tufte classes: they load hyperref too early. With pdfx, it is this package that should load it.



There is another small problem about tufte-book loading xcolor with options and pdfx doing the same with different options.



PassOptionsToPackage{cmyk,hyperref}{xcolor}
documentclass[nohyper]{tufte-book}
usepackage{adforn}
usepackage[x-1a]{pdfx}

begin{document}

textcopyright

end{document}


If you want to use the same hyperref setup as tufte-book, add



hypersetup{
pdfborder = {0 0 0},
bookmarksdepth = section,
citecolor = DarkGreen,
linkcolor = DarkBlue,
urlcolor = DarkGreen,
}


before begin{document}.



Why does the issue show when adforn is loaded? It's a bug of adforn explained in https://tex.stackexchange.com/a/394388/4427. It causes the U fontencoding to be current when pdfx is loaded, so for reasons too long to be explained, L8U ends up being assigned as the default encoding for textcopyright and many other commands, which is wrong because this encoding is only for internal use.



The fix I add below might be sufficient, but it's best to use nohyper anyways.



PassOptionsToPackage{cmyk,hyperref}{xcolor}
documentclass[nohyper]{tufte-book}
usepackage{adforn}
fontencoding{T1}selectfont % work around the adforn bug

usepackage[x-1a]{pdfx}

hypersetup{
pdfborder = {0 0 0},
bookmarksdepth = section,
citecolor = DarkGreen,
linkcolor = DarkBlue,
urlcolor = DarkGreen,
}

begin{document}

textcopyright

end{document}






share|improve this answer














share|improve this answer



share|improve this answer








edited Dec 3 at 0:05

























answered Dec 2 at 23:33









egreg

703k8618743151




703k8618743151












  • Or maybe not. I don't know how I generated it.
    – cfr
    Dec 3 at 1:36










  • Thank you, this seemed to work! Though now there are other problems from pdfx, but perhaps I can sort them out.
    – Cass Sackett
    Dec 3 at 1:47












  • When I try to compile the example in the question, I get an error, which is fine, and then it hangs on loading the MPS to PDF converter.
    – cfr
    Dec 3 at 1:52










  • Sounds like I should be thankful this thing compiles for me at all!
    – Cass Sackett
    Dec 3 at 1:54










  • For future reference: the nohyper option seemed to cause a lot of trouble (on my real doc, not the test), but just including your adforn fix resolved the character problem
    – Cass Sackett
    Dec 3 at 1:56


















  • Or maybe not. I don't know how I generated it.
    – cfr
    Dec 3 at 1:36










  • Thank you, this seemed to work! Though now there are other problems from pdfx, but perhaps I can sort them out.
    – Cass Sackett
    Dec 3 at 1:47












  • When I try to compile the example in the question, I get an error, which is fine, and then it hangs on loading the MPS to PDF converter.
    – cfr
    Dec 3 at 1:52










  • Sounds like I should be thankful this thing compiles for me at all!
    – Cass Sackett
    Dec 3 at 1:54










  • For future reference: the nohyper option seemed to cause a lot of trouble (on my real doc, not the test), but just including your adforn fix resolved the character problem
    – Cass Sackett
    Dec 3 at 1:56
















Or maybe not. I don't know how I generated it.
– cfr
Dec 3 at 1:36




Or maybe not. I don't know how I generated it.
– cfr
Dec 3 at 1:36












Thank you, this seemed to work! Though now there are other problems from pdfx, but perhaps I can sort them out.
– Cass Sackett
Dec 3 at 1:47






Thank you, this seemed to work! Though now there are other problems from pdfx, but perhaps I can sort them out.
– Cass Sackett
Dec 3 at 1:47














When I try to compile the example in the question, I get an error, which is fine, and then it hangs on loading the MPS to PDF converter.
– cfr
Dec 3 at 1:52




When I try to compile the example in the question, I get an error, which is fine, and then it hangs on loading the MPS to PDF converter.
– cfr
Dec 3 at 1:52












Sounds like I should be thankful this thing compiles for me at all!
– Cass Sackett
Dec 3 at 1:54




Sounds like I should be thankful this thing compiles for me at all!
– Cass Sackett
Dec 3 at 1:54












For future reference: the nohyper option seemed to cause a lot of trouble (on my real doc, not the test), but just including your adforn fix resolved the character problem
– Cass Sackett
Dec 3 at 1:56




For future reference: the nohyper option seemed to cause a lot of trouble (on my real doc, not the test), but just including your adforn fix resolved the character problem
– Cass Sackett
Dec 3 at 1:56


















draft saved

draft discarded




















































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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f462849%2fconflict-between-tufte-book-adforn-and-pdfx%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

How to send String Array data to Server using php in android

Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

Is anime1.com a legal site for watching anime?