MobileRead Forums - View Single Post

rosewood · 01-25-2023, 06:56 PM

Thank you BetterRed. I used an online txt to markdown converter (https://products.aspose.app/words/conversion/txt-to-md) to convert a couple of paragraphs of text into markdown and found the output indistinguishable from the input.

I then read the section on headers in the Markdown syntax link

https://daringfireball.net/projects/markdown/syntax

I found the above link in the link which you referred me to:

https://manual.calibre-ebook.com/con...-specific-tips

I have copy/pasted this header section (in bold italics) below:

Headers

Markdown supports two styles of headers, Setext and atx.

Setext-style headers are “underlined” using equal signs (for first-level headers) and dashes (for second-level headers). For example:

This is an H1
=============

This is an H2
-------------

Any number of underlining =’s or -’s will work.

Atx-style headers use 1-6 hash characters at the start of the line, corresponding to header levels 1-6. For example:

# This is an H1

## This is an H2

###### This is an H6

Optionally, you may “close” atx-style headers. This is purely cosmetic — you can use this if you think it looks better. The closing hashes don’t even need to match the number of hashes used to open the header. (The number of opening hashes determines the header level.) :

# This is an H1 #

## This is an H2 ##

### This is an H3 ######

So, would I be right in saying that if the Chapter name string in my text file is preceded with ##, the Calibre Preprocessor would add this name to its table of contents, or would I have to change the file name from filename.txt to filename.md for the Preprocessor to include the (## Chapter Name string) into the ToC?

01-25-2023, 06:56 PM	#8
rosewood Member Posts: 14 Karma: 10 Join Date: Jan 2023 Device: fire hd 10	Thank you BetterRed. I used an online txt to markdown converter (https://products.aspose.app/words/conversion/txt-to-md) to convert a couple of paragraphs of text into markdown and found the output indistinguishable from the input. I then read the section on headers in the Markdown syntax link https://daringfireball.net/projects/markdown/syntax I found the above link in the link which you referred me to: https://manual.calibre-ebook.com/con...-specific-tips I have copy/pasted this header section (in bold italics) below: Headers Markdown supports two styles of headers, Setext and atx. Setext-style headers are “underlined” using equal signs (for first-level headers) and dashes (for second-level headers). For example: This is an H1 ============= This is an H2 ------------- Any number of underlining =’s or -’s will work. Atx-style headers use 1-6 hash characters at the start of the line, corresponding to header levels 1-6. For example: # This is an H1 ## This is an H2 ###### This is an H6 Optionally, you may “close” atx-style headers. This is purely cosmetic — you can use this if you think it looks better. The closing hashes don’t even need to match the number of hashes used to open the header. (The number of opening hashes determines the header level.) : # This is an H1 # ## This is an H2 ## ### This is an H3 ###### So, would I be right in saying that if the Chapter name string in my text file is preceded with ##, the Calibre Preprocessor would add this name to its table of contents, or would I have to change the file name from filename.txt to filename.md for the Preprocessor to include the (## Chapter Name string) into the ToC? Last edited by rosewood; 01-25-2023 at 06:59 PM.