From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,ac4955b8006bd13c X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.204.154.133 with SMTP id o5mr20418bkw.0.1339026678323; Wed, 06 Jun 2012 16:51:18 -0700 (PDT) MIME-Version: 1.0 Path: e27ni21726bkw.0!nntp.google.com!news2.google.com!goblin1!goblin2!goblin.stu.neva.ru!news.stack.nl!nuzba.szn.dk!news.jacob-sparre.dk!munin.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: Q: type ... is new String Date: Wed, 6 Jun 2012 18:51:13 -0500 Organization: Jacob Sparre Andersen Research & Innovation Message-ID: References: <82defba0-2d39-4418-b678-ebbefeb105d7@x21g2000vbc.googlegroups.com> <4fcccd1f$0$6583$9b4e6d93@newsspool3.arcor-online.net> <4fccdd0c$0$6578$9b4e6d93@newsspool3.arcor-online.net> <4fcd20dd$0$9519$9b4e6d93@newsspool1.arcor-online.net> <1tr1nuc1xy9mp$.d5s1fz9vuczz.dlg@40tude.net> NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net X-Trace: munin.nbi.dk 1339026676 8637 69.95.181.76 (6 Jun 2012 23:51:16 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Wed, 6 Jun 2012 23:51:16 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-RFC2646: Format=Flowed; Original Date: 2012-06-06T18:51:13-05:00 List-Id: "Dmitry A. Kazakov" wrote in message news:1tr1nuc1xy9mp$.d5s1fz9vuczz.dlg@40tude.net... > On Mon, 04 Jun 2012 22:56:01 +0200, Georg Bauhaus wrote: > >> On 04.06.12 19:05, Dmitry A. Kazakov wrote: > >>> There is nothing ambiguous in character encoding, >> >> In processing data from any source that speaks HTTP, you don't really >> know >> the character encoding: you may be told the encoding is X but actually it >> is Y. > > <=> I do know the encoding. > > You are trying to pursue some absolute truth, e.g. "true encoding" of a > broken page, which simply does not exist and is irrelevant. You should > define an encoding and that is all the corresponding component need to > know > about it. I agree with Dmitry here. It is idiotic for web tools to do anything with malformed input (pages, whatever) other than to reject them. If they did that, we'd have far fewer ways to attack web programs (like browsers), and far fewer malformed inputs as well (because hardly anyone would want to write pages that couldn't be rendered -- they'd fix them in a hurry). The sloppiness in handling input is the bane of the Internet; software that doesn't do that is garbage. Unfortuately, garbage is all we have (thus the popularity of apps). Note that for my spam filter, I block or quarantine almost everything malformed. I had to allow some holes in that, because some very common tools and sites send out only malformed mail; which is aggrevating and allows ways for spammers and other criminals to make successful attacks. Grumble. Randy.