Your reply makes sense. And I understand how fonts not universally installed may get substitution. But it doesn't explain why the site displayed in Baskerville and Gill Sans for three days and then - when I opened it in DW this morning - the file showed no signs of having ANY CSS information at all. And no, I am viewing it on the same computer I use 90% of the time (I have double-checked and Baskerville and Gill are installed). So it's not a font issue it's a DW issue. I am rebuilding a new CSS doc from scratch in hopes that this will bring me back to where I was yesterday. I greatly appreciate the reference to the @font-face rule and will try to adopt that. Thanks for your help. (For the record, I have come to expect erratic, unpredictable, inconsistent - and sometimes disastrous - behavior from DW, which I consider to be one of the worst apps ever foisted on poor, unsuspecting designers. I had hoped that Adobe would graft some of their UI thinking and consistency onto DW, but after years of waiting, I guess that's not going to happen. Part of my problem is that I don't use it every day, so my expertise is paper-thin, but I - like everyone else in the world who doesn't want to slog through code - will fall to Wordpress. Argh.)
Clik here to view.
