xe'e: Difference between revisions

From Lojban
Jump to navigation Jump to search
mNo edit summary
 
mNo edit summary
Line 1: Line 1:


A minority of Lojbanists think using the [http://www.csclub.uwaterloo.ca/u/relipper/tolkien/rootpage.html olkien] script [http://www.geocities.com/TimesSquare/4948/tengwar/index.htm engwar] ('''lerfrtengua''') for Lojban is at the least cute, and at the most [http://www.raphael.poss.name/tengwar/lojteng2 nstructive]. The kind of person interested in Lojban intersects with the kind of person interested in Tolkienian linguistics. Nonetheless, the majority of Lojbanists, it is fair to say, regard the enterprise as folly. This includes [[jbocre: Ivan Derzhanski|Ivan Derzhanski]], who is a Tolkienist of long standing.
Used for what was originally proprosed for nau, but annulled in the changes leading up to version 2.33 (I think the file can be found in parser.zip at [http://www.lojban.org/files/software/parser/)


I doubt anyone is planning on switching the list over to Tengwar en masse once the Tengwar section of Unicode is established.... [[jbocre: Here is the proposal: [http://std.dkuug.dk/jtc1/sc2/wg2/docs/n1641/n1641.htm]] However, as [[User:Nick Nicholas|nitcion]] pointed out, it would be nice to use it on the covers of things like the lessons. I could see Tengwar being used in the way calligraphic English is used (or maybe hyper-intricate gothic fonts). Sort of the thing that classy Lojbanists would use on their wedding invitations. --[[jbocre: Jay Kominek|Jay]]
The] proposal is to use ''xe'e'' (and maybe [[jbocre: ne'e|ne'e]] at some point) for the word proposed below.


An example of a lojbanic text written in Tengwar is {file name="Berenstain_Fight_Tengwar.zip" showdesc=1} (The Berenstain Bears Get in a Fight).
''If it's a modal, why is it GOI and not BAI??''


Actually, I already have converted the cmavo, gismu and lujvo lists to use Tengwar.  -- [[jbocre: xwaver|xwaver]] / ficyr.
It connects a modal to a sumti, like GOI. For example, we currently say (see [[jbocre: Frank likes Betty more than Mary|Frank likes Betty more than Mary]]:


'''See also [[jbocre: Why Tengwar?]]''' and '''[[jbocre: Tengwar Resources|Tengwar Resources]]'''
;:la frank. nelci la betis. ne semau la meiris.


that's the truth
But this is not just meant to be an abbreviation of ''la frank. nelci la betis noi zmadu la meiris.'', it's meant to be an abbreviation of ''le ni la frank nelci la betis cu zmadu le ni la frank nelci la meiris.'' This is a second meaning for ''ne'', and would it be better to give it its own word:
 
;:la frank. nelci la betis xe'e semau la meiris.


----
----


There are two published mappings
CHANGE 28:  (Probably ANNULLED)
 
CURRENT LANGUAGE:
 
The draft textbook had a cmavo "mo'u" used to attach a relative phrase to a
 
sumti 'modally'. i.e. neither restrictively or non-restrictively.  As part
 
of an early cmavo change, "mo'u" was combine into the non-restrictive "ne"
 
because at the time there was not seen to be any logical distinction between
 
the two.  This was an error.
 
The relative-phrase introducer "ne" is used before a tagged sumti in two
 
different ways: to add incidental information (the non-restrictive equivalent


* [http://www.catb.org/~esr/tengwar/lojban-tengwar.html ric Raymond's proposed mapping]
of "pe"), and to attach a new sumti to the bridi, modally associating it with
* [http://www.raphael.poss.name/tengwar/ lrond's revised mapping]


** Mode 1: separate vowel carriers for each vowel
some already existing sumti.  Paradigm cases are:
** Mode 2: full vowels (Beleriand mode)


** Mode 3: full vowel + ''tehta'' for diphthongs
mi nelci la .apasionatas ne fi'e la betoven.
* [http://www.fa-kuan.muc.de/LOJBAN.RXML ulun's mapping samples mainly following elrond's proposal (Mode 1)]


** {V'V}: short vowel carrier modified for this purpose (Sindarin), modified  i.e. shortened about the size of apostrophe (Gandalf)
I like the Appassionata, created by Beethoven.
** {V,V}: use of  comma (adapted to Tengwar) '' As in Raymond's proposal.''


** (rejection of the Beleriand mode)
and
*[[jbocre: cmeclax|cmeclax]] has [http://lexx.shinn.net/cmeclax/ lso used Tengwar]


(BTW, in order to achieving a good-looking script one ought to have '''at least''' two kinds of different widths tehtar!) ''The single-byte fonts tend to; the Unicode fonts won't, because this is properly an issue for Smart Fonts. Thankfully, Smart Fonts are now on the market, though it'll be a year or two [[jbocre: as of 2001]] before they come into general use.''
la djan. nelci la betis. ne semau la meris.


The characteristics of Elrond's Mode 1 are:
John likes Betty more than (he likes) Mary.


** separate vowel carriers for each vowel
respectively.  In the former sentence, "ne fi'e la betoven." means no more
** CVV: tengwa+tehta, (short) carrier+ tehta


** VV: (short) carrier+ tehta for both vowels
than "noi la betoven. finti"; in the latter sentence, however, "ne semau
** special case {uu}: long carrier as abbreviature


** special case {.i}: colon as  abbreviature
la meris." does not mean "noi la meris. se zmadu", since the information is
** 'doubling' (underlining') the first tengwa for stress (Sindarin and Gandalf)


** various final-s (joined to different tengwar)
essential to the bridi, not merely incidental.  That is, John may like Betty


The main technical issue with Tengwar seems to be what to do with VV and V'V.
more than Mary, but not really 'like' Betty or Mary at all. In fact, the


==== VV ====
second example generally means:


[[jbocre: Elrond|Elrond]] in his [http://www.raphael.poss.name/tengwar/ ublished proposal] advocates a mode in which VV are handled with separate vowel carriers (a la Quenya), and a mode in which VV are handled with ''tehtar'' over full vowel letters (a la Sindarin; preferred).
le ni la djan. nelci la betis. cu zmadu


[[jbocre: xwaver|xwaver]] uses Beleriand full vowel tengwa for the primary vowel, tethar for the trailing
le ni la djan. nelci la meris.


'' I currently vote Quenya -- [[User:Nick Nicholas|nitcion]]''
The amount-of John's liking Betty is-more-than


He has since come to believe that double ''tehtar'' are preferrable -- though this will prove typographically unwieldy. cmeclax concurs.  However, if 'typographically unwieldy' refers to font design, xuinkrbin disagrees since any font designed for such use could employee a ligature.  When typing ".ia.", a ligature could be used to display a combined 'i+a' tehta above the first full-stop.
the amount-of John's liking Mary.


'' But since the VV are not just double vowels, I doubt it's very Tolkienesque -- [[User:Nick Nicholas|nitcion]].''
The confusion between the two types of "ne" is unacceptably ambiguous. The


==== V'V ====
second type is especially valuable with "semau" and "seme'a", and has seen


Established usage (Raymond, Elrond, [[jbocre: cmeclax|cmeclax]], [[jbocre: xwaver|xwaver]]) is to use the ''halla''. nitcion would prefer to use the long vowel carrier, in order to deemphasise the distinction between VV and V'V.
considerable use, but this use is contrary to the nominal definition of "ne".


cmeclax makes the vowel following ' a ''tehta'' to the right of the ''halla''. There is no Tolkien precedent for this, presumably because the ''halla'' is taken in the Tolkien universe to be an archaic variant of the ''hyarmen'', so it wouldn't have been used much in extant Tengwar.
PROPOSED CHANGE:


[[jbocre: xwaver|xwaver]] eliminates the carrier altogether, using Beleriand mode for the first vowel (ie. the explicit vowel carriers), tetha for the second.
Assign the cmavo "nau" to the latter use. Since "sumti NAU tag sumti" is


aulun uses a shortened vowel carrier to render the aposrtrophe, and a normal short vowel carrier for the vowel after it.
really a kind of non-logical connection between sumti, it no longer makes


*[[jbocre: Originally misunderstood as:]] aulun shortens the second carrier to the size of an apostrophe.
sense to treat it as a relative phrase; this grammar change makes "NAU tag"
**''Do I read you correctly? Could you point me to a sample? --- the samples on your page seem to be straight Elrond mode 1 -- mi'e [[User:Nick Nicholas|nitcion]]''


***''What I did was designing a better looking apostrophe by shortening the (short) carrier - using Fontographer - i.e. I use the '''apostrophe''' like in romanized Lojban for /h/. In the Gandalf font the modified carrier is almost the size of a normal apostrophe: will post a sample soon!''
a kind of non-logical connective, usable between sumti, tanru units,
****OK, but be aware that Unicode won't be including non-Tolkien glyphs, and this will mean problems down the road. (Or am I ''still'' confused, and this is indeed a Tolkienian variant attributed to Gandalf in the mythos?) Still, the fact that aulun, cmeclax and nitcion independently arrive at a different 'carrier' for the vowel after an apostrophe than the short vowel carrier is surely significant. [[jbocre: wrong, as it turns out|wrong, as it turns out]]


Here's a sample for .aulun's modified apostrophe in Gandalf (being aware of the problems pointed out above, it's just for personal use within graphic format):
operators, and operands only.


[http://www.fa-kuan.muc.de/apsampl.gif]
COUNTER-ARGUMENT:


==== r ====
This mechanism only works correctly if a second place is implicitly given


*Raymond prescribes ''ore'' (untrilled r) rather than ''romen'' (trilled r)
the modal or tense tag.  For tenses, the second place is the space/time
*Elrond makes this an optional choice


*nitcion would prefer ''romen'', but ''ore'' looks less disruptive
origin; for the comparatives, it is what is being compared; for the causals,
*aulun uses ''romen''


==== Full vowels ====
it is the effect (and vice versa).  But for a tag such as "bau", using the


*Raymond picks ''hyarmen'' for full e
x2 place of "bangu" simply isn't useful.
*Elrond picks ''yanta'', which looks about the same but is less disruptive


==== Double vowels ====
For most uses of this construction, the right thing to do is to use the


*Elrond treats uu and ii as double vowels (''tehta'' over long vowel carrier)
actual underlying gismu, which has all the necessary places:  recast pure
*nitcion thinks this bogus.


*Elrond starts to think about using yet different ''tehta'' for diphtongs
comparisons using "zmadu", "mleca", or "dunli".  If you want to


==== Stress ====
simultaneously make positive and comparative claims, use ".esemaubo".  To


*Raymond and [[jbocre: xwaver|xwaver]] double (underbar) the consonant/carrier of any capitalised letter
apply tags separately to the two parts of a non-logical connective ("I
*Elrond wants only the first such consonant/carrier to be doubled. This is far saner, but existing [http://user.tninet.se/~xof995c/tengscribe.htm oftware] won't deal with it well, so this requires a separate script to be written.


==== Comma ====
in Lojban, with you in English, discuss"), use Change 30's non-logical


*Raymond and aulun incorporate the comma into Tengwar
termset connection.
*Elrond and [[jbocre: xwaver|xwaver]] advocate a circumflex underneath, as a reused rare Tengwar


*nitcion can't find such a thing in the standard repertoire, and awaits further instruction. There are various other ''tehta'' floating around.
It has been argued that the standard use of "semau" in relative phrases is


==== Final S ====
logically misleading.  If we are saying that "John likes Betty more than


*xwaver uses the final s curls after consonants, considering that while they would be handy in CVS. and CVVS. circumstances, they are slightly more confusing.
(he likes) Mary", the essential claim is not "likes"/"nelci" but "zmadu" as


==== Prenasalisation ====
stated above, and the main bridi should therefore be "zmadu".  This


Noone seems to think introducing the prenasalisation ''tehta'' into Lojban Tengwar would be a good thing.
essential logical structure is hidden by the status quo, and to some


==== Non-Lojban letters ====
extent by the proposed change.  The counter-argument to this, that natural


To cope with cited non-Lojban text, nitcion proposes mappings for the non-Lojban letters:
language usage of comparison warrants an abbreviated form, is logically


*q: nwalme
unsound.
*w: hwesta


*h: hyarmen
Change 28 will probably not be accepted, and is not incorporated into the


Comments from [[User:Nick Nicholas|nitcion]]: ''If anything in Lojban tengwar is sacred by now, it's that k = quesse. It's inefficient, but we are keeping coronals (palatoalveolars & palatals) distinct from velars. Even if we allowed series IV stops to be (also) written as series III, I'd still rather q keep out of the way; in nwalme, it's safe. Besides, it's not canonical Lojban; why should be anywhere near the usual tengwar in a Lojban mode?''
published E-BNF, but is being retained here until all interested parties


''Right, but still, nwalme has a strong nasal connotation. Why not using the additional tengwar 34 (arda ?) instead ?''
have seen the arguments on all sides.


If we pick a totally arbitrary tengwar, arda's as good as any ('course, arda kinda ''looks'' like q). But it'd be nice if the glyph for q was associated with either velar or labial. How about (16) unque?
PROPOSAL:


''Seems nice indeed, and easy to write :-) I vote. -- Elrond''
Clarify that "ne semau" is non-restrictive, not simply comparative. This


So:
means that the example Lojban sentence above requires that John like both


*q: unque
Betty and Mary, in order for the non-restrictive "ne semau" phrase to be
*w: hwesta


*h: hyarmen
true.  By comparison, the English can be used if John likes Betty, but


To illustrate all the foregoing, here's one construal of all this:
doesn't like Mary.


[http://www.opoudjis.net/dist/tengwar.gif]
This clarification requires no grammar change, but substantial reworking of


xwaver [http://www.xwaver.net/lojban/tlcursive.GIF]
draft textbook lesson 6.


----
----


a little bit more about the Tengwar, ''bau la lojban'', [[jbocre: tenguar here|tenguar here]]
*'''xe'e''' was also a protoform of [[jbocre: jai|jai]]. Apparently, [[User:Nick Nicholas|Nick Nicholas]] proposed this (http://balance.wiw.org/~jkominek/lojban/9203/msg00039.html), although he has only dim recollections of this.

Revision as of 17:20, 4 November 2013

Used for what was originally proprosed for nau, but annulled in the changes leading up to version 2.33 (I think the file can be found in parser.zip at [http://www.lojban.org/files/software/parser/)

The] proposal is to use xe'e (and maybe ne'e at some point) for the word proposed below.

If it's a modal, why is it GOI and not BAI??

It connects a modal to a sumti, like GOI. For example, we currently say (see Frank likes Betty more than Mary:

la frank. nelci la betis. ne semau la meiris.

But this is not just meant to be an abbreviation of la frank. nelci la betis noi zmadu la meiris., it's meant to be an abbreviation of le ni la frank nelci la betis cu zmadu le ni la frank nelci la meiris. This is a second meaning for ne, and would it be better to give it its own word:

la frank. nelci la betis xe'e semau la meiris.

CHANGE 28: (Probably ANNULLED)

CURRENT LANGUAGE:

The draft textbook had a cmavo "mo'u" used to attach a relative phrase to a

sumti 'modally'. i.e. neither restrictively or non-restrictively. As part

of an early cmavo change, "mo'u" was combine into the non-restrictive "ne"

because at the time there was not seen to be any logical distinction between

the two. This was an error.

The relative-phrase introducer "ne" is used before a tagged sumti in two

different ways: to add incidental information (the non-restrictive equivalent

of "pe"), and to attach a new sumti to the bridi, modally associating it with

some already existing sumti. Paradigm cases are:

mi nelci la .apasionatas ne fi'e la betoven.

I like the Appassionata, created by Beethoven.

and

la djan. nelci la betis. ne semau la meris.

John likes Betty more than (he likes) Mary.

respectively. In the former sentence, "ne fi'e la betoven." means no more

than "noi la betoven. finti"; in the latter sentence, however, "ne semau

la meris." does not mean "noi la meris. se zmadu", since the information is

essential to the bridi, not merely incidental. That is, John may like Betty

more than Mary, but not really 'like' Betty or Mary at all. In fact, the

second example generally means:

le ni la djan. nelci la betis. cu zmadu

le ni la djan. nelci la meris.

The amount-of John's liking Betty is-more-than

the amount-of John's liking Mary.

The confusion between the two types of "ne" is unacceptably ambiguous. The

second type is especially valuable with "semau" and "seme'a", and has seen

considerable use, but this use is contrary to the nominal definition of "ne".

PROPOSED CHANGE:

Assign the cmavo "nau" to the latter use. Since "sumti NAU tag sumti" is

really a kind of non-logical connection between sumti, it no longer makes

sense to treat it as a relative phrase; this grammar change makes "NAU tag"

a kind of non-logical connective, usable between sumti, tanru units,

operators, and operands only.

COUNTER-ARGUMENT:

This mechanism only works correctly if a second place is implicitly given

the modal or tense tag. For tenses, the second place is the space/time

origin; for the comparatives, it is what is being compared; for the causals,

it is the effect (and vice versa). But for a tag such as "bau", using the

x2 place of "bangu" simply isn't useful.

For most uses of this construction, the right thing to do is to use the

actual underlying gismu, which has all the necessary places: recast pure

comparisons using "zmadu", "mleca", or "dunli". If you want to

simultaneously make positive and comparative claims, use ".esemaubo". To

apply tags separately to the two parts of a non-logical connective ("I

in Lojban, with you in English, discuss"), use Change 30's non-logical

termset connection.

It has been argued that the standard use of "semau" in relative phrases is

logically misleading. If we are saying that "John likes Betty more than

(he likes) Mary", the essential claim is not "likes"/"nelci" but "zmadu" as

stated above, and the main bridi should therefore be "zmadu". This

essential logical structure is hidden by the status quo, and to some

extent by the proposed change. The counter-argument to this, that natural

language usage of comparison warrants an abbreviated form, is logically

unsound.

Change 28 will probably not be accepted, and is not incorporated into the

published E-BNF, but is being retained here until all interested parties

have seen the arguments on all sides.

PROPOSAL:

Clarify that "ne semau" is non-restrictive, not simply comparative. This

means that the example Lojban sentence above requires that John like both

Betty and Mary, in order for the non-restrictive "ne semau" phrase to be

true. By comparison, the English can be used if John likes Betty, but

doesn't like Mary.

This clarification requires no grammar change, but substantial reworking of

draft textbook lesson 6.