Stephen J. Turnbull wrote: > But the Web in general provides (mandatory) protocols for identifying > content-type, yet I regularly see HTML files with incorrect http-equiv > meta elements, and XHTML with no encoding declaration containing Shift > JIS. which reminds me: the HTTP protocol says that a charset specified at the HTTP protocol level should override any encoding specified in the document itself. how do we deal with this? an encoding override to compile()? </F>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4