Received: from mail-ob0-f192.google.com ([209.85.214.192]:33522) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1VzsSu-0006F1-OQ for lojban-list-archive@lojban.org; Sun, 05 Jan 2014 10:30:33 -0800 Received: by mail-ob0-f192.google.com with SMTP id uy5sf4143178obc.19 for ; Sun, 05 Jan 2014 10:30:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe:content-type; bh=2H1W0QN1vPfPxR8RvL177/wyapSAjPKe2d/l4dGyHCA=; b=rmW0UYjKx0QcemkcJjgvx+OFzuuKXQ1nC/xIXAdP00KCd8b9Cny26MzMP+JhQqeTry 3d73vjhbqUNkfTf1dHtGBCuGXtfumNOrc2d2d4ylDihdItJrEmlzpmm4S2iv7DrzzubE Pau+7RwjsIHScp3BwTRuAH4mxchHBF7Ipz56uvJpSKLV8dFdC6jMFNWESxuaAgDUWhrX hHWjr/UL/AosOp3ft0rBNNFq6UahpXm4xtGfHXrmbzdVq7aMxqapMOb58EW/1StzpUGJ EC4lLz/2/CPa4NcKxRWi8BMOHBGUHisilhM1jjzzipVCwS+Vyne1LeTBiS/yqLGL6AW8 IFHA== X-Received: by 10.182.231.170 with SMTP id th10mr273779obc.0.1388946617775; Sun, 05 Jan 2014 10:30:17 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.182.181.6 with SMTP id ds6ls2204461obc.77.gmail; Sun, 05 Jan 2014 10:30:17 -0800 (PST) X-Received: by 10.182.34.169 with SMTP id a9mr9912084obj.49.1388946617542; Sun, 05 Jan 2014 10:30:17 -0800 (PST) Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [2607:f8b0:4001:c05::229]) by gmr-mx.google.com with ESMTPS id o30si3003734yhn.1.2014.01.05.10.30.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 05 Jan 2014 10:30:17 -0800 (PST) Received-SPF: pass (google.com: domain of felipeg.assis@gmail.com designates 2607:f8b0:4001:c05::229 as permitted sender) client-ip=2607:f8b0:4001:c05::229; Received: by mail-ig0-f169.google.com with SMTP id hk11so5414267igb.0 for ; Sun, 05 Jan 2014 10:30:17 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.51.15.130 with SMTP id fo2mr15003341igd.28.1388946616992; Sun, 05 Jan 2014 10:30:16 -0800 (PST) Received: by 10.64.223.166 with HTTP; Sun, 5 Jan 2014 10:30:16 -0800 (PST) In-Reply-To: <52C9939B.2070705@gmx.de> References: <52C9939B.2070705@gmx.de> Date: Sun, 5 Jan 2014 16:30:16 -0200 Message-ID: Subject: Re: [lojban] [oz] Assorted translation questions From: =?ISO-8859-1?Q?Felipe_Gon=E7alves_Assis?= To: lojban@googlegroups.com X-Original-Sender: felipeg.assis@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of felipeg.assis@gmail.com designates 2607:f8b0:4001:c05::229 as permitted sender) smtp.mail=felipeg.assis@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=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=001a1134b50eb7cbbf04ef3d5521 X-Spam-Score: 0.0 (/) X-Spam_score: 0.0 X-Spam_score_int: 0 X-Spam_bar: / --001a1134b50eb7cbbf04ef3d5521 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable ki'e selpa'i Just one more point about item 1: On 5 January 2014 14:17, selpa'i wrote: > > Chapter 1 >> >> 1. {lo zd=C4=81ni cu k=C4=81ndi gi'e gr=C5=B3si kei du'i tu'a ro dr=C4= =81ta}; >> >> >> Why the {tu'a}? To me, it is quite normal for dunli1 and dunli2 to be >> simple objects. >> > > This topic is one of my specialties. :D > > I use BAI in such a way that whenever their source predicate has a sumti > place that could integrate the main bridi, then they will do so (I > explained the same thing in the {to'e ri'a} thread). > > {du'i} is one such BAI. I define it thus: > > broda du'i X ~=3D X dunli lo su'u broda > > So, I would say, for example: > > (1) do bajra du'i lo nu lo tirxu cu bajra > "Your run is like that of a tiger." > > It is seldom the case that a concrete object is {dunli} to an abstraction= , > although it is not impossible. But usually, replacing the X in the above > equation with a concrete object will create "non-sense". But we can use > {tu'a X} when we don't want to specify the full abstraction, or when it's > obvious. > > (2) do bajra du'i tu'a lo tirxu > "You run like a tiger [runs]" > > The expansion of this {tu'a X} is almost always {lo nu X no'a}, which > correspsonds to the English in []-brackets in (2). > > Fair enough. It is a nice idea. I personally don't treat the event described by a bridi so much more specially than its other constituents. As you seem to imply, the main bridi can't always fit a sumti place from the source predicate; {bau} comes to my mind. In my style, two important constituents of the main bridi would fill sumti places of the source predicate, that is, lo zdani and lo ka kandi gi'e grusi. This is not true of your tiger example, where the dunli3 couldn't be exactly lo ka bajra, and admittedly there might be good reason to compare the events instead of the runners. In any case, I will give your idea some more consideration through future experience. By the way, it just occurred to me that the original sentence should have a {vau} instead of the {kei}, right? Putting it on the errata. mu'o mi'e .asiz. --=20 You received this message because you are subscribed to the Google Groups "= lojban" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban. For more options, visit https://groups.google.com/groups/opt_out. --001a1134b50eb7cbbf04ef3d5521 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
ki'e selpa'i

Just one more point= about item 1:


On 5 January 2014 14:17, selpa'i <seladwa@gmx.de> wrot= e:

Chapter 1

1. {lo zd=C4=81ni cu k=C4=81ndi gi'e gr=C5=B3si kei du'i tu'a r= o dr=C4=81ta};


Why the {tu'a}? To me, it is quite normal for dunli1 and dunli2 to be simple objects.

This topic is one of my specialties. :D

I use BAI in such a way that whenever their source predicate has a sumti pl= ace that could integrate the main bridi, then they will do so (I explained = the same thing in the {to'e ri'a} thread).

{du'i} is one such BAI. I define it thus:

broda du'i X ~=3D X dunli lo su'u broda

So, I would say, for example:

=C2=A0 =C2=A0(1) do bajra du'i lo nu lo tirxu cu bajra
=C2=A0 =C2=A0 =C2=A0 =C2=A0"Your run is like that of a tiger."
It is seldom the case that a concrete object is {dunli} to an abstraction, = although it is not impossible. But usually, replacing the X in the above eq= uation with a concrete object will create "non-sense". But we can= use {tu'a X} when we don't want to specify the full abstraction, o= r when it's obvious.

=C2=A0 =C2=A0(2) do bajra du'i tu'a lo tirxu
=C2=A0 =C2=A0 =C2=A0 =C2=A0"You run like a tiger [runs]"

The expansion of this {tu'a X} is almost always {lo nu X no'a}, whi= ch correspsonds to the English in []-brackets in (2).


Fair enough. It is a nice idea.
I personally don't treat the event described by a bridi so much more s= pecially than its other constituents. As you seem to imply, the main bridi = can't always fit a sumti place from the source predicate; {bau} comes t= o my mind.

In my style, two important constituents of the main bridi wo= uld fill sumti places of the source predicate, that is, lo zdani and lo ka = kandi gi'e grusi. This is not true of your tiger example, where the dun= li3 couldn't be exactly lo ka bajra, and admittedly there might be good= reason to compare the events instead of the runners.

In any case, I will give your idea some more consideration through futu= re experience.


By the way, it just occurred to me tha= t the original sentence should have a {vau} instead of the {kei}, right? Pu= tting it on the errata.

mu'o
mi'e .asiz.

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http:= //groups.google.com/group/lojban.
For more options, visit https://groups.google.com/groups/opt_out.
--001a1134b50eb7cbbf04ef3d5521--