| |
| META TOPICPARENT |
name="UnicodeTestPlan" |
CNV TEXT Statement |
| |
- 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
- 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".
|
|
<
< |
- 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.
|
>
> |
- When converting from Unicode to National, where the Unicode field contains characters not in the National character set, does not throw a transcode error.
|
| |
- 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.
|
|
<
< |
- When converting a Unicode field containing a spiky ball (0xA4), I get a Euro symbol in my Raw field.
|
>
> |
- When converting a Unicode field containing a spiky ball (0xA4), I get a Euro symbol in my Raw field. Same with National to Raw.
|
| |
- 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.
- 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.
- When converting from Unicode Text to National or Raw array, does not word wrap.
|
| |
- Does not move all characters when converting from Unicode to Raw (destination truncated)
- Does not give transcode error when converting Unicode to National when Unicode contains non National characters
- 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 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.
- 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 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(!).
- 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 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.
- 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(!).
- 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(!).
- CNV TEXT from Unicode record to Raw field does not generate transcode errors when there are Unicode characters in the record.
- 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.
- When moving from National to Raw, the spiky ball gets transcoded to a Euro symbol.
|
| |
-- PeteBrower - 2011-03-17 |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.