Book, Part, Chapter

[p3aul]

I use a txt file and convert that to epub. When I have a book title and chapter symbols I use # for the title, ##chapter using markdown everything works fine.

The problem occurs when I have a book broken down into parts and further broken down into chapters. I have tried using # for the title ## for the parts and ### for the chapters but it doesn't work. Calibre just doesn't seem to recognize the triple #'s. Can anyone help me?
TIA,
Paul

[kovidgoyal]

That's strange. Can you attach a test case.

[p3aul]

Ok I have shortened the file to a couple of parts and the chapters to two or three.

I am using the latest version of Calibre .6.45. I am using the program itself to convert, selecting Markdown in Text input. As you can see, the parts are in the TOC because of ## but the chapters are missing. I used ### in front of the chapter headings

[kovidgoyal]

If you want page breaks before the ### elements you have to change the

insert page breaks before setting to

//*[name()='h1' or name()='h2' or name()='h3']

[p3aul]

I just want the chapter names to show in the TOC. As it is only part names(the ones with##) are showing in the TOC I thought the hash marks would indicate to the parser that a ###Chapter is to be placed in the TOC below the Part name or number that begins with ##. That doesn't seem to be the case here.

[p3aul]

I was able to get the chapters but not the parts listed in the TOC in a RTF file by using //h3 in the preferences.

Well I guess this problem is so far down in the list it will never get solved sigh......

[kovidgoyal]

What happens is the following:

# gets turned into h1

## gets turned into h2

### gets turned into h3

By default calibre creates a TOC base donly on h1 and h2

If you want to create one based on h3 as well, you have to explicitly tell it so, via the level 1/2/3 TOC options, as I outlined above

[p3aul]

f you want to create one based on h3 as well, you have to explicitly tell it so, via the level 1/2/3 TOC options, as I outlined above

I did that Kovid, just as you said. In RTF I could get the h3 rendered as a chapter not in TXT though. This is what I had in mind:

Title rendered by h1 or #

Part one as h2 or ##

Chapter one as h3 or ###

Chapter Two as h3 or ###

Chapter Three as h3 or ###

Part Two as h2 or ##

Chapter One as h3 or ###

Chapter Two as h3 or ###

And so forth.


It may be that Calbre simply can't do this or that it was not written to do this. This is the way the TOC would appear in a paper book.

It also may be that it can be done with css?

Thanks,

Paul

[DoctorOhh]

Let me preface this by saying I have never attempted this before.

Originally Posted by kovidgoyal

//*[name()='h1' or name()='h2' or name()='h3']

I took your Test Case text file, followed Kovid's suggestion as quoted above. To avoid confusion I attached an image of the settings I used.

Originally Posted by p3aul

This is what I had in mind:

Title rendered by h1 or #

Part one as h2 or ##

Chapter one as h3 or ###

Chapter Two as h3 or ###

Chapter Three as h3 or ###

Part Two as h2 or ##

Chapter One as h3 or ###

Chapter Two as h3 or ###

This seemed to create the TOC structure you want. It shows the h2 and h3 items. I might be missing something, check out the attached image of the TOC.

I also attached the ePub it created. Isn't this what you asked for?

[p3aul]

Yes that's exactly what I wanted. Why can't it work for me? Here is the setting I used, as cut and pasted into this post.

(1) This under "Detect Structure: Detect Chapters at(xpath expression)

//*[((name()='h1' or name()='h2' or name()='h3') and re:test(., 'chapter|book|section|part\s+', 'i')) or @class = 'chapter']

All I did was add "or name()='h3' to the default line.

(2) In "Table of Contents" I just added //h3

(3) in Text Input I checked "Use Markdown"

Isn't this the same as you and Kovid said was what to do?

[DoctorOhh]

Originally Posted by p3aul

Yes that's exactly what I wanted. Why can't it work for me? Here is the setting I used, as cut and pasted into this post.

(1) This under "Detect Structure: Detect Chapters at(xpath expression)

//*[((name()='h1' or name()='h2' or name()='h3') and re:test(., 'chapter|book|section|part\s+', 'i')) or @class = 'chapter']

All I did was add "or name()='h3' to the default line.

He didn't say to add something to the default. He gave you a new string. That is why I included an image so you could see what I used.

Originally Posted by p3aul

(2) In "Table of Contents" I just added //h3

I didn't put anything in the "Table of Contents" area. I left it blank. Kovid said to do one thing, so that's what I did.

I thought I saw you say you didn't want pagebreaks so I did change that to none (see previous image).

Originally Posted by p3aul

(3) in Text Input I checked "Use Markdown"

I selected this too.

Originally Posted by p3aul

Isn't this the same as you and Kovid said was what to do?

No, but I hope you understand now.

I'm glad this solution does what you want.

[p3aul]

hi! thanks for answering so quickly and thanks for taking the trouble to troubleshoot my code. You know, when I was composing that last post, I looked back and saw that Kovid just had an abbreviated line of code and I wondered, but just thought he didn't want to put the whole thing there. I guess all that chapter stuff can't be there if you want the TOC to be hierarchical in form. I havn't tried it yet but I'm sure the solution is what you said. It sure makes sense.
Thanks,
Paul