[OASIS Issue Tracker] Commented: (OFFICE-1739) Editor Note: Section17.489 style:leader-text

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

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

Dennis Hamilton commented on OFFICE-1739:
-----------------------------------------

With regard to addition of 17.3.x, if you reference XML Schema Section 3.2.1, you might want to emphasize that the the single character (Char) is as defined in [XML10] section 2.2.  This makes the admissable single characters very precise (and surprising).   [Note that length here is in terms of Unicode characters, not UTF-8 or UTF-16 frames.]

COMPATIBILITY WARNING

If the version of XML Schema or the edition of XML 1.0 is updated in the references, this can change the definition of the single Char.

INTEROPERABILITY CONCERN

With regard to 17.489, "An implementation may supports only the display of specific characters as textual leaders. If this is the case, and if the attribute specifies a character that is not supported by the implementation, then the implementation should display a leader character that it supports instead of the one specified by this attribute": I think there need to be three different cases:

1. Conforming Documents - what characters are allowed.  For example, are only "printable" or visible characters allowed.  A different subset of Unicode than the full Chars of XML 1.0 ed.2 might be preferable.

2. Document Consumer.  I think there must be a better way to say this.  Perhaps on the lines of "A document consumer my limit its support for textual leaders to a fixed implementation-defined set of characters.  A document consumer shall provide an implementation-defined textual leader when the style:leader-text is not one of the supported characters.

3. Document Producer.  "How and whether a producer preserves style:leader-text values that are not in its implementation-defined set of characters is implementation-defined."

CLARIFICATION

Finally, the statement "Textual leaders specified by a style:leader-text attribute have a higher priority than line leaders specified by a style:leader-style attribute."  might be stated as something like "When both a style:leader-text and style:leader-style attribute are applicable, the style:leader-text attribute interpretation shall apply."  Or whatever is precisely intended.

> Editor Note: Section 17.489 style:leader-text
> ---------------------------------------------
>
>                 Key: OFFICE-1739
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-1739
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>    Affects Versions: ODF 1.2
>            Reporter: Robert Weir 
>            Assignee: Patrick Durusau
>            Priority: Blocker
>             Fix For: ODF 1.2
>
>
> Transcribed from ODF_Revised_Editorial_Notes_27May2009.odt
> Original author: Patrick Durusau
> Section 17.489 style:leader-text
> Ed. Note The schema does not enforce the single Unicode character restriction. I have re-cast this text as it seemed deeply confusing to me. How an application could not support "textual" and still use any of the line leaders, which are also Unicode characters is beyond me. I suspect we need to change the substantive requirements of this attribute to simply use the specified text leader if specified and the line leader if not. 
> Oliver says: "Yes, the schema should reflect the restriction - Michael, changing its 
> data type to character? 
> No further input from my side, because I am also a little bit confused. "

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