W3C home > Mailing lists > Public > public-ppl@w3.org > February 2013

Re: Customer requirement, a critque

From: Liam R E Quin <liam@w3.org>
Date: Sun, 24 Feb 2013 23:28:42 -0500
To: Patrick Gundlach <gundlach@speedata.de>
Cc: xsl-fo Community Group <public-ppl@w3.org>
Message-ID: <1361766522.4624.155.camel@localhost.localdomain>
On Sun, 2013-02-24 at 14:13 +0100, Patrick Gundlach wrote:
> > Rather than just go in an modify them, comments on the requirements.
> > http://www.w3.org/community/ppl/wiki/CustomerRequirements
> > 
> > 3. -1 talking about products, surely we should be talking of
> > fo:blocks? Like it. Just a bigger version of 1?
> >   Please fit [id range perhaps?] or the contents of a
> > block-container, in n pages (please add 'starting on
> >   new page' as an option)
> 
> I am not sure why you use the term "fo:blocks". As far as I know, this is not a special FO community.

It was originally an FO community.

Note that there's an implementation for Apache FOP of copy-fitting (with
a somewhat configurable strategy) compatible with the design in the
XSL-FO 2 draft. Changing the order of the products might be
hard ,although we had started on a design for alternate content that
might work for it and also for (5), adding content to fill the table of
contents. Another way might be to put the content always there and have
overflow: hidden.

We didn't get as far as describing how multiple output streams would
work, I think, but the design would likely work for (4), product catalog
in many languages, in many cases; where it didn't, sure, you'd probably
want a processor-specific extension. I've done synoptic pagination in
the past, probably with some similar constraints to catalog printing
(e.g. if someone on the 'phone says, turn to page 36, see the first
image, it had better be the same (or a corresponding image) in all
versions) and some dissimilar (e.g. whitespace handling), although not
with XSL-FO.

A strength of XML has been that non-programmers can do some
sophisticated text processing with it.

You can always come up with things a given system can't handle, of
course. The idea is to make system that can handle all of the essential
needs of most or all of the users, and enough of the inessential needs
of those users to make them a little happier. It's not to satisfy every
fantasy :)


-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml
Received on Monday, 25 February 2013 04:28:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 25 February 2013 04:28:45 GMT