From: Neal Peacock <neal@coinfree.com>
To: linux-bluetooth@vger.kernel.org
Subject: UTF8 to UTF-8 name patch for obexd
Date: Fri, 29 Jun 2012 18:31:59 -0400 [thread overview]
Message-ID: <4FEE2CDF.7030806@coinfree.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]
My first post here so I hope I am doing this the right way.
This is a short patch for obexd to change the charset name passed into
glib from UTF8 to UTF-8, which I think is the proper name. I was
working on an embedded system that didn't have the aliases setup to
convert the names like typical desktops. I was pulling my hair out
trying to figure out how to add the charsets in glib until I realized I
could just change the name in obexd and UTF-8 seems to be universally
included unlike UTF8.
Thanks.
--
Neal Peacock
[-- Attachment #2: fix-UTFName.patch --]
[-- Type: text/plain, Size: 751 bytes --]
>From abe899bbdeac414610970cdcad31dc2d02463085 Mon Sep 17 00:00:00 2001
From: Neal Peacock <neal@coinfree.com>
Date: Fri, 29 Jun 2012 18:15:57 -0400
Subject: [PATCH] Changed UTF name to standard
---
| 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
--git a/gobex/gobex-header.c b/gobex/gobex-header.c
index 77dcc6e..56dd9b2 100644
--- a/gobex/gobex-header.c
+++ b/gobex/gobex-header.c
@@ -187,7 +187,7 @@ GObexHeader *g_obex_header_decode(const void *data, gsize len,
}
header->v.string = g_convert((const char *) ptr, hdr_len - 5,
- "UTF8", "UTF16BE",
+ "UTF-8", "UTF-16BE",
NULL, &str_len, &conv_err);
if (header->v.string == NULL) {
g_set_error(err, G_OBEX_ERROR,
--
1.7.2.5
next reply other threads:[~2012-06-29 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 22:31 Neal Peacock [this message]
2012-06-30 11:53 ` UTF8 to UTF-8 name patch for obexd 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=4FEE2CDF.7030806@coinfree.com \
--to=neal@coinfree.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 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.