This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html Multipage: http://www.whatwg.org/C#table-http-equiv Complete: http://www.whatwg.org/c#table-http-equiv Referrer: Comment: The pragma is "unlike" the HTTP header? Shouldn’t this be the opposite? Posted from: 109.145.134.13 User agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0
I’m confused by "almost entirely unlike".
I recommend reading the Hitchhiker's Guide to the Galaxy. "entirely unlike" means "nothing like". "not entirely unlike" means "not nothing like". "almost entirely unlike" means "almost nothing like". Seems pretty unambiguous to me. What's the problem?
I expected the meaning to be the opposite because they do not seem that different as far as I can tell, but ok.
It parses differently, it has different semantics, it does something different... it's only superficially the same. And you really should read the Hitchhiker's Guide to the Galaxy. :-)