From: Bastien Nocera <hadess@hadess.net>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] non-ASCII chars in device names
Date: Wed, 07 Mar 2007 00:27:13 +0000 [thread overview]
Message-ID: <1173227233.10237.44.camel@cookie.hadess.net> (raw)
Heya,
I got this report for gnome-bluetooth some time ago:
http://bugzilla.gnome.org/show_bug.cgi?id=380408
I fixed the problem altogether by replacing this code by D-Bus code
calling hcid. The problem is that the name of the device only shows up
the very first time the device is discovered, and it seems to me that
the cache is busted:
In hcid/storage.c:
for (i = 0; i < 248 && name[i]; i++)
if ((unsigned char) name[i] < 32 || name[i] == 127)
str[i] = '.';
else
str[i] = name[i];
Why? If the data is correct UTF-8, it could be saved as-is in the file,
minus any tabs, unbreakable spaces, or line feeds.
--
Bastien Nocera <hadess@hadess.net>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2007-03-07 0:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 0:27 Bastien Nocera [this message]
2007-03-07 11:34 ` [Bluez-devel] non-ASCII chars in device names Marcel Holtmann
2007-03-07 13:05 ` Bastien Nocera
2007-03-07 3:31 ` Johan Hedberg
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=1173227233.10237.44.camel@cookie.hadess.net \
--to=hadess@hadess.net \
--cc=bluez-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).