Publisher 2.6 Problem with Arial font

[anto]

If you select Artistic text tool, only some of the 9 digits on the keyboard are printed. I have only 579.

[Hangman]

Hi @anto,

Printed as in you can only physically type 5, 7 and 9 or only those characters print to a printer?

It makes little sense, can you ‘print’ all numbers using Frame Text using Arial?

 

[anto]

1 minute ago, Hangman said:

It makes little sense, can you ‘print’ all numbers using Frame Text using Arial?

 

Sorry, 'print' means 'type' in document.

[anto]

Here is video

 

 

[MikeTO]

This is very odd. I can't duplicate it even with Langauge>Spelling set to Ukrainian and Script set specifically to Cyrillic.

Is it happening only with Arial? If you choose Select All and then change the font do the missing numbers appear?

Could you save that test file and upload it for us? It would be interesting too see if it opens this way on my computer.

Thanks

[MikeTO]

If the problem is just with Arial, please see this reply to somebody else which might provide the answer. You might have recently installed a font that has an internal name of Arial and wasn't renamed properly.

 

[anto]

4 minutes ago, MikeTO said:

Is it happening only with Arial? If you choose Select All and then change the font do the missing numbers appear?

 

Yes

[carl123]

Can you upload a document with 1234567890 typed in Artistic text using that Arial font?

[Gabe]

We are aware of weird issues when using Arial. It's similar to your other issue where you saw Greek characters. It's not a font conflict issue, but an internal issue on our end. 

[Affinity Info Bot]

An issue raised in this thread ("Arial text rendered in app fails to show or appears Greek after some actions.") has now been reported to the developers by the testing team (Ref: AF-5329). Thank you very much for reporting this issue to us.

[Affinity Info Bot]

The issue "Arial text rendered in app fails to show or appears Greek after some actions." (REF: AF-5329) has been fixed by the developers in the latest beta build (2.6.0.3058). The fix 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 @Affinity Info Bot to notify us.