On 10.01.2008 15:44:02 Li, Hao wrote: > Thanks Jeremias. > > Is tagged PDF (PDF/A-1a) on your plan and any possible schedule for > implementation?
No, it's not on any plan, yet, and therefore, there's no schedule. It's just that some of my clients are playing with the idea but the itch isn't strong enough, yet. > Any decent XSL-FO product you can recommend for a first try? AntennaHouse > I appreciate it a lot. > > -----Original Message----- > From: Jeremias Maerki [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 09, 2008 3:43 PM > To: fop-users@xmlgraphics.apache.org > Subject: Re: 508 compliance > > On 09.01.2008 21:29:31 Andreas L Delmelle wrote: > > > > On Jan 9, 2008, at 20:53, Li, Hao wrote: > > > > > Thanks Andreas. > > > > > > Yes. It is about accessibility. Although the pdf can be generated, > the > > > customer does not like it because of accessibility issues, for > > > example: > > > missing PDF tags, lacking language specification etc. > > > > > > After searching about tagged pdf, I found > > > http://xmlgraphics.apache.org/fop/trunk/pdfa.html. It seems that > > > PDF/A-1b is implemented, but not PDF/A-1a. Does it mean tagged PDF > is > > > not supported yet? > > > > Indeed. I know Jeremias recently mentioned tagged PDF as a (rather > > long term) goal, so there is definitely interest from other parties > > in adding this functionality as well. > > Right, there is some interest but so far it rather seems to be "nice to > have" than "must have". Furthermore, nobody can tell how far we'd have > to go with support for Tagged PDF. You can take a minimal approach or go > all the way. But in any scenario it will have a larger impact on the > area tree and renderers as far as I can judge right now (without having > looked into it too closely). > > > > I will be testing it as well. If not, do you happen > > > to know nay java plugin or product that can make accessible FO > > > conversion? > > > > Maybe you can have a look at post-processors, like iText (http:// > > www.lowagie.com/iText/) or PDFBox (http://www.pdfbox.org/). > > They can be used in conjunction with FOP in a fairly straightforward > > manner. Use FOP to generate the basic PDF, and feed the output to the > > > post-processor for further enhancements. > > Only they won't help with accessibility. As long as FOP cannot pass on > accessibility information from XSL-FO to the PDF there's nothing that > any post-processor can magically add. > > I think there are some commercial XSL-FO implementations that support a > certain degree of Tagged PDF but I don't know far they go and if that > would cover the 508 requirements. > > > > > HTH! > > > > Cheers > > > > Andreas > > > Jeremias Maerki > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
