From: Sam Ravnborg <sam@ravnborg.org>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-kbuild@vger.kernel.org,
Artem Bityutskiy <dedekind1@gmail.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
Martin Walch <walch.martin@web.de>
Subject: Re: [PATCH 2/2] kconfig: nconfig: fix multi-byte UTF handling
Date: Fri, 6 Jun 2014 15:18:13 +0200 [thread overview]
Message-ID: <20140606131813.GD4889@ravnborg.org> (raw)
In-Reply-To: <1401868351-24014-3-git-send-email-computersforpeace@gmail.com>
On Wed, Jun 04, 2014 at 12:52:31AM -0700, Brian Norris wrote:
> Currently, Kconfig descriptions that use multi-byte UTF-8 characters
> (such as MTD_NAND_CAFE) will have their menu entries dropped from the
> 'make nconfig' ncurses menu, and all subsequent entries in the same
> window will be omitted. This seems to be due to the ncurses 'menu'
> library, which does not traditionally handle UTF-8 >8-bit characters
> properly.
>
> The ncursesw library ('w' is for "wide") is written to handle these
> UTF-8 characters, and is practically a drop-in replacement at the source
> level. Use it by default, if available.
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=43067
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: linux-kbuild@vger.kernel.org
> Cc: Martin Walch <walch.martin@web.de>
Acked-by: Sam Ravnborg <sam@ravnborg.org>
next prev parent reply other threads:[~2014-06-06 13:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 7:52 [PATCH 0/2] kconfig: fix multi-byte UTF handling in nconfig Brian Norris
2014-06-04 7:52 ` [PATCH 1/2] kconfig: lxdialog: fix spelling Brian Norris
2014-06-04 7:52 ` [PATCH 2/2] kconfig: nconfig: fix multi-byte UTF handling Brian Norris
2014-06-06 13:18 ` Sam Ravnborg [this message]
2014-06-05 1:53 ` [PATCH 0/2] kconfig: fix multi-byte UTF handling in nconfig Martin Walch
2014-06-06 13:16 ` Sam Ravnborg
2014-06-06 13:17 ` Sam Ravnborg
2014-07-10 8:52 ` Brian Norris
2014-08-20 16:40 ` Brian Norris
2014-08-22 11:02 ` Michal Marek
2014-08-24 5:17 ` Brian Norris
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=20140606131813.GD4889@ravnborg.org \
--to=sam@ravnborg.org \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=walch.martin@web.de \
--cc=yann.morin.1998@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.