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: Re: [office] Email issues - If no objection by Monday, 4 June 2018, proposals are approved.


Michael,

Glad you wrote because the text I suggest was your proposal.

What is it that should be done differently?

Thanks!

Hope you are looking forward to a great weekend!

Patrick


On 06/01/2018 04:17 AM, Michael Stahl wrote:
>
> hi Patrick,
>
> On 31/05/18 22:41, Patrick Durusau wrote:
>> Office-3950 - 3.17 Foreign Elements and Attributes: failure to handle
>> the special case of the ruby element.
>>
>> https://issues.oasis-open.org/browse/OFFICE-3950
>>
>> Present: "OpenDocument schema permits the inclusion of character data
>> for all its ancestors up to the
>> <text:p> or <text:h> element ancestor element, ...."
>>
>> Proposed: "OpenDocument schema permits the inclusion of character
>> data for all its ancestors up to the
>> <text:p> or <text:h> element ancestor, *or a <text:ruby-base>
>> ancestor element,*
>>
>> Proposed: Plus add <text:ruby-base> to root elements in schema:
>>
>> <rng:define name="office-document">
>>     <rng:element name="office:document">
>>       <rng:ref name="office-document-attrs"/>
>>       <rng:ref name="office-document-common-attrs"/>
>>       <rng:ref name="office-meta"/>
>>       <rng:ref name="office-settings"/>
>>       <rng:ref name="office-scripts"/>
>>       <rng:ref name="office-font-face-decls"/>
>>       <rng:ref name="office-styles"/>
>>       <rng:ref name="office-automatic-styles"/>
>>       <rng:ref name="office-master-styles"/>
>>       <rng:ref name="office-body"/>
>>     </rng:element>
>>   </rng:define>
>>
>> to:
>>
>> <rng:define name="office-document">
>>     <rng:element name="office:document">
>>       <rng:ref name="office-document-attrs"/>
>>       <rng:ref name="office-document-common-attrs"/>
>>       <rng:ref name="office-meta"/>
>>       <rng:ref name="office-settings"/>
>>       <rng:ref name="office-scripts"/>
>>       <rng:ref name="office-font-face-decls"/>
>>       <rng:ref name="office-styles"/>
>>       <rng:ref name="office-automatic-styles"/>
>>       <rng:ref name="office-master-styles"/>
>>       <rng:ref name="office-body"/>
>>
>> *<rng:ref name="text:ruby-base"/>*
>>
>>     </rng:element>
>>   </rng:define>
>>
>> Yes?
>>
>
> i don't understand what problem that would solve; the ruby element
> exists only as child of <text:ruby> which only exists inside paragraph
> elements.
>
> the only problem with the current text is that it technically excludes
> <text:ruby-base> because its parent <text:ruby> does not allow
> immediate character content children.
>
> if we know we're inside <text:ruby-base>, this implies that we're
> inside one of the paragraph elements as well, hence my proposal.
>

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


Attachment: signature.asc
Description: OpenPGP digital signature



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