A few comments to this patch: A few months ago, I was asked by a client
to implement Tagged PDF support for FOP but I didn't have time to do it
myself. I was able to pass the lead over to Jost. Since then I've been
coaching Jost (in the background) to get this done. He had his reasons
to only appear on the mailing lists now. I'm hoping he will participate
in any follow-up discussions concerning accessibility and this patch.
I've already reviewed an early version of the patch and I was already
quite happy although I had some issues which Jost has now addressed (I
assume). I have yet to take a first look at the new patch. Since there
was next to no discussion about this topic here, I will of course not
just process the patch in a hurry. It's important that everyone has a
chance to review what's being proposed here. I also have to figure out
how best to approach the merge of the IF branch into Trunk, i.e. with or
without this patch to begin with. We can also put the patch into its own
branch at the beginning. All open for discussion.
Since it's a relatively big patch I'd like to have a vote about its
integration into our codebase once everyone had a chance to review this.
Jost has already submitted an ICLA to the ASF's secretary and I'm
monitoring its recording. We also have to see if the patch is big enough
to require a software grant to the ASF (like we did for the AFP renderer
or the PostScript DSC parser in XGC). I'll look into this in the next
If there are any questions, Jost is on this list, and I'll help out to
fill the gaps where I can.
That said, I think this is exciting new functionality for FOP. Once this
is integrated, I will implement PDF/A-1a functionality which another
client of mine would like.
There are also other possibilities for improvement later: Full support
for controlling the document language, optional addition of layout
attributes (like indents, text align, text decoration), or support for
the "role" property in FO (RoleMap in PDF) and probably more.