undefined | Better HN

0 pointsmajewsky4y ago0 comments

Nitpick 1: That DTD is for HTML 2.0, which was published in 1995. If that does not qualify as "back in the day", I don't know what does.

Nitpick 2: <meta> goes inside <html> (inside <head>, really).

Nitpick 3: The <meta> tag is only a band-aid for shitty webhosting where you cannot access the webserver config to make it send the correct Content-Type in the actual HTTP response headers. The modern <!DOCTYPE html> instead implies a default of UTF-8 which works well for most.

0 comments

skymt4y ago

Nitpick nitpick: the html doctype doesn't imply UTF-8. Valid modern HTML documents must be encoded using UTF-8, but the standard also requires that the encoding be specified somehow.

> The Encoding standard requires use of the UTF-8 character encoding and requires use of the "utf-8" encoding label to identify it... If an HTML document does not start with a BOM, and its encoding is not explicitly given by Content-Type metadata, and the document is not an iframe srcdoc document, then the encoding must be specified using a meta element with a charset attribute or a meta element with an http-equiv attribute in the Encoding declaration state.

<https://html.spec.whatwg.org/multipage/semantics.html#charac...>

j / k navigate · click thread line to collapse