From lojban-out@lojban.org Mon Sep 05 21:44:49 2005 Return-Path: X-Sender: lojban-out@lojban.org X-Apparently-To: lojban@yahoogroups.com Received: (qmail 82218 invoked from network); 6 Sep 2005 04:44:48 -0000 Received: from unknown (66.218.66.172) by m26.grp.scd.yahoo.com with QMQP; 6 Sep 2005 04:44:48 -0000 Received: from unknown (HELO chain.digitalkingdom.org) (64.81.49.134) by mta4.grp.scd.yahoo.com with SMTP; 6 Sep 2005 04:44:48 -0000 Received: from lojban-out by chain.digitalkingdom.org with local (Exim 4.52) id 1ECVKA-0006LS-3d for lojban@yahoogroups.com; Mon, 05 Sep 2005 21:44:46 -0700 Received: from chain.digitalkingdom.org ([64.81.49.134]) by chain.digitalkingdom.org with esmtp (Exim 4.52) id 1ECVJW-0006Ks-8i; Mon, 05 Sep 2005 21:44:08 -0700 Received: with ECARTIS (v1.0.0; list lojban-list); Mon, 05 Sep 2005 21:43:58 -0700 (PDT) Received: from nobody by chain.digitalkingdom.org with local (Exim 4.52) id 1ECVJE-0006Kj-Gj for lojban-list-real@lojban.org; Mon, 05 Sep 2005 21:43:48 -0700 Received: from wproxy.gmail.com ([64.233.184.198]) by chain.digitalkingdom.org with esmtp (Exim 4.52) id 1ECVJC-0006Kb-6R for lojban-list@lojban.org; Mon, 05 Sep 2005 21:43:48 -0700 Received: by wproxy.gmail.com with SMTP id 71so826745wra for ; Mon, 05 Sep 2005 21:43:44 -0700 (PDT) Received: by 10.54.121.12 with SMTP id t12mr4113928wrc; Mon, 05 Sep 2005 21:43:44 -0700 (PDT) Received: by 10.54.140.6 with HTTP; Mon, 5 Sep 2005 21:43:44 -0700 (PDT) Message-ID: Date: Tue, 6 Sep 2005 00:43:44 -0400 In-Reply-To: <8f2fd4aa050905195922e9cca2@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_11205_3467672.1125981824601" References: <20050906010833.24545.qmail@web81310.mail.yahoo.com> <8f2fd4aa050905181732abb68a@mail.gmail.com> <8f2fd4aa050905195922e9cca2@mail.gmail.com> X-Spam-Score: -2.4 (--) X-archive-position: 10505 X-ecartis-version: Ecartis v1.0.0 Errors-to: lojban-list-bounce@lojban.org X-original-sender: matt.mattarn@gmail.com X-list: lojban-list X-Spam-Score: -2.4 (--) To: lojban@yahoogroups.com X-Originating-IP: 64.81.49.134 X-eGroups-Msg-Info: 1:12:0:0 X-eGroups-From: Matt Arnold From: Matt Arnold Reply-To: matt.mattarn@gmail.com Subject: [lojban] Re: Orthography X-Yahoo-Group-Post: member; u=116389790; y=JxPRDZbiReFEc5ntMpoCPg37_f8-40wWmyRRdvE1Kj7FpxIG5Q X-Yahoo-Profile: lojban_out X-Yahoo-Message-Num: 24887 ------=_Part_11205_3467672.1125981824601 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I have attempted to make a chart in which I count in binary using LCD clock= =20 characters. http://www.nemorathwald.com/lojban/LCD_binary_chart.jpg Black represents on, blue represents off. There are a hundred and twenty=20 eight, if you include zero, so that matches John's count. I'm fairly sure=20 every possible way for it to light up is represented in this chart. Each of= =20 the seven strokes is to represent a digit in a binary number, and John=20 described the scheme as follows: top, upper right, upper left, middle, lower right, lower left, bottom I would have numbered them but I don't know how to count in binary so I=20 don't know if I've got them in the wrong order. Can somebody type out a=20 comma-separated or space-separated list numbering them according to what=20 each represents? For instance, unless I am mistaken, I think the first row= =20 is:=20 0 and the second row is: 1 2 3 4 5 6 7 ...I think. The last row is: 128 Then I'll remake the chart, numbered, and put it online. Then when we=20 discuss changes to DSO we could just refer to a character by number and loo= k=20 it up to know what somebody's talking about. -epkat On 9/5/05, Brandon Wirick wrote: >=20 > It certainly doesn't suck! Good idea on the vowels. Too bad it's > impossible to do that with only connected characters. >=20 > Maybe I can create an applet or something that generates orthographies > from a hex string. That way we can all play around with orthographies > and communicate along these lines: > "Check out this orthography: 4FA39F6..." > "Ooh, I like what you did with {ty} and {dy}, but I think it would be > better if you did this: 4FA3C96..." >=20 > I'll get on that soon, or if anyone else is itching to do it, be my guest ------=_Part_11205_3467672.1125981824601--