PDF/A eFile ready mode (#2) #8
Open
Conversation
This file contains 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
Added a class option efileReady that enables the correct package for PDF/A output Added a few lines to the documentation to point this out Added metadata file PatentApplication.xmpdata (required for PDF/A)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added a class option efileReady that enables the correct package for PDF/A output
Added a few lines to the documentation to point this out
Added metadata file PatentApplication.xmpdata (required for PDF/A)
Hi Pete, I wound up having to do the PDF/A thing with a class option, since the class load change has to be done in the preamble of the class before the patent office mode switch is evaluated. I also added a bit of documentation, but let me know if you'd like more. The lyx file was complaining about unicode even before I made changes, so I set it to a unicode output based on some search engine results.
Let me know if there are any changes made; it looks like I can make them on my end and they will be incorporated into the pull request.