DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=jY327D+gGFSuJpBz8OBwwwAsBWLmFYNXVV+fUOtbWw9FtlccjvGa+X/+8gE0g5tUpBh7almkwH3QXkGLT0LbOKKuFMcl5NhchlJz6LugjgjFtWjZ9nK899KGTlyh9eqLrTrOenvP+gfGotC2CPDhOgAj/yOvszYoEfHgMMj4big=
Message-ID: <8f2fd4aa0508211445564ce745@mail.gmail.com>
Date: Sun, 21 Aug 2005 14:45:29 -0700
From: Brandon Wirick <brandon.wirick@gmail.com>
To: lojban-beginners@chain.digitalkingdom.org
Subject: [lojban-beginners] Fwd: Re: Why 16
In-Reply-To: <H00061428e5a8f57.1124496193.seurat.artisan.calpoly.edu@MHS>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
References: <H00061428e5a8f57.1124496193.seurat.artisan.calpoly.edu@MHS>
Sender: lojban-beginners-bounce@chain.digitalkingdom.org
Errors-to: lojban-beginners-bounce@chain.digitalkingdom.org
Precedence: bulk
Reply-to: lojban-beginners@chain.digitalkingdom.org
Content-Length: 728

Hexadecimal is in wide use (shoot, I read hexadecimal traces at work)
but unless you're reading, like, technical documents from ancient
Babylon, you're not going to need more than 16 digits for any
practical purpose. The cmavo-space is way bloated as it is, and since
every number after 16 would just be arbtitrary cutoff points for digit
cmavo, 16 is a good place to cut it off.

mi'e .uirik.

> Umm... we're not speaking about the same issue. :) 
My question was about basic names for digits, from {no} to {vai}: why
do we have exactly 16 of them?
I understand the usefulness of hexa digits, but for that reason we
could also use a hundred or even more basic numbers, as those cover 16
as well. So what's the point (of 16)?