On Thursday 10 January 2008 10:36, Alexander Griesser wrote:
> Hi!
>
> I'm still stuggling with getting the german umlauts (ä,ö,ü, a.s.o)
> working on my thinclient installation.
> The really strange thing is, that it doesn't seem to be a keyboard
> layout problem at all.
>
> When I'm at the ash command prompt, I can _NOT_ type ö, ä, ü and what
> is really strange, I cannot type the § character.
>
> In the following output I tried to enter these characters in the first
> line (you can't see them, because they didn't get accepted).
> In the second line, I used the `read` builtin to fill a variable with
> input and that worked perfectly.
>
> I can reproduce this every time and on all my systems (even with a
> freshly compiled busybox on my desktop system), so I'm sure it has
> nothing todo with keyboard layout settings, language settings, etc.
>
> ~/busybox/busybox-1.9.0 $ ll"!$"$"$
> ~/busybox/busybox-1.9.0 $ read TEST
> äöü"!§$
> ~/busybox/busybox-1.9.0 $
>
> Can anyone reproduce this too?
Works for me. Please post your .config
Assuming that you are using line editing,
this is the plase where "ordinary" chars are inserted
into line buffer. Can you add bb_error_msg(...)
as indicated by '+'? Does it trigger for umlauts?
libbb/lineedit.c
================
default: /* If it's regular input, do the normal thing */
/* Control-V -- force insert of next char */
if (c == CTRL('V')) {
if (safe_read(STDIN_FILENO, &c, 1) < 1)
goto prepare_to_die;
if (c == 0) {
beep();
break;
}
}
#if ENABLE_FEATURE_EDITING_VI
if (vi_cmdmode) /* Don't self-insert */
break;
#endif
if (command_len >= (maxsize - 2)) /* Need to
leave space for enter */
break;
+bb_error_msg("Adding char with code %d", c);
command_len++;
if (cursor == (command_len - 1)) { /* Append if at
the end of the line */
command[cursor] = c;
command[cursor+1] = '\0';
cmdedit_set_out_char(' ');
} else { /* Insert otherwise */
--
vda
_______________________________________________
busybox mailing list
[email protected]
http://busybox.net/cgi-bin/mailman/listinfo/busybox
