[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (OFFICE-2392) 6.5 TraditionalComplex Number Notation - error in description
[ http://tools.oasis-open.org/issues/browse/OFFICE-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eike Rathke updated OFFICE-2392:
--------------------------------
Fix Version/s: ODF 1.2 Part 2 CD 2
Affects Version/s: (was: ODF 1.2 Part 2 CD 2)
> 6.5 Traditional Complex Number Notation - error in description
> --------------------------------------------------------------
>
> Key: OFFICE-2392
> URL: http://tools.oasis-open.org/issues/browse/OFFICE-2392
> Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
> Issue Type: Bug
> Components: OpenFormula
> Reporter: Patrick Durusau
> Fix For: ODF 1.2 Part 2 CD 2
>
>
> We currently say:
> "Applications claiming to implement "Traditional Complex Number Notation" shall allow traditional inline notation for complex numbers, that is, "i" or "j" optionally prefixed with Number produces a type Complex."
> That's incorrect. A complex type consists of a real number plus an imaginary number.
> Rather than filing a separate JIRA issue, why do we define acceptance of complex types by infix operators here? Isn't this covered by Number as a type already?
> What does the "...no required to accept the Text type as equivalent." mean?
> Most of this looks like repetition so I am deleting it until the case is made for its return.
--
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]