Unicode Client Validations

The client will not perform data entry validations to make sure data values entered are consistent with the field encoding types. This will be done by the engine.

Overview

Initially, Only the Java Client will communicate using unicode data. The Win32 and Character clients will not support unicode data at this time.

The engine will validate entered characters against the target field's defined encoding method and issue an error if invalid. This should be a 'hard' edit check, ie, the same type of check that prevents alpha characters from being entered into a numeric, or invalid characters in a Format field.

• RAW - 8859-15
• NATIONAL - specified single-byte encoding method as specified in System Admin
• UNICODE

Test Plan:

1. Try to enter National characters into a Raw field, Unicode characters into a Raw file and Unicode characters into a National field. The engine should throw an error if the national/unicode character is not part of the Raw character set, or if the Unicode character is not part of the National set.

Bugs

1. The engine accepts any character into any field, no errors are displayed. However, trying to enter a ¤ symbol (00A4) into a raw field does not get accepted, ie, the previous field contents of the raw field are unchanged.