Difference: UnicodeSETStmt (6 vs. 7)

Line: 1 to 1

META TOPICPARENT	name="UnicodeTestPlan"

SET Statement

Line: 48 to 48

- Unicode characters can be embedded in literals using unicode escape sequences. \u#### or \U########
- Truncation and UTF-32 or Space padding will take place.

Deleted:

<
<

Changed:

<
<

Test Requirements:

>
>

Test invalid combinations (Group -> Unicode/National, Unicode/National -> Group), is error message understandable?
For each of the types (Date, Format, Logic, Numeric, Text, Token), perform 4 tests: move from type into Unicode, move from type into National, move from Unicode into type, move from National into type.
Test Raw to National (with/without transcode error)
Test Raw to Unicode
Test National to Raw (with/without transcode error)
Test Unicode to Raw (with/without transcode error)
Test Unicode to Unicode
Test National to National
Test Unicode to National
Test National to Unicode
Test Truncation & padding

Changed:

<
<

Does the ILF Editor allow all valid combinates from the above list?

Does the ILF Editor give a meaningful error when entering invalid combinations?

Test Results and Notes:

Untested

Test Requirements:

Does the Process Compiler allow all valid combinates from the above list?

Does the Process Compiler give a meaningful error when encountering invalid combinations? (can use Opt-88 to force saving or errors)

Test Results and Notes:

Untested

>
>

Bug: Setting a Unicode alpha field equal to a Token field does not work. It appears to do a byte by byte set, not a character set of the Token string. (Note CNV TEXT does work) * FIXED * March 28 engine

-- SteveFrizzell - 2011-03-07