diff --git a/www/contribute/how-tos/how-to-review-an-ebook-production-for-publication.php b/www/contribute/how-tos/how-to-review-an-ebook-production-for-publication.php index 5d2d5b50..77fe7809 100644 --- a/www/contribute/how-tos/how-to-review-an-ebook-production-for-publication.php +++ b/www/contribute/how-tos/how-to-review-an-ebook-production-for-publication.php @@ -47,7 +47,7 @@ require_once('Core.php');
Run the following command to examine possible miscurled sing-quote marks:
+Run the following command to examine possible miscurled single quotes:
se interactive-replace "(\s)‘([a-z])" "\1’\2" .
Note the use of ‘
(left single-quotation mark, U+2018) and ’
(right single-quotation mark, U+2019) in the command above, and not '
or `
. Using se interactive-replace
is the safest as there are many potential false positive cases here that should not be change. Refer the the relevant section of the Manual. Note that sometimes this type of mistakes might be committed by se typogrify
. For example:
Note the right single-quotation mark is applied twice under this situation. More cases like this is in the section of the Manual linked above.
Run the following command to examine punctuation that might have to be moved inside quotation marks:
+se interactive-replace "’([\.\,])" "\1’" .
+ In general, periods and commas always go inside qoutation marks, both single and double. For example:
+<p>He pronounced it “pleasure”, and as he said it he licked his lips.</p>
+ <p>He pronounced it “pleasure,” and as he said it he licked his lips.</p>
+ Note the right single-quotation mark is applied twice under this situation. More cases like this is in the section of the Manual linked above.
+As noted in the Manual text in call caps is rarely correct. Use the following command to check for instance of all caps:
@@ -76,8 +90,10 @@ require_once('Core.php');The elements <i></i>
and <em></em>
are not to be used interchangeably (see relevant section of the Manual here and here). Use the following command to check their usage in the production (alternatively, use the regular expression search function in a text editor):
grep --recursive --line-number "<i\|<em" src/epub/text/*.xhtml
+ The <i>
and <em>
elements are not to be used interchangeably (see relevant section of the Manual here and here). Use the following command to check their usage in the production (alternatively, use the regular expression search function in a text editor):
grep --recursive --line-number "<i|<em" src/epub/text/*.xhtml
+ Are there any <i>
elements that lack semantics?
grep --recursive --line-number "<i>" src/epub/text/*.xhtml
Check that the correct semantics for elements are used. (e.g. correct usage of <blockquote>
, no <div>
blocks are used, etc.
If the book is in "parts,", "books," or "volumes":
+If the book is in ”parts,” “books,” or “volumes”:
Do the chapters have the right filenames? (See Manual)
@@ -134,7 +150,7 @@ require_once('Core.php');Is author, translator(s), cover artist, etc. in the correct order and in expected style?
Check all links, such as author/work Wikipedia links, are correct by opening them in a browser.
+Check all links, such as author/work Wikipedia links, are correct by opening them in a browser. Sometimes se create-draft
guesses the wrong Wikipedia link for a book or person with the same name as another book or person.
If the book has a subtitle, check that it is represented as expected. See here for reference.