May 28, 2026
8:42 p.m.
On Thu May 28 20:32:27 2026 +0000, Nikolay Sivov wrote:
I also tried WCHAR content with leading spaces, and that also doesn't work on Windows. FWIW I've seen more differences in encoding detection while looking into it:
* on Windows parse and parseURL behaves differently in some cases (e.g. parseURL doesn't allow UTF-8 xml files with leading white spaces) * it's only possible to detect UTF-16 by specyfing BOM when stream is passed on Windows (while we're detecting L"\<..." prefix) Above observations may be version specific. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/11015#note_141566