Difference: UnicodeTestPlan (32 vs. 33)

Revision 332011-04-29 - JeanNeron

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

Unicode Test Plan

Line: 37 to 37
 

RECEIVE / LOCAL*** (Tested/Bugs)

CNV BIN**** (Tested/Bugs)

CNV PORT

Changed:
<
<

PACK / UNPACK

>
>

PACK / UNPACK**** (Tested/Bugs)

 

CNV TEXT

SET DAY / SET MNTH**** (Tested/Bugs)

DEFINE / UNDEFINE

Line: 46 to 46
 

COMPUTE / TOTAL**** (Tested/Bugs)

SCAN

PRINT

Changed:
<
<

BROWSE

>
>

BROWSE**** (No Changes Required) ***

  ...

Misc Bugs

Line: 62 to 62
 
  1. The ILF editor does not accept valid characters in the 8859-15 character set, ie, the £ symbol exists in 8859-15, but I cannot enter it on an ILF command.
  2. Changing the value of a --- TEMP field in the new debugger during execution seems to corrupt the field.
  3. Appx doesn't complain when a Unicode character is entered into a Raw field. The character is silently discarded, but either the engine or the client should give the user some kind of error, probably the same error when entering invalid characters into a formatted field.
Added:
>
>
  1. If I have a National or Unicode field on an image with no GUI attributes, I can enter Unicode/National data into it. if I call the record up in Inquire mode, the Unicode/National data does not show properly (reverse image diamond with embedded question mark). However, if I call it up in change mode, the data shows properly. Why the difference? If I make the field RAW TEXT, then it shows properly in all modes.
  Language Translation Support:
View topic | History: r59 < r58 < r57 < r56 | More topic actions...
 
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