First Production: Sailing Alone Around The World, Joshua Slocum

[Brett Roper]

Hi,

I'd like to do this famous sailing memoir from the first person to sail single handed around the world.

https://en.wikipedia.org/wiki/Sailing_Alone_Around_the_World

There's a scan at the internet archive here: https://archive.org/details/sailingalonearo01slocgoog

Does this seem appropriate?

Thanks, Brett

[Alex Cabal]

Sure, you could start on that one.

Usually we cut decorative illustrations, which I would say *most* of the
ones in this book are. However there are some ones directly relevant to
the book which I think we should keep, namely the charts and maps. So
keep those but cut the rest.

The transcription removed bridgehead styling, so make sure to restore
that to the opening line of each chapter.

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/8138b8e3-5136-4a7b-b538-e3610dc29c06n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/8138b8e3-5136-4a7b-b538-e3610dc29c06n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Brett Roper]

Thank you for the guidance and encouragement.

My GitHub repo is https://github.com/eggplantpasta/joshua-slocum_sailing-alone-around-the-world based on the PG source https://www.gutenberg.org/ebooks/6317.

There won't be much updated for a bit as I read through the homework you've set me :) .

I'll do the illustration light version for inclusion in the collection but might consider forking my own version to so I can have pretty pictures on my Kindle while at anchor.

Cheers, Brett

[Alex Cabal]

David can you manage this with Vince reviewing?

On 2/9/24 1:50 AM, Brett Roper wrote:
> Thank you for the guidance and encouragement.
>
> My GitHub repo
> is https://github.com/eggplantpasta/joshua-slocum_sailing-alone-around-the-world based on the PG source https://www.gutenberg.org/ebooks/6317.
>
> There won't be much updated for a bit as I read through the homework
> you've set me :) .
>
> I'll do the illustration light version for inclusion in the collection
> but might consider forking my own version to so I can have pretty
> pictures on my Kindle while at anchor.
>
> Cheers, Brett
>
> On Thursday 8 February 2024 at 11:36:53 pm UTC+8 Alex Cabal wrote:
>
> Sure, you could start on that one.
>
> Usually we cut decorative illustrations, which I would say *most* of
> the
> ones in this book are. However there are some ones directly relevant to
> the book which I think we should keep, namely the charts and maps. So
> keep those but cut the rest.
>
> The transcription removed bridgehead styling, so make sure to restore
> that to the opening line of each chapter.
>
> 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/8138b8e3-5136-4a7b-b538-e3610dc29c06n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/8138b8e3-5136-4a7b-b538-e3610dc29c06n%40googlegroups.com> <https://groups.google.com/d/msgid/standardebooks/8138b8e3-5136-4a7b-b538-e3610dc29c06n%40googlegroups.com?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/8138b8e3-5136-4a7b-b538-e3610dc29c06n%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/d3c87513-71b7-451a-83ee-eaa77375be17n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/d3c87513-71b7-451a-83ee-eaa77375be17n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Alex Cabal]

Also note that these images should be converted to SVG, this guide will
help though yours will only be one color:
https://standardebooks.test/contribute/how-tos/how-to-create-svgs-from-maps-with-several-colors

On 2/9/24 1:50 AM, Brett Roper wrote:

> Thank you for the guidance and encouragement.
>
> My GitHub repo
> is https://github.com/eggplantpasta/joshua-slocum_sailing-alone-around-the-world based on the PG source https://www.gutenberg.org/ebooks/6317.
>
> There won't be much updated for a bit as I read through the homework
> you've set me :) .
>
> I'll do the illustration light version for inclusion in the collection
> but might consider forking my own version to so I can have pretty
> pictures on my Kindle while at anchor.
>
> Cheers, Brett
>
> On Thursday 8 February 2024 at 11:36:53 pm UTC+8 Alex Cabal wrote:
>
> Sure, you could start on that one.
>
> Usually we cut decorative illustrations, which I would say *most* of
> the
> ones in this book are. However there are some ones directly relevant to
> the book which I think we should keep, namely the charts and maps. So
> keep those but cut the rest.
>
> The transcription removed bridgehead styling, so make sure to restore
> that to the opening line of each chapter.
>
> 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/8138b8e3-5136-4a7b-b538-e3610dc29c06n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/8138b8e3-5136-4a7b-b538-e3610dc29c06n%40googlegroups.com> <https://groups.google.com/d/msgid/standardebooks/8138b8e3-5136-4a7b-b538-e3610dc29c06n%40googlegroups.com?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/standardebooks/8138b8e3-5136-4a7b-b538-e3610dc29c06n%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/d3c87513-71b7-451a-83ee-eaa77375be17n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/d3c87513-71b7-451a-83ee-eaa77375be17n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[David]

I can manage. 

Those SVGs may be challenging, but the guide Alex already linked to should be a big help.

David / Fife, UK

[David]

And I just noticed that link was to a "test" server :) Not that it would occasion much confusion, but here's a working link:

https://standardebooks.org/contribute/how-tos/how-to-create-svgs-from-maps-with-several-colors

D.

[Alex Cabal]

Oops, I usually copy and paste from my browser history which has the
test site, and I forget to check the tld!

> https://standardebooks.test/contribute/how-tos/how-to-create-svgs-from-maps-with-several-colors <https://standardebooks.test/contribute/how-tos/how-to-create-svgs-from-maps-with-several-colors>

>
> --
> 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/b7ef047b-d0d2-4c7c-a28d-cb785624d952n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/b7ef047b-d0d2-4c7c-a28d-cb785624d952n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Brett Roper]

Hi,

re: capitalisation

I've started and have my first question. I'n the passage below the capitalisation appears is transcribed as it appears in the book. I'm assuming it is copying how the dedication was capitalised in the original handwriting? Should I keep it or not?

<p>Following the subject of voyages, she gave me the four beautiful volumes of sailing directories for the Mediterranean, writing on the fly-leaf of the first:</p>
<p>To CAPTAIN SLOCUM. These volumes have been read and re-read many times by my husband, and I am very sure that he would be pleased that they should be passed on to the sort of seafaring man that he liked above all others. FANNY V. DE G. STEVENSON.</p>

I have kept other capitalisation elsewhere where it was transcribing a plaque.

Cheers, Brett

[Brett Roper]

Hi,

Taking a break from committing changes to browse some art. Would this be appropriate for my cover?

https://thegriggs.org/gallery/la-mer-orageuse-gustave-courbet/

Cheers, Brett - Perth, Australia

[Brett Roper]

Hi again,

I've just committed my removal of the decorative illustrations. This book works quite well without them - but some books like Pooh are famous for them. I was wondering if someone could point me to the mailing list link of where this rule was debated. I'm just curious.

Thanks, Brett.

[Vince]

It’s been discussed multiple times, but the most recent extended discussion I think was towards the end of the Winnie the Pooh thread.

[David]

It helps to see these things in context - and in this case, it looks like a hand-written inscription is being conformed to typesetting standards.

To my eye, that section would go in a simple blockquote (it's not a letter or poem, so no further semantic markup is needed for the blockquote itself). The capitalized bits should be marked up like a salutation (with `b` span), and footer + signature (with the necessary CSS rules copied into local.css).

For other capitalization, like the plaques you note, do refer to SEMoS § 8.3 on this if you haven't already. :)

[David]

Hi again - that certainly works, and I've added it to the artworks database.

I expect you'll want your crop for the cover to include the wee sailboat at the horizon line on the right, much as David Griggs's mockup does (it wouldn't hurt to post your own mock-up here for checking before committing, actually).

@ Alex - I see the database has 1871 for Gustave Courbet's year of death, but his Wikipedia entry (and other authorities I've checked) give 1877. I don't think there are two "Gustave Courbets", are there? Hopefully we can correct these in the db.

[David]

P.s. I should have been explicit in my earlier note on capitalization: the text of "To CAPTAIN SLOCUM" and "FANNY V. DE G. STEVENSON" should be in regular case in your code, of course.

D.

[David]

And just to save you hunting, if you start with this post in that thread, the numerous responses below it are the relevant ones.

D.

[Brett Roper]

Thanks to the link to the discussion David and Vince. The logic behind the images decision seems to make sense for this project.

Thanks for the pointer to the style manual and the suggestion of how to proceed on the capitalisation David. I promise I did my homework and read the manual start to end before starting but I'm not totally familiar with it yet :).

Thanks also  for the decision on the cover. I'll commit the source image but won't get distracted until I have the words under control.

I'm having fun.

[Alex Cabal]

Thanks, I've fixed his death year

On 2/12/24 2:55 AM, David wrote:
> Hi again - that certainly works, and I've added it to the artworks database.
>
> I expect you'll want your crop for the cover to include the wee sailboat
> at the horizon line on the right, much as David Griggs's mockup does (it
> wouldn't hurt to post your own mock-up here for checking before
> committing, actually).
>
> @ Alex - I see the database has 1871 for Gustave Courbet's year of
> death, but his Wikipedia entry

> <https://en.wikipedia.org/wiki/Gustave_Courbet> (and other authorities
> <http://id.loc.gov/authorities/names/n80057228> I've checked) give 1877.

> I don't think there are two "Gustave Courbets", are there? Hopefully we
> can correct these in the db.
>
> On Monday 12 February 2024 at 06:24:13 UTC Brett wrote:
>
> Hi,
>
> Taking a break from committing changes to browse some art. Would
> this be appropriate for my cover?
>
> https://thegriggs.org/gallery/la-mer-orageuse-gustave-courbet/
> <https://thegriggs.org/gallery/la-mer-orageuse-gustave-courbet/>
>
> Cheers, Brett - Perth, Australia
>

> --
> 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/dbea6141-17c5-4b93-9647-5e7a4f6f1d20n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/dbea6141-17c5-4b93-9647-5e7a4f6f1d20n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Brett Roper]

Today has been a good day. 736 lint errors reduced to 219.

[David]

That's a lot of fixes! I'm wondering, too, why you might have had quite so many lint issues to deal with?

Just taking a quick look at your repo, you've got some, ahhh, "features" I normally wouldn't expect to see (although I don't think these would occasion your lint errors, assuming you're running your `se command` from the correct directory).

I wouldn't expect to see pdf source stored, nor would I expect that the main ebook files would be moved to a subdirectory in the repo. Also, I can see why you might have thought that use of "README" is a help — I keep all that sort of thing in a gist for each project. That should keep the project repo "clean".

And just a word about commit messages (this was something I needed tutoring in!): it's a significant help for the review process to have meaningful commit messages with pretty much one "kind" of thing per commit. Like the Step-by-step guide says in the guidance directly above the ToC, "Commits are easy and free—it’s perfectly acceptable to have many very small commits, as long as each one is a single logical unit of work and doesn’t mix editorial and non-editorial changes."

Now when I'm dealing with lint fixes, I try to group things related to semantics, typography, layout, typo-fixes, etc., each into their own commit. Not so easy when you have so many to deal with, but worth the attempt to help your reviewer!

Sorry for the lengthy missive, but I hope it's a help as you make progress with this project -

David / Fife, UK

[Alex Cabal]

Very good points. Note that the ebook repo should not be a workspace to
commit scratch files or reorganize. Our ebooks have a set internal
structure and you shouldn't deviate from that, including adding
unexpected files.

On 2/14/24 2:39 AM, David wrote:
> That's a lot of fixes! I'm wondering, too, why you might have had quite
> so many lint issues to deal with?
>
> Just taking a quick look at your repo, you've got some, ahhh, "features"
> I normally wouldn't expect to see (although I don't think these would
> occasion your lint errors, assuming you're running your `se command`
> from the correct directory).
>
> I wouldn't expect to see pdf source stored, nor would I expect that the
> main ebook files would be moved to a subdirectory in the repo. Also, I
> can see why you might have thought that use of "README" is a help — I
> keep all that sort of thing in a gist

> <https://gist.github.com/dajare/f30f4be78c50d7a56485254a38adff1d> for

> each project. That should keep the project repo "clean".
>
> And just a word about commit messages (this was something I needed
> tutoring in!): it's a significant help for the review process to have
> meaningful commit messages with pretty much one "kind" of thing per
> commit. Like the Step-by-step guide says in the guidance directly above
> the ToC

> <https://standardebooks.org/contribute/producing-an-ebook-step-by-step#toc>, "Commits are easy and free—it’s perfectly acceptable to have many very small commits, as long as each one is a single logical unit of work and doesn’t mix editorial and non-editorial changes."

>
> Now when I'm dealing with lint fixes, I try to group things related to
> semantics, typography, layout, typo-fixes, etc., each into their own
> commit. Not so easy when you have so many to deal with, but worth the
> attempt to help your reviewer!
>
> Sorry for the lengthy missive, but I hope it's a help as you make
> progress with this project -
>
> David / Fife, UK
>
> On Wednesday 14 February 2024 at 05:01:06 UTC Brett wrote:
>
> Today has been a good day. 736 lint errors reduced to 219.
>

> --
> 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/773892fb-cbbe-4cbf-9998-9cd771ff04c8n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/773892fb-cbbe-4cbf-9998-9cd771ff04c8n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Brett Roper]

Hi Alex and David,

Thanks for the input.

Firstly I counted wrong. Oops!

I used "se lint . | wc -l / 3" rather than the slightly more accurate "se lint . | grep "├" | wc -l". I did consider adding a --count flag to the tool but I didn't want to get distracted programming :).

So the correct(ish) count before cleaning, typogrifying, and linting (just after the split chapter commit) is 2109! After all my changes I have it down to 157.

I think the huge amount of initial lint errors are due to the Gutenberg HTML being from 2004 with tonnes of inline styles etc.

Now to the repository. I have renamed the old repo and started again from scratch applying the relevant commits one at a time to a new repo. The comments are hopefully now clearer (although longer than best practice suggests) They were mostly single purpose commits although I did see the opportunity to split one of them into 2 sorts of changes. The new repository conforms to the SE standard - I hope that is ok now.

I need to keep my working folder in a repo as I work on 2 computers and one of them (the raspberry pi) is mostly used offline (hence the local PDF source). The subdirectory for the source was so the tool worked without bombing out on the PDF. That repo is now separate to the one you guys are interested in.

https://github.com/eggplantpasta/joshua-slocum_sailing-alone-around-the-world.git

I hope the reorganising work I put in this morning is ok. I'm itching to get back to production.

Cheers, Brett.

[David]

That "re-organized" repo looks much more recognizable - thanks! :)

I've found that by slavishly following the step-by-step guide, things do unfold nicely. In particular, all the PG cruft you mention gets dealt with either at step 6 ("rough clean") before split, or as a tidy up operation after split (at step 8, "clean up"). That would remove all the markup around illustrations (you have some you're keeping, I know), "inline" styles, drop-caps, small-caps, etc., etc.

But it looks like you're gathering some good momentum now. Sticking as closely as possible to the "script" (= Step-by-step guide) should keep you right moving forward. Glad you're enjoying the project so far!

David

[David]

Sorry! One more thing I meant to say about following the Steps closely: there's no point running `se lint` until you're at Step 21, "Clean and lint". There is such a thing as using that tool too soon... ;-)

Hope that helps! D.

[Brett Roper]

Hi,

Small question. I've just been through rationalising <i> tags by adding xml:lang or removing or changing to <em>. I found a word in italics kpeting (crab)  that is from when he was in the cocos and keeling islands where they speak Malay the issue is that Google couldn't find a translation of it so I couldn't confirm that it is a Malay word. I did add a xml:lang="ms" based on where he was. Was that the correct thing to do?

One day after this, when I tried to haul the sloop and found her fast in the sand, the children all clapped their hands and cried that a kpeting (crab) was holding her by the keel; 

Cheers, Brett

[David]

It looks to me like an issue of how Slocum represented the word - Google Translate does have a "kepiting = crab" entry for Malay, so that looks right.

The alternative is to go with "unknown" if it seems like this is one of the local/indigenous languages, but I think it's safe to go with Malay ("ms").

D.

[Brett Roper]

Which brings up another point. Should I do an editorial change to fix the spelling kpeting => kepiting?

[David]

Hmmm... Is it a "sound-alike"? (Which is the basic criterion.) It could be, but I'm not 100% sure, and slightly complicated in that it's Malay, not English. We had best seek a higher authority.

Alex? What's your sense?

Thanks! D.

[Alex Cabal]

It's a transposed letter in a non-English language so it's probably just
a typo. You can fix it to kepiting.

On 3/1/24 2:42 AM, David wrote:
> Hmmm... Is it a "sound-alike"? (Which is the basic criterion.) It

> /could/ be, but I'm not 100% sure, and slightly complicated in that it's

> Malay, not English. We had best seek a higher authority.
>
> Alex? What's your sense?
>
> Thanks! D.
>
> On Friday 1 March 2024 at 04:44:39 UTC Brett wrote:
>
> Which brings up another point. Should I do an editorial change to
> fix the spelling kpeting => kepiting?
>
> On Thursday 29 February 2024 at 5:26:00 pm UTC+8 David wrote:
>
> It looks to me like an issue of how Slocum represented the word
> - Google Translate does have a "kepiting = crab

> <https://translate.google.com/details?sl=ms&tl=en&text=kepiting&op=translate>" entry for Malay, so that looks right.

>
> The alternative is to go with "unknown

> <https://standardebooks.org/manual/1.7.4/single-page#8.2.9.8>"

> if it seems like this is one of the local/indigenous languages

> <https://en.wikipedia.org/wiki/Cocos_(Keeling)_Islands#Demographics>, but I think it's safe to go with Malay ("ms").

>
> D.
>
> On Thursday 29 February 2024 at 08:35:54 UTC Brett wrote:
>
> Hi,
>
> Small question. I've just been through rationalising <i>
> tags by adding xml:lang or removing or changing to <em>. I

> found a word in italics /kpeting (crab) / that is from when

> he was in the cocos and keeling islands where they speak
> Malay the issue is that Google couldn't find a translation
> of it so I couldn't confirm that it is a Malay word. I did
> add a xml:lang="ms" based on where he was. Was that the
> correct thing to do?
>

> /One day after this, when I tried to haul the sloop and

> found her fast in the sand, the children all clapped their
> hands and cried that a kpeting (crab) was holding her by the

> keel; /
>
> Cheers, Brett

>
> --
> 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/71ddac36-eb82-430e-970b-15b99860ce22n%40googlegroups.com <https://groups.google.com/d/msgid/standardebooks/71ddac36-eb82-430e-970b-15b99860ce22n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Brett Roper]

Thanks. Another small question.

Slocum uses the old fashioned "P.&O."  for the ocean liner company but the company now uses "P&O". Should I change it and also should I wrap int in <abbr epub:type="z3998:initialism">?

Cheers, Brett

[David]

Maybe a little tricky — it's an abbreviation of "Peninsular & Oriental", and with the ampersand isn't properly (I think) an initialism. I'd retain the full stops, rather than omit. It can just be wrapped with a simple `abbr`.

See SEMoS § 8.7.3 on handling the ampersand.

D.

[Brett Roper]

Hi David,

Thanks for your help so far. I'm making good (slow) progress on the text (trying to avoid the SVG conversion for as long as possible).

I have a lint error and am wondering what the proper grammar is:

 y-014 │ Manual Review │ chapter-13.xhtml │ Possible typo: Unexpected . at the end of quotation. Hint: If a dialog tag    │
│       │               │                  │ follows, should this be ,?                                                    │
├───────┼───────────────┼──────────────────┼───────────────────────────────────────────────────────────────────────────────┤
│       │               │                → │ <p>There was little to report on this part of the voyage, except changeable   │
│       │               │                  │ winds, “busters,” and rough seas. The 12th of December, however, was an       │
│       │               │                  │ exceptional day, with a fine coast wind, northeast. The <i                    │
│       │               │                  │ epub:type="se:name.vessel.ship">Spray</i> early in the morning passed Twofold │
│       │               │                  │ Bay and later Cape Bundooro in a smooth sea with land close aboard. The       │
│       │               │                  │ lighthouse on the cape dipped a flag to the <i                                │
│       │               │                  │ epub:type="se:name.vessel.ship">Spray</i>’s flag, and children on the         │
│       │               │                  │ balconies of a cottage near the shore waved handkerchiefs as she passed by.   │
│       │               │                  │ There were only a few people all told on the shore, but the scene was a happy │
│       │               │                  │ one. I saw festoons of evergreen in token of Christmas, near at hand. I       │
│       │               │                  │ saluted the merrymakers, wishing them a “Merry Christmas.” and could hear     │
│       │               │                  │ them say, “I wish you the same.”</p>

[Brett Roper]

Oh wait. I think I answered my question. Looks like a transcription typo. Cool.

“Merry Christmas,” and could hear them say, “I wish you the same.”

[Brett Roper]

OK. that was easy. Here's another error:

  m-009 │ Error    │ content.opf │ <meta property="se:url.vcs.github"> value does not match expected:                                                                     │
│       │          │             │ https://github.com/standardebooks/joshua-slocum_sailing-alone-around-the-world_thomas-fogarty_george-varian.

It seems that lint wants me to include the illustrators names in the repo name. Is that correct?

Cheers, Brett.

[David]

[Grrr... I think I just sent a "private" message instead of to the group - not sure how I did that!]

Since you have Fogarty and Varian credited as illustrators in content.opf, lint wants to add them to the SE slug as in SEMoS § 9.2.2.

We were going cut decorative illustrations, though, and I don't think maps/charts usually attract this kind of credit. E.g., that Roosevelt, Brazilian Wilderness title that serves as the example for the SVG tutorial cuts illustrator credits, and assigns the `ill` marc relator to the author.

I would be inclined to do the same here - but it would be good to have this confirmed. (Thanks!)

Hope this helps - D.

[Lukas Bystricky]

If you have maps/charts or non-decorative illustrations and you know who produced them you can add credit to an illustrator (ill) or a cartographer (ctg) as appropriate and set display-seq to 0 (see SEMoS 9.10.4). This excludes them from the SE identifier. 

[David]

Thanks, Lukas - always more to learn! :)

@Brett - btw, when the time comes for the SVGs, there is the tutorial Alex pointed to originally. I've also bookmarked this post from Vince (including advice from David Grigg, who also authored that tutorial) which gives a useful step-by-step for creating SVG images for SE productions. It partly overlaps with the tutorial, but helpful to have both (IMO!).

D.

[Brett Roper]

Hi David and all,

My book gives coordinates like "7 degrees 35′ south" rather than "7° 35′ S". Should I leave as is?

Cheers, Brett.

[Brett Roper]

Oops. Pressed post too soon...

When I have a illustration printed sideways in the book do I copy that in my svg? It's too small to read if I do it in the same orientation as the text. e.g.

[David]

There is at least one example of that kind of mixed-mode presentation in the corpus. I would be inclined to leave it as-is, provided the symbols are correct where they are used.

[David]

We always (?) have the image orientation "horizontal", as "page" constraints in epubs/e-readers are quite different from the printed page. Human readers can always enlarge the image.

Any maps/charts you're including can be rotated so they are parallel to the reading line. (Conventions for images are in SEMoS § 10.5 : I expect you've become familiar with that section already!)

Hope that helps!

D·

[David]

Hey Brett - just checking in to see how things are going, as it's been a while since the last update.

Hopefully the project is still making progress! If there's anything you think we might do to help, do shout, and we'll see what we can do.

David / Fife, UK

[Brett Roper]

Hi David,

I got down to the SVG generation and hit a wall. When I turn the detail up the SVGs become too big but when I turn it down they aren't accurate enough. When I left it it was at the point where I was thinking I'd just do a low detail one and fix it by hand - but that takes time that I didn't have right at that second.

It's time for me to have another look at Inkscape with fresh eyes.

Apart from that I think I'm done (except for getting corrections from others). It was so satisfying to hit no lint errors. I did throw the jpgs in there and generate a copy for my kindle to proof read. Nothing jumped out at me but I'm a really poor copy editor so I wouldn't trust that.

Cheers, Brett

[David]

That sounds very encouraging, actually. I think of "no lint errors" as a cause for celebration!

Is this the sort of image that's proving troublesome? (To my eye, that scan has the sharpest images, and might provide a good starting point.) What are you getting as "too big"? If you have particular examples in mind, providing links would help, too.

Maybe I'll have a go and see what happens, but perhaps we could get advice from our SVG ninjas, too. :)

D.

[David]

Okay, here's my quick attempt on that map linked in the previous message. It's ~660Kb after a rough-and-ready "optimizing"; but I'm sure it needs further tweaks to meet SE standards for inclusion in a production.

Note that in addition to the how-to that Alex linked much earlier in this thread, there is also a reply in another thread (David Grigg via Vince) that I depend on, and might also be helpful.

Hopefully once you get one image "right", you'll have the standards for the others needing treatment, and they'll go more quickly.

FWIW! D.

[Brett Roper]

Hi David,

Sorry I've been quiet lately. My folks are getting old and now need 24 hour care so I 've been sharing shifts with my brothers looking after them. That and work is leaving no time to scratch myself. I'm setting aside time tomorrow to get back into this. Thank you so much for your encouragement.

Regards, Brett.

--
You received this message because you are subscribed to a topic in the Google Groups "Standard Ebooks" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/standardebooks/_Dsf5MHNcag/unsubscribe.
To unsubscribe from this group and all its topics, send an email to standardebook...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/b4568f83-4973-4942-8626-37ed4fa2bdc6n%40googlegroups.com.

[David]

Hi Brett - thanks for the update. I certainly understand the challenges that this phase of life brings. I hope all goes well as possible for you and yours.

It's good to know, too, that you're still able to chip away at this project. As ever, do let us know if there's anything we can do to help.

Bye for now! David

On Friday 9 August 2024 at 01:18:51 UTC+1 Brett wrote:

Hi David,

[Brett Roper]

Hi David and all,

I've got a new MB Air and I'm finally back at it (almost a year's break - sorry). The SE toolset is updated and my formally lint free repo now has errors again. Just a clarification on markup. The text says "Captain Fisher, R.N." so do I mark that up as "Captain Fisher, <abbr epub:type="z3998:name-title">R.N.</abbr>" ?

Cheers, Brett

[David Reimer]

Hi Brett - welcome back. :) And yes, you've got that correct.

On Wednesday, 23 July 2025, Brett Roper wrote:

Hi David and all,

I've got a new MB Air and I'm finally back at it (almost a year's break - sorry). The SE toolset is updated and my formally lint free repo now has errors again. Just a clarification on markup. The text says "Captain Fisher, R.N." so do I mark that up as "Captain Fisher, <abbr epub:type="z3998:name-title">R.N.</abbr>" ?

Cheers, Brett

--

David Reimer
Fife, UK
djre...@gmail.com