Quote:
Originally Posted by Notjohn
Charles Seper has this to say on the subject:
If this was true yesterday, it isn't true today. I just tried it and monospace works all by its lonesome. This is what works for monospace:
font-family: monospace;
font-family: 'Courier New', Courier, monospace
These do NOT work:
font-family: 'Courier New', monospace
font-family: Courier, monospace
As to heading fonts, they've been very hit and miss for a long time now. Some fonts work, others don't. And some only work if you list them in a specific way. My way of making helvetica still works fine:
font-family: Helvetica, sans-serif
Specifying Arial doesn't:
font-family: Arial, sans-serif
|
I think what you're seeing is a series a policies that try to throw out font rules that look like they were automatically blown in by Microsoft Word. You probably can't realistically ship an embedded copy of Helvetica or Arial, so listing it by itself in a font declaration doesn't make a lot of sense. Thus, the only way such rules would likely end up in a submission would be if somebody just let Word spew its awful HTML.
Chances are, if you avoid the stock Windows fonts, you'll be fine.