First of all, I wanted to thank you (again!) for such a great software.
I’ve been using Scrivener for years for my screenplays and it’s changed my life.
I’ve just finished formatting a new non-fiction book for print and ebook publishing. My designer has handled the print formatting, and I decided to do the ebook formatting myself. It’s incredibly easy and powerful to be able to generate the ebook file directly from Scrivener, so I’m very happy with this feature.
Apart from some issues with illustrations (now solved), I have a couple of requests as these are the only outstanding points that prevent me from getting the result I’d like:
Please find a way to support basic formatting in titles. I mention movie titles in my titles in my non-fiction book and they have to be in Italics (just the title, not the whole line), both in the table of contents and in the manuscript itself. For print formatting, I can go through the MS Word exported file and add the italics by hand, it’s not great but it’s doable. However, I can’t do this with the kindle version. I totally understand why this isn’t supported, because with styles you can get any formatting for the whole title, but it would be great to have the flexibility to format parts of the title as well.
Please find a way to support “keep with next” in the kindle export. I’m assuming here that Kindle supports this, but if it does it would be great if the “keep with next” attributes in Scrivener were applied to the Kindle file (and other ebook formats if possible). At the moment, they are not taken into account, so you end up with orphans/widows in places you don’t want to.
Finally, I found a way to get rid of the page numbers in the contents by using replacements (my Kindle format preset replaces <$p> with nothing in the preset replacements) but as they can’t be used in the Kindle, it would be great if they were stripped automatically (that one isn’t for myself as I have found the solution).
That’s about it, once again, thanks for a fantastic tool and keep up the good work!
All the best,
Just realised I posted this in the wrong forum, I guess it should be in the Wish List forum. Sorry about that.
Any chance a mod could move it? Thanks!
Thanks for the feedback! Glad to hear Scrivener has been of help to you over the years.
On these two points:
- There may be a suitable solution available to you in the future. I can’t make any promises on that, but we have discussed some options in the past. By the way, e-books are editable documents, you just need an editor for them as most software cannot even read the format let alone edit it. Sigil and Calibre are good choices. You’ll need to start with ePub out of Scrivener, edit the ePub, then convert it to Mobi using Kindle Previewer (or the kindlegen command-line utility itself if you’re comfortable with that). Finally, for Mobi itself there is a checkbox in the KindleGen compile option pane for exporting the source files (mostly simple HTML and CSS with a few other files you can ignore unless you want to mess with the structure of the book) used to create the e-book. That puts you in direct control of the output. When you’re done, open the OPF file in Kindle Previewer to turn the folder into a .mobi.
- As far as I know there is no method that works for Kindle.
P.S. I have moved your topic to the wish list as requested; no worries!
Thanks for the reply, very helpful as always. It would be GREAT if there was an internal solution for #1, and I’ll explore your external suggestions as soon as I find the time.
It’s a shame for Kindle that there is no solution for #2, but at least that can’t be blamed on me if everyone suffers from it, so that makes me feel slightly better. It’s such a basic feature, it’s incredible they don’t support this.
Thanks again and keep up the good work!
Just to say that I did generate the source file using the Kindlegen option and was able to add the italics to all my titles. It’s time consuming as I have to find the right file for each title (I have more than twenty to edit in about 60 source files), but it works, so thanks a lot for the tip, it’s a good workaround until you implement internal support (if it happens, I’m aware you made no promise).
Glad that’s working out for you then. By the way that NCX file is plain old XML, and can serve as a “cheat sheet” for finding the files you need to edit. You’ll find the title of the section (as it will appear in the ToC, as this file is the ToC) followed by a element containing the name of the HTML file associated with that section.
Thanks, I had seen that, but finding the file isn’t too difficult, it’s adding all the HTML flags everywhere in the many subtitles in each file that takes time.
Nothing too bad as long as there are not too many revisions that require a recompile.
I used to work as a software developer in another life, so it’s not too hard to adapt, just inconvenient .
Thanks again for all your help!
Hello Scrivener Team,
I just wanted to know if there had been any progress on the title formatting? Editing the sources files works but it’s very time consuming to make corrections in the source files as well so you don’t have to re-compile and have to re-do all the titles formatting.
Thanks for an update!
Yes, at this point I can confirm that there will be a way to use simple markings in your titles to indicate italic or bold spans within them (in fact I just tested it with an internal build). This will be included as part of a major upgrade, as yet to be officially announced.
This is fantastic news, thanks a lot for the update
Just wondering if you had a rough ETA for when the upgrade including this Kindle titles formatting feature will be available?
Just to know if we’re talking days, weeks or months…
We’re not talking anything yet, it’s not even official. We’ll have more news once we’re closer to the final stages.
Thanks Amber, sounds like I can safely rule out days or weeks
This is a very safe assumption. 8)
I was wondering if were getting any nearer to a release of this magical build…
Just about to have to reformat the titles, so hoping help might be in sight…
Just to know if this formatting feature is present in the Scrivener version released on the Apple Store today?
If yes, how do we use it?
No, I was referring to a much larger upgrade event than a minor point increment which fixes a few bugs and compatibility issues with 10.12. Change logs are found here.
Any chance to get a rough ETA for the availability of the build that is going to implement this feature?
Am I correct to assume/hope that these features will be supported in the upcoming V3.0? Thanks!