Publisher 2.6 shows tricks with fonts

[anto]

It's not the first time Publisher has written in hieroglyphics

 

 

 

[anto]

No spaces between words in Arial font

 

 

[Hangman]

Hi @anto,

That looks like a font conflict to me...

Can you show us all nine weights of Arial you have installed...

From your screen recording when converting between Anticva and Arial, Arial is not displaying the letters, 't', 'o' or 's'...

If you uninstall Anticva completely and then reboot Publisher do you still see the same issue with Arial?

[anto]

5 minutes ago, Hangman said:

If you uninstall Anticva completely and then reboot Publisher do you still see the same issue with Arial?

The problem has not disappeared.

 

 

[Hangman]

1 minute ago, anto said:

The problem has not disappeared.

Thanks for checking... Have you installed any other new fonts recently?

Can you upload a Publisher document like the one shown in your screen recording, where you see the Greek letters? That way, we can see how it's interpreted when we open it, which may give us some clues as to what is going on.

[anto]

I don't choose the font. It is selected by default in Publisher.

 

 

[Latens]

I think you have a frankenfont installed that takes over Arial because its name is used in its settings.

[Hangman]

Just now, anto said:

I don't choose the font. It is selected by default in Publisher.

I realise that but there is clearly some font conflict which is why a sample document would be helpful...

[anto]

4 minutes ago, Hangman said:

Can you upload a Publisher document like the one shown in your screen recording, where you see the Greek letters?

When I opened the saved file, it was displayed fine.

[Hangman]

Just now, anto said:

When I opened the saved file, it was displayed fine.

And if you add some additional text to the re-opened document, does Arial still get converted to Greek characters?

[anto]

5 minutes ago, Return said:

I think you have a frankenfont installed that takes over Arial because its name is used in its settings.

I found only the following fonts with a similar name

[Hangman]

Just now, anto said:

I found only the following fonts with a similar name

I think @Return meant you have a dodgy font installed rather than a font called Frankenfont...

[Latens]

yes frankenfont as in Frankenstein 

[anto]

12 minutes ago, Hangman said:

And if you add some additional text to the re-opened document, does Arial still get converted to Greek characters?

If I open this document first after start Publisher, it displays correctly. If I open it second, it does not.

 

font bug.afpub

[Hangman]

45 minutes ago, anto said:

If I open this document first after start Publisher, it displays correctly. If I open it second, it does not.

There is something odd going on... When you select the Artistic Text tool and drag it out to start creating text it displays a Serif rather than a Sans Serif font, i.e., it's not displaying Arial Regular despite it showing Arial Regular when you start typing up until the point you type a space...

[Sean P]

Hi Anto,

I've finally run into this issue, and although I'm not able to reproduce it in the same way you were, I believe I've found a reliable way of reproducing it. It is now logged with development.  

1. Start either Designer or Photo from a clean start
2. Create a new document (I used Print - Letter Portrait preset)
   • I don’t think the document matters especially, but creating a document at this step does - without it I wasn’t reproducing the issue.
3. File > Open and select the attached Blur - Copy.afphoto file
4. Switch to the Slices Persona
   • ❌Observe that nearly all the text is missing
5. Switch persona and add some artistic text
6. Attempt to type using Arial
   • ❌Observe it will come out in Greek

Note:

If you create a slice in the document in Step 2 prior to opening the document in Step 3, it changes which characters are displayed incorrectly.

 

Blur - Copy.afphoto

[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.

[anto]

@Sean P 

I've noticed another bug that's still being reproduced in Photos.
Sometimes when I select an artistic text and start drawing, the bounding box does not appear. In this case, the spaces between words are not set.

 

 

[Komatös]

11 minutes ago, anto said:

noticed another bug

This should be discussed in a separate thread.

[MikeTO]

Agree that this should be a separate thread but there's something else curious about Anto's screen recording. When you draw an art text object on macOS, it doesn't show the bounding box as you drag but a capital A to help you judge the size of the text - it changes to a bounding box only when you release the mouse button. Does the Windows version not work this way?

[Sean P]

7 minutes ago, MikeTO said:

Agree that this should be a separate thread but there's something else curious about Anto's screen recording. When you draw an art text object on macOS, it doesn't show the bounding box as you drag but a capital A to help you judge the size of the text - it changes to a bounding box only when you release the mouse button. Does the Windows version not work this way?

I believe this is likely the same problem manifested in a different way. The app is using Arial to show the A, but due to the bug, its unable to render A (in the same way the ruler isn't rendering numbers) so you don't actually see it.

[Sean P]

If you change font first and then drag out the Artistic Text frame does it display the preview 'A' correctly?

[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.