Effect on page ranges of adding and deleting pages

[Nemo]

If you number pages with more than one page range then if you delete a page within a page range it does not affect the numbering of subsequent ranges. However if you add a page it does affect subsequent ranges.

Let me give an example. Suppose you have a 30 page document with pages numbered A1 to A10, B1 to B10, and C1 to C10.

If you delete page number A5 then the page previously numbered A6 will become the new A5, the page previously numbered A7 will become the new A6, the page previously numbered A8 will become the new A7, the page previously numbered A9 will become the new A8, and the page previously numbered A10 will become the new A9. There will be no page A10 and pages in range B1 to B10, and C1 to C10 will not be affected.

However if, instead of deleting page A5, you add a new page after A5 then the new page becomes the new A6, the old A6 becomes the new A7, the old A7 becomes the new A8, the old A8 becomes the new A9, the old A9 becomes the new A10, but the old A10 does NOT become the new A11. There is no A11. Instead the old A10 becomes the new B1 etc. so that the pages in range B1 to B10, and C1 to C10 get changed.

Can the design be altered to be consistent - i.e. if you add a page within a particular page range it should expand that range so that it does not affect subsequent ranges.

[Stefan - PDF-XChange]

Hello Nemo,

Are you speaking of "Logical page" ranges? Those that are displayed in e.g. the Thumbnails pane?
The problem with adding pages is the logic to be applied to 'border cases' - e.g. when you add a new page after A10 and before B1 - would that be A11 or should the old B1 become the new B2? So I suspect this is the main reason why our devs have left the behaviour different, but will check with them what can be done in this case!

Kind regards,
Stefan

[Nemo]

Hello Stafan,

Yes logical page ranges.

With regard to border cases, in the example you give I would say that the new page should be A11. This is consistent with the notion that existing page numbers should change as little as possible.

Kind Regards

John

[Stefan - PDF-XChange]

Hello John,

Thanks for the feedback!
I have created a ticket in our internal system for this:
#5185: Editor 338: Inconsistency in logical page number ranges updates when pages are added and deleted.
And our developers will see to get this logic corrected for a future build.

Kind regards,
Stefan

[Nemo]

Hello Stefan

Just to add an additional reason why this change is highly desirable: it is currently very difficult to insert a TOC without it messing up page ranges.

For example, if you want to have section A with page numbers A1, A2, A3 etc. and section B with page numbers B1, B2, B3 etc. then you have to work out how many pages the TOC is going to take up, and then initially set the section page numbers adrift by that amount. I.E. you have to set the third page in section A to A1, the fourth page to A2 etc. so that when you insert a two page TOC they adjust to be correct.

[Stefan - PDF-XChange]

Hello Nemo, John,

Just an update that this ticket has now been marked as resolved.
The new logic will be available in V9 of our products planned for release this autumn.

Kind regards,
Stefan

[Nemo]

That is good news. Do you know when in the autumn? Will there be a Beta release?

[Stefan - PDF-XChange]

Hello Nemo,

It should be very soon, and probably before the end of October, but for now I do not have the exact date.

Kind regards,
Stefan

[CivilEngineer]

Hello Stefan,

that's very good to hear, that the problem will be fixed in the next release. I'm waiting for this a lot and was always disappointed when I didn't find it in the changelog of the last few updates.

So I'm looking forward for the release of version 9! Is there any news about the timing?

[Daniel - PDF-XChange]

Hi, CivilEngineer

V9 is now slated to be an Early January release, but I do not have a specific date available.

Kind regards,