CSS problems

I've got some CSS syles in a sperate style sheet but for some reason I can't
get my bold text style to work. The title Medical Device Manufacturer is
supposed to be bold text, it works when viewing the sit in DW but when
published and viewed in IE it won't work, it does work in netscape.

http://www.medicaldevicemanufacturer.biz

Any help would be greatly appreciated.

As far as i can see your TEXT.CSS file has no bold/weight selected

HTH

"nomayo" <webforumsuser (AT) macromedia (DOT) com> wrote

I've got some CSS syles in a sperate style sheet but for some reason I
can't
get my bold text style to work. The title Medical Device Manufacturer is
supposed to be bold text, it works when viewing the sit in DW but when
published and viewed in IE it won't work, it does work in netscape.

http://www.medicaldevicemanufacturer.biz

Any help would be greatly appreciated.

I notice you have your font: defined on one line..Avoid using shorthand css.
Split it up as follows:

.style1 {
font-family: Verdana, Arial, Helvetica, sans-serif;
font-weight: bold;
color: #000000;
}
.bodytext {
font-family: Verdana, Arial, Helvetica, sans-serif;
text-transform: none;
color: #000000;
}
body {
background-image: url(images/background.gif);
}

this is the copied css from my style sheet

.style1 {
font: bold normal small/normal Verdana, Arial, Helvetica, sans-serif;
text-transform: none;
color: #000000;
text-decoration: none;
}
.bodytext {
font: normal small/normal Verdana, Arial, Helvetica, sans-serif;
text-transform: none;
color: #000000;
}
body {
background-image: url(images/background.gif);
}

You should clean up your font declaration into multiple lines like the example above. Don't do:

Font: bold normal small/normal Verdana, Arial, Helvetica, sans-serif;
all on one line.

Ahh, now I see, thanks, I'll try that

Why?

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"Vinh X" <webforumsuser (AT) macromedia (DOT) com> wrote

You should clean up your font declaration into multiple lines like the
example above. Don't do:

Font: bold normal small/normal Verdana, Arial, Helvetica, sans-serif;
all on one line.

.oO(Vinh X)

You should clean up your font declaration into multiple lines like the
example above.

There's nothing wrong with using shorthand properties.

Don't do:
Font: bold normal small/normal Verdana, Arial, Helvetica, sans-serif;
all on one line.

It's absolutely correct syntax. My IE 5 gets confused about the first
'normal' (NN4 surprisingly gets it right), but the following works:

font: bold small Verdana, Arial, Helvetica, sans-serif

And in recent browsers such things are no problem at all.

@nomayo: You should consider using appropriate markup. "Medical Device
Manufacturer and Design Facility" looks like a heading to me. So why not
use a h1 or h2-element (with h1 being the company name) there? Bold text
inside a div doesn't make a heading, it's just meaningless bold text.

Micha

Michael Fesser wrote:

.oO(Vinh X)


You should clean up your font declaration into multiple lines like the
example above.


There's nothing wrong with using shorthand properties.

Are you sure about they? I gave up using shorthand to declare font
properties because I found issues with it x-browser.

It may be that you need to get the attributes into a specific order like
you do when declaring bg images in shorthand, which also have issues
unless you get the declaration in the correct running order.

Osgood wrote:

Are you sure about that? not they, duh.

Are you sure about they? I gave up using shorthand to declare font
properties because I found issues with it x-browser.

It may be that you need to get the attributes into a specific order like
you do when declaring bg images in shorthand, which also have issues
unless you get the declaration in the correct running order.