---+ SET DAY / SET MNTH Statements <br />%TOC% ---++ 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 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. Test SET DAY and SET MNTH with a National Alpha field. ---++ Bugs 1 <span style="color: #ff0000;"><span style="color: black;" class="WYSIWYG_COLOR">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. ** FIXED ** July 4 engine.</span></span> 1 <span style="color: #ff0000;"><span style="color: black;" class="WYSIWYG_COLOR">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. ** FIXED ** July 4 engine.</span></span> -- Main.JeanNeron - 2011-03-16
This topic: Main
>
WebHome
>
UnicodeTestPlan
>
UnicodeSET_DAY_SET_MNTHStmt
Topic revision: r4 - 2011-07-05 - JeanNeron
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback