[First Project} Jules Verne's Ticket No. "9672"

[Genevieve Segol]

i would like to start with the above title -- or any other Jules Verne fiction  If there are higher priorities, I could also work on one of P. G. Wodehouse's novels.  

thank you.

[Alex Cabal]

Great, that one would be a good start.

Remove the quotation marks from the title. I see there's a letter or two
in there, see the manual for styling. I also see a Latin quote that's
not in italics: remember that all non-English must be in italics. You
can remove the page numbers before starting by using a regex.

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/0b90595e-d1b7-4b62-a263-1466bc294e0en%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/0b90595e-d1b7-4b62-a263-1466bc294e0en%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Genevieve Segol]

Help needed.

I installed brew and standardebooks using pipx, following the Github instructions for MacOS.  Everything seems to have worked fine.  But the se command is not found.

 se --version

Suggestions?  Thank you.

[Vince]

On May 21, 2021, at 5:58 PM, Genevieve Segol <genevie...@gmail.com> wrote:

Help needed.

I installed brew and standardebooks using pipx, following the Github instructions for MacOS.  Everything seems to have worked fine.  But the se command is not found.

 se --version

Suggestions?  Thank you.

You didn’t show the output–what does se --version return (cut-and-paste, please)?

What does which se return?

What version of MacOS? Intel or M1?

[Genevieve Segol]

se returns nothing.

1. end of installation:

⚠️  Note: '/Users/gsegol/.local/bin' is not on your PATH environment variable. These apps will not be globally accessible until your PATH is updated. Run `pipx ensurepath` to automatically add it, or manually modify your PATH in your shell's config file (i.e. ~/.bashrc).

done! ✨ 🌟 ✨

2. So, I did as suggested

(base) GS-MacBookAir:~ gsegol$ pipx ensurepath

Success! Added /Users/gsegol/.local/bin to the PATH environment variable.

3. Then trying to verify version:

(base) GS-MacBookAir:~ gsegol$ se --version

-bash: se: command not found

(base) GS-MacBookAir:~ gsegol$ 

Thank you for your help

P.S. Using MacOs 11.3.1

[Alexis]

Genevieve Segol <genevie...@gmail.com> writes:

> Success! Added /Users/gsegol/.local/bin to the PATH environment
> variable.
> 3. Then trying to verify version:
>
> (base) GS-MacBookAir:~ gsegol$ se --version
>
> -bash: se: command not found

Does it work after doing:

$ hash -r

?


Alexis.

[Genevieve Segol]

Alexis,

Thank you.

I tried your trick, but the result is the same:  

se: command not found.

Other ideas?

[Genevieve Segol]

I did echo $PATH and did not see the addition expected after running 

pipx ensure path

So, i tried adding the path manually, i.e., 

export PATH=$PATH:/Users/gsegol/.local/bin

Surprise, that works :). Now running 

se --version

returns 

1.9.3

[François Grandjean]

Great, I'm glad you got it working!

Although, if you entered the command in the terminal, the change to $PATH will expire as soon as you exit the terminal. If you don't fancy typing it multiple times, you can add that line to ~/.bashrc and it will “stick”. Of course, you might have already done it. :)

And a small recommendation: ideally, your line should be:

export PATH=/Users/gsegol/.local/bin:$PATH

The point of adding $PATH at the end and not at the start is that when you execute a program, your computer will look for it on all locations in $PATH. As soon as it finds the program somewhere, it stops the search and executes it. Ideally, you want the first locations to be those in your user directory because you might have different versions of the same program on your system but those in your user directory should typically be more up-to-date than those found in system directories. It shouldn't be a problem for the SE toolset, but it might happen with other programs.

[Genevieve Segol]

Thank you, François!

[Genevieve Segol]

I have made a first commit to GitHub.  My git skills are rudimentary, so I would be grateful if someone would review what I have done so far.  Thank you.

https://github.com/gsegol/jules-verne_ticket-no-9672

[François Grandjean]

I’ll try to help, but please keep in mind that other, smarter, people may want to say something and what they say would likely take precedence over whatever I say. In particular Alex always has the final word.

From what I see, you are headed in the right direction but you seem a bit confused. For example, looking at your commit history, the first commit is called “split body into chapters and basic clean”. But looking at its content, body.xhtml still has the header content before the text and the Project Gutenberg license after the text, and it isn’t split into chapters. It doesn’t exactl do what we expect it to do from the name.

The next two commits, however, do seem to do what they state (splitting chapters and deleting the body) so we’re back on tracks.

I assume you’ve read the step-by-step guide (https://standardebooks.org/contribute/producing-an-ebook-step-by-step). It is designed to give you a good idea on what you are supposed to do to produce an ebook, but it also helps standardise the process. While each book is different and may require some special steps, the process is generally standardised and that helps us see what step you are at and where you are headed.

Looking back at the guide, the first commit is expected to be called “Initial commit”. Ideally, that would be your book project right after you create it and with the body edited so all the code at the top (class definitions, table of content, etc.) and the PG license at the bottom removed. Then the next commit would take several step, i.e., split the body into chapters and remove the body, run se clean, and then typogrify. That structure gives a good idea of the current state of your production, where it is headed, and keeps it consistent with others.

It is always possible to do things a bit differently (each book, after all, is different) but it is important that you understand the workflow first, and following this guide for your first production should help you do that. For example, your last two commits (split chapters and delete body) could have been one single commit. Not every action needs to be on its own commit, rather one commit represents one logical unit of work and may contain several actions logically linked together.

I’m not sure what the best course of action should be. You’re at the very beginning, so it might be worth starting over to follow the guide closely. That would give you a clean start. But may someone else has suggestions on how to clean your repo history. In any case, I suggest you become more familiar with Git by creating a dummy repo where you can add and remove simple text files, edit them, commit the changes, etc. We use Git extensively, so practise would help you be more comfortable with it.

I hope that helps clarify things. Please do ask again if you are lost. Many of us already had prior experience with Git before our first book production, but that’s not everyone.

[Alex Cabal]

Yes, I agree with Francois. Follow the step by step guide to the letter
for your first production. It contains everything you need to complete
an ebook from start to finish. Using the commit messages in the guide,
in that order, will also make it much easier to review later.

> --
> 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/0e4fd3e9-ec1f-4713-80f3-92ad4cf4a7c7n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/0e4fd3e9-ec1f-4713-80f3-92ad4cf4a7c7n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Genevieve Segol]

OK.  Thank you.

I will remove the repository and do it again.

[Genevieve Segol]

What is the standard for commit messages during proof-reading?  Should we make a commit for every error corrected and identify the correction?  Or use one commit to reflect several corrections?

Thank you.

[Robin Whittleton]

It’s down to you to a certain extent, but focus on what might be useful to preserve in history. For example, you could choose to commit once per chapter, or you could wait until the end of the book and group your fixes by category.

-Robin

On 2 Jun 2021, at 21:41, Genevieve Segol <genevie...@gmail.com> wrote:

What is the standard for commit messages during proof-reading?  Should we make a commit for every error corrected and identify the correction?  Or use one commit to reflect several corrections?

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/058b67e1-b60f-43c1-bb60-d8e2116a92d8n%40googlegroups.com.

[Genevieve Segol]

The report from se lint shows an error for every instance of a page number.

Example:

Message

Empty element. Use <hr/> for thematic breaks if appropriate.

Pointer

<a id="page6" name="page6"/> 

<a id="page7" name="page7"/> 

etc.

These tags were generated automatically in the initial draft.  

What is the problem, and how do I fix this?

Thank you!

[Vince]

They weren’t generated, they were already part of the transcription.

You can remove all of them, we do not keep them in our productions.

[François Grandjean]

These were likely part of the original PG transcription. You should remove them.

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/IrGadZi33ck/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/0c2ff906-e308-48b6-818f-b7f6ee14df06n%40googlegroups.com.

[Genevieve Segol]

OK.  I removed these tags.  I have one error left in the content file which I don't know how to resolve:

Double spacing found. Sentences should be single-spaced. (Note that double spaces   might include Unicode no-break spaces!)

If I open this chapter in a browser, I do not see any double spacing.  The chapter is visually similar to others in this book.

No special character I can think of, except for em-dash, which occurs in a few other chapters.

This newbie will be grateful for any clues.  Thank you!

[David Grigg]

Just do a global search replace for two spaces. You might need to do a regex search looking for hairspace, non-breaking space, etc.

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/bee347cd-5941-485c-85a8-a0a12c3cf78bn%40googlegroups.com.

[Genevieve Segol]

 Error  No <meta property="se:long-description"> element in content.opf.

Here is the format used:

<meta id="long-description" property="se:long-description" refines="#description"><p>Hulda, the daughter of an innkeeper in the Norwegian countryside, is engaged to Ole, a fisherman. When Ole fails to return, Hulda fears him dead, until she receives a message which Ole scribbled at the back of a lottery ticket. Her story is recounted by the press, generating excitement ahead of the drawing.</p>

</meta>

I checked other books on GitHub and they seem to be using the same syntax.

What is the problem?

Thank you.

[Vince]

See section 9.6.2 of the manual. A search on the manual for “long description” would also lead you there.

[Genevieve Segol]

According to Google Translate,  

“God-aften!”

is either Swedish or Danish, but not Norwegian.

However, immediately after this dialog, the text continues:

"“This is the Norwegian good night. ”

So, is Norwegian or Swedish the right choice for the language tag? 

[Vince]

Contrary to Google’s opinion of itself, it is not always correct. Especially Translate. It’s always a good idea to do a general search for the term, if there’s any question about it.

https://en.wiktionary.org/wiki/god_aften

https://www.italki.com/post/question-107317?hl=en

[Robin Whittleton]

“God aften” is legit Norwegian in the Bokmål dictionary at least: https://ordbok.uib.no/perl/ordbok.cgi?OPP=God+aften&ant_bokmaal=5&ant_nynorsk=5&bokmaal=+&ordbok=nynorsk It’s probably historical though. It is correct Danish nowadays. “God afton” is the Swedish so it’s definitely not that.

On 4 Jun 2021, at 22:30, Genevieve Segol <genevie...@gmail.com> wrote:

According to Google Translate,  

--
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/898c32f2-211e-4e19-8947-2c66e08e8466n%40googlegroups.com.

[Genevieve Segol]

:-). Great

How about this:

Wed bekomme

[Robin Whittleton]

Spelling mistake for “wel bekomme”? W and V are often used the same way in older Scandinavian, and “vel bekomme” is “you’re welcome” in Bokmål Norwegian: https://ordbok.uib.no/perl/ordbok.cgi?OPP=Vel+bekomme&ant_bokmaal=5&ant_nynorsk=5&bokmaal=+&ordbok=bokmaal

On 4 Jun 2021, at 22:50, Genevieve Segol <genevie...@gmail.com> wrote:

:-). Great

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/d42028da-ffce-4ef3-a4a7-dc88a2011d72n%40googlegroups.com.

[David Grigg]

We almost need some kind of flag which means “this is supposed to be language X, but the author hasn’t got it quite right”. There’s a fair bit of this in Lavengro!

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/4361BA53-BAEB-4D66-B4AB-24F21932FA12%40reala.net.

[Matt Chan]

I wonder if this is fair game for an editorial correction/edit? Like, I feel like if correcting the foreign language spelling doesn't detracts from the intention of the author and decreases potential reader's distraction? 

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/4e0df4e7-69e1-4191-af02-c8e4369103eb%40Spark.

[Segol Genevieve]

I checked the original text in French:  “Wed bekomme” is how Jules Verne put it.  It could be a local patois, or a 19th century term, or the author’s mistake.

For now, I just put this in italics without the language code.

Geneviėve
genevie...@gmail.com

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/CAB6ohTeuu7igWNXJ%3DhWm0xiLgwgoG3dQXftN%3D-2UwiHjc8O32w%40mail.gmail.com.

[Vince]

There’s some discussion about Verne’s Norwegian in general, and Wed bekomme in particular, here.

On Jun 5, 2021, at 2:55 PM, Segol Genevieve <genevie...@gmail.com> wrote:

I checked the original text in French:  “Wed bekomme” is how Jules Verne put it.  It could be a local patois, or a 19th century term, or the author’s mistake.

For now, I just put this in italics without the language code.

[Genevieve Segol]

Napoleon gifted Norway to Sweeden.  This union  lasted until 1905, so Norway and Sweeden were a single country when Jules Verne wrote his novel.  This may explain the confusing origin of some terms.  Anyway, I will mark God aften as Norwegian.  Thanks.l

On Friday, June 4, 2021 at 1:43:54 PM UTC-7 robin wrote:

[Genevieve Segol]

Submitted for review.

https://github.com/gsegol/jules-verne_ticket-no-9672

Notes:

1. I removed all references to digital scans since I could not find any from this specific translation of the work and was told to proceed without  them.
2. The imprint, colophon, and content files are new territory for me.  Please check carefully.
3. Most of the changes made while proofreading include a) italicizing ships' names and newspapers' names, which were indicated by single or double quotes in Gutenberg; b) removing hyphens in common terms (e.g., wedding-day, dining-room); c) adding language tags for foreign terms.  I made one commit per chapter so you can track the specific corrections.
   
4.  I corrected the following details in the Gutenberg version:

• we find the terms soetur, , soeter, and souter to refer to “the little mountain farm where a young shepherd kept guard over half a dozen cows and about thirty sheep."  The French edition uses soeter, so I use this term in all occurrences.
• I changed protégées to protegés (without italics) when referring to a man and a woman.

Thank you.

[Alex Cabal]

Robin do you have time to review this?

On 6/7/21 6:30 PM, Genevieve Segol wrote:
> Submitted for review.
> https://github.com/gsegol/jules-verne_ticket-no-9672
>
> Notes:
>

> 1. I removed all references to digital scans since I could not find any

> from this specific translation of the work and was told to proceed
> without  them.

> 2. The imprint, colophon, and content files are new territory for me.
>  Please check carefully.
> 3. Most of the changes made while proofreading include a) italicizing

> ships' names and newspapers' names, which were indicated by single
> or double quotes in Gutenberg; b) removing hyphens in common terms
> (e.g., wedding-day, dining-room); c) adding language tags for
> foreign terms.  I made one commit per chapter so you can track the
> specific corrections.

> 4.  I corrected the following details in the Gutenberg version:
>
> * we find the terms /soetur/, , /soeter/, and /souter/ to refer to

> “the little mountain farm where a young shepherd kept guard over
> half a dozen cows and about thirty sheep."  The French edition uses
> soeter, so I use this term in all occurrences.

> * I changed /protégées/ to /protegés/ (without italics) when referring

> to a man and a woman.
>
> Thank you.
> On Saturday, June 5, 2021 at 4:47:16 PM UTC-7 Genevieve Segol wrote:
>
> Napoleon gifted Norway to Sweeden.  This union  lasted until 1905,
> so Norway and Sweeden were a single country when Jules Verne wrote
> his novel.  This may explain the confusing origin of some terms.

>  Anyway, I will mark /God aften/ as Norwegian.  Thanks.l

>
> On Friday, June 4, 2021 at 1:43:54 PM UTC-7 robin wrote:
>
> “God aften” is legit Norwegian in the Bokmål dictionary at
> least:
> https://ordbok.uib.no/perl/ordbok.cgi?OPP=God+aften&ant_bokmaal=5&ant_nynorsk=5&bokmaal=+&ordbok=nynorsk
> <https://ordbok.uib.no/perl/ordbok.cgi?OPP=God+aften&ant_bokmaal=5&ant_nynorsk=5&bokmaal=+&ordbok=nynorsk> It’s
> probably historical though. It is correct Danish nowadays. “God
> afton” is the Swedish so it’s definitely not that.
>
>> On 4 Jun 2021, at 22:30, Genevieve Segol
>> <genevie...@gmail.com> wrote:
>>
>> According to Google Translate,

>> /“God-aften!”/

>> is either Swedish or Danish, but not Norwegian.
>> However, immediately after this dialog, the text continues:

>> /"“This is the Norwegian good night. ”/

>> So, is Norwegian or Swedish the right choice for the language
>> tag?
>>
>>
>>
>> On Thursday, June 3, 2021 at 9:55:55 PM UTC-7 Vince wrote:
>>
>> See section 9.6.2

>> <https://standardebooks.org/manual/1.5.0/single-page#9.6.2> of

>> <https://groups.google.com/d/msgid/standardebooks/898c32f2-211e-4e19-8947-2c66e08e8466n%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/97ca7f38-31a1-477a-8616-e1faa1c6b055n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/97ca7f38-31a1-477a-8616-e1faa1c6b055n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Robin Whittleton]

Yep, I can do this.

> On 8 Jun 2021, at 01:59, Alex Cabal <al...@standardebooks.org> wrote:
>
> Robin do you have time to review this?

> To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/44e38180-bf34-3e2e-0e9f-3a2833fb56d6%40standardebooks.org.

[Robin Whittleton]

There are a couple of XML errors. I’ve filed an issue for that at https://github.com/gsegol/jules-verne_ticket-no-9672/issues/1.

Once those are fixed, can you run se lint again? That throws up a set of errors that need investigating. Most of them should be fairly self-explanatory, but if anything’s not obvious let me know. Once those are dealt with I’ll review again.

Just to double-check: you’ve completed a proofread through the whole book right?

-Robin

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/97ca7f38-31a1-477a-8616-e1faa1c6b055n%40googlegroups.com.

[Genevieve Segol]

1. Thank you for the review

2. Yes, I proofread the whole book, cover to cover.

3. I have a question regarding your request to add a language tag to the newspaper title.

"also, Morgon-Blad should probably have xml:lang="no" semantics too? It literally translates as Morning Page"

How do I combine the xml language tag with the epub type--both of which demand italics?  Semi-column? I could not find an example in the manual of style

<i epub:type="se:name.publication.newspaper">Morgen-Blad</i>

<i xml:lang="no">Morgen-Blad</i>

==>?

<i epub:type="se:name.publication.newspaper"; xml:lang="no">Morgen-Blad</i>

Note:  For some reason, the ships' names were translated to English but the newspapers' names were not.

[François Grandjean]

You almost got it right. HTML tags can take more than one attribute, so in this case it would be:

<i epub:type="se:name.publication.newspaper" xml:lang="no">Morgen-Blad</i> (Note that attributes are not separated by semicolons but by spaces.)

It likely isn't in the Manual because it's standard HTML behaviour.

[Genevieve Segol]

Thank you!

 One more question.

se lint flags for manual review my treatment of abbreviations.  In this instance, I have the name of a company called Help Bros., which I entered as Help <abbr>Bros.</abbr> or at the end of a sentence, Help <abbr>Bros.</abbr>.

The comment is:

Initialism or name followed by period. Hint: Periods go within <abbr>. <abbr>s containing periods that end a clause     

require the eoc class. 

The period is part of the abbreviation, so it is properly put inside the tag.  So, can you explain how to handle this "eoc class" requirement"?

Thanks again.

[Vince]

Yes, they go in the tag, but you have them both in and out of the tag. We don’t see

Help Bros..

in print, so we don’t do that in the ebook, either.

See section 8.10 of the manual, especially 8.10.3.

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/49568ebe-2518-4711-b119-d22209354171n%40googlegroups.com.

[Genevieve Segol]

Got it!  Thank you!

[Genevieve Segol]

Re-submitted for review:

https://github.com/gsegol/jules-verne_ticket-no-9672

I ran se lint and fixed all errors in the text.  I am left with two "manual review" in colophon and imprint, which highlight the fact that I do not provide a reference to Hathitrust.  As noted earlier, I don't have any scans for this translation, thus no reference to provide.

[Emma Sweeney]

It's giving you those errors because your content.opf contains <dc:source>https://catalog.hathitrust.org/Record/011261430</dc:source>.

Emma

[Genevieve Segol]

Thank you, Emma.  I understand.

Since this record points to a different translation, I suppose I should remove the reference in content.opf.  Correct?

[Emma Sweeney]

Yes. You should only add links that you used to correct the transcription.

Emma

[Genevieve Segol]

re-submitted after one more correction.  Passed se lint without error.

https://github.com/gsegol/jules-verne_ticket-no-9672

Thanks.

[Robin Whittleton]

Thanks Genevieve, I’ll give this a look over tonight / tomorrow morning.

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/338f47a9-55f8-4474-9f91-ecb7a7905b65n%40googlegroups.com.

[Robin Whittleton]

Ah, just tried running lint and hit a few more warnings. Could you upgrade to the latest version of the toolkit (pipx upgrade standardebooks) and run it again?

• se:name.transport-vessel.ship should be se:name.vessel.ship
• se:color-depth.black-on-transparent needs to be se:image.color-depth.black-on-transparent
• The manifest needs to be regenerated with se build-manifest .
• Uncopyright page can just be replaced with the markup at https://raw.githubusercontent.com/standardebooks/tools/master/se/data/templates/uncopyright.xhtml

-Robin

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/338f47a9-55f8-4474-9f91-ecb7a7905b65n%40googlegroups.com.

[Genevieve Segol]

I have upgraded to SE 2.0.1 and changed all occurrences of se:name.transport-vessel.ship  to se:name.vessel.ship 

I need help pushing these changes to GitHub.  

There are two edits on GitHub that are not in my local repo.  

Your branch and 'origin/main' have diverged, and have 2 and 40 different commits each, respectively.

  (use "git pull" to merge the remote branch into yours)

So, I tried 

git pull origin main

With the result

fatal: refusing to merge unrelated histories

What is the right way to get the local and remote repos in sync?

Thank you!

[Genevieve Segol]

Not elegant, but this will get me out of this jam.  I created a new repo  at 

https://github.com/gsegol/jules-verne_ticket-no-9672A

The 'initial commit" is really commit #41 , which changed  se:name.transport-vessel.ship  to se:name.vessel.ship 

I still would like to understand the problem with the other repo, but in the meantime, I will continue with the changes Robin requested.

[Alex Cabal]

We need the whole commit history, this isn't going to be a long-term
solution

It's hard to say what went wrong with Git without seeing the history.
However there are many git tutorials, how-tos, and troubleshooting
guides out there. Google will get you far. You can make a copy of your
repo directory in its current state somewhere else so that you have a
backup in case things go wrong.

On 6/11/21 5:18 PM, Genevieve Segol wrote:
> Not elegant, but this will get me out of this jam.  I created a new repo
>  at
> https://github.com/gsegol/jules-verne_ticket-no-9672A
>
> The 'initial commit" is really commit #41 , which changed
>  se:name.transport-vessel.ship  to se:name.vessel.ship
>
> I still would like to understand the problem with the other repo, but in
> the meantime, I will continue with the changes Robin requested.
>
> On Friday, June 11, 2021 at 1:01:35 PM UTC-7 Genevieve Segol wrote:
>
>
> I have upgraded to SE 2.0.1 and changed all occurrences of
> se:name.transport-vessel.ship  to se:name.vessel.ship
>

> *I need help pushing these changes to GitHub. *

> There are two edits on GitHub that are not in my local repo.
>
> Your branch and 'origin/main' have diverged, and have 2 and 40
> different commits each, respectively.
>
>   (use "git pull" to merge the remote branch into yours)
>
> So, I tried
>
> git pull origin main
>
> With the result
>
> fatal: refusing to merge unrelated histories
>
> What is the right way to get the local and remote repos in sync?
>
> Thank you!
>
> On Friday, June 11, 2021 at 9:45:29 AM UTC-7 robin wrote:
>
> Ah, just tried running lint and hit a few more warnings. Could
> you upgrade to the latest version of the toolkit (pipx upgrade
> standardebooks) and run it again?
>

> * se:name.transport-vessel.ship should be se:name.vessel.ship
> * se:color-depth.black-on-transparent needs to
> be se:image.color-depth.black-on-transparent
> * The manifest needs to be regenerated with se build-manifest .
> * Uncopyright page can just be replaced with the markup at

>> <https://standardebooks.org/manual/1.6.0/single-page#8.10> of

>> the manual, especially 8.10.3.
>>
>>
>>> On Jun 9, 2021, at 4:35 PM, Genevieve
>>> Segol <genevie...@gmail.com> wrote:
>>>
>>> Thank you!
>>>  One more question.

>>> se lintflags for manual review my

>>> treatment of abbreviations.  In this
>>> instance, I have the name of a
>>> company called Help Bros., which I

>>> entered as*Help <abbr>Bros.</abbr>*or
>>> at the end of a sentence, *Help
>>> <abbr>Bros.</abbr>.*

>>> The comment is:
>>> Initialism or name followed by
>>> period. Hint: Periods go within
>>> <abbr>. <abbr>s containing periods
>>> that end a clause
>>> require the eoc class.
>>>
>>> The period is part of the
>>> abbreviation, so it is properly put
>>> inside the tag.  So, can you explain
>>> how to handle this "eoc class"
>>> requirement"?
>>>
>>> Thanks again.
>>> On Wednesday, June 9, 2021 at
>>> 12:26:56 PM UTC-7
>>> francois....@gmail.com

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

>>>
>>> You almost got it right. HTML
>>> tags can take more than one
>>> attribute, so in this case it
>>> would be:
>>> <i
>>> epub:type="se:name.publication.newspaper"
>>> xml:lang="no">Morgen-Blad</i>
>>> (Note that attributes are not
>>> separated by semicolons but by
>>> spaces.)
>>>
>>> It likely isn't in the Manual
>>> because it's standard HTML behaviour.
>>>
>>> On Wednesday, 9 June 2021 at
>>> 13:50:36
>>> UTC-5genevie...@gmail.comwrote:
>>>
>>> 1. Thank you for the review
>>>
>>> 2. Yes, I proofread the whole
>>> book, cover to cover.
>>>
>>> 3. I have a question
>>> regarding your request to add
>>> a language tag to the
>>> newspaper title.

>>> "also, /Morgon-Blad/ should

>>> probably
>>> have xml:lang="no" semantics
>>> too? It literally translates

>>> as /Morning Page"/

>>>
>>> How do I combine the xml
>>> language tag with the epub
>>> type--both of which demand
>>> italics?  Semi-column? I
>>> could not find an example in
>>> the manual of style
>>> <i
>>> epub:type="se:name.publication.newspaper">Morgen-Blad</i>
>>> <i xml:lang="no">Morgen-Blad</i>
>>> ==>?
>>> <i epub:type="se:name.publication.newspaper";
>>> xml:lang="no">Morgen-Blad</i>
>>>
>>> Note:  For some reason, the
>>> ships' names were translated
>>> to English but the
>>> newspapers' names were not.
>>> On Tuesday, June 8, 2021 at
>>> 11:41:05 PM UTC-7 robin wrote:
>>>
>>> There are a couple of XML
>>> errors. I’ve filed an
>>> issue for that at
>>> https://github.com/gsegol/jules-verne_ticket-no-9672/issues/1

>>> <https://github.com/gsegol/jules-verne_ticket-no-9672/issues/1>.

>>>
>>> Once those are fixed, can
>>> you run se lint again?
>>> That throws up a set of
>>> errors that need
>>> investigating. Most of
>>> them should be fairly
>>> self-explanatory, but if
>>> anything’s not obvious
>>> let me know. Once those
>>> are dealt with I’ll
>>> review again.
>>>
>>> Just to double-check:
>>> you’ve completed a
>>> proofread through the
>>> whole book right?
>>>
>>> -Robin
>>>
>>>> On 8 Jun 2021, at 01:30,
>>>> Genevieve Segol
>>>> <genevie...@gmail.com>
>>>> wrote:
>>>>
>>>> Submitted for review.
>>>> https://github.com/gsegol/jules-verne_ticket-no-9672

>>>> <https://github.com/gsegol/jules-verne_ticket-no-9672>
>>>>
>>>> Notes:
>>>>
>>>> 1. I removed all

>>>> references to
>>>> digital scans since
>>>> I could not find any
>>>> from this specific
>>>> translation of the
>>>> work and was told to
>>>> proceed without  them.

>>>> 2. The imprint,

>>>> colophon, and
>>>> content files are
>>>> new territory for
>>>> me.  Please check
>>>> carefully.

>>>> 3. Most of the changes

>>>> made while
>>>> proofreading include
>>>> a) italicizing
>>>> ships' names and
>>>> newspapers' names,
>>>> which were indicated
>>>> by single or double
>>>> quotes in Gutenberg;
>>>> b) removing hyphens
>>>> in common terms
>>>> (e.g., wedding-day,
>>>> dining-room); c)
>>>> adding language tags
>>>> for foreign terms.
>>>>  I made one commit
>>>> per chapter so you
>>>> can track the
>>>> specific corrections.

>>>> 4.  I corrected the

>>>> following details in
>>>> the Gutenberg version:
>>>>

>>>> * we find the
>>>> terms/soetur/,
>>>> ,/soeter/,
>>>> and/souter/to refer

>>>> to “the little
>>>> mountain farm where
>>>> a young shepherd
>>>> kept guard over half
>>>> a dozen cows and
>>>> about thirty sheep."
>>>>  The French edition
>>>> uses soeter, so I
>>>> use this term in all
>>>> occurrences.

>>>> * I
>>>> changed/protégées/to/protegés/ (without

>>>> italics) when
>>>> referring to a man
>>>> and a woman.
>>>>
>>>> Thank you.
>>>> On Saturday, June 5,
>>>> 2021 at 4:47:16 PM UTC-7
>>>> Genevieve Segol wrote:
>>>>
>>>> Napoleon gifted
>>>> Norway to Sweeden.
>>>>  This union  lasted
>>>> until 1905, so
>>>> Norway and Sweeden
>>>> were a single
>>>> country when Jules
>>>> Verne wrote his
>>>> novel.  This may
>>>> explain the
>>>> confusing origin of
>>>> some terms.  Anyway,

>>>> I will mark/God
>>>> aften/as Norwegian.

>>>>> /“God-aften!”/

>>>>> is either
>>>>> Swedish or
>>>>> Danish, but not
>>>>> Norwegian.
>>>>> However,
>>>>> immediately
>>>>> after this
>>>>> dialog, the
>>>>> text continues:

>>>>> /"“This is the
>>>>> Norwegian good
>>>>> night. ”/

>>>>> So, is
>>>>> Norwegian or
>>>>> Swedish the
>>>>> right choice
>>>>> for the
>>>>> language tag?
>>>>>
>>>>>
>>>>>
>>>>> On Thursday,
>>>>> June 3, 2021 at
>>>>> 9:55:55 PM
>>>>> UTC-7 Vince wrote:
>>>>>
>>>>> See section
>>>>> 9.6.2

>>>>> <https://standardebooks.org/manual/1.5.0/single-page#9.6.2> of

>>>>> <https://groups.google.com/d/msgid/standardebooks/898c32f2-211e-4e19-8947-2c66e08e8466n%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/97ca7f38-31a1-477a-8616-e1faa1c6b055n%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/standardebooks/97ca7f38-31a1-477a-8616-e1faa1c6b055n%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/49568ebe-2518-4711-b119-d22209354171n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/standardebooks/49568ebe-2518-4711-b119-d22209354171n%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/338f47a9-55f8-4474-9f91-ecb7a7905b65n%40googlegroups.com
>> <https://groups.google.com/d/msgid/standardebooks/338f47a9-55f8-4474-9f91-ecb7a7905b65n%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/13f9d632-0516-4509-afee-e2475e7c9c64n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/13f9d632-0516-4509-afee-e2475e7c9c64n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Weijia Cheng]

Can you run "git status", "git --no-pager log" and "git --no-pager reflog" and paste the output of each so that we can see your full commit and reference history? I suspect there is an easy way to fix the problem but I need more info first.

[Weijia Cheng]

Worst case if you don''t mind discarding your progress after commit #40 (it doesn't seem to be a big change) you can run "git reset --hard origin/main" which sets the state of your local repo to exactly the state of the remote repo.

[Genevieve Segol]

Alex,

I understand that we need the whole history.  I have kept the initial repo intact.

I have not made any changes on the remote, so I have no idea why the two are not in sync.

I consulted various tutorials and documentation, but have been unable to fix the problem

Tried fetch and then merge instead of pull

Tried git config pull.rebase false

I always get the same message about "refusing to merge unrelated histories"

On Friday, June 11, 2021 at 3:34:51 PM UTC-7 Alex Cabal wrote:

[Alex Cabal]

Have you tried searching for that error message?

On 6/11/21 5:51 PM, Genevieve Segol wrote:
> Alex,
> I understand that we need the whole history.  I have kept the initial
> repo intact.

> I have not made any changes /on the remote,/ so I have no idea why the

> two are not in sync.
>
> I consulted various tutorials and documentation, but have been unable to
> fix the problem

> Triedfetch and then merge instead of pull
> Triedgit config pull.rebase false

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

> <http://groups.google.com/d/msgid/standardebooks/898c32f2-211e-4e19-8947-2c66e08e8466n%40googlegroups.com>
>
> >>>>>
> <https://groups.google.com/d/msgid/standardebooks/898c32f2-211e-4e19-8947-2c66e08e8466n%40googlegroups.com?utm_medium=email&utm_source=footer

> <https://groups.google.com/d/msgid/standardebooks/898c32f2-211e-4e19-8947-2c66e08e8466n%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/97ca7f38-31a1-477a-8616-e1faa1c6b055n%40googlegroups.com

> <http://groups.google.com/d/msgid/standardebooks/97ca7f38-31a1-477a-8616-e1faa1c6b055n%40googlegroups.com>
>
> >>>>
> <https://groups.google.com/d/msgid/standardebooks/97ca7f38-31a1-477a-8616-e1faa1c6b055n%40googlegroups.com?utm_medium=email&utm_source=footer

> <https://groups.google.com/d/msgid/standardebooks/97ca7f38-31a1-477a-8616-e1faa1c6b055n%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/49568ebe-2518-4711-b119-d22209354171n%40googlegroups.com

> <http://groups.google.com/d/msgid/standardebooks/49568ebe-2518-4711-b119-d22209354171n%40googlegroups.com>
>
> >>>
> <https://groups.google.com/d/msgid/standardebooks/49568ebe-2518-4711-b119-d22209354171n%40googlegroups.com?utm_medium=email&utm_source=footer

> <https://groups.google.com/d/msgid/standardebooks/49568ebe-2518-4711-b119-d22209354171n%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/338f47a9-55f8-4474-9f91-ecb7a7905b65n%40googlegroups.com

> <http://groups.google.com/d/msgid/standardebooks/338f47a9-55f8-4474-9f91-ecb7a7905b65n%40googlegroups.com>
>
> >>
> <https://groups.google.com/d/msgid/standardebooks/338f47a9-55f8-4474-9f91-ecb7a7905b65n%40googlegroups.com?utm_medium=email&utm_source=footer

> <https://groups.google.com/d/msgid/standardebooks/338f47a9-55f8-4474-9f91-ecb7a7905b65n%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/13f9d632-0516-4509-afee-e2475e7c9c64n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/13f9d632-0516-4509-afee-e2475e7c9c64n%40googlegroups.com>
>
> >

> <https://groups.google.com/d/msgid/standardebooks/13f9d632-0516-4509-afee-e2475e7c9c64n%40googlegroups.com?utm_medium=email&utm_source=footer
> <https://groups.google.com/d/msgid/standardebooks/13f9d632-0516-4509-afee-e2475e7c9c64n%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/0207e464-6dbb-4527-a55b-12cbd5beddd4n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/0207e464-6dbb-4527-a55b-12cbd5beddd4n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Vince]

If the two are not in sync, then either a change was made on the remote, or commits were deleted from the local and then other local commits added after them.

A web search on "refusing to merge unrelated histories” will yield more information on what it is, what might cause it, and what you can do to move forward.

But the first thing you’re going to have to determine is what is in the commits that are present in the remote that you don’t have locally, and whether they matter.

As Alex said, make a copy of your local repository before you do anything, so in a worst case scenario you can get back to where you started.

[Genevieve Segol]

Here are the logs you suggested.

I don't understand this part:

2d9ac98 HEAD@{5}: commit (initial): split body into chapters and basic clean

This goes back to May 26.  It was my first commit and I was told it was wong because I was not following the step-by-step guid to the letter.

I DELETED the repository and did it again.  Right now, the older commit on GitHub is May 27 and titled "initial commit."

The other problem may be with the naming/renaming of the local repository.  Master vs. Main.  I have no idea how this happened.

Thank you!

[Matt Chan]

When I encounter some mysterious cases like this, when I'm dealing with a project that involves only me, and that I'm confident my local (not remote) repo is the truth (in terms of commit history) and I just kinda need to push that to origin (remote), I just do a force push and the only commit history from my local repo is retained... This is usually a bad idea for any project tha requires collaboration, I've done so in SE-related projects BEFORE I had to share the repo for editor proofreading and publishing.

--
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/C7CABF36-06CB-46A0-9B4C-7078D7C5F0AB%40letterboxes.org.

[Genevieve Segol]

Yes, I have looked at Stackoverflow.  151 entries for "fatal: refusing to merge unrelated histories".  The proposed solutions are all over the place.  Will continue searching.  Promise :)

[Matt Chan]

Can you show a quick screenshot of remote repo log? maybe something like

git log origin/master --oneline --graph

(this will depends on what the name of your remote repo/branch is named; the format is git log <repo>/<branch>

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/fe7b1855-8c7e-4b38-8085-b686b2cf0c57n%40googlegroups.com.

[Genevieve Segol]

I did a force push as you suggested earlier, because I am 100% confident that my local repo is the master.  That worked. Thank you!

Here is the log you asked for.  I still don't understand this part:

2d9ac98 split body into chapters and basic clean

[Matt Chan]

This does look a little strange without knowing the full context, it seems that as far as the remote repo is concerned, there is only 2 commits, the initial one (2d9ac98) that split the body to chapters, and the most recent one (5b73ff4) that replaced ship semantic tags. When you do the same git log on your local branch, are there only two commits as well?

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/68b6339a-dd5c-4720-a5a6-cabbe53b0faan%40googlegroups.com.

[Genevieve Segol]

I think I messed up everything with the force push. Will start from scratch

[Matt Chan]

I'm sorry about that... Hopefully it won't be too frustrating

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/543b9661-806a-47df-9743-ae6469b4a404n%40googlegroups.com.

[Genevieve Segol]

Not your fault.  I really appreciate your trying to help.

I am going for a walk and do it again.

Live and learn :-)

[Genevieve Segol]

Trying to add the markers before splitting the file, but

sed --in-place "s|<h2|<!--se:split--><h2|g" src/epub/text/body.xhtml

returns

-bash: !--se: event not found

That was working for me before.  I checked body.xhtml:  the <h2> tags are there as expected.

Suggestions?

[Robin Whittleton]

This command was changed recently in the docs from using Perl to sed, and that doesn’t seem to work on macOS. I’ll see if I can rework it now. In the meantime, you can run the old command:

perl -pi -e "s|<h2|<\!--se:split--><h2|g" src/epub/text/body.xhtml

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/982aefb7-163d-48e6-b393-796615e14b7dn%40googlegroups.com.

[Vince Rice]

I’m guessing it needs the GNU version of sed? Brew has them, and you call it with gsed (they name all the gnu utilities with a leading g.

This is one of many reasons why I wanted to integrate that into the split-file command itself.

On Jun 12, 2021, at 4:41 AM, Robin Whittleton <ro...@reala.net> wrote:

This command was changed recently in the docs from using Perl to sed, and that doesn’t seem to work on macOS. I’ll see if I can rework it now. In the meantime, you can run the old command:

To view this discussion on the web visit https://groups.google.com/d/msgid/standardebooks/45259785-4084-4460-9C90-A189356C5FDA%40reala.net.

[Alex Cabal]

Are you redoing the entire ebook from scratch instead of fixing the
repo? Are you sure you just can't fix the repo instead and save yourself
many hours of duplicated work?

> <http://gmail.com/> <http://gmail.com/

> <http://groups.google.com/d/msgid/standardebooks/898c32f2-211e-4e19-8947-2c66e08e8466n%40googlegroups.com

> <http://groups.google.com/d/msgid/standardebooks/898c32f2-211e-4e19-8947-2c66e08e8466n%40googlegroups.com>>
>
> >
> > >>>>>
> >
> <https://groups.google.com/d/msgid/standardebooks/898c32f2-211e-4e19-8947-2c66e08e8466n%40googlegroups.com?utm_medium=email&utm_source=footer
> <https://groups.google.com/d/msgid/standardebooks/898c32f2-211e-4e19-8947-2c66e08e8466n%40googlegroups.com?utm_medium=email&utm_source=footer>
>
> >
> <https://groups.google.com/d/msgid/standardebooks/898c32f2-211e-4e19-8947-2c66e08e8466n%40googlegroups.com?utm_medium=email&utm_source=footer
> <https://groups.google.com/d/msgid/standardebooks/898c32f2-211e-4e19-8947-2c66e08e8466n%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/97ca7f38-31a1-477a-8616-e1faa1c6b055n%40googlegroups.com
> <http://groups.google.com/d/msgid/standardebooks/97ca7f38-31a1-477a-8616-e1faa1c6b055n%40googlegroups.com>
>
> >

> <http://groups.google.com/d/msgid/standardebooks/97ca7f38-31a1-477a-8616-e1faa1c6b055n%40googlegroups.com

> <http://groups.google.com/d/msgid/standardebooks/97ca7f38-31a1-477a-8616-e1faa1c6b055n%40googlegroups.com>>
>
> >
> > >>>>
> >
> <https://groups.google.com/d/msgid/standardebooks/97ca7f38-31a1-477a-8616-e1faa1c6b055n%40googlegroups.com?utm_medium=email&utm_source=footer
> <https://groups.google.com/d/msgid/standardebooks/97ca7f38-31a1-477a-8616-e1faa1c6b055n%40googlegroups.com?utm_medium=email&utm_source=footer>
>
> >
> <https://groups.google.com/d/msgid/standardebooks/97ca7f38-31a1-477a-8616-e1faa1c6b055n%40googlegroups.com?utm_medium=email&utm_source=footer
> <https://groups.google.com/d/msgid/standardebooks/97ca7f38-31a1-477a-8616-e1faa1c6b055n%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/49568ebe-2518-4711-b119-d22209354171n%40googlegroups.com
> <http://groups.google.com/d/msgid/standardebooks/49568ebe-2518-4711-b119-d22209354171n%40googlegroups.com>
>
> >

> <http://groups.google.com/d/msgid/standardebooks/49568ebe-2518-4711-b119-d22209354171n%40googlegroups.com

> <http://groups.google.com/d/msgid/standardebooks/49568ebe-2518-4711-b119-d22209354171n%40googlegroups.com>>
>
> >
> > >>>
> >
> <https://groups.google.com/d/msgid/standardebooks/49568ebe-2518-4711-b119-d22209354171n%40googlegroups.com?utm_medium=email&utm_source=footer
> <https://groups.google.com/d/msgid/standardebooks/49568ebe-2518-4711-b119-d22209354171n%40googlegroups.com?utm_medium=email&utm_source=footer>
>
> >
> <https://groups.google.com/d/msgid/standardebooks/49568ebe-2518-4711-b119-d22209354171n%40googlegroups.com?utm_medium=email&utm_source=footer
> <https://groups.google.com/d/msgid/standardebooks/49568ebe-2518-4711-b119-d22209354171n%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/338f47a9-55f8-4474-9f91-ecb7a7905b65n%40googlegroups.com
> <http://groups.google.com/d/msgid/standardebooks/338f47a9-55f8-4474-9f91-ecb7a7905b65n%40googlegroups.com>
>
> >

> <http://groups.google.com/d/msgid/standardebooks/338f47a9-55f8-4474-9f91-ecb7a7905b65n%40googlegroups.com

> <https://groups.google.com/d/msgid/standardebooks/0207e464-6dbb-4527-a55b-12cbd5beddd4n%40googlegroups.com?utm_medium=email&utm_source=footer

> <https://groups.google.com/d/msgid/standardebooks/0207e464-6dbb-4527-a55b-12cbd5beddd4n%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/fe7b1855-8c7e-4b38-8085-b686b2cf0c57n%40googlegroups.com

> <https://groups.google.com/d/msgid/standardebooks/fe7b1855-8c7e-4b38-8085-b686b2cf0c57n%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/68b6339a-dd5c-4720-a5a6-cabbe53b0faan%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/68b6339a-dd5c-4720-a5a6-cabbe53b0faan%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/543b9661-806a-47df-9743-ae6469b4a404n%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/543b9661-806a-47df-9743-ae6469b4a404n%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/982aefb7-163d-48e6-b393-796615e14b7dn%40googlegroups.com
> <https://groups.google.com/d/msgid/standardebooks/982aefb7-163d-48e6-b393-796615e14b7dn%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Genevieve Segol]

perl works.  Thank you!

[Genevieve Segol]

Alex,

Yes, I started from scratch.  I think I really messed up with a forced-push to GitHub and I don't know enough about git to fix it.  It is going faster the second time and I had kept notes of the edits in each chapter while proofreading.  And I am using the latest SE version.

Anyway, it is all my fault.  

I will take a day off after this book to improve my git skills :-)

[Matt Chan]

I'm really sorry if my suggestion to force push messed everything up... 

[François Grandjean]

Keep in mind that the whole process can be complicated if you aren’t familiar with the tools we use—and even if you are familiar with them, the whole process of producing an ebook is tricky for newbies. Hence the discussion in another thread to have documents aimed at non-programmers.

Git in particular is a very powerful tool that can help you save your work at various states so you can experiment with it and always have a backup to fall on to, but there are also ways to lose it. If you have time, I suggest you look into branches in Git and how they work. That might save you a lot of time and trouble in the future.

[Matt Chan]

So I understand if no one wanna listen to my suggestions ever again but... I have found this git tutorial about branching to be SUPER helpful

https://learngitbranching.js.org/

[Vince]

A force push could have messed up the GitHub repository (although it’s unlikely), but it couldn’t have messed up your local one. Are you sure your local one is messed up?

[François Grandjean]

Robin: the problem with the command is likely related to Bash in general and not just to macOS.

sed --in-place "s|<h2|<!--se:split--><h2|g" src/epub/text/body.xhtml won’t work because the exclamation will be expanded, but

sed --in-place 's|<h2|<!--se:split--><h2|g' src/epub/text/body.xhtml will because the single quotes will treat the exclamation as a string without any meaning for the shell.

Alternatively, sed --in-place "s|<h2|<\!--se:split--><h2|g" src/epub/text/body.xhtml will also work (same regex as the Perl one, if I’m not mistaken).

[Vince]

Well, it’s both. As I suspected earlier but didn’t have time to confirm, the command uses a parameter (--in-place) that the sed that ships with MacOS doesn’t support; you have to install gnu-sed from brew, and then use gsed instead of sed.

Alex, why was this switched from perl? That works everywhere.

[Genevieve Segol]

I get an error when building the spine

 Error  Not a Standard Ebooks source directory: /Users/gsegol/jules-verne_ticket-no-9672

The directory was built automatically at the start of the project, right at the top of my home folder, and has not given me any trouble until now.

I am wondering if this has something to do with the fact that the ebook's name includes both the author's and translator's names (e.g., jules-verne_laura-kendall_ticket-no-9672.epub).  On the other hand, I did not have that problem before (se 1.9.3), and I have not built the ebook yet.

Suggestions? Thanks.

[Asher Smith]

I don't have an answer to the question of the directory and I seem to have missed the excitement yesterday, but I just wanted to add my two cents about git: whenever I need to rebase or figure out a repository, I find it a lot easier to do with a visual interface. There's a number of git GUIs out there, and I've been using Sourcetree successfully. If you made a copy of your repo, you could probably open it up with that and see if it's salvageable. I also like it because it allows me to split out individual lines from a commit if I need to commit just a couple lines from a larger batch of changes. Most importantly, it shows you really clearly where the problems are when you have a problem like the one above.

[Genevieve Segol]

Probably the wrong guess.  I remembered that, in my previous attempt,  I had to correct urls in content.* and colophon.* after running lint to change 'jules-verne' to 'jules-verne_laura-kendall'.

I made those edits (but did not commit) and tried se build-spine . again.  The error message is the same.

[Vince]

You should specify the illustrator in the se create-draft command; it will take care of all that for you.

I don’t know what specifically causes the error (and I can’t replicate it; if I run an se command outside an SE source tree, I just get a stack trace and a complaint that it can’t find the container.xml file), but either you’re not in the top-level directory of the book, or something has gone wrong in the directory tree of the book.

Do you have all the “standard” files and directories? Do a create-draft somewhere else and make sure you have everything (all files, all directories) from that clean directory in your current project tree.

[Genevieve Segol]

Vince,

Thank you for looking into this.  I don't see anything missing in my directory (compared to the illustration provided in the step-by-step guide), and I am definitely running the command from the top of the tree.  Please see screenshots.

[Vince]

Is build-spine the only command that fails? What happens with, e.g., build-manifest?

Can you create a public repo on GitHub and push this one up so I can take a look at it?

On Jun 13, 2021, at 4:38 PM, Genevieve Segol <genevie...@gmail.com> wrote:

<Screen Shot 2021-06-13 at 14.33.27.png><Screen Shot 2021-06-13 at 14.32.43.png>Vince,

Thank you for looking into this.  I don't see anything missing in my directory (compared to the illustration provided in the step-by-step guide), and I am definitely running the command from the top of the tree.  Please see screenshots.<Screen Shot 2021-06-13 at 14.31.54.png>

[Vince]

Also, are you current on the se tools? What does se --version say?

[Genevieve Segol]

Yes, build-spine is the only command that fails.  So far, everything has done smoothly.

I have a public repo here that contains all the commits through "Add titles".  Given my recent adventure with git/GitHub, I am pretty cautious with the commits, but I can commit the "Add manifest and spine" in spite of the error if you want.

https://github.com/gsegol/jules-verne_ticket-no-9672

Se version 2.0.1

Thanks again for your help.

[Vince]

I cloned it and build-spine works perfectly here. So whatever is wrong, it would appear to only be on your local copy.

Maybe Alex will poke his head in and have some more detail about what might cause the error. As I said, I haven’t been able to make it happen even when running build-spine on a “bad” (non-SE) directory tree.

-- 
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/a5ceacdd-7c3f-449e-a4f4-b461bddb8167n%40googlegroups.com.

[Genevieve Segol]

So, should I move on (commit and continue), and hope to fix this when running se lint later?

Many. thanks.

[Vince]

Since I don’t know what the error is or what’s causing it, I have no way to answer that. Sorry!

What does a git status show?

Something else you can do is:

1. Make a backup of your repository, i.e. copy the entire directory tree to another place.
2. On the copy (not your original), get rid of your local changes and see if build-spine works. (You can search for how to do that.)
3. If it doesn’t, undo your last commit and try it again. (Ditto.)
4. Keep doing that until build-spine works.
5. At whatever point it works, you know where things went wrong, and you can try to look at the differences in your master copy to see what changed.

[Genevieve Segol]

I cloned the gitHub repo locally, which brings me back to the "Add titles" commit.  I repeated  the se build-manifest and build-spine commands.  Same error.  

I removed the repo and cloned it again.  Then I did the two commands in the opposite order:  se build-spine and then se build-manifest.  This time I don't get the error.  If the two processes are independent, the order should not matter, but are they?

[Emma Sweeney]

It looks like the toc.xhtml is missing.

Emma

[Genevieve Segol]

Emma,

According to the step-by-step guide, I would build the toc after the manifest and the spine.

[Genevieve Segol]

Are you saying that I should have a placeholder file?  

[Emma Sweeney]

When you build an epub skeleton it should come with a toc file. se build-toc only changes the inside of that file with information from the content.opf's spine.

Emma

[Genevieve Segol]

Well, it is not there, and I certainly did not remove it intentionally.  I will try adding tis file. Still very strange.

Thank you.

[Emma Sweeney]

If the file wasn't built this might mean there are other issues that are not as visible with your current epub skeleton. This may be why you are getting the error (Error: Not a Standard Ebooks source directory).

Emma

[Vince]

The create-draft command does load a template toc file. This is why I said do a create-draft and then compare the files in that fresh copy to yours. You should have seen the difference then.

However, that doesn’t prevent the build-spine command from working, at least for me. (Interestingly, though, deleting the toc file and then trying to regen it gives an error that the file doesn’t exist. Alex, does that not work, i.e. can build-toc not build a file from scratch?)

But let’s go back to this.

I cloned the gitHub repo locally, which brings me back to the "Add titles" commit.  I repeated  the se build-manifest and build-spine commands.  Same error.  

I cloned your repo. The git history looks like this:

* d4dce5f 2021-06-12 22:34:31 | Add titles (HEAD -> main, origin/main, origin/HEAD) [gsegol]

* 5af0eaf 2021-06-12 22:28:47 | corrected quotes in newspaper tag [gsegol]

* 124082d 2021-06-12 22:14:22 | [Editorial] Modernize hyphenation and spelling [gsegol]

* 0523865 2021-06-12 17:20:25 | Semanticate [gsegol]

* dabd4ff 2021-06-12 10:55:19 | Typogrify [gsegol]

* 09444f6 2021-06-11 21:25:08 | Initial commit [gsegol]

I then ran both build-manifest and build-spine, using 2.0.1 of the tools, without any errors.

If you cloned the repo to a fresh directory and still get the error in that fresh copy, then that would seem to point to something besides the repo being the problem.

Whoa. I just ran the commands a second time, and got the error. Which would imply that the commands themselves did something the first time that caused the error. Give me a few minutes…

[Alex Cabal]

build-toc will create a toc file if it doesn't exist

On 6/13/21 9:43 PM, Vince wrote:
> The create-draft command does load a template toc file. This is why I
> said do a create-draft and then compare the files in that fresh copy to
> yours. You should have seen the difference then.
> However, that doesn’t prevent the build-spine command from working, at
> least for me. (Interestingly, though, deleting the toc file and then
> trying to regen it gives an error that the file doesn’t exist. Alex,
> does that not work, i.e. can build-toc not build a file from scratch?)
>
> But let’s go back to this.
>> I cloned the gitHub repo locally, which brings me back to the "Add
>> titles" commit.  I repeated  the se build-manifest and build-spine
>> commands.  Same error.
>
> I cloned your repo. The git history looks like this:
>
> * d4dce5f 2021-06-12 22:34:31 | Add titles (HEAD -> main,
> origin/main, origin/HEAD) [gsegol]
> * 5af0eaf 2021-06-12 22:28:47 | corrected quotes in newspaper tag
> [gsegol]
> * 124082d 2021-06-12 22:14:22 | [Editorial] Modernize hyphenation
> and spelling [gsegol]
> * 0523865 2021-06-12 17:20:25 | Semanticate [gsegol]
> * dabd4ff 2021-06-12 10:55:19 | Typogrify [gsegol]
> * 09444f6 2021-06-11 21:25:08 | Initial commit [gsegol]
>
>
> I then ran both build-manifest and build-spine, using 2.0.1 of the
> tools, without any errors.

> If /you/ cloned the repo to a fresh directory and still get the error in

> that fresh copy, then that would seem to point to something besides the
> repo being the problem.
>
> Whoa. I just ran the commands a second time, and got the error. Which
> would imply that the commands themselves did something the first time
> that caused the error. Give me a few minutes…
>

> --
> 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/768E8DDD-9FF7-4ED5-BF1C-DA53A1E1634E%40letterboxes.org
> <https://groups.google.com/d/msgid/standardebooks/768E8DDD-9FF7-4ED5-BF1C-DA53A1E1634E%40letterboxes.org?utm_medium=email&utm_source=footer>.