No identifier causes delay in View and Edit Book - Page 2

eschwartz · 05-30-2014, 07:31 PM

But it's all right, turns out I was right -- calibre does need prefixes. The prefix is "http:" which isn't a known prefix.

BetterRed · 05-30-2014, 09:20 PM

Where's my 'yawn' smiley gone. How does you being 'right' solve the OPs problem - excessive times to open an epub in the viewer & editor.

BR

MerlinMama · 06-02-2014, 07:03 PM

Sorry, I've been ill and away from computer. Initial problem...long time to open viewer and editor. I was adding personal books (that I wrote), which were converted to epub using an online converter. I was then adding them, so nothing in the id file. It was taking forever to open. Since the regular ebooks I've added (and a few fanfics) had something in the 'id' box, be it ISBN or the url where the fanfic came from, I added a link to one of my websites. This 'seemed' to stop the lag...until the next day when it became even longer.

I've since seen that I can either add the 'url' prefix before the http and that works...but whatever the initial problem was, it's gone, even after I cleared the field and it was fine. THEN it started to lag again when opening editor, and I noticed that even though I did a check book and save before closing it earlier, when I reopened, there were additional tags put in. I've done my best to fix that up (and I have no more to add which helps), and now all files open normally.

All that (whew tired of typing) to say, still not sure what caused the initial lag, because the last 3 I added were just fine, no lags at all. Hopefully it was just a clash with something and it won't happen again.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Can I view from the Edit Metadata screen?	Opus97	Library Management	1	11-16-2012 08:07 PM
replace in book view changes view to code view	cybmole	Sigil	4	10-28-2012 01:20 PM
Sigil highlight Book View No Longer Shows in Code View	Themus	Sigil	4	10-04-2012 07:54 PM
Can I edit (or even view) .txt files imported from sdcard?	Dragginz	enTourage Archive	6	06-30-2010 02:18 PM
one cover in edit meta, another in library view	Debby	Calibre	13	05-16-2010 05:32 PM

05-30-2014, 07:31 PM	#16
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	But it's all right, turns out I was right -- calibre does need prefixes. The prefix is "http:" which isn't a known prefix.

05-30-2014, 09:20 PM	#17
BetterRed null operator (he/him) Posts: 21,732 Karma: 29711016 Join Date: Mar 2012 Location: Sydney Australia Device: none	Where's my 'yawn' smiley gone. How does you being 'right' solve the OPs problem - excessive times to open an epub in the viewer & editor. BR

06-02-2014, 07:03 PM	#18
MerlinMama Evangelist Posts: 498 Karma: 32554 Join Date: May 2014 Location: Canada Device: Kobo Sage	Sorry, I've been ill and away from computer. Initial problem...long time to open viewer and editor. I was adding personal books (that I wrote), which were converted to epub using an online converter. I was then adding them, so nothing in the id file. It was taking forever to open. Since the regular ebooks I've added (and a few fanfics) had something in the 'id' box, be it ISBN or the url where the fanfic came from, I added a link to one of my websites. This 'seemed' to stop the lag...until the next day when it became even longer. I've since seen that I can either add the 'url' prefix before the http and that works...but whatever the initial problem was, it's gone, even after I cleared the field and it was fine. THEN it started to lag again when opening editor, and I noticed that even though I did a check book and save before closing it earlier, when I reopened, there were additional tags put in. I've done my best to fix that up (and I have no more to add which helps), and now all files open normally. All that (whew tired of typing) to say, still not sure what caused the initial lag, because the last 3 I added were just fine, no lags at all. Hopefully it was just a clash with something and it won't happen again.