XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: ODF 1.2 Part 2 CD 1
    • Fix Version/s: ODF 1.2 Part 2 CD 2
    • Component/s: Database, OpenFormula, Table
    • Labels:
      None
    • Environment:

      This issue applies to OpenFormula, how open formula is profiled for ODF 1.2, and also how regular expression and wildcard patterns are used as features in OpenFormula and in unrelated parts of ODF 1.2 Part 1.

    • Proposal:
      Hide

      Add a section (as 2.4.1 after 2.4 Document Settings):
      Where stated the match of search criteria is affected by table:use-regular-expressions or table:use-wildcards settings.

      For the individual functions COUNTIF, COUNTIFS, HLOOKUP, LOOKUP, MATCH, VLOOKUP, SUMIF, SUMIFS, AVERAGEIF, AVERAGEIFS and SEARCH add a reference to then 2.4.1 in normative text and remove the TODO paragraphs.

      For 3.11.9 Criteria:

      Bullet "A text value beginning with a comparator ...":
      Change to "A value beginning with a comparator ...".
      Change "For = and <>, if calculation setting ..." to "For = and <>, if the value can not be interpreted as a Number type or one of its subtypes and calculation setting ...".
      Add "For = and <>, if the value can not be interpreted as a Number type or one of its subtypes 2.4.1 applies."

      Add to bullet "Other text value.":
      2.4.1 applies.

      Show
      Add a section (as 2.4.1 after 2.4 Document Settings): Where stated the match of search criteria is affected by table:use-regular-expressions or table:use-wildcards settings. For the individual functions COUNTIF, COUNTIFS, HLOOKUP, LOOKUP, MATCH, VLOOKUP, SUMIF, SUMIFS, AVERAGEIF, AVERAGEIFS and SEARCH add a reference to then 2.4.1 in normative text and remove the TODO paragraphs. For 3.11.9 Criteria: Bullet "A text value beginning with a comparator ...": Change to "A value beginning with a comparator ...". Change "For = and <>, if calculation setting ..." to "For = and <>, if the value can not be interpreted as a Number type or one of its subtypes and calculation setting ...". Add "For = and <>, if the value can not be interpreted as a Number type or one of its subtypes 2.4.1 applies." Add to bullet "Other text value.": 2.4.1 applies.

      Description

      Clarify the specification of pattern processing (regular expressions and wildcards).
      Section 3.3 briefly notes wildcards; need to define more clearly.
      Need to clearly note that table:use-regular-expressions and table:use-wildcards are mutually exclusive (at most one can be true).

      Database criteria specification (section 4.9.8) needs to be clearer.

      Each function affected by patterns (other than the database functions which are governed by the database criteria text) need to be clearly identified as such.

      David A. Wheeler will help with this.

        Attachments

          Activity

            People

            • Assignee:
              erack Eike Rathke (Inactive)
              Reporter:
              david.wheeler David Wheeler (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: