![]() ![]() You can add emphasis by formatting your text as bold or italic. That’s why I only use the hash symbols to indicate headers nowadays.ģ.3 Emphasis, sub- and superscripts and block quotes The line of hyphens or equals signs does not have to be exactly the same length as the text but if you’re like me it does anyway or I can’t rest. You can also indicate header 1 text by underlining it with hyphens, and header 2 by underlining with equals signs: If you start using header 1 for the main sections in your document and then absent-mindedly throw in some header 2s you’ll find that your table of contents reflects your confusion. When you render your document, if you ask nicely it will automatically generate a table of contents on the basis of the header types that you use, so it’s worth making sure that you are consistent in your use of the different levels of header. Second, don’t forget the space after the hash symbol or symbols. First, you need one or more blank lines before the header - if it just follows a previous line without a space the rendering software won’t recognise it as a header. Top tip Two things need you know about formatting headers. … 3.1 This for a sub-sub-sub-sub-header (AKA Header 5) If we render these, they’ll look like this:ģ.1 This indicates a header (often called a “Header 1”) 3.1 This for a sub-header (or Header 2) # This for a sub-sub-sub-sub-header (AKA "Header 5") # This indicates a header (often called a "Header 1") In markdown you use a hash # symbol to indicate a header, and the number of hashes sets the type of header - one for a main header, two for a sub-header, three for a sub-sub-header and so on. In other words, markdown 2 uses a hierarchy of headers, ranging from big headers that define whole sections or chapters down to sub-headers for large parts of those sections, sub-sub-headers if you want to divide those subsections up further and so on. If you’re writing in markdown then you’ll need to think explicitly about the structure of your document - think of your text as being structured as a hierarchy, with top level pieces (maybe think of these as chapters or something similar) each defined by a top-level header and then each of these optionally containing smaller pieces of material defined by sub-headers, each of which could then optionally contain smaller parts defined by sub-sub-headers and so on. If you’ve previously just used word-processors to prepare documents you might not have thought too much about how your document is structured - you might have simply made headers by changing the size and weight of some of your text, or you might have used some of the built-in header styles. 9.3.1 Using a style file to load a package: chemical formulae.9.2 Including LaTeX markup in your text.9 Creating and customising pdf documents.8.9 Using classes to format your document.8.8 Using a Cascading Style Sheet to format headers and body text.8.7 Using html for images in your document.7.1 Setting options with the front material.7 YAML Schmamal: Customising your document by setting global options.6.4 Choosing referencing styles using csl templates.5.3 Building a complex equation using LaTeX.4.7 Using R to add images to your document.4.6.1 Table from a matrix using stargazer, xtable and kable. ![]() 3.6.6 Things you can’t do with images in markdown.3.6.3 Use a picture that’s on the internet rather than one on your computer.3.3 Emphasis, sub- and superscripts and block quotes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |