Page 1 of 1

Arabic VS English - localized Feature

Posted: Thu Jan 03, 2019 3:51 pm
by yazode
Hi,

We have a font that has Arabic and Latin (English) glyphs, everything is great except the Multiplication Sign. It is designed for the Arabic language, so when we use it in English it is way bigger and looks bad.
We want to Substitute it with another one we designed when the English language is used.
Do you have any suggestions on how we could do that, because (Required Chaining Context) just replaces the glyph using backtrack and lookahead. If we use a space it doesn’t substitute.
if we use Localized feature it doesn't work in Office Word.

For example:
in Required Chaining Context
(13256×1245) good substitution
(1231 × 1354) doesn’t substitute because of the spaces
please help
this is our script:
designer.JPG
designer.JPG (103.1 KiB) Viewed 554 times

Re: Arabic VS English - localized Feature

Posted: Fri Jan 04, 2019 11:24 am
by Erwin Denissen
You could add a single substitution lookup to the standard ligatures feature (liga) or to the contextual alternates feature (calt) for Latin script.

Re: Arabic VS English - localized Feature

Posted: Fri Jan 04, 2019 4:20 pm
by yazode
Erwin Denissen wrote:
Fri Jan 04, 2019 11:24 am
You could add a single substitution lookup to the standard ligatures feature (liga) or to the contextual alternates feature (calt) for Latin script.
Thank you so much. I'll try that and I'll update you

Re: Arabic VS English - localized Feature

Posted: Sat Jan 05, 2019 1:27 am
by yazode
Erwin Denissen wrote:
Fri Jan 04, 2019 11:24 am
You could add a single substitution lookup to the standard ligatures feature (liga) or to the contextual alternates feature (calt) for Latin script.
unfortunately it didn't work.

Contextual Alternates gave similar results to Required Chaining Context.

standard ligatures also requires a string of characters. and if space is involved then it doesn't work

any ideas?