How to make Sigil live (in calibre)

[DrChiper]

Originally Posted by theducks

Exactly
Set the cursor on class="calibre29" and right click Goto Link or class

Amazingly, I've never ever knew that this existed. Oh well, RTFM.

What I do use a lot is the "delete unused stylesheet classes" option just to trim hugely cluttered stylesheets to make them more manageable.

[GRiker]

Kovid, I'm seeing an error when opening a file on my desktop under OS X:

calibre, version 1.13.0
ERROR: Failed to open book: Failed to open book, click Show details for more information.

Traceback (most recent call last):
File "site-packages/calibre/gui2/tweak_book/job.py", line 34, in run
File "site-packages/calibre/gui2/tweak_book/boss.py", line 38, in get_container
File "site-packages/calibre/ebooks/oeb/polish/container.py", line 1077, in get_container
File "site-packages/calibre/ebooks/oeb/polish/container.py", line 830, in __init__
File "site-packages/calibre/ebooks/oeb/polish/container.py", line 136, in __init__
InvalidBook: Could not locate opf file: u'/private/var/folders/jv/z9ntx89x53lbh83qw3qy410r0000gn/T/calibre_1.13.0_tmp_cMk1T2/xPPNqg/00000-y8nSVU/OEBPS/content.opf'

This is a very simple epub created with Sigil. I cracked open the package to confirm that content.opf is in fact in the OEBPS folder (it is).

Shall I send you a copy of the file?

G

[theducks]

Originally Posted by DrChiper

Amazingly, I've never ever knew that this existed. Oh well, RTFM.

What I do use a lot is the "delete unused stylesheet classes" option just to trim hugely cluttered stylesheets to make them more manageable.

A definate with the corporate 'Master' stylesheet.
Recently: 3100 lines -> 130 lines that were in use

[DrChiper]

Originally Posted by theducks

Recently: 3100 lines -> 130 lines that were in use

I bet that most of those 130 remaining where just small variations of otherwise 99% identical classes. Yesterday I reduced one stylesheet to just about 10 useful classes ...

However, just be warned: sometimes the stylesheet is not well formed either. I had several cases that a semi-colon was missing, so some classes were not properly recognized, hence removed but still used.

[mrmikel]

FWIW, I get this error when opening in the terminal box that stays open:
Failed to initialize plugin: u'C:\\Users\\Mike\\AppData\\Roaming\\calibre\\plug i
ns\\eReader PDB 2 PML.zip'
Traceback (most recent call last):
File "site-packages\calibre\customize\ui.py", line 567, in initialize_plugins
File "site-packages\calibre\customize\ui.py", line 53, in load_plugin
File "site-packages\calibre\customize\zipplugin.py", line 188, in load
File "site-packages\calibre\customize\zipplugin.py", line 282, in _locate_code

InvalidPlugin: The plugin in u'C:\\Users\\Mike\\AppData\\Roaming\\calibre\\plug i
ns\\eReader PDB 2 PML.zip' is invalid. It does not contain a top-level __init__.
py file

It doesn't stop anything.

[kovidgoyal]

@mrmikel: Saving is an asynchronous process (this is because Tweak Book supports both epub and azw3 and saving azw3 is slow, because the book has to be rebuilt). So a traditional save as would not work well. However, I could implement a save copy as which will save the copy in the background at the state you are in while you can continue to work on the book. Will that work for you?

Regrading your error, it is because you have a broken plugin installed, uninstall it from calibre, and the error will go away.

@GRiker: Might be something OS X specific (I have really only tested Tweak Book on my linux dev machine so far) but send me the book anyway.

[mrmikel]

Any save as would work for me, since it would be more or less precautionary in case my great idea turned out to be not so great.

The recovery from global search and replace is exceedingly valuable. Things go along so well for a while then one gets a really bright idea and tries it quickly...too quickly.

I will check the error message and see if I can get rid of the plug in.

One useful thing that Sigil does in its book view is it allows you to join broken paragraphs just by deleting everything in between on the screen. That is not something that is available in code view. I am not sure there is an answer for this with this program...maybe there shouldn't be given the unpredictable skill level that could knock out things worth keeping. But I thought I would mention it.

But this is not a high priority item considering the tremendous demands on your time.

One other item I ran across today that is not really an issue with the program is the fact that it seems to be epub3 compatible, rather than epub2. Since most devices are epub2 still and will be for a while, is there any chance of a right click open with command so it could be spun out into something that would display in the more limited epub2 vocabulary.

I got an svg example that I put into this program and it displayed image and text great. But older devices do not display the image at all, so it would be nice if I could be alerted if this were the case. This too is not high priority, but I mention it so you can be aware of a potential issue.

This is program for the future, whereas Sigil will be stuck in the past, so it may not be an issue at all.

[kovidgoyal]

@mrmikel: Book view type operations are not really possible here. For that, someone would have to implement book view. As for the preview panel displaying svg, it is basically the same as calibre's ebook viewer, it will display anything the viewer is capable of displaying. Trying to restrict the viewer to device specific limitations is way too much work, since those limitations vary across devices and across time.

[kovidgoyal]

@Griker: No need to send me a book, I think I know what the problem is, it is caused by OS X's use of symlinks for /tmp

I will implement a fix when I have some time to work on OS X.

EDIT: Fix committed, if you run from source, it should work.

[jbacelar]

This is going very well. I like.

[mrmikel]

I understand entirely.

Are you considering implementing the clips or spellcheck features of Sigil? The clips feature is a desirable one and the ability to fix multiple spelling errors at once is also nice. The latter, as I recall in Sigil development, took quite a bit of time to get right.

[kovidgoyal]

Spell check is on my TODO list.

Clips and various other editor niceties like auto-indent, auto-complete and so on are on my nice-to-have but only get to after the basic functionality is in place. I have been neglecting mainline calibre development working on this for the past few weeks, so I am focusing on getting it done and out the door asap for the moment.

Of course, people are welcome to contribute code to add in their favorite features.

[GRiker]

Originally Posted by kovidgoyal

@Griker: No need to send me a book, I think I know what the problem is, it is caused by OS X's use of symlinks for /tmp

I will implement a fix when I have some time to work on OS X.

EDIT: Fix committed, if you run from source, it should work.

I updated my source, but I'm still seeing the error:

calibre, version 1.13.0
ERROR: Failed to open book: Failed to open book, click Show details for more information.

Traceback (most recent call last):
  File "site-packages/calibre/gui2/tweak_book/job.py", line 34, in run
  File "site-packages/calibre/gui2/tweak_book/boss.py", line 38, in get_container
  File "site-packages/calibre/ebooks/oeb/polish/container.py", line 1077, in get_container
  File "site-packages/calibre/ebooks/oeb/polish/container.py", line 830, in __init__
  File "site-packages/calibre/ebooks/oeb/polish/container.py", line 136, in __init__
InvalidBook: Could not locate opf file: u'/private/var/folders/jv/z9ntx89x53lbh83qw3qy410r0000gn/T/calibre_1.13.0_tmp_0Apdef/3R30jF/00000-f5XDAy/OEBPS/content.opf'

G

[kovidgoyal]

Works for me on my OS X machine. Are you sure you are running from updated source?

In particular, see this commit: https://github.com/kovidgoyal/calibr...6f6487193ff255

In fact looking at that traceback, your line numbers dont match, up. Line 830 should be line 836 in the current source

[GRiker]

Originally Posted by kovidgoyal

Works for me on my OS X machine. Are you sure you are running from updated source?

In particular, see this commit: https://github.com/kovidgoyal/calibr...6f6487193ff255

In fact looking at that traceback, your line numbers dont match, up. Line 830 should be line 836 in the current source

My mistake - I had updated my source, but I had not exported my path to CALIBRE_DEVELOP_FROM in the terminal window.

It works.

G