summaryrefslogtreecommitdiff
path: root/test/hubbub.c
diff options
context:
space:
mode:
authorJohn Mark Bell <jmb@netsurf-browser.org>2009-01-06 17:16:09 +0000
committerJohn Mark Bell <jmb@netsurf-browser.org>2009-01-06 17:16:09 +0000
commit9b5ab3bdedb0431168d676775df12780cbd17e51 (patch)
tree39fc94b73ab07781816c42b746ce5bdf47bb33d7 /test/hubbub.c
parentc00d6e3b878e120e6e2b1b131127262b3c0d4eeb (diff)
downloadlibhubbub-9b5ab3bdedb0431168d676775df12780cbd17e51.tar.gz
libhubbub-9b5ab3bdedb0431168d676775df12780cbd17e51.tar.bz2
Some kind of recovery from not supporting an auto-detected charset. We fall back to Windows-1252 and hope for the best.
Note that this only occurs when autodetecting. If the client has specified a charset, they get told about it immediately and get to decide what to do about it. If a meta charset is encountered after a successful autodetection, the client is informed in the usual way. As this requires the client to throw out the parser and start afresh, specifying the meta charset as the one to use, there's no problem as, again, the client will be informed immediately in that case. All of this ensures that charset autodetection is pretty well transparent as far as the client application is concerned. svn path=/trunk/hubbub/; revision=5970
Diffstat (limited to 'test/hubbub.c')
0 files changed, 0 insertions, 0 deletions