Hayavadana

yes, I agree. That is why I am requesting. I hope They will consider (I know it may/will take far time .) Thanks for replay.

"Bengali shaping in OpenType"
That is about the shaping engine issues I discussed above, not some deficiency in handling basic OpenType tables.
It is another good example of what needs to be programmed into the shaping engine.

Affinity applications already have "Unicode font support."
That is not the issue.
The issue is about creating an entirely new text rendering or shaping engine for the Indic scripts.
That is a very complex task.
For example, all you have to do is take all of the info on these pages:
https://r12a.github.io/scripts/devanagari/
https://www.omniglot.com/language/articles/devanagari.htm
And convert that into If/Then/Else code.
Use that to process the input "Unicode" characters.
Then connect that to the OpenType feature code in the fonts to build the correct text.
And then output the "Unicode" (and/or glyphs).
This is a huge task.

I see nothing in the post by @wonderings that deserves to be labelled as ‘abuse’.
The Affinity apps do support Unicode, but if you know a modest amount about Unicode you should be aware that there’s a huge range of features in the specification. Unicode Indic fonts require the use of particular features that are not currently supported by the Affinity apps, but most other fonts work very well.

Hi @Hayavadana,
I'm part of the Affinity Forums moderation team and a member of Technical Support for Affinity/Serif - I understand this is a little counter intuitive, however I'm commenting here to inform you that our team doesn't tend to reply to feature requests / feedback here, my apologies.
We take all feedback into consideration and our team read these posts, but due to the nature of feature requests we don't usually respond to these posts as we can't provide any timescales or promises.
I hope this clears things up