| |
| META TOPICPARENT |
name="UnicodeTestPlan" |
CNV BIN Statement |
| |
- Painted 1 character national field on image, displayed as 4 characters. unicode was ok. * FIXED * March 28 engine
- CNV BIN from negative literal does not generate compile time error, generates 'Invalid Sign' runtime error. Might not be actual bug, just different implementation? Confirmed 4/2/11, designed this way
- National fields are not transcoded to their proper character set. I can CNV BIN a character from the Unicode character set (but that does not exist in the National character set as specified on the SYSPARM file) into a National field, and it will display the Unicode character. Instead, it should transcode the Unicode character to the National character, and display that. ** Not a bug FAD**
|
|
<
< |
- Overflow errors are not occurring at the expected limit. The max value for a 4 byte unsigned number is 4294967295, if I use this value I get overflow errors. If I decrease that by 1 to 4294967294, I do not get an overflow.
|
>
> |
- Overflow errors are not occurring at the expected limit. The max value for a 4 byte unsigned number is 4294967295, if I use this value I get overflow errors. If I decrease that by 1 to 4294967294, I do not get an overflow. * FIXED * June 9 engine
|
| |
- Uses wrong character set? Example, I use CNV BIN to put 0xA4 into TEMP 1. This is a spiky ball character, but the debugger shows that TEMP 1 contains a Euro symbol. ** I think the problem is that my reference table only has the 8859-1 character set, where A4 is the spiky ball, but Appx is using 8859-15, where the same binary value is the Euro symbol. **
-- JeanNeron - 2011-03-11 |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.