Thread: ebook Workflow
View Single Post
Old 06-21-2012, 04:19 AM   #13
SBT
Evangelist
SBT ought to be getting tired of karma fortunes by now.SBT ought to be getting tired of karma fortunes by now.SBT ought to be getting tired of karma fortunes by now.SBT ought to be getting tired of karma fortunes by now.SBT ought to be getting tired of karma fortunes by now.SBT ought to be getting tired of karma fortunes by now.SBT ought to be getting tired of karma fortunes by now.SBT ought to be getting tired of karma fortunes by now.SBT ought to be getting tired of karma fortunes by now.SBT ought to be getting tired of karma fortunes by now.SBT ought to be getting tired of karma fortunes by now.
 
SBT's Avatar
 
Posts: 437
Karma: 560981
Join Date: Sep 2010
Location: Norway
Device: prs-t1, phone/Cool Reader, tablet/BlueFire, Nook Simple
uieluck: How much of your workflow is automated with scripts? The more standard the operations, the easier to automate. E.g. stripping of extraneous stuff, do you do that manually?

Personally, I've found it easier to stick the formatting I want into a plain text file, rather than strip out all the cruft word processors stuff in.
- If you've wondered about what a word processor does with your words, think about what a food processor does with your food.

My own workflow is roughly as follows:
  1. Proofread OCR txt
  2. Add homebrew markup for headings, footnotes, images etc.
  3. Add any special-case html code
  4. run text through the following pipeline of scripts:
    • footnote code insertion
    • image code insertion
    • convert to xhtml
    • split xhtml file into chapter files
    • generate opf file
    • generate ncx file
    • zip
    • validate
  5. repeat relevant steps
Post-editing:
  • edit opf meta-info
  • sometimes edit opf spine
  • sometimes edit ncx, renumbering done by script
  • edit image size properties in css file
SBT is offline   Reply With Quote