Received: from mail-la0-f55.google.com ([209.85.215.55]:35583) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1U6jdN-0003Bp-5G; Sat, 16 Feb 2013 07:25:17 -0800 Received: by mail-la0-f55.google.com with SMTP id fr10sf1214495lab.10 for ; Sat, 16 Feb 2013 07:24:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received:x-received:received-spf:date:from :to:subject:message-id:references:mime-version:content-type :content-disposition:in-reply-to:user-agent: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; bh=SLB/fBd/lMSRr7DvgOAw2viU3QmZ0oVAE56cjlaAR40=; b=ULFd3/PUYjSlAaReyOOIDD1tqWwdfLnFnwxs0AMOh2TXZkgNSOfnZN5kzvJwDYxACx 260389EBkH6y+NpQpij2dkDIerMjOY5j/LNHQaFrhegsCZnSKyt+1OZnNmTK261hZRg1 18O/QQaqFwT5uRQygL9N8kUF/OrvGfm9tr3aBcIRD5hlJLZshJ64R7e++f2f6lfDCK5e ib8JtOyAbq3988Vxe9q96Sh5xn1jyr32ZHnnCi7qC8sEYHdPjpIeTAL2KreVmdPKzpJB TZ8inf9GKsF6neQ8h4K70IH3U58BiBWeHyu5U1gGgVMkwMXuRkBMG0iN22D1KlC/v55q 95tA== X-Received: by 10.181.11.164 with SMTP id ej4mr431189wid.4.1361028292833; Sat, 16 Feb 2013 07:24:52 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.180.20.111 with SMTP id m15ls231315wie.38.gmail; Sat, 16 Feb 2013 07:24:51 -0800 (PST) X-Received: by 10.14.220.131 with SMTP id o3mr6893312eep.3.1361028291327; Sat, 16 Feb 2013 07:24:51 -0800 (PST) X-Received: by 10.14.220.131 with SMTP id o3mr6893310eep.3.1361028291316; Sat, 16 Feb 2013 07:24:51 -0800 (PST) Received: from dd17822.kasserver.com (dd17822.kasserver.com. [85.13.138.119]) by gmr-mx.google.com with ESMTPS id 6si10347168eej.0.2013.02.16.07.24.51 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 16 Feb 2013 07:24:51 -0800 (PST) Received-SPF: neutral (google.com: 85.13.138.119 is neither permitted nor denied by best guess record for domain of me@v4hn.de) client-ip=85.13.138.119; Received: from samsa (brln-4dbadcfd.pool.mediaWays.net [77.186.220.253]) by dd17822.kasserver.com (Postfix) with ESMTPA id 8B65486509E for ; Sat, 16 Feb 2013 16:24:50 +0100 (CET) Date: Sat, 16 Feb 2013 16:24:50 +0100 From: v4hn To: lojban@googlegroups.com Subject: Re: [lojban] srana zo za'o Message-ID: <20130216152450.GE10126@samsa.fritz.box> References: <20130216005511.GB10126@samsa.fritz.box> <1360984797.53603.YahooMailNeo@web184402.mail.bf1.yahoo.com> <20130216115553.GD10126@samsa.fritz.box> <1361026438.11748.YahooMailNeo@web184403.mail.bf1.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="n+lFg1Zro7sl44OB" Content-Disposition: inline In-Reply-To: <1361026438.11748.YahooMailNeo@web184403.mail.bf1.yahoo.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Original-Sender: me@v4hn.de X-Original-Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.13.138.119 is neither permitted nor denied by best guess record for domain of me@v4hn.de) smtp.mail=me@v4hn.de 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: , X-Spam-Score: -0.0 (/) X-Spam_score: -0.0 X-Spam_score_int: 0 X-Spam_bar: / --n+lFg1Zro7sl44OB Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Feb 16, 2013 at 06:53:58AM -0800, John E Clifford wrote: > From: v4hn > To: lojban@googlegroups.com=20 > Sent: Saturday, February 16, 2013 5:55 AM > Subject: Re: [lojban] srana zo za'o > =20 > How would you utter "ko'a keeps on running after reaching one mile" > in your two miles example? >=20 > It will depend.=C2=A0 If the aim was to run two miles and the > expectation was that he would do it, then {ca'o} is probably > appropriate but not {za'o}, since he is still running the two miles. > But if you expected him to fall out after a mile, {za'o} might be > appropriate, since your expectation provides a (not quite) natural > stopping point.=C2=A0 You can play a lot with nuance here.=20 ok > Also how would you translate the {na za'o surla kakne} sentence in snow w= hite > without za'o? ("could not continue to relax") >=20 > This seems weird to me: > Therefore it is not the case that the prince kept on being able > to relax day and night.=C2=A0 Presumably, he could relax if the crisis mo= ment > were past, so keeping relaxing seems to mean he was doing it earlier, > which doesn't seem right. I don't think so? > So, not being able to relax is appropriate before > the crisis point and thus not a matter of {za'o} before that point. > So, I think the {za'o} is probably a mistake, but the scope problems > still bother me a bit. ok, we are talking about the queen here, not the prince. The context of this sentence is as follows: The queen is told that snow white is more beautiful than her and becomes more and more jealous of her. _This_ is the reason why the queen can not relax anymore (neither at day nor at night). Could you provide a translation that seems fitting to you, please? > > I just think this ending point is something that wasn't there before the > > translation and I wonder how to translate these sentences without > > introducing this point. >=20 > Usually, probably {ca'o}or nothing. Hm, maybe my definition of "ending point" is just a bit to narrow. I just wanted to point out that the marked point does not necessarily mark and end, but maybe context can probably bend that definition quite a lot. You're right, if there's no need to mark /any/ point as special {ca'o} is fine... But then, I'm unsure about what "still" indicates in english... Maybe it really matches {za'o} roughly? v4hn --n+lFg1Zro7sl44OB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlEfpMEACgkQMBKLZs4+wjwJegCeKhp4oP6PfORvEf3+OnfVLy0T VOYAoJN5Sm4XuDF7RxHiufAeVyV35na8 =34fo -----END PGP SIGNATURE----- --n+lFg1Zro7sl44OB--