I cannot put text on the front of the image.

[mico]

Sorry, I am having trouble putting text on top of an image. Please help me, when I open a jpeg image in affinity publisher or affinity photo and place a text frame over it, I can't type (can't see anything).
The text size (pt) is not selectable.
When I look at the history, the text I type is reflected, so it is not a keyboard issue.
What should I do?
(I used translation software).

[Catshill]

Check that the outline colour of the text is not transparent or non contrasting.

Temporarily hide the image layer to ensure the text is visible and doesn’t have an attribute set, like leading, that means the text isn’t visible.

[David in Яuislip]

1 hour ago, mico said:

The text size (pt) is not selectable.

When you create a text frame you should see something like the screenshot below
If you don't see that then check that Show Context Toolbar is ticked
If that doesn't help please post a screenshot showing what you see

 

[mico]

Catshill-san, thank you very much.
I believe the text color is set correctly.
What is leading?

David in Яuislip-san, thank you very much.
That pull-down menu always shows only "pt" without reflecting my choice of number.

[firstdefence]

Can you upload the afpub file?

[mico]

Sorry, I can't upload the file.
I can't reproduce the phenomenon with other images.
I can't upload the images that cause the problem here because they are used for work.
The image in question is in jpg format, but there are images in the same jpg format that work fine. The difference is not clear to me...

[mico]

I take back my previous statement.

I was able to reproduce the phenomenon.
It seems that only still images captured from videos using the windows preset photo apps will have this symptom.

I am attaching the project file.

report230607.afpub

[firstdefence]

Ok, I could not get your text frame to work so I created an new version and added a text frame and mine works, try it in your Affinity Publisher...

Report - Test document.afpub

[firstdefence]

The only other option would be to go to Affinity Publisher > Preferences > Miscellaneous: Reset Text Styles

[walt.farrell]

There is something weird in the OP's .afpub file.

If I open on my iPad, and select the Text Frame, I can set the font size, but it doesn't seem to take effect. Additionally, if I switch to the Node Tool, it shows the Width as "nanpt".

[GarryP]

When I open the OP’s document in Publisher 2.1 on Windows, after selecting the frame text layer, the font size is ‘stuck’ at “ pt” (with a leading space) and cannot be changed either via the drop-down list or by manually entering a value in the Context Toolbar field.

Using the “Revert Defaults” Toolbar button has no effect.

Resizing the text frame, with either bottom-right handle, has no effect.

Changing the font size value in the Character Panel has no effect.

Going into the Text Styles Panel I noticed that the only Paragraph Style which exists has no name, not even “[No Style]”. This could be a symptom of the problem if the text doesn’t even have “[No Style]” (whatever that means).

However, when I create a new document by dragging an image onto the Publisher window all looks to be as expected.

P.S. It’s possible that the “nanpt”, as reported by Walt, could be a result of converting a “Not A Number” value to a string without checking first.

[joe_l]

My observation: Change the document dpi from 0!!!! to e.g. 300 and use the "Revert defaults" button on the textframe.

[Old Bruce]

2 hours ago, joe_l said:

My observation: Change the document dpi from 0!!!! to e.g. 300 and use the "Revert defaults" button on the textframe.

Yeah, the page being infinite inches wide really messes things up.

[Pšenda]

4 hours ago, GarryP said:

“Not A Number”

NaN is mostly a result of division by zero, which is probably a result of setting DPI to 0.
https://en.wikipedia.org/wiki/NaN

It is interesting that the document has this meaningless value at all - if I enter zero DPI in New Document, the value automatically changes to 1 (which is correct).
So this erroneous value, which Affinity apparently no longer tests and corrects, must have been obtained by the document through some kind of import.

[mico]

Thank you all so much for your help.
Was this caused by the DPI being set to 0? I was not aware of this at all.
So it seems that if I want to use an image like this one, I have to create a new document and then load the image, instead of "open image from program".
I will do so in the future.

[GarryP]

29 minutes ago, mico said:

I have to create a new document and then load the image, instead of "open image from program".

How are you performing the “open image from program” operation, and where are you doing it?
Can you give us the exact steps you use, detailing which application(s) you are using, when you do this?

I’ve tried various ways to ‘open’ an image in Publisher:

• in Explorer, right-clicking the file and choosing “Open With → Affinity Publisher 2” from the context menu;
• dragging the image file from a folder to the Publisher window;
• typing the filename with extension into the ‘Open’ dialog filename field;

...and can’t reproduce the result of getting a zero DPI document.

[mico]

1 hour ago, GarryP said:

in Explorer, right-clicking the file and choosing “Open With → Affinity Publisher 2” from the context menu;

This one.

However, this phenomenon occurs only for images captured from videos using the PHOTO application, which is a standard Windows implementation.

I can send you an image of it so you can try it out.

If you can't reproduce it using this image, it could be a problem with my computer.

[mico]

Sorry, maybe the properties of the image will change once it is uploaded to the internet.
The best way to be sure is to try it yourself by creating a still image from the video (e.g. mp4) using a photo application.

[walt.farrell]

16 minutes ago, mico said:

Sorry, maybe the properties of the image will change once it is uploaded to the internet.

To be sure, you can Zip the image first, then upload the .zip file.

[carl123]

17 minutes ago, mico said:

Sorry, maybe the properties of the image will change once it is uploaded to the internet.

Zip the image and upload the zip file to the forum, then the properties will not change

[Pšenda]

27 minutes ago, mico said:

Sorry, maybe the properties of the image will change once it is uploaded to the internet.

It's alright.
Save image and Open image with APhoto:

 

P.S. This is a "bug" in Affinity - image processing with such erroneous/incorrect data must be properly treated.

Edited June 8, 2023 by Pšenda

[walt.farrell]

12 minutes ago, Pšenda said:

P.S. This is a "bug" in Affinity - image processing with such erroneous/incorrect data must be properly treated.

In this case, would you want the application to invent something (which will probably be incorrect) or simply reject the file as containing incorrect information?

[Callum]

Hi All stellar detective work as always.

Whilst I'm not entirely sure if this is a bug or something we can actually fix I'm going to log this with our dev team to see if it can be improved in some way.

Thanks
C

[Pšenda]

15 minutes ago, walt.farrell said:

In this case, would you want the application to invent something (which will probably be incorrect) or simply reject the file as containing incorrect information?

??? Why do you think the application comes up with a wrong (probably incorrect) value when entering DPI=0?

22 hours ago, Pšenda said:

It is interesting that the document has this meaningless value at all - if I enter zero DPI in New Document, the value automatically changes to 1 (which is correct).

Simply 0 is nonsense, and the application must not work with it - the calculator also does not divide by zero!

Edited June 8, 2023 by Pšenda

[NotMyFault]

22 minutes ago, Pšenda said:

36 minutes ago, walt.farrell said:

In this case, would you want the application to invent something (which will probably be incorrect) or simply reject the file as containing incorrect information?

??? Why do you think the application comes up with a wrong (probably incorrect) value when entering DPI=0?

Walt didn't say that. Instead, he asked a question:  "would you want the application to invent something?"- Probably because the application cannot derive a correct DPI value from the image itself.