Start with a UTF-8-BOM file instead of creating it from the the ASCII…

… encoded batch file.

.pre-commit-config.yaml

@@ -33,14 +33,15 @@ repos:
     rev: v4.3.0
     hooks:
       - id: fix-byte-order-marker
-        exclude: ^.*(\.cbproj|\.groupproj|\.props|\.sln|\.vcxproj|\.vcxproj.filters)$
+        exclude: ^.*(\.cbproj|\.groupproj|\.props|\.sln|\.vcxproj|\.vcxproj.filters|UTF-8-BOM.txt)$
       - id: check-case-conflict
       - id: check-json
       - id: check-merge-conflict
       - id: check-xml
       - id: check-yaml
         exclude: ^\.clang-format$
       - id: end-of-file-fixer
+        exclude: ^.*UTF-8-BOM.txt$
       - id: mixed-line-ending
       - id: trailing-whitespace
         exclude: \.(c|cc|cxx|cpp|frag|glsl|h|hpp|hxx|ih|ispc|ipp|java|js|m|mm|proto|vert)$

tools/UTF-8-BOM.txt

@@ -0,0 +1 @@
+

tools/windows_buildenv.bat

@@ -1,6 +1,5 @@
 @ECHO OFF
 SETLOCAL ENABLEDELAYEDEXPANSION
-REM this í is just to force some editors to recognize this file as ANSI, not UTF8.
 
 CALL :REALPATH "%~dp0\.."
 SET MIXXX_ROOT=%RETVAL%
@@ -174,13 +173,13 @@ REM Generate CMakeSettings.json which is read by MS Visual Studio to determine t
 
     CALL :SETANSICONSOLE
     SET OLDCODEPAGE=%RETVAL%
-    REM set byte order mark (BOM) for the file .
-    REM WARNING: Ensure that the script is saved as ANSI, or these characters will not
-    REM contain the correct values. Correct values are EF BB BF (ï » ¿) .
-    REM The last character is an actual character for the file, the start "{"
-    >"%CMakeSettings%" echo {
+    REM Start with a UTF-8-BOM
+    REM Correct values are EF BB BF (ï » ¿)
+    REM Make sure the BOM is not removed from UTF-8-BOM.txt
+    copy "%MIXXX_ROOT%\tools\UTF-8-BOM.txt" "%CMakeSettings%"
     CALL :SETUTF8CONSOLE
 
+    >>"%CMakeSettings%" echo {
     >>"%CMakeSettings%" echo   "configurations": [
     SET configElementTermination=,
     CALL :Configuration2CMakeSettings_JSON off       Debug