Comment by robin_reala
9 hours ago
I’m a contributor – I did Kafka’s The Castle, Agatha Christie’s Giant’s Bread, and Stella Benson’s The Faraway Bride for this launch – and I’m happy to answer any questions about Standard Ebooks.
9 hours ago
I’m a contributor – I did Kafka’s The Castle, Agatha Christie’s Giant’s Bread, and Stella Benson’s The Faraway Bride for this launch – and I’m happy to answer any questions about Standard Ebooks.
I could not find out if there are outstanding todos that I could assign myself to as a newcomer. I'd like to contribute, but don't know where to start. Is there an issue board somewhere with missing books, or something else?
We have a list of wanted ebooks here: https://standardebooks.org/contribute/wanted-ebooks
First-time contributors should select something from the appropriate section, because that gives you the greatest chance of succeeding and the least burden on our reviewers as you get started.
Our toolset has a help wanted section and some outstanding issues: https://github.com/standardebooks/tools#help-wanted
Yep! Have a look at our contribution page that lists a bunch of different options, including a list of good first books. https://standardebooks.org/contribute
Probably a dumb question, but how do you guys decide (and source) the book covers? I love how they look, but as a philistine can't put into words why.
Also thanks for doing this, I've read a bunch of stuff (GK Chesterton, Dorothy Sayers, Dashiell Hammett) that I wouldn't have otherwise if it weren't for this service.
The historical criteria is fine-art style oil painting. These days we’re starting to use first-edition cover art a bunch for more modern productions if it’s good quality. We also tend to use abstract oil paintings for sci-fi.[1] Obviously, all art is sourced from the public domain too. We’ve also started a database of confirmed-US-PD artwork that we can use for future productions.[2]
[1] https://standardebooks.org/subjects/science-fiction
[2] https://standardebooks.org/artworks
As Robin mentioned the typical style is "fine art oil painting", with some wiggle room allowed for exceptionally difficult cases (like Asian-themed books, as there just wasn't much fine art on that subject pre-1930).
We also require that the art have some kind of connection to the book itself, so it's not just some random fine art. Sometimes the connection is a little fuzzy, but we do the best we can given that art must be pre-1930 and also must have been previously published.
(My personal favorite artwork selection of the books I worked on is The Communist Manifesto[1]. That painting was actually made specifically for a different book by Willa Cather[2], but I thought the peasant laborer, holding a sickle in one hand, with a faraway look in her eyes as the red sun rises behind her was just too good to pass up for Marx!)
1920ish was when it started becoming much more common for books to have illustrated dust jackets, so now that more books from that era and onwards are entering the public domain, we opt to use the first edition dust jacket if it's in the appropriate style. Fortunately for us, that era also happens to be the so-called Golden Age of Illustration so it's not hard finding beautiful art to use!
[1] https://standardebooks.org/ebooks/karl-marx_friedrich-engels...
[2] https://standardebooks.org/ebooks/willa-cather/the-song-of-t...
Do you think the things that makes an edition special goes missing while converting to e.g. Standard Ebooks. I remember both the The Castle and Das Schloss like they had typesetting that helped me in perceiving the feel of the book. Is there anyway to preserve that feeling and still keep within the bounds of standardisation you adhere to? (I did a quick look through my copy and it does not seem to be much that makes it unique really, just the size of the book, and the chapter heading graphics..)
Do you know if the project try to look at other languages at all?
Nothing particularly in The Castle, from my production of it. As this was not previously PD there wasn’t any Gutenberg (or other) transcription available, so I did my own from the OCR of the original scans. A large part of the feel of the work, to me at least, comes from the extreme sentence / paragraph lengths though.
We do have a default typography across all our works (the “Standard” in “Standard Ebooks” refers to a standard imprint; think Penguin) but we usually retain specific famous things where possible in a reflowable format. For example, the Mouse’s Tail in Alice’s Adventures in Wonderland,[1] or the letter in E. A. Poe’s “Thou Art the Man”.[2]
We don’t take on other languages, no. Our tooling[3] and style guides[4] are tailored specifically to English. Absolutely nothing stopping another project from forking the codebase (it’s GPL-3) and giving it a go.
[1] https://standardebooks.org/ebooks/lewis-carroll/alices-adven...
[2] https://standardebooks.org/ebooks/edgar-allan-poe/short-fict...
[3] https://github.com/standardebooks/tools
[4] https://standardebooks.org/manual/
It seems you may be making assumptions that the formatting and typesetting of any particular edition were intentional or even deliberate on the part of the author, not any number of people, from editors to printers, who could and would have influenced those things for various reasons.
Something I am rather familiar with is brought out by your mention of the German edition/title; that the continental market seems to generally produce books that are far more densely formatted, i.e., smaller font and typesetting, thinner pages, and leading to overall tighter book formats. I actually appreciate it when, e.g., a book is 1/2 the size and weight, and usually also made far more durably; but it will invariably compromise any author intention related to the arrangement of the lettering.
Maybe you can confirm that based on what seems to be your English and German editions of the same novel.
Well that depends, there are obviously authors that care about these things. I have no idea what Brods intentions were with the book, and if he cared about layout.
The German and Swedish editions I read were similarly typeset, and the first scan I found in English felt similar. What I wanted to know was if there was some thought into it, because the website is nicely designed so striving for a unique typesetting strategy could be a goal.
> tighter
I found it amusing, considering all those memes about German words with 35 letters each.
And, as I get older, I began to consider letter size relevant to choose a book edition. Gave up buying new books and went for used, older editions with bigger letters.
The formatting they are referring to is not that of the original text but that of the Standard Ebooks project.
I seem to remember that they had some very opinionated rules at the beginning regarding allowed spelling and typography. Some of them felt distinctly American to me. I don't know if that's still the case.
Apart from that, they produce nice editions.
It’s en-US typography (flavoured by the Chicago Manual of Style). Spelling is based on the original book, though some modernisations are made. Commits with these always start with [Editorial] for easy later reference, and are typically things like to-day -> today.
What’s the approach to embedding fonts in standard ebooks’ epubs? Curious whether there’s a set of fonts that producers are allowed to embed in finished books, or whether there’s project consciously avoids embedding fonts, and if so why.
I tried to find a policy page on this via a standardebooks.org site search but nothing looked relevant.
I’m asking after realizing that some of my favorite books were books where the ebook had intentional font choices, for example different fonts for chapter titles vs body text, fonts that matched the vibe of the book (historical, more modern, etc.) It would be nice if more ebook readers made it easy to import more than the ~8 fonts they include by default but the next best thing is when the book itself includes a great font.
The ebooks we produce are entirely in the US public domain, including metadata and any other files. Unfortunately there are basically no good fonts released under the CC0 license. (Most open fonts are released under the OFL license, which is not the same.) Therefore we don't embed any font files, except for Standard Blackletter[1] when necessary, which is a font we developed especially for our use based on public domain specimens, and released via the CC0 license.
[1] https://github.com/standardebooks/standard-blackletter
>and I’m happy to answer any questions about Standard Ebooks.
When will they start assigning catalog numbers to each of their works in the way that Project Guteneberg does? I'd like a unique id per ebook and since you don't (for obvious reasons) use ISBNs, there's nothing really to be done. I can't use an OCLC id because Standard Ebooks aren't consistently listed in Worldcat, I can't use Bookbrainz or Open Library ids for the same reason.
It costs nothing and is a low-effort fix. It's been an industry (and library science) thing for decades or longer. Can Standard Ebooks finally stop the amateur hour crap?
I know you griped about this in a different thread, but we won't be doing that, sorry. You can uniquely identify an ebook and its version by using dc:identifier in combination with dcterms:modified in the metadata file. If you desperately need a filesystem-safe string then concatenate those two and sha it.
How did you get these ready for release on Public Domain Day without breaking copyright law during the production process? I am not a lawyer, so I have only a surface understanding.
I’m not based in the US and have no intention of travelling there, so I don’t count myself in much danger for US copyright law.
Regardless, my understanding of copyright is that people broadly get annoyed when you infringe by distribution. In this case the distribution didn’t happen until the copyright had expired. People preparing these projects for later launch do it purely on their own machines, and nothing arrives at Standard Ebooks until the day of release.
Do you plan to provide PDF ?
SE makes ebooks available in four formats: "compatible" epub; "advanced" epub; kobo-compatible ("kepub"); and kindle ("azw3"). No PDFs.
One of the SE editors experimented with turning SE ebooks into PDFs, though. See more about that here: https://groups.google.com/g/standardebooks/c/Xy2bwiexLeM/m/f...
I don't know their reasons but PDF is a rather problematic format so I suspect that's why.
You can run their EPUB through Pandoc to convert yourself, or put some effort in and setup your own Calibre instance which will do something similar when you ask it to.