From: Peter Todd <pete@petertodd•org>
To: Ken Shirriff <ken.shirriff@gmail•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Proposal to add the bitcoin symbol to Unicode
Date: Sun, 6 Sep 2015 19:26:54 -0400 [thread overview]
Message-ID: <20150906232654.GF10728@muck> (raw)
In-Reply-To: <CALBHtZzHeDy-6Ar+DWUb8hFG4kJcg9+x4Y=TUEiQr3-rbgannw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
On Sat, Sep 05, 2015 at 07:11:27AM -0700, Ken Shirriff via bitcoin-dev wrote:
> Use of the bitcoin symbol in text is inconvenient, because the bitcoin
> symbol isn't in the Unicode standard. To fix this, I've written a proposal
> to have the common B-with-vertical-bars bitcoin symbol added to Unicode.
> I've successfully proposed a new character for Unicode before, so I'm
> familiar with the process and think this has a good chance of succeeding.
> The proposal is at http://righto.com/bitcoin-unicode.pdf
>
> I received a suggestion to run this proposal by the bitcoin-dev group, so I
> hope this email is appropriate here. Endorsement by Bitcoin developers will
> help the Unicode Committee realize the importance of adding this symbol, so
> please let me know if you support this proposal.
ACK
--
'peter'[:-1]@petertodd.org
000000000000000010f9e95aff6454fedb9d0a4b92a4108e9449c507936f9f18
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-09-06 23:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-05 14:11 Ken Shirriff
2015-09-05 14:26 ` Theo Chino
2015-09-05 14:58 ` Richard Moore
2015-09-05 18:48 ` Andreas Schildbach
2015-09-06 23:26 ` Peter Todd [this message]
2015-09-08 20:28 ` Danny Thorpe
2015-09-08 21:05 ` Ken Shirriff
[not found] ` <CAFh0iXOtc6H-NdP+D_tkizvqG0xWaYy-PGBuu2VTXPdX2O83qQ@mail.gmail.com>
2017-06-20 22:13 ` [bitcoin-dev] Fwd: " Theo Chino
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=20150906232654.GF10728@muck \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=ken.shirriff@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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