10-01-2014, 01:07 PM | #31 |
Resident Curmudgeon
Posts: 75,244
Karma: 133361584
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-01-2014, 01:24 PM | #32 |
Grand Sorcerer
Posts: 27,718
Karma: 196949708
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. |
Advert | |
|
10-01-2014, 04:21 PM | #33 | |
actually it is /var/log
Posts: 341
Karma: 2994236
Join Date: Sep 2012
Location: usually Europa
Device: prs t1
|
Quote:
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? |
|
10-01-2014, 04:40 PM | #34 | |
actually it is /var/log
Posts: 341
Karma: 2994236
Join Date: Sep 2012
Location: usually Europa
Device: prs t1
|
Quote:
|
|
10-01-2014, 04:50 PM | #35 | |
Resident Curmudgeon
Posts: 75,244
Karma: 133361584
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
|
|
Advert | |
|
10-01-2014, 04:52 PM | #36 |
Grand Sorcerer
Posts: 27,718
Karma: 196949708
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
|
10-01-2014, 05:15 PM | #37 | ||
Grand Sorcerer
Posts: 27,718
Karma: 196949708
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
Quote:
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. |
||
10-01-2014, 05:35 PM | #38 | ||
actually it is /var/log
Posts: 341
Karma: 2994236
Join Date: Sep 2012
Location: usually Europa
Device: prs t1
|
Quote:
Quote:
|
||
10-01-2014, 05:52 PM | #39 | |
actually it is /var/log
Posts: 341
Karma: 2994236
Join Date: Sep 2012
Location: usually Europa
Device: prs t1
|
Quote:
Just inserting Sigil split mark should not make it necessary to parse all links again? Last edited by varlog; 10-01-2014 at 05:58 PM. |
|
10-01-2014, 06:04 PM | #40 | |
Grand Sorcerer
Posts: 27,718
Karma: 196949708
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
No. There is no specific "this is where a chapter break occurs" markup in a traditional mobi.
Quote:
"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. Last edited by DiapDealer; 10-01-2014 at 06:11 PM. |
|
10-01-2014, 06:09 PM | #41 |
actually it is /var/log
Posts: 341
Karma: 2994236
Join Date: Sep 2012
Location: usually Europa
Device: prs t1
|
|
10-01-2014, 06:12 PM | #42 |
actually it is /var/log
Posts: 341
Karma: 2994236
Join Date: Sep 2012
Location: usually Europa
Device: prs t1
|
why KindleUnpack stays obsolete than?
Last edited by varlog; 10-01-2014 at 06:19 PM. |
10-01-2014, 06:21 PM | #43 |
Grand Sorcerer
Posts: 27,718
Karma: 196949708
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
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. |
10-01-2014, 06:28 PM | #44 | |
actually it is /var/log
Posts: 341
Karma: 2994236
Join Date: Sep 2012
Location: usually Europa
Device: prs t1
|
Quote:
I'm have my future teller hat on me now: This topic will come again . |
|
10-04-2014, 08:39 PM | #45 |
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. |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
epubcheck plugin for Sigil | Doitsu | Plugins | 519 | 07-22-2024 04:59 PM |
kindlegen plugin for Sigil | Doitsu | Plugins | 169 | 02-16-2024 06:48 AM |
[Plugin] PunctuationSmarten Sigil plugin | DiapDealer | Plugins | 138 | 07-11-2023 11:22 AM |
[Plugin] ePub3-itizer - epub3 output plugin for Sigil | KevinH | Plugins | 435 | 01-19-2023 09:46 PM |
smoothRemove_v010 plugin for Sigil | kbanelas | Plugins | 15 | 01-27-2017 05:51 PM |