ODF New Proposal Template


Proposal owner:

Doug Mahugh

Proposal short name:

additional numbering formats


Use cases:

The standard currently does not specify how the value of style:num-format should be formatted if the numbering format is not one of the three described explicitly in the body of the standard.  Clarifying the process that should be used to create these strings will improve interoperability.

Alternatives considered:


Requested changes to the ODF Standard

Text changes/additions (please state section numbers):

Section 18.788 Style:num-format

The style:num-format attribute specifies a numbering sequence. The supported number sequences:

•       Alphabetic: a, b, c, ... or A, B, C, ...
•       Numeric: 1, 2, 3, ...
•       Roman: i, ii, iii, iv, ... or I, II, III, IV,...

The value of this attribute can be "1", "a", "A", "i", or "I". For some elements, the attribute value also can be empty. In that case, no numbering sequence is displayed.

Additional formats, that are used by an application, can be represented by this attribute by using the following rules to construct the value of style:num-format:

•       The string value should consist of the first three items of the numbering sequence --- each items should be followed by a comma
•       The string value should end with three periods
For example, the string for the Thai alphabet would be: “ก, ข, ค,...”
For example, the string for ordinal text would be: “First, Second, Third, ...” 

•       If two different numbering sequences begin with the same three items, then the three items for each string should consist of --- the first number of the sequence, followed by the first two numbers on which they differ.

For example, the first differences between two Chinese numbering formats may be the digits used for the ten and hundred value.  So, the string for the two formats may be:  一, 十, 一○○,... and一, 十, 一百,...

[NOTE] it may be preferable to replace this prose with an equivalent regular expression

Schema changes/additions:

No schema changes.



If an existing implementation uses a different approach, it may not be compliant with this change.

Backwards compatibility:

If an existing implementation uses a different approach, it may not be compatible with this change.

Accessibility impact:

No impact.

Workflow (to be filled in by TC Chairs)

Category: CategoryNewProposal

Date Proposal initially made:

Dates Proposal discussed on TC calls:

Date vote is requested:

Date vote is held:

Results of vote:

additional_numbering_formats (last edited 2009-08-12 18:04:26 by localhost)