Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #17683

Re: Potential FAQ mechanism on GitHub

Show all headers | View raw

In article <kaacf6$4uh$1@dont-email.me>,
 "Jukka K. Korpela" <jkorpela@cs.tut.fi> wrote:

> 2012-12-12 17:41, John G Harris wrote:
> 
> > On Tue, 11 Dec 2012 at 22:31:25, in comp.lang.javascript, Thomas
> > 'PointedEars' Lahn wrote:
> >> Jeff North wrote:
> >
> >    <snip>
> >>> The code element is an inline element much like em, b, u etc.
> >>
> >> Yes, although it is spelled “CODE element” before HTML5 (WD).
> >    <snip>
> >
> > Well, the HTML standards had to spell it some way. As tags are case
> > independent, <cOdE> is legal and so is <code>.
> 
> Of course. Even many novices know that, and this makes the off-topic 
> lectures of “Thomas 'PointedEars' Lahn” even more ridiculous. (He also 
> lectures on Usenet conduct, including “From” lines, still failing to 
> obey the good old rule that the “From” line contains the full name and 
> e-mail address of the sender and nothing more.)
> 
> > It was XHTML that insisted on tag names being lower case.
> 
> Or insists; XHTML isn’t actually dead.
> 
> > And "before HTML5" is a bit premature, to say the least.
> 
> In reality, “HTML5” is just as case-insensitive as HTML specs have used 
> to be. “HTML5” lets you use XML syntax, too, but “HTML5” as such does 
> not require tag names in any particular case. In fact, the “HTML5” 
> drafts, and the “Living HTML Standard” documents, intentionally (but 
> rather confusingly) use case variation in tag names.
> 
> The only excuse for posting these off-topic notes are that they help to 
> reveal some of the bogosity of the person that has volunteered to become 
> the comp.lang.javascript FAQ maintainer, despite his continued rants 
> “there is no javascript”.

+1

-- 
Tim

"That excessive bail ought not to be required, nor excessive fines imposed,
nor cruel and unusual punishments inflicted"  --  Bill of Rights 1689

Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Potential FAQ mechanism on GitHub Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-09 20:12 -0800
  Re: Potential FAQ mechanism on GitHub John G Harris <john@nospam.demon.co.uk> - 2012-12-10 11:26 +0000
    Re: Potential FAQ mechanism on GitHub Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-10 04:29 -0800
      Re: Potential FAQ mechanism on GitHub John G Harris <john@nospam.demon.co.uk> - 2012-12-10 18:35 +0000
        Re: Potential FAQ mechanism on GitHub Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-10 11:03 -0800
          Re: Potential FAQ mechanism on GitHub John G Harris <john@nospam.demon.co.uk> - 2012-12-11 11:02 +0000
            Re: Potential FAQ mechanism on GitHub Jeff North <jnorthau@yahoo.com.au> - 2012-12-12 01:27 +1100
              Re: Potential FAQ mechanism on GitHub John G Harris <john@nospam.demon.co.uk> - 2012-12-11 14:52 +0000
              Re: Potential FAQ mechanism on GitHub Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-11 22:31 +0100
                Re: Potential FAQ mechanism on GitHub John G Harris <john@nospam.demon.co.uk> - 2012-12-12 15:41 +0000
                Re: Potential FAQ mechanism on GitHub "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2012-12-12 18:47 +0200
                Re: Potential FAQ mechanism on GitHub Tim Streater <timstreater@greenbee.net> - 2012-12-12 23:20 +0000
            Re: Potential FAQ mechanism on GitHub Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-11 06:30 -0800
      Re: Potential FAQ mechanism on GitHub Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-12 21:13 +0000
  Re: Potential FAQ mechanism on GitHub Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-12 21:27 +0000
    Re: Potential FAQ mechanism on GitHub Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-13 08:29 -0800

csiph-web