https://sourceforge.net/p/koma-script/wiki-en/HowTo_Images/Recent changes to HowTo_ImagesenWed, 05 Jan 2022 13:30:18 -0000https://sourceforge.net/p/koma-script/wiki-en/HowTo_Images/<div class="markdown_content"><h1 id="how-to-include-images-and-pictures">How to include images and pictures</h1> <p>Many papers include external image files. Currently the most modern package for this purpose is <a class="" href="https://www.ctan.org/pkg/graphicx" rel="nofollow"><code>graphicx</code></a> as part of the <a class="" href="https://ctan.org/pkg/latex-graphics" rel="nofollow"><code>graphics</code> collection</a>. For more details on its use, see the <a class="" href="http://mirrors.ctan.org/macros/latex/required/graphics/grfguide.pdf" rel="nofollow">related manual</a>. It should be noted that you do not need the <code>pdftex</code> option, which is often used on the Internet, when loading the package and that it can even be annoying - not only when using LuaLaTeX or XeLaTeX. Therefore you should do without it. This is normally also true for option <code>dvips</code>. Therefore it is not necessary to distinguish between the different TeX engines within the document preamble and load the package with different options depending on whether PDFLaTeX, LuaLaTeX or XeLaTeX is used. A simple</p> <div class="codehilite"><pre><span></span><span class="k">\usepackage</span><span class="nb">{</span>graphicx<span class="nb">}</span> </pre></div> <p>is sufficient.</p> <p>By the way, the package is automatically loaded by some other graphics packages such as <a class="" href="https://www.ctan.org/pkg/pdfpages" rel="nofollow">pdfpages</a> or <a class="" href="https://www.ctan.org/pkg/pgf" rel="nofollow">TikZ</a> and does not need to be additionally loaded explicitly. If you load it yourself after such a package, the specification of one of the mentioned options would be an error. One more reason to leave them out.</p></div>Markus KohmWed, 05 Jan 2022 13:30:18 -0000https://sourceforge.net1f3423a2257d6409a69eec833d27f513998c38b3