[OASIS Issue Tracker] (OFFICE-4108) new attribute for list level format string

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

    [ https://issues.oasis-open.org/browse/OFFICE-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=79768#comment-79768 ] 

Regina Henschel commented on OFFICE-4108:
-----------------------------------------

If <number:num-list-format>is as child of <office:styles>/<office:automatic-style>, then it is possible to use the same structure of a list item label in different lists. If it is a child of <text:list-level-style-number>, that would be similar to my proposal, and didn't we agree last week not to follow my proposal? But having it in <text:list-level-style-number> might be easier to implement and easier to design a UI.

ÂSome more points:
(A)
<quote>Any placeholder specifying a list level higher than the list level containing the style:num-list-format-name attribute shall be ignored.</quote>
What happens with the <number:text> child elements in case of ignoring a placeholder?
(B)
<quote>If the attribute is present, style:num-prefix [REF 19.506] and style:num-suffix [REF 19.507] shall be ignored.</quote>
Is the attribute text:display-levels(19.803) still evaluated? In case yes, same as (A), what happens with the <number:text> child elements?


> new attribute for list level format string
> ------------------------------------------
>
>                 Key: OFFICE-4108
>                 URL: https://issues.oasis-open.org/browse/OFFICE-4108
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: New Feature
>          Components: Formatting Properties, Lists, Part (Schema)
>    Affects Versions: ODF 1.3
>            Reporter: Michael Stahl
>            Priority: Minor
>             Fix For: ODF 1.4
>
>         Attachments: ManualExamples.zip, loext-num-list-format-proposal.odt
>
>
> Add a new attribute style:num-list-format containing a list level format string, see attachment for details.



--
This message was sent by Atlassian Jira
(v8.3.3#803004)