[544] in tlhIngan-Hol
Re: case flexibility
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Tue Apr 13 14:51:02 1993
Errors-To: tlhIngan-Hol-request@village.boston.ma.us
Errors-To: tlhIngan-Hol-request@village.boston.ma.us
Errors-To: tlhIngan-Hol-request@village.boston.ma.us
Errors-To: tlhIngan-Hol-request@village.boston.ma.us
Errors-To: tlhIngan-Hol-request@village.boston.ma.us
Errors-To: tlhIngan-Hol-request@village.boston.ma.us
Errors-To: tlhIngan-Hol-request@village.boston.ma.us
Errors-To: tlhIngan-Hol-request@village.boston.ma.us
Reply-To: "Klingon Language List" <tlhIngan-Hol@village.boston.ma.us>
From: cowan@snark.thyrsus.com (John Cowan)
To: "Klingon Language List" <tlhIngan-Hol@village.boston.ma.us>
Date: Tue, 13 Apr 1993 11:10:37 -0400 (EDT)
In-Reply-To: <9304060920.AA00645@sunlight.Stanford.EDU> from "mosquito@leland.S
mosquito@leland.Stanford.EDU writes:
> Now I have a little sed script to convert lowercase tlhIngan Hol to
> tlhIngan-cased tlhingan Hol. Problems: if you have English text mixed
> in it tries to treat it like tlhIngan Hol and there's no way to delimit
> it now. Also, Q and q need to be distinguished by the user when typed.
> It also uses k internally so if your English text uses, e.g. ck, it will
> change it to ch. (the perl version only has this problem with qk).
I don't grok perl, but the sed version can be made to process text between
line-level delimiters very easily by prefixing each 's' command with:
/^.KL$/,/^.KE$/
Text will be processed only between lines consisting of .KL (for Klingon)
and .KE (for Klingon-end), thus:
.KL
Qapla'!
.KE
Those who prefer TeX to troff can make appropriate adjustments. Consistent
use of such a convention would also make it easy to process the tlhIngan-Hol
archives to extract the Klingon texts for future analysis. (There is
nothing more annoying, when processing text corpora, than having to strip
out stuff in another language.)
--
John Cowan cowan@snark.thyrsus.com ...!uunet!lock60!snark!cowan
e'osai ko sarji la lojban.
