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: ODF Chat log for 6 March 2017


The chat log for the ODF teleconference, 6 March 2017:

anonymous morphed into Jos van den Oever
anonymous morphed into Thorsten
Patrick: https://issues.oasis-open.org/browse/OFFICE-2102
Patrick: mostly talking about input fields, content of other fields,
generated so doesn't matter as much, not user input.
Patrick: From Michael's comment in Jira: the elements where the decision
matters most are text:text-input and text:variable-input
Svante Schubert: What opportunities do we have to fix the problems?
Patrick: apply whitespace rule if and only if <text:s> is allowed in the
parent element
Svante Schubert: Michael: Rephrase white-space handling to drop
whitespacehandling from thoe elements where text:s (etc.) is not allowed.
Patrick: what elements should have <text:s> allowed as a child element?
Svante Schubert: The existing ones are in ODF 1.2:
Svante Schubert: Consumers shall collapse white space characters that
occur in those elements where <text:s> [6.1.3], <text:tab> [6.1.4] and
<text:line-break> [6.1.5] are allowed as element content.

now, in ODF 1.2 that would mean:
* text:p
* text:h
* text:span
* text:a
* text:ruby-base
* text:meta
* text:meta-field
Michael Stahl: text:text-input and text:variable-input
Svante Schubert: Fine with me :)
Svante Schubert: Michael: The alternative: Otherwise we should remove
them explicitly from whitespace handling
Svante Schubert: Currently they SHOULD be taken into account of
whitespacehandling, but do not allow elements for whitespacehandling
<text:line-break>, <text:tab>, <text:s>
Svante Schubert: collapsing = exchanging multiple spaces (not in the
beginning and end) to whitespace elements
Svante Schubert:
Svante Schubert: Michael's suggestion: Leave the schema as is, so he
don't need to fix his application
Svante Schubert: Is there any problem, when someones does processing XML
on a server and suddenly there are these XML text content elements
without whitespace handling? Like doing a text indent?
Svante Schubert: Seems to more consistent to fix the schema.. that all
text content aware elements are doing whitespace handling consistently
Svante Schubert: IF the application believes there is whitespace
handling in one of those elements in questions, it would
Svante Schubert: remove multiple spaces, which were intended by the
user, right?
Svante Schubert: But the XML application can be fixed as well :)
Svante Schubert: So I am open for both alternatives, I guess.
Svante Schubert: Best would be to have some test documents and play around..
Svante Schubert: @Michael: Could you add you test documents to the JIRA
issue? ;)
Svante Schubert: Thanks ->
Michael Stahl:
Patrick: svante will run test docs for ODF Toolkit - Patrick - prepare
schema fragments
Svante Schubert: I will take a look at Michael's test documents with
solely XML based applications such as ODF Toolkit and JEDIT (doing XML

I 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]