Catalogue font properties incorrect.

[smold]

Currently my catalogue is displaying the incorrect fonts, if you look at the following page for example:

http://www.mookey.com/acatalog/Onlin...ewall_198.html

The fonts seem to be New Times Roman instead of the correct font, within the page preview in Actinic they are displayed correctly.

This issue maybe related to one of my previous posts:

http://community.actinic.com/showthread.php?t=13341

Any ideas?

Thanks

[EaglesNest]

Currently my catalogue is displaying the incorrect fonts, if you look at the following page for example:

http://www.mookey.com/acatalog/Onlin...ewall_198.html

The fonts seem to be New Times Roman instead of the correct font, within the page preview in Actinic they are displayed correctly.

This issue maybe related to one of my previous posts:

http://community.actinic.com/showthread.php?t=13341

Any ideas?

Thanks

Steve,

I just looked at the page and the fonts seem to be displaying as Arial to me, what are they supposed to be?

Eagle

[DaveT]

The font is Verdana on my page. There's no Arial or TNR as far as I can see.

[webyourbusiness]

I see verdana in both IE and Firefox.

It's a css site, so if your fonts mess up, it likely to be a problem with the css file - either it's got a problem, or it fails to be sent/requested by the browser.

In theory, if you begin clicking around in the page before it's finished, you can stop the css file from loading... I've not seen it happen in a while, but our connection is super fast - it's a more likely situation if using a dialup though.

one thing to check is your CSS file using the w3 css validator (jigsaw):

http://jigsaw.w3.org/css-validator/

if you css file has "errors" - you can expect some problems at SOME point...

[EaglesNest]

The font is Verdana on my page. There's no Arial or TNR as far as I can see.

You are right, Verdana is what I am seeing too. I always get those two mixed up. Definitely not TNR though...

Eagle

[smold]

Thanks!

I send all my catalogue back up including 'files' and it seems to have corrected the problem.

Thanks everybody for having a look

Steve

[retekdirect]

Can i just add something i find very handy:

When updating pages, and in particular CSS files (which are occasionally a bit temperamental when updating), ensure you reload the files to view the newest version (replacing the cache). Sometimes the new versions won't be loaded automatically.

In Firefox and IE, force a reload with Ctrl+F5.