mirror of
https://github.com/standardebooks/web.git
synced 2025-07-22 07:14:59 -04:00
Correct GitHub capitalization
This commit is contained in:
Trey Piepmeier
Alex Cabal
parent
adccb462cf
commit
a73d547df8
5 changed files with 7 additions and 7 deletions
|
|
@ -10,7 +10,7 @@
|
|||
<a href="/contribute/">Get Involved</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://github.com/standardebooks">Github</a>
|
||||
<a href="https://github.com/standardebooks">GitHub</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="/opds/">OPDS</a>
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ require_once('Core.php');
|
|||
<p>While there are plenty of places where you can download free and accurately-transcribed public domain ebooks, we feel the <em>quality</em> of those ebooks can often be greatly improved.</p>
|
||||
<p>For example, <a href="https://gutenberg.org">Project Gutenberg</a>, a major producer of public-domain ebooks, hosts epub and Kindle files that sometimes lack basic typographic necessities like curly quotes; some of those ebooks are automatically generated and can’t take full advantage of modern ereader technology like popup footnotes or popup tables of contents; they sometimes lack niceties like cover images and title pages; and the quality of individual ebook productions varies greatly.</p>
|
||||
<p>Archival sites like the <a href="https://archive.org">Internet Archive</a> (and even Project Gutenberg, to some extent) painstakingly preserve entire texts word-for-word, including original typos and ephemera that are of limited interest to modern readers: everything including centuries-old publishing marks, advertisements for long-vanished publishers, author bios, deeply archaic spellings, and so on. Sometimes all you get is a scan of the actual book pages. That’s great for researchers, archivists, and special-interest readers, but not that great for casual, modern readers.</p>
|
||||
<p>The Standard Ebooks project differs from those etext projects in that we aim to make free public domain ebooks that are carefully typeset, cleaned of ancient and irrelevant ephemera, take full advantage of modern ereading technology, are formatted according to a detailed style guide, and that are each held to a standard of quality and internal consistency. Standard Ebooks include carefully chosen cover art based on public domain artwork, and are presented in an attractive way on your ebookshelf. For technically-inclined readers, Standard Ebooks conform to a rigorous coding style, are completely open source, and are <a href="https://github.com/standardebooks/">hosted on Github</a>, so anyone can contribute corrections or improvements easily and directly without having to deal with baroque forums or opaque processes.</p>
|
||||
<p>The Standard Ebooks project differs from those etext projects in that we aim to make free public domain ebooks that are carefully typeset, cleaned of ancient and irrelevant ephemera, take full advantage of modern ereading technology, are formatted according to a detailed style guide, and that are each held to a standard of quality and internal consistency. Standard Ebooks include carefully chosen cover art based on public domain artwork, and are presented in an attractive way on your ebookshelf. For technically-inclined readers, Standard Ebooks conform to a rigorous coding style, are completely open source, and are <a href="https://github.com/standardebooks/">hosted on GitHub</a>, so anyone can contribute corrections or improvements easily and directly without having to deal with baroque forums or opaque processes.</p>
|
||||
</section>
|
||||
<section id="what-makes-se-different">
|
||||
<h2>What makes a Standard Ebook different?</h2>
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ require_once('Core.php');
|
|||
<section id="intro">
|
||||
<h2>Help create ebooks that are a pleasure to read</h2>
|
||||
<p>Standard Ebooks is a volunteer driven project, and there’s room for people of all skill levels to contribute.</p>
|
||||
<p>At the most basic level, anyone can <a href="https://groups.google.com/forum/#!forum/standardebooks">contribute feedback via our mailing list</a>. Day-to-day readers can <a href="/contribute/report-errors">tell us about errors they spot in our ebooks</a>. People with an eye for typography and a talent for editing can proofread whole ebooks. Technically inclined readers can produce ebooks themselves, or <a href="https://github.com/standardebooks">contribute via Github</a>.</p>
|
||||
<p>At the most basic level, anyone can <a href="https://groups.google.com/forum/#!forum/standardebooks">contribute feedback via our mailing list</a>. Day-to-day readers can <a href="/contribute/report-errors">tell us about errors they spot in our ebooks</a>. People with an eye for typography and a talent for editing can proofread whole ebooks. Technically inclined readers can produce ebooks themselves, or <a href="https://github.com/standardebooks">contribute via GitHub</a>.</p>
|
||||
</section>
|
||||
<section id="everyone">
|
||||
<h2>Everyone</h2>
|
||||
|
|
@ -73,10 +73,10 @@ require_once('Core.php');
|
|||
<p><a href="/contribute/toolset">Guidelines for contributing to the Standard Ebooks toolset.</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/standardebooks">All Standard Ebooks ebook source files on Github.</a></p>
|
||||
<p><a href="https://github.com/standardebooks">All Standard Ebooks ebook source files on GitHub.</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/standardebooks/tools">The Standard Ebooks toolset on Github.</a></p>
|
||||
<p><a href="https://github.com/standardebooks/tools">The Standard Ebooks toolset on GitHub.</a></p>
|
||||
</li>
|
||||
</ul>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ require_once('Core.php');
|
|||
<p>Advances in ereading devices and software have made proofreading ebooks a whole lot easier than in the past.</p>
|
||||
<p>Most ereading software allows you to highlight text and add notes to those highlights. If you’re using a device like a Kindle or a phone or tablet with the Google Play Books app, try holding your finger on some text. It’ll become highlighted, and you can drag the highlight to include more text if you like.</p>
|
||||
<p>That means the quickest way for you to proofread an ebook is to <a href="/help/how-to-use-our-ebooks">transfer it to your ereader</a> and start reading! Once you find an error, use the highlight feature to mark it, and keep on reading. Many errors, like mis-curled quotation marks or obvious spelling errors, don’t need a written note to accompany the highlight. But you should make a brief written note if the error wouldn’t be clear to a passing reader.</p>
|
||||
<p>Once you’ve finished the ebook, use your ereader’s “view all notes” option to find all of your highlights in one place. Then you can either <a href="/contribute/report-errors">report them to us</a>, or if you’re technically-minded, correct them directly in the ebook’s <a href="http://github.com/standardebooks">Github repository</a>. Remember to read our <a href="/contribute/typography">typography manual</a> to make sure the error you found is covered.</p>
|
||||
<p>Once you’ve finished the ebook, use your ereader’s “view all notes” option to find all of your highlights in one place. Then you can either <a href="/contribute/report-errors">report them to us</a>, or if you’re technically-minded, correct them directly in the ebook’s <a href="http://github.com/standardebooks">GitHub repository</a>. Remember to read our <a href="/contribute/typography">typography manual</a> to make sure the error you found is covered.</p>
|
||||
<section id="common-errors">
|
||||
<h2>Common errors to watch out for</h2>
|
||||
<p>Lots of different errors can occur during the long and complex process of digitizing a print book, but here are some of the more common ones:</p>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ require_once('Core.php');
|
|||
<main>
|
||||
<article>
|
||||
<h1>Toolset Guidelines</h1>
|
||||
<p>You can <a href="https://github.com/standardebooks/tools">view our toolset on Github</a>.</p>
|
||||
<p>You can <a href="https://github.com/standardebooks/tools">view our toolset on GitHub</a>.</p>
|
||||
<p>Contributions should be in Python 3.</p>
|
||||
<p>In general we follow a relaxed version of <a href="https://www.python.org/dev/peps/pep-0008/">PEP 8</a>. In particular, we use tabs instead of spaces, and there is no line length limit.</p>
|
||||
<p>Always use the <code class="path">regex</code> module instead of the <code class="path">re</code> module.</p>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue