Petr Olšák

Please, re-open this issue. The position of page.center is totally wrong if its calculation depends on \voffset, \hoffset. The calcuation is based on \lastxpos \lastypos of \savepos of current point...

But the linked issue is seven years not solved. And the discussion here is off topic of the core problem: not to use \hoffset and \hoffset for calculation.

Yes, I know the problem about missing information about \pdfpagewidth in dvi mode. Simply, page.center or page.east has no sense in dvi mode because we don't know \pdfpagewidth, the physical...

Please, be more clear and give an exact MWE example what "backwad compatibility" is broken. Now, the compatiblity with the manual page 262 is broken and this is more important...

If somebody needs a depenedency of the position of the result on \hoffset, \voffset then he can write `($(current page.center) + ... $)`.

The commit cdacb87 is buggy commit. The manual at page 261 says: It is the node of shape rectangle whose west anchor is left corner of the page. But is...

Note that when users are using OpTeX then this bug is much more visible because \hoffset is equal to left margin not "left margin minus 1in". Maybe in another plain...

This is not only OpTeX problem: when plain TeX sets \hoffset, \voffset to different sizes than default then the bug is shown. When a user sets \hoffset, \voffset different from...

If I understand well, you insist to the current state because of a latex package `crop.sty`. (I still waiting for MWE.) The `crurrent page` position calculation was broken by commit...

@muzimuzhi Thank you for the example. I see that there was very bad decision in 2013 because two different features (primitive feture and feature needed by crop.sty) were merged to...