[YG Conlang Archives] > [ceqli group] > messages [Date Index] [Thread Index] >


[Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: [txeqli] Re: C: if not 'ch'...



on 2/12/02 4:40 AM, uaxuctum at uaxuctum@hidden.email wrote:

>> Yes.  My reasoning is that if you have a single symbol for 'ts,'
> then you
>> also must have one for 'tS,' 'dz', 'dZ,' 'ks,' 'gz,' etc.
>> 
>> Now, I can see Txeqli _expanding- in the future, to include other
> letters
>> for other sounds.  At this point in technology, tho, it has to be
> limited to
>> the 26.  I could also see it adopting the Shavian system entirely.
> 
> Where's the new phoneme chart posted?
> If it happens that /tS/ retains its status as a
> single phoneme, I don't see why "tx" is preferrable
> to "c". Besides, to me the digraph "tx" instantly
> reminds me of Basque.

Preferable in the interest of symmetry and consistency.  If there's a single
symbol for /tS/ then there should also be one for /dZ/, and there isn't
enough alphabet for it.  And, as I said above, there are several other such
combinations that would seem to deserve their own symbols, too.

> 
> About Shavian, I've always liked it, but I think the
> use of any other alphabet that's not the roman will
> only cause that most people all over the world will
> have problems writing the language and will thus feel
> very disencouraged to use it. Not to mention the fact
> that the roman alphabet has thousands and thousands
> of already available fonts, while nothing similar can
> be said of the Greek, Cyrillic, Chinese, etc. writing
> systems and less of Shavian, which to my knowledge
> offers just one font.

Agree completely.  I'm talking about what may be possible, and convenient,
in the future.

> 
> About the use of "c" in a way such as "ctcin", I don't
> like tha idea at all. I think that for modifying the
> value of a letter (if there's really a need for that)
> it's much better to use non-letters, such as diacritics,
> apostrophes and the like (t'in, t*in). But the main
> question here is: Which value should t assume when
> appearing between c's? Why [T] and not e.g. a
> glottalized or a retroflex t? What would "cbc", "chc",
> "cac"... stand for?
> 
I wasn't clear.  In 'ctcin,' the first c makes the t into a th sound, the
second t makes the i into a short i.  I intend this not to be an actual part
of Txeqli, just as in English we represent German umlauts by following them
with 'e.'  I'd expect the c option to really almost only be used for foreign
names.  To germanpe kyam ta gcorciq.  The German's name is Goering.

And you're right when you suggest that there may not be a need for this.
It's just a matter of deciding something useful for C to do.  And of course
the values of c+whatever would be arbitrary.  You'd want to pick the volues
most likely to be needed.
-- 
>PLEASE NOTE MY NEW E-MAIL ADDRESS: rmay@hidden.email
> Rex F. May (Baloo)
> Daily cartoon at: http://www.cnsnews.com/cartoon/baloo.asp
> Buy my book at: http://www.kiva.net/~jonabook/gdummy.htm
> Language site at: http://www.geocities.com/ceqli/Uploadexp.htm