Once it's merged, I'll quickly add the German translation so that everything can be rolled out at once, including my previous pull request.

Excellent work on the position list — this is exactly the right foundation. I can bring two missing pieces.

**1. The Qt API you were looking for: `QPdfEngine::drawHyperlink`**

The Qt PDF engine already supports link annotations internally via a private method:

```cpp
void QPdfEngine::drawHyperlink(const QRectF &r, const QUrl &url)
```

It is accessible (unofficially) by casting the paint engine after `diagram->render()`:

```cpp
#include <private/qpdf_p.h>

// After diagram->render(painter, ...) on each page:
if (printer->outputFormat() == QPrinter::PdfFormat) {
    auto *pdfEngine = dynamic_cast<QPdfEngine*>(painter->paintEngine());
    if (pdfEngine) {
        // painter->worldTransform() captures the scale applied by render()
        // Use it to map scene coordinates -> printer coordinates
        QTransform t = painter->worldTransform();
        for (auto &link : xrefLinksForThisPage) {
            QRectF printerRect = t.mapRect(link.sourceRect);
            QUrl   target(QString("page=%1&x=%2&y=%3")
                          .arg(link.targetPage)
                          .arg(link.targetX)
                          .arg(link.targetY));
            pdfEngine->drawHyperlink(printerRect, target);
        }
    }
}
```

This is private API (requires Qt private headers: `QT += gui-private` in .pro or `find_package(Qt6 ... PRIVATE)` in CMake), so it could theoretically change between Qt versions — but it has been present and stable since Qt 4 and is still there in Qt 6.11. QTBUG-44563 (open since 2015) tracks the request for a public API.

The `painter->worldTransform()` is the key to solving your zoom/fit_page problem: after each `diagram->render(painter, targetRect, sourceRect, Qt::KeepAspectRatio)`, the painter's world transform already encodes the exact scale and offset applied. Mapping the scene-space link rectangles through this transform gives the correct printer-space coordinates automatically.

**2. An important correctness issue: page number vs. folio label**

Using `page=N` as the link target works if folio order never changes. But QET supports two different ways to identify folios:

- `%f` — position in the tree (physical page number in the PDF). If the user reorders folios, all links break.
- `%F` — the folio label, stable regardless of position in the tree.

If users configure their XRef formulas with `%F` instead of `%f`, they expect links to follow the folio wherever it moves. A link based on `page=N` does not honour this.

The robust solution is to build a **named destination dictionary** before the print pass:
```
folio_label -> (physical_page_number, y_position)
```
Then use the label as the link target instead of the page number. Unfortunately `drawHyperlink` only accepts a `QUrl`, so named internal destinations would require writing raw PDF annotations — which means either a post-processing step (as Alfonso's Python script does) or a third-party library (libmupdf, QPDF).

For a pragmatic first implementation, `page=N` with `drawHyperlink` is a good start — it works correctly as long as the folio order at export time matches the XRef labels. Just worth documenting the limitation.

**Summary**

- `QPdfEngine::drawHyperlink` + `painter->worldTransform()` solves the injection and the coordinate scaling in one step
- Named destinations (for `%F` stability) require a post-processing pass or lib — this is a known limitation of what Qt exposes today
- Your position list code is the right foundation; the missing piece was just how to inject it

Happy to help test or integrate this if you share the patch.

Momentan wird in der projectprintwindow.cpp noch verschiedene Sachen erkannt. Ich habe euch meinen aktuellen Stand mal angehangen.
Die blauen Rechtecke sind die, die schon passend auf den Slave-Querverweisen positioniert werden.

Möglicherweise hat noch jemand von euch eine Idee.
Damit ihr euch ein Bild machen könnt, habe ich auch ein kleines Projekt angehangen, womit ich das teste.

Translate:
I'm really stuck at the moment.
It still depends on the cross-reference being attached to the component.

At the moment, various things are still being recognized in projectprintwindow.cpp. I've attached my current status for you.
The blue rectangles are the ones that are already positioned correctly on the slave cross-references.

Maybe one of you has an idea.
To give you an idea, I've also attached a small project that I'm using to test this.

Translated with DeepL.com (free version)

Wir arbeiten auf dem Skript von PLC-User weiter.

Wir haben bereits den Erfolg, dass Rote Rechtecke reingezeichnet werden.

Hierbei fällt auf, dass diese nicht richtig positioniert werden. Die landen auf dem Bauteil und nicht auf dem Verweis.

Weiß jemand, wo die Koordinaten vom den Querverweis gespeichert ist, damit man diese übernehmen kann?

Translate:
I've been working with ChatGPT for a long time and am trying to get the link to work.

We are continuing to work on the PLC-User script.

We have already succeeded in drawing red rectangles.

However, it is noticeable that these are not positioned correctly. They end up on the component and not on the reference.

Does anyone know where the coordinates of the cross-reference are stored so that they can be transferred? 

Translated with DeepL.com (free version)

Are there any further developments on this?

I would like to leave a link to the post where I share a tool that generates the links in a .pdf automatically.
https://qelectrotech.org/forum/viewtopic.php?id=2982
We have built on what has been published in this post so far, and with the help of AI we have generated the tool.

I preferred to separate the posts so as not to mix up the tools.

Hopefully this can help in the development to integrate the function into QET!

By the way: I have to take a closer look at git-branches. How to use them and so ... 

You could share a patch?

In the meantime, I have written a code that creates a position list with links and targets in the print module that can be used to insert PDF links.
I just haven't found anything in the Qt docs that explains what a link or a corresponding target should look like so that it works in the PDF file!

***** find positions for PDF-internal links...
XRef from page 3 QPoint(1380,620) to page 4 QPoint(120,440)
XRef from page 3 QPoint(1380,770) to page 4 QPoint(120,90)
XRef from page 3 QPoint(1380,640) to page 4 QPoint(120,420)
XRef from page 3 QPoint(1380,600) to page 4 QPoint(120,400)
XRef from page 3 QPoint(1380,790) to page 4 QPoint(120,110)
XRef from page 4 QPoint(120,90) to page 3 QPoint(1380,770)
XRef from page 4 QPoint(1320,90) to page 5 QPoint(120,90)
XRef from page 4 QPoint(120,110) to page 3 QPoint(1380,790)
XRef from page 4 QPoint(120,440) to page 3 QPoint(1380,620)
XRef from page 4 QPoint(1320,110) to page 5 QPoint(120,110)
XRef from page 4 QPoint(120,400) to page 3 QPoint(1380,600)
XRef from page 4 QPoint(120,420) to page 3 QPoint(1380,640)
XRef from page 5 QPoint(1380,90) to page 6 QPoint(120,90)
XRef from page 5 QPoint(120,90) to page 4 QPoint(1320,90)
XRef from page 5 QPoint(1380,110) to page 6 QPoint(120,110)
XRef from page 5 QPoint(120,110) to page 4 QPoint(1320,110)
XRef from page 6 QPoint(120,110) to page 5 QPoint(1380,110)
XRef from page 6 QPoint(1380,270) to page 8 QPoint(110,180)
XRef from page 6 QPoint(1380,440) to page 8 QPoint(110,440)
XRef from page 6 QPoint(1380,410) to page 8 QPoint(110,410)
XRef from page 6 QPoint(1380,240) to page 8 QPoint(110,210)
XRef from page 6 QPoint(120,90) to page 5 QPoint(1380,90)
XRef from page 8 QPoint(110,440) to page 6 QPoint(1380,440)
XRef from page 8 QPoint(110,180) to page 6 QPoint(1380,270)
XRef from page 8 QPoint(110,410) to page 6 QPoint(1380,410)
XRef from page 8 QPoint(110,210) to page 6 QPoint(1380,240)

There are also additional constraints such as fitting on the page or the print area. "Automagic" zoom factors are used here, which also have to be applied to the positions of the links and targets.

If you look at this post from 20. February:
https://qelectrotech.org/forum/viewtopi … 099#p21099

There should be a png as attachment, but there is only a link!
When I follow the link, it says:

Bad request. The link you followed is incorrect or outdated.

Same here with post from 10. March
https://qelectrotech.org/forum/viewtopi … 220#p21220

Bad request. The link you followed is incorrect or outdated.

But the last backup was made yesterday at 15h00, so please put again your script, many sorry.