| |
| META TOPICPARENT |
name="WebHome" |
Unicode Test Plan |
| |
- File Management functions (create, restruct, etc) crash with a 'Value Does Not Fit in Mask' error when setting MESSAGE2 MSG TXT into STAT2 MSG. * FIXED * April 24 engine
- Engine should be transcoding when fields are moved, and throwing a runtime error (like numeric overflow) if the encoding of the receiving field does not contain the necessary characters. ** No, will not be implemented this way **
- The 'Global EPs for Images' is not highlighted when I add code to the global start of frame. None of the EP's in the Global section turn on highlighting when code is entered. * FIXED * tested with April 24 engine, seems to be ok now.
|
|
<
< |
- Cross Reference display is messed up. Do an x-ref on APPEND NORMAL in App TST, then click 'References' to see what I mean. Retested with April 24 engine, better but still different from 4.2.a. In 4.2.a, in the 'Context' column the word RECORD is immediately followed by the frame & image information. In the Unicode version, the word RECORD is followed by many spaces, then the rest of the context. (Should be fixed - 28-Nov)
|
>
> |
- Cross Reference display is messed up. Do an x-ref on APPEND NORMAL in App TST, then click 'References' to see what I mean. Retested with April 24 engine, better but still different from 4.2.a. In 4.2.a, in the 'Context' column the word RECORD is immediately followed by the frame & image information. In the Unicode version, the word RECORD is followed by many spaces, then the rest of the context. * FIXED * in Dec 10 engine
|
| |
- Put the field --- X on an input image, run the process & try to enter data. If you enter '12345', you will get 'Invalid Numeric Value' error. Add a decimal point to the end and it's accepted. * FIXED * tested with May 23 engine.
- The ILF editor does not accept valid characters in the 8859-15 character set, ie, the £ symbol exists in 8859-15, but I cannot enter it on an ILF command. (Should be fixed - 10-Dec)
- Changing the value of a --- TEMP field in the new debugger during execution seems to corrupt the field. * FIXED * July 28th engine. Could have been a display problem in the debugger, but either way, seems ok now.
|
| |
- New debugger does not show fields values correctly when using F12 to view/change a field. Field is displayed with many trailing reverse image diamonds. Try changing a --- TEMP field during execution. (Should be fixed - 27-Nov)
- Tooltips in new debugger only show the first character of the field value.(Should be fixed - 27-Nov)
- After changing the 0SA DICTIONRY file to have unicode fields, I get errors when processing the DD. Not sure what the errors are because when I drill down, I get a transcode error on statement "SET 0AD MSG2 MSG TXT ZI = 0AD MSG3 MSG TXT" in CMPL DD (VIEW DETAIL). * FIXED * Oct 9 engine
|
|
<
< |
- Certain error / warning messages are missing parts of the message. For example, go to Sys Admin/Applications and change the database id on any application to an invalid database. You'll get the message " Warning - ~1 Not on file". ~1 should be replaced by the table name - Databases in this case. (Should be fixed - 27-Nov)
|
>
> |
- Certain error / warning messages are missing parts of the message. For example, go to Sys Admin/Applications and change the database id on any application to an invalid database. You'll get the message " Warning - ~1 Not on file". ~1 should be replaced by the table name - Databases in this case. ** FIXED ** in Dec 10 engine
- The fix for ERROR/WARNING etc, broke the status area. It fills with the Unicode Replacement Character during "Em Compile" messages.
|
| |
Language Translation Support: |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.