|
META TOPICPARENT |
name="UnicodeTestPlan" |
Unicode Client Validations |
|
< < | The client will now perform data entry validations to make sure data values entered are consistent with the field encoding types. |
> > | 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 client will validate entered characters against the target field's defined encoding method before sending field to engine |
> > | 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:
\ No newline at end of file |
|
> > |
- 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
- The engine accepts any character into any field.
|