From: Bastien Nocera <hadess@hadess.net>
To: Fabian Greffrath <fabian@greffrath.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: WRT non-UTF-8 device names
Date: Tue, 25 May 2010 13:38:39 +0100 [thread overview]
Message-ID: <1274791119.27274.17718.camel@localhost.localdomain> (raw)
In-Reply-To: <1274432516.4068.29.camel@vfrodo>
On Fri, 2010-05-21 at 11:01 +0200, Fabian Greffrath wrote:
> Dear Bluez list,
>
> I am experiencing the following issues with the bluez 4.63-2 and
> gnome-bluetooth 2.30.0-1 packages from Debian unstable:
Stupid question, but do you use a UTF-8 locale, or not?
The output of "locale" as root would probably help.
My guess is that we make assumptions as to a user entry being valid
UTF-8 somewhere, when it could be non-UTF-8.
As for your problem, I don't think we want to allow non-UTF-8 device
names anyhow. They're not valid spec.
next prev parent reply other threads:[~2010-05-25 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 9:01 WRT non-UTF-8 device names Fabian Greffrath
2010-05-25 11:35 ` Fabian Greffrath
2010-05-25 12:38 ` Bastien Nocera [this message]
2010-05-25 12:56 ` Fabian Greffrath
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=1274791119.27274.17718.camel@localhost.localdomain \
--to=hadess@hadess.net \
--cc=fabian@greffrath.com \
--cc=linux-bluetooth@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).