PuTTY bug win-tounicodeex-bis
Home
|
FAQ
|
Feedback
|
Licence
|
Updates
|
Mirrors
|
Keys
|
Links
|
Team
Download:
Stable
·
Pre-release
·
Snapshot
|
Docs
|
Privacy
|
Changes
|
Wishlist
summary: Regression in Windows Unicode keyboard handling
class: bug: This is clearly an actual problem we want fixed.
difficulty: fun: Just needs tuits, and not many of them.
priority: high: This should be fixed in the next release.
absent-in: 0.68 b189df947d2625499cf508fd1fae7e18b03b9247
present-in: 73039b7831aa863fabba1e6ff06471643303ae09 0.69
fixed-in: 5a576e0c891ddc745ea1f67bcca10f1386ff1849 (0.70)
PuTTY 0.69 inadvertently reverted to using the Windows API
ToAsciiEx() instead of ToUnicodeEx(), which we had
started using in 0.63 (win-tounicodeex).
This prevents typing characters outside the current Windows code page
into the PuTTY terminal window. We haven't tested for the
consequences, but previous correspondence suggests that this can be
expected to cause problems including the following:
- Inability to enter Romanian characters s-comma and t-comma (ș
and ț), which are in ISO-8859-16 but not ISO-8859-2, on at least
Windows XP.
- Trouble with keyboards in Unicode-only locales (Armenian, Georgian
etc).
- Inability to enter characters outside the current ANSI code page
with Alt-Numpad-plus.
If you want to comment on this web site, see the
Feedback page.
(last revision of this bug record was at 2017-04-29 12:34:56 +0100)