Thanks Everyone...
I'm slowly getting the idea.
I just found a little file on the Fedora called '/etc/sysconfig/i18n' which
contains what appear to be environment variables setting the locale. That would
explain why nobody is using .profile anymore.
The installation procedures need to set up this file correctly... and compiling
the utf-8 locales, of course. I'll try compiling the locales on the Debian
myself.
My next step is figuring out how the fonts work... The Fedora installs like a
dream, but the fonts are all ugly. Yes, all the editors work fine, except Open
Office 1.1.2, which does not render accented Greek vowels, either in the text,
or on the menus. [The SuSE Open Office works great!]
--- Pablo Saratxaga <[EMAIL PROTECTED]> wrote:
>
> The reason why Ctrl-Alt-K works from us->el but not the other way around
> is a known KDE bug; the reason is that the KDE keyboard switcher applet
> doesn't load a stack of keyboard maps, but only one at once,
> and in the Greek layout there is no latin "k" letter! so you cannot
> type Ctrl-Alt-K (nor anything with latin letters) when the greek layout
> has been loaded that way.
I naturally made the assumption that the 'K' was the name of the key, not a
letter in the character set. The keyboard extention (or X itself?) should be
translating keyboard events into actions (eg "switch to next map"). All other
keyboard events get translated into characters by the current keymap. The KDE
applet is getting in the way. "If thine eye offend thee cast it out," or "Non
sunt multiplicanda entia praeter necessitatem."
[That would explain the curious behavior of the KDE Control Panel when I try to
use a non-function key in the change-keymap setting. It displays a mysterious
little box, then throws my key combination away, and reverts to the previous
setting, when I say "OK".]
> Instead of using the KDE keyboard switcher you use X11 directly
> (with setxkbmap or in the config file) and load two or more layouts
> (eg "us,el" above) then Ctrl-X or Alt-X etc with X a latin letter will
> work, as X11 will be able to find it on the "us" layout (or other layout
> you choosed).
So, 'setxkbmap' must be the command-line interface to the keyboard "extension".
This should do the trick. <happy-face>
Now, what about "input methods?"
I read somewhere, these seem to be separate processes which provide visual
feedback while the character is being composed. [They must be X applications
themselves.] I like Yudit, because it puts down the character representation of
the compose key (like the ';', the greek accent key) before I press the vowell.
I haven't seen any of that so far with xkb.
[The only problem with an input method as an application process is that the
kernel would have to perform a context switch on each keyboard event. This
seems ridiculously time consuming.]
Does it make sense to use an IM for Greek?
Any help in understanding how it all works is greatly appreciated.
I'll keep googling.
[Thanks also for the tip on setting up the Greek support.]
Thanks.
Elvis
PS
Give me some more time to get registered on the other lists, but here is
another big surprise: It looks to me like the 'rpm' command is internally used
by installation programs on archives in their data set. That would explain why
I can't make rpm recursively install all the required archives in a
distribution directory. I can't be typing dozens of command lines, or poking
around in a package-manager dialog box, to take Yudit from my SuSE dvd and put
it on my Fedora. Am I missing something?
__________________________________
Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.
http://info.mail.yahoo.com/mail_250
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
