Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

currency symbol


bagman

Recommended Posts

Posted

I am having a problem with displaying a pound sign on my front page. This is used to give an indication of postage but I keep getting a "£1" symbol...does anyone have any ideas as I have just spent nearly two hours searching the forums for an answer.

 

thanx in advance

Posted

I don't have any problems seeing a £ sign, it is displayed correctly.

Upon receiving fixes and advice, too many people don't bother to post updates informing the forum of how it went. Until of course they need help again on other issues and they come running back!

 

Why receive the information you require in good faith for free, only to then have the attitude to ignore the people who gave it to you?

 

There's no harm in saying, 'Thanks, it worked'. On the contrary, it creates a better atmosphere.

 

CHOOCH

Posted

try using the unicode for pound, which is &_pound_; (remove the underscores, i have to put them there, or the forum software will actually print the symbol you want.)

 

in general, it is good coding practice (imho) to use unicode entities for all such symbols.

 

cheers,

rj

 

ps: google search: unicode pound sign

Posted

Excellent........cant thank you enough been trying to sort that for weeks, have tried unicode but must have been doing something wrong!

 

Can now get on in peace and happiness with one less niggly bit to stress about

 

Again...many thanx

 

Nigel

  • 9 months later...
Posted
in which file / files does this ammendment need to be made?

 

(I too have the same problem on a store migrating to our servers)

Do it in admin localisation currencies.

Posted

I advise against using unicode characters, for the simple reason that it will ouput in some features of osCommerce as unicode and not as a £ sign.

 

With a new website there is no reason why you should have a problem with the £ sign. It's on existing sites moving from one server to another that the problem occurs - and that's because of a difference in the MySQL Character Set Collation. On modern servers its utf8 whilst on older servers its Latin 1, or iso-8859-1 (which is the same as Latin 1).

 

All you need do in this instance is, when importing an existing database into phpMyAdmin, select Latin 1 for the Import in place of utf8 and the £ sign will carry over correctly - both for the currencies table and the Orders Total table.

 

Vger

Posted
I advise against using unicode characters, for the simple reason that it will ouput in some features of osCommerce as unicode and not as a £ sign.

 

With a new website there is no reason why you should have a problem with the £ sign. It's on existing sites moving from one server to another that the problem occurs - and that's because of a difference in the MySQL Character Set Collation. On modern servers its utf8 whilst on older servers its Latin 1, or iso-8859-1 (which is the same as Latin 1).

 

All you need do in this instance is, when importing an existing database into phpMyAdmin, select Latin 1 for the Import in place of utf8 and the £ sign will carry over correctly - both for the currencies table and the Orders Total table.

 

Vger

 

That will only work if the end-user's encoding is also Latin 1 - much better to use the HTML &-pound-; as previously suggested here and other places - that way it will always show as the pound sign regadless of the end-user's default encoding. I discovered all this years ago, as I run multi-language systems and unless you use the HTML version, it will show whichever character is mapped to that position within the user's language set.

 

For example, if the end-user encoding is Thai, you will get the "Khor" letter - the only way to get it to correctly display the pound sign regardless of end-user language encoding is to use the HTML &_pound_; entity.

* * * * * * * * * * * * * * * * * * * * *

Porpoises are most happy when wet!

\ _ \ _ \ _ \ _ \ _ \ _ \ _ \ _ \ _ \ _ \ _ \ _

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...