This usually happens when a tag is closed incorrectly or in an
unexpected order. se clean will run everything into one line because the
xml/xhtml is not correctly structured.
> times, where a* linefeed* and *tab* in the xhtml file is replaced with a
> space only, so the all text
> ends up on a single line. When I run *se lint, *it**doesn't seem to
> pick**up an error, and I do run *se clean* frequently. The only way for
> me to find the issue is to manually inspect each *xhtml *file in BBEdit
> or on Github, which I've been doing before I declare the production
> complete. I guess the same thing can happen with the *content.opf* file
> as well, so I will manually check this as well from now on.
> At any rate, I think I've taken care of all the issues, Weijia. Thanks
> On Sunday, June 4, 2023 at 7:08:35 AM UTC-6 Weijia Cheng wrote:
> Ok, I got to review again and the changes are looking good, except
> the formatting for content.opf became jumbled in this commit
>. I am not sure what you did to break it but you might want to revert that commit and try fixing content.opf again.
> On Saturday, June 3, 2023 at 9:45:54 AM UTC-7 Norman Walz wrote:
> Thanks's Robin. I going to practice this rebasing stuff on a
> test Github repo.
> On Friday, June 2, 2023 at 10:24:57 PM UTC-6 Robin Whittleton wrote:
> For the future, you can configure git to use your editor of
> choice rather than vim:
>> On 3 Jun 2023, at 01:16, Norman Walz <ncwm...@gmail.com
>> Well I found the attempt at changing the commit message
>> using vim fairly frustrating. Probably should have stuck
>> it out longer, but after
>> several hours I decided to simply create a revised
>> repository here:
> 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