From lojban-out@lojban.org Sat Jul 27 09:54:19 2002
Return-Path: <lojban-out@lojban.org>
X-Sender: lojban-out@lojban.org
X-Apparently-To: lojban@yahoogroups.com
Received: (EGP: mail-8_0_7_4); 27 Jul 2002 16:54:19 -0000
Received: (qmail 75463 invoked from network); 27 Jul 2002 16:54:19 -0000
Received: from unknown (66.218.66.217)
  by m6.grp.scd.yahoo.com with QMQP; 27 Jul 2002 16:54:19 -0000
Received: from unknown (HELO chain.digitalkingdom.org) (204.152.186.175)
  by mta2.grp.scd.yahoo.com with SMTP; 27 Jul 2002 16:54:19 -0000
Received: from lojban-out by chain.digitalkingdom.org with local (Exim 4.05)
  id 17YUpf-0006PO-00
  for lojban@yahoogroups.com; Sat, 27 Jul 2002 09:54:19 -0700
Received: from digitalkingdom.org ([204.152.186.175] helo=chain)
  by chain.digitalkingdom.org with esmtp (Exim 4.05)
  id 17YUpP-0006P6-00; Sat, 27 Jul 2002 09:54:03 -0700
Received: with ECARTIS (v1.0.0; list lojban-list); Sat, 27 Jul 2002 09:54:00 -0700 (PDT)
Received: from cs6668125-184.austin.rr.com ([66.68.125.184] ident=root)
  by chain.digitalkingdom.org with esmtp (Exim 4.05)
  id 17YUpK-0006Ox-00
  for lojban-list@lojban.org; Sat, 27 Jul 2002 09:53:58 -0700
Received: from cs6668125-184.austin.rr.com (asdf@localhost [127.0.0.1])
  by cs6668125-184.austin.rr.com (8.12.3/8.12.3) with ESMTP id g6RGwBoT009827
  for <lojban-list@lojban.org>; Sat, 27 Jul 2002 11:58:11 -0500 (CDT)
  (envelope-from fracture@cs6668125-184.austin.rr.com)
Received: (from fracture@localhost)
  by cs6668125-184.austin.rr.com (8.12.3/8.12.3/Submit) id g6RGwADC009826
  for lojban-list@lojban.org; Sat, 27 Jul 2002 11:58:10 -0500 (CDT)
Date: Sat, 27 Jul 2002 11:58:10 -0500
To: lojban-list@lojban.org
Subject: Re: [lojban] Re: Dictionary software--Unicode, please
Message-ID: <20020727165810.GA9771@allusion.net>
References: <20020727011618.GA1045@allusion.net> <Pine.GSO.4.33.0207271637001.18245-100000@jeeves.stud.ntnu.no>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp"
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.33.0207271637001.18245-100000@jeeves.stud.ntnu.no>
User-Agent: Mutt/1.4i
X-archive-position: 327
X-ecartis-version: Ecartis v1.0.0
Sender: lojban-list-bounce@lojban.org
Errors-to: lojban-list-bounce@lojban.org
X-original-sender: fracture@allusion.net
Precedence: bulk
X-list: lojban-list
X-eGroups-From: Jordan DeLong <fracture@allusion.net>
From: Jordan DeLong <lojban-out@lojban.org>
Reply-To: fracture@allusion.net
X-Yahoo-Group-Post: member; u=116389790
X-Yahoo-Profile: lojban_out

--17pEHd4RhPHOinZp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Jul 27, 2002 at 04:43:05PM +0200, Arnt Richard Johansen wrote:
> On Fri, 26 Jul 2002, Jordan DeLong wrote:
>=20
> > Various allowed IPA spellings should be able to be generated from
> > the lojban spelling, correct? People adding words shouldn't need
> > to enter that i'd imagine.
>=20
> I think it is unnecessary to print IPA descriptions after each and every
> entry in the dictionary. But it might be a good idea to clarify with IPA
> in cases where some more obscure pronunciation rules take effect. For
> example, should the hypothetical name "kuias." be pronounced [kwI.As] or
> [kujas]? If "kuias." were really a name, people should be able to look i=
t
> up in a dictionary instead of working through the necessary chapters of
> CLL.

Shouldn't it be spelled ``ku,ias.'' xor ``kui,as.''? Or are there some
sort of default rule if someone leaves out the commas?

> Another case is that a good dictionary should have an appendix (a
> prependix?) which give most or all pronunciation rules.

This would be a pretty short thing for lojban :P There aren't very
many such rules.

--=20
Jordan DeLong
fracture@allusion.net


--17pEHd4RhPHOinZp
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)

iD8DBQE9QtEiDrrilS51AZ8RAh/TAJ9/AFxi/HiW5eko89Uf0ZkUQLFO9ACeKhtq
jqHVhbMxq0eBcBm5j1lbnu0=
=PGNo
-----END PGP SIGNATURE-----

--17pEHd4RhPHOinZp--

