Received: from mail-qy0-f189.google.com ([209.85.216.189]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1QDoHZ-00080q-Dz; Sat, 23 Apr 2011 18:38:45 -0700 Received: by qyk36 with SMTP id 36sf5161491qyk.16 for ; Sat, 23 Apr 2011 18:38:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:x-beenthere:received-spf:mime-version:date :message-id:subject:from: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=HhG/uWhYMxmTaBOM8CDCyIdLqIugrhcC+MuJr19TWMU=; b=MgkfGDusWqtpHJoXoyqMI4xPhXPjEW1Xsa3JBQeyYdoSfQxsHa5ihdM/e+9dkbv0m8 ozrmfgMVUCNuize5a51SHpB98GfGyvoOJCxujAC1fSmsxaNENBid/8FYSexUPdCUJWfJ dkams28gIIDm9G/+GDNm+rlzWMcAEJqUTCnJI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:date:message-id:subject:from :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; b=IbsOsu27RIR8ZYYG4MWP8Ympmefi21cFbCbonU+Je/hVRy2ZvngB/dSmyLWIcsU5Zb wieYYNUAL9HZ+jFUL8ySJSPVorvyvEo+vokbekSDYIz6XYkk/17hxcTKh/C7olKe41a5 s+SJPQp0Tl9HqKmuruXqSLQE/Mwj5Gi62s+5M= Received: by 10.229.43.98 with SMTP id v34mr401738qce.36.1303609110855; Sat, 23 Apr 2011 18:38:30 -0700 (PDT) X-BeenThere: lojban-beginners@googlegroups.com Received: by 10.229.205.76 with SMTP id fp12ls1351855qcb.0.gmail; Sat, 23 Apr 2011 18:38:30 -0700 (PDT) Received: by 10.229.234.67 with SMTP id kb3mr180440qcb.24.1303609110067; Sat, 23 Apr 2011 18:38:30 -0700 (PDT) Received: by 10.229.234.67 with SMTP id kb3mr180439qcb.24.1303609110049; Sat, 23 Apr 2011 18:38:30 -0700 (PDT) Received: from mail-vw0-f49.google.com (mail-vw0-f49.google.com [209.85.212.49]) by gmr-mx.google.com with ESMTPS id n4si908881qcg.15.2011.04.23.18.38.28 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 23 Apr 2011 18:38:29 -0700 (PDT) Received-SPF: pass (google.com: domain of skaryzgik@gmail.com designates 209.85.212.49 as permitted sender) client-ip=209.85.212.49; Received: by vws8 with SMTP id 8so1596085vws.8 for ; Sat, 23 Apr 2011 18:38:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.98.5 with SMTP id ee5mr4162646vdb.200.1303609108680; Sat, 23 Apr 2011 18:38:28 -0700 (PDT) Received: by 10.52.161.97 with HTTP; Sat, 23 Apr 2011 18:38:28 -0700 (PDT) Date: Sat, 23 Apr 2011 20:38:28 -0500 Message-ID: Subject: [lojban-beginners] letter(as in note)/email endings? From: Marjorie Scherf To: lojban-beginners@googlegroups.com X-Original-Sender: skaryzgik@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of skaryzgik@gmail.com designates 209.85.212.49 as permitted sender) smtp.mail=skaryzgik@gmail.com; dkim=pass (test mode) header.i=@gmail.com Reply-To: lojban-beginners@googlegroups.com Precedence: list Mailing-list: list lojban-beginners@googlegroups.com; contact lojban-beginners+owners@googlegroups.com List-ID: X-Google-Group-Id: 300742228892 List-Post: , List-Help: , List-Archive: Sender: lojban-beginners@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=20cf307f34a6d94e7b04a1a025bf Content-Length: 2948 --20cf307f34a6d94e7b04a1a025bf Content-Type: text/plain; charset=ISO-8859-1 It appears that common practice for ending emails is to have {mu'o mi'e _______ } where "________" is the name, but I recently noticed an email signature in which the writer used {mi'e ________ mu'o} which, once I thought about it, seems to make more sense. If {mu'o} is supposed to signal the end of the transmission, anything after that would be disregarded, and the self-introduction conventionally put at the end of emails and letters, if put after the {mu'o} instead of before, would seem to be excluded from the message. So when I actually think about it, it seems like {mi'e _________ mu'o} would make more sense than the more common {mu'o mi'e ________ } I more commonly see. I'm wondering whether my friend has has an insight missed by the majority of the most vocal lojbanists, or if there is some reason for the common form that I have not yet considered. .i mi'e la .jdakrat.skaryzgik. mu'o -- You received this message because you are subscribed to the Google Groups "Lojban Beginners" group. To post to this group, send email to lojban-beginners@googlegroups.com. To unsubscribe from this group, send email to lojban-beginners+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban-beginners?hl=en. --20cf307f34a6d94e7b04a1a025bf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable It appears that common practice for ending emails is to have {mu'o mi&#= 39;e _______ } =A0where "________" is the name, but I recently no= ticed an email signature in which the writer used {mi'e ________ mu'= ;o} which, once I thought about it, seems to make more sense. If {mu'o}= is supposed to signal the end of the transmission, anything after that wou= ld be disregarded, and the self-introduction conventionally put at the end = of emails and letters, if put after the {mu'o} instead of before, would= seem to be excluded from the message. So when I actually think about it, i= t seems like {mi'e _________ mu'o} would make more sense than the m= ore common {mu'o mi'e ________ } I more commonly see. I'm wonde= ring whether my friend has has an insight missed by the majority of the mos= t=A0vocal lojbanists, or if there is some reason for the common form that I= have not yet considered.

.i mi'e la .jdakrat.skaryzgik. mu'o

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