i run a woody 3.0r1 linux, and i can't seem to get certain german characters displayed (or typed). this effect is limited to certain applications. for example, i can see and type the characters in my mailer, (as they appear in the subject line), emacs will take them (though saving files with these characters will typically bugger them up), but in an xterm (or konsole), or when i work with x11 disabled, i can't type or see these characters: when i call "ls" on a directory that holds entries with these characters, they will be replaced by a question mark... trying to type them gives me the error beep.
i'd be thankful for suggestions.
thanks for your help in advance.
matthias schweinoch
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
maybe you can try this
http://eyegene.ophthy.med.umich.edu/unicode/
I'vnt try myself!
> i run a woody 3.0r1 linux, and i can't seem to get certain german characters displayed (or typed). this effect is limited to certain applications. for example, i can see and type the characters in my mailer, (as they appear in the subject line), emacs will take them (though saving files with these characters will typically bugger them up), but in an xterm (or konsole), or when i work with x11 disabled, i can't type or see these characters: when i call "ls" on a directory that holds entries with these characters, they will be replaced by a question mark... trying to type them gives me the error beep.
Hi,
maqybe you try this:
1) edit /etc/inputrc:
# To allow the use of 8bit-characters like the german umlauts, comment out
# the line below. However this makes the meta key not work as a meta key,
# which is annoying to those which don't need to type in 8-bit characters.
set convert-meta off
2) run dpkg-reconfigure localeconf
3) run dpkg-reconfigure locales
4) change your language settings in kde
Oliver
--
... don't touch the bang bang fruit
> hi,
>
> when i call "ls" on a directory that holds entries with these
> characters, they will be replaced by a question mark... trying to type
> them gives me the error beep.
This effect is due to a mismatch between the charset used for the
filename and the console charset or the console using a font that
doesn't contain those characters. If you get a single question mark,
it's probably the second one as UTF8 or other unicode encodings tend to
produce longer replacements.
You might try reconfiguring the locales package to create some UTF8
charsets and then run the console with one of those locales. Be aware
however that playing with locales can be somewhat painful with funny and
unexpected results if you use it for a longer time since you'll get a
mix of the old (probably iso8859-1 or 8859-15) and utf8 encodings which
can be quite irritating at times.
--
Got Backup?
Jabber: Shadowdancer at jabber.fsinf.de