Modular projects: Compile parent and child documents using separate custom classes












0















I would like to compile a main.tex parent document using a custom class as well as child documents using different custom classes. I would like compilation of the parent document to automatically compile and correctly insert the child documents in place. How can I accomplish this without simply inserting a separate PDF file with pdfpages? The standalone and subfiles packages appear to nearly work, but custom classes must also be defined for the child documents.



Parent document:



documentclass{acustomclass}

begin{document}
childdocument
end{document}


Child document:



documentclass{anothercustomclass}

begin{document}
Hooray!
end{document}









share|improve this question

























  • What does "appear to nearly work" mean? Can you describe the intended output and post some code of what you've already tried (minimal working example (MWE)) and describe, where it falls short, e.g. what should happen with the page numbers, etc.

    – DG'
    Jan 22 at 13:35











  • It's a rather generic question in that I simply would like to include a child document that uses a custom documentclass in a main document.

    – Adam Erickson
    Jan 22 at 19:14






  • 2





    The combine class may be of some help. Read the manual (> texdoc combine).

    – Peter Wilson
    Jan 22 at 19:46











  • @AdamErickson I fear then, that your question (without problem description and expected output) is simply too generic

    – DG'
    Jan 22 at 19:46






  • 1





    In addition to Peter's comment: There are several packages that could probably do what you want. Here is a list on CTAN: ctan.org/topic/subdocs

    – DG'
    Jan 22 at 19:51
















0















I would like to compile a main.tex parent document using a custom class as well as child documents using different custom classes. I would like compilation of the parent document to automatically compile and correctly insert the child documents in place. How can I accomplish this without simply inserting a separate PDF file with pdfpages? The standalone and subfiles packages appear to nearly work, but custom classes must also be defined for the child documents.



Parent document:



documentclass{acustomclass}

begin{document}
childdocument
end{document}


Child document:



documentclass{anothercustomclass}

begin{document}
Hooray!
end{document}









share|improve this question

























  • What does "appear to nearly work" mean? Can you describe the intended output and post some code of what you've already tried (minimal working example (MWE)) and describe, where it falls short, e.g. what should happen with the page numbers, etc.

    – DG'
    Jan 22 at 13:35











  • It's a rather generic question in that I simply would like to include a child document that uses a custom documentclass in a main document.

    – Adam Erickson
    Jan 22 at 19:14






  • 2





    The combine class may be of some help. Read the manual (> texdoc combine).

    – Peter Wilson
    Jan 22 at 19:46











  • @AdamErickson I fear then, that your question (without problem description and expected output) is simply too generic

    – DG'
    Jan 22 at 19:46






  • 1





    In addition to Peter's comment: There are several packages that could probably do what you want. Here is a list on CTAN: ctan.org/topic/subdocs

    – DG'
    Jan 22 at 19:51














0












0








0








I would like to compile a main.tex parent document using a custom class as well as child documents using different custom classes. I would like compilation of the parent document to automatically compile and correctly insert the child documents in place. How can I accomplish this without simply inserting a separate PDF file with pdfpages? The standalone and subfiles packages appear to nearly work, but custom classes must also be defined for the child documents.



Parent document:



documentclass{acustomclass}

begin{document}
childdocument
end{document}


Child document:



documentclass{anothercustomclass}

begin{document}
Hooray!
end{document}









share|improve this question
















I would like to compile a main.tex parent document using a custom class as well as child documents using different custom classes. I would like compilation of the parent document to automatically compile and correctly insert the child documents in place. How can I accomplish this without simply inserting a separate PDF file with pdfpages? The standalone and subfiles packages appear to nearly work, but custom classes must also be defined for the child documents.



Parent document:



documentclass{acustomclass}

begin{document}
childdocument
end{document}


Child document:



documentclass{anothercustomclass}

begin{document}
Hooray!
end{document}






pdfpages standalone import subfiles






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 22 at 21:58







Adam Erickson

















asked Jan 21 at 21:13









Adam EricksonAdam Erickson

1918




1918













  • What does "appear to nearly work" mean? Can you describe the intended output and post some code of what you've already tried (minimal working example (MWE)) and describe, where it falls short, e.g. what should happen with the page numbers, etc.

    – DG'
    Jan 22 at 13:35











  • It's a rather generic question in that I simply would like to include a child document that uses a custom documentclass in a main document.

    – Adam Erickson
    Jan 22 at 19:14






  • 2





    The combine class may be of some help. Read the manual (> texdoc combine).

    – Peter Wilson
    Jan 22 at 19:46











  • @AdamErickson I fear then, that your question (without problem description and expected output) is simply too generic

    – DG'
    Jan 22 at 19:46






  • 1





    In addition to Peter's comment: There are several packages that could probably do what you want. Here is a list on CTAN: ctan.org/topic/subdocs

    – DG'
    Jan 22 at 19:51



















  • What does "appear to nearly work" mean? Can you describe the intended output and post some code of what you've already tried (minimal working example (MWE)) and describe, where it falls short, e.g. what should happen with the page numbers, etc.

    – DG'
    Jan 22 at 13:35











  • It's a rather generic question in that I simply would like to include a child document that uses a custom documentclass in a main document.

    – Adam Erickson
    Jan 22 at 19:14






  • 2





    The combine class may be of some help. Read the manual (> texdoc combine).

    – Peter Wilson
    Jan 22 at 19:46











  • @AdamErickson I fear then, that your question (without problem description and expected output) is simply too generic

    – DG'
    Jan 22 at 19:46






  • 1





    In addition to Peter's comment: There are several packages that could probably do what you want. Here is a list on CTAN: ctan.org/topic/subdocs

    – DG'
    Jan 22 at 19:51

















What does "appear to nearly work" mean? Can you describe the intended output and post some code of what you've already tried (minimal working example (MWE)) and describe, where it falls short, e.g. what should happen with the page numbers, etc.

– DG'
Jan 22 at 13:35





What does "appear to nearly work" mean? Can you describe the intended output and post some code of what you've already tried (minimal working example (MWE)) and describe, where it falls short, e.g. what should happen with the page numbers, etc.

– DG'
Jan 22 at 13:35













It's a rather generic question in that I simply would like to include a child document that uses a custom documentclass in a main document.

– Adam Erickson
Jan 22 at 19:14





It's a rather generic question in that I simply would like to include a child document that uses a custom documentclass in a main document.

– Adam Erickson
Jan 22 at 19:14




2




2





The combine class may be of some help. Read the manual (> texdoc combine).

– Peter Wilson
Jan 22 at 19:46





The combine class may be of some help. Read the manual (> texdoc combine).

– Peter Wilson
Jan 22 at 19:46













@AdamErickson I fear then, that your question (without problem description and expected output) is simply too generic

– DG'
Jan 22 at 19:46





@AdamErickson I fear then, that your question (without problem description and expected output) is simply too generic

– DG'
Jan 22 at 19:46




1




1





In addition to Peter's comment: There are several packages that could probably do what you want. Here is a list on CTAN: ctan.org/topic/subdocs

– DG'
Jan 22 at 19:51





In addition to Peter's comment: There are several packages that could probably do what you want. Here is a list on CTAN: ctan.org/topic/subdocs

– DG'
Jan 22 at 19:51










0






active

oldest

votes











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


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f471203%2fmodular-projects-compile-parent-and-child-documents-using-separate-custom-class%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f471203%2fmodular-projects-compile-parent-and-child-documents-using-separate-custom-class%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

Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

ComboBox Display Member on multiple fields

Is it possible to collect Nectar points via Trainline?