Why am I asked to save a PDF after only viewing a file

In Acrobat 11, even when there has been no change, I have to tell acrobat not to save a viewed document

Are you sure there are no form fields at all?
That would include read only fields alike a date field that is populated when the PDF opems or a button?

Similar Messages

Why is the option to save a pdf as a jpg gone?

why is the option to save a pdf as a jpg gone?

My mistake. This is how it used to work for me in Reader: I hovered over SAVE AS and there used to be an option to save as an IMAGE, and hovering over IMAGE gave me the option to save as a jpg.
So you are suggesting that this all used to happen in Acrobat or AIR, or something?
What I’m trying to do and what I used to do is create a word doc, then save it as a pdf, then convert it to jpg.
Thank you,
Stacey Rice-Westphal
Monterey County
Department of Child Support Services
(831)769-8722
CONFIDENTIALITY NOTICE: This communication with its contents may contain confidential and/or legally privileged information. It is solely for the use of the intended recipient(s). Unauthorized interception, review, use or disclosure is prohibited and may violate applicable laws including the Electronic Communications Privacy Act. If you are not the intended recipient, please contact the sender and destroy all copies of the communication.
IRS Circular 230 Disclosure: Recently adopted Internal Revenue Service regulations generally provide that, for the purpose of avoiding federal tax penalties, a taxpayer may rely only on formal written advice meeting specific requirements. Any tax advice in this message (including any attachments) does not meet those requirements and is not intended or written to be used, and cannot be used, for the purpose of avoiding federal tax penalties or promoting, marketing or recommending to another party any transaction or matter addressed herein.

Why does Apple ask to save passwords?

Why does Apple ask to save passwords?I am using PC's.

Thanks Doc, and apologies for tardy reply. I've checked the file permissions and all seems to be right. I've also re-made the bookfile with the same result.

I cant save a pdf after editing

I cant save a pdf after editing it. My edits = mark up of text using yellow highlight marker.
the file downloaded from internet by doing saving as (in explorer that opened the pdf once cliced upon in the browser)
the file looks like an pdf in my organizer
use acrobat 9 pro
browers explorer 9
system windows 9 enterprise

I have the same problem. I have a PDF thats 1gb, and it hasnt been any problems saving it in the past, but now when i try to add other pdf-documents to it i cant save the file. Literally nothing happens when i press "save", or "save as".
I have tried to make a copy of the file and that doesnt help. Everything is "Allowed" when i check ctrl+d.
What can be wrong?

When I save a site after I modify the file the changes do not show up in my upload file.

When I save a site after I modify the file the changes do not show up in my upload file. What am I doing wrong?

Start here:
iPhone, iPad, or iPod touch: Device not recognized in iTunes for Windows

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...

Why am I unable to save unsecured PDFs

I have Acrobat 9 on a new Vista PC. All of a sudden I am having difficulty saving downloaded PDF documents, even tho they are not secured (i.e. Properties/Security shows everything Allowed including copying). Am even in email correspondence with one of the PDF's publishers who can't reproduce my problem - i.e. he also thinks that I should be able to save a download of his PDF document !
Neither clicking the save icon in the Acrobat toolbar nor picking File/Save As in the Explorer toolbar brings up the usual save dialogue box.
The strange thing is that the difficulty seems to arise on only some sites/downloads, not all.
Does anyone have any technical insights into this issue? Anything to do with Vista security or McAfee, perhaps?
With thanks for any assistance!!
David
London

Hi David,
The suggestion you made did the trick. Can download web pdfs again.
Looking forward to more solutions.
Louis
2009/10/11 DavidJacquesA <[email protected]>
Hi Louis,
>
I found a decent guy at Adobe who is looking into the matter for me, in
case there are other lurking issues. Meanwhile he suggested an Adobe Acrobat
9.1 workaround that does seem to solve the problem in the short term. Try it
- if it's available in Reader - and good luck!
>
David
>
EXTRACT FROM ADOBE MESSAGE:
>
>
I'm sorry to hear you are still having problems with Acrobat. I am going to
run a couple of tests with a Vista image here to see if I get the same
issue.
>
In the mean time, in Acrobat, you would probably benefit from not
displaying the PDF in browser:
menu Edit > Preferences : Internet : uncheck "Display PDF in browser" This
should in theory allow you to save the PDF using Acrobat's own menus.
>
Another option is to right click a link that points to a PDF and use Save
Target As...
>
>
END OF EXTRACT FROM ADOBE MESSAGE
>
David Abrahams
Brand Mediation
London
>
+44 (0)7771 601 652
>

When i save as pdf I only get half of a page

I am trying to save as a PDF and when i open the saved file only half of the data is viewable. I cant figure out how to View/print/email a compleate document.

What program are you trying to save as PDF *from*? Adobe Reader only shows PDFs on screen, it doesn't make them.

Why does Pages ask me to save changes when I only open a file and print it?

I have documents that I open regularly but only want to print (and not make changes to). But, even if I open them and do nothing other than print them, Pages prompts me to save changes when I close the file. Why is this?
If I've had the document open for a while, I'm always concerned that maybe I've made changes that I want to save and forgotten.

But it always, always, always ignores it, fruhulda. That's what I'm saying. A brand new document on a brand new computer with a fresh install of iwork, and the same thing happens. Every time I open it and print--Do you want to Save? Do you want to Save?
For instance, I have a contract form I use regularly and I get that every.single.time even though I always use the same printer, and have hardly ever used the printer that pages has chosen as my default printer (a medium format inkjet with archival ink that costs far too much to use for things like correspondence). It is not my default printer in OS X, incidentally. No matter how many times I tell Pages to save the information about the printer, it will not. And I also get the same nag on the rare occasions when I do use the printer that pages has chosen (usually by mistake because I forgot to change it in the print dialog).
Perhaps this is a localization-specific bug and that's why you don't see it.
EDIT And most oddly, it happens just the same in lion with the current version of pages, which I would have thought should have autosaved that change without asking me about it.

Why am I asked to save every time I quit?

I have a project with several VI's in it.
Ex:
Init VI
Master control Panel
Test panels
I have to open them and use them periodically, however I only open them and run them, then close them.
One vi (the init VI) asks me to save everytime, however, I havn't made any changes to it. Anybody have a clue why this is happening, or how to make it stop?
-Regards
eximo
UofL Bioengineering M.S.
Neuronetrix
"I had rather be right than be president" -Henry Clay
Solved!
Go to Solution.

show changes in this dialog will let you know what has changed, could be a linking to a different subvi, could have been last saved in a different LV version, lots of things.
Why dont you just make an exe?
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA

Why does TS ask to save 'NI_Database_Types.ini' every time I quite TS?

Ever since I installed TestStand 3.5 I have been getting this. Every time I quit the TestStand application, i get a popup box that says
'The following files are modified. Check the files you wish to save before exiting. You will lose any modifications to unchecked files.' and it always lists NI_DatabaseTypes.ini as a changed file.
I don't use databases.
I don't have them enabled. I have checked 'Disable Database Logging' and all of the tabs in the Database OPtions pane are greyed out.
All I have to do to duplicate this is to start up teststand and then quit teststand. I don't even need to load a sequence file.
What can I do to stop this annoying message?
(Why can't you guys introduce a new version without introducing new errors? )

Hi,
Out of interest, what do you install first, the LabVIEW or the TestStand.
Regards
Ray Farmer
Regards
Ray Farmer

Problem with Reader file when we try to save a pdf version of filled in file.

We currently create fillable forms in Acrobat XI and enable them for fill-in with Acrobat Reader. Our end users are able to key information and save it to the enabled pdf file with Reader, but they want to create a protected version of the form so nothing can be modified once they have approved it. They have been creating "locked" pdf versions of the completed form using CutePdf software. The PDF files they are creating open fine with Acrobat Pro XI or our free FoxIT reader, but when we try to open the files they created with CutePDF with Acrobat Reader, they are quite distorted. According to users, this worked with older versions of Acrobat Reader. Please let us know if you have any suggestions (other than switching from Acrobat Reader to the free FoxIT reader.
Thanks for the help!!
Ken K. - 2191

Can't endorse FoxIt or CutePDF, since I don't use either of them, and Adobe doesn't like us endorsing thrid party products in their forums anyway. On top of that I know several people who had really bad adware experiences with FoxIt, so I'd say stay away from it.
Most likely neither of these software developers has updated THIER software to work with Acrobat/Reader XI and the problem lies with them, since PDF is an Adobe format and they must follow the lead from here, not vice-versa.

When I save a pdf from Safari 7, the file is empty

Before I upgraded to MAvericks and Safari 7 I used to be able to save pdfs to my desktop with no problem. However, when I save now, all I get is an icon. When I try to open it, I get the message that the file is empty, and sure enough when I go to info the size of the file is zero.
As far as I can tell I am doing exactly the same as I was doing before upgrading.
What is wrong? And idea how I can fix this?

Better to save files to a designated folder in the Finder then the desktop.
Desktop preferences may be corrupted.
Open the Finder. From the Finder menu bar click Go > Go to Folder
Type or copy paste the following:
~/Library/Preferences/com.apple.desktop.plist
Click Go then move the com.apple.desktop.plist file to the Trash
Try saving a PDF file.

Why I am losing aspects of the PDF after replacing pages?

Hi,
I am using Adobe Acrobat 9 Pro with Windows 7, and I want to replace certain pages in one PDF with certain pages from another PDF. The pages are replaced, but anything that was added with the typewriter is lost in the pages I'm replacing. In other words, it replaces the pages, but does not copy across the page numbers and a few other additions that I made with the typewriter. Am I doing something wrong or is the program not capable of carrying across the additions? I am desperate & would appreciate any help! Thanks.

First of all, this forum is about Adobe Reader. The Acrobat forums are located here: http://forums.adobe.com/community/acrobat
Regarding your question: Try to flatten the file before copying the pages over. Doing so makes your edits an integral part of the PDF page and should cause them to carry over.

Preview: Save as PDF while approximately keeping the file size ?

Hello!
I know that several good discussions took place about the way to reduce the file size when saving (as) a PDF from the application Preview.
I tried:
• the default poor quality "Reduce File Size" preset filter,
• the additional filters provided by Jérôme Colas (http://discussions.apple.com/thread.jspa?messageID=6250289)
• the "Compress PDF Workflow 4.0" that reenables feature for Leopard (http://www.apple.com/downloads/macosx/automator/compresspdfworkflow.html)
Has anyone come across a method to _keep in about the *original size*_ of the original Adobe PDF ?
When saving a 3 MB PDF with Preview, I see it increase to 80 MB, so that dramatically reducing it to 40MB is not really satisfying, is it?
Thank you in advance for any suggestion !

Bernd, thank you for your attempt to help but the option dialog windows do not contain the same options. There are numerous other posts on this forum about this issue and there is no answer. Clearly, there is an issue. I have submitted this issue to our internal help desk.

Why am I asked to save a PDF after only viewing a file

Similar Messages

Maybe you are looking for