New subject: [Bug 49694] mc.exe: UTF-16 decoding does not use UTF-16LE by default, breaking files without a BOM

11 Aug 2020


      https://bugs.winehq.org/show_bug.cgi?id=49694
Bug ID: 49694
           Summary: mc.exe: UTF-16 decoding does not use UTF-16LE by
                    default, breaking files without a BOM
           Product: Wine
           Version: 5.14
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs@winehq.org
          Reporter: ppdplayer@gmail.com
      Distribution: ---
Created attachment 67936
  --> https://bugs.winehq.org/attachment.cgi?id=67936
Two .mc Files, BOM.mc with a proper UTF-16LE BOM, and NOBOM.mc with no UTF-16LE
BOM.
Tested on both wine-staging and wine-vanilla on WINEARCH=win64 using VS-16.5
(and the latest installed though the script VS-16.7) though I suspect this
isn't a program exclusive bug.
When building reactos using msvc on linux, I ran into this bug when building
the .mc files. They are not generated with a UTF-16LE BOM, which Wine does not
properly handle and will fail compilation.
Steps to Reproduce:
1. Download and install VS-16 using https://github.com/mstorsjo/msvc-wine
Sidenote: You may install VS-16 however you like, we just need mc.exe for this.
The script may give socket timeout errors, that's normal. Just retry. You will
also need msiextract and libgcab to run the script. 
2. Using "kits/10/bin/10.0.18362.0/x86/mc.exe -u" or
"kits/10/bin/10.0.18362.0/x64/mc.exe -u" compile the attached BOM.mc and
observe no errors.
3. Using the same programs, observe compiling NOBOM.mc and seeing the error:
z:/home/<censored>/Downloads/tmp/NOBOM.mc(1) : error : expected keyword - M
-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.

[Bug 49694] New: mc.exe: UTF-16 decoding does not use UTF-16LE by default, breaking files without a BOM