Jump to content

An error occurred while exporting to pdf - Affinity Publisher 1.10.4.1198


Recommended Posts

Hi. I am working on a project using Affinity Publisher.

I tried to export my document(.afpub) file to PDF, but I keep getting the following error message:

 

An error occurred while exporting to: [path]

 

Please help.

Edited by sssms
Link to comment
Share on other sites

Welcome to the Serif Affinity forums.

You might enable PDFLib Logging, and see if the log file reveals any details of the problem:

 

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

It does seem to be something about the Cafe24Ohsquare font. I'm suspicious of the 2nd line that I show below, for two reasons:

  1. There's a space in the middle of the font name, when compared with the 1st line.
  2. Just guessing, but the ",700" may indicate the use of a Variable font, which are not supported by Affinity.
PDF_load_font(p_0x000001C4FCCD1220, "Cafe24Ohsquare", /*c*/0, "glyphid", "readkerning=false readfeatures=false readselectors=false readshaping=false errorpolicy=return embedding=true subsetlimit=90% subsetminsize=50")
[-1]
PDF_load_font(p_0x000001C4FCCD1220, "Cafe24 Ohsquare,700", /*c*/0, "glyphid", "readkerning=false readfeatures=false readselectors=false readshaping=false errorpolicy=return embedding=true subsetlimit=90% subsetminsize=50")
[-1]
PDF_set_option(p_0x000001C4FCCD1220, "FontOutline={{Cafe24Ohsquare}={C:\\USERS\\POSEIDON\\APPDATA\\ROAMING\\PROGRAM\\COMMON\\DATA\\{5BF53A77-2F75-9219-61A6-D5D68DB1B509}\\{324B9AD7-86A4-CC7A-5437-E682222E9F79}\\5485F2C6EA3A55EA409BE8DF20DFA28B}}")
[Last exception 1472 in PDF_set_option]["Option 'FontOutline': Opening brace '{' is missing within the value '{{Cafe24Ohsquare}={C:\USERS\POSEIDON\APPDATA\ROAMING\PROGRAM\COMMON\DATA\{5BF53A77-2F75-9219-61A6-D5D68DB1B509}\{324B9AD7-86A4-CC7A-5437-E682222E9F79}\5485F2C6EA3A55EA409BE8DF20DFA28B}'"]

 

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

@walt.farrell

Thanks for your reply.

 

I've changed all the fonts in my file but still having issues exporting to PDF.

Attached is the log file. Can you check this file again?

errorlog.txt

 

I think this part below would be the error but I have no idea about the "FontOutline" thing.

 

PDF_set_option(p_0x0000020753C93C20, "FontOutline={{SDNemony2gObliqueLt}={C:\\USERS\\POSEIDON\\APPDATA\\ROAMING\\PROGRAM\\COMMON\\DATA\\{5BF53A77-2F75-9219-61A6-D5D68DB1B509}\\{324B9AD7-86A4-CC7A-5437-E682222E9F79}\\3E09975C95627BBD53007124F250D86D}}")
[Last exception 1472 in PDF_set_option]["Option 'FontOutline': Opening brace '{' is missing within the value '{{SDNemony2gObliqueLt}={C:\USERS\POSEIDON\APPDATA\ROAMING\PROGRAM\COMMON\DATA\{5BF53A77-2F75-9219-61A6-D5D68DB1B509}\{324B9AD7-86A4-CC7A-5437-E682222E9F79}\3E09975C95627BBD53007124F250D86D}'"]

 

 

Edited by sssms
Link to comment
Share on other sites

I've never seen font names like the ones you're using. Where did you get them, and how did you install them?

Does it work if you use more "normal" (for want of a better word) fonts, such as Arial?

Also, what is the install path you used for Publisher? I'm a bit suspicious about that "PROGRAM" in the middle of the pathname.

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

@Lagarto@walt.farrell

 

I'm using Cloud font service, not installed software font. and I've installed Affinity publisher in Downloads. 

I think this would be solved if i change all the fonts to Arial which is already installed in my Windows Computer software but I need to use this Cloud Font service due to my project.

Cloud font company assumes this problem would be affinity publisher's internal problem because of the error message Opening brace '{' is missing within the value.

Does affinity publisher do something with the path AppData\Roaming\Program\Common\Data when I'm using Cloud font service with affinity publisher?

Link to comment
Share on other sites

  • 10 months later...

I`m with the same problem  error while exporting to pdf ...

 

The scenario
A simple file, 4 pages only with few images from ~stock palette~ Arial font and nothing special
except the anchors and hyperlinks that I need for this special project

Affinity Team, please take a closer look - in short

with anchors and hyperlinks  = error

without anchors and hyperlinks = normal export.

win10 and affinity publisher 1.10.5.1342

Link to comment
Share on other sites

@Dan C, maybe the PDF export log can be made accessible from a dedicated menu command? To avoid clutter, it can be generated and deleted in the background, and shown only on request. This type of log is unfortunately more often needed that one would hope.

Paolo

 

Link to comment
Share on other sites

On 12/30/2021 at 7:58 PM, walt.farrell said:

Welcome to the Serif Affinity forums.

You might enable PDFLib Logging, and see if the log file reveals any details of the problem:

 

 

On 11/23/2022 at 7:45 PM, Emily Fowl said:

Hiya! I've also encountered this error, which is peculiar, considering the export worked just fine over the weekend on the very same file. I've only added some more text since then. I've run the recommended PDFLibLogging, which I'll try to attach now.

link to the txt file in drive, i failed to attach it directly

 

SAME EXPERIENCE HERE. IT JUST SUDDENLY WON'T EXPORT. USED THE SAME FONT BEFORE AND HAD NO PROBLEMS EXPORTING INTO PDF, BUT NOW I'M SUDDENLY HAVING THIS ERROR. HELP PLEASE

Link to comment
Share on other sites

4 hours ago, Dong said:

SAME PROBLEM HERE!

An error occurred while exporting to:

Which application are you using, and which version?

 

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

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.