Problem with Thai script

[andmocychmen]

I'm working on a project for a client, but I am unable to complete it, as AD does not seem to support Thai script on iPad. I did not face this problem on the desktop version, but here the following problem occurs : Diacritics appear on the side of the parent letter instead of being on top of it. The dashed circle should be the position of the parent letter.

Can this be fixed please? I need to complete my job soon. Thanks.

PS: similar but not exactly the same problem as 

 

[kenmcd]

On 9/5/2021 at 3:32 AM, andmocychmen said:

as AD does not seem to support Thai script on iPad.

The problem is Apple does not follow OpenType standards in their proprietary fonts.
So the real problem is Apple.
That looks like the Thonburi font from Apple.
The Thonburi font includes non-standard tables such as feat, morx, and Zapf.
I think the morx table is the one they use for the diacritics.

Affinity apps currently do not support the non-standard morx table.
I hope they never support it (and not submit to Apple's nonsense).
But, it is my understanding they may add support some time in the future. Bleah.

On 9/5/2021 at 3:32 AM, andmocychmen said:

Diacritics appear on the side of the parent letter instead of being on top of it. The dashed circle should be the position of the parent letter.

That is because Apple actually includes those dotted circles in the diacritic glyphs.
I guess the shaper is supposed to remove them - total nonsense.
Normally when you see the dotted circle below diacritics it is only used to demo the diacritic.
It is a separate base character, not part of the diacritic glyph.
More Apple making sure their fonts do not work in other operating systems and apps.

I saw your post about some Google Fonts work and some do not, but I have not looked at why that is the case. My guess it is that certain OpenType features are used or not used, and there are different ways of stacking diacritics (my #1 guess). I would assume the Affinity folks know the actual situation.

Your only option at the moment is to use an OpenType font which follows the standards
and is constructed in a manner which works in current Affinity apps.

[Alfred]

7 hours ago, LibreTraining said:

The problem is Apple does not follow OpenType standards in their proprietary fonts.

Read all about it!

[kenmcd]

14 hours ago, Alfred said:

Read all about it!

Been there. Done that. :-)
But those are Apple's own docs, not the actual OpenType standards.
The ISO Open Font Format standard is in the pipeline now (an update and expansion).
I am sure they will not comply with that either.

Apple's ignoring the standards and doing their own thing, along with their intentional sabotage of fonts which do otherwise comply, just creates problems for unsuspecting users (victims).
Like this one and other issues posted in here the forum.

[Alfred]

49 minutes ago, LibreTraining said:

Been there. Done that. :-)
But those are Apple's own docs, not the actual OpenType standards.

Sorry, I thought it was clear that I was referring to the proprietary Apple Advanced Typography, not OpenType.

[andmocychmen]

Thank you all. Working on this and will post some update soon.