Jump to content

PDF Export with arial bold doesn´t work


Recommended Posts

Welcome to the Serif Affinity forums.

Your .afphoto file works fine for me. What release of Windows, and what release of Photo?

What Export settings did you use?

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Link to comment
Share on other sites

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

My posts focus on technical aspects and leave out most of social grease like „maybe“, „in my opinion“, „I might be wrong“ etc. just add copy/paste all these softeners from this signature to make reading more comfortable for you. Otherwise I’m a fine person which respects you and everyone and wants to be respected.

 

Link to comment
Share on other sites

1 hour ago, walt.farrell said:

Welcome to the Serif Affinity forums.

Your .afphoto file works fine for me. What release of Windows, and what release of Photo?

What Export settings did you use?

I´ve windows 10 with the lastest release of Affinity 1.10.35514.
Export setting see attachment:
 

If you export my .afphoto to pdf does it work? Could you upload your pdf?

Thanks

Marcus

export.jpg

Link to comment
Share on other sites

1 hour ago, MWehrstein said:

I´ve windows 10 with the lastest release of Affinity 1.10.35514.

First, try the latest "lastest release" of APhoto - v1.10.4.1198
So install that and restart Windows.

It also works fine for me. The PDF output is correct.

Text like that usually points to a font cache corruption.
So restarting Windows may help.
If not, then clear the Windows font cache, and restart again.

If that does not fix it, then you probably have some bad fonts installed which are corrupting the font cache.

Link to comment
Share on other sites

1 hour ago, LibreTraining said:

First, try the latest "lastest release" of APhoto - v1.10.4.1198
So install that and restart Windows.

It also works fine for me. The PDF output is correct.

Text like that usually points to a font cache corruption.
So restarting Windows may help.
If not, then clear the Windows font cache, and restart again.

If that does not fix it, then you probably have some bad fonts installed which are corrupting the font cache.

Thanks. I did all the points. But no success.
With an other programm the export of arial bold in pdf is working.
The point is, it is only bold. Regular,... is working.

Link to comment
Share on other sites

1 minute ago, MWehrstein said:

Thanks. I did all the points. But no success.
With an other programm the export of arial bold in pdf is working.
The point is, it is only bold. Regular,... is working.

When you say "other programm" do you mean other Affinity apps?
In what app does it work properly?

Since it does work in some apps, that indicates there is not an issue with the font file itself being corrupted.

Have you installed any fonts recently?
Some fonts may cause font cache issues which appear in unexpected ways.

 

Link to comment
Share on other sites

2 hours ago, MWehrstein said:

If you export my .afphoto to pdf does it work? Could you upload your pdf?

Yes, it works when exporting your .afphoto file.

test.pdf

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Link to comment
Share on other sites

Please try this file: test-2.afphoto

I just rearranged the order of the fonts required, and added Bold Italic.

Here is the PDF output: test-2.pdf

Some MS fonts have an odd way of creating the fonts' PostScript Name.
And I think it may sometimes confuse Affinity apps.

You could also try using the Arial Nova family instead.
It is available in the Pan-European Supplemental Fonts package.
Free to download and to use.

Link to comment
Share on other sites

On 12/18/2021 at 8:41 PM, LibreTraining said:

Please try this file: test-2.afphoto

I just rearranged the order of the fonts required, and added Bold Italic.

Here is the PDF output: test-2.pdf

Some MS fonts have an odd way of creating the fonts' PostScript Name.
And I think it may sometimes confuse Affinity apps.

You could also try using the Arial Nova family instead.
It is available in the Pan-European Supplemental Fonts package.
Free to download and to use.

Thank you for the hint. But the same effect. See attachment.
But because it´s running on your system (you also have a windows system?), it seems not to be a Affinty bug.
Some is wrong on my system. Usings Microsoft Publisher or Photoline on my compute, it´s running well with pdf export of arial bold.
But why not with Affinity?

test-2.pdf

Link to comment
Share on other sites

1 hour ago, MWehrstein said:

But why not with Affinity?

Perhaps it is because you are using a Type 1 font for Arial Bold! Replace that with a TrueType equivalent and you should be fine.

type1.jpg

------
Windows 10 | i5-8500 CPU | Intel UHD 630 Graphics | 32 GB RAM | Latest Retail and Beta versions of complete Affinity range installed

Link to comment
Share on other sites

4 hours ago, Joachim_L said:

Perhaps it is because you are using a Type 1 font for Arial Bold! Replace that with a TrueType equivalent and you should be fine.

Good catch.

@MWehrstein Un-install the Type 1 versions as that is confusing the Affinity font cache (the fonts have the same PostScript Names as in the TTF files).
Restart Affinity Photo after you have deleted the Type 1 fonts and it should rebuild its font cache - and it should work.

Arial Type 1 fonts ... that's a new one to me.

Link to comment
Share on other sites

4 minutes ago, MWehrstein said:

I deleted some other installed Arial fonts like Arial MT and Arial Nova.

Arial Nova is OK - the names do not conflict with regular Arial. So you can keep that.

Just the regular Arial TTF and Type1 have a conflict because the PostScript Name is the same inside the fonts. And the PostScript name is used when embedding the fonts in the PDF. So the duplicate names confused the Affinity app.

Link to comment
Share on other sites

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.