I am trying to convert a novel into an eBook for the Kindle. All goes well, except that the prefix for files level 2+ is being applied to folders level 1 in the TOC (not in the text, there the titles are correct).
My douments level 2+ are set up to use a prefix of “(<$n:section>)”. This gives me numbered sections in the book. The chapters (with a section break before, so shoing up in the TOC) have a normal text, such as “London, 15 September”.
Now, this example chapter pops up in the TOC, assuming it is the first chapter, as “(1London, 15 September”. Interestingly enough, the closing “)” is missing. I tried with different settings, and always the last character of the prefix is not used, the suffix – if set – is also used. This looks a bit like a wrong refernce in the code? Some wrong pointer?
Still, neither prefix nor suffix for level2 should pop up in level 1 folders. Or am I missing a setting here? Would not exclude that possibility, but then appreciate help in finding that setting. Thanks lot!!
…an addition: if I set the prefix and suffix for Level 1+, eg. to only a space, then the TOC is formatted correctly. Except of course, I got all those superfluous spaces in the book. Seems Scrivener coughs a bit if the prefix setting is blank??
will send a test project in a moment. The real one is a bit big to email, but I just created one from the novel template, put in two dummy sections, and applied my compile settings. Same thing happens. When you export to PDF etc. there is no problem, because Scrivener does not create a TOC. (Or does it? Coudn’t find it.)
I’ll send you the project, the compile settings (were in the Applications Support folder) and a translated mobi-file. If you go to the TOC you will see the “(1Chapter” entry.
Hope you’ll find a fix!
Cheers,
Hendrik
BTW, in trying out different settings I also found that “Keith Blout” and “ePubTest” are hard-coded into the “Page Settings”.
And one more, totally different topic: in eBook export, it would be nice if Scrivener would support fixed-width font/font-family Courier. According to Amazon’s readmes, Kindle does support it and I’ve seen fixed-width font used in books. Would at least give a meagre way to separate some parts from the normal text.
And one more, totally different topic: in eBook export, it would be nice if Scrivener would support fixed-width font/font-family Courier. According to Amazon’s readmes, Kindle does support it and I’ve seen fixed-width font used in books. Would at least give a meagre way to separate some parts from the normal text.
[/quote]
I’ll see about this, but can’t promise anything because of the way I have to modify the standard Apple HTML exporters at the moment.
Thanks for sending the files - I’ve received them and will test them tomorrow. I’ll get back to you then with what I find.
super support!! The version you sent fixed the problem! Perfect!
Now I’m just wondering what your secret is! Write a great masterpiece of software and deliver good support and have a latte on the side?? You must have figured out how to make days a few hours longer! Care to share how to do this??
Glad that worked! The secret is that it is all the perfect procrastination technique: “I really ought to write something for The-Novel-I’ve-Been-Planning-For-Years; but wait, here’s something urgent that needs doing instead!” Bug-fixing is my perfect software equivalent of doing the dishes.
Thanks again for reporting the bug and providing the project to help me fix this; I have the thing about fonts on my list for investigation.
