ghis
Newbie
Karma: +0/-0
Posts: 5
|
 |
« on: September 24, 2008, 04:19:21 AM » |
|
Hi,
I have made a (Truetype) font with Typetool, including some ligatures like 'fl' and 'fi'. I am able to find them in Indesign using Glyphs, but in other programs they seem to have disappeared. Typing alt, shift 5 or 6 using other fonts gives me the ligatures 'fi' and 'fl' without fail, but blanks in my own font. So what did I do wrong?
Thanks,
Ghis
|
|
|
|
|
Logged
|
|
|
|
Der FontMeister
Jr. Member
Karma: +1/-0
Posts: 84
|
|
« Reply #1 on: September 24, 2008, 02:05:29 PM » |
|
what other apps are you using? there are prefs that you must set to use ligatures...
Jimmy G.
|
|
|
|
|
Logged
|
|
|
|
ghis
Newbie
Karma: +0/-0
Posts: 5
|
|
« Reply #2 on: September 25, 2008, 02:25:39 AM » |
|
Hi Jimmy,
I was confronted with the problem of the vanished ligatures when I wanted to make a website in Freeway Pro 5, but got the same result (i.e. nothing) in Quark XPress 6. And the strange thing is: ligutures in other fonts could be reached in these programs without a problem...
|
|
|
|
|
Logged
|
|
|
|
|
Alex Petrov
|
|
« Reply #3 on: September 25, 2008, 07:32:35 AM » |
|
I think you just have to assign proper name and Unicode index to your ligatures.
|
|
|
|
|
Logged
|
Alex Petrov
|
|
|
ghis
Newbie
Karma: +0/-0
Posts: 5
|
|
« Reply #4 on: September 25, 2008, 11:07:27 AM » |
|
As far as I can see they do have Unicode name (FB01 and FB02), but if they are proper?
|
|
|
|
|
Logged
|
|
|
|
|
Alex Petrov
|
|
« Reply #5 on: September 25, 2008, 11:41:19 AM » |
|
Try duplicate indexes: F001 FB01 and F002 FB02. Open system font Georgia for reference.
|
|
|
|
|
Logged
|
Alex Petrov
|
|
|
ghis
Newbie
Karma: +0/-0
Posts: 5
|
|
« Reply #6 on: September 26, 2008, 05:17:32 AM » |
|
Unfortunately, that didn't work either. I think the solution to my problem lies elsewhere. I noticed 1. that the ligatures are there, but in a different font (I think Helvetica CY, even after I deactivated this Helvetica) 2. that in another font I made the ligatures work properly. So now I think: could it be a font-conflict problem. And what can be done about that?
|
|
|
|
|
Logged
|
|
|
|
|
Alex Petrov
|
|
« Reply #7 on: September 26, 2008, 08:45:03 AM » |
|
Perhaps the problem is just in cached old version of the font? Font caches should be emptied every time you replace the installed font with the new version.
|
|
|
|
|
Logged
|
Alex Petrov
|
|
|
ghis
Newbie
Karma: +0/-0
Posts: 5
|
|
« Reply #8 on: September 26, 2008, 11:26:08 AM » |
|
Sorry, no results...
|
|
|
|
|
Logged
|
|
|
|
|
Alex Petrov
|
|
« Reply #9 on: September 27, 2008, 05:06:11 AM » |
|
Ghis, then email me the font in question. I'll see if it works here.
|
|
|
|
|
Logged
|
Alex Petrov
|
|
|
|
Alex Petrov
|
|
« Reply #10 on: September 30, 2008, 08:26:29 AM » |
|
As it appeared after looking at the font it was exported in the Names mode without proper Unicode indices attached to the glyphs.
|
|
|
|
|
Logged
|
Alex Petrov
|
|
|
Weeman
Newbie
Karma: +0/-0
Posts: 3
|
|
« Reply #11 on: December 27, 2008, 06:10:32 AM » |
|
@ghis, in order to make ligatures work you will need to produce the font as an Opentype file, this will allow other programmes to access the features.
You will also need to do some Opentype scripting in order to substitute one glyph for another, but the basics are relatively simple to do.
|
|
|
|
|
Logged
|
|
|
|
|
