[Next Project] Emily Climbs (Emily of New Moon book 2)

[Ben Winstead]

Hello all,

I contributed a couple years back to this project and I wanted to give it another go with the second book in the series that I did before, Emily of New Moon. Last time I tried this I got a bit confused about the commit history issue that popped up before. If this project gets approved, what should I be thinking about and doing in terms of committing? I re-read the step by step guide which says to commit early and often, which I felt like I did, but there was some issue with unnecessary commits in the previous project which I want to avoid. Particularly where it says:

    "Commits are easy and free—it’s perfectly acceptable to have many very small commits,       as long as each one is a single logical unit of work and doesn’t mix editorial and non-             editorial changes."

 If I recall correctly the issues had something to do with me making commits as I went through each chapter instead of going through each chapter and committing after that step was done. So to confirm, when it says "single logical unit of work" does that mean "fixing the same issue throughout the chapters and then committing" or can it mean "fixing an issue that's present in the whole book, but only one chapter at a time"? I'm just trying to avoid a scenario where I need to rebase again 🙃. 

In regards to the book itself, Gutenberg doesn't have a copy of it but I did find the text on Wikisource here, and Archive.org has page scans here. Hopefully that would be enough to get started on.

[devino...@gmail.com]

Having worked with a few Wikisource transcriptions, I can tell you they're a huge pain to deal with, since they have all sorts of weird extra HTML code that you have to strip out.

However, Faded Page has a transcription of this book, and you can use "--fp-id" when you do "se create-draft" (instead of "--pg-id", which you use for Project Gutenberg transcriptions) to automatically download the transcription in the draft. It'd probably make for an easier transcription to work with, and an easier process.

Devin

[Alex Cabal]

Sure, you could work on that.

How to commit is a matter of general taste that goes beyond what SE
does. Put yourself in the shoes of someone looking at your history a
year from now. Is it easier to read 100 separate commits where each one
fixes a single typo? Or one single commit that fixes many minor typos
across the whole ebook?

Likewise, it is easier to read one single commit that typogrifies,
modernizes spelling, breaks up chapters, and also adds semantics? or 5
separate commits that each do one of those things?

For now, follow the step by step guide exactly. It will lay out the
exact commits you have to make to your ebook.

Once you get started, send a link to your repo so we can assign you a
manager and reviewer.

On 2/18/26 4:54 PM, Ben Winstead wrote:
> Hello all,
>
> I contributed a couple years back to this project and I wanted to give
> it another go with the second book in the series that I did before,

> Emily of New Moon <https://groups.google.com/g/standardebooks/c/
> XUKr_49Sqrg/m/ClTwvBjHBwAJ>. Last time I tried this I got a bit confused

> about the commit history issue that popped up before. If this project
> gets approved, what should I be thinking about and doing in terms of
> committing? I re-read the step by step guide which says to commit early
> and often, which I felt like I did, but there was some issue with
> unnecessary commits in the previous project which I want to avoid.
> Particularly where it says:
>
>     "Commits are easy and free—it’s perfectly acceptable to have many
> very small commits,       as long as each one is a single logical unit
> of work and doesn’t mix editorial and non-             editorial changes."
>
>  If I recall correctly the issues had something to do with me making
> commits as I went through each chapter instead of going through each
> chapter and committing after that step was done. So to confirm, when it
> says "single logical unit of work" does that mean "fixing the same issue
> throughout the chapters and then committing" or can it mean "fixing an
> issue that's present in the whole book, but only one chapter at a time"?
> I'm just trying to avoid a scenario where I need to rebase again 🙃.
>
> In regards to the book itself, Gutenberg doesn't have a copy of it but I

> did find the text on Wikisource here <https://en.wikisource.org/wiki/
> Emily_Climbs>, and Archive.org has page scans here <https://archive.org/
> details/emilyclimbs0000lucy_f3w1>. Hopefully that would be enough to get
> started on.
>
> --
> 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/dc168379-0e40-4e63-b136-223ffadee218n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/dc168379-0e40-4e63-
> b136-223ffadee218n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[devino...@gmail.com]

You could also use Project Gutenberg Australia's transcription, which is better than the Faded Page one, after taking a look at it. Just go here, right-click on the "HTML" link for Emily Climbs and click "Save Link As...", and then you can download it. (Always check, with either transcription, that it aligns with your page scans, of course.)

Devin 

[Ben Winstead]

If I'm using the Australian PG ID, the toolkit doesn't pull automatically since that ID isn't found on the gutenberg.org site. I can just leave that part out and place the single HTML file in the src/epub/text/ file and then work from there, right?

[Alex Cabal]

Please send a link to your repo, so that I can assign you a manager who
can best answer these questions. Thanks!

On 2/18/26 7:15 PM, Ben Winstead wrote:
> If I'm using the Australian PG ID, the toolkit doesn't pull
> automatically since that ID isn't found on the gutenberg.org site. I can
> just leave that part out and place the single HTML file in the src/epub/
> text/ file and then work from there, right?
>
> On Wednesday, February 18, 2026 at 7:25:23 PM UTC-5 devino...@gmail.com
> wrote:
>
> You could also use Project Gutenberg Australia's transcription

> <https://gutenberg.net.au/ebooks03/0300151h.html>, which is better

> than the Faded Page one, after taking a look at it. Just go here

> <https://gutenberg.net.au/plusfifty-a-m.html#montgomery>, right-
> click on the "HTML" link for /Emily Climbs/ and click "Save Link

> As...", and then you can download it. (Always check, with either
> transcription, that it aligns with your page scans, of course.)
>
> Devin
>
> On Wednesday, February 18, 2026 at 5:16:30 PM UTC-7
> devino...@gmail.com wrote:
>
> Having worked with a few Wikisource transcriptions, I can tell
> you they're a huge pain to deal with, since they have all sorts
> of weird extra HTML code that you have to strip out.
>

> However, Faded Page <https://www.fadedpage.com/showbook.php?
> pid=20160126> has a transcription of this book, and you can use

> "--fp-id" when you do "se create-draft" (instead of "--pg-id",
> which you use for Project Gutenberg transcriptions) to
> automatically download the transcription in the draft. It'd
> probably make for an easier transcription to work with, and an
> easier process.
>
> Devin
>
>
>
> On Wednesday, February 18, 2026 at 4:46:42 PM UTC-7
> bawin...@outlook.com wrote:
>
> Hello all,
>
> I contributed a couple years back to this project and I
> wanted to give it another go with the second book in the

> series that I did before, Emily of New Moon <https://
> groups.google.com/g/standardebooks/c/XUKr_49Sqrg/m/
> ClTwvBjHBwAJ>. Last time I tried this I got a bit confused

> about the commit history issue that popped up before. If
> this project gets approved, what should I be thinking about
> and doing in terms of committing? I re-read the step by step
> guide which says to commit early and often, which I felt
> like I did, but there was some issue with unnecessary
> commits in the previous project which I want to avoid.
> Particularly where it says:
>
>     "Commits are easy and free—it’s perfectly acceptable to
> have many very small commits,       as long as each one is a
> single logical unit of work and doesn’t mix editorial and
> non-             editorial changes."
>
>  If I recall correctly the issues had something to do with
> me making commits as I went through each chapter instead of
> going through each chapter and committing after that step
> was done. So to confirm, when it says "single logical unit
> of work" does that mean "fixing the same issue throughout
> the chapters and then committing" or can it mean "fixing an
> issue that's present in the whole book, but only one chapter
> at a time"? I'm just trying to avoid a scenario where I need
> to rebase again 🙃.
>
> In regards to the book itself, Gutenberg doesn't have a copy

> of it but I did find the text on Wikisource here <https://

> en.wikisource.org/wiki/Emily_Climbs>, and Archive.org has

> page scans here <https://archive.org/details/

> emilyclimbs0000lucy_f3w1>. Hopefully that would be enough to
> get started on.
>

> --
> 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/70c24430-1f5c-4fe7-8652-7d78bcf8446en%40googlegroups.com
> <https://groups.google.com/d/msgid/
> standardebooks/70c24430-1f5c-4fe7-8652-7d78bcf8446en%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

[Ben Winstead]

I did see the step that addresses that in the step by step guide but I just don't know if having the ID is preferred, if it's available.

[Ben Winstead]

Oh yes, here it is:
https://github.com/Revali25/emilyclimbs

[Alex Cabal]

OK, Lukas will manage with Weijia reviewing.

On 2/18/26 7:19 PM, Ben Winstead wrote:
> Oh yes, here it is:
> https://github.com/Revali25/emilyclimbs
>
>

> --
> 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/442e23bc-6112-404d-a1c0-9c765fc07c79n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/442e23bc-6112-404d-
> a1c0-9c765fc07c79n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Weijia Cheng]

Ok, I will review.

The option to create a project from the PG ID is just a shortcut. In principle you could everything it does manually.

[Ben Winstead]

Alright sounds good. I went ahead with the manual steps and continued from there. I've done the first three commits from the guide tonight and will continue the manual typography changes tomorrow, should I push those commits now or wait?

[Weijia Cheng]

It's better to push commits regularly in case something happens to your local repository.

[Ben Winstead]

I've pushed the first 3 commits from the guide. Could you take a look and make sure everything looks good to start out with? I'm going to be checking to make sure things are good frequently, I just want to avoid what happened last time. 

The fourth commit is the one where there's a manual check for typography, if I follow the steps from that list, the ones that use the interactive-replace commands, am I good to commit and push that to have as a baseline, then other manual changes can happen iteratively after I finish the other steps in the guide? Just checking because it's saying to do manual typography checking before committing and I'm not sure if that counts interactive-replace. 

[Ben Winstead]

Also, when checking if stretched words have non-breaking hyphens there was one word that came up that I'm unsure about, in chapter-24 line 17 there's "wee-est", I'm assuming that's not a word extension but applying "-est" to the word, but want to make sure. 

[Vince]

Lukas will answer your question, but when asking questions about the source, please provide a link to the page in the scans the question is about, so the manager can easily go straight to it.

[Ben Winstead]

https://archive.org/details/emilyclimbs0000lucy_f3w1/page/290/mode/2up

Here's the link to the specific page, it's typeset the same way in the book as it is in the file. It looks to me like it's supposed to be wee - est, with the est applied to wee, but wanted to confirm that leaving it as-is with a hyphen or if it should be an em-dash.

[Lukas Bystricky]

I've pushed the first 3 commits from the guide. Could you take a look and make sure everything looks good to start out with? I'm going to be checking to make sure things are good frequently, I just want to avoid what happened last time. 

Looks good so far!

The fourth commit is the one where there's a manual check for typography, if I follow the steps from that list, the ones that use the interactive-replace commands, am I good to commit and push that to have as a baseline, then other manual changes can happen iteratively after I finish the other steps in the guide? Just checking because it's saying to do manual typography checking before committing and I'm not sure if that counts interactive-replace.

It's up to you how you want to do it. What you proposed is absolutely fine, and it's probably what I would do. The important thing is to make sure each commit only contains one "type" of change.  So if you want to split manual typographic changes into many commits that's fine, but don't mix them with other kinds of commits, especially editorial ones. 

Also, when checking if stretched words have non-breaking hyphens there was one word that came up that I'm unsure about, in chapter-24 line 17 there's "wee-est", I'm assuming that's not a word extension but applying "-est" to the word, but want to make sure. 

I think in context it's the superlative of wee, i.e. most wee. Searching for "weest" in Merriam Webster links to the page for wee, so I would change it (as an [Editorial] commit) to weest. 

[devino...@gmail.com]

Hello Ben,

I find that managing my commits is much easier with a desktop application (rather than exclusively using the terminal), so you can download GitHub Desktop for free, if that makes managing your commits easier. I personally use SmartGit, which I find to be more robust and easier to manage my commits than GitHub Desktop, though both are fine. (With SmartGit, you need to have a licence, but if all your code on GitHub is for Standard Ebooks, you can apply for a Hobby Licence and use it for free.)

Devin