From lee@piclab.com Fri Jan 10 11:46:58 2003 Return-Path: X-Sender: lee@piclab.com X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_2_3_0); 10 Jan 2003 19:46:55 -0000 Received: (qmail 85345 invoked from network); 10 Jan 2003 19:46:54 -0000 Received: from unknown (66.218.66.218) by m9.grp.scd.yahoo.com with QMQP; 10 Jan 2003 19:46:54 -0000 Received: from unknown (HELO sanantonio.piclab.com) (66.216.68.43) by mta3.grp.scd.yahoo.com with SMTP; 10 Jan 2003 19:46:57 -0000 Received: (qmail 12294 invoked by uid 502); 10 Jan 2003 19:47:43 -0000 Date: Fri, 10 Jan 2003 13:47:43 -0600 To: lojban@yahoogroups.com Subject: Re: [lojban] Re: open and save] Message-ID: <20030110194743.GA12287@piclab.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i X-URL: http://www.piclab.com/lee/ From: Lee Daniel Crocker X-Yahoo-Group-Post: member; u=1436760 X-Yahoo-Profile: bowtie95841 > (robin ): > > Do we really want to continue the metaphor? Isn't there something else > which would represent the state of an open file (i.e. that it is > currently being read from / written to)? "Active" springs to mind, > except that unless it's an executable, it's really more passive than active. Seems to me the right metaphor for opening/closing a file is {kalri} and {ganlo}: we're not opening a container so much as we're being granted access (where the "door" is access rights, etc.), allowing information to flow between program and disk. That makes the button labels {kargau} and {ga'ogau} (perhaps with {pe'a} if desired). -- Lee Daniel Crocker "All inventions or works of authorship original to me, herein and past, are placed irrevocably in the public domain, and may be used or modified for any purpose, without permission, attribution, or notification."--LDC