2008/7/1 <>:
>
> A few other scenarios:
>
> 1) A user loads a ODF spreadsheet document where no print range was
> specified. They select a range of cells and click the print button. What
> prints? The selected range? Or the default range? Note that they have not
> saved the document with the new print range yet.
You're detailing how now. That's implementation dependent.
>
> 2) A user loads an ODF spreadsheet document with a pre-defined print range.
> They select a range of cells and click the print button. What prints? The
> selected range? Or the stored print range? Note that they have not saved
> the document with the new print range yet.
Ditto. Another vendor uses common sense and takes the selected range
as a print selection. Hence complies with the spec.
>
> 3) A user loads a ODF spreadsheet document where no print range was
> specified. The user clicks the print button. The application queries the
> user for what range they want to print.
Ditto. Direct interpretation of the spec. If there isn't a range specified,
ask the user.
>
>
> My point here is that runtime print behavior is more complicated than what
> we are saying in the standard.
So say 'what', simply. Not how.
The stored print range expresses what the
> document author
or last user
set as the preferred print range. But it does not determine
> what is printed the next time. It can be overridden by the user, in the
> application, without changing the file. So it is really a hint or a
> preference.
Which vendors can work with.
>
> Similarly, the lack of a specified print range could invoke some logic to
> calculate a default print range,
And get the nasty user surprises you see today.
>
> Once we go down the road of defining runtime print behavior
No. We specify what.
Implementors say how.
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
