build a font for your endangered language...

[Heather Souter]

Kihchi-maarsii pur toñ repoñs, Bill!  Thanks for your response, Bill!

So, I guess that our present way of using <ñ> really is still perhaps the
best (read easiest) compromise for our orthographic purposes?  Or, is it
simply a matter of educating myself (and other potential users of the
orthography) on the process (key strokes necessary) to produce the character
when writing?  Is there a simple way to program a key to produce the
character when hit once (using shift or control or whatever)?  Or, will it
always take a couple of key strokes?

Eekoshi kihtwaam.
Heather

On Fri, May 16, 2008 at 9:48 PM, William J Poser <wjposer at ldc.upenn.edu>
wrote:

> Heather,
>
> Unicode does not encode n with a slash through it as a single codepoint,
> but it does have slash as a combining character. In fact, it has two:
> U+0337 COMBINING SHORT SOLIDUS OVERLAY
> U+0338 COMBINING LONG SOLIDUS OVERLAY
> (The forward slash is called "solidus" in Unicode-speak.)
>
> So, you can get a lower-case n overlaid by a long slash by entering
> first the n and then U+0338. They are two separate codepoints but will
> be rendered by Unicode-aware software as the single character you want.
>
> Because this is treated as a sequence of two "characters" in Unicode,
> you may have to do something special to get your sort order the
> way you want it. Such things are a little easier if you can get what you
> want as a single codepoint, but the Unicode Consortium is reluctant
> to add single codepoints for things that can be composed from existing
> combining characters.
>
> Bill
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserv.linguistlist.org/pipermail/ilat/attachments/20080516/bb8621d8/attachment.htm>