[First Project] W. E. B. Du Bois, The Quest of the Silver Fleece

[Bennett Helm]

I thought I'd give this a shot.

Text Source: https://www.gutenberg.org/ebooks/15265

Scan Source: https://archive.org/details/questofsilverfle0000dubo_n0o6

Repository: https://github.com/bwhelm/DuBois-Quest-of-Silver-Fleece

Any advice would be welcome!

Bennett

[Alex Cabal]

Great, that one would be a good start.

This book has a dedication and preface, so you'll have to include a half
title page. Otherwise this should be pretty straightforward.

Robin will manage with Weijia reviewing.

Make sure to read the Standard Ebooks Manual of Style before starting,
as you won't know what to fix if you haven't read the standards. In
particular, please closely review the semantics, high level patterns,
and typography sections:

https://standardebooks.org/manual

https://standardebooks.org/manual/latest/4-semantics

https://standardebooks.org/manual/latest/7-high-level-structural-patterns

https://standardebooks.org/manual/latest/8-typography

The step by step guide will take you from start to finish. Please follow
it exactly:

https://standardebooks.org/contribute/producing-an-ebook-step-by-step

This page on common issues in older books may be useful:

https://standardebooks.org/contribute/how-tos/common-issues-when-working-on-public-domain-ebooks

Please email often if you have any questions at all. Our standards are
well-established so there is probably already a standard for formatting
whatever problem you've encountered.

When you're ready, email back with a link to your Github repository so
that I can assign you a manager and reviewer.

Have fun! :)

> --
> 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/de9e8a1d-9557-4979-aa15-601dbc3295c9n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/de9e8a1d-9557-4979-
> aa15-601dbc3295c9n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Weijia Cheng]

Ok, noted.

I took a look at your repository and I noticed that there are some issues with your commit structure. For example, modernizing hyphenation and spelling is supposed to be a single editorial commit, but you mixed those changes with non-editorial semantics changes. In general, for your first project, you want to follow the commits outlined in the step-by-step guide closely to make your project easier to review. I also noticed that you included the illustrations, but we don't include decorative illustrations (i.e. illustrations that are not essential to the plot) in our projects.

I suggest that now that you have become more familiar with the toolset, you should start over and follow the step-by-step guide closely to ensure that your work meets our standards. This will ultimately save both you and your review (i.e. me) down the line.

[Bennett Helm]

Ok -- I've deleted that repository and started over. The new version is at the same url: https://github.com/bwhelm/DuBois-Quest-of-Silver-Fleece

One note on something I found confusing in the step-by-step guide, which I think was behind my doing things out of the order you wanted them in: Step 12 ("Add a List of Illustrations") says to use `se build-loi`, but only after building the manifest and spine first. Those can be found in Step 19, so I jumped down to do that, and then tried to get caught up on other things. That part of the guide should probably be revised.

It would also be good in Step 12 to indicate that you don't include decorative illustrations.

Currently I'm at Step 22 (Proofread), which will probably take a while. But I'm getting two items from `se lint` for "Manual Review", which I'm not understanding how to fix:

1. |  m-090 │ Manual Review │ dedication.xhtml │ dedication semantic inflection found, but no MARC relator dto (Dedicator).  |
2. |  m-031 │ Manual Review │ preface.xhtml    │ preface semantic inflection found, but no MARC relator wpr (Writer of preface).  |

Help on that would be appreciated.

Bennett

[Alex Cabal]

You have to add MARC roles in the metadata for the writer of the preface
and the dedicator, which are usually the author.
https://standardebooks.org/manual/1.8.8/single-page#9.11.8

On 6/7/26 4:12 PM, Bennett Helm wrote:
> Ok -- I've deleted that repository and started over. The new version is
> at the same url: https://github.com/bwhelm/DuBois-Quest-of-Silver-Fleece
> <https://github.com/bwhelm/DuBois-Quest-of-Silver-Fleece>
>
> One note on something I found confusing in the step-by-step guide, which
> I think was behind my doing things out of the order you wanted them in:
> Step 12 ("Add a List of Illustrations") says to use `se build-loi`, but
> only after building the manifest and spine first. Those can be found in
> Step 19, so I jumped down to do that, and then tried to get caught up on
> other things. That part of the guide should probably be revised.
>
> It would also be good in Step 12 to indicate that you don't include
> decorative illustrations.
>
> Currently I'm at Step 22 (Proofread), which will probably take a while.
> But I'm getting two items from `se lint` for "Manual Review", which I'm
> not understanding how to fix:
>

> 1. |  m-090 │ Manual Review │ dedication.xhtml │ dedication semantic

> inflection found, but no MARC relator dto (Dedicator).  |

> 2. |  m-031 │ Manual Review │ preface.xhtml    │ preface semantic

> inflection found, but no MARC relator wpr (Writer of preface).  |
>
> Help on that would be appreciated.
>
> Bennett
> On Sunday, June 7, 2026 at 2:38:12 PM UTC-4 weij...@bu.edu wrote:
>
> Ok, noted.
>
> I took a look at your repository and I noticed that there are some
> issues with your commit structure. For example, modernizing
> hyphenation and spelling is supposed to be a single editorial
> commit, but you mixed those changes with non-editorial semantics
> changes. In general, for your first project, you want to follow the

> commits outlined in the step-by-step guide <https://
> standardebooks.org/contribute/producing-an-ebook-step-by-
> step> closely to make your project easier to review. I also noticed

> that you included the illustrations, but we don't include decorative
> illustrations (i.e. illustrations that are not essential to the
> plot) in our projects.
>
> I suggest that now that you have become more familiar with the
> toolset, you should start over and follow the step-by-step guide
> closely to ensure that your work meets our standards. This will
> ultimately save both you and your review (i.e. me) down the line.
>
> On Sunday, June 7, 2026 at 12:04:51 PM UTC-4 Alex Cabal wrote:
>
> Great, that one would be a good start.
>
> This book has a dedication and preface, so you'll have to
> include a half
> title page. Otherwise this should be pretty straightforward.
>
> Robin will manage with Weijia reviewing.
>
> Make sure to read the Standard Ebooks Manual of Style before
> starting,
> as you won't know what to fix if you haven't read the standards. In
> particular, please closely review the semantics, high level
> patterns,
> and typography sections:
>
> https://standardebooks.org/manual <https://standardebooks.org/
> manual>
>

> https://standardebooks.org/manual/latest/4-semantics <https://
> standardebooks.org/manual/latest/4-semantics>
>
> https://standardebooks.org/manual/latest/7-high-level-
> structural-patterns <https://standardebooks.org/manual/latest/7-
> high-level-structural-patterns>
>
> https://standardebooks.org/manual/latest/8-typography <https://
> standardebooks.org/manual/latest/8-typography>

>
> The step by step guide will take you from start to finish.
> Please follow
> it exactly:
>
> https://standardebooks.org/contribute/producing-an-ebook-step-

> by-step <https://standardebooks.org/contribute/producing-an-
> ebook-step-by-step>

>
> This page on common issues in older books may be useful:
>
> https://standardebooks.org/contribute/how-tos/common-issues-

> when-working-on-public-domain-ebooks <https://
> standardebooks.org/contribute/how-tos/common-issues-when-
> working-on-public-domain-ebooks>

>
> Please email often if you have any questions at all. Our
> standards are
> well-established so there is probably already a standard for
> formatting
> whatever problem you've encountered.
>
> When you're ready, email back with a link to your Github
> repository so
> that I can assign you a manager and reviewer.
>
> Have fun! :)
>
>
> On 6/6/26 8:15 PM, Bennett Helm wrote:
> > I thought I'd give this a shot.
> >

> > Text Source: https://www.gutenberg.org/ebooks/15265 <https://
> www.gutenberg.org/ebooks/15265>
> > Scan Source: https://archive.org/details/
> questofsilverfle0000dubo_n0o6 <https://archive.org/details/
> questofsilverfle0000dubo_n0o6>
> > Repository: https://github.com/bwhelm/DuBois-Quest-of-Silver-
> Fleece <https://github.com/bwhelm/DuBois-Quest-of-Silver-Fleece>

> >
> > Any advice would be welcome!
> >
> > Bennett
> >
> > --
> > 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/de9e8a1d-9557-4979-
> aa15-601dbc3295c9n%40googlegroups.com <http://40googlegroups.com>
> > <https://groups.google.com/d/msgid/standardebooks/
> de9e8a1d-9557-4979- <https://groups.google.com/d/msgid/
> standardebooks/de9e8a1d-9557-4979->
> > aa15-601dbc3295c9n%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/c295351c-60d6-47af-94d0-778cc38c74f8n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/
> c295351c-60d6-47af-94d0-778cc38c74f8n%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

[Weijia Cheng]

The new respository looks much better! Please post all future responses in the public thread so that all of the communications are visible.

Robin is your manager so he will be answering any questions you have until you get to the review stage.

[Bennett Helm]

Got it. I haven't gotten to metadata yet, but that makes sense.

One further question about how you want git commits as I proofread. In my local repository (not yet pushed to github.com), I have these commits:

--------------------------------

commit bc91795be0ad18e28b2d19714ef4a09fb6868316 (HEAD -> main)
Author: Bennett Helm
Date:   Wed Jun 10 09:25:17 2026 -0400

    [Editorial] Correct missing elision

    "Go way" --> "Go ’way"

commit e22447b6e37435c7c63eea07ff67a795c97cb1f2
Author: Bennett Helm
Date:   Wed Jun 10 09:23:44 2026 -0400

    [Editorial] Modernize spelling of "anæmic"

commit 12589000d26c3ad175406f992436ce200353f267
Author: Bennett Helm
Date:   Wed Jun 10 09:21:32 2026 -0400

    [Editorial] Correct mismatched spelling

    There's one instance of "veranda" and multiple instances of "verandah".
    I'm standardizing on the more common spelling, "veranda".

--------------------------------

Is that how the commits should be structured, or should I revise them before I push to github.com? I'm mostly wondering how I should do this as I continue proofreading.

Thanks!

Bennett

On Wednesday, June 10, 2026 at 9:48:10 AM UTC-4 Alex Cabal wrote:

[Alex Cabal]

Yes, that looks good!

> https://standardebooks.org/manual/1.8.8/single-page#9.11.8 <https://
> standardebooks.org/manual/1.8.8/single-page#9.11.8>

> <http://standardebooks.org/contribute/producing-an-ebook-step-by->

> > step> closely to make your project easier to review. I also noticed
> > that you included the illustrations, but we don't include decorative
> > illustrations (i.e. illustrations that are not essential to the
> > plot) in our projects.
> >
> > I suggest that now that you have become more familiar with the
> > toolset, you should start over and follow the step-by-step guide
> > closely to ensure that your work meets our standards. This will
> > ultimately save both you and your review (i.e. me) down the line.
> >
> > On Sunday, June 7, 2026 at 12:04:51 PM UTC-4 Alex Cabal wrote:
> >
> > Great, that one would be a good start.
> >
> > This book has a dedication and preface, so you'll have to
> > include a half
> > title page. Otherwise this should be pretty straightforward.
> >
> > Robin will manage with Weijia reviewing.
> >
> > Make sure to read the Standard Ebooks Manual of Style before
> > starting,
> > as you won't know what to fix if you haven't read the standards. In
> > particular, please closely review the semantics, high level
> > patterns,
> > and typography sections:
> >
> > https://standardebooks.org/manual <https://standardebooks.org/

> manual> <https://standardebooks.org/ <https://standardebooks.org/>

> > manual>
> >
> > https://standardebooks.org/manual/latest/4-semantics <https://
> standardebooks.org/manual/latest/4-semantics> <https://

> > standardebooks.org/manual/latest/4-semantics <http://
> standardebooks.org/manual/latest/4-semantics>>
> >
> > https://standardebooks.org/manual/latest/7-high-level- <https://
> standardebooks.org/manual/latest/7-high-level->
> > structural-patterns <https://standardebooks.org/manual/latest/7-

> <https://standardebooks.org/manual/latest/7->
> > high-level-structural-patterns>
> >
> > https://standardebooks.org/manual/latest/8-typography <https://

> standardebooks.org/manual/latest/8-typography> <https://
> > standardebooks.org/manual/latest/8-typography <http://

> standardebooks.org/manual/latest/8-typography>>
> >
> > The step by step guide will take you from start to finish.
> > Please follow
> > it exactly:
> >
> > https://standardebooks.org/contribute/producing-an-ebook-step-
> <https://standardebooks.org/contribute/producing-an-ebook-step->
> > by-step <https://standardebooks.org/contribute/producing-an-
> <https://standardebooks.org/contribute/producing-an->
> > ebook-step-by-step>
> >
> > This page on common issues in older books may be useful:
> >
> > https://standardebooks.org/contribute/how-tos/common-issues-
> <https://standardebooks.org/contribute/how-tos/common-issues->
> > when-working-on-public-domain-ebooks <https://
> > standardebooks.org/contribute/how-tos/common-issues-when-

> <http://standardebooks.org/contribute/how-tos/common-issues-when->

> > working-on-public-domain-ebooks>
> >
> > Please email often if you have any questions at all. Our
> > standards are
> > well-established so there is probably already a standard for
> > formatting
> > whatever problem you've encountered.
> >
> > When you're ready, email back with a link to your Github
> > repository so
> > that I can assign you a manager and reviewer.
> >
> > Have fun! :)
> >
> >
> > On 6/6/26 8:15 PM, Bennett Helm wrote:
> > > I thought I'd give this a shot.
> > >
> > > Text Source: https://www.gutenberg.org/ebooks/15265 <https://

> www.gutenberg.org/ebooks/15265> <https://
> > www.gutenberg.org/ebooks/15265 <http://www.gutenberg.org/
> ebooks/15265>>
> > > Scan Source: https://archive.org/details/ <https://archive.org/
> details/>
> > questofsilverfle0000dubo_n0o6 <https://archive.org/details/

> <https://archive.org/details/>
> > questofsilverfle0000dubo_n0o6>
> > > Repository: https://github.com/bwhelm/DuBois-Quest-of-Silver-
> <https://github.com/bwhelm/DuBois-Quest-of-Silver->
> > Fleece <https://github.com/bwhelm/DuBois-Quest-of-Silver-Fleece
> <https://github.com/bwhelm/DuBois-Quest-of-Silver-Fleece>>
> > >
> > > Any advice would be welcome!
> > >
> > > Bennett
> > >
> > > --
> > > 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/
> <https://groups.google.com/d/>

> > msgid/ <https://groups.google.com/d/msgid/ <https://
> groups.google.com/d/msgid/>>
> > > standardebooks/de9e8a1d-9557-4979-
> > aa15-601dbc3295c9n%40googlegroups.com <http://40googlegroups.com>
> <http://40googlegroups.com <http://40googlegroups.com>>
> > > <https://groups.google.com/d/msgid/standardebooks/ <https://
> groups.google.com/d/msgid/standardebooks/>
> > de9e8a1d-9557-4979- <https://groups.google.com/d/msgid/ <https://
> groups.google.com/d/msgid/>
> > standardebooks/de9e8a1d-9557-4979->
> > > aa15-601dbc3295c9n%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/
> c295351c-60d6-47af-94d0-778cc38c74f8n%40googlegroups.com
> <http://40googlegroups.com>
> > <https://groups.google.com/d/msgid/standardebooks/ <https://
> groups.google.com/d/msgid/standardebooks/>
> > c295351c-60d6-47af-94d0-778cc38c74f8n%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/367edff4-17d9-4bc4-8c82-64a8f6edf05cn%40googlegroups.com
> <https://groups.google.com/d/msgid/
> standardebooks/367edff4-17d9-4bc4-8c82-64a8f6edf05cn%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

[Bennett Helm]

I'm working my way through this book, and there's one passage I'm unsure of whether to make editorial changes or not. Here's the passage (with a bit of preceding context; source text, with this passage highlighted):

"Through yonder doorway had trooped an army of hundreds upon hundreds of bright and dull, light and dark, eager and sullen faces. There had been good and bad, honest and deceptive, frank and furtive. Some had caught, kindled and flashed to ambition and achievement; some, glowing dimly, had plodded on in slow, dumb faithful work worth while; and yet others ...".

What I'm uncertain of is what to do with "slow, dumb faithful work worth while" towards the end. In particular:

1. Should I change "worth while" to "worthwhile"?
2. Should I add a comma after "dumb"?

Bennett

[Robin Whittleton]

No and no. For a first production you’re unlikely to hit anything that we’d potentially change that hasn’t been automated or at least written out as a manual check in the step-by-step guide. If you do feel really strongly about anything then of course double-check, but it doesn’t sound like that’s the case here?

-Robin

--
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/2022929f-4b2b-4048-93be-c5add10bf6c6n%40googlegroups.com.

[Bennett Helm]

Sounds right. I'm mostly just making sure I've got a good grasp of what the standards are....

Bennett

[Bennett Helm]

I've been looking at artwork for this book. My first choice is Winslow Homer's "The Cotton Pickers". The link is to the Los Angeles County Museum of Art, which has details of its provenance (created in 1876 by an artist who died in 1910). However, LACMA does not explicitly list this painting as CC0, and I have been unable to find a page scan of it in a book published before 1931. As I understand it, then, this one would not be permitted.

Failing that, my second choice is William Gilbert Gaul's "Picking Cotton". The link is to the National Gallery of Art, which indicates that it is CC0. Would that work?

Bennett

[Robin Whittleton]

Yep, as you say, it’d need to be CC0 or in a book. But you’re in luck, I had a quick look and found it on the front cover of American Art News in 1916: https://archive.org/details/sim_artnews_1916-12-09_15_9/ . I’ve uploaded both to the artworks DB, so feel free to pick which one you’d prefer to use and I’ll assign it. If you use the Wilmslow Homer the site has a super-high resolution TIFF available which drops to 25MB if you save it as a 100% JPEG.

-Robin

To view this discussion visit https://groups.google.com/d/msgid/standardebooks/a410ac67-8eff-433b-85c9-0e037de4e62bn%40googlegroups.com.

[Bennett Helm]

Good find! I'll go with the Winslow Homer, then.

Below is a low-quality, reduced-size version of the cropped image I'd intend to use. The high-quality, full-sized (1400 x 2100) version is 1.4 MB, and the conversion I made of the original 236 MB .tiff cuts it down to a 12 MB .jpg. Are those appropriate file sizes to commit to github? 

Bennett

 

[Robin Whittleton]

Anything up to 100MB is fine for GitHub. But I’d export the cover crop at 80 jpeg quality, more is normally really not visually discernible, and it cuts the download size for our users. Also have a think about how the titlebox sits over the image: you might find that you need to crop so that the centre of focus is slightly higher than you expect. But I’ll leave that to your eye.

-Robin

On 18 Jun 2026, at 20:55, Bennett Helm <bennet...@gmail.com> wrote:



Good find! I'll go with the Winslow Homer, then.

Below is a low-quality, reduced-size version of the cropped image I'd intend to use. The high-quality, full-sized (1400 x 2100) version is 1.4 MB, and the conversion I made of the original 236 MB .tiff cuts it down to a 12 MB .jpg. Are those appropriate file sizes to commit to github? 

Bennett

 

<cover-small.jpg>

To view this discussion visit https://groups.google.com/d/msgid/standardebooks/3f4c7741-2b1a-4870-887a-949d77a7aeffn%40googlegroups.com.

<cover-small.jpg>

[David]

Just a thought — a glance at that image suggests it's fairly underexposed, confirmed by the histogram. A nudge of the levels gives this:

So it might be worth having a look at that while you're at it.

FWIW! David / Fife, UK

On Thursday, 18 June 2026 at 20:01:03 UTC+1 robin wrote:

Anything up to 100MB is fine for GitHub. But I’d export the cover crop at 80 jpeg quality, more is normally really not visually discernible, and it cuts the download size for our users. Also have a think about how the titlebox sits over the image: you might find that you need to crop so that the centre of focus is slightly higher than you expect. But I’ll leave that to your eye.

-Robin

On 18 Jun 2026, at 20:55, Bennett Helm wrote:

[Bennett Helm]

David -- you're absolutely right on the histogram. Robin, should I make this adjustment?

[Robin Whittleton]

Yep, that’s fine. Only make it to the cover.jpg, not cover.source.jpg. That stays the same, so if we need to tweak anything in future we’ve got an original copy.

-Robin

On 18 Jun 2026, at 22:00, Bennett Helm <bennet...@gmail.com> wrote:

David -- you're absolutely right on the histogram. Robin, should I make this adjustment?

--

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/485ca0f8-d460-4dc0-8537-bdd06899364fn%40googlegroups.com.

[Bennett Helm]

Got it.

I have a few proofreading/editorial questions. Given that the language is en-US, should I make the following editorial changes? —

1. "an holy" -> "a holy"
2. "centre" -> "center" (and "centring" -> "centering")

Also, should I ensure that there are non-breaking spaces after abbreviations of people's titles ("Mrs. Smith", "Hon. Jones", etc.) to keep the title and name together?

Bennett

[Robin Whittleton]

I wouldn’t worry about changing those spellings. Older en-US books often used en-GB / en-CA spellings for various words, and it’s a bit of a never ending game if you start going down that road.

For titles, yes, we’d typically include a non-breaking space, see https://standardebooks.org/manual/1.8.8/single-page#8.10.7.3. You might find though that running typogrify again catches them?

-Robin

To view this discussion visit https://groups.google.com/d/msgid/standardebooks/14b52d5b-5c70-44ed-9c68-2d68e8bc2a79n%40googlegroups.com.

[Bennett Helm]

I'm trying to figure out how to lay out the end of this book. See https://archive.org/details/questofsilverfle0000dubo_n0o6/page/434/mode/1up for the page scan. What I currently have is the following: 

<blockquote>
<p class="center">
<i xml:lang="fr">L’Envoi</i>
</p>
<p>
<i>Lend me thine ears, O God the Reader, whose Fathers aforetime sent mine down into the land of Egypt, into this House of Bondage. Lay not these words aside for a moment’s fantasy, but lift up thine eyes upon the Horror in this land;⁠—the maiming and mocking and murdering of my people, and the prisonment of their souls. Let my people go, O Infinite One, lest the world shudder at</i>
</p>
<p> </p>
<p class="center">
<b>The End</b>
</p>
</blockquote>

While in general "The End" is not supposed to appear, though in this case it is required to complete the final sentence. I have, however, kept it centered and with "<b>" tags around it, as in the original. Is that appropriate here?

The original also has vertical space above that final "The End", which to me seems appropriate (since "The End" is doing double duty as the end of the last sentence and as indicating the end of the work). Should I include that? If so, how is it best to achieve it? (I put in "<p> </p>", but I'm guessing that's wrong.)

Bennett

[Robin Whittleton]

You’re right: typically we wouldn’t include “The End”, but as it’s part of the sentence we would.

I think I’d add this as a new section at the end of the last chapter. Something like:

<section id="chapter-38-conclusion" epub:type="conclusion">

<h3 epub:type="title">

<i xml:lang="fr">L’Envoi</i>

</h3>

<p>Lend me thine ears, O God the Reader, whose Fathers aforetime sent mine down into the land of Egypt, into this House of Bondage. Lay not these words aside for a moment’s fantasy, but lift up thine eyes upon the Horror in this land;⁠—the maiming and mocking and murdering of my people, and the prisonment of their souls. Let my people go, O Infinite One, lest the world shudder at <b>The End</b></p>

</section>

You could then style this with:

#chapter-38-conclusion b{

display: block;

margin-top: 2em;

text-align: center;

}

Or something like that. Typically I wouldn’t retail large blocks of italics, but if you felt it adds to the reading experience you could style that with #chapter-38-conclusion > p{ font-style: italic; }.

-Robin

To view this discussion visit https://groups.google.com/d/msgid/standardebooks/1d4e1b74-a57a-457d-9a2c-1030ce390a0dn%40googlegroups.com.

[Weijia Cheng]

It might be better to make it a <div> instead of a section, and to use the 7.2.10.8 pattern, so that it doesn't appear in the table of contents.

[Robin Whittleton]

I was assuming it’d be wanted in the ToC, but yes, if not, follow Weijia’s example.

-Robin

To view this discussion visit https://groups.google.com/d/msgid/standardebooks/5652a346-96fd-4963-b243-c774d7fa78d6n%40googlegroups.com.

[Vince Rice]

The 7.2.10.8 pattern is specifically for sections (“Sections that require titles…”), so it can stay a section, it doesn’t need to be a div.

On Jun 24, 2026, at 8:09 AM, 'Weijia Cheng' via Standard Ebooks <standar...@googlegroups.com> wrote:

It might be better to make it a <div> instead of a section, and to use the 7.2.10.8 pattern, so that it doesn't appear in the table of contents.

[Bennett Helm]

I don't think it is wanted in the ToC. (It's not in the original page scans.)

So here's what I now have (including the very end of the main text):

<p>“Will you⁠—marry me, Bles?”</p>
</section>
<section id="chapter-38-section-1" epub:type="conclusion">
<p>
<b xml:lang="fr">L’Envoi</b>
</p>
<p>Lend me thine ears, O God the Reader, whose Fathers aforetime sent mine down into the land of Egypt, into this House of Bondage. Lay not these words aside for a moment’s fantasy, but lift up thine eyes upon the Horror in this land;⁠—the maiming and mocking and murdering of my people, and the prisonment of their souls. Let my people go, O Infinite One, lest the world shudder at</p>
<p>

<b>The End</b>
</p>
</section>

With the following css:

#chapter-38-section-1 > p{ font-style: italic; }
#chapter-38-section-1 b{
display: block;
margin-top: 2em;
margin-bottom: 1em;
text-align: center;
}

It renders fine, though `se lint` shows two manual review items that I assume we can ignore:

1. "Multiple <article>s or <section>s in file, but missing break-after: page;." (A page break is not in the original.)
2. "Possible typo: Paragraph missing ending punctuation." (This, of course, is not a typo.)

How does that look?

Bennett

[Weijia Cheng]

You should put the section inside of the chapter-level section instead of making them sibling elements. That would fix the first lint error. It would also be better to name the section "chapter-38-conclusion" as Robin suggested.

You should still use the 7.2.10.8 pattern to make "L’Envoi" the header of the section.

[Robin Whittleton]

Include the “The End” inside the final para. The styling will drop it down to a new line, and you won’t need a lint exception then.

On 24 Jun 2026, at 16:03, 'Weijia Cheng' via Standard Ebooks <standar...@googlegroups.com> wrote:



--

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/3d67f6d2-8cf2-4e7a-84c4-f74732b464een%40googlegroups.com.

[Bennett Helm]

I'm not sure I know what "use the 7.2.10.8 pattern" means: how much of the pattern do you mean? In particular, should the styling be applied to the <header> tag? I'm assuming not, since I want that styling to apply to "The End" as well. Here's what I currently have:

<section id="chapter-38-conclusion" epub:type="conclusion">

<header>

<p>
<b xml:lang="fr">L’Envoi</b>
</p>

</header>
<p>Lend me thine ears, O God the Reader, whose Fathers aforetime sent mine down into the land of Egypt, into this House of Bondage. Lay not these words aside for a moment’s fantasy, but lift up thine eyes upon the Horror in this land;⁠—the maiming and mocking and murdering of my people, and the prisonment of their souls. Let my people go, O Infinite One, lest the world shudder at <b>The End</b></p>
</section>

With the following css:

#chapter-38-conclusion > p{ font-style: italic; }
#chapter-38-conclusion b{
display: block;
margin-top: 2em;
text-align: center;
}

Note that I still get the "Possible typo" lint issue. (I could put a period after "The End", but that's not in the original.)

Bennett

[Weijia Cheng]

Try

<section id="chapter-38-conclusion" epub:type="conclusion">

<header>

<p xml:lang="fr">L’Envoi</p>

</header>
<p>Lend me thine ears, O God the Reader, whose Fathers aforetime sent mine down into the land of Egypt, into this House of Bondage. Lay not these words aside for a moment’s fantasy, but lift up thine eyes upon the Horror in this land;⁠—the maiming and mocking and murdering of my people, and the prisonment of their souls. Let my people go, O Infinite One, lest the world shudder at <b>The End</b></p>
</section>

header{
font-variant: small-caps;
margin: 1em;
text-align: center;
}

#chapter-38-conclusion > p{ font-style: italic; }
#chapter-38-conclusion b{
display: block;
margin-top: 2em;
text-align: center;
}

The "L’Envoi" doesn't need a <b> tag when you can get the small-caps effect from the header CSS. The header and "The End" shouldn't share styling.

Also, you can put in a se-lint-ignore entry for the lack of punctuation at the end.

[Bennett Helm]

Got it. I added "font-style: italic;" to the header element and "font-style: normal;" to the b element in CSS, to match formatting in the original.

I've also added the following for the se-lint-ignore.xml file:

<?xml version="1.0" encoding="utf-8"?>
<se-lint-ignore>
<file path="chapter-38.xhtml">
<ignore code="y-003">
<reason>The final sentence ends without punctuation.</reason>
</ignore>
</file>
</se-lint-ignore>

However, when I run lint, I get: "Error  se-lint-ignore.xml is invalid: failed to compile: Wrong escape sequence, misuse of character '\'". ... But I don't have a "\" in the file. Also, when I try pasting in the example from https://standardebooks.org/manual/1.8.8/single-page#2.3, I get the same error. Any ideas what's going wrong?

Bennett

[Robin Whittleton]

Difficult to tell as you haven’t pushed your file, but I took the example you pasted there, added it to a copy of your repo, and didn’t get that error when linting. Are you on the latest version of the standardebooks package?

-Robin

To view this discussion visit https://groups.google.com/d/msgid/standardebooks/313bb0ec-4541-4a8a-8f69-caa378090180n%40googlegroups.com.

[Bennett Helm]

Yes, I'm on latest standardebooks package (via brew): 3.1.0.

I just pushed my repo to github.

Bennett

[Alex Cabal]

This has happened before to several people and it has to do with your
python version, but I can't remember the details. Try updating to the
latest python, or reinstalling the toolset completely.

>> manual/1.8.8/single-page#2.3 <https://standardebooks.org/
>> manual/1.8.8/single-page#2.3>, I get the same error. Any ideas

>> what's going wrong?
>>
>> Bennett
>>
>> On Wednesday, June 24, 2026 at 11:20:15 AM UTC-4 weij...@bu.edu

>> <http://bu.edu/>wrote:

>> I'm not sure I know what "use the7.2.10.8 <https://
>> standardebooks.org/manual/1.8.8/7-high-level-structural-
>> patterns#7.2.10.8>pattern" means: how much of the pattern

>>> You should still use the7.2.10.8 <https://
>>> standardebooks.org/manual/1.8.8/7-high-level-
>>> structural-patterns#7.2.10.8>pattern to make

>>> 1. "Multiple <article>s or <section>s in file,

>>> but missing break-after: page;." (A page
>>> break is not in the original.)

>>> 2. "Possible typo: Paragraph missing ending

>>> punctuation." (This, of course, is not a typo.)
>>>
>>> How does that look?
>>>
>>> Bennett
>>>
>>>
>>> On Wednesday, June 24, 2026 at 9:43:53 AM UTC-4
>>> Vince Rice wrote:
>>>
>>> The 7.2.10.8 pattern is specifically for
>>> sections (“Sections that require titles…”),
>>> so it can stay a section, it doesn’t need to
>>> be a div.
>>>
>>>> On Jun 24, 2026, at 8:09 AM, 'Weijia Cheng'
>>>> via Standard Ebooks
>>>> <standar...@googlegroups.com> wrote:
>>>>
>>>> It might be better to make it a <div>
>>>> instead of a section, and to use the

>>>> 7.2.10.8 <https://standardebooks.org/
>>>> manual/1.8.8/7-high-level-structural-
>>>> patterns#7.2.10.8> pattern, so that it

>>>> doesn't appear in the table of contents.
>>>
>>>
>>> --
>>> 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
>>> tostandardebook...@googlegroups.com.
>>> To view this discussion visithttps://
>>> groups.google.com/d/msgid/
>>> standardebooks/3d67f6d2-8cf2-4e7a-84c4-

>>> f74732b464een%40googlegroups.com <https://
>>> groups.google.com/d/msgid/
>>> standardebooks/3d67f6d2-8cf2-4e7a-84c4-
>>> f74732b464een%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 tostandardebook...@googlegroups.com.
>> To view this discussion visithttps://groups.google.com/d/msgid/

>> standardebooks/313bb0ec-4541-4a8a-8f69-
>> caa378090180n%40googlegroups.com <https://groups.google.com/d/
>> msgid/standardebooks/313bb0ec-4541-4a8a-8f69-
>> caa378090180n%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/12c6027f-6be7-4366-84f7-606f0faa043bn%40googlegroups.com
> <https://groups.google.com/d/msgid/
> standardebooks/12c6027f-6be7-4366-84f7-606f0faa043bn%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

[Vince]

I believe it’s also happened when passing lint the wrong directory. Lint should be run for the top-level directory of the book, e.g. either `lint .` if your pwd is that directory, or `lint <path>/author-name_book-name` if it's not.

[Bennett Helm]

I am running `se lint .` in the root directory of the project.

I have 3 versions of python installed via brew: 3.14.6, 3.13.14, and 3.12.13_4; the first of these (3.14.6) is linked to "python3" and so is the default.

I tried `brew uninstall standardebooks` and then `brew install standardebooks`, but I still get the same error. I tried switching the default python version to the other two, and still get the same error.

In the meantime, I can run `se lint -s .` and see all the other lint errors/warnings.

Bennett

[Alex Cabal]

Try editing se/data/se-lint-ignore.rng and replacing line 8 with:

<param name="pattern">[-/a-z0-9.*?!\[\]]+</param>

Then try running lint again to see if that works

On 6/24/26 3:50 PM, Bennett Helm wrote:
> I am running `se lint .` in the root directory of the project.
>
> I have 3 versions of python installed via brew: 3.14.6, 3.13.14, and
> 3.12.13_4; the first of these (3.14.6) is linked to "python3" and so is
> the default.
>
> I tried `brew uninstall standardebooks` and then `brew install
> standardebooks`, but I still get the same error. I tried switching the
> default python version to the other two, and still get the same error.
>
> In the meantime, I can run `se lint -s .` and see all the other lint
> errors/warnings.
>
> Bennett
>
>
> On Wednesday, June 24, 2026 at 4:17:36 PM UTC-4 Vince wrote:
>

> I /believe/ it’s also happened when passing lint the wrong

> directory. Lint should be run for the top-level directory of the
> book, e.g. either `lint .` if your pwd is that directory, or `lint
> <path>/author-name_book-name` if it's not.
>
>
>> On Jun 24, 2026, at 3:04 PM, 'Alex Cabal' via Standard Ebooks
>> <standar...@googlegroups.com> wrote:
>>
>> This has happened before to several people and it has to do with
>> your python version, but I can't remember the details. Try
>> updating to the latest python, or reinstalling the toolset completely.
>>
>> On 6/24/26 1:33 PM, Bennett Helm wrote:
>>> Yes, I'm on latest standardebooks package (via brew): 3.1.0.
>>> I just pushed my repo to github.
>

> --
> 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/f0f4c479-a362-42ec-a7d4-25d52ad4537an%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/f0f4c479-a362-42ec-
> a7d4-25d52ad4537an%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Bennett Helm]

Yes, that works: no error from `se lint .`, and the output correctly ignores the warning.

Bennett

[Alex Cabal]

OK, you can keep that change in your local install to fix it, and I'll
update the toolset with this in the next version.

> <https://groups.google.com/d/msgid/>
> > standardebooks/f0f4c479-a362-42ec-
> a7d4-25d52ad4537an%40googlegroups.com <http://40googlegroups.com>
> > <https://groups.google.com/d/msgid/standardebooks/f0f4c479-
> a362-42ec- <https://groups.google.com/d/msgid/standardebooks/
> f0f4c479-a362-42ec->
> > a7d4-25d52ad4537an%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/7b683d79-1e86-493f-a54f-e258c18c7880n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/7b683d79-1e86-493f-
> a54f-e258c18c7880n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Bennett Helm]

I'm getting close. I think just one final thing: laying out the signature line in the preface. The source has the signature with the location and date left justified, and the author right justified. So I put that into a table, adding a "text-align='right'" to the cell containing the author. But running `se build --check-only` gave me an error, indicating that I shouldn't use "text-align". So I added a class with styling in the .css, but `se lint` gave an error, indicating that I shouldn't have a single-use class, but should craft a selector instead. So I try an "id" selector instead, but `se lint` still gives me a warning that I have an "Unused id attribute". So I'm not sure what you're looking for.

Here's what I currently have:

<table>
<tbody>
<tr>
<td id="preface-td-1">
<b>New York City,</b>
</td>
<td id="preface-td-2">
<b>The Author.</b>
</td>
</tr>
<tr>
<td>
<i>August 15, 1911.</i>
</td>
<td/>
</tr>
</tbody>
</table>

... with this .css:

#preface table{
width: 100%;
}

#preface-td-1{
text-align: initial;
}

#preface-td-2{
text-align: right;
}

Suggestions?

Bennett

[Alex Cabal]

Robin, thoughts?

On 6/27/26 1:49 PM, Bennett Helm wrote:
> I'm getting close. I think just one final thing: laying out the

> signature line in the preface. The source <https://archive.org/details/
> questofsilverfle0000dubo_n0o6/page/n14/mode/1up> has the signature with

> > <https://groups.google.com/d/msgid/ <https://groups.google.com/d/
> msgid/>>
> > > standardebooks/f0f4c479-a362-42ec-
> > a7d4-25d52ad4537an%40googlegroups.com <http://40googlegroups.com>
> <http://40googlegroups.com <http://40googlegroups.com>>
> > > <https://groups.google.com/d/msgid/standardebooks/f0f4c479-

> <https://groups.google.com/d/msgid/standardebooks/f0f4c479->
> > a362-42ec- <https://groups.google.com/d/msgid/standardebooks/
> <https://groups.google.com/d/msgid/standardebooks/>
> > f0f4c479-a362-42ec->

> > > a7d4-25d52ad4537an%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/7b683d79-1e86-493f-a54f-
> e258c18c7880n%40googlegroups.com <http://40googlegroups.com>
> > <https://groups.google.com/d/msgid/
> standardebooks/7b683d79-1e86-493f- <https://groups.google.com/d/
> msgid/standardebooks/7b683d79-1e86-493f->
> > a54f-e258c18c7880n%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/2bcf714c-507e-4015-abc9-059e43721801n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/2bcf714c-507e-4015-
> abc9-059e43721801n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Robin Whittleton]

Sorry, missed this one.

You definitely don’t want to use a table here, and given that it’s just a preface I wouldn’t try to replicate the exact layout: it’s the sort of thing that would change between different imprints and releases anyway. I’d just go with our standard markup:

<footer>

<p><b epub:type="z3998:signature">The Author</b>.<br/>

New York City,<br/>

<time datetime="1911-08-15">August 15, 1911</time>.</p>

</footer>

Then add standard footer styling as per https://standardebooks.org/manual/1.8.8/single-page#7.7.4.2. If you want to italicise the time then you can: time{ font-style: italic; } But I wouldn’t say it’s 100% necessary.

-Robin

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/2bcf714c-507e-4015-abc9-059e43721801n%40googlegroups.com.

[Bennett Helm]

Ok -- thanks.

I think I'm ready for a review of this. The git repository is here: https://github.com/bwhelm/DuBois-Quest-of-Silver-Fleece.

Bennett

[Weijia Cheng]

Ok, I'll work on the review soon.

[Weijia Cheng]

Great work, especially for a first project! I filed a review with some issues. For the most part, they are individually long and shouldn't take too long to complete.

[Weijia Cheng]

*individually small

[Bennett Helm]

Thanks. I've made those corrections, and pushed to github. Let me know if there's anything further I should do.

Bennett

[Weijia Cheng]

Thanks! I found two minor corrections to make, and after that this should be good to go.

[Bennett Helm]

All done. Let me know if I should close the github issue.

[Weijia Cheng]

Alex, this is ready for you.

[Alex Cabal]

OK, great work Bennet! Good attention to detail and very good long
description. I've released it, thanks!

> <https://github.com/bwhelm/DuBois-Quest-of-
> Silver-Fleece>.

>
> Bennett
>
> On Monday, June 29, 2026 at 3:07:13 PM UTC-4
> robin wrote:
>
> Sorry, missed this one.
>
> You definitely don’t want to use a table
> here, and given that it’s just a preface
> I wouldn’t try to replicate the exact
> layout: it’s the sort of thing that
> would change between different imprints
> and releases anyway. I’d just go with
> our standard markup:
>
> <footer>
> <p><b epub:type="z3998:signature">The
> Author</b>.<br/>
> New York City,<br/>
> <time datetime="1911-08-15">August 15,
> 1911</time>.</p>
> </footer>
>
> Then add standard footer styling as per
> https://standardebooks.org/manual/1.8.8/

> single-page#7.7.4.2 <https://
> standardebooks.org/manual/1.8.8/single-
> page#7.7.4.2>. If you want to italicise

> the time then you can: time{ font-style:
> italic; } But I wouldn’t say it’s 100%
> necessary.
>
> -Robin
>
>> On 27 Jun 2026, at 20:49, Bennett Helm
>> <bennet...@gmail.com> wrote:
>>
>> I'm getting close. I think just one
>> final thing: laying out the signature
>> line in the preface.The source

>> <https://archive.org/details/
>> questofsilverfle0000dubo_n0o6/page/
>> n14/mode/1up>has the signature with

>> > <https://groups.google.com/d/

>> msgid/ <https://groups.google.com/
>> d/msgid/>>
>> > > standardebooks/f0f4c479-a362-42ec-
>> >

>> a7d4-25d52ad4537an%40googlegroups.com <http://40googlegroups.com/><http://40googlegroups.com <http://40googlegroups.com/>>
>> > > <https://groups.google.com/d/
>> msgid/standardebooks/f0f4c479-
>> <https://groups.google.com/d/
>> msgid/standardebooks/f0f4c479->
>> > a362-42ec- <https://
>> groups.google.com/d/msgid/
>> standardebooks/ <https://
>> groups.google.com/d/msgid/
>> standardebooks/>
>> > f0f4c479-a362-42ec->
>> > >
>> a7d4-25d52ad4537an%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
>> tostandardebook...@googlegroups.com
>> >

>> <mailto:standardebook...@googlegroups.com>.
>> > To view this discussion
>> visithttps://groups.google.com/d/
>> msgid/ <https://groups.google.com/
>> d/msgid/>
>> >

>> standardebooks/7b683d79-1e86-493f-
>> a54f-
>> e258c18c7880n%40googlegroups.com
>> <http://40googlegroups.com/>
>> > <https://groups.google.com/d/
>> msgid/
>> standardebooks/7b683d79-1e86-493f-
>> <https://groups.google.com/d/
>> msgid/
>> standardebooks/7b683d79-1e86-493f->
>> > a54f-
>> e258c18c7880n%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 tostandardebook...@googlegroups.com.

>> To view this discussion visithttps://

>> groups.google.com/d/msgid/
>> standardebooks/2bcf714c-507e-4015-
>> abc9-059e43721801n%40googlegroups.com
>> <https://groups.google.com/d/msgid/
>> standardebooks/2bcf714c-507e-4015-
>> abc9-059e43721801n%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/89884df1-7127-4c7c-a185-b754123a4da3n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/89884df1-7127-4c7c-
> a185-b754123a4da3n%40googlegroups.com?utm_medium=email&utm_source=footer>.