[OASIS Issue Tracker] Updated: (OFFICE-2322) Input Constraints forArabic Function

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

     [ http://tools.oasis-open.org/issues/browse/OFFICE-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eike Rathke updated OFFICE-2322:
--------------------------------

     Summary: Input Constraints for Arabic Function  (was: NEEDS-DISCUSSION: Input Constraints for Arabic Function)
    Proposal: 
For 5.19.2 ARABIC:

Remove from Portable Constraints:
X must contain at least one Roman numeral, and only contain Roman numerals.

Add Constraint:
X must only contain Roman numerals, or an empty string.


In Semantics:

Remove the sentence
The symbols V, L and D may not be followed by a symbol of greater or equal value.

Change
The following identity holds ...
to
The following identity shall hold ...

Add:
If X is an empty string, 0 is returned.

[rationale for empty string: that is what ROMAN produces for 0]


For 5.19.17 ROMAN:

Change Portable Constraint
from
N>=1
to
N>=0

In Semantics:

Add:
If N is 0, an empty string is returned.

[rationale: Excel, Gnumeric, OOo and KSpread return an empty string for 0]

Change
The following identity holds ...
to
The following identity shall hold ...


  was:
Move from Portable Constraints to Constraints:
X must contain at least one Roman numeral, and only contain Roman numerals.

Add to Semantics:
A consecutively repeated symbol may not be followed by a symbol of greater value.



Heh, nice source :)

Adapted the Proposal field to our discussion. plus added definition for numeric 0 and empty string.


> Input Constraints for Arabic Function
> -------------------------------------
>
>                 Key: OFFICE-2322
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2322
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: OpenFormula
>            Reporter: Eric Patterson
>            Assignee: Eike Rathke
>             Fix For: ODF 1.2
>
>
> It's unclear in the spec (5.19.2) whether "non-traditional" roman numerals are supported as input strings.  For example, are things like IIIV or IIVI expected to work?  The spec needs more detail here.

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