02-15-2019, 04:41 PM | #1 |
Wizard
Posts: 1,539
Karma: 6613969
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
|
Something weird is happening when I want to build an Index
I don't know if is a bug of Sigil or something I'm doing wrong. The following is a picture of my "Book Browser View" BEFORE building an Index:
As you can see, the order of the files is: Cover, Sinopsis, Titulo, Dedicatoria, TDC, Introduccion, Prefacio, Seccion_01, etc. And this is the picture (of my "Book Browser View") AFTER building the Index: Now the order of the files is: Dedicatoria, Introduccion, Prefacio, Sinopsis, Título, cover, TdC, Seccion_01, etc. The question is: why is that happening? That is happening even with a blank index. EDIT: I'm using Sigil 0.9.10 and Windows 7 x64. Last edited by RbnJrg; 02-15-2019 at 04:44 PM. |
02-15-2019, 04:48 PM | #2 |
Sigil Developer
Posts: 7,630
Karma: 5433388
Join Date: Nov 2009
Device: many
|
Please open the content.opf in a code view tab and snap pictures of the manifest and spine tags (so we can see the order as specified in the spine) both before and after creating the index.
That may give us some hint as to what is going on. |
02-15-2019, 05:44 PM | #3 |
Grand Sorcerer
Posts: 5,583
Karma: 22735033
Join Date: Dec 2010
Device: Kindle PW2
|
I was able to reproduce this issue with a commercial epub2 book (Crichton, Michael - Dragon Teeth, Harper Collins, 2017). I simply opened the book and selected Tools > Index > Create Index.
The original order of the first 4 XHTML files in the Book Browser was: cover.html title.html copyright.html contents.html original spine Spoiler:
after selecting Create Index the Book Browser order was changed to: contents.html cover.html title.html copyright.html updated spine Spoiler:
I.e., the Book Browser display doesn't match the actual spine. Also the spine reference of the item that was moved to the first position (<itemref idref="toc"/>) was deleted. The cover image spine entry (<itemref idref="my-html-cover" linear="yes"/>) was also deleted. content.opf contained the following guide section: Code:
<guide> <reference type="cover" title="Cover" href="Text/cover.html"/> <reference type="toc" title="Contents" href="Text/contents.html"/> <reference type="text" title="Start" href="Text/title.html"/> </guide> @RbnJrg If your guide section contains entries, please temporarily remove them for testing purposes, before selecting Create Index and report back whether this makes a difference. EDIT: You can also use this MR book by GrannyGrump to reproduce this issue. Last edited by Doitsu; 02-15-2019 at 05:53 PM. |
02-15-2019, 05:55 PM | #4 |
Grand Sorcerer
Posts: 27,546
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Crap. I see it on Linux as well. Why do people always seem to find stuff immediately after I tag the source for a new release?
Although the opf and toc will flip in the Book Browser if one of them is highlighted when creating the index, that's just cosmetic. The elements that are being reordered in the spine seems to be limited to those items that are also guide elements (semantics). EDIT: I see that Doitsu also figured out the Guide connection. |
02-15-2019, 06:14 PM | #5 | |
Grand Sorcerer
Posts: 27,546
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
I'm starting at:
Quote:
We need to start linking changelog entries to commits/issues/forum threads, I think. |
|
02-15-2019, 06:31 PM | #6 | |
Wizard
Posts: 1,539
Karma: 6613969
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
|
Quote:
Spoiler:
And these are the <manifest> and <spine> tags after creating the index: Spoiler:
I can watch the content of the <spine> changed drastically. |
|
02-15-2019, 06:45 PM | #7 |
Wizard
Posts: 1,539
Karma: 6613969
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
|
Yes, I confirm Doitsu's words; after deleting the entries of the guide section, the bug disappears.
|
02-15-2019, 07:32 PM | #8 |
Sigil Developer
Posts: 7,630
Karma: 5433388
Join Date: Nov 2009
Device: many
|
An alternative work-around that will work correctly without removing the guide entries is to do the following:
1. Create a new empty html page. It will get appended to the end of the spine 2. Rename it to whatever you want to call the index. 3. Use the context menu button to set Semantics on that newly created html file and set it as the index. Then go ahead and create the index. It should find the "index" you created and marked and replace it with the new index and nothing in the spine should be changed. Sorry about that. We are testing a bug fix right now that will appear in the next release hopefully this weekend or soon after. Thank you for your bug report! KevinH Last edited by KevinH; 02-15-2019 at 07:51 PM. |
02-15-2019, 07:59 PM | #9 | |
Wizard
Posts: 1,539
Karma: 6613969
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
|
Quote:
|
|
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Weird Things Happening | Ellachanted | Calibre | 3 | 01-03-2014 10:50 AM |
Index: Making a linked index in epub | virtual_ink | ePub | 21 | 10-19-2011 11:23 PM |
Not too sure what is happening here ... | GeoffC | Calibre | 10 | 05-19-2011 11:07 AM |
Speakin' of weird: Linux build eating accented chars. | Hitch | Sigil | 2 | 12-17-2010 01:24 PM |
The Lost Symbol -- WEIRD HAPPENING | Neil | Deals and Resources (No Self-Promotion or Affiliate Links) | 70 | 09-30-2009 07:53 PM |