From: Michael Terry <michael.terry@ubuntu.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Support translations in bluez-utils
Date: Wed, 21 May 2008 10:38:24 -0400 [thread overview]
Message-ID: <1211380704.5826.22.camel@bongo> (raw)
In-Reply-To: <1211380276.13248.61.camel@californication>
[-- Attachment #1.1: Type: text/plain, Size: 556 bytes --]
On Wed, 2008-05-21 at 16:31 +0200, Marcel Holtmann wrote:
> actually this is going away in the near future. The logic to provide a
> service friendly name will be done in bluez-gnome and the bluez-utils
> will only export a service identifier.
Aha. Good.
> In addition I also think that translation for system level functionality
> is useless :)
Well, these strings were being presented to the user, so it's just as
useful as any other translation, eh? But if the strings are moving to
bluez-gnome, that's just as good.
Thanks,
-mt
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 230 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-05-21 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 12:57 [Bluez-devel] [PATCH] Support translations in bluez-utils Michael Terry
2008-05-21 14:31 ` Marcel Holtmann
2008-05-21 14:38 ` Michael Terry [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=1211380704.5826.22.camel@bongo \
--to=michael.terry@ubuntu.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 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.