Jump to content

Recommended Posts

Posted

In meinen Dokumenten arbeite ich häufig mit Tabellen, in die ich Farbfelder oder Materialbilder einfüge. Seit dem letzten Update von Publisher (2.6.0) funktioniert der PDF-Export von Dokumenten, die solche Tabellen enthalten, nicht mehr. Andere Exporte funktionieren.

Da der Absturz sehr schnell geht, kann ich keinen Screenshot machen.

MacOS Sonoma (Update auf Sequoia ist nicht möglich, da sonst mein CAD-Programm nicht mehr kompatibel ist).

MacBook Pro 16" Nov. 2023, M3 Max, 48 MB RAM

Posted

Hi @Annemary and welcome to the forums. There is a known bug with exporting to PDF files with specific languages. You might find that creating a blank text frame on the first page and setting it's spelling language to None will solve the problem.

If not, you could consider installing the 2.6.2 beta version in which this and another export bug have been fixed to see if that will work for you.

Good luck

Posted

Hallo @Annemary und noch einmal herzlich willkommen im Forum.

Könnten Sie die im Bereich „Sprache“ des Zeichenfensters für Ihre Publisher-Datei angezeigte Rechtschreibsprache bestätigen?

Es könnte sich um einen anderen bekannten Fehler in Version 2.6.0 handeln, der sich auf in Tabellen verschachtelte Objekte beim PDF-Export mit aktivierter Option „Tagged PDF“ bezieht. Dieser Fehler wurde ebenfalls in der Beta-Version 2.6.2 behoben.

„Tagged PDF“ wird beim Exportieren mit den Voreinstellungen „PDF (digital – hohe Qualität), „PDF (digital – kleine Größe)“ oder „PDF (für den Export)“ automatisch aktiviert.

Wenn in Ihren PDF-Exporteinstellungen „Tagged PDF“ aktiviert ist, wird Ihre Datei exportiert, wenn diese Option im Bereich „Erweitert“ der PDF-Exporteinstellungen deaktiviert ist?

_________________________________________

Can you confirm the spelling language shown in the language section of the Character panel for your Publisher file?

This may be a different known bug in the 2.6.0 release relating to objects nested inside Tables when exporting to PDF with Tagged PDF enabled, which has also been fixed in the 2.6.2 Beta Release...

Tagged PDF is set automatically when exporting using the PDF (digital - high quality), PDF (digital - small size) or PDF (for export) presets.

If your PDF Export settings have Tagged PDF enabled, does your file export when this option is unchecked in the Advanced section of the PDF Export settings?

If either Mike's suggestion or unchecking Tagged PDF still causes the file to crash, could you upload a sample document so we can see what specifically is causing the issue?

Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0
Affinity Designer 2.6.2 (3213) Beta | Affinity Photo 2.6.2 (3213) Beta | Affinity Publisher 2.6.2 (3213) Beta

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted
12 hours ago, MikeTO said:

Hi @Annemary and welcome to the forums. There is a known bug with exporting to PDF files with specific languages. You might find that creating a blank text frame on the first page and setting it's spelling language to None will solve the problem.

If not, you could consider installing the 2.6.2 beta version in which this and another export bug have been fixed to see if that will work for you.

Good luck

I tried this and it worked for Export PDF digital hihg quality, but not for small size, I also unchecked the Tagged PDF, but sometimes the crash is too quick, so it is not so clear, which one solved the problem. Thanks anyway!

Posted

Hi @Annemary,

If you can confirm the spelling language shown in the language section of the Character panel for your Publisher file before setting the language to None that would help us figure out which bug this is...

Or if you can upload a sample document where you see the crash we can take a look as it may be neither of these two bugs but something else completely...

Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0
Affinity Designer 2.6.2 (3213) Beta | Affinity Photo 2.6.2 (3213) Beta | Affinity Publisher 2.6.2 (3213) Beta

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

Hallo @Annemary,

Vielen Dank für die Datei...

Der Absturz wird durch den leeren Bilderrahmen verursacht, der in der Tabelle auf Seite 12 fixiert ist. Wenn Sie dem Bilderrahmen ein Bild hinzufügen oder den leeren Bilderrahmen lösen, sodass er nicht mehr in der Tabelle verschachtelt ist, sollte die Datei sowohl als PDF (digital – hohe Qualität) als auch als PDF (digital – kleine Größe) exportiert werden. Sollte dies nicht der Fall sein, teilen Sie uns dies bitte mit.

__________________________

Many thanks for the file...

The crash is caused by the empty Picture Frame pinned in the Table on Page 12. If you either add an image to the Picture Frame or unpin the empty Picture Frame so it's no longer nested in the Table you should find the file exports as both PDF (digital - high quality) and PDF (digital - small size) but let us know if that is not the case...

Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0
Affinity Designer 2.6.2 (3213) Beta | Affinity Photo 2.6.2 (3213) Beta | Affinity Publisher 2.6.2 (3213) Beta

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

Das ist überhaupt kein Problem. Hoffentlich wird dieser Fehler in einer zukünftigen Version behoben.

Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0
Affinity Designer 2.6.2 (3213) Beta | Affinity Photo 2.6.2 (3213) Beta | Affinity Publisher 2.6.2 (3213) Beta

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

  • 1 month later...
  • Staff
Posted

The issue "An Empty Picture Frame Pinned Inside a Table Crashes Publisher when Exporting as a Tagged PDF File" (REF: AF-6319) has been fixed by the developers in the latest beta build (2.6.3.3273). 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.

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.