GoTo X,Y coordinates aren't converted when cropping with "Adjust page size" and "Normalize Media box" options enabled

[rakunavi]

Hello all,

I have noticed that when X,Y coordinates are set as the destination of a GoTo action, the coordinates set in the Action are not converted as intended when the following two options are both enabled in the Crop Pages dialog and then cropping is executed.

• Adjust the page size to match the cropped area
• Normalize Media Box to start from (0;0)

• figure.png

In the video, the following three cases are examined with the "Adjust the page size to match the cropped area" option enabled. The same sample file is copied and displayed in multiple tabs for easy understanding, and verified in turn.

1. Crop with "Normalize Media Box to start from (0;0)" option Disabled
2. Crop with "Normalize Media Box to start from (0;0)" option Enabled
3. Crop with "Normalize Media Box to start from (0;0)" option Disabled and then run Normailze Pages

In each case, first click on the bookmark to check the preset destination location, then use the Crop Pages dialog to crop the page (in case (C), also perform Normalize Pages), and click on the bookmark again to see if the destination location has changed.

For (A) and (C), the bookmark destination still shows the correct location after cropping, but not for (B). Until now I had assumed that operations (B) and (C) would produce nearly identical results, but apparently not. The video shows the case of a bookmark, but the same result is obtained in the case of a link.

• Animation.gif

• sample.zip

For reference, the bookmarks in the original sample file and the file after the operation are as follows. Each was output using the "Export Bookmark(s) to Text File" feature.

• Original sample file
  PDF-XChange Editor; goto:{1; XYZ; 8; 192.315; 571.577; 4.000}
• After processing (A) "Crop with "Normalize Media Box to start from (0;0)" option Disabled"
  PDF-XChange Editor; goto:{1; XYZ; 8; 192.315; 571.577; 4.000}
• After processing (B) "Crop with "Normalize Media Box to start from (0;0)" option Enabled"
  PDF-XChange Editor; goto:{1; XYZ; 8; 192.315; 571.577; 4.000}
• After processing (C) "Crop with "Normalize Media Box to start from (0;0)" option Disabled and then run Normailze Pages"
  PDF-XChange Editor; goto:{1; XYZ; 8; 92.315; 471.577; 4.000}

The Resize Pages feature can be used in a similar way to the Crop Pages feature, but if the "Normalize Media Box to start from (0;0)" option is enabed in the Resize Pages dialog, the exact same issue described above occurs.

• figure2.png
  
  
  Animation2.gif

Hoping that the above information will be of some help to you.
Thank you so much for your continued support.

Best regards,
rakunavi

- PDF-XChange Editor Plus Version: 10.3.1 build 387
- OS Version: Windows 11 Home 23H2 Build 22631.3880
- PC Model: Lenovo IdeaPad C340-15IWL, HP All-in-One 22-c0xx

[Daniel - PDF-XChange]

Hello, rakunavi

Thank you for the reports, I have reproduced these and passed them along to the Dev team.

RT#7050: Bug: Crop/resize pages normalize media box does not update actions

Kind regards,

[rakunavi]

Hello Daniel, thank you for contacting developers.

I am relieved to share my situation with you.
Please give my best regards to the developers.

Best regards,
rakunavi

[Daniel - PDF-XChange]

[rakunavi]

Hello Tracker Support,

Congratulations on the release of build 388. Now, the version history mentions that the following issue has been fixed.

• Build 10.4.0.388 Bugfixes and Improvements
  Fixed an issue where the Crop Pages feature did not normalize the action's data. (T# 7050) (43428)

The Resize Pages feature can be used in a similar way to the Crop Pages feature, but if the "Normalize Media Box to start from (0;0)" option is enabed in the Resize Pages dialog, the exact same issue described above occurs.

The issue with the Crop Pages dialog has indeed been fixed, but the same issue reported later in the topic with the Resize Pages dialog persists in build 388. I am aware that this continues to be a problem, but has the development team concluded that this was not a problem? Or is it simply not fixed yet? I would appreciate it if you could look into this.

• Animation.gif

Best regards,
rakunavi

[Daniel - PDF-XChange]

Hello, rakunavi

Thank you for the report, I see the same here and have passed it up the chain for a review. I expect this was a case of something being overlooked, as there are no notes about a technical reason for there not being a change. If I hear back from the Dev team saying otherwise, I will let you know.

Kind regards,

[rakunavi]

Hello Daniel, thank you for contacting developers.

Thank you for taking time out of your busy schedule.
Please give my best regards to developers.

Best regards,
rakunavi

[Stefan - PDF-XChange]