[First Project] Manalive by G.K. Chesterton

[Ryan Vanden Bos]

Hello,

I love all the work you guys do here. I have a technical background and would love to give back and produce a new ebook!

I would like to start with Manalive by G.K. Chesteron using Project Gutenburg's text.

Any tips/guidance before I start hacking away at it?

Thanks,

Ryan

[Ryan Vanden Bos]

I'd love to give back and produce Manalive by G.K. Chesterton using PG's text.

Any tips/guidance before I start hacking away at it with the help of the MoS, etc.?

Thanks,

Ryan

[Alex Cabal]

Sure, that one would be a good start.

As the wanted list states, this transcription uses all caps instead of
italics, so you must restore italics. You should also eyeball each page
of the page scans to restore any missing italics/formatting (for example
on an italicized `I`).

I see some verse - see the manual for copy and paste HTML/CSS.

I also see at least one letter (starting with `Dear Sir,`) which should
be in a blockquote. See the manual again for styling.

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:

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 mark you as having started.

Have fun! :)

On 2/10/25 9:45 AM, Ryan Vanden Bos wrote:
> Hello,
>
> I love all the work you guys do here. I have a technical background and
> would love to give back and produce a new ebook!
>

> I would like to start with /Manalive
> <https://standardebooks.org/ebooks/g-k-chesterton/manalive>/ by G.K.

> Chesteron using Project Gutenburg's text

> <https://www.gutenberg.org/ebooks/1718>.

>
> Any tips/guidance before I start hacking away at it?
>
> Thanks,
>
> Ryan
>

> --
> 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/e334df53-fbba-42c9-85bb-fab176097cb9n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/e334df53-fbba-42c9-85bb-fab176097cb9n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Ryan Vanden Bos]

Thanks Alex!

I have started. Currently I have all of the chapters split up. HERE is the repo.

[Alex Cabal]

OK, Lukas will manage this with Robin reviewing.

On 2/11/25 8:34 AM, Ryan Vanden Bos wrote:
> Thanks Alex!
>
> I have started. Currently I have all of the chapters split up. HERE

> <https://github.com/rvbcldud/se-gk-chesterton-manalive.git> is the repo.

>
> On Monday, February 10, 2025 at 10:28:38 AM UTC-8 Alex Cabal wrote:
>
> Sure, that one would be a good start.
>
> As the wanted list states, this transcription uses all caps instead of
> italics, so you must restore italics. You should also eyeball each page
> of the page scans to restore any missing italics/formatting (for
> example
> on an italicized `I`).
>
> I see some verse - see the manual for copy and paste HTML/CSS.
>
> I also see at least one letter (starting with `Dear Sir,`) which should
> be in a blockquote. See the manual again for styling.
>
> 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:
>

> 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>

> https://groups.google.com/d/msgid/standardebooks/e334df53-fbba-42c9-85bb-fab176097cb9n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/e334df53-fbba-42c9-85bb-fab176097cb9n%40googlegroups.com> <https://groups.google.com/d/msgid/standardebooks/e334df53-fbba-42c9-85bb-fab176097cb9n%40googlegroups.com?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/e334df53-fbba-42c9-85bb-fab176097cb9n%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/e9bc05da-cff6-477a-b3f5-7e32841d8f0fn%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/e9bc05da-cff6-477a-b3f5-7e32841d8f0fn%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Ryan Vanden Bos]

Hello,

I have done most of the automated bits of formatting and need help with some trickier parts:

• On line 108 of chapter-2-3 there is an extra single quote after "ancient eagles" ... should this be removed? Or am I missing something?
• On line 31 of chapter-2-4 "re" is italicized. Should I wrap it in an em tag ... if so, is this Latin, French? Let me know what you think!
• Starting on line 16 of chapter-1-3 I have started to format a snippet of verse. However, I am having trouble figuring out how to format the author's name "Tennyson" at the end. It should be right aligned ... but not all the way right. You know? Thanks for any help on that one.
• Lastly, I'd like some help formatting the letters in this book. There are several. They are usually enclosed all in double quotation marks and look very much like regular dialogue. I believe this is because they are likely being read aloud. How should I put these in the letter blockquote? Thanks again!
  • An example of this can be found on line 29 of chapter-2-3
• Let me know if you find anything else amiss

HERE is my repo for ease of access.

Ryan

[Lukas Bystricky]

On line 108 of chapter-2-3 there is an extra single quote after "ancient eagles" ... should this be removed?

It's a bit odd, but it looks to me like a possessive. As in the voice belongs to one of the ancient eagles. I would leave it.

On line 31 of chapter-2-4 "re" is italicized. Should I wrap it in an em tag 

In this context it stands for "regarding", so you can remove the italics.

Starting on line 16 of chapter-1-3 I have started to format a snippet of verse. However, I am having trouble figuring out how to format the author's name "Tennyson" at the end. It should be right aligned ... but not all the way right

You can apply rule 5.8.2 here. 

They are usually enclosed all in double quotation marks and look very much like regular dialogue.

It's fine to just include the quotation marks inside the blockquote. 

Just for future reference, for questions like these it's much easier for the manager if you include screenshots from the scans. 

[Ryan Vanden Bos]

Thanks Lukas! I will make sure to include scans next time.

Quick question (hopefully): My html text includes a good amount of word join characters (\u2060). Is it recommended to remove these or leave them in?

Thanks again.

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/oBuk3P4eQh8/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/a99377bc-3056-4eb5-bad3-0990bbcb1677n%40googlegroups.com.

[Ryan Vanden Bos]

It looks like 8.7.7.7 answers my question. So no worries there.

[Ryan Vanden Bos]

I am getting the following lint error:


When reading through the manual, it does not seem to require adding this CSS information. Is there something else wrong?

Thanks!

[Weijia Cheng]

See https://standardebooks.org/manual/1.8.2/7-high-level-structural-patterns#7.7.4.2

[Ryan Vanden Bos]

Thanks for the link. I’ve seen this. My understanding was that this was already applied to the footer element. Do I have to manual add this in somewhere?

Thanks!

To view this discussion visit https://groups.google.com/d/msgid/standardebooks/42125195-5be3-4377-9c2b-4d21eefbe57cn%40googlegroups.com.

[Lukas Bystricky]

You'll want to add this (and any other CSS you need) to src/epub/css/local.css.

[Ryan Vanden Bos]

Thanks for clarifying, Lukas. It helps a lot!

To view this discussion visit https://groups.google.com/d/msgid/standardebooks/ba7a66bd-0c75-438b-a4cb-bad9e29f5eedn%40googlegroups.com.

[Ryan Vanden Bos]

Hello again!

I am resuming work on this book. I am almost complete.

I am running into an issue with the ToC and data-parent attribute of the sections. There are 2 parts on Manalive. I have 2 part sections defined with IDs "part-1" and "part-2" and have the data-parent attribute of each chapter set accordingly. However, the linter is giving me errors and when I build the book the 2 part pages are at the end of the book.

I cannot seem to track down the issue. Any tips would be appreciated. Thanks!

[Weijia Cheng]

You need to manually rearrange the spine in content.opf to be in the appropriate order. So part 1 and then all of the part 1 chapters, and then part 2 and the part 2 chapters.