Uploaded image for project: 'OASIS Open Document Format for Office Applications (OpenDocument) TC'
  1. OASIS Open Document Format for Office Applications (OpenDocument) TC
  2. OFFICE-3950

text:ruby element needs special casing in 3.17 Foreign Elements and Attributes

    Details

    • Proposal:
      Hide

      considering the existing schema, the easiest fix is to just add the <text:ruby-base> element to the list of "root" elements:

      "if the OpenDocument schema permits the inclusion of character data for all its ancestors up to the <text> or <text:h> ancestor element, or a <text:ruby-base> ancestor element,"

      (Note: the sentence begins with "If a foreign element has a <text:h> or <text> ancestor element" - this should not be changed, it's OK.)

      to clarify, no changes to the existing schema are needed.

      Show
      considering the existing schema, the easiest fix is to just add the <text:ruby-base> element to the list of "root" elements: "if the OpenDocument schema permits the inclusion of character data for all its ancestors up to the <text > or <text:h> ancestor element, or a <text:ruby-base> ancestor element," (Note: the sentence begins with "If a foreign element has a <text:h> or <text > ancestor element" - this should not be changed, it's OK.) to clarify, no changes to the existing schema are needed.

      Description

      ODF 1.2 part 1, 3.17 Foreign Elements and Attributes
      contains this sentence:

      "if the OpenDocument schema permits the inclusion of character data for all its ancestors up to the <text> or <text:h> element ancestor element,"

      clearly the intent here is character data that ends up as paragraph text, and as usual the special case of the ruby element isn't handled.

      			<element name="text:ruby">
      				<optional>
      					<attribute name="text:style-name">
      						<ref name="styleNameRef"/>
      					</attribute>
      				</optional>
      				<element name="text:ruby-base">
      					<zeroOrMore>
      						<ref name="paragraph-content-or-hyperlink"/>
      					</zeroOrMore>
      				</element>
      				<element name="text:ruby-text">
      					<optional>
      						<attribute name="text:style-name">
      							<ref name="styleNameRef"/>
      						</attribute>
      					</optional>
      					<text/>
      				</element>
      			</element>
      

      <text:ruby> does not allow <text/> directly, so any character data inside <text:ruby-base> is excluded by the language in 3.17.

        Attachments

          Activity

            People

            • Assignee:
              michaelst Michael Stahl
              Reporter:
              michaelst Michael Stahl
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: