The Thai Baht (฿) has always been the most frequently used Bitcoin symbol right?

[Hasimir]

Have you successfully rendered this symbol on a system using UTF-8?

Yep, in fact I'm pretty sure these forums use UTF-8 only.

Edit: Actually, looking at the source, I see the forum is choosing ISO-8859-1 encoding, which doesn't work with Unicode at all. This is likely the reason why many people are having technical problems.

If that's the case then the Bitcoin wiki has the same problem.

No, the wiki seems to select UTF-8 properly.

We've already established from the numerous responses to you earlier in this thread that you're one of the exceptions who can see this symbol, you're not in the majority.  Not by a long stretch.

I expect (and intend) to use a symbol which will display on the widest range of hardware and software available globally.  This means taking into account older systems and operating systems.

So as much as you may wish it weren't so, both ฿ and Ƀ still have an edge.

[1714249369]

1714249369

[1714249369]

1714249369

[bg002h]

Have you successfully rendered this symbol on a system using UTF-8?

Yep, in fact I'm pretty sure these forums use UTF-8 only.

Edit: Actually, looking at the source, I see the forum is choosing ISO-8859-1 encoding, which doesn't work with Unicode at all. This is likely the reason why many people are having technical problems.

If that's the case then the Bitcoin wiki has the same problem.

No, the wiki seems to select UTF-8 properly.

We've already established from the numerous responses to you earlier in this thread that you're one of the exceptions who can see this symbol, you're not in the majority.  Not by a long stretch.

I expect (and intend) to use a symbol which will display on the widest range of hardware and software available globally.  This means taking into account older systems and operating systems.

So as much as you may wish it weren't so, both ฿ and Ƀ still have an edge.

It would be nice to have an educated, well thought out, and reasonable estimate of the amount of time it would take for a large fraction of users to have the BTC symbol work (and for someone to fill in all the assumptions with reasonable guesses)...

[Hasimir]

i guess it's a function of the OS more than the broswer then?

Very likely.  Which means it will be years before Luke-Jr will be satisfied.

What I'd like to know is whether an OLPC system will display this alleged "standard" symbol.

[bg002h]

i guess it's a function of the OS more than the broswer then?

Very likely.  Which means it will be years before Luke-Jr will be satisfied.

What I'd like to know is whether an OLPC system will display this alleged "standard" symbol.

I sold my iPhone 4s when I ordered the iPhone 5...and got a temp junk phone for the interim...I should see how it renders the test site...it's a modern "pre-iphone" phone with keyboard and what not...lol!

[Hasimir]

It would be nice to have an educated, well thought out, and reasonable estimate of the amount of time it would take for a large fraction of users to have the BTC symbol work (and for someone to fill in all the assumptions with reasonable guesses)...

There's no way of avoiding years of time and effort.  It's either a system related issue of failing to implement existing UTF-8 to get the double symbol to work or needs a single symbol (with both strokes) added to Unicode.  Either way we'll be waiting years before 80-90% have moved on to systems which will support it.

The alternative is to use ฿, Ƀ, ¤ or some other symbol until a consistently displaying independent symbol is available to everyone without relying on the web or customisations.  As much as Luke-Jr rails against it, this is exactly what will happen.

[Luke-Jr]

OS X 10.5.8

So, an OS that is now 5 years old and beyond end of life (no more security fixes). You shouldn't even be allowed online with that.

[Hasimir]

OS X 10.5.8

So, an OS that is now 5 years old and beyond end of life (no more security fixes). You shouldn't even be allowed online with that.

There are plenty of older systems around, if you really want to enforce your ideal OS standard then I'll believe it when you turn up on my doorstep.  I'm easy to find.

[Luke-Jr]

OS X 10.5.8

So, an OS that is now 5 years old and beyond end of life (no more security fixes). You shouldn't even be allowed online with that.

There are plenty of older systems around, if you really want to enforce your ideal OS standard then I'll believe it when you turn up on my doorstep.  I'm easy to find.

At the very least, it's grounds for automatic ignoring complaints about standard things not working for you. The bugs were already fixed, you're just using a known-buggy version.

[Hasimir]

OS X 10.5.8

So, an OS that is now 5 years old and beyond end of life (no more security fixes). You shouldn't even be allowed online with that.

There are plenty of older systems around, if you really want to enforce your ideal OS standard then I'll believe it when you turn up on my doorstep.  I'm easy to find.

At the very least, it's grounds for automatic ignoring complaints about standard things not working for you. The bugs were already fixed, you're just using a known-buggy version.

And how do you respond to people using Ubuntu 12.04 encountering the same problem?  Or other Windows users who reported the same thing?  It's not just me, remember.

[greyhawk]

I made a test page for the BTC symbol in Unicode since this forum forces a non-Unicode encoding.

Windows 7 Home Premium SP1 (64 Bit) with all updates, even optional ones.

Google Chrome 22.0.1229.79 m




On my Gnex, it's a bunch of normal B's.

Android 4.1.1 (Jelly Bean) / unrooted
Baseband:  I9250XXLF1
Kernel:  3.0.31-g6fb96c9
android-build@vpbs1 )
#1 SMP PREEMPT Thu Jun 28 11:02:39 PDT 2012

Chrome 18.0.1025308

[FLHippy]

OS X 10.5.8

So, an OS that is now 5 years old and beyond end of life (no more security fixes). You shouldn't even be allowed online with that.

There are plenty of older systems around, if you really want to enforce your ideal OS standard then I'll believe it when you turn up on my doorstep.  I'm easy to find.

At the very least, it's grounds for automatic ignoring complaints about standard things not working for you. The bugs were already fixed, you're just using a known-buggy version.

If this is truly a serious discussion about adopting a standard symbol.... whatever is picked should display on the least advanced media..

like a green screen WYSE terminal. Vt100 terminal, etc.

Or a piece of paper.

Suggesting that people who aren't upgraded to the latest version of something should be discounted is really elitist.

[dree12]

B⃦ sucks extra hard for being 2 chars (we invented new problems for you!)

B⃦ is itself a single character, even if comprised of two codepoints.
It's also the same character the forum is using a webfont to render in BTC.
Using multiple codepoints for a single character is not new.

How many times do you need to see posts from others saying (and even showing) that it isn't displaying for the majority of people as it does for you?

Such problems are irrelevant. I'm not suggesting changing anything.

Are you using UTF-16 instead of UTF-8?

No, I only use UTF-8.

Have you successfully rendered this symbol on a system using UTF-8?

Yep, in fact I'm pretty sure these forums use UTF-8 only.

Edit: Actually, looking at the source, I see the forum is choosing ISO-8859-1 encoding, which doesn't work with Unicode at all. This is likely the reason why many people are having technical problems.

No, it's not. The forum encodes the text in ISO-8859-1 encoding, which is the standard for all webpages and has full support of all languages. The only deficiency in ISO-8859-1 is that unicode characters cannot be sent directly, which is not what the forum does. It, correctly, encodes all non-codepage characters with HTML entities, which is the standard method of unicode encoding today and is universally used.

Your test page accomplishes even less support than this forum, because some browsers choose to ignore encodings in the HTTP header and detect it themselves.

[nimda]

What about mobile browsers? They represent a growing portion of the market, and some of these symbols don't even show up on the Galaxy S3.

[dree12]

What about mobile browsers? They represent a growing portion of the market, and some of these symbols don't even show up on the Galaxy S3.

Then use BTC, inline images, or webfonts. I'm not supporting usage of the proper unicode symbol, unlike Luke, but rather discontinuation of usage of the Baht symbol.

[Hasimir]

I made a test page for the BTC symbol in Unicode since this forum forces a non-Unicode encoding.

Windows 7 Home Premium SP1 (64 Bit) with all updates, even optional ones.

Google Chrome 22.0.1229.79 m

I got the same on my Nokia N9 running MeeGo 1.2 Harmattan version PR1.3 (the current version) using the current version of Opera Mobile.

The same thing appears with Amaya.

[Luke-Jr]

Or a piece of paper.

There shouldn't be any problems writing/reading it on paper...

Suggesting that people who aren't upgraded to the latest version of something should be discounted is really elitist.

I didn't say that. His version is so old that it isn't even patched against known security vulnerabilities. It's like driving a car with known-bad brakes.

[FLHippy]

Suggesting that people who aren't upgraded to the latest version of something should be discounted is really elitist.

I didn't say that. His version is so old that it isn't even patched against known security vulnerabilities. It's like driving a car with known-bad brakes.

It came off that way. Especially when combined with the suggested ban of old operating systems from the internet

FWIW... I am upgraded to the latest version of OS X and safari and the two character double vertical line thing looks like crap on my browser also. The lines are shifted to the right as shown by others. All of the samples on the luke-jr test page kind of look like a hacked B in one way or another. (which is what they are)

The BTC conversion to the image looks good where supported and requires no mandatory support by those who don't wish to support it. It will look good and be understood on everything from a typewriter to a web browser.

[dree12]

Suggesting that people who aren't upgraded to the latest version of something should be discounted is really elitist.

I didn't say that. His version is so old that it isn't even patched against known security vulnerabilities. It's like driving a car with known-bad brakes.

It came off that way. Especially when combined with the suggested ban of old operating systems from the internet

FWIW... I am upgraded to the latest version of OS X and safari and the two character double vertical line thing looks like crap on my browser also. The lines are shifted to the right as shown by others. All of the samples on the luke-jr test page kind of look like a hacked B in one way or another. (which is what they are)

The BTC conversion to the image looks good where supported and requires no mandatory support by those who don't wish to support it. It will look good and be understood on everything from a typewriter to a web browser.

On a typewriter, one can write B, go back, and write the double bar.

By the way, the "B-Box" looks perfect on my computer. Ubuntu 12.04.

[Blind]

Luke, did you get giant BTC tatooed on your butt that you defend it so religiously?

[giszmo]

Luke -- here's how it renders on Mountain Lion / chrome:

pfft! oh my god! coffee everywhere