Your message dated Wed, 28 Oct 2015 07:56:43 +0000
with message-id <[email protected]>
and subject line done
has caused the Debian Bug report #452785,
regarding Can not input UTF-8 chars in prompt
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
452785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452785
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ksh
Version: 93s+20071105-1
Severity: normal
It seems AT&T KSH93 can not do what zsh, bash and mksh already can do:
It is not possible to input UTF-8 -chars to its prompt, excpet those
that belong to US-ASCII. Whenever I hit some Scnadinavian characters
(ÅÄÖåäö), it works like a Return-key.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (1100, 'testing'), (990, 'stable'), (500,
'testing-proposed-updates'), (500, 'proposed-updates'), (101, 'testing'), (99,
'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-3-k7 (SMP w/1 CPU core)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages ksh depends on:
ii libc6 2.6.1-5 GNU C Library: Shared libraries
ksh recommends no packages.
-- no debconf information
--
Juhapekka "naula" Tolvanen * http colon slash slash iki dot fi slash juhtolv
"S teki. S teki. S teki. S wo kakusei. S teki. S teki. S teki. S wo umekome.
S teki. S teki. S teki. M wo setsudan. S teki. S teki. Puratonikku wo
hajimemashou." Dir en grey
--- End Message ---
--- Begin Message ---
Version: 93u+-1
Seeing as I can'treproduce this and based upon this entry in
http://www2.research.att.com/~astopen/download/gen/ast-ksh.html#ksh93
"07-11-27 A bug in which compound variable UTF-8 multibyte values were not
expanded or traced properly has been fixed."
I think it was probably closed earlier.
--- End Message ---
