From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with Languages Busybox
Date: Mon, 16 Jun 2014 08:00:50 +0200 [thread overview]
Message-ID: <539E8812.8050608@mind.be> (raw)
In-Reply-To: <CAEex6OREg7DJBsawCM_Gto_hk3VUyieLTcBz=sCRZpQ7BPL=Mg@mail.gmail.com>
On 06/12/14 22:15, Correa Romero, Julian wrote:
> Hello, I am new at this.
>
> I built a system with buildroot-2014.02 glibc and buildroot toolchain, I have
> problems with my language that is Spanish when I press the letter ?, ?, ?, ?, ?,
> ? or ? it appears on the terminal (arg: 1). I did the loadkmap < es.bin. if the
> file has this characters also they aren't showed.
>
> What can I do to give support to the language?
First of all, I'm surprised you don't have this on your host machine, since
this is normal bash behaviour.
From the bash manual:
convert-meta (On)
If set to On, readline will convert characters with the eighth bit set to
an ASCII key sequence by stripping the eighth bit and prefixing an escape
character (in effect, using escape as the meta prefix).
Since ? in UTF-8 is encoded as 0xc3 0xb1, this sequence is interpreted by bash
as M-C M-1. M-C is not bound to anything by default so is ignored. M-1 is bound
to digit-argument.
So to solve this problem, add the following to your .inputrc:
set convert-meta Off
Note that bash will still expand these characters to escape sequences, but it
should be sufficient for typing file names. Read the man page to find out how to
solve _that_ issue.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2014-06-16 6:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 20:15 [Buildroot] Problem with Languages Busybox Correa
2014-06-16 6:00 ` Arnout Vandecappelle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=539E8812.8050608@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox