[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bpfk] dag-cll git updates for Sun Feb 13 13:21:01 EST 2011
commit afe6ef9bae64918fd72fa51a20b255de2340ee2a
Author: Robin Lee Powell <rlpowell@digitalkingdom.org>
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 @@
</example>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>recognizing</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>number of letters in</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>consonant cluster requirement in</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>final letter of</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>summary of form characteristics</secondary></indexterm> As noted above, CVC-form rafsi cannot appear as the 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 first five letters – this ensures that they cannot be mistaken for compound cmavo. Of course, all lujvo have at least six letters since they have two or more rafsi, each at least three letters long; hence they cannot be confused with gismu.</para>
<para> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>requirements for hyphen insertion in</secondary></indexterm> <indexterm type="general-imported"><primary>hyphen letter</primary><secondary>definition</secondary></indexterm> <indexterm type="general-imported"><primary>hyphens</primary><secondary>use of</secondary></indexterm> When attaching two rafsi together, it may be necessary to insert a hyphen letter. In Lojban, the term
<quote>hyphen</quote> always refers to a letter, either the vowel
<letteral>y</letteral> or one of the consonants
<letteral>r</letteral> and
<letteral>n</letteral>. (The letter
<letteral>l</letteral> can also be a hyphen, but is not used as one in lujvo.)</para>
<para> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>requirements for y-hyphen insertion in</secondary></indexterm> The
- <letteral>y-</letteral>hyphen is used after a CVC-form rafsi when joining 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).</para>
+ y-hyphen is used after a CVC-form rafsi when joining 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).</para>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>and consonant pairs</secondary></indexterm> Thus, the tanru
<oldjbophrase>pante tavla</oldjbophrase> (
<quote>protest talk</quote>) cannot produce the lujvo
<oldjbophrase valid="false">patta'a</oldjbophrase>, because
<morphology>tt</morphology> is not a permissible consonant pair; the lujvo must be
<oldjbophrase>patyta'a</oldjbophrase>. Similarly, the tanru
<oldjbophrase>mudri siclu</oldjbophrase> (
<quote>wooden whistle</quote>) cannot form the lujvo
<oldjbophrase valid="false">mudsiclu</oldjbophrase>; instead,
<oldjbophrase>mudysiclu</oldjbophrase> must be used. (Remember that
<letteral>y</letteral> is not counted in determining whether the first five letters of a brivla contain a consonant cluster: this is why.)</para>
<para> <indexterm type="general-imported"><primary>rafsi</primary><secondary>four-letter</secondary><tertiary>requirement for y-hyphen</tertiary></indexterm> The
- <letteral>y-</letteral>hyphen is also used to attach a 4-letter rafsi, formed by dropping the final vowel of a gismu, to the following rafsi. (This procedure was shown, but not explained, in
+ y-hyphen is also used to attach a 4-letter rafsi, formed by dropping the final vowel of a gismu, to the following rafsi. (This procedure was shown, but not explained, in
<xref linkend="example-random-id-qj84"/> to
<xref linkend="example-random-id-qjbP"/>.)</para>
<para>The lujvo forms
<oldjbophrase>zunlyjamfu</oldjbophrase>,
<oldjbophrase>zunlyjma</oldjbophrase>,
<oldjbophrase>zuljamfu</oldjbophrase>, and
<oldjbophrase>zuljma</oldjbophrase> are all legitimate and equivalent forms made from the tanru
<oldjbophrase>zunle jamfu</oldjbophrase> (
<quote>left foot</quote>). Of these,
<oldjbophrase>zuljma</oldjbophrase> is the preferred one since it is the shortest; it thus is likely to be the form listed in a Lojban dictionary.</para>
<para> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>requirements for n-hyphen insertion in</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo form</primary><secondary>requirements for r-hyphen insertion in</secondary></indexterm> <indexterm type="general-imported"><primary>r-hyphen</primary><secondary>use of</secondary></indexterm> The
- <letteral>r-</letteral>hyphen and its close relative, the
- <letteral>n-</letteral>hyphen, are used in lujvo only after CVV-form rafsi. A hyphen is always required in a two-part lujvo of the form CVV-CVV, since otherwise there would be no consonant cluster.</para>
+ r-hyphen and its close relative, the
+ n-hyphen, are used in lujvo only after CVV-form rafsi. A hyphen is always required in a two-part lujvo of the form CVV-CVV, since otherwise there would be no consonant cluster.</para>
<para>An
- <letteral>r-</letteral>hyphen or
- <letteral>n-</letteral>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 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 would be interpreted as a cmavo, and the remainder of the word as a valid lujvo that is one rafsi shorter.</para>
- <para> <indexterm type="general-imported"><primary>r-hyphen</primary><secondary>contrasted with <letteral>n-</letteral>hyphen in requirements for use</secondary></indexterm> <indexterm type="general-imported"><primary>n-hyphen</primary><secondary>contrasted with <letteral>r-</letteral>hyphen in requirements for use</secondary></indexterm> <indexterm type="general-imported"><primary>n-hyphen</primary><secondary>use of</secondary></indexterm> An
- <letteral>n-</letteral>hyphen is only used in place of an
- <letteral>r-</letteral>hyphen when the following rafsi begins with
+ r-hyphen or
+ 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 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 would be interpreted as a cmavo, and the remainder of the word as a valid lujvo that is one rafsi shorter.</para>
+ <para> <indexterm type="general-imported"><primary>r-hyphen</primary><secondary>contrasted with n-hyphen in requirements for use</secondary></indexterm> <indexterm type="general-imported"><primary>n-hyphen</primary><secondary>contrasted with r-hyphen in requirements for use</secondary></indexterm> <indexterm type="general-imported"><primary>n-hyphen</primary><secondary>use of</secondary></indexterm> An
+ n-hyphen is only used in place of an
+ r-hyphen when the following rafsi begins with
<letteral>r</letteral>. For example, the tanru
<oldjbophrase>rokci renro</oldjbophrase> (
<quote>rock throw</quote>) cannot be expressed as
<oldjbophrase valid="false">ro'ire'o</oldjbophrase> (which breaks up into two cmavo), nor can it be
<oldjbophrase valid="false">ro'irre'o</oldjbophrase> (which has an impermissible double consonant); the
- <letteral>n-</letteral>hyphen is required, and the correct form of the hyphenated lujvo is
+ n-hyphen is required, and the correct form of the hyphenated lujvo is
<oldjbophrase>ro'inre'o</oldjbophrase>. The same lujvo could also be expressed without hyphenation as
<oldjbophrase>rokre'o</oldjbophrase>.</para>
<para><!-- FIXME: what to do with this indexterm? --><indexterm type="lojban-word-imported"><primary>ZEI selma'o</primary></indexterm><indexterm type="general-imported"><primary>lujvo</primary><secondary>with zei</secondary></indexterm> 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
<valsi>zei</valsi>. Thus,</para>
<example role="lujvo-example" xml:id="example-random-id-VeGL">
<title>
<anchor xml:id="c4e6d12"/>
</title>
<lujvo-making>
<jbo>bridi zei valsi</jbo>
@@ -1164,27 +1164,27 @@
</listitem>
<listitem>
<para>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 adding a suggestively chosen final vowel.</para>
</listitem>
<listitem>
<para>If the first letter is not a consonant, modify the beginning so that the word begins with a consonant, either by removing an initial vowel or adding a suggestively chosen initial consonant.</para>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>fu'ivla categorizer</primary><secondary>selection consideration for</secondary></indexterm> <indexterm type="general-imported"><primary>l-hyphen</primary><secondary>use of</secondary></indexterm> Prefix the result of steps 1-5 with a 4-letter rafsi that categorizes the fu'ivla into a
<quote>topic area</quote>. 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
- <letteral>r-</letteral>hyphen; if that would produce a double
+ r-hyphen; if that would produce a double
<letteral>r</letteral>, use an
- <letteral>n-</letteral>hyphen instead; if the rafsi ends in
+ n-hyphen instead; if the rafsi ends in
<letteral>r</letteral> and the rest of the fu'ivla begins with
<letteral>n</letteral> (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
- <letteral>l-</letteral>hyphen. (This is the only use of
- <letteral>l-</letteral>hyphen in Lojban.)</para>
+ l-hyphen. (This is the only use of
+ l-hyphen in Lojban.)</para>
<para>Alternatively, if a CVC-form short rafsi is available it can be used instead of the long rafsi.</para>
</listitem>
<listitem>
<para>Remember that the stress necessarily appears on the penultimate (next-to-the-last) syllable.</para>
</listitem>
</orderedlist>
<para> In this section, the hyphen is set off with commas in the examples, but these commas are not required in writing, and the hyphen need not be pronounced as a separate syllable.</para>
<para>Here are a few examples:</para>
<example role="lojbanization-example" xml:id="example-random-id-ufin">
@@ -1972,56 +1972,56 @@
<para>Choose a 3-letter (CVV-form or CCV-form) or 5-letter rafsi for the final gismu in the tanru.</para>
</listitem>
<listitem>
<para>Join the resulting string of rafsi, initially without hyphens.</para>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>hyphens in lujvo</primary><secondary>proscribed where not required</secondary></indexterm> Add 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 recommended, for reasons discussed below.</para>
<orderedlist>
<listitem>
<para>If there are more than two words in the tanru, put an
- <letteral>r-</letteral>hyphen (or an
- <letteral>n-</letteral>hyphen) after the first rafsi if it is CVV-form. If there are exactly two words, then put an
- <letteral>r-</letteral>hyphen (or an
- <letteral>n-</letteral>hyphen) between the two rafsi if the first rafsi is CVV-form, unless the second rafsi is CCV-form (for example,
+ r-hyphen (or an
+ n-hyphen) after the first rafsi if it is CVV-form. If there are exactly two words, then put an
+ r-hyphen (or an
+ n-hyphen) between the two rafsi if the first rafsi is CVV-form, unless the second rafsi is CCV-form (for example,
<oldjbophrase>saicli</oldjbophrase> requires no hyphen). Use an
- <letteral>r-</letteral>hyphen unless the letter after the hyphen is
+ r-hyphen unless the letter after the hyphen is
<letteral>r</letteral>, in which case use an
- <letteral>n-</letteral>hyphen. Never use an
- <letteral>n-</letteral>hyphen unless it is required.</para>
+ n-hyphen. Never use an
+ n-hyphen unless it is required.</para>
</listitem>
<listitem>
<para>Put a
- <letteral>y-</letteral>hyphen between the consonants of any impermissible consonant pair. This will always appear between rafsi.</para>
+ y-hyphen between the consonants of any impermissible consonant pair. This will always appear between rafsi.</para>
</listitem>
<listitem>
<para> <indexterm type="general-imported"><primary>tosmabru test</primary></indexterm> Put a
- <letteral>y-</letteral>hyphen after any 4-letter rafsi form.</para>
+ y-hyphen after any 4-letter rafsi form.</para>
</listitem>
</orderedlist>
</listitem>
<listitem>
<para>Test all forms with one or more initial CVC-form rafsi – with the pattern
<quote>CVC ... CVC + X</quote> – for
<oldjbophrase>tosmabru failure</oldjbophrase>. X must either be a CVCCV long rafsi that happens to have a permissible initial pair as the consonant cluster, or is something which has caused a
- <letteral>y-</letteral>hyphen to be installed between the previous CVC and itself by one of the above rules.</para>
+ y-hyphen to be installed between the previous CVC and itself by one of the above rules.</para>
<para>The test is as follows:</para>
<orderedlist>
<listitem>
- <para>Examine all the C/C consonant pairs up to the first <letteral>y-</letteral>hyphen, or up to the end of the word in case there are no <letteral>y-</letteral>hyphens.</para>
+ <para>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.</para>
<para>These consonant pairs are called "joints”.</para>
</listitem>
<listitem>
<para>If all of those joints are permissible initials, then the trial 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.</para>
</listitem>
<listitem>
- <para>Install a <letteral>y-</letteral>hyphen at the first such joint.</para>
+ <para>Install a y-hyphen at the first such joint.</para>
</listitem>
</orderedlist>
</listitem>
</orderedlist>
<para> <indexterm type="general-imported"><primary>lujvo</primary><secondary>selection of best form of</secondary></indexterm> <indexterm type="general-imported"><primary>lujvo</primary><secondary>scoring of</secondary></indexterm> Note that the
<quote>tosmabru test</quote> implies that the algorithm will be more efficient if rafsi junctures are tested for required hyphens from right to left, instead of from left to right; when the test is required, it cannot be completed until hyphenation to the right has been determined.</para>
</section>
<section xml:id="section-lujvo-scoring">
@@ -2033,21 +2033,21 @@
<varname>L</varname>.</para>
</listitem>
<listitem>
<para>Count the number of apostrophes; call it
<varname>A</varname>.</para>
</listitem>
<listitem>
<para>Count the number of
<letteral>y-</letteral>,
<letteral>r-</letteral>, and
- <letteral>n-</letteral>hyphens; call it
+ n-hyphens; call it
<varname>H</varname>.</para>
</listitem>
<listitem>
<para>For each rafsi, find the value in the following table. Sum this value over all rafsi; call it
<varname>R</varname>:
<informaltable>
<tgroup cols="3">
<colspec colnum="1" colname="col1"/>
<colspec colnum="2" colname="col2"/>
@@ -2194,25 +2194,25 @@
<valsi>ge</valsi> cannot fall off the front, because the following word would begin with
<morphology>rz</morphology>, which is not a permissible initial consonant pair. So the lujvo forms are
<oldjbophrase>gerzda</oldjbophrase> and
<oldjbophrase>gerzdani</oldjbophrase>.</para>
<para>The third form,
<rafsi>ge'u</rafsi><rafsi>-zda</rafsi>, needs no hyphen, because even though the first rafsi is CVV, the second one is CCV, so there is a consonant cluster in the first five letters. So
<oldjbophrase>ge'uzda</oldjbophrase> is this form of the lujvo.</para>
<para>The fourth form,
<oldjbophrase valid="false">ge'u-zdani</oldjbophrase>, however, requires an
- <letteral>r-</letteral>hyphen; otherwise, the
+ r-hyphen; otherwise, the
<rafsi>ge'u-</rafsi> part would fall off as a cmavo. So this form of the lujvo is
<oldjbophrase>ge'urzdani</oldjbophrase>.</para>
<para>The last two forms require
- <letteral>y-</letteral>hyphens, as all 4-letter rafsi do, and so are
+ y-hyphens, as all 4-letter rafsi do, and so are
<oldjbophrase>gerkyzda</oldjbophrase> and
<oldjbophrase>gerkyzdani</oldjbophrase> respectively.</para>
<para> <!-- FIXME: there's nowhere for this indexterm to go --><indexterm type="example-imported"><primary>boat class</primary><secondary>example</secondary></indexterm> The scoring algorithm is heavily weighted in favor of short lujvo, so we might expect that
<oldjbophrase>gerzda</oldjbophrase> would win. Its <varname>L</varname> score is 6, its <varname>A</varname> score is 0, its <varname>H</varname> score is 0, its <varname>R</varname> score is 12, and its <varname>V</varname> 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 would probably appear in the dictionary in the form
<oldjbophrase>gerzda</oldjbophrase>.</para>
<para>For the next example, we will use the tanru
<oldjbophrase>bloti klesi</oldjbophrase> (
<quote>boat class</quote>) presumably referring to the category (rowboat, 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.</para>
<para>The rafsi for
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.
WRT rafsi: <rafsi type="prefix">man</rafsi> seems best
Will that suck for <member><jbophrase role="rafsi">ger</jbophrase><jbophrase role="rafsi">-zda</jbophrase></member> ?
Let alone <member><jbophrase
role="rafsi">logj</jbophrase><jbophrase
role="rafsi">-bang</jbophrase><jbophrase
role="rafsi">-girz</jbophrase></member>
-<jbophrase role="letteral">r-</jbophrase>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-entries matches?
Also: maybe rename jbo/gloss for this purpose, or introduce roles.
2.xml:
6.xml:
remove "This stuff was here before, not sure what it means - zort"
3.xml:
--
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@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/bpfk-list?hl=en.