Many, many years ago, I loaded an extra font, Dom Casual, onto one of my previous computers. Every time I've upgraded, I've loaded it onto the new machine.
I've had no problems whatsoever with using and seeing it, till the latest version of Firefox came along. Previous Firefox versions were okay. The latest version completely ignores the fact the font's on the machine, and in the correct location.
Anything supposed to be in Dom Casual comes out in the Firefox default font, Arial I think.
I've looked in the various Firefox fora and can find lots of references to this problem, but unless I'm going blind again, no sign of a solution that works.
There are lots of references to changing various settings, which I've done, but it still comes out in the Firefox default.
Knowing that many of you must have lots of extra fonts loaded, I'm wondering if anyone here has the definitive solution to this one?
Question for you Firefox People
- Nick Harvey
- God
- Posts: 4160
- Joined: Fri 15 Aug, 2003 22.26
- Location: Deepest Wiltshire
- Contact:
-
- Posts: 1447
- Joined: Sat 08 Nov, 2008 19.48
It might be a problem with the Arial font itself, if this Yahoo! Answers answer is right.Nick Harvey wrote:Many, many years ago, I loaded an extra font, Dom Casual, onto one of my previous computers. Every time I've upgraded, I've loaded it onto the new machine.
I've had no problems whatsoever with using and seeing it, till the latest version of Firefox came along. Previous Firefox versions were okay. The latest version completely ignores the fact the font's on the machine, and in the correct location.
Anything supposed to be in Dom Casual comes out in the Firefox default font, Arial I think.
I've looked in the various Firefox fora and can find lots of references to this problem, but unless I'm going blind again, no sign of a solution that works.
There are lots of references to changing various settings, which I've done, but it still comes out in the Firefox default.
Knowing that many of you must have lots of extra fonts loaded, I'm wondering if anyone here has the definitive solution to this one?
- Nick Harvey
- God
- Posts: 4160
- Joined: Fri 15 Aug, 2003 22.26
- Location: Deepest Wiltshire
- Contact:
Thanks for the try, but that's one I'd looked at and it's not the problem.
-
- Posts: 1447
- Joined: Sat 08 Nov, 2008 19.48
- Nick Harvey
- God
- Posts: 4160
- Joined: Fri 15 Aug, 2003 22.26
- Location: Deepest Wiltshire
- Contact:
It's a .ttf, which as I understand it, ought to be okay.
-
- Posts: 1447
- Joined: Sat 08 Nov, 2008 19.48
- Nick Harvey
- God
- Posts: 4160
- Joined: Fri 15 Aug, 2003 22.26
- Location: Deepest Wiltshire
- Contact:
Set in a number of web pages.
-
- Posts: 1447
- Joined: Sat 08 Nov, 2008 19.48
- Nick Harvey
- God
- Posts: 4160
- Joined: Fri 15 Aug, 2003 22.26
- Location: Deepest Wiltshire
- Contact:
This isn't an old problem, it's only started happening in the latest version, 3.6.12. All the previous versions displayed the page perfectly correctly.
It's a change they've introduced in 3.6.12 which has suddenly caused the problem.
It's a change they've introduced in 3.6.12 which has suddenly caused the problem.
-
- Posts: 1447
- Joined: Sat 08 Nov, 2008 19.48
Looking at Mozilla's site, the only changes are a security issue, and a problem with frames. Did you upgrade from 3.6.11? Also, have you got a link to the page?Nick Harvey wrote:This isn't an old problem, it's only started happening in the latest version, 3.6.12. All the previous versions displayed the page perfectly correctly.
It's a change they've introduced in 3.6.12 which has suddenly caused the problem.