W3C home > Mailing lists > Public > public-digipub-ig@w3.org > November 2014

RE: [Page DOM] page counters across multiple documents

From: Siegman, Tzviya - Hoboken <tsiegman@wiley.com>
Date: Tue, 18 Nov 2014 06:45:16 -0500
To: Robin Berjon <robin@w3.org>, Dave Cramer <dauwhe@gmail.com>, "W3C Digital Publishing IG" <public-digipub-ig@w3.org>
Message-ID: <C274A5503C851E43A8ED400AC86E0285048FCDF1DE@SOM-MB.wiley.com>
What about a publication that includes cross-references to every figure? Consider also that, terms like "figure" and the figure numbering are (ideally) generated by CSS in both the link and the target (with a little scripting help). . Probably it will process once and then cache, but would it be a long and painful process? 

Tzviya Siegman * Digital Book Standards & Capabilities Lead * John Wiley & Sons, Inc.
111 River Street, MS 5-02 * Hoboken, NJ 07030-5774 * 201-748-6884 * tsiegman@wiley.com

-----Original Message-----
From: Robin Berjon [mailto:robin@w3.org] 
Sent: Tuesday, November 18, 2014 5:32 AM
To: Dave Cramer; W3C Digital Publishing IG
Subject: Re: [Page DOM] page counters across multiple documents

On 03/11/2014 14:10 , Dave Cramer wrote:
> Most book-like documents consist of multiple HTML files. Consider a 
> tiny book with two HTML files, one for the first chapter and one for 
> the second chapter. We'd like to display page numbers throughout the 
> document, so chapter two would need to know how many pages were in 
> chapter one.
> CSS counters can be initialized, but we'd need some method to obtain 
> information about previous and subsequent files in the same book, and 
> pass that to the page and pages counters. This could get expensive...

I've thought about similar problems a few times in the past, specifically how to handle things like ToCs and in-document cross-references for multi-page specs (for ReSpec).

I haven't found any kind of magic bullet... You basically have to process all the documents. Hopefully you can cache the result of that processing so it only needs to happen once.

Robin Berjon - http://berjon.com/ - @robinberjon

Received on Tuesday, 18 November 2014 11:45:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:35:53 UTC