[Plugin] KindleImport Sigil plugin - Page 3

JSWolf · 10-01-2014, 01:07 PM

If the Mobi was split at the chapter sections, then it would be a lot easier to fix the mess that left (because it's Mobi, there will be a mess).

DiapDealer · 10-01-2014, 01:24 PM

Not going to happen. Why do you think Sigil has a splitting feature built in to it?

KF8 are usually (but not always) split into individual "flows" as part of its structure. Some times they will come out of Kindle(Import|Unpack) as one big file too. Mobis are always one big flow. And I'm just not interested in parsing an ncx--if one is present--to find "chapter" breakpoints (or heuristically guess where they should be if there IS no ncx). Especially when Sigil already provides an easy way to do so.

varlog · 10-01-2014, 04:21 PM

Quote:

Originally Posted by DiapDealer

@varlog
I'm not convinced that something might not break with the filename experimentation I've done (it's actually incomplete on the KF8 side of things in this beta), but let me know what you think.

Well, ok, it is second choice.
It works in my environment, for my samples. Still, my prefered solution would be BookName. Don't feel pressed if you don't want to be

. It is just that I know it is possible because of my cascading script I've done for DGSM. I guess AA is to blame...
The linking issue "name" versus "id" is still there... Some input on it?

varlog · 10-01-2014, 04:40 PM

Quote:

Originally Posted by user_none

That is correct. You should have been clearer about the reason for the patch. The patch itself would still have been rejected. You shouldn't check for special dir names in the path. The proper solution is to expose a clear_save_name function from MainWindow and have plugin runner call this after loading the book.

It was one of my first ideas but I thought it would be too much interference in MainWindow code (new public function!). Don't bother to answer. I'll propose something new and then, if appropriate, again

. Will take some time because I'm on the road again.

JSWolf · 10-01-2014, 04:50 PM

Quote:

Originally Posted by DiapDealer

Not going to happen. Why do you think Sigil has a splitting feature built in to it?

KF8 are usually (but not always) split into individual "flows" as part of its structure. Some times they will come out of Kindle(Import|Unpack) as one big file too. Mobis are always one big flow. And I'm just not interested in parsing an ncx--if one is present--to find "chapter" breakpoints (or heuristically guess where they should be if there IS no ncx). Especially when Sigil already provides an easy way to do so.

How about just replacing the Mobi pagebreak with the Sigil split mark then we can do with it as we want. I think that would work rather well. Then you don't have to do any extra parsing/building except for this one search/replace.

DiapDealer · 10-01-2014, 04:52 PM

Quote:

Originally Posted by JSWolf

How about just replacing the Mobi pagebreak with the Sigil split mark then we can do with it as we want. I think that would work rather well. Then you don't have to do any extra parsing/building except for this one search/replace.

In short: no.

DiapDealer · 10-01-2014, 05:15 PM

Quote:

Originally Posted by varlog

Well, ok, it is second choice.
It works in my environment, for my samples. Still, my prefered solution would be BookName. Don't feel pressed if you don't want to be

. It is just that I know it is possible because of my cascading script I've done for DGSM. I guess AA is to blame...

I think it's all kind of moot now anyway. There's currently a bug where clicking "Save" immediately after the import plugin finishes causes a Sigil error. The fix for the bug is going to wiping any existing filename before the final handoff to Sigil. It will truly be out of the plugin developer's hands at that point out "untitled.epub" is what it's going to be. Sorry.

Quote:

The linking issue "name" versus "id" is still there... Some input on it?

I'm not parsing KF8 books in any further way. What comes out of KindleUnpack is what gets handed to Sigil. And that particular Kindlebook's markup just happpened to use "name" instead of "id". Doing a quick replace of all instances of <a name= with <a id= in a Sigil S&R made all the links work again your test case.

Again... nine times out of ten, people ARE going to have work to do after this input plugin finishes. I never intended it to be a new two-step Import--and then Save As--Kindlebook to epub converter.

Maybe some new Sigil Edit plugins could be written to take up the cause of automating some of these fixes you guys are looking for.

varlog · 10-01-2014, 05:35 PM

Quote:

Originally Posted by DiapDealer

I think it's all kind of moot now anyway. There's currently a bug where clicking "Save" immediately after the import plugin finishes causes a Sigil error. The fix for the bug is going to wiping any existing filename before the final handoff to Sigil. It will truly be out of the plugin developer's hands at that point out "untitled.epub" is what it's going to be. Sorry.

I know at least one way to avoid it. Will try my best.

Quote:

I'm not parsing KF8 books in any further way. What comes out of KindleUnpack is what gets handed to Sigil. And that particular Kindlebook's markup just happpened to use "name" instead of "id". Doing a quick replace of all instances of <a name= with <a id= in a Sigil S&R made all the links work again your test case.

Again... nine times out of ten, people ARE going to have work to do after this input plugin finishes. I never intended it to be a new two-step Import--and then Save As--Kindlebook to epub converter.

Maybe some new Sigil Edit plugins could be written to take up the cause of automating some of these fixes you guys are looking for.

thanks... is it really not apparent in markup that the guys meant "id", not "name"?.

varlog · 10-01-2014, 05:52 PM

Quote:

Originally Posted by JSWolf

How about just replacing the Mobi pagebreak with the Sigil split mark then we can do with it as we want. I think that would work rather well. Then you don't have to do any extra parsing/building except for this one search/replace.

As I understand it Mobi pagebreak is not really what we would like to have as file breake . Imagine book with thousand pages

. We would like Chapter brake. Is there something like Chapter break in Mobi?
Just inserting Sigil split mark should not make it necessary to parse all links again?

DiapDealer · 10-01-2014, 06:04 PM

No. There is no specific "this is where a chapter break occurs" markup in a traditional mobi.

Quote:

Originally Posted by varlog

thanks... is it really not apparent in markup that the guys meant "id", not "name"?.

Sorry, I sometimes forget that these things aren't common knowledge.

"name" was deprecated a while back and is succeeded by "id". But it often still "works" in many environments even though it's not supposed to be used any more. Apparently, Qt5's Webkit is not one of those environments.

varlog · 10-01-2014, 06:09 PM

Quote:

Originally Posted by DiapDealer

No. There is no specific "this is where a chapter break occurs" markup in a traditional mobi.

@JSWolf
there you are

.

varlog · 10-01-2014, 06:12 PM

Quote:

Originally Posted by DiapDealer

Sorry, I sometimes forget that these things aren't common knowledge.

"name" was deprecated a while back and is succeeded by "id".

why KindleUnpack stays obsolete than

?

DiapDealer · 10-01-2014, 06:21 PM

Quote:

Originally Posted by varlog

why KindleUnpack stay obsolete than

?

Because KindleUnpack is striving to preserve the original markup as much as possible. It's a "revealer," not a "fixer." The ebook creator used "name" so KindleUnpack revealed "name."

And the mobi page-break could be the closest thing to a chapter break. It would probably come close to working if split (or marked) at those tags. I'm just not interested in doing so.

varlog · 10-01-2014, 06:28 PM

Quote:

Originally Posted by DiapDealer

Because KindleUnpack is striving to preserve the original markup as much as possible. It's a "revealer," not a "fixer." The ebook creator used "name" so KindleUnpack revealed "name."

And the mobi page-break could be the closest thing to a chapter break. It would probably come close to working if split (or marked) at those tags. I'm just not interested in doing so.

That is perfectly reasonable and understandable explanation.
I'm have my future teller hat on me now:
This topic will come again

.

blackest · 10-04-2014, 08:39 PM

Good work with kindle import

I had to apt-get install python-tk but the plugin told me that so not an issue

spliting at chapters is pretty easy really

find

<blockquote>
<span class="rule_9"

replace

<hr class="sigil_split_marker" /> <blockquote>
<span class="rule_9" 

replace all , job done. your book may vary.
but you just need to find what the start of a chapter looks like.

10-01-2014, 01:24 PM	#32
DiapDealer Grand Sorcerer Posts: 28,627 Karma: 204624552 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Not going to happen. Why do you think Sigil has a splitting feature built in to it? KF8 are usually (but not always) split into individual "flows" as part of its structure. Some times they will come out of Kindle(Import\|Unpack) as one big file too. Mobis are always one big flow. And I'm just not interested in parsing an ncx--if one is present--to find "chapter" breakpoints (or heuristically guess where they should be if there IS no ncx). Especially when Sigil already provides an easy way to do so. Last edited by DiapDealer; 10-01-2014 at 03:23 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Plugin] PunctuationSmarten Sigil plugin	DiapDealer	Plugins	143	07-30-2025 06:58 AM
[Plugin] ePub3-itizer - epub3 output plugin for Sigil	KevinH	Plugins	457	05-28-2025 06:14 PM
epubcheck plugin for Sigil	Doitsu	Plugins	539	04-19-2025 08:45 AM
kindlegen plugin for Sigil	Doitsu	Plugins	173	10-15-2024 02:51 AM
smoothRemove_v010 plugin for Sigil	kbanelas	Plugins	15	01-27-2017 05:51 PM

10-01-2014, 01:07 PM	#31
JSWolf Resident Curmudgeon Posts: 79,796 Karma: 146391129 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	If the Mobi was split at the chapter sections, then it would be a lot easier to fix the mess that left (because it's Mobi, there will be a mess).

10-04-2014, 08:39 PM	#45
blackest Connoisseur Posts: 67 Karma: 10 Join Date: Sep 2014 Device: sony prs 2	Good work with kindle import I had to apt-get install python-tk but the plugin told me that so not an issue spliting at chapters is pretty easy really find <blockquote> <span class="rule_9" replace <hr class="sigil_split_marker" /> <blockquote> <span class="rule_9"  replace all , job done. your book may vary. but you just need to find what the start of a chapter looks like.

Advert

Advert