2008/7/1 <>:
>
>
>>
>> So reflect on what happens, not how.
>>
>> 1. No default in the spec.
>> 2. User selection overrides stored values for a print
>> 3. User selection stored over existing stored values .
>> 4. No value, request one.
>> 5. No more. Apps have run out of options. Hence non-compliant if they
>> get this far
>>
>> Job done.
>>
>
> I don't believe #4 is what happens today.
I'm proposing this sequence for 1.2, to address what happens today
(I.e. it is unspecified)
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
