From 8168a125d0a03e5e0f5d84e01c2a18f5b5b22523 Mon Sep 17 00:00:00 2001 From: Alex Cabal Date: Tue, 5 Jul 2022 15:09:15 -0500 Subject: [PATCH] Expand flag in 'how to review' guide --- .../how-to-review-an-ebook-production-for-publication.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 e1f05450..01c82f81 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 @@ -86,7 +86,7 @@ require_once('Core.php');

  • Review italics and emphasis elements

    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 -E "<i|<em" src/epub/text/*.xhtml + grep --recursive --line-number --extended-regexp "<i|<em" src/epub/text/*.xhtml

    Are there any <i> elements that lack semantics?

    grep --recursive --line-number "<i>" src/epub/text/*.xhtml