Re: Standards compliance (HTML)
From: James Van Buskirk (not_valid_at_comcast.net)
Date: 07/21/04
- Next message: David Ham: "Re: Standards compliance (HTML)"
- Previous message: David Ham: "Re: Standards compliance (HTML)"
- In reply to: Richard Edgar: "Re: Standards compliance (HTML)"
- Next in thread: David Ham: "Re: Standards compliance (HTML)"
- Reply: David Ham: "Re: Standards compliance (HTML)"
- Reply: Richard Edgar: "Re: Standards compliance (HTML)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 21 Jul 2004 16:57:16 GMT
"Richard Edgar" <rge21@astro.su.se> wrote in message
news:cdm3id$1vg$1@news.su.se...
> James Van Buskirk wrote:
> >
'<title>документ</title>'
> Yes.
OK, that's fixed.
> If you think that it should be a monospaced font, why don't you have
> <body style="font-family: monospace;">
But how do you specify both monospaced and serif? It seems the
the browser is supposed to scan the font families until it finds
something it likes, so if it sees monospace it may present a sans-
serif font while if it sees serif first it may serve up a proportional
font. Is HTML really this badly broken?
-- write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, & 6.0134700243160014d-154/),(/'x'/)); end
- Next message: David Ham: "Re: Standards compliance (HTML)"
- Previous message: David Ham: "Re: Standards compliance (HTML)"
- In reply to: Richard Edgar: "Re: Standards compliance (HTML)"
- Next in thread: David Ham: "Re: Standards compliance (HTML)"
- Reply: David Ham: "Re: Standards compliance (HTML)"
- Reply: Richard Edgar: "Re: Standards compliance (HTML)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|