The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] long lived programs
Date: Fri, 06 Apr 2018 04:27:59 +0000	[thread overview]
Message-ID: <CANCZdfoikWhOYcFzmk039WT-fawvr0NtNGq_9J8TjkwPcpT0nA@mail.gmail.com> (raw)
In-Reply-To: <1522980220.3263789.1328338032.3CD6D7F7@webmail.messagingengine.com>

On Thu, Apr 5, 2018, 8:04 PM Random832 <random832 at fastmail.com> wrote:

> On Thu, Apr 5, 2018, at 17:38, Bakul Shah wrote:
> > May be case itself is such a historical artifact?  AFAIK all non-roman
> > scripts are without case distinction.
>
> Greek and Cyrillic both have cases. And the Hiragana/Katakana distinction
> in Japanese is similar to case in some ways (including limited computer
> systems using only one)
>

Really? Those must be quite old as everything I've seen has both. But the
difference between kata and kana is much larger than upper and lower case.
It is rare to convert one to another as they are used to write different
things. Only to look things up in a dictionary would you convert, and then
you'd also be converting kanji to...

In Roman languages, very little is changed with all caps, though a few
things become ambiguous depending on the language...

In Japanese, it could turn some foreign loan word into a native word with a
totally different meaning...

Warner

> Full list of scripts in unicode that have case distinctions (based on
> analyzing character names): Adlam, Armenian, Cherokee, Coptic, Cyrillic,
> Deseret, Georgian, Glagolitic, Greek, Latin, Old Hungarian, Osage, and
> Warang Citi.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180406/59f22529/attachment.html>


  reply	other threads:[~2018-04-06  4:27 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05 21:03 Norman Wilson
2018-04-05 21:23 ` Clem Cole
2018-04-05 21:38   ` Bakul Shah
2018-04-06  2:03     ` Random832
2018-04-06  4:27       ` Warner Losh [this message]
2018-04-06  4:31         ` Jon Steinhart
2018-04-06  4:58         ` Steve Nickolas
2018-04-06  5:02           ` Jon Steinhart
2018-04-06  4:29       ` Steve Johnson
2018-04-06  5:57       ` Bakul Shah
2018-04-06 21:52         ` Peter Jeremy
2018-04-05 22:46   ` Arthur Krewat
2018-04-05 23:23   ` Paul Winalski
2018-04-05 23:33     ` Arthur Krewat
2018-04-06  0:05       ` Toby Thain
2018-04-06  4:51 ` Dave Horsfall
2018-04-06 15:00 ` Tony Finch
2018-04-07 20:41 ` Paul Winalski
  -- strict thread matches above, loose matches on Subject: below --
2018-04-06 22:33 Doug McIlroy
2018-04-07  1:01 ` Paul Winalski
2018-04-07  1:09   ` Larry McVoy
2018-03-23 18:27 [TUHS] long lived programs (was Re: RIP John Backus Bakul Shah
2018-03-23 20:50 ` [TUHS] long lived programs Steve Johnson
2018-03-23 21:07   ` Clem Cole
2018-03-23 15:51 Ron Natalie
2018-03-23 15:57 ` Clem Cole
2018-03-23 16:25   ` Lars Brinkhoff
2018-03-23 16:59     ` Lawrence Stewart
2018-03-23 17:31       ` Steve Nickolas
2018-03-23 16:32   ` Ron Natalie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANCZdfoikWhOYcFzmk039WT-fawvr0NtNGq_9J8TjkwPcpT0nA@mail.gmail.com \
    --to=imp@bsdimp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).