FBReader2 - link - page computation - common bug

Hello,
For a very long time we maintain a FBReader fork (for a very specialized group).
We noticed a bug in the last versions of the open-sourced FBReader2 (while the bug was not there ~5 yr back, and it's not in the now closed source FBReader application on the market).
I would like to know if you know it, or if you have any investigation on it.

On big books (like the Bible, but not limited to this book), some of the intra-book links (to some other page) are processes wrong, and the app sends the user to a wrong location in the book.
I have tested also on your app, and the bug can be replicated.
To replicate it, you can try big books. E.g. Biblia from this archive: https://drive.google.com/file/d/1G2bGSxOXIUsMYJKknUfWQ1oJKn9wA0Mk/view

Not all links are computed wrong, only some. Here are few examples:

1. In the Bible, all links starting from the Acts of the Apostles 28: 4, to the Epistle to Romans 16:17, all explanatory notes lead to the page with this text: "In radacina verbului oninemi (a fi folositor) e implicat numele lui Onisim (Folositorul)".

2. Problems with the link in the application - the content from the psalms leads me to "citarea cintarilor". Browsing, I reach Psalm 116 or 117, but from the TOC, it to another section.

My repos with both very old version which always computed links ok as well as the version similar to yours which has the issue, are listed here: https://github.com/aplicatii-romanesti/imbunatatiri_si_problemele/issues/7

If you are willing to join fixing this common bug and you have any hints, please let me know.