[First Project] Demian by Herman Hesse

[Sasha]

Previously discussed here.

- Scans: https://catalog.hathitrust.org/Record/102954224

- Gutenberg: https://www.gutenberg.org/ebooks/74222

It would appear the translator wasn't listed anywhere in the book, but as Alex mentioned Wikipedia credits N.H. Priday. Not sure if we would need to find a primary source for the information.

Also, the original German edition was published under the pseudonym "Emil Sinclair". Should I include the information in the metadata somewhere?

[Alex Cabal]

Please send a link to your repo once you get started so we can assign
you a manager and reviewer. Note that the translator name should have
spaces between the initials. Thanks!

On 4/23/25 5:40 PM, Sasha wrote:
> Previously discussed here <https://groups.google.com/g/standardebooks/c/
> FHhmBKi0iSY/m/MAAE4JWABgAJ>.

> --
> You received this message because you are subscribed to the Google
> Groups "Standard Ebooks" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to standardebook...@googlegroups.com
> <mailto:standardebook...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/
> standardebooks/a2795b2c-a03a-4704-b3b0-a41d8480cd8en%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/a2795b2c-a03a-4704-
> b3b0-a41d8480cd8en%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Sasha]

Hi, apologies for the delay. A change in my work occurred earlier than I expected, so I've had to deal with that over the past few weeks. But now I'm free to start work on this production.

Project Repo: https://github.com/SashaPrawn/hermann-hesse_demian

A few questions about formatting the book:

1 - In the 'prologue' at the start, there is italicized text which is a quote of a passage in Chapter 5. Should I consider this an epigraph in the section header? If so, just to double check, I wouldn't need to add any citation to the text, right? I also considered formatting this with the <q> element since it is technically a thought of the narrator, but it doesn't seem very correct.

2 - In the manual, 7.2.8 says that a section without any header content should have ```margin-top: 8em```; but then 7.2.10.9 says that sections without any titles at all should have ```margin-top: 20vh```. Which rule should I give preference to? Maybe I'm just misunderstanding the manual, though.

3 - There are a few cases in the book where words will be wrapped in single quotes, though I am not entirely sure if they are being used for emphasis, ambiguity, or irony. One example is this sentence:  But you haven’t yet reached that point where one can see what is ‘permitted’ and what is really ‘taboo.’ In this case the quotes seem to be used to denote ambiguity in the definitions of permitted or taboo, since the discussion is rather philosophical.  But then again, it could also be just simple emphasis to highlight the concepts being discussed. Here's the paragraph in question: link. The single quotes are also used for the word 'sign' and 'personal' in other parts.

- Sasha

[Alex Cabal]

OK, Vince will manage this with Weijia reviewing.

Vince can you address these questions?

Additional note - you must use `se create-draft` with the `--translator`
flag to make sure the translator gets included in various boilerplate
files. If you haven't gotten far I would just recreate the repo from
scratch using that flag.

On 5/14/25 5:25 PM, Sasha wrote:
> Hi, apologies for the delay. A change in my work occurred earlier than I
> expected, so I've had to deal with that over the past few weeks. But now
> I'm free to start work on this production.
>
> Project Repo: https://github.com/SashaPrawn/hermann-hesse_demian
>
> A few questions about formatting the book:
>
> 1 - In the 'prologue' at the start, there is italicized text which is a
> quote of a passage in Chapter 5. Should I consider this an epigraph in
> the section header? If so, just to double check, I wouldn't need to add
> any citation to the text, right? I also considered formatting this with
> the <q> element since it is technically a thought of the narrator, but
> it doesn't seem very correct.
>
> 2 - In the manual, 7.2.8 says that a section without any header content
> should have ```margin-top: 8em```; but then 7.2.10.9 says that sections
> without any titles at all should have ```margin-top: 20vh```. Which rule
> should I give preference to? Maybe I'm just misunderstanding the manual,
> though.
>
> 3 - There are a few cases in the book where words will be wrapped in
> single quotes, though I am not entirely sure if they are being used for

> emphasis, ambiguity, or irony. One example is this sentence: /But you

> haven’t yet reached that point where one can see what is ‘permitted’ and

> what is really ‘taboo.’ /In this case the quotes seem to be used to

> denote ambiguity in the definitions of permitted or taboo, since the
> discussion is rather philosophical.  But then again, it could also be
> just simple emphasis to highlight the concepts being discussed. Here's

> the paragraph in question: link <https://github.com/SashaPrawn/hermann-
> hesse_demian/blob/182dc53a64182ea355780569770c4ab66a51c24e/src/epub/
> text/chapter-3.xhtml#L60>. The single quotes are also used for the word

> 'sign' and 'personal' in other parts.
>
> - Sasha
>
> On Wednesday, April 23, 2025 at 4:01:16 PM UTC-7 Alex Cabal wrote:
>
> Please send a link to your repo once you get started so we can assign
> you a manager and reviewer. Note that the translator name should have
> spaces between the initials. Thanks!
>
> On 4/23/25 5:40 PM, Sasha wrote:
> > Previously discussed here <https://groups.google.com/g/

> standardebooks/c/ <https://groups.google.com/g/standardebooks/c/>

> > FHhmBKi0iSY/m/MAAE4JWABgAJ>.
> >
> > - Scans: https://catalog.hathitrust.org/Record/102954224
> <https://catalog.hathitrust.org/Record/102954224>

> > - Gutenberg: https://www.gutenberg.org/ebooks/74222 <https://
> www.gutenberg.org/ebooks/74222>

> >
> > It would appear the translator wasn't listed anywhere in the
> book, but
> > as Alex mentioned Wikipedia credits N.H. Priday. Not sure if we
> would
> > need to find a primary source for the information.
> >
> > Also, the original German edition was published under the pseudonym
> > "Emil Sinclair". Should I include the information in the metadata
> somewhere?
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Standard Ebooks" group.
> > To unsubscribe from this group and stop receiving emails from it,
> send
> > an email to standardebook...@googlegroups.com
> > <mailto:standardebook...@googlegroups.com>.
> > To view this discussion visit https://groups.google.com/d/msgid/

> <https://groups.google.com/d/msgid/>
> > standardebooks/a2795b2c-a03a-4704-b3b0-
> a41d8480cd8en%40googlegroups.com <http://40googlegroups.com>
> > <https://groups.google.com/d/msgid/standardebooks/a2795b2c-
> a03a-4704- <https://groups.google.com/d/msgid/standardebooks/
> a2795b2c-a03a-4704->
> > b3b0-a41d8480cd8en%40googlegroups.com?
> utm_medium=email&utm_source=footer <http://40googlegroups.com?
> utm_medium=email&utm_source=footer>>.

>
> --
> You received this message because you are subscribed to the Google
> Groups "Standard Ebooks" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to standardebook...@googlegroups.com
> <mailto:standardebook...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/

> standardebooks/b2934fb5-5fd0-484b-a9a4-08dd1a6ad457n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/b2934fb5-5fd0-484b-
> a9a4-08dd1a6ad457n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Weijia Cheng]

Ok, I will review.

[Sasha]

Hi, I fixed the missing translator metadata, but just committed it on top of the existing repository rather create a new one. The changes are directly from `se create-draft`, so there shouldn't be problems with the svg layouts or missing metadata. I'll start proofreading the text in the meantime, but I won't commit the changes before finishing semantics.

[Alex Cabal]

That's fine!

> hesse_demian <https://github.com/SashaPrawn/hermann-hesse_demian>

> SashaPrawn/hermann- <https://github.com/SashaPrawn/hermann->
> > hesse_demian/blob/182dc53a64182ea355780569770c4ab66a51c24e/

> src/epub/
> > text/chapter-3.xhtml#L60>. The single quotes are also used
> for the word
> > 'sign' and 'personal' in other parts.
> >
> > - Sasha
> >
> > On Wednesday, April 23, 2025 at 4:01:16 PM UTC-7 Alex Cabal
> wrote:
> >
> > Please send a link to your repo once you get started so we
> can assign
> > you a manager and reviewer. Note that the translator name
> should have
> > spaces between the initials. Thanks!
> >
> > On 4/23/25 5:40 PM, Sasha wrote:
> > > Previously discussed here <https://groups.google.com/g/

> <https://groups.google.com/g/>
> > standardebooks/c/ <https://groups.google.com/g/

> standardebooks/c/ <https://groups.google.com/g/standardebooks/c/>>
> > > FHhmBKi0iSY/m/MAAE4JWABgAJ>.
> > >
> > > - Scans: https://catalog.hathitrust.org/Record/102954224
> <https://catalog.hathitrust.org/Record/102954224>

> > <https://catalog.hathitrust.org/Record/102954224 <https://

> catalog.hathitrust.org/Record/102954224>>
> > > - Gutenberg: https://www.gutenberg.org/ebooks/74222

> <https://www.gutenberg.org/ebooks/74222> <https://
> > www.gutenberg.org/ebooks/74222 <http://www.gutenberg.org/

> ebooks/74222>>
> > >
> > > It would appear the translator wasn't listed anywhere in the
> > book, but
> > > as Alex mentioned Wikipedia credits N.H. Priday. Not sure
> if we
> > would
> > > need to find a primary source for the information.
> > >
> > > Also, the original German edition was published under the
> pseudonym
> > > "Emil Sinclair". Should I include the information in the
> metadata
> > somewhere?
> > >
> > > --
> > > You received this message because you are subscribed to the
> Google
> > > Groups "Standard Ebooks" group.
> > > To unsubscribe from this group and stop receiving emails
> from it,
> > send
> > > an email to standardebook...@googlegroups.com
> > > <mailto:standardebook...@googlegroups.com>.
> > > To view this discussion visit https://groups.google.com/d/
> msgid/ <https://groups.google.com/d/msgid/>

> > <https://groups.google.com/d/msgid/ <https://
> groups.google.com/d/msgid/>>
> > > standardebooks/a2795b2c-a03a-4704-b3b0-
> > a41d8480cd8en%40googlegroups.com <http://40googlegroups.com>
> <http://40googlegroups.com <http://40googlegroups.com>>
> > > <https://groups.google.com/d/msgid/standardebooks/a2795b2c-

> <https://groups.google.com/d/msgid/standardebooks/a2795b2c->
> > a03a-4704- <https://groups.google.com/d/msgid/standardebooks/
> <https://groups.google.com/d/msgid/standardebooks/>
> > a2795b2c-a03a-4704->
> > > b3b0-a41d8480cd8en%40googlegroups.com

> <http://40googlegroups.com>?
> > utm_medium=email&utm_source=footer <http://40googlegroups.com
> <http://40googlegroups.com>?

> > utm_medium=email&utm_source=footer>>.
> >
> > --
> > You received this message because you are subscribed to the
> Google
> > Groups "Standard Ebooks" group.
> > To unsubscribe from this group and stop receiving emails from
> it, send
> > an email to standardebook...@googlegroups.com
> > <mailto:standardebook...@googlegroups.com>.
> > To view this discussion visit https://groups.google.com/d/

> msgid/ <https://groups.google.com/d/msgid/>
> > standardebooks/b2934fb5-5fd0-484b-
> a9a4-08dd1a6ad457n%40googlegroups.com <http://40googlegroups.com>
> > <https://groups.google.com/d/msgid/standardebooks/
> b2934fb5-5fd0-484b- <https://groups.google.com/d/msgid/
> standardebooks/b2934fb5-5fd0-484b->
> > a9a4-08dd1a6ad457n%40googlegroups.com?

> utm_medium=email&utm_source=footer <http://40googlegroups.com?
> utm_medium=email&utm_source=footer>>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Standard Ebooks" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to standardebook...@googlegroups.com
> <mailto:standardebook...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/

> standardebooks/2b17a7d7-dfc5-4f75-9508-bb478a53a3b5n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/2b17a7d7-
> dfc5-4f75-9508-bb478a53a3b5n%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

[Vince]

When you’re asking about the source, please provide links to the pertinent position in the scans. This is especially true in the case of #3—it’s the scans that need to be examined, not your text.

Alex, #2 is for you.

1. It definitely should be a blockquote, but I’m ambivalent about whether it should be an epigraph. It doesn’t seem to me to fit a true epigraph, especially since it’s from later in the book. I think I would just leave it as a plain blockquote (which you can use CSS to italicize).

2. That’s a really good question; I don’t think I’ve ever noticed 7.2.8 before. And I can’t make any sense of a distinction between the two; 7.2.8 specifically mentions not having epigraphs or other non-prose material and 7.2.10.9 doesn’t, but if the latter means that they could be present, it doesn’t make any sense to me to use less of a top margin when they are not present than when they could be. Alex will have to explain this one; they may just be an inconsistency that we’ve never caught. (I’ve always used 20vh, but as I said I don’t think I’ve ever noticed 7.2.8.)

3. They should be left as is, it’s not emphasis.

[Alex Cabal]

Re #2, looks like a duplicate snuck in. 8em is about 20vh for many
ereader aspect ratios. Use rule 7.2.10.9 in the current version of the
manual. In the next version that rule will be renumbered to 7.2.8.

On 5/15/25 3:00 PM, Vince wrote:
> When you’re asking about the source, please provide links to the
> pertinent position in the scans. This is especially true in the case of
> #3—it’s the scans that need to be examined, not your text.
>
> Alex, #2 is for you.
>
> 1. It definitely should be a blockquote, but I’m ambivalent about
> whether it should be an epigraph. It doesn’t seem to me to fit a true
> epigraph, especially since it’s from later in the book. I think I would
> just leave it as a plain blockquote (which you can use CSS to italicize).
>
> 2. That’s a really good question; I don’t think I’ve ever noticed 7.2.8
> before. And I can’t make any sense of a distinction between the two;
> 7.2.8 specifically mentions not having epigraphs or other non-prose
> material and 7.2.10.9 doesn’t, but if the latter means that they could

> be present, it doesn’t make any sense to me to use /less/ of a top

>> for emphasis, ambiguity, or irony. One example is this sentence: /But

>> you haven’t yet reached that point where one can see what is

>> ‘permitted’ and what is really ‘taboo.’/In this case the quotes seem

>> to be used to denote ambiguity in the definitions of permitted or
>> taboo, since the discussion is rather philosophical.  But then again,
>> it could also be just simple emphasis to highlight the concepts being

>> discussed. Here's the paragraph in question:link <https://github.com/
>> SashaPrawn/hermann-hesse_demian/
>> blob/182dc53a64182ea355780569770c4ab66a51c24e/src/epub/text/
>> chapter-3.xhtml#L60>. The single quotes are also used for the word

>> 'sign' and 'personal' in other parts.
>

> --
> You received this message because you are subscribed to the Google
> Groups "Standard Ebooks" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to standardebook...@googlegroups.com
> <mailto:standardebook...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/

> standardebooks/75665ED8-DC8F-428F-9511-7AA8524A3989%40letterboxes.org
> <https://groups.google.com/d/msgid/standardebooks/75665ED8-
> DC8F-428F-9511-7AA8524A3989%40letterboxes.org?
> utm_medium=email&utm_source=footer>.

[Sasha]

Thank you Vince and Alex for helping with those questions. I would have responded earlier, but I thought it best to wait until I finished proofreading the text (although, I may need to do a second pass-through to find typos since I mostly used the scans to locate possible semantic issues).

I have a few more questions about semantics/typography in the text:

1. On page 14, the phrase "O dear" is used twice. Should the O here be considered an apostrophe and left as is? Or is the phrase just an older spelling of the phrase "Oh dear" which should be corrected as an editorial edit? Or maybe the 'O' is being used as shortened version of 'Oh', and a single quotation mark should be added afterwards to form O' dear? The last option doesn't feel right, but I thought I should include it just in case.

2. On page 46, Demian is speaking to the narrator and mentions a "the boy S." You can easily infer Demian is referring to the protagonist Sinclair, but avoiding using his name to speak in the third person, and somewhat in a hypothetical, about a situation that's occurring to the protagonist. Since the abbreviation is being used indirectly and its meaning needs to be (lightly) inferred, should it still be marked as a "given-name" abbreviation, or something different?

3. On page 71, Demian speaks about the initial of his name directly ("... he knows my name is Demian ..., whose initial is D"). Is the 'D' here a grapheme, or an abbreviation of the name? Maybe both? In the same sentence, Demian also says "... sitting among the S's", referring to him sitting in a section of a classroom where the desks are ordered alphabetically. This I believe is a grapheme, but plural. Rule 8.2.8.2.2 seems to suggest grapheme plurals are an exception which shouldn't be italicized, but the rule doesn't include a description other than a single example. Could the description for this rule be missing?

4. On page 79, there's some text wrapped around em-dashes and quotes: ⁠[ —“perfect seriousness”⁠— ]. The narrator here is referring to something he has just written down, since the book is structured as if the author is the narrator. Should I leave this text as it is, or is there anything I should change about it typographically?

5. On page 129, there is a quote within and at the end of another quote, so it ends like a period followed by a single closing quotation mark, followed by a double closing quotation mark (with a hairspace in between). Just wanted to check here that the period is placed appropriately inside the inner quote, rather than outside of it but still inside the outer quote (so in between the single and double closing quotation marks).

6. Would removing the umlauts for the words zoölogy and Zürich be an editorial edit, or as a typography edit similar to what is done with ligatures?

I also found some words which may have outdated spelling, but I'll ask about them later after finishing semantics/typography.

[Sasha]

Sorry, just realized I forgot to link the pages like I intended. Here they are for each question:

1. https://babel.hathitrust.org/cgi/pt?id=pur1.32754063251692&seq=26

2. https://babel.hathitrust.org/cgi/pt?id=pur1.32754063251692&seq=58

3. https://babel.hathitrust.org/cgi/pt?id=pur1.32754063251692&seq=83

4. https://babel.hathitrust.org/cgi/pt?id=pur1.32754063251692&seq=91

5. https://babel.hathitrust.org/cgi/pt?id=pur1.32754063251692&seq=141

[Vince]

1. Leave them as is.
2. Abbreviations of names are tagged as abbreviations of names, regardless of the circumstance.
3. Here it’s not an initial, it’s a letter, indicating the letter the name starts with, which makes it a grapheme.
4. As is.
5. In US English, periods and commas go within all quotes. Leave it as is.
6. I would probably consider it editorial, but do them in a separate commit so it’s easy to change if need be.

[Sasha]

Thank you for the help. Sorry for sporadically working on this project, but I've been having trouble managing my free time after work. I also took some time to clean my commit history since I had missed typography fixes before adding semantics, so I'll be force pushing those changes soon.

Here are the questions I have right now:

1. How are plural grapheme semantics/formatting structured? I assume it is the same as phonemes, but I want to verify since it isn't explicit in the manual. Also, I would update the wording of rule 8.2.8.2.2 since it isn't clear whether the example is referring to the phrase itself (one's p's and q's) or the particular grapheme structure, especially if you haven't heard that phrase before.

2.  Should "slaughter house" be changed to "slaughterhouse"? (page, second paragraph, line 9) (dictionary)

3. Should "sale yard" be changed to "saleyard"? (page, last paragraph, line 8) (dictionary)

I'll also begin looking for appropriate artwork for this project. I'll try SE's artwork database first, but ideally I can find something directly related to the book.

[Vince]

1. Your assumption is correct.

2/3. See the “Manual spelling changes” section at the end of step 15 in the Step by Step guide. We generally don’t mess with compound words except what modernize spelling already adjusts.

[Sasha]

I found what seems to be a suitable cover for the book. It's "Hawk's Nest" by Bruno Liljefors. I'm fairly sure the reproduction isn't an etching because both contain exactly the same signature (or at least, it appears that way).

- HQ: https://artvee.com/dl/hawks-nest/#00

- Reproduction Scan: https://hdl.handle.net/2027/nyp.33433105078624?urlappend=%3Bseq=149%3Bownerid=118965847-163

I think this painting suits the book quite well. Part of the plot is connected to a crest with a hawk on it, which later urges the protagonist to paint a similar bird coming out of a an egg. Originally I wanted a painting of an egg hatching to be the cover, but I couldn't find anything suitable.

[Vince]

A tentative OK, but please do a mockup so we see what it looks like cropped and with the title bar on it.

[Vince]

Also, you may have already seen it, and of course you would need PD proof, but the Hawk and Black-Game on his Wiki page is perhaps a more striking image of a hawk. Up to you, I just saw it when I was browsing him.

[Sasha]

Thanks for the suggestion! I think did see that one while browsing the book scans, though at a very poor resolution. I'll make a mock-up of it too (once I find the reproduction), since in the book they repeat a few times that the bird coming out of the egg will destroy the world, so the violence might fit in. We can then discuss which one looks nicer.

[Sasha]

I'm attaching here the mockups for both covers, please let me know what you think. One note though, in the second image the artist's signature is visible but partially cut-off, so it looks odd if you focus on the bottom left corner. I can't really fix it without partially cutting off the black bird or the hawk.

Also one question: when including the raw image file, does it necessarily need to be in jpeg format, or converted to it? The highest quality images I got for both of these came from Wikimedia in tiff format and are quite large.

[Vince]

Did you find PD proof for the first one?

I haven’t read the story, so it’s totally your choice, provided you have PD proof for both. Let me know which you prefer, and I’ll add it to the database.

The source image does not have to be .jpg (see SEMoS 10.3, specifically 10.3.3.5), and the 25MB or so of at least the first image is fine. (I didn’t see the second one in Wikimedia.)

[Sasha]

Here is the PD proof of the first cover: link.

I've decided to use the second one as the cover, though. Here is its Wikimedia page: link. This one is around 100mb, so it might be too big for the repo. Let me know if a png or jpeg would be better.

As a side note, Bruno Liljefors seems to have a ton of very good nature paintings. It might be a good idea to put the book I'm using as a candidate to have indexed for the art archive.

[Vince]

That’s just a link to the book, we need a link to the page# where the illustration appears, please.

I know there’s a limit on GitHub, but I don’t know what it is. It’s larger than our artwork database, though, so I’ll have to convert it to jpg for that, anyway.

[Sasha]

Whoops, I copied the wrong link. Here is the correct one: link. I'll try uploading the tiff to GitHub, and convert it to something else if it's rejected.

[Sasha]

Hello! Sorry for being away for some time, but I've finally finished the pending changes needed before final review (the metadata was the only thing pending). Here is my GitHub repo again for reference: https://github.com/SashaPrawn/hermann-hesse_demian_n-h-priday.

The one thing that may need some improving is the long description. I think it mostly summarizes the themes of the book, but the wording sounds a bit off (I've never been the best writer =P).  Any suggestions to improve it (and maybe the short description too) are welcome. Also, word count and reading ease are filled in just before publication, right? I can also take care of them on my end if needed.

[Alex Cabal]

Weijia you're up for review on this one

On 9/1/25 12:32 AM, Sasha wrote:
> Hello! Sorry for being away for some time, but I've finally finished the
> pending changes needed before final review (the metadata was the only
> thing pending). Here is my GitHub repo again for reference: https://

> github.com/SashaPrawn/hermann-hesse_demian_n-h-priday <https://
> github.com/SashaPrawn/hermann-hesse_demian_n-h-priday>.

>
> The one thing that may need some improving is the long description. I
> think it mostly summarizes the themes of the book, but the wording
> sounds a bit off (I've never been the best writer =P).  Any suggestions
> to improve it (and maybe the short description too) are welcome. Also,
> word count and reading ease are filled in just before publication,
> right? I can also take care of them on my end if needed.
> On Monday, June 16, 2025 at 10:03:36 PM UTC-7 Sasha wrote:
>
> Whoops, I copied the wrong link. Here is the correct one: link

> <https://hdl.handle.net/2027/nyp.33433105078624?
> urlappend=%3Bseq=153%3Bownerid=118965847-167>. I'll try uploading

> the tiff to GitHub, and convert it to something else if it's rejected.
>
> On Monday, June 16, 2025 at 9:17:50 PM UTC-7 Vince wrote:
>
> That’s just a link to the book, we need a link to the page#
> where the illustration appears, please.
>
> I know there’s a limit on GitHub, but I don’t know what it is.
> It’s larger than our artwork database, though, so I’ll have to
> convert it to jpg for that, anyway.
>
>
>> On Jun 16, 2025, at 11:09 PM, Sasha <sasha...@gmail.com> wrote:
>>

>> Here is the PD proof of the first cover: link <https://
>> hdl.handle.net/2027/nyp.33433105078624>.

>>
>> I've decided to use the second one as the cover, though. Here

>> is its Wikimedia page: link <https://commons.wikimedia.org/
>> wiki/File:Hawk's_Nest_(Bruno_Liljefors)_-
>> _Gothenburg_Museum_of_Art_-_F_88.tif>. This one is around

>> 100mb, so it might be too big for the repo. Let me know if a
>> png or jpeg would be better.
>>
>> As a side note, Bruno Liljefors seems to have a ton of very
>> good nature paintings. It might be a good idea to put the book
>> I'm using as a candidate to have indexed for the art archive.
>

> --
> You received this message because you are subscribed to the Google
> Groups "Standard Ebooks" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to standardebook...@googlegroups.com
> <mailto:standardebook...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/

> standardebooks/424184d9-fb50-4f24-9a9f-6a6e3fd862d4n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/424184d9-
> fb50-4f24-9a9f-6a6e3fd862d4n%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

[Weijia Cheng]

Yes--thanks for the reminder. I'll try and get on it within a day or two.

[Weijia Cheng]

Hi Sasha, can you make sure to update your toolset and fix all of the issues from se lint first?

[Sasha]

Hi Weijia, thanks for the review! Sorry about the lint errors, I didn't realize "se lint" stopped running when it couldn't read a file. In MacOS, we get those annoying .DS_Store files added to directories which are hidden to a lot of applications. I removed them, so now I can address the errors that pop up. I'll leave a reply here once I'm done.

Alex, would it be a good idea to manually ignore .DS_Store files in MacOS? Or at least keep running the command when a file can't be read, with a warning printed out?

[Sasha]

Hello Weijia, I added a new commit which fixes all problems reported by "se lint." Should be ready for review now.

[Alex Cabal]

The tools should at least crash if a file can't be read. I believe lint
does warn you about .DS_Store files but I can't exactly remember right
now. Not everyone uses Mac, and in any case a good file manager should
not leave metadata file litter in every directory it touches.

> <http://github.com/SashaPrawn/hermann-hesse_demian_n-h-
> priday> <https://
> > github.com/SashaPrawn/hermann-hesse_demian_n-h-priday
> <http://github.com/SashaPrawn/hermann-hesse_demian_n-h-

> priday>>.
> >
> > The one thing that may need some improving is the long
> description. I
> > think it mostly summarizes the themes of the book, but
> the wording
> > sounds a bit off (I've never been the best writer =P).
> Any suggestions
> > to improve it (and maybe the short description too) are
> welcome. Also,
> > word count and reading ease are filled in just before
> publication,
> > right? I can also take care of them on my end if needed.
> > On Monday, June 16, 2025 at 10:03:36 PM UTC-7 Sasha wrote:
> >
> > Whoops, I copied the wrong link. Here is the correct one:
> link

> > <https://hdl.handle.net/2027/nyp.33433105078624 <https://
> hdl.handle.net/2027/nyp.33433105078624>?

> > urlappend=%3Bseq=153%3Bownerid=118965847-167>. I'll try
> uploading
> > the tiff to GitHub, and convert it to something else if
> it's rejected.
> >
> > On Monday, June 16, 2025 at 9:17:50 PM UTC-7 Vince wrote:
> >
> > That’s just a link to the book, we need a link to the page#
> > where the illustration appears, please.
> >
> > I know there’s a limit on GitHub, but I don’t know what
> it is.
> > It’s larger than our artwork database, though, so I’ll
> have to
> > convert it to jpg for that, anyway.
> >
> >
> >> On Jun 16, 2025, at 11:09 PM, Sasha <sasha...@gmail.com>
> wrote:
> >>
> >> Here is the PD proof of the first cover: link <https://

> >> hdl.handle.net/2027/nyp.33433105078624 <http://

> hdl.handle.net/2027/nyp.33433105078624>>.
> >>
> >> I've decided to use the second one as the cover, though.
> Here
> >> is its Wikimedia page: link <https://

> commons.wikimedia.org/ <https://commons.wikimedia.org/>

> >> wiki/File:Hawk's_Nest_(Bruno_Liljefors)_-
> >> _Gothenburg_Museum_of_Art_-_F_88.tif>. This one is around
> >> 100mb, so it might be too big for the repo. Let me know
> if a
> >> png or jpeg would be better.
> >>
> >> As a side note, Bruno Liljefors seems to have a ton of very
> >> good nature paintings. It might be a good idea to put
> the book
> >> I'm using as a candidate to have indexed for the art
> archive.
> >
> > --
> > You received this message because you are subscribed to
> the Google
> > Groups "Standard Ebooks" group.
> > To unsubscribe from this group and stop receiving emails
> from it, send
> > an email to standardebook...@googlegroups.com
> > <mailto:standardebook...@googlegroups.com>.
> > To view this discussion visit https://groups.google.com/

> d/msgid/ <https://groups.google.com/d/msgid/>
> > standardebooks/424184d9-
> fb50-4f24-9a9f-6a6e3fd862d4n%40googlegroups.com
> <http://40googlegroups.com>
> > <https://groups.google.com/d/msgid/
> standardebooks/424184d9- <https://groups.google.com/d/msgid/
> standardebooks/424184d9->
> > fb50-4f24-9a9f-6a6e3fd862d4n%40googlegroups.com

> <http://40googlegroups.com>?
> > utm_medium=email&utm_source=footer>.
>

> --
> You received this message because you are subscribed to the Google
> Groups "Standard Ebooks" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to standardebook...@googlegroups.com
> <mailto:standardebook...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/

> standardebooks/8c710570-5fa4-4109-ab07-6db81b4adaa7n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/8c710570-5fa4-4109-
> ab07-6db81b4adaa7n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Bob R. Kenyon]

The step-by-step instructions are very clear about dealing with .DS_store files, and even supply a regex you can use to nuke them.

If you’re careful about staying out of those directories with an open window in the Finder, you won’t get them, but that’s hard sometimes.

Bob

> To unsubscribe from this group and stop receiving emails from it, send an email to standardebook...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/standardebooks/facb9eed-2e9b-4917-978f-32ac854a686f%40standardebooks.org.
>

[Vince]

Every Mac user, or at least every Mac SE user, should have an alias/function to kill them. As Bob pointed out, the command to do is in the Step by Step.

Lint doesn’t crash, it exits gracefully with a “Couldn’t read file” with the filename, which is the time to invoke the above alias/command.

[Sasha]

Thanks for the insight everyone!

On my end, I do agree that it is usually fairly simple to deal with the problem; you can just run find or something similar, and use .gitignore for repositories. Though in the case of lint, it seems unnecessary for the whole program to stop running when the error is easily recoverable from, even with other unreadable files like thumbs.db on windows. Especially since these files are technically an annoyance you can never get rid of due to Finder/Explorer being baked into the OS. Even in build-manifest and build-spine, I think it would make more sense to automatically ignore these type of files in the toolset rather than letting them seep their way into an epub accidentally, user error notwithstanding (also, not sure if this is how the tools currently behave, just going based on the current step-by-step guide).

I mean, there is a reason why git allows you to have a .gitignore file rather than tell users "you deal with it". It's nice to have the convenience be included in the tool rather than set up a solution on your end. Maybe the toolset could have its own global ignore file, if you want to avoid hardcoding these exceptions? Or at least we could do with some additional text at the end of lint's output that says "failed to run successfully" or similar since the tool is supposed to find errors, and getting an error message is technically expected unless you already know what the correct formatting looks like (Honestly, I forgot about the formatting since I hadn't worked on this for a while).

But then again, I don't really need any of these changes since I know about the issue now (and will be switching to a Linux machine soon, regardless). Mostly thinking about general usability in the future.

[Weijia Cheng]

I just filed a review. Great work on your first project! Most of my points are very minor but there is one small issue that requires a rebase. Rebasing can be hard if you don't have a lot of practice with it so please reach out if you have questions or need resources (or even a step by step guide).