Jump to content

Search the Community

Showing results for tags 'preflight'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support Forums
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Feedback
    • Bugs in Affinity Designer & Affinity Photo
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Affinity Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  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. I love how Affinity Publisher turned out. Can we except something similar to the Preflight panel in InDesign? Thanks for the hard work!
  3. I know that similar subjects were posted on this forum before in different places, but now when time to public beta of Publisher is near, I think it's good to remind this. To unleash the whole power of Affinity Range, we need proper pro printing tools, like good preflight, good colour management, ink coverage measurement... Simply, all what is industry standard for this kind of work. I think that all these tools should be quite similiar (at least at some major points) to Adobe products. (For now, people designing for example in AD, must also use Adobe Acrobat Pro, pdfToolbox or other software if they want to print something at pro standard - and to avoid money loss because of wrong printing results) And a quick question, because I saw in some general topics, that such tools, maybe will be introduced in Publisher, and then maybe will be transferred in future to AD and maybe Photo too. But I wanted to create recent, separate topic for this, because this is quite important. So.... maybe my feature request is now ready in some shape (in APub?) or at least You can say something more about this? I have seen video sneak previews for AD 1.7 and all features are awesome and I'm waiting for an update. Also I have of course seen APub short video preview but...it was short and there was nothing about printing features, but I think that this is very important for many of us here. To be honest, already I'm waiting with some shopping and other business decisions to see what you guys have prepared for us and I think that I'm not alone And after AD and APhoto I believe in you guys.
  4. Hello, Sry, i agree i'm a bit LAZY and not go thru thoroughly through the ocean of the forum, but still searching in a zippy i didn't found my answers, hence writing this ticket. 1. if Team-A wanna fix some error in their Adobe creation by forwarding the project to Team-B with all legal acceptance (via their Affinity product), do team-B need to start over from "Zero" as no support for Adobe's working file extensions? 2. Any Error Fixing/Analysing tools to compete with Adobe's PREFLIGHT, COMPARE(Check out 4th compare tool of Power Styles from Blatner for eg.), Etc. 3. Any Support for third party XML(obviously with DTD), Python, XSLT, Java Scripts. i know i shd. not ask for the product still not in market(ie.. Publisher), but 1st the feature is helpful in all 3-in-1 Package UNITs, & 2nd.ly it really matters. Sry. for the casual english. Thank You, Anant Singh(anant.anant@gmail.com) End Note : Watching Tutorials, but Subtitles as well as an e-book as ref. Requested.
×