Problem with character variants / ligatures

[eskel]

Hi.

I'm trying to add diacritic signs to a font, to localize it for my language. (Czech, charset Windows-1250) The problem is, it's a script font and uses postscript glyph variants such as "p.end".

Once I export the edited font and preview it in Photoshop or CSS, the ligatures stop working.

We've bought the Pro license hoping the advanced features would help us, but it doesn't seem to make a difference. It's a great software, would have bought it anyway, but we need to get this resolved somehow.
Not sure if it's a bug or ignorance on my part. Could someone please take a look?

Here are the files:

original font: dl.dropboxusercontent.com/u/20969924/Font/Mission-Script.otf
edited version otf: dl.dropboxusercontent.com/u/20969924/Font/Mission-Script-CE.otf
edited version gfs: dl.dropboxusercontent.com/u/20969924/Font/Mission-Script-CE.gfs

Watch for small "p" glyph at the end of a word for example, it should be without the tail.

Any help would be much appreciated.

[Allan Murray]

Type 3.2 has two options for inserting OpenType features in an edited font:
1 - retain only the original OpenType features
2 - input only new ones from scripts

In the above font you have opted to insert new ones, and you have chosen all the default scripts that come with Type 3.2. But this is less than the number of OpenType features in the original font. I think maybe you should have chosen the 'retain original OpenType features' option. Unfortunately you will have to go back to the original font if you want to retain all those features, as they are not longer in the CE version of your font.

The only other thing you can do is to recreate the original features with scripts.
eg if you add the line:
sub p p by p_p;
to the standard ligatures.feax file, you will get your pp ligature back (but there are many other features in the original font - some of them not supported by creation via script in Type 3.2).

[eskel]

Thanks for your reply.
Now I went step by step, saving the font and testing it after each operation. The moment it breaks down is when I create new glyph.

I can rename the font, change 'active' typeset (although I'm not sure what it means), but when I click to create new glyph and accept the prompt 'create a new glyph mapped to this character?', I loose the ligatures. There is no indication for me that I'm switching to new OpenType features. Also no idea how to retain the old OTF features and also create new glyphs. Can it be done? (preferably without learning how the scripting works

Again, thank you very much for helping me out.

[Allan Murray]

Yes, sorry - at present if you add glyphs then you can no longer retain the original OpenType features.
This is unnecessarily restrictive (as opposed to removing glyphs - which could be a problem, as the original OpenType tables may then reference glyphs which no longer exist), and I will fix this in the current update which is being worked on at the moment.

[eskel]

That would be awesome, thank you very much

[Allan Murray]

This has been updated in version 3.2.024 (Windows) and 3.2.013x (OS X).

[eskel]

That solved my problem perfectly, thanks a lot.