[Kde-accessibility] PDF accessibility

[Olaf Jan Schmidt]

[Bill Haneman]
> I don't believe an XML conversion would help here.  What is needed is a
> PDF viewer component/canvas that is able to report character positions
> as well as string content.  Only the rendering component can know this
> for sure - converting the content defeats the purpose of knowing where
> the "regular/normal" output is rendered to the screen.

Bill, this is not about screen reading or AT-SPI support in KPDF. This is 
about document reading in KSayIt, for example.

Olaf