| |
| META TOPICPARENT |
name="UnicodeTestPlan" |
ERROR / WARNING / MESSAGE / CANCEL / 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)
|
>
> |
|
| | Overview
- The internal storage type of all messages created by these statements must be UTF-32.
|
| | Bugs
- 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)
|
>
> |
- CANCEL screen using literals has extra characters after the cancel message (looks like a question mark in a reverse image diamond).
- If the command contains an embedded literal Unicode characters, nothing displays at all. Applies to all commands.
- 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.
- Using TEMP 80 with embedded Unicode does not display at all, all statements.
- Using TEMP 80 with no embedded Unicode displayed incorrectly (characters had spaces between them), all statements. * FIXED * July 4 engine.
- 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.
|
| |
- When displaying multiple messages via Control+M, characters are triple spaced.
|
|
<
< |
- Runtime messages are garbled, ie, the 'Select Acknowledge Delete to delete this record' message is messed up
|
>
> |
- Runtime messages are missing, ie, the 'Select Acknowledge Delete to delete this record' message does not appear.
|
| |
- 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 |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.