[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Notes for ODF teleconference 10 May 2021
Greetings!
The notes for the ODF teleconference on 10 May 2021 follow.
Hope everyone is at the start of a great week!
Patrick
********************
Patrick: quorum yes
Patrick: agenda approved by consent
Patrick: minutes of April 26th - approved by consent
Patrick: Clarification of charter passes by consent
Patrick: form:default-button "implementation-defined"
Patrick: If multiple buttons with form:default-button attributes with values of true are present in a form, it is implementation-defined which button is the default for the form.
Patrick: There shall be only one button with the form:default-button attribute with value of true are present in a form.
Patrick: There shall be at most one button with the form:default-button attribute with value of true are present in a form.
Patrick: <form:button>
Patrick: Michael - implementation-defined - means it has to be documented but problem should not exist in the first place
Patrick: apparently uses the first default button presently
Patrick: I'm assuming "first" means in document order?
Patrick: Regina - LO has a field where you can make it a default button
Patrick: Svante to add a test document to the issue
Patrick: Regina - UI allows 2 buttons as default buttons
Patrick: deferred for discussion
Patrick: +1 to Regina's comment on being consistent with <table:highlighted-range>
Svante Schubert: see https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part3-schema/OpenDocument-v1.3-cs02-part3-schema.html#attribute-table_name_element-table_operation
Svante Schubert: and https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part3-schema/OpenDocument-v1.3-cs02-part3-schema.html#element-table_highlighted-range
Patrick: implementation-defined -> implementation-dependent
Patrick: resolved by consent - implementation-defined -> implementation-dependent
Patrick: implementation-defined logo -> implementation-dependent logo is the suggested change
Svante Schubert: https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part3-schema/OpenDocument-v1.3-cs02-part3-schema.html#attribute-presentation_show-logo
Patrick: Regina - logo meant so be advert for the implementation so no need for documentation
Patrick: resolved by consent - implementation-defined logo -> implementation-dependent logo
Svante Schubert: https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part3-schema/OpenDocument-v1.3-cs02-part3-schema.html#attribute-style_num-letter-sync
Patrick: Regina - for LO - aa, bb true - other case not written at all -
Patrick: Svante to prepare test documents
Patrick: Regina - tested in Word - aa, bb, - but ab doesn't work. no default value
Patrick: Regina will make documents for the issue.
Patrick: Regina - not documented in the issue but the change was made
Patrick: Bookkeeping -
Patrick: Resolved/closed
Patrick: is there a comparison - sort order for color?
Patrick: where is high to low?
Patrick: Regina sees it as style applied to the cell - we have lots of styles that can be applied to a cell
Patrick: Andreas - filters in Gnumeric - keep the cell format with the value - sometimes not - when sorting - having formatting with a filter - what is supposed to happen - does change in color change what is visilble?
Patrick: Michael - what is the difference to other filter options? If you change something there, visible/invisible changes
Patrick: Andreas - styles are separate from the content of the cell. filtering on something other than content.
Svante Schubert: see https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part3-schema/OpenDocument-v1.3-cs02-part3-schema.html#attribute-table_data-type
Patrick: Andreas - ODF styles and content are separate from each other - this blurs that distinction by filtering by style
Patrick: Andreas - colors can be used for other purposes
Michael Stahl1: https://bugs.documentfoundation.org/show_bug.cgi?id=76258
Patrick: Andreas - if we start filtering, this will become even more complicated - what are the user expectations?
Patrick: Andreas - what if alternating gray/white rows? would have to define default behavior -
Patrick: Francis - could create contradictory statements of what is to appear.
Patrick: Svante - user is using color as metadata
Patrick: Andreas - need to describe how it relates to other features/formatting -
Patrick: Andreas - danger we will underspecify
Patrick: Svante - look at Excel - expected behavior
Patrick: Adjourned
-- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]