Where is the new page count stored / can it be a column?

[Mister L]

I have just noticed there is a new "pages" number in the book info and I have seen from other posts that it is used to calculate the width of the covers in bookshelf view (nice I like that view and I wondered how it was done).

I already have the Count Pages PlugIn installed and I send the page count to my kobo as a subtitle, because I hate the kepub system of "screen count" which changes every time you change font size or font or literally anything.

So now I have 2 page count numbers and they are not the same.

Question 1. how is the new page count calculated? Presumably based on x characters = 1 page?

Question 2. where is the new page count data stored and can it be added in a column, specifically the column I currently use for the plugin ? If it can't, I will just modify the plugin to calculate the same way, if it is based on character count, so that the two agree.

I would rather have only one page count number (even if it's displayed twice) and I am not bothered which one it is but having 2 different ones is triggering my OCD.

[BetterRed]

Added: It is a column, have a look at Preferences->Add your own columns.

To the extent that it's possible, I ignore it.

I renamed the custom column I had from 'pages/Pages' to 'cc_pages/CC Pages' and made necessary adjustments to the Count Pages plugin, Book Details settings etc. And I customised the bookshelf view settings to suit my preference for minimalism:



I wish there was a setting for shelf colour, dark brown on grey wash looks awful.

The page/Pages built in column is stored in the book-pages-link table in the metadata.db database.

BR

[un_pogaz]

Globaly, yes, the Calibre Pages use a system base of number characters by page, with some subtlety. Due to these minor differences, the values returned by Calibre Pages will always differ from those produced by the Pages Count plugin, and there are no plans to make them equal.

Since the Calibre Pages Count is stored in a specific and read only column (named {pages}), where the plugin store it value in a custom column of you choice, their is no conflict. It up to you to choose wich value/column to use/show.

[ownedbycats]

The built-in pages doesn't quite work if you use dummy records (no formats or 0-byte formats) for records of non-eBooks.

[un_pogaz]

Originally Posted by BetterRed

I wish there was a setting for shelf colour, dark brown on grey wash looks awful.

There is all the tab Color. You will probaly need to search and download a wood texture background image to use.

Originally Posted by ownedbycats

The built-in pages doesn't quite work if you use dummy records (no formats or 0-byte formats) for records of non-eBooks.

What do you mean? When no format, it show a "None" message. And except for TXT file, you can't have 0-byte file for the supported formats.

[Mister L]

Thanks everyone for the help.

I have found the column, it is called "pages", my column is called "#pages".

My subtitle page count code looks like this, in the Calibre "Configure this device" dialogue (only available when the device is connected) and also in the Kobo Utilities plugin "Update metadata in Device Library" subtitle field :

program:
	if field('#pages') then
		 template('{#pages} pages')
		fi

Is there a way for my #pages column to just copy the number from Calibre's pages column, or is there a way to use the pages column instead of my #pages column in that code ? (I think no, because it needs the # to reference it, is that right ?) I'm using the ADE algorithm and it's pretty close to the Calibre count so that would be fine for my uses.

I checked in the plugin page if there are any plans to add the Calibre count in the plugin options but it does not seem to be the case.

If it's not possible, it's not the end of the world, this is just a reference for me so I have some idea if it's a "long" book or a "short" book, but I would prefer to have the same count since both are displayed next to each other.

[theducks]

Originally Posted by Mister L

Thanks everyone for the help.

I have found the column, it is called "pages", my column is called "#pages".

My subtitle page count code looks like this, in the Calibre "Configure this device" dialogue (only available when the device is connected) and also in the Kobo Utilities plugin "Update metadata in Device Library" subtitle field :

program:
	if field('#pages') then
		 template('{#pages} pages')
		fi

Is there a way for my #pages column to just copy the number from Calibre's pages column, or is there a way to use the pages column instead of my #pages column in that code ? (I think no, because it needs the # to reference it, is that right ?) I'm using the ADE algorithm and it's pretty close to the Calibre count so that would be fine for my uses.

I checked in the plugin page if there are any plans to add the Calibre count in the plugin options but it does not seem to be the case.

If it's not possible, it's not the end of the world, this is just a reference for me so I have some idea if it's a "long" book or a "short" book, but I would prefer to have the same count since both are displayed next to each other.

Looks like you can use the Bulk mode Metadata edit Search and replace to copy from pages to #pages source

[Mister L]

Originally Posted by theducks

Looks like you can use the Bulk mode Metadata edit Search and replace to copy from pages to #pages source

Thanks ! Very good to know. That will fix all the books currently in my library.

Edit: just did it, worked perfectly.


Is it possible to do that automatically somehow for new books as well ? I don't think I care enough to manually update every future book (although... we'll see how much it bothers me ).

[Sirtel]

You can create a custom pages column built from other columns and have it automatically copy the values from the calibre pages column.

[PeterT]

Maybe I'm missing something but have you tried just hanging the #pages in the template to pages.. ie

program:

if field('pages') then

 template('{pages} pages')

fi

# is needed to reference user created columns; lack of a # means built in column

[Mister L]

Originally Posted by PeterT

Maybe I'm missing something but have you tried just hanging the #pages in the template to pages.. ie

program:

if field('pages') then

 template('{pages} pages')

fi

# is needed to reference user created columns; lack of a # means built in column

Wow. I think I have set a new personel record for over-complicating my life here That is exactly what I wanted to do, but I misunderstood / misremembered that if there is not a # in a column name you cannot reference it in the code.

THANK YOU for bringing me back to reality with the simplest possible answer to my question.