Difference: UnicodeERROR_WARNING_MESSAGE_CANCEL_REFRESHStmt (3 vs. 4)

Revision 42011-04-01 - JeanNeron

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

ERROR / WARNING / MESSAGE / CANCEL / REFRESH Statements

Changed:
<
<

>
>
CANCEL screen using literals has extra characters after the cancel message (looks like a question mark in a reverse image diamond). Sometimes wraps text unnecessarily or displays other garbage characters, depending on what other tests were done first.
No embedded literal Unicode characters were transcoded, they were displayed as is.
Invalid embedded literal Unicode characters did not generate an error (probably due to previous bug).
Using TEMP 80 with embedded Unicode displayed incorrectly (characters had spaces between them), all statements
Using TEMP 80 with no embedded Unicode displayed incorrectly (characters had spaces between them), all statements
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)

 

Overview

  1. The internal storage type of all messages created by these statements must be UTF-32.
Line: 18 to 18
 
  1. Test TEMP fields, all statements

Bugs

Changed:
<
<
  • All literal messages are truncated after approx 20 characters (including the leading Error - , Warning - , etc) for ERROR/WARNING/MESSAGE/REFRESH Statements - * FIXED * March 28 engine
  • CANCEL screen using literals has extra characters after the cancel message (looks like a question mark in a reverse image diamond). Sometimes wraps text unnecessarily or displays other garbage characters, depending on what other tests were done first.
  • No embedded literal Unicode characters were transcoded, they were displayed as is.
  • Invalid embedded literal Unicode characters did not generate an error (probably due to previous bug).
  • Using TEMP 80 with embedded Unicode displayed incorrectly (characters had spaces between them), all statements
  • Using TEMP 80 with no embedded Unicode displayed incorrectly (characters had spaces between them), all statements
  • 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)
>
>
  1. All literal messages are truncated after approx 20 characters (including the leading Error - , Warning - , etc) for ERROR/WARNING/MESSAGE/REFRESH Statements - * FIXED * March 28 engine
  2. CANCEL screen using literals has extra characters after the cancel message (looks like a question mark in a reverse image diamond). Sometimes wraps text unnecessarily or displays other garbage characters, depending on what other tests were done first.
  3. No embedded literal Unicode characters were transcoded, they were displayed as is.
  4. Invalid embedded literal Unicode characters did not generate an error (probably due to previous bug).
  5. Using TEMP 80 with embedded Unicode displayed incorrectly (characters had spaces between them), all statements
  6. Using TEMP 80 with no embedded Unicode displayed incorrectly (characters had spaces between them), all statements
  7. 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)
  -- JeanNeron - 2011-03-09 \ No newline at end of file
 
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