Cybook with Calibre, minor problems

taspool · 02-20-2009, 06:33 PM

(cross posted with Calibre forum, not sure which was most appropriate)
I have changed from using Mobipocket software to Calibre for my recently acquired Cybook. I love Calibre, the look and feel is professional and the degree of user control over functions is fantastic.

A couple of issues have arisen for me, which may well be my own inexperience;

1. When importing or replacing the cover image in Calibre, this works fine as far as then reading the book in Cybook (the cover image comes up full screen if I've imported an 800x600 image) but no matter what size jpg I start with, the thumbnail picture in the Cybook library does not take up the full thumbnail space in the books listing, instead the cover image is a tiny picture in the centre with a large white margin around it. Other books, such as purchased prc files, have "full size" thumbnails. What can I do to get "full size" thumbnails from Calibre?

2. I'm one of those who'd like the maximum amount of the cybook screen filled with text to minimise page turning. Is there any way of formatting the conversion or send-to-device process in Calibre so that the header is not shown and instead used by text, or so that side margin white space can be reduced? Simply turning off "show header" in the cybook just leaves blank space at the top.

Thanks for any help!

DDHarriman · 02-20-2009, 08:15 PM

Hi

I do not use Calibre for my Mobipocket files, but Mobipocket Creator instead, so can not help you with (1).

Concerning question (2), no, the margins in the Cybook can not be changed, at least up to the last firmware.

Good reading,

taspool · 02-20-2009, 08:29 PM

Quote:

Originally Posted by DDHarriman

Hi

I do not use Calibre for my Mobipocket files, but Mobipocket Creator instead, so can not help you with (1).

Concerning question (2), no, the margins in the Cybook can not be changed, at least up to the last firmware.

Good reading,

Okay, thanks for the response. As to margins, I see from the forum that a new firmware version is pending, so hopefully that is one of the issues to be addressed. Also more flexible folders and sort by author would be nice.

If anyone else on the forum has calibre working with cybook and has thumbnails correctly sized, I'd be pleased to hear how you do it.

Jellby · 02-21-2009, 04:08 AM

Hmm... as far as I know, thumbnails are generated by the Cybook[*], they are the .t2b files you can find next to the ebooks. Try deleting the .t2b files, the Cybook will generate them again, see if they are correctly maximised.

[*] Mobipocket files have "thumbnails", but the Cybook does not used them (or didn't with the last firmware I tried).

taspool · 02-21-2009, 08:24 AM

Quote:

Originally Posted by Jellby

Hmm... as far as I know, thumbnails are generated by the Cybook[*], they are the .t2b files you can find next to the ebooks. Try deleting the .t2b files, the Cybook will generate them again, see if they are correctly maximised.[*] Mobipocket files have "thumbnails", but the Cybook does not used them (or didn't with the last firmware I tried).

Jellby, you are a hero. Deleting the t2b files did indeed fix the problem, all thumbnails regenerated at the right size.

Thanks very much! If you get near Sydney, I owe you a beer or seven.

Jellby · 02-21-2009, 08:56 AM

Quote:

Originally Posted by taspool

Thanks very much! If you get near Sydney, I owe you a beer or seven.

Hmm... If you get me a ticket to Sydney I'll get you the beer(s)

user_none · 02-21-2009, 12:48 PM

Calibre auto generates the t2b files. It's a feature because say you put 1,000 book on in one go, well, the Cybook is a bit slow and it takes some time to generate all those thumbnails. The size issue for Calibre generated thumbnail is a known problem. I just haven't gotten around to sorting it out yet.

user_none · 02-21-2009, 03:14 PM

Fix has been committed to trunk. Will appear in the next release (after 0.4.139)

FizzyWater · 02-21-2009, 03:22 PM

Hey, user_none...I've seen this on Mobileread a few times - "committed to trunk". Would you mind sharing a definition of what that means? At first I thought it meant you knew what it would take to fix the problem and were promising to do so, but then I thought, since you already can say it will be in the next release, maybe it means you're already done...?

user_none · 02-21-2009, 03:57 PM

In a nutshell what happens is: I make a change (fix a bug, add a feature) and commit it to my branch (You can see all branches here.). If Kovid approves of it and feels it's ready he will then import my changes to trunk (You can follow the progress here). Periodically Kovid will take trunk and release it as a new version (this happens when there are enough changes or a critical fix to warrant a new version). Anything in trunk will appear in the next release.

Branches are trunk at some point in time (branches can track changes in trunk though time) plus any changes the branch owner has made. They are a way to make upcoming features that are incomplete, need testing, or could take awhile to develop without slowing down releases with other finished features.

When commenting on fixes in the forums or in bugs I like to state what release the fix will be appearing in because of how often Kovid makes them. Also, so anyone searching for a particular bug can see what version it was fixed in here or in on the bug tracker without having to look though the changes made to trunk.

When you see committed to trunk it means that the issue has been fixed, it has been included in the mainline code and will be in the next release.

FizzyWater · 02-21-2009, 04:04 PM

Thanks for the explanation! And now I also see it's like tree - "branch" and "trunk" - and not like a container - "suitcase" or "trunk".

I learn so much here!

pilotbob · 02-21-2009, 06:33 PM

Quote:

Originally Posted by FizzyWater

Thanks for the explanation! And now I also see it's like tree - "branch" and "trunk" - and not like a container - "suitcase" or "trunk".

User none gave you the technical answer. But, for those that don't follow...

There is basically a place where all the source code for the program is stored. This is known as a source control or version control system. It keeps track of all the changes that developers make to the program.

There can be divisions or separate areas (folders if you will)... actually they ARE like containers. Trunk is the "container" or "folder" in the source control where the approved code is kept. This is where the program is built from.

HTH too... I hope user none isn't upset that I added to his explanation.

BOb

user_none · 02-21-2009, 07:09 PM

Quote:

Originally Posted by pilotbob

HTH too... I hope user none isn't upset that I added to his explanation.

No worries. I rewrote my explanation three times trying to tone down the technicalness. I appreciate adding to it so everyone can follow.

FizzyWater · 02-21-2009, 07:17 PM

Quote:

Originally Posted by pilotbob

There can be divisions or separate areas (folders if you will)... actually they ARE like containers. Trunk is the "container" or "folder" in the source control where the approved code is kept.

Aieeee. My head is spinning!

Thanks, Bob!

GeoffC · 02-22-2009, 06:43 AM

Quote:

Originally Posted by FizzyWater

Aieeee. My head is spinning!

Thanks, Bob!

Is that all !

Mine span off, and a certain Aussie has a spinner permanently attached to his headgear ....

02-20-2009, 06:33 PM	#1
taspool Member Posts: 17 Karma: 10 Join Date: Feb 2009 Device: cybook gen3	Cybook with Calibre, minor problems (cross posted with Calibre forum, not sure which was most appropriate) I have changed from using Mobipocket software to Calibre for my recently acquired Cybook. I love Calibre, the look and feel is professional and the degree of user control over functions is fantastic. A couple of issues have arisen for me, which may well be my own inexperience; 1. When importing or replacing the cover image in Calibre, this works fine as far as then reading the book in Cybook (the cover image comes up full screen if I've imported an 800x600 image) but no matter what size jpg I start with, the thumbnail picture in the Cybook library does not take up the full thumbnail space in the books listing, instead the cover image is a tiny picture in the centre with a large white margin around it. Other books, such as purchased prc files, have "full size" thumbnails. What can I do to get "full size" thumbnails from Calibre? 2. I'm one of those who'd like the maximum amount of the cybook screen filled with text to minimise page turning. Is there any way of formatting the conversion or send-to-device process in Calibre so that the header is not shown and instead used by text, or so that side margin white space can be reduced? Simply turning off "show header" in the cybook just leaves blank space at the top. Thanks for any help!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Minor Calibre issues	starrigger	Calibre	20	02-09-2009 10:54 AM
Calibre : minor suggestions	carpii	Calibre	14	12-16-2008 07:47 PM
Minor errors on calibre web site!	itimpi	Calibre	17	11-23-2008 05:01 PM
Have you had any problems with the Cybook?	Over	Bookeen	74	06-13-2008 04:50 AM
Cybook problems	solodoc	Bookeen	70	02-14-2008 07:44 PM

02-20-2009, 08:15 PM	#2
DDHarriman Guru Posts: 860 Karma: 4380 Join Date: Feb 2008 Location: Almada, Portugal Device: Cybook Gen3, Sony PRS 505, Kindle DXG and Samsung Galaxy Note	Hi I do not use Calibre for my Mobipocket files, but Mobipocket Creator instead, so can not help you with (1). Concerning question (2), no, the margins in the Cybook can not be changed, at least up to the last firmware. Good reading,

02-21-2009, 04:08 AM	#4
Jellby frumious Bandersnatch Posts: 7,516 Karma: 18512745 Join Date: Jan 2008 Location: Spaniard in Sweden Device: Cybook Orizon, Kobo Aura	Hmm... as far as I know, thumbnails are generated by the Cybook[], they are the .t2b files you can find next to the ebooks. Try deleting the .t2b files, the Cybook will generate them again, see if they are correctly maximised. [] Mobipocket files have "thumbnails", but the Cybook does not used them (or didn't with the last firmware I tried).

02-21-2009, 12:48 PM	#7
user_none Sigil & calibre developer Posts: 2,488 Karma: 1063785 Join Date: Jan 2009 Location: Florida, USA Device: Nook STR	Calibre auto generates the t2b files. It's a feature because say you put 1,000 book on in one go, well, the Cybook is a bit slow and it takes some time to generate all those thumbnails. The size issue for Calibre generated thumbnail is a known problem. I just haven't gotten around to sorting it out yet.

02-21-2009, 03:14 PM	#8
user_none Sigil & calibre developer Posts: 2,488 Karma: 1063785 Join Date: Jan 2009 Location: Florida, USA Device: Nook STR	Fix has been committed to trunk. Will appear in the next release (after 0.4.139)

02-21-2009, 03:22 PM	#9
FizzyWater You kids get off my lawn! Posts: 4,220 Karma: 73492664 Join Date: Aug 2007 Location: Columbus, Ohio Device: Oasis 2 and Libra H2O and half a dozen older models I can't let go of	Hey, user_none...I've seen this on Mobileread a few times - "committed to trunk". Would you mind sharing a definition of what that means? At first I thought it meant you knew what it would take to fix the problem and were promising to do so, but then I thought, since you already can say it will be in the next release, maybe it means you're already done...?

02-21-2009, 03:57 PM	#10
user_none Sigil & calibre developer Posts: 2,488 Karma: 1063785 Join Date: Jan 2009 Location: Florida, USA Device: Nook STR	In a nutshell what happens is: I make a change (fix a bug, add a feature) and commit it to my branch (You can see all branches here.). If Kovid approves of it and feels it's ready he will then import my changes to trunk (You can follow the progress here). Periodically Kovid will take trunk and release it as a new version (this happens when there are enough changes or a critical fix to warrant a new version). Anything in trunk will appear in the next release. Branches are trunk at some point in time (branches can track changes in trunk though time) plus any changes the branch owner has made. They are a way to make upcoming features that are incomplete, need testing, or could take awhile to develop without slowing down releases with other finished features. When commenting on fixes in the forums or in bugs I like to state what release the fix will be appearing in because of how often Kovid makes them. Also, so anyone searching for a particular bug can see what version it was fixed in here or in on the bug tracker without having to look though the changes made to trunk. When you see committed to trunk it means that the issue has been fixed, it has been included in the mainline code and will be in the next release.

02-21-2009, 04:04 PM	#11
FizzyWater You kids get off my lawn! Posts: 4,220 Karma: 73492664 Join Date: Aug 2007 Location: Columbus, Ohio Device: Oasis 2 and Libra H2O and half a dozen older models I can't let go of	Thanks for the explanation! And now I also see it's like tree - "branch" and "trunk" - and not like a container - "suitcase" or "trunk". I learn so much here!

Advert

Advert