Hi there,
I started on writing a specification document that maps the DocBook elements to the necessary PDF structure elements.
Well, I started with FOP (based of PDF v1.5) as basis, but I think that the other processors act the same way. It would be great if someone familiar with XEP, Antenna, DocMill, etc. could have a look at the document and give some feedback. The document can be found over here: https://docs.google.com/document/d/1DrADbdNjFEeXBv5n7LNIBrKsI1Kl-oqY5jkN-U8K5p8/edit?usp=sharing
The document is not yet finished but it is a good starting point for implementing tagged structure elements in the DocBook -> FO transformation process.
So, if someone likes to add some content, please contact me (via this mail address) for edit-privileges.
During my time writing this document I came across several 'anomalies' of the DocBook XSL transformation that I also would like to discuss with you:
The list types 'simplelist' and 'segmentedlist' don't generate fo:list-block-code content. simplelist uses a table or inline element for rendering. I think this will not be that easy to tag in PDF. Maybe the implementation could be changed? In the case of segmentedlist there is fo:block code generated. Maybe the reuse of quandaset code could help in that case.
Any feedback is welcome!
Thanks to Tony and Katharina providing me further information!
Thx + Bye,
Holger
> Gesendet: Dienstag, 04. April 2017 um 09:18 Uhr
> Von: "Bob Stayton" <>
> An: "Dave Pawson" <>, "Holger Bast" <>
> Cc: docbook-apps <>
> Betreff: Re: [docbook-apps] tagged and accessible PDF document with DocBook
>
> On 4/3/2017 11:31 PM, Dave Pawson wrote:
> > No, xsl-fo has no document wide 'structure'. If any, that should come
> > from your source XML and
> > be carried over to the fo, then PDF.
>
> Exactly. Now, what I need is a mapping from DocBook elements to fo, for
> the three FO processors. Then I can implement it in the XSL. If
> someone were to generate that spec, it would speed up the process greatly.
>
>
> Bob Stayton
> Sagehill Enterprises
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
>
>
