The only attributes on the <svg> root element are: xmlns, version, and viewBox.
-
The contents of the SVG’s <title> element matches the alt attribut of its <img> element in the text.
+
The contents of the SVG’s <title> element matches the alt attribute of its <img> element in the text.
Grouping with <g> is avoided, unless it makes semantic sense. Groups whose sole purpose is to apply transforms should have those transforms applied to the children, and the group removed.
The use of fill color is avoided unless strictly necessary. Not defining a fill color allows for night mode compatibility.
The transform attribute is illegal; transforms are applied to their elements directly.
@@ -230,4 +230,4 @@ require_once('Core.php');
-
+
\ No newline at end of file
diff --git a/www/manual/1.0/code-style.php b/www/manual/1.0.0/code-style.php
similarity index 97%
rename from www/manual/1.0/code-style.php
rename to www/manual/1.0.0/code-style.php
index 9c486e32..68ee2198 100644
--- a/www/manual/1.0/code-style.php
+++ b/www/manual/1.0.0/code-style.php
@@ -3,9 +3,10 @@ require_once('Core.php');
?> '1. XHTML, CSS, and SVG Code Style - The Standard Ebooks Manual', 'highlight' => 'contribute', 'manual' => true]) ?>
+
XHTML, CSS, and SVG Code Style
-
The se clean tool in the Standard Ebooks toolset formats XHTML code according to our style guidelines. The vast majority of the time its output is correct and no further modifications to code style are necessary.
+
The se clean tool in the Standard Ebooks toolset formats XHTML, CSS, and SVG code according to our style guidelines. The vast majority of the time its output is correct and no further modifications to code style are necessary.
XHTML formatting
@@ -27,7 +28,7 @@ require_once('Core.php');
<br/> elements
-
<br/> elements within phrasing content are on the same line as the precediong phrasing content, and are followed by a newline.
+
<br/> elements within phrasing content are on the same line as the preceding phrasing content, and are followed by a newline.
<p>“Pray for the soul of the
<br/>
Demoiselle Jeanne D’Ys.</p>
@@ -104,7 +105,7 @@ Demoiselle Jeanne D’Ys</p
Selectors
-
Selectors are each on their own line, directly followed by a comma or a brace with no whitespace inbetween.
+
Selectors are each on their own line, directly followed by a comma or a brace with no whitespace in between.
abbr.era,.signature{font-variant:all-small-caps;}
@@ -173,10 +174,10 @@ Demoiselle Jeanne D’Ys</p
-
+
\ No newline at end of file
diff --git a/www/manual/1.0/filesystem.php b/www/manual/1.0.0/filesystem.php
similarity index 97%
rename from www/manual/1.0/filesystem.php
rename to www/manual/1.0.0/filesystem.php
index 1122bbbe..61e6aaf0 100644
--- a/www/manual/1.0/filesystem.php
+++ b/www/manual/1.0.0/filesystem.php
@@ -23,7 +23,7 @@ require_once('Core.php');
./src/images/titlepage.svg is the editable titlepage file that is later compiled for distribution.
./src/images/cover.svg is the editable cover file that is later compiled for distribution.
./src/images/cover.source.(jpg|png|bmp|tiff) is the raw cover art file that may be cropped, resized, or otherwise edited to create ./src/images/cover.jpg.
-
./src/images/cover.jpg is the final edited cover art that will be compiled in to ./src/epub/images/cover.svg for distribution.
+
./src/images/cover.jpg is the final edited cover art that will be compiled into ./src/epub/images/cover.svg for distribution.
Images compiled or derived from raw source images, that are then distributed with the ebook, are located in ./src/epub/images/.
@@ -32,7 +32,7 @@ require_once('Core.php');
The ONIX metadata file is located in ./src/epub/onix.xml. This file is identical for all ebooks.
The ONIX metadata file is located in ./src/epub/onix.xml. This file is identical for all ebooks.
The ./src/META-INF/ and ./src/mimetype directory and files are epub structural files that are identical for all ebooks.
-
The ./LICENSE.md contains th ebook license and is identical for all ebooks.
+
The ./LICENSE.md contains the ebook license and is identical for all ebooks.
@@ -228,4 +228,4 @@ require_once('Core.php');
-
+
\ No newline at end of file
diff --git a/www/manual/1.0/general-xhtml-patterns.php b/www/manual/1.0.0/general-xhtml-patterns.php
similarity index 99%
rename from www/manual/1.0/general-xhtml-patterns.php
rename to www/manual/1.0.0/general-xhtml-patterns.php
index 219f0517..93cdae58 100644
--- a/www/manual/1.0/general-xhtml-patterns.php
+++ b/www/manual/1.0.0/general-xhtml-patterns.php
@@ -237,4 +237,4 @@ require_once('Core.php');
-
+
\ No newline at end of file
diff --git a/www/manual/1.0/high-level-structural-patterns.php b/www/manual/1.0.0/high-level-structural-patterns.php
similarity index 97%
rename from www/manual/1.0/high-level-structural-patterns.php
rename to www/manual/1.0.0/high-level-structural-patterns.php
index ed0114c8..0e22ab7e 100644
--- a/www/manual/1.0/high-level-structural-patterns.php
+++ b/www/manual/1.0.0/high-level-structural-patterns.php
@@ -12,11 +12,11 @@ require_once('Core.php');
Major structural divisions of a larger work, like parts, volumes, books, chapters, or subchapters, are contained in a <section> element.
Individual items in a larger collection (like a poem in a poetry collection) are contained in a <article> element.
-
In <section> or <articles> elements that have titles, the first child element is an <h1>–<h6> element, or a <header> element containing the section's title.
+
In <section> or <articles> elements that have titles, the first child element is an <h1>–<h6> element, or a <header> element containing the section’s title.
Recomposability
-
“Recomposability” is the concept of generating a single structurally-correct HTML5 file out of an epub file. All SE ebooks are recomposable.
+
“Recomposability” is the concept of generating a single structurally-correct HTML5 file out of an epub file. All Standard Ebooks are recomposable.
XHTML files that contain <section> or <articles> elements that are semantic children of <section> or <articles> elements in other files, are wrapped in stubs of all parent <section> or <articles> elements, up to the root.
Each such included parent element has the identical id and epub:type attributes of its real counterpart.
@@ -50,10 +50,10 @@ require_once('Core.php');
Headers
-
<h1>–<h6> elements are used for headers of sections that are structural divisions of a document, i.e., divisions that appear in the table of contents. <h1>–<h6> elements are not used for headers of components that are not in the table of contents. For example, they are not used to mark up the the title of a short poem in a chapter, where the poem itself is not a structural component of the larger ebook.
+
<h1>–<h6> elements are used for headers of sections that are structural divisions of a document, i.e., divisions that appear in the table of contents. <h1>–<h6> elements are not used for headers of components that are not in the table of contents. For example, they are not used to mark up the title of a short poem in a chapter, where the poem itself is not a structural component of the larger ebook.
A section containing an <h1>–<h6> appears in the table of contents.
-
The book's title is implicitly at the <h1> level, even if <h1> is not present in the ebook. Because of the implicit <h1>, all other sections begin at <h2>.
-
Each <h1>–<h6> element uses the correct number for the section's heading level in the overall book, not the section's heading level in the individual file. For example, given an ebook with a file named part-2.xhtml containing:
+
The book’s title is implicitly at the <h1> level, even if <h1> is not present in the ebook. Because of the implicit <h1>, all other sections begin at <h2>.
+
Each <h1>–<h6> element uses the correct number for the section’s heading level in the overall book, not the section’s heading level in the individual file. For example, given an ebook with a file named part-2.xhtml containing:
<sectionid="part-2"epub:type="part"><h2epub:type="title">Part <spanepub:type="z3998:roman">II</span></h2></section>
@@ -137,7 +137,7 @@ require_once('Core.php');
</header><header><h2epub:type="title z3998:roman">X</h2>
- <pepub:type="bridgehead">Our first night—Under canvas—An appeal for help—Contrariness of teakettles, how to overcome—Supper—How to feel virtuous—Wanted! a comfortably-appointed, well-drained desert island, neighbourhood of South Pacific Ocean preferred—Funny thing that happened to George’s father—a restless night.</p>
+ <pepub:type="bridgehead">Our first nightwj—Under canvaswj—An appeal for helpwj—Contrariness of teakettles, how to overcomewj—Supperwj—How to feel virtuouswj—Wanted! a comfortably-appointed, well-drained desert island, neighbourhood of South Pacific Ocean preferredwj—Funny thing that happened to George’s fatherwj—A restless night.</p></header>
In addition to the CSS used for all epigraphs, this additional CSS is included for epigraphs in section headers:
+
In addition to the CSS used for all epigraphs, this additional CSS is included for epigraphs in section headers:
/* Epigraphs in section headers */section>header[epub|type~="epigraph"]{display:inline-block;
@@ -219,7 +219,7 @@ require_once('Core.php');
In full-page epigraphs, the epigraph is centered on the page for ereaders that support advanced CSS. For all other ereaders, the epigraph is horizontally centered with a small margin above it.
Full-page epigraphs that contain multiple quotations are represented by multiple <blockquote> elements.
-
In addition to the CSS used for all epigraphs, this additional CSS is included for full-page epigraphs:
+
In addition to the CSS used for all epigraphs, this additional CSS is included for full-page epigraphs:
/* Full-page epigraphs */section[epub|type~="epigraph"]{text-align:center;
@@ -484,7 +484,7 @@ require_once('Core.php');
<td>I didn’t think it polite to listen, sir.</td></tr>
-
When several personas speak at once, or a group of personas ("The Actors") speaks at once, the containing <tr> element has the together class, and the the first <td> child has a rowspan attribute corresponding to the number of lines spoken together.
+
When several personas speak at once, or a group of personas ("The Actors") speaks at once, the containing <tr> element has the together class, and the first <td> child has a rowspan attribute corresponding to the number of lines spoken together.
tr.togethertd{padding:0.5em00;vertical-align:middle;
@@ -599,7 +599,7 @@ require_once('Core.php');
Letter headers
Parts of a letter prior to the body of the letter, for example the location where it is written, the date, and the salutation, are wrapped in a <header> element.
-
If there is only a salutation and no other header content, the <header> element is ommitted.
+
If there is only a salutation and no other header content, the <header> element is omitted.
The location and date of a letter have the semantic inflection of se:letter.dateline. Dates are in a <time> element with a computer-readable date.
<header><pepub:type="se:letter.dateline">Blarney Castle, <timedatetime="1863-10-11">11th of October, 1863</time></p>
@@ -680,14 +680,14 @@ require_once('Core.php');
<footer><pepub:type="z3998:valediction">Your loving niece,</p><pclass="signature"epub:type="z3998:sender">Mabel</p>
- <pepub:type="z3998:postscript">P.S.—Lots, please, because some of us are very hungry.</p>
+ <pepub:type="z3998:postscript"><abbr>P.S.</abbr>wj—Lots, please, because some of us are very hungry.</p></footer></blockquote><blockquoteepub:type="z3998:letter"><header><pepub:type="se:letter.dateline">Gracechurch-street, <timedatetime="08-02">August 2</time>.</p></header>
- <p><spanepub:type="z3998:salutation">My dear Brother</span>, At last I am able to send you some tidings of my niece, and such as, upon the whole, I hope will give you satisfaction. Soon after you left me on Saturday, I was fortunate enough to find out in what part of London they were. The particulars, I reserve till we meet. It is enough to know they are discovered, I have seen them both—</p>
+ <p><spanepub:type="z3998:salutation">My dear Brother</span>, At last I am able to send you some tidings of my niece, and such as, upon the whole, I hope will give you satisfaction. Soon after you left me on Saturday, I was fortunate enough to find out in what part of London they were. The particulars, I reserve till we meet. It is enough to know they are discovered, I have seen them bothwj—</p><p>I shall write again as soon as anything more is determined on.</p><footer><pepub:type="z3998:valediction">Yours, etc.</p>
@@ -703,7 +703,7 @@ require_once('Core.php');
The alt attribute describes the visual image itself in words, which is not the same as writing a caption or describing its place in the book.
<imgalt="The illustration for chapter 10"src="..."/>
- <imgalt="Pierre's fruit-filled dinner"src="..."/>
+ <imgalt="Pierre’s fruit-filled dinner"src="..."/><imgalt="An apple and a pear inside a bowl, resting on a table."src="..."/>
The alt attribute is one or more complete sentences ended with periods or other appropriate punctuation. It is not composed of sentence fragments or complete sentences without ending punctuation.
@@ -714,8 +714,8 @@ require_once('Core.php');
<img> element whose image is black-on-white line art (i.e. exactly two colors, not grayscale!) are PNG files with a transparent background. They have the se:image.color-depth.black-on-transparent semantic inflection.
<img> elements that are meant to be aligned on the block level or displayed as full-page images are contained in a parent <figure> element, with an optional <figcaption> sibling.
-
when contained in a <figure> element, the <img> element does not have an id attribute; instead the <figure> element has the id attribute.
-
An optional <figcaption> element containing a concise context-dependent caption may follow the <img> element within a <figure> element. This caption depends on the surrounding context, and is not necessarily (or even ideally) identical to the <img> element's alt attribute.
+
When contained in a <figure> element, the <img> element does not have an id attribute; instead the <figure> element has the id attribute.
+
An optional <figcaption> element containing a concise context-dependent caption may follow the <img> element within a <figure> element. This caption depends on the surrounding context, and is not necessarily (or even ideally) identical to the <img> element’s alt attribute.
All figure elements, regardless of positioning, have this CSS:
figureimg{display:block;
@@ -801,18 +801,19 @@ require_once('Core.php');
List of Illustrations (the LoI)
-
If an ebook has any illustrations that are major structural components of the work (even just one!), then the ebook includes an loi.xhtml file at the end of the ebook. This file lists the illustrations in the ebook, along with a short caption or description. #. The LoI is an XHTML file located in ./src/epub/text/loi.xhtml.
+
If an ebook has any illustrations that are major structural components of the work (even just one!), then the ebook includes an loi.xhtml file at the end of the ebook. This file lists the illustrations in the ebook, along with a short caption or description.
+
The LoI is an XHTML file located in ./src/epub/text/loi.xhtml.
The LoI file has the backmatter semantic inflection.
The LoI only contains links to images that are major structural components of the work.
An illustration is a major structural component if, for example: it is an illustration of events in the book, like a full-page drawing or end-of-chapter decoration; it is essential to the plot, like a diagram of a murder scene or a map; or it is a component of the text, like photographs in a documentary narrative.
-
An illustration is not a major structural components if, for example: it is a drawing used to represent a person's signature, like an X mark; it is an inline drawing representing text in alien languages; it is a drawing used as a layout element to illustrate forms, tables, or diagrams.
+
An illustration is not a major structural components if, for example: it is a drawing used to represent a person’s signature, like an X mark; it is an inline drawing representing text in alien languages; it is a drawing used as a layout element to illustrate forms, tables, or diagrams.
The LoI file contains a single <sectionid="loi"epub:type="loi"> element, which in turn contains an <h2epub:type="title">List of Illustrations</h2> element, followed by a <navepub:type="loi"> element containing an <ol> element, which in turn contains list items representing the images.
If an image listed in the LoI has a <figcaption> element, then that caption is used in the anchor text for that LoI entry. If not, the image’s alt attribute is used. If the <figcaption> element is too long for a concise LoI entry, the alt attribute is used instead.
-
Links to the images go directly to the image's corresponding id hashes, not just the top of the containing file.
+
Links to the images go directly to the image’s corresponding id hashes, not just the top of the containing file.
Examples
@@ -924,4 +925,4 @@ require_once('Core.php');
-
+
\ No newline at end of file
diff --git a/www/manual/1.0.0/index.php b/www/manual/1.0.0/index.php
new file mode 100644
index 00000000..53a1c044
--- /dev/null
+++ b/www/manual/1.0.0/index.php
@@ -0,0 +1,25 @@
+ 'The Standard Ebooks Manual', 'highlight' => 'contribute', 'manual' => true]) ?>
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/www/manual/1.0/metadata.php b/www/manual/1.0.0/metadata.php
similarity index 98%
rename from www/manual/1.0/metadata.php
rename to www/manual/1.0.0/metadata.php
index b5de55c4..3685e311 100644
--- a/www/manual/1.0/metadata.php
+++ b/www/manual/1.0.0/metadata.php
@@ -34,7 +34,7 @@ require_once('Core.php');
Start with the URL-safe author of the work, as it appears on the titlepage. If there is more than one author, continue appending subsequent URL-safe authors, separated by an underscore. Do not alpha-sort the author name.
Append a forward slash, then the URL-safe title of the work. Do not alpha-sort the title.
If the work is translated, append a forward slash, then the URL-safe translator. If there is more than one translator, continue appending subsequent URL-safe translators, separated by an underscore. Do not alpha-sort translator names.
-
If the work is illustrated, append a foreward slash, then the URL-safe illustrator. If there is more than one illustrator, continue appending subsequent URL-safe illustrators, separated by an underscore. Do not alpha-sort illustrator names.
+
If the work is illustrated, append a forward slash, then the URL-safe illustrator. If there is more than one illustrator, continue appending subsequent URL-safe illustrators, separated by an underscore. Do not alpha-sort illustrator names.
Finally, do not append a trailing forward slash.
@@ -128,7 +128,7 @@ require_once('Core.php');
SE subjects
-
Along with the Library of Congress categories, we include a custom list of SE subjects in the ebook metadata. Unlike Library of Congress categories, SE subjects are purposefully broad. They’re more like the subject categories in a medium-sized bookstore, as opposed to the precise, detailed, heirarchal Library of Congress categories.
+
Along with the Library of Congress categories, we include a custom list of SE subjects in the ebook metadata. Unlike Library of Congress categories, SE subjects are purposefully broad. They’re more like the subject categories in a medium-sized bookstore, as opposed to the precise, detailed, hierarchical Library of Congress categories.
It’s the producer’s task to select appropriate SE subjects for the ebook. Usually just one or two of these categories will suffice.
All SE subjects
@@ -170,7 +170,7 @@ require_once('Core.php');
The short description
The <dc:description> element contains a short, single-sentence summary of the ebook.
-
The description is a single complete sentence ending in a period, not a sentence fragment or restatment of the title.
+
The description is a single complete sentence ending in a period, not a sentence fragment or restatement of the title.
The description is typogrified, i.e. it contains Unicode curly quotes, em-dashes, and the like.
@@ -183,7 +183,7 @@ require_once('Core.php');
The long description is in escaped HTML, with the HTML beginning on its own line after the <metaproperty="se:long-description"> element.
The long description element is directly followed by: <metaproperty="meta-auth"refines="#long-description">https://standardebooks.org</meta>
@@ -228,7 +228,7 @@ require_once('Core.php');
General contributor rules
The following apply to all contributors, including the author(s), translator(s), and illustrator(s).
-
If there is exactly one contributor in a set (for example, only one author, or only one translator) then the <metaproperty="display-seq"> element is ommitted for that contributor.
+
If there is exactly one contributor in a set (for example, only one author, or only one translator) then the <metaproperty="display-seq"> element is omitted for that contributor.
If there is more than one contributor in a set (for example, multiple authors, or translators) then the <metaproperty="display-seq"> element is specified for each contributor, with a value equal to their position in the SE identifier.
The epub standard specifies that in a set of contributors, if at least one has the display-seq attribute, then other contributors in the set without the display-seq attribute are ignored. For SE purposes, this also means they will be excluded from the SE identifier.
By SE convention, contributors with <metaproperty="display-seq">0</meta> are excluded from the SE identifier.
@@ -266,7 +266,7 @@ require_once('Core.php');
The translator metadata block
If the work is translated, the <dc:contributorid="translator"> metadata block follows the author metadata block.
-
If there is more than one translator, then the first translator's id is translator-1, the second translator-2, and so on.
+
If there is more than one translator, then the first translator’s id is translator-1, the second translator-2, and so on.
Each block is identical to the author metadata block, but with <dc:contributorid="translator"> instead of <dc:creatorid="author">.
The MARC relator tag is trl: <metaproperty="role"refines="#translator"scheme="marc:relators">trl</meta>.
Translators often annotate the work; if this is the case, the additional MARC relator tagann is included in a separate <metaproperty="role"refines="#translator"scheme="marc:relators"> element.
@@ -276,7 +276,7 @@ require_once('Core.php');
The illustrator metadata block
If the work is illustrated by a person who is not the author, the illustrator metadata block follows.
-
If there is more than one illustrator, the first illustrator's id is illustrator-1, the second illustrator-2, and so on.
+
If there is more than one illustrator, the first illustrator’s id is illustrator-1, the second illustrator-2, and so on.
Each block is identical to the author metadata block, but with <dc:contributorid="illustrator"> instead of <dc:creatorid="author">.
The MARC relator tag is ill: <metaproperty="role"refines="#illustrator"scheme="marc:relators">ill</meta>.
@@ -347,4 +347,4 @@ require_once('Core.php');
-
+
\ No newline at end of file
diff --git a/www/manual/1.0/semantics.php b/www/manual/1.0.0/semantics.php
similarity index 96%
rename from www/manual/1.0/semantics.php
rename to www/manual/1.0.0/semantics.php
index cf2135b5..3655e756 100644
--- a/www/manual/1.0/semantics.php
+++ b/www/manual/1.0.0/semantics.php
@@ -16,7 +16,7 @@ require_once('Core.php');
That demmed, elusive Pimpernel?”</div></div>
While that snipped might visually present the text as a paragraph followed by a quotation of verse, the actual HTML tells us nothing about what these lines of text actually are.
-
Compare the above snippet to this next snippet, which renders almost identically but uses semantically-correct tags and epub's semantic inflection to tell us what the text is:
+
Compare the above snippet to this next snippet, which renders almost identically but uses semantically-correct tags and epub’s semantic inflection to tell us what the text is:
<p>“All done in the tying of a cravat,” Sir Percy had declared to his clique of admirers.</p><blockquoteepub:type="z3998:poem"><p>
@@ -71,7 +71,7 @@ require_once('Core.php');
<i>: Text rendered in italics, without any explicit semantic meaning. Because <i> lacks semantic meaning, the epub:type attribute is added with appropriate semantic inflection to describe the contents of the tag.
<p>The <abbrclass="initialism">HMS</abbr><iepub:type="se:name.vessel.ship">Bounty</i>.</p>
-
<b>: Text rendered in small caps, without any explicit semantic meaning. Because <i> lacks semantic meaning, the epub:type attribute is added with appropriate semantic inflection to describe the contents of the tag.
+
<b>: Text rendered in small caps, without any explicit semantic meaning. Because <b> lacks semantic meaning, the epub:type attribute is added with appropriate semantic inflection to describe the contents of the tag.
<span>: Plain inline text that requires specific styling or semantic meaning that cannot be achieved with any other semantically meaningful inline tag. Typically used in conjunction with a class or epub:type attribute.
@@ -90,7 +90,7 @@ require_once('Core.php');
If the z3998 vocabulary doesn’t have an appropriate keyword, the Standard Ebooks vocabulary is consulted next.
Keywords using this vocabulary are preceded by the se namespace.
Unlike other vocabularies, the Standard Ebooks vocabulary is organized hierarchically. A complete vocabulary entry begins with the root vocabulary entry, with subsequent children separated by ..
- The <iepub:type="se:name.vessel.ship"><abbrclass="initialism">HMS</abbr> Bounty</i>.
+ The <abbrclass="initialism">HMS</abbr><iepub:type="se:name.vessel.ship">Bounty</i>.
The epub:type attribute can have multiple keywords separated by spaces, even if the vocabularies are different.
<sectionepub:type="chapter z3998:letter">...</section>
@@ -113,4 +113,4 @@ require_once('Core.php');
-
+
\ No newline at end of file
diff --git a/www/manual/1.0/table-of-contents-patterns.php b/www/manual/1.0.0/table-of-contents-patterns.php
similarity index 94%
rename from www/manual/1.0/table-of-contents-patterns.php
rename to www/manual/1.0.0/table-of-contents-patterns.php
index 3c342888..022368cc 100644
--- a/www/manual/1.0/table-of-contents-patterns.php
+++ b/www/manual/1.0.0/table-of-contents-patterns.php
@@ -6,18 +6,18 @@ require_once('Core.php');
Table of Contents Patterns
-
The table of contents (the ToC) is not viewable as a page in the ebook's reading order. Instead, the reader's ereading system displays the ToC as part of its reading interface.
+
The table of contents (the ToC) is not viewable as a page in the ebook’s reading order. Instead, the reader’s ereading system displays the ToC as part of its reading interface.
These rules outline how to structure the ToC. Typically, the output of se print-toc constructs ToCs according to these rules, without further changes being necessary.
The ToC <nav> element
-
The first child of the Toc's <body> tag is a <nav> element with the semantic inflection toc.
+
The first child of the Toc’s <body> tag is a <nav> element with the semantic inflection toc.
The first child of the <nav> element is a <h2epub:type="title">Table of Contents</h2> element.
The second child of the <nav> element is an <ol> element representing the items in the Table of Contents.
The top-level <ol> element
-
The <nav> element's top-level <ol> element contains a list of items in the Table of Contents.
+
The <nav> element’s top-level <ol> element contains a list of items in the Table of Contents.
The first child is a link to the titlepage.
<li>
@@ -39,7 +39,7 @@ require_once('Core.php');
<ahref="text/uncopyright.xhtml">Uncopyright</a></li>
-
In books with half title pages, the half title page is listed in the ToC and the next sibling is an <ol> element containing the book's contents.
+
In books with half title pages, the half title page is listed in the ToC and the next sibling is an <ol> element containing the book’s contents.
<li><ahref="text/halftitle.xhtml">The Moon Pool</a><ol>
@@ -56,7 +56,7 @@ require_once('Core.php');
<li> descendents
Each <li> contains an <a> tag pointing to a file or hash, and optionally also contains an <ol> element representing a nested series of ToC items.
-
If an <li> element contains a nested <ol> element, that <li>'s first child is an <a> element that points to the beginning of that section.
+
If an <li> element contains a nested <ol> element, that <li>’s first child is an <a> element that points to the beginning of that section.
<li><ahref="text/halftitle.xhtml">Sybil</a><ol>
@@ -89,29 +89,29 @@ require_once('Core.php');
<a> descendents
-
Chapters without titles are represented by their Roman ordinal, without the word Chapter:
+
Chapters without titles are represented by their Roman ordinal, without the word Chapter.
<aepub:type="title z3998:roman">XI</a>
-
Chapters with titles are represented by their Roman ordinal, followed by a colon and a space, followed by the chapter title:
+
Chapters with titles are represented by their Roman ordinal, followed by a colon and a space, followed by the chapter title.
<ahref="text/chapter-3.xhtml"><spanepub:type="z3998:roman">III</span>: The Moon Rock</a>
-
Chapters with unique identifiers (i.e. not Chapter, but something unique to the style of the book, like Book or Stave), include that unique identifier in the <a> element:
+
Chapters with unique identifiers (i.e. not Chapter, but something unique to the style of the book, like Book or Stave), include that unique identifier in the <a> element.
<ahref="text/chapter-1.xhtml">Stave <spanepub:type="z3998:roman">I</span>: Marley’s Ghost</a>
-
High-level sections (like parts or divisions) without titles are represented by their identifier (like Book or Part), followed by their Roman ordinal:
+
High-level sections (like parts or divisions) without titles are represented by their identifier (like Book or Part), followed by their Roman ordinal.
<ahref="text/book-1.xhtml">Book <spanepub:type="z3998:roman">I</span></a>
-
High-level sections (like parts or divisions) with titles include the title:
+
High-level sections (like parts or divisions) with titles include the title.
<ahref="text/book-10.xhtml">Book <spanepub:type="z3998:roman">X</span>: The Boys</a>
-
Sections that are not chapters do not include their subtitles in the ToC:
+
Sections that are not chapters do not include their subtitles in the ToC.
<ahref="text/epilogue.xhtml">Epilogue: A Morning Call</a><ahref="text/epilogue.xhtml">Epilogue</a>
-
High-level sections (like parts or divisions) with titles include the title:
+
High-level sections (like parts or divisions) with titles include the title.
<ahref="text/book-10.xhtml">Book <spanepub:type="z3998:roman">X</span>: The Boys</a>
-
Entries for half title pages do not include the subtitle:
+
Entries for half title pages do not include the subtitle.
<li><ahref="text/halftitle.xhtml">His Last Bow</a><ol>
@@ -155,4 +155,4 @@ require_once('Core.php');
-
+
\ No newline at end of file
diff --git a/www/manual/1.0/the-structure-of-an-ebook.php b/www/manual/1.0.0/the-structure-of-an-ebook.php
similarity index 92%
rename from www/manual/1.0/the-structure-of-an-ebook.php
rename to www/manual/1.0.0/the-structure-of-an-ebook.php
index f5d1a337..af23b253 100644
--- a/www/manual/1.0/the-structure-of-an-ebook.php
+++ b/www/manual/1.0.0/the-structure-of-an-ebook.php
@@ -8,10 +8,10 @@ require_once('Core.php');
The Structure of an Ebook
Books consist of three major partitions: Front Matter, Body Matter, and Back Matter.
-
These terms become important when building the Table of Contents (ToC). The Landmarks section of the ToC requires items to be labeled with the appropriate partition identifier. See ToC Patterns for more information about the ToC.
+
These terms become important when building the Table of Contents (ToC). The Landmarks section of the ToC requires items to be labeled with the appropriate partition identifier. See ToC Patterns for more information about the ToC.
Front matter
-
Front matter is material that appears before to the main content of the work. It includes such items as a dedication, an epigraph, an introduction, and so on.
+
Front matter is material that appears before the main content of the work. It includes such items as a dedication, an epigraph, an introduction, and so on.
Cover
The cover presents the outer appearance of the book, usually consisting of an image, the title of the book and the author’s name. For Standard Ebooks productions, the cover is an SVG image generated from template that combines the book title and author, and a background image. The se build-images tool generates the cover image used for distribution.
@@ -31,7 +31,7 @@ require_once('Core.php');
Epigraph
A quotation or poem at the start of a book which may set the mood or inspire thoughts about the work to come.
-
If the epigraph is a poem or quotation from poetry, it must follow the standards for verse described in High-Level Structural Patterns
+
If the epigraph is a poem or quotation from poetry, it must follow the standards for verse described in High-Level Structural Patterns
Acknowledgements
@@ -59,9 +59,9 @@ require_once('Core.php');
Table of Contents
-
Also known as the ”ToC.” The Table of Contents lists the main headings in the book. In traditionally printed books, the table of contents is part of the front matter of the book.
+
Also known as the “ToC.” The Table of Contents lists the main headings in the book. In traditionally printed books, the table of contents is part of the front matter of the book.
-
In Standard Ebooks productions, the table of contents is ommitted from the ebook's spine and is instead presented to the reader via their ereader’s ToC feature.
+
In Standard Ebooks productions, the table of contents is omitted from the ebook’s spine and is instead presented to the reader via their ereader’s ToC feature.
@@ -106,4 +106,4 @@ require_once('Core.php');
-
+
\ No newline at end of file
diff --git a/www/manual/1.0/typography.php b/www/manual/1.0.0/typography.php
similarity index 96%
rename from www/manual/1.0/typography.php
rename to www/manual/1.0.0/typography.php
index abee50ed..54b25a44 100644
--- a/www/manual/1.0/typography.php
+++ b/www/manual/1.0.0/typography.php
@@ -10,7 +10,7 @@ require_once('Core.php');
Section titles and ordinals
Section ordinals in the body text are set in Roman numerals.
-
Section ordinals in a file's <title> element are set in Arabic numerals.
+
Section ordinals in a file’s <title> element are set in Arabic numerals.
<title>Chapter VII</title><title>Chapter 7</title>
@@ -39,8 +39,8 @@ require_once('Core.php');
<p>“Look at <em>that</em>!” she shouted.</p>
When an entire clause is italicized, trailing punctuation is italicized, unless that trailing punctuation is a comma at the end of dialog.
-
<p>“<em>Charge!</em>” she shouted.</p>
-
<p>“<em>But I want to</em>,” she said.</p>
+ <p>“<em>Charge!</em>” she shouted.</p>
+ <p>“<em>But I want to</em>,” she said.</p>
Words written to be read as sounds are italicized with <i>.
<p>He could hear the dog barking: <i>Ruff, ruff, ruff!</i></p>
@@ -72,7 +72,7 @@ require_once('Core.php');
<p>The <ixml:lang="fr">corps de ballet</i> was flung into consternation.</p>
Foreign words that are proper names, or are in proper names, are not italicized, unless the name itself would be italicized according to the rules for italicizing or quoting names and titles. Such words are wrapped in a <spanxml:lang="LANGUAGE"> element, to assist screen readers with pronunciation.
- <p>She got off the metro at the <ixml:lang="fr">Place de Clichy</i> stop, next to the <ixml:lang="fr">PLe Bon Petit Déjeuner restaurant</i>.</p>
+ <p>She got off the metro at the <ixml:lang="fr">Place de Clichy</i> stop, next to the <ixml:lang="fr">Le Bon Petit Déjeuner restaurant</i>.</p><p>“<ixml:lang="fr">Où est le métro?</i>” he asked, and she pointed to <spanxml:lang="fr">Place de Clichy</span>, next to the <spanxml:lang="fr">Le Bon Petit Déjeuner</span> restaurant.
If certain foreign words are used so frequently in the text that italicizing them at each instance would be distracting to the reader, then only the first instance is italicized. Subsequent instances are wrapped in a <spanxml:lang="LANGUAGE"> element.
@@ -118,7 +118,7 @@ require_once('Core.php');
Periodicals like magazines, newspapers, and journals.
Publications like books, novels, plays, and pamphlets, except “holy texts,” like the Bible or books within the Bible.
-
Long poems and ballads, like the Iliad, that are book-length.
+
Long poems and ballads, like the Iliad, that are book-length.
Long musical compositions or audio, like operas, music albums, or radio shows.
When something is addressed as an apostrophe <https://www.merriam-webster.com/dictionary/apostrophe#dictionary-entry-2>.., O is capitalized.
+
When something is addressed as an apostrophe, O is capitalized.
<p>I carried the bodies into the sea, O walker in the sea!</p>
Titlecasing follows the formula used in the se build-images tool.
@@ -221,7 +221,7 @@ require_once('Core.php');
Ampersands in names of things, like firms, are surrounded by no-break spaces.
<p>The firm of Hawkinsnbsp&nbspHarker.</p>
-
Some older works include spaces in common contrations; these spaces are removed.
+
Some older works include spaces in common contractions; these spaces are removed.
<p>Would n’t it be nice to go out? It ’s such a nice day.</p><p>Wouldn’t it be nice to go out? It’s such a nice day.</p>
@@ -245,7 +245,7 @@ require_once('Core.php');
Ellipses
The ellipses glyph (… or u+2026) is used for ellipses, instead of consecutive or spaced periods.
-
When ellipses are used as suspension points (for example, to indicate dialog that pauses or trails off), the ellipses is not preceded by a comma.
+
When ellipses are used as suspension points (for example, to indicate dialog that pauses or trails off), the ellipses are not preceded by a comma.
Ellipses used to indicate missing words in a quotation require keeping surrounding punctuation, including commas, as that punctuation is in the original quotation.
A hair space (u+200A) glyph is located before all ellipses that are not directly preceded by punctuation, or that are directly preceded by an em-dash or a two- or three-em-dash.
@@ -339,7 +339,7 @@ require_once('Core.php');
<p>I need 1/4 cup of sugar.</p><p>I need ¼ cup of sugar.</p>
-
If a fraction doesn't have a corresponding Unicode glyph, it is composed using the fraction slash Unicode glyph (⁄ or u+2044) and superscript/subscript Unicode numbers. See this Wikipedia entry for more details.
+
If a fraction doesn’t have a corresponding Unicode glyph, it is composed using the fraction slash Unicode glyph (⁄ or u+2044) and superscript/subscript Unicode numbers. See this Wikipedia entry for more details.
<p>Roughly 6/10 of a mile.</p><p>Roughly ⁶⁄₁₀ of a mile.</p>
@@ -367,7 +367,7 @@ require_once('Core.php');
Math
-
In works that are not math-oriented or that dont't have a significant amount of mathematical equations, equations are set using regular HTML and Unicode.
+
In works that are not math-oriented or that dont’t have a significant amount of mathematical equations, equations are set using regular HTML and Unicode.
Operators and operands in mathematical equations are separated by a space.
<p>6−2+2=6</p>
@@ -509,7 +509,7 @@ require_once('Core.php');
</m:math></p>
-
If a MathML variable includes an overline, it is set by combining the variable's normal Unicode glyph and the Unicode overline glyph (‾ or u+203E) in a <m:mover> element. However in the alttext attribute, the Unicode overline combining mark (u+0305) is used to represent the overline in Unicode.
+
If a MathML variable includes an overline, it is set by combining the variable’s normal Unicode glyph and the Unicode overline glyph (‾ or u+203E) in a <m:mover> element. However in the alttext attribute, the Unicode overline combining mark (u+0305) is used to represent the overline in Unicode.
<p><m:mathalttext="x̅"><m:mover>
@@ -527,13 +527,13 @@ require_once('Core.php');
Latinisms (except sic) that can be found in a modern dictionary are not italicized. Examples include e.g., i.e., ad hoc, viz., ibid., etc.. The exception is sic, which is always italicized.
Whole passages of Latin language and Latinisms that aren’t found in a modern dictionary are italicized.
Latinisms that are abbreviations are set in lowercase with periods between words and no spaces between them, except BC, AD, BCE, and CE, which are set without periods, in small caps, and wrapped with <abbrclass="era">:
abbr.era{font-variant:all-small-caps;
@@ -545,9 +545,9 @@ require_once('Core.php');