Uploaded image for project: 'OASIS Open Document Format for Office Applications (OpenDocument) TC'
  1. OASIS Open Document Format for Office Applications (OpenDocument) TC
  2. OFFICE-2392

6.5 Traditional Complex Number Notation - error in description

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: ODF 1.2 Part 2 CD 1
    • Component/s: OpenFormula
    • Labels:
      None
    • Proposal:
      Hide

      Remove section 6.5 Traditional Complex Number Notation and all references.

      Show
      Remove section 6.5 Traditional Complex Number Notation and all references.
    • Resolution:
      Hide

      Removed section 6.5 Traditional Complex Number Notation and reference in 3.4 Complex Number.

      Show
      Removed section 6.5 Traditional Complex Number Notation and reference in 3.4 Complex Number.

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              erack Eike Rathke (Inactive)
              Reporter:
              Patrick Patrick Durusau
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: