From 60d9299d458aec2ebf22cb38593d38792076c3c4 Mon Sep 17 00:00:00 2001
From: Andre Rummler <andre.rummler@cern.ch>
Date: Tue, 15 Sep 2026 23:23:32 +0200
Subject: [PATCH] New installation instructions for Qt6/CMake. Proposal:
 translations as INSTALL_XY.md

---
 INSTALL    | 179 ---------------------------
 INSTALL.md | 349 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 README     |  30 ++---
 README.md  | 102 ++++++++--------
 4 files changed, 415 insertions(+), 245 deletions(-)
 delete mode 100644 INSTALL
 create mode 100644 INSTALL.md

diff --git a/INSTALL b/INSTALL
deleted file mode 100644
index 04817c0cf..000000000
--- a/INSTALL
+++ /dev/null
@@ -1,179 +0,0 @@
-[Qt6 / CMake]
-Building the Qt6 line with CMake additionally requires the private
-development headers of QtGui. On Debian/Ubuntu these live in a separate
-package that is NOT pulled in by qt6-base-dev:
-
-    apt install qt6-base-private-dev
-
-(other distributions: install your Qt 6 "private headers" development
-package, e.g. qt6-qtbase-private-devel on Fedora)
-
-QET needs the private QtGui API (QPdfEngine) for clickable hyperlinks in
-the PDF export. Without the package, find_package(Qt6 ... GuiPrivate)
-succeeds but CMake later fails at generate time with:
-"Imported target Qt6::GuiPrivate includes non-existent path".
-
-[ca]
-Dependències:
-libQt5 (paquets libqt5*)
-cupsys-bsd per imprimir
-
-Com compilar:
-$ qmake (qmake-qt5 pels sistemes basats en Debian)
-$ make
-# umask 0022
-# make install
-
-[en]
-Requirements :
-libQt5 (see packages libqt5*)
-cupsys-bsd for printing
-
-Howto compile :
-$ qmake (qmake-qt5 for Debian-based systems)
-$ make
-# umask 0022
-# make install
-
-[fr]
-Pré-requis :
-libQt5 (paquets libqt5*)
-cupsys-bsd pour l'impression
-
-Comment compiler :
-$ qmake (qmake-qt5 pour les systèmes basés sur Debian)
-$ make
-# umask 0022
-# make install
-
-[de]
-Abhängigkeiten:
-libQt5 (Pakete libqt5*)
-cupsys-bsd zum Drucken
-
-Kompilieren:
-$ qmake (qmake-qt5 für Debian-basierende Systeme)
-$ make
-# umask 0022
-# make install
-
-[ru]
-Зависимости:
-libQt5 (пакет libqt5*)
-cupsys-bsd для печати
-
-Как компилировать?:
-$ qmake (qmake-qt5 для систем основанных на Debian)
-$ make
-# umask 0022
-# make install
-
-[pt]
-Dependências:
-libQt5 (ver pacotes libqt5*)
-cupsys-bsd para impressão
-
-Como compilar:
-$ qmake (qmake-qt5 para sistemas baseados em Debian)
-$ make
-# umask 0022
-# make install
-
-[es]
-Dependencias:
-libQt5 (paquetes libqt5*)
-cupsys-bsd para imprimir
-
-Cómo compilar:
-$ qmake (qmake-qt5 para los sistemas basados en Debian)
-$ make
-# umask 0022
-# make install
-
-[cs]
-Požadavky :
-libQt5 (viz balíček libqt5*)
-cupsys-bsd kvůli tisku
-
-Jak program sestavit :
-$ qmake (qmake-qt5 u systémů založených na Debianu)
-$ make
-# umask 0022
-# make install
-
-[pl]
-Zależności:
-libQt5 (pakiety libqt5 *)
-cupsys-bsd do druku
-
-Sposób kompilacji:
-$ qmake (qmake-qt5 dla systemów opartych na Debianie)
-$ make
-# umask 0022
-# make install
-
-[it]
-Dipendenze:
-libQt5 (vedi pacchetti libqt5*)
-cupsys-bsd per la stampa
-
-Come compilare:
-$ qmake (qmake-qt5 per sistemi basati su Debian)
-$ make
-# umask 0022
-# make install
-
-[el]
-Απαιτήσεις:
-libQt5 (δείτε για πακέτα libqt5*)
-cupsys-bsd για εκτύπωση
-
-Πως να το μεταγλωττίσετε:
-$ qmake (qmake-qt5 για συστήματα βασισμένα σε Debian)
-$ make
-# umask 0022
-# make install
-
-[nl]
-vereisten:
-libqt5 (zie pakketten libqt5 *)
-cupsys-bsd om af te drukken  
-
-Hoe te compileren:
-     $ Qmake (qmake-qt5 voor Debian-gebaseerde systemen)
-     $ make
-     # Umask 0022
-     # Make install
-
-[be]
-Vereisten:
-libQt5 (pakketten libqt5*)
-cupsys-bsd voor het afdrukken
-
-Hoe te compileren :
-$ qmake (qmake-qt5 voor systemen op basis van Debian)
-$ make
-# umask 0022
-# make install
-
-[da]
-Krav:
-libQt5 (se pakke libqt5*)
-cupsys-bsd til udskrivning
-
-Hvordan man kompilerer:
-$ qmake (qmake-qt5 for Debian baserede systemer)
-$ make
-# umask 0022
-# make install
-
-[ja]
-必要条件 :
-libQt5 (パッケージ libqt5* を参照)
-cupsys-bsd 印刷用
-
-コンパイルの方法 :
-$ qmake (Debian ベースのシステムでは qmake-qt5)
-$ make
-# umask 0022
-# make install
diff --git a/INSTALL.md b/INSTALL.md
new file mode 100644
index 000000000..44d37d05a
--- /dev/null
+++ b/INSTALL.md
@@ -0,0 +1,349 @@
+# Building QElectroTech from source
+
+QElectroTech is built with **CMake** and requires the  **current Qt6 only**; Qt5 and the
+old `qmake`-based build described in earlier versions of this file have
+been retired.
+
+## 1. Getting the source
+
+QET uses git submodules, so clone recursively:
+
+```sh
+git clone --recursive https://github.com/qelectrotech/qelectrotech-source-mirror.git
+cd qelectrotech-source-mirror
+```
+
+If you already have a non-recursive clone:
+
+```sh
+git submodule update --init --recursive
+```
+
+## 2. Requirements
+
+| Component | Status | Notes |
+|---|---|---|
+| CMake ≥ 3.5 | required | CMake 4.3+ is also fine, see note below |
+| C++17 compiler | required | GCC or Clang on Unix-like platforms; MSVC or MinGW-w64 g++ on Windows — see [Choosing a compiler](#3-choosing-a-compiler-unix) / [Building on Windows](#6-building-on-windows-msvc--mingw) |
+| Qt6 base + widgets | required | |
+| Qt6 **GuiPrivate** headers | required | needed for clickable PDF hyperlinks; **hard build failure** at CMake generate time if missing, see below |
+| SQLite3 | required | used by the nomenclature/summary database |
+| Qt Linguist tools (`lrelease`) | required | compiles the tracked `.ts` files into `.qm` as part of every normal build |
+| pugixml | handled automatically | fetched and built via CMake FetchContent if not already present on the system — see [pugixml](#8-pugixml) below |
+| Qt Test module | required if building tests | `PACKAGE_TESTS` is `ON` by default; QtTest ships as part of the base Qt6 dev packages listed below on every platform, no extra package needed |
+| KDE Frameworks (KF6) | optional | see [Building without KDE Frameworks](#9-building-without-kde-frameworks) |
+| QtPdf module | optional | see [PDF page import](#7-pdf-page-import-qtpdf) |
+
+A note on CMake versions: the project declares a minimum of 3.5 but is
+routinely built with much newer releases; if your CMake is older than 4.3 it
+simply won't have the newer `SQLite3::SQLite3` target name, which the build
+script compensates for automatically. There is nothing you need to do either
+way.
+
+## 3. Building (out-of-source build)
+
+Always build in a separate directory from the source tree — in-source builds
+are not supported.
+
+```sh
+mkdir build
+cd build
+cmake ..
+cmake --build . --parallel
+```
+
+For a Unix-like platform you'll usually also want an explicit build type,
+since CMake's default (empty) build type means no optimization and no
+debug info either:
+
+```sh
+cmake .. -DCMAKE_BUILD_TYPE=Release
+```
+
+To install (default prefix is `/usr/local`; adjust with
+`-DCMAKE_INSTALL_PREFIX=...` at the configure step if needed):
+
+```sh
+sudo cmake --install .
+```
+
+Useful configure-time options (pass as `-D<OPTION>=ON/OFF`):
+
+| Option | Default | Effect |
+|---|---|---|
+| `PACKAGE_TESTS` | `ON` | build the test suite (needs the Qt Test module) |
+| `BUILD_WITH_KF` | distro-dependent | build against KDE Frameworks; see below |
+| `QET_ENABLE_PCH` | `OFF` | precompiled headers for faster rebuilds (needs CMake ≥ 3.16) |
+
+## 3.1 Choosing a compiler (Unix)
+
+Both **GCC** and **Clang** are supported on Unix-like platforms; any
+reasonably recent release with solid C++17 support works. Neither is
+hard-coded — CMake picks up whichever `cc`/`c++` (or `CC`/`CXX` environment
+variables) resolve to by default, and you can force one explicitly at
+configure time:
+
+```sh
+cmake .. -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++
+# or
+cmake .. -DCMAKE_C_COMPILER=gcc   -DCMAKE_CXX_COMPILER=g++
+```
+
+or equivalently, by exporting `CC`/`CXX` before calling `cmake`. The
+per-distro package lists below install GCC by default (via
+`build-essential`/`gcc-c++`/the base toolchain); see each section for the
+Clang alternative.
+
+## 4. Distribution packages
+
+Exact package names vary by release/branch; if a name below doesn't resolve,
+search your package manager (`apt search`, `pkg search`, `brew search`) for
+the closest match.
+
+### Debian / Ubuntu
+
+```sh
+sudo apt install \
+    build-essential cmake ninja-build git \
+    qt6-base-dev qt6-base-private-dev qt6-tools-dev qt6-tools-dev-tools \
+    libsqlite3-dev \
+    libkf6coreaddons-dev libkf6widgetsaddons-dev
+```
+
+`qt6-base-private-dev` is **not** pulled in automatically by `qt6-base-dev`
+but is mandatory for the build (see
+[Qt6 private headers](#6-qt6-private-headers-mandatory) below).
+
+For Clang instead of GCC:
+
+```sh
+sudo apt install clang
+```
+
+Optional, for PDF page import:
+
+```sh
+sudo apt install libqt6pdf6-dev
+```
+
+Optional, to use a system pugixml instead of letting CMake fetch it:
+
+```sh
+sudo apt install libpugixml-dev
+```
+
+### Fedora / RHEL
+
+```sh
+sudo dnf install \
+    cmake gcc-c++ git \
+    qt6-qtbase-devel qt6-qtbase-private-devel qt6-qttools-devel \
+    sqlite-devel \
+    kf6-kcoreaddons-devel kf6-kwidgetsaddons-devel
+```
+
+For Clang instead of GCC: `sudo dnf install clang`.
+
+Optional, for PDF page import: `qt6-qtwebengine-devel` provides `QtPdf` on
+some Fedora releases — check `dnf provides '*/QPdfDocument'` if unsure.
+
+Optional, for a system pugixml: `sudo dnf install pugixml-devel`.
+
+### FreeBSD
+
+```sh
+pkg install \
+    cmake git \
+    qt6-base qt6-tools \
+    sqlite3 \
+    kf6-kcoreaddons kf6-kwidgetsaddons
+```
+
+(from ports: `devel/qt6-base`, `devel/qt6-tools`, `databases/sqlite3`,
+`devel/kf6-kcoreaddons`, `x11-toolkits/kf6-kwidgetsaddons`.) Qt6's
+`GuiPrivate` headers ship as part of `qt6-base` on FreeBSD, no separate
+package is needed. `QtPdf` is not packaged on FreeBSD at the time of writing
+— PDF page import will simply be disabled (see below).
+
+Clang is the FreeBSD base system compiler and needs nothing extra; GCC is
+available via `pkg install gcc` if you'd rather use it.
+
+Optional, for a system pugixml: `pkg install pugixml` (`devel/pugixml`).
+
+### macOS
+
+Using [Homebrew](https://brew.sh):
+
+```sh
+brew install cmake qt sqlite ninja
+```
+
+Homebrew's `qt` formula is Qt6 and includes the private headers, so no
+extra package is required there. KDE Frameworks are not practically
+available via Homebrew, so macOS builds are normally done **without KF**
+(`-DBUILD_WITH_KF=OFF`) — see the caveat below.
+
+Apple's Clang (from the Xcode Command Line Tools, `xcode-select --install`)
+is the default and needs no extra package; GCC is available via
+`brew install gcc` if you specifically want it instead.
+
+Optional, for a system pugixml: `brew install pugixml`.
+
+### Windows
+
+See [Building on Windows](#6-building-on-windows-msvc--mingw) below — the
+package sources differ enough from the Unix-like platforms above (no system
+package manager, SQLite3 and Qt aren't provided the same way) that it gets
+its own section.
+
+## 5. pugixml
+
+QET links against [pugixml](https://pugixml.org) for XML parsing.
+`cmake/fetch_pugixml.cmake` handles this automatically: if a suitable
+pugixml isn't already available on the system, CMake fetches and builds it
+from source via `FetchContent` as part of the normal configure step — you
+don't need to do anything to get a working build.
+
+If you'd rather avoid that network fetch and use your distribution's own
+pugixml package instead, install it before running `cmake ..` (package
+names are listed per platform in the [Distribution
+packages](#4-distribution-packages) section above — e.g. `libpugixml-dev`
+on Debian/Ubuntu, `pugixml-devel` on Fedora).
+
+## 6. Building on Windows (MSVC / MinGW)
+
+Both toolchains QET's CMake build targets on Windows are covered here:
+**MSVC** (Visual Studio 2019/2022) and **MinGW-w64** (gcc). Unlike the
+Unix-like platforms above, there's no single system package manager, so
+Qt, SQLite3 and (optionally) KDE Frameworks each need to be sourced
+separately per toolchain.
+
+One piece of good news either way: unlike Debian/Fedora, the official Qt
+Windows kits (both MSVC and MinGW) **already include the GuiPrivate private
+headers** — there's no separate "private headers" package to remember on
+Windows (see [Qt6 private headers](#7-qt6-private-headers-mandatory) below
+for why this matters).
+
+`QtPdf` is available as an optional component in the Qt Online Installer
+(look for "Qt PDF" under the Qt 6.4+ node); if you skip it, PDF page import
+is silently disabled exactly as on the other platforms. KDE Frameworks are
+not prebuilt for Windows by any of the routes below, so Windows builds
+normally use `-DBUILD_WITH_KF=OFF` (see the
+[autosave caveat](#9-building-without-kde-frameworks)).
+
+### MSVC (Visual Studio 2019 / 2022)
+
+1. Install Visual Studio with the "Desktop development with C++" workload,
+   and install Qt6 for MSVC (e.g. the `msvc2019_64` or `msvc2022_64` kit)
+   via the [Qt Online Installer](https://www.qt.io/download-qt-installer).
+2. Get SQLite3 — the simplest route is [vcpkg](https://vcpkg.io):
+   ```bat
+   vcpkg install sqlite3:x64-windows
+   ```
+3. Configure and build from an "x64 Native Tools Command Prompt for VS":
+   ```bat
+   mkdir build && cd build
+   cmake .. -G "Visual Studio 17 2022" -A x64 ^
+       -DCMAKE_PREFIX_PATH="C:\Qt\6.x.x\msvc2022_64" ^
+       -DCMAKE_TOOLCHAIN_FILE="C:\vcpkg\scripts\buildsystems\vcpkg.cmake" ^
+       -DBUILD_WITH_KF=OFF
+   cmake --build . --config Release --parallel
+   ```
+   Ninja works too, in place of the Visual Studio generator, if you prefer
+   (`-G Ninja -DCMAKE_BUILD_TYPE=Release`, run from the same VS developer
+   prompt so `cl.exe` is on `PATH`).
+
+### MinGW-w64 (gcc)
+
+Two common ways to get a MinGW toolchain that matches a Qt6 MinGW kit: Qt's
+own bundled MinGW (installed alongside a `mingw_64` Qt kit via the Qt
+Online Installer), or [MSYS2](https://www.msys2.org).
+
+Using MSYS2, from a **MINGW64** shell:
+```sh
+pacman -S --needed \
+    mingw-w64-x86_64-toolchain \
+    mingw-w64-x86_64-qt6-base mingw-w64-x86_64-qt6-tools \
+    mingw-w64-x86_64-cmake mingw-w64-x86_64-ninja \
+    mingw-w64-x86_64-sqlite3
+
+mkdir build && cd build
+cmake .. -G Ninja -DBUILD_WITH_KF=OFF -DCMAKE_BUILD_TYPE=Release
+cmake --build .
+```
+(KF6 isn't packaged in MSYS2 either, hence `-DBUILD_WITH_KF=OFF` again.)
+
+Using the Qt Online Installer's bundled MinGW kit instead: point
+`CMAKE_PREFIX_PATH` at that kit (e.g. `C:\Qt\6.x.x\mingw_64`) and make sure
+its bundled `g++.exe` comes first on `PATH`, or pass
+`-DCMAKE_C_COMPILER`/`-DCMAKE_CXX_COMPILER` explicitly so CMake doesn't pick
+up a different MinGW installation. SQLite3 still has to come from elsewhere
+in this path — vcpkg with a `mingw`-flavoured triplet, or MSYS2's package as
+above.
+
+## 7. Qt6 private headers (mandatory)
+
+QET uses the private `QPdfEngine` API (`<private/qpdf_p.h>`) to produce
+clickable hyperlinks in PDF export. This requires Qt's `GuiPrivate` target,
+which on several distributions (notably Debian/Ubuntu) is shipped in a
+separate "private headers" package rather than the normal `-dev` package —
+e.g. `qt6-base-private-dev` on Debian/Ubuntu, or
+`qt6-qtbase-private-devel` on Fedora. Without it, CMake's `find_package`
+step succeeds but configuration later fails at generate time with:
+
+```
+Imported target "Qt6::GuiPrivate" includes non-existent path
+```
+
+If you hit this, install your distribution's Qt6 private-headers package
+(on Windows this is a non-issue — see [Building on
+Windows](#6-building-on-windows-msvc--mingw) above).
+
+## 8. PDF page import (QtPdf)
+
+The toolbar's "Add a PDF" feature (`QPdfDocument::pagePointSize()`) needs
+the separate `QtPdf` Qt module, available since Qt 6.4.
+
+**This is optional and soft-fails**: if `QtPdf` isn't found, or is present
+but older than 6.4, CMake prints a status message and simply disables the
+feature (`QET_HAS_QTPDF` stays `FALSE`) — it does **not** stop the build.
+Some Qt6 distributions don't ship `QtPdf` at all (it lives outside Qt's
+core module set, alongside QtWebEngine), so this is expected on several
+platforms, including FreeBSD as of this writing.
+
+## 9. Building without KDE Frameworks
+
+`BUILD_WITH_KF=OFF` builds QET against a bundled fallback UI layer instead
+of KDE Frameworks (`kcoreaddons`/`kwidgetsaddons`). This is a fully
+supported configuration and is, in practice, the default on platforms where
+KF6 isn't readily packaged (macOS and Windows in particular).
+
+Almost everything works identically either way. The one known caveat:
+**autosave behavior is not as polished without KF**, since QET relies on
+KCoreAddons' autosave/backup-file handling when it's available. Expect
+autosave to work, but less robustly than on a KF-enabled build.
+
+## 10. Translations (developer operation)
+
+Everything in this section is a **maintainer/translator task**, not
+something a normal build or a packager needs to touch.
+
+The `.qm` files shipped with the application are compiled from the tracked
+`.ts` files automatically as part of every normal build (via `lrelease`) —
+regular builds and packages get up-to-date translated UI strings for free,
+with no developer action needed.
+
+Refreshing the `.ts` files themselves from the source code (`lupdate`) is
+the actual developer operation: it's exposed as its own opt-in build
+target, separate from the normal build:
+
+```sh
+cmake --build . --target update_translations
+```
+
+This is **not** run automatically and should not be added to routine or
+parallel CI builds: it rewrites the tracked `.ts` files as a side effect,
+and running it concurrently with the normal `lrelease` compilation step (as
+would happen under `-j`/parallel builds) can corrupt a `.ts` file mid-write,
+causing `lrelease` to fail with "Premature end of document". Run it on its
+own, review the diff, and commit the updated `.ts` files separately.
diff --git a/README b/README
index d35aac646..006477258 100644
--- a/README
+++ b/README
@@ -1,60 +1,60 @@
 [ca]
-QElectroTech és una aplicació Qt5 per crear esquemes elèctrics.
+QElectroTech és una aplicació Qt6 per crear esquemes elèctrics.
 QET utilitza el format XML per als seus elements i esquemes i inclou un editor d'esquemes, un editor d'elements i un editor de caixetins.
 
 [en]
-QElectroTech is a Qt5 application to design electric diagrams.
+QElectroTech is a Qt6 application to design electric diagrams.
 It uses XML files for elements and diagrams, and includes both a diagram editor, a element editor, and an titleblock editor.
 
 [fr]
-QElectroTech est une application Qt5 pour réaliser des schémas électriques.
+QElectroTech est une application Qt6 pour réaliser des schémas électriques.
 QET utilise le format XML pour ses éléments et ses schémas et inclut un éditeur de schémas, un éditeur d'élément, ainsi qu'un editeur de cartouche.
 
 [de]
-QElectroTech ist eine Qt5 Software, um Schaltpläne zu erstellen.
+QElectroTech ist eine Qt6 Software, um Schaltpläne zu erstellen.
 QET benutzt das XML Format für seine Bauteile und seine Projekte, und beinhaltet einen Schaltplaneditor, einen Bauteileditor sowie einen Schriftfeldeditor.
 
 
 [ru]
-QElectroTech - приложение написанное на Qt5 и предназначенное для разработки электрических схем.
+QElectroTech - приложение написанное на Qt6 и предназначенное для разработки электрических схем.
 Оно использует XML-файлы для элементов и схем, и включает, как редактор схем, так и редактор элементов.
 
 [pt]
-QElectroTech é uma aplicação baseada em Qt5 para desenhar esquemas eléctricos.
+QElectroTech é uma aplicação baseada em Qt6 para desenhar esquemas eléctricos.
 QET utiliza ficheiros XML para os elementos e para os esquemas e inclui um editor de esquemas e um editor de elementos.
 
 [es]
-QElectroTech es una aplicación Qt5 para diseñar esquemas eléctricos.
+QElectroTech es una aplicación Qt6 para diseñar esquemas eléctricos.
 Utiliza archivos XML para los elementos y esquemas, e incluye un editor de esquemas y un editor de elementos.
 
 [cs]
-QElectroTech je aplikací Qt5 určenou pro návrh nákresů elektrických obvodů.
+QElectroTech je aplikací Qt6 určenou pro návrh nákresů elektrických obvodů.
 Pro prvky a nákresy používá soubory XML, a zahrnuje v sobě jak editor nákresů, tak editor prvků.
 
 [pl]
-QElectroTech to aplikacja napisana w Qt5, przeznaczona do tworzenia schematów elektrycznych.
+QElectroTech to aplikacja napisana w Qt6, przeznaczona do tworzenia schematów elektrycznych.
 Wykorzystuje XML do zapisywania plików elementów i projektów. Posiada edytor schematów i elementów.
 
 [it]
-QElectroTech è una applicazione fatta in Qt5 per disegnare schemi elettrici.
+QElectroTech è una applicazione fatta in Qt6 per disegnare schemi elettrici.
 QET usa il formato XML per i suoi elementi e schemi, includendo anche un editor per gli stessi.
 
 [el]
-Το QElectroTech είναι μια εφαρμογή Qt5 για σχεδίαση ηλεκτρικών διαγραμμάτων.
+Το QElectroTech είναι μια εφαρμογή Qt6 για σχεδίαση ηλεκτρικών διαγραμμάτων.
 Χρησιμοποιεί αρχεία XML για στοιχεία και διαγράμματα, και περιλαμβάνει επεξεργαστή διαγραμμάτων καθώς και επεξεργαστή στοιχείων.
 
 [nl]
-QElectroTech is een Qt5 applicatie om elektrische schema's te ontwerpen.
+QElectroTech is een Qt6 applicatie om elektrische schema's te ontwerpen.
 Het maakt gebruik van XML-bestanden voor elementen en diagrammen, en omvat zowel een diagram bewerker, een element bewerker, en een bloksjabloon bewerker.
 
 [be]
-QElectroTech is een Qt5 toepassing voor het maken en beheren van elektrische schema's.
+QElectroTech is een Qt6 toepassing voor het maken en beheren van elektrische schema's.
 QET gebruikt XML voor de elementen en schema's en omvat een schematische editor, itemeditor, en een titel sjabloon editor.
 
 [da]
-QElectroTech er et Qt5 program til at redigere elektriske diagrammer.
+QElectroTech er et Qt6 program til at redigere elektriske diagrammer.
 Det bruger XML filer for symboler og diagrammer og inkluderer diagram, symbol og titelblok redigering.
 
 [ja]
-QElectroTech は電気回路図を作成する Qt5 アプリケーションです。
+QElectroTech は電気回路図を作成する Qt6 アプリケーションです。
 QET は要素と回路図に XML 形式を利用し、回路図エディタ、要素エディタ、表題欄エディタを含みます。
diff --git a/README.md b/README.md
index 7a398c5ea..bbd246ca6 100644
--- a/README.md
+++ b/README.md
@@ -5,9 +5,9 @@
 
 ### What it is
 
-QElectroTech, or QET in short, is a libre and open source desktop application to create diagrams and schematics.  
-The software is primarily intended to create electrical documentation but it can also be used to draw any kinds of diagrams, such as those made in pneumatics, hydraulics, process industries, electronics...  
-Generally speaking, QET is a **CAD/CAE editor focusing on schematics drawing features**.  
+QElectroTech, or QET in short, is a libre and open source desktop application to create diagrams and schematics.
+The software is primarily intended to create electrical documentation but it can also be used to draw any kinds of diagrams, such as those made in pneumatics, hydraulics, process industries, electronics...
+Generally speaking, QET is a **CAD/CAE editor focusing on schematics drawing features**.
 
 This means that there are no embedded simulating or calculating functionalities and it is not planned to implement them.
 
@@ -24,7 +24,7 @@ Users who want to test and take benefits from the last software implementations
 
 ### License
 
-The software is licensed under [GNU/GPL](https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html).  
+The software is licensed under [GNU/GPL](https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html).
 You are free to use, copy, modify and redistribute it under the terms of the license.
 
 Like many other open source software, QElectroTech is provided as is, without any warranty.
@@ -40,13 +40,13 @@ git clone --recursive https://github.com/qelectrotech/qelectrotech-source-mirror
 Here are the technical choices made for the software development:
 
 *   Integrated development environment: [Qt Framework](https://www.qt.io/ide/)
-*   Libraries: Qt 5.x
-*   [KF5 Framework](https://github.com/KDE)  
-    [Cmake](https://cmake.org/install/)   
-    [kcoreaddons](https://github.com/KDE/kcoreaddons/tree/kf5)   
-    [kwidgetsaddons](https://github.com/KDE/kwidgetsaddons/tree/kf5).  
+*   Libraries: Qt 6.x
+*   [KF6 Framework](https://github.com/KDE)
+    [Cmake](https://cmake.org/install/)
+    [kcoreaddons](https://github.com/KDE/kcoreaddons/tree/kf6)
+    [kwidgetsaddons](https://github.com/KDE/kwidgetsaddons/tree/kf6).
 *   Coding language: [C++](https://en.wikipedia.org/wiki/C%2B%2B)
-*   GUI translations: [Qt Linguist](http://doc.qt.io/qt-5/qtlinguist-index.html)
+*   GUI translations: [Qt Linguist](http://doc.qt.io/qt-6/qtlinguist-index.html)
 *   Version control: [GIT](https://github.com/qelectrotech/qelectrotech-source-mirror.git)
 *   Doxygen documentation :[Doxygen](https://download.qelectrotech.org/qet/doxygen/html/)
 *   QtCreator qch doxygen :[QElectroTech.qch](https://download.qelectrotech.org/qet/doxygen/QElectroTech.qch)
@@ -62,20 +62,20 @@ If you wish to be informed of the latest developments, browse the [archive](http
 
 # Features
 
-QElectroTech is a free and open source software.  
-No need to worry about restrictive licensing, privacy violation or dependency on a company.  
-Zero cost and no licensing fees!  
+QElectroTech is a free and open source software.
+No need to worry about restrictive licensing, privacy violation or dependency on a company.
+Zero cost and no licensing fees!
 But you are welcome to make a donation to support the development
 
-QElectroTech runs on the 3 most widespread operating systems for desktop computers in the world.  
-Files that were created on an OS can be edited on another OS without any conversion or restriction.  
+QElectroTech runs on the 3 most widespread operating systems for desktop computers in the world.
+Files that were created on an OS can be edited on another OS without any conversion or restriction.
 MS Windows users can even run the "ready-to-use" version of QElectroTech from an external medium with no need to install it on an access restricted computer.
 
 
 Take advantage of the modern GUI
 
-Toolbars and panels can be enabled/disabled, moved and displayed the way you want to work.  
-Panels can be stacked on each other (as tabs) or docked on the sides (as docks) or completely separated from the main window (as windows).  
+Toolbars and panels can be enabled/disabled, moved and displayed the way you want to work.
+Panels can be stacked on each other (as tabs) or docked on the sides (as docks) or completely separated from the main window (as windows).
 The GUI can fit to small or big screens, and even to multi-display configurations.
 ![](https://download.qelectrotech.org/qet/images-features/0030.png "GUI overview")
 
@@ -86,31 +86,31 @@ You only need to restart the application for the new selected language to take e
 
 Create technical documentation in professional quality
 
-Size, look and informations of the folios (sheets) are fully configurable.  
+Size, look and informations of the folios (sheets) are fully configurable.
 You can set vertical and horizontal headers (printed rulers) individually on and off, set number of columns and rows, and set width/height of each column/row.
 
-Titlebocks can be created and edited with the embedded titleblock editor to perfectly suit your needs.  
+Titlebocks can be created and edited with the embedded titleblock editor to perfectly suit your needs.
 Custom variables can be defined to display the informations you wish in the titleblock.
 ![](https://download.qelectrotech.org/qet/images-features/0055.png "Titleblock editor")
 
-With only 2 mouse clicks you can add a full automatic generated table of content.  
+With only 2 mouse clicks you can add a full automatic generated table of content.
 Changes in the documentation are updated on the fly.
 ![](https://download.qelectrotech.org/qet/images-features/0060.png "Table of content")
 
 Choose from more than 8.200 symbols...
-The embedded QET collection contains a rich library of electric, logic, pneumatic, hydraulic and fluid symbols.  
+The embedded QET collection contains a rich library of electric, logic, pneumatic, hydraulic and fluid symbols.
 The library grows at every new release thanks to an active user community.
 ![](https://download.qelectrotech.org/qet/images-features/0070.png "Collections")
 
 ...or create your own collection
 
-The embedded element editor is a nice tool to create your own elements (symbols or anything else).  
+The embedded element editor is a nice tool to create your own elements (symbols or anything else).
 Your own elements are stored in the user collection.
 ![](https://download.qelectrotech.org/qet/images-features/0080.png "Element editor")
 
 Quickly find what you need
 
-All collections can quickly be searched with the integrated search engine.  
+All collections can quickly be searched with the integrated search engine.
 Furthermore, the search request can be restricted to the folder of your choice.
 ![](https://download.qelectrotech.org/qet/images-features/0090.png "Search engine")
 
@@ -128,7 +128,7 @@ And of course, you can accurately zoom with the mouse wheel over the drawing are
 
 Link elements together to create cross references
 
-Several types of element can be linked together to display a cross reference text.  
+Several types of element can be linked together to display a cross reference text.
 All types of cross references are automatically updated on the fly, you don't need to think about them if you make changes.
 ![](https://download.qelectrotech.org/qet/images-features/0112.png "Cross ref elements")
 To speed up your work, linkable elements are easily searched and shown.
@@ -143,7 +143,7 @@ This way, you can make your own parts list or bill of material using the full po
 ![](https://download.qelectrotech.org/qet/images-features/0125.png "Spreadsheet")
 Print to pdf and/or export your work to images
 
-Your whole documentation or only selected parts of it can be printed to a real printer or to a pdf file.  
+Your whole documentation or only selected parts of it can be printed to a real printer or to a pdf file.
 Alternatively, you can export to vector (svg) or pixel (png, jpg, bmp) format images.
 
 ### And much more:
@@ -161,44 +161,44 @@ Alternatively, you can export to vector (svg) or pixel (png, jpg, bmp) format im
 Nomenclature
 
 A new nomenclature tool appears in the menu: project -> Add a nomenclature.
-The nomenclature is presented in the form of a configurable table separated into two parts: the display (the form) and the content (the background).  
-- Display: the size and position of the table, the margins between text and the table cell, the alignment of the text in the cells and the font. The configuration of the table headers and the table itself are separate.  
-- Content: the information to display in the table and the order in which it should be displayed.  
+The nomenclature is presented in the form of a configurable table separated into two parts: the display (the form) and the content (the background).
+- Display: the size and position of the table, the margins between text and the table cell, the alignment of the text in the cells and the font. The configuration of the table headers and the table itself are separate.
+- Content: the information to display in the table and the order in which it should be displayed.
 
 ![](https://download.qelectrotech.org/qet/images_depeche_linuxfr/08/dialogue_nomenclature.png "nomenclature dialogue")
 
-In order to speed up the establishment of a nomenclature, it is possible to export / import the display and content configurations separately. This is the "Configuration" part that can be seen in the photos above.  
+In order to speed up the establishment of a nomenclature, it is possible to export / import the display and content configurations separately. This is the "Configuration" part that can be seen in the photos above.
 
-Behind the scenes, an SQLite database does the work, so setting up the content is nothing more or less than an SQL query created using a dialog (screenshot by right).  
-The SQL query is configured as follows (from top to bottom in the screenshot):  
-- “Available information”: the information to display;  
-- "Filter": filter the information (is not empty, is empty, contains, does not contain, is equal to, is not equal to) only one filter can be applied per information, it is not possible combine several;  
-- "Type of elements": allows you to filter on what type of element you want to obtain information.  
+Behind the scenes, an SQLite database does the work, so setting up the content is nothing more or less than an SQL query created using a dialog (screenshot by right).
+The SQL query is configured as follows (from top to bottom in the screenshot):
+- “Available information”: the information to display;
+- "Filter": filter the information (is not empty, is empty, contains, does not contain, is equal to, is not equal to) only one filter can be applied per information, it is not possible combine several;
+- "Type of elements": allows you to filter on what type of element you want to obtain information.
 
-At the bottom, a checkmark "SQL query" allows you to edit a personalized query, if the basic options are not sufficient.  
+At the bottom, a checkmark "SQL query" allows you to edit a personalized query, if the basic options are not sufficient.
 
-When a nomenclature is too large to be contained in a single folio, it is possible to separate it on several folios, the tables of each folio are then linked together. When creating a nomenclature, this option is activated by default, which has the effect of adding the necessary number of folios, adding a table in each of them and linking them together.  
+When a nomenclature is too large to be contained in a single folio, it is possible to separate it on several folios, the tables of each folio are then linked together. When creating a nomenclature, this option is activated by default, which has the effect of adding the necessary number of folios, adding a table in each of them and linking them together.
 
-Finally two buttons are available in the property panel:    
-- "Fit the table to the folio": positions and adjusts the size and determines the number of rows in the table in relation to the folio;  
-- "Apply geometry to all tables linked to this one": applies the three properties mentioned above to all linked tables in order to save time and maintain aesthetic consistency.  
+Finally two buttons are available in the property panel:
+- "Fit the table to the folio": positions and adjusts the size and determines the number of rows in the table in relation to the folio;
+- "Apply geometry to all tables linked to this one": applies the three properties mentioned above to all linked tables in order to save time and maintain aesthetic consistency.
 
-And to finish a table   
+And to finish a table
 ![](https://download.qelectrotech.org/qet/images_depeche_linuxfr/08/tableau.png "table")
 
 
 Summary
 
-The old summary has been completely removed from the code in order to make room for the new one which is exactly the same as the nomenclature (a large amount of the code is common), with the exception of the SQL query (and its dialog to configure it) which offers specific information for editing a summary.  
+The old summary has been completely removed from the code in order to make room for the new one which is exactly the same as the nomenclature (a large amount of the code is common), with the exception of the SQL query (and its dialog to configure it) which offers specific information for editing a summary.
 
-Export of the internal database  
+Export of the internal database
 
-The database used by the nomenclature and the summary can be exported in a “.sqlite” file.  
-Currently this is irrelevant, as the function was created during development for debugging purposes, we left it.  
-Note that the database will become increasingly important in the future of Qet.  
+The database used by the nomenclature and the summary can be exported in a “.sqlite” file.
+Currently this is irrelevant, as the function was created during development for debugging purposes, we left it.
+Note that the database will become increasingly important in the future of Qet.
 
 
-Export of the wiring list  
+Export of the wiring list
 
 In order to be able to use the wiring number printers more easily, the names of conductors can be exported in CSV format, the export respects the quantity of conductors in order to print the right quantity of numbers, for example a potential numbered 240 composed of 3 wires will give 6 × 240 (2 numbers per wire × 3 wires) in the CSV. 
 
@@ -206,13 +206,13 @@ In order to be able to use the wiring number printers more easily, the names of
 
 ### Story
 
-The QElectroTech project was founded in 2007 by two french students, Xavier and Benoit.  
-Xavier developed the base application itself and made all technical choices about the development.  
-The first version of QET (0.1) was released on 09.03.2008.  
+The QElectroTech project was founded in 2007 by two french students, Xavier and Benoit.
+Xavier developed the base application itself and made all technical choices about the development.
+The first version of QET (0.1) was released on 09.03.2008.
 However, both Xavier and Benoit do not participate anymore in the project since 2013.
 
-Following this period, new developers and contributors took over the project and kept it alive.  
-The development and the many translations are actively maintained.  
+Following this period, new developers and contributors took over the project and kept it alive.
+The development and the many translations are actively maintained.
 New functionalities and evolutions are planned to make QET ever better.
 
 Nowadays, QET is not only used by many individuals, teachers and students but also by professional electricians and companies all over the world.