I made a discovery, but should I use it?

[Tex2002ans]

Originally Posted by travger

Now it takes me whole day to check all the classes and figure out what they do.

In Sigil's Code View, if you right click a class and click "Go To Link or Style" it will jump you right into the CSS where that class is located. This really speeds things up when trying to figure out what class is doing what (especially with Calibre's "calibre01", "calibre02", "calibre03" classes.)

[travger]

Originally Posted by Tex2002ans

In Sigil's Code View, if you right click a class and click "Go To Link or Style" it will jump you right into the CSS where that class is located. This really speeds things up when trying to figure out what class is doing what (especially with Calibre's "calibre01", "calibre02", "calibre03" classes.)

In that end I have no problems, it's mostly "do I need 'calibre32' or 'calibre55' and where are they?". Report shows the file and I can search for the classes but usually it's too much clicking and copypasting to bother.

Though I must really start using Replace All more often and get accustomed that it only feels out of control.

[theducks]

Originally Posted by travger

In that end I have no problems, it's mostly "do I need 'calibre32' or 'calibre55' and where are they?". Report shows the file and I can search for the classes but usually it's too much clicking and copypasting to bother.

Though I must really start using Replace All more often and get accustomed that it only feels out of control.

The report also show 1st discovered (file) usage, makes it easy to check out usage context in many cases.
It is those crazy use of spans everywhere that drive me

[Toxaris]

Look at the stylesheet and check out the differences between the styles. If the difference is minor (font-size: 0.993 instead of font-size: 0.995), delete the styles. Usually you can cope between 5-15 styles and that includes seperate styles for italic, bold and so on.

[travger]

Originally Posted by theducks

The report also show 1st discovered (file) usage, makes it easy to check out usage context in many cases.
It is those crazy use of spans everywhere that drive me

I hear you! Right now I have a book where the only p-s are in headings Every paragraph is between spans AND divs.

It still looks very nice, but I'm curious how much smaller the file will be, so I think it's perfect to experiment on with Replace All.

[Turtle91]

Originally Posted by HarryT

Absolutely - that's exactly the way to do it. That's why they're called cascading style sheets, because each new style modifies the previous ones. If you have a "paragraph" style, which indents paragraphs, and you want a style for "initial paragraph" with no indent, simply specify the lack of indentation as a modification to the normal paragraph style; don't duplicate the entire style.

I was just testing this in Sigil...I don't know if it's a QT bug or not but it didn't seem to work as expected. I had the following CSS/HTML:

div.fluff p {text-align:justify; font-style:italic}
p.att {text-align:right; font-style:normal}

<div class="fluff">
<p>Stuff, stuff, and more stuff.</p>
<p>Stuff, stuff, and more stuff.</p>
<p>Stuff, stuff, and more stuff.</p>
<p class="att">Should be normal and right aligned</p>

<p>Stuff, stuff, and more stuff.</p>
<p>Stuff, stuff, and more stuff.</p>
<p>Stuff, stuff, and more stuff.</p>
<p class="att">Should be normal and right aligned</p>
</div>

Neither the right align of the font style normal were applied in the "att" class unless I used the !important tag in the "att" declaration.

Anyone seen this before?

[pdurrant]

Originally Posted by Turtle91

I was just testing this in Sigil...I don't know if it's a QT bug or not but it didn't seem to work as expected. I had the following CSS/HTML:

div.fluff p {text-align:justify; font-style:italic}
p.att {text-align:right; font-style:normal}

<div class="fluff">
<p>Stuff, stuff, and more stuff.</p>
<p>Stuff, stuff, and more stuff.</p>
<p>Stuff, stuff, and more stuff.</p>
<p class="att">Should be normal and right aligned</p>

<p>Stuff, stuff, and more stuff.</p>
<p>Stuff, stuff, and more stuff.</p>
<p>Stuff, stuff, and more stuff.</p>
<p class="att">Should be normal and right aligned</p>
</div>

Neither the right align of the font style normal were applied in the "att" class unless I used the !important tag in the "att" declaration.

Anyone seen this before?

I'm not sure why that's doing that, but I'd suggest changing
div.fluff p {text-align:justify; font-style:italic}
to
div.fluff {text-align:justify; font-style:italic}

there's no need to specify the p — they inherit from the div anyway.

[pdurrant]

Originally Posted by Turtle91

I was just testing this in Sigil...I don't know if it's a QT bug or not but it didn't seem to work as expected. I had the following CSS/HTML:

div.fluff p {text-align:justify; font-style:italic}
p.att {text-align:right; font-style:normal}

<div class="fluff">
<p>Stuff, stuff, and more stuff.</p>
<p>Stuff, stuff, and more stuff.</p>
<p>Stuff, stuff, and more stuff.</p>
<p class="att">Should be normal and right aligned</p>

<p>Stuff, stuff, and more stuff.</p>
<p>Stuff, stuff, and more stuff.</p>
<p>Stuff, stuff, and more stuff.</p>
<p class="att">Should be normal and right aligned</p>
</div>

Neither the right align of the font style normal were applied in the "att" class unless I used the !important tag in the "att" declaration.

Anyone seen this before?

Aha! I have it. Your problem is the selector specificity. See 6.4.3 here:

A selector's specificity is calculated as follows:

count 1 if the declaration is from is a 'style' attribute rather than a rule with a selector, 0 otherwise (= a) (In HTML, values of an element's "style" attribute are style sheet rules. These rules have no selectors, so a=1, b=0, c=0, and d=0.)
count the number of ID attributes in the selector (= b)
count the number of other attributes and pseudo-classes in the selector (= c)
count the number of element names and pseudo-elements in the selector (= d)

for both, a=0 and b=0

but for div.fluff p, c=1 d=3
for p.att, c=1, d=2

so div.fluff p overrides p.att, unless you make it important (which you should probably not do.)

[Turtle91]

wow! I didn't realize specificity went into such detail...I thought an inline class would take priority (like an inline style) over a parent style.

Thanks for the edumacation!

[pdurrant]

Originally Posted by Turtle91

wow! I didn't realize specificity went into such detail...I thought an inline class would take priority (like an inline style) over a parent style.

Thanks for the edumacation!

I didn't know either, until I looked it up. It does seem an odd way to define the priority of styles, but that's the way it's done.