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
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • 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 13 results

  1. 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!
  2. As you can see from the image the preflight missing font is not showing in the font manager. Be great if it can be added to your fix list thanks Mike
  3. 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
  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. 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.
  6. I have the following problems with the upgrade of 1.8.1 which I did directly from the same Publisher programmme. 1. Prepapring a PDF for printing with 1.8.1 ends up weighing not twice but three times more! I had to make a correction on a document I made last year that weighed only 274 MB. I made a correction on the text, and now the same document, following the same settings I used before when exporting as a PDF file for prining, weighs 1,23 GB!!! 2. Problems importing PDF files into your document. This problem I've had since the very beginning with every Affinity programme. I produce a monthly magazine and most of the adverts are sent as PDF files. Every single programme in Affinty (Designer, Photo and Publisher) completely deconstructs PDF files and sorts them out as layers, and if you don't have the exact same font as the one in the pdf, it will replace it for another. The only way I could work this out, is by converting the PDF files into images—using Photoshop! 3. I don't know if pre-flight was available before, as I never noticed it—but with version 1.8.1 it's mandatory! It opens all the time, and according to your pre-flight everything you have done is wrong (all buttons are orange or yellow)! The problem is that all the mistakes it detects are proper names, the names of cities, foreign words or any word that doesn't have a meaning in the English language (which is the one I use). So a name like MacHale, the spelling checker will ask you to change it into 'manhole' or some such absurdity. Is there a way to avoid having the spelling checker check spelling to proper names, cities and/or foreign words? Again, with version 1.8.1 the pre-flight signaled with a red button something wrong with an image, but no explanation. It happened to be a PDF image as mentioned in the above point. So I had to convert the PDF into an image, and then place it back in the document. The pre-flight red button then disappeared. Oddly enough, this same PDF image had been used last year and sent to the printer with no problem. Now PDF images pose a problem with version 1.8.1. 4. This isn't a bug, but rather a question. I have to send a document to the printer by the end of the month, and can't wait another 6 months until these bugs are fixed, so is there anyway of downgrading to a previous version? Do I have to first bin the 1.8.1 version an then re-install an older version? I haven't checked Photo or Designer upgrades yet, but for the time being these are the bugs/problems I have with Publisher 1.8.1. Please I need a reply asap, as I have to send a document to the printer by the end of the month! Best wishes!
  7. This has happened early in the 1.8 beta and had already been fixed. Now, again, the preflight panel is missing. Serious question to Affinity staff: Does anybody of you use separated mode at all? (It always seems like you don't care that much...) Anyways, thank you for this otherwise awesome new release!
  8. I love how Affinity Publisher turned out. Can we except something similar to the Preflight panel in InDesign? Thanks for the hard work!
  9. 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.
  10. 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.
  11. 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
  12. 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.
  13. 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.
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.