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.
Exports: DXF blocks and attributes, circle/arc fix, repeatable PDF, landscape PDF pages, wiring export columns, folder options in headless runs
Documents PRs #1350-#1353, #1257/#1286/#1317, #1255, #1249, #1287/#1311,
#1248, #1262. Print and export option labels now quote the current
English interface. CLI page: settings location and QET_SETTINGS_DIR
corrected. Project database page: --export-wiring reads
wiring_list_view, not --export-cables/--export-wires.
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.
aligning_items: Align left/centre/right/top/middle/bottom (pending #1087); drop merged notices for #1074, #1078, #1079, #1084
Aligning items, grouping items, DXF command line and layers (PRs #1073, #1074, #1078, #1079, pending)
New pages aligning_items (snap to grid) and grouping_items; dxf gains
--export-dxf and the layer table with a rendered example; cli_reference
and scripting list --export-dxf / exportDxf(). Each section carries a
pending notice naming its PR. Sidebar and see-also links added.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document DXF: two unrelated features reduced to one bullet each
sources/createdxf.*, sources/dxfpaintdevice.*, sources/dxf/dxftoelmt.*
total ~1,780 lines. The only wiki coverage was a single repeated bullet
-- 'DXF -- CAD format for collaboration' -- across features, faq and
user_manual, in all three languages, describing neither direction
accurately: it reads as one feature, and it's actually two that share
nothing but a file extension.
Export (File -> Export, alongside PDF/PNG/SVG, in-process) reuses every
item's existing paint() code through a custom QPaintEngine
(DxfPaintEngine) rather than a separate DXF renderer -- documented from
that class's own thorough header comment, including the real fidelity
table it specifies: rectangles and filled paths lose their fill (no
HATCH primitive in this DXF dialect), arcs become straight-line chords,
and images become position-preserving placeholder rectangles since DXF
has no raster entity here. No CLI verb exists for it, unlike PDF/PNG/SVG.
Import (element editor only, not the diagram editor -- File -> Import a
DXF file) is a symbol-authoring tool: it shells out to dxf2elmt, a
separate third-party program QET does not bundle, the same external-tool
pattern as qet_tb_generator already documented in api_reference. Traces
the actual call: , stdout read as .elmt XML, pushed
onto the element editor's undo stack as one operation.
Makes explicit what neither direction is: not a way to place a DXF
drawing on a folio, not round-trip safe (export's own limitations rule
that out before even considering the code is entirely separate), and not
a full CAD interchange path -- no layers, blocks or metadata, just
primitives.
Links the existing one-line mentions in features/faq/user_manual (all
three languages) to the new page instead of rewriting them, since they
are fine as list bullets. EN/FR/DE.