Jo Even Skarstein, 07.01.2013 21:39:34:
On Sat, 2013-01-05 at 08:37 +0100, Vincent Rivière wrote:Do you mean that loading an external keyboard layout with keyboard.tbl alsochanges the UI language? That would be very wrong.Actually it does. It resets the UI language part of the cookie to the NVRAM language (if present, os_conf language if not) every time a keyboard table is set. Don't know why, but it does. It would normally not do any harm though, so you're right, loading a keyboard table shouldn't change the UI language.
It uses the _AKP-language, if not present the NVRAM-language, if not present the OS-language. If the UI-language is changed at runtime, it should always be represented in the _AKP-cookie and everything is o.k.
But IIRC this was discussed here a while ago. Something about the TT only setting the lowest byte in the _AKP cookie (i.e. there's only one
I guess _AKP exists only since falcon-TOS at all and MiNT did only set the keyboard in the cookie, which would lead to a wrong UI-language (0).
language, it doesn't differ between UI and keyboard) so XaAES use the "keyboard" language in this case.
That was an older version.
Maybe Helmut remembers more about this than I do.
I hope I do ... -- Helmut Karlowski