[tlhIngan Hol] xifan hol: k and q

De'vID de.vid.jonpin at gmail.com
Thu Jun 7 05:16:58 PDT 2018

On Sat, 2 Jun 2018 at 21:08, nIqolay Q <niqolay0 at gmail.com> wrote:

> boQwI' gives you an option of using k -> {q} or {Q}, is that something
> feasible on your end?
> I prefer to use boQwI' with k -> {Q}, since I can just use q for {q}. But
> I have noticed that some fonts use k for {q} and q for {Q} (or,
> technically, they use K for {q} and Q for {Q}, since the fonts map pIqaD to
> capital letters). I think I might be in the minority on this one.

Everyone keeps talking about fonts but that's only relevant if you're
typesetting {pIqaD}, presumably on your PC (or laptop).

Many people (maybe most, in some demographics) are primarily on their
mobile devices. The advantage of the "k" -> {Q} mapping is that it's
effectively "optional" on soft keyboards: if you type Klingon as you
normally would, you wouldn't even notice it was enabled. However, {Q} and
{'} are on shifted keys, and mapping "k" and "z" to them allows a user to
type them without shifting, which is a nuisance on a small device. It's
also handy to be able to type "x" for {tlh} and drop "h" when its presence
is unambiguous (like after "c"). With the "k" -> {Q} mapping, you can leave
"xifan hol" mode on and the typical user (who knows nothing about font
mappings) won't be confused when they're typing things in as-is. That's why
that's the default, and swapping {q} and {Q} (i.e., "k" -> {q}, "q" -> {Q})
is an advanced option.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kli.org/pipermail/tlhingan-hol-kli.org/attachments/20180607/0a273d44/attachment-0005.htm>

More information about the tlhIngan-Hol mailing list