[First Project] Search the Sky, by Frederik Pohl & C. M. Kornbluth?

[Andy Tinkham]

Hi, everyone! I'm Andy. I've read a few books from the corpus (and plan to read many more!) and have lurked for a bit on the mailing list. I really like what you're doing here and would like to get involved!  I've had various software engineering roles throughout my career - currently I'm a security architect at CyberArk.  I live in Minnesota, where I'm usually either reading or curating my ebook collection when I'm not working/sleeping. 

I'd like to start on a sci-fi book. "Search the Sky" by Frederik Pohl & C. M. Kornbluth caught my eye and reading the first chapter on PG left me wanting to read more. I see there have been a couple of attempts at this previously, but both seem to have petered out pretty quickly. The last message I see on it was about 2 years ago.  Is it OK to start anew on it?

From past threads, I see https://archive.org/details/SearchTheSky/ has the scans. I've read the step-by-step walkthrough and the SEMOS. Pretty sure it didn't all stick, so I'm sure I'll be reading it again many times. :D. I'll reference other multi-author works to make sure I get the .opf set up correctly.  Anything else I should know before jumping in?

Thanks!

[Andy Tinkham]

Hmmm - I thought I had successfully installed the toolset previously, but it doesn't look like it. Trying to do it now, I get an error "invalid version number in 'MACOSX_DEPLOYMENT_TARGET=13'. I see the instructions only cover up to MacOS 12. All my machines are running Ventura. Am I unable to contribute, then? 

[B Keith]

Not sure what went wrong with your install but I am running it on Ventura 13.4 (M2) just fine

Bruce

_________

Gaudeamus igitur iuvenes dum sumus

-- 
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 on the web visit https://groups.google.com/d/msgid/standardebooks/c1cf70c4-d24f-4d5d-b43f-766bd2fe14ban%40googlegroups.com.

[Andy Tinkham]

Hmmm - mine's an Intel machine still and I'm on 13.4.1. Python's not a language I know well, but I'll look around in the repo and see id anything jumps out to me. Thanks! I think I could make an Ubuntu container and make it work too... will think on that.

[Vince]

I’m on a couple of Intels running Ventura, no problems.

This has come up on the list before, and if I remember correctly Robin pointed out something, but I don’t remember what. Let me see if I can find it…

Yes, the last time this happened, it was that there were problems with the XCode’s command line tools install. (See here.) They reinstalled it and were good.

[Andy Tinkham]

Ah! Thanks. I had noticed I had python 3.8, 3.9, 3.10, and 3.11 installed with 3.9 as the default and was trying to get pyenv running. That gave me an error too where I was about to look at the Xcode tools as your message came in. Reinstalling them fixed everything, so I'm good to go, pending approval of starting Search the Sky. 

Thank you both!!

[Alex Cabal]

Sure, that one would be a good start.

As you noted it's been attempted a few times in the past. Please check
the past threads for any notes.

Cover art for sci fi is usually an abstract/cubist/futurist painting.
See the art section of the manual for some links to unsorted futurist
art books that you can browse through for covers.

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

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! :)

> --
> 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 on the web visit

> https://groups.google.com/d/msgid/standardebooks/408ec1e1-382d-484b-8d3d-9319e7048992n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/408ec1e1-382d-484b-8d3d-9319e7048992n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Andy Tinkham]

I started on the book and the step-by-step guide last night. Here's my repo: https://github.com/andytinkham/frederik-pohl_c-m-kornbluth_search-the-sky

[Alex Cabal]

Weijia can you manage this with Robin reviewing?

On 7/10/23 10:11 AM, Andy Tinkham wrote:
> I started on the book and the step-by-step guide last night. Here's my
> repo: https://github.com/andytinkham/frederik-pohl_c-m-kornbluth_search-the-sky
>
> On Sunday, July 9, 2023 at 7:52:40 PM UTC-5 Alex Cabal wrote:
>
> Sure, that one would be a good start.
>
> As you noted it's been attempted a few times in the past. Please check
> the past threads for any notes.
>
> Cover art for sci fi is usually an abstract/cubist/futurist painting.
> See the art section of the manual for some links to unsorted futurist
> art books that you can browse through for covers.
>
> 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>

> https://groups.google.com/d/msgid/standardebooks/408ec1e1-382d-484b-8d3d-9319e7048992n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/408ec1e1-382d-484b-8d3d-9319e7048992n%40googlegroups.com> <https://groups.google.com/d/msgid/standardebooks/408ec1e1-382d-484b-8d3d-9319e7048992n%40googlegroups.com?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/408ec1e1-382d-484b-8d3d-9319e7048992n%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 on the web visit

> https://groups.google.com/d/msgid/standardebooks/fb9e7fa5-fd80-4087-a86a-73d9f538e8cfn%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/fb9e7fa5-fd80-4087-a86a-73d9f538e8cfn%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Robin Whittleton]

Can review.

> On 10 Jul 2023, at 17:22, Alex Cabal <al...@standardebooks.org> wrote:
>
> Weijia can you manage this with Robin reviewing?

> To unsubscribe from this group and stop receiving emails from it, send an email to standardebook...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/fabf0d61-06f4-2a1e-d603-151e09822ce5%40standardebooks.org.

[Weijia Cheng]

Sure, I will manage this and answer any questions that come up.

[Andy Tinkham]

OK, I’m through a proofread and addressing the things I noticed. Here’s the questions I’ve accumulated. Sorry for dumping them all at once. Most came up yesterday when I started over or late last night as I was proofreading.  (if you look at the repo, changes are currently in the attempt-2 branch. I’ll get them into main soon.)

- Is “radar” considered an acronym still, and thus needs <abbr> tags?

- The scans & transcript have “glamor” instead of the more common “glamour” (see lower middle of page 12: https://archive.org/details/SearchTheSky/page/n17/mode/2up).  “Glamor” is in Merriam-Webster, but should I replace it?

- Should I replace “week end” with “weekend” (bottom of page 4: https://archive.org/details/SearchTheSky/page/n9/mode/2up) and “pet cocks” with “petcocks” (bottom of page 34: https://archive.org/details/SearchTheSky/page/n39/mode/2up)? Removing the space wouldn’t change the meaning - so this would just be a modernization as well.

- Same vein - the text uses “Whups” instead of “Whoops” (as in “Whoops, I made a mistake” not “gonna get a whupping”. Middle of page 13: https://archive.org/details/SearchTheSky/page/n19/mode/2up). Should that change?

- For names of spaceships - my understanding is that they should be italicized. There’s no epub:type for “spaceship" though. I tried just “se:name:vessel” but se lint didn’t like that. Should I use “se:name:vessel:ship”, make a new entry, or leave the epub:type attribute off? (Or not italicize the names? They’re single quoted in the scans and transcript.)

- For acronyms, the text uses F-T-L for faster than light. It talks about “F-T-L ships” and “F-T-L drives”. Other acronyms like GCA (ground control authority) don’t have the dashes. I shifted the non-dash ones to have periods and <abbr> tags. Do the hyphenated ones get changed to periods too? (I assume they do get tags either way.) Also, there’s “L-C” (“Lindbergh-Carrel” - a brand name of a heart pump in the story).

- One of the changes made automatically was changing “God damned” to “Goddamned”. It left a “God damn” though (as “God damn it”) (middle of page 47: https://archive.org/details/SearchTheSky/page/n53/mode/2up). Should that be changed?

- The word “semilegendary” appears in the text. It hyphenated on my ereader as “semile-gendary”. Is there anything I should do to prevent this, or is it just a fluke?

- The original text uses “Jonesfearing” (Jones is a diety/currency/general population standard among other things on the planet Jones)  top of page 118 - https://archive.org/details/SearchTheSky/page/n123/mode/2up).  There are lots of other Jones words that aren’t hyphenated in the text. “Jonesologist”, “Jonesgrad”, “Jonesboro”, “Jonesism”, etc. The transcriber decided that only “Jones-fearing” should be changed to have the hyphen and added a transcription note for that. I’m inclined to change it back. Should I leave it? 

- There are signs whose text is shown in the scans: (see https://archive.org/details/SearchTheSky/page/n129/mode/2up). Right now, I have them formatted basically like poems, but that doesn’t make them centered and right-aligned, just indents them. Should these be formatted differently, and, if so, could I get some help with the CSS to do so, please? CSS is not my strong suit.

- At one point, a minor character says “Yuhsehtheybebems!” (see middle of page 139 https://archive.org/details/SearchTheSky/page/n145/mode/2up). This is English, on Earth, but at a point in the future where the general population is losing intelligence. I *think* that the character is saying “Yes sir, they be thems”, but that’s just my interpretation. The meaning doesn’t need to be clearer in the story. Should I put some sort of semantics / language tagging on this?

- Late in the book, a character is drunk and singing (see bottom of page 138 https://archive.org/details/SearchTheSky/page/n143/mode/2up). I put the song text in a blockquote and a single <p>. Should I split the lines up into spans and brs, or just leave it as a single p?

- The original text includes “boy!,” (bottom of page 151: https://archive.org/details/SearchTheSky/page/n157/mode/2up). se lint doesn’t like the !, combo. Should I change the text or make an exception for linting?

- The original scan has an errant smudge that the transcription reports as a comma (page 162, “First, education…” paragraph,  end of 8th line - “…a child would be simply too” https://archive.org/details/SearchTheSky/page/n167/mode/2up). Zooming in shows it’s clearly not a fully printed comma. I assume the right step here is make a non-editorial commit and then report it to Gutenberg. Is that correct?

- I’ve got some poems early on in the book (see pages 39 & 40: https://archive.org/details/SearchTheSky/page/n45/mode/2up). The last line of the stanza is indented. I used the CSS in the SEMOS. It worked later in the book, but for the linked scans, it doesn’t show as indented. I’ve got:

<blockquote epub:type="z3998:verse">

<p>

<span>“In great-grandfather’s time the target was Clyde,</span>

<br/>

<span>Rocketry firm and ores on the side.</span>

<br/>

<span>If we hadn’t of seen them direct we’d of missed ’em;</span>

<br/>

<span>There wasn’t a blip from the whole damn system.</span>

<br/>

<span class="i1">That was the first.</span>

<br/>

<span>Before great-grandfather’s day was done</span>

<br/>

<span>We cut the orbit of Cyrnus One.</span>

<br/>

<span>The contact there was Trader McCue,</span>

<br/>

<span>But the sons o’ bitches missed us too.</span>

<br/>

<span class="i1">That was the second.</span>

<br/>

<span>My grandpa lived to see the green</span>

<br/>

<span>Of Target Three through the high-powered screen.</span>

<br/>

<span>But where in hell was Builder Carruthers?</span>

<br/>

<span>They let us go by like all the others.</span>

<br/>

<span class="i1">That was the⁠—”</span>

</p>

in the xhtml and 

p span.i1{

padding-left: 2em;

text-indent: -1em;

}

[epub|type~="z3998:verse"] p{

text-align: initial;

text-indent: 0;

}

[epub|type~="z3998:verse"] p > span{

display: block;

padding-left: 1em;

text-indent: -1em;

}

[epub|type~="z3998:verse"] p > span + br{

display: none;

}

in the CSS. Any idea what I’m doing wrong? 

Thanks! I’ve got an idea for a cover, but I’ll put that in another mail. Given work commitments, it’ll probably be next weekend before I have significant time to address the remaining things. 

Andy

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/63e12e69-f410-4180-902f-629a950c8750n%40googlegroups.com.

[Andy Tinkham]

For a cover, I’m thinking of https://babel.hathitrust.org/cgi/pt?id=hvd.32044034099648&view=1up&seq=10

Points in its favor:

- it’s cubist, fitting the overall guidance for sci fi

- it’s in a book specifically recommended in the past for sci fi covers, published in 1919

- the circles and extra lines in the background remind me of visiting different colonies that are “off” due to genetic limitations of small populations, the main idea of the book

- I didn’t try the search thing from a few days back, but before I saw that, I scrolled through the corpus and didn’t see that the painting had been used

Points against it:

- the main protagonist is described as “solid and fair”. That’s a bit of a stretch for the guy in the painting, but not hugely off. He’s solid and white skin still could be fair. My mental picture of the protagonist has lighter hair though.

- I’m new at this and it’s nearly the first painting I looked at. It’s the first painting in the book. I had a moment of “that would work!” but I have no calibration as to whether that’s a good instinct of not 😆

So, am I even on the right track here?

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/88A61FE5-733D-43E8-B675-EFA3A2875B99%40tinkham.org.

[Weijia Cheng]

• No <abbr> tag on "radar"
• Per ngrams usage you can change "glamor" to "glamour" in an editorial commit
• You can remove the spaces in "week end" and "pet cocks" in editorial commits
• You should leave "whups" as is, that's not a sound-alike change and could be taken to be dialectical usage anyways
• Use <i epub:type="se:name.vessel.ship"> for spaceship names. You can add italics in a non-editorial commit
  
• You can set "F-T-L" as "F.T.L." like any other initialism. See 8.10.2. If "L-C" is a brand name, you can follow 8.10.9.5 and leave it as is.
• You should leave "God damn" as is
• That's either a quirk of the Pyphen module we use to add soft hyphens to the text for certain epub builds or an issue with the rendering software on your ereader. In either case, it's not something we can control as the ebook producer so you can disregard that
• I agree, you should revert "Jones-fearing" to "Jonesfearing." This can be done in a non-editorial commit
  
• For the stop sign, I think the HTML should look something like
  <blockquote>
  <p>Stop!</p>
  <p>Restricted Area Ahead</p>
  <p>Warning: This Road Is Mined</p>
  <p>“Trespassers beyond this point will be shot without further notice.” Decree #404⁠‒⁠5</p>
  <p>People’s Commissariat of Culture and Solidarity.</p>
  </blockquote>
  
  You don't need to capture the exact formatting of the original printing. We're trying to capture the semantics of the book, not the original appearance. There isn't a semantic reason for a break after "shot" or "Commissariat of," that just happens to be where the original printer ran out of space. Similarly the first three lines should be distinct paragraphs because they are distinct thoughts.
  With this HTML format you can play with the :nth-child selector to give different treatments to each line. Some pointers:
  - Use text-transform: uppercase for the "STOP!" line
  - Use font-variant: all-small-caps for the "Restricted Area Ahead" line
  - Use font-variant: small-caps for the third and fourth lines (the difference between all-small-caps and small-caps is that small-caps preserves capitalization and all-small-caps does not, just like you see in the original printing)
  - Use text-align: center on the sign blockquote to center all of the lines, then add a rule for the last line specifically to right-align the "People's Commissariat" etc. line
  
• No need for tagging on that, that's just a somewhat extreme case of English dialect if your interpretation is right
• Just leave it as is, the text doesn't really indicate how you would scan the song as verse so splitting it up would just be conjecture
• You can delete the comma in an editorial commit. We have plenty of cases of an exclamation point in the middle of a sentence in the corpus and it's a more standard usage than an exclamation point followed by a comma
• That's correct, fix it as a non-editorial commit (transcription fixes are non-editorial) and report it to Gutenberg
• The order that you specify the CSS rules matter. Try copying the CSS exactly as you find it in the manual example, with the i1 rule coming after the other verse rules. That will add the indentation. As a side note, you should consolidate the z3998:verse and z3998:poetry rules so that they are just different selectors on the same rules. E.g.
  [epub|type~="z3998:poem"] p,
  [epub|type~="z3998:verse"] p { etc. }

The painting looks OK to me. It's hard enough to find a painting and generally I'm ok with anything that isn't egregiously off-base (though among the S.E. editors I might be one of the least picky when it comes to paintings). Since you found PD proof you can use the higher quality image found on Wikipedia https://en.wikipedia.org/wiki/File:Albert_Gleizes,_l%27Homme_au_Balcon,_1912,_oil_on_canvas,_195.6_x_114.9_cm,_Philadelphia_Museum_of_Art.jpg

[Andy Tinkham]

Thank you, Weijia! I think that takes care of all my content issues. Nearly done!

I’ve got 2 questions on the cover… 

1) Is your OK enough, or do I need Alex to approve it as well before committing to my repo?

2) I made a mockup using se build-images but the font looks wrong. I do have the League Spartan font installed on my computer (at least it shows up when I open Font Book…). Any thoughts on where I may have gone astray here? (the white edge is just my poor screenshotting.)

Before I ran se build-images ., the blank cover was looking like this. The font is heavier weight there, though it may only be the weight itself that’s different… At a guess, the new cover uses Regular weight while the old one was a SemiBold.  

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/e4db13b3-c715-4943-aae7-de1a68ad6a4an%40googlegroups.com.

[Robin Whittleton]

I think both Weijia and I are a bit tied up for the moment so apologies for the delay. Weijia’s approved the painting so feel free to commit it.

With the font problem, are you looking at the image in ./images, or the image in ./src/epub/images? The fonts don’t need to be installed separately as they’re provided in the Standardebooks tool for build-images to use.

-Robin

On 23 Jul 2023, at 01:34, Andy Tinkham <an...@tinkham.org> wrote:

Thank you, Weijia! I think that takes care of all my content issues. Nearly done!

I’ve got 2 questions on the cover… 

1) Is your OK enough, or do I need Alex to approve it as well before committing to my repo?

2) I made a mockup using se build-images but the font looks wrong. I do have the League Spartan font installed on my computer (at least it shows up when I open Font Book…). Any thoughts on where I may have gone astray here? (the white edge is just my poor screenshotting.)

<Screenshot 2023-07-22 at 7.27.11 PM.png>

Before I ran se build-images ., the blank cover was looking like this. The font is heavier weight there, though it may only be the weight itself that’s different… At a guess, the new cover uses Regular weight while the old one was a SemiBold.  

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/84B4D301-50EC-4F1E-81ED-83E56980D1DB%40tinkham.org.

[Weijia Cheng]

Sorry, I missed this over the weekend! As Robin says, it's fine to commit as long as the manager Alex assigns (me in this case) approves the image. I think what you're seeing in the mockup has something to do with how SVG renders in different image viewing software. Can you push your repo so that I can clone it and take a look on my laptop?

[Andy Tinkham]

Thank you both! I pushed everything to my repo and rebased `main` so it’s all in the default branch.  Looking at./src/epub/images/cover.svg in GitHub, it looks like things are correct, so I think it might have been different programs.

I’ll pick up the remaining tasks soon, maybe even tonight!

Andy

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/8c8288e6-dae9-4eb5-b8a3-3cff9a9464e1n%40googlegroups.com.

[Andy Tinkham]

OK, one last question. Everything up to here is checked in to my repo should you want to look at the files or start reviewing.

se lint is complaining about “Element with text-align: center; but text-indent is 1em.”

This is happening in my signs, chapter 11, lines 18-21 and lines 47-49, and chapter 12, lines 77-79.  These are the signs I asked about earlier. I’ve tried removing “padding-left: 1em;” in the blockquote.sign CSS, using text-indent: -1em; like in the poem/verse CSS, and I’ve tried overriding text-indent to be 0em in that sign CSS, but none made lint happy. The signs look like they render correctly in KOReader when I build an ebook. 

Any suggestions?

Thanks!

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/28321CA0-EF42-4A50-9EEC-35FA489BDC1B%40tinkham.org.

[Alex Cabal]

Open the file in a web browser and use the inspector to see what style
is indenting the text. Then you'll get a better idea of how to override it.

>>>>> * No <abbr> tag on "radar"
>>>>> * Perngrams
>>>>> <https://books.google.com/ngrams/graph?content=glamor%2Cglamour&year_start=1800&year_end=2019&corpus=en-2019&smoothing=3>usage you can change "glamor" to "glamour" in an editorial commit
>>>>> * You can remove the spaces in "week end" and "pet cocks" in
>>>>> editorial commits
>>>>> * You should leave "whups" as is, that's not a sound-alike

>>>>> change and could be taken to be dialectical usage anyways

>>>>> * Use <i epub:type="se:name.vessel.ship"> for spaceship

>>>>> names. You can add italics in a non-editorial commit

>>>>> * You can set "F-T-L" as "F.T.L." like any other initialism.
>>>>> See8.10.2
>>>>> <https://standardebooks.org/manual/1.7.1/8-typography#8.10.2>. If "L-C" is a brand name, you can follow8.10.9.5 <https://standardebooks.org/manual/1.7.1/8-typography#8.10.9.5>and leave it as is.
>>>>> * You should leave "God damn" as is
>>>>> * That's either a quirk of the Pyphen module we use to add

>>>>> soft hyphens to the text for certain epub builds or an
>>>>> issue with the rendering software on your ereader. In
>>>>> either case, it's not something we can control as the ebook
>>>>> producer so you can disregard that

>>>>> * I agree, you should revert "Jones-fearing" to

>>>>> "Jonesfearing." This can be done in a non-editorial commit

>>>>> * For the stop sign, I think the HTML should look something like

>>>>> <blockquote>
>>>>> <p>Stop!</p>
>>>>> <p>Restricted Area Ahead</p>
>>>>> <p>Warning: This Road Is Mined</p>
>>>>> <p>“Trespassers beyond this point will be shot without
>>>>> further notice.” Decree #404⁠‒⁠5</p>
>>>>> <p>People’s Commissariat of Culture and Solidarity.</p>
>>>>> </blockquote>
>>>>>
>>>>> You don't need to capture the exact formatting of the

>>>>> original printing. We're trying to capture the/semantics/of

>>>>> the book, not the original appearance. There isn't a
>>>>> semantic reason for a break after "shot" or "Commissariat
>>>>> of," that just happens to be where the original printer ran
>>>>> out of space. Similarly the first three lines should be
>>>>> distinct paragraphs because they are distinct thoughts.
>>>>> With this HTML format you can play with the:nth-child

>>>>> <https://www.w3schools.com/cssref/sel_nth-child.php>selector to give different treatments to each line. Some pointers:
>>>>> - Usetext-transform: uppercase
>>>>> <https://developer.mozilla.org/en-US/docs/Web/CSS/text-transform>for the "STOP!" line

>>>>> - Use font-variant: all-small-caps for the "Restricted Area
>>>>> Ahead" line
>>>>> - Use font-variant: small-caps for the third and fourth
>>>>> lines (the difference between all-small-caps and small-caps
>>>>> is that small-caps preserves capitalization and
>>>>> all-small-caps does not, just like you see in the original
>>>>> printing)
>>>>> - Usetext-align: center

>>>>> <https://developer.mozilla.org/en-US/docs/Web/CSS/text-align>on the sign blockquote to center all of the lines, then add a rule for the last line specifically to right-align the "People's Commissariat" etc. line
>>>>> * No need for tagging on that, that's just a somewhat extreme

>>>>> case of English dialect if your interpretation is right

>>>>> * Just leave it as is, the text doesn't really indicate how

>>>>> you would scan the song as verse so splitting it up would
>>>>> just be conjecture

>>>>> * You can delete the comma in an editorial commit. We have

>>>>> plenty of cases of an exclamation point in the middle of a
>>>>> sentence in the corpus and it's a more standard usage than
>>>>> an exclamation point followed by a comma

>>>>> * That's correct, fix it as a non-editorial commit

>>>>> (transcription fixes are non-editorial) and report it to
>>>>> Gutenberg

>>>>> * The order that you specify the CSS rules matter. Try
>>>>> copying the CSS/exactly/as you find it in themanual example
>>>>> <https://standardebooks.org/manual/1.7.1/7-high-level-structural-patterns#7.5.7>, with the i1 rule coming after the other verse rules. That will add the indentation. As a side note, you should consolidate the z3998:verse and z3998:poetry rules so that they are just different selectors on the same rules. E.g.

>>>>> [epub|type~="z3998:poem"] p,
>>>>> [epub|type~="z3998:verse"] p { etc. }
>>>>>
>>>>> The painting looks OK to me. It's hard enough to find a
>>>>> painting and generally I'm ok with anything that isn't
>>>>> egregiously off-base (though among the S.E. editors I might be
>>>>> one of the least picky when it comes to paintings). Since you
>>>>> found PD proof you can use the higher quality image found on

>>>>> Wikipediahttps://en.wikipedia.org/wiki/File:Albert_Gleizes,_l%27Homme_au_Balcon,_1912,_oil_on_canvas,_195.6_x_114.9_cm,_Philadelphia_Museum_of_Art.jpg <https://en.wikipedia.org/wiki/File:Albert_Gleizes,_l%27Homme_au_Balcon,_1912,_oil_on_canvas,_195.6_x_114.9_cm,_Philadelphia_Museum_of_Art.jpg>

>>>>>
>>>>> On Sunday, July 16, 2023 at 2:59:34 PM UTC-7 an...@tinkham.org

>>>>> <http://tinkham.org/>wrote:

>>>>>
>>>>> For a cover, I’m thinking of

>>>>> https://babel.hathitrust.org/cgi/pt?id=hvd.32044034099648&view=1up&seq=10 <https://babel.hathitrust.org/cgi/pt?id=hvd.32044034099648&view=1up&seq=10>

>>>>>> 12:https://archive.org/details/SearchTheSky/page/n17/mode/2up <https://archive.org/details/SearchTheSky/page/n17/mode/2up>).  “Glamor” is in Merriam-Webster, but should I replace it?

>>>>>>
>>>>>> - Should I replace “week end” with “weekend” (bottom of
>>>>>> page

>>>>>> 4:https://archive.org/details/SearchTheSky/page/n9/mode/2up <https://archive.org/details/SearchTheSky/page/n9/mode/2up>) and “pet cocks” with “petcocks” (bottom of page 34:https://archive.org/details/SearchTheSky/page/n39/mode/2up <https://archive.org/details/SearchTheSky/page/n39/mode/2up>)? Removing the space wouldn’t change the meaning - so this would just be a modernization as well.

>>>>>>
>>>>>> - Same vein - the text uses “Whups” instead of “Whoops”
>>>>>> (as in “Whoops, I made a mistake” not “gonna get a
>>>>>> whupping”. Middle of page

>>>>>> 13:https://archive.org/details/SearchTheSky/page/n19/mode/2up <https://archive.org/details/SearchTheSky/page/n19/mode/2up>). Should that change?

>>>>>>
>>>>>> - For names of spaceships - my understanding is that they
>>>>>> should be italicized. There’s no epub:type for “spaceship"
>>>>>> though. I tried just “se:name:vessel” but se lint didn’t
>>>>>> like that. Should I use “se:name:vessel:ship”, make a new
>>>>>> entry, or leave the epub:type attribute off? (Or not
>>>>>> italicize the names? They’re single quoted in the scans
>>>>>> and transcript.)
>>>>>>
>>>>>> - For acronyms, the text uses F-T-L for faster than light.
>>>>>> It talks about “F-T-L ships” and “F-T-L drives”. Other
>>>>>> acronyms like GCA (ground control authority) don’t have
>>>>>> the dashes. I shifted the non-dash ones to have periods
>>>>>> and <abbr> tags. Do the hyphenated ones get changed to
>>>>>> periods too? (I assume they do get tags either way.) Also,
>>>>>> there’s “L-C” (“Lindbergh-Carrel” - a brand name of a
>>>>>> heart pump in the story).
>>>>>>
>>>>>> - One of the changes made automatically was changing “God
>>>>>> damned” to “Goddamned”. It left a “God damn” though (as
>>>>>> “God damn it”) (middle of page

>>>>>> 47:https://archive.org/details/SearchTheSky/page/n53/mode/2up <https://archive.org/details/SearchTheSky/page/n53/mode/2up>). Should that be changed?

>>>>>>
>>>>>> - The word “semilegendary” appears in the text. It
>>>>>> hyphenated on my ereader as “semile-gendary”. Is there
>>>>>> anything I should do to prevent this, or is it just a fluke?
>>>>>>
>>>>>> - The original text uses “Jonesfearing” (Jones is a
>>>>>> diety/currency/general population standard among other
>>>>>> things on the planet Jones)  top of page 118 -

>>>>>> https://archive.org/details/SearchTheSky/page/n123/mode/2up <https://archive.org/details/SearchTheSky/page/n12/mode/2up>).  There are lots of other Jones words that aren’t hyphenated in the text. “Jonesologist”, “Jonesgrad”, “Jonesboro”, “Jonesism”, etc. The transcriber decided that only “Jones-fearing” should be changed to have the hyphen and added a transcription note for that. I’m inclined to change it back. Should I leave it?

>>>>>>
>>>>>> - There are signs whose text is shown in the scans: (see

>>>>>> https://archive.org/details/SearchTheSky/page/n129/mode/2up <https://archive.org/details/SearchTheSky/page/n129/mode/2up>). Right now, I have them formatted basically like poems, but that doesn’t make them centered and right-aligned, just indents them. Should these be formatted differently, and, if so, could I get some help with the CSS to do so, please? CSS is not my strong suit.

>>>>>>
>>>>>> - At one point, a minor character says “Yuhsehtheybebems!”
>>>>>> (see middle of page 139

>>>>>> https://archive.org/details/SearchTheSky/page/n145/mode/2up <https://archive.org/details/SearchTheSky/page/n145/mode/2up>). This is English, on Earth, but at a point in the future where the general population is losing intelligence. I *think* that the character is saying “Yes sir, they be thems”, but that’s just my interpretation. The meaning doesn’t need to be clearer in the story. Should I put some sort of semantics / language tagging on this?

>>>>>>
>>>>>> - Late in the book, a character is drunk and singing (see
>>>>>> bottom of page 138

>>>>>> https://archive.org/details/SearchTheSky/page/n143/mode/2up <https://archive.org/details/SearchTheSky/page/n143/mode/2up>). I put the song text in a blockquote and a single <p>. Should I split the lines up into spans and brs, or just leave it as a single p?

>>>>>>
>>>>>> - The original text includes “boy!,” (bottom of page 151:

>>>>>> https://archive.org/details/SearchTheSky/page/n157/mode/2up <https://archive.org/details/SearchTheSky/page/n157/mode/2up>). se lint doesn’t like the !, combo. Should I change the text or make an exception for linting?

>>>>>>
>>>>>> - The original scan has an errant smudge that the
>>>>>> transcription reports as a comma (page 162, “First,
>>>>>> education…” paragraph,  end of 8th line - “…a child would
>>>>>> be simply

>>>>>> too”https://archive.org/details/SearchTheSky/page/n167/mode/2up <https://archive.org/details/SearchTheSky/page/n167/mode/2up>). Zooming in shows it’s clearly not a fully printed comma. I assume the right step here is make a non-editorial commit and then report it to Gutenberg. Is that correct?

>>>>>>
>>>>>> - I’ve got some poems early on in the book (see pages 39 &
>>>>>> 40:
>>>>>> https://archive.org/details/SearchTheSky/page/n45/mode/2up

>>>>>> <https://archive.org/details/SearchTheSky/page/n45/mode/2up>). The last line of the stanza is indented. I used the CSS in the SEMOS. It worked later in the book, but for the linked scans, it doesn’t show as indented. I’ve got:

>>>>>>> <http://standardebooks.org/>> wrote:
>>>>>>> >
>>>>>>> > Weijia can you manage this with Robin reviewing?
>>>>>>> >
>>>>>>> >> On 7/10/23 10:11 AM, Andy Tinkham wrote:
>>>>>>> >> I started on the book and the step-by-step guide
>>>>>>> last night. Here's my

>>>>>>> repo:https://github.com/andytinkham/frederik-pohl_c-m-kornbluth_search-the-sky <https://github.com/andytinkham/frederik-pohl_c-m-kornbluth_search-the-sky>

>>>>>>> >> On Sunday, July 9, 2023 at 7:52:40 PM UTC-5 Alex
>>>>>>> Cabal wrote:
>>>>>>> >> Sure, that one would be a good start.
>>>>>>> >> As you noted it's been attempted a few times in
>>>>>>> the past. Please check
>>>>>>> >> the past threads for any notes.
>>>>>>> >> Cover art for sci fi is usually an
>>>>>>> abstract/cubist/futurist painting.
>>>>>>> >> See the art section of the manual for some links
>>>>>>> to unsorted futurist
>>>>>>> >> art books that you can browse through for covers.
>>>>>>> >> 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 <https://standardebooks.org/manual>>

>>>>>>> >>https://standardebooks.org/manual/latest/4-semantics <https://standardebooks.org/manual/latest/4-semantics>
>>>>>>> >>
>>>>>>> <https://standardebooks.org/manual/latest/4-semantics
>>>>>>> <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/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>
>>>>>>> >>
>>>>>>> <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><https://standardebooks.org/contribute/producing-an-ebook-step-by-step <https://standardebooks.org/contribute/producing-an-ebook-step-by-step>>

>>>>>>> <http://googlegroups.com/>
>>>>>>> >> > <mailto:standardebook...@googlegroups.com
>>>>>>> <http://googlegroups.com/>>.

>>>>>>> >> > To view this discussion on the web visit
>>>>>>> >> >

>>>>>>> >>https://groups.google.com/d/msgid/standardebooks/408ec1e1-382d-484b-8d3d-9319e7048992n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/408ec1e1-382d-484b-8d3d-9319e7048992n%40googlegroups.com><https://groups.google.com/d/msgid/standardebooks/408ec1e1-382d-484b-8d3d-9319e7048992n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/408ec1e1-382d-484b-8d3d-9319e7048992n%40googlegroups.com>> <https://groups.google.com/d/msgid/standardebooks/408ec1e1-382d-484b-8d3d-9319e7048992n%40googlegroups.com?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/408ec1e1-382d-484b-8d3d-9319e7048992n%40googlegroups.com?utm_medium=email&utm_source=footer><https://groups.google.com/d/msgid/standardebooks/408ec1e1-382d-484b-8d3d-9319e7048992n%40googlegroups.com?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/408ec1e1-382d-484b-8d3d-9319e7048992n%40googlegroups.com?utm_medium=email&utm_source=footer>>>.

>>>>>>> >> --
>>>>>>> >> You received this message because you are
>>>>>>> subscribed to the Google Groups "Standard Ebooks" group.
>>>>>>> >> To unsubscribe from this group and stop receiving
>>>>>>> emails from it, send an email
>>>>>>> tostandardebook...@googlegroups.com

>>>>>>> <http://googlegroups.com/><mailto:standardebook...@googlegroups.com <http://googlegroups.com/>>.

>>>>>>> >> To view this discussion on the web

>>>>>>> visithttps://groups.google.com/d/msgid/standardebooks/fb9e7fa5-fd80-4087-a86a-73d9f538e8cfn%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/fb9e7fa5-fd80-4087-a86a-73d9f538e8cfn%40googlegroups.com><https://groups.google.com/d/msgid/standardebooks/fb9e7fa5-fd80-4087-a86a-73d9f538e8cfn%40googlegroups.com?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/fb9e7fa5-fd80-4087-a86a-73d9f538e8cfn%40googlegroups.com?utm_medium=email&utm_source=footer>>.

>>>>>>> >
>>>>>>> > --
>>>>>>> > You received this message because you are
>>>>>>> subscribed to the Google Groups "Standard Ebooks" group.
>>>>>>> > To unsubscribe from this group and stop receiving
>>>>>>> emails from it, send an email
>>>>>>> tostandardebook...@googlegroups.com

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

>>>>>>> > To view this discussion on the web

>>>>>>> visithttps://groups.google.com/d/msgid/standardebooks/fabf0d61-06f4-2a1e-d603-151e09822ce5%40standardebooks.org <https://groups.google.com/d/msgid/standardebooks/fabf0d61-06f4-2a1e-d603-151e09822ce5%40standardebooks.org>.

>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> You received this message because you are subscribed to
>>>>>>> the Google Groups "Standard Ebooks" group.
>>>>>>> To unsubscribe from this group and stop receiving emails

>>>>>>> from it, send an email tostandardebook...@googlegroups.com.

>>>>>>> To view this discussion on the web

>>>>>>> visithttps://groups.google.com/d/msgid/standardebooks/63e12e69-f410-4180-902f-629a950c8750n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/63e12e69-f410-4180-902f-629a950c8750n%40googlegroups.com?utm_medium=email&utm_source=footer>.

>>>>>>
>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to
>>>>>> the Google Groups "Standard Ebooks" group.
>>>>>> To unsubscribe from this group and stop receiving emails

>>>>>> from it, send an email tostandardebook...@googlegroups.com.

>>>>>> To view this discussion on the web

>>>>>> visithttps://groups.google.com/d/msgid/standardebooks/88A61FE5-733D-43E8-B675-EFA3A2875B99%40tinkham.org <https://groups.google.com/d/msgid/standardebooks/88A61FE5-733D-43E8-B675-EFA3A2875B99%40tinkham.org?utm_medium=email&utm_source=footer>.

>>>>>
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the
>>>>> Google Groups "Standard Ebooks" group.
>>>>> To unsubscribe from this group and stop receiving emails from

>>>>> it, send an email tostandardebook...@googlegroups.com.

>>>>> To view this discussion on the web

>>>>> visithttps://groups.google.com/d/msgid/standardebooks/e4db13b3-c715-4943-aae7-de1a68ad6a4an%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/e4db13b3-c715-4943-aae7-de1a68ad6a4an%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.
>>>> To view this discussion on the web visit

>>>> https://groups.google.com/d/msgid/standardebooks/84B4D301-50EC-4F1E-81ED-83E56980D1DB%40tinkham.org <https://groups.google.com/d/msgid/standardebooks/84B4D301-50EC-4F1E-81ED-83E56980D1DB%40tinkham.org?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 on the web visit

>>> https://groups.google.com/d/msgid/standardebooks/8c8288e6-dae9-4eb5-b8a3-3cff9a9464e1n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/8c8288e6-dae9-4eb5-b8a3-3cff9a9464e1n%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 on the web visit

>> https://groups.google.com/d/msgid/standardebooks/28321CA0-EF42-4A50-9EEC-35FA489BDC1B%40tinkham.org <https://groups.google.com/d/msgid/standardebooks/28321CA0-EF42-4A50-9EEC-35FA489BDC1B%40tinkham.org?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 on the web visit

> https://groups.google.com/d/msgid/standardebooks/A15BA1F2-FDE3-4272-8A81-CC8CAE343D6C%40tinkham.org <https://groups.google.com/d/msgid/standardebooks/A15BA1F2-FDE3-4272-8A81-CC8CAE343D6C%40tinkham.org?utm_medium=email&utm_source=footer>.

[Andy Tinkham]

Thanks, Alex! That, plus sleeping on it and looking anew in the morning lead me straight to the answer. (I needed another block called “blockquote.sign p” to change the p element. Previous attempts had been changing the style on the blockquote element. D’oh!).

Weijia & Robin - I think everything is set for review at this point.  

Just in case you need them since all the links are way down the thread now...

Repo: https://github.com/andytinkham/frederik-pohl_c-m-kornbluth_search-the-sky

PG book: https://www.gutenberg.org/ebooks/52228

IA scans: https://archive.org/details/SearchTheSky/

Thanks for all the help! I’m already thinking about what my next project might be. (Of course, I’ll get this one over the finish line before starting anything else.)

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/3495b8a2-07a5-da22-bf8d-b753340f5325%40standardebooks.org.

[Robin Whittleton]

OK, I’ll probably need until the end of the week due to other commitments but I’ll get through this asap.

-Robin

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/84524CA4-8F19-47B5-B970-6BB6FF74E5C6%40tinkham.org.

[Robin Whittleton]

OK, super good first run through. I’ve filed a set of issues at https://github.com/andytinkham/frederik-pohl_c-m-kornbluth_search-the-sky/issues/1, let me know if you need any additional info.

-Robin

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/84524CA4-8F19-47B5-B970-6BB6FF74E5C6%40tinkham.org.

[Andy Tinkham]

Thanks, Robin! I have a couple questions:

- For adding <meta property=“se:subject”>Fiction</meta> to the content.opf – I originally had it and se lint complained that Science Fiction implied Fiction. Should I put it back and add an ignore in se-lint-ignore?

- In chapter 11, I used the <q> tag as I interpreted the “Round pillars” text as Ross’ internal thoughts per 8.2.7. It didn’t really fit with the spoken dialogue around it, and “marveled” could be either a mental action or a spoken action.  Are you interpreting it differently, or am I misinterpreting the SEMOS?

I’ll get all the other changes made shorlty.

Thanks again!

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/1A3F6B82-9EC0-4AF7-AB4C-B90DDE5AD339%40reala.net.

[Andy Tinkham]

One more question.

You requested the en-dashes in longdesc all become em-dashes.  There are 2 sets:

- faster-than-light

- extrapolating-beyond-the-point-of-absurdity

My understanding is that the first should stay en-dashes because those words are being coupled as a single thing. The second should get the em-dashes. Is that correct?

Additional, the second bit currently ends with an em-dash, separating it from an aside comment. Does anything change with the ending em-dash?

Thanks!

[Robin Whittleton]

On Fiction implication, that’s fine then, I must have missed that update.

On <q>, that’s a reasonable interpretation, so leave it.

On the en-dash examples: faster-than-light is correctly using standard hyphens. But extrapolating–beyond–the–point–of–absurdity– currently uses en-dashes for everything. It should use hyphens to separate the words, and be followed by an em-dash. So: extrapolating-beyond-the-point-of-absurdity—

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/5689CA82-C453-483F-A62E-FD6DF7C4767F%40tinkham.org.

[Andy Tinkham]

Thanks, Robin! I think all the changes are made now. Do you re-review ti now, or what’s the next step in the process?

Andy

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/8E9A376A-75FB-4374-AEC5-390B5A0E896F%40reala.net.

[Robin Whittleton]

Did you push your latest changes? Either way, once you do I’ll give it another quick run through. If anything else crops up then I’ll flag it, but usually it’s a formality before we hand it over to Alex for publishing.

-Robin

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/ACD47442-402E-43E8-BA54-90E6E76FDBF5%40tinkham.org.

[Andy Tinkham]

I think so - didn’t make any changes today. I anticipated the em-dash change would be answered as you did, so pushed that yesterday with the unquestioned changes. Everything seems to be pushed to github - no uncommitted changes locally, and git push says “Everything up to date”.

Thanks!

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/1E8D0335-DC22-4189-B07E-347F47D788E4%40reala.net.

[Robin Whittleton]

Great, just checked and 👍 So the one remaining change is the en-dashes in the long description. As I mentioned we currently have extrapolating–beyond–the–point–of–absurdity– using en-dashes for everything. We should use hyphens to separate the words with an em-dash to separate the phrase from the following. So: extrapolating-beyond-the-point-of-absurdity—

-Robin

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/EA872290-34E9-42D2-B46D-7DAAC0DBEDA2%40tinkham.org.

[Andy Tinkham]

Now I’m confused. I thought you were saying to use emdashes for everything in "extrapolating–beyond–the–point–of–absurdity–“ (em-dashes everywhere) so that’s what’s in the repo now, but rereading today’s mail, it seems that you want "extrapolating-beyond-the-point-of-absurdity–", (regular - between words, em-dash at the end), which is what I had originally, I think. Am I confused about what dash is which type? (Regular - is the hyphen key on my US keyboard, – is Option-<Regular dash> and VSCode shows it as U+2013.)

I can put it back to hyphens with em-dash at the end, but if I do that, I don’t understand what I had differently originally, so want to make sure I get that for next time.

Thanks!

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/EA840A72-39FD-4938-A14B-A15AB5E16368%40reala.net.

[Andy Tinkham]

I pasted in exactly what you had in your mail. VS Code doesn’t flag your em-dash with a yellow box like other special characters, so I probably have my dashes confused.  The change is in my repo now.

Thanks, Robin!

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/E162DCFA-7D0F-4688-B568-B2E62F60A494%40tinkham.org.

[Vince]

There are hyphens (U+002D, the character to the right of 0 (zero) on US keyboards), en-dashes (U+2013) that are the width of an “n”, and em-dashes (U+2014) that are the width of an “m”. There are others, but those are the only three involved here.

Hyphens are used in compound words. En-dashes are used between ranges of numbers and dates. Em-dashes are used for interruptions. That’s a general summary, not intended to be exhaustive. :)

Originally, according to Robin’s first message, "extrapolating-beyond…" was using en-dashes between the words rather than hyphens, so those needed to be changed to hyphens.

[Andy Tinkham]

Ah, thanks, Vince! I think originally, I had hyphen followed by en-dash.  Then, I changed to all en-dashes.  Now I see where I got confused.

Thanks again!

-- 
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 on the web visit https://groups.google.com/d/msgid/standardebooks/4E085341-3B64-4529-B68A-04A631F72B81%40letterboxes.org.

[Robin Whittleton]

Thanks Vince. So yep, when you’ve changed the en-dashes in that phrase to hyphens with an em-dash on the end we’re done.

-Robin

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/4A1C09B9-4E73-40DA-A8FF-B3BA8CD263CE%40tinkham.org.

[Andy Tinkham]

Thanks, Robin! I believe that change is now pushed up.

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/677EB07B-D5E6-4277-93E4-ECB701024535%40reala.net.

[Robin Whittleton]

Good stuff, and congrats on getting your first SE book under your belt!

Over to you Alex.

-Robin

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/6FD6830A-ECD0-4BA0-BC35-A5BB002A2936%40tinkham.org.

[Andy Tinkham]

Thank you, Robin, Weijia, Vince, and Alex for all the help getting through this!

Does this feeling of eagerly watching email to see when Alex posts a release mail decrease the more books you do? 😆 It’s pretty exciting right now! 

Now to get back to the thread around what’s next and pick my next project…

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/69D58A6C-0267-4424-BBAC-06F921F69015%40reala.net.

[Kevin Palm]

I'm only on my third production but, at least in my case, it hasn't decreased for me!  I keep checking my email...  :-)

[Andy Tinkham]

Such a great feeling of accomplishment when it's done! I'm glad to hear the excitement doesn't wear off quickly!

On Aug 3, 2023, at 8:21 AM, Kevin Palm <pipe...@gmail.com> wrote:

I'm only on my third production but, at least in my case, it hasn't decreased for me!  I keep checking my email...  :-)

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/e3733966-57e4-45d5-9302-c0177c229b18n%40googlegroups.com.

[Robin Whittleton]

Hi Alex, just checking that you saw that this was ready.

-Robin

On 3 Aug 2023, at 15:26, Andy Tinkham <an...@tinkham.org> wrote:



To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/FF2C5E14-C714-4CDE-8C82-8E96EA854745%40tinkham.org.

[Alex Cabal]

Commit 7254adf is mixed up, it includes a lot of changes that are not
spelling related. Robin can you work with Andy to sort this out?

>>>>>>>> visithttps://groups.google.com/d/msgid/standardebooks/4E085341-3B64-4529-B68A-04A631F72B81%40letterboxes.org <https://groups.google.com/d/msgid/standardebooks/4E085341-3B64-4529-B68A-04A631F72B81%40letterboxes.org>.

>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> You received this message because you are subscribed to the
>>>>>>> Google Groups "Standard Ebooks" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from
>>>>>>> it, send an email to standardebook...@googlegroups.com.
>>>>>>> To view this discussion on the web visit

>>>>>>> https://groups.google.com/d/msgid/standardebooks/4A1C09B9-4E73-40DA-A8FF-B3BA8CD263CE%40tinkham.org <https://groups.google.com/d/msgid/standardebooks/4A1C09B9-4E73-40DA-A8FF-B3BA8CD263CE%40tinkham.org?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.
>>>>>> To view this discussion on the web visit

>>>>>> https://groups.google.com/d/msgid/standardebooks/677EB07B-D5E6-4277-93E4-ECB701024535%40reala.net <https://groups.google.com/d/msgid/standardebooks/677EB07B-D5E6-4277-93E4-ECB701024535%40reala.net?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.
>>>>> To view this discussion on the web visit

>>>>> https://groups.google.com/d/msgid/standardebooks/6FD6830A-ECD0-4BA0-BC35-A5BB002A2936%40tinkham.org <https://groups.google.com/d/msgid/standardebooks/6FD6830A-ECD0-4BA0-BC35-A5BB002A2936%40tinkham.org?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.
>>>> To view this discussion on the web visit

>>>> https://groups.google.com/d/msgid/standardebooks/69D58A6C-0267-4424-BBAC-06F921F69015%40reala.net <https://groups.google.com/d/msgid/standardebooks/69D58A6C-0267-4424-BBAC-06F921F69015%40reala.net?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 on the web visit

>>> https://groups.google.com/d/msgid/standardebooks/e3733966-57e4-45d5-9302-c0177c229b18n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/e3733966-57e4-45d5-9302-c0177c229b18n%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 on the web visit

>> https://groups.google.com/d/msgid/standardebooks/FF2C5E14-C714-4CDE-8C82-8E96EA854745%40tinkham.org <https://groups.google.com/d/msgid/standardebooks/FF2C5E14-C714-4CDE-8C82-8E96EA854745%40tinkham.org?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 on the web visit

> https://groups.google.com/d/msgid/standardebooks/382A7A00-C1B7-45CD-A39D-C094F92C01A6%40reala.net <https://groups.google.com/d/msgid/standardebooks/382A7A00-C1B7-45CD-A39D-C094F92C01A6%40reala.net?utm_medium=email&utm_source=footer>.

[Alex Cabal]

Also there are a lot of en dashes that are incorrect and should be em
dashes. Use the following to see them:

grep --only-matching ".{,10}–.{,10}" src/epub/text/*

Lastly, there are lint ignore entries for song. You can see where the
line breaks are supposed to go because the clause is capitalized in a
strange place. That's where we should put line breaks. Once you do that
you can remove the ignore entries.

On 8/4/23 12:58 PM, Robin Whittleton wrote:

>>>>>>>> visithttps://groups.google.com/d/msgid/standardebooks/4E085341-3B64-4529-B68A-04A631F72B81%40letterboxes.org <https://groups.google.com/d/msgid/standardebooks/4E085341-3B64-4529-B68A-04A631F72B81%40letterboxes.org>.
>>>>>>>
>>>>>>>

>>>>>>> --
>>>>>>> You received this message because you are subscribed to the
>>>>>>> Google Groups "Standard Ebooks" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from
>>>>>>> it, send an email to standardebook...@googlegroups.com.
>>>>>>> To view this discussion on the web visit

>>>>>>> https://groups.google.com/d/msgid/standardebooks/4A1C09B9-4E73-40DA-A8FF-B3BA8CD263CE%40tinkham.org <https://groups.google.com/d/msgid/standardebooks/4A1C09B9-4E73-40DA-A8FF-B3BA8CD263CE%40tinkham.org?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.
>>>>>> To view this discussion on the web visit

>>>>>> https://groups.google.com/d/msgid/standardebooks/677EB07B-D5E6-4277-93E4-ECB701024535%40reala.net <https://groups.google.com/d/msgid/standardebooks/677EB07B-D5E6-4277-93E4-ECB701024535%40reala.net?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.
>>>>> To view this discussion on the web visit

>>>>> https://groups.google.com/d/msgid/standardebooks/6FD6830A-ECD0-4BA0-BC35-A5BB002A2936%40tinkham.org <https://groups.google.com/d/msgid/standardebooks/6FD6830A-ECD0-4BA0-BC35-A5BB002A2936%40tinkham.org?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.
>>>> To view this discussion on the web visit

>>>> https://groups.google.com/d/msgid/standardebooks/69D58A6C-0267-4424-BBAC-06F921F69015%40reala.net <https://groups.google.com/d/msgid/standardebooks/69D58A6C-0267-4424-BBAC-06F921F69015%40reala.net?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 on the web visit

>>> https://groups.google.com/d/msgid/standardebooks/e3733966-57e4-45d5-9302-c0177c229b18n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/e3733966-57e4-45d5-9302-c0177c229b18n%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 on the web visit

>> https://groups.google.com/d/msgid/standardebooks/FF2C5E14-C714-4CDE-8C82-8E96EA854745%40tinkham.org <https://groups.google.com/d/msgid/standardebooks/FF2C5E14-C714-4CDE-8C82-8E96EA854745%40tinkham.org?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 on the web visit

> https://groups.google.com/d/msgid/standardebooks/382A7A00-C1B7-45CD-A39D-C094F92C01A6%40reala.net <https://groups.google.com/d/msgid/standardebooks/382A7A00-C1B7-45CD-A39D-C094F92C01A6%40reala.net?utm_medium=email&utm_source=footer>.

[Andy Tinkham]

I got the commit split up. (Ended up reseting everything to the previous commit, splitting that commit, and then re-doing all the subsequent changes. The step-by-step guide was not kidding about how painful rebasing is.  Glad I restarted early on in doing this book or it would have been much worse!)

Other than changes around the songs for the “Lastly…” comment below and one pair of seemingly identical but still flagged as different ines in the content.opf (short description), the end result is the same, so I don’t think I screwed anything up in redoing that.

Alex, I copied that grep command line and ran it, but it didn’t return any results for me.  I’m not 100% sure I have dashes staight entirely in practice, but I think I was able to use VSCode’s replace to replace the dash you have in the grep command with the dash Robin used where I was supposed to have an em dash. I hope I got the replacement right… Visually recognizing & inserting the correct dashes are definitely things I need to work on. 

Anyhow, I think everything is set. Not sure if it goes back to Robin for re-review or to Alex for another final check before release at this point, but it should be ready for that step, I think…

Andy

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/6150c266-6e27-d55b-4ea7-5d8a4c906594%40standardebooks.org.

[Andy Tinkham]

I should have put one extra thing in.  Between my second paragraph where I say everything is the same and the next where I start talking about dashes, I did the dash replacement. There are now more differences between old and new where all those dashes got replaced as expected for making that change. 

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/132E26DF-431F-45F1-BDBE-EDC63A2DCFF9%40tinkham.org.

[Robin Whittleton]

Odd about the dashes, I thought I’d checked that fairly thoroughly previously. Anyway, there are no en-dashes in the book now, so I guess that’s resolved.

Well done with the rebase Andy, that’s not particularly easy but this spelling commit looks to only contain spelling / hyphenation changes now. Typically I wouldn’t bother converting four-dot ellipses to three-dot (we don’t have a standard about that to the best of my knowledge) but it doesn’t hurt and you’ve marked it as Editorial so that’s good.

So I think that that (along with the se-lint-ignore changes) means that it’s ready again for you Alex.

-Robin

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/34677364-3B7E-4947-89B5-CFDCEFE47C22%40tinkham.org.

[Alex Cabal]

OK, looks good and I've gone ahead and released it. Thanks Andy!

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

>>>>>>>>>>>> visithttps://groups.google.com/d/msgid/standardebooks/4E085341-3B64-4529-B68A-04A631F72B81%40letterboxes.org <visithttps://groups.google.com/d/msgid/standardebooks/4E085341-3B64-4529-B68A-04A631F72B81%40letterboxes.org><https://groups.google.com/d/msgid/standardebooks/4E085341-3B64-4529-B68A-04A631F72B81%40letterboxes.org <https://groups.google.com/d/msgid/standardebooks/4E085341-3B64-4529-B68A-04A631F72B81%40letterboxes.org>>.

>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>    --     You received this message because you are
>>>>>>>>>>> subscribed to the
>>>>>>>>>>>    Google Groups "Standard Ebooks" group.
>>>>>>>>>>>    To unsubscribe from this group and stop receiving emails from
>>>>>>>>>>>    it, send an email to standardebook...@googlegroups.com

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

>>>>>>>>>>>    To view this discussion on the web visit

>>>>>>>>>>> https://groups.google.com/d/msgid/standardebooks/4A1C09B9-4E73-40DA-A8FF-B3BA8CD263CE%40tinkham.org <https://groups.google.com/d/msgid/standardebooks/4A1C09B9-4E73-40DA-A8FF-B3BA8CD263CE%40tinkham.org><https://groups.google.com/d/msgid/standardebooks/4A1C09B9-4E73-40DA-A8FF-B3BA8CD263CE%40tinkham.org?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/4A1C09B9-4E73-40DA-A8FF-B3BA8CD263CE%40tinkham.org?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

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

>>>>>>>>>>    To view this discussion on the web visit

>>>>>>>>>> https://groups.google.com/d/msgid/standardebooks/677EB07B-D5E6-4277-93E4-ECB701024535%40reala.net <https://groups.google.com/d/msgid/standardebooks/677EB07B-D5E6-4277-93E4-ECB701024535%40reala.net><https://groups.google.com/d/msgid/standardebooks/677EB07B-D5E6-4277-93E4-ECB701024535%40reala.net?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/677EB07B-D5E6-4277-93E4-ECB701024535%40reala.net?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

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

>>>>>>>>>    To view this discussion on the web visit

>>>>>>>>> https://groups.google.com/d/msgid/standardebooks/6FD6830A-ECD0-4BA0-BC35-A5BB002A2936%40tinkham.org <https://groups.google.com/d/msgid/standardebooks/6FD6830A-ECD0-4BA0-BC35-A5BB002A2936%40tinkham.org><https://groups.google.com/d/msgid/standardebooks/6FD6830A-ECD0-4BA0-BC35-A5BB002A2936%40tinkham.org?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/6FD6830A-ECD0-4BA0-BC35-A5BB002A2936%40tinkham.org?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

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

>>>>>>>>    To view this discussion on the web visit

>>>>>>>> https://groups.google.com/d/msgid/standardebooks/69D58A6C-0267-4424-BBAC-06F921F69015%40reala.net <https://groups.google.com/d/msgid/standardebooks/69D58A6C-0267-4424-BBAC-06F921F69015%40reala.net><https://groups.google.com/d/msgid/standardebooks/69D58A6C-0267-4424-BBAC-06F921F69015%40reala.net?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/69D58A6C-0267-4424-BBAC-06F921F69015%40reala.net?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 tostandardeboo...@googlegroups.com
>>>>>>> <mailto:standardebook...@googlegroups.com><mailto:standardebook...@googlegroups.com <mailto:standardebook...@googlegroups.com>>.

>>>>>>> To view this discussion on the web

>>>>>>> visithttps://groups.google.com/d/msgid/standardebooks/e3733966-57e4-45d5-9302-c0177c229b18n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/e3733966-57e4-45d5-9302-c0177c229b18n%40googlegroups.com><https://groups.google.com/d/msgid/standardebooks/e3733966-57e4-45d5-9302-c0177c229b18n%40googlegroups.com?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/e3733966-57e4-45d5-9302-c0177c229b18n%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 tostandardeboo...@googlegroups.com
>>>>>> <mailto:standardebook...@googlegroups.com><mailto:standardebook...@googlegroups.com <mailto:standardebook...@googlegroups.com>>.

>>>>>> To view this discussion on the web

>>>>>> visithttps://groups.google.com/d/msgid/standardebooks/FF2C5E14-C714-4CDE-8C82-8E96EA854745%40tinkham.org <https://groups.google.com/d/msgid/standardebooks/FF2C5E14-C714-4CDE-8C82-8E96EA854745%40tinkham.org><https://groups.google.com/d/msgid/standardebooks/FF2C5E14-C714-4CDE-8C82-8E96EA854745%40tinkham.org?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/FF2C5E14-C714-4CDE-8C82-8E96EA854745%40tinkham.org?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 tostandardeboo...@googlegroups.com
>>>>> <mailto:standardebook...@googlegroups.com><mailto:standardebook...@googlegroups.com <mailto:standardebook...@googlegroups.com>>.

>>>>> To view this discussion on the web

>>>>> visithttps://groups.google.com/d/msgid/standardebooks/382A7A00-C1B7-45CD-A39D-C094F92C01A6%40reala.net <https://groups.google.com/d/msgid/standardebooks/382A7A00-C1B7-45CD-A39D-C094F92C01A6%40reala.net><https://groups.google.com/d/msgid/standardebooks/382A7A00-C1B7-45CD-A39D-C094F92C01A6%40reala.net?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/382A7A00-C1B7-45CD-A39D-C094F92C01A6%40reala.net?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 tostandardeboo...@googlegroups.com

>>>> <mailto:standardebook...@googlegroups.com>.
>>>> To view this discussion on the web

>>>> visithttps://groups.google.com/d/msgid/standardebooks/6150c266-6e27-d55b-4ea7-5d8a4c906594%40standardebooks.org <https://groups.google.com/d/msgid/standardebooks/6150c266-6e27-d55b-4ea7-5d8a4c906594%40standardebooks.org>.

>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Standard Ebooks" group.
>>> To unsubscribe from this group and stop receiving emails from it,
>>> send an email to standardebook...@googlegroups.com
>>> <mailto:standardebook...@googlegroups.com>.
>>> To view this discussion on the web visit

>>> https://groups.google.com/d/msgid/standardebooks/132E26DF-431F-45F1-BDBE-EDC63A2DCFF9%40tinkham.org <https://groups.google.com/d/msgid/standardebooks/132E26DF-431F-45F1-BDBE-EDC63A2DCFF9%40tinkham.org?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 on the web visit

>> https://groups.google.com/d/msgid/standardebooks/34677364-3B7E-4947-89B5-CFDCEFE47C22%40tinkham.org <https://groups.google.com/d/msgid/standardebooks/34677364-3B7E-4947-89B5-CFDCEFE47C22%40tinkham.org?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 on the web visit

> https://groups.google.com/d/msgid/standardebooks/8905E012-E8DB-4EE9-80AA-7B5C7A2EAD24%40reala.net <https://groups.google.com/d/msgid/standardebooks/8905E012-E8DB-4EE9-80AA-7B5C7A2EAD24%40reala.net?utm_medium=email&utm_source=footer>.