boeonoz
-
Posts
5 -
Joined
-
Last visited
Posts posted by boeonoz
-
-
On 1/18/2023 at 7:05 AM, MikeTO said:
Hi, I saw the same issue as you, it worked in v1 but not in v2.
But then I uninstalled the fonts you sent me (version 2.000) and replaced them with the latest version of these fonts from Google's site (version 2.001) and it worked well in Affinity 2.0.3.
So, please edit your last post (click the ... in its upper right) and delete the font files from the post to avoid issues, and then download the latest version of this font from Google: https://fonts.google.com/noto/specimen/Noto+Sans+Thai
Install this font and then restart Affinity. Please let me know if this solves it for you.
Cheers
Thank you for your reply, but I still can't find exact font that I use in the link.
It seems to be normal Noto Sans not the UI one, but after testing it still having same symptom.
V1.10.5 don't having this issue
V2.0.0 don't having this issue
V2.0.3 having issue
Thank you.
-
On 1/17/2023 at 9:51 PM, MikeTO said:
Hi and welcome to the forum.
Could you please make a test document in v1 to share here?
Using v1, copy that first line of text with the problem to a new document and save it.
Thank you
I have attached V1 save file and also include font in this upload (I hope it is correct one, Google Font - Noto Sans Thai UI). Font just for sample purpose I hope there is no issue with their licensing.
Thank you.
-

.png.f5028fa7d8f3fbfb42c26f6020ab4b94.png)

V2 Local Font Issue?
in Affinity on Desktop Questions (macOS and Windows)
Posted
Thank you for your finding. I still wonder why V1 and V2.0.0 (In my finding) handle this perfectly (If set correct Typography Script) but V2.0.3 is not, I do hope they will do something with next updates.
Thank you again.