Difference: UnicodeDataEntry (1 vs. 4)

Revision 42011-04-13 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="UnicodeTestPlan"

Unicode Client Validations

Line: 19 to 19
 
  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

Deleted:
<
<
  1. The engine accepts any character into any field.
 \ No newline at end of file
Added:
>
>
  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.
 \ No newline at end of file

Revision 32011-04-01 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="UnicodeTestPlan"

Unicode Client Validations

Line: 19 to 19
 
  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

Changed:
<
<
  1. The engine accepts any character into any field.
>
>
  1. The engine accepts any character into any field.
 \ No newline at end of file

Revision 22011-03-22 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="UnicodeTestPlan"

Unicode Client Validations

Changed:
<
<		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.

Changed:
<
<		 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
Added:
>
>
  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.

Revision 12011-03-09 - PeteBrower

Line: 1 to 1
Added:
>
>
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.

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

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

Test Plan:

View topic | History: r4 < r3 < r2 < r1 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback