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 10.224.126.137 with SMTP id c9mr9525476qas.2.1380297226740; Fri, 27 Sep 2013 08:53:46 -0700 (PDT) X-Received: by 10.49.48.197 with SMTP id o5mr31051qen.31.1380297226708; Fri, 27 Sep 2013 08:53:46 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.glorb.com!q9no61449qas.0!news-out.google.com!9ni404qaf.0!nntp.google.com!q9no61438qas.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 27 Sep 2013 08:53:46 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=174.28.152.201; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC NNTP-Posting-Host: 174.28.152.201 References: User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Information Request. From: Shark8 Injection-Date: Fri, 27 Sep 2013 15:53:46 +0000 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Xref: news.eternal-september.org comp.lang.ada:17309 Date: 2013-09-27T08:53:46-07:00 List-Id: On Friday, September 27, 2013 3:45:27 AM UTC-6, Austin Obyrne wrote: > I=92m Sure Somebody Knows This.=20 >=20 > Question:=20 >=20 > Unicode is a splendid solution to a huge problem but how does it work in = practice. Is it? The problem of "combining characters" seems to me to defeat that if = there is any way to display the same character with different combining-seq= uences/codepoints. (e.g. "overstriking" w/ combining characters |S and S| t= o yield $ [just an example from my 105-key keyboard].) This is to say that = there should be only one combination of combining-character to yield a glyp= h. Another problem is casing. (e.g. how do you handle '=DF'? Does "ss" ever be= come '=DF'? Does '=DF' ever become 'S'?) While there has been a lot of work on the Unicode standard, I'm not sure th= at (a) the majority of Unicode *users* understand the vision that the Unico= de standard embodies, and (b) the Unicode standard has as clear an insight = into matters as, say, the ARG has into Ada. (After all, Unicode is aiming t= o be a universal character-encoding scheme, and that requires an insight in= to *all* languages and their writing-systems, while the ARG is focused only= on a single artificial/constructed language.) > I would be very grateful to anybody who can shed light on how it is done = in such cases especially from anybody with hands-on experience. Well, you could try starting here: http://www.joelonsoftware.com/articles/Unicode.html