My action from todayâs meeting is to summarise the discussion on https://issues.oasis-open.org/browse/OFFICE-3847.
Svante Schubert introduced the discussion by summarising the Proposal and Description recorded in JIRA. The standard currently specifies that, if the paragraph property fo:line-height has the value normal, this âdisables the effects of the properties Âstyle:line-height-at-least and style:line-spacingâ. The proposal is based upon the premise that, by disabling these other properties, the effect is supposed to be the same as setting the value of the property fo:line-height to 100%. In addition to proposing that this be made explicit in the standard, it is also proposed that the RNG schema be changed to make these attributes mutually exclusive properties on the same element. The use of any one of these properties would override the setting on the parent style.
During the discussion a number of points were made, with contributions from all meeting participants:
- In general the fo:line-height value normal is not expected to be the same as the value 100%, as for many fonts a value of 100% would place lines of text too close together for comfortable legibility.
- The intention of the current specification of fo:line-height is that, when the value is set to normal, the application determines the line height, disabling or ignoring any other properties that have the effect of specifying a fixed line height.
- Implementations might use a variety of strategies for determining line height, but typically will do so with reference to the metrics of the fonts used in the line in question.
- The terms âline heightâ and âdistance between two linesâ, which are used in the definitions of fo:line-height and fo:line-spacing, are currently undefined in the standard. There was discussion about the merit of introducing suitable definitions for these terms, possibly with reference to existing standards. Michael Stahl provided a link to some tutorial material on font metrics (see draft minutes). Some illustrations will probably be needed to support any such definitions.
- Regina Herschel pointed out that there had been many comments added since the issue was first created in 2013, and that these need to be carefully reviewed before deciding how to resolve the issue.
Iâd be most grateful if those in the meeting would add any further points that I have missed, and correct any misconceptions that I may have introduced.
Francis
From: office@lists.oasis-open.org <office@lists.oasis-open.org> On Behalf Of Patrick Durusau
Sent: 11 January 2021 18:05
To: ODF TC List <office@lists.oasis-open.org>
Subject: [office] Notes From 11 Jan. 2021 - Next meeting - 25 Jan. 2021
Greetings!
The ODF TC teleconference notes are below.
Hope everyone is at the start of a great week!
Patrick
*****
Patrick: Michael Stahl before holidays
Patrick: agenda approved by consent
Patrick: minutes of December 14, 2020 - approved by consent
Patrick: Has new employer - as of Jan. 1st working for Thorsten
Michael Stahl: allotropia GmbH
Patrick: Holidays for 2021 -
Regina Henschel: 1.Nov, All Saints' Day
Andreas Guelzow: February
Patrick: February 15th - Family Day
Andreas Guelzow: Easter Monday
Patrick: Francis - 3rd of May, 30th of August
Patrick: Patrick to clean list of holidays
Patrick: August 2nd - Holiday in Canada
Andreas Guelzow: August 2: Heritage Day
Patrick: Oct. 11th - holiday in Candada
Patrick: January 18, 2021 Martin Luther King
February 15 2021 Family Day
April 5, 2021 Easter Monday
May 3, 2021
May 24, 2021 Queen Victoria
May 31, 2021 Memorial Day
July 5, 2021 Independence Day
August 2, 2021
August 30, 2021
September 6, 2021 Labor Day
October 11, 2021
November 1, 2021 - All Saints Day
December 27, 2021 Monday after Christmas
January 3, 2022 Monday after New Years
Patrick: Holidays - for 2021 - by consent
Patrick: 5. Statements of use - review by the TC - 25th January 2021 the only agenda items
Regina Henschel: relationsship between "frame" and ""drawing object"?
Regina Henschel: relation ship between attribute of <draw:frame> and same as graphic property?
Patrick: Proposal to resolve Office-4100 needs to address these issues
Patrick: Opened and assigned to Regina
Patrick: line spacing is from baseline to baseline -
Patrick: Regina - can be the full height - but badly designed font, need to increase the baseline to baseline
Patrick: Regina - look at the font, is leading defined ok, but is not, need to calculate the needed leading
Patrick: Does 100% include leading from the font or not (Michael)
Patrick: Andreas - need a picture for the standard
Patrick: Look for glyph images to include
Patrick: Svante - give a summary of what has been discussed in the issue - others can add other comments - postpone to 1 Feb. 2021
Patrick: Francis will summarize today's discussion
Michael Stahl: sorry the phone ran out of batteries
Patrick: Regina - finds typos - how to collect typos for issues - There is a Github issue for editorial issues
Andreas Guelzow: I need to switch meetings. bye!
--
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