Klammertext on Windows is the Linux build inside WSL 2, or the prebuilt
containers through Docker Desktop. The native build from source (MSYS2) is
no longer offered:
- doc/install/windows_source_install.md and the bundled shell under win/
are removed.
- doc/install/windows_wsl_install.md is the Windows page. It says there is
no native build, and its editor section says what holds for each editor:
Emacs, Vim and Visual Studio Code (through its WSL extension) as on
Linux; Sublime Text and Notepad++ on the Windows side, with their
self-contained packages, on files opened through \\wsl.localhost.
- The README lists six install guides; the Notepad++ and VS Code READMEs
no longer refer to the MSYS2 shell.
No change to the language, the Standard Klammer Set or the commands.
- CRLF line endings are read as newlines on every system (the reader used
to delete the pair, collapsing a Notepad++ file into one line on Linux
and macOS); a leading UTF-8 byte-order mark is ignored; a UTF-16 or
Windows-1252 source is refused with the encoding, the place and the
remedy named. .gitattributes pins LF in every clone.
- Windows source install: the repository path must hold no space (GNU
Make), accented letters are fine (every linker input is relative now);
python.org's Python is selected ahead of an MSYS2 one that poppler pulls
in; TeX Live goes to its Windows default C:\texlive\2026.
- The Python binding needs an ASCII installation path on Windows, and its
suite says so there.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Assembled from development commit c3c40f6c8fca. Since 830b193: on Windows the
products carry Windows names (ktext.exe, klammertext.dll, document.dll,
reflect.dll) and the console's output code page is UTF-8 for a run; the
editor tooling works on Windows (VS Code, Sublime Text, Vim, with the
interpreter's name chosen by platform) and Notepad++ joins it
(doc/edit/notepadpp: a User Defined Language and two Run-menu commands);
a sixth install page, doc/install/windows_wsl_install.md, for Linux
inside WSL; the Windows page opens with the three routes and gains its
editor section, the PowerShell quoting and Path notes; the Linux page
installs OpenImageIO from the python3-openimageio package and verifies
with kdiag --machine; the README lists all six install pages. Linux and
macOS behaviour is unchanged.
ack
