<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 22.02.2011 23:36, John Was wrote:
<blockquote cite="mid:E3C20D4FB35846D086166A0D3ADE5AB7@k2010"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<meta name="GENERATOR" content="MSHTML 8.00.6001.19019">
<style></style>
<div><font face="Arial Unicode MS">Hello</font></div>
<div> </div>
<div><font face="Arial Unicode MS">Forgive the puzzlement of a new
recruit to FontForge (which is installed via Cygwin on a Windows XP
machine). And apologies if this isn't the right forum - though
frequent discussion of font-related issues here gives me hope.</font></div>
<div> </div>
<div><font face="Arial Unicode MS">I edited a font which had just the
fi and fl ligatures (in their true Unicode positions at FB01 and FB02)
and I managed to create tolerable versions of the other three standard
ligatures (ff, ffi, ffl). Using FontForge I have added these in the
slots FB00, FB03, and FB04. But "mapping=tex-text" in the font call
(in plain XeTeX) doesn't access any of them, neither the two that were
there already nor the three that I created; however, the standard ` '
`` and '' for opening and closing quotations do work so the mapping
call is basically functioning as normal. The glyphs are accessible to
TeX if I give them manually as \char"FB00 etc. but I obviously would
like to have them delivered automatically as usual.</font></div>
<div> </div>
<div><font face="Arial Unicode MS">I have tinkered with various
FontForge menus and had hoped that adding 'liga' to the GSUB
window would be sufficient, but there is clearly something I am not
doing right. Can anyone advise?</font></div>
<div> </div>
<div><font face="Arial Unicode MS">Many thanks</font></div>
<div> </div>
<div> </div>
<div><font face="Arial Unicode MS">John</font></div>
<div> </div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
--------------------------------------------------
Subscriptions, Archive, and List information, etc.:
<a class="moz-txt-link-freetext" href="http://tug.org/mailman/listinfo/xetex">http://tug.org/mailman/listinfo/xetex</a>
</pre>
</blockquote>
Hi,<br>
<br>
Here are some simple observations which, I hope, may be of some use to
you. <br>
I assume having \defaultfontfeatures{Ligatures=TeX} activated, of
course.
<style type="text/css">p, li { white-space: pre-wrap; }</style><br>
<br>
1. Fonts which are missing all ligatures except for "fi" and "fl"
usually get these two "wrong" too, i.e., those are not in their "usual"
places, at U+FB00 and U+FB01, so make sure that you have them at those
positions, or they will not be recognized (compare the resulting TTF
font from the attached .sfd file and the original one).<br>
<br>
2. When creating ligatures composed of other ligatures, make sure you
have those also, i.e., to get "ffi" correct, you should have "ff"
created too.<br>
<br>
3. When you create, e.g., "ffi" ligature, name it "f_f_i" and add two
liga entries: <br>
a) f f i <br>
b) f_f (ff) i<br>
This applies to other "compound" ligatures as well. Having "f f i" only
may not be enough and it's possible that it'll get ignored.<br>
<br>
4. The old problem about PDF search unfortunately still remains: only
basic standard ligatures are recognized. I would be happy if someone
knows a way to correct this during font creation or correcting existing
ones.<br>
<br>
In the attachment is an example .sfd file for font Neuton.ttf from <a
href="http://www.fontsquirrel.com/fonts/neuton">http://www.fontsquirrel.com/fonts/neuton</a>
to which I added ligatures "fb", "ff" and "ffh" for testing purposes.<br>
</body>
</html>