\nNotes

1note↩

\n\n

2This is the footnote content.↩

\n\n

3This is the footnote text. We are now going to add a second line\nafter typing in four spaces.↩

\n\n\n

",{"_437":438,"_42":43,"_46":47,"_44":45,"_64":65,"_439":440,"_543":435},"previewContent","

\n Introduction\n
- \n Leanpub Flavoured Markdown vs. Markua\n
- \n Switching Writing Modes\n
- \n Scope of this Manual\n
\n
\n Book.txt, Sample.txt and Manuscript Files\n
- \n The Book.txt File\n
- \n Making a Sample Book for Readers to Browse for Free\n
- \n Adding Images or Pictures to Your Book\n
- \n A Note About Character Encoding\n
\n
\n How Markdown is Used in Leanpub\n
\n Attributes\n
\n Creating A New Book\n
- \n How To Set The Book’s Structure\n
\n
\n Sample Books\n
- \n Why Sample Books?\n
- \n Consequences for Manuscripts\n
\n
\n Images\n
- \n How To Insert An Image\n
- \n Image Format And Resolution\n
- \n Positioning An Image On The Page\n
\n
\n Languages and Letter Accents\n
- \n Setting the Main Language Used in the Book\n
- \n Overriding Leanpub Language Defaults\n
- \n Switching back and forth between language fonts\n
- \n A note about writing Leanpub books in Japanese, Korean and Chinese\n
- \n A note about writing Leanpub books in right-to-left (RTL) languages\n
\n
\n Parts, Chapters and Sections\n
- \n Parts\n
- \n Chapters, Sections and Sub-sections\n
- \n Table of Contents\n
- \n Front Matter, Main Matter and Back Matter\n
\n
\n Styling Text\n
- \n Bold, Emphasis/Italics, and Underlining\n
- \n Superscripts\n
- \n Monospaced Text\n
- \n Non-Breaking Spaces\n
\n
\n Blocks Of Text\n
- \n Paragraphs\n
- \n Centering Paragraphs Or Lines Of Text\n
- \n Numbered/Ordered Lists\n
- \n Unordered/Bulleted Lists\n
- \n Definition Lists\n
- \n Blockquotes\n
- \n Asides/Sidebars\n
- \n More Text Block Types\n
- \n Warning!\n
- \n Tips\n
- \n Errors\n
- \n Information\n
- \n Questions\n
- \n Discussions\n
- \n Exercises\n
- \n Generic Boxes\n
\n
\n Code\n
- \n Code Samples\n
- \n Code Sample Titles\n
- \n Marking lines as deleted or added to a code block\n
\n
\n Poetry\n
- \n Poetry Stanzas in Regular Markdown\n
- \n Spacing Control for Poetry\n
- \n Line Lengths\n
\n
\n Links\n
- \n Formatting Links\n
- \n Long Hyperlinks\n
- \n Footnotes and Hyperlinks in PDF\n
\n
\n Footnotes and Endnotes\n
- \n Footnotes\n
- \n Endnotes\n
- \n Remove Footnotes\n
\n
\n Crosslinks\n
- \n Quick Explanation\n
- \n Longer Explanation\n
- \n Crosslinking to something with an ID\n
- \n Some Crosslink Details\n
\n
\n Breaks\n
- \n Pagebreaks\n
- \n Line Breaks\n
\n
\n Tables\n
- \n Table Width\n
- \n Multi-line rows\n
- \n Alignment and footer rows\n
- \n Table Titles\n
- \n HTML Tables\n
- \n A note on combining attributes\n
\n
\n Miscellaneous\n
- \n Escaping Markdown Syntax Characters\n
- \n How To Exclude Lines From Your Book\n
- \n Mathematical Equations\n
- \n Curly Quotes\n
- \n Figure Captions and Labels\n
- \n Links In Footnotes\n
- \n Why can’t I put section commands in Book.txt?\n
- \n Trouble With Accents? Forcing Text Editors To Save As UTF-8\n
- \n I don’t understand how things get added to a Table of Contents\n
- \n What encoding should I use to write files in Markdown? Should I write in ASCII or UTF-8?\n
- \n How Can I Add Blank Lines To My Text?\n
- \n Adding a motto or epigraph to the beginning of a chapter\n
- \n Disabling Line Numbers While Nesting Code Blocks In Lists\n
- \n Indentation\n
- \n Hanging Indents\n
- \n Long strings of characters running off the right-hand side of the page / the right margin\n
\n
\n Notes\n

\nIntroduction

\n\n

\nLeanpub Flavoured Markdown vs. Markua

\n\n

On Leanpub, there are two ways to write in plain text:

\n\n

Leanpub Flavoured Markdown (LFM)
Markua 0.10

\n\n

Leanpub Flavoured Markdown came first; Markua is its replacement. Both LFM and Markua are dialects of Markdown. Markua is newer and better than LFM, but there are still some advanced features in Markua that aren’t finished yet.

\n\n

The version of Markua that Leanpub uses is Markua 0.10. It is documented here.

\n\n

To write in LFM or Markua, you need to be in Dropbox, GitHub or Bitbucket writing mode, or you need to be writing in the Leanpub In-Browser Text Editor. The Leanpub Visual Editor, Google Docs and Bring Your Own Book mode do not support LFM or Markua formatting.

\n\n

There are six good reasons to write a book in Markua:

\n\n

Markua is better than LFM. A lot better. Markua fixes the many mistakes we made with LFM.
Markua is the future of Leanpub.
Markua has more features than LFM.
If you want to create a course on Leanpub, you need to use Markua.
The Leanpub In-Browser Text Editor is better with Markua now, and it’s going to be way better soon. (We’re working on an upgrade to the Leanpub In-Browser Text Editor which will only be available for Markua books.)
The Markua Manual is newer and better than the Leanpub Flavoured Markdown Manual.

\n\n

There are two good reasons to write a book in LFM:

\n\n

You already started your book in LFM and you don’t want to convert it yet.
You are writing a translation of a book which is written in LFM.

\n\n

\nSwitching Writing Modes

\n\n

If you have an existing Leanpub book and you want to switch writing modes, you go here:

\n\n

Author > Books > (your book) > Settings > Writing Mode

\n\n

Again, Google Docs, our Visual Editor and Bring Your Own Book do not support Markua or LFM formatting.

\n\n

Once you’ve chosen an appropriate writing mode, you then can switch between the Markua and LFM dialects of Markdown here:

\n\n

Author > Books > (your book) > Settings > Markdown Dialect

\n\n

\nScope of this Manual

\n\n

This manual explains how to write in Leanpub Flavoured Markdown, or LFM for short.

\n\n

This manual does not explain how to use Leanpub, just how to write in LFM.

\n\n

To learn more about how to use Leanpub, you can see The Leanpub Manual.

\n\n

If you can’t find the answers there, there are 3 ways to get help…

\n\n

Search our Help Center at http://help.leanpub.com/\n
Join the Leanpub Forum at https://community.leanpub.com/c/authors and post your question there. Our authors enjoys helping each other out! Please ask all general questions here.
If you have a specific problem that you don’t want to post on the forum, email us at hello@leanpub.com and we’ll be happy to help you.

\n\n

To learn more about Leanpub Flavoured Markdown, read on…

\n\n

\nBook.txt, Sample.txt and Manuscript Files

\n\n

Your book will consist of a bunch of text files. Typically they have the file extension .txt. You can write them using any program you like; just save the files as plain text.

\n\n

To illustrate, we’re going to write an epic fantasy novel together. Let’s give it a suitably epic title: The Cliché Chronicles.

\n\n

This is the content of the file called chapter1.txt:

\n\n

# Chapter 1: A Stormy Beginning

\n\n

Lord Char, black cloak flapping around him in the rising storm, rubbed his hands together in anticipation as he strode to the middle of the circle of stones. He had been years in preparation for this, his moment of triumph.

\n\n

It was time to use the knowledge he had gained through years of patient planning. Now The Unnamed One would pay!

\n\n

And this is the content of the file called chapter2.txt:

\n\n

# Chapter 2: You Are Not My Father!

\n\n

## A Horrible realization

\n\n

Suddenly, he realized who his father had to have been.\nNo wonder the dark riders had chased him half way across the continent!

\n\n

## The Horror Grows

\n\n

With growing horror, he pulled the dark pulsing amulet from his cloak.\nIf The Unnamed One was truly his father, he shuddered, then the amulet must be The Jewel of Rak Crasha!

\n\n

See those number # signs? They’re an example of what it’s like to write in the formatting style called Markdown. If you want to write a chapter heading, just put a # at the start of the line, instead of hunting for ‘styles’ like you would in Microsoft Word. And if you want a sub-heading, just type two number signs ‘##’. We chose Markdown as our formatting system (even typewriters have a formatting system!) because it was created to make sense and let you focus on writing words instead of overly complex formatting stuff.

\n\n

Anyways, back to the book we’re writing!

\n\n

When Leanpub converts this text into a book for you, the # headings will start new chapters and the ## headings will start new sections. So, there are two chapters here - “Chapter 1: A Stormy Beginning” and “Chapter 2: You Are Not My Father!”. Chapter 2 contains two sections: “A Horrible Realization” and “The Horror Grows”.

\n\n

\nThe Book.txt File

\n\n

As mentioned above, the content of your book is all tied together by the Book.txt file. This is a list of all the files you want in your book, in the correct order.

\n\n

The text you’d type in the Book.txt file for The Cliché Chronicles would look like this:

\n\n

1 chapter1.txt\n2 chapter2.txt\n

\n\n\n\n

Yup, that’s it. It’s just a list of the names of the files in your manuscript folder that you want to appear in your book, in the order you want them to appear. Think of it as your Table of Contents.

\n\n\n\n

\nMaking a Sample Book for Readers to Browse for Free

\n\n

(Please note that if you are using our in-browser editor with LFM, it’s currently not possible to make a sample book, sorry. It is possible with Markua books.)

\n\n

If you want prospective customers to read a sample of your book for free, you can make a file called Sample.txt in your manuscript folder. This file works exactly like Book.txt. Just list all of the files that you want to be included in your book sample.

\n\n

(Please note that a new Sample Book file will be created for you to review every time you make a new preview of your book. However, the Sample Book available to customers will only be updated when you publish a new version of your book.)

\n\n\n\n

OK, let’s let potential readers of The Cliché Chronicles browse the first chapter for free. Once they read that, they’ll be hooked and will rush to buy the book so they can read the rest.

\n\n

To do this, just type this in the Sample.txt file:

\n\n

chapter1.txt

\n\n

Next time you Preview or Publish your book, Leanpub will create a separate sample ebook containing just chapter one, because that’s the only chapter listed in Sample.txt.

\n\n

\nAdding Images or Pictures to Your Book

\n\n

It’s easy to add images or pictures to your book. To do this, you need to:

\n\n

Put the images or pictures in your images folder (it’s in your manuscript folder).
Tell Leanpub where you want the image to appear in your book. You do this by typing the image name directly into your text, with a little help from Markdown formatting.

\n\n

So, to add images to your book, first put them in the images folder inside your book’s manuscript folder.

\n\n

Then, you need to tell Leanpub where to put the images in your book.

\n\n

Let’s say we want to put an image in our book that we’ve saved as ‘Sword.png’. Just put the ‘Sword.png’ file in your images folder, and then type this in your .txt file, in a line on its own, wherever you’d like the image to appear:

\n\n

![An awesome sword](images/Sword.png)

\n\n

Now, the next time you create a Preview, the image will appear with the caption ‘An awesome sword’. If you don’t want a caption, just leave that part of the instruction empty, like this:

\n\n

![](images/Sword.png)

\n\n

\nA Note About Character Encoding

\n\n

Depending on the text editor you are using and its settings, sometimes you may see weird characters appear in your text, and some characters may fail to appear at all. If you are experiencing this issue, you can try forcing the character encoding to be UTF-8.

\n\n

To edit character encoding, go to Author > Books > your book > Settings > Generation Settings.

\n\n

\nHow Markdown is Used in Leanpub

\n\n

Even if you know Markdown, you need to learn a few things about how we use it at Leanpub.

\n\n

\nImporting Markdown Files

\n\n

To import Markdown files to Leanpub, you can just save them as .txt files, put them in your book’s manuscript folder, and refer to them in Book.txt (the list of files to be included in your book, in the order you’d like them to appear), and generate a new Preview of your book.

\n\n

\nHeading Levels Become Chapters and Sections

\n\n

First, we use # chapters, ## for sections and ### for sub-sections. (You can also use #### for sub-sub-sections, but don’t get carried away! Most technical books are good with just #, ## and ###, and most business and fiction books are good with just # and possibly ##.)

\n\n

So, if you look at the top of the Markdown.txt file you’ll see that it has one #, meaning it is a Chapter.

\n\n

Another thing this means is that one file can contain as many chapters or sections as you want: every # makes a new chapter; it has nothing to do with what file it is in. However, we strongly recommend having one file per chapter (or one file per chapter section), since it makes creating sample books easier and keeps your book directory cleaner. Since we recommend this, that’s what we’ll do in this example book.

\n\n

\nLinks Become Footnotes

\n\n

We support Markdown syntax for links, as well as normal HTML links. Both of these are converted into functioning footnotes in the PDF. Here’s an example of a link to Leanpub.

\n\n

And here’s what it looks like in Markdown (i.e., this is what you type in the text file to get that link):

\n\n

[Leanpub](http://leanpub.com)

\n\n

\nMarkdown Extensions in Leanpub

\n\n

We’ve made a few additions to Markdown for use in Leanpub. Two of the most important are tables and crosslinks. Furthermore, since Leanpub is so good for technical books, we also support extensions for external code samples, special directives for code syntnax highlighting, etc.

\n\n

We use almost all of the Kramdown extensions (see http://kramdown.gettalong.org/syntax.html for a list of them). Two exceptions are:

\n\n

1) HTML blocks – we don’t support HTML elements in our Markdown.

\n\n

2) << becoming a left guillemet. We took this out when we created the external code sample syntax.

\n\n

\nFormatting Email Links

\n\n

Email links are formatted by simply surrounding the address with < and >.

\n\n

Just click on hello@leanpub.com to send us an email.

\n\n

1 Just click on <hello@leanpub.com> to send us an email.\n

\n\n\n\n

\nAttributes

\n\n

You can set various ‘attributes’ directly in your book files, like setting the code language, or line numbering. You do this by adding the syntax on their own separate lines in the text.

\n\n

To be clear, each attribute should be alone on a line, with blank lines above and below it (unless it’s at the beginning of the file, in which case you just need a blank line below it!).

\n\n

In general, the syntax works like this:

\n\n

{some-attribute=value}

\n\n

{some-attribute=”some attribute value”}

\n\n

Quotes are only necessary if there are spaces.

\n\n

You can have multiple attributes too. Separate them with commas.

\n\n

{language=ruby,line-numbers=off}

\n\n

Spaces are not significant, so you could also write:

\n\n

{language=ruby, line-numbers=off}

\n\n

id: {#some-id}

\n\n

So, for example, if you want a file or section to be front matter (like an introduction, which will have roman numerals for page numbers), at the top of the file or section just type:

\n\n

{frontmatter}

\n\n

Or if you want to turn on line numbering just for that section, type:

\n\n

{line-numbers=on}

\n\n

Here are the attributes supported:

\n\n

general: id\ncode blocks: language, line-numbers\nfiles: encoding

\n\n

special names:\n{pagebreak}\n{frontmatter}\n{mainmatter}\n{backmatter}

\n\n

\nCreating A New Book

\n\n

\nHow To Set The Book’s Structure

\n\n

To set the structure for your book - that is, what content you want to appear and in what order - you use the Book.txt file in your book’s ‘manuscript’ folder.

\n\n

‘Book.txt’ is a list of the files that you want included in your book, in the order that you want them to appear.

\n\n

So if you have .txt files in your ‘manuscript’ folder called ‘chapterone.txt’ and ‘chaptertwo.txt’ and you want them to appear one after the other in your book, open Book.txt and type:

\n\n

chapterone.txt\nchaptertwo.txt

\n\n

This means that you can actually have content in your ‘manuscript’ folder that isn’t included in your ebook. Only the files listed in ‘Book.txt’ will appear in your book. This is useful if you’re working on new chapters that you don’t yet want to include in the latest version of your book, for example. You don’t have to take the file out of ‘manuscript’; you can just take it out of the list of files in ‘Book.txt’.

\n\n

\nSample Books

\n\n

\nWhy Sample Books?

\n\n

Leanpub lets you create a sample book, which readers can download for free to help them decide whether they want to buy the real book.

\n\n

To do this, you create or edit a file called Sample.txt in the ‘manuscript’ folder for your book. Note that, like Book.txt, the Sample.txt file is just a list of files. It’s supposed to be a smaller list than what is in Book.txt, or else you’re giving your whole book away! If you don’t want a sample book, just delete the Sample.txt file.

\n\n

\nConsequences for Manuscripts

\n\n

One consequence of this approach to specifying a sample book is that it’s an “all or nothing” decision to include a file. If you include a file in the list in Book.txt, all the chapters and sections in that file are inserted in your book. Because of this, we recommend a couple things:

\n\n

Either use a separate text file for each chapter, or
Never let a section span multiple text files.

\n\n

These two guidelines mean that your sample book is a lot less likely to have problems. If you don’t follow them, things can still work, but you can sometimes create a situation where your book will be created fine but your sample book will not.

\n\n

So, if you use the “separate text file for each chapter” approach, things will just work.

\n\n

\nImages

\n\n

\nHow To Insert An Image

\n\n

This section shows how you can insert images into your Leanpub book.

\n\n

First, you need to put the image in the ‘images’ folder in the ‘manuscript’ folder for your book.

\n\n

Second, type in a reference to the image like this:

\n\n

1 ![This is the Image Caption](images/LeanpubLogo1200x610_300ppi.png)\n

\n\n\n\n

Then you’ll see the image appear:

\n\n\n

That’s it! (See this web page for details on images in Markdown.)

\n\n

Note: Captions will only appear if an image is on a line all by itself.

\n\n

\nImage Format And Resolution

\n\n

We support PNG, JPEG and GIF formats for images.

\n\n

There are notes about the sizes of images at Author > Books > your book > Settings > Image Sizing Help.

\n\n

\nPositioning An Image On The Page

\n\n

You can ‘float’ your image on the page, aligning it to the right and left as your prefer. (You can also use {float=inside} or {float=outside} rather than {float=left} and {float=right} in your Markdown).

\n\n

For example, if you type this (using the name of your image and not the Leanpub logo, of course):

\n\n

1 {width=60%,float=left}\n2 ![This is the Image Floated Left](images/LeanpubLogo1200x610_300ppi.png)\n

\n\n\n\n

Then you willl see the image floated to the left, with text wrapping around it, like this:

\n\n

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

\n\n\n

\n\n

\n\n\n\n

Please note that it is not currently possible to set images side-by-side.

\n\n

\nLanguages and Letter Accents

\n\n

\nSetting the Main Language Used in the Book

\n\n

In the General Settings page in your book tools, you can set the main language used in the book.

\n\n

\n
When you create a book, to set the language, click on “Writing” in the menu on the left and then click on “General Settings”. There, you will see a dropdown where you can set the main language used in the book. Once you’ve selected a language, click the blue “Update Book” button at the bottom of the page.
\n

\n\n

By default, the main language is English.

\n\n

This helps us to set up the fonts that we use in your book. If you are writing with a mixture of languages that includes Chinese, Japanese or Korean, then you should check out the language switcher section (right below here). If you have troubles with characters not showing up properly, please let us know at hello@leanpub.com.

\n\n

\nOverriding Leanpub Language Defaults

\n\n

You can tell Leanpub what encoding a file is in via a snippet of text that you put at the top of the file:

\n\n

1 {:: encoding=\"utf-8\" /}\n

\n\n\n\n

This will let you over-ride our encoding guessing.

\n\n

\nSwitching back and forth between language fonts

\n\n

You can switch back and forth between language fonts by indicating the font in curly brackets.

\n\n

For example, you can switch to a Chinese font by typing {chinesefont} and back to latin characters again by typing {latinfont}.

\n\n

Here’s an example:

\n\n

Here is some Chinese text 办事去了 and here’s some English.

\n\n

Here is some Chinese text {chinesefont}办事去了{latinfont} and here's some English.\n

\n\n\n\n

There are also equivalent switches for Japanese {japanesefont}, Korean {koreanfont} and Thai {thaifont}.

\n\n

\nA note about writing Leanpub books in Japanese, Korean and Chinese

\n\n

If you are writing with a mixture of languages that includes Chinese, Japanese or Korean, then you should select Chinese, Japanese or Korean as the main language for your book.

\n\n

\nA note about writing Leanpub books in right-to-left (RTL) languages

\n\n

If you are writing in a right-to-left language such as Arabic or Hebrew, please use Markua. Our right-to-left language support is not perfect, but we will not be fixing any more bugs in Leanpub Flavoured Markdown mode with it. So, if you want to have any chance of being happy with Leanpub’s right-to-left language support, use Markua.

\n\n

\nParts, Chapters and Sections

\n\n

\nParts

\n\n

To start a new “Part” in your book, you start a line with -# followed by the title of the Part.

\n\n

1 -# Part 1\n

\n\n\n\n

\nChapters, Sections and Sub-sections

\n\n

Chapters are started by a single #. Sections with two ##, sub-sections with three ### all the way down to sub-sub-sub-sections #####.

\n\n

1 # Chapter 1\n2 \n3 ## Section 1.1\n4 \n5 ### Sub-section 1.1.1\n6 \n7 #### Sub-sub-section 1.1.1.1\n8 \n9 ##### Sub-sub-sub-section 1.1.1.1.1\n

\n\n\n\n

Please note that only lines of text with one or more number signs will show up in the Table of Contents (you can control what level of hierarchy you want to show up in your Table of Contents in the Settings section for your book).

\n\n

\nTable of Contents

\n\n

Leanpub automatically generates a Table of Contents for you. It will show Chapter headings in bold in a large font.

\n\n

\nFront Matter, Main Matter and Back Matter

\n\n

Authors often want their books to be composed of distinct front, main, and even back ‘parts’. For example, an Introduction will be numbered separately from the main chapters of the book. So an Introduction might be numbered (if you want numbering) 1, and then for Chapter One the numbering will start over at 1.

\n\n

To format sections as front matter (like an introduction), main matter (the chapters of your book) and back matter (an appendix, say), you just need to type the following at the point where you want the front matter, main matter or back matter section to begin:

\n\n

{frontmatter}

\n\n

{mainmatter}

\n\n

{backmatter}

\n\n

Each instruction should be on a line by itself, with blank lines above and below it. Unless the instruction is the first line in a .txt file, in which case you just need a blank line below it.

\n\n

We do generally recommend that each instruction for a part should have its own file, so things are clear in book.txt. That means you should have a separate file that contains only the e.g. backmatter instruction and is called “backmatter.txt”.

\n\n

\nIntroduction & Acknowledgments

\n\n

These sections are usually included at the front of the book as front matter. Files designated as front matter will be numbered as a separate set of files and their page numbers will be roman numerals (i.e. 5 is V). This means that when you start the next section, the numbering starts over.

\n\n

To designate that a section is front matter, at the beginning of the section, just type:

\n\n

{frontmatter}

\n\n

on a separate line, with blank lines above and below it.

\n\n

When you want the ‘mainmatter’ section to start, just type:

\n\n

{mainmatter}

\n\n

at the start of the main matter section (or at the end of the front matter section) on a separate line, with blank lines above and below it.

\n\n

One easy way to do this is to make a separate text file that just contains the syntax indicating the start of the section.

\n\n

So you could create a new text file, and just type:

\n\n

{frontmatter}

\n\n

and nothing else! If you save the file as frontmatter.txt in your Book.txt file, it might look like this:

\n\n

frontmatter.txt

\n\n

introduction.txt

\n\n

and Leanpub will know to format introduction.txt as front matter.

\n\n

Front matter has no section numbering, even if you have turned on section numbering for the rest of your book.

\n\n

Also, you only need to give each instruction once, and that instruction applies to everything that comes after, unless you type a new instruction. So if you type {frontmatter} in one file, everything after it will be frontmatter until you type {mainmatter}.

\n\n

\nAppendix, Appendices, Index

\n\n

These sections are usually included at the back of the book as back matter. Back matter has no section numbering, even if you have turned on section numbering for the rest of your book. However, page numbering continues unchanged.

\n\n

To designate that a section is back matter, at the beginning of the section, just type:

\n\n

{backmatter}

\n\n

on a separate line, with blank lines above and below it.

\n\n

\nFront Matter, Main Matter, and Back Matter Example

\n\n

 1 {frontmatter}\n 2 \n 3 # Preface\n 4 \n 5 This is the first front matter section.\n 6 \n 7 # Introduction\n 8 \n 9 This is the first front matter section.\n10 \n11 {mainmatter}\n12 \n13 # Chapter One\n14 \n15 This is the first main matter section\n16 \n17 # Chapter Two\n18 \n19 This is the second main matter section\n20 \n21 # Chapter Three\n22 \n23 This is the third main matter section.\n24 \n25 {backmatter}\n26 \n27 # Appendix One\n28 \n29 This is the first back matter section.\n30 \n31 # Appendix Two\n32 \n33 This is the second back matter section.\n

\n\n\n\n

\nStyling Text

\n\n

\nBold, Emphasis/Italics, and Underlining

\n\n

You can emphasise text by putting * or _ (one underscore) before and after the text.

\n\n

1 I am *emphatic*\n

\n\n\n\n

You can make bold text by putting ** or __ (two underscores) before and after the text.

\n\n

1 I am **bold**\n

\n\n\n\n

You can do bold-italic with *** or ___ (three underscores) before and after the text.

\n\n

1 I am ***bold-italic***\n

\n\n\n\n

You can underline text with ____ (four underscores) before and after the text.

\n\n

1 I am ____underlined____\n

\n\n\n\n

Please note that some ebook viewers don’t display underlining. For example, you can see underlines on Kindle for Mac and on the Kindle Paperwhite, but Adobe Digital Editions doesn’t display them. Older Kindles may fail to display underlines as well.

\n\n

\nSuperscripts

\n\n

Surround something in carets ^ to make it superscript. Like 1^st or 2^nd.

\n\n

1 1^st^ or 2^nd^\n

\n\n\n\n

\nMonospaced Text

\n\n

Use backticks to make text monospaced (it looks red here, but won’t in your book).

\n\n

1 I am `monospaced`!\n

\n\n\n\n

\nNon-Breaking Spaces

\n\n

You can add non-breaking spaces with  . This is useful for e.g. numbers that would be confusing if they were split onto more than one line. Here’s an example: 120 000 €

\n\n

1 120&nbsp;000&nbsp;€\n

\n\n\n\n

\nBlocks Of Text

\n\n

\nParagraphs

\n\n

Paragraphs are consecutive lines of text. You can separate paragraphs from each other by putting a blank line between them.

\n\n

You can also separate paragraphs, or blocks of text, by adding two spaces at the end of the paragraph. This is useful when you are going to follow a paragraph with another kind of text block, like a numbered list, or any of the other kinds listed in this section.

\n\n

1 Paragraphs are consecutive lines of text.\n2 \n3 You can separate paragraphs from each other by putting a blank line between them.\n4 \n5 You can also separate paragraphs, or blocks of text, by adding two spaces\n6 at the end of the paragraph. This is useful when you are going to follow\n7 a paragraph with another kind of text block, like a numbered list.\n

\n\n\n\n

\nCentering Paragraphs Or Lines Of Text

\n\n

You can center paragraphs or lines of text by putting C> (followed by a space) at the start of the line.

\n\n

Just type this in your .txt file:

\n\n

1 C> This is a centered sentence on its own.\n

\n\n\n\n

…and you’ll see this in your Leanpub book:

\n\n

This is a centered sentence on its own.

\n\n

You can also group together blocks of centered text. Just type something like this in your .txt file:

\n\n

1 C> This is a centered sentence.\n2 C> Another centered sentence, in the same paragraph as sentence one.\n3 C>\n4 C> This sentence will be in a new paragraph.\n

\n\n\n\n

…and you’ll see this in your Leanpub book:

\n\n

This is a centered sentence.\nAnother centered sentence, which will be in the same paragraph as sentence one.

\n\n

This sentence will be in a new paragraph.

\n\n

\nNumbered/Ordered Lists

\n\n

Numbered lists are easy to make.

\n\n

This is the first item in the numbered list.
Each number (plus a period) should be followed by a space.
Once you start a numbered list, it doesn’t matter what number you put at\nthe beginning of the line. This line starts with 1. as it is written, but\nappears in the ebook as 3.

\n\n

1 1. This is the first item in the numbered list.\n2 2. Each number (plus a period) should be followed by a space.\n3 1. Once you start a numbered list, it doesn't matter what number you put at the begi\\\n4 nning of the line. This line starts with 1. as it is written, but appears in the ebo\\\n5 ok as 3.\n

\n\n\n\n

\nUnordered/Bulleted Lists

\n\n

To make a list without numbers, where items are separated by bullets, you add an asterisk * followed by a space at the beginning of a line.

\n\n

This is the first item in a bulleted list.
This is the second item in a bulleted list.
You can also use hyphens - to indicate you are making a bulleted list

\n\n

1 * This is the first item in a bulleted list.\n2 * This is the second item in a bulleted list.\n3 - You can also use hyphens - to indicate you are making a bulleted list\n

\n\n\n\n

\nNested Lists

\n\n

If you want nested lists, then you indent by two spaces:

\n\n

one
two
three\n
- three.one
- three.two
\n

\n\n

1 * one\n2 * two\n3 * three\n4   * three.one\n5   * three.two\n

\n\n\n\n

\nPutting Code Blocks Inside Lists

\n\n

To put a code block in a list, do something like this:

\n\n

one\n

1   #!/usr/bin/env ruby\n2   puts \"hiya\"\n3   10.times {|n| puts n}\n

\n\n \n

two
three

\n\n

Some notes:

\n\n

The code is indented by 8 spaces, not the usual 4.
There must be a blank line before and after the code block
Tilde delimited code blocks do not work.

\n\n

1 * one\n2 \n3         #!/usr/bin/env ruby\n4         puts \"hiya\"\n5         10.times {|n| puts n}\n6 \n7 * two\n8 * three\n

\n\n\n\n

\nPutting Paragraphs Into Lists

\n\n

If you’d like to add a paragraph in the middle of a list, and have the list numbering continue afterwards, you can indent the paragraph by four spaces.

\n\n

This is the first one
The second\n
A whole lot more info about the above item.
\n
This is the third item
This is the 4th item

\n\n

1 1. This is the first one\n2 1. The second\n3 \n4     A whole lot more info about the above item.\n5 1. This is the third item\n6 1. This is the 4th item\n

\n\n\n\n

\nPutting Images Into Lists

\n\n

You can put images in lists, like this:

\n\n

One thing.
Second thing.\n\n
\n
\n $\"Leanpub$ \n
Leanpub Logo
\n
\n
\n\n
Third thing.
Fourth thing.

\n\n

1 1. One thing\n2 2. Second thing.\n3 \n4    ![Leanpub Logo](images/LeanpubLogo1200x610_300ppi.png)\n5 \n6 3. Third thing\n7 4. Fourth thing.\n

\n\n\n\n

\nDefinition Lists

\n\n

Put the thing you want to define on a line by itself. On the next line, or after a blank line, type a colon followed by the definition. For a more detailed example that explains how to nest definitions and have multiple paragraphs in definitions, see http://kramdown.gettalong.org/syntax.html#definition-lists.

\n\n

Ruby: A wonderful language.
JavaScript: Lovely little language that really shines when you add CoffeeScript to\nthe mix. This is a longer entry to see what it looks like when it wraps to\na second line.
Haskell: Messes with my head.

\n\n

 1 Ruby\n 2 \n 3 : A wonderful language.\n 4 \n 5 JavaScript\n 6 \n 7 : Lovely little language that really shines when you add CoffeeScript to\n 8 the mix. This is a longer entry to see what it looks like when it wraps to\n 9 a second line.\n10 \n11 Haskell\n12 : Messes with my head.\n

\n\n\n\n

\nPutting Footnotes Into Definition Lists

\n\n

You can include a footnote text in a list by putting two spaces before the line where you define the footnote. Here’s an example:

\n\n

item1: some explanation without a footnote
item2: some explanation¹.\n\n
item3: more

\n\n

 1 item1\n 2 : some explanation without a footnote\n 3 \n 4 item2\n 5 : some explanation[^foot].\n 6 \n 7   [^foot]:note\n 8 \n 9 item3\n10 : more\n

\n\n\n\n

\nBlockquotes

\n\n

\n
This is a blockquote
\n\n
A blockquote should be indented.
\n\n
The second paragraph should be indented as well.
\n\n
And the third!
\n\n
\n
You can also have blockquotes inside blockquotes
\n
\n

\n\n

1 > **This is a blockquote**\n2 >\n3 > A blockquote should be indented.\n4 >\n5 > The second paragraph should be indented as well.\n6 >\n7 > And the third!\n8 >\n9 > > You can also have blockquotes in blockquotes\n

\n\n\n\n

\nNesting Lists In Blockquotes

\n\n

You can put lists in blockquotes. To do this, just add two spaces before each list item, and don’t type a > sign:

\n\n

\n
This is a blockquote
\n\n
\n
This is a list item.
\n
This is another list item.
\n
This is a third list item.
\n
\n\n
Now this is regular text in the same blockquote.
\n

\n\n

1 > **This is a blockquote**\n2 >\n3 >  1. This is a list item.\n4 >  2. This is another list item.\n5 >  3. This is a third list item.\n6 >\n7 > Now this is regular text in the same blockquote.\n

\n\n\n\n

\nAsides/Sidebars

\n\n

The code for the aside is:

\n\n

1 A> This is an aside.\n2 A>\n3 A> This is also sometimes known as a sidebar.\n4 A>\n5 A> To make one of these, put `A>` at the beginning of the lines of\n6 A> the aside, similar to the `>` that you use for a blockquote.\n

\n\n\n\n

This is what the aside will look like:

\n\n\n\n

If you want to title an Aside, you do it like this:

\n\n

1 A> ## Your title goes here.\n2 A>\n3 A> This is also sometimes known as a sidebar.\n

\n\n\n\n

This is what the aside with a title will look like:

\n\n\n\n

If you want to cross-link to your aside, you can name your aside like this:

\n\n

1 A> ## Your Aside title {#your-aside-title}\n2 A>\n3 A> This is also sometimes known as a sidebar.\n

\n\n\n\n\n\n

Please note that headers ## that are inside of quotes, asides, etc. are not included in section numbering.

\n\n

\nMore Text Block Types

\n\n

In addition to asides, there are warnings (W>), tips (T>), errors (E>), information (I>), questions (Q>), discussions (D>) and exercises (X>). There are also generic text blocks (G>) where you can pick an icon from a large selection. There’s more info below on how to do that.

\n\n

Please note that these types of text blocks are meant to be short. While asides (defined with A>) carry over multiple pages, warnings and such do not.

\n\n

Below you’ll find examples of each block type.

\n\n

\nWarning!

\n\n

Here’s the code for a Warning:

\n\n

1 W> ## This is a Warning\n2 W>\n3 W> Warnings are generated by using `W>` at the beginning of lines.\n

\n\n\n\n

And here’s what it looks like:

\n\n\n\n

\nTips

\n\n

Here’s the code for a Tip:

\n\n

1 T> ## This is a Tip\n2 T>\n3 T> To make a tip, put `T>` at the beginning of the lines of\n4 T> the tip, similar to the `>` that you use for a blockquote.\n5 T>\n6 T> To make paragraphs in a tip, you need to put lines\n7 T> with just `T>` between your paragraphs.\n

\n\n\n\n

And here’s what it looks like:

\n\n\n\n

\nErrors

\n\n

Here’s the code for an Error:

\n\n

1 E> ## This is an Error\n2 E>\n3 E> Describe a common Error here.\n

\n\n\n\n

And here’s what it looks like:

\n\n\n\n

\nInformation

\n\n

Here’s the code for an Information box:

\n\n

1 I> ## This is an Information box\n2 I>\n3 I> Put some special information here.\n

\n\n\n\n

And here’s what it looks like:

\n\n\n\n

\nQuestions

\n\n

Here’s the code for a Question box:

\n\n

1 Q> ## This is a Question box\n2 Q>\n3 Q> Ask & answer a common question here.\n

\n\n\n\n

And here’s what it looks like:

\n\n\n\n

\nDiscussions

\n\n

Here’s the code for a Discussion box:

\n\n

1 D> ## This is a Discussion box\n2 D>\n3 D> You can discuss aspects of the main text in a Discussion box.\n

\n\n\n\n

And here’s what it looks like:

\n\n\n\n

\nExercises

\n\n

Here’s the code for an Exercise:

\n\n

1 X> ## This is an Exercise\n2 X>\n3 X> Exercises are generated by using `X>` at the beginning of lines.\n

\n\n\n\n

And here’s what it looks like:

\n\n\n\n

\nGeneric Boxes

\n\n

If you want a different icon, you can take a look at the icons available from Font Awesome. Find one you like on that page, and then note the text beside it. For example, the first one has the text fa-automobile. Leaving out the fa-, we do the following to use an automobile icon:

\n\n

1 {icon=automobile}\n2 G> ## Vrooom!\n3 G>\n4 G> The freedom of the road!\n

\n\n\n\n

\nCode

\n\n

Lots of Leanpub authors write about computer programming. Here are some instructions and tips for using code in your Leanpub book.

\n\n

\nCode Samples

\n\n

If you are writing a programming or technical book you may want to add code blocks.

\n\n

There are three ways to insert code blocks into a Leanpub book.

\n\n

First, you can just type in the code directly. To indicate that you are writing a code block, indent each new line of code with 4 spaces.

\n\n

1 This is the first line of code.\n2 This is the second line of code.\n3 And this is the third line of code!\n

\n\n\n\n

1     This is the first line of code.\n2     This is the second line of code.\n3     And this is the third line of code!\n

\n\n\n\n

Second, you can also make code blocks by adding a set of 8 tildes above and below the code block.

\n\n

(Actually, we support any number of tildes for code blocks as long as the number of tildes before and after the code-block is the same, but we recommend using 8 as best practice).

\n\n

Third, when you’re writing you can refer to external code samples in a ‘code’ folder in the ‘manuscript’ folder for your book.

\n\n

1 Here is a code sample:\n2 \n3 <<(code/sample1.rb)\n

\n\n\n\n

You can also put titles on your code samples:

\n\n

1 <<[This Code Sample Has A Title](code/sample2.rb)\n

\n\n\n\n

Actually there’s one more way to format lines of code. For short chunks, less than a line in length, you can put the code between back-ticks `.

\n\n

Here is some code between back-ticks

\n\n

1 `Here is some code between back-ticks`\n

\n\n\n\n

\nOverriding The Default Syntax System

\n\n

Leanpub attempts to guess the language for syntax highlighting. However, sometimes you will want to specify the language yourself, for example if Leanpub guesses wrong.

\n\n

When things don’t work, you can force the language by doing this:

\n\n

1 {lang=\"js\"}\n2     Error: Something terrible has happened!\n

\n\n\n\n

We use Pygments for our syntax highlighting. You can see the list of languages supported here: http://pygments.org/languages. It includes Java, bash, JSON and HTML.

\n\n

If you have a code block for which you want no syntax highlighting, you can use lang=\"text\".

\n\n

1 {lang=\"text\"}\n2     Error: Something terrible has happened!\n

\n\n\n\n

\nVim Syntax Fix for Code Markup

\n\n

Here’s how to make sure your code snippets will work with the official Markdown syntax provided by the Vim text editor.

\n\n

Just create a markdown.vim file in your .vim/after/syntax dir and add the following lines:

\n\n

1 syn match markdownLeanCode '^<<(.*)$'\n2 \n3 hi def link markdownLeanCode   markdownH1\n

\n\n\n\n

\nLine Numbers in Code Samples

\n\n

On the Book Theme tab for your book there is a setting called “Show line numbers on code samples” that sets whether or not we show line numbers on your code samples.

\n\n

You can also turn line-numbers on or off for an individual code-sample by setting the linenos attribute to either on or off. This will force line-numbers to be on:

\n\n

1 {linenos=on}\n2     def hello\n3       puts \"Hello, world\"\n4     end\n

\n\n\n\n

While this will force line-numbering to be off:

\n\n

1 {linenos=off}\n2     def hello\n3       puts \"Hello, world\"\n4     end\n

\n\n\n\n

\nSetting First Line Number

\n\n

Sometimes you may want to begin a code sample with number that shows it is a continuation of a previous code sample. You use the starting-line-number attribute to do this. Like so:

\n\n

1 {line-numbers=on,starting-line-number=32}\n

\n\n\n\n

…. though of course you can choose whatever number you like.

\n\n

Here’s an example of how this looks, followed by the text as it is written in Markdown:

\n\n

32 module Leanpub\n33   module Generate\n34 \n35     class Leanpub::Generate::BinaryLatexGenerator\n36 \n37       attr_reader :start_chapter, :end_chapter\n38       attr_accessor :results\n39 \n40       ...\n41 \n42     end\n43   end\n44 end\n

\n\n\n\n

 1 {line-numbers=on,starting-line-number=32}\n 2 ~~~~~~~~\n 3 module Leanpub\n 4   module Generate\n 5 \n 6     class Leanpub::Generate::BinaryLatexGenerator\n 7 \n 8       attr_reader :start_chapter, :end_chapter\n 9       attr_accessor :results\n10 \n11       ...\n12 \n13     end\n14   end\n15 end\n16 ~~~~~~~~\n

\n\n\n\n

\nDisplaying only part of a code file

\n\n

You can use the crop-start-line and crop-end-line attributes to set the start and end line of a code sample to display. This is useful if you have a large file and you only want to display parts of it. For example, if you have a large file called books_controller.rb and only wanted to show lines 15–30 of it, you would do this:

\n\n

1 {crop-start-line=15,crop-end-line=30}\n2 <<[BooksController](code/books_controller.rb)\n

\n\n\n\n

\nCode Samples In Asides

\n\n

This will work if you put the A> before every line in the code sample. Note that you’ll have a few less characters to work with due to the indentation in the aside.

\n\n

Like this:

\n\n

 1 A> ^[r1184]^ This behaviour makes it hard to execute VCL code from the\n 2 `OnStop` so revision 1184 introduced another variation of `OnStop` that\n 3 accepts a delegate with an `IOmniTask` parameter.\n 4 A>\n 5 A> {lang=\"pascal\"}\n 6 A> ~~~~~~~~~~~~~~~\n 7 A>   TOmniTaskStopDelegate = reference to procedure (const task: IOmniTask);\n 8 A>\n 9 A>   IOmniParallelLoop = interface\n10 A>     ...\n11 A>     function  OnStop(stopCode: TOmniTaskStopDelegate):\n12 IOmniParallelLoop; overload;\n13 A>   end;\n14 A> ~~~~~~~~~~~~~~~\n15 A>\n16 A>^[r1184]^ Using this version of `OnStop`, the termination handler can use\n17 `task.Invoke` to execute some code in the main thread. This, however,\n18 requires the `ForEach` abstraction to stay alive until the `Invoke`-d code\n19 is executed so you must store the `ForEach` result\n

\n\n\n\n

^[r1184] This behaviour makes it hard to execute VCL code from the\nOnStop so revision 1184 introduced another variation of OnStop that\naccepts a delegate with an IOmniTask parameter.

\n\n

1   TOmniTaskStopDelegate = reference to procedure (const task: IOmniTask);\n2 \n3   IOmniParallelLoop = interface\n4     ...\n5     function  OnStop(stopCode: TOmniTaskStopDelegate):\n6 IOmniParallelLoop; overload;\n7   end;\n

\n\n \n\n

^[r1184] Using this version of OnStop, the termination handler can use\ntask.Invoke to execute some code in the main thread. This, however,\nrequires the ForEach abstraction to stay alive until the Invoke-d code\nis executed so you must store the ForEach result

\n\n

\nCode Sample Titles

\n\n

A code block without a title looks like this:

\n\n

1 class Book\n2 \n3   def initialize(title, subtitle)\n4     @title = title\n5     @subtitle = subtitle\n6   end\n7 \n8 end\n

\n\n\n\n

You can give a codeblock a title using the title attribute. Adding a title styles it a bit differently. Here is an example of what it looks like, followed by the actual text written in Markdown that produces the title and code block:

\n\n

Example 12: Creating a class in Ruby

1 class Book\n2 \n3   def initialize(title, subtitle)\n4     @title = title\n5     @subtitle = subtitle\n6   end\n7 \n8 end\n

\n\n\n\n

 1 {title=\"Example 12: Creating a class in Ruby\", lang=ruby}\n 2 ~~~~~~~\n 3 class Book\n 4 \n 5   def initialize(title, subtitle)\n 6     @title = title\n 7     @subtitle = subtitle\n 8   end\n 9 \n10 end\n11 ~~~~~~~\n

\n\n\n\n

You can specify multiple attributes (like the title and the language for syntax highlighting) like this:

\n\n

{title=\"Some Title\", lang=coffeescript}\n

\n\n\n\n

Here’s an example:

\n\n

Example 13: Creating a class in CoffeeScript

1 class Book\n2   constructor: (@title, @subtitle) ->\n3     # Other initialization code goes here\n

\n\n\n\n

Here’s the text in Markdown that produced the code sample above:

\n\n

1 {title=\"Example 13: Creating a class in CoffeeScript\", lang=coffeescript}\n2 ~~~~~~~\n3 class Book\n4   constructor: (@title, @subtitle) ->\n5     # Other initialization code goes here\n6 ~~~~~~~\n

\n\n\n\n

\nMarking lines as deleted or added to a code block

\n\n

If you are building up an example while writing your book, you will probably want to emphasise lines of code that have been added to your book and strike-out lines of code that have been removed. This is done by adding comment lines to your code. The special words that can be used are leanpub-start-delete, leanpub-end-delete, leanpub-start-insert and leanpub-end-insert. Note that any line containing these strings will be removed completely from your code before being inserted in the book. This should allow you to use any comment syntax you require.

\n\n

Also, please note that if you use leanpub-start-delete or leanpub-end-delete in a code sample that you are showing in a book, then it will turn off any syntax highlighting; otherwise the bolded text gets hidden by syntax highlighting.

\n\n

For example, the following code has leanpub-start-delete before def old_stuff and leanpub-end-delete after it, and leanpub-start-insert before def new_stuff and leanpub-end-insert after it. (It’s hard to put this inline as we strip it out, so I’ll just have to describe it).

\n\n

 1 def nochange\n 2   \"No change here\"\n 3 end\n 4 \n 5 def old_stuff\n 6   \"Old\"\n 7 end\n 8 \n 9 def new_stuff\n10   \"New\"\n11 end\n12 \n13 def unmoving\n14   \"No change here either\"\n15 end\n

\n\n\n\n

\nPoetry

\n\n

You can write poetry in Leanpub books. Here are a couple of tips:

\n\n

\nPoetry Stanzas in Regular Markdown

\n\n

To make stanzas, you have to put two blank spaces at the end of each line (i.e. press the space bar twice). Then you can get poems to look like this:

\n\n

In Xanadu did Kubla Khan\nA stately pleasure dome decree:\nWhere Alph, the sacred river, ran\nThrough caverns measureless to man\nDown to a sunless sea.

\n\n

\nSpacing Control for Poetry

\n\n

For more powerful spacing control, for example to put letters wherever you like in the line, we have made a special block of text for poetry. This is necessary in order to produce poetry in a reasonably uniform way in many different e-formats with one click.

\n\n

To make a block of poetry, you need to indicate where you are starting and stopping the block of poetry. Your readers will not see the instructions to start and stop the block of poetry; they will only see the poetry. Here is an example of what you need to do:

\n\n

1 {style=poem}\n2 ~~~~~~\n3 In Xanadu did Kubla Khan\n4    A stately pleasure-dome decree:\n5       Where Alph, the sacred river, ran\n6          Through caverns measureless to man\n7             Down to a sunless sea.\n8 ~~~~~~\n

\n\n\n\n

If you type the above example into your text file, and then generate a Preview, in the ebook you will see this:

\n\n

In Xanadu did Kubla Khan\n   A stately pleasure-dome decree:\n      Where Alph, the sacred river, ran\n         Through caverns measureless to man\n            Down to a sunless sea.\n\n

\n\n

Please note the poem needs to have a line of six tildes ~ above and below it. This indicates that it’s a special block of text. And don’t forget to type {style=poem} where the poem starts, to indicate that the following block of text is a poem. Don’t worry, the tildes and {style=poem} won’t be visible in the book!

\n\n

If you write using our special poem block of text, you don’t have to worry about putting the two spaces at the end of your lines.

\n\n

\nLine Lengths

\n\n

If a line of poetry is too long to fit in the margins, you will have to manually edit the line. You can also try changing the size of the book page, in the “Book Theme” tab under “Writing” in the book tools menu.

\n\n

One last thing: you can actually copy and paste poetry from Microsoft Word in between the tilde lines, and the spacing of your words will be retained.

\n\n

\nLinks

\n\n

\nFormatting Links

\n\n

We support Markdown syntax for links, as well as normal HTML links. Here’s an example of a link to Leanpub:

\n\n

Leanpub

\n\n

1 [Leanpub](http://leanpub.com)\n

\n\n\n\n

You can also create links like this:

\n\n

http://leanpub.com

\n\n

1 <http://leanpub.com>\n

\n\n\n\n

Please note that we do not support reference-style links. Our opinion is that while they are a great idea for shorter texts like blog posts, they are generally a bad idea for longer texts, like books. This will be explained explicitly when we implement Markua (the successor to Leanpub-flavored Markdown).

\n\n

\nLong Hyperlinks

\n\n

If you have particularly long hyperlinks in your text, you may prefer to make the long link show up only in the footnote in the PDF.

\n\n

To do this, first you should make sure you have ticked ‘Show links as footnotes in PDFs’ on the “Book Theme” tab under “Writing” in your book tools menu (and then scrolled to the bottom of the page and clicked ‘Update Book’ to save the change).

\n\n

Then you can format the link with a custom name, so only that name shows up in the body of your text, and the link shows up in the footnote.

\n\n

For example, instead of doing this:

\n\n

https://groups.google.com/group/leanpub/browse_thread/thread/9dd1391e6d9899c9

\n\n

1 [https://groups.google.com/group/leanpub/browse_thread/thread/9dd1391e6d9899c9](http\\\n2 s://groups.google.com/group/leanpub/browse_thread/thread/9dd1391e6d9899c9)\n

\n\n\n\n

You can do this:

\n\n

add a link name here

\n\n

1 [add a link name here](https://groups.google.com/group/leanpub/browse_thread/thread/\\\n2 9dd1391e6d9899c9)\n

\n\n\n\n

The part inside of the square brackets becomes a clickable link followed by a footnote number. The part in parentheses becomes a footnote, which is also clickable.

\n\n

\nFootnotes and Hyperlinks in PDF

\n\n

If you select “Book Theme” under “Writing” in your book tools menu, you will see a section called “Links”. The options here allow you to choose whether links are rendered only as links in the body of your text, or to also show them as footnotes or html-style-links in PDFs. The latter option only affects normal links (links where the displayed link text in the body of your book is different than the URL).

\n\n

\nFootnotes and Endnotes

\n\n

\nFootnotes

\n\n

To add a footnote, you insert a footnote tag like this².

\n\n

Then you add the footnote content later in the text, using the same tag, with a colon and a space:

\n\n

That’s it. You can keep writing your text after the footnote content.

\n\n

To add a footnote, you insert a footnote tag like this[^foo].\n\nThen you add the footnote content later in the text, using the same tag, with a colo\\\nn and a space:\n\n[^foo]: This is the footnote content.\n\nThat's it.  You can keep writing your text after the footnote content.\n

\n\n\n\n

Please note it is best to put the lines with footnote content at the end of the text file (this helps avoid problems when you are e.g. using code blocks in your book).

\n\n

In response to author feedback, we’d like to be very explicit about a few things:

\n\n

There needs to be a blank line before and after the footnote content.
The ^ caret symbol is required.
Each footnote will need its own unique tag. So the first one might be [^foo1], the second [^foo2], etc.
The tag doesn’t have to have foo in it. It can be anything, like [^note1] or [^tag1].
At the moment, we don’t support periods in footnote tags, like this [^55.3].

\n\n

Footnotes will format themselves correctly over multiple lines. However, if you want to continue the footnote on a second line using a line break of your own choice, you indent the second line (and any following lines) by 4 spaces.

\n\n

Like this:³

\n\n

[^foo2]: This is the footnote text. We are now going to add a second line\n    after typing in four spaces.\n

\n\n\n\n

\nEndnotes

\n\n

We don’t have specific support for endnotes, but you can achieve this with crosslinks.

\n\n

\nRemove Footnotes

\n\n

If you want to remove footnotes for a specific section, and not for your entire book, you can put the following on a line by itself (with blank lines above and below it):

\n\n

{footnotes-off}\n

\n\n\n\n

To turn them back on, do this:

\n\n

{footnotes-on}\n

\n\n\n\n

\nCrosslinks

\n\n

Crosslinks link one part of your book to another part of your book.

\n\n

There are two steps to making a crosslink:

\n\n

Give the thing you want to crosslink to an ID.
Create a crosslink to that ID.

\n\n

\nQuick Explanation

\n\n

Crosslinks are just like other links in Markdown, except that instead of linking to a web page, you link to an ID name you’ve created.

\n\n

So, if you want to link the words ‘a previous chapter’ to a chapter heading in your book, you would type something like:

\n\n

As we discussed in [a previous chapter](#chapter-32)...\n

\n\n\n\n

… if you have already assigned an ID name to the chapter heading, like this:

\n\n

# Chapter 32 {#chapter-32}\n

\n\n\n\n

\nA Quick Note About Crosslinks

\n\n

The ID can be on the same line as a chapter or section header, like this:

\n\n

# Chapter 32 {#chapter-32}\n

\n\n\n\n

But it can’t be on a line of text. So, for example, this won’t work:

\n\n

{#SirHDavyResults} Sir H. Davy, a British chemist\n

\n\n\n\n

To make it work, the ID should be above the text, with no blank line between the ID and the text, like this:

\n\n

{#SirHDavyResults}\nSir H. Davy, a British chemist\n

\n\n\n\n

In order to crosslink to an image, you will need to use the following syntax:

\n\n

{id=\"cat-picture\"}\n![A picture of a cat](images/cat.jpg)\n

\n\n\n\n

Then crosslink to it like this:

\n\n

Remember that [picture of a cat](#cat-picture)?\n

\n\n\n\n

It’s important not to have any blank lines between the id and the image, and the image needs to be by itself on the line.

\n\n

The exact same thing works for a code-block, you just need to add an id:

\n\n

{id='something-amazing',line-numbers=off,lang=ruby}\n~~~~~~\ndef something\n  puts \"something, something, something\"\nend\n~~~~~~\n

\n\n\n\n

\nLonger Explanation

\n\n

To link from one word (or set of words) to another, you first need to identify the word (or words) you want to link to. To do that, you need to give the word you want to link to an ID name. The ID name will not be visible to the reader.

\n\n

You can create an ID name by adding some text enclosed in { and }, plus a number sign #, like this:

\n\n

{#IDname}

\n\n

You can call the ID anything you like, which is why we just wrote ‘IDname’ in this example.

\n\n

So, for example, if you want to link to the start of a chapter, you can add an ID to the line at the start of the chapter, like this:

\n\n

# Chapter 32 {#chapter-32}\n

\n\n\n\n

\nCrosslinking to something with an ID

\n\n

Now that the item you are crosslinking to has an ID, you can link to it from anywhere in your text.

\n\n

To do that, surround the word or words you want to turn into a link with [ and ], and then follow that with a section in ( and ) which includes the ID name you made up.

\n\n

To complete the example, here’s what you would type if you wanted the words ‘a previous chapter’ to become a link to the ID {#chapter-32}:

\n\n

As we discussed in [a previous chapter](#chapter-32)...\n

\n\n\n\n

\nSome Crosslink Details

\n\n

Here we give an ID of shopping-list to a list.

\n\n

{#shopping-list}\n* Bananas\n* Cream\n* Pie Crust\n

\n\n\n\n

Make sure not to put the ID within an element, like a list or a code block, however. The ID should come before or after the element. So you can do this:

\n\n

{#anchor}\n- `test`\n\n    abc\n

\n\n\n\n

but not this:

\n\n

- `test`\n{#anchor}\n\n    abc\n

\n\n\n\n

Here are some further technical details:

\n\n

This Markdown:

\n\n

{#anchor}\n- `test`\n\n    abc\n

\n\n\n\n

Produces this HTML (and similar LaTeX):

\n\n

<ul id=\"anchor\">\n  <li><code>test</code>\n    <p>abc</p>\n  </li>\n</ul>\n

\n\n\n\n

\nBreaks

\n\n

Here’s how you can create line breaks and page breaks on Leanpub.

\n\n

\nPagebreaks

\n\n

You can force a page break by adding {pagebreak} on a line by itself, with blank lines before and after. For example:

\n\n

1 And the winner is....\n2 \n3 {pagebreak}\n4 \n5 Ta-dah!\n

\n\n\n\n

\nLine Breaks

\n\n

In Markdown, in order to indicate a line break, you type two spaces after a line and press return.

\n\n

Also, in your book Settings you can select the option: “No indent, small vertical space between paragraphs”.

\n\n

\nTables

\n\n

To make a table, you use vertical bars (|) to separate the columns of your tables. Here are a few examples.

\n\n

This results in a very simple table with two columns of ingredients:

\n\n

1 | 2 cups old fashioned oats          | 1 1/2 tsp vanilla              |\n2 | 1 cup sunflower seeds              | 1/4 tsp salt                   |\n3 | 1 cup shredded coconut             | 1/2 cup chopped pitted dates   |\n4 | 1/2 cup toasted wheat germ or bran | 1/2 cup chopped dried apricots |\n5 | 3 tbsp unsalted butter             | 1/2 cup dried cranberries      |\n6 | 2/3 cup honey                      |                                |\n7 | 1/4 cup packed brown sugar         |                                |\n

\n\n\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n

2 cups old fashioned oats	1 1/2 tsp vanilla
1 cup sunflower seeds	1/4 tsp salt
1 cup shredded coconut	1/2 cup chopped pitted dates
1/2 cup toasted wheat germ or bran	1/2 cup chopped dried apricots
3 tbsp unsalted butter	1/2 cup dried cranberries
2/3 cup honey
1/4 cup packed brown sugar

\n\n

If you want the first line to be formatted as a heading, then do something like this:

\n\n

1 |Verb   |Action                                          |Idempotent?|\n2 |-------|------------------------------------------------|-----------|\n3 |GET    |Responds with information about the resource    |Yes        |\n4 |POST   |Creates a sub-resource of the resource POSTed to|No         |\n5 |PUT    |Creates or updates the resource being PUT to    |Yes        |\n6 |DELETE |DELETES the resource                            |Yes        |\n7 |HEAD   |Gets metadata about the resource                |Yes        |\n

\n\n\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n

Verb	Action	Idempotent?
GET	Responds with information about the resource	Yes
POST	Creates a sub-resource of the resource POSTed to	No
PUT	Creates or updates the resource being PUT to	Yes
DELETE	DELETES the resource	Yes
HEAD	Gets metadata about the resource	Yes

\n\n

\nTable Width

\n\n

Your book has a default table-width setting. By default, it’s set to “default”, which stretches tables to 80% of the page width.

\n\n

The other two settings are “narrow” and “wide”. Narrow makes the table as narrow as possible, wide makes it take up the full page width.

\n\n

You can set the default table-width on the “Book Theme” tab under “Writing” in your book tools menu.

\n\n

The major drawback to narrow is that we do no automatic word-wrapping in PDFs, so the table may go off the side of the page. We recommend using default or wide mode.

\n\n

You can also over-ride the width of individual tables by setting a width attribute. For example, if your book had a default table width of “wide”, the table below would be narrow:

\n\n

1 {width=\"narrow\"}\n2 | one | two | three |\n3 |-------------------|\n4 | a   | b   | c     |\n5 |-------------------|\n6 | d   | e   | f     |\n

\n\n\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n

one	two	three
a	b	c
d	e	f

\n\n

Here it is with {width=\"default\"}:

\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n

one	two	three
a	b	c
d	e	f

\n\n

You can use “wide”, “default” or “narrow”, or a percentage for the width parameter. The following table would take up exactly half the page-width

\n\n

1 {width=\"50%\"}\n2 | one | two | three |\n3 |-------------------|\n4 | a   | b   | c     |\n5 |-------------------|\n6 | d   | e   | f     |\n

\n\n\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n

one	two	three
a	b	c
d	e	f

\n\n

\nMulti-line rows

\n\n\n\n

Here is that table from above reformatted to be narrower by using multi-line rows. The first dashed line makes the line before it a heading. The rest of the dashed lines just result in a larger vertical gap than a plain newline.

\n\n

 1 |Verb   | Action                                   |  Idempotent?   |\n 2 |-------|------------------------------------------|----------------|\n 3 |GET    | Responds with information about the      |  Yes           |\n 4 |       | resource                                 |                |\n 5 |-------|------------------------------------------|----------------|\n 6 |POST   | Creates a sub-resource of the resource   |  No            |\n 7 |       | being POSTed to                          |                |\n 8 |-------|------------------------------------------|----------------|\n 9 |PUT    | Creates or updates the resource being    |  Yes           |\n10 |       | PUT to                                   |                |\n11 |-------|------------------------------------------|----------------|\n12 |DELETE | DELETES the resource                     |  Yes           |\n13 |-------|------------------------------------------|----------------|\n14 |HEAD   | Gets metadata about the resource         |  Yes           |\n

\n\n\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n

Verb	Action	Idempotent?
GET	Responds with information about the	Yes
	resource
POST	Creates a sub-resource of the resource	No
	being POSTed to
PUT	Creates or updates the resource being	Yes
	PUT to
DELETE	DELETES the resource	Yes
HEAD	Gets metadata about the resource	Yes

\n\n

IF you want to put line breaks in table cells, you can do the following:

\n\n

 1 |Verb          | Action                                 |\n 2 |--------------|----------------------------------------|\n 3 |Multiline     | You can have multiple-lines in a       |\n 4 |              | table, and line-breaks are respected.  |\n 5 |              |                                        |\n 6 |              | This is a second paragraph             |\n 7 |-------------------------------------------------------|\n 8 |continued!    | You create new table cells with a      |\n 9 |              | line of dashes surrounded by pipes     |\n10 |              |                                        |\n11 |              | (Pipes are the vertical lines, \"\\|\")    |\n

\n\n\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n

Verb	Action
Multiline	You can have multiple-lines in a
	table, and line-breaks are respected.

	This is a second paragraph
continued!	You create new table cells with a
	line of dashes surrounded by pipes

	(Pipes are the vertical lines, “\|”)

\n\n\n\n

You can also do fancy things with alignment and footer rows. Here is an example.

\n\n

1 | Default aligned |Left aligned| Center aligned  | Right aligned  |\n2 |-----------------|:-----------|:---------------:|---------------:|\n3 | First body part |Second cell | Third cell      | fourth cell    |\n4 | Second line     |2nd line    | **strong**      |                |\n5 |-----------------|------------|-----------------|----------------|\n6 | Second body     |            |                 |                |\n7 | 2 line          |            |                 |                |\n8 |=================|============|=================|================|\n9 | Footer          | footer2    | footer3         | footer4        |\n

\n\n\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n

Default aligned	Left aligned	Center aligned	Right aligned
First body part	Second cell	Third cell	fourth cell
Second line	2nd line	strong
Second body
2 line
Footer	footer2	footer3	footer4

\n\n

\nTable Titles

\n\n

You add a title to a table by adding a title attribute to the table, like this:

\n\n

{title=\"Figure 32\"}\n| City          | Annual Rainfall (inches) |\n|------------------------------------------|\n| Rome          | 23                       |\n| London        | 29                       |\n

\n\n\n\n

Here’s what that looks like:

\n\n\n \n \n \n \n \n\n

\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n

Figure 32
City	Annual Rainfall (inches)
Rome	23
London	29

\n\n

If you want to set both the title and the width, it looks like this:

\n\n

{title=\"Figure 32\",width=\"60%\"}\n| City          | Annual Rainfall (inches) |\n|------------------------------------------|\n| Rome          | 23                       |\n| London        | 29                       |\n

\n\n\n\n

\nHTML Tables

\n\n

If you try putting an HTML table in a .txt file, you’ll find that it works in the epub and mobi version but is missing in the PDF. Here’s why:

\n\n

Markdown normally just generates HTML. So it could “support” using HTML tables and any other HTML construct by just not parsing the HTML. But we need to actually parse the Markdown (we use a slightly modified Kramdown parser), in order to generate LaTeX and then PDF.

\n\n

\nA note on combining attributes

\n\n

To combine attributes for a table, add a comma and a space between the attributes, like this:

\n\n

{title=\"table title\", width=\"wide\"}

\n\n

\nMiscellaneous

\n\n

\nEscaping Markdown Syntax Characters

\n\n

Sometimes you’ll want to use a character or set of characters that is a part of the Markdown syntax. To make the character show up in your text, instead of acting as a Markdown formatting marker, just put the backslash \\ character in front of it.

\n\n

For example, if you just type “# Header” at the beginning of a line, it will appear as a header, and you won’t see the number sign “#”.

\n\n

If you want “# Header” to show up at the beginning of a line, type “\\# Header”, and you’ll see the number sign:

\n\n

# Header

\n\n

\\# Header\n

\n\n\n\n

\nHow To Exclude Lines From Your Book

\n\n

If you have some lines in your .txt files that you’re working on, but don’t want to appear in your book, you can hide or ‘comment out’ the lines by adding two ‘%’ characters:

\n\n\n

1 %% You won't see this text!\n

\n\n\n\n

Please note the ‘comment out’ line must be preceded by a blank line.

\n\n

Any line that meets these requirements will not show up in the published PDF, EPUB or MOBI files.

\n\n

To ‘comment out’ like this in Book.txt, type a # at the beginning of a line.

\n\n

\nMathematical Equations

\n\n

You can put mathematical equations in your book.

\n\n

You use LaTeX math syntax, surrounded by {$$} and {/$$}. You can do both inline and block math. Here is a full example:

\n\n

\nEquations

\n\n

You create a block equation by putting it by itself:

\n\n\n$$\n\\left|\\sum_{i=1}^n a_ib_i\\right|\n\\le\n\\left(\\sum_{i=1}^n a_i^2\\right)^{1/2}\n\\left(\\sum_{i=1}^n b_i^2\\right)^{1/2}\n$$\n\n

1 {$$}\n2 \\left|\\sum_{i=1}^n a_ib_i\\right|\n3 \\le\n4 \\left(\\sum_{i=1}^n a_i^2\\right)^{1/2}\n5 \\left(\\sum_{i=1}^n b_i^2\\right)^{1/2}\n6 {/$$}\n

\n\n\n\n

Inline equations are written inline. For example:

\n\n

The four kinematics equations are \$d = v_i t + \\frac{1}{2} a t^2\$,\n\$v_f^2 = v_i^2 + 2 a d\$, \$v_f = v_i + a t\$ and \$d = \\frac{1}{2}(v_i + v_f) t\$.

\n\n

1 The four kinematics equations are {$$}d = v_i t + \\frac{1}{2} a t^2{/$$},\n2 {$$}v_f^2 = v_i^2 + 2 a d{/$$}, {$$}v_f = v_i + a t{/$$} and {$$}d =\n3 \\frac{1}{2}(v_i + v_f) t{/$$}.\n

\n\n\n\n

Please note that if you are going to include a percent sign % in an equation, you need to “escape” it with a backslash, like this:

\n\n

1 {$$} value  = (1 x 4) \\% 5  = 4 \\% 5 = 4{/$$}\n

\n\n\n\n

\nCurly Quotes

\n\n

Ideally you should just have “straight” ‘quotes’ in the Markdown. We auto-produce curly quotes for you. We change curly quotes into straight quotes and then make them curly again.

\n\n

\nFigure Captions and Labels

\n\n

In technical books, is common to have figures with a label and a corresponding reference in the text.

\n\n

Here’s how you can do something like this in Leanpub:

\n\n

1 # Chapter 1\n2 See [figure 32](#figure-32) for an example.\n3 # Chapter 2\n4 {#figure-32}\n5 ![Figure 32](images/figure32.jpg)\n

\n\n\n\n

What we don’t do (yet) is provide auto-numbering of figures and captions.

\n\n

\nLinks In Footnotes

\n\n

Currently, a link mentioned within a footnote doesn’t generate a new footnote (in the PDF), and doesn’t have a clickable URL either. We’ll implement a solution to this soon.

\n\n

\nWhy can’t I put section commands in Book.txt?

\n\n

After a lot of thought and experimenting, we’ve decided to make Book.txt just a list of files. That means you can’t put section commands in the Book.txt file, like

\n\n

1 {frontmatter}\n2 Introduction.txt\n3 {mainmatter}\n4 Chapter1.txt\n5 {backmatter}\n6 Appendix1.txt\n

\n\n\n\n

Instead, we recommend you make a separate .txt file for each section command, and then refer to it in Book.txt. So e.g. you’d make a frontmatter.txt file that only has this content:

\n\n

1 {frontmatter}\n

\n\n\n\n

… and do the same for mainmatter and backmatter. Then, your Book.txt file will look like this:

\n\n

1 frontmatter.txt\n2 Introduction.txt\n3 mainmatter.txt\n4 Chapter1.txt\n5 backmatter.txt\n6 Appendix1.txt\n

\n\n\n\n

… and you can still see your book’s structure in Book.txt.

\n\n

This is an easier thing to explain and understand than if we’d turned Book.txt into a DSL. We had started down that approach many years ago, and it was confusing.

\n\n

Now, since Book.txt is just a list of files, you could in theory write an entire book in one file. We don’t recommend this, since if you did that, you couldn’t give away a subset as Sample.txt, since it’s also just a list of files. Also, splitting your book up into different .txt files actually makes it easier to find and edit content, and to reorganize or delete sections. So we still recommend one file per chapter, both for clarity and for ease of creating book samples.

\n\n

\nTrouble With Accents? Forcing Text Editors To Save As UTF-8

\n\n

Normally, to get things like letter accents to work if you’re having troubles, you can force the encoding by putting this at the top of your text file:

\n\n

{:: encoding=\"UTF-8\" /}

\n\n

However, you may still have problems if the text editor you’re using is not set to save to UTF-8. Normally you can change this setting by doing ‘Save As’, and finding the ‘Encoding’ option.

\n\n

\nI don’t understand how things get added to a Table of Contents

\n\n

By default, all headers are added to the Table of Contents. A header looks like this:

\n\n

# Chapter One

\n\n

… where you put the number sign # at the beginning of the line, and follow the number sign with the text you want for the header.

\n\n

Also by default, all ‘Part’ titles are added to the Table of Content. You create a Part by typing -# like this:

\n\n

# Part One

\n\n

You can choose to have the Table of Contents include sections as well. To do this, go to your book’s Settings page and select the “Book Theme” tab under “Writing” in your book tools menu, and then scroll down to the Table of Contents section. There, you can select ‘Parts, Chapters and Sections’ or ‘Everything’.

\n\n

Then, sections will also appear in the Table of Contents. A section is subordinate to a heading, so you type two or more number signs, like this:

\n\n

## This is a section subordinate to a heading.\n### This is a section subordinate to ## sections\n#### This is a section subordinate to ### sections

\n\n

\nWhat encoding should I use to write files in Markdown? Should I write in ASCII or UTF-8?

\n\n

We translate everything to UTF-8 internally, so if you start with UTF-8 everything will work smoothly.

\n\n

\nHow Can I Add Blank Lines To My Text?

\n\n

While there is no official way to add a larger space between paragraphs, adding a blank table (two vertical pipes separated by a space, like this | |) works. For example:

\n\n

This is a line.

\n\n

This is a second line. It has a larger space after it.

\n\n\n \n \n \n \n \n\n

\n\n

This is a third line.

\n\n

This is a fourth line.

\n\n

1 This is a line.\n2 \n3 This is a second line. It has a larger space after it.\n4 \n5 |  |\n6 \n7 This is a third line.\n8 \n9 This is a fourth line.\n

\n\n\n\n

\nAdding a motto or epigraph to the beginning of a chapter

\n\n

There is no special feature for adding a motto or epigraph to the beginning of a chapter, but one nice way to do this is to use text centering.

\n\n

So, if you type this:

\n\n

1 C> *It was the best of times, it was the worst of times*\n2 C>\n3 C> -- Charles Dickens\n4 \n5 It was a dark and stormy night...\n6 \n7 Suddenly, a shot rang out!\n

\n\n\n\n

You’ll see this:

\n\n

It was the best of times, it was the worst of times

\n\n

– Charles Dickens

\n\n

It was a dark and stormy night…

\n\n

Suddenly, a shot rang out!

\n\n

\nDisabling Line Numbers While Nesting Code Blocks In Lists

\n\n

For the indentation method:

\n\n

There must be a blank line between the list item and the code.
The {line-numbers=off} line should be indented by four characters.
The code should be indented by 3 more characters than the {line-numbers=off} line.

\n\n

* with no line numbers:\n\n  {line-numbers=off}\n      def foo\n        \"foo\"\n      end\n\n* with line-numbers on:\n\n      def foo\n        \"foo\"\n      end\n

\n\n\n\n

For the tildes method

\n\n

There must be a blank line between the list item and the first line of the code block
The tildes and the code should be indented to match the indentation of the list.

\n\n

* with no line numbers:\n\n  {line-numbers=off}\n

\n\n\n

def foo\n “foo”\n end\n

\n\n

with line-numbers on:\n
\n
```
1 def foo\n2   \"foo\"\n3 end\n
```
\n\n
\n
\n

\n\n

\nIndentation

\n\n

If you are looking to indent some text you can use the Unicode character ‘figure space’ (U+2007) to add as many spaces as you need. You can add this character to your clipboard by selecting the blank space between the following quotes and copying it.

\n\n

“ ”

\n\n

\nHanging Indents

\n\n

Scholarly works sometimes need bibliographical entries to be formatted with hanging indents. So, we’ve added this to Leanpub.

\n\n

To use it, you use the directives {begin-hanging-paragraphs} to start using hanging paragraphs, and {end-hanging-paragraphs} to end it. These should be on lines by themselves, with blank lines above and below them. Here’s a quick example, showing first what you would type in your text file, and second how this would look when published:

\n\n

 1 This is a normal paragraph.\n 2 \n 3 \n 4 {begin-hanging-paragraphs}\n 5 \n 6 Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec hendrerit tempor tel\\\n 7 lus. Donec pretium posuere tellus.\n 8 \n 9 Aliquam erat volutpat. Nunc eleifend leo vitae magna.\n10 \n11 Pellentesque dapibus suscipit ligula. Donec posuere augue in quam. Etiam vel tortor \\\n12 sodales tellus ultricies commodo. Suspendisse potenti. Aenean in sem ac leo mollis b\\\n13 landit. Donec neque quam, dignissim in, mollis nec, sagittis eu, wisi. Phasellus lac\\\n14 us.\n15 \n16 Pellentesque dapibus suscipit ligula. Donec posuere augue in quam. Etiam vel tortor \\\n17 sodales tellus ultricies commodo. Suspendisse potenti. Aenean in sem ac leo mollis b\\\n18 landit. Donec neque quam, dignissim in, mollis nec, sagittis eu, wisi. Phasellus lac\\\n19 us.\n20 \n21 {end-hanging-paragraphs}\n22 \n23 This is a normal paragraph again.\n

\n\n\n\n

This is a normal paragraph.

\n\n

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec hendrerit tempor tellus. Donec pretium posuere tellus.

\n\n

Aliquam erat volutpat. Nunc eleifend leo vitae magna.

\n\n

Pellentesque dapibus suscipit ligula. Donec posuere augue in quam. Etiam vel tortor sodales tellus ultricies commodo. Suspendisse potenti. Aenean in sem ac leo mollis blandit. Donec neque quam, dignissim in, mollis nec, sagittis eu, wisi. Phasellus lacus.

\n\n

This is a normal paragraph again.

\n\n

\nLong strings of characters running off the right-hand side of the page / the right margin

\n\n

Sometimes very long strings of characters will run off the right-hand side of the page, without a line-break happening automatically. Unfortunately there’s not much we can do to fix this. Usually, we see it with long Java class names. The only fix that we know of is to manually insert a line-break before the problematic code-span by putting two-spaces followed by a carriage return right before it. Sorry we don’t have a better answer!

\nNotes

1note↩

\n\n

2This is the footnote content.↩

\n\n

3This is the footnote text. We are now going to add a second line\nafter typing in four spaces.↩

\n\n\n

\n\n

\n\n","tocStructure",[441,442,443,444,445,446,447,448,449,450,451,452,453,454,455,456,457,458,459,460,461,462,463,464,465,466,467,468,469,470,471,472,473,474,475,476,477,478,479,480,481,482,483,484,485,486,487,488,489,490,491,492,493,494,495,496,497,498,499,500,501,502,503,504,505,506,507,508,509,510,511,512,513,514,515,516,517,518,519,520,521,522,523,524,525,526,527,528,529,530,531,532,533,534,535,536,537,538,539,540,541,542],{"_74":75,"_42":76,"_69":-5,"_77":78,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":84,"_69":-5,"_77":85,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":90,"_69":-5,"_77":91,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":93,"_69":-5,"_77":94,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":96,"_69":-5,"_77":97,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":100,"_69":-5,"_77":101,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":103,"_69":-5,"_77":104,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":106,"_69":-5,"_77":107,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":109,"_69":-5,"_77":110,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":112,"_69":-5,"_77":113,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":116,"_69":-5,"_77":117,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":120,"_69":-5,"_77":121,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":124,"_69":-5,"_77":125,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":127,"_69":-5,"_77":128,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":131,"_69":-5,"_77":132,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":134,"_69":-5,"_77":135,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":137,"_69":-5,"_77":138,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":141,"_69":-5,"_77":142,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":144,"_69":-5,"_77":145,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":147,"_69":-5,"_77":148,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":150,"_69":-5,"_77":151,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":154,"_69":-5,"_77":155,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":157,"_69":-5,"_77":158,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":160,"_69":-5,"_77":161,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":163,"_69":-5,"_77":164,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":166,"_69":-5,"_77":167,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":169,"_69":-5,"_77":170,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":173,"_69":-5,"_77":174,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":176,"_69":-5,"_77":177,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":179,"_69":-5,"_77":180,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":182,"_69":-5,"_77":183,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":185,"_69":-5,"_77":186,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":189,"_69":-5,"_77":190,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":192,"_69":-5,"_77":193,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":195,"_69":-5,"_77":196,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":198,"_69":-5,"_77":199,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":201,"_69":-5,"_77":202,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":205,"_69":-5,"_77":206,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":208,"_69":-5,"_77":209,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":211,"_69":-5,"_77":212,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":214,"_69":-5,"_77":215,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":217,"_69":-5,"_77":218,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":220,"_69":-5,"_77":221,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":223,"_69":-5,"_77":224,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":226,"_69":-5,"_77":227,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":229,"_69":-5,"_77":230,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":232,"_69":-5,"_77":233,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":235,"_69":-5,"_77":236,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":238,"_69":-5,"_77":239,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":241,"_69":-5,"_77":242,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":244,"_69":-5,"_77":245,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":247,"_69":-5,"_77":248,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":250,"_69":-5,"_77":251,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":253,"_69":-5,"_77":254,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":257,"_69":-5,"_77":258,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":260,"_69":-5,"_77":261,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":263,"_69":-5,"_77":264,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":266,"_69":-5,"_77":267,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":270,"_69":-5,"_77":271,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":273,"_69":-5,"_77":274,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":276,"_69":-5,"_77":277,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":279,"_69":-5,"_77":280,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":283,"_69":-5,"_77":284,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":286,"_69":-5,"_77":287,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":289,"_69":-5,"_77":290,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":292,"_69":-5,"_77":293,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":296,"_69":-5,"_77":297,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":299,"_69":-5,"_77":300,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":302,"_69":-5,"_77":303,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":305,"_69":-5,"_77":306,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":309,"_69":-5,"_77":310,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":312,"_69":-5,"_77":313,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":315,"_69":-5,"_77":316,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":318,"_69":-5,"_77":319,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":321,"_69":-5,"_77":322,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":325,"_69":-5,"_77":326,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":328,"_69":-5,"_77":329,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":331,"_69":-5,"_77":332,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":335,"_69":-5,"_77":336,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":338,"_69":-5,"_77":339,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":341,"_69":-5,"_77":342,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":344,"_69":-5,"_77":345,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":347,"_69":-5,"_77":348,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":350,"_69":-5,"_77":351,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":353,"_69":-5,"_77":354,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":357,"_69":-5,"_77":358,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":360,"_69":-5,"_77":361,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":363,"_69":-5,"_77":364,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":366,"_69":-5,"_77":367,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":369,"_69":-5,"_77":370,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":372,"_69":-5,"_77":373,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":375,"_69":-5,"_77":376,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":378,"_69":-5,"_77":379,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":381,"_69":-5,"_77":382,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":384,"_69":-5,"_77":385,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":387,"_69":-5,"_77":388,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":390,"_69":-5,"_77":391,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":393,"_69":-5,"_77":394,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":396,"_69":-5,"_77":397,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":399,"_69":-5,"_77":400,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":83,"_42":402,"_69":-5,"_77":403,"_70":79,"_86":-5,"_87":-5,"_88":-5},{"_74":75,"_42":405,"_69":-5,"_77":406,"_70":79,"_86":-5,"_87":-5,"_88":-5},"publicChapterContent","nextChapter","sections",[],"routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]