|
META TOPICPARENT |
name="UnicodeTestPlan" |
|
|
< < | SET DAY/SET MNTH |
> > | SET DAY / SET MNTH Statements |
|
|
|
< < |
Expected Behaviour
- These statements need to be revised to support all three encoding types for the destination alpha field
|
> > | Overview
- These statements have been revised to support all three encoding types for the destination alpha field
|
|
- The text for the result is taken from the 0SA MESSAGE file. This text is currently stored in a RAW alpha field.
|
|
< < |
- If the Encoding type of the destination field is NATIONAL, then the text needs to be transcoded from the RAW encoding of 8859-15 to the specified NATIONAL encoding.
- If the Encoding Type of the destination field is UNICODE, then the text needs to be transcoded from the RAW encoding of 8859-15 to UTF-32.
|
> > |
- If the Encoding type of the destination field is NATIONAL, then the text will be transcoded from the RAW encoding of 8859-15 to the specified NATIONAL encoding.
- If the Encoding Type of the destination field is UNICODE, then the text will be transcoded from the RAW encoding of 8859-15 to UTF-32.
Test Plan
Test SET DAY and SET MNTH with a Raw Alpha field.
Test SET DAY and SET MNTH with a Unicode Alpha field. |
| |
|
< < | BUGS |
> > | Test SET DAY and SET MNTH with a National Alpha field.
Bugs |
|
- The last letter of the day is repeated when using the "L" option of SET DAY. To reproduce, run SET DAY/MNTH in TST, start with 03/16/2011 date then change to 03/15/2011 (do NOT use the calendar control). Unicode/National long day fields have extra "y" at the end.
- Garbage characters are added to end of National/Unicode fields if Clock/Calendar control is used. Same example as previous, except use the Clock/Calendar control to change date to 03/17/2011.
|