How to reposition character before sequence of letters?

[Bernie Cossentino]

Forgive me for bumping up my last post this one time. I'm hoping someone can point me in the right direction with regards to the baseline query above.

Thank you

[Erwin Denissen]

It is a bug because we try to make FontCreator more flexible than the specs allow.

In the final font classes within a ligature item are not allowed. Right now FontCreator will store it as one item. For example
sub bar @ABC @abc -> ".null";
will end up in the font as:
sub bar A a -> ".null";

We'll have this fixed with the next upcoming release.

For now you'll have to provide the individual items:
lookup Ligature1 {
sub bar A a -> ".null";
sub bar A b -> ".null";
sub bar A c -> ".null";
sub bar B a -> ".null";
sub bar B b -> ".null";
sub bar B c -> ".null";
sub bar C a -> ".null";
sub bar C b -> ".null";
sub bar C c -> ".null";
}

Thanks for your reply. But I must say this news is very discouraging. Seems like a significant program bug to me.
My target font (stemming from the test above) would have to contain over 80 "individual" sub entries for the ligature lookup instead of just one (when using classes).

How soon is the upcoming release?

That bug has been fixed.

Forgive me for bumping up my last post this one time. I'm hoping someone can point me in the right direction with regards to the baseline query above.

Thank you

I have no idea how to fix that, as this is a total different problem and might require a completely new solution.

[Bernie Cossentino]

It is a bug because we try to make FontCreator more flexible than the specs allow.

In the final font classes within a ligature item are not allowed. Right now FontCreator will store it as one item. For example
sub bar @ABC @abc -> ".null";
will end up in the font as:
sub bar A a -> ".null";

We'll have this fixed with the next upcoming release.

For now you'll have to provide the individual items:
lookup Ligature1 {
sub bar A a -> ".null";
sub bar A b -> ".null";
sub bar A c -> ".null";
sub bar B a -> ".null";
sub bar B b -> ".null";
sub bar B c -> ".null";
sub bar C a -> ".null";
sub bar C b -> ".null";
sub bar C c -> ".null";
}

Thanks for your reply. But I must say this news is very discouraging. Seems like a significant program bug to me.
My target font (stemming from the test above) would have to contain over 80 "individual" sub entries for the ligature lookup instead of just one (when using classes).

How soon is the upcoming release?

That bug has been fixed.

Thanks for the news on the fix. Is there a patch available for download?

[Bhikkhu Pesala]

The latest version is build 2430.

When an update is available you can fetch it from the Help menu, Check for Updates.

You can change the automatic check from one week to every day in Tools, Options, General, if you wish.

The Changelog will also tell you when each update was released, with a brief list of the changes made.

[Bernie Cossentino]

The latest version is build 2430.

When an update is available you can fetch it from the Help menu, Check for Updates.

You can change the automatic check from one week to every day in Tools, Options, General, if you wish.

The Changelog will also tell you when each update was released, with a brief list of the changes made.

Thank you