Then there is something wrong with your system. Here on my standard Windows 7 64bit with 8GB RAM it displays just fine.

(Ok, seriously, are you talking about this: BTC? So either it should load the Webfont resulting in BTC being displayed as "B with decoration", "invisible T", "invisible C" or your w3c/lynx on a non-unicode console should just display BTC … or your smart browser decides that there is something wrong with letters that have zero width so it defaults to another font. Which browser are you using?)

Konqueror displays ฿ and Ƀ right but I have the same problem with BTC. Interesting. For me, it's really narrowing down to either ฿ or Ƀ then.

Sounds like your browser is ignoring parts of my webfont, likely in violation of standards.

Anyone know how to fix this?

I see...so it will require two codes to generate...in time I suppose the implementation will catch up with the spec. I get Bbox on my iPad on iOS 6.

I'm not talking about countries getting into legal trouble... how does that even work? I mean "OMG you scammer, I obviously meant Nicaraguan córdoba!". Imagine people in Thailand start using BTC!

We're not damned imposters of anything else. There's no reason to use that other than it looking "familiar", which I also find wrong for Bitcoin. It's a stupid choice, and it doesn't need a great analyst to see that.



Ƀ really doesn't look like a bad choice. I never liked the color scheme people advertise with it, but the symbol seems perfect.

I like it too, and about the criticism that it looks almost like the number 8, maybe serifs should be added, like:

Ligatures would, and they would fix the copying problem too (hint, hint).

Except not every implementation of Unicode displays whatever symbol that is.

In Firefox 15 on OS X Leopard I see the letter B followed by "20E6" for a Unicode symbol that won't display (Combining Double Vertical Stroke Overlay).  In Emacs I see B followed by a different symbol (Both Firefox and Emacs are configured to use UTF-8 on my system).

The problem is that you've opted for a UTF-16 character instead of a UTF-8 character.  UTF-8 is far more common and accessible.  This is why, like shamoons, I argued in favour of using the Thai Baht symbol last year.

The only argument against using ฿ is that it is used for THB aleady.  On the other hand $ is already used for USD, CAD, AUD and NZD.  While ¥ is used for Yen and Yuan.  Currencies sharing symbols is nothing new, that's why we have three letter codes for them as well.

Once again, I don't see any problem with using the baht symbol for Bitcoin and it has the added advantage of displaying correctly on a wide range of systems.

This was debated in detail last year and my post in that thread (which included a couple of other suggestions in addition the the baht) is here.  My opinion in my first paragraph hasn't changed:  I think that the symbol ought to be an existing UTF-8 symbol so that it can be readily used on most systems or browsers and not require additional fonts to be installed.

BTW, there's a poll in that thread from last year which was resoundingly in favour of using the baht symbol.

Which is fine if everything you do is on the web, but not everything is and it should not have to be.

How long until implementations work for most people? 1 year, 5 years, a decade?