| |
| META TOPICPARENT |
name="UnicodeTestPlan" |
IF / AND / OR Statements |
| |
- Test Unicode to Literal (\uxxx, \UXXXXXXXX, normal)
Bugs |
|
<
< |
- The EX operator gives the same result as IN, ie, IF ... IN ... and IF ... EX .... both return true when used with Unicode fields. Use 'testing' for LHS and 'ing' for RHS. Seems to work ok with single character operands.
- The EX operator gives the same result as IN, ie, IF ... IN ... and IF ... EX .... both return true when used with National fields. Use 'testing' for LHS and 'ing' for RHS. Seems to work ok with single character operands.
- Compiler does not flag Group field to Unicode comparison as an error
- Compiler does not flag Group field to National comparison as an error
- Executing an IF .. RS/RI with Unicode or National fields causes process to abort. 2nd attempt causes session to crash.
|
>
> |
- The EX operator gives the same result as IN, ie, IF ... IN ... and IF ... EX .... both return true when used with Unicode fields. Use 'testing' for LHS and 'ing' for RHS. Seems to work ok with single character operands.* FIXED * April 5 engine
- The EX operator gives the same result as IN, ie, IF ... IN ... and IF ... EX .... both return true when used with National fields. Use 'testing' for LHS and 'ing' for RHS. Seems to work ok with single character operands.* FIXED * April 5 engine
- Compiler does not flag Group field to Unicode comparison as an error * FIXED * April 5 engine
- Compiler does not flag Group field to National comparison as an error * FIXED * April 5 engine
- Executing an IF .. RS/RI with Unicode or National fields causes process to abort. 2nd attempt causes session to crash. *FIXED * April 5 engine
|
| |
- Not sure if this is a bug or not: If I compare 2 raw alphas, then 'a' is GT 'A', as per the ASCII table. If I compare raw 'a' to Unicode 'A', then the opposite is true. It this because the raw was transcoded to unicode, and then the Unicode collating sequence was used, which puts the lower case before the upper case?
|
|
>
> |
- IF .. RS/RI .. always returns False. Example, IF Testing RI ING returns T under 4.2.a, F under unicode. Tested with Unicode and Raw fields, same result.
- Does not give transcode error as expected. The specs say National/Unicode fields should be transcoded down to 8859-1 first. Or does this mean Regular Expressions will work with Unicode, and don't have to be transcoded?
-
|
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.