From: Denis KENZIOR <denis.kenzior@trolltech.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] PATCH: handle unicode local device name
Date: Fri, 17 Nov 2006 13:57:24 +1000 [thread overview]
Message-ID: <200611171357.25160.denis.kenzior@trolltech.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 107 bytes --]
Hey,
This patch fixes a problem with storage.c turning unicode local device names
into '.' dots.
-Denis
[-- Attachment #2: storage.patch --]
[-- Type: text/x-diff, Size: 733 bytes --]
Index: storage.c
===================================================================
RCS file: /cvsroot/bluez/utils/hcid/storage.c,v
retrieving revision 1.43
diff -u -5 -r1.43 storage.c
--- storage.c 27 Oct 2006 14:43:23 -0000 1.43
+++ storage.c 17 Nov 2006 03:53:12 -0000
@@ -119,11 +119,11 @@
char filename[PATH_MAX + 1], str[249];
int i;
memset(str, 0, sizeof(str));
for (i = 0; i < 248 && name[i]; i++)
- if ((unsigned char) name[i] < 32 || name[i] == 127)
+ if ((unsigned char) name[i] < 32)
str[i] = '.';
else
str[i] = name[i];
create_filename(filename, PATH_MAX, bdaddr, "config");
[-- Attachment #3: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
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
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-11-17 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 3:57 Denis KENZIOR [this message]
2006-11-17 10:10 ` [Bluez-devel] PATCH: handle unicode local device name Marcel Holtmann
2006-11-17 18:19 ` Albert Huang
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=200611171357.25160.denis.kenzior@trolltech.com \
--to=denis.kenzior@trolltech.com \
--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