From 3SbK4SwoJBgAleos.molasgmail.comlojbangooglegroups.com@groups.bounces.google.com Sun Apr 04 08:38:12 2010 Received: from mail-yw0-f160.google.com ([209.85.211.160]) by chain.digitalkingdom.org with esmtp (Exim 4.71) (envelope-from <3SbK4SwoJBgAleos.molasgmail.comlojbangooglegroups.com@groups.bounces.google.com>) id 1NyRtm-0007tK-OF for lojban-list-archive@lojban.org; Sun, 04 Apr 2010 08:38:11 -0700 Received: by ywh32 with SMTP id 32sf3773316ywh.28 for ; Sun, 04 Apr 2010 08:38:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:received:x-beenthere:received:received:received :received:received-spf:received:received:received:message-id:date :from:user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type:x-original-authentication-results :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:x-thread-url:x-message-url:sender :list-subscribe:list-unsubscribe; bh=Mb++/yppMj1/f4C4fFcs4dsYaThw/uNb7roMuQwsCjg=; b=Ne1C/EDW7t8BV7eSzqKRwRxpzSgQ9ZXn8lpJ5LjSYTSOMx4MweUKM1X184YHSiN3lg pm/crsTz6bmjWZOn84xal6TVm/uQJUxJlYwsL8jn9B+ai14kJJLL8naxQYyl1ptRSNwv kIrBLjyWKNRpiKZ/wmc7ITwwyQhqXzKuMSqzc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:message-id:date:from:user-agent :mime-version:to:subject:references:in-reply-to:x-enigmail-version :content-type:x-original-authentication-results:x-original-sender :reply-to:precedence:mailing-list:list-id:list-post:list-help :list-archive:x-thread-url:x-message-url:sender:list-subscribe :list-unsubscribe; b=YRku+Euobhs1DQdDM9bipPTno322D89vM28pj9h3rLarjl9S36Hh4oUZvMHQ0E3LMR Pn1/WFUhnjXlEaTrX+maaXQhEEvBqIT0lCYyb5LCSqq47DvzVbhOwM5pPzR6WXxFrmtU 94jWSl+Ii/ErAmLl6r+HF8i5C0wst8Gjmt8yE= Received: by 10.151.33.3 with SMTP id l3mr198882ybj.51.1270395465972; Sun, 04 Apr 2010 08:37:45 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.90.216.14 with SMTP id o14ls125056agg.5.p; Sun, 04 Apr 2010 08:37:44 -0700 (PDT) Received: by 10.91.11.27 with SMTP id o27mr953582agi.0.1270395464231; Sun, 04 Apr 2010 08:37:44 -0700 (PDT) Received: by 10.91.11.27 with SMTP id o27mr953579agi.0.1270395464047; Sun, 04 Apr 2010 08:37:44 -0700 (PDT) Received: from mail-gx0-f221.google.com (mail-gx0-f221.google.com [209.85.217.221]) by gmr-mx.google.com with ESMTP id 19si232836yxe.15.2010.04.04.08.37.43; Sun, 04 Apr 2010 08:37:43 -0700 (PDT) Received-SPF: pass (google.com: domain of leos.molas@gmail.com designates 209.85.217.221 as permitted sender) client-ip=209.85.217.221; Received: by gxk21 with SMTP id 21so2404484gxk.2 for ; Sun, 04 Apr 2010 08:37:42 -0700 (PDT) Received: by 10.150.141.10 with SMTP id o10mr4202045ybd.311.1270395462860; Sun, 04 Apr 2010 08:37:42 -0700 (PDT) Received: from [127.0.0.1] ([190.97.37.224]) by mx.google.com with ESMTPS id 4sm3014319ywd.58.2010.04.04.08.37.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 04 Apr 2010 08:37:42 -0700 (PDT) Message-ID: <4BB8B24F.3080101@gmail.com> Date: Sun, 04 Apr 2010 12:37:51 -0300 From: Leo Molas User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-AR; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: lojban@googlegroups.com Subject: Re: [lojban] Currency units References: <4BB7D709.1050007@gmail.com> In-Reply-To: X-Enigmail-Version: 1.0.1 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig345641781BC8B0208A90622D" X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of leos.molas@gmail.com designates 209.85.217.221 as permitted sender) smtp.mail=leos.molas@gmail.com; dkim=pass (test mode) header.i=@gmail.com X-Original-Sender: leos.molas@gmail.com Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: X-Thread-Url: http://groups.google.com/group/lojban/t/39f98ae3f0b3d959 X-Message-Url: http://groups.google.com/group/lojban/msg/b3e319c675c86cd9 Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig345641781BC8B0208A90622D Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Oren said: > I like it because > * it coins meaningful words (you know by the rafsi what it is) > * it coins words rather uniformly, about as 'neutral' as you can get > * it defers difficult distractions, like international standards, to > a larger, more accountable and qualified decision-making body >=20 > and also > * it's automated > * the script is 1KB >=20 > co'o mi'e korbi Thanks :) El 04/04/2010 11:28 a.m., Jorge Llamb=EDas escribi=F3: > On Sat, Apr 3, 2010 at 11:43 PM, komfo,amonan w= rote: >> >> I find myself vehemently opposed to these proposals. Some of the reaso= ns >> I've stated earlier in this or another related thread, but to summariz= e. >=20 > I will make a comment for each of the reasons, but only one of them > (number 2) seems like an actual reason to oppose the proposal. All the > others seem at most like reasons to remain indifferent. >=20 >> 1) There is cultural bias all over the language. Whatever bias is perc= eived >> as a result of autonymous vocabulary creation isn't IMHO much of a big= deal >> in comparison. >=20 > Personally, I would agree with that. I wouldn't put cultural > neutrality as the main advantage of making use of the ISO codes to > create fu'ivla, even though this was what started the idea.. Just > forget about cultural neutrality for a minute, is the use of ISO codes > to make fu'ivla still a bad idea? I didn't noticed other points in the language with cultural bias... that's an awful thing, and it should be removed, only if it is possible. But it's true this method is beyond the cultural problem. We have the opportunity to coin uniformly words for several areas, without much work.= >=20 >> 2) The ISO approach yields hundreds of words which are to me frustrati= ngly >> similar. >=20 > This is the only one that sounds like an actual reason to me. >=20 > But I'm not sure how valid it is. Of course, if you see an > alphabetical list of all of them together they will look very similar, > but in practice you would be unlikely to be using more than a few at a > time. >=20 > Consider for example: >=20 > gugde'i'e: x1 is the country with ISO code 'IE' (Ireland) > gugde'isu: x1 is the country with ISO code 'IS' (Iceland) > gugdesuzu: x1 is the country with ISO code 'SZ' (Swaziland) >=20 > Both the suffix -land in English and the prefix gugde- in the fu'ivla > give you a hint that it's the name of a country. > The difference in the fu'ivla is actually greater than the difference > between "Ireland" and "Iceland" in English. >=20 > Of course, not that many country names in English use the suffix > -land, but I think in Chinese most country names do use the same > sufffix. (And lujvo ending in "-gu'e" are also quite frequent). This is actually ugly to me too. However, I believe what xorxes said: they are awful in a list. It's unlikely to see a book of geography (for example) with few of this in an only paragraph. Moreover, they can live among other fu'ivla. So, I think this ISO fu'ivla shall be used in scientific writings, or when you are a person that don't use that word too much. But when is your country (or language or currency), or you're familiar with it (because your parents are from there), perhaps you'll be more comfortable with a autonym fu'ivla. And, finally, they are easy to remember. This may seem a fraud, but it's because you only need to remember two or three letters, and usually those letters will resemble the name of the country; with the letters, you build the fu'ivla. >=20 >> 3) The ISO approach can't help you with defunct countries, so the Inca= >> Empire will presumably remain {la tauantinsuius}. >=20 > So what? Nobody is saying that every single fu'ivla ever will have to > be based on an ISO code. All the proposal does is assign a fu'ivla to > each ISO code. There is nothing wrong in not having a fu'ivla for that; if you need it, and it doesn't exists, you coin it. >=20 >> 4) The ISO approach can't help you with ethnicities, so a Buryat will >> presumably be {*prenrburiada} or {*se natmrburiada} or {*burdiada}, wh= ile >> the Buryat language will carry an ISO code. >=20 > Again, so what? >=20 > banbu'u'a: x1 is the language with ISO code 'bua' (Buryat (generic)) > banbuxu'u: x1 is the language with ISO code 'bxu' (China Buriat) > banbuxumu: x1 is the language with ISO code 'bxm' (Mongolia Buriat) > banbuxuru: x1 is the language with ISO code 'bxr' (Russia Buriat) >=20 > If you wanted to, you could use the language code 'bua' to form > nairbu'u'a for the Buryat ethnic group, but that's outside the scope > of the proposal. The approach is not meant to provide a method for > creating every single fu'ivla ever, it is just a method for creating > fu'ivla out of ISO codes, nothing more than that. >=20 > And if you do happen to like something like 'bangrburiada', there is > nothing to stop the two forms from coexisting: >=20 > banbu'u'a: x1 is the language with ISO code 'bua' (Buryat (genetric)). > bangrburiada: x1 is the Buryat language. >=20 > This proposal does not use type-3 forms at all, so there won't be any > conflicts there. We where not talking about ethnicities. If someone need to talk about any of those, he should coin it. >=20 >> 5) The ISO presumably had different goals in developing the codes than= >> Lojbanistan does in developing vocabulary. >=20 > Again, so what? Why does it matter what the goals of ISO are. There is > a list of ISO codes. We might wish to have a convenient way of using > them as fu'ivla. That's all. >=20 >> I laud all the work y'all have put into generating this vocabulary. Le= o just >> asked for opinions, so I gave one. Yes, thanks :) >> >> I don't have enough time to devote to Lojban these days to generate 25= 0 >> autonymous words for languages & put them into jbovlaste, or even to d= ecide >> why they should be brivla rather than cmevla. Shrug. But it's a fascin= ating >> discussion. >=20 > It's actually 7704 language codes, not just 250. It's unlikely that > anyone would have the time or the desire to handcraft them one by one. >=20 > The ISO codes exist. It seems useful to make predicates out of them. > This proposal just gives a method that churns out reasonably looking > fu'ivla out of two letter or three letter codes. I don't really see > anything problematic with that. >=20 > A different question is whether you would actually use these words, > and in what contexts, but why oppose the concept? It's not as if the > method blocks a terribly big chunk of fu'ivla space. How many fu'ivla > are likely to be otherwise created with forms gugdeXXXX or banXXXXXX? >=20 > mu'o mi'e xorxes >=20 About this, I forgot to mention I asked first if people like the idea to know if this was actually going to be used. And if people oppose the idea, to know if it is just plain wrong, and shouldn't be done; and to continue discussing this. There might be people who won't like it. That's not a bad thing; just don't use this ugly fu'ivla. That might be the solution for many allegations. But if your guts tell you this is actually wrong, let us know why, so we can correct them. mu'o mi'e .leos. --=20 My lojban journal: http://learninglojban.wordpress.com My personal blog: http://leomolas.tumblr.com --------------enig345641781BC8B0208A90622D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLuLJVAAoJEGPqAjdF26uER/sH/02KsWVi/P42BurSXvvxIn6x OKST3WHKUAwJd1reOOXEbFkJgCRFAnMnCB1K65vjJyyTirVjles9ez6GnMYAPRg8 ZPwqyQlqnQFw8vW8yaiy+URnXejLQT+ACC/edynWCyOBCkQ66VSjpsBtaj7wf1yi KxyHhiR05ZdgtdQfGIQwjOCPo0jsh1pR58TMp8nSDpMdjrhKQiLly0xUquAZ35hX WJg7P1Ts4sHpQvcy1zoSqQ8Tz7ZZrwPgj4cX8gQdUo9l5JTpYGoa8xXbdqq265a0 2h/2OE3DLWZ4fw4FSgr7nWMxvwS7zJDtYqxDLHDDWChLgX+eTNmIbL5lYLN8hT8= =ytDx -----END PGP SIGNATURE----- --------------enig345641781BC8B0208A90622D--