Pages:
Author

Topic: The Thai Baht (฿) has always been the most frequently used Bitcoin symbol right? - page 4. (Read 30427 times)

member
Activity: 98
Merit: 10
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.
legendary
Activity: 2576
Merit: 1186
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.
member
Activity: 98
Merit: 10
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.
legendary
Activity: 2576
Merit: 1186
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.
member
Activity: 98
Merit: 10
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.
donator
Activity: 1464
Merit: 1047
I outlived my lifetime membership:)
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!
member
Activity: 98
Merit: 10
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.
donator
Activity: 1464
Merit: 1047
I outlived my lifetime membership:)
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)...
member
Activity: 98
Merit: 10
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.
donator
Activity: 1464
Merit: 1047
I outlived my lifetime membership:)
i guess it's a function of the OS more than the broswer then?
member
Activity: 98
Merit: 10

OS X 10.5.8 and Firefox 15.  Seamonkey produced the same result.

Safari, on the other hand, produced this:



I included the top of the browser which shows a different symbol.  That symbol matches what Emacs produces.
donator
Activity: 1464
Merit: 1047
I outlived my lifetime membership:)
member
Activity: 98
Merit: 10
legendary
Activity: 2576
Merit: 1186
Luke -- here's how it renders on Mountain Lion / chrome:

Looks pretty good - except for bold and italic. Wonder why those are messed up for you.

Are you using UTF-16 instead of UTF-8?
No, I only use UTF-8.
Which version?
RFC 3629

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.
donator
Activity: 1464
Merit: 1047
I outlived my lifetime membership:)
looks the same on safari and chrome on mountain lion.
member
Activity: 98
Merit: 10
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.

It's hardly irrelevant if people can't see what you mean to show them.

Are you using UTF-16 instead of UTF-8?
No, I only use UTF-8.

Which version?

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.

Have you viewed this symbol on any system other than your own?
Yep, just pulled it up on a Mac I have lying around and it rendered fine in Lion/Safari.

Well, on mine it gives me trouble on Firefox, Seamonkey and Safari.

A standard that does not work consistently across multiple platforms doesn't really meet the definition of standard.
legendary
Activity: 2576
Merit: 1186
My system supports Unicode 5.0 or 5.1 with UTF-8 and all my programs are configured to use UTF-8, I can assure you your pet favourite isn't displaying properly.
Obviously not then, at least if you tested with my test page (since the forums don't support Unicode properly). Unicode 5.0 chapter 3 ("Conformance") definitely covers combining characters.
donator
Activity: 1464
Merit: 1047
I outlived my lifetime membership:)
Luke -- here's how it renders on Mountain Lion / chrome:
member
Activity: 98
Merit: 10
My vote is for the Thai Baht. It's clean, elegant and standard.
This isn't a vote; B⃦ has been the standard symbol since the beginning, and there is no good reason to change that. This is just Atlas trying to turn Bitcoin into mere "Silk Road currency".

Except not every implementation of Unicode displays whatever symbol that is.
If they don't, it's a bug.

If so then it's a bug that affects the majority of systems, programs and users, not to mention the wider world.

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.
B⃦ is standard UTF-8, it is not UTF-16.

My system supports Unicode 5.0 or 5.1 with UTF-8 and all my programs are configured to use UTF-8, I can assure you your pet favourite isn't displaying properly.

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.
I'm not addressing whether baht is an acceptable replacement or not; just the reality that it isn't the current standard BTC symbol.

Then the current standard is a woeful choice for one.

I'm throwing my support behind either ฿ or Ƀ.
legendary
Activity: 2576
Merit: 1186
I made a test page for the BTC symbol in Unicode since this forum forces a non-Unicode encoding.
Pages:
Jump to: