Beta testers for calibre 9 needed

[un_pogaz]

Originally Posted by Comfy.n

Thanks. bloody easy

Yeah, but be warned: If you edit the file outside of Calibre (like by using Sigil), request a re-count will do nothing because Calibre could not take trace of the file change.
It not a bug, it work as intended (in this sens, it like the book size field).

Force the recount will be a feature that fit more to Quality Check plugin.

(is experienced, take a time to understand it)

[kovidgoyal]

Originally Posted by un_pogaz

Yeah, but be carefull: If you edit the file outside of Calibre (like by using Sigil), request a re-count will do nothing because Calibre could not take trace of the file change.
It not a bug, it work as intended (in this sens, it like the book size field).

Force the recount will be a feature that fit more to Quality Check plugin.

IIRC the rescan does work if the file has been modified (it checks the file size and if it is different does the recount).

[un_pogaz]

Originally Posted by kovidgoyal

IIRC the rescan does work if the file has been modified (it checks the file size and if it is different does the recount).

No, just check in to be sure (and what I say it's seem intended to me):
Calibre first check if the Page Object in the db has the same format_size that the "db.format_db_size()", and only if their is different, redo the calc.
The new size of the files is retrived only after that and used only in the new Page Object.

So you need to commit a size change for this format for that a new Page Object could be create.

MaintainPageCounts.count_book()

[JimmXinu]

Up or Down
Book spines titles are being written from bottom up. Looking over as my RL bookshelves, 99% of the titles are written from top down. Should that be changed? Or customizable?

Author
I agree that including author is important. I suggest it should be in the default template.

Resize/Multiline
Real book spines resize the text to fit, even if it ends up small. Since the book spine is larger due to pages, it would ideally word wrap.

Or at least allow for multiple lines in templates. Adding \n or <br> to the template didn't work for me.

Font
Changing the font in the title template editor doesn't change it on the shelf, only in the editor??

[kovidgoyal]

Originally Posted by un_pogaz

So you need to commit a size change for this format for that a new Page Object could be create.

MaintainPageCounts.count_book()

Ah yes, you are talking about the case of the format size being incorrect because the book file was modified outside calibre. Yes, in that case it wont recount.

[un_pogaz]

Up or Down: Certainly feasible (on it)
Author: See how even with the title is realy easy to reach the max size, definitely not a good idea. User edit.
Font: Font in the template editor was always for the code of the template editor, never as a output. Or their is magik a don't know.

Resize/Multiline: I have no idea is a multiline resize is possible. Seem hard to do.
Eventualy, it would be possible to add a optional second line powerd by template, in this case Calibre could know to increase the min size (and also a bit the max) to take it in count. This way, you can also display the author. (but personally, the default value for this second line should be empty)
Your call Kovid.

[kovidgoyal]

@JimmXinu: Whether paper books have them up or down is very country dependent. This can certainly be made an option.

The font size is automatically scaled to fit as much of the title as possible. As for wrapping, it doesnt look good, at least to me, and has the problem that it works only if the spine is thick. The length of the title is not correlated with the thickness of the spine, nor should it be. Paper books get away with this because they are physically much larger. A paper book is maybe 8 inches to a foot in length. Books on a shelf on a screen are not and should not be that large, they are typically an inch or two. That said I am not adamantly opposed to wrapping. It's certainly worth experimenting if it can be made to look OK.

The font setting in the template editor is only for the template editor, as the tooltip for that setting indicates.

[un_pogaz]

Originally Posted by kovidgoyal

Books on a shelf on a screen are not and should not be that large, they are typically an inch or two. That said I am not adamantly opposed to wrapping. It's certainly worth experimenting if it can be made to look OK.

Before wrapping, I suggest to try a new spine height.
150px was the default value, but with the various changes, it has become quite small. Quick test, I suggest 160, it render better.
We could also make this value controllable by the user (range 150-200px). This would require some adjustment, but since all these calculations are based on a few values, it would naturally affect everything without overflowing.

[kovidgoyal]

Making spine height configurable has the problem of invalidating the full thumbnail cache. And if we really want to make it configurable then the way to do it is like in the cover grid, by default have calibre pick a size automatically based on the screen size. Allow the user to override it if they want.

[un_pogaz]

*snap* Right. So only intenal value.
Also, I take back my word and suggest 180px, it way better. It's really comfortable but not too big, and the ratio of the spine seem more natural/corresponding to real book. Test to you.

[BetterRed]

Originally Posted by kovidgoyal

No DOCX metadata has only a page count if word bothers to update it, it doesnt always, sometimes leaving it wildly off and other software does not set it. Thus I chose not to use it.

Page counts are done using a modified version of the original calibre algorithm to yield numbers closer to paper book values.

Fair enough, nevertheless they are still incorrect.

BR

[JSWolf]

kovid, can you please allow the page column to be used by plugins? That way Count Pages plugin could be configured to use the new page column.

[kovidgoyal]

Originally Posted by BetterRed

Fair enough, nevertheless they are still incorrect.

BR

Yeah the only way to get them "correct" would be to do a full layout of the DOCX file. DOCX markup doesnt define pages, only block level elements like paragraphs. How they are laid out in pages is upto the software displaying the file. If by correct you mean what word would show then yes one has to re-implement words layout engine. This is both way too much work and way too slow for page counting.

[kovidgoyal]

Originally Posted by JSWolf

kovid, can you please allow the page column to be used by plugins? That way Count Pages plugin could be configured to use the new page column.

the pages column is auto-updated every time a new book is added or a new format is added to an existing books. It has to be done that way otherwise it becomes unuseable since it will rely on the user to remember to update it. If you want to use a different column for pages you are welcome to do so. Simply dont add the builtin Pages to the book list (it is not added by default) and pretend it doesnt exist and continue using page count plugin or whatever else you want. You can configure the bookshelf view to use your custom column instead of the builtin column as well, already.

[JSWolf]

Originally Posted by kovidgoyal

the pages column is auto-updated every time a new book is added or a new format is added to an existing books. It has to be done that way otherwise it becomes unuseable since it will rely on the user to remember to update it. If you want to use a different column for pages you are welcome to do so. Simply dont add the builtin Pages to the book list (it is not added by default) and pretend it doesnt exist and continue using page count plugin or whatever else you want. You can configure the bookshelf view to use your custom column instead of the builtin column as well, already.

Maybe Count pages could be itngrated into calibre so we can set the count to different formats based on the format. For example, ADE page number for ePub and calibre's count for Kindle formats.