Isn't ASSUME_CHARSET for documents which do not declare their charset, i.e., the Lynx user is _assuming_ that the document author wrote in the ASSUME_CHARSET?
If a web page declares its charset incorrectly, that seems to be the responsibility of the author. I don't think it is Lynx's job to "override" what the author [mis]intended. In such a case, I would either contact the author, or, if too much bother, just download the document and edit the charset declaration. Or as I often do, download and convert the document to UTF-8 (iconv, nkf). YES, thank you for Lynx! 2024年1月18日(木) 5:03 Steffen Nurpmeso <stef...@sdaoden.eu>: > > Hello! > > I stumbled over the above, ie., > > curl -o x.html https://www.google.com > > from here in Germany (in C.UTF-8 locale; but also Poland, said > a PLD-Linux developer) fetches a document that declares itself as > UTF-8, but in fact contains ISO-8859-1 (-2). > I had to copy the document and modify it, because -assume_charset > is overruled by the in-document thing. It is documented, but > i find it strange. > > Thank you for lynx! > > --steffen > | > |Der Kragenbaer, The moon bear, > |der holt sich munter he cheerfully and one by one > |einen nach dem anderen runter wa.ks himself off > |(By Robert Gernhardt) >
