CSS and other WARNINGS

[chaot]

Hola!

I would like to make a suggestion regarding the Edit books > Check book function.

It would be helpful to be able correcting the errors individually rather than entirety by:
Try to correct all fixable errors automatically

That would be (for some of us) more helpful: What is wrong? Automatically to correct and how?
Correcting in bulk can lose track.

Error OEBPS / Styles / stylesheet.css (line 37 column: 5)
is obvious: There is no
-epub-ruby-position
and no value over.

Note: This type of error can not be corrected automatically.

I'm posting this here although it is of course aimed at Kovid Goyal (which is watching anyway).

[kovidgoyal]

If you want to correct an error manually simply double click on it and the editor will jump to its location

[chaot]

Thank you, I knew that. But I would like to see 'step by step' the automatic correction delivered by calibre - to improve the learning effect. Especially by great amounts of errors.

[kovidgoyal]

I'm not sure I understand what you are asking. When correcting all errors, you can see all the changes made using the diff tool. When an individual error is fixable, there is a link that you can click to fix the individual error.

[theducks]

BTW that is a (yellow) warning.
There may be nothing that NEEDS to be corrected,
That all depends on your device. ADE rolls over and barfs on some "unknown" stylesheet entries (the EPUB spec says just ignore ), so you may need to REMOVE those lines

Worry about the 2 RED items at the top

[chaot]

Sometimes the questions / perspectives change even in respect to a specific matter - imho the dimension expands often by handling queries in calibre. But that doesn't matter. And to say it here once (again): We thank you so much for to help us and improving the matter if possible (and recommended).

Originally Posted by kovidgoyal

I'm not sure I understand what you are asking.

In addition to the tool
Try to correct all fixable errors automatically
I would like to get (something like)
Try to correct this specific error
If this is not possible for some reason: No action or message.

When correcting all errors, you can see all the changes made using the diff tool.

Where's the diff tool?
I know the Revert to ''xyz?'' taps (blue arrows left/right) and the Undo/Redo taps to see changes - but these are here not really helpfull
a) with a lot of changes made automatically one time
b) as the center part of the Edit book page isn't stable showing the same aspekt. Of course, there are line numbers to follow, I know.

Originally Posted by theducks

BTW that is a (yellow) warning.
There may be nothing that NEEDS to be corrected,
That all depends on your device.

Can be yes, can be no!? Would be advisable just to remove it, or not!?
To be serious: I have been working for years with calibre (trying to edit more than 10,000 books) but still do not have any e-reader (device), always I think they will get better / cheaper anyway next Christmas.

ADE rolls over and barfs on some "unknown" stylesheet entries (the EPUB spec says just ignore ), so you may need to REMOVE those lines

ADE???
I add the complete list of errors, you may see quite a lot (29) of the type: WARNING: CSS: Property: Unknown Property name.
Removing manually isn't so funny! The automatic doesn't do it. But could be!?

Worry about the 2 RED items at the top

Same book, but now 3 of them (don't ask for why). Lets try to sort out:
Look https://developer.mozilla.org/de/docs/Web/CSS/position

1) OEBPS/Styles/stylesheet.css (line: 14 column: 15)
position: ?;
Value ? doesn't exist.

2) OEBPS/Styles/stylesheet.css (line: 37 column: 5)
position: over;
Value over doesn't exist.
Nevertheless there is a difference between these 2 errors.
CSS: PropertyValue: Missing token for production Choice ...
CSS: Property: Invalid value for ''CSS Level 2.1'' property: over ...
Can you explain?

3a) OEBPS/toc.ncx (line: 13)
<navPoint class="chapter" id=" " playOrder="0">
respectively
3b) OEBPS/toc.ncx (line: 133)
<navPoint class="chapter" id=" " playOrder="20">
Comment given: The id is present on more than one element in OEBPS/toc.ncx. This is not allowed. Remove the id from all but one of the elements
+
Remove the duplicate ids from all but the first element

Why to use the first element?

Even beginners can think logically and see so many things! Showing links/pictures can often improve helping

[Terisa de morgan]

Originally Posted by chaot

I add the complete list of errors, you may see quite a lot (29) of the type: WARNING: CSS: Property: Unknown Property name.
Removing manually isn't so funny! The automatic doesn't do it. But could be!?

Filter information style (Alt + F): Other css properties: -epub-ruby-position. (for example). No need to remove it manually.

[kovidgoyal]

Automatic is not going to remove css properties. Just because a CSS property is unknown does not mean it should be removed. An unknown CSS property simply means that the CSS property was not defined in the CSS 2.1 spec. There are plenty of useful CSS properties that dont exist in that spec and that work in actual reader devices.

[DrChiper]

Originally Posted by kovidgoyal

There are plenty of useful CSS properties that dont exist in that spec and that work in actual reader devices.

Keeping that in mind, wouldn't it be thinkable to make the check book function able to learn as a way to allow the user to extend the book check function capabilities. Then when you use for example some obscure CSS property because it does work on your device, but is not part of the currently supported properties, you are able to avoid unnecessary warnings.

No need to say that the risk on using those user added properties is then fully with the user. But it might support perhaps some knowledgeable power users.

Just a thought.

[kovidgoyal]

Sure, patches are welcome

[chaot]

Originally Posted by Terisa de morgan

Filter information style (Alt + F): Other css properties: -epub-ruby-position. (for example). No need to remove it manually.

Please note that we use different keyboards, Spanishs are not effective here. (Alt + F) opens me the Tab File.
But I found it anyway: Edit book> Tools> Filter style information.

Annex shows the filtered error list of WARNING: CSS: Property: Unknown property name (total 29).

But they differ in types (8):
[60: 5: -epub-ruby-position] (19x)
[62: 5: break-after] (3x)
[379: 5: break-before] (1x)
[404: 5: -epub-hyphens] (2x)
[405: 5: -webkit-hyphens] (2x)
[559: 5: -webkit-line-break] (1)
[560: 5: -webkit-nbsp-mode] (1)
[571: 5: word-wrap] (1)

Note: The beginning numbers figure only the locations (line: column) (they are here unrelevant).

The tool is pretty picky. It accepts (and removes) only the search terms in an exact given form, otherwise appears message: No matching style rules were found. For example: -epub-ruby-position (NOT: -epub-ruby-position:

Using the tool opens automatically the window Differences between books. You can see/control the just made changes (and even reset: Revert changes).
Without closing this page you may make in Edit Book> Check book further Re-run checks. The corresponding values ​​(eg. over) get also deleted. The list is now reduced to the still pending list of Errors/Warnings/Informations. Each additional filtering opens a new window Differences between books.

Works really breathtaking!

Note: Apparently makes this method of filtering only sense for frequent occurrences (here the first two):
[60: 5: -epub-ruby-position] (19x)
[62: 5: break-after] (3x)
The rest is handled faster manuell.

One little discrepancy ??? still struck me:
The first warning [60: 5: -epub-ruby-position] related to line 60.
But page Differences between books begins with correction on line 14 position:?; and then follows line 60 -epub-ruby-position: over;.

Why?

Your post was very helpful.

Even a blind chicken finds a corn once!

[Terisa de morgan]

Glad you find it useful. I'm aware of keyboard (and language) differences, it was a translation "on the fly", bad, as you have noted. Another think I haven't commented (I suppose you already has found it) is that you can put different elements, comma-separated, and it removes all.

[chaot]

Originally Posted by Terisa de morgan

Another think [...] is that you can put different elements, comma-separated, and it removes all.

I already fiddled around with it, thanks anyway of collective thinking.

@Kovid Goyal please look: Making Filter style information input field bigger or variable for a better overview. Worth changing!?

[JohnRJohnson]

OK. I know how to click on the error and see it jump to the location in the XHTML. Not much help since I know nothing about XHTML. It would be a lot easier if I knew where the problem was in the actual file. Looking at this code, I have no idea what I would be fixing. The error says: CSS: Property: Unknown Property name. [1:65: -webkit-transform-origin] What does that mean? When I started learning INDESIGN so that I could create digital files, I didn't know I would also have to learn HTML. Extremely frustrating.

[theducks]

Originally Posted by JohnRJohnson

OK. I know how to click on the error and see it jump to the location in the XHTML. Not much help since I know nothing about XHTML. It would be a lot easier if I knew where the problem was in the actual file. Looking at this code, I have no idea what I would be fixing. The error says: CSS: Property: Unknown Property name. [1:65: -webkit-transform-origin] What does that mean? When I started learning INDESIGN so that I could create digital files, I didn't know I would also have to learn HTML. Extremely frustrating.

First of all:
That is a warning (this is one of 2 common ones that frequently appears)

Second of all:
That one does not need to be fixed. just ignore. even touchy Adobe RMSDK works just fine with it present.

It is an additional control outside the EPUB spec (thus the warning), that many QT based viewers (Calibre, Sigil) use to keep tighter control.

Errors MUST be fixed. There is no magic bullet. Some errors are only discovered LATER, when the next command is illegal because the prior one did not complete. You need to discover WHERE the real command end was supposed to be.


Learning to use the tools and rules of ones trade is what most professionals do. No one made you choose to be your own Layout, Marketing ... departments in addition to the craft of writing, then you will need to expand your education or hire an expert for that phase.