- #ADOBE READER FOR MAC OS X 10.5.8 CAUSING PROBLEMS PDF#
- #ADOBE READER FOR MAC OS X 10.5.8 CAUSING PROBLEMS FULL#
Nam in felis fringilla, dignissim metus et, tristique diam. Proin pulvinar erat elit, ac elementum ex placerat in. Vestibulum gravida aliquam tellus, pharetra semper nulla vulputate nec. Proin ac convallis libero, quis bibendum " + "Lorem ipsum dolor sit amet, consectetur adipiscing elit. TextField textField = new TextField(writer, new Rectangle(llx, lly, urx, ury), "textField") Its top edge will be directly under the label, and it will be
#ADOBE READER FOR MAC OS X 10.5.8 CAUSING PROBLEMS FULL#
It will be the full width of the document, minus a 2-point String.Format("Text Field (NeedAppearances = )", needAppearances),įontFactory.GetFont(BaseFont.HELVETICA, 10, Font.BOLD)) Create and add a label for the text field. Using (PdfWriter writer = PdfWriter.GetInstance(doc, ms)) Using (Document doc = new Document(PageSize.LETTER, marginsH, marginsH, marginsV, marginsV)) Using (MemoryStream ms = new MemoryStream()) MarginsV = Utilities.InchesToPoints(0.5f) Public static byte CreatePdf(bool needAppearances)įloat marginsH = Utilities.InchesToPoints(0.65f), OutputFilePath = Path.Combine(outputDirName, "PdfTest_NeedAppsFalse.pdf") will be slightly closer together when focused, and some lines will change their CON: The text field's appearance will change when it gains or loses focus the characters PRO: Adobe Reader won't prompt you to save changes when you close the file, unless
#ADOBE READER FOR MAC OS X 10.5.8 CAUSING PROBLEMS PDF#
Create a PDF form with NeedAppearances = false. OutputFilePath = Path.Combine(outputDirName, "PdfTest_NeedAppsTrue.pdf") CON: Adobe Reader will prompt you to save changes when you try to close the file, PRO: The text field will have a consistent appearance, whether it's focused or not. Create a PDF form with NeedAppearances = true. I'm using iTextSharp 5.5.5, but I tried upgrading to the latest version (5.5.8) and it didn't help.ĭirectory.CreateDirectory(outputDirName) My question to you is: can I get both of these advantages at once? Or do I have to resign myself to choosing one or the other?
![adobe reader for mac os x 10.5.8 causing problems adobe reader for mac os x 10.5.8 causing problems](https://i.ytimg.com/vi/1-1r3aUfMAI/maxresdefault.jpg)
![adobe reader for mac os x 10.5.8 causing problems adobe reader for mac os x 10.5.8 causing problems](https://spirebowl.weebly.com/uploads/1/2/6/6/126603080/284057974.jpg)
If I set NeedAppearances to true, I get a consistent appearance whether the field is focused or not but if I don't set NeedAppearances to true, Reader stops prompting me to save changes when I didn't make any. when a word didn't fit on a line before, but does fit when the spacing becomes narrower) when that happens, it's very noticeable, since it affects all lines that come after it. It's only narrower by a small amount, so it usually isn't that severe, but there are some cases when it causes the line wrapping positions to shift (e.g. However, the field's character spacing also changes when it gains focus, becoming slightly narrower. The most obvious change is that the contents shift downwards by a fair amount, but I can fix that by adding a top margin, using the TextField.SetExtraMargin() method. When you click a (multiline text) field to edit it, the Reader-defined appearance takes over, causing a visible change to the field's text contents. Without that flag, iTextSharp generates the form fields' appearances itself - but they only apply to the fields' default, unfocused state. Removing the NeedAppearances flag fixed this issue, but spawned a new one to take its place.
![adobe reader for mac os x 10.5.8 causing problems adobe reader for mac os x 10.5.8 causing problems](https://creativepro.com/wp-content/uploads/2009/08/save-as-adobe-pdf-options-300x124.jpg)
![adobe reader for mac os x 10.5.8 causing problems adobe reader for mac os x 10.5.8 causing problems](https://baplus.weebly.com/uploads/1/2/5/4/125463588/376631118.jpg)
Further investigation revealed the culprit: I was setting the AcroForm's NeedAppearances flag to true, which causes Reader to generate the form fields' appearances when you open the file, and then delete the NeedAppearances flag from the file - thus modifying the PDF, and prompting you to save your "changes" when you close it. I did some research, and apparently this is caused by Adobe Reader making some kind of change to the PDF file behind the scenes, either because the PDF itself is corrupted (and Reader fixes it for you) or for some other reason. However, recently my organization upgraded to Adobe Reader XI since then, the generated PDFs have started displaying a "Do you want to save changes" dialog when you open the PDF in Reader and then close it again, even if you haven't made any changes to the form. I've been generating PDF forms using iTextSharp for quite a while now, and it's been working fine.