View Single Post
Old 03-09-2016, 07:32 AM   #25
fbrzvnrnd
Fanatic
fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.
 
Posts: 559
Karma: 400004
Join Date: Feb 2009
Device: ONYX M96
Quote:
Originally Posted by RbnJrg View Post
Ah, now I understand what you want to say. In order that CoolReader can know when a link is a note and when a link is a navigation element, you need to use the css [atribute] selector. Let's say that when you want a note, you should style your ebook with:

In your css stylesheet:

Code:
a [type="note"]  { /* and here you set the properties you want for notes, for example: */
     font-weight: bold;
     text-decoration: none;
     vertical-align: super; 
     font-size: 0.7em;
}
and in the .xhtml file:

Code:
<p>blah, blah, blah, blah <a type="note" href="#n1">1</a>, blah, blah, etc.</p>
CoolReader knows that the atribute type="note" is a note and not a navigation element. When a <a> selector doesn't have a type="note" atribute CoolReader will consider it as a navigation element.
Uhm. Why css? If I simple use the type element in <a> coolreader do not see it?


f.
fbrzvnrnd is offline   Reply With Quote