1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <g.rowe.froot@gmail.com>) id 1WO5hp-0004BR-Uy
for bitcoin-development@lists.sourceforge.net;
Thu, 13 Mar 2014 13:29:53 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.128.170 as permitted sender)
client-ip=209.85.128.170; envelope-from=g.rowe.froot@gmail.com;
helo=mail-ve0-f170.google.com;
Received: from mail-ve0-f170.google.com ([209.85.128.170])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WO5ho-0006y4-DN
for bitcoin-development@lists.sourceforge.net;
Thu, 13 Mar 2014 13:29:53 +0000
Received: by mail-ve0-f170.google.com with SMTP id pa12so1073550veb.15
for <bitcoin-development@lists.sourceforge.net>;
Thu, 13 Mar 2014 06:29:47 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.52.11.100 with SMTP id p4mr72137vdb.52.1394717386902; Thu,
13 Mar 2014 06:29:46 -0700 (PDT)
Sender: g.rowe.froot@gmail.com
Received: by 10.220.251.65 with HTTP; Thu, 13 Mar 2014 06:29:46 -0700 (PDT)
In-Reply-To: <CAJHLa0OMcTCgGESi-F4jT2NA3FyCeMYbD_52j47t3keEYBfK8g@mail.gmail.com>
References: <CAKaEYhK4oXH3hB7uS3=AEkA6r0VB5OYyTua+LOP18rq+rYajHg@mail.gmail.com>
<52852C2D.9020103@gmail.com> <52853D8A.6010501@monetize.io>
<CAJHLa0M6CkoDbD6FFixf9-mmhug7DvehSWCJ+EHWVxUDuwNiBg@mail.gmail.com>
<EE02A310-8604-4811-B2D0-FC32C72C20F3@grabhive.com>
<CAJHLa0OMcTCgGESi-F4jT2NA3FyCeMYbD_52j47t3keEYBfK8g@mail.gmail.com>
Date: Thu, 13 Mar 2014 13:29:46 +0000
X-Google-Sender-Auth: MAMSUGbUFLC6m1lldYUEvW1_YOY
Message-ID: <CAKm8k+3J9Po4xQn9LhTQrnrGCvG36-kLCjWPX4kmd-c7h+LujA@mail.gmail.com>
From: Gary Rowe <g.rowe@froot.co.uk>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=20cf3030bfd568928c04f47cf25e
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(g.rowe.froot[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WO5ho-0006y4-DN
Subject: Re: [Bitcoin-development] moving the default display to mbtc
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 13 Mar 2014 13:29:54 -0000
--20cf3030bfd568928c04f47cf25e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
The MultiBit HD view is that this is a locale-sensitive presentation issue.
As a result we offer a simple configuration panel giving pretty much every
possible combination: icon, m+icon, =CE=BC+icon, BTC, mBTC, =CE=BCBTC, XB=
T,
mXBT, =CE=BCXBT, sat along
with settings for leading/trailing symbol, commas, spaces and points. This
allows anyone to customise to meet their own needs beyond the offered
default.
We apply the NIST guidelines for representation of SI unit symbols (i.e no
conversion to native language, no RTL giving icon+m etc).
Right now MultiBit HD is configured to use m+icon taken from the Font
Awesome icon set. However reading earlier posts it seems that =CE=BC+icon i=
s
more sensible.
Let us know what you'd like.
Links:
m+icon screenshot: http://imgur.com/a/WCDoG
Font Awesome icon: http://fortawesome.github.io/Font-Awesome/icon/btc/
NIST SI guidelines: http://physics.nist.gov/Pubs/SP811/sec07.html
On 13 March 2014 12:56, Jeff Garzik <jgarzik@bitpay.com> wrote:
> Resurrecting this topic. Bitcoin Wallet moved to mBTC several weeks
> ago, which was disappointing -- it sounded like the consensus was
> uBTC, and moving to uBTC later --which will happen-- may result in
> additional user confusion, thanks to yet another decimal place
> transition.
>
>
>
> On Sun, Nov 17, 2013 at 9:28 PM, Wendell <w@grabhive.com> wrote:
> > We're with uBTC too. Been waiting for the signal to do this, let's do i=
t
> right after the fee system is improved.
> >
> > -wendell
> >
> > grabhive.com | twitter.com/hivewallet | gpg: 6C0C9411
> >
> > On Nov 15, 2013, at 6:03 AM, Jeff Garzik wrote:
> >
> >> Go straight to uBTC. Humans and existing computer systems handle
> numbers to
> >> the left of the decimals just fine (HK Dollars, Yen). The opposite is
> >> untrue (QuickBooks really does not like 3+ decimal places).
> >
>
>
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>
>
> -------------------------------------------------------------------------=
-----
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and thei=
r
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--20cf3030bfd568928c04f47cf25e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">The MultiBit HD view is that this is a locale-sensitive pr=
esentation issue. As a result we offer a simple configuration panel giving =
pretty much every possible combination: icon, m+icon,=C2=A0<span style=3D"f=
ont-family:arial,sans-serif;font-size:12.800000190734863px">=C2=A0=CE=BC</s=
pan>+icon, BTC, mBTC,=C2=A0<span style=3D"font-family:arial,sans-serif;font=
-size:12.800000190734863px">=C2=A0=CE=BC</span>BTC, XBT, mXBT,=C2=A0<span s=
tyle=3D"font-family:arial,sans-serif;font-size:12.800000190734863px">=C2=A0=
=CE=BC</span>XBT,=C2=A0sat=C2=A0along with settings for leading/trailing sy=
mbol, commas, spaces and points. This allows anyone to customise to meet th=
eir own needs beyond the offered default.=C2=A0<div>
<br></div><div>We apply the NIST guidelines for representation of SI unit s=
ymbols (i.e no conversion to native language, no RTL giving icon+m etc).<di=
v><br></div><div>Right now MultiBit HD is configured to use m+icon taken fr=
om the Font Awesome icon set. However reading earlier posts it seems that<s=
pan style=3D"font-family:arial,sans-serif;font-size:12.800000190734863px">=
=C2=A0</span><span style=3D"font-family:arial,sans-serif;font-size:12.80000=
0190734863px">=CE=BC+icon is more sensible.=C2=A0</span></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:12.8000001907348=
63px"><br></span></div><div><span style=3D"font-family:arial,sans-serif;fon=
t-size:12.800000190734863px">Let us know what you'd like.</span></div><=
div>
<span style=3D"font-family:arial,sans-serif;font-size:12.800000190734863px"=
><br></span></div><div><span style=3D"font-family:arial,sans-serif;font-siz=
e:12.800000190734863px">Links:</span></div><div><span style=3D"font-family:=
arial,sans-serif;font-size:12.800000190734863px">m+icon screenshot:=C2=A0</=
span><font face=3D"arial, sans-serif"><a href=3D"http://imgur.com/a/WCDoG">=
http://imgur.com/a/WCDoG</a></font></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:12.8000001907348=
63px">Font Awesome icon:=C2=A0</span><a href=3D"http://fortawesome.github.i=
o/Font-Awesome/icon/btc/">http://fortawesome.github.io/Font-Awesome/icon/bt=
c/</a></div>
<div><span style=3D"font-family:arial,sans-serif">NIST SI guidelines:=C2=A0=
<a href=3D"http://physics.nist.gov/Pubs/SP811/sec07.html">http://physics.ni=
st.gov/Pubs/SP811/sec07.html</a></span><br></div></div></div><div class=3D"=
gmail_extra">
<br><br><div class=3D"gmail_quote">On 13 March 2014 12:56, Jeff Garzik <spa=
n dir=3D"ltr"><<a href=3D"mailto:jgarzik@bitpay.com" target=3D"_blank">j=
garzik@bitpay.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Resurrecting this topic. =C2=A0Bitcoin Wallet moved to mBTC several weeks<b=
r>
ago, which was disappointing -- it sounded like the consensus was<br>
uBTC, and moving to uBTC later --which will happen-- may result in<br>
additional user confusion, thanks to yet another decimal place<br>
transition.<br>
<div class=3D""><br>
<br>
<br>
On Sun, Nov 17, 2013 at 9:28 PM, Wendell <<a href=3D"mailto:w@grabhive.c=
om">w@grabhive.com</a>> wrote:<br>
> We're with uBTC too. Been waiting for the signal to do this, let&#=
39;s do it right after the fee system is improved.<br>
><br>
> -wendell<br>
><br>
> <a href=3D"http://grabhive.com" target=3D"_blank">grabhive.com</a> | <=
a href=3D"http://twitter.com/hivewallet" target=3D"_blank">twitter.com/hive=
wallet</a> | gpg: 6C0C9411<br>
><br>
> On Nov 15, 2013, at 6:03 AM, Jeff Garzik wrote:<br>
><br>
>> Go straight to uBTC. Humans and existing computer systems handle n=
umbers to<br>
>> the left of the decimals just fine (HK Dollars, Yen). The opposite=
is<br>
>> untrue (QuickBooks really does not like 3+ decimal places).<br>
><br>
<br>
<br>
<br>
--<br>
</div>Jeff Garzik<br>
Bitcoin core developer and open source evangelist<br>
BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.com/" target=3D"=
_blank">https://bitpay.com/</a><br>
<br>
---------------------------------------------------------------------------=
---<br>
Learn Graph Databases - Download FREE O'Reilly Book<br>
"Graph Databases" is the definitive new guide to graph databases =
and their<br>
applications. Written by three acclaimed leaders in the field,<br>
this first edition is now available. Download your free book today!<br>
<a href=3D"http://p.sf.net/sfu/13534_NeoTech" target=3D"_blank">http://p.sf=
.net/sfu/13534_NeoTech</a><br>
<div class=3D"HOEnZb"><div class=3D"h5">___________________________________=
____________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div>
--20cf3030bfd568928c04f47cf25e--
|
