Unicode Test Plan

1. Invalid (blank) occurrence number in Image Editor after hitting F11 then attempting to edit Item. ** FIXED ** March 21 engine
2. 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
3. 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.

1. 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.
2. 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.
3. 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.
4. Changing the value of a --- TEMP field in the new debugger during execution seems to corrupt the field.