View Single Post
Old 05-19-2009, 07:17 AM   #14
rogue_ronin
Banned
rogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-books
 
Posts: 475
Karma: 796
Join Date: Sep 2008
Location: Honolulu
Device: Nokia 770 (fbreader)
Hmmm, another thought. Does it make sense to include the following two things?

#1: versioning info. Often when I get a file, the version number is basically meaningless. Here's the versioning ranks I use:

Code:
0.10 Initial Conversion
   0.20 Cover and Frontispiece
   0.30 Sections, Chapters and TOC
   0.40 Endnotes and/or Blockquotes
   0.50 Initial Spellcheck
   0.60 Mdashes and Hyphens and Ellipses
   0.70 Italics, Bold, and Pre-Formatted Text
   0.80 Reading Proof
   0.90 Checked against Canonical Source
   1.00 Touched Up and Packaged For Release
#2: structure hints. Should someone have to examine the entire source for a clue to how it's been assembled? Or could you add something like this as a comment?:

Code:
Title: h1 class="title"
Subtitle: h3 class="subtitle"
Chapter: h3 class="chapter"
Paragraph: p class="normal"
Epigram: p class="epigram"
etc. etc.
m a r
rogue_ronin is offline   Reply With Quote