Beta testers for calibre 9 needed

[kovidgoyal]

The restriction on non duplicate column headers is cosmetic only for user convenience. The UI prevents the user from creating duplicate columns because that's typically not a useful thing to do. But you can actually have as many duplicate header names as you like (lookup names have to be unique). Thus there is no issue with having a builtin column with title Pages and a custom column with title Pages as well.

[Comfy.n]

I find it interesting that, as BR pointed out other times, case variants matter for heading duplicate detection:

[JimmXinu]

Originally Posted by kovidgoyal

The restriction on non duplicate column headers is cosmetic only for user convenience. The UI prevents the user from creating duplicate columns because that's typically not a useful thing to do.

But earlier you said:

Originally Posted by kovidgoyal

You can have any number of columns with the same name. The new builtin column is not visible by default, most people would not even be aware it exists. And since column names is a global namespace such clashes are inevitable, the price of allowing people to create their own columns.

That says to me that I should be able to make a *new* cc named 'Pages' (or Title or whatever) if I want, and I can't.

I tested all the standard columns Headings (in English) and got a popup "ERROR: The heading X is already in use" for each -- except Authors, 'On device' and Size.

Originally Posted by kovidgoyal

But you can actually have as many duplicate header names as you like (lookup names have to be unique). Thus there is no issue with having a builtin column with title Pages and a custom column with title Pages as well.

If you mean it's not harmful to the library and won't break anything when importing a library that already has a Pages header cc, I'm not disputing that.

I'm not saying that the dup Header check should be removed; but what I see happen appears to contradict your earlier post, and is inconsistently applied (Author etc).

[kovidgoyal]

Originally Posted by JimmXinu

But earlier you said:

That says to me that I should be able to make a *new* cc named 'Pages' (or Title or whatever) if I want, and I can't.

I tested all the standard columns Headings (in English) and got a popup "ERROR: The heading X is already in use" for each -- except Authors, 'On device' and Size.

I didnt say you can make new ones, I said you can have them. Which is the situation under discussion here, people already with a column titled Pages.
The point is there is no requirement in calibre that column titles, as opposed to lookup names be unique. The UI for creating columns prevents you from creating duplicate ones, for convenince, that's all.

[DisabledReader]

The built-in Pages column defaults to On in the Book Details panel and the Book Information (I) window. Should probably be Off by default.
Also, it's not showing in the Create Catalogue function.

[un_pogaz]

Originally Posted by kovidgoyal

That's a corrupted PDF that podofo cant read. It's not as tolerant of corrupted PDF as other software. And you can always share files by putting them in zip archives.

My concern was more about copyright.
And see the fix, thanks.

Originally Posted by kovidgoyal

I didnt say you can make new ones, I said you can have them. Which is the situation under discussion here, people already with a column titled Pages.

The point is there is no requirement in calibre that column titles, as opposed to lookup names be unique. The UI for creating columns prevents you from creating duplicate ones, for convenince, that's all.

Ah. And I used the French name when the restriction is for original names.
So, I can understand how this might be annoying for some people, especially for those who have already created a Page column before this "late" support... But what did you want Kovid to do? Seriously?
Sorry, I don't mean to be rude, but on a matter of relative comfort because "Their two column named Pages in my library!", please, that very light.
I understand wanting to compromise and suggestion to try to suit as much as possible, but a some point, line need to be draw.

Else,
Personally, I suggest that the UI, rather than complitly denied the creation of a new shared Header, the show a warning/confimation "You trying to create a Column with a shared Header with another. This can be confusing, are you sure?"
It is one of the rare things where Calibre return a unilateral No when is not a true limitation and just a confort safe guard.

[JSWolf]

Originally Posted by Karellen

Bzzzz! Wrong.

.

That's because you have invalid code. For example, you have nexted <p> which is invalid. But just <p></p> is valid. You cannot have a second <p> before you have a </p>.

Here's a screen grab showing the correct code,

[BetterRed]

Should the data item in question even be labelled 'pages' - probably not.

Has nothing to with bound sheets of paper, adolescents running hither and thither in the US Capitol, or Cinderella's Buttons. It determines the amount of space a book will consume on a graphical representation of a wooden bookshelf.

BR

[un_pogaz]

Originally Posted by BetterRed

Should the data item in question even be labelled 'pages' - probably not.

Has nothing to with bound sheets of paper, adolescents running hither and thither in the US Capitol, or Cinderella's Buttons. It determines the amount of space a book will consume on a graphical representation of a wooden bookshelf.

BR

But if is matter so little, why your custom column "Pages (#pages)" should take the priority on a Calibre "Pages (pages)"?

Also, yeah, use "pages" for reflowable e-book make no sens, but it also not just for graphical representation of a wooden bookshelf: This value give a sens of the size of the book itself. Is a skeuomorphism, a design style with visual cues (or affordances) that imitate the texture, shape, or function of physical objects. Some use words counts, but if pages is still so commonly used it because is still make sens for a lot of people. Like me, I can say that I can read a book of 300 pages in one day.

We can discute of the way Calibre caclul this value, but how it named, is a dead end and pointless.

[DNSB]

Originally Posted by Karellen

Not sure if this is a bug with Check Book in v8.99.x or if it has always been like this.

Noticed a paragraph with nested <p></p> tags but Check Book did not pick this up as an error. Tried with <div></div> tags also, and no error.

PHP Code:

<p>This is a <p></p>paragraph.</p> 


Should this be found?

Strictly speaking, nesting <p> tags is an error and I would correct them. Epubcheck does flag this as an error and it will prevent quite a few publishers from accepting an ebook.

OTOH, most renderers will not hiccough on that error.

[BetterRed]

Originally Posted by un_pogaz

But if is matter so little, why your custom column "Pages (#pages)" should take the priority on a Calibre "Pages (pages)"?

Also, yeah, use "pages" for reflowable e-book make no sens, but it also not just for graphical representation of a wooden bookshelf: This value give a sens of the size of the book itself. Is a skeuomorphism, a design style with visual cues (or affordances) that imitate the texture, shape, or function of physical objects. Some use words counts, but if pages is still so commonly used it because is still make sens for a lot of people. Like me, I can say that I can read a book of 300 pages in one day.

We can discute of the way Calibre caclul this value, but how it named, is a dead end and pointless.

The ONLY books for which I maintain a page count in a custom column (#pages/Pages), are those that have a format of HARDBACK, PAPERBACK or PDF otherwise it's empty (Undefined).

Oh, and Comics

Added : then there's the documentation for the widely used Count Pages plugin (which was released in May 2011) :-



BR

[Karellen]

Originally Posted by DNSB

OTOH, most renderers will not hiccough on that error.

It will split the paragraph, though. See image in post#255

[DNSB]

Originally Posted by Karellen

It will split the paragraph, though. See image in post#255

That I knew. Much like placing a <br/> in the middle of a sentence.

What I meant by hiccough was the renderer would error on that structure.

[JSWolf]

Originally Posted by un_pogaz

But if is matter so little, why your custom column "Pages (#pages)" should take the priority on a Calibre "Pages (pages)"?

Also, yeah, use "pages" for reflowable e-book make no sens, but it also not just for graphical representation of a wooden bookshelf: This value give a sens of the size of the book itself. Is a skeuomorphism, a design style with visual cues (or affordances) that imitate the texture, shape, or function of physical objects. Some use words counts, but if pages is still so commonly used it because is still make sens for a lot of people. Like me, I can say that I can read a book of 300 pages in one day.

We can discute of the way Calibre caclul this value, but how it named, is a dead end and pointless.

So a book with say a graphics for the chapter titles will show up a lot larger then it should because of the 1000 words per graphics. How is that representative of size when it shows up larger then it should?

[BetterRed]

I just discovered one can have a fixed width spine.

Why do the 'shelves' have to be horizontal, if they were vertical ('piles') one would not have to adopt the posture of a swivel-eyed loon to read the titles

BR