[85916] in tlhIngan-Hol
Re: Klingon orthography
daemon@ATHENA.MIT.EDU (ghunchu'wI' 'utlh)
Wed Jun 24 12:51:12 2009
In-Reply-To: <BC3C4829-7681-4D7C-92D6-ED3BD878A04A@evertype.com>
Date: Wed, 24 Jun 2009 12:49:27 -0400
From: "ghunchu'wI' 'utlh" <qunchuy@alcaco.net>
To: tlhingan-hol@kli.org
Errors-to: tlhingan-hol-bounce@kli.org
Reply-to: tlhingan-hol@kli.org
On Wed, Jun 24, 2009 at 12:05 PM, Michael Everson <everson@evertype.com>wrote:
> > Current case issues are a feature, not a bug.
>
> They are a problem for data integrity. There is no question of this.
>
You keep saying this, and you keep repeating this, but such repetition is
not convincing. The only explanation you give is that the distinction
between {q} and {Q} can be lost if you apply a case transformation. You
dismiss other lossy transformations because they're harder to do
"accidentally". You don't seem to acknowledge that case transformations can
be similarly lossy in other languages, but the example you presented was a
typical one where capitalization *does* matter: God vs. god.
Anecdotally, I've never encountered a case-transforming accident, but I have
seen several instances of text being mangled beyond repair by someone trying
to do a global search and replace of a misspelled word. I strongly question
the contention that the q/Q pair presents a special "data integrity"
problem. If your standard of "problem" involves Google's search treatment, I
think the existence of the apostrophe as a consonant is a worse offender.
-- ghunchu'wI'
