What a Windows editor saves, and a standard user's Windows install (from dev 9d6f66456a3d)

- 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>

mac/file.h

@@ -70,6 +70,12 @@ std::vector<std::string> group_filename_tokens(
 std::vector<std::string> resolve_filename_list(
     const std::string& text, const std::string& base_dir="");
 std::string string_from_file(const std::string& pathname, bool strip_surrounding_whitespace=false);
+// A Klammertext source (a .kt, a .k, a @read file): string_from_file() plus
+// the check that it IS text Klammertext can read -- a File_error names the
+// first byte that is not UTF-8 (line and character), or a UTF-16 file by its
+// byte-order mark, with what to do in an editor.  string_from_file() itself
+// stays permissive: it also reads XeTeX logs and a shell command's stderr.
+std::string klammertext_from_file(const std::string& pathname);
 void string_to_file(const std::string& pathname, std::string contents);
 std::vector<std::string> get_files_in_directory(const std::string& dir);
 std::string find_file(const std::string& basename, std::vector<std::string> search_path,