PDF::Content 0.4.3 has some loosely coupled support for writing marked content.
PDF::Tags (under construction) can read, but not write tagged content.
So there's two competing APIs, (one for writing and another for reading).
Proposal is to export the newly created 0.4.x functionality for creating tags to PDF::Tags, so that there's a single API for both reading and writing tags.
Will leave the ability to read and write content stream tags in place (may rename). Will remove anything related to the struct tree.
PDF::Content 0.4.3 has some loosely coupled support for writing marked content.
PDF::Tags (under construction) can read, but not write tagged content.
So there's two competing APIs, (one for writing and another for reading).
Proposal is to export the newly created 0.4.x functionality for creating tags to PDF::Tags, so that there's a single API for both reading and writing tags.
Will leave the ability to read and write content stream tags in place (may rename). Will remove anything related to the struct tree.