Project

General

Profile

Bug #5570

properly support keyboard input for multi-byte charsets

Added by Alexandru Lungu almost 3 years ago. Updated almost 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:

History

#1 Updated by Alexandru Lungu almost 3 years ago

FWD does not properly map UTF-8 characters to key codes as 4GL uses a rather raw bitstring representation. Consider ĵ (Latin Small Letter J with circumflex), which in FWD is mapped to key code 309 and in 4GL to 50357. This issue may cause key code conflicts; ĵ ans F9 has the same key code in FWD (309). For other charsets (e.g. UTF-16), the key code for ĵ or F9 may differ (to be tested).

For better understanding, consider:
  • testcases/uast/i18n/printable_checker.p, which displays a simple fill-in. Experiment with different UTF-8 inputs and check which ones are printable. Specifically for ĵ, use the Esperanto keyboard language - this way the key code conflict can be reproduced.
  • testcases/uast/i18n/key_code_checker.p, which prints a key's code and its representation. Experiment with different UTF-8 inputs and check the codes both in 4GL and FWD. Note that -cpstream UTF-8 should be used in 4GL.

#3 Updated by Greg Shah almost 3 years ago

  • Subject changed from Add support for multi-byte charsets to properly support keyboard input for multi-byte charsets

Also available in: Atom PDF