Michael,
If you have time, please check the following schema mods to make sure I
have caught all the cases for adding <text:ruby-base> element:
*****
<rng:define name="header-footer-content">
<rng:choice>
<rng:group>
<rng:ref name="text-tracked-changes"/>
<rng:ref name="text-decls"/>
<rng:zeroOrMore>
<rng:choice>
<rng:ref name="text-h"/>
<rng:ref name="text-p"/>
to:
<rng:define name="header-footer-content">
<rng:choice>
<rng:group>
<rng:ref name="text-tracked-changes"/>
<rng:ref name="text-decls"/>
<rng:zeroOrMore>
<rng:choice>
<rng:ref name="text-h"/>
<rng:ref name="text-p"/>
<rng:ref name="text:ruby-base/>
*******************************
<rng:define name="text-content">
<rng:choice>
<rng:ref name="text-h"/>
<rng:ref name="text-p"/>
to:
<rng:define name="text-content">
<rng:choice>
<rng:ref name="text-h"/>
<rng:ref name="text-p"/>
<rng:ref name="text:ruby-base"/>
************************************
<rng:define name="text-list-item-content">
<rng:optional>
<rng:ref name="text-number"/>
</rng:optional>
<rng:zeroOrMore>
<rng:choice>
<rng:ref name="text-p"/>
<rng:ref name="text-h"/>
to:
<rng:define name="text-list-item-content">
<rng:optional>
<rng:ref name="text-number"/>
</rng:optional>
<rng:zeroOrMore>
<rng:choice>
<rng:ref name="text-p"/>
<rng:ref name="text-h"/>
<rng:ref name="text:ruby-base/>
*******************************************
<rng:define name="text-numbered-paragraph">
<rng:element name="text:numbered-paragraph">
<rng:ref name="text-numbered-paragraph-attr"/>
<rng:optional>
<rng:ref name="text-number"/>
</rng:optional>
<rng:choice>
<rng:ref name="text-p"/>
<rng:ref name="text-h"/>
</rng:choice>
</rng:element>
to:
<rng:define name="text-numbered-paragraph">
<rng:element name="text:numbered-paragraph">
<rng:ref name="text-numbered-paragraph-attr"/>
<rng:optional>
<rng:ref name="text-number"/>
</rng:optional>
<rng:choice>
<rng:ref name="text-p"/>
<rng:ref name="text-h"/>
<rng:ref name="text:ruby-base"/>
</rng:choice>
</rng:element>
I searched for pairs of "text-p" and "text-h" twice so I suspect it to
be correct but a second set of eyes never hurts!
Hope you are having a great week!
Patrick
On 06/01/2018 11:40 AM, Patrick Durusau wrote:
> Michael,
>
> Thanks!
>
> Hope you are nearing a great weekend!
>
> Patrick
>
>
> On 06/01/2018 11:10 AM, Michael Stahl wrote:
>> hi Patrick,
>>
>> On 01/06/18 16:48, Patrick Durusau wrote:
>>> Michael,
>>>
>>> Glad you wrote because the text I suggest was your proposal.
>>>
>>> What is it that should be done differently?
>> i'm sorry, i now realise i was writing something very ambiguous in the
>> proposal:
>>
>> 'the easiest fix is to just add the <text:ruby-base> element to the
>> list of "root" elements:'
>>
>> here i meant the <text:p> and <text:h> as the "root" elements in the
>> context of that sentence, and to add the <text:ruby-base> to the list
>> as another "root" element in that context:
>>> On 06/01/2018 04:17 AM, Michael Stahl wrote:
>>>> On 31/05/18 22:41, Patrick Durusau wrote:
>>>>> 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,*
>> ... but now you thought it means i want to add it to the document's
>> root elements, which i don't :)
>>
>> probably i should have written "ancestor element" instead.
>>
--
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
