dotCooCoo ead3cd1ebd Variables: Import Data Sets reads UTF-16 CSV files without a byte-order mark ...

A CSV file that holds NUL bytes and has no byte-order mark was refused.
It is now read as UTF-16 when at least half of its two-byte units hold
a NUL byte, in the byte order that reads a line break. A file with fewer
NUL bytes (UTF-8 or Windows-1252 text with stray NUL bytes, or UTF-16
text made mostly of characters above U+00FF) is still refused, and so is
a file that reads a line break in both byte orders, has an odd length,
isn't valid UTF-16 in that order or holds a NUL character. Refused files
get the same message as before.

2026-11-13 16:34:43 -08:00

..

examples

…

src

Variables: Import Data Sets reads UTF-16 CSV files without a byte-order mark

2026-11-13 16:34:43 -08:00

tests

Merge pull request #7216 from dotCooCoo/feat/trim-at-crossings

2026-11-14 04:30:27 +07:00

Cargo.toml

Data Recovery: on Windows the lock file check compares file identity

2026-11-11 16:59:13 -08:00