-
Notifications
You must be signed in to change notification settings - Fork 537
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
[FEATURE] Add support for Tagged PDFs #2046
Comments
Looking at the API, it appears fairly straight forward. |
@mattleibow That's very promising! Thanks for the reply. Any estimate for when this might get implemented/released? I have a project that's looking for this feature to replace existing aging technology. Thanks! |
Hi @mattleibow |
Any news for a release date? This library seems promising but i won't be able to use it if it has no accessibility features :( |
Initial builds are here! See #2865 (comment) Let me know if this is working as expected. |
@mattleibow Would it be possible for you to re-publish the package builds? I currently get this: (Not sure if there's a MyGet or "non-public"/experimental NuGet feed instead?) I'd be interested in playing with this. |
Is your feature request related to a problem? Please describe.
I want to produce a tagged PDF document. A tagged PDF document is a document who contains "tags", also called bookmarks, which is an accessibility feature (see image below). When the PDF is read in a compliant reader, there's a UI that allows the user to jump to the tagged locations in the PDF.
Describe the solution you'd like
A solution that supports what the native Skia library supports. I tried to review the Skia code and found the following commit from 2018. It contains a test as well that describes the usage of the feature.
In particular, the
PDFTag
,SkPDF::Metadata.fStructureElementTreeRoot
andSkPDF::SetNodeId
were the key pieces. I think an identical structure in SkiaSharp would be a great starting point.On top of the basic functionality, it would be amazing if there was an option to auto-generate the tags based on the document links already provided in the document rather than manually building it.
Describe alternatives you've considered
I didn't see a way to do this with the current APIs so I do not believe there's a work around. You can build document links and generate a TOC for example, but if you want links to all elements of a large PDF, the TOC becomes huge. It would be better to have a high-level TOC and a fully linked bookmark tree.
Additional context
For example:
The text was updated successfully, but these errors were encountered: