OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook-apps] tagged and accessible PDF document with DocBook

Hi Holger,
There is a good reason simplelist and segmentedlist do not use fo:list-block. That element can only format two columns, but both of these kinds of lists can have any number of entries in a row, so a table is required. In the case of simplelist, the flat list of members can be laid out in any number of columns. In the case of segmentedlist, a seglistitem can have any number of seg children.

Bob Stayton
Sagehill Enterprises

On 4/24/2017 9:24 AM, Holger Bast wrote:
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,

Gesendet: Dienstag, 04. April 2017 um 09:18 Uhr
Von: "Bob Stayton" <bobs@sagehill.net>
An: "Dave Pawson" <dave.pawson@gmail.com>, "Holger Bast" <holgerbast@gmx.de>
Cc: docbook-apps <docbook-apps@lists.oasis-open.org>
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: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]