Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PDF X/3 compliance #640

Open
LukasKlement opened this issue Jun 13, 2018 · 11 comments
Open

PDF X/3 compliance #640

LukasKlement opened this issue Jun 13, 2018 · 11 comments
Labels
feature New feature that should be supported

Comments

@LukasKlement
Copy link

I'd like to achieve PDF X/3 compliance for the PDFs generated with WeasyPrint. Is it possible to set the following details:

  • Set OutputIntent to GTS_PDFX
  • GTSPDFXVersion key
  • Document ID

Also, I get the following error in Acrobat:

  • Trapped key not true or false

The list of requirements were determined by the Acrobat PDF/X compliance tool.

@liZe liZe added the feature New feature that should be supported label Jun 19, 2018
@liZe
Copy link
Member

liZe commented Jun 19, 2018

That's a good idea!

If you know what these properties are (I don't), it's probably easy to add: we use the pdfrw library to modify the generated PDF file, we can add/change these values when editing metadata.

If you don't, we have to read the PDF specification to know how and where to add these values.

@LukasKlement
Copy link
Author

I answer as far as my knowledge goes in that respect:

Output Intent
Needs to be of the subtype GTS_PDFX, here's an example metadata: <</Metadata 2 0 R/OutputIntents[<</DestOutputProfile 5 0 R/Info(U.S. Web Coated \(SWOP\) v2)/OutputConditionIdentifier(CGATS TR 001)/RegistryName(http://www.color.org)/S/GTS_PDFX/Type/OutputIntent>>]/Pages 3 0 R/Type/Catalog/ViewerPreferences<</Direction/L2R>>>>

GTSPDFXVersion key
Should simply be set to the PDF X version: PDF/X-3:2002 (GTS_PDFXVersion(PDF/X-3:2002))

Document ID
The document ID is an array of two byte-strings constituting a file identifier
for the file. The first byte string is a permanent identifier based on the
contents of the file at the time it was originally created and the second
byte string is a changing identifier based on the file's contents at the time
it was last updated. It should be a MD5 hash.

Trapped key
The trapped flag in a PDF document indicates whether the document has been "trapped", i.e. corrected for slight color misregistrations, or not.
We simply need to set it to false (/Trapped/False)

Please let me know if I should provide example documents.

@grewn0uille
Copy link
Member

grewn0uille commented May 5, 2021

Hello!

(The survey is now closed. Thanks for all your answers! We’ll share the results soon 😉)

If you’re interested in PDF X/3 compliance, we created a short survey where you can give a boost to this feature and help us to improve WeasyPrint 😉

Vote for it!

@oneWaveAdrian
Copy link

@grewn0uille I would also be very interested in PDF/X compliance, it's been a while, is there any update on what you guys achieved so far / what the timeline is / how to help?

@grewn0uille
Copy link
Member

Hello,
You can find the results of the survey in this article. PDF X/3 didn’t do very well… so, except if it becomes a sponsored feature, it’s not on our roadmap.
If you want to have an idea of what is coming next, you can have a look at the milestones (please keep in mind they’re not set in stone).

@oneWaveAdrian
Copy link

Thanks for the quick response @grewn0uille, would you be willing to share the hardships of X/3 when you have time?
Maybe we can solve some of the challenges collectively as a community effort?

@grewn0uille
Copy link
Member

Hello again @oneWaveAdrian,

Sorry for the delay. I wanted to check on that but didn’t find time to do it.

The best thing to do to start digging into PDF X/3 (or other X version) is to get the spec, see what WeasyPrint does and doesn’t and find a tool to use to check the PDF X/3 compliance.

@grewn0uille
Copy link
Member

grewn0uille commented Sep 12, 2022

Hello!

As it’s soon our 2-year anniversary as CourtBouillon, we opened a short survey to know more about your expectations.
Don’t hesitate to support this feature and give it a boost 🚀!

The survey will be opened until October 10th.

Update: the survey is now closed. You can find the results here.

@grewn0uille
Copy link
Member

Hello!

As you may know, two weeks ago was CourtBouillon 3-year anniversary 🎉.

For this occasion, we prepared a short survey to have your opinion on this year’s features and to know what you’d like to see in the future!
Don’t hesitate to give a boost to this feature ✨️

The survey is opened until November 19.

@FelixSchwarz
Copy link
Contributor

Not sure but maybe it is time to close this issue now. WeasyPrint can generated PDF/A-3 compliant PDFs. I guess a lot of smaller things need to be fixed but in general I think at least some level of compliance is possible.

@liZe
Copy link
Member

liZe commented May 27, 2024

Not sure but maybe it is time to close this issue now. WeasyPrint can generated PDF/A-3 compliant PDFs. I guess a lot of smaller things need to be fixed but in general I think at least some level of compliance is possible.

Even if PDF/A is a great feature, some people may still be interested in PDF/X. This is not at the top of our priorities, but someone would be interested to work on it in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature that should be supported
Projects
None yet
Development

No branches or pull requests

5 participants