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

ODF 1.2 Part 1 16.27.27 <number:text-content> underspecified

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Applied
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: ODF 1.2 CD 05
    • Fix Version/s: ODF 1.2 CD 06
    • Component/s: Public Review
    • Labels:
      None
    • Environment:

      This situation applies to <number:text-content> since the OASIS ODF 1.0 Standard.

    • Proposal:
      Hide

      Provide an explanation of the way that <number:text-content/> serves as a marker as a child of a <number:text-style> element and when it is required.

      Show
      Provide an explanation of the way that <number:text-content/> serves as a marker as a child of a <number:text-style> element and when it is required.
    • Resolution:
      Hide

      Adapt 16.27.27 to

      "The <number:text-content> element marks the position of variable text content of a text style."

      Adapt 16.27.24 to:

      The <number:boolean> element marks the position of the Boolean value of a Boolean style.

      Show
      Adapt 16.27.27 to "The <number:text-content> element marks the position of variable text content of a text style." Adapt 16.27.24 to: The <number:boolean> element marks the position of the Boolean value of a Boolean style.

      Description

      Setion 16.27.27 states that

      "The <number:text-content> element contains any variable text content of a text content."

      However, the schema specifies that <number:text-content> is <empty/>, meaning that it has no attributes an no children (including text).

      It appears that, unlike <number:text> the <number:text-content> does not contain anything. Rather, it seems to be a marker for or about something. This needs to be explained.

      For example, here is an use of the element as a child of a <number:text-style> instance in a prominent and presumably-correct implementation of ODF:

      <number:text-style style:name="N5136" number:language="en" number:country="US">
      <number:text></number:text>
      <number:text-content/>
      <number:text></number:text>
      <style:map style:condition="value()>0" style:apply-style-name="N5136P0"/>
      <style:map style:condition="value()<0" style:apply-style-name="N5136P1"/>
      <style:map style:condition="value()=0" style:apply-style-name="N5136P2"/>
      </number:text-style>

      Q1: What is a consumer expected to understand about that element? Does it have something to do with the presence of style:map elements and their style:condition expressions?

      Q2: How does a producer know when it is appropriate to provide that element (here or elsewhere).

        Attachments

          Activity

            People

            • Assignee:
              Patrick Patrick Durusau
              Reporter:
              orcmid Dennis Hamilton (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: