I'd like to thank Barry and Pat for this conversation. It's refreshing to see a new standard that, for a change, makes life simpler. If I read Barry's "No requirement.." correctly, it means all that extra stuff isn't needed in the HTML5 standard. We no longer need to choose between "strict" and "transitional" nor tell the browser where to find the definitions. About character sets, the "charset=" declaration: You may recall that I had a problem a while ago with included files displaying garbage characters. (Gosh, you wouldn't think plain text could be so complicated.) After much head-scratching and asking here, it seemed to be caused by a mismatch in character sets; the included files used a different character set than the one specified for the including doc. The problem was resolved only after changing the charset declaration in the doc head from "iso-8859-1" to "utf-8" and saving the included files in utf-8 format. Thanks, -rt_/)
On Tuesday, February 28, 2012 10:21 AM (UTC+13)Ralph wrote: > > If I read Barry's "No requirement.." correctly, it means all that extra > stuff isn't needed in the HTML5 standard. We no longer need to choose > between "strict" and "transitional" nor tell the browser where to find the > definitions. > ------------------------------ Ralph, That is right. Put another way, it does no harm to include them, nor if you don't. When you validate pages at:- http://validator.nu - you may find errors with some of your meta tags, e.g. <meta name="copyright" content="Sing A Song Of Sixpence Co. Inc"> There is most likely no problem with the same tags when validated as HTML4, and the reason for them failing in the HTML5 validator is they haven't as yet not all been included in the Standard, and "copyright" is just one of those. My advice is to just ignore those sort of errors as they will eventually be resolved. As I have mentioned earlier; where a page validated as XHTML1.0 Strict, the same page when equipped with the HTML5 <!DOCTYPE html> will also be rendered in Strict mode irrespective of some minor HTML5 validation errors. Barry