Difference: UnicodeCNV_TEXTStmt (11 vs. 12)

Revision 122011-06-02 - JeanNeron

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

CNV TEXT Statement

Line: 46 to 46
 
  1. It's not handling Logic fields properly. When CNV TEXT into National/Unicode from Logic the destination field is wrong somehow. It looks ok in the debugger, but if I display it on an image, it shows the field is filled with reverse image diamonds. When comparing via IF to either Y or N, always returns False. * FIXED * Tested with May 23 engine.
  2. Since SET does not work with Group fields and National/Unicode fields, then this probably should not either. It does give compile errors, but the error is "Length of Record Exceeds Maximum Allowed (32k)". Probably should give the same error SET does: "Invalid Storage Type".
Changed:
<
<
  1. When converting from Unicode to National, where the Unicode field contains characters not in the National character set, does not throw a transcode error.
  2. When converting from Unicode to Raw, where the Unicode field contains characters not in the Raw character set, does not throw a transcode error, just silently drops the Unicode character. Should be a transcode error.
>
>
  1. When converting from Unicode to National, where the Unicode field contains characters not in the National character set, does not throw a transcode error. ** Functions as Designed **
  2. When converting from Unicode to Raw, where the Unicode field contains characters not in the Raw character set, does not throw a transcode error, just silently drops the Unicode character. Should be a transcode error or it should use the substitute character.
 
  1. When converting a Unicode field containing a spiky ball (0xA4), I get a Euro symbol in my Raw field. Same with National to Raw.

    • 0xA4 in Unicode is the CURRENCY SIGN (¤) - you cannot convert that symbol to ISO 8859-15 so the CNV TEXT statement converts it to a substitution character (which is actually an ampersand (&). I've modified CNV TEXT to substitute a question mark instead of an ampersand.

  2. When converting from Unicode to National or Raw, causes Appx to crash. Not sure if it's the National or Raw, all the statements run but when the Event Point ends, the client closes. Doesn't seem to matter if there's any data to convert or not. This also happened when converting from National to Unicode/Raw, but somewhat inconsistently. It worked for a while, then suddenly started crashing Appx every time.
Line: 62 to 62
 
  1. When converting from National or Unicode back to Raw, it only moves the part of the string. Sometimes just the first word, sometimes more.
  2. Does not give transcode error when converting Unicode to Raw when Unicode contains non Raw characters
  3. Does not move all characters when converting from Unicode to Raw (destination truncated)
Changed:
<
<
  1. Does not give transcode errors when converting from Raw to National when Raw contains non National Characters.
  2. Does not move all characters when converting from Unicode to Raw (destination truncated)
  3. Does not give transcode error when converting Unicode to National when Unicode contains non National characters
>
>
  1. Does not give transcode errors when converting from Raw to National when Raw contains non National Characters. ** Functions as Designed **
  2. Does not move all characters when converting from National to Raw (destination truncated)
  3. Does not give transcode error when converting Unicode to National when Unicode contains non National characters ** Functions as Designed **
 
  1. When CNV TEXT from Unicode into occ (1) of multi occ National field, occ (2) of the destination is cleared. If the source field was a TEXT type field and I specified 000 as a destination occ number, that would make sense, but the source is plain alpha and I did not specify occ 000 on the destination. Is it supposed to work this way?
  2. CNV TEXT from a record containing Raw into Unicode or National field shows garbage in the fields. Attempting to move the National or Unicode back to the record results in truncated data in the fields.
  3. CNV TEXT from a record containing National data into Raw field is incorrect. It looks like there are too many spaces between fields. Moving it back to the record results in garbage in the National field.
 
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