Issue 20475 - PDF export not fully compatible
Summary: PDF export not fully compatible
Status: CLOSED DUPLICATE of issue 17335
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 RC4
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: ---
Assignee: christof.pintaske
QA Contact: issues@gsl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-30 16:07 UTC by Unknown
Modified: 2003-11-19 17:56 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-09-30 16:07:52 UTC 
Using Adobe Reader for Windows, I am able to read all pdf documents exported by 
Openoffice. However, I am not able to convert those documents to the Palm 
format using Adobe Reader for Palm. I get the following error from Adobe reader 
for Palm:  

"Error converting to tagged PDF: Bad PDF; could not read page structure (bad 
page contents) .[1]

All other PDF documents created by other programs (Acrobat, Ghostview, etc) can 
be converted to Palm format. Only the PDF documents created by Openoffice have 
this problem. I have tried different versions of Adobe Reader for Palm and 
still get the same error. I suspect the PDF export function in Openoffice isn't 
100% compatible?
Comment 1 christof.pintaske 2003-09-30 18:04:15 UTC 
since pdf created by ooo works with almost every pdf-1.4 capable
viewer, including but not limited to the Adobe Acrobat Reader family,
I'm inclined to believe that ooo pdf is valid. 
we work on support for more pdf features in the next major release,
including structure information, which should make the Palm Reader
happy. Unless you have a more specific idea what might be the
stumbling stone for the palm reader here we will not dig further into
that now

*** This issue has been marked as a duplicate of 17335 ***
Comment 2 christof.pintaske 2003-09-30 18:05:09 UTC 
closed duplicate
Comment 3 philipp.lohmann 2003-11-19 17:56:18 UTC 
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.