I'm om FF 2.0.0.4 as well - can you confirm that tou see the ampersand
character styled in 'Gates & Railings' the same way on both the heading
and the menus ? I see different - with the menu being more stylised.
Hi Nick,
I think the issue may be that the tag is defaulting to different font
weig
007 2:04 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] H1 font not set in IE
Thanks to everyone who has sent suggestions. I have tried different
quotes, no quotes, reloading, etc, etc - but still no joy.
This just seems to be an issue on FF/Windows and the really weird thing
is that the font works
2:04 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] H1 font not set in IE
Thanks to everyone who has sent suggestions. I have tried different
quotes, no quotes, reloading, etc, etc - but still no joy.
This just seems to be an issue on FF/Windows and the really weird thing
is that the font
Thanks to everyone who has sent suggestions. I have tried different
quotes, no quotes, reloading, etc, etc - but still no joy.
This just seems to be an issue on FF/Windows and the really weird thing
is that the font works in one area of the page - the menus - but not for
the headings. The fo
Raena wrote:
No, either doubles or singles are correct.
http://www.w3.org/TR/REC-CSS1#font-family
Double quotes might be correct in the specs and for all browsers that
follow the specs including surprisingly IE6. Except for FF on windows, it
does not want to play by the rules it needs single q
On 7/18/07, Nick Cowie <[EMAIL PROTECTED]> wrote:
You do not need to wrap font names in quotes unless the have a space in
them and them you should use single quotes ie 'apple garamond'
No, either doubles or singles are correct.
http://www.w3.org/TR/REC-CSS1#font-family
--
Raena Jackson Ar
Nick
The odd results you are getting is because you are wrapping the fonts in
double quotes ie "garamond".
You do not need to wrap font names in quotes unless the have a space in them
and them you should use single quotes ie 'apple garamond'
Nick
*
On Tue, 17 Jul 2007 11:40:00 +0100, Nick Roper wrote:
> http://dev.logical.co.uk/castlewelding/final/gates_railings.php
>
> The font for the h1 should be Garamond - as it is for the menus at
> the left. However it refuses to render in FF/Windows - although it is
> fine on FF/Mac. The other weird
Hello Nick,
I'm using FF 2.0.0.4 in Windows 2000 and I see Garamond bold italic
for the h1, even after I smudge out the inline style with the Web
Developer toolbar--so your style sheet is working, at least for me.
Menus are also displayed in Garamond, but normal weight, italic (too
light for
On Tue, 17 Jul 2007 14:25:00 +0100, Nick Roper wrote:
> Hi James,
>
> Yup, as I say, it works fine for both headers and menus on FF/MAc, but only
> for the
> menus on FF/Win.
>
> What I'm trying to figure out is why the menus render in Garamamond but the
> headings
> don't on FF/Win
>
Correction
On Tue, 17 Jul 2007 14:25:00 +0100, Nick Roper wrote:
> Hi James,
>
> Yup, as I say, it works fine for both headers and menus on FF/MAc, but only
> for the
> menus on FF/Win.
>
> What I'm trying to figure out is why the menus render in Garamamond but the
> headings
> don't on FF/Win
>
Correction
On Tue, 17 Jul 2007 14:25:00 +0100, Nick Roper wrote:
> Hi James,
>
> Yup, as I say, it works fine for both headers and menus on FF/MAc, but only
> for the
> menus on FF/Win.
>
> What I'm trying to figure out is why the menus render in Garamamond but the
> headings
> don't on FF/Win
>
Interestin
On Tue, 17 Jul 2007 14:25:00 +0100, Nick Roper wrote:
> Hi James,
>
> Yup, as I say, it works fine for both headers and menus on FF/MAc, but only
> for the
> menus on FF/Win.
>
> What I'm trying to figure out is why the menus render in Garamamond but the
> headings
> don't on FF/Win
>
Interestin
Nick Roper wrote:
Hi,
We are making some changes to an existing site for a client -
basically converting to CSS as far as possible. I'd appreciate it if
someone could take a look at this page:
http://dev.logical.co.uk/castlewelding/final/gates_railings.php
The font for the h1 should be Gara
Hi James,
Yup, as I say, it works fine for both headers and menus on FF/MAc, but
only for the menus on FF/Win.
What I'm trying to figure out is why the menus render in Garamamond but
the headings don't on FF/Win
Nick
James Jeffery wrote:
Im using FireFox on a Mac and it works fine.
:P
Im using FireFox on a Mac and it works fine.
:P
On 7/17/07, Nick Roper <[EMAIL PROTECTED]> wrote:
Hi Nick,
Thanks for that. The weird thing is though that Garamond does render for
the menus. So, on the same machine/browser, the menus render in Garamond
- so the font is there OK - but the head
Hi Nick,
Thanks for that. The weird thing is though that Garamond does render for
the menus. So, on the same machine/browser, the menus render in Garamond
- so the font is there OK - but the headers don't.
Nick
Nick Gleitzman wrote:
On 17 Jul 2007, at 8:40 PM, Nick Roper wrote:
http://
Hi Tony,
But the weird thing is that it renders OK for the menus, which also
specify italic.
Nick
Tony Crockford wrote:
On 17 Jul 2007, at 11:40, Nick Roper wrote:
I have stared at it until I can't see wood for trees any more. I even
tried adding an inline style attribute into the H1 ta
On 17 Jul 2007, at 8:40 PM, Nick Roper wrote:
http://dev.logical.co.uk/castlewelding/final/gates_railings.php
The font for the h1 should be Garamond - as it is for the menus at the
left. However it refuses to render in FF/Windows - although it is fine
on FF/Mac. The other weird thing is that
On 17 Jul 2007, at 11:40, Nick Roper wrote:
I have stared at it until I can't see wood for trees any more. I
even tried adding an inline style attribute into the H1 tag - but
that didn't work either. Am I missing something startlingly obvious?
assuming windows actually has the font insta
20 matches
Mail list logo
