Merged
Conversation
Co-Authored-By: Martin Haug <mhaug@live.de>
laurmaedje
commented
Sep 30, 2024
Collaborator
|
Do you think there is really value in allowing selecting the PDF version as well? I think the only thing users might care about is choosing the right standard (PDF/A, PDF/UA, etc.), which themselves always dictate which PDF version must be used. And removing that would make it impossible to accidentally choose a wrong combination. Maybe there is value in keeping it, but just thought I might ask. 🙂 |
Member
Author
|
Wrong combinations would result in an error. The idea here was to allow opt in PDF 2.0 support down the road. We wouldn't add 1.6 or lower. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull requests adds support for optional conformance to the PDF/A-2b standard. This is realized through a new
--pdf-standardCLI option which takes one (or multiple comma-separated) PDF standards that Typst should try to conform with. This list is validated for compatibility (though the current two options (1.7, a-2b) are simply always compatible). Support for more standards is planned for the future.Closes #2995
Closes #3002
Closes #3004