Apache OpenOffice (AOO) Bugzilla – Issue 17335
Adobe's attempts to convert exported PDF to tagged PDF fail
Last modified: 2003-11-19 17:55:58 UTC
A PDF created by OOo 1.1 RC1 is not a tagged PDF; that is an issue for an RFE. This, however, is a bug: the Windows component of Adobe Acrobat Reader for Palm OS 2.0 attempts to convert it to a tagged PDF anyway, and produces the following error: Error converting to tagged PDF: Could not read page structure (bad page contents)[1]
Created attachment 7988 [details] Sample PDF file that fails to convert
Created attachment 7989 [details] Original sxw file
sorry, I cannot find any error. As the PalmOS converter states during the conversion: It might not be able to convert all valid PDF documents. That's what actually seems to happen. If you think this is an error, then please provide more information which PDF features need to be supported to make the PalmOS converter happy.
It's not saying, "Sorry, this is one of those PDF files that I warned you I might not be able to handle"; it's saying "Error" and "could not read page structure" and "bad page contents" -- which wording rather suggests to me that, according to Adobe's analysis, the file is not merely inadequate, but downright broken.
I'd say it cannot be that bad a PDF file as Adobe's Acrobat Reader as well as ghostscript and xpdf can display the file flawlessly. I must say i don't quite understand that error message as the document has a valid page tree; what it does not have is the structure information that would belong into tagged PDF (which OOo currently does not produce, no doubt).
As already said: If you think this is an error, then please provide more information which PDF features need to be supported to make the PalmOS converter happy.
I entered a separate issue the same day asking for tagged-PDF format to be supported. But I don't think it looks good -- to say the least -- that an Adobe product is saying that the file is not only inadequate, but actually broken. I know nothing of PDF internals, so I can't really help more than that. It's especially troublesome because, thanks to a _third_ issue I've raised, export as AportisDoc doesn't work right either. (And there's a fourth issue, not mine, pointing out that the AportisDoc Reader is a dead product anyway, even though it continues to be OOo's officially targeted solution for PDA support.) So, right now, trying to get an OOo document onto a PalmOS PDA is a real bang-your-head-against-the-wall experience, while, in the meantime, there's a third-party PalmOS program, reputed to be excellent, for handling (both reading and writing) MS Office documents -- but which I don't have, and don't know for certain will work with OOo imports and exports either.
sorry, I can't see what we could do here.
closing
*** Issue 20475 has been marked as a duplicate of this issue. ***
*** Issue 20824 has been marked as a duplicate of this issue. ***
FYI: we have worked out with Adobe's help what the actual problem is and will build in a workaround for the problem. The new issue for that is issue 22452.