Help with ligatures, etc.

Hey, thanks for the replies, guys! Things still aren’t working right, though. I regenerated the font with the legacy kerning table added, and that had no effect – I still have this weird extra space to the right of that double-longs ligature. I have no idea why it’s even arising like that, as my right-hand bearing on that glyph is actually “negative” (if you know what I mean), and yet when it renders in my ebook it’s almost as though there’s an extra space in-between it and the adjacent character.

Another strange thing I’ve noticed, too, is that only some of my ligature lookups seem to be working – only lowercase ligs, but not uppercase ligs (I haven’t tested out every single one of my ligs, but that would seem to be the case). So my st, ct, ſſ, ſt, etc. ligs all come out just fine, but my SS, WI, etc. ligs don’t render at all. (All my ligature lookups are standard, by the way, not discretionary.)

How weird is that? I have NO idea what I’m doing anymore! :unamused:

Do send us the font along with some sample text so we can look into it.

I’ve been wanting to just post the font here, actually, hoping that someone could take a look at it, but that thought has brought up another issue – what if I were to decide I want to sell this font (as I’ve been urged to by other professional type designer friends I have)? By posting it here, aren’t I just effectively giving it away for free (albeit in a preliminary, unfinalized form)?

Oh, crap… I just said to myself “what the heck” and figured I share the font here anyway, along with my ebook, too, so you could see what’s “going funny,” wrote up a nice description of the issues-at-hand, attached the font (no problem) but then when I tried to attach the ebook I got a message saying “invalid file extension” (and it’s not!). So I tried changing the “.epub” extension to “.zip” but then I got a message saying “file too large” (1.8 megs is too large???).

I could load the ebook up to my website instead and then post the link for it here, if that’s okay to do – or if you’re not able to view ebooks, I could take some screenshots instead.

If you are not sure if you want to sell the font, then better not post it here. You can send it to me; I’ll send you a pm with my email address.

Nope. As long as your font contains at least some information identifying you as the author in the Legal Tab of Font Properties, it is protected by copyright.

Even if you sell it, Tom can buy it, then share it with Dick and Harry if he does not care about copyright infringements. Protecting fonts is difficult, and expensive, if you need to hire lawyers.

The same goes for E-books.

Okay, what the heck – here’s my font (attached). I think my needing advice here is probably more important than worrying about “font theft” (which, as you pointed out, is pretty hard to police anyway). :wink: I’ve also attached here a couple screenshots from my ebook (as it looks in iBooks on my iPad) that I’ve been working on that goes along with it. The reason the font and the ebook “go together” is because the ebook is a digital version of the original 1561 text from which I created this font (although I only was able to glean just the most basic character set from that, and had to create all the additional glyphs – Greek, Cyrillic, symbols, etc. – myself).

Some things to note in the ebook screenshots…

  • In the main book “cover” graphic (which is tentative – like everything else in the book) you’ll see the word “WICKEDNESSE” in all-caps. There’s actually four ligatures in that one word: WI, CK, DN, and SS. In creating that cover image in Photoshop, all the ligatures – never mind the kerning – come out just fine, no problems!

  • And this brings up where all the main issues are with my font, i.e. in the actual text itself. If you look at the screenshot of the title page, you’ll see both “WICKEDNESSE” again as well as “Wickedneſſe” (with only an initial cap) – it’s there twice for the moment just for testing purposes. As you can see, in this all-caps version of the word, none of those uppercase ligs show up – but as you can also see here, the lowercase ligs do show up no problem! You can see an “st” lig in “Detestable,” as well as the double-longs one in “Wickedneſſe.” In that latter instance, however, there’s way too much space between it and the following “e” (and also a little too much between the double-longs and the preceding “e,” too).

Again, everything seems to work fine in Photoshop – it’s very mysterious to me why things are only “half-working” in my ebook. :frowning:

And just a note on my font…

  • Please be gentle with me! Apart from a very simple font of my handwriting that I did a decade or so ago, this is actually my very first “real” font that I’ve ever put any great effort into, so I’m sure it’s far from perfect – but I am trying my best to get it right (with your help)! :wink: And yes, I still have a ton of empty glyphs in my PUA – I’ll delete all those later on, as I just left those empty slots there for now as “placeholders” in case I need to make some more ligs (or alts).


    Any thoughts, comments, suggestions, critiques, scathing condemnations, etc. welcome! :wink:
    Wickednesse.ttf (831 KB)

Okay, I’m trying very hard to do this kerning thing right this time – I think it was a combined effort of miscommunication on Bhikkhu’s part and misunderstanding on my part in why I went off in the wrong direction with this before. In entering into this (as a newbie) I assumed – perhaps naively, but not unnaturally – that when creating a font, at a certain point (when you’re reasonably happy with your glyphs) you run autokern, first, and then you start tweaking your kerning from there, whether that’s by making additional adjustments to those now-already-existing pairs, or else adding in additional pairs that autokerning didn’t take into account (like one’s PUA glyphs).

It was from this standpoint that I approached this forum with the query for how to kern those PUA glyphs (where I have a LOT of ligs, etc.), and Bhikkhu very kindly and generously provided me with assistance – but the one thing he did NOT say was “Forget about autokerning completely and just do it all yourself, from scratch.”

And aye, there’s the rub, and where I’ve been pulling my hair out for weeks now trying to figure this out and understand this. :wink: I do hope I have that understanding correct now (and Bhikkhu, even though you weren’t clear about that, and do think this was a “combined effort” in it taking so long to sink in, nevertheless I’ll still take the bulk of the blame for this for being soooooo dang slow in grasping it), and that’s what I’ve been endeavouring to do. :slight_smile:

So I started by deleting ALL my pair adjustments completely – and then looked at various samples of my font, and said to myself “Hey, without any kerning at all, it actually doesn’t look too bad! So I guess I’ve done a pretty reasonable job on getting my bearings right, at the very least.” :slight_smile: However, I couldn’t help but notice that some of my ligs (in the PUA) did need additional kerning, and so that’s what I’ve been working on.

And this raises TWO issues for me (and perhaps might be an issue for FontCreator’s engineers, too, if there’s a problem with the software itself).

To explain, after working on my font (off and on) for the past few days, here’s a revised version of one of the images I loaded up earlier (elsehwere)…


For the most part, I’m quite happy to see that the kerning looks pretty reasonable (even with rather limited pair adjustments – indeed, almost none at all on the main glyphs, but mostly just on some of the ligatures in my PUA). The bulk of the kerning issues that I had cleared up had to do with fixing the spacing between those PUA ligatures and whatever characters came after them, but if you look at the above image, just a few lines down on the left-hand side you’ll see the word “testefieth” (or “teſtifieth,” rather, with the longs), and there’s too much space between the “e” and the “ſti” lig.

So I take a look at that pairing in my preview and I see this…


…which reflects what I see in my Photoshopped image above, of course – i.e. there’s too much space in-between the “e” and the “ſti” lig.

So I go in my OT Designer, and create a new kerning pair for those…


…then I press ok and then THIS is what I see…

Without making any adjustments at all, not only is there not “too much” space, but if anything there’s too little and the glyphs are bumped right up against each other.

Huh??? What’s going on there? Shouldn’t what I see at first (before moving anything around) reflect what I saw before, i.e. too much space between those two glyphs? Am I not grasping something here, or is there an issue with the software itself?

And then comes my second conundrum…

Having added in that one additional kerning pair, my code won’t validate because I added in that “a” on it’s own, and I already have it included in a class for kerning it “second” with regard to other pair adjustments (I would have had the same problem, of course, if I had tried to create an additional “first” class including that “a”).

Clearly I don’t understand classes. Like, for each of the vowels (especially) I created basically two sets of “second” classes – for example, one for “a” (no accents) and accents that, say, hung from the right-bottom corner or wherever, which wouldn’t affect kerning next to glyphs to the left, and then another kerning pair for all the “a”-characters that did have accents up top.

But now I have to kern the “a” (and all its variants) as the first glyph in the pair adjustment – but clearly those classes that I made before wouldn’t apply to this, you need different criteria for picking/choosing which glyphs are included in each class.

I’m not sure if I’ve explained that well, but do you see the dilemma I’m having here? It’s totally different to kern glyphs based on their right-side shape and their left-side shape, and yet you can only create classes for each glyph once.

So what’s a poor dummy like me to do? :open_mouth:

Never mind, I think I may have discovered the reason (and solution) for all my confusion – my stupid bearings are off on a whole pile of my ligatures. D’oh. :unamused:

Sorry for putting you all through that. :blush: