Difference: UnicodeIFStmt (16 vs. 17)

Revision 172011-05-16 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="UnicodeTestPlan"

IF / AND / OR Statements

Line: 59 to 59
 
  1. Compiler does not flag Group field to National comparison as an error * FIXED * April 5 engine
  2. Executing an IF .. RS/RI with Unicode or National fields causes process to abort. 2nd attempt causes session to crash. *FIXED * April 5 engine
  3. 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?
Changed:
<
<
  1. 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.
>
>
  1. 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. * FIXED * Tested ok with April 24 engine.
 
  1. 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? ** Correct, RS/RI should work with Unicode fields (but don't, see #7 above).
\ No newline at end of file
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback