Jump to content

Recommended Posts

Posted (edited)

Hi,

Problem.. Designer lost letter (w, j, t ect standard letter). I have changed all option, and the problem is again...

What do i wrong?

image.jpeg.84242e205ae2e2252ea4bb55ffcb7d83.jpeg

Edited by serpe
  • 2 weeks later...
Posted

The box is probably the font .notdef character.
This means the character code embedded in the PDF is not defined in the font.

Can you attach the source PDF?
Then we can see what is actually in there.

 

Posted

I opened the PDF in ADesigner2 and APub2.
The text looks fine. No .notdef boxes.

Exported to PNG from APub2 - looks fine.
Exported to PDF from ADes2 - looks fine.

Examined the text in the PDF you supplied (the codes behind it) - looks fine.

It probably would have been helpful if you had attached the same PDF page as in your image above.
Then we would have a direct comparison.

So, I do not see any issue.

EDIT: Are you on a Mac or Windows? I am on Win10.
The font used is Calibri - Regular and Bold.

Posted

The document was created with Calibri Regular and Bold. Most of it is the Bold.
Affinity applications are to stupid to know Calibri,Bold = Calibri-Bold so it comes up as a missing font.
I selected Calibri Bold as the replacement for Calibri,Bold.
In your video for some reason you selected Arial Narrow Bold first, and then Arial Bold.
Try it with Calibri Bold.

But it does appear you have a font issue on your system.
I tested with Arial Narrow Bold and Arial Bold - and they also worked fine for me.
So this leads me to believe you may have a font cache corruption.
- Shut down the Affinity applications
- Clear your Windows font cache
- Restart Windows
- Restart ADes2, open the PDF, and see if it works now.

If it still does not work, you may have other font issues such as duplicate font files in the fonts folders. Try the above first, if that does not work we can go from there.

Here is a screenshot of your PDF opened in ADes2, with Calibri Bold replacement.

Calibri-Bold.png.62ee16ed577b2d9c736110e6d2aa4664.png

Looks fine to me.

 

Posted

Looked at the PDF again.
In item 7 on the left, there are errors in how the "y" characters are embedded.
If I copy that text and paste it here: Ucwt relingowe  (Note: no h, no y's)
The first y actually has the code for a space character behind it.
The second y has nothing there at all (it is not text, it is just a shape).
Same with the h - it has the code for the space character.
The h has the right CID, but the Unicode character code is wrong.

So this looks like part of the problem is in the PDF.
Affinity applications look for the Unicode character codes.
And some of those codes are wrong in the PDF.

And part of the problem is Affinity applications not understanding the CID codes,
in the PDFs, in old fonts, etc.
If all of the CID codes were correct it may be possible to read it that way.
But in this case the CID codes and the Unicode character codes are in conflict.
No way for this to work without some manual editing.

PDF viewers are just displaying the shapes that are there.
So even badly constructed PDFs can still "look" OK.
But as soon as you try to edit them the proper codes matter.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.