Received: from mail-pb0-f61.google.com ([209.85.160.61]:41974) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1THGe8-0000jL-Q9; Thu, 27 Sep 2012 09:09:15 -0700 Received: by pbbrp8 with SMTP id rp8sf2686991pbb.16 for ; Thu, 27 Sep 2012 09:08:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-beenthere:received-spf:mime-version:from:date:message-id:subject :to:x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:x-google-group-id:list-post :list-help:list-archive:sender:list-subscribe:list-unsubscribe :content-type; bh=D2vcGzerwCV4oY/WvXk/aOutiAwTl+ZRA8/F53NWqjE=; b=qcSbLEJjW4gDxoST/EFfA6rVB9N7/1SCjHavP2aXkbWP8gqmT0hPwXfl24EmQh1a9V UfiVGvaO35CVRIDI+cpLKGFPTXZ5DzpzCWNN5nBcMxsDXFkAimQb/6WS0dGLt10QSkZl k6ZgpDVfl8zQnF605TvMe7rjt9zJO4zWe2JkVJ8S1HRdEhBzLCcUS333nZA7YHFDWwnY 1dI7EQrdhhfzZiCTWHXmwVdW3wu0+hWldnZn4bI0zfVXkaPGnhH1KLrbV9SFFFA5F6OU bTvjKJv6uwMiRW73LCVCU7bDOmLVRCPpBXxP/H/zhFGeSwdaemKRQIhWE/F3hhe0dvfD MlWw== Received: by 10.229.137.13 with SMTP id u13mr431402qct.6.1348762138086; Thu, 27 Sep 2012 09:08:58 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.229.178.10 with SMTP id bk10ls4432629qcb.3.gmail; Thu, 27 Sep 2012 09:08:57 -0700 (PDT) Received: by 10.59.10.42 with SMTP id dx10mr1262494ved.14.1348762137467; Thu, 27 Sep 2012 09:08:57 -0700 (PDT) Received: by 10.59.10.42 with SMTP id dx10mr1262493ved.14.1348762137455; Thu, 27 Sep 2012 09:08:57 -0700 (PDT) Received: from mail-vb0-f49.google.com (mail-vb0-f49.google.com [209.85.212.49]) by gmr-mx.google.com with ESMTPS id r14si357777vdu.1.2012.09.27.09.08.57 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 27 Sep 2012 09:08:57 -0700 (PDT) Received-SPF: pass (google.com: domain of nictytan@gmail.com designates 209.85.212.49 as permitted sender) client-ip=209.85.212.49; Received: by vbbfo1 with SMTP id fo1so2835748vbb.22 for ; Thu, 27 Sep 2012 09:08:57 -0700 (PDT) Received: by 10.52.35.116 with SMTP id g20mr1977328vdj.97.1348762137137; Thu, 27 Sep 2012 09:08:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.92.48 with HTTP; Thu, 27 Sep 2012 09:08:36 -0700 (PDT) From: Jacob Errington Date: Thu, 27 Sep 2012 09:08:36 -0700 Message-ID: Subject: [lojban] IP Addresses in Lojban To: lojban@googlegroups.com X-Original-Sender: nictytan@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of nictytan@gmail.com designates 209.85.212.49 as permitted sender) smtp.mail=nictytan@gmail.com; dkim=pass header.i=@gmail.com Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=20cf3079ba4812125304cab128e9 X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / --20cf3079ba4812125304cab128e9 Content-Type: text/plain; charset=ISO-8859-1 coi I don't see why numbers couldn't do this: e.g. li pareze pi'e no pi'e no pi'e pa Indicating a port could be done with {pi}: e.g. li pareze pi'e no pi'e no pi'e pa pi bino Also, in the same way that denpa bu colloquially refers to the dot, how about we let diklo bu refer to localhost? If so, we can attach a port to a non-number sumti referring to a URL like this: {li pi bino pe diklo bu} Otherwise, we can use a moi-based approach like this: {.i lo bino moi co me diklo bu moi} would probably convey the right meaning, given that the listener knows what diklo bu refers to. Thoughts? .i mi'e la tsani mu'o -- You received this message because you are subscribed to the Google Groups "lojban" group. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en. --20cf3079ba4812125304cab128e9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable coi

I don't see why numbers couldn't do this:
e.g. li pareze pi'e no pi'e no pi'e pa
Indica= ting a port could be done with {pi}:
e.g. li pareze pi'e no p= i'e no pi'e pa pi bino

Also, in the same way that denpa bu colloquially refers= to the dot, how about we let diklo bu refer to localhost?

If so, we can attach a port to a non-number sumti referring to a U= RL like this:
{li pi bino pe diklo bu}
Otherwise, we can use a moi-based a= pproach like this:
{.i lo bino moi co me diklo bu moi} would prob= ably convey the right meaning, given that the listener knows what diklo bu = refers to.

Thoughts?

.i mi'e la tsani= mu'o

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com.
For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.
--20cf3079ba4812125304cab128e9--