| |
| META TOPICPARENT |
name="UnicodeTestPlan" |
Unicode Client Communications |
| | Test Plan:
Bugs: |
|
<
< |
- Some characters do not display properly. In the range U+0400 to U+0402, the top part of the character is missing, which makes the first two characters look the same (Mac client) or the U+0400 character does not display at all (Windows client).
- A field that contains '\n', chr(10) or '\r' and is set as a Label widget does not display correctly. Those characters should create a new line, but instead display as a space.
|
>
> |
- Some characters do not display properly. In the range U+0400 to U+0402, the top part of the character is missing, which makes the first two characters look the same (Mac client) or the U+0400 character does not display at all (Windows client). The Windows probelm could be because the font DialogInput does not have anythhing to display for U+0400.
- A field that contains '\n', chr(10) or '\r' and is set as a Label widget does not display correctly. Those characters should create a new line, but instead display as a space, or treat them as literals (as the non unicode client does).
|
| | |
|
<
< | |
| | \ No newline at end of file |
|
>
> | -- PeteBrower - 2011-03-04 |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.