[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OFFICE-3950) text:ruby element needs special casing in 3.17 Foreign Elements and Attributes
[ https://issues.oasis-open.org/browse/OFFICE-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stahl updated OFFICE-3950: ---------------------------------- Proposal: 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:p> 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:p> ancestor element" - this should not be changed, it's OK.) to clarify, no changes to the existing schema are needed. was: considering the 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:p> 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:p> ancestor element" - this should not be changed, it's OK.) > 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 > Priority: Minor > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]