Re: Standards compliance (HTML)
From: David Ham (d.a.ham_at_citg.tudelft.nl)
Date: 07/21/04
- Next message: James Van Buskirk: "Re: Standards compliance (HTML)"
- Previous message: Richard Edgar: "Re: Standards compliance (HTML)"
- In reply to: James Van Buskirk: "Re: Standards compliance (HTML)"
- Next in thread: Gary L. Scott: "Re: Standards compliance (HTML)"
- Reply: Gary L. Scott: "Re: Standards compliance (HTML)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 21 Jul 2004 18:30:59 +0200
On Wed, 21 Jul 2004 15:18:30 GMT
"James Van Buskirk" <not_valid@comcast.net> wrote:
> "David Ham" <d.a.ham@citg.tudelft.nl> wrote in message
> news:20040721112535.59e902b3.d.a.ham@citg.tudelft.nl...
>
> > On Tue, 20 Jul 2004 19:40:05 GMT
> > "James Van Buskirk" <not_valid@comcast.net> wrote:
>
> > Umm, I think it did. I checked. The message which the system
> > produced was
> > that the page was tentatively valid subject to a correct character
> > encoding. Character encoding is usually specified by the web server
> > in the http headers so I didn't fix it. Providing the information in
> > a meta element is, of course, also OK.
>
> The validator said that I was supposed to put a file whose name
> started with a period in my directory to fix the error but my
> ISP doesn't permit that.
>
I suspect that you managed to click through to something which told you
how to fix it in Apache using the .htaccess file. Apache is fairly
unixish even when running on Windows. If your ISP uses something else
(eg IIS) then that won't apply. Anyway, using the meta element is
always fine.
> > > write(11,'(a)') '<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01
> > > Transitional//EN">'
> > ^
> > The transitional DTD is deprecated (by W3C) for new work.
>
> Jeez, this is like java... everything is deprecated.
>
Yes. I think early versions of html were done in a fairly haphazard
way and a lot of structural markup and presentational stuff got mixed
up. html 4.0 was an attempt to clean up html and to line up with current
thinking in markup. As a result, there's an awful lot of older stuff
which is deprecated.
> > > write(11,'(a)')
> > > '<title>документ</title>'
> >
> > ^
> > That bit is quite cool, even if I can't read it.
>
> I was kind of curious about the above. MSIE displays this title
> just fine, but am I really supposed to terminate each number with
> a semicolon? As in:
>
> '<title>документ</tit
> le>'
>
> > > write(11,'(a)') '<font face="Courier New">'
> > ^
> > Font is one of those deprecated tags. We now have stylesheets for
> > this. For a little page like this one, the simplest thing to do is
> > chuck a style attribute in the body tag. eg :
> >
> > <body style="font-family:'Courier New',sans-serif">
> >
> > One of the advantages of this approach is that it does graceful
> > fallover.
>
> The 'Doze default for everything is Arial, which is proportional,
> sans-serif. If possible, I would prefer to fall back on
> monospaced, serif font, like Courier (which I think comes with
> a Mac.) The serifs need to be there to distinguish between 1Il
> and I consider monospaced fonts to be much more readable, perhaps
> due to habituation to punch card and line printer output.
Ah, my bad. I thought courier was sans-serif. Anyway, the comment about
fall back still applies.
>
> Well, thanks for your comments. We managed to get some Fortran
> code posted to this thread in any case.
>
:-).
David
> --
> write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, &
> 6.0134700243160014d-154/),(/'x'/)); end
>
>
- Next message: James Van Buskirk: "Re: Standards compliance (HTML)"
- Previous message: Richard Edgar: "Re: Standards compliance (HTML)"
- In reply to: James Van Buskirk: "Re: Standards compliance (HTML)"
- Next in thread: Gary L. Scott: "Re: Standards compliance (HTML)"
- Reply: Gary L. Scott: "Re: Standards compliance (HTML)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]