[Tex2002ans]

Originally Posted by KevinH

One last question since I do not use calibre ... does clicking in their Preview make CodeView sync to the same place and visa-versa like Sigil does?

Yep. Just like Sigil.

A click in Preview jumps you to exact location in Code View.

Side Note: Calibre also has 2 helpful buttons below Preview:

• "Disable auto-reload of Preview"
• "Disable syncing of preview position to editor position"

(I have whatever the defaults are... both of those buttons are off.)

Originally Posted by KevinH

And if so, what happens if you try to sync from Preview to CodeView when Preview is cached during the merge time window, before the updating message comes up?

Okay. I just tried it.

When you:

1. Merge

2. Press into Code View.

Preview says "Loading preview, please wait..." for a few seconds. Everything works great and is responsive the entire time.

When you:

1. Merge

2. Press into Preview.

Calibre stuttered a little bit. When I tried to scroll or click around in Preview, it wouldn't work, and neither would Code View (or the entire Calibre window). But within ~6 seconds, it recreated another Preview and everything was back to normal.

Originally Posted by KevinH

Also does calibre properly test all files to be merged to check if well-formed *before* starting the merge and giving you a chance to abort before the merge?

Looks like it just auto-corrects with no acknowledgement.

I went into Chapter2.html and busted one of the tables by removing the closing </tr></table>:

Spoiler:

 <table class="bdr" summary="0" width="100%">
    <colgroup>
      <col width="30%"/>
      <col width="40%"/>
      <col width="30%"/>
    </colgroup>

    <tr valign="middle">
      <td>Joseph R. Peden, Publisher</td>

      <td class="center">Washington Editor, Karl Hess</td>

      <td class="right">Murray N. Rothbard, Editor</td>
    </tr>

    <tr valign="middle">
      <td id="ch_2">VOL. I, NO. II</td>

      <td class="center">APRIL 15, 1969</td>

      <td class="right">35¢</td>
    </tr>          <---- Removed
  </table>         <---- Removed
  
    <h2 class="cts" id="ch_2_1">Tax Day</h2>

[... All of Chapter 2's code...]

and Calibre's merge silently "corrected" + shoved it at the very end of "Chapter2.html"'s code:

Spoiler:

[... All of Chapter 2's code...]

<table class="bdr" summary="0" width="100%">
    <colgroup>
      <col width="30%"/>
      <col width="40%"/>
      <col width="30%"/>
    </colgroup>

    <tbody><tr valign="middle">
      <td>Joseph R. Peden, Publisher</td>

      <td class="center">Washington Editor, Karl Hess</td>

      <td class="right">Murray N. Rothbard, Editor</td>
    </tr>

    <tr valign="middle">
      <td id="ch_2">VOL. I, NO. II</td>

      <td class="center">APRIL 15, 1969</td>

      <td class="right">35¢</td>
 

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

</tr></tbody></table>

so in the final merge, you had:

- Chapter1's HTML
- Chapter2's HTML
--- With busted <table> removed from location, placed at end before Chapter3, and corrected.
- Chapter3's HTML

Originally Posted by KevinH

Does it check for duplicate or missing url fragments in all files and give you a chance to abort before starting the merge?

Looks as if it regenerates new ids if needed.

Like I gave it 3 chapters with the same:

<p class="footnote"><a href="#ft.ast1" id="fn.ast1">[*]</a> [...] </p>

and Calibre's merge auto-updated to:

<p class="footnote"><a href="#ft.ast1" id="fn.ast1">[*]</a> [...] </p>
<p class="footnote"><a href="#ft.ast1_1" id="fn.ast1_1">[*]</a> [...] </p>
<p class="footnote"><a href="#ft.ast1_2" id="fn.ast1_2">[*]</a> [...] </p>

I believe it silently does everything, no warnings. (Although I'm no expert in Calibre's innards... I don't usually feed it mangled code. :P)

And on non-existent/duplicate IDs. No, Calibre doesn't warn about those on merge. It only warns about them when you Tools > Check Book (F7) (similar to an epubcheck) or look in the Reports.

Originally Posted by KevinH

Right now Sigil is checking for well-formed before, during, and after which seems to be a bit of overkill since testing just before should be enough. That should make for a simple speedup.