Difference: UnicodeERROR_WARNING_MESSAGE_CANCEL_REFRESHStmt (1 vs. 10)

Revision 102011-11-22 - JeanNeron

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

ERROR / WARNING / MESSAGE / CANCEL / REFRESH Statements

Line: 20 to 20
 
  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). * FIXED * 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.
Changed:
<
<
  1. If the command contains an embedded literal Unicode characters, nothing displays at all. Applies to all commands.
  2. 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. * FIXED * Aug 4 engine
  3. Using TEMP 80 with embedded Unicode does not display at all, all statements.
>
>
  1. If the command contains an embedded literal Unicode characters, nothing displays at all. Applies to all commands. * FIXED * Nov 21 engine and 510a2 client
  2. 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. * FIXED * Aug 4 engine
  3. Using TEMP 80 with embedded Unicode does not display at all, all statements. * FIXED * Nov 21 engine and 510a2 client
 
  1. Using TEMP 80 with no embedded Unicode displayed incorrectly (characters had spaces between them), all statements. * FIXED * July 4 engine.
  2. 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) * FIXED * July 4 engine.
Changed:
<
<
  1. When displaying multiple messages via Control+M, characters are triple spaced. * FIXED * Aug 4 engine
>
>
  1. When displaying multiple messages via Control+M, characters are triple spaced. * FIXED * Aug 4 engine
 
  1. Runtime messages are missing, ie, the 'Select Acknowledge Delete to delete this record' message does not appear. * FIXED * July 28th engine.
  2. Runtime errors do not have the 'Error' prefix, ie, 'Already on File' does not have Error and therefore shows as green instead of red * FIXED * changed severity of message 200170 to 2.

Revision 92011-08-04 - JeanNeron

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

ERROR / WARNING / MESSAGE / CANCEL / REFRESH Statements

Line: 21 to 21
 
  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). * FIXED * 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.
  3. If the command contains an embedded literal Unicode characters, nothing displays at all. Applies to all commands.
Changed:
<
<
  1. 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.
>
>
  1. 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. * FIXED * Aug 4 engine
 
  1. Using TEMP 80 with embedded Unicode does not display at all, all statements.
  2. Using TEMP 80 with no embedded Unicode displayed incorrectly (characters had spaces between them), all statements. * FIXED * July 4 engine.
  3. 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) * FIXED * July 4 engine.
Changed:
<
<
  1. When displaying multiple messages via Control+M, characters are triple spaced.
  2. Runtime messages are missing, ie, the 'Select Acknowledge Delete to delete this record' message does not appear. * FIXED * July 28th engine.
>
>
  1. When displaying multiple messages via Control+M, characters are triple spaced. * FIXED * Aug 4 engine
  2. Runtime messages are missing, ie, the 'Select Acknowledge Delete to delete this record' message does not appear. * FIXED * July 28th engine.
 
  1. Runtime errors do not have the 'Error' prefix, ie, 'Already on File' does not have Error and therefore shows as green instead of red * FIXED * changed severity of message 200170 to 2.

-- JeanNeron - 2011-03-09

Revision 82011-07-29 - JeanNeron

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

ERROR / WARNING / MESSAGE / CANCEL / REFRESH Statements

Line: 19 to 19
 

Bugs

  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
Changed:
<
<
  1. CANCEL screen using literals has extra characters after the cancel message (looks like a question mark in a reverse image diamond). * FIXED * 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.
>
>
  1. CANCEL screen using literals has extra characters after the cancel message (looks like a question mark in a reverse image diamond). * FIXED * 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.
 
  1. If the command contains an embedded literal Unicode characters, nothing displays at all. Applies to all commands.
  2. 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.
  3. Using TEMP 80 with embedded Unicode does not display at all, all statements.
  4. Using TEMP 80 with no embedded Unicode displayed incorrectly (characters had spaces between them), all statements. * FIXED * July 4 engine.
  5. 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) * FIXED * July 4 engine.
  6. When displaying multiple messages via Control+M, characters are triple spaced.
Changed:
<
<
  1. Runtime messages are missing, ie, the 'Select Acknowledge Delete to delete this record' message does not appear.
  2. Runtime errors do not have the 'Error' prefix, ie, 'Already on File' does not have Error and therefore shows as green instead of red
>
>
  1. Runtime messages are missing, ie, the 'Select Acknowledge Delete to delete this record' message does not appear. * FIXED * July 28th engine.
  2. Runtime errors do not have the 'Error' prefix, ie, 'Already on File' does not have Error and therefore shows as green instead of red * FIXED * changed severity of message 200170 to 2.
  -- JeanNeron - 2011-03-09 \ No newline at end of file

Revision 72011-07-27 - JeanNeron

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

ERROR / WARNING / MESSAGE / CANCEL / REFRESH Statements

Line: 19 to 19
 

Bugs

  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
Changed:
<
<
  1. CANCEL screen using literals has extra characters after the cancel message (looks like a question mark in a reverse image diamond).
>
>
  1. CANCEL screen using literals has extra characters after the cancel message (looks like a question mark in a reverse image diamond). * FIXED * 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.
 
  1. If the command contains an embedded literal Unicode characters, nothing displays at all. Applies to all commands.
  2. 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.
  3. Using TEMP 80 with embedded Unicode does not display at all, all statements.
Changed:
<
<
  1. Using TEMP 80 with no embedded Unicode displayed incorrectly (characters had spaces between them), all statements. * FIXED * July 4 engine.
  2. 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) * FIXED * July 4 engine.
>
>
  1. Using TEMP 80 with no embedded Unicode displayed incorrectly (characters had spaces between them), all statements. * FIXED * July 4 engine.
  2. 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) * FIXED * July 4 engine.
 
  1. When displaying multiple messages via Control+M, characters are triple spaced.
  2. Runtime messages are missing, ie, the 'Select Acknowledge Delete to delete this record' message does not appear.
  3. Runtime errors do not have the 'Error' prefix, ie, 'Already on File' does not have Error and therefore shows as green instead of red

Revision 62011-07-05 - 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: 19 to 19
 

Bugs

  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
Changed:
<
<
  1. 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.
  2. No embedded literal Unicode characters were transcoded, they were displayed as is.
  3. Invalid embedded literal Unicode characters did not generate an error (probably due to previous bug).
  4. Using TEMP 80 with embedded Unicode displayed incorrectly (characters had spaces between them), all statements
  5. Using TEMP 80 with no embedded Unicode displayed incorrectly (characters had spaces between them), all statements
  6. 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. CANCEL screen using literals has extra characters after the cancel message (looks like a question mark in a reverse image diamond).
  2. If the command contains an embedded literal Unicode characters, nothing displays at all. Applies to all commands.
  3. 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.
  4. Using TEMP 80 with embedded Unicode does not display at all, all statements.
  5. Using TEMP 80 with no embedded Unicode displayed incorrectly (characters had spaces between them), all statements. * FIXED * July 4 engine.
  6. 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) * FIXED * July 4 engine.
 
  1. When displaying multiple messages via Control+M, characters are triple spaced.
Changed:
<
<
  1. Runtime messages are garbled, ie, the 'Select Acknowledge Delete to delete this record' message is messed up
>
>
  1. Runtime messages are missing, ie, the 'Select Acknowledge Delete to delete this record' message does not appear.
 
  1. Runtime errors do not have the 'Error' prefix, ie, 'Already on File' does not have Error and therefore shows as green instead of red

-- JeanNeron - 2011-03-09 \ No newline at end of file

Revision 52011-04-28 - JeanNeron

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

ERROR / WARNING / MESSAGE / CANCEL / REFRESH Statements

Line: 25 to 25
 
  1. Using TEMP 80 with embedded Unicode displayed incorrectly (characters had spaces between them), all statements
  2. Using TEMP 80 with no embedded Unicode displayed incorrectly (characters had spaces between them), all statements
  3. 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)
Added:
>
>
  1. When displaying multiple messages via Control+M, characters are triple spaced.
  2. Runtime messages are garbled, ie, the 'Select Acknowledge Delete to delete this record' message is messed up
  3. Runtime errors do not have the 'Error' prefix, ie, 'Already on File' does not have Error and therefore shows as green instead of red
  -- JeanNeron - 2011-03-09 \ No newline at end of file

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

Revision 32011-03-28 - JeanNeron

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

ERROR / WARNING / MESSAGE / CANCEL / REFRESH Statements

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
>
>
  • 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).

Revision 22011-03-17 - PeteBrower

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

ERROR / WARNING / MESSAGE / CANCEL / REFRESH Statements


Changed:
<
<
Expected Behaviour:
>
>

Overview

 
  1. The internal storage type of all messages created by these statements must be UTF-32.
  2. These statements need to be modified to accept UTF-32 TEMP fields as an operand.
  3. These statements need to be modified to output UTF-32 text.
  4. 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.
  5. 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
Changed:
<
<
Testing
>
>

Test Plan

 
  1. Test normal literals, all statements
  2. Test literals with embedded Unicode, all statements

Revision 12011-03-09 - JeanNeron

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

ERROR / WARNING / MESSAGE / CANCEL / REFRESH Statements


Expected Behaviour:

  1. The internal storage type of all messages created by these statements must be UTF-32.
  2. These statements need to be modified to accept UTF-32 TEMP fields as an operand.
  3. These statements need to be modified to output UTF-32 text.
  4. 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.
  5. 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

Testing

  1. Test normal literals, all statements
  2. Test literals with embedded Unicode, all statements
  3. Test literals with invalid embedded Unicode (?), all statements
  4. Test TEMP fields, all statements

Bugs

  • All literal messages are truncated after approx 20 characters (including the leading Error - , Warning - , etc) for ERROR/WARNING/MESSAGE/REFRESH Statements
  • 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)

-- JeanNeron - 2011-03-09

 
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