View Full Version : Currency symbols dont render in Firefox

04-20-2007, 11:31 PM
I'm using Firefox with a Mac G4 iBook, running System X.4.8. The British pound and euro symbols are not being rendered correctly.

I have tried various fonts, I have tinkered with the character encoding (its set to Western currently), I've adjusted the language preferences all different ways, and still the pound is rendered as an "i" with an acute accent over it, and the euro is rendered as a "u" with an acute accent.

I know this is not a system wide problem, as both Safari and Opera translate the character codes of € and £ correctly. But no matter what I do to the options and prefs of Firefox, I cant get it to correctly render them.

In my user group many folk use Firefox with various Macs running System x.4 and nobody but me reports this problem. What on earth have I overlooked to set correctly?

04-21-2007, 01:35 AM
Are you using the correct code?
Lets see what you are using. I see the symbols fine.

04-21-2007, 09:00 AM
&#163; and € pound and Euro <br>
&#165; and ™ yen and Trademark <br>
&#167; and ∑ section sign and sum <br>
&#169; and &#250; copyright and u with acute accent <br>

The pound and Euro print as &#237; and &#250; respectively.
The yen prints correctly, but the Trademark prints as something else.
The section sign doesnt print the section sign but sum prints Sum.
Copyright prints okay. and &#250; prints the same as the Euro.

These are only a sample of Firefox mis-behaviour. I didnt go through the entire list of characters.

04-21-2007, 09:03 AM
P.S. I see them fine as well when I view this thread with Safari or Opera. Its only Firefox (and earlier versions as well) with Mac where they are rendered incorrectly.

04-21-2007, 10:54 AM
Hi there jockm,

you could try posting your problem here...



04-21-2007, 05:14 PM

04-22-2007, 01:28 PM
Hm, could be the default text encoding of your Firefox? I think this can be set in the preferences somewhere. It displays fine here (Fx 2 too). Are you using the appropriate HTML entities?

&euro; = €
&pound; = £

04-22-2007, 01:47 PM
Yes, I am using the correct entities, and I already tried putting my problem up on the Firefox (Mozilla) help forum and got no joy.

I have tinkered with every possible preference I can think of with Firefox and nothing makes any difference whatsoever.

I think the next step is to delete ALL the preferences, options and other associated files that go with Firefox and see if Firefox recreates these in such a way that I can see the symbols like everyone else can see them with Firefox. Can somebody tell me what files I need to delete? Thanks!


04-22-2007, 04:36 PM
Have you got a test page up? Let us see your code.

04-24-2007, 03:24 PM
Please look at

The pound and euro are used extensively on this page, and are rendered by i and u with acute accents when I view the page with Firefox Macintosh.

The page is rendered correctly on my machine by any number of other browsers, including Safari and Opera.

I have just deleted Firefox and all its associated library files completely off my machine and re-installed it from a fresh download. And still the problem persists. And nobody seems to have any idea why since other Mac users also using System X.4 with Firefox dont seem to have the problem.


04-24-2007, 04:41 PM
The symbols show fine on IE7 and FF2 on my Vista box.
The validator does not like your encoding:
A fatal error occurred when attempting to transcode the character encoding of the document. Either we do not support this character encoding ("x-mac-roman") yet, or you have specified a non-existent character encoding (often a misspelling).

The error was: x-mac-roman undefined; replace by macintosh

If you believe the character encoding to be valid you can submit a request for that character encoding (see the feedback page for details) and we will look into supporting it in the future.

IANA maintains the list of official names for character sets and the WDG has some information to help you correctly specify the character encoding.

What happens when you change character encoding? Make the first few lines look like this:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

Sorry if this has been discussed already...

04-25-2007, 10:04 AM
No, your suggestion had not been discussed previously. So far nobody had suggested changing meta tags in a document or the initial declaration. I was very hopeful it might work, and implemented it.

Alas, no change. The euro and pound are still not showing, only u and i with acute accents over them.

I also tried changing &#163; (which is the euro equivalent) to &euro; but that also had no effect.

I'm completely baffled why my Firefox doesnt behave itself, whilst everyone elses seems to render these (and many other symbols) perfectly correctly.

04-25-2007, 10:05 AM
P.S. Maybe in UTF-8 the euro needs to be written completely differently from &euro; Anybody know?

04-25-2007, 12:11 PM
What about writing the unicode directly in the code

€ => & # 8 3 6 4 ;
£ => & # 1 6 3 ;

(remove the spaces b/w chars, I failed to post in true value)
just a suggestion, please ignore if its wrong...

04-26-2007, 03:00 PM
Maybe in UTF-8 the euro needs to be written completely differently from &euro; Anybody know?You can type those and virtually every other character directly into a document without the need for character entity references while using UTF‐8. Switching to UTF‐8 entails doing more than just altering the value of a meta element attribute value, however; you need to actually open the file in an editor and save it as a UTF‐8–encoded file. The meta element attribute’s value should then be changed to match the encoding that the document was saved under.

The current encoding that you’re using is indicated to be x-mac-roman. The “x-” indicates that it’s proprietary and the “mac” indicates that it’s proprietary to the Macintosh operating system. I would encode your documents using an encoding that isn’t proprietary to a single OS. It wouldn’t be surprising for a browser that doesn’t recognize a given encoding to incorrectly map characters.