For every occurrence of the pound symbol (£) in my store, I am instead seeing a '?' question mark symbol in a black diamond. Googling has resulted in suggestions of charset - mine is set as utf-8 as below...
<meta http-equiv="content-type" content="text/html;charset=utf-8" />
I believe the store was origonally set up in Os commerce. In the currencies table I have used the ascii code of $pound; instead of the £ symbol but again this seems to have no affect.
Any suggestions would be great
Cheers
The problem with using
or
in osCommerce is that plain text emails won't show the pound symbol and just show the codes above.
A work around is to use GBP or UK Pound in the 'symbol to the left' entry in Admin / Localization / Currencies. But osCommerce won't allow you to put a space after the GBP, to solve this use phpMyAdmin, enter the space after GBP in the table called currencies, in the column called symbol_left.
This gives me: GBP 9.40 in my store listings, and in my plain text emails.
Alternatively for '9.40 Pounds' ,apply the above method to 'symbol to the right' and 'symbol_right' adding a space before the value 'Pounds'
Can you not replace £ with
&pound;
(or&amp;pound;
in OS commerce)View to source code of the HTML markup and paste the result - OS commerce could be transforming it server-side which would mean adding the meta tag would be worthless.
We had a similar issue with websites (our own and one from other well established websites) where the pound (£) symbol showed as a letter J. We also noticed that at the same time the text was bold and oblique when it shouldn't have been.
After much investigation it turned out that much of the machines we came across had something wrong with the Helvetica font installed on the machines, and there are two possible solutions:
You can simply solve this problem by putting following line:
between
<head>
and</head>
tags of your html code.I recommend it should be placed immediately after
<head>
tag.I have tested it and it works.
Try using the HTML entity:
Not sure exactly where you're plugging it in, but that should do the trick for most situations if it allows HTML characters like that.