See minutes online for a more detailed record of the discussions.
Charter renewal update
The proposed draft charter of the Interest Group has been sent to the Advisory Committee members for an informal discussion before a formal vote. The W3C Team has already started to explicitly reach out to persons in various communities for comments; any comments are welcome through, e.g., the relevant github issues system.
The past few weeks concentrated on the pagination issues and its relations to CSS. However, it is worth collecting other issues that the publishing community has v.a.v. CSS. Dave Cramer set up a first set of such issues which was discussed.
At the moment, the page contains a categorized list of requirements. It is not clear whether those requirements are fulfilled at all or not by current or planned CSS documents, whether the issue is the lack of implementations or problems (or not) in the specifications, etc. It was agreed on the meeting that an overall table will be created, on the basis of this list, showing those issues as well.
Some additional issues that were discussed are
- cross references, and their control (e.g., reference to generated content like bullet point numbers) is vital in, e.g., scholarly publishing; a better control (and implementations) of these features is very important. Note that this raises serious accessibility issues, too.
- additional control over the details of typography of fonts should be added, e.g., to make use of the various features that existing fonts have (different weights, optical properties, etc)
- to be checked whether the requirements of, e.g., CJK languages are properly handled (although some of these issues are taken care of by the Internationalization Activity at W3C)
- to be checked whether the current control over colors (reba, hsla) is adequate for publishing (although the limitations are probably on the monitor, i.e., hardware side that CSS cannot really control)
Finally, the group also has a publication called “Requirements for Latin Text Layout and Pagination” (latinreq). However, that document is (intentionally) very detailed; this dependency table can be seen as some sort of an executive summary.
Work to be continued…