Theiling Online    Sitemap    Conlang Mailing List HQ   

Re: Futurese

From:Kala Tunu <kalatunu@...>
Date:Tuesday, May 14, 2002, 12:54
i think plenty of us here understand quite well the merits of combining roots
like you do with Futurese since plenty of our conlangs do that too. i also have
around 1450 root concepts and a head+tail word order written separately.
combining "roots" (concepts or logograms) this way is pretty much what
indonesian, khmer and other natlangs do and many conlangs do too. writing two
roots together or separately doesn't make much difference, especially with
scripts like japanese and khmer which don't separate words with a blank or else.
the thing to keep in mind is that there are as many valid lists of roots as
there are conlangs and conlangers. one will select "shellfish" as a root,
another will make it "sea"+"shell"+"animal", some will say "juice" as
"plant+sap" and "blood" as "human+sap", others will have separate words for
"blood" and "sap", etc. i made my own list of roots as a mix of the joyo kanjis
(each tunu root can be written with a specific kanji), the basic english and a
list of "useful words" i grew through learning and translating other languages.
it's my root list, only worth for my own language.
>>>
So, if you have an everyday vocabulary consisting of about 15,000 units (single morphemes and compounds) and you write each of them as a single visual unit ("word"), then for being a fluent reader you'll have to memorize those 15,000 units individually, while if you just write separately each of those about 1,500 basic morphemes from which you get all those 15,000 items, you'll only have to memorize 1,500 instead of 15,000 visual units to read fluently. Thus, "steam" would be written as "hiz was" (vapour water) instead of "hizwas" (vapourwater), "apple juice" as "suk pom" (juice apple) instead of "sukpom" (juiceapple), "sake" as "xin rim" (alcoholic-beverage rice) instead of "xinrim" (alcoholicbeveragerice), etc. Cheers, Javier <<< Mathias http://takatunu.free.fr/tunugram.htm

Reply

Raymond Brown <ray.brown@...>