View Single Post
Old 05-09-2014, 09:23 PM   #10
cdhigh
Enthusiast
cdhigh ought to be getting tired of karma fortunes by now.cdhigh ought to be getting tired of karma fortunes by now.cdhigh ought to be getting tired of karma fortunes by now.cdhigh ought to be getting tired of karma fortunes by now.cdhigh ought to be getting tired of karma fortunes by now.cdhigh ought to be getting tired of karma fortunes by now.cdhigh ought to be getting tired of karma fortunes by now.cdhigh ought to be getting tired of karma fortunes by now.cdhigh ought to be getting tired of karma fortunes by now.cdhigh ought to be getting tired of karma fortunes by now.cdhigh ought to be getting tired of karma fortunes by now.
 
Posts: 41
Karma: 333334
Join Date: Oct 2011
Device: KINDLE 3
yes, it is in html header (meta field), this is reason that TRUST_ENCODING_IN_HEADER_OR_META=True will solve the problem.
I mean that it not in http response header, KindleEar will use encoding if encoding in http header and that in html header are the same, otherwise, will use encoding detected by chardet.
for other countries I have not sure, but sites in China are very complicated, frequently them are not the same (there are many programers inexperienced and lazy).

TRUST_ENCODING_IN_HEADER_OR_META=True redefine the encoding finding behavior, use first one found (http response header is primary priority, followed by html header, chardet)

TRUST_ENCODING_IN_HEADER_OR_META=False is the default behavior, first is header encoding (if same in http header and html header), followed by chardet.
cdhigh is offline   Reply With Quote