[Next Project] Dark Princess by W.E.B. Du Bois

449 views
Skip to first unread message

Cecil New

unread,
Jun 26, 2025, 11:57:00 AM6/26/25
to Standard Ebooks
I was thinking of this for my next project, but it does have some differences...

Query for scans: https://archive.org/search?query=title%3A%28dark%20princess%29%20AND%20creator%3A%28Du%20Bois%2C%20W.%20E.%20B.%29


This query shows 5 scans.


The “most wanted page” links to https://en.wikisource.org/wiki/Dark_Princess 


There are no transcriptions on Project Gutenberg


This would only be my third effort - Is this suitable or should I look for something else?

Hendrik Kaiber

unread,
Jun 26, 2025, 12:01:09 PM6/26/25
to Standard Ebooks

Alex will be the one to tell you if this is appropriate, but I would like to point out that Wikisource lists this LoC scan as the source for the transcription, so I assume you would use it.

--Hendrik

Alex Cabal

unread,
Jun 26, 2025, 12:56:42 PM6/26/25
to standar...@googlegroups.com
Wikisource is fine as a source. As Hendrik pointed out you can use the
LoC page scans. Please send a link to your repo once you start.

On 6/26/25 10:57 AM, Cecil New wrote:
> I was thinking of this for my next project, but it does have some
> differences...
>
> Query for scans: https://archive.org/search?
> query=title%3A%28dark%20princess%29%20AND%20creator%3A%28Du%20Bois%2C%20W.%20E.%20B.%29 <https://archive.org/search?query=title%3A%28dark%20princess%29%20AND%20creator%3A%28Du%20Bois%2C%20W.%20E.%20B.%29>
>
>
> This query shows 5 scans.
>
> *
>
> One is audio
>
> *
>
> Two are “borrow unavailable”
>
> *
>
> One is “borrowable” https://archive.org/details/
> darkprincessroma0000dubo_n6y2 <https://archive.org/details/
> darkprincessroma0000dubo_n6y2>
>
> *
>
> One is not actually the book itself, but is about the author.
>
>
> The “most wanted page” links to https://en.wikisource.org/wiki/
> Dark_Princess <https://en.wikisource.org/wiki/Dark_Princess>
>
>
> There are no transcriptions on Project Gutenberg!
>
>
> This would only be my third effort - Is this suitable or should I look
> for something else?
>
> --
> 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/ed05e3ef-e4fb-46dc-a5dc-2c37fe8ffffdn%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/ed05e3ef-e4fb-46dc-
> a5dc-2c37fe8ffffdn%40googlegroups.com?utm_medium=email&utm_source=footer>.

Cecil New

unread,
Jun 27, 2025, 9:57:26 AM6/27/25
to Standard Ebooks
Link: https://github.com/mandolyte/william-edward-burghardt-du-bois_dark-princess

Note that this book is in parts with a different naming convention for the file parts. I did a bit of renaming and cleanup to conform to https://standardebooks.org/manual/1.8.2/single-page#2.2.4.2.

But there is still a lot of work to do for "Step 7 Split the source text at logical divisions"

I'd like to crop and use the existing cover at https://en.wikisource.org/wiki/Dark_Princess ... as long as it upscales OK. It is a JPEG file 500x723 (uncropped).

Alex Cabal

unread,
Jun 27, 2025, 10:02:28 AM6/27/25
to standar...@googlegroups.com
OK, Emma will manage this with Vince reviewing.

On 6/27/25 8:57 AM, Cecil New wrote:
> Link: https://github.com/mandolyte/william-edward-burghardt-du-
> bois_dark-princess
>
> Note that this book is in parts with a different naming convention for
> the file parts. I did a bit of renaming and cleanup to conform
> to https://standardebooks.org/manual/1.8.2/single-page#2.2.4.2.
>
> But there is still a lot of work to do for "Step 7 Split the source text
> at logical divisions"
>
> I'd like to crop and use the existing cover at https://
> en.wikisource.org/wiki/Dark_Princess ... as long as it upscales OK. It
> is a JPEG file 500x723 (uncropped).
>
> On Thursday, June 26, 2025 at 12:56:42 PM UTC-4 Alex Cabal wrote:
>
> Wikisource is fine as a source. As Hendrik pointed out you can use the
> LoC page scans. Please send a link to your repo once you start.
>
> On 6/26/25 10:57 AM, Cecil New wrote:
> > I was thinking of this for my next project, but it does have some
> > differences...
> >
> > Query for scans: https://archive.org/search <https://archive.org/
> search>?
> >
> query=title%3A%28dark%20princess%29%20AND%20creator%3A%28Du%20Bois%2C%20W.%20E.%20B.%29 <https://archive.org/search?query=title%3A%28dark%20princess%29%20AND%20creator%3A%28Du%20Bois%2C%20W.%20E.%20B.%29 <https://archive.org/search?query=title%3A%28dark%20princess%29%20AND%20creator%3A%28Du%20Bois%2C%20W.%20E.%20B.%29>>
> >
> >
> > This query shows 5 scans.
> >
> > *
> >
> > One is audio
> >
> > *
> >
> > Two are “borrow unavailable”
> >
> > *
> >
> > One is “borrowable” https://archive.org/details/ <https://
> archive.org/details/>
> > darkprincessroma0000dubo_n6y2 <https://archive.org/details/
> <https://archive.org/details/>
> > darkprincessroma0000dubo_n6y2>
> >
> > *
> >
> > One is not actually the book itself, but is about the author.
> >
> >
> > The “most wanted page” links to https://en.wikisource.org/wiki/
> <https://en.wikisource.org/wiki/>
> > Dark_Princess <https://en.wikisource.org/wiki/Dark_Princess
> <https://en.wikisource.org/wiki/Dark_Princess>>
> >
> >
> > There are no transcriptions on Project Gutenberg!
> >
> >
> > This would only be my third effort - Is this suitable or should I
> look
> > for something else?
> >
> > --
> > 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/ed05e3ef-e4fb-46dc-
> a5dc-2c37fe8ffffdn%40googlegroups.com <http://40googlegroups.com>
> > <https://groups.google.com/d/msgid/standardebooks/ed05e3ef-
> e4fb-46dc- <https://groups.google.com/d/msgid/standardebooks/
> ed05e3ef-e4fb-46dc->
> > a5dc-2c37fe8ffffdn%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/8427c075-3d87-484a-be14-295b78c886a3n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/8427c075-3d87-484a-
> be14-295b78c886a3n%40googlegroups.com?utm_medium=email&utm_source=footer>.

Emma Sweeney

unread,
Jun 27, 2025, 11:59:09 AM6/27/25
to Standard Ebooks
For this production you'll have four files named `part-#.xhtml`. In each file, the short sections should be placed in their own <section> elements with `z3998:subchapter` semantics. See the example in SEMoS 5.1.2.8.

Unfortunately, the original cover won't work. It is obvious that it is a print and not in the fine art oil painting
style.


Emma

Alex Cabal

unread,
Jun 27, 2025, 12:01:09 PM6/27/25
to standar...@googlegroups.com
I think if we cropped it, it would look acceptable.

On 6/27/25 10:59 AM, Emma Sweeney wrote:
> For this production you'll have four files named `part-#.xhtml`. In each
> file, the short sections should be placed in their own <section>
> elements with `z3998:subchapter` semantics. See the example in SEMoS
> 5.1.2.8 <https://standardebooks.org/manual/1.8.2/single-page#5.1.2.8>.
>
> Unfortunately, the original cover won't work. It is obvious that it is a
> print and not in the fine art oil painting
> style.
>
>
> Emma
> On Friday, June 27, 2025 at 10:02:28 AM UTC-4 Alex Cabal wrote:
>
> OK, Emma will manage this with Vince reviewing.
>
> On 6/27/25 8:57 AM, Cecil New wrote:
> > Link: https://github.com/mandolyte/william-edward-burghardt-du-
> <https://github.com/mandolyte/william-edward-burghardt-du->
> > bois_dark-princess
> >
> > Note that this book is in parts with a different naming
> convention for
> > the file parts. I did a bit of renaming and cleanup to conform
> > to https://standardebooks.org/manual/1.8.2/single-page#2.2.4.2
> <https://standardebooks.org/manual/1.8.2/single-page#2.2.4.2>.
> >
> > But there is still a lot of work to do for "Step 7 Split the
> source text
> > at logical divisions"
> >
> > I'd like to crop and use the existing cover at https://
> > en.wikisource.org/wiki/Dark_Princess <http://en.wikisource.org/
> wiki/Dark_Princess> ... as long as it upscales OK. It
> > is a JPEG file 500x723 (uncropped).
> >
> > On Thursday, June 26, 2025 at 12:56:42 PM UTC-4 Alex Cabal wrote:
> >
> > Wikisource is fine as a source. As Hendrik pointed out you can
> use the
> > LoC page scans. Please send a link to your repo once you start.
> >
> > On 6/26/25 10:57 AM, Cecil New wrote:
> > > I was thinking of this for my next project, but it does have some
> > > differences...
> > >
> > > Query for scans: https://archive.org/search <https://
> archive.org/search> <https://archive.org/ <https://archive.org/>
> > search>?
> > >
> >
> query=title%3A%28dark%20princess%29%20AND%20creator%3A%28Du%20Bois%2C%20W.%20E.%20B.%29 <https://archive.org/search?query=title%3A%28dark%20princess%29%20AND%20creator%3A%28Du%20Bois%2C%20W.%20E.%20B.%29 <https://archive.org/search?query=title%3A%28dark%20princess%29%20AND%20creator%3A%28Du%20Bois%2C%20W.%20E.%20B.%29> <https://archive.org/search?query=title%3A%28dark%20princess%29%20AND%20creator%3A%28Du%20Bois%2C%20W.%20E.%20B.%29 <https://archive.org/search?query=title%3A%28dark%20princess%29%20AND%20creator%3A%28Du%20Bois%2C%20W.%20E.%20B.%29>>>
> > >
> > >
> > > This query shows 5 scans.
> > >
> > > *
> > >
> > > One is audio
> > >
> > > *
> > >
> > > Two are “borrow unavailable”
> > >
> > > *
> > >
> > > One is “borrowable” https://archive.org/details/ <https://
> archive.org/details/> <https://
> > archive.org/details/ <http://archive.org/details/>>
> > <https://groups.google.com/d/msgid/ <https://groups.google.com/d/
> msgid/>>
> > > standardebooks/ed05e3ef-e4fb-46dc-
> > a5dc-2c37fe8ffffdn%40googlegroups.com <http://40googlegroups.com>
> <http://40googlegroups.com <http://40googlegroups.com>>
> > > <https://groups.google.com/d/msgid/standardebooks/ed05e3ef-
> > > a5dc-2c37fe8ffffdn%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/8427c075-3d87-484a-
> be14-295b78c886a3n%40googlegroups.com <http://40googlegroups.com>
> > <https://groups.google.com/d/msgid/
> standardebooks/8427c075-3d87-484a- <https://groups.google.com/d/
> msgid/standardebooks/8427c075-3d87-484a->
> > be14-295b78c886a3n%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/2d7d4c55-8362-4830-925f-e3b0b826ddabn%40googlegroups.com
> <https://groups.google.com/d/msgid/
> standardebooks/2d7d4c55-8362-4830-925f-e3b0b826ddabn%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

Cecil New

unread,
Jun 27, 2025, 4:39:16 PM6/27/25
to Standard Ebooks

I have a question or two... this is how part 1 begins: https://en.wikisource.org/wiki/Dark_Princess/Part_1 

(The scan is similar).


Here is the bit from SEMoS 5.1.2.8:

<section id="chapter-1" epub:type="chapter">

<header>

<h2 epub:type="title">...</h2>

<p epub:type="bridgehead">...</p>

</header>

<p id="chapter-1-p-2">...</p>

<section id="chapter-1-1" epub:type="z3998:subchapter">

<p>...</p>



Then for part 1 the title is “THE EXILE”.

The bridgehead would be something like:

<p epub:type="bridgehead"><i>August, 1923</i></p>

<p><i>Summer is come with bursting flower and promise of perfect fruit. Rain is rolling down Nile and Niger. Summer sings on the sea where giant ships carry busy worlds, while mermaids swarm the shores. Earth is pregnant. Life is big with pain and evil and hope. Summer in blue New York; summer in gray Berlin; summer in the red heart of the world!</i></p>


What I don’t see is:

  • Where the text “Part I” will come from

  • Where the Roman numeral “I” (and the subsequent ones) will come from


Thanks!

Emma Sweeney

unread,
Jun 27, 2025, 7:29:20 PM6/27/25
to Standard Ebooks
  • Part Titles: See SEMoS 7.2.10.6.
  • Bridgeheads: See SEMoS 7.2.11. Both "August, 1923" and "Summer is come with bursting flower..." are bridgeheads. You can structure them like:
<div epub:type="bridgehead">
<p>August, 1923.</p>
<p>Summer is come with bursting flower and promise of perfect fruit. Rain is rolling down Nile and Niger. Summer sings on the sea where giant ships carry busy worlds, while mermaids swarm the shores. Earth is pregnant. Life is big with pain and evil and hope. Summer in blue New York; summer in gray Berlin; summer in the red heart of the world!</p>
</div>
  • Section Titles: See SEMoS 7.2.10.8. The section headers are inside each subchapter <section> element.

Emma

Cecil New

unread,
Jun 28, 2025, 9:25:17 AM6/28/25
to Standard Ebooks
Thanks! Before I get too far along, can you check the below for the part 1 (sub)chapter 1? 

Also, I see that both the wikisource and scans use small caps for the first word(s) of the first chapter of each part, but not the remaining subchapters. But I don't think that practice is part of the standard style. Correct?

<section id="part-1" epub:type="part">

<hgroup>
<h2>
<span epub:type="label">Part</span>
<span epub:type="ordinal z3998:roman">I</span>
</h2>
<p epub:type="title">The Exile</p>
</hgroup>


<div epub:type="bridgehead">
<p>August, 1923.</p>
<p>Summer is come with bursting flower and promise of perfect fruit. Rain is rolling down Nile and Niger. Summer sings on the sea where giant ships carry busy worlds, while mermaids swarm the shores. Earth is pregnant. Life is big with pain and evil and hope. Summer in blue New York; summer in gray Berlin; summer in the red heart of the world!</p>
</div>

<section id="chapter-1-1" epub:type="z3998:subchapter">
<h2 epub:type="ordinal z3998:roman">I</h2>

<p>Matthew Towns was in a cold white fury. He stood on the deck of the <i epub:type="se:name.vessel.ship">Orizaba</i> looking down on the flying sea. In the night America had disappeared and now there was nothing but waters heaving in the bright morning. There were many passengers walking, talking, laughing; but none of them spoke to Matthew. They spoke about him, noting his tall, lean form and dark brown face, the stiff, curled mass of his sinewy hair, and the midnight of his angry eyes.</p>

<!-- elided -->

</section>

<section id="chapter-1-2" epub:type="z3998:subchapter">
<h2 epub:type="ordinal z3998:roman">II</h2>

Emma Sweeney

unread,
Jun 28, 2025, 9:48:16 AM6/28/25
to Standard Ebooks
  • The file section semantics should be `<section id="part-1" epub:type="chapter">`.
  • The part title and bridgeheads should be in a `<header>` element. See SEMoS 7.2.11.
  • The subchapter titles should be formatted like in SEMoS 7.2.10.8, because they do not appear in the ToC.
  • Correct. Remove styling for the first word.

Emma

Cecil New

unread,
Jun 28, 2025, 11:25:04 AM6/28/25
to Standard Ebooks
Thanks! I now have this structure for part-1. If I missed anything, let me know.

<section id="part-1" epub:type="chapter">

<header>
<h2>
<span epub:type="label">Part</span>
<span epub:type="ordinal z3998:roman">I</span>
</h2>
<p epub:type="title">The Exile</p>
</header>

<div epub:type="bridgehead">
<p>August, 1923.</p>
<p>Summer is come with bursting flower and promise of perfect fruit. Rain is rolling down Nile and Niger. Summer sings on the sea where giant ships carry busy worlds, while mermaids swarm the shores. Earth is pregnant. Life is big with pain and evil and hope. Summer in blue New York; summer in gray Berlin; summer in the red heart of the world!</p>
</div>

<section id="chapter-1-1" epub:type="z3998:subchapter">
<header epub:type="ordinal z3998:roman">I</header>
</section>

<section id="chapter-1-2" epub:type="z3998:subchapter">
<header epub:type="ordinal z3998:roman">II</header>
</section>

<section id="chapter-1-3" epub:type="z3998:subchapter">
<header epub:type="ordinal z3998:roman">III</header>
</section>

<section id="chapter-1-4" epub:type="z3998:subchapter">
<header epub:type="ordinal z3998:roman">IV</header>
</section>

<section id="chapter-1-5" epub:type="z3998:subchapter">
<header epub:type="ordinal z3998:roman">V</header>
</section>

<section id="chapter-1-6" epub:type="z3998:subchapter">
<header epub:type="ordinal z3998:roman">VI</header>
</section>

<section id="chapter-1-7" epub:type="z3998:subchapter">
<header epub:type="ordinal z3998:roman">VII</header>
</section>
</section>


Emma Sweeney

unread,
Jun 28, 2025, 8:06:24 PM6/28/25
to Standard Ebooks
  • The parts title is missing the <hgroup> element.
  • Bridgeheads should also be in the <header> element.
  • Subchapter <header>s need a <p> element.
Running `se lint` can also help you figure out what is wrong with your structuring.


Emma

Cecil New

unread,
Jun 30, 2025, 9:50:46 AM6/30/25
to Standard Ebooks
Quick question... The LoC transcription has a mistake... it omits subchapter II from Part II. Of course, it is ok in the scan. My question:

Should I tag my correction with [Editorial] in this case? Or just keep with all the other clean up I'm doing?

Cecil New

unread,
Jun 30, 2025, 12:53:23 PM6/30/25
to Standard Ebooks
Lint has been helpful, but I can't seem to get the beginning right. This is what I have now and, for which, lint has reported the fewest errors:

<head>
<title>Part I</title>
<link href="../css/core.css" rel="stylesheet" type="text/css"/>
<link href="../css/local.css" rel="stylesheet" type="text/css"/>
</head>
<body epub:type="bodymatter z3998:fiction">
<section id="part-1" epub:type="chapter">
<hgroup>
<header>
<h2 epub:type="title">
<span epub:type="label">Part</span>
<span epub:type="ordinal z3998:roman">I</span>
</h2>
<p epub:type="subtitle">The Exile</p>
</header>
<div epub:type="bridgehead">
<p>August, 1923.</p>
<p>Summer is come with bursting flower and promise of perfect fruit. Rain is rolling down Nile and Niger. Summer sings on the sea where giant ships carry busy worlds, while mermaids swarm the shores. Earth is pregnant. Life is big with pain and evil and hope. Summer in blue New York; summer in gray Berlin; summer in the red heart of the world!</p>
</div>
</hgroup>
<section id="chapter-1-1" epub:type="z3998:subchapter">
<header>
<p epub:type="ordinal z3998:roman">I</p>
</header>
<p>Matthew Towns was in a cold white fury. He stood on the deck of the <i

Here is the single error that lint reports on this:
Unexpected value for <title>        
│       │               │                │ element. Expected: Part I The       
│       │               │                │ Exile: August, 1923. Summer is come 

│       │               │                │ with bursting flower and promise of 
│       │               │                │ perfect fruit. Rain is rolling down 
│       │               │                │ Nile and Niger. Summer sings on the 
│       │               │                │ sea where giant ships carry busy    
│       │               │                │ worlds, while mermaids swarm the    
│       │               │                │ shores. Earth is pregnant. Life is  
│       │               │                │ big with pain and evil and hope.    
│       │               │                │ Summer in blue New York; summer in  
│       │               │                │ gray Berlin; summer in the red      
│       │               │                │ heart of the world!. (Beware hidden 
│       │               │                │ Unicode characters!)    


I also spent some time trying to find an example like this in the SE org repos. But didn't find anything - I'm sure I just didn't have the right search value(s). Do you know of one?

Alex Cabal

unread,
Jun 30, 2025, 2:17:05 PM6/30/25
to standar...@googlegroups.com
It might be illustrative to look at the HTML spec for what is or isn't
allowed within certain elements:
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/hgroup

The manual provides copy and paste structures for everything you're
trying to do here.
> * The parts title is missing the <hgroup> element.
> * Bridgeheads should also be in the <header> element.
> * Subchapter <header>s need a <p> element.
> * The file section semantics should be `<section
> id="part-1" epub:type="chapter">`.
> * The part title and bridgeheads should be in a
> `<header>` element. See SEMoS 7.2.11 <https://
> standardebooks.org/manual/1.8.2/single-page#7.2.11>.
> * The subchapter titles should be formatted like in
> SEMoS 7.2.10.8 <https://standardebooks.org/
> manual/1.8.2/single-page#7.2.10.8>, because they do
> not appear in the ToC.
> * Correct. Remove styling for the first word.
> * Part Titles: See SEMoS 7.2.10.6 <https://
> standardebooks.org/manual/1.8.2/single-
> page#7.2.10.6>.
> * Bridgeheads: See SEMoS 7.2.11 <https://
> standardebooks.org/manual/1.8.2/single-
> page#7.2.11>. Both "August, 1923" and
> "Summer is come with bursting flower..." are
> bridgeheads. You can structure them like:
>
> <div epub:type="bridgehead">
> <p>August, 1923.</p>
> <p>Summer is come with bursting flower and
> promise of perfect fruit. Rain is rolling down
> Nile and Niger. Summer sings on the sea where
> giant ships carry busy worlds, while mermaids
> swarm the shores. Earth is pregnant. Life is big
> with pain and evil and hope. Summer in blue New
> York; summer in gray Berlin; summer in the red
> heart of the world!</p>
> </div>
>
> * Section Titles: See SEMoS 7.2.10.8 <https://
> standardebooks.org/manual/1.8.2/single-
> page#7.2.10.8>. The section headers are
> inside each subchapter <section> element.
>
>
> Emma
> On Friday, June 27, 2025 at 4:39:16 PM UTC-4
> ceci...@gmail.com wrote:
>
> I have a question or two... this is how part
> 1 begins: https://en.wikisource.org/wiki/
> Dark_Princess/Part_1 <https://
> en.wikisource.org/wiki/Dark_Princess/Part_1>
>
> (The scan is similar).
>
>
> Here is the bit from SEMoS 5.1.2.8
> <http://5.1.2.8>:
>
> <section id="chapter-1" epub:type="chapter">
>
> <header>
>
> <h2 epub:type="title">...</h2>
>
> <p epub:type="bridgehead">...</p>
>
> </header>
>
> <p id="chapter-1-p-2">...</p>
>
> <section id="chapter-1-1"
> epub:type="z3998:subchapter">
>
> <p>...</p>
>
>
>
> Then for part 1 the title is “THE EXILE”.
>
> The bridgehead would be something like:
>
> <p epub:type="bridgehead"><i>August, 1923</
> i></p>
>
> <p><i>Summer is come with bursting flower
> and promise of perfect fruit. Rain is
> rolling down Nile and Niger. Summer sings on
> the sea where giant ships carry busy worlds,
> while mermaids swarm the shores. Earth is
> pregnant. Life is big with pain and evil and
> hope. Summer in blue New York; summer in
> gray Berlin; summer in the red heart of the
> world!</i></p>
>
>
> What I don’t see is:
>
> *
>
> Where the text “Part I” will come from
>
> *
>
> Where the Roman numeral “I” (and the
> subsequent ones) will come from
>
>
> Thanks!
>
> --
> 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/b9df6daf-aaf7-4bf3-9171-ec1519e49941n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/b9df6daf-
> aaf7-4bf3-9171-ec1519e49941n%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

Emma Sweeney

unread,
Jun 30, 2025, 10:59:50 PM6/30/25
to Standard Ebooks
Transcription corrections are not [Editorial] corrections.

In your file, you need to switch the <header> and <hgroup> elements. The title semantics aren't quite right. Take a closer look at the SEMoS links I sent earlier.


Emma

Cecil New

unread,
Jul 11, 2025, 3:51:49 PM7/11/25
to Standard Ebooks
Lint complains about this - missing an opening quote before the word "We".
Screenshot from 2025-07-11 15-01-46.png

The wikisource matches this. But it looks like the scanned edition is wrong. It puts a quote after the question mark and it should not be there.

Am I correct? If so, do I isolate this with an [Editorial] comment?

Alex Cabal

unread,
Jul 11, 2025, 3:54:50 PM7/11/25
to standar...@googlegroups.com
This is clearly a printer's typo, it looks like you should remove quote
after `Perigua`. you can fix it without it being editorial.

On 7/11/25 2:05 PM, Cecil New wrote:
> Lint complains about this - missing an opening quote before the word "We".
> Screenshot from 2025-07-11 15-01-46.png
>
> The wikisource matches this. But it looks like the scanned edition is
> wrong. It puts a quote after the question mark and it should not be there.
>
> Am I correct? If so, do I isolate this with an [Editorial] comment?
>
> On Monday, June 30, 2025 at 10:59:50 PM UTC-4 Emma Sweeney wrote:
>
> Transcription corrections are not [Editorial] corrections.
>
> In your file, you need to switch the <header> and <hgroup> elements.
> The title semantics aren't quite right. Take a closer look at the
> SEMoS links I sent earlier.
>
>
> Emma
> On Monday, June 30, 2025 at 2:17:05 PM UTC-4 Alex Cabal wrote:
>
> It might be illustrative to look at the HTML spec for what is or
> isn't
> allowed within certain elements:
> https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/
> Elements/hgroup <https://developer.mozilla.org/en-US/docs/Web/
> HTML/Reference/Elements/hgroup>
> > standardebooks.org/manual/1.8.2/single-page#7.2.11 <http://
> standardebooks.org/manual/1.8.2/single-page#7.2.11>>.
> > * The subchapter titles should be formatted like in
> > SEMoS 7.2.10.8 <https://standardebooks.org/ <https://
> standardebooks.org/>
> > standardebooks.org/manual/1.8.2/single- <http://
> standardebooks.org/manual/1.8.2/single->
> > page#7.2.10.6>.
> > * Bridgeheads: See SEMoS 7.2.11 <https://
> > standardebooks.org/manual/1.8.2/single- <http://
> standardebooks.org/manual/1.8.2/single->
> > page#7.2.11>. Both "August, 1923" and
> > "Summer is come with bursting flower..." are
> > bridgeheads. You can structure them like:
> >
> > <div epub:type="bridgehead">
> > <p>August, 1923.</p>
> > <p>Summer is come with bursting flower and
> > promise of perfect fruit. Rain is rolling down
> > Nile and Niger. Summer sings on the sea where
> > giant ships carry busy worlds, while mermaids
> > swarm the shores. Earth is pregnant. Life is big
> > with pain and evil and hope. Summer in blue New
> > York; summer in gray Berlin; summer in the red
> > heart of the world!</p>
> > </div>
> >
> > * Section Titles: See SEMoS 7.2.10.8 <https://
> > standardebooks.org/manual/1.8.2/single- <http://
> standardebooks.org/manual/1.8.2/single->
> > page#7.2.10.8>. The section headers are
> > inside each subchapter <section> element.
> >
> >
> > Emma
> > On Friday, June 27, 2025 at 4:39:16 PM UTC-4
> > ceci...@gmail.com wrote:
> >
> > I have a question or two... this is how part
> > 1 begins: https://en.wikisource.org/wiki/ <https://
> en.wikisource.org/wiki/>
> > Dark_Princess/Part_1 <https://
> > en.wikisource.org/wiki/Dark_Princess/Part_1 <http://
> en.wikisource.org/wiki/Dark_Princess/Part_1>>
> >
> > (The scan is similar).
> >
> >
> > Here is the bit from SEMoS 5.1.2.8
> > <http://5.1.2.8 <http://5.1.2.8>>:
> msgid/ <https://groups.google.com/d/msgid/>
> > standardebooks/b9df6daf-aaf7-4bf3-9171-
> ec1519e49941n%40googlegroups.com <http://40googlegroups.com>
> > <https://groups.google.com/d/msgid/standardebooks/b9df6daf-
> <https://groups.google.com/d/msgid/standardebooks/b9df6daf->
> > aaf7-4bf3-9171-ec1519e49941n%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/2048bd5f-28b3-4608-97fe-56da62bd6432n%40googlegroups.com
> <https://groups.google.com/d/msgid/
> standardebooks/2048bd5f-28b3-4608-97fe-56da62bd6432n%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

Vince

unread,
Jul 11, 2025, 4:18:10 PM7/11/25
to Standard Ebooks
> On Jul 11, 2025, at 2:54 PM, Alex Cabal <al...@standardebooks.org> wrote:
>
> This is clearly a printer's typo, it looks like you should remove quote after `Perigua`. you can fix it without it being editorial.

?? Really? Correcting printer typos is changing the text, and thus you have always said they're editorial (“always” as in as long as I’ve been doing this). Confirming that, a quick search of the corpus indicates 95%+ of commits with “printer(’s) typo” in them are marked editorial. It’s fine if they shouldn’t be, but it’s a marked change.

Cecil New

unread,
Jul 12, 2025, 1:03:40 PM7/12/25
to Standard Ebooks
Consider the following snippet:
Screenshot from 2025-07-12 11-07-16.png

Neither the wikisource or the printed book distinguish the text on the piece of paper in any way.

But shouldn't it at least be marked up as a blockquote? Perhaps with letter semantics?

Emma Sweeney

unread,
Jul 12, 2025, 3:18:13 PM7/12/25
to Standard Ebooks
You can put this in a <blockquote> element with letter semantics.

Emma

Cecil New

unread,
Jul 13, 2025, 9:50:56 AM7/13/25
to Standard Ebooks
I have encountered a long dialogue where the two speakers often quote someone. So the structure looks like this:

<p>...and whispered: ‘Flee, flee! The English will kill you too.’ That was all.</p>
<p>“I do not know how it happened. ...</p>

The second paragraph continues the first so the first doesn't include a closing quote.

In each case like this, the linter complains:

│ y-007 │ Manual Review │ part-4.xhtml   │ Possible typo: ‘ not within “.      │
│       │               │                │ Hints: Should ‘ be replaced with “? │
│       │               │                │ Is there a missing closing quote?   │
│       │               │                │ Is this a nested quote that should  │
│       │               │                │ be preceded by “? Are quotes in     │
│       │               │                │ close proximity correctly closed?   │

I wondered if this might be a mistake in how the linter is looking at this. In each case the single quotes are matched.  So the "possible typo" part is not true.

It is a manual review, so for now I think I will have to have each instance overridden with the ignore file. Does this sound right?

Emma Sweeney

unread,
Jul 13, 2025, 11:25:51 AM7/13/25
to Standard Ebooks
It looks like from your repository that you need to fix the `t-003` lint errors, remove illegal styling, and re-run `se typogrify .` After you correct these, the `y-007` errors should also disappear.

Emma

Cecil New

unread,
Jul 14, 2025, 8:28:00 AM7/14/25
to Standard Ebooks
Thanks! I'm at the proof reading stage now, but will have little time to read for next two weeks. So I'm aiming to finish in first week of August.

Cecil New

unread,
Jul 18, 2025, 8:46:56 AM7/18/25
to Standard Ebooks
There is something after the word "This" in the scan:
Screenshot from 2025-07-18 08-40-01.png

The wikisource made it a straight single quote:
Screenshot from 2025-07-18 08-44-45.png

But I think it is a printer's mistake. If I remove it should I isolate the commit as [Editorial]?

Cecil New

unread,
Jul 18, 2025, 9:03:47 AM7/18/25
to Standard Ebooks
Another question... the book mentions a Bach Prelude "Komm, Gott, Schopfer". In the scan, it is merely quoted - no italics.


But, unless I misunderstand, the example shown in that section is not an example of that rule. So was a bit confusing at first.

Cecil New

unread,
Jul 18, 2025, 9:23:44 AM7/18/25
to Standard Ebooks
OK, third and last question for now...

The bridgeheads look like in the scan:
Screenshot from 2025-07-18 09-19-14.png

Each of the four bridgeheads have a time period as the first paragraph. 

1. The time period should be centered. Should I make a class? use an inline? use a clever "pick the first paragraph and center" selector?
2. The linter will complain that the paragraph does not have an ending punctuation. So I plan to have an ignore rule for this case. Sound right?

Emma Sweeney

unread,
Jul 18, 2025, 10:32:07 AM7/18/25
to Standard Ebooks
1. This looks like the OCR thought the ink dot was a quote. You can commit this as "Fix typo" since this a transcription error.
2. That's correct, it should be quoted.
3. You should add a period after the dates. The dates should follow the manual's bridgehead styling.

Emma

Cecil New

unread,
Jul 31, 2025, 8:59:14 AM7/31/25
to Standard Ebooks
There was some discussion earlier about the suitability of re-using the cover used by the scan. See post above at:
https://groups.google.com/g/standardebooks/c/ek8sy93OAzA/m/YiqIzqdQAwAJ

I started with this original scanned of the dust jacket:
https://en.wikisource.org/wiki/Index:Dark_Princess_(1928)_cropped_BW.pdf#/media/File:Dark_Princess_(1928,_DuBois)_1st_Edition_Dust_Jacket.jpg

After cropping, etc., here is what it looks like -- what do you think?
Screenshot from 2025-07-31 08-53-42.png


Emma Sweeney

unread,
Jul 31, 2025, 10:16:01 AM7/31/25
to Standard Ebooks
The art looks good! I've added it to the art db.

There is one issue with the cover: the author's name should appear as "W. E. B. Du Bois". You can build a dummy repo with the correct name, then copy and paste the `./images/cover.svg`, `./images/titlepage.svg`, and `./src/epub/text/titlepage.xhtml` files into your working repo. You can re-run `se build-images` to update the other SVGs in the `./src/epub/images/` folder.

Emma

Cecil New

unread,
Jul 31, 2025, 11:11:09 AM7/31/25
to Standard Ebooks
I'm working thru the content.opf...

a. Found that no seems to know the illustrator for the dust jacket. Should I remove the "cover artist" block?
b. In trying to track down the transcriber, I think it might be https://www.wikidata.org/wiki/User:Giantflightlessbirds. However, I'm not confident in how to interpret the wikisource edit history. And as far as I can tell, there is no explicit mention or acknowledgement of the transcriber(s). Am I on the right track here?

Thanks!

Cecil New

unread,
Jul 31, 2025, 11:21:53 AM7/31/25
to Standard Ebooks
As far as the transcriber is concerned... I also found another reference to https://en.wikisource.org/wiki/User:Beeswaxcandle. But I suspect these are the same person. At least they are both from New Zealand.

Alex Cabal

unread,
Jul 31, 2025, 11:25:56 AM7/31/25
to standar...@googlegroups.com
https://standardebooks.org/manual/1.8.3/single-page#6.6.4.4

Just list Wikisource as the transcriber, without a credit line like PG
provides we don't list individual contributors.

On 7/31/25 10:21 AM, Cecil New wrote:
> As far as the transcriber is concerned... I also found another reference
> to https://en.wikisource.org/wiki/User:Beeswaxcandle. But I suspect
> these are the same person. At least they are both from New Zealand.
>
> On Thursday, July 31, 2025 at 11:11:09 AM UTC-4 Cecil New wrote:
>
> I'm working thru the content.opf...
>
> a. Found that no seems to know the illustrator for the dust jacket.
> Should I remove the "cover artist" block?
> b. In trying to track down the transcriber, I think it might be
> https://www.wikidata.org/wiki/User:Giantflightlessbirds <https://
> www.wikidata.org/wiki/User:Giantflightlessbirds>. However, I'm not
> confident in how to interpret the wikisource edit history. And as
> far as I can tell, there is no explicit mention or acknowledgement
> of the transcriber(s). Am I on the right track here?
>
> Thanks!
>
> On Thursday, July 31, 2025 at 10:16:01 AM UTC-4 Emma Sweeney wrote:
>
> The art looks good! I've added it to the art db.
>
> There is one issue with the cover: the author's name should
> appear as "W. E. B. Du Bois". You can build a dummy repo with
> the correct name, then copy and paste the `./images/cover.svg`,
> `./images/titlepage.svg`, and `./src/epub/text/titlepage.xhtml`
> files into your working repo. You can re-run `se build-images`
> to update the other SVGs in the `./src/epub/images/` folder.
>
> Emma
> On Thursday, July 31, 2025 at 8:59:14 AM UTC-4 ceci...@gmail.com
> wrote:
>
> There was some discussion earlier about the suitability of
> re-using the cover used by the scan. See post above at:
> https://groups.google.com/g/standardebooks/c/ek8sy93OAzA/m/
> YiqIzqdQAwAJ <https://groups.google.com/g/standardebooks/c/
> ek8sy93OAzA/m/YiqIzqdQAwAJ>
>
> I started with this original scanned of the dust jacket:
> https://en.wikisource.org/wiki/
> Index:Dark_Princess_(1928)_cropped_BW.pdf#/media/
> File:Dark_Princess_(1928,_DuBois)_1st_Edition_Dust_Jacket.jpg <https://en.wikisource.org/wiki/Index:Dark_Princess_(1928)_cropped_BW.pdf#/media/File:Dark_Princess_(1928,_DuBois)_1st_Edition_Dust_Jacket.jpg>
>
> After cropping, etc., here is what it looks like -- what do
> you think?
> Screenshot from 2025-07-31 08-53-42.png
>
>
> On Friday, July 18, 2025 at 10:32:07 AM UTC-4 Emma Sweeney
> wrote:
>
> 1. This looks like the OCR thought the ink dot was a
> quote. You can commit this as "Fix typo" since this a
> transcription error.
> 2. That's correct, it should be quoted.
> 3. You should add a period after the dates. The dates
> should follow the manual's bridgehead styling.
>
> Emma
> On Friday, July 18, 2025 at 9:23:44 AM UTC-4
> ceci...@gmail.com wrote:
>
> OK, third and last question for now...
>
> The bridgeheads look like in the scan:
> Screenshot from 2025-07-18 09-19-14.png
>
> Each of the four bridgeheads have a time period as
> the first paragraph.
>
> 1. The time period should be centered. Should I make
> a class? use an inline? use a clever "pick the first
> paragraph and center" selector?
> 2. The linter will complain that the paragraph does
> not have an ending punctuation. So I plan to have an
> ignore rule for this case. Sound right?
>
> On Friday, July 18, 2025 at 9:03:47 AM UTC-4 Cecil
> New wrote:
>
> Another question... the book mentions a Bach
> Prelude "Komm, Gott, Schopfer". In the scan, it
> is merely quoted - no italics.
>
> This seems to be correct per https://
> standardebooks.org/manual/1.8.3/single-
> page#8.2.11.3 <https://standardebooks.org/
> manual/1.8.3/single-page#8.2.11.3>
>
> But, unless I misunderstand, the example shown
> in that section is not an example of that rule.
> So was a bit confusing at first.
>
> On Friday, July 18, 2025 at 8:46:56 AM UTC-4
> Cecil New wrote:
>
> There is something after the word "This" in
> the scan:
> Screenshot from 2025-07-18 08-40-01.png
>
> The wikisource made it a straight single quote:
> --
> 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/2fded21e-750b-4630-ac12-9e00bc407cd8n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/2fded21e-750b-4630-
> ac12-9e00bc407cd8n%40googlegroups.com?utm_medium=email&utm_source=footer>.

Emma Sweeney

unread,
Jul 31, 2025, 11:26:40 AM7/31/25
to Standard Ebooks
a. You can label the artist Anonymous.
b. You can just include Wikisource as a corporate entity as a transcriber.

Emma

Cecil New

unread,
Aug 4, 2025, 2:40:16 PM8/4/25
to Standard Ebooks
I am using se version 2.8.0, which I think is the latest. I am getting a lint error for the colophon file, which says:

> Anonymous contributors in the colophon must be exactly <b>An  Anonymous Volunteer</b> or <b>An Unknown Artist</b>.  

and it points me to this offending text:

> <b>January 1, 1900, 12:00 <abbr class="eoc">a.m.</abbr></b>   

Speculating that the linter thinks bold tags enclose a personal name.

Alex Cabal

unread,
Aug 4, 2025, 2:41:37 PM8/4/25
to standar...@googlegroups.com
The colophon standard has changed since you started the book. Replace
<b> with <time datetime="1900-01-01T00:00:00Z">

On 8/4/25 1:40 PM, Cecil New wrote:
> I am using se version 2.8.0, which I think is the latest. I am getting a
> lint error for the colophon file, which says:
>
> > Anonymous contributors in the colophon must be exactly <b>An
> Anonymous Volunteer</b> or <b>An Unknown Artist</b>.
>
> and it points me to this offending text:
>
> > <b>January 1, 1900, 12:00 <abbr class="eoc">a.m.</abbr></b>
>
> Speculating that the linter thinks bold tags enclose a personal name.
> On Thursday, July 31, 2025 at 11:26:40 AM UTC-4 Emma Sweeney wrote:
>
> a. You can label the artist Anonymous.
> b. You can just include Wikisource as a corporate entity as a
> transcriber.
>
> Emma
> On Thursday, July 31, 2025 at 11:11:09 AM UTC-4 ceci...@gmail.com wrote:
>
> I'm working thru the content.opf...
>
> a. Found that no seems to know the illustrator for the dust
> jacket. Should I remove the "cover artist" block?
> b. In trying to track down the transcriber, I think it might be
> https://www.wikidata.org/wiki/User:Giantflightlessbirds
> <https://www.wikidata.org/wiki/User:Giantflightlessbirds>.
> However, I'm not confident in how to interpret the wikisource
> edit history. And as far as I can tell, there is no explicit
> mention or acknowledgement of the transcriber(s). Am I on the
> right track here?
>
> Thanks!
>
> On Thursday, July 31, 2025 at 10:16:01 AM UTC-4 Emma Sweeney wrote:
>
> The art looks good! I've added it to the art db.
>
> There is one issue with the cover: the author's name should
> appear as "W. E. B. Du Bois". You can build a dummy repo
> with the correct name, then copy and paste the `./images/
> cover.svg`, `./images/titlepage.svg`, and `./src/epub/text/
> titlepage.xhtml` files into your working repo. You can re-
> run `se build-images` to update the other SVGs in the `./
> src/epub/images/` folder.
>
> Emma
> On Thursday, July 31, 2025 at 8:59:14 AM UTC-4
> ceci...@gmail.com wrote:
>
> There was some discussion earlier about the suitability
> of re-using the cover used by the scan. See post above at:
> standardebooks/c/ek8sy93OAzA/m/YiqIzqdQAwAJ>
>
> I started with this original scanned of the dust jacket:
> https://en.wikisource.org/wiki/
> Index:Dark_Princess_(1928)_cropped_BW.pdf#/media/
> File:Dark_Princess_(1928,_DuBois)_1st_Edition_Dust_Jacket.jpg <https://en.wikisource.org/wiki/Index:Dark_Princess_(1928)_cropped_BW.pdf#/media/File:Dark_Princess_(1928,_DuBois)_1st_Edition_Dust_Jacket.jpg>
>
> After cropping, etc., here is what it looks like -- what
> do you think?
> Screenshot from 2025-07-31 08-53-42.png
>
>
> On Friday, July 18, 2025 at 10:32:07 AM UTC-4 Emma
> Sweeney wrote:
>
> 1. This looks like the OCR thought the ink dot was a
> quote. You can commit this as "Fix typo" since this
> a transcription error.
> 2. That's correct, it should be quoted.
> 3. You should add a period after the dates. The
> dates should follow the manual's bridgehead styling.
>
> Emma
> On Friday, July 18, 2025 at 9:23:44 AM UTC-4
> ceci...@gmail.com wrote:
>
> OK, third and last question for now...
>
> The bridgeheads look like in the scan:
> Screenshot from 2025-07-18 09-19-14.png
>
> Each of the four bridgeheads have a time period
> as the first paragraph.
>
> 1. The time period should be centered. Should I
> make a class? use an inline? use a clever "pick
> the first paragraph and center" selector?
> 2. The linter will complain that the paragraph
> does not have an ending punctuation. So I plan
> to have an ignore rule for this case. Sound right?
>
> On Friday, July 18, 2025 at 9:03:47 AM UTC-4
> Cecil New wrote:
>
> Another question... the book mentions a Bach
> Prelude "Komm, Gott, Schopfer". In the scan,
> it is merely quoted - no italics.
>
> This seems to be correct per https://
> standardebooks.org/manual/1.8.3/single-
> page#8.2.11.3 <https://standardebooks.org/
> manual/1.8.3/single-page#8.2.11.3>
>
> But, unless I misunderstand, the example
> shown in that section is not an example of
> that rule. So was a bit confusing at first.
>
> On Friday, July 18, 2025 at 8:46:56 AM UTC-4
> Cecil New wrote:
>
> There is something after the word "This"
> in the scan:
> Screenshot from 2025-07-18 08-40-01.png
>
> The wikisource made it a straight single
> quote:
> --
> 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/09d4dfa3-d01f-40a0-9409-0328a3d4cc80n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/09d4dfa3-
> d01f-40a0-9409-0328a3d4cc80n%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

Cecil New

unread,
Aug 4, 2025, 4:29:49 PM8/4/25
to Standard Ebooks
This is ready for review. Some notes to consider...

I updated the dedication css to get rid of a linter complaint. If there is another approach I should use let me know.

Before
section[epub|type~="dedication"]{
text-align: center;
}

After:
section[epub|type~="dedication"] p{
text-align: center;
text-indent: 0;
}

For two manual reviews, I added two ignore rules in the se lint ignore file. 
- One rule ignores an error that says there is ending punctuation, which is not true. 
- The second says a dash should be an em-dash, but it is an em-dash.

Finally, while I made the bridgeheads conform to the SMoS style, they don't look right. The first "paragraph" of each part's bridgehead is a date or a duration. In the scans they are centered and without ending punctuation. As printed, they look better than what I have done to them.

Cecil New

unread,
Aug 4, 2025, 4:32:03 PM8/4/25
to Standard Ebooks
Sorry, just noticed I missed a word. Should be: "...there is no ending punctuation, which is not true."

Vince

unread,
Aug 4, 2025, 5:03:45 PM8/4/25
to Standard Ebooks
I’ll get to the review in a day or three, but re the below: ignore lint at your peril. :)

If lint says something needs to be an em-dash, you can be confident it’s not an em-dash. Maybe it doesn’t need to be an em-dash (that’s the manual review part), but it’s definitely not one now. And in this case it isn’t; as lint indicates, this is a regular hyphen, and should be an em-dash.
courtesies of life-they are the real end

In the case of the dedication, even if the text-indent was needed, it should be additional, not replacing existing CSS. But it’s not needed, because there should only be one p; the “etc., etc.” isn’t terminating, so the “of whose faith…” is still part of the same clause.

Re the part-4 bridgehead, it’s being fooled into thinking it’s something it’s not because of the two em-dashes, but the first em-dash should be an en-dash; date ranges are like number ranges, en-dashes are used rather than em-dashes. (<rhetorical>And why the weird formatting for that date? Why not the more expected April 1926–April 1927? That’s just odd.</rhetorical>) You will need to rerun typogrify after making that change.

I also would put the dates in the header, not the bridgehead. But that’s an Alex call, I think.
Alex, the bridgeheads look like this. Should the date be part of the header hgroup, or part of the bridgehead?
PastedGraphic-1.png

Vince

unread,
Aug 4, 2025, 5:12:20 PM8/4/25
to Standard Ebooks
And a question for Emma: early on, you indicated this should be in four files, with “chapter” as the major epub type and “subchapter” as the minor. But since each major is called a part, e.g. “Part I,” Part II,”, why wouldn’t we have the major epub type be “part” and the minor be chapters? That seems to me to be more what’s happening, especially since there are individual pages for the PART X breaks, e.g. here.. It’s looks to me like a four part structure with chapters, just with no page breaks within the chapters. But I don’t claim to know what I’m doing…

Emma Sweeney

unread,
Aug 4, 2025, 5:22:40 PM8/4/25
to Standard Ebooks
I just suggested using “chapter” and “subchapter”, because the “subchapters” seemed a little too short to be normal chapters, some are less than a page long. To be fair, I rarely work on prose projects...

Emma

Alex Cabal

unread,
Aug 4, 2025, 5:23:01 PM8/4/25
to standar...@googlegroups.com
If you can picture the dates appearing in the ToC, then they are heading
material. If not, they are bridgehead material.

On 8/4/25 4:03 PM, Vince wrote:
> I’ll get to the review in a day or three, but re the below: ignore lint
> at your peril. :)
>
> If lint says something needs to be an em-dash, you can be confident
> it’s /not/ an em-dash. Maybe it doesn’t /need/ to be an em-dash (that’s
> the manual review part), but it’s definitely not one now. And in this
> case it isn’t; as lint indicates, this is a regular hyphen, and should
> be an em-dash.
>
> courtesies of life-they are the real end
>
>
> In the case of the dedication, even if the text-indent was needed, it
> should be additional, not replacing existing CSS. But it’s not needed,
> because there should only be one p; the “etc., etc.” isn’t terminating,
> so the “of whose faith…” is still part of the same clause.
>
> Re the part-4 bridgehead, it’s being fooled into thinking it’s something
> it’s not because of the two em-dashes, but the first em-dash should be
> an en-dash; date ranges are like number ranges, en-dashes are used
> rather than em-dashes. (<rhetorical>And why the weird formatting for
> that date? Why not the more expected April 1926–April 1927? That’s just
> odd.</rhetorical>) You will need to rerun typogrify after making that
> change.
>
> I also would put the dates in the header, not the bridgehead. But that’s
> an Alex call, I think.
> Alex, the bridgeheads look like this. Should the date be part of the
> header hgroup, or part of the bridgehead?
> PastedGraphic-1.png
>
>> On Aug 4, 2025, at 3:29 PM, Cecil New <ceci...@gmail.com> wrote:
>>
>> This is ready for review. Some notes to consider...
>>
>> *I updated the dedication css to get rid of a linter complaint.* If
>> there is another approach I should use let me know.
>>
>> _Before_:
>> section[epub|type~="dedication"]{
>> text-align: center;
>> }
>>
>> _After_:
>> section[epub|type~="dedication"] p{
>> text-align: center;
>> text-indent: 0;
>> }
>>
>> *For two manual reviews, I added two ignore rules in the se lint
>> ignore file.*
>> - One rule ignores an error that says there is ending punctuation,
>> which is not true.
>> - The second says a dash should be an em-dash, but it is an em-dash.
>>
>> *Finally*, while I made the bridgeheads conform to the SMoS style,
>> they don't look right. The first "paragraph" of each part's bridgehead
>> is a date or a duration. In the scans they are centered and without
>> ending punctuation. As printed, they look better than what I have done
>> to them.
>
> --
> 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/23B25627-0A0F-40AD-A576-15E47D354956%40letterboxes.org
> <https://groups.google.com/d/msgid/standardebooks/23B25627-0A0F-40AD-
> A576-15E47D354956%40letterboxes.org?utm_medium=email&utm_source=footer>.

Vince

unread,
Aug 4, 2025, 5:27:52 PM8/4/25
to Standard Ebooks
I wouldn’t picture either one—they’re at best a subtitle, but if it was me I wouldn’t put an epub type on them at all. Either way, they wouldn’t appear in the ToC.

Cecil New

unread,
Aug 4, 2025, 6:11:08 PM8/4/25
to Standard Ebooks
I fixed per your initial feedback and pushed the commits. 

FWIW, for the bridgehead, just visually to match the scan: a) remove the punctuation; b) center the text.

Vince

unread,
Aug 6, 2025, 4:55:11 PM8/6/25
to standar...@googlegroups.com
Are you sure you pushed them? I didn’t see them, so I went ahead and added them to the review, which is now posted.

Cecil New

unread,
Aug 6, 2025, 7:13:23 PM8/6/25
to standar...@googlegroups.com
Sorry, I'm out of town and can't check. Thanks for going ahead. I'll review next week

Cecil




--
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.
To view this discussion visit https://groups.google.com/d/msgid/standardebooks/22991EE7-B015-47B2-86E8-5A4C7DA65E49%40letterboxes.org.

Alex Cabal

unread,
Aug 20, 2025, 7:31:26 PM8/20/25
to standar...@googlegroups.com
Are we about wrapped up here?

On 8/6/25 6:13 PM, Cecil New wrote:
> Sorry, I'm out of town and can't check. Thanks for going ahead. I'll
> review next week
>
> Cecil
>
>
>
>
> On Wed, Aug 6, 2025, 3:55 PM Vince <vr_se...@letterboxes.org
> <mailto:vr_se...@letterboxes.org>> wrote:
>
> Are you sure you pushed them? I didn’t see them, so I went ahead and
> added them to the review, which is now posted.
>
>> On Aug 4, 2025, at 5:11 PM, Cecil New <ceci...@gmail.com
> <mailto:standardebook...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/
> standardebooks/22991EE7-
> B015-47B2-86E8-5A4C7DA65E49%40letterboxes.org <https://
> groups.google.com/d/msgid/standardebooks/22991EE7-
> B015-47B2-86E8-5A4C7DA65E49%40letterboxes.org?
> 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/
> CAHy3j8fgFFehy0Y7zJ2AJPmEzcOPc%2BeC_5R%3DzHmCGze9SNo7ug%40mail.gmail.com
> <https://groups.google.com/d/msgid/standardebooks/
> CAHy3j8fgFFehy0Y7zJ2AJPmEzcOPc%2BeC_5R%3DzHmCGze9SNo7ug%40mail.gmail.com?utm_medium=email&utm_source=footer>.

Vince

unread,
Aug 21, 2025, 12:02:14 AM8/21/25
to Standard Ebooks
He finished his changes from the first pass a couple of days ago, and I gave him some additional things to fix from that, and will go through everything again when those are complete. We’re in different parts of the world, I think, so back and forth has been slower than normal.

Cecil New

unread,
Aug 22, 2025, 9:49:39 AM8/22/25
to Standard Ebooks
I apologize that this has taken so long. Because of a few misunderstandings on my part, this took more time than it should have. Knowing what I know now, I could probably do it in about week or so. 

Vince

unread,
Aug 22, 2025, 3:32:39 PM8/22/25
to standar...@googlegroups.com
No worries—the first book or two can be a steep learning curve.

I’ve gone through everything again, and opened a new issue with a few minor things.

Vince

unread,
Aug 24, 2025, 7:47:43 PM8/24/25
to Standard Ebooks
All right, Alex, I believe this is ready for you.

Alex Cabal

unread,
Aug 24, 2025, 11:22:31 PM8/24/25
to standar...@googlegroups.com
Looks very good Cecil, I've gone ahead and released it. Thanks!
Reply all
Reply to author
Forward
0 new messages