Talk:LaTeX/Modular Documents

I am considering adding a section explaining how \include{file} compared to \input{file} allows one to reference between different included files. Input file does not allow this, good information at web.science.mq.edu.au. Keplerspeed (talk) 00:32, 25 May 2010 (UTC) Keplerspeed 25/05/2010
 * That's rather important piece of information. It would also be good to link to it from LaTeX/Basics Tomato86 (talk) 22:29, 22 July 2010 (UTC)
 * I removed all the \input and \include stuff from the Basic section, as it was a less detailed duplicate of the current chapter. I just left the link to this part. --Ambrevar (discuss • contribs) 14:28, 21 December 2012 (UTC)

Section on calling files in other directories
I wonder if this section should not be moved to a separate item, since the information contained here is common to any command which calls another file (e.g. graphicx commands)? Also, the reference to *nix may be too cryptic for some of the readership this manual addresses. This section could thus be reduced to a single-sentence reference to a more complete and generally useful section. Ediahist (discuss • contribs) 12:42, 14 July 2011 (UTC)

Sub folders issue
Trying to implement subfiles example I encounter a problem. If you put your subfiles in subdirectories e.g. chapter 1, chapter 2 etc and use this subfiles to call subsubfiles (this may seem peculiar but it normal if you have a plot in chapter 1 and want to call it with \includegraphics{./plot.pdf}) when you try to compile the chapter 1 tex file it works ok but if you go on and try to compile the main tex file you will end up with an error "./plot.pdf" not found. This is most probably because the main tex file and the chapter1.tex are in different directories.

Moved chapter
This chapter was previously called General Guidelines and I could never figure out what it was supposed to contain, I renamed it to Modular Documents, which is actually 95% of the chapter. I moved the last 5% (the last paragraph) to the programming part. I left a link to the Macros chapter in the Basic chapter so that first time readers will get to know how much macros are important. --Ambrevar (discuss • contribs) 14:28, 21 December 2012 (UTC)

Should there be information about installing LaTeX packages here?
It just seems a little out of scope to describe how to install some suggested packages.Nixphoeni (discuss • contribs) 16:06, 8 April 2014 (UTC)

document.tex
What is the advantage of putting

\usepackage{graphicx} \usepackage{ifpdf} \ifpdf % put here packages only for the PDF: \DeclareGraphicsExtensions{.pdf,.png,.jpg,.mps} \usepackage{hyperref} \else % put here packages only for the DVI: \fi

in document.tex file instead of the mystyle.sty file? Howeworth (discuss • contribs) 21:23, 19 August 2014 (UTC)


 * There is absolutely no need for that in any document written later than 2010. I'll remove that from the page.--Johannes Bo (discuss • contribs) 08:48, 7 October 2016 (UTC)


 * Another question… — this section says You import the only package you need, that is your mystyle.sty (note that in the code it has to be imported without the extension), then your document starts. …however, it actually does import hyperref and graphicx. Is this a typo? --Srl (discuss • contribs) 14:40, 16 February 2017 (UTC)


 * @Srl Do not create own package files, unless you feel you are experienced enough. Load the packages you need in your preamble. Load only the packages you need. But yes, the wikipage is incorrect and needs to be updated. Which is complicated, because i would simply delete it for containing bad advice.--Johannes Bo (discuss • contribs) 17:40, 17 February 2017 (UTC)

Version control systems
As this document focuses on writing 'a proper text with LaTeX', I would strongly recommend to mention version control systems. This no place to describe any of them, but to suggest to use such tools and what for. Then just provide some useful links (e.g. http://www.desy.de/~bargheer/gitintro/git.html --just the first result from Google). Does it make sense? --81.133.151.226 (discuss) 10:10, 22 March 2017 (UTC)

Master & slave
master and the slave files

Could you possibly replace the terminology there? Using it, is disputed and other projects already replaced them, see https://en.wikipedia.org/wiki/Master/slave_(technology)#Terminology_concerns. --Rugk (discuss • contribs) 14:40, 13 September 2018 (UTC)

incongruence "project structure" vs using \include and \includeonly
hi, as a newbie I just went through this page and am wondering whether the following is incongruent:


 * 1) the advice in the first section ("project structure") to create a directory "tex" for the .tex files (I did this and put the individual .tex files, that is, the chapters of my book in there, leaving just the main/"master" .tex-file on the parent directory - this is how I understood the advice).
 * 2) the following sections reference the .tex files to be included in the main document as if they were located in the same directory, not in the "tex" directory. e.g. \include{Chapter_1}  when it should be \include{tex/Chapter_1}. and the same for \includeonly.

This might cause a problem (it did for me) because readers might take "\input{filename}" literally. It should at least say that "filename" actually means "path to the file". While there is a section even explaining absolute and relative file paths, it is not immediately evident that one needs to use the relative file path instead of just the filename for "\input". The example code should be in line with the advice on project structure.

And of course: For whoever contributed to this: Thank you very much for this book/tutorial!

Jafado (discuss • contribs) 09:16, 5 November 2022 (UTC)