From: Sam Ravnborg <sam@ravnborg.org>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-kbuild@vger.kernel.org,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH 0/2] kconfig: fix multi-byte UTF handling in nconfig
Date: Fri, 6 Jun 2014 15:17:49 +0200 [thread overview]
Message-ID: <20140606131748.GC4889@ravnborg.org> (raw)
In-Reply-To: <1401868351-24014-1-git-send-email-computersforpeace@gmail.com>
On Wed, Jun 04, 2014 at 12:52:29AM -0700, Brian Norris wrote:
> Hi,
>
> The first patch is trivial.
>
> The second is inspired by a long-standing bugzilla entry:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=43067
>
> The MTD_NAND_CAFE Kconfig symbol (drivers/mtd/nand/Kconfig) has description
> text which uses a multi-byte UTF-8 character: the 'É' in 'CAFÉ'. This
> character (and other similar >8bit UTF-8 characters) is not handled
> correctly by many of the kernel configuration tools (notably 'make nconfig'
> and 'make xconfig'). nconfig was especially broken, as it would completely
> drop any menu entry which had non-ASCII characters, as well as ALL
> subsequent entries in the same window (!!).
Thanks for fixing this.
Sam
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
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 [this message]
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=20140606131748.GC4889@ravnborg.org \
--to=sam@ravnborg.org \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--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.