Difference: UnicodeTestPlan (54 vs. 55)

Line: 1 to 1

META TOPICPARENT	name="WebHome"

Unicode Test Plan

Line: 57 to 57

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.

Changed:

<
<

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. (Should be fixed - 28-Nov)

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.

Changed:

<
<

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.

>
>

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.

Changed:

<
<

Appx doesn't complain when a Unicode character is entered into a Raw field. The character is silently discarded, but either the engine or the client should give the user some kind of error, probably the same error when entering invalid characters into a formatted field.
If I have a National or Unicode field on an image with no GUI attributes, I can enter Unicode/National data into it. if I call the record up in Inquire mode, the Unicode/National data does not show properly (reverse image diamond with embedded question mark). However, if I call it up in change mode, the data shows properly. Why the difference? If I make the field RAW TEXT, then it shows properly in all modes.

>
>

Appx doesn't complain when a Unicode character is entered into a Raw field. The character is silently discarded, but either the engine or the client should give the user some kind of error, probably the same error when entering invalid characters into a formatted field. (Should be fixed - 10-Dec)
If I have a National or Unicode field on an image with no GUI attributes, I can enter Unicode/National data into it. if I call the record up in Inquire mode, the Unicode/National data does not show properly (reverse image diamond with embedded question mark). However, if I call it up in change mode, the data shows properly. Why the difference? If I make the field RAW TEXT, then it shows properly in all modes. (Should be fixed - 10-Dec)

Run a field cross reference in TST on the field APPEND NORMAL. After the results are displayed, just press END and then Enter at the 'Are you sure' dialog box. Appx crashes with: * glibc detected * corrupted double-linked list: 0x0898b488 * in character mode. In GUI mode, the client

just hangs. Even simpler, just run the X-ref and cancel out before selecting anything, same result. * FIXED * July 28 engine.
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)