From jjllambias@gmail.com Fri Jul 22 08:37:14 2005 Received: with ECARTIS (v1.0.0; list llg-members); Fri, 22 Jul 2005 08:37:14 -0700 (PDT) Received: from wproxy.gmail.com ([64.233.184.200]) by chain.digitalkingdom.org with esmtp (Exim 4.52) id 1DvzaG-0001EI-SF for llg-members@lojban.org; Fri, 22 Jul 2005 08:37:12 -0700 Received: by wproxy.gmail.com with SMTP id i23so369260wra for ; Fri, 22 Jul 2005 08:37:06 -0700 (PDT) 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=XvhC+M3i/VmuPAsACGKT9bW/swsl5/4pqAcObGN6BzoOalJjMKu1v2Rbc28tXcNkv1SLpaGKIvjYXJGJXBXXWp/mlBrsjEl1Ls2VusT21X6zOXtC9yGXBAy1e8HQsxAlSdZDtFx+8WM9tI60quLgFhBZIm16UJQOFauREGcliLs= Received: by 10.54.52.55 with SMTP id z55mr1299408wrz; Fri, 22 Jul 2005 08:36:40 -0700 (PDT) Received: by 10.54.68.12 with HTTP; Fri, 22 Jul 2005 08:36:40 -0700 (PDT) Message-ID: <925d1756050722083624970a05@mail.gmail.com> Date: Fri, 22 Jul 2005 12:36:40 -0300 From: =?ISO-8859-1?Q?Jorge_Llamb=EDas?= To: llg-members@lojban.org Subject: [llg-members] Re: Supplicatory Model: papri In-Reply-To: <42DB5132.1040507@lojban.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by Ecartis Content-Disposition: inline References: <20050716010140.GU2444@chain.digitalkingdom.org> <42D95380.802@lojban.org> <20050718044439.GE2444@chain.digitalkingdom.org> <42DB5132.1040507@lojban.org> X-Spam-Score: -2.5 (--) X-archive-position: 31 X-ecartis-version: Ecartis v1.0.0 Sender: llg-members-bounce@lojban.org Errors-to: llg-members-bounce@lojban.org X-original-sender: jjllambias@gmail.com Precedence: bulk Reply-to: llg-members@lojban.org X-list: llg-members Some comments: 1- I don't see why the "nonphysical" analogue of a paper page would have to be a screenful of text. Although that is a possible analogue, it is not necessarily the best one. When one scrolls the page up or down, it is the same page that moves on the screen, we don't see it as a new page with a different content. The screenshot has changed, but the page is the same. In many cases the full page just doesn't fit in the screen, so we only see one part of it, but if we can move around it continuously with the cursor, (much as we could point with a finger to a place on a paper page and move continuously around it) we remain on the same page. In this case, we "turn" the page when we click on "next page" or "previous page", for example, not when we move one screen up or down. The nature of webpages is such that, unlike paper pages, we can usually fit a whole document in one of them. They are much more capacious than paper pages, that's all. 2- A given webpage as papri can belong to different selpapri. Paper pages are more limited, they usually belong to a single selpapri. There are special cases when you can remove from or add paper pages to a selpapri, or move them from one selpapri to another, but usually they stay put. Webpages are more flexible, they can be "bound" together more easily and it is not always clear where a selpapri ends, but I don't see any problem for example in talking about {lo papri be la lojban.org.}, "the webpages of lojban.org", or {lo papri be la ueb} for pages of the Web in general. 3- If we are going to use {tcana} for "webpage", its definition and keywords neeed adjustment. As it is, it would be very confusing, because "station" already has another use in computer parlance. I find {papri} more apt and less confusing than {tcana}. mu'o mi'e xorxes