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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a02:b572:: with SMTP id z47-v6mr3016189jaj.18.1530809252835; Thu, 05 Jul 2018 09:47:32 -0700 (PDT) X-Received: by 2002:aca:eb15:: with SMTP id j21-v6mr1479775oih.6.1530809252669; Thu, 05 Jul 2018 09:47:32 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.uzoreto.com!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!d7-v6no2800166itj.0!news-out.google.com!z3-v6ni2839iti.0!nntp.google.com!d7-v6no2800165itj.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Thu, 5 Jul 2018 09:47:32 -0700 (PDT) In-Reply-To: <176034645.552448963.078419.laguest-archeia.com@nntp.aioe.org> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=76.113.16.86; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC NNTP-Posting-Host: 76.113.16.86 References: <5de5f768-40bf-4518-a647-22788658de74@googlegroups.com> <64454862-b293-4ed7-9c3e-c8a1252344db@googlegroups.com> <0ebf920a-61fa-47e8-a34f-54da2e143bb6@googlegroups.com> <6af9d974-b2b4-4ab9-82e6-690ffaee2901@googlegroups.com> <795161eb-b58c-4146-9721-9b553039868a@googlegroups.com> <176034645.552448963.078419.laguest-archeia.com@nntp.aioe.org> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <1064fcce-1b1c-4672-bd4e-9eb93c3a0240@googlegroups.com> Subject: Re: Strange crash on custom iterator From: Shark8 Injection-Date: Thu, 05 Jul 2018 16:47:32 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader02.eternal-september.org comp.lang.ada:53655 Date: 2018-07-05T09:47:32-07:00 List-Id: On Wednesday, July 4, 2018 at 8:07:56 PM UTC-6, Luke A. Guest wrote: > Shark8 wrote: >=20 > >> Shark8, what would be the better solution for character-encoding itsel= f? > >> (not whole words) > >=20 > > Whole-word isn't a terrible idea, per se. But the thrust I was getting = at > > is the delination between languages: with Unicode it's a sequence of > > codepoints, independent of the actual item (word, sentence, etc) other > > than [perhaps] graphic-presented. That the example is (Eng,Eng,Eng...En= g, > > Heb,Heb,Heb,Heb, Eng,Eng,Eng...) codepoints is not the problem, though > > related, because it discards all information in favor of (num, num, num= , > > num, ...) rather than actually considering alternate languages: IMO, > > ("The Hebrew word for man" (quote ADAM) (quote "Adam") ".") is much > > better as 'text' because we're preserving structure: [ENGLISH [THIS > > SECTION HEBREW] ENGLISH]. > >=20 >=20 > I don=E2=80=99t understand why you think Unicode should carry linguistic > information when all it has ever been designed to do is encode symbols > across all languages and their direction. I'm not saying that "Unicode should" do *anything* -- I'm saying Unicode so= lves *the wrong problem*. "Encoding symbols" ties everything to a stupidly primitive level, forcing e= verything to such lowest common denominator so as to apply "the unix way" p= rocessing to text: discard all structural information, all semantic informa= tion, and have "some tool" regenerate it later... just like "the unix way" = discards type-information in favor of forcing ad-hoc parsing on unstructure= d-text at every step between it's "small tools" connected together with 'pi= pes'.