[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

*Subject*: **[OASIS Issue Tracker] (OFFICE-4042) part 4, 6.15.8 OR: typo "shall returns"**

*From*:**OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>***To*: office@lists.oasis-open.org*Date*: Mon, 15 Jul 2019 02:33:00 +0000 (UTC)

[ https://issues.oasis-open.org/browse/OFFICE-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Guelzow updated OFFICE-4042: ------------------------------------ Proposal: 2.4 change the second bullet to: "There need not be a distinguishable Logical type. Applications may have a Logical type distinct from both Number and Text (see 8.2 Distinct Logical), but Logical values may also be represented by the Number type using the values 1 (True) and 0 (False). This means that functions that take number sequences (such as SUM) may but need not include true and false values in the sequence." by inserting "and Text" and "8.2" 4.3.7 Logical (Number) change this section to: Applications may have a Logical type distinct from both Number and Text (see 4.5 Logical (Boolean)), but Logical values may also be represented by the Number type using the values 1 (True) and 0 (False). (see 8.2 Distinct Logical for details) 4.5 Logical (Boolean) change this section to: Applications may have a Logical type distinct from both Number and Text, but Logical values may also be represented by the Number type using the values 1 (True) and 0 (False) (see 4.3.7 Logical (Number)). (see 8.2 Distinct Logical for details) 8.2 Distinct Logical change this section to: Applications may have a Logical type distinct from both Number and Text (see 4.5 Logical (Boolean)), but Logical values may also be represented by the Number type using the values 1 (True) and 0 (False) (see 4.3.7 Logical (Number)). In this standard, we are using TRUE to represent the logical value (true) and FALSE to represent the logical value (false), independent from the concrete representation used by the evaluator. For an evaluator that represents Logical values using the Number type with values 1 (TRUE) and 0 (FALSE): â For the implicit conversion operator âConvert to Logicalâ 6.3.12, when a Number is passed as a condition, 0 is considered FALSE and all other numeric values are considered TRUE. An evaluator that has a Logical type distinct from both Number and Text shall have the following properties: â ISNUMBER() applied to a Logical value (constant or calculated) will return FALSE, and ISLOGICAL() applied to a Number will be FALSE, either directly or via a reference. â TRUE will not be equal to 1, and FALSE will not be equal to 0, when they are compared using â=â. â In a NumberSequence (such as when using SUM), Logical values are skipped when inside a range, but are included and automatically converted to a Number if provided as the NumberSequence itself. was: 2.4 change the second bullet to: "There need not be a distinguishable Logical type. Applications may have a Logical type distinct from both Number and Text (see 8.2 Distinct Logical), but Logical values may also be represented by the Number type using the values 1 (True) and 0 (False). This means that functions that take number sequences (such as SUM) may but need not include true and false values in the sequence." by inserting "8.2" 4.3.7 Logical (Number) change this section to: Applications may have a Logical type distinct from both Number and Text (see 4.5 Logical (Boolean)), but Logical values may also be represented by the Number type using the values 1 (True) and 0 (False). (see 8.2 Distinct Logical for details) 4.5 Logical (Boolean) change this section to: Applications may have a Logical type distinct from both Number and Text, but Logical values may also be represented by the Number type using the values 1 (True) and 0 (False) (see 4.3.7 Logical (Number)). (see 8.2 Distinct Logical for details) 8.2 Distinct Logical change this section to: Applications may have a Logical type distinct from both Number and Text (see 4.5 Logical (Boolean)), but Logical values may also be represented by the Number type using the values 1 (True) and 0 (False) (see 4.3.7 Logical (Number)). In this standard, we are using TRUE to represent the logical value (true) and FALSE to represent the logical value (false), independent from the concrete representation used by the evaluator. For an evaluator that represents Logical values using the Number type with values 1 (TRUE) and 0 (FALSE): â For the implicit conversion operator âConvert to Logicalâ 6.3.12, when a Number is passed as a condition, 0 is considered FALSE and all other numeric values are considered TRUE. An evaluator that has a Logical type distinct from both Number and Text shall have the following properties: â ISNUMBER() applied to a Logical value (constant or calculated) will return FALSE, and ISLOGICAL() applied to a Number will be FALSE, either directly or via a reference. â TRUE will not be equal to 1, and FALSE will not be equal to 0, when they are compared using â=â. â In a NumberSequence (such as when using SUM), Logical values are skipped when inside a range, but are included and automatically converted to a Number if provided as the NumberSequence itself. > part 4, 6.15.8 OR: typo "shall returns" > --------------------------------------- > > Key: OFFICE-4042 > URL: https://issues.oasis-open.org/browse/OFFICE-4042 > Project: OASIS Open Document Format for Office Applications (OpenDocument) TC > Issue Type: Bug > Components: OpenFormula, Part 2 (Formulas) > Affects Versions: ODF 1.2 > Reporter: Michael Stahl > Assignee: Andreas Guelzow > Priority: Minor > Fix For: ODF 1.3 > > > grammar: "if any are TRUE, it shall returns TRUE." > Since TRUE and FALSE are not defined, this requires in fact a more elaborate resolution. -- This message was sent by Atlassian JIRA (v7.7.2#77003)

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]