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: Chat log for May 24, 2017 - Next Meeting, May 8th, 2017


The ODF chat log for May 24, 2017:

anonymous morphed into Jos van den Oever
Svante Schubert: Hello everyone!
Michael Stahl seconds Svante's motion
anonymous1 morphed into Thorsten
Thorsten: hi, back at last
Patrick: 8 of 10
Patrick: https://issues.oasis-open.org/browse/OFFICE-2102
Patrick: "remove" element doesn't refer to the file but the
determination of where whitespace occurs
Patrick: Proposal for resolution of Office-2102 accepted unanimously
Patrick: caveat, more discussion of interoperability with Word
Patrick: After more discussion, Proposal for resolution of Office-2102
accepted unanimously
Patrick: https://issues.oasis-open.org/browse/OFFICE-2104
Patrick: 2104 is already odf-later
Patrick: https://issues.oasis-open.org/browse/OFFICE-2103
Svante Schubert: Regina: Two sequential table/paragraph with each having
a page break (the first after, the second before)
Svante Schubert: Regina: We found out that tested ODF applications used
only one page break, although two were defined
Svante Schubert: Michael: Schema says both break attributes are optional
Svante Schubert: Michael: The text of the spec defines something
different (only one of those attributes (page before or after) can be used)
Svante Schubert: Michael: maybe remove this restriction
Svante Schubert: Regina and Michael are suggesting to remove this
restriction from the spec text
Svante Schubert: We might extent the set of test documents to 'know'
more about the current ODF behavior and provide a test corpus for future
feature testing..
Svante Schubert: If valid documents are being serialized by current ODF
applications using a different XML set, we might simplify the set of
used XML or document their different meaning more adequate as Florian
had requested
Svante Schubert: As noted in
Svante Schubert: <text:soft-page-break> was used when serialized by MSO
Svante Schubert: Is their usage desired or is it redundant?
Svante Schubert:
Svante Schubert: Florian question was once:"Clarify how
master-page-break and fo:break-before resp. fo:break:after interact.
More precise: A master-page-break should break accoring to the
break-before resp. break-after values."
Michael Stahl: 19.497 style:master-page-name
Svante Schubert:
Svante Schubert: Next meeting on German Public Holiday,
Svante Schubert: May 1st
Svante Schubert: Patrick: Next Meeting on May the 8th
Patrick: May 1st holiday, next meeting May 8th!
Svante Schubert: bye

Hope everyone is at the start of a great week!


Patrick Durusau
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 

Attachment: signature.asc
Description: OpenPGP digital signature

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