Differences

This shows you the differences between two versions of the page.

--- publishing:digital:ebook [2021/03/20 20:56] – [Publishing your ebook] maarten
+++ publishing:digital:ebook [2024/02/14 12:20] (current) – external edit 127.0.0.1
@@ Line 18: / Line 18: @@
   - Set the correct metadata in the content.opf file. It is a good idea to have a look at a few Wellred or external examples. Important: set either a unique ISBN or, as we have started doing, simply use a (free) UUID on https://www.uuidgenerator.net/ to get a unique identifier for the ebook. Make sure the UUID is the same in content.opf and the legacy file toc.ncx
   - Check the end result in Adobe Digital Editions and make further edits as required
-  - Validate your epub file at http://validator.idpf.org/ (or this site) and fix any errors it generates. Your book will be rejected from most commercial platforms if you have any errors here.
+  - Validate your epub file at http://validator.idpf.org/ (or [[https://www.ebookit.com/tools/bp/Bo/eBookIt/epub-validator|this site]]) and fix any errors it generates. Your book will be rejected from most commercial platforms if you have any errors here.
   - At this point it is useful to close Sigil and to open Calibre editor for some final tweaking (strictly speaking not necessary, but good practice)
   - In Calibre editor set the semantics: ''Tools -> Set semantics''
@@ Line 34: / Line 34: @@
   - Under export options, select epub 3.0, unless you want to stick with 2.0. Change Navigation TOC to Multi Level (TOC style). Under HTML & CSS it can be useful to add a style sheet at this point (at the bottom ''Add style sheet…''), e.g. the Wellred template.css file. Make sure to ''Include classes in HTML'' to keep the formatting, but you can untick ''Generate CSS''
   - Once you have an InDesign generated Epub file, you can continue from step 4) under Method 1. It is also possible to start from step 3) if you prefer to work from another template, though that is more time-consuming and generally using good templates from the start saves a lot of time.
-  - For Wellred, this export from InDesign to final ebook is now almost fully automated by making use of a list of “saved searches” (available upon request), which you can organise in Sigil. By using a series of “find and replace” regular expressions, developed over the years, you can clean up most of the unnecessary/dirty HTML code generated by InDesign in a matter of minutes. (See the [[:regex|separate section on Regular expressions / scripts]]. There is also a way to use Python scripts within Sigil, as a plugin, to further speed up/optimise everything, although the saved searches seem to work well enough.)
+  - For Wellred, this export from InDesign to final ebook is now almost fully automated by making use of a list of “saved searches” ((Available in this document: {{ ::publishing:digital:sigil_searches.odt |}}Save as a plain text .ini file and then import it under ''Tools -> Saved searches'', then first run the 'normal' set as a normal search and subsequently the 'regex' set as a regular expression)), which you can organise in Sigil. By using a series of “find and replace” regular expressions, developed over the years, you can clean up most of the unnecessary/dirty HTML code generated by InDesign in a matter of minutes. (See the [[:regex|separate section on Regular expressions / scripts]]. There is also a way to use Python scripts within Sigil, as a plugin, to further speed up/optimise everything, although the saved searches seem to work well enough.)
 ===== Publishing your ebook =====