Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: unicode is a fail Date: Wed, 02 Dec 2015 11:27:49 -0800 Organization: None to speak of Lines: 28 Message-ID: References: <22fccd29-addc-4070-8d1d-c3f876f5f12e@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: mx02.eternal-september.org; posting-host="945944de09706c9b4e29b53c9d2efdc2"; logging-data="13325"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18AhQQ6Ye7Km0gtoh4TC6eg" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:hZUgpLLPXzk7IA4+c4nIFsxSTQQ= sha1:xff0dtbxsGHVpKX1yvGIufh+Clo= Xref: csiph.com comp.lang.c:77650 Stephen Sprunk writes: > On 02-Dec-15 10:18, Malcolm McLean wrote: >> UTF-8 is the best compromise. But there are some problem that are >> very hard to avoid., like supporting archaic ash and thorn in English >> (mediaeval, ye olde coffee shoppe), when half the population think >> the latter is a y as in yellow. > > What problems? > > wynn Ƿ ƿ > thorn Þ þ > eth Ð ð > ash Æ æ > ethel Œ œ > yogh Ȝ ȝ > ond ⁊ > > This message is encoded in UTF-8, and unless your system doesn't have > any fonts with the proper glyphs (unlikely), you should see them fine. That last one is U+204A, "TIRONIAN SIGN ET". There doesn't appear to be anything in Unicode called "ond". -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"