pdfkit: add Options.Subject and Keywords for the info dictionary - #25
Merged
Conversation
The document information dictionary held only Title and Author. Subject (a one-line description) and Keywords (search terms) are the other two standard text fields a viewer's document properties and reference managers read. Both are written as PDF text strings, so a non-ASCII value is encoded UTF-16BE like Title/Author. Verified: Subject/Keywords appear in the info dictionary; an accented value is UTF-16BE (<FEFF…>), not raw UTF-8. 100% coverage; go vet and gofmt clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
The document information dictionary held only
TitleandAuthor.Subject(a one-line description) andKeywords(search terms, conventionally comma-separated) are the other two standard text fields a viewer's document properties and reference managers read. Both are written as PDF text strings, so a non-ASCII value is encoded UTF-16BE like Title/Author.Verification
Subject/Keywordsappear in the (uncompressed) info dictionary; an accented value is UTF-16BE (<FEFF…>), not raw UTF-8. 100% coverage;go vetandgofmtclean.Unblocks go-tex/engine wiring hyperref's
\hypersetup{pdfsubject=…,pdfkeywords=…}to these fields.🤖 Generated with Claude Code