Zipping LR produced PDF Files

Have just produced my first PDF files using LR - one of 10MB, the other 8MB. When attempting to send these as an attachment to an email I received a pop-up advizing me that 10MB was the limit for any single attachment. I then had the idea of zipping the files but as it turned out the resultant zip files were almost as big as the original PDF's. I sent an email to PKZip enquiring as to whether or not I was doing something wrong. Part of the reply I received is as follows:
PKZIP will always get the best compression ration possible. If a file is already compressed or encrypted it can not be made much smaller by any compression software. If you are compressing a lot of pictures, images, movies, etc this will not compress well. My guess is that your PDFs you are trying to compress includes some of these types of files.
Well they guessed right as of course the PDF's were comprised of images. My question: not being a techie, does anyone know of a method of reducing the PDF's created by LR without obviously reducing the number of images or quality etc or is it something that I shall just have to learn with and from. Thanks :-)

Hi Alan
Unfortunately PKZIP (or any other equivalent program) can only significantly reduce files that are not already in a compressed format (otherwise you would be able to zip your zip file and so on :-) ). The PDFs that LR produces contain JPEG images which are already in a compressed format so you cannot get much further compression.
I suggest that you experiment with exporting the slideshow in a smaller format (e.g. 800 x 600) or use a slightly lower "quality" setting.
Another option is to split your large PDF into smaller parts so that each part can be emailed and then re-assembled at the destination.
Regards, Nigel

Similar Messages

ZIP attachments in PDF file

How can ZIP files be opened from a PDF file using Preview.
First, how can you see attachments within Preview, and then, how can it be opened.

For full details on the fix / workaround, see thread this post <http://forums.adobe.com/message/1152245#1152245> in the "Acrobat 9 Pro can't open zip attachment in Adobe tutorial PDF".

Cannot open the zip attachment in pdf file

I am using the Adobe Acrobat 8.1.2 professional
and i attach the zip file in the pdf file
after that, the user that just use the Adobe Reader 8.1.2 cannot open the Adobe zip attachment.
Do i do any one in add the attachment or the Reader cannot open the attachment with zip file
thx for your help..

I have the same issue. With acrobat 7, it is possible to modify a register. But what is solution for acrobat 8 ?(the register is not available anymore)
It is not possible to save the attached file to disk neither.
JB

Acrobat 5.05 Distiller not Producing .pdf Files

When I first purchased Acrobat 5.05 and installed it, to produce a .pdf file from an application, I printed the file from the application choosing Acrobat Distiller as the printer. This prompted for a file name and location. When the OK button was clicked, Acrobat 5.05 launched, and the .pdf file appeared, and was able to be saved. No other steps were needed.
Now when I attempt to do this, the application indicates that it is printing, but Acrobat 5.05 does not launch, and no .pdf file is produced in any folder.
Re installing Acrobat 5.05 does not correct the problem.
What needs to be done, to make this version of acrobat distiller operate as it originally operated?

Normally it is only needed if you are requesting a PS file that may be sent to someone else and they do not have the fonts OR if you are printing another PDF that had embedded fonts that you do not have one your system. Otherwise, Acrobat will go to find the fonts on your system as per the distiller font list.
The print to file is the most fundamental PDF creation process in AA 5. All of the other options build on it. The repeating the process, but unchecking the print-to-file button. In that case a PS file will be created by the print driver (directed to the Adobe PDF port or such -- I would have to go to my other machine to check the name for sure, but should be obvious unless it is missing) and then AcroTray is supposed to recognize that the file exists and then run distiller in the background. PDF Maker is just a front end processor for the Acrobat Distiller printer. Note that the name has since been changed since folks got the print driver confused with the program Distiller. They did the same change in name to Reader since folks keep thinking they had Acrobat when they only had the Reader. (At least that is my take on their reasons that I have not really seen.)
AcroTray is found in the Distiller folder. It should be in the startup folder of Win XP, listed as Acrobat Assistant. If you look at the running processes with ctrl-alt-del, it should be listed (just click on the program columns to get an alphabetic list). If it is not running, then start it. If it is running and you are having problems, then try ending it and then restarting it from the Distiller folder (just double click on the program).
Also, be aware that unless you change a preference in Distiller, the settings you pick in the Acrobat Distiller printer properties will over ride those of Distiller for the most part. And any changes you make in the printer properties from within a program will over ride the default printer properties, but will not be carried over to the next use of the program -- the defaults will again be loaded. So if you want a particular default setting, use the Start>Printers>Acrobat Distiller (right click for properties) to set the default properties. I never use the standard job settings for instance, but always use something like the press or print settings that embed all fonts. I reality I use a job settings created by a publisher.
So all I am trying to step you through are the basic trouble shooting steps that are necessary to get your system working. Finding where the problem is becomes the first step. We now know that you can print-to-file and produce a PDF with Distiller. Actually, I loaded AA5 on a Win7 Starter system and was able to create PDFs using this process. The AcroTray from AA5 does not work in Win7. Actually, for Win7, I just tried it by changing the port to File and so I don't even have to check the print-to-file button. That was really more of a test to see what broke, and I was surprised that it even installed on the 32-bit netbook. My guess is it may not work at all on a 64-bit system. However, on XP, your AA5 should work fine once we trace down the culprit.

Producing PDF files on the fly

I'm on a team of three developers. Unfortunately, all are novice level. We need to create PDF reports from data retrieved from the database. We are already displaying this information in a JSP page. I know there are some options out there. We just don't understand how to start. Anyone care to tutor me on this?

I dont know what you mean with tutor, but:
(1) Generate XML from the data in the database.
(2) Use XSL to transform your XML into XML-FO.
(3) Use FOP to transform XML-FO into PDF.
(4) Use a servlet (not a JSP) and write the bytes of the PDF to the response outputstream.

FAQ: Creating PDF Files from FrameMaker v.6 & earlier Documents -- Why you should not use "save as PDF"! -- Windows & MacOS Only!

An issue that has come up over and over again on several FrameMaker and Acrobat/PDF email lists as well on the corresponding Adobe User-to-User forums is that of creation of PDF files. FrameMaker 5.5.6 and 6 have what looks like a convenient feature that is supposed to allow you to create PDF files via simply saving the document as a PDF file. I have gone on record as advising end-users not to use this approach for reliable creation of PDF files from FrameMaker documents under Windows and MacOS with FrameMaker 6 and earlier. Why do I most vociferously offer this advice and why doesn't the problem get fixed? And how SHOULD you create PDF files from FrameMaker?
GOOD NEWS
I will start with the good news. The "next major version" of FrameMaker will indeed have "save as PDF" re-implemented in a manner that it will be as reliable as printing to the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS. I am personally working with the FrameMaker development organization to make sure this really happens and is fully and properly tested and debugged! Furthermore, this next major revision of FrameMaker, unlike FrameMaker 6, will come with a Distiller installer that will properly install the "Acrobat Distiller" printer instance under Windows and the "Create Adobe PDF" desktop printer on the Macintosh (of course assuring that the latest PostScript driver is also automatically and correctly installed).
DON'T USE "SAVE AS PDF"
But what's wrong with "save as PDF" as currently implemented?
The following are some of the SYMPTOMS reported over the last few years by FrameMaker users that were traced back to use of "save as PDF" under FrameMaker:
(1) No PDF file is produced at all, possibly with a log file showing not-readily apparent PostScript errors during distillation.
(2) The PDF file "loses" color in images. All or some images (raster, bitmap images, NOT vector artwork) appear in the PDF file in grayscale.
(3) The resultant PDF file is on the wrong paper size, i.e., the document's logical page size does not match the output page size as seen in Acrobat or Acrobat Reader.
(4) Some or all text in the resultant PDF file is blotchy looking or overly bold.
(5) Some or all text in the resultant PDF file cannot be searched or indexed.
(6) Some or all text in the resultant PDF file appears in Courier or in some other substitution font.
(7) Interword or intercharacter spacing is a bit irregular in the resultant PDF file.
(8) Content is missing in the margin areas of the page, i.e. you cannot do full-page bleeds.
(9) Some or all page content is missing (other than margin areas).
(10) Relatively inefficient PDF is generated.
If this list by itself isn't enough for you, please note that some of these symptoms are very subtle and may escape attention when the PDF is first viewed or printed. Oftimes, it is when one attempts to manipulate the PDF file in Acrobat or repurpose its content or even view or print on a system other than the one on which the PDF file was created, that some of these symptoms make themselves obnoxiously visible (or invisible in some cases I won't make any bad jokes here about graphic examples!).
It is important to understand that FrameMaker does NOT have its own native ability to create PDF. Any and all PDF created from FrameMaker documents is actually done by creating PostScript via the PostScript driver and having the Acrobat Distiller create PDF from that PostScript. The only exception to this is creation of PDF via the Acrobat PDFWriter driver, which is likewise not recommended (see below).
In order for "save as PDF" to work correctly, FrameMaker must do the equivalent of calling Printer Setup and selecting the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS followed by setting the driver's options correctly for paper size, page range, etc., followed by sending the proper commands to the driver to create PostScript.
Contrary to popular belief, PostScript as generated by the Windows and MacOS PostScript drivers is VERY device-dependent. The information in the PPD file associated with a printer driver instance provides critical parameters for generation of PostScript including:
Whether the printer supports color (Acrobat Distiller does)
What PostScript language level is supported (Acrobat Distiller 4.x and Acrobat Distiller 5.x are both PostScript language level 3)
Whether native TrueType support is available (Acrobat supports native TrueType as Type 42 fonts)
Available binary communications (Acrobat Distiller supports pure binary and ASCII, but NOT TCP, TBCP, or PJL)
Resident fonts (Acrobat Distiller doesn't really have resident fonts)
Available paper sizes and custom paper size availability (Acrobat Distiller supports a wide range of predefined sizes and continually variable "custom" sizes up to 200" by 200")
Margins / printable areas (for PDF and the Acrobat Distiller, there are no margins in which imaging is not permitted)
Device resolution (Acrobat Distiller can be set to any value from 72 to 4000 dpi; as a convenience, the Acrobat Distiller PPD provides a series of values for use by the driver. Since there is no inherent "resolution" of a PDF file, this parameter is used only for purposes of allowing PostScript programs that query for such a value to be satisfied and for the driver to be able to communicate this value to the operating system and/or application as required.)
Paper handling (totally irrelevant to Acrobat Distiller if input or output tray selection via "setpagedevice" is found in the PostScript stream, it is ignored by Acrobat Distiller)
Thus, if the wrong printer driver instance is selected (i.e., it isn't associated with the Acrobat Distiller PPD file) or that driver instance is improperly configured, improper PostScript will result and one or more of the symptoms described above can occur. As currently implemented, FrameMaker depending upon version will not necessarily choose the correct printer driver instance and/or correctly parameterize the print job via driver setup options. In fact, FrameMaker 5,5,6 might even try to generate PDF via calling a PCL driver, FAX driver, or even a non-PostScript inkjet printer!
DON'T USE PDFWRITER
The Acrobat PDFWriter is a relic of older versions of Acrobat. In fact, it is no longer installed by default in the "easy install" or the "typical install" of Acrobat 5. It hasn't really be updated since Acrobat 3 and only supports PDF 1.2. It is a GDI (Windows) / QuickDraw (MacOS) driver that directly generates PDF without any intermediary PostScript. Since it is not a PostScript printer driver, applications cannot pass through EPS graphics and/or PDFMark information (used for a wide variety of purposes by FrameMaker). For EPS graphics, most applications will send the low resolution TIFF (or PICT) EPS header in lieu of the PostScript text, if they send anything at all, to the driver. Forget about links, structure, or any other PDF "goodies." Expect that PDFWriter will fully "bite the dust" in the next major version of Acrobat.
SO HOW DO I GENERATE PDF FILES FROM FRAMEMAKER 6 & EARLIER?
The ONLY method that is really reliable for producing PDF files with FrameMaker 6 and earlier requires the generation of PostScript via a properly set printer driver instance associated with the Acrobat Distiller PPD and distillation of the resultant PostScript by Acrobat Distiller.
Case 1: FrameMaker and the Full Acrobat 4.05 or Acrobat 5.0x Products
PDF file from a "chapter" -- print directly to the Acrobat Distiller printer instance (Windows) or the Create Adobe PDF desktop printer (MacOS) already installed by Acrobat. If you check the "Acrobat data" option, then make sure to UNcheck the "print to file" option that gets set at the same time. As a result, the driver will automatically send the generated PostScript to the Distiller for you and delete the intermediate PostScript when done.
PDF file from a "book" -- print directly to the Acrobat Distiller printer instance with the "print to file" option checked (Windows) or the Virtual Printer desktop printer (MacOS) associated with the Distiller PPD (see details below under Case 2/MacOS). You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
In both the above sub-cases, the default driver options generally will be OK, but check on paper size and communication protocol (Use pure binary, not ASCII, for optimal performance AND no CTRL-D characters under Windows. Make sure to set Level 3 only and Binary under MacOS. Font inclusion "All" for Acrobat 4.05 and "None" for Acrobat 5 under MacOS.). With Acrobat 4.05, make sure you preset the Distiller to use the joboptions you want. With Acrobat 5, you can set this on a job-by-job basis via the driver printer setup interface (or print dialog on MacOS).
Case 2: FrameMaker 6 and the Bundled Acrobat 4.05 Distiller
Windows -- Create a new printer driver instance using the latest version of the Adobe Universal PostScript Driver Installer, downloadable from Adobe's web site AND the Acrobat Distiller PPD file (located in the XTRAS subdirectory of the Distiller directory). This driver instance should be set to print to the local port named "FILE:". Name this driver instance as "Acrobat Distiller". The default driver options generally will be OK, but check on paper size and communication protocol (use pure binary, not ASCII, for optimal performance AND no CTRL-D characters). Make sure you preset the Distiller to use the joboptions you want. Print directly to this Acrobat Distiller printer instance. Make sure that the "print to file" option is checked. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
MacOS -- Install the latest version of AdobePS 8.7.x, downloadable from Adobe's web site. In FrameMaker, go to Page Setup and select the "Virtual Printer" and go to the "Virtual Printer" window pane. Select the Acrobat Distiller PPD file (located in the XTRAS subfolder of the Distiller folder). Print directly to the "Virtual Printer" (Make sure to set Level 3 only, Binary, and font inclusion "All".). Make sure you preset the Distiller to use the joboptions you want. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
Case 3: Acrobat 3
Acrobat 3 is not officially supported for the latest OS versions and I personally would no longer recommend its use for generation of PDF files given that Acrobat 5.0.5 is the current version of Acrobat.
- Dov

You're asking a lot of ancient Acrobat to work with an Office that never existed when it was made. "Just updated my office suite" is a massive change, and Window 8 didn't exist at that time either...

PDF file size

I have an HP Officejet 6500 E710n-z (Network) that I use at home to scan into PDFs, and I know exactly how to move the slider from "Smallest size" to "Best quality"
However the size of the PDFs are unacceptably large when image quality is acceptable, and if I move the slider to reduce the size then the image becomes unacceptable. It is impossible to scan a legal document of more than a few legible pages without producing a file size too large to email . I am forced to break these scanned documents into 3-4 page bite-sized chunks.
A simple one page HOA Disclosure form, at 220 DPI and the slider in the middle for balance, produces a 699K PDF. I have used other printer scanners at work (different brands) at the same 200 DPI that results in very clear documents at less than 100K per page.
I believe there is something wrong with HP's scan-to-PDF algorithm. The problem must be due to some unskilled (or flawed) software design. What will it take to have HP or third party developer (and developer staff supervision) take this seriously -- compare HP vs other brand scanners PDF files -- and update the HP drivers to fix this?
This question was solved.
View Solution.

Just a follow up. I went into chat mode with some low-level tech named Nathan, giving him the link to this thread. After reading it, he suggested I can improve file size by using greyscale and 200 DPI. DUH!!!! I complained he was just humoring me, so he said I should call the tech support number.
I did that next and spoke with a very nice young lady who actually DID take me seriously. I could hear her typing away vigorously in the background, capturing every detail of my plea for this to be forwarded up the chain of command for serious consideration. It was clear she understood and captured from me that there are many forum complaints that can be found with a search term "PDF File Size" that are getting weak or unacceptable "solutions" to push the slider left or use lower DPI etc. She also captured my assurances that some competitor brands produce PDF file sizes 20 times smaller for the same image quality.
I believe that this might actually be opened up at a higher level for consideration of an improvement in the compression algorithm. My fingers are crossed. Since I have about 11 months left for warranty support, I plan to contact them once or twice again before it expires, using the same case number to see if there is any progress.
Bottom line: At my default of 200 DPI and 20% image quality, with an average file size for a single sample page producing a file size of 281KB, a 25-page document creates a PDF file that is 7MB! That will just barely make it past the file size limit for my email provider, but might be too large for the recipient. That is still unacceptable, and is forcing me to consider products other than HP for this business purpose.

Linking to a pdf-File in Captivate 5.5

Hello,
I hope you can help me with th following question, thanks! I've seen similar problems like mine on the forums, but it's not exactly the same.
The screenshots are in german, but I think you get the idea.
When linking to the file of the button I use the following options (used "New Window"):
After publishing (.swf-File) I copy the folder "PDF" containing the file "Hardcopy.pdf" into the published folder. When I click the button in the WBT the pdf file opens perfectly.
But now I want to upload the WBT to our LMS and therefore I need to zip the file. In the zipped mode the pdf file doesn't open when clicking the button.
Any solutions? Thank you for your help!

If you're talking about a zipped SCORM package, did you test opening the PDF on your LMS after uploading the SCORM and setting up the course? What normally happens is that the LMS unzips the SCORM package to a location on the web server when you set up the course. If your PDF was inside the zip file, and the relative path from the calling SWF to the PDF was not changed, then it should still work.
One suggestion I would make is to always use lower case for all file and folder names. I notice you have a combination of upper and lower case filenames. This is not good practice when uploading content to web servers as some servers are case sensitive and others are not. I've seen instances where broken links were simply due to the way the server interpreted mixed case filenames. If you only use lower case, you don't usually suffer this issue.

Convert PS to PDF file in Adobe Distiller using javascript

Hi scripters,
I have created some PS files from Indesign using javascript. Files are d:\test\1.ps,2.ps
Now I want to convert this ps files into pdf files uisng javascript?(I am not comfort to use export as PDF option for this job)
how I can do this?
Thanks in advance
regards
a r u l

Hi arul
Firstable, you may not need to create PS files as Indesign is able to produce PDF files natively. I was told that it was more reliable to do so using a certification profile such as PDFX.
You will find a lot of PDF export script everywhere.
However, if you want to go that way (PS to PDF). I did that once.
First you determine into distiller a hotfolder where you ps files wille be generated. Then in the hotfolder options, you precise the profile you want to use. Otherwise, distiller may be using low quality PDF as default and your PDF may not be as good as you want.
var distiller = File("c:/xxx/yyy/zzz/distiller.exe"); //the path to your distiller app.
distiller.execute();
Here you are !
Loic

Jsf form to pdf file, how?

Hi all how to transform a jsf form to a pdf to download?
many thanks

There is no such thing. Generally you use the print function of the browser - it is your job to properly apply css so a page prints nicely. Otherwise you have to dig into itext which is the api for producing pdf files.

Automatic conversion from XDP file fo PDF file

Hello!
I have an application that creates an XDP file with a certain report.
I can open the XDP file in Designer 7.0 and then save it as PDF, but I would like to know, how can I automatically produce PDF file from XDP file.
Is it possible?
Thanks for your answers,
Bostjan

Hi All:
We have a similar requirement for our product.
We have existing XDP templates (for use with Form server), but we have a need for another Client using an older version of XML Forms - AcroForms (PDF Forms).
So, we need to convert these XML forms in XDP files into PDF Forms (AcroForms). We tried File->SaveAs (PDF Forms) from Adobe designer, but it looks like the hidden fields (in XDP files) get messed-up.
Did you guys find any solution for this? I would appreciate if you can share your experiences and insights in this regard.
Thanks
Shashi Velur

Would Doclet API helps while converting frame maker files to pdf files

Through Doclet API, can we convert frame maker (.fm) files to the PDF files ?
I have requirement that I need to convert bulk of frame maker files to the pdf files actually, while googling I came to know that Doclet may support.
If anyone has worked on this type of project, please help me.
Thanks a lot.

Someswara wrote:
Through Doclet API, can we convert frame maker (.fm) files to the PDF files ?No.
Someswara wrote:
I have requirement that I need to convert bulk of frame maker files to the pdf files actually, while googling I came to know that Doclet may support.There is a doclet (called [MIF doclet|http://java.sun.com/j2se/javadoc/mifdoclet/]) that can produce .fm files from Java source files, if a you have fmbatch installed. To produce PDF file using MIF doclet or from *fm files you still need Adobe FrameMaker.

How to exreact multiple pdf files from a zip files from application server to presentation server

Hello exprts,
I am passing one pdf file and one text file to zip file in apllication server through my custom program and then downloading it using standard function module to my desktop. its working fine. Then I added another pdf file to my zip file. But only single pdf file is getting download . So can you please help me regardiong this issue?

Dear Experts ,
I finded out the way to extrcat pdf files in presentation server. But now my problem is that I am not able to add multiple pdf files in a zip file. When I am adding new pdf file then older one is not coming in read data set. So please kindly tell me how can I add multiple pdf file in my zip file and again I can get all the pdf files from here.

Grey background while saving pdf file as a ZIP in IE browser

I am getting grey background while saving pdf file as a ZIP file in IE browser like below screen shot
The pdf open properly but when I click on save button on below screen it become grey.
The file is getting saved properly.
But the same thing working fine in firefox(I will not become grey while saving)
we are using adobe 11 version.

I am getting grey background while saving pdf file as a ZIP file in IE browser like below screen shot
The pdf open properly but when I click on save button on below screen it become grey.
The file is getting saved properly.
But the same thing working fine in firefox(I will not become grey while saving)
we are using adobe 11 version.

Scanning always produces invalid PDF files

I recently purchased an HP OfficeJet 4636, and I notice that when scanning documents to PDF, the generated PDF files are always invalid. When opening these files in Acrobat Reader or Acrobat Pro, one gets the message "The file is damaged but is being repaired." Many other PDF tools can't open the files at all.
I have installed the newest firmware update and restarted the printer, but the problem was not solved.
I tried many different settings (e.g., resolution, paper size, scan from ADF, scan from Glass), but the problem is always the same. For the record, I am using the "Web scan" interface: http://XX.XX.XX.XX/#hId-pgWebScan.
If there were an opportunity to attach a file to this bug report, I would attach an actual PDF file generated by this printer. I am happy to supply the file later, and I will refer to this specific file in my analysis of the bug below.
I am familiar with Adobe's PDF definition:
PDF Reference, sixth edition. Adobe Portable Document Format
Version 1.7, November 2006. Abobe Systems Incorporated.
I examined the PDF file in detail and it is quite clear what the bug is. Object 1 of the PDF file starts at byte offset 10, and it is a stream object containing the main image data in compressed JPEG format. The Length field for the stream object (at byte offset 168) is set to 1051875. However, the actual compressed stream data is only 64914 bytes long.
This is incorrect, because the PDF Reference (Section 3.2.7, p.61, "Stream Extent") specifies that "If the stream has a filter, Length is the number of bytes of encoded data." (emphasis in original). In other words, the stream length should be set to 64914, which is the length of the JPEG encoded data, and not 1051875 (which is presumably the length of the raw unencoded image data).
Moreover, four of the entries in the PDF xref table (at offset 65504) are incorrect:
the byte offset for object 2 is given as 1052085 (actual location of object 2 is 65124);
the byte offset for object 3 is given as 1052140 (actual location of object 3 is 65179);
the byte offset for object 4 is given as 1052206 (actual location of object 4 is 65245);
the byte offset for object 5 is given as 1052383 (actual location of object 5 is 65422).
Also, the PDF startxref pointer (at offset 65674) points to 1052465, whereas the actual location of the xref table is byte offset 65504.
Note that in all six cases, the error is exactly equal to the difference between the declared stream length (1051875) and the actual stream length (64914):
1051875 - 64914 = 986961
1052085 - 65124 = 986961
1052140 - 65179 = 986961
1052206 - 65245 = 986961
1052383 - 65422 = 986961
1052465 - 65504 = 986961
It looks like this is a simple programming error in the printer's PDF generation software: all the offsets are computed as if the length of the embedded image stream were 1051875, whereas it is actually 64914.
I scanned at different page sizes, resolutions, and so on. Each time, the actual byte offsets were slightly different (depending on the length of the encoded image stream), but the above relationships still hold in each case.
Please fix this! It is not really acceptable for an HP scanner to produce broken PDF files. Thanks, -- Peter

Hi @Selinger
One of the important things to point out is that the Webscan feature was designed for diagnostic purposes. The intended method of scanning is with HP software and the software build into the OS.
For Mac users this includes Apple Preview, Image Capture, or scanning from the Print and Fax Window.
For Windows users, non HP software includes, Windows Live Photo GAllery, Paint, and Windows Fax and Scan.
Webscan is a great alternative, but it is very basic. Your best option it to install the HP software and us the HP Scan program.
If there is a particular reason you are using Webscan and prefer to scan this way, the only thing I can really suggest is to try a different browser.
Please let me know the outcome of a different Browser, what Browser you are currently using, and what happens when you scan with HP software. If you require further assistance, please also include your operating system. What operating system, and version do you have? Mac or Windows?
I hope this helps.
Please click the Thumbs up icon below to thank me for responding.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Please click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution.
Sunshyn2005 - I work on behalf of HP

Zipping LR produced PDF Files

Similar Messages

Maybe you are looking for