Name the interface in English on the English pages English is QElectroTech's source language since PR #1390 (merged 2026-10-08), so the English interface shows English labels. Menu, dialog and button names on the English pages were French with an English gloss; they now use the exact English labels from the program (lang/qet_fr.ts read backwards), and the glosses are dropped. The Configuration menu is Settings in English, and the keyboard_control mnemonics follow the English labels (Display Alt+A, Settings Alt+S, Help Alt+H). Screenshot captions still describe the French captures they show. The -FR and -DE pages are unchanged.
Call a folio a sheet, as the English interface now does (PR #1216) Prose only: page URLs (folio_links, navigating_folios), image names, code, XML tag and variable names, and French menu names are unchanged. Readers arriving from older forum posts are told a sheet used to be called a folio. Generated by qelectrotech-docker tools/wiki-folio-sheet/rename.py.
Drop stale pending notices: #1047, #1048, #1049 merged today; #1036; #896 (merged 17 Sept)
Add "Finding your place on a folio": go to a cell, keep headers visible New page navigating_folios covers going to a cell with Ctrl+G (B13, or 4-B7 for another page, as cross-references print it) and keeping the row/column headers in sight while zoomed. Both are pending, PR #1036 and PR #1038 (issue #1034), and each section says so. Also: linked from the sidebar and from folio_links, and keyboard_control now says what Ctrl+G does on master (select an element on the current folio), not "finds it in the Collections panel". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01G2d2Zi8BfrYRPX88zhaoFG
Document page/wire linking -- folio reports -- in the user's own words Wires continuing across pages had no page anywhere: element_linking covers master/slave cross-references, not next_report/previous_report. Written with "page" and "wire" in the prose and a glossary mapping them to folio and conductor, since that is how people ask about it. The central fact, taken from LinkElementCommand::isLinkable(): QET checks exactly two things when linking two reports -- matching inverse type, and both being free. It does not check that they are on different pages, that either has a wire attached, that the two wires share a potential, or that the arrows point sensibly. A link is an assertion the user makes and QET renders without verifying, so --export-links is the only real audit. Also documents what was written down nowhere: a report's dynamic text is restricted to five variables (folioReportInfoKeys), the label describes the partner's position rather than its own, report terminals are deliberately excluded from wire-number counts because they are not real terminals, linking replaces rather than adds, and a report is only clickable in an exported PDF when its text actually shows %{label}. EN/FR/DE.