From: Artem Bityutskiy <dedekind1@gmail.com>
To: Martin Walch <walch.martin@web.de>
Cc: Scott Wood <scottwood@freescale.com>,
Wolfram Sang <wolfram@the-dreams.de>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: nand: Kconfig: drop utf8 characters
Date: Tue, 15 Jan 2013 12:40:00 +0200 [thread overview]
Message-ID: <1358246400.2731.123.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1568980.QkbR4hXzWB@tacticalops>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
On Mon, 2012-12-17 at 04:27 +0100, Martin Walch wrote:
>
> To make a long story short: multibyte characters in Kconfig files lead to
> undefined behaviour. This is no implementation bug. The configuration system
> just has not been designed for processing them. So utf-8 support can not be
> achieved with an easy fix, but will need comprehensive changes.
>
> I do not know if anyone is willing to actually make all the necessary work to
> properly support utf-8 in the configuration system. However, I suppose this
> will not happen any time soon. Therefore I suggest removing the multibyte
> characters for now.
Sure, thanks for a detailed analysis. What I agree with is removing
non-ASCII characters in case they cause a functional or build problems,
just because, as you said, fixing Kbuild is a big task.
However, in this particular case, this is just about user seeing rubbins
in the configuration menu, which is not a big deal, I think, so I would
prefer to rather expose the issue than fix it.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-15 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 23:07 [PATCH] mtd: nand: Kconfig: drop utf8 characters Wolfram Sang
2012-11-26 23:18 ` Scott Wood
2012-12-03 13:29 ` Artem Bityutskiy
2012-12-03 13:29 ` Wolfram Sang
2012-12-17 3:27 ` Martin Walch
2013-01-15 10:40 ` Artem Bityutskiy [this message]
2013-01-15 11:00 ` Artem Bityutskiy
2012-12-03 13:28 ` Artem Bityutskiy
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=1358246400.2731.123.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=scottwood@freescale.com \
--cc=walch.martin@web.de \
--cc=wolfram@the-dreams.de \
/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