From pycyn@aol.com Mon Oct 01 06:04:47 2001 Return-Path: X-Sender: Pycyn@aol.com X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-7_4_1); 1 Oct 2001 13:04:47 -0000 Received: (qmail 20064 invoked from network); 1 Oct 2001 13:04:47 -0000 Received: from unknown (10.1.10.27) by 10.1.1.222 with QMQP; 1 Oct 2001 13:04:47 -0000 Received: from unknown (HELO imo-r01.mx.aol.com) (152.163.225.97) by mta2 with SMTP; 1 Oct 2001 13:04:46 -0000 Received: from Pycyn@aol.com by imo-r01.mx.aol.com (mail_out_v31_r1.7.) id r.125.52a90aa (4406) for ; Mon, 1 Oct 2001 09:04:41 -0400 (EDT) Message-ID: <125.52a90aa.28e9c3e9@aol.com> Date: Mon, 1 Oct 2001 09:04:41 EDT Subject: Re: [lojban] possible A-F... To: lojban@yahoogroups.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_125.52a90aa.28e9c3e9_boundary" X-Mailer: AOL 6.0 for Windows US sub 10535 From: pycyn@aol.com --part1_125.52a90aa.28e9c3e9_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 9/30/2001 9:40:13 PM Central Daylight Time, thinkit8@lycos.com writes: > > *** * * * *** *** > * * * * * * > * *** *** *** * *** > * * * * * * > * * * * *** * > > that's 10-15, in order. now all i have to do is wait generations to > have hexadecimal accepted, then more generations for the numbers to > . Could you do these a little more clearly? It is hard to see what they might look like since they apparently overlap. Oh, and don't hold your breath for hex acceptance. --part1_125.52a90aa.28e9c3e9_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 9/30/2001 9:40:13 PM Central Daylight Time, thinkit8@lycos.com writes:




*** *     * *   *** ***
*   *     * *     * *
*   *** *** ***   * ***
*   *   *     *   *   *
*   *   *     * ***   *

that's 10-15, in order.  now all i have to do is wait generations to
have hexadecimal accepted, then more generations for the numbers to
be standardized
.

Could you do these a little more clearly?  It is hard to see what they might look like since they apparently overlap.  Oh, and don't hold your breath for hex acceptance.
--part1_125.52a90aa.28e9c3e9_boundary--