Jump to content
lghthd7

Does Affinity offer export to pdf/x-1a:2001?

Recommended Posts

7 minutes ago, Dave Harris said:

However, we do support PDF/X-1a:2003. You may find your printer will accept that too.

Their automatic checks may well reject the file out of hand. Many/most do.

2003 never really caught on in the industry. 

Share this post


Link to post
Share on other sites

Are you thinking of adding this soon as IngramSpark is pretty standard for producing indie hardbound books, they have registered over 7 million books and are rather well known.

It's like saying you won't be supporting Barnes & Nobles, it's pretty big. I haven't seen too many other hardbound book publishers that give me the options they do at their price.

Considering you have the other formats how hard would it be to add pdf/x-1a:2001?

 

 

Edited by softsound
Minor additional text added

Share this post


Link to post
Share on other sites

Yeah, I would go either pdf/x-1a:2001 or pdf/x-4

pdf/x-1a:2001 is the most widely used PDF/X.
Would be nice if I cloud export this.

pdf/x-4 would be the successor but not being widely used yet.
But it's useful to send a file to Adobe users

Share this post


Link to post
Share on other sites

Actually it appears that pdf/x-1a:2003 works fine for IngramSpark checks!

Don't use pdf/X-3:2003 just use pdf/x-1a:2003 and it clears the checks. I looked a little further into the file type and it appears it that covers PDF/X‑1a (2001 and 2003).

Since I illustrate children's books I also have to set the color profile to CMYK as well as a heads up to anyone else looking at this problem.

Share this post


Link to post
Share on other sites
13 hours ago, softsound said:

Actually it appears that pdf/x-1a:2003 works fine for IngramSpark checks!

My experience has been similar, as both are pretty old standards. Automated checks may fail for trivial reasons, and if the upload is discarded, there is normally a way to hand over the job by other means. The standards were created to facilitate print pdf ceation, delivery and processing, and not to create obstacles where preflight tools or expensive third party libraries are needed to check that everything is "go".

PDF/X-1a:2001 is PDF 1.3 based and PDF/X-1a:2003 also supports PDF 1.4 (which is the default for creating any non PDF/X-based press PDFs from within InDesign). PDF 1.3 is "idiot-proof" but very rare printers actually require PDF 1.3. I do not think that Affinity apps even support exporting to PDF using other than 1.4+ based versions, so if the printer really requires PDF/X-1a:2001, I guess there is no other option than picking up a printer that is more flexible.

UPDATE: The major difference between PDF 1.3 and 1.4 is that the latter supports transparency. However, Affinity's PDF/X-1a:2003 does flatten all transparencies so it is "technically" PDF/X-1a:2001 compliant, so if it does not pass a check, the reason is (probably) trivial and the file itself should work without problems. 

UPDATE2: For anyone interested, the PDF Preflight tool that comes with Adobe Acrobat Pro X, does not make a distinction between PDF/X-1a:2001 and PDF/X-1a:2003. I tested a couple of simple Affinity Publisher exported print PDFs created by using the default (unmodified) internal PDF/X-1a:2003 settings, containing overlapping transparent texts and graphic objects (both having a transparency setting) -- which at the export get flattened -- , and the files passed the PDF/X-1a compliance verifying routines of this Preflight app without any warnings. As Affinity routine also seems to flatten the flattens the transparencies, this export routine could be considered pretty failsafe. But it is naturally recommended to create the PDFs according to the specs instructed by the printer, if the requested method is available in Publisher.

Share this post


Link to post
Share on other sites
8 hours ago, Lagarto said:

As Affinity routine also seems to flatten the transparencies

Not sure if I know what you mean... I have exported PDF/X-4 files with transparency (logos, etc) from A. Designer. Ofc, checking the pref on Acrobat Reader (or the like ) on, as that one does not have it default.

Share this post


Link to post
Share on other sites
41 minutes ago, SrPx said:

Oh... I had the idea that anyway transparency is never carried in a PDF/X-1a , no matter what software.  Oki

Yes, that seems to be so. At least InDesign flattens transparencies when exporting using PDF/X-1a, whether using the 2001 or 2003 version. But version 2003 is based on PDF 1.4 and this version itself supports transparency. I think that PDF/X-1a requires flattening of transparencies no matter which sub version. That would explain why Adobe Acrobat Preflight does not make any distinction between the 2001 and 2003 sub versions. 

Share this post


Link to post
Share on other sites

Yep, when I need transparency in a design, In A. Designer I set the document "background" as transparent in "document properties" and export as PDF/X-4 (I believe PDF/X-3 does not support transparency, either, but am not sure, as I never really use that one). It seems most modern RIPs  do support greatly PDF/X-4 and surely is more bullet proof. My usual workflow in the arcane times needed to be ALWAYS be very sure to check in the specs in the print company (well, I still check every bit, color profiles, bleed, margins, if they provide with templates, etc) which color profile do they use. As far as I know, PDF/X-1a enforces CMYK (btw, a certain a number of Chinese print companies have required from me recently CMYK files yes or yes, while many PODs require sRGB, others CMYK, others Adobe RGB...u know, it's a varied world), and you need to work (specially when exporting as PDF/X-1a) with the profile that the print company uses or do a final conversion to that profile . When digital painting, is much better to do so, and having worked all the time in RGB, and doing a final conversion. For simple vector files, logos, etc, I personally start with the requested color profile, if I've been very assured A or B print company is going to be used. But lately, I try to work everything (raster or vector) in RGB (Adobe or sRGB) and adapt to the needed output at the end. Kind of less destructive and more flexible ( I have the screen calibrated by hardware, and is a pro-ish monitor...).

I'm trying to make the output be always PDF/X-4, since a while, with every project. It also opens quite well in some apps that some eventual (I mostly work alone, lone wolf, hehe) colleagues use, and who have issues opening certain other formats. Even while using PDFs for that I/O is less than desirable.

I'm not super expert in PDF/X and its specs, I've only learnt (like in many matters) what I needed to work....

 

Edit : It took me a while to realize that Acrobat reader does have that 'view with transparency' preference setting (by default off). It's handy for a client to check that a PDF is really transparent (otherwise they'll always see a white background). They rarely have any design tool at all, let alone know-how to handle it. If you send the pdf, they keep opening it with Acrobat or whatever, and keep asking you to send a transparent background one.  In some cases the most practical solution is to send them a transparent PNG (ONLY for their own home printer and doing screen based mockups, not for sending that to the print shop), as they handle that format with less troubles, for some reason, most likely that the basic image apps they use don't support transparent PDFs. 

Share this post


Link to post
Share on other sites
3 minutes ago, SrPx said:

I try to work everything (raster or vector) in RGB (Adobe or sRGB) and adapt to the needed output at the end. Kind of less destructive and more flexible ( I have the screen calibrated by hardware, and is a pro-ish monitor...).

Likewise. The processes have become more and more flexible, much because of the need to produce from the same material for diverse purposes. Many printers prefer PDF/X-4 nowadays and as color management has become pretty standard across all apps used for production, and printing processes are based on ISO standards, you pretty much always get what you expect. When coming from Adobe environment, there has seldom been need to get wise with color profiles, because things have "just worked", and because printers often give detailed instructions when producing with InDesign. Though it is certainly possible to mess things up in Adobe environment, as well. But all in all, working with color has become pretty straight forward and predictable at least when working with displays with measured luminance and wide gamut governed by device profiles -- disregarding the platform. 

Share this post


Link to post
Share on other sites
2 hours ago, ashf said:

I just noticed that DrawPlus does export PDF/X-1a:2001 using PDFlib which Affinity use.
Why Affinity does not support PDF/X-1a:2001?

PagePlus supports embedded fonts in PDFs, Affinity Publisher doesn't.

I'm not sure that the fact that old Serif "legacy" products did something is particularly relevant to what the new Affinity apps do!

Share this post


Link to post
Share on other sites
On 12/31/2019 at 6:55 AM, ashf said:

I just noticed that DrawPlus does export PDF/X-1a:2001 using PDFlib which Affinity use.
Why Affinity does not support PDF/X-1a:2001?

PDFLib used to support it, but decided to stop doing so in recent versions. I've not been able to convince them that it is needed.

Share this post


Link to post
Share on other sites
53 minutes ago, Dave Harris said:

PDFLib used to support it, but decided to stop doing so in recent versions. I've not been able to convince them that it is needed.

That's sad.
As you see many major printers still require 2001. they are living in the past.
And they may keep using 2001 till the end of the world.
 

Share this post


Link to post
Share on other sites

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.


×
×
  • 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.