[Project] Back to Methuselah, by George Bernard Shaw

98 views
Skip to first unread message

Asher Smith

unread,
Jan 3, 2026, 8:44:16 PMJan 3
to Standard Ebooks
My next project will be Back to Methuselah, continuing with the George Bernard Shaw. This one is rather longer, and seems like it will be the most complicated structurally since Man and Superman, or perhaps Fanny's First Play: it's a 30k word long preface followed by a sequence of five plays. I imagine it will take me some time to produce.

For the preface, which has a series of subdivisions, I propose to have a series of <h3> subdivisions but a single preface.xhtml file, rather than several dozen preface files. It will of course have a halftitlepage.xhtml after that with the title of the whole volume. The other frontmatter will be a dramatis-personae, which I think will be for all five plays separated by headings within (like that in Fanny's First Play), rather than five separate dramatis personae files.

The plays are a mix of one-, two-, and three-act plays. I'm struggling to parse how SEMoS 7.2 would apply here, so would appreciate some guidance on this before I try to commit anything to text.
  • For all of them, I propose to have part-N.xhtml pages with <h2> elements. The page scans show that the titles of the parts include a subtitle in the table of contents that is not then repeated on the part title page; I'm proposing to include the part number, the title, and the subtitle(s) all on the part title pages. I think that this means that, for example, "Part III" would be <h2>, "The Thing Happens" would be <p> styled with nth-child to be the same size as the <h2> and tagged epub:type="title", and then "A.D. 2170" would be a <p> tagged epub:type="subtitle" and styled smaller, all of which would be within an <hgroup> - is that correct? Is there a semantically correct way to make more than just "Part N" appear in the ToC?
  • For the multi-act plays, the filenames will be the standard act-1-1.xhtml; they will contain standard <h3> elements with the act number, but will not repeat the <h2> name of the play (which the page scans do).
  • For the one-act plays, the filenames will follow SE convention and be the name of the play. Usually, they would contain an <h3> element which is the name of the play, but that would have the unfortunate consequence of the ToC having a second line with the same name on it. As per SEMoS 7.2.10.8, I would be tempted to give them a title that would not appear in the ToC via a <p> in the <header> - is this allowed?
Apart from those issues, there are the usual GBS foibles vis-à-vis contractions, some pretty standard together dialogue formatting, and the odd verse blockquote. I can use these IA scans, and this PG transcription.

Emma Sweeney

unread,
Jan 4, 2026, 12:17:21 AMJan 4
to Standard Ebooks
1. I think <h3> subdivisions inside the preface.xhtml is fine. That is a really long preface!
2. That title structure is fine. If you structure the part titles like in SEMoS 7.2.10.6 plus a subtitle, the label, ordinal, and title will appear in the ToC.
3. That's correct; don't repeat the part names.
3. If there is a part with no act title, you can have the dialogue inside the part file. There's no need for an repeated header.

it seems like the file names and order would be:

part-1.xhtml
act-1-1.xhtml
act-1-2.xhtml
act-1-3.xhtml
part-2.xhtml
part-3.xhtml
part-4.xhtml
act-4-1.xhtml
act-4-2.xhtml
act-4-3.xhtml
part-5.xhtml


Emma

Asher Smith

unread,
Jan 4, 2026, 2:10:32 AMJan 4
to standar...@googlegroups.com
OK, that makes sense to me, thanks! I presume that I just target those particular header with a "break-after: page” to get the same effect?

-- 
You received this message because you are subscribed to a topic in the Google Groups "Standard Ebooks" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/standardebooks/EiGjMuXBk5Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to standardebook...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/standardebooks/21790471-6926-45e4-a575-3ce14a5957d0n%40googlegroups.com.

Emma Sweeney

unread,
Jan 4, 2026, 3:01:13 AMJan 4
to Standard Ebooks
You could do that.

Emma

Alex Cabal

unread,
Jan 5, 2026, 2:16:27 PMJan 5
to standar...@googlegroups.com
Can you send a link to your repo?

On 1/3/26 7:44 PM, Asher Smith wrote:
> My next project will be /Back to Methuselah/, continuing with the George
> Bernard Shaw. This one is rather longer, and seems like it will be the
> most complicated structurally since /Man and Superman/, or perhaps /
> Fanny's First Play/: it's a 30k word long preface followed by a sequence
> of five plays. I imagine it will take me some time to produce.
>
> For the preface, which has a series of subdivisions, I propose to have a
> series of <h3> subdivisions but a single preface.xhtml file, rather than
> several dozen preface files. It will of course have a
> halftitlepage.xhtml after that with the title of the whole volume. The
> other frontmatter will be a dramatis-personae, which I think will be for
> all five plays separated by headings within (like that in /Fanny's First
> Play/), rather than five separate dramatis personae files.
>
> The plays are a mix of one-, two-, and three-act plays. I'm struggling
> to parse how SEMoS 7.2 would apply here, so would appreciate some
> guidance on this before I try to commit anything to text.
>
> * For all of them, I propose to have part-N.xhtml pages with <h2>
> elements. The page scans show that the titles of the parts include a
> subtitle in the table of contents that is not then repeated on the
> part title page; I'm proposing to include the part number, the
> title, and the subtitle(s) all on the part title pages. I think that
> this means that, for example, "Part III" would be <h2>, "The Thing
> Happens" would be <p> styled with nth-child to be the same size as
> the <h2> and tagged epub:type="title", and then "A.D. 2170" would be
> a <p> tagged epub:type="subtitle" and styled smaller, all of which
> would be within an <hgroup> - is that correct? Is there a
> semantically correct way to make more than just "Part N" appear in
> the ToC?
> * For the multi-act plays, the filenames will be the standard
> act-1-1.xhtml; they will contain standard <h3> elements with the act
> number, but will not repeat the <h2> name of the play (which the
> page scans do).
> * For the one-act plays, the filenames will follow SE convention and
> be the name of the play. Usually, they would contain an <h3> element
> which is the name of the play, but that would have the unfortunate
> consequence of the ToC having a second line with the same name on
> it. As per SEMoS 7.2.10.8 <https://standardebooks.org/manual/1.8.5/
> single-page#7.2.10.8>, I would be tempted to give them a title that
> would not appear in the ToC via a <p> in the <header> - is this allowed?
>
> Apart from those issues, there are the usual GBS foibles vis-à-vis
> contractions, some pretty standard together dialogue formatting, and the
> odd verse blockquote. I can use these IA scans <https://archive.org/
> details/in.ernet.dli.2015.208046/>, and this PG transcription <https://
> gutenberg.org/cache/epub/13084/pg13084-images.html>.
>
> --
> 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/ab21c12e-7de1-4563-978a-1dd8a2d97ed4n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/
> ab21c12e-7de1-4563-978a-1dd8a2d97ed4n%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

Asher Smith

unread,
Jan 6, 2026, 6:12:06 AMJan 6
to standar...@googlegroups.com

Alex Cabal

unread,
Jan 6, 2026, 1:17:10 PMJan 6
to standar...@googlegroups.com
OK, Vince will manage with David reviewing.

On 1/6/26 5:11 AM, Asher Smith wrote:
> george-bernard-shaw_back-to-methuselah.png
> ACBSmith/george-bernard-shaw_back-to-methuselah <https://github.com/
> ACBSmith/george-bernard-shaw_back-to-methuselah>
> github.com <https://github.com/ACBSmith/george-bernard-shaw_back-to-
> methuselah>
>
> <https://github.com/ACBSmith/george-bernard-shaw_back-to-methuselah>
>>> manual/1.8.5/ <https://standardebooks.org/manual/1.8.5/>
>>>    single-page#7.2.10.8>, I would be tempted to give them a title that
>>>    would not appear in the ToC via a <p> in the <header> - is this
>>> allowed?
>>> Apart from those issues, there are the usual GBS foibles vis-à-vis
>>> contractions, some pretty standard together dialogue formatting, and
>>> the odd verse blockquote. I can use these IA scans <https://
>>> archive.org/ details/in.ernet.dli.2015.208046/ <https://archive.org/
>>> %20details/in.ernet.dli.2015.208046/>>, and this PG transcription
>>> <https://gutenberg.org/cache/epub/13084/pg13084-images.html <http://
>>> gutenberg.org/cache/epub/13084/pg13084-images.html>>.
>>> --
>>> 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 tostandardeboo...@googlegroups.com
>>> <mailto:standardebook...@googlegroups.com><mailto:standardebook...@googlegroups.com <mailto:standardebook...@googlegroups.com>>.
>>> To view this discussion visithttps://groups.google.com/d/msgid/
>>> <https://groups.google.com/d/msgid/>standardebooks/
>>> ab21c12e-7de1-4563-978a-1dd8a2d97ed4n%40googlegroups.com
>>> <http://40googlegroups.com/><https://groups.google.com/d/msgid/
>>> standardebooks/
>>> ab21c12e-7de1-4563-978a-1dd8a2d97ed4n%40googlegroups.com?
>>> utm_medium=email&utm_source=footer <https://groups.google.com/d/
>>> msgid/standardebooks/
>>> %20ab21c12e-7de1-4563-978a-1dd8a2d97ed4n%40googlegroups.com?
>>> %20utm_medium=email&utm_source=footer>>.
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Standard Ebooks" group.
>> To unsubscribe from this topic, visithttps://groups.google.com/d/
>> topic/standardebooks/EiGjMuXBk5Q/unsubscribe <https://
>> groups.google.com/d/topic/standardebooks/EiGjMuXBk5Q/unsubscribe>.
>> To unsubscribe from this group and all its topics, send an email
>> tostandardeboo...@googlegroups.com
>> <mailto:standardebook...@googlegroups.com>.
>> To view this discussion visithttps://groups.google.com/d/msgid/
>> standardebooks/38449d66-ae18-4279-
>> a22d-80249345e353%40standardebooks.org <https://groups.google.com/d/
>> msgid/standardebooks/38449d66-ae18-4279-
>> a22d-80249345e353%40standardebooks.org>.
>
> --
> 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/AFE07048-B5B2-42D3-B61B-BD9A8EE08B73%40gmail.com
> <https://groups.google.com/d/msgid/standardebooks/AFE07048-B5B2-42D3-
> B61B-BD9A8EE08B73%40gmail.com?utm_medium=email&utm_source=footer>.

Asher Smith

unread,
Feb 21, 2026, 6:15:56 AM (yesterday) Feb 21
to Standard Ebooks
Quick question about SEMoS 8.10.5 - does this also apply to orders or titles? If someone has an OBE or the like (in the case of this book, a made-up title written as "O.M."), is it treated the same way as this? Or do I just give it a standard initialism semantic?
Message has been deleted

David Reimer

unread,
Feb 21, 2026, 6:37:49 AM (yesterday) Feb 21
to standar...@googlegroups.com
While we wait for Vince, I expect you've already noticed that the corpus is divided on the issue. Perhaps that's what prompts the question! There are others that are split over `name-title` v. `initialism`, too.

And could the "OM" be Order of Merit?

Asher Smith

unread,
Feb 21, 2026, 6:43:49 AM (yesterday) Feb 21
to Standard Ebooks
I was thinking it might be an Order of Merit, but the play is set in the year 3000 so I wasn't sure. If that is the case, then I think it should probably be styled without the periods and in small caps.

It might be a question for Alex, then, and we can put the answer into SEMoS to forestall further questions. This would apply to membership of orders or fellowship of societies (e.g. FRS).

Asher Smith

unread,
Feb 21, 2026, 9:57:40 AM (yesterday) Feb 21
to Standard Ebooks
Unrelatedly, could I please claim this artwork from the database? The first play takes place in the Garden of Eden and the last in another natural setting; while it may come to pass that I have a better idea, I think it not unlikely that I'll stay with this.

Vince

unread,
Feb 21, 2026, 1:12:54 PM (yesterday) Feb 21
to Ebooks Standard
I would assume it’s an Order of Merit, and in the absence of an Alex override, I would also assume name-title is the best fit. I don’t see any reason for it to be small caps—it’s not an acronym.

Vince

unread,
Feb 21, 2026, 1:13:42 PM (yesterday) Feb 21
to Ebooks Standard
I don’t see any reason why not, but would you please do a mockup so we can see the crop?

Asher Smith

unread,
Feb 21, 2026, 4:25:03 PM (yesterday) Feb 21
to Standard Ebooks
I've definitely seen honorifics given the small caps treatment; Wikipedia is one place where post-nominals are given small caps. However, I see that CMOS says they're to be in all caps, so I'm assuming that's the desired outcome.
For a crop, I'm thinking like this:
Screenshot 2026-02-21 at 21.22.59.png

Vince

unread,
Feb 21, 2026, 6:37:35 PM (23 hours ago) Feb 21
to Ebooks Standard
Perfect, thanks, looks good! I’ve assigned it.

Right, we don’t care what other people are doing, we care what SEMoS says do. :)

On Feb 21, 2026, at 3:25 PM, Asher Smith <forlackofa...@gmail.com> wrote:

I've definitely seen honorifics given the small caps treatment; Wikipedia is one place where post-nominals are given small caps. However, I see that CMOS says they're to be in all caps, so I'm assuming that's the desired outcome.
For a crop, I'm thinking like this:
Reply all
Reply to author
Forward
0 new messages