Jump to content
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 (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer V2
    • Report a Bug in Affinity Photo V2
    • Report a Bug in Affinity Publisher V2
    • Report a Bug in Affinity Version 1 applications
  • Beta Software Forums
    • macOS Beta Forums
    • Windows Beta Forums
    • iPad Beta Forums
    • [ARCHIVE] Reports from Affinity Version 1 Betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


Skype


Facebook


Twitter


Location


Interests


Member Title

  1. 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.
  2. 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
  3. Would be nice if long preflight comments are collapsed to 2-3 lines by default and expandable with the "read more" button.
  4. 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.
  5. 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?
  6. 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!
  7. 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.
  8. 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!
  9. 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!
  10. 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
  11. 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.
  12. 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.
  13. 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!
  14. 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?
  15. 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
  16. 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.
  17. 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
  18. 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?
  19. 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
  20. A couple days ago I asked about the value of pdfTool in a Quark forum. One comment was unexpected in that they pointed out that the tool is especially good for adding to a Publisher workflow in that it hasn't been around as long and may need a little more help than mature products like Quark and InDesign. That one perspective alone almost justified it's $500+ price tag. I wanted to know have other people found that those two products work really well together? Publisher is the only tool in the suite I haven't explored extremely in depth and I haven't even installed pdfToolbox yet. I like how Serif keeps the price low which allows for workflows like installing it on non-designers computers as I mentioned a couple days ago. Since the work in my company needs to pass by me the more expensive product (pdfToolbox) only needs to be installed on my machine. At first I didn't understand the very low pricing that Serif was doing but now it makes sense. I have even grown to like the name in that it may confuse some Microsoft Publisher users to accidentally start using Serif Publisher.
  21. Prior to exporting my document to PDF, preflight said TOC needed updating. I hit the FIX option and Publisher crashed. I have version 1.8.5.703 on Windows 10.
  22. Hello everyone, I am writing an instruction book for my Taekwondo students. To translate some of the Korean words I have used phonetically spelled English words for example "Kyungnet (sounds like Kunray) means Bow". Unfortunately, there is no universally agreed way to "spell" these translations and consequently I have saved a few different versions of the phonetically spelled English version when I have right clicked and selected Learn Spelling. I would like to ensure that all my "mis-spelled" words are consistently spelled the same way. I guess sci-fi writers have a similar issue with strange names. Can I reset all the "Learn Spelling" en mass so I don't have to go through every word and Unlearn Learn Spelling? Thank you. By the way if you have any tips for strategies to deal with this in the future that would be great. Cheers. James
  23. The Preflight panel shows missing fonts. The 'Fix' option provides the ability to locate the missing font. However there is no facility to make a font substitution permanent, and therefore no longer displayed as an error. Please provide the ability for font substitutions to be accepted as permanent, enabling users to permanently dismiss a preflight issue relating to a particular substituted font.
  24. I love how Affinity Publisher turned out. Can we except something similar to the Preflight panel in InDesign? Thanks for the hard work!
  25. Hi, thanks for the good work on the Affinity products! Having spent some first moments on tuning in with Affinity publisher I'm missing a preflight checker. That's why I have the following feature request: User Stories: As an Affinity Publisher user I would like Affinity Publisher to check whether my document layout and the document content fulfills before-configured criteria in order to not export unwanted documents. I would like Affinity Publisher to provide sane default values/configurations for the below-mentioned checks. I would like Affinity Publisher to enable me to define and administrate (create,read,update,delete) several preflight profiles. Desired checks: The checks that I would like Affinity publisher to perform are: Image resolution: I would like to get notified which image does not match a document's defined resolution to prevent pixelated prints. Image colour space: I would like to get notified if an image potentially contains colours which might get lost when producing a exporting a document, e.g. for CMYK printing. Content-bleed-distance: I would like to get notified which contents are too close to a document's bleed, e.g. a background image that should expand to the "bleeding edge". Outdated links: I would like to get notified which objects displayed in Publisher do not represent the latest version of a referenced file. Missing external resources: I would like to get notified which external resources cannot be located by Affinity Publisher anymore. Text overflows: I would like to get notified which text boxes have an overflow issue. Background: My first project is going to be a simple poster. But I plan to recreate an old InDesign project using Affinity Publisher, a poetry anthology with several pictures etc. I definitely need the software to notify me if I accidentally messed up my layout, e.g. by adjusting a paragraph style etc. I hope you are already on it. Such a preflight check definitely is part of what I would consider a professional desktop publishing program.
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.