05-02-2018, 07:49 PM | #1 |
Junior Member
Posts: 6
Karma: 10
Join Date: May 2018
Device: none
|
Question re: Calibre bug report
Hi all. I don't understand some error messages I got when I had Calibre CHECK the eBOOK I created in Pressbooks. I'm only a code sophomore, so go easy on me, please.
1. Calibre CHECK BOOK error message: "WARNING: CSS: Property: Unknown Property name. [181:3: hyphens]****[OEBPS/baker.css]" The explanation reads: "This CSS construct is not recognized. That means that it most likely will not work on reader devices. Consider replacing it with something else." This construct being: .no-hyphens, span.no-hyphens, p.no-hyphens { hyphens: none; -webkit-hyphens: none; } which is the code that was already in Pressbooks. Yet when try to find a fix I get plenty Google hits for "hyphens: none; -webkit-hyphens: none;" being sound code. Should I just ignore the error as a non-error? 2. Calibre CHECK BOOK error message: Same deal, except this time regarding code for a textbox: margin-outside: auto; and margin-inside: auto; This was also code that was already in Pressbooks, and as far as I can tell it's sound. Should I just ignore the error as a non-error? Thank you so much for any feedback! |
05-02-2018, 11:23 PM | #2 |
creator of calibre
Posts: 43,850
Karma: 22666666
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
|
Those are warnings not errors and they refer to the fact that those CSS properties are not in the CSS 2.1 standard which means they may not be supported in some readers. It's up to you whether you are OK with ignoring them or not.
|
05-03-2018, 12:26 AM | #3 |
creator of calibre
Posts: 43,850
Karma: 22666666
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
|
Oh and just FYI
hyphens is not in any CSS specification (IIRC it is only present in the CSS3 Text module working draft) And margin-inside/margin-outside are not even in any CSS working draft. IIRC they are only used by Prince XML https://github.com/w3c/csswg-drafts/issues/255 |
05-03-2018, 01:32 AM | #4 |
Junior Member
Posts: 6
Karma: 10
Join Date: May 2018
Device: none
|
Thank you!
Thanks so much. Not just for your reply, but also for your genius and generosity in creating Calibre in the first place. Cheers!
|
05-03-2018, 03:43 PM | #5 |
Bibliophagist
Posts: 35,367
Karma: 145435140
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
If you haven't tried it already, you can check out the CSS validator at CSS Validator. It does give a bit more information about errors in stylesheets including some proprietary items.
Sample output: Code:
1 Unrecognized at-rule @namespace h 22 .epbody Value Error : height only 0 can be a length. You must put a unit after your number : 792 23 .epbody Value Error : width only 0 can be a length. You must put a unit after your number : 528 41 .paraindent Value Error : orphans 0 is not valid, only values greater than 0 allowed. : 0 42 .paraindent Property so-language doesn't exist : en-US 61 .paranonindent Value Error : widows 0 is not valid, only values greater than 0 allowed. : 0 |
06-04-2018, 05:26 PM | #6 |
Junior Member
Posts: 6
Karma: 10
Join Date: May 2018
Device: none
|
Sorry I never replied to this. Thanks for your helpful tip! I've used it several times since. Cheers.
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Question re: Calibre bug report | rapunza | Introduce Yourself | 2 | 05-02-2018 07:51 PM |
How to report a bug | osmin | Calibre | 4 | 06-20-2017 05:56 PM |
Bug report | mtravellerh | PocketBook | 303 | 11-03-2013 07:21 PM |
How to report a bug??? | tmlee51 | Calibre | 2 | 02-14-2012 11:07 PM |
Unable to report bug in bugs.launchpad.net/calibre | MNF | Calibre | 1 | 05-22-2011 06:34 PM |