Beta testers for calibre 3.0 needed

[Martina Schein]

I just edited an eBook with the Caliber editor and discovered the following error (editing the table of contents):
Whenever I pick different points through drag and drop under a superior point, the editor sorts these points from bottom to top and not from top to bottom.
The two screenshots (first = right / second = wrong) are for visualization purposes.


Windows 10, 64Bit
Calibre 2.99.5

[kovidgoyal]

@DD: For the erorr when deleting multiple users. https://github.com/kovidgoyal/calibr...9b2329284a7cdb

As for 3b it does not really matter as library names are matched case-insensitively by the restriction rules. However, it should be fixed in the next beta.

[kovidgoyal]

@Martina: This should take care of it: https://github.com/kovidgoyal/calibr...ceaf096112ae33

[Martina Schein]

Thank you for this, Kovid.

[Divingduck]

@Kovid,
a cosmetic one:
Custom column: Type Long text, interpret this column as Short text like a title.

Is it possible to trim the display of this column in Web-GUI/details to the length of used characters? Just now it show a big area of blanks after the last character

[Divingduck]

@Kovid, thanks a lot too.

[Atherton25]

@Kovid
Awesome, I appreciate it.

I noticed something and thought I'd bring it up. You *may* want to modify the alt/help text for 'Ignore user-defined metadata fields' to include more information or some sort of example. I still haven't got mine to work right, though I'm currently trying different modifications to get it to work.

IE, I tried using the lookup name with and without the #, using no space, and a space after the comma and none of them worked. Should I be using the column header? I did try, but it didn't seem to work. Is it capitalization dependent? I may not have done that correct, if it's using the header.

Just in case, I have almost 2 dozen columns I was trying to block, is there a limit?

[BetterRed]

Originally Posted by Divingduck

@Kovid,
a cosmetic one:
Custom column: Type Long text, interpret this column as Short text like a title.

Is it possible to trim the display of this column in Web-GUI/details to the length of used characters? Just now it show a big area of blanks after the last character

I'm seeing different but also undesirable effects with long text columns :



Came From is Plain text, Show heading in the side
Location is HTML, Show heading on the side

I don't think this was happening in earlier beta's.

I've also noticed different fonts are used. Plain text uses a CN-like font, and HTML uses a TNR-like font, but everything else looks a bit Verdana-ish. I don't mind the the CN-like for Plain text, but I'd prefer the HTML to be the same as everything else - Verdana-ish. Is there somewhere I can control this?

BR

[JSWolf]

Any idea yet why when reading with Firefox, I lose that one line in that one chapter?

[kovidgoyal]

@JSWolf: No idea, haven't been able to repoduce it. Most likely it is some minor glitch in Firefox. Firefox does tend to have more buggy support for rendering than Chrome. For example, it does not support CSS 3 column-break which means that inline page breaks will not work in the reader on Firefox. https://bugzilla.mozilla.org/show_bug.cgi?id=549114

[kovidgoyal]

The problem with long text columns is somewhat gnarly. The issue is that because they contain arbitrary HTML, they are a security risk. So I changed them to display in a sandboxed iframe. The problem is that iframes have sizing issues. Not sure if that is going to be fixable or not.

I can probably fix the font being different issue.

[kovidgoyal]

@Atherton: That setting only affects the OPDS and /mobile views. Not the main web interface. I'll add an example to the help string. You use the lookup name, which is the name you get by hovering over the column header in the main calibre program. As discussed way back somewhere in this thread with BetterRed, the web UI will likely grow some version of a preference controlling the displayed fields at some point.

[kovidgoyal]

I fixed the rendering issue for at least long text columns that are to be interpreted as plain text. https://github.com/kovidgoyal/calibr...4f572c158ae920

There is still a problem if you have a long text column interpreted as HTML or markdown with heading at the side. My advice is, dont do that, instead put heading above.

[eschwartz]

Originally Posted by kovidgoyal

Oh well, I decided to implement this, turns out to not be too hard as there was already existing code for it (originally I intended the new server to have the same restriction capability as the old server). Will be in the next beta release.

Thanks.

Although it looks like you haven't wired this up to calibre-server --manage-users yet.

Speaking of which, I was able to use the CLI for that while calibre was running (in fact, while I was looking at the Preferences UI for managing calibre-server users).
I guess this is exempt because it only touches the user database and it reads directly from there rather than running a potentially-conflicting in-memory copy?

[kovidgoyal]

Oh and I should note that the iframe sizing issues are peculiar to firefox, they dont show up in chrome, at least on my sytem, which is why I didn't notice them originally.