From: Pierre-Yves Paulus <py@idlum.be>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Accented characters in friendly name properly handled in BlueZ?
Date: Mon, 08 Jan 2007 19:50:37 +0100 [thread overview]
Message-ID: <45A2927D.2030501@idlum.be> (raw)
In-Reply-To: <20070108183907.GA12105@jh-mbp>
Hi Johan,
> On Mon, Jan 08, 2007, Pierre-Yves Paulus wrote:
>> I'm using the D-Bus API to get the friendly name of a terminal wich name
>> contains accented chars. In the String I get, each accented character
>> (eg not a 1-byte ASCII char) gets replaced by 2 chars, each with value 0x2e.
>>
>> Is the problem coming from BlueZ or from the D-Bus bindings layer? Where
>> should I look to get a clue?
>
> It's a bug in the validation code responsible for storing the
> friendly name. It has been fixed in the 3.8 release.
Thanks for the fast answer. I will upgrade soon then (am currently using
3.7).
Best Regards,
Pierre-Yves
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2007-01-08 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 18:32 [Bluez-devel] Accented characters in friendly name properly handled in BlueZ? Pierre-Yves Paulus
2007-01-08 18:39 ` Johan Hedberg
2007-01-08 18:50 ` Pierre-Yves Paulus [this message]
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=45A2927D.2030501@idlum.be \
--to=py@idlum.be \
--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 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.