garbled font name

[JP GRAY]

I use designer 2 in Japanese.

Some fonts are garbled and not displayed correctly.

I can't confirm the name of the font I am using.

 

 

[Dan C]

Hi @JP GRAY,

Thanks for your report and sorry to see you're having trouble!

Can you please confirm for me, was this font installed from Adobe CC Fonts?

Many thanks

[JP GRAY]

Hi Dan C

I confirm some font about this problem.

I do not use Adobe CC Fonts on my i pad.

Many fonts have this problem,I tell you following example.

American typewriter, Apple symbols, Arial Hebrew, Baskerville, Gill sans, Copperplate, and almost Japanese Fonts.

I`m looking forward to resolve the problem!

Thank you.

 

 

[Dan C]

Thanks for verifying that for me - I've set both my iPad and Affinity app language to Japanese, then used the fonts named above in a new document and all names appear in English for me, as expected.

I then closed and reopened the app and they continue to display as expected, finally I restarted the iPad, and even then these font names continue to display as expected for me.

Can you please confirm:

What version of Affinity iPad is in use?

What version of iOS is installed?

What iPad model are you using?

Many thanks once again!

[JP GRAY]

Thank you for your reply.

I tell you about your question.

 

Affinity designer for i Pad ver 2.0.4

iPad os 16.3

iPad pro 11 inch third generation.

 

Buy the way, in designer ver 1.10.7, same fonts Accurate display.

 

Thank you.

 

 

 

[Dan C]

Many thanks for confirming that for me - a colleague of mine has been able to replicate this issue internally so I'm getting it logged as a bug with our developers now.

I hope this helps

[Affinity Info Bot]

The issue "[iPad] Fonts installed from creative cloud show on context toolbar with name in Chinese " (REF: AFD-6170) has been improved by the developers in internal build "2.1.0.1736".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.