[First Project] Ralestone Luck by Andre Norton

[Cecil New]

Hello,

I'd like to start with one I found on the "wanted list":

• Ralestone Luck by Andre Norton
• https://www.gutenberg.org/ebooks/18817

Gutenberg already has several Ebook formats, plain text, and an HTML version (which is online).

Please let me know if I may proceed.

Regards,

Cecil

[Alex Cabal]

Great, that one would be a good start.

Cut the illustrations. There is an epigraph so you'll have to include a
half title page.

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 4/14/25 9:43 PM, Cecil New wrote:
> Hello,
>
> I'd like to start with one I found on the "wanted list":
>

> * Ralestone Luck by Andre Norton
> * https://www.gutenberg.org/ebooks/18817

>
> Gutenberg already has several Ebook formats, plain text, and an HTML
> version (which is online).
>
> Please let me know if I may proceed.
>
> Regards,
> 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
> <mailto:standardebook...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/
> standardebooks/49900cfc-6239-4c53-a461-df723618c86bn%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/49900cfc-6239-4c53-
> a461-df723618c86bn%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Cecil New]

In reading the Manual of Style at https://standardebooks.org/manual/1.8.2/single-page#8.17.4.3 

I see this: <p>Matthew 5:1–7:29.</p>

I think the intent is that "29" is a verse in chapter 5. So shouldn't the preceding colon be a comma, which is the following rule:

https://standardebooks.org/manual/1.8.2/single-page#8.17.4.4

Thanks!

[Weijia Cheng]

I wrote that section of the MoS and made up that example :)

As the line above it says, "Ranges may also span multiple chapters within the same book." Matthew 5:1–7:29 is the entirety of the Sermon on the Mount, which spans multiple chapters.

[Cecil New]

So sorry! Must have been late... I associated the 7 with a verse range. Your comment was kind... thank you.

[Cecil New]

Started! Link to Github repo:

https://github.com/mandolyte/andre-norton_ralestone-luck

[Alex Cabal]

OK, Lukas will manage this with David reviewing.

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

>
> 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 4/14/25 9:43 PM, Cecil New wrote:
> > Hello,
> >
> > I'd like to start with one I found on the "wanted list":
> >
> > * Ralestone Luck by Andre Norton

> > * https://www.gutenberg.org/ebooks/18817 <https://
> www.gutenberg.org/ebooks/18817>

> >
> > Gutenberg already has several Ebook formats, plain
> text, and an HTML
> > version (which is online).
> >
> > Please let me know if I may proceed.
> >
> > Regards,
> > 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
> > <mailto:standardebook...@googlegroups.com>.
> > To view this discussion visit https://

> groups.google.com/d/msgid/ <https://groups.google.com/d/
> msgid/>
> > standardebooks/49900cfc-6239-4c53-a461-
> df723618c86bn%40googlegroups.com
> <http://40googlegroups.com>
> > <https://groups.google.com/d/msgid/
> standardebooks/49900cfc-6239-4c53- <https://
> groups.google.com/d/msgid/
> standardebooks/49900cfc-6239-4c53->
> > a461-df723618c86bn%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/e3a2c348-bf45-42f2-92b7-3efab0b66499n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/e3a2c348-
> bf45-42f2-92b7-3efab0b66499n%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

[David]

Just picking up this discussion for later review. I notice, Cecil, you've already gone "off piste" from the Producing guide after three commits.

The first commit should not be a "read-me", it should follow Step 5 exactly. The "body.xhtml" file added in the 2nd commit at least doesn't have the PG license at the bottom, but it also shouldn't have the PG cruft at the top, before the main text starts.

It might not be too late to start over with a "clean" project, but some of these things might need a rebase later (possibly more painful!).

Hope that helps!

David / Fife, UK

[Cecil New]

I don't mind restarting. After comparing the scanned and the epub, I have a lot of questions that, so far, I haven't found answers to. 

I've always started repos on the github side... I'll have to find out how to start from the client side. 

Today will be pretty full, so I'll make some headway tomorrow.

Thanks for such early and timely feedback. 

Cheers!

[David]

Glad that made sense! I see from your Github account that you're no stranger to git ... but perhaps that's where it was "easier" for someone like me for whom Github was a foreign country (pretty much) before getting stuck in with Standard Ebooks. The established workflow of the "Step-by-step" guide may be a bit different from other projects you're used to, but following it closely will make completing your ebook as painless as possible.

David / Fife, UK

[Cecil New]

Yeah, I've never started on the client side before... it was rather painful. It looks like I have to have a deploy key per repo... weird.

At any rate, found some time to complete step 5. Can you tell me if it looks ok now?

(I renamed the old repo and then recreated it from scratch).

[David]

Clean as a whistle! (I'm sure someone, somewhere still uses that phrase.)

Probably from this point on the "pushes" to git will be more straightforward. I'm not fully aware of the different ways of authenticating with Github for managing repos. I mostly use Github Desktop which manages that nicely, easily. (Except for rebasing things I've already pushed; that I do from the command line.)

D.

[Vince Rice]

> On Apr 16, 2025, at 11:14 AM, Cecil New <ceci...@gmail.com> wrote:
>
> Yeah, I've never started on the client side before... it was rather painful. It looks like I have to have a deploy key per repo... weird.

If you set up an ssh key, that’s all you need.

[Cecil New]

I think I figured it out... turns out I was adding the key at the repo level, not at the org level. And since you can't reuse keys, it would complain when I tried recreating my SE repo. The problem I have with these things is that you only do them once every few years and I have to relearn them again every time I get new hardware. Sigh...

[Cecil New]

In step typogrify checklist in step 9 is this:
- Two-em dashes should be used for partially-obscured words.

I looked for two consecutive dashes and didn't find any... any tricks for locating such? 

[Weijia Cheng]

“two-em” here refers to a specific character that is a dash the width of two ems (U+2E3A). What you should do is look for partially obscured words while proofreading and manually make sure that those use two-em dashes.

[Cecil New]

Of partially obscured words... 

1. are these words that appear as "sh*t" or "*nix" or etc.?

2. should one U+2E3A glyph replace each obscured letter or just one for an entire run of obscured letters?

Might be nice to include the answers in the step-by-step guide.

Thanks in advance!

[Alex Cabal]

These answers are in the manual, not the step by step guide.

See https://standardebooks.org/manual/1.8.2/single-page#8.7.7.9.3

Though I think we can just un-obscure swear words.

> --
> 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/7097b479-9eae-4db4-b2ad-c800dace3cban%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/7097b479-9eae-4db4-
> b2ad-c800dace3cban%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Cecil New]

The step-by-step guide at that point links to https://standardebooks.org/manual/latest/8-typography#8.7.7

which is about the whole topic of dashes.

Consider https://standardebooks.org/manual/1.8.2/8-typography#8.7.7.9 instead.

Thanks!

[David]

Done! That should refine the clarity of that link from the Step-by-step Guide to SEMoS. Thanks for the alert.

(Also, it's worth noting that at the start of the "Typography checklist" section in the SbSG links to the "Typography" section of SEMoS, which reinforces the *kind* of documents these two are: SbSG is a working manual; SEMoS is the reference work.)

D.

[Cecil New]

Quick question... I find the partially obscured word rules fairly subtle. 

Does anyone have a set of steps to detect these non-conforming cases? I keep thinking I've found a way, only to discover that I don't.

Sort of a trying to find-something-that's-not-there kind of problem. 

My latest idea is to look for all ordinary hyphens and verify they are correctly used. My rationale is that any incorrect obscured word will most likely use hyphens.

Advice appreciated!

[David]

My advice is to follow Weijia's advice, above: that is, just leave this (mainly)  for the proof-reading stage. That's when you'll turn up any instances, while you read the book.

I usually do a project-wide search for 2-em dashes (`⸺`), since sometimes these ought to be 3-em (in my experience). Beyond that, I just leave this for proof-reading, just like Weijia suggests.

Hope that helps!

David / Fife, UK

[Lukas Bystricky]

Not a complaint, just an observation. I appreciate the help managing all round. I've been travelling a bit so maybe I haven't been answering as quickly as normal. David, since you've more or less taken over managing duties, do you want to officially switch roles?

--

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/64a5ccd6-a7db-458e-8b63-f2bb355641a6n%40googlegroups.com.

[Cecil New]

I was told to cut the illustrations in the initial approval to proceed. So at step 12 where the LoI handling is done, I went thru and removed all the illustrations. (note: the images were referenced but they don't actually exist; nor does the scanned book have them).

Since the commits have some meaning in the SE process, should I commit these changes using `git commit -m "Add LoI"` or should I make up one like `git commit -m "Cut illustrations"`?

[David]

Ah, apologies, Lukas. I had the impression you were out-and-about, so thought it could help to pick up a quickie.

If you're still travelling, why don't we swap in this case, then. Thanks!

D.

[David]

It's more important that the commit message matches the unit of work, and that it is meaningful. If you're NOT doing the "unit of work" that corresponds to the Guide, then do use a bespoke message, so in this instance `Cut illustrations` would be just fine.

D.

[Alex Cabal]

Partially obscured words are fairly uncommon, so it's not worth it to
try to find them before you start reading. As David said, during
proofreading mark any that you come across and check them after you're
done. I would be surprised if there are more than 2-3 *unique* cases.

On 4/19/25 8:14 AM, Cecil New wrote:
> Quick question... I find the partially obscured word rules fairly subtle.
>
> Does anyone have a set of steps to detect these non-conforming cases? I
> keep thinking I've found a way, only to discover that I don't.
>
> Sort of a trying to find-something-that's-not-there kind of problem.
>
> My latest idea is to look for all ordinary hyphens and verify they are
> correctly used. My rationale is that any incorrect obscured word will
> most likely use hyphens.
>
> Advice appreciated!
>
> On Friday, April 18, 2025 at 12:51:50 PM UTC-4 David wrote:
>
> Done! That should refine the clarity of that link from the Step-by-
> step Guide to SEMoS. Thanks for the alert.
>
> (Also, it's worth noting that at the start of the "Typography
> checklist" section in the SbSG links to the "Typography" section of
> SEMoS, which reinforces the *kind* of documents these two are: SbSG

> is a working *manual*; SEMoS is the *reference work*.)

>
> D.
>
> On Thursday, 17 April 2025 at 21:33:17 UTC+1 Cecil wrote:
>
> The step-by-step guide at that point links to https://

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

> which is about the whole topic of dashes.
>
> Consider https://standardebooks.org/manual/1.8.2/8-

> typography#8.7.7.9 <https://standardebooks.org/manual/1.8.2/8-
> typography#8.7.7.9> instead.

>
> Thanks!
>
> On Thursday, April 17, 2025 at 3:06:13 PM UTC-4 Alex Cabal wrote:
>
> These answers are in the manual, not the step by step guide.
>
> See https://standardebooks.org/manual/1.8.2/single-

> page#8.7.7.9.3 <https://standardebooks.org/manual/1.8.2/
> single-page#8.7.7.9.3>

>
> Though I think we can just un-obscure swear words.
>

> --
> 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/df155ee7-1431-44c3-a573-843276291ce9n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/df155ee7-1431-44c3-
> a573-843276291ce9n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Cecil New]

The command se semanticate is crashing

'''

Traceback (most recent call last):

  File "/home/cecil/.local/bin/se", line 8, in <module>

    sys.exit(main())

             ^^^^^^

  File "/home/cecil/.local/share/pipx/venvs/standardebooks/lib/python3.12/site-packages/se/main.py", line 81, in main

    sys.exit(getattr(module, command_function)(args.plain_output))

             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/home/cecil/.local/share/pipx/venvs/standardebooks/lib/python3.12/site-packages/se/commands/semanticate.py", line 37, in semanticate

    processed_xhtml = se.formatting.semanticate(xhtml)

                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/home/cecil/.local/share/pipx/venvs/standardebooks/lib/python3.12/site-packages/se/formatting.py", line 162, in semanticate

    dom = se.easy_xml.EasyXmlTree(xhtml)

          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/home/cecil/.local/share/pipx/venvs/standardebooks/lib/python3.12/site-packages/se/easy_xml.py", line 74, in __init__

    raise se.InvalidXmlException(f"Couldn’t parse XML. Exception: {ex}") from ex

se.InvalidXmlException: Couldn’t parse XML. Exception: Unescaped '<' not allowed in attributes values, line 10, column 23 (<string>, line 10)

$ 

'''

Chapter 1 worked ok... but several after that are failing the same way. The area in question - line 10, column 23 - looks like below. I can't spot anything wrong with it. I also looked at every equal sign looking for an attribute with a less than sign, but found none.

Content for Chapter 2 (for example) is at:
https://github.com/mandolyte/andre-norton_ralestone-luck/blob/main/src/epub/text/chapter-2.xhtml

[Alex Cabal]

This is because semanticate is trying to add a Roman span to the id
attribute of the <a> at line 10. Remove the <a> at that line and it will
work. I will see if I can fix this but it might not be possible.

> for an attribute with a less than sign, but found none. Screenshot from

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

> standardebooks.org/manual/latest/8-typography#8.7.7>>
> > which is about the whole topic of dashes.
> >

> > Consider https://standardebooks.org/manual/1.8.2/8- <https://
> standardebooks.org/manual/1.8.2/8->
> > typography#8.7.7.9 <https://standardebooks.org/manual/1.8.2/8-

> <https://standardebooks.org/manual/1.8.2/8->
> > typography#8.7.7.9> instead.
> >
> > Thanks!
> >
> > On Thursday, April 17, 2025 at 3:06:13 PM UTC-4 Alex Cabal wrote:
> >
> > These answers are in the manual, not the step by step guide.
> >

> > See https://standardebooks.org/manual/1.8.2/single- <https://
> standardebooks.org/manual/1.8.2/single->
> > page#8.7.7.9.3 <https://standardebooks.org/manual/1.8.2/

> <https://standardebooks.org/manual/1.8.2/>
> > single-page#8.7.7.9.3>
> >
> > Though I think we can just un-obscure swear words.
> >
> > --
> > 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/df155ee7-1431-44c3-
> a573-843276291ce9n%40googlegroups.com <http://40googlegroups.com>
> > <https://groups.google.com/d/msgid/standardebooks/
> df155ee7-1431-44c3- <https://groups.google.com/d/msgid/
> standardebooks/df155ee7-1431-44c3->
> > a573-843276291ce9n%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/0d33af02-43c2-4427-979b-7b59e227bf3cn%40googlegroups.com
> <https://groups.google.com/d/msgid/
> standardebooks/0d33af02-43c2-4427-979b-7b59e227bf3cn%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

[Cecil New]

OK, I'm down to Step 14 after the semanticate work - the manual semantics work.

I have a bit of text like this:

Now it is a very well-known fact that dishes do <i>not</i> obligingly leap from a table into a pan of well-soaped water

This is commentary from the narrator and is not spoken. But, nonetheless, if it was spoken the word "not" would be emphasized. So I think it should be changed to <em> per https://standardebooks.org/manual/1.8.2/4-semantics#4.1.2.1

Just wanted to be sure I'm on the right track...

Thanks!

[David]

Yes, that's exactly the idea. Emphasis gets `<em>...</em>` tags.

As a rough rule of thumb, *ALMOST* everything in `<i>...</i>` wrappers (book titles, ship names, phonemes/graphemes, etc. etc.) needs a semantic attribute of some kind. These can be found at various places in SEMoS (see the link in the Producing guide at this point).

Hope that helps!

[Cecil New]

Another case... I have this bit of text

From the direction of the hidden water came the faint <i>putt-putt</i> of a motor-boat

So this is (I think) an https://en.wikipedia.org/wiki/Onomatopoeia, but I don't see this in the list at https://www.daisy.org/z3998/2012/vocab/structure/. I also looked at the peer documents at the vocab level without finding one.

An recommendations?

[David]

SEMoS deals with "sounds" at § 8.2.6. (This is one of the exceptions to the `<i>`-need-semantics rule-of-thumb.)

These are sometimes a judgment call. I find it helpful to search the corpus, as after ~1200 titles, the chances are good it's been seen before. In this case, "putt putt" hasn't been deemed a "sound" worth italicizing, though two of those three hits could readily be (IMO).

If your source text has italics for this "sound", I would be inclined to retain it as-is.

[Cecil New]

Found an old spelling: tick-tack-toe. Note: This was not caught by the modernize spelling tool.

Replacing with tic-tac-toe, which I understand is preferred. Did not see this in the corpus.

I came across while using meld to compare hyphenation changes.

[David Reimer]

The basic rule-of-thumb here is: we don't modernize what the automated
spelling tool does not modernize. This is especially the case with
hyphenations: attempting this is the path to madness.

Having said that, we can modernize where there is a clear-cut,
sound-alike case. This one strikes me as iffy: MW has your original
spelling as a variant[1], and I would be inclined to leave it. If you
want to go ahead and modernize it, I would put it in its own commit
with the message as: `[Editorial] tick-tack-toe -> tic-tac-toe` which
will signal clearly to your reviewer (or anyone interested in this
text at a later date) exactly what you've done.

[1]: https://www.merriam-webster.com/dictionary/tick-tack-toe

[Vince]

Tick-tack-toe is a valid variant listed in M-W.

Modernize spelling can't contain every possible modernization, so it only contains those that have some level of frequency, which, as you note, this one does not have.

[Alex Cabal]

We do want to modernize sound-alike spelling that catches your eye. As
Vince said, `se modernize-spelling` can't contain every possible word,
so producers have freedom to spot old spelling that can be modernized on
a case by case basis. This looks like one of those cases.

The rule is sound-alike changes only.

[Cecil New]

In step 18, where this is run: se build-title .

It found no changes. When I looked at the title elements they are simply the chapter roman numeral. For example: <title>XII</title>

Thus no need for a commit. But in this case, unlike previous cases, it doesn't say "if any are found then commit...".

So wanted to make sure that all is well before I get too far...

[David Reimer]

There are cases of chapters with only roman numerals, and no proper
titles, but that's not your case.

At the moment you have:

<h2 epub:type="ordinal z3998:roman"><a id="CHAPTER_I"/>I</h2>
<h3>The Ralestones Come Home</h3>

But this should be formatted like [SEMoS
7.2.10.3](https://standardebooks.org/manual/1.8.2/single-page#7.2.10.3)

<hgroup>
<h2 epub:type="ordinal z3998:roman">I</h2>
<p epub:type="title">The Ralestones Come Home</p>
</hgroup>

And *then* `se build-title` will find the titles to build. (You need
to remove that `<a id...` bit too, of course.)

While we're at it, could you provide the URL for the page-scans you're
using? That would be a help. Thanks!

D.

[Cecil New]

Ah, that makes sense. I remember thinking that one of tools would create the "hgroup" if it was required. Thanks!

Here are my Step 3 artifacts:

Located a good scan at:

https://archive.org/details/ralestoneluck0000nort/mode/2up

Other files here have just pictures/drawings.

GP web version:

https://www.gutenberg.org/cache/epub/18817/pg18817-images.html

GP plain text version:

https://www.gutenberg.org/cache/epub/18817/pg18817.txt

[David Reimer]

Thanks - I guess this is one of those cases where the "copyright
renewal" is post-1964, so this work is PD, and these scans are good. I
think! (Since PG has the transcription I'm sure the PD status is
clear: I'm just thinking out loud about the scans.)

D.

[Cecil New]

Made it thru all the linter findings (it does a great job, my complements). 

I made the ebook and have begun to proof read on my Kindle.

I noticed that there was no mention in the SbyS of doing a commit after the lint work.I have always committed/pushed after completing some unit of work (software world). It makes me a bit nervous having this just on my computer.

Is it ok to commit/push? If so, is there a "standard" commit message I should use?

[David Reimer]

Hmm... I'm a little puzzled. At the very top of the Step-by-Step Guide
(SbSG) there is a big yellow box:
https://standardebooks.org/contribute/producing-an-ebook-step-by-step
which includes this:

[quote]
Maintaining a clean and orderly Git history is very important to the
final ebook. You should commit early and often.

A single commit should only contain a single logical unit of work,
like `Typogrified text` or `Fixed transcription typos`. Don’t cram a
lot of different changes into a single commit because you forgot to
commit early and often.

In particular, commits that contain editorial changes to the source
text, like spelling changes, must have their commit message prefaced
with `[Editorial]` and must not contain any non-editorial changes.
[/quote]

So the SbSG doesn't prescribe every single commit that should be made.

Hopefully the *lint* errors/fixes that you've needed to do are all,
e.g., typo-fixing, adding semantics, or tidying markup in some other
way. IF there were any changes that would be "[Editorial]" (where some
aspect of *content* has changed in relation to the *scans*), then
these must not be included.

Your software practice of committing after a "unit of work" still
holds in the SE workflow, but lint throws up all manner of things, and
it's best to keep commits of these kinds of interventions discrete.

As noted earlier, commit messages should be clear and relevant for the
work done. So `Fixed lint errors` does not convey much meaningful, but
`Fixed typos, semantics, and formatting` does. Only you know what
you've done, of course, so use your best judgement here. (With that
*caveat* that [Editorial] interventions must not be included with
non-[Editorial]. That big yellow box at the top of the SbSG finishes
with this:

[quote]
If your working directory contains a mix of changes and you only want
to commit some of them, `git add --patch` is a useful way to only
commit parts of a file[1].
[1]: http://git-scm.com/docs/git-add#Documentation/git-add.txt--p
[/quote]

Hope that helps!

D.

[Cecil New]

Proofreading has turned up two cases where the GP text used divs with a blockquot class. Looking thru SMoS, I think these must be altered per:
https://standardebooks.org/manual/1.8.2/single-page#5.8, right?

One of the two uses an odd double plus single quote structure. Looks like this:

```

<div class="blockquot">
<p>“ ’<span class="smcap">This Room Was Occupied by General Andrew Jackson, the Victor of the Battle of New Orleans, upon the Tenth Day after the Battle</span>.’ ”</p>
</div>
```

(I see the single quote needs to be fixed (if retained)). 
Should I simplify this to just double quotes?

For comparison, the second looks like this (elided):
```

<div class="blockquot">
<p>“Gatty has returned from the city. The raiders calling themselves ... Gatty⁠—”</p>
</div>

```

Scanned locations are, respectively:

https://archive.org/details/ralestoneluck0000nort/page/11/mode/1up?q=General+Jackson

and

https://archive.org/details/ralestoneluck0000nort/page/94/mode/1up?q=%22themselves+the+%E2%80%98Buck+Boys%E2%80%99%22

[David Reimer]

Correct - these `div`s must be converted to `blockquote`s as per your
link in SEMoS.

As it happens, *both* those blockquotes are also being spoken by a
character. They thus need the dialogue quotations, and that's why they
have the double + single nested quotation marks.

https://standardebooks.org/manual/1.8.2/single-page#8.7.5.2

But(!) the second example ("This Room Was Occupied...") is very much
like one that just came up in one of my productions, and the advice
was to drop the inner single quote marks. (Dropping the inner
single-quotes is [Editorial]!) They can be retained in the other
example, though.

`typogrify` will take care of the formatting of the nested quotes if
you have the doubles and singles correct. I.e., make the necessary
formatting changes, then run `se typogrify` on that file should do the
trick.

[Cecil New]

Follow-up question...

Here is the scanned text. It is text read from a plaque:

Here is how it looks in Calibre reader:

Here is what I did in order to mimic what I think the author is doing, namely making the text on the page to resemble the format on the plaque.

Thoughts? Advice? I couldn't quite find anything in the SMoS that seemed to apply (but I have been wrong many times already).

[David]

Almost! We don't use any inline styles. This needs to go in `src/epub/css/local.css`. You'll need a rule like

    #chapter-1 blockquote{

        text-align: center;

    }

(Run `se clean` after adding your rule(s) to `local.css`, and it will ... clean it up. :)

And we shouldn't use the `strong` wrapper. That's a "semantic" wrapper . Rather, use `b` for this.

I would also put a `br` after `General`, so that the name "Andrew Jackson" is on its own line.

After you're happy with the formatting (and it's committed!), *then* you can remove the inner single-quotes in an [Editorial] commit.

Hope that all makes sense.

[Vince]

Is his name is on a separate line because of the plaque, or because of the width of the printed page? Where it breaks would tend to point to the latter, I would think; if it was the former, I would have expected the “General” to accompany the name.

On Apr 27, 2025, at 3:27 PM, David <djre...@gmail.com> wrote:

Almost! We don't use any inline styles. This needs to go in `src/epub/css/local.css`. You'll need a rule like

    #chapter-1 blockquote{

        text-align: center;

    }

(Run `se clean` after adding your rule(s) to `local.css`, and it will ... clean it up. :)

And we shouldn't use the `strong` wrapper. That's a "semantic" wrapper . Rather, use `b` for this.

I would also put a `br` after `General`, so that the name "Andrew Jackson" is on its own line.

After you're happy with the formatting (and it's committed!), *then* you can remove the inner single-quotes in an [Editorial] commit.

Hope that all makes sense.

On Sunday, 27 April 2025 at 20:10:54 UTC+1 Cecil wrote:

Follow-up question...

Here is the scanned text. It is text read from a plaque:

<Screenshot from 2025-04-27 15-04-46.png>

Here is how it looks in Calibre reader:

<Screenshot from 2025-04-27 15-06-44.png>

Here is what I did in order to mimic what I think the author is doing, namely making the text on the page to resemble the format on the plaque.

[David Reimer]

My assumption was - the plaque, and that the name's the thing, as it were.

But hey, like Cecil says, "I have been wrong many times already."

On Sun, 27 Apr 2025 at 21:56, Vince wrote:
>
> Is his name is on a separate line because of the plaque, or because of the width of the printed page? Where it breaks would tend to point to the latter, I would think; if it was the former, I would have expected the “General” to accompany the name.
>

[Vince]

Me more than both of you combined. :)

[Cecil New]

Completed proofreading last night and this morning I thought I'd take a look at what's next, which is the cover...

But the book was published in 1938, so I will find not cover connected with this book specifically prior to January 1, 1930.

Are we sure this book is public domain? (see also above https://groups.google.com/g/standardebooks/c/eB9JSXWjspQ/m/OfD83jsHBwAJ)

The cover art for this book is a bit off (it depicts nothing that actually happened in the book - strictly to draw attention to it).
And it has stuff on it that we don't want - perhaps this can be edited out?? But again, it comes after 1930...

Or should I just start looking for something else?

[David Reimer]

I'd recommend you just start looking for something else.

There is an (unwritten) convention that sci-fi titles
often/regularly/normally get abstract art for covers.[1] You can also
see what's been used for other Andre Norton productions[2] to get a
feel for this.

[1}: https://standardebooks.org/subjects/science-fiction
[2}: https://standardebooks.org/ebooks/andre-norton

The advent of the SE Artworks DB has made the often painful task of
finding cover art MUCH less arduous. There a quite a few abstracts
approved, but not yet assigned, and you can see if you think any of
them "gel" with this book:
https://standardebooks.org/artworks?status=approved_not_in_use&query=abstract&sort=created-newest&per-page=20

Otherwise, see the advice at SEMoS §10.3 and following,[3] and do it
the old fashioned way. :) (Worth reading that section anyway,
actually.)

[3]: https://standardebooks.org/manual/1.8.2/single-page#10.3.3

When you've found something you like, please submit a "mock up" here
(doesn't have to be full-sized; see other production threads for
examples), and I'll review and make the assignment.

[David]

P.s. You can tell I don't know this book! It's possibly *not* sci-fi (?), but still the broad advice holds:

- read through SEMOS §10.3;

- check the SE artworks DB by key/theme word for any possibilites there;

- if nothing, start hunting! :)

On Tuesday, 29 April 2025 at 14:22:28 UTC+1 David wrote:

I'd recommend you just start looking for something else.

There is an (unwritten) convention that sci-fi titles
often/regularly/normally get abstract art for covers.[1] You can also
see what's been used for other Andre Norton productions[2] to get a
feel for this.

[1}: https://standardebooks.org/subjects/science-fiction
[2}: https://standardebooks.org/ebooks/andre-norton

. . .

[Alex Cabal]

Anything on Project Gutenberg is in the US public domain. There are
various exceptions for work published after 1929, see their website for
details.

On 4/29/25 8:11 AM, Cecil New wrote:
> Completed proofreading last night and this morning I thought I'd take a
> look at what's next, which is the cover...
>
> But the book was published in 1938, so I will find not cover connected
> with this book specifically prior to January 1, 1930.
>

> /Are we sure this book is public domain? (see also above /https://
> groups.google.com/g/standardebooks/c/eB9JSXWjspQ/m/OfD83jsHBwAJ)

> --
> 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/2679001f-deca-4183-9c23-06bf316da50cn%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/2679001f-
> deca-4183-9c23-06bf316da50cn%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

[Cecil New]

I like these two best:

Could be an abstract pirate ship (piracy figures large in the story):
https://standardebooks.org/artworks/rupert-d-turnbull/untitled

Could be Cinders aka “Satan” the cat in the story:
https://standardebooks.org/artworks/jean-bloe-niestle/wildernde-katze

Others that might suitable are landscapes with a dark/swamp-like character (takes place in the bayou) or castle ruins.

[David Reimer]

Having taken a closer look at the book, I don't think we should be
using an abstract for this one, but should reserve for actual sci-fi
titles.

If you think the cat picture is suitable, then that could work - how
central is "Cinders" to the story?

In a quick browse of the DB, this one caught my eye:
https://standardebooks.org/artworks/william-henry-dethlef-koerner/rest-in-the-woods

Not sure it's quite the bayou(!), but rural anyway, and the characters
might suit: Ricky wears ties, and Val wears hats....

[Cecil New]

Yes... this is more of a mystery story, not sci-fi.

I missed that picture... the three could be the siblings in the story:

- Rupert: the older brother owns the Ralestone "pirate haven" property

- The girl, Ricky (short for Richanda)

- The boy, Val (short for Valerius)
(Those two nicknames kept tripping me up until I was well into the story :-))

The cat Cinders (Satan) was key to discovering a hidden room and was the "star" of chapter 6. And also discovered some key evidence afterwards.

All the commercial covers, however, always show Ricky... even tho the youngest, she was most important character in the story.

Hope this helps!

[Cecil New]

Down to the two choices... which gets the nod? Let me know!
https://standardebooks.org/artworks/william-henry-dethlef-koerner/rest-in-the-woods

or

https://standardebooks.org/artworks/jean-bloe-niestle/wildernde-katze

[David Reimer]

But ... it's *your* call! :) My hunch based on a very (very) limited
understanding of the book is that the Koerner painting has more
narrative quality, and the Niestle would be a bit more enigmatic. But
perhaps that's a good thing!

Worth trying a mockup, though, as seeing them in a crop with the
title-box might swing it one way or the other.

[Cecil New]

Hmmm - here is a screen shot of the cat version... I used Chrome to open and see this. I don't think it is quite right or do I need to something else... 

And here is the second. Neither are properly aligning.

[Cecil New]

Now that I am looking closely, I'm not sure the figure on the left is male. So let's go with the cat...

[Cecil New]

Also, just noticed that in the next bullet that I need to scale... so that will take care of alignment. 

[David Reimer]

It's worth having a look (again?) at SEMoS §10.3.3
https://standardebooks.org/manual/1.8.2/single-page#10.3.3

The image will need to be 1400x2100 (is a ratio of 2:3), so if your source is too small, it will have be be upscaled to meet those dimensions when cropped.

I copy the `images/cover.svg` file out of my project repo into my own "working" directory (OUT of the repo path), and usually rename it, just so I don't get confused down the line (e.g. `cover-luck.svg`).

You'll need the "League Spartan" font on your system:
https://github.com/theleagueof/league-spartan/releases

Use GIMP (or whatever) to get the image cropped and sized; you can then open the `cover-luck.svg` file in Inkscape (or whatever), and import your cover image. You can then export a JPG.

The result might look something like the attached. (Others have different workflow for this!)

Hope that makes sense!

[David]

P.s. I forgot (doh!) that we have a "How to..." that covers much of this:

https://standardebooks.org/contribute/how-tos/how-to-choose-and-create-a-cover-image

Also worth a read!

[Cecil New]

Funny, I ended up doing pretty much as you described above. The original image height is less than 2100. So I figured out to resize first with imagemagick, then I used gimp to crop to 1400x2100.

Phew... I took personal notes... will go faster next time :-)

[Cecil New]

Now in final checks... Lint is reporting these:

1. The first is one is ok, being an elision, not a typo
2. The second ... not sure... se clean did the escaping?? I can't spot anything wrong with it.
3. What about the last one? Is there anything I can do/should do?

[David Reimer]

1. That's tricky: that lsquo is doing "double duty", it seems to me: it's both an elision, as you note; but it's also closing the nested quote (notice the rsquo before "peaked"!). And that's not right![1] You should see what your scans have - I think there may be a printer typo here. It looks this way in the in the IA edition I'm searching:

[1]: https://github.com/search?q=org%3Astandardebooks+%2F%E2%80%99%5C.%E2%80%99.%E2%80%9D%2F&type=code

So that ought to be fixed, and whether it's "[Editorial]" depends on what *your* scans show (fixing printer typos is classed as [Editorial]).

2. Without seeing your long description (it's not yet in your repo online), that's hard to say. If you ran `se clean` before running `se lint`, it *should* be fine. Post an extract or screenshot if you still can't spot the issue.

3. Yes, you should compress the JPG. I always run my cover image through this online tool (I'm sure there are other approaches, but this is what I do):
https://compressjpeg.com/

[Cecil New]

On 1... great catch... it took some staring to understand what was going on.

On 2... here is the long description

<meta id="long-description" property="se:long-description" refines="#description">
A young brother and sister return to their family’s mansion with their older brother. They all know their family’s history and legend. With barely enough money to return, they seek the “luck” of the family, knowing neither what it is or where it is. But when found, their fortunes will be assured. This is the first book written by &lt;a href="https://standardebooks.org/ebooks/andre-norton"&gt;Andre Norton&lt;/a&gt;, circa 1930, and was the second to be published in 1938.</meta>

On 3... Thanks for the pointer to the compression tool

[David Reimer]

Re #2 (long description) - If lint is still complaining about that long description, then there must be some glitch in the `content.opf` file that I can't see. I don't know whether any of the more experienced hands around with sharper eyes than mine can spot the issue.

If lint's still complaining, then perhaps best to push this to the public repo so we can take a closer look.

[Vince]

The text needs <p>’s around it, just as in normal text. It should be valid HTML before it’s handed to clean to escape.

[David Reimer]

Ack. I think I need more sleep. :/

Thanks, Vince!

On Fri, 2 May 2025 at 22:05, Vince wrote:
>
> The text needs <p>’s around it, just as in normal text. It should be valid HTML before it’s handed to clean to escape.
>

[Cecil New]

OK - lint and build checks-only complete with no errors.

I do have one more thing... above in the approval to proceed, @Alex Cabal says:

There is an epigraph so you'll have to include a half title page.

I think he meant the dedication page here: https://archive.org/details/ralestoneluck0000nort/page/n6/mode/1up 

I found an example of such here:
https://github.com/standardebooks/bram-stoker_dracula/blob/6fd8c5b0b7a78f9c34355352cbb07ceb4261024a/src/epub/text/dedication.xhtml#L4 

I'll use that as an example to follow and, of course, https://standardebooks.org/manual/1.8.2/single-page#7.3 

Let me know if there is anything else to consider (or if I'm wrong about what Alex meant!).

[Cecil New]

Ah, lint complains if the halfpagetitle is missing when front matter exists... Working thru it now...

[David]

Not quite, I think. You have a dedication (to which you linked), AND a full-page epigraph...

https://archive.org/details/isbn_9781421827339/page/n7/mode/2up

...although I can't tell what your scans show, as that copy is borrowed just now. :)

So you will need a `halftitlepage.xhtml` file in any case:

https://standardebooks.org/manual/1.8.2/single-page#6.5

And you have a "full page" epigraph:

https://standardebooks.org/manual/1.8.2/single-page#7.4

As well as the dedication. The CSS rules you need for the dedication and epigraph go into `local.css`, of course. You can style the dedication to match (as near as never mind) what you have in the print edition, but use normal casing for the `dedication.xhtml` file, and style it as necessary with CSS.

The Great Gatsby has this same structure:

https://github.com/standardebooks/f-scott-fitzgerald_the-great-gatsby

so you can use its files as templates (if you're careful!). Both books are `en-US`, anyway.

[David Reimer]

Ack - no it's not. It's `en-GB`. Sigh. Not sure whether it's sleep or
coffee I need....

On Sat, 3 May 2025 at 14:57, David wrote:
> . . .

[Cecil New]

That epigraph is not present in the scan I've using. For some reason, I did not come across the scan you just linked to. The one you pointed to is a lot "cleaner" looking.

I just pushed so you can see where things stand.

If I draw from both scans, I'll need to mention both (I remember seeing that somewhere). Or if the one you linked to is a pure superset, then I could just update references to use it, right?

I like the idea of using the epigraph, since it is quoted from several times in the book but never in full (if my memory is right). So this would be a nice addition.

So, I propose to see if the two scans are comparable. Then update to reference the better one if nothing found to inhibit that. Or go back and see what is needed for drawing upon more than one scan.

Sound good?

[David Reimer]

I think the reason that Alex likely mentioned the "epigraph" in the
first place, is that it is present as such in the PG transcription,
immediately above where the text of the story starts (scroll up from
this link):
https://www.gutenberg.org/cache/epub/18817/pg18817-images.html#CHAPTER_I

I think we *typically* wouldn't use two scans for the same book.
Multiple scans come into play when there are two separate volumes, or
in an omnibus combining content from different works. I see that SEMoS
does not limit multiple scans to this situation, though:
https://standardebooks.org/manual/1.8.2/single-page#9.8.3

It gets tricky switching now since, I assume, your `[Editorial]`
commits have been made on the basis of your present choice.

Perhaps best to call in advice from higher up the food chain! I'm
really not sure how to proceed here.

[Cecil New]

If it helps...

a) I spot checked five chapters and didn't find any editorial change differences between the two scans.

b) The newer book scan I noticed that it was never available. So I started digging and found that newer scan was under dispute. Here are links:
https://help.archive.org/help/why-are-so-many-books-listed-as-borrow-unavailable-at-the-internet-archive/

Given point b, perhaps we should just omit the epigraph for now. Perhaps record this in an issue for future disposition???

[Alex Cabal]

If the epigraph is in PG then it can and should be included

On 5/3/25 3:41 PM, Cecil New wrote:
> If it helps...
>
> a) I spot checked five chapters and didn't find any editorial change
> differences between the two scans.
> b) The newer book scan I noticed that it was never available. So I
> started digging and found that newer scan was under dispute. Here are links:
> https://help.archive.org/help/why-are-so-many-books-listed-as-borrow-
> unavailable-at-the-internet-archive/
>
> Given point b, perhaps we should just omit the epigraph for now. Perhaps
> record this in an issue for future disposition???
>
> On Saturday, May 3, 2025 at 10:32:03 AM UTC-4 David wrote:
>
> I think the reason that Alex likely mentioned the "epigraph" in the
> first place, is that it is present as such in the PG transcription,
> immediately above where the text of the story starts (scroll up from
> this link):
> https://www.gutenberg.org/cache/epub/18817/pg18817-

> images.html#CHAPTER_I <https://www.gutenberg.org/cache/epub/18817/
> pg18817-images.html#CHAPTER_I>

>
> I think we *typically* wouldn't use two scans for the same book.
> Multiple scans come into play when there are two separate volumes, or
> in an omnibus combining content from different works. I see that SEMoS
> does not limit multiple scans to this situation, though:

> https://standardebooks.org/manual/1.8.2/single-page#9.8.3 <https://
> standardebooks.org/manual/1.8.2/single-page#9.8.3>

>
> It gets tricky switching now since, I assume, your `[Editorial]`
> commits have been made on the basis of your present choice.
>
> Perhaps best to call in advice from higher up the food chain! I'm
> really not sure how to proceed here.
>
> On Sat, 3 May 2025 at 15:15, Cecil New <ceci...@gmail.com> wrote:
> >
> > That epigraph is not present in the scan I've using. For some
> reason, I did not come across the scan you just linked to. The one
> you pointed to is a lot "cleaner" looking.
> >
> > I just pushed so you can see where things stand.
> >
> > If I draw from both scans, I'll need to mention both (I remember
> seeing that somewhere). Or if the one you linked to is a pure
> superset, then I could just update references to use it, right?
> >
> > I like the idea of using the epigraph, since it is quoted from
> several times in the book but never in full (if my memory is right).
> So this would be a nice addition.
> >
> > So, I propose to see if the two scans are comparable. Then update
> to reference the better one if nothing found to inhibit that. Or go
> back and see what is needed for drawing upon more than one scan.
> >
> > Sound good?
>

> --
> 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/fbf09b56-db55-4648-bedb-492d7a2ef9e3n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/fbf09b56-db55-4648-
> bedb-492d7a2ef9e3n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Cecil New]

Oh, one more thing... if there is agreement with previous post, then I guess it is ready for review.

Cheers!

[Cecil New]

Post crossed... so questions on provenance...

a. do we need a scan with the epigraph to show provenance? (given the IA item is under dispute -- see couple of posts prior)

b. since PG has it at https://www.gutenberg.org/cache/epub/18817/pg18817-images.html and if I need to use it for provenance, do I reference the web page just like I would a scan?

[Vince]

In this case, the transcription is the provenance, and it’s already being referenced it in the dc:source for the transcription in the metadata.

[Cecil New]

The linter is giving me:

And I can't spot the problem...

Here is file (for which I followed https://standardebooks.org/manual/1.8.2/7-high-level-structural-patterns#7.5.7):

<?xml version="1.0" encoding="utf-8"?>
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" epub:prefix="z3998: http://www.daisy.org/z3998/2012/vocab/structure/, se: https://standardebooks.org/vocab/1.0" xml:lang="en-US">
<head>
<title>Epigraph</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="frontmatter">
<section id="epigraph" epub:type="epigraph">
<blockquote epub:type="z3998:poem">
<p>
<span><i>How hold ye Lorne?</i></span>
<br/>
<span>By the oak leaf,</span>
<br/>
<span>By the sea wave,</span>
<br/>
<span>By the broadsword blade,</span>
                    <br/>
<span>Thus hold we Lorne!</span>
                </p>
                <p>
<span><i>The oak leaf is dust,</i></span>
                    <br/>
<span><i>The sea wave is gone,</i></span>
                    <br/>
<span><i>The broadsword is rust,</i></span>
                    <br/>
<span><i>How now hold ye Lorne?</i></span>
                    <br/>
<span>By our Luck, thus hold we Lorne!</span>
</p>
</blockquote>
</section>
</body>
</html>

In italics show the "call and response" character of the poem. Here is a link to the PG source:
https://www.gutenberg.org/cache/epub/18817/pg18817-images.html

The poem/epigraph immediately precedes chapter 1.

[David Reimer]

Try running `se clean` on that file. If what you copy/pasted has equates with your native file, then quite a few of the lines are padded with spaces rather than the tab character.

[Cecil New]

Wow! that did it. I'll remember that trick. Thanks!

[Cecil New]

Ready for review: https://github.com/mandolyte/andre-norton_ralestone-luck

[Lukas Bystricky]

Noted; I'll get to that this week sometime.

--

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/8194c9a7-441d-4af8-af18-d7981ac19be2n%40googlegroups.com.

[Lukas Bystricky]

Very nice work Cecil. I've filed a review with a few things to look at. You might need a rebase unfortunately, but hopefully it's not too difficult. Let me know if you need a hand with that. 

[Lukas Bystricky]

Ok Alex, this is ready for you.

[Alex Cabal]

The cover art is not marked in the database, can you update that before
we continue?

On 5/12/25 11:51 PM, Lukas Bystricky wrote:
> Ok Alex, this is ready for you.
>
> On Friday, May 9, 2025 at 10:09:41 PM UTC+2 Lukas Bystricky wrote:
>
> Very nice work Cecil. I've filed a review with a few things to look
> at. You might need a rebase unfortunately, but hopefully it's not
> too difficult. Let me know if you need a hand with that.
>
> On Monday, May 5, 2025 at 5:29:06 PM UTC+2 Lukas Bystricky wrote:
>
> Noted; I'll get to that this week sometime.
>
>
> On Mon, May 5, 2025, 17:02 Cecil New <ceci...@gmail.com> wrote:
>
> Ready for review: https://github.com/mandolyte/andre-

> norton_ralestone-luck <https://github.com/mandolyte/andre-
> norton_ralestone-luck>

>
> On Monday, May 5, 2025 at 10:56:14 AM UTC-4 Cecil New wrote:
>
> Wow! that did it. I'll remember that trick. Thanks!
>
> On Monday, May 5, 2025 at 10:43:12 AM UTC-4 David wrote:
>
> Try running `se clean` on that file. If what you
> copy/pasted has equates with your native file, then
> quite a few of the lines are padded with spaces
> rather than the tab character.
>
> On Mon, 5 May 2025 at 15:01, Cecil wrote:
>
> The linter is giving me:
>

> Screenshot from 2025-05-05 09-52-50.png
> And I can't spot the problem...
>
> Here is file (for which I followed https://
> standardebooks.org/manual/1.8.2/7-high-level-

> structural-patterns#7.5.7 <https://
> standardebooks.org/manual/1.8.2/7-high-level-
> structural-patterns#7.5.7>):

>
> <?xml version="1.0" encoding="utf-8"?>
> <html xmlns="http://www.w3.org/1999/xhtml
> <http://www.w3.org/1999/xhtml>"
> xmlns:epub="http://www.idpf.org/2007/ops
> <http://www.idpf.org/2007/ops>"
> epub:prefix="z3998: http://www.daisy.org/

> z3998/2012/vocab/structure/ <http://
> www.daisy.org/z3998/2012/vocab/structure/>, se:
> https://standardebooks.org/vocab/1.0 <https://
> standardebooks.org/vocab/1.0>" xml:lang="en-US">

> pg18817-images.html <https://www.gutenberg.org/
> cache/epub/18817/pg18817-images.html>

>
> The poem/epigraph immediately precedes chapter 1.
>
> --
>
> 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/8194c9a7-441d-4af8-af18-

> d7981ac19be2n%40googlegroups.com <https://groups.google.com/
> d/msgid/standardebooks/8194c9a7-441d-4af8-af18-
> d7981ac19be2n%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/a61fa935-5fde-4a46-b353-c4bad1c0ea13n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/a61fa935-5fde-4a46-
> b353-c4bad1c0ea13n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Lukas Bystricky]

Ok, I've updated the DB.

[Alex Cabal]

Can you flesh out the long description more? In the short description
you mention pirates, which sounds like an important plot point, but it's
not mentioned in the short description. What else can you say about this
novel and its plot? What kind of book is it? etc.

On 5/13/25 11:57 PM, Lukas Bystricky wrote:
> Ok, I've updated the DB.
>
> On Wednesday, May 14, 2025 at 3:50:54 AM UTC+2 Alex Cabal wrote:
>
> The cover art is not marked in the database, can you update that before
> we continue?
>
> On 5/12/25 11:51 PM, Lukas Bystricky wrote:
> > Ok Alex, this is ready for you.
> >
> > On Friday, May 9, 2025 at 10:09:41 PM UTC+2 Lukas Bystricky wrote:
> >
> > Very nice work Cecil. I've filed a review with a few things to look
> > at. You might need a rebase unfortunately, but hopefully it's not
> > too difficult. Let me know if you need a hand with that.
> >
> > On Monday, May 5, 2025 at 5:29:06 PM UTC+2 Lukas Bystricky wrote:
> >
> > Noted; I'll get to that this week sometime.
> >
> >
> > On Mon, May 5, 2025, 17:02 Cecil New <ceci...@gmail.com> wrote:
> >

> > Ready for review: https://github.com/mandolyte/andre- <https://
> github.com/mandolyte/andre->
> > norton_ralestone-luck <https://github.com/mandolyte/andre-

> <https://github.com/mandolyte/andre->
> > norton_ralestone-luck>
> >
> > On Monday, May 5, 2025 at 10:56:14 AM UTC-4 Cecil New wrote:
> >
> > Wow! that did it. I'll remember that trick. Thanks!
> >
> > On Monday, May 5, 2025 at 10:43:12 AM UTC-4 David wrote:
> >
> > Try running `se clean` on that file. If what you
> > copy/pasted has equates with your native file, then
> > quite a few of the lines are padded with spaces
> > rather than the tab character.
> >
> > On Mon, 5 May 2025 at 15:01, Cecil wrote:
> >
> > The linter is giving me:
> >
> > Screenshot from 2025-05-05 09-52-50.png
> > And I can't spot the problem...
> >
> > Here is file (for which I followed https://

> > standardebooks.org/manual/1.8.2/7-high-level- <http://
> standardebooks.org/manual/1.8.2/7-high-level->
> > structural-patterns#7.5.7 <https://
> > standardebooks.org/manual/1.8.2/7-high-level- <http://

> standardebooks.org/manual/1.8.2/7-high-level->
> > structural-patterns#7.5.7>):
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <html xmlns="http://www.w3.org/1999/xhtml <http://
> www.w3.org/1999/xhtml>
> > <http://www.w3.org/1999/xhtml <http://www.w3.org/1999/xhtml>>"
> > xmlns:epub="http://www.idpf.org/2007/ops <http://
> www.idpf.org/2007/ops>
> > <http://www.idpf.org/2007/ops <http://www.idpf.org/2007/ops>>"

> > epub:prefix="z3998: http://www.daisy.org/ <http://www.daisy.org/>
> > z3998/2012/vocab/structure/ <http://
> > www.daisy.org/z3998/2012/vocab/structure/ <http://www.daisy.org/

> z3998/2012/vocab/structure/>>, se:
> > https://standardebooks.org/vocab/1.0 <https://standardebooks.org/

> vocab/1.0> <https://
> > standardebooks.org/vocab/1.0 <http://standardebooks.org/

> > https://www.gutenberg.org/cache/epub/18817/ <https://
> www.gutenberg.org/cache/epub/18817/>
> > pg18817-images.html <https://www.gutenberg.org/ <https://
> www.gutenberg.org/>

> > cache/epub/18817/pg18817-images.html>
> >
> > The poem/epigraph immediately precedes chapter 1.
> >
> > --
> >
> > 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/

> <https://groups.google.com/d/>
> > msgid/standardebooks/8194c9a7-441d-4af8-af18-
> > d7981ac19be2n%40googlegroups.com <http://40googlegroups.com>
> <https://groups.google.com/ <https://groups.google.com/>
> > d/msgid/standardebooks/8194c9a7-441d-4af8-af18-
> > d7981ac19be2n%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/a61fa935-5fde-4a46-b353-
> c4bad1c0ea13n%40googlegroups.com <http://40googlegroups.com>
> > <https://groups.google.com/d/msgid/standardebooks/
> a61fa935-5fde-4a46- <https://groups.google.com/d/msgid/
> standardebooks/a61fa935-5fde-4a46->
> > b353-c4bad1c0ea13n%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/aea05eaf-ce35-4a10-ace7-7b37cc934735n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/aea05eaf-ce35-4a10-
> ace7-7b37cc934735n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Cecil New]

I expanded the long description (and noticed I had an unsaved change to the lint ignore file). 

[Alex Cabal]

OK, much better, thanks. Great work! I've gone ahead and released it.

If you'd like to work on something more advanced next, check our Wanted
list for moderate difficulty suggestions, or pitch something else that
might interest you to the mailing list.

> github.com/mandolyte/andre-> <https://
> > github.com/mandolyte/andre- <http://github.com/mandolyte/andre->>

> > > norton_ralestone-luck <https://github.com/mandolyte/andre-
> <https://github.com/mandolyte/andre->
> > <https://github.com/mandolyte/andre- <https://github.com/
> mandolyte/andre->>
> > > norton_ralestone-luck>
> > >

> > > On Monday, May 5, 2025 at 10:56:14 AM UTC-4 Cecil New wrote:
> > >
> > > Wow! that did it. I'll remember that trick. Thanks!
> > >
> > > On Monday, May 5, 2025 at 10:43:12 AM UTC-4 David wrote:
> > >
> > > Try running `se clean` on that file. If what you
> > > copy/pasted has equates with your native file, then
> > > quite a few of the lines are padded with spaces
> > > rather than the tab character.
> > >
> > > On Mon, 5 May 2025 at 15:01, Cecil wrote:
> > >
> > > The linter is giving me:
> > >
> > > Screenshot from 2025-05-05 09-52-50.png
> > > And I can't spot the problem...
> > >
> > > Here is file (for which I followed https://
> > > standardebooks.org/manual/1.8.2/7-high-level- <http://

> standardebooks.org/manual/1.8.2/7-high-level-> <http://

> > standardebooks.org/manual/1.8.2/7-high-level- <http://
> standardebooks.org/manual/1.8.2/7-high-level->>
> > > structural-patterns#7.5.7 <https://
> > > standardebooks.org/manual/1.8.2/7-high-level- <http://

> standardebooks.org/manual/1.8.2/7-high-level-> <http://

> > standardebooks.org/manual/1.8.2/7-high-level- <http://
> standardebooks.org/manual/1.8.2/7-high-level->>
> > > structural-patterns#7.5.7>):
> > >
> > > <?xml version="1.0" encoding="utf-8"?>
> > > <html xmlns="http://www.w3.org/1999/xhtml <http://

> www.w3.org/1999/xhtml> <http://
> > www.w3.org/1999/xhtml <http://www.w3.org/1999/xhtml>>
> > > <http://www.w3.org/1999/xhtml <http://www.w3.org/1999/xhtml>

> <http://www.w3.org/1999/xhtml <http://www.w3.org/1999/xhtml>>>"
> > > xmlns:epub="http://www.idpf.org/2007/ops <http://

> www.idpf.org/2007/ops> <http://
> > www.idpf.org/2007/ops <http://www.idpf.org/2007/ops>>
> > > <http://www.idpf.org/2007/ops <http://www.idpf.org/2007/ops>

> <http://www.idpf.org/2007/ops <http://www.idpf.org/2007/ops>>>"
> > > epub:prefix="z3998: http://www.daisy.org/ <http://

> www.daisy.org/> <http://www.daisy.org/ <http://www.daisy.org/>>

> > > z3998/2012/vocab/structure/ <http://
> > > www.daisy.org/z3998/2012/vocab/structure/ <http://

> www.daisy.org/z3998/2012/vocab/structure/> <http://www.daisy.org/
> <http://www.daisy.org/>

> > z3998/2012/vocab/structure/>>, se:
> > > https://standardebooks.org/vocab/1.0 <https://

> standardebooks.org/vocab/1.0> <https://standardebooks.org/ <https://
> standardebooks.org/>

> > vocab/1.0> <https://
> > > standardebooks.org/vocab/1.0 <http://standardebooks.org/

> vocab/1.0> <http://standardebooks.org/ <http://standardebooks.org/>

> www.gutenberg.org/cache/epub/18817/> <https://
> > www.gutenberg.org/cache/epub/18817/ <http://www.gutenberg.org/

> cache/epub/18817/>>
> > > pg18817-images.html <https://www.gutenberg.org/ <https://

> www.gutenberg.org/> <https://
> > www.gutenberg.org/ <http://www.gutenberg.org/>>

> > > cache/epub/18817/pg18817-images.html>
> > >
> > > The poem/epigraph immediately precedes chapter 1.
> > >
> > > --
> > >
> > > 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/
> <https://groups.google.com/d/>
> > <https://groups.google.com/d/ <https://groups.google.com/d/>>
> > > msgid/standardebooks/8194c9a7-441d-4af8-af18-
> > > d7981ac19be2n%40googlegroups.com <http://40googlegroups.com>

> <http://40googlegroups.com <http://40googlegroups.com>>

> > <https://groups.google.com/ <https://groups.google.com/>
> <https://groups.google.com/ <https://groups.google.com/>>
> > > d/msgid/standardebooks/8194c9a7-441d-4af8-af18-
> > > d7981ac19be2n%40googlegroups.com <http://40googlegroups.com>

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

> > <https://groups.google.com/d/msgid/ <https://groups.google.com/d/
> msgid/>>
> > > standardebooks/a61fa935-5fde-4a46-b353-
> > c4bad1c0ea13n%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/>
> > a61fa935-5fde-4a46- <https://groups.google.com/d/msgid/ <https://
> groups.google.com/d/msgid/>
> > standardebooks/a61fa935-5fde-4a46->
> > > b353-c4bad1c0ea13n%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/aea05eaf-ce35-4a10-
> ace7-7b37cc934735n%40googlegroups.com <http://40googlegroups.com>
> > <https://groups.google.com/d/msgid/standardebooks/aea05eaf-
> ce35-4a10- <https://groups.google.com/d/msgid/standardebooks/
> aea05eaf-ce35-4a10->
> > ace7-7b37cc934735n%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/0eef7873-8aab-42e9-96fd-850f653c5c65n%40googlegroups.com
> <https://groups.google.com/d/msgid/
> standardebooks/0eef7873-8aab-42e9-96fd-850f653c5c65n%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

[Nitoy Gonzales]

what work can I contribute to this?

To view this discussion visit https://groups.google.com/d/msgid/standardebooks/0c9e86a3-03a8-4d31-acf2-d1e035c49320%40standardebooks.org.

--

Nitoy Gonzales https://linktr.ee/delightinggrace

[Weijia Cheng]

This project was already completed. If you want to get involved, take a look at the suggested books for first-time contributors.

[Nitoy Gonzales]

Thank you. Can't wait to get involved...

To view this discussion visit https://groups.google.com/d/msgid/standardebooks/fdfc8204-897a-4733-9809-21521401064en%40googlegroups.com.