Unexpected behavior of 'disable automatic alignment' in glyphs 3

1

Salam

I see an unexpected behavior of ‘disable automatic alignment’ in glyphs 3. for combining each two glyphs into one via glyphs generation recipe.

  • mekkablue script “encoding converter” used to correct old wrong mapped axt font.
    the option ‘disable automatic alignment’ is unchecked to get the desired output. but still there is no true alignment.

glyphs 2 is doing the job right.
but not glyphs 3

Another problem with the script is that in ‘glyphs 3’ letters gets classified as PUA

Screenshot 1445-12-23 at 10.46.06 PM
Screenshot 1445-12-23 at 10.46.06 PM2964×1770 792 KB

2

It depends on the input and on your GlyphData. The script just renames the glyphs, it does not assign Unicode values. Do you have custom glyphdata?

3

No, I don’t have any custom glyphdata on either versions of glyphs.app

I also tried both ways ‘with and without’ adding the custom parameter ‘use arabic unicodes for presentation forms ‘in glyphs 3’

All output is the same
The two combined glyphs does not align properly in glyphs 3

4

It seems that the components are in the wrong order. Can you show a screenshot of the parts that make up one of the misaligned glyphs?

You show that the glyph percent-ar has a unicode of F025. That is not the correct unicode. Try running “Glyph > Update glyph info”.

5

screenshot

Screenshot 1445-12-24 at 2.00.56 AM
Screenshot 1445-12-24 at 2.00.56 AM1828×2000 303 KB

sorry for typo.
the order is 2+1=3

the very same font does not show this misalignment and overlapping in glyphs 2

6
  • the script on glyphs 2 does both renaming and reassignment of the true unicodes. not the case with glyphs 3

I also tried the process with custom parameter Use Arabic Presentation Form Unicodes

-renamed letters retain wrong old mapping unicodes and thus classified as PUA

7

Can you manually remove the unicode. Then run “Glyph > Update glyphs info”?

8

Part 2 needs to be 1 in order for automatic alignment to work, alignment works RTL for Arabic letters.

9

Don’t. It breaks your font.

This is just intended for very specific testing needs. Or conversion compatibility with software from the nineties.

10

PUA codes are sticky in order to allow custom naming.

The script only renames. And Glyphs assigns a Unicode (or not) based on the glyph name. The issue appears to be that PUA Unicode values were assigned before running the script.

11

Nothing changed.

recipe order is as you mentioned but really not resolved by this

basically:

  • the script on glyphs 2 do the renaming and assign a unicode (satisfying result)
  • the script on glyphs 3 do the renaming but retain old wrong unicode. thus PUA classification (wrong result)

for the recipe part:

  • recipe works fine on glyphs 2 with ‘disable automatic alignment’ unchecked (good result)
  • on glyphs 3 the alignment is wrong.

yes. the PUA unicode values is there in the old font. but still glyphs 2 did the job. but not glyphs 3.

12

Can you send me the file?

13

Sure.
I’ve sent a DM

Thanks.