- From: Dave Cramer <dauwhe@gmail.com>
- Date: Wed, 24 Jun 2015 10:40:22 -0400
- To: W3C Digital Publishing IG <public-digipub-ig@w3.org>
- Message-ID: <CADxXqOxAyhXs3Xw0auY4Q06AkSzg5Tqdmv03MAb49H2vVcjZkg@mail.gmail.com>
On Mon, Jun 22, 2015 at 4:12 PM, Dave Cramer <dauwhe@gmail.com> wrote: > During the call today, Ivan expressed interest in having some more detail > on the CSS priorities. I've just started such an attempt: > > > https://docs.google.com/spreadsheets/d/15IsDMPwSXx197Iqe4I9xh7K8anmJ5c0-OFEG7w0LHYM/edit?usp=sharing > > I have lots of work to do here, but just wanted to know if this looks like > a useful approach. > > Yesterday I asked folks on Twitter what improvements they wanted to see to CSS. The most common responses were to have ebook reading systems support more of the CSS that browsers do. The other major theme was about how ebook reading systems override the CSS in EPUB files. This process is totally opaque to ebook developers, very frustrating for all involved, and results in unpredictable end results. Shining some light on this process, providing a way for developers to respond to various types of overrides, and giving end users the control they need would be of immense value. I think this should be a priority of DPUB, perhaps even a task force. Many of the other suggestions related to typography--better control over hyphenation, open type font features such as ligatures, and drop caps. * * * I've added priorities to the spreadsheet[1], and sorted by those priorities. In general, specs exist for most of the features listed, but browser support is often spotty. In many cases, some major browsers support a given feature, and other major browsers don't. And that is our fundamental issue. Dave [1] yes, all my priorities are wrong.
Received on Wednesday, 24 June 2015 14:40:50 UTC