<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><DIV>On 18 Nov 2005, at 9:25 am, mike leonard wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><DIV> <BLOCKQUOTE class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Just a question about this last point; how do people actually enter<BR>most of the non-ascii characters directly into their source? I'm all <BR>for being able to type a literal alpha in my math sources to get a<BR>math alpha, but unless the text editor "auto-completes" this for me,<BR>along the lines of how iTeXMac 2 does (although only for viewing), I <BR>don't see how this is actually convenient to use...<BR><BR>(Will we, in the future, have multiple keyboard on our desks that<BR>contain different subsets of unicode?)</BLOCKQUOTE> <DIV> </DIV> <DIV>I've found Jonathan's Ukelele tool (<A href="http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&item_id=ukelele">http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&item_id=ukelele</A>) to be very useful. You can remap your keyboard to your heart's content. <BR></DIV></DIV></BLOCKQUOTE><BR></DIV><DIV>Glad you've found it useful, but to give credit where it's due..... Ukelele isn't "my" tool. The author is a colleague, John Brownie, who should receive all the credit for it. I just posted it on our web site for him.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>JK</DIV><DIV><BR class="khtml-block-placeholder"></DIV></BODY></HTML>