How to make non-unicoded added glyphsdata friendly. with auto-generated OT features

Glyphs
1

Hi;

if my font contains characters/ligature-characters that are not part of unicode charts, if I added them to a glyphdata.xml with all possible attributes filled (Name, category, case, script, decompose, etc) . and give them nice names.

Can glyphsapp auto-generate OT features code for them?

I’m not familiar with coding whatsoever (that why we like and use glyphsapp)

screenshot of examples of non-unicoded characters: isolate + initial form + final form
in font there will be other different types of glyphs & ligatures & positions

help.

Screen Shot 2023-09-18 at 3.29.04 PM
Screen Shot 2023-09-18 at 3.29.04 PM2000×816 66.1 KB

2

You don’t need to add them to glyphData. Put the name parts together with underscores.

But the examples you showed shouldn’t need to be precomposed glyphs. Those can be made with mark positioning.

1 Like
3

Thanks Georg!

if you mean Hamza and dots?
yes mark positioning are involved for hamza and dots (& other diacritics)
but these diacritics are not independent in my font (especially dots)

thanks I will try your advice.

4

Before you get too far down the wrong path, do yourself a favour and read this article on designing Arabic in Glyphs (if you haven’t already done so)

2 Likes
5

What do you type to get to those ligatures. And what names do you use for them?

6

I will post more to this if I encounter:

theh_khah-ar
theh_khah-ar.init
theh_jeem-ar.init

tcheh_alefMaksura-ar
tcheh_alefMaksura-ar.fina
tcheh_yeh-ar
tcheh_yeh-ar.fina
tcheh_yehHamzaabove-ar
tcheh_yehHamzaabove-ar.fina
tcheh_meem-ar
tcheh_meem-ar.init

dyeh_alefMaksura-ar
dyeh_alefMaksura-ar.fina
dyeh_yeh-ar
dyeh_yeh-ar.fina
dyeh_yehHamzaabove-ar
dyeh_yehHamzaabove-ar.fina
dyeh_meem-ar
dyeh_meem-ar.init

tcheheh_alefMaksura-ar
tcheheh_alefMaksura-ar.fina
tcheheh_yeh-ar
tcheheh_yeh-ar.fina
tcheheh_yehHamzaabove-ar
tcheheh_yehHamzaabove-ar.fina
tcheheh_meem-ar
tcheheh_meem-ar.init

seen_zain-ar
seen_zain-ar.fina
sheen_zain-ar
sheen_zain-ar.fina

seen_jeh-ar
seen_jeh-ar.fina
sheen_jeh-ar
sheen_jeh-ar.fina

seen_rreh-ar
seen_rreh-ar.fina
sheen_rreh-ar
sheen_rreh-ar.fina

sad_zain-ar
sad_zain-ar.fina
dad_zain-ar
dad_zain-ar.fina

sad_jeh-ar
sad_jeh-ar.fina
dad_jeh-ar
dad_jeh-ar.fina

sad_rreh-ar
sad_rreh-ar.fina
dad_rreh-ar
dad_rreh-ar.fina



seen_yehHamzaabove-ar
seen_yehHamzaabove-ar.fina
sheen_yehHamzaabove-ar
sheen_yehHamzaabove-ar.fina


sad_yehHamzaabove-ar
sad_yehHamzaabove-ar.fina
dad_yehHamzaabove-ar
dad_yehHamzaabove-ar.fina

yehHamzaabove-ar_jeem.ar
yehHamzaabove-ar_jeem.ar.fina
yehHamzaabove-ar_hah.ar
yehHamzaabove-ar_hah.ar.fina
yehHamzaabove-ar_khah.ar
yehHamzaabove-ar_khah.ar.fina
yehHamzaabove-ar_hah.ar
yehHamzaabove-ar_hah.ar.fina
yehHamzaabove-ar_tcheh.ar
yehHamzaabove-ar_tcheh.ar.fina
yehHamzaabove-ar_tcheheh.ar
yehHamzaabove-ar_tcheheh.ar.fina

alefMaksura_jeem.ar
alefMaksura_jeem.ar.fina
alefMaksura_hah.ar
alefMaksura_hah.ar.fina
alefMaksura_khah.ar
alefMaksura_khah.ar.fina
alefMaksura_tcheh.ar
alefMaksura_tcheh.ar.fina
alefMaksura_tcheheh.ar
alefMaksura_tcheheh.ar.fina

behDotless_jeem.ar
behDotless_jeem.ar.fina
behDotless_hah.ar
behDotless_hah.ar.fina
behDotless_khah.ar
behDotless_khah.ar.fina
behDotless_tcheh.ar
behDotless_tcheh.ar.fina
behDotless_tcheheh.ar
behDotless_tcheheh.ar.fina

beh_hah.ar
beh_hah.ar.fina
beh_tcheh.ar
beh_tcheh.ar.fina
beh_tcheheh.ar
beh_tcheheh.ar.fina

teh_hah.ar
teh_hah.ar.fina
teh_tcheh.ar
teh_tcheh.ar.fina
teh_tcheheh.ar
teh_tcheheh.ar.fina

theh_hah.ar
theh_hah.ar.fina
theh_tcheh.ar
theh_tcheh.ar.fina
theh_tcheheh.ar
theh_tcheheh.ar.fina

there are more of such combinations i will post sometime
\thanks

7

Most of them look good. Some issues:

yehHamzaabove-ar_jeem.ar > yehHamzaabove_jeem-ar
beh_hah.ar > beh_hah-ar

you have yehHamzaabove-ar_hah.ar twice.

Here is a file with the ligature from the list and automatic features:
Adabic Ligatures.glyphs (43.1 KB)

8

thanks mr georg

i think i made some mistakes of duplicating -ar suffix within a single name.

i will try to post another group of such similar needed combinations within next weekend.

thanks alot.

9

If you stick to the glyphs name scheme, all opentype feature code will be correctly generated with Font Info > Features > Updates.

1 Like
10

Thanks goerg

Just a question
What if i wanted to apply calt salt jalt cswh to be friendly (compatible) with OT features auto-generation

Can I combine two suffixes after each other like (kaf-ar.medi.salt) & kaf-ar.medi.jalt)
I’am aware of ss01 sequence naming
But I don’t know how to apply cswh jalt salt calt

If (for example) I have three medial kaf forms
One regular .medi
Second with a second shape
A third looks like the second but elongated (swach)

I already searched forum & read features 4 tutorials but no clarification of applying calt salt jalt cswh after arabic .fina .medi .init suffixes within a name like
(Kaf-ar.medi.calt) (kaf-ar.medi.cswh)

Thanks

11

You can stack most feature suffixes and you should get the automatic feature code. Except for calt. It needs context and that can’t be derived from the glyph name. So you need to write the calt feature yourself.

And as usual: play around with it and test.

1 Like
12

I did this
I stacked fina suffix with cswh suffix but no feature generated for cswh
i have these in font

feh-ar
feh-ar.cswh

feh-ar.fina
feh-ar.fina.cswh

fehDotless-ar
fehDotless-ar.cswh

fehDotless-ar.fina
fehDotless-ar.fina.cswh

cswh feature not generated !

is there different in glyphs behavior between cswh and swsh?

13

Contextual features cannot be autogenerated because the software cannot guess the contexts for you.

1 Like