Received: from mail-px0-f189.google.com ([209.85.212.189]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1PogZa-0004NK-JU; Sun, 13 Feb 2011 10:21:35 -0800 Received: by pxi19 with SMTP id 19sf2157247pxi.16 for ; Sun, 13 Feb 2011 10:21:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:mime-version:x-beenthere:received-spf:date :message-id:to:subject:from: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:content-transfer-encoding; bh=ChFQTZimAWgSixjc72V6LrDeq1/ap3z2U1hNPZAgjK4=; b=tGWWmVJsKRVOgXhhRkKqT3ZrG7Yws7e1+Ah6Cy8PcJVQh+yAZcs+Ee3uh3gyOV7k3v dKAlKudhm63VUscyvc0tqvn6g4Td3ADtAVZo6/4Z+LRSUJET0SHBI4mB9g1WyJIDRTwW cFR5B8qyA+xYWKClQ72NyoHdQ6J6jimC1CjVY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=mime-version:x-beenthere:received-spf:date:message-id:to:subject :from: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 :content-transfer-encoding; b=37Zy0DyWj3NjPjx8AtQ5V2XbqThbl8bB2VTz2/z1pI2Csk9AMR45Wz1/CNmUitW0yy gtGVfpJAgeFuVDNZepGWUbt6G31XsB5Us62g8YCvF2vFeVOchyOk/2RdV8QpJ9M1geAy lHANZ3Vbiim7rt4vw8DHhCrinJ6mqGB7O5OWQ= Received: by 10.142.218.21 with SMTP id q21mr209839wfg.10.1297621274550; Sun, 13 Feb 2011 10:21:14 -0800 (PST) MIME-Version: 1.0 X-BeenThere: bpfk-list@googlegroups.com Received: by 10.142.2.41 with SMTP id 41ls6012990wfb.0.p; Sun, 13 Feb 2011 10:21:13 -0800 (PST) Received: by 10.142.180.18 with SMTP id c18mr615064wff.28.1297621273836; Sun, 13 Feb 2011 10:21:13 -0800 (PST) Received: by 10.142.180.18 with SMTP id c18mr615063wff.28.1297621273757; Sun, 13 Feb 2011 10:21:13 -0800 (PST) Received: from chain.digitalkingdom.org (digitalkingdom.org [173.13.139.234]) by gmr-mx.google.com with ESMTPS id p40si2124610wfc.2.2011.02.13.10.21.12 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Feb 2011 10:21:12 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of nobody@digitalkingdom.org designates 173.13.139.234 as permitted sender) client-ip=173.13.139.234; Received: from nobody by chain.digitalkingdom.org with local (Exim 4.72) (envelope-from ) id 1PogZJ-0004N4-OY for bpfk-list@googlegroups.com; Sun, 13 Feb 2011 10:21:10 -0800 Received: from 128-177-28-49.ip.openhosting.com ([128.177.28.49] helo=oh-www1.lojban.org) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1PogZD-0004Me-0l for bpfk@lojban.org; Sun, 13 Feb 2011 10:21:09 -0800 Received: from www-data by oh-www1.lojban.org with local (Exim 4.72) (envelope-from ) id 1PogZB-0002PU-Qf for bpfk@lojban.org; Sun, 13 Feb 2011 13:21:01 -0500 Date: Sun, 13 Feb 2011 13:21:01 -0500 Message-Id: To: bpfk@lojban.org Subject: [bpfk] dag-cll git updates for Sun Feb 13 13:21:01 EST 2011 From: www-data X-Original-Sender: www-data@oh-www1.lojban.org X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of nobody@digitalkingdom.org designates 173.13.139.234 as permitted sender) smtp.mail=nobody@digitalkingdom.org Reply-To: bpfk-list@googlegroups.com Precedence: list Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: Sender: bpfk-list@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Content-Length: 21839 commit afe6ef9bae64918fd72fa51a20b255de2340ee2a Author: Robin Lee Powell Date: Sun Feb 13 09:46:38 2011 -0800 Fixed up some personal annoyance with [nmlry]-hypens. diff --git a/todocbook/4.xml b/todocbook/4.xml index 532ac4b..6f47353 100644 --- a/todocbook/4.xml +++ b/todocbook/4.xml @@ -943,59 +943,59 @@ lujvorecognizing lujvo formnumber of letters in lujvo form= consonant cluster requirement in lujvo formfinal letter of lujvosummary of form characteristics= As noted above, CVC-form rafsi cannot appear as th= e final rafsi in a lujvo, because all lujvo must end with one or two vowels= . As a brivla, a lujvo must also contain a consonant cluster within the fir= st five letters – this ensures that they cannot be mistaken for compo= und cmavo. Of course, all lujvo have at least six letters since they have t= wo or more rafsi, each at least three letters long; hence they cannot be co= nfused with gismu. lujvo formrequirements for hyphen insertion in = hyphen letterdefinition hyphensuse of Whe= n attaching two rafsi together, it may be necessary to insert a hyphen lett= er. In Lojban, the term=20 =20 hyphen always refers to a letter, either the vowel=20 y or one of the consonants=20 r and=20 n. (The letter=20 l can also be a hyphen, but is not used as one in= lujvo.) lujvo formrequirements for y-hyphen insertion in The=20 - y-hyphen is used after a CVC-form rafsi when join= ing it with the following rafsi could result in an impermissible consonant = pair, or when the resulting lujvo could fall apart into two or more words (= either cmavo or gismu). + y-hyphen is used after a CVC-form rafsi when joining it with the follo= wing rafsi could result in an impermissible consonant pair, or when the res= ulting lujvo could fall apart into two or more words (either cmavo or gismu= ). lujvoand consonant pairs Thus, the tanru=20 pante tavla (=20 protest talk) cannot produce the lujvo=20 patta'a, because=20 tt is not a permissible consonant pair; the l= ujvo must be=20 patyta'a. Similarly, the tanru=20 mudri siclu (=20 wooden whistle) cannot form the lujvo=20 mudsiclu; instead,=20 mudysiclu must be used. (Remember that=20 y is not counted in determining whether the first= five letters of a brivla contain a consonant cluster: this is why.) rafsifour-letterrequirement for y-hyphen The=20 - y-hyphen is also used to attach a 4-letter rafsi,= formed by dropping the final vowel of a gismu, to the following rafsi. (Th= is procedure was shown, but not explained, in=20 + y-hyphen is also used to attach a 4-letter rafsi, formed by dropping t= he final vowel of a gismu, to the following rafsi. (This procedure was show= n, but not explained, in=20 to=20 .) The lujvo forms=20 zunlyjamfu,=20 zunlyjma,=20 zuljamfu, and=20 zuljma are all legitimate and equivalent = forms made from the tanru=20 zunle jamfu (=20 left foot). Of these,=20 zuljma is the preferred one since it is t= he shortest; it thus is likely to be the form listed in a Lojban dictionary= . lujvo formrequirements for n-hyphen insertion in lujvo formrequirements for r-hyphen insertion in r-hyphenuse of= The=20 - r-hyphen and its close relative, the=20 - n-hyphen, are used in lujvo only after CVV-form r= afsi. A hyphen is always required in a two-part lujvo of the form CVV-CVV, = since otherwise there would be no consonant cluster. + r-hyphen and its close relative, the=20 + n-hyphen, are used in lujvo only after CVV-form rafsi. A hyphen is alw= ays required in a two-part lujvo of the form CVV-CVV, since otherwise there= would be no consonant cluster. An=20 - r-hyphen or=20 - n-hyphen is also required after the CVV-form rafs= i of any lujvo of the form CVV-CVC/CV or CVV-CCVCV since it would otherwise= fall apart into a CVV-form cmavo and a gismu. In any lujvo with more than = two parts, a CVV-form rafsi in the initial position must always be followed= by a hyphen. If the hyphen were to be omitted, the supposed lujvo could be= broken into smaller words without the hyphen: because the CVV-form rafsi w= ould be interpreted as a cmavo, and the remainder of the word as a valid lu= jvo that is one rafsi shorter. - r-hyphencontrasted with n-hyphen in requirements f= or use n-hyphencontrasted with r-hyph= en in requirements for use n-hyphenuse of An=20 - n-hyphen is only used in place of an=20 - r-hyphen when the following rafsi begins with=20 + r-hyphen or=20 + n-hyphen is also required after the CVV-form rafsi of any lujvo of the= form CVV-CVC/CV or CVV-CCVCV since it would otherwise fall apart into a CV= V-form cmavo and a gismu. In any lujvo with more than two parts, a CVV-form= rafsi in the initial position must always be followed by a hyphen. If the = hyphen were to be omitted, the supposed lujvo could be broken into smaller = words without the hyphen: because the CVV-form rafsi would be interpreted a= s a cmavo, and the remainder of the word as a valid lujvo that is one rafsi= shorter. + r-hyphencontrasted with n-hyphen in requirements for use n-hyphen= contrasted with r-hyphen in requirements for use n-hyphen<= secondary>use of An=20 + n-hyphen is only used in place of an=20 + r-hyphen when the following rafsi begins with=20 r. For example, the tanru=20 rokci renro (=20 rock throw) cannot be expressed as=20 ro'ire'o (which breaks up= into two cmavo), nor can it be=20 ro'irre'o (which has an i= mpermissible double consonant); the=20 - n-hyphen is required, and the correct form of the= hyphenated lujvo is=20 + n-hyphen is required, and the correct form of the hyphenated lujvo is= =20 ro'inre'o. The same lujvo could also be e= xpressed without hyphenation as=20 rokre'o. ZEI selma'olujvowith zei There is also a different way of building lujvo, or = rather phrases which are grammatically and semantically equivalent to lujvo= . You can make a phrase containing any desired words, joining each pair of = them with the special cmavo=20 zei. Thus, <anchor xml:id=3D"c4e6d12"/> bridi zei valsi @@ -1164,27 +1164,27 @@ If the last letter is not a vowel, modify the ending so that= the word ends in a vowel, either by removing a final consonant or by addin= g a suggestively chosen final vowel. If the first letter is not a consonant, modify the beginning= so that the word begins with a consonant, either by removing an initial vo= wel or adding a suggestively chosen initial consonant. fu'ivla categ= orizerselection consideration for l-hyphenuse of Prefix the result of steps 1-5 with a 4= -letter rafsi that categorizes the fu'ivla into a=20 topic area. It is only safe to use a 4-letter rafsi= ; short rafsi sometimes produce invalid fu'ivla. Hyphenate the rafsi to the= rest of the fu'ivla with an=20 - r-hyphen; if that would produce a double=20 + r-hyphen; if that would produce a double=20 r, use an=20 - n-hyphen instead; if the rafsi ends in=20 + n-hyphen instead; if the rafsi ends in=20 r and the rest of the fu'ivla begins with=20 n (or vice versa), or if the rafsi ends in "r= " and the rest of the fu'ivla begins with "tc", "ts", "dj", or "dz" (using = "n" would result in a phonotactically impermissible cluster), use an=20 - l-hyphen. (This is the only use of=20 - l-hyphen in Lojban.) + l-hyphen. (This is the only use of=20 + l-hyphen in Lojban.) Alternatively, if a CVC-form short rafsi is available it can= be used instead of the long rafsi. =20 Remember that the stress necessarily appears on the penultim= ate (next-to-the-last) syllable. In this section, the hyphen is set off with commas in the exam= ples, but these commas are not required in writing, and the hyphen need not= be pronounced as a separate syllable. Here are a few examples: @@ -1972,56 +1972,56 @@ Choose a 3-letter (CVV-form or CCV-form) or 5-letter rafsi for t= he final gismu in the tanru. Join the resulting string of rafsi, initially without hyphens. hyphens in lujvo<= /primary>proscribed where not required A= dd hyphen letters where necessary. It is illegal to add a hyphen at a place= that is not required by this algorithm. Right-to-left tests are recommende= d, for reasons discussed below. If there are more than two words in the tanru, put an=20 - r-hyphen (or an=20 - n-hyphen) after the first rafsi if it is CVV-= form. If there are exactly two words, then put an=20 - r-hyphen (or an=20 - n-hyphen) between the two rafsi if the first = rafsi is CVV-form, unless the second rafsi is CCV-form (for example,=20 + r-hyphen (or an=20 + n-hyphen) after the first rafsi if it is CVV-form. If there are ex= actly two words, then put an=20 + r-hyphen (or an=20 + n-hyphen) between the two rafsi if the first rafsi is CVV-form, un= less the second rafsi is CCV-form (for example,=20 saicli requires no hyphen). Use an=20 - r-hyphen unless the letter after the hyphen i= s=20 + r-hyphen unless the letter after the hyphen is=20 r, in which case use an=20 - n-hyphen. Never use an=20 - n-hyphen unless it is required. + n-hyphen. Never use an=20 + n-hyphen unless it is required. Put a=20 - y-hyphen between the consonants of any imperm= issible consonant pair. This will always appear between rafsi. + y-hyphen between the consonants of any impermissible consonant pai= r. This will always appear between rafsi. tosmabru test= Put a=20 - y-hyphen after any 4-letter rafsi form. + y-hyphen after any 4-letter rafsi form. Test all forms with one or more initial CVC-form rafsi – w= ith the pattern=20 CVC ... CVC + X – for=20 tosmabru failure. X must either be a CVCC= V long rafsi that happens to have a permissible initial pair as the consona= nt cluster, or is something which has caused a=20 - y-hyphen to be installed between the previous CVC= and itself by one of the above rules. + y-hyphen to be installed between the previous CVC and itself by one of= the above rules. The test is as follows: - Examine all the C/C consonant pairs up to the first y-hyphen, or up to the end of the word in case there are no y-hyphens. + Examine all the C/C consonant pairs up to the first y-hyphen= , or up to the end of the word in case there are no y-hyphens. These consonant pairs are called "joints=94. If all of those joints are permissible initials, then the tr= ial word will break up into a cmavo and a shorter brivla. If not, the word = will not break up, and no further hyphens are needed. - Install a y-hyphen at the first such jo= int. + Install a y-hyphen at the first such joint. lujvoselection of best form of lujvoscoring of Note that the=20 tosmabru test implies that the algorithm will be more e= fficient if rafsi junctures are tested for required hyphens from right to l= eft, instead of from left to right; when the test is required, it cannot be= completed until hyphenation to the right has been determined. =20 =20
@@ -2033,21 +2033,21 @@ L. Count the number of apostrophes; call it=20 A. Count the number of=20 y-,=20 r-, and=20 - n-hyphens; call it=20 + n-hyphens; call it=20 =20 H. For each rafsi, find the value in the following table. Sum= this value over all rafsi; call it=20 R:=20 @@ -2194,25 +2194,25 @@ =20 ge cannot fall off the front, because the following wor= d would begin with=20 rz, which is not a permissible initial conson= ant pair. So the lujvo forms are=20 gerzda and=20 gerzdani. The third form,=20 ge'u-zda, needs no hyphen, because even = though the first rafsi is CVV, the second one is CCV, so there is a consona= nt cluster in the first five letters. So=20 ge'uzda is this form of the lujvo. The fourth form,=20 ge'u-zdani, however, requ= ires an=20 - r-hyphen; otherwise, the=20 + r-hyphen; otherwise, the=20 ge'u- part would fall off as a cmavo. So this form of t= he lujvo is=20 ge'urzdani. The last two forms require=20 - y-hyphens, as all 4-letter rafsi do, and so are= =20 + y-hyphens, as all 4-letter rafsi do, and so are=20 =20 gerkyzda and=20 gerkyzdani respectively. boat classexamp= le The scoring algorithm is heavily weighted in fav= or of short lujvo, so we might expect that=20 gerzda would win. Its L score is 6, its A score is 0, its H= score is 0, its R score is 12, and its V score is 3, for a final score of 5878. The other forms have scores of = 7917, 6367, 9506, 8008, and 10047 respectively. Consequently, this lujvo wo= uld probably appear in the dictionary in the form=20 gerzda. For the next example, we will use the tanru=20 bloti klesi (=20 boat class) presumably referring to the category (rowbo= at, motorboat, cruise liner) into which a boat falls. We will omit the long= rafsi from the process, since lujvo containing long rafsi are almost never= preferred by the scoring algorithm when there are short rafsi available. The rafsi for=20 diff --git a/todocbook/TODO b/todocbook/TODO index 0d1e76b..79ce722 100644 --- a/todocbook/TODO +++ b/todocbook/TODO @@ -5,24 +5,20 @@ Chapter 6 lojban-word-importeds. for this. =20 WRT rafsi: man seems best =20 Will that suck for ger-zda ? =20 Let alone logj-bang-girz =20 -r-hyphen -- just wrong - -Drop all the damned gismu definition tables in favour of cross references - Handling chapter 2: why don't we just require that the number of sub-entri= es matches? Also: maybe rename jbo/gloss for this purpose, or introduce roles. =20 2.xml: =20 =20 6.xml: remove "This stuff was here before, not sure what it means - zort" =20 3.xml: --=20 You received this message because you are subscribed to the Google Groups "= BPFK" group. To post to this group, send email to bpfk-list@googlegroups.com. To unsubscribe from this group, send email to bpfk-list+unsubscribe@googleg= roups.com. For more options, visit this group at http://groups.google.com/group/bpfk-l= ist?hl=3Den.