UnicodeERROR_WARNING_MESSAGE_CANCEL_REFRESHStmt < Main

---+ ERROR / WARNING / MESSAGE / CANCEL / REFRESH Statements

<br />%TOC%
---++ Overview

   1 The internal storage type of all messages created by these statements must be UTF-32.
   1 These statements need to be modified to accept UTF-32 TEMP fields as an operand.
   1 These statements need to be modified to output UTF-32 text.
   1 A Literal operand is consider to be a RAW Alpha value and must therefore be transcoded from an 8859-1 encoding to a UTF-32 encoding before the operation can be performed.
   1 If a literal operand contains embedded Unicode escape sequences, the corresponding UTF-32 character will replace the Unicode escape sequences in the resulting UTF-32 message
---++ Test Plan

   1 Test normal literals, all statements
   1 Test literals with embedded Unicode, all statements
   1 Test literals with invalid embedded Unicode (?), all statements
   1 Test TEMP fields, all statements
---++ Bugs

   1 All literal messages are truncated after approx 20 characters (including the leading Error - , Warning - , etc) for ERROR/WARNING/MESSAGE/REFRESH Statements - <strong>* FIXED *</strong> March 28 engine
   1 <span style="color: #ff0000;"><span style="color: black;" class="WYSIWYG_COLOR">CANCEL screen using literals has extra characters after the cancel message (looks like a question mark in a reverse image diamond). <strong>* FIXED *</strong> 7/27/11 by changing the input 0LA ERROR MESSAGE to use '\n' instead of chr(182) for a newline and changing --- WORK ERROR TXT to a label widget. </span></span>
   1 <span style="color: #ff0000;"><span style="color: black;" class="WYSIWYG_COLOR">If the command contains an embedded literal Unicode characters, nothing displays at all. Applies to all commands. ** FIXED ** Nov 21 engine and 510a2 client</span></span>
   1 <span style="color: #ff0000;"><span style="color: black;" class="WYSIWYG_COLOR"><span style="color: black;">Invalid embedded literal Unicode characters cause the process to end abruptly or the session to crash, all statements. The first time you attempt this, the process just ends, the second time the session crashes. After that, the Em must be recompiled before the process will even run.</span></span></span> <strong>* FIXED *</strong> Aug 4 engine
   1 <span style="color: #ff0000;"><span style="color: black;" class="WYSIWYG_COLOR">Using TEMP 80 with embedded Unicode does not display at all, all statements. ** FIXED ** Nov 21 engine and 510a2 client</span></span>
   1 <span style="color: #ff0000;"><span style="color: black;" class="WYSIWYG_COLOR">Using TEMP 80 with no embedded Unicode displayed incorrectly (characters had spaces between them), all statements. <strong>* FIXED *</strong> July 4 engine.</span></span>
   1 <span style="color: #ff0000;"><span style="color: black;" class="WYSIWYG_COLOR">Using TEMP 80 and MESSAGE command appeared to combine text of previous WARNING statement with new MESSAGE command (Unicode and non Unicode characters in TEMP 80) <strong>* FIXED *</strong> July 4 engine.</span></span>
   1 <span style="color: #ff0000;"><span style="color: black;" class="WYSIWYG_COLOR"><span style="color: black;">When displaying multiple messages via Control+M, characters are triple spaced.</span></span></span> <strong>* FIXED *</strong> Aug 4 engine
   1 <span style="color: #ff0000;"><span style="color: black;" class="WYSIWYG_COLOR">Runtime messages are missing, ie, the 'Select Acknowledge Delete to delete this record' message does not appear. <strong>* FIXED *</strong> July 28th engine.</span></span>
   1 <span style="color: #ff0000;"><span style="color: black;" class="WYSIWYG_COLOR">Runtime errors do not have the 'Error' prefix, ie, 'Already on File' does not have Error and therefore shows as green instead of red <strong>* FIXED *</strong> changed severity of message 200170 to 2.</span></span>

-- Main.JeanNeron - 2011-03-09
This topic: Main > WebHome > UnicodeTestPlan > UnicodeERROR_WARNING_MESSAGE_CANCEL_REFRESHStmt
Topic revision: r10 - 2011-11-22 - JeanNeron