David Wooten said this at Fri, 11 Mar 2005 15:40:14 -0800:

>That is, when I try to use 
>any special glyph, be it an accented character of any kind, or e.g. an 
>eth.

Hi David,

I took a look at your file (off-list), and it looks like you're using the
8r encoding. Interesting that you bring the "eth" up, because that
character doesn't exist in the 8r encoding.

> The result of something like \"a (or \"{a}) is _a_ without the 
>diacritic. 

Hmm. What do your typescript definitions look like, then? Does ConTeXt
know you're using 8r as the encoding for the font?

>Curiously (to me, at least:), if I enter the actual glyph: 
>ä, it gives me the character I need…but only for a few runs!

Okay, that now becomes an interaction between regime (input file
encoding) and the rest. It could be coincidence that ä is in the same
slot (228) with both regime and encoding. Which regime are you using? Are
you sure it lines up with the encoding in (say) TeXshop?

>Some trials evince an ff-ligature as the diacritic.

That's another data point pointing to the encoding not being in synch.

So. More input required, but right now I'm eyeing the encoding with suspicion.

adam

P.S. As a side point, Andulka does indeed look like a nice, sturdy,
legible text font. A bit like the free (but masterfully drawn) Charter,
but with a lot more personality.
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept.     atl@comp.lancs.ac.uk
 Lancaster University, InfoLab21        +44(0)1524/510.514
 Lancaster, LA1 4WA, UK             Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-