tlhIngan-Hol Archive: Wed Jun 24 13:49:15 2009
[Date Prev][Date Next][Thread Prev][Thread Next]
Re: Klingon orthography
- From: Brent Kesler <[email protected]>
- Subject: Re: Klingon orthography
- Date: Wed, 24 Jun 2009 13:47:28 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Z/U8Orrn9g7dUOQT6TuCWRm8EWCYidknL2yEMFw5BzM=; b=cavjxnZ0b8Db2Ya6H5S99NB+9zYkydTvcAvov9bnt/J3h/qsb+NVAijqP5PGH2pjOK erQdrAZnMov2CxDlARdDEQZk81F4jXbNhMSZc/ZxXA7i4iuL0kPut53ZgI1WccFvEmqc LTZk2ibpOxO3JmjFUF4eOJumo7PvSIa56tBwQ=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=lkiDbW5BApJ3LvRT/GNv7ZVXjty3GTZhW0KyWxYXePt0Cqxk7DR4V5xOQf/qzlIDgu wCTr5+CiFBJ+7GkHyhveRJxWZ0XbKcGBLKTF9MMmCrdjkmmlgybhdich5zB1SMldRqTe gdrcL6RRDOJWmM6divKFqsYfeeOWX7u+lN6ig=
- In-reply-to: <[email protected]>
- References: <[email protected]> <[email protected]> <[email protected]> <[email protected]>
On Wed, Jun 24, 2009 at 11:26 AM, David Trimboli<[email protected]> wrote:
>
> I encountered some transformation problems when I was working the bugs
> out of my MUSH regional speech commands, which let you type ta' Hol and
> you speak a regional accent.
[...]
> I don't remember what bugs I saw in setting this up, but this is exactly
> the sort of situation where case matters a great deal.
True, but if you're already working at the level of regular
expressions, working around Q/q is trivial. The Unicode standard in
not going to get in your way.
To Mr. Everson, you obviously understand Unicode in great detail, but
as someone who's hacked out a lot of Perl, the Q/q problem seems
trivial.
On Wed, Jun 24, 2009 at 10:47 AM, Michael Everson<[email protected]> wrote:
> Further, I also indicate that sorting operations are made more complex
> if you attempt to treat a casing pair as two separate entities.
How much more complex? Off the top of my head, I don't think
controlling for Q/q is going bump a logarithmic sort algorithm into
polynomial time, or even linear time. If I'm the programmer, it might
annoy me, but if I run the server farm, I care more about processor
cycles.
> Moreover, I outlined the political benefits of taking this data issue
> seriously in terms of an eventual re-try at encoding pIqaD.
Really? pIqaD was rejected because there was "no substantial
information exchange in the script". I don't see how adopting another
orthography is going to fix that.
> Your suggestion that I have given one explanation only is
> disingenuous. I don't think your arguments are going very well, so
> you've tried to disparage my attempt at dialogue because I may not
> know as much Klingon as you do,
Not really. When it comes to Unicode and related technologies, you're
the alpha geek in this forum and all lesser geeks bow before you (like
me: I'm clearly a dilletante on the subject). All the problems you
raise would be major issues if our goal were encoding a character set.
But since our goal is mastery of Klingon words and grammar and
actually using the language, the problems you mention are simply
problems we don't have. We can study, read, and write just fine the
way it is. Yeah, there are some quirks we need to work around, but
we've already adapted.
It ain't broke. Stop fixing it.
bI'reng
![[KLI Member]](../../../pics/KLImemberbutton.gif "[KLI Member]"){kind=small}