OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (OFFICE-3264) ODF 1.2 Part 116.27.27 <number:text-content> underspecified

    [ http://tools.oasis-open.org/issues/browse/OFFICE-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20313#action_20313 ] 

Michael Stahl  commented on OFFICE-3264:

a <number:text-style> can contain both fixed text and a position mark where variable text can be inserted.
the fixed text is contained in <number:text>.
the variable text position is marked by <number:text-content/>.

so your example specifies a style with an empty prefix and an empty suffix fixed text;
both fixed texts seem redundant.

re Q1:
it has nothing to do with conditional styles.
consumers need to understand that the <number:text-content/> element specifies the position at which the variable part of e.g. a field expansion is inserted.

re Q2:
producers would probably always include a <number:text-content/> in a <number:text-style>, because a style with only fixed text is kind of boring and useless.

perhaps the description could be improved, given that <number:text-content/> does not actually "contain" anything.
how about this:

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

> ODF 1.2 Part 1 16.27.27 <number:text-content> underspecified
> ------------------------------------------------------------
>                 Key: OFFICE-3264
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3264
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Part 1 (Schema), Styles
>    Affects Versions: ODF 1.2 CD 05
>         Environment: This situation applies to <number:text-content> since the OASIS ODF 1.0 Standard.
>            Reporter: Dennis Hamilton
>             Fix For: ODF 1.2 CD 06
> 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()&gt;0" style:apply-style-name="N5136P0"/>
>             <style:map style:condition="value()&lt;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).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]