Fontlab, ttf/otf and ligatures

Primary tabs

6 posts / 0 new
Last post
Typofan's picture
Offline
Joined: 26 Feb 2005 - 9:43am
Fontlab, ttf/otf and ligatures
0

Hi all,

I am creating a font with fontlab 4.6 that uses non-standard (custom) ligatures.

Everything seems ok when compiling the font and testinf it in the preview pane.

nb: I entered the ligatures by first drawing the glyphs and assigning names to them, then, I entered a feature liga { sub b a by ba; } liga.

where “ba” is a custom caracter.

The thing is, although it compiles and is working perfectly in the preview pane, the ttf or otf fontlab generates from it seems unaware of the ligatures…

Is there anything I could do about it (I think there is… but what is it?)?

thanks in advance!

paul d hunt's picture
Offline
Joined: 15 Jan 2004 - 11:00am
0

the software you’re using has to implement these features. so far, only Adobe CS products (and InDesign 2.0) support automatic substitution of OT features.

If you’re hoping to see automatic ligature substitution in Microsoft apps or in Quark, you’ll have to wait until they release software that supports these things.

Typofan's picture
Offline
Joined: 26 Feb 2005 - 9:43am
0

So there is no way to have OT features work automatically… Is there instead any workaround or trick to have the desired result displayed in any application that at least supports ttf?

Many thanks.

Tiffany Wardle's picture
Offline
Joined: 13 Jul 2001 - 11:00am
0

Problems with custom ligature creation in FontLab

This is a thread started in the GENERAL area which I thought might get a few more useful eyeballs on it if it were here in the BUILD area.

Simon Daniels's picture
Offline
Joined: 11 Apr 2002 - 6:37pm
0

On Windows the Uniscribe component (usp10.dll) handles the application of OpenType features — traditionally it’s only been used for the so-called complex script languages. Automatic features for are supported by the latest version of Uniscribe, supplied with XP SP2, so in notepad and elsewhere fonts like Zapfino and Bickham Script have their default OTL features applied.

Office uses its own version of Uniscribe, and also bypasses Uniscribe for all but complex script languages due to the performance issues.

Not sure about the Mac but I think there’s a similar situation there too.

Behnam's picture
Offline
Joined: 7 Feb 2005 - 5:37pm
0

If you want them to be permanent and not optional, have you tried to put them in ‘rlig’?