diff --git a/www/contribute/producing-an-ebook-step-by-step.php b/www/contribute/producing-an-ebook-step-by-step.php index 60e16cb3..49fd6058 100644 --- a/www/contribute/producing-an-ebook-step-by-step.php +++ b/www/contribute/producing-an-ebook-step-by-step.php @@ -180,9 +180,10 @@ proceed to seal up my confession, I bring the life of that unhappy Henry Jekyll
While se typogrify
does a lot of work for you, each ebook is totally different so there’s almost always more work to do that can only be done by hand. However, you will do a third commit first, to put the automated changes in a separate commit from any manual changes.
git add -A git commit -m "Typogrify"
- As an example of manual changes that might be needed, in Jekyll, you’ll notice that the chapter titles are in all caps. The S.E. standard requires chapter titles to be in title case, and se titlecase
can do that for us. se titlecase
accepts a string as its argument, and outputs the string in title case. For filtering chapter titles, use it with the --no-newline
switch (abbreviated -n
) to prevent the closing heading tag from being placed on its own line.
As an example of manual changes that might be needed, in Jekyll, you’ll notice that the chapter titles are in all caps. The S.E. standard requires chapter titles to be in title case, and se titlecase
can do that for us. se titlecase
accepts a string as its argument, and outputs the string in title case.
There are many things that se typogrify
isn’t well suited to do automatically. Check the Typography section of the SEMoS to see exactly how to format the work. Below is a brief, but incomplete, list of common issues that arise in ebooks: