[Conversion Output] KePub Output Plugin - Page 11

davidfor · 05-01-2016, 07:57 AM

The series setting is actually part of the main KoboTouch driver rather than the extended driver. The extended driver is reusing the function.

Assuming that everything is configured correctly, it should just work. The configuration to check is the driver option and that metadata management is set to automatic. But, if it is working for other books, they must be set correctly.

The other trap with this is that the series info is set the next time you connect the device after sending the books. That means the book has to be processed into the devices library and that calibre shows the book on the device when you reconnect.

If all that is OK, then I need to see a debug log. Restart calibre in debug mode, connect the device and let the connection jobs run. Then close calibre and post the log that is displayed.

jgoguen · 05-01-2016, 10:15 AM

It wouldn't be this plugin, it would be the KoboTouchExtended device plugin, but even there that option is passed directly to the main driver for updating series data. I have books sent with the latest version of all my plugins and series info shows correctly.

Can you make sure that after you send a book to your device you're ejecting it and plugging it back in? Series info is only updated when the book has already been processed by the Kobo and we can't set series info on first upload. That's been a Kobo restriction longer than I've been using calibre. If that isn't working for you, post a debug log of both where you send the books to your device and the second connection for updating series data.

BobC · 05-01-2016, 10:22 AM

Quote:

Originally Posted by davidfor

The series setting is actually part of the main KoboTouch driver rather than the extended driver. The extended driver is reusing the function.

Assuming that everything is configured correctly, it should just work. The configuration to check is the driver option and that metadata management is set to automatic. But, if it is working for other books, they must be set correctly.

The other trap with this is that the series info is set the next time you connect the device after sending the books. That means the book has to be processed into the devices library and that calibre shows the book on the device when you reconnect.

If all that is OK, then I need to see a debug log. Restart calibre in debug mode, connect the device and let the connection jobs run. Then close calibre and post the log that is displayed.

Thank you for that - I went through the options and noticed that "Set Series" was not set for the main KoboTouch driver so I checked it. I searched high and low for the Metadate Management option but couldn't find it (no doubt it is there somewhere and I've just missed it). I then re-uploaded the books and then disconnected. After another re-connection I can now see the Series info for those books .

I did think that was what I was doing before but I must have missed a step.

All working now

BobC

jgoguen · 05-01-2016, 10:56 AM

Metadata management isn't a driver option, but I forget where it is. If it worked for you though it's already set right

davidfor · 05-01-2016, 07:30 PM

Quote:

Originally Posted by BobC

Thank you for that - I went through the options and noticed that "Set Series" was not set for the main KoboTouch driver so I checked it. I searched high and low for the Metadate Management option but couldn't find it (no doubt it is there somewhere and I've just missed it). I then re-uploaded the books and then disconnected. After another re-connection I can now see the Series info for those books .

I did think that was what I was doing before but I must have missed a step.

If selecting the Set Series option in the KoboTouch driver solved it, that means you are using it instead of the extended driver. Are you converting to kepub and then sending the books? Or are you simple using epubs?

And the Metadata Management option is on the "Sending books to devices" page of the calibre preferences.

BobC · 05-02-2016, 04:02 AM

Quote:

Originally Posted by davidfor

If selecting the Set Series option in the KoboTouch driver solved it, that means you are using it instead of the extended driver. Are you converting to kepub and then sending the books? Or are you simple using epubs?

And the Metadata Management option is on the "Sending books to devices" page of the calibre preferences.

Well spotted - yes I do convert to kepub and then send the book. By doing it that way I can preview the Kepub in the Calibre viewer before sending it. The odd thing is though that now you have pointed me to where "Metadata management" is in the options I find it is set to "Manual".

Looks like I need to go through my config with a fine-tooth comb.

BobC

davidfor · 05-02-2016, 08:05 AM

Quote:

Originally Posted by BobC

Well spotted - yes I do convert to kepub and then send the book. By doing it that way I can preview the Kepub in the Calibre viewer before sending it.

That might not show anything. The calibre view will just treat the kepub as an epub. It doesn't have any of the extra rules the kepub renderer has on the Kobo.

Quote:

The odd thing is though that now you have pointed me to where "Metadata management" is in the options I find it is set to "Manual".

Looks like I need to go through my config with a fine-tooth comb.

Always a good idea every now and then as there might be something new.

jackie_w · 05-21-2016, 07:35 AM

I have a question about the various Kobo-fications which turn a standard epub into a kepub ...

Whilst tinkering around with a 'minimal' format shift hack, I tried reducing the changes to just these two:

edit the opf manifest item for cover image (properties="cover-image")
add the koboSpans

i.e. no special <div>s, no style-hacks.css, no kobo.js, no kte file.
The kepubs were transferred using standard send-to-device with KoboTouch

When reading the 'minimal kepub' on the Kobo, it's not immediately obvious to me that anything is broken. Is that what you'd expect? Or maybe I've broken some options which I never use (e.g. annotations, reading stats, anything wi-fi related ...)?

jgoguen · 05-21-2016, 10:48 AM

What do you mean "broken"? Those two changes are indeed the minimum for making a KePub (along with using the double extension, but that's hidden unless you look at the file name on the device). With just those changes, it should load the KePub reader and work normally.

jackie_w · 05-21-2016, 12:06 PM

Quote:

Originally Posted by jgoguen

What do you mean "broken"?

What I mean by "broken" is:
By deliberately NOT adding

kobo.js,
special <div>s,
style-hacks.css
kte file (I'm assuming this is for admin/troubleshooting purposes)

to the best of your knowledge, would I have inadvertantly prevented at least one standard kepub feature from working correctly on the Kobo device?

Your initial reply suggests that 'minimal changes only' would not adversely affect kepub readability/functionality.

jgoguen · 05-21-2016, 01:16 PM

The JS is only added if the reference KePub is in place, so that's considered optional for everyone. It may improve the experience but is not required. Similarly for style hacks, it improves the experience but isn't required. There are no special divs, only spans. The kte file is indeed for troubleshooting only, it encodes some data about calibre and plugin versions, selected options, and the date and time of conversion. It should always be added but other than me needing more information for troubleshooting it's OK to be missing.

jackie_w · 05-21-2016, 02:08 PM

Quote:

Originally Posted by jgoguen

Similarly for style hacks, it improves the experience but isn't required. There are no special divs

By 'special divs' I meant the <div id="book-columns"><div id="book-inner"> additions associated with style-hacks.css.

This is what I'm trying to understand. In what ways does it 'improve the experience', particularly when kobo.js is not added?

GeoffR · 05-21-2016, 02:14 PM

Quote:

Originally Posted by jackie_w

When reading the 'minimal kepub' on the Kobo, it's not immediately obvious to me that anything is broken. Is that what you'd expect? Or maybe I've broken some options which I never use (e.g. annotations, reading stats, anything wi-fi related ...)?

There are a couple of things that are needed to fix problems that occur when reading KePubs in full-screen mode: (Edit: See this post for examples.)

1. The margin/padding for body needs to be set to zero, or else the viewport gets shifted off-centre.

2. Wrapper divs added inside body are needed as a place to add padding in order to avoid text being clipped at the edge of the viewport. (padding can't be added to body because of 1.)

jgoguen · 05-21-2016, 02:48 PM

Right, that

And that's also why I say there are no special divs—I could name those anything as long as I update the CSS to match, and they could well be spans as well. It's semantically correct to make it a div, but as some people can attest to, publishers don't always care about being semantically (or mostly) correct as long as the book mostly works. They aren't even strictly necessary divs, with a different CSS hack you could probably (not 100% certain) achieve the same result with no added tags.

jackie_w · 05-21-2016, 03:10 PM

Ah-ha! Thanks GeoffR and jgoguen

That may be why I didn't notice any problems. I don't read in full-screen mode.

05-21-2016, 07:35 AM	#158
jackie_w Grand Sorcerer Posts: 6,252 Karma: 16544692 Join Date: Sep 2009 Location: UK Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3	A question for the kepub gurus ... I have a question about the various Kobo-fications which turn a standard epub into a kepub ... Whilst tinkering around with a 'minimal' format shift hack, I tried reducing the changes to just these two: edit the opf manifest item for cover image (properties="cover-image") add the koboSpans i.e. no special <div>s, no style-hacks.css, no kobo.js, no kte file. The kepubs were transferred using standard send-to-device with KoboTouch When reading the 'minimal kepub' on the Kobo, it's not immediately obvious to me that anything is broken. Is that what you'd expect? Or maybe I've broken some options which I never use (e.g. annotations, reading stats, anything wi-fi related ...)?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
catalogue builder output columns are not in the same order in the output	KWhytte	Library Management	5	12-04-2012 02:03 AM
Plugin not customizable: Plugin: HTML Output does not need customization	flyingfoxlee	Conversion	2	02-24-2012 02:24 AM
Plugin which uses net as input and output	medve	Development	0	12-04-2011 03:20 PM
Creat new Output plugin (LaTeX and/or txt2tags)	Lebewesen	Development	3	11-22-2011 11:10 AM
AZW Conversion Output Plugin	tylau0	Plugins	59	08-14-2011 10:36 PM

05-01-2016, 07:57 AM	#151
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	The series setting is actually part of the main KoboTouch driver rather than the extended driver. The extended driver is reusing the function. Assuming that everything is configured correctly, it should just work. The configuration to check is the driver option and that metadata management is set to automatic. But, if it is working for other books, they must be set correctly. The other trap with this is that the series info is set the next time you connect the device after sending the books. That means the book has to be processed into the devices library and that calibre shows the book on the device when you reconnect. If all that is OK, then I need to see a debug log. Restart calibre in debug mode, connect the device and let the connection jobs run. Then close calibre and post the log that is displayed.

05-01-2016, 10:15 AM	#152
jgoguen Generally Awesome Person Posts: 1,100 Karma: 2191133 Join Date: Jan 2013 Location: /dev/kmem Device: Kobo Clara HD, Kindle Oasis	It wouldn't be this plugin, it would be the KoboTouchExtended device plugin, but even there that option is passed directly to the main driver for updating series data. I have books sent with the latest version of all my plugins and series info shows correctly. Can you make sure that after you send a book to your device you're ejecting it and plugging it back in? Series info is only updated when the book has already been processed by the Kobo and we can't set series info on first upload. That's been a Kobo restriction longer than I've been using calibre. If that isn't working for you, post a debug log of both where you send the books to your device and the second connection for updating series data.

05-01-2016, 10:56 AM	#154
jgoguen Generally Awesome Person Posts: 1,100 Karma: 2191133 Join Date: Jan 2013 Location: /dev/kmem Device: Kobo Clara HD, Kindle Oasis	Metadata management isn't a driver option, but I forget where it is. If it worked for you though it's already set right

05-21-2016, 10:48 AM	#159
jgoguen Generally Awesome Person Posts: 1,100 Karma: 2191133 Join Date: Jan 2013 Location: /dev/kmem Device: Kobo Clara HD, Kindle Oasis	What do you mean "broken"? Those two changes are indeed the minimum for making a KePub (along with using the double extension, but that's hidden unless you look at the file name on the device). With just those changes, it should load the KePub reader and work normally.

05-21-2016, 01:16 PM	#161
jgoguen Generally Awesome Person Posts: 1,100 Karma: 2191133 Join Date: Jan 2013 Location: /dev/kmem Device: Kobo Clara HD, Kindle Oasis	The JS is only added if the reference KePub is in place, so that's considered optional for everyone. It may improve the experience but is not required. Similarly for style hacks, it improves the experience but isn't required. There are no special divs, only spans. The kte file is indeed for troubleshooting only, it encodes some data about calibre and plugin versions, selected options, and the date and time of conversion. It should always be added but other than me needing more information for troubleshooting it's OK to be missing.

05-21-2016, 02:48 PM	#164
jgoguen Generally Awesome Person Posts: 1,100 Karma: 2191133 Join Date: Jan 2013 Location: /dev/kmem Device: Kobo Clara HD, Kindle Oasis	Right, that And that's also why I say there are no special divs—I could name those anything as long as I update the CSS to match, and they could well be spans as well. It's semantically correct to make it a div, but as some people can attest to, publishers don't always care about being semantically (or mostly) correct as long as the book mostly works. They aren't even strictly necessary divs, with a different CSS hack you could probably (not 100% certain) achieve the same result with no added tags.

05-21-2016, 03:10 PM	#165
jackie_w Grand Sorcerer Posts: 6,252 Karma: 16544692 Join Date: Sep 2009 Location: UK Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3	Ah-ha! Thanks GeoffR and jgoguen That may be why I didn't notice any problems. I don't read in full-screen mode.