Quote:
Originally Posted by pepak
It does make sense, but seems a bit too detailed to me. It may be interesting, but:
- the book should never leave your computer in the intermediate stages
- after version 1.00, most of the changes will be along the lines of "fixed typo on page 123 line 15".
|
Your analysis of my words is correct, but I
might release earlier -- some of the sources I don't have, so I cannot go past 0.80 on that scale, yet there's no reason to keep them locked up on my hard drive. I should probably reword as follows:
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 Final Version -- Optimal
1.00+ Minor Error Corrections
I think that including it would suggest to someone how to add value and version it consistently. I can think of arguments for releasing at 0.50 and 0.60 as well.
Quote:
Personally, I prefer the "no-clue" approach. If someone wants to see the clues, he can easily do that (for all books at one stroke) by modifying CSS, e.g.
Code:
h1.title:before { content: "Title: "; }
|
You've got me there, I can't follow you yet -- just starting to get into the CSS.
Quote:
If you use a proper tagging, hiding all "clues" would be even easier:
Code:
.clue { display: none; }
|
I assume you mean to put the "clues" into a special container. I'm just thinking to put it into a comment. Could you explain more fully?
Thanks as always for your insightful comments,
m a r
ps: did you start your regex thread?