[First Project] The Adventures of Sally (?)

[Systemchalk]

I noticed that The Adventures of Sally by P.G. Wodehouse is listed as a first project option, but that it has been the subject of two threads already.

If this project is available (and still suitable as a first project) I would be happy to take it on. If not, I do have an alternative I can submit as a separate thread.

[Alex Cabal]

Yes, you can definitely work on that.

Please see the previous threads for introductory information and any
gotchas.

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 visit
> https://groups.google.com/d/msgid/standardebooks/45c63d2d-fc23-4a79-a828-9aba366aaf62n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/45c63d2d-fc23-4a79-a828-9aba366aaf62n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Systemchalk]

Thanks for the resources.

The GitHub is up with the first three commits at: GitHub - systemchalk/p-g-wodehouse_the-adventures-of-sally

I've had very little experience with markdown so I'm sure I'll benefit from a re-read of the style manual and send a flurry of questions. That said, the instructions have been straightforward to follow and I do have the 'guide to the guide' to fall back on.

[Alex Cabal]

Fortunately we don't use markdown anywhere in the process!

Robin will be managing this project with Weijia reviewing.

On 12/29/24 11:12 AM, Systemchalk wrote:
> Thanks for the resources.
>
> The GitHub is up with the first three commits at: GitHub -
> systemchalk/p-g-wodehouse_the-adventures-of-sally

> <https://github.com/systemchalk/p-g-wodehouse_the-adventures-of-sally>

>
> I've had very little experience with markdown so I'm sure I'll benefit
> from a re-read of the style manual and send a flurry of questions. That
> said, the instructions have been straightforward to follow and I do have
> the 'guide to the guide' to fall back on.
>
> On Friday, December 27, 2024 at 2:13:45 PM UTC-5 Alex Cabal wrote:
>
> Yes, you can definitely work on that.
>
> Please see the previous threads for introductory information and any
> gotchas.
>
> 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>

>
> 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 12/26/24 10:10 PM, Systemchalk wrote:
> > I noticed that The Adventures of Sally by P.G. Wodehouse is
> listed as a
> > first project option, but that it has been the subject of two
> threads
> > already.
> >
> > If this project is available (and still suitable as a first
> project) I
> > would be happy to take it on. If not, I do have an alternative I can
> > submit as a separate thread.
> >
> > --
> > 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/45c63d2d-fc23-4a79-a828-9aba366aaf62n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/45c63d2d-fc23-4a79-a828-9aba366aaf62n%40googlegroups.com> <https://groups.google.com/d/msgid/standardebooks/45c63d2d-fc23-4a79-a828-9aba366aaf62n%40googlegroups.com?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/45c63d2d-fc23-4a79-a828-9aba366aaf62n%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/0c8b3b7f-f3cd-4143-9c6a-f43ae6821e3bn%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/0c8b3b7f-f3cd-4143-9c6a-f43ae6821e3bn%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Weijia Cheng]

Review noted.

[Systemchalk]

Hey folks. I thought I should give an account for my lack of comments/progress. This is a purely weekends project and sadly I have been sick for the last two and so have been held up at the symanticate step. I hope to be on track next weekend at the latest (though I'll try to sneak in some time on Tuesday or Thursday). No questions that weren't handled by the documentation yet but I suspect there will be a couple of formatting choices from the scan that I'll flag for comment once I implement them.

[Weijia Cheng]

That is no problem. Just be aware that if this goes by for many months without progress, it might be marked as abandoned and someone else could claim this book to work on.

[Systemchalk]

Thank you for the understanding. I made a bit of progress tonight and had some questions but they didn't seem to get added to the thread. I'll try to remember them here (but apologies if this winds up being a double post).

A few questions from the work I've done so far:

1) The reference copy on Internet Archive includes a dedication that is not included in the PG source text. I would be inclined to include it in the ebook since it's written by P. G. Wodehouse, but I'm trying to follow the guide quite strictly, and I figure this can easily be added at the end of the work anyway.

2) The standard is quite clear that chapters are only given roman numerals without the chapter name (unless it's a stylistic choice). As such, I have not included the preceding 'chapter' as found in the reference copy on Internet Archive, but was wondering if the inclusion of sub-chapters would justify the inclusion of 'Chapter' for clarity. Right now I'm not including them, but I figure I'd mark cases where I'm conflicting with the reference.

3) There's quite a bit of French in the text which in the reference is often italicized. However, by the standard, most of these instances are found in the Mirriam-Webster dictionary and so I have marked them with <span> instead of <i> (and the language tag). For example, in Chapter 2, Sub-chapter 1 (4th paragraph), it refers to the "Roville plage" but Mirriam-Webster does define this. Where I may be going astray as to what constitues a "basic online search result." Quite a number of these instances are found in the dictionary and so I have generally found myself using <span> more than I would have expected to use <i> which is the reason why I think I might be misinterpreting the guidance.

I have commited the manual semantic work for the first three chapters to the repository. I'm most likely to be free to work on this next weekend and will be happy to incorporate any guidance or corrections for these preliminary sections or in response to these questions.

[Robin Whittleton]

1. I think we should include that. Read the guidelines for dedications: https://standardebooks.org/manual/1.8.1/single-page#7.3. As this is frontmatter we’ll need a halftitlepage to go between that and the bodymatter too: https://standardebooks.org/manual/1.8.1/single-page#6.5. I’d recommend doing it now rather than later, as you’ll need to run all the future steps against it. Come back if you need additional info on this.
2. No, you can omit the word chapter, even for subchapters.
3. plage is fine as is. I wouldn’t even mark them up with a span, as if they’re in MW we consider them adopted into English at this point.

-Robin

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/8bca99a7-0369-4de7-acc5-d166996116ddn%40googlegroups.com.

[Systemchalk]

Hello! I have some much belated updates to this which have (mostly) been added to the repo. I have a follow up question and then a couple of new items that have come up over the course of adding the chapters.

To (1): Thank you for these links. I think I'm still uncertain on adding this in because the tools have done a good job of providing all the tags at the top. I used the Gulliver's Travels source as a point of reference just because I know that book has some front matter (although not explicitly a letter) and I tried to exercise some judgement from the source material as well as the other sections regarding letters. That said, I can see a few areas where I have gone astray.
a. The title itself is stylized in all caps with one word on each line, and I don't know how much of a purist to be about this. So far I've treated it like an ordinary title because we're already deviating from the conventions of all capitals for the chapter titles.
b. The body and section tags are all dedication (these seemed to be present in the specification but I think it's quite likely I've misunderstood this), but this is effectively a letter and it has not been treated as a letter in the sense of getting a blockquote. This is mostly justified through the Gulliver's Travels example, but that doesn't completely cover this case because it very obviously is a dedication to a real person, George Grossmith, with all the usual elements of a letter.
c. Leaving aside the concerns in (b), one other oddity was the Garrick Club at the bottom. This seemed to be, in effect, a letter.dateline without a date, but it does appear at the end. I'm grasping onto the closest fit I could find but all instances of a letter.dateline I could find were in headers. Happy to get some guidance on how to handle this (I also didn't give it italics because I'm finding most instances of italics don't align with the SE standard and this seemed to be like the stylized dedication at the top in the sense that it wasn't essential to the meaning for this first pass).
And, of course, this is the first instance where I'm adding something completely new rather than modifying something from the standard outputs, so I imagine that increases the chance of errors that I didn't even know to check for or ask about.

The remaining questions coming from new chapters:
2. a. Chapter 4 contains a telegram and I'll confess that I found the documentation a bit confusing on this one. I started treating it as a letter, but then saw that there was a special case for telegrams involving a class which I couldn't really follow even when comparing to the segment on classes at the top. I could try and break this down into a few specific steps where I'm getting confused, but it might be easier to ask if you happen to have an example of this? I couldn't find one on an (admittedly brief) search in the repo.
b. In addition, the telegram includes a 'signature' (single initial). Assuming this is treated as a letter, is there a way I should treat a signature on the same line? 

3. Chapter 6 has an instance of onomatopoeia (well multiple instances of the same word). This may be covered in the manual and I just wasn't sure where to look, but I wasn't sure how to handle this if at all. I could use some guidance either on the relevant section or just a confirmation that it doesn't need to be handled.

[Robin Whittleton]

1a: We can just follow our imprint style here rather than trying to replicate the book exactly. What you’ve done is fine (although you don’t need the hgroup).

1b: I was going to say that you’re welcome to add z3998:letter as well, but it looks like Alex removed the same from at least one of my productions, so let’s just leave it as dedication.

1c: You can leave out the dateline semantics. I’d be tempted to just put it in the same <p> as above with a <br/> separating it, and move the sender semantics to a span? You can replicate the italics if you want with a style: we don’t have any house style on that.

(sidenote: produciton -> production)

2a: for telegrams, treat them semantically as an ordinary letter, but also add the class and the associated style from https://standardebooks.org/manual/1.8.2/single-page#7.7.2 . For an example, look at https://github.com/standardebooks/p-g-wodehouse_short-fiction/blob/master/src/epub/text/death-at-the-excelsior.xhtml#L118-L120

2b: see above example

3: can you give me an example? We don’t have anything specific for onomatopoeia, but plain written-out sounds get italics without semantics: https://standardebooks.org/manual/1.8.2/single-page#8.2.6

-Robin

To view this discussion visit https://groups.google.com/d/msgid/standardebooks/f79dfd57-cdc5-4751-9eb3-509c993f4e5en%40googlegroups.com.

[Systemchalk]

Thanks for the follow up and catching the error in the dedication.

Regarding 3, I lost my note for this but I was almost certainly referring to the "Tiddly-omty-om" on page 105 in the source book (line 98 in chapter-6.xhtml in the files). I kind of seems like it falls under sound, but maybe not as clear as the usual suspects like 'poof'.

I think that's what I need so far. I either have or will quickly implement the remaining points. I suspect I'll have some follow up because the next few chapters have a bunch of signs and posters, but where I can I try to see if there's a clear rule in the manual and then just collect the ones I was uncertain about into one of these messages.

[Robin Whittleton]

Nonsense words don’t get italicised, just things that are specifically representing sounds. Let’s leave it as is.

-Robin

To view this discussion visit https://groups.google.com/d/msgid/standardebooks/75d7439c-daf1-416d-93ae-675d6a84779an%40googlegroups.com.

[Systemchalk]

Hello.

I ran in to a small difficulty in Chapter 11 as there is an extended letter. Only part of it is treated with special typing, but given that it was technically a letter I encased it with the  letter tagging. I have a suspicion though that this might make for odd formatting in the final product, so I wanted to check in before committing too much else so  I could make a simple adjustment. The section is in: https://github.com/systemchalk/p-g-wodehouse_the-adventures-of-sally/blob/main/src/epub/text/chapter-11.xhtml

[Robin Whittleton]

Yes, this is the correct approach. The scans take the unusual approach of centring and italicising the first blockquote: I think we might want to do that to with a custom CSS rule (blockquote:first-of-type, etc).

Looking at your code there are a few more semantic annotations you’d want to add to the letter: recipient, validiction, a footer, etc. Have a read through https://standardebooks.org/manual/1.8.4/single-page#7.7. Also, we don’t do all-caps signatures, so you can convert SALLY to Sally and add appropriate CSS: https://standardebooks.org/manual/1.8.4/single-page#7.7.4.4

-Robin

To view this discussion visit https://groups.google.com/d/msgid/standardebooks/fc292857-20ea-4f55-9366-6eff77774173n%40googlegroups.com.

[Systemchalk]

Thanks for this guidance Robin. I suspect I’m going to need another crack at this but I tried to implement the recommended changes from what you wrote and the guidelines in 7.7. There are a few lingering questions which might be good before moving on to another section:

1. Is the custom CSS something that should be done before moving ahead? I suspect this will be something I need to dedicate some time to, but I’m happy to work on (I’m currently travelling and so everything has been done directly in GitHub which isn’t a deal breaker, but it does make side by side comparisons more of a challenge).

2. I think the proper CSS referred to when converting was the additional semantic annotations. Letting the all caps SALLY was a straight up mistake on my part (I know that’s one the style guide strongly comments against), but I wanted to make sure I wasn’t missing a proper marking to capitalize (although that might be the function of the <b>?).

3. The one correction I think I’ll need to make is adding the recipient marking to Ginger in the body of the document. I was a little unclear on what kind of marking it gets (span or b or whatever), as well as the overall logic for marking the recipient outside of the salutation is (you specifically mentioned sender and it’s mentioned in the style guide so I absolutely acknowledge it’s there, it’s just not quite clear to me what purpose it’s serving).

I’m sure there will be more, but this seems like a really good case to get right as I believe there are some extended sections of letters and at least one more telegram coming up.

[Alex Cabal]

Robin, thoughts?

> page#7.7 <https://standardebooks.org/manual/1.8.4/single-page#7.7>.

> Also, we don’t do all-caps signatures, so you can convert SALLY to
> Sally and add appropriate CSS: https://standardebooks.org/

> manual/1.8.4/single-page#7.7.4.4 <https://standardebooks.org/
> manual/1.8.4/single-page#7.7.4.4>

>
> -Robin
>
>> On 9 Aug 2025, at 23:23, Systemchalk <syste...@gmail.com> wrote:
>>
>> Hello.
>>
>> I ran in to a small difficulty in Chapter 11 as there is an
>> extended letter. Only part of it is treated with special typing,
>> but given that it was technically a letter I encased it with the
>> letter tagging. I have a suspicion though that this might make for
>> odd formatting in the final product, so I wanted to check in
>> before committing too much else so  I could make a simple
>> adjustment. The section is in: https://github.com/systemchalk/p-g-
>> wodehouse_the-adventures-of-sally/blob/main/src/epub/text/

>> chapter-11.xhtml <https://github.com/systemchalk/p-g-
>> wodehouse_the-adventures-of-sally/blob/main/src/epub/text/
>> chapter-11.xhtml>

>>
>> On Sunday, May 25, 2025 at 5:57:54 AM UTC-4 robin wrote:
>>
>> Nonsense words don’t get italicised, just things that are
>> specifically representing sounds. Let’s leave it as is.
>>
>> -Robin
>>
>>> On 24 May 2025, at 20:58, Systemchalk <syste...@gmail.com> wrote:
>>>
>>> Thanks for the follow up and catching the error in the
>>> dedication.
>>>
>>> Regarding 3, I lost my note for this but I was almost
>>> certainly referring to the "Tiddly-omty-om" on page 105 in
>>> the source book (line 98 in chapter-6.xhtml in the files). I
>>> kind of seems like it falls under sound, but maybe not as
>>> clear as the usual suspects like 'poof'.
>>>
>>> I think that's what I need so far. I either have or will
>>> quickly implement the remaining points. I suspect I'll have
>>> some follow up because the next few chapters have a bunch of
>>> signs and posters, but where I can I try to see if there's a
>>> clear rule in the manual and then just collect the ones I was
>>> uncertain about into one of these messages.
>>> On Monday, May 12, 2025 at 3:05:05 PM UTC-4 robin wrote:
>>>
>>> 1a: We can just follow our imprint style here rather than
>>> trying to replicate the book exactly. What you’ve done is
>>> fine (although you don’t need the hgroup).
>>>
>>> 1b: I was going to say that you’re welcome to add
>>> z3998:letter as well, but it looks like Alex removed the

>>> same from at least one of my productions <https://
>>> github.com/standardebooks/compton-mackenzie_sinister-
>>> street/commit/39d892547a8911f9e10732753930ebe887234e7e>,

>>> so let’s just leave it as dedication.
>>>
>>> 1c: You can leave out the dateline semantics. I’d be
>>> tempted to just put it in the same <p> as above with a
>>> <br/> separating it, and move the sender semantics to a
>>> span? You can replicate the italics if you want with a
>>> style: we don’t have any house style on that.
>>>
>>> (sidenote: produciton -> production)
>>>
>>> 2a: for telegrams, treat them semantically as an ordinary
>>> letter, but also add the class and the associated style
>>> from https://standardebooks.org/manual/1.8.2/single-

>>> page#7.7.2 <https://standardebooks.org/manual/1.8.2/
>>> single-page#7.7.2> . For an example, look at https://
>>> github.com/standardebooks/p-g-wodehouse_short-fiction/
>>> blob/master/src/epub/text/death-at-the-
>>> excelsior.xhtml#L118-L120 <https://github.com/
>>> standardebooks/p-g-wodehouse_short-fiction/blob/master/
>>> src/epub/text/death-at-the-excelsior.xhtml#L118-L120>

>>>> 1. I think we should include that. Read the

>>>> guidelines for dedications: https://
>>>> standardebooks.org/manual/1.8.1/single-page#7.3

>>>> <https://standardebooks.org/manual/1.8.1/single-
>>>> page#7.3>. As this is frontmatter we’ll need a

>>>> halftitlepage to go between that and the
>>>> bodymatter too: https://standardebooks.org/

>>>> manual/1.8.1/single-page#6.5 <https://
>>>> standardebooks.org/manual/1.8.1/single-
>>>> page#6.5>. I’d recommend doing it now rather

>>>> than later, as you’ll need to run all the future
>>>> steps against it. Come back if you need
>>>> additional info on this.

>>>> 2. No, you can omit the word chapter, even for
>>>> subchapters.
>>>> 3. plage is fine as is. I wouldn’t even mark them

>>>> up with a span, as if they’re in MW we consider
>>>> them adopted into English at this point.
>>>>
>>>>
>>>> -Robin
>>>>
>>>>> On 3 Feb 2025, at 03:15, Systemchalk

>>>>> paragraph), it refers to the "Roville/plage/" but

>>>>> Mirriam-Webster does define this. Where I may be
>>>>> going astray as to what constitues a "basic online
>>>>> search result." Quite a number of these instances
>>>>> are found in the dictionary and so I have generally
>>>>> found myself using <span> more than I would have
>>>>> expected to use <i> which is the reason why I think
>>>>> I might be misinterpreting the guidance.
>>>>>
>>>>> I have commited the manual semantic work for the
>>>>> first three chapters to the repository. I'm most
>>>>> likely to be free to work on this next weekend and
>>>>> will be happy to incorporate any guidance or
>>>>> corrections for these preliminary sections or in
>>>>> response to these questions.
>>>>> On Sunday, January 12, 2025 at 10:39:41 PM UTC-5

>>>>> weijia...@gmail.com <http://gmail.com/>wrote:

>>>>>
>>>>> That is no problem. Just be aware that if this
>>>>> goes by for many months without progress, it
>>>>> might be marked as abandoned and someone else
>>>>> could claim this book to work on.
>>>>>
>>>>> On Sunday, January 12, 2025 at 8:26:36 PM UTC-5
>>>>> Systemchalk wrote:
>>>>>
>>>>> Hey folks. I thought I should give an
>>>>> account for my lack of comments/progress.
>>>>> This is a purely weekends project and sadly
>>>>> I have been sick for the last two and so
>>>>> have been held up at the symanticate step.
>>>>> I hope to be on track next weekend at the
>>>>> latest (though I'll try to sneak in some
>>>>> time on Tuesday or Thursday). No questions
>>>>> that weren't handled by the documentation
>>>>> yet but I suspect there will be a couple of
>>>>> formatting choices from the scan that I'll
>>>>> flag for comment once I implement them.
>>>>>
>>>>> On Sunday, December 29, 2024 at 5:10:48 PM

>>>>> UTC-5weijia...@gmail.com <http://gmail.com/

>>>>> >wrote:
>>>>>
>>>>> Review noted.
>>>>>
>>>>> On Sunday, December 29, 2024 at
>>>>> 3:04:42 PM UTC-5 Alex Cabal wrote:
>>>>>
>>>>> Fortunately we don't use markdown
>>>>> anywhere in the process!
>>>>>
>>>>> Robin will be managing this project
>>>>> with Weijia reviewing.
>>>>>
>>>>> On 12/29/24 11:12 AM, Systemchalk
>>>>> wrote:
>>>>> > Thanks for the resources.
>>>>> >
>>>>> > The GitHub is up with the first
>>>>> three commits at: GitHub -
>>>>> > systemchalk/p-g-wodehouse_the-
>>>>> adventures-of-sally
>>>>> > <https://github.com/systemchalk/
>>>>> p-g-wodehouse_the-adventures-of-

>>>>> sally <https://github.com/
>>>>> systemchalk/p-g-wodehouse_the-

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

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

>>>>> > > To view this discussion visit
>>>>> > >
>>>>> >https://groups.google.com/d/msgid/
>>>>> standardebooks/45c63d2d-fc23-4a79-

>>>>> a828-9aba366aaf62n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/45c63d2d-fc23-4a79-a828-9aba366aaf62n%40googlegroups.com><https://groups.google.com/d/msgid/standardebooks/45c63d2d-fc23-4a79-a828-9aba366aaf62n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/45c63d2d-fc23-4a79-a828-9aba366aaf62n%40googlegroups.com>> <https://groups.google.com/d/msgid/standardebooks/45c63d2d-fc23-4a79-a828-9aba366aaf62n%40googlegroups.com?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/45c63d2d-fc23-4a79-a828-9aba366aaf62n%40googlegroups.com?utm_medium=email&utm_source=footer><https://groups.google.com/d/msgid/standardebooks/45c63d2d-fc23-4a79-a828-9aba366aaf62n%40googlegroups.com?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/45c63d2d-fc23-4a79-a828-9aba366aaf62n%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 visit
>>>>> >https://groups.google.com/d/msgid/

>>>>> standardebooks/0c8b3b7f-
>>>>> f3cd-4143-9c6a-
>>>>> f43ae6821e3bn%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/
>>>>> standardebooks/0c8b3b7f-
>>>>> f3cd-4143-9c6a-
>>>>> f43ae6821e3bn%40googlegroups.com><https://groups.google.com/d/msgid/standardebooks/0c8b3b7f-f3cd-4143-9c6a-f43ae6821e3bn%40googlegroups.com?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/0c8b3b7f-f3cd-4143-9c6a-f43ae6821e3bn%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 visithttps://
>>>>> groups.google.com/d/msgid/

>>>>> standardebooks/8bca99a7-0369-4de7-acc5-
>>>>> d166996116ddn%40googlegroups.com <https://
>>>>> groups.google.com/d/msgid/
>>>>> standardebooks/8bca99a7-0369-4de7-acc5-
>>>>> d166996116ddn%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 visithttps://groups.google.com/
>>>> d/msgid/standardebooks/f79dfd57-
>>>> cdc5-4751-9eb3-509c993f4e5en%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/standardebooks/
>>>> f79dfd57-
>>>> cdc5-4751-9eb3-509c993f4e5en%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 visithttps://groups.google.com/d/
>>> msgid/standardebooks/75d7439c-
>>> daf1-416d-93ae-675d6a84779an%40googlegroups.com <https://
>>> groups.google.com/d/msgid/standardebooks/75d7439c-
>>> daf1-416d-93ae-675d6a84779an%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 visit https://groups.google.com/d/msgid/
>> standardebooks/

>> fc292857-20ea-4f55-9366-6eff77774173n%40googlegroups.com <https://
>> groups.google.com/d/msgid/standardebooks/
>> fc292857-20ea-4f55-9366-6eff77774173n%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/f7dd674c-a60b-418e-aa3c-ab15ef8ef7f6n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/f7dd674c-a60b-418e-
> aa3c-ab15ef8ef7f6n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Robin Whittleton]

1. That can be done later, sure. Will be painful to do in GitHub’s interface I think.

2. <b> will do small caps, yep.

3. Re-reading SEMOS, I realised that I’d been getting this wrong myself: we don’t mark up the recipient if it’s in a salutation: https://standardebooks.org/manual/1.8.4/single-page#7.7.3.8 . So nothing for you to do here.

-Robin

To view this discussion visit https://groups.google.com/d/msgid/standardebooks/f7dd674c-a60b-418e-aa3c-ab15ef8ef7f6n%40googlegroups.com.