[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Notes from 1 March 2021 ODF TC meeting
Greetings! Minutes from our 1 March 2021 ODF TC teleconference are below. Hope everyone is at the start of a great week! Patrick ********** Patrick: Sorry for the bad paste, I've befouled my keyboard settings on a Greek project. ï But, at least I still has ASCII for the meeting notes! Patrick: We have quorum Patrick: Agenda - Regina - want to address the proposal template take up before #4 Patrick: Before Regina - FYI on Daylight Savings time Patrick: agenda - with those changes - approved by consent Patrick: Minutes of 22 February 2021 - approved by consent US clocks "spring forward" on Sunday, March 14th. European clocks follow suit on Sunday, March 28th. Patrick: - dates from Chet Patrick: Keep meetings at NOON - Patrick: Keep the correct time link for the meeting - Regina - Regina Henschel: https://wiki.oasis-open.org/office/ProposalTemplate%20ODF%201.4 Svante Schubert: Suggestion for previous time topic: March 1 and March 29 (incl. NY) https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021&month=3&day=1&hour=17&min=0&sec=0&p1=25&p2=37&p3=179 https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021&month=3&day=29&hour=16&min=0&sec=0&p1=25&p2=37&p3=179 Patrick: Proposal Template Incremental Proposal Template Incremental Patrick: Not for discussion this week - set for next week Svante Schubert: I love Reginas approach. Enabling the feature based review and fast agile round-trip to an OASIS committee specification. Patrick: Andreas - export and import to ODF - features are agnostic to ODF - never really a question of ODF - Svante Schubert: Making the intermediate XML until an OASIS/ISO standard is being published unnecessary. Allow fast review & adoption. Patrick: Regina - before export to ODF - define an attribute in gnumeric namespace - Patrick: Svante - applications should not use ODF namespace - fast track for new features - Patrick: Andreas - in the past - someone has to have implemented it - for feature to be considered Michael Stahl: to Andreas: the reason we always said we only want to add things that have already been implemented is that we don't want to add features to ODF that later turn out to be too difficult or impossible to implement in an interoperable way; i don't see this risk with the proposed workflow because we get immediate feedback from implementers Svante Schubert: The advantage could be to activate the developer to do work according to the wishes of the TC: test documents, XML design. Instead of talking to the developer, when his task was already done (and is not much willing to changed a finsihed task). Patrick: Set Regina's template for discussion - 8 March 2021 Patrick: Michael - feedback process back to developers is too long from the standards process - Patrick: https://issues.oasis-open.org/browse/OFFICE-3843 Patrick: We need to describe how a border works with a shadow - Patrick: Regina - need a marker of the position of the text with regard to the shadow Svante Schubert: Regina: No decision how the text outside of the border is drawn with the shadow. Unclear if text behind the shadow or overlapping? Patrick: marker -> margin Svante Schubert: Regina: To descripe this we likely need a margin to position the content related to the shadow Svante Schubert: Regina: Current implementations are using overlapping of shadow & content Patrick: Michael - shadows have margins Svante Schubert: ^NOT overlap (only CSS do overlapping) Regina Henschel: What should happen with nested spans? text <span> some text <span> other text </span> text </span> outside Patrick: Michael - inner one should override the outer ones Svante Schubert: Nested text:span are just a syntax feature, but it just equal to split up spans on one level. Patrick: 6.1.7 The <text:span> element represents the application of a style to the character data of a portion of text. The content of this element is the text which uses that text style. The <text:span> element can be nested.The <text:span> element represents the application of a style to the character data of a portion of text. The content of this element is the text which uses that text style. The <text:span> element can be nested. Patrick: overrides is only on the conflicting sub-span Patrick: Francis - flattening has 3 boxes - outer span , inner span , outer span, if any Patrick: Andreas - display of multiple spans with same properties is not defined. Patrick: possible bug in 1.3 -- 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]