Welcome Guest Search | Active Topics | Sign In | Register

Landscape page fields are populated in wrong orientation Options
Pejman
Posted: Thursday, December 3, 2015 6:35:47 PM
Rank: Newbie
Groups: Member

Joined: 12/3/2015
Posts: 6
Hello everyone,

i have problem with the orientation of fields populated using eopdf. I'm working for Passporthealth which has a license from you guys.

My pdf is landscape and when i use the pdfDocument to get this pdf and populate data in each field, they show up vertically in the horizontal textfield!

can anyone help me with this?
eo_support
Posted: Friday, December 4, 2015 11:53:29 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,229
Hello,

Can you send a small test project to us with your PDF file? See here for more information on how to send us test project:

http://www.essentialobjects.com/forum/test_project.aspx

Thanks!
Pejman
Posted: Monday, December 7, 2015 11:48:27 AM
Rank: Newbie
Groups: Member

Joined: 12/3/2015
Posts: 6
I have sent you the test project. Thank you.
eo_support
Posted: Monday, December 7, 2015 6:34:56 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,229
Hi,

We have looked into your test project and file. This looks like a bug with Chrome's built-in PDF viewer. Some other viewers display the file fine, this include Adobe's reader and IE's built-in PDF reader.

The root of the problem is the input field in your PDF file has a "rotate 90" attribute on it. We do not change that flag when you use EO.Pdf to fill the field. However apparently Chrome does not honor this flag when it display the value of the property. Adobe Reader on the other hand, does honor this flag correctly. Both honor this flag when entering contents as it should.

It is not possible for us to "fix" such issues from our end. If we were to make Chrome happy then Adobe would display the file wrong. Chrome might claim they are right and Adobe is wrong --- but since the PDF standard is from Adobe, it might not be a good idea to go against their implementation. As such you can report this to Chrome and see if they can fix this on their end. In the mean time you might want to avoid using vertical fields.

Thanks!
Pejman
Posted: Tuesday, December 8, 2015 10:43:50 AM
Rank: Newbie
Groups: Member

Joined: 12/3/2015
Posts: 6
But my problem is that I don't care about chrome! As i mentioned, i print this to printer by converting it directly from pdf to tiff and there is no Adobe involved to honor the rotation to fix it so whatever comes on the paper is exactly like what you see on chrome. That is why i brought up chrome for giving you an example. It would be nice to tell eopdf to do the rotation or not, you might not want to use Adobe to open this pdf and print it directly to the printer.
eo_support
Posted: Wednesday, December 9, 2015 11:30:41 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,229
Hi,

Please download the latest build from our download page and see if it resolves the issue for you. The new build contains some changes specifically for this scenario.

Thanks!
Pejman
Posted: Wednesday, December 9, 2015 3:20:43 PM
Rank: Newbie
Groups: Member

Joined: 12/3/2015
Posts: 6
i get this exception after i replaced the old EO.Pdf.dll with the new one downloaded from your site:

An unhandled exception of type 'System.IO.FileNotFoundException' occurred in EO.Pdf.dll

Additional information: Could not load file or assembly 'EO.Base, Version=15.3.43.0, Culture=neutral, PublicKeyToken=e92353a6bf73fffc' or one of its dependencies. The system cannot find the file specified.
eo_support
Posted: Wednesday, December 9, 2015 3:35:01 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,229
Hi,

You do need to reference EO.Base.dll as well. This DLL is new in EO.Pdf 2015.

Thanks!
Pejman
Posted: Wednesday, December 9, 2015 3:45:34 PM
Rank: Newbie
Groups: Member

Joined: 12/3/2015
Posts: 6
It works.

Thanks
Pejman
Posted: Thursday, December 10, 2015 12:41:35 PM
Rank: Newbie
Groups: Member

Joined: 12/3/2015
Posts: 6
Should we purchase the new license for this fix?
eo_support
Posted: Thursday, December 10, 2015 4:06:22 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,229
Hi,

It depends on what version you purchased and when you have purchased it. If the version you purchased is for 2015, then your existing license will cover this new build fine since it is the same version.

If the version you purchased is an old version, then you may or may not need to upgrade. When you purchase your original version, it automatically includes one year free upgrade. So if this build is within one year of your purchase date, then you do not need to upgrade. In that case you can just log into your account and revisit your license key page. You should see an option allowing you to download new license key for the new version.

If the new build is not the same version and it is also beyond one year, then you will need to upgrade. In that case you can log into your account, then go to "My Orders" page, then click "Renew" next to the "Subscription" column to renew your subscription to current. Once you renew your subscription to current, you will be able to downlod license key for the current version.

Thanks!


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.