OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [office] Public comment #20 -- default print range in tables

2008/7/1  <robert_weir@us.ibm.com>:

> What you state is a fact.  But it is also irrelevant.
> The question is not what a default value would mean for conformance.  The
> question is whether this value should be defined as a hint, and whether it
> should have a default.

Read my earlier email.

> I think it would be particularly bad practice to define a feature in ODF in
> a way which contradicts existing application practice as well as user
> expectations.

Despite the OP specified issue?

  I believe that a user would be astonished if an application
> printed the range stored in the document rather than the range he/she has
> currently selected.

See my last email.

> This can all be solved if we define a runtime model, a runtime DOM, events,
> etc.

How about leaving that to implementors.

 Then we just say that when you print, you print the current value of
> printrange in the DOM,

And what if an implementor doesn't use the dom?
Oasis get it in the neck?

> But I don't sense any appetite for doing this in ODF 1.2.  We're a standard
> for a document format,

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.


Dave Pawson

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]