Update 19.07.00 20190719.193727 Bug
Updated to latest version and now our forms have illegible text fields for the forms which are oriented in landscape after the forms upload from our iPads to our Cloud server. The portrait oriented forms are not having this issue. I have done quite a bit of testing and the previous Acrobat Version 19.06.02 20190719.162937 and earlier does not have this problem. We have been using these forms which I designed and coded for three years without this problem, until now, after the most recent update.
-
Hi all,
We just released Acrobat 19.08.00 to the App Store.
Acrobat 19.08.00 includes the fix for the Printing problem with distorted text in PDF forms in Landscape orientation.
Would you please update to 19.08.00 and let us know if it works for you?
Thank you for your help!
-
Michael Smith commented
Please fix!
-
Anonymous commented
Any timeline on a resolution to this problem? We produce a very large amount of reports using Adobe PDFs and this is a challenge to get the forms turned in for our Technicians. Appreciate all the assistance in getting this resolved.
Also, 'Rich' on this message board seems to be having the same issue as we are, possibly.
-
Hi,
Thank you for sharing your documents with us.
We are investigating the cause of the problem with the PDF forms in Landscape orientation.
Thank you again for your help.
-
Anonymous commented
Will attach remaining three examples, since first one went through without hanging up like they did last week.
-
Anonymous commented
Examples of original forms. Will attach one at a time, if possible, because of previous problems doing so. Two examples of Landscape forms (which have the problem with text appearing when shared flattened); two examples of Portrait oriented forms (which do not have this issue when shared flattened).
-
Anonymous commented
Last week I tried to upload the example file here as you requested, but it would not upload. I replied to your email with the example attached. Is there a better way to get this to you? Also have you identified this problem and are working on an update to correct it?