On 12/06/2010 04:02 PM, Khaled Hosny wrote:
On Mon, Dec 06, 2010 at 03:55:13PM +0100, Pander wrote:
On 2010-12-04 18:28, Taco Hoekwater wrote:
On 12/04/2010 04:47 PM, Pander wrote:
But the font "Romande ADF Style Std" has only the following ligatures:
liga: f_f_i, f_i, f_f, f_f_l, f_l, germandbls
dlig: s_t
rlig: AE, ae, OE, oe
According to TTX there are more, see
If the target glyph does not exist, it seems fontforge& ICU silently
remove the lookup entry, whereas TTX does not. There appears to really
not be a uniE001 nor a uniE002 glyph in the font.
Still the following needs attention.
Rendered correctly by LuaLateX:
AE OE ae ff fi fl oe ss
rendered as white space:
ffi ffl st
not rendered because of missing glyphs: (reported at font's maintainer)
ct cp
I just tried this with context, and I get visible ligature renderings
for all sequences, except for separate glyphs c,t and c,p instead of
a ligature. I think that is exactly as it should be.
My input was:
\definefontfeature[romande][liga=yes,dlig=yes,rlig=yes]
\definefontsynonym[romande][file:RomandeADFStyleStd-Regular][features=romande]
\starttext
\definedfont[romande] AE OE ae ff fi fl oe ss ffi ffl st ct cp
\stoptext
Best wishes,
Taco
--------------------------------------------------
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
