Jump to content
You must now use your email address to sign in [click for more info] ×
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

Search the Community

Showing results for tags 'preflight'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Staff and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.5 Beta New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

  1. Dear Affinity Users and Developers We’re just in the process of evaluating Affinity Publisher (tested with 1.7.0.305 and 1.7.0.312) and we’ve come upon a problem with the PDF/X export: In our workflow our print PDF files are checked in Adobe Acrobat against the preflight profile PDFX-ready Sheetfed Offset Classic HQ V1.5. Among other things this profile checks the MD5 checksums of the used ICC profile against a pre-defined list of profiles known to be appropriate for offset printing. When exporting a PDF as PDF/X-1a with the ICC profile ISO Coated v2 300% (ECI) from Affinity Publisher the preflight returns this error: Looking at the preflight report in the section Output Intents I noticed a difference between a PDF exported from InDesign and Affinity Publisher: The Output Intent is stated as ISO Coated v2 300% (ECI) for the InDesign-PDF and as ISO Coated v2 300% (ECI) (Custom) for Affinity Publisher The Color Management Module had a value of HDM (InDesign) and lcms (Affinity Publisher). Primäre Zielplattform (in English probably: Primary Target Platform): empty (InDesign) and Apple Computer, Inc. (APPL) (Affinity Publisher) Profil erstellt mit (in English probably: Profile created with): Heidelberger Druckmaschinen AG (HDM ) (InDesign) and lcms (Affinity Publisher) The other fields were the same in both files. So I suspected this to be the reason for the different MD5 checksums. But not being an expert on the ins and outs of PDFs and colour management I turned to HilfDirSelbst.ch where we discussed this (in German) in this thread. Olaf Drümmer of callas concluded (my translation): So the question is Is Affinity Publisher correct in changing the meta-data of the profile when writing the PDF file? And if so: Would PDFX-ready need to append their list of MD5 checksums to include those of profiles created with lcms? Any insights and suggestions would be greatly appreciated! Best phph
  2. Hi, This is probably a silly question but I'm getting all these 'Missing dictionary for language (en-ES)' warnings in Preflight. They are probably harmless, but my Preflight is flooded with them to the point that I cannot find the few other warnings and errors that are sprinkled among them. How can I make these 'Missing dictionary for language (en-ES)' warnings go away? Thanks!
  3. I'm working on a document in Publisher 2.3.1 that has a good number of unique words in it. There are also a lot of pictures 150 mb worth approx. The total document is 260 pages. As the document got bigger, the spell check would forget the "ignore" on some of the words. I started to ignore the spell checker. Now that the document is put together and I'm editing, periodically it would forget all the ignored words. I just stopped worrying about it. Now, every so often, preflight will mark EVERY image in the document as modified. I have to go through every single one in the resource manager and update them. None of the files are being modified. They images are all in two folders local to the document.
  4. I have a customized Mac with an English MacOS version and a Norwegian keyboard, since I am Norwegian. However, much of the DTP work I do on Affinity Publisher is in English. A big project I'm working on at the moment is entirely written in English. However, when I run the Preflight check I get a mile long list stating: I have followed the instructions here but the problem is that I cannot find any dictionary named (en-NO). And I have switched on every Norwegian and English dictionary in System Preferences in my MacOS and restarted Affinity Publisher, but the error messages persist. Now I just want to exclude that type of error message, because in the first edition of the document I was working on, some important error messages had snuck in between the enormous amounts of "Missing dictionary for language (en-NO)" which I didn't notice. I enclose two screenshots, and as you can see, it is extremely difficult to spot the real important messages in the sea of nonsensical "missing dictionary" messages that reports on every page over and over. Since the missing dictionary message isn't important, and the spell checking of the English text in the document works just fine, I would very much just get rid of the dictionary error messages so they don't inadvertently hide actual important error messages. How do I do that? Is it even possible, or is there a workaround?
  5. When 'Maximum ink' is set to 320%, so it catches incorrectly converted RGB blacks, the preflight panel will flag any object with an 'Outline' layer effect as "Filter Effect ink density too high (327%)". This happens even if the outline effect is well under the 320% mark, as shown in the image below: Furthermore, disabling the outline effect will not stop the object being flagged. See below: You need to press the 'X' to remove the effect, so the object is no longer flagged: Moreover, if you deliberately set the effect to something over 320%, and also different from 327%, you'll get two errors. One for the actual real problem, and another for the imagined 327%. See the attached image: Even moreover, disabling the outline effect will remove neither of the errors, only deletion will work as mentioned above: Finally, this error happens even if the outline effect is applied to an object inside another document, provided the option 'Look inside placed documents' is active: The steps to reproduce are: Enabling the preflight options mentioned: Maximum ink set to 320% Look inside placed documents Create any shape Apply the outline effect Check the error on the preflight panel Thanks!
  6. Hello there, not sure if this is the right place to report this as it's technically not a bug, but the "Never" label in the preflight dialog is not aligned with the other two labels. I have attached a screenshot, as well as a magnified view with a red line to show this non-alignment. I am currently using Affinity Publisher 2.0.3 on Windows 10.
  7. Can someone explain what does this mean? The PDF export version is not known before you actually initiate the Export and select it, yet this error seems to be thrown all the time in Live Preflight, before I actually select anything in Export function
  8. Would be nice if long preflight comments are collapsed to 2-3 lines by default and expandable with the "read more" button.
  9. There is definitely some sort of bug when updating the Table of Contents. Before, it suddenly changed the formatting so that each paragraph started in a new column. (see this thread). Later that same day, an update of the TOC caused all the text to suddenly have additional space between each line, which I managed to control by adding a Leading override (which had previously been set to [no change] without being affected). Now, I went to refresh the TOC and it's suddenly decided to apply Superscript to all of the text. At no point did I edit the format of the TOC, and the TOC styles are in no way connected to any other format that would suddenly change the style. So to fix this new problem, I now have to change the Superscript setting from [No change] to None, even though that's what it had been set to previously and it had not been altered in any way by me. The amount of times I've had to 'fix' my TOC because the update caused odd formatting to be applied is starting to get obnoxious. Any ideas why this keeps happening to my TOC? I'm updating the TOC through the Preflight dialogue using the "Fix" button. I'm on Affinity Publisher 1.10.5 using Mac OS 11.7.
  10. To Serif: Hi, To my surprise when exporting pages to pdf I'm getting preflight warnings with all kinds of spelling issues. Looking where they appear they all appear in the used master page. But these warnings are redundant as all these text fields' content is overwritten in the pages themselves and the master pages only contain dummy text and/or templates, so spelling isn't important on these master pages. So to me this check doesn't make sense while exporting the final pages. It would be better IMO if Affinity would only check and warn about misspellings on actual used text when exporting, not text that is overwritten by the pages. Thanks in advance!
  11. I like working with Publisher. The software is clear and intuitive in many areas. My wish 1): The possibility to take over full tone channels from PSD image files and to be able to assign them to a global colour as desired. My wish 2): A real design mode. Affinity seems to save previews in the project file. Nevertheless, all images are reloaded in the background every time, even if they are only linked. This costs an enormous amount of RAM and slows down the computer during this time. My wish 3) A separation-preview.
  12. for Affinity Publisher Request: For prepress workflows it would be very helpful to switch to a preflight mode where you can quickly check what objects are on which colour plates (eg. spot colours) Problem: Sometimes there are shadow-effects or overlaying colours and multiplying images that change the otherwise clean constructed set of elements in your layout. For example, you know every text has this global colour and every icon has that corporate-design colours, but where things overlap and blend, you need to know "how dark this black really is" to be successfully printed. Solution: Of course Indesign has had this feature long ago, and I'm even only using version CS5 from 2010... But you can also look for Photo's Channel panel: Like Photoshop, you can disable the green and red channels and look how the blue channel looks in isolated mode. in RGB mode this is maybe not as useful but in the prepress-world looking at your isolated CMYK plates is essential!
  13. Hi, I get a "missing character" error in preflight for every word in the document. This is my process: I copy/paste a text into the 3-column spread. I spliced the content with a Column Break. I repeated it with the new text, and it happened again. I have the latest version of the Publisher, and my Mac is up-to-date. AP_Preflight .mp4 AP_Preflight .afpub
  14. To my mind, the preflight function is overzealous. Spelling mistakes shouldn't even create warnings. Spelling check is done by my colleagues who do the copy editing/proof reading. It should be done in a word processor, not in a DTP app. Therefore, I would like to get rid of those annoying warnings for good! How can I do that? I know that I can create my own profile and that I can create even categories. But that means I have to choose this profile/category first. For me, this is one click to many. I want it out of the box, by default. Is this possible? Maybe by somehow (but how?) changing the settings of the Default category? Can I break the habit of always creating warnings in regard to (alleged) spelling mistakes? Thanks!
  15. I'm using Affinity Publisher, Windows build 1.10.4.1198. I'm using XLSX as a data source. It hasn't been changed recently. Preflight panel shows the warning and a Fix button, but it doesn't seem to work. I have no idea if my manipulations caused some kind of disconnect. But here are the things I did to create a template: Initially, I began the whole process in my main document, "Puzzles" I created a page (not Master) and used the Data Merge Layout tool to create a "Sudoku" grid After learning more about Data Merge, I decided I should have a separate .AFPUB template I copy/pasted the page from "Puzzles" to a new document I belatedly realized that I should be using a Master page I copy/pasted from the normal page in my new document to Master A This is key: I was concentrating on the Master page and totally forgot to delete the Data merge Layout from the normal page The source field on the normal page was called "Solution", then I changed it to "Puzzle" before I copied it to Master A Meanwhile, I kept tweaking the Master page and renamed the field from "Puzzle" to "N" to help get rid of an Overflowing text frame error After each tweak, I would save the project as a template. Every time I generated the merged document and tried to export it to PDF, Preflight complained about three errors I finally removed the old Data Merge Layout from the normal page. I resized the text frame in the upper cell to handle the Overflowing text error Maybe all that copying, pasting and renaming confused the software. If not, then perhaps the preflight check is not seeing the XLSX as being unchanged.
  16. Hi all! I've discovered a pretty strange, but not debilitating bug in the Publisher preflight. Basically, when I add afpub files to my layout, preflight says that the "Linked resource is missing" for every afpub placed, even though they are properly linked, and the source afpubs have properly linked images within them (if you look at attached, you can see that each image is on a different page, and are all OK in resource manager). What's stranger? No matter what page the afpub is on, preflight shows that the error is always on page 1 (also see attached). Anyone experience this, or know of a way to fix this? PDFs output correctly and in high resolution, so the preflight error is definitely a false-positive. Is placing an afpub in an afpub not best practice? Would it be better if I added flattened afphoto instead? Thanks so much!
  17. HI How do you preflight your PDF files - if you don't have Adobe subscription anymore. I got pdf export settings from my printer, how can I import that into to publisher. I know I can see if there is anything wrong in the document preflight panel - but is that all I need.
  18. For me it would be very useful, if Affinity Publishers Preflight would be able to find colours, that are not in the used swatches panel. That could prevent the accidental use of Colours, that are not wanted. I don't know, if I can make my point clear – I'm from Germany and my English is a bit clumsy.
  19. Affinity applications (and other) do not have full support for Variable fonts, the export of which then causes problems, see for example Therefore, it would be good if the Preflight report points out this fact - that the user uses font types that can be problematic. Thanks P.S. And maybe a vector/bitmap Color fonts?
  20. Hello, I'm almost ready with the first book I made with Affinity Publisher and I uploaded to lulu.com for a quick test. I keep getting a warning stating: I opened a thread but at the end I realized it will be a nice feature if Preflight could check if there is text with a size under a predefined value in the document. Ideally it would be nice to set the minimum font size somewhere in the preferences, however checking for anything smaller or equal 5 pt should be helpful enough. Thank you
  21. After completing a publication and creating a PDF, the pre-flight panel remained stuck across the screen. I upgraded to 1.9.1 but it's still there, only it's now grey but in the same shape and position as before. It covers up most of the screen, so I can't use Publisher because I can't see anything behind it. Command +W doesn't work.
  22. I observed this on Affinity Publisher 1.9.0.932 on Windows. I have a document with several linked PDFs. When I export this document to PDF there is a preflight warning for every single linked PDF, stating: The warning appears only for PDFs in "Passthrough" mode and is obviously a false alarm. The linked Sub-PDFs are not rasterised in any kind in the exported PDF. This is not a big deal, since the result is as desired, but the warnigs are a bit distracting (especialy if you have many linked PDFs in your document). I attached a simple document Example.afpub which contains a linked Embedded_PDF.pdf. The resulting PDF is stored in Example_exported.pdf. On the screenshot you can see the contradictory messages:. Embedded_PDF.pdf Example.afpub Example_exported.pdf
  23. Either I've found some weird bug, or I'm doing something wrong. My Preflight says that "The document index needs updating." and provides a "Fix" button. However, every time I mash the button, nothing happens other than additional entries showing up in the Index Panel (but not on the page). The error remains, and the Index Panel resets itself back to one entry per after a few moments. (see screenshots attached) If I delete the frame with the entry, the error still remains. I have only 1 index and 1 table of contents inserted in the entire document. Am I missing something here?
  24. When exporting a document to certain formats, typically PDF, there is sometimes an undesirable and for user surprising rasterization of vector objects and texts. For example, when using Blend Mode Multiply, see Therefore, it would be very useful, when the Preflight check allowed a warning, that these objects will be rasterized during export. Thank you
×
×
  • 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.