View Single Post
Old 03-18-2014, 01:55 PM   #972
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,340
Karma: 171313058
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Caramon77 View Post
We really need

- Hyerarchical Indexes
- Better detection of note links
- Choice to display/not display fixed title on top in ACCESS
- Automatic detection of "main text CSS classes" and more aggressivity on 'em, mainly for line-height property.
1. Hierarchical tables of contents? Would be nice to have but not a real need for me.

2. Better detection of note links? In most of the books I read that have footnotes, the problem is the footnote link is so small, it's hard to touch. The Aura does better here with the finer resolution of it's capacitive touch.

3. Title display in ACCESS? Again not a real biggie for me.

4. Huh? I've never noticed that CSS styles either in a stylesheet or embedded in the text has had issues with being detected. I have seen issues where the creator of the ebook has forgotten the that CSS stands for Cascading Style Sheets. When you apply multiple styles, inheritance can cause odd results. My personal preference is to handle styling though the stylesheet.css and not by embedding styling in the body text.

Regards,
David

Last edited by DNSB; 03-18-2014 at 06:36 PM.
DNSB is online now   Reply With Quote