3 Commits

Author	SHA1	Message	Date
oleibman	2f9ddd04ef	Support UTF-16 and UTF-32 Without Endian-ness and BOM ... My research indicates they should be treated as Big-Endian. This leaves UTF-7 as the only encoding known to be unsupported by CsvChunk; it will be handled by parent.	2026-04-29 08:38:44 -07:00
oleibman	8e92f0d343	UTF-16 Surrogates ... Chunk routine would fail if chunk ended between two halves of a surrogate. Fix that. UTF-7, UTF-16 and UCS-2 (no endian-ness specified and no BOM), UTF-32 and UCS-4 (no endian-ness specified regardless of BOM) all revert to parent routine.	2026-04-28 19:57:39 -07:00
oleibman	8a033d05f0	Resolve Merge Conflicts	2026-04-06 22:30:37 -07:00