|
What are you using to create the PDF files? I know some software is more "picky" about exact PDF specs than others, and one wrong byte and they won't like them. I know on my software that creates PDFs you have the option of selecting the code page to use (defaults to 819). Brad www.bvstools.com On Thu, 30 Jun 2005 15:58:35 -0400 "Allen" <rallen@xxxxxxxxxxx> wrote: > We have been converting our reports to PDF on the AS/400 > and > placing them either in the IFS or onto a NT file server > > using CPYTOSTMF. > > Everything works great and the users love it. > > > > Now we need to place some PDF files onto a Linux box. > > We have mounted a drive and all that stuff and we have > been > able to successfully place the PDF files on a Linux Box. > > > > When we open these files (on the Linux box) using Windows > explorer they open fine. > > > > Problem: > > When we try to open these files (on the Linux box) from a > web browser we get an adobe error "File damaged cannot be > opened.." > > If we create the files in the IFS and copy them to the > Linux > box they open fine from the Web Browser. > > > > I was told it could be the code page (in the IFS they are > created as code page 1252 (as is the directory), > > on the Linux Box they are created with Code Page 437 (as > is > the directory). > > I am not sure why they would open in Windows Explorer if > the > problem was the code page. > > > > Does anyone have any suggestions of where I should look > for > a solution? > > Does anyone know how I can force the directory and files > to > be created with Code Page 1252? > > > > Someone else says it could be an authority issue when a > file > is placed on the Linux there are more authorities then on > the iSeries > > So they may not have the correct authorities. And when > the > files are copied from the IFS to the Linux (using Windows > Explorer) the > > Authorities are set correctly by Windows????? > > If this is the case does anyone know how I can create > them > with plenty of authority > > (these are public documents) > > Thanks all > > > > Allen > > > > > > > > -- > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: > http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/midrange-l. > Bradley V. Stone BVS.Tools www.bvstools.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.