[OASIS Issue Tracker] (OFFICE-3950) text:ruby element needs special casing in 3.17 Foreign Elements and Attributes

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Michael Stahl created OFFICE-3950:
-------------------------------------

             Summary: text:ruby element needs special casing in 3.17 Foreign Elements and Attributes
                 Key: OFFICE-3950
                 URL: https://issues.oasis-open.org/browse/OFFICE-3950
             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
          Issue Type: Bug
          Components: Document Structure, Part 1 (Schema)
    Affects Versions: ODF 1.2
            Reporter: Michael Stahl
            Assignee: Michael Stahl
             Fix For: ODF 1.3


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:p> 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.

{noformat}
			<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>
{noformat}

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



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)