CNV TEXT Statement

Bugs

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.

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.* FIXED * June 9 engine, Returns F if conversion cannot be performed.
   
3. When converting a Unicode field containing a spiky ball (0xA4), I get a Euro symbol in my Raw field. Same with National to Raw.* FIXED * June 9 engine, Returns F if conversion cannot be performed.

1. When converting from National to Raw, where National field contains a character not in the Raw character set, does not throw a transcode error. The character is silently converted to something else. * FIXED * June 9 engine, Returns F if conversion cannot be performed.
   
2. When converting from Unicode Text to National or Raw array, does not word wrap. * FIXED * June 9 engine, Returns F if conversion cannot be performed.

1. When converting from National Text to Unicode or Raw array, does not word wrap. * FIXED * June 9 engine
2. When converting from National Text to Raw array, converts spiky ball (0xA4) to euro symbol.** FIXED ** June 9 engine
   
3. When converting from Raw Text to National or Unicode array, does not word wrap. * FIXED * June 9 engine
   

CNV TEXT Statement

Bugs

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.

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.* FIXED * June 9 engine, Returns F if conversion cannot be performed.
   
3. When converting a Unicode field containing a spiky ball (0xA4), I get a Euro symbol in my Raw field. Same with National to Raw.* FIXED * June 9 engine, Returns F if conversion cannot be performed.

CNV TEXT Statement

1. 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.* FIXED * June 9 engine, Returns F if conversion cannot be performed.
   
2. When converting a Unicode field containing a spiky ball (0xA4), I get a Euro symbol in my Raw field. Same with National to Raw.* FIXED * June 9 engine, Returns F if conversion cannot be performed.
3. 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. Retest when GUI working again.

1. When converting from Unicode Text to National or Raw array, does not word wrap. * FIXED * June 9 engine, Returns F if conversion cannot be performed.
2. When converting from Unicode Text to National or Raw array, does not throw transcode errors, just silently converts the characters to something else (Raw) or converts them unchanged (National). Raw array sometimes contains garbage characters, this might depend on the specific strings entered. Retest when GUI is working again.
3. When converting from National Text to Unicode or Raw array, does not word wrap. * FIXED * June 9 engine

1. When converting from National or Unicode to Format field, C-assert 'Unexpected src_buf size (15)' in module CVALP.C.1945 and format field contains incorrect data.* FIXED * June 9 engine
2. When converting from National or Unicode back to Raw, it only moves the part of the string. Sometimes just the first word, sometimes more.* FIXED * June 9 engine
3. Does not give transcode error when converting Unicode to Raw when Unicode contains non Raw characters.* FIXED * June 9 engine, Returns F if conversion cannot be performed.

1. Does not give transcode errors when converting from Raw to National when Raw contains non National Characters. ** Functions as Designed **

1. Does not give transcode error when converting Unicode to National when Unicode contains non National characters ** Functions as Designed **
   
2. 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? * FIXED * June 9 engine
3. 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.* FIXED * June 9 engine

CNV TEXT Statement

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".
3. 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 **

1. When converting from National to Raw, where National field contains a character not in the Raw character set, does not throw a transcode error. The character is silently converted to something else.
   

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. CNV TEXT from Unicode record to National field does not generate transcode errors when there are Unicode characters in the record that are not in the National character set. ** FAD, National & Unicode are the same internally
   

CNV TEXT Statement

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.

1. CNV TEXT from a record containing Unicode 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 Unicode fields.
   
2. CNV TEXT from a record containing Unicode data into Unicode field is incorrect. Some Unicode fields were transcoded to garbage characters. Moving it back to the record results in the correct data in the record(!).
   
3. CNV TEXT from a record containing Unicode data into National field is incorrect. Some Unicode fields were transcoded to garbage characters. Moving it back to the record results in the correct data in the record(!).
   
4. CNV TEXT from Unicode record to Raw field does not generate transcode errors when there are Unicode characters in the record.

CNV TEXT Statement

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".

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.

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)

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.

CNV TEXT Statement

1. Test CNV TEXT with Numeric, Date, and Logic fields using RAW, UNICODE, and NATIONAL alpha fields.

Bugs

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.
   
3. When converting a Unicode field containing a spiky ball (0xA4), I get a Euro symbol in my Raw field. Same with National to Raw.
   
   

CNV TEXT Statement

1. Test CNV TEXT with Numeric, Date, and Logic fields using RAW, UNICODE, and NATIONAL alpha fields.

Bugs

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.

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.

1. When converting from Unicode Text to National or Raw array, does not word wrap.
2. When converting from Unicode Text to National or Raw array, does not throw transcode errors, just silently converts the characters to something else (Raw) or converts them unchanged (National). Raw array sometimes contains garbage characters, this might depend on the specific strings entered.
3. When converting from National Text to Unicode or Raw array, does not word wrap.

1. When converting from Raw Text to National or Unicode array, does not word wrap.
   
2. When converting from Token to National or Unicode, unused parts of destination are not cleared.
3. When converting from National or Unicode to Format field, C-assert 'Unexpected src_buf size (15)' in module CVALP.C.1945 and format field contains incorrect data.

1. Does not move all characters when converting from Unicode to Raw (destination truncated)
   
2. Does not give transcode error when converting Unicode to National when Unicode contains non National characters
   
3. 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?

1. 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.
2. CNV TEXT from a record containing National data into National field is incorrect. The non National field was transcoded to garbage characters. Moving it back to the record results in the correct data in the record(!).
3. CNV TEXT from a record containing National data into Unicode field is incorrect. The non National field was transcoded to garbage characters. Moving it back to the record results in the correct data in the record(!).
   

CNV TEXT Statement

1. Does not move all characters when converting from Unicode to Raw (destination truncated)
   
2. Does not give transcode error when converting Unicode to National when Unicode contains non National characters
   
3. 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?

1. 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.
2. CNV TEXT from a record containing National data into National field is incorrect. The non National field was transcoded to garbage characters. Moving it back to the record results in the correct data in the record(!).
3. CNV TEXT from a record containing National data into Unicode field is incorrect. The non National field was transcoded to garbage characters. Moving it back to the record results in the correct data in the record(!).
   

CNV TEXT Statement

1. Test CNV TEXT with Numeric, Date, and Logic fields using RAW, UNICODE, and NATIONAL alpha fields.

Bugs

1. 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".
2. When converting from Unicode to National, where the Unicode field contains characters not in the National character set, does not throw a transcode error.

1. 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.

1. When converting from Unicode Text to National or Raw array, does not word wrap.
2. When converting from Unicode Text to National or Raw array, does not throw transcode errors, just silently converts the characters to something else (Raw) or converts them unchanged (National). Raw array sometimes contains garbage characters, this might depend on the specific strings entered.
3. When converting from National Text to Unicode or Raw array, does not word wrap.

1. When converting from Raw Text to National or Unicode array, does not word wrap.
   
2. When converting from Token to National or Unicode, unused parts of destination are not cleared.
3. When converting from National or Unicode to Format field, C-assert 'Unexpected src_buf size (15)' in module CVALP.C.1945 and format field contains incorrect data.

CNV TEXT Statement

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
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".

1. 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 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.
2. When converting from National to Raw, where National field contains a character not in the Raw character set, does not throw a transcode error. The character is silently converted to something else.
3. When converting from Unicode Text to National or Raw array, does not word wrap.

1. Does not move all characters when converting from Unicode to Raw (destination truncated)
   
2. Does not give transcode error when converting Unicode to National when Unicode contains non National characters
   
3. 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?

CNV TEXT Statement

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. It should.
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.
3. When converting a Unicode field containing a spiky ball (0xA4), I get a Euro symbol in my Raw field.

1. When converting from National to Raw, where National field contains a character not in the Raw character set, does not throw a transcode error. The character is silently converted to something else.
2. When converting from Unicode Text to National or Raw array, does not word wrap.

1. When converting from National Text to Unicode or Raw array, does not word wrap.
2. When converting from National Text to Raw array, converts spiky ball (0xA4) to euro symbol.
   
3. When converting from Raw Text to National or Unicode array, does not word wrap.
   

-- PeteBrower - 2011-03-17

CNV TEXT Statement

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. It should.
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.
3. When converting a Unicode field containing a spiky ball (0xA4), I get a Euro symbol in my Raw field.

CNV TEXT Statement

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
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".

CNV TEXT Statement

1. Test CNV TEXT with Numeric, Date, and Logic fields using RAW, UNICODE, and NATIONAL alpha fields.

Bugs

CNV TEXT Statement

Test Plan

Bugs

-- PeteBrower - 2011-03-17 \ No newline at end of file