Update applocal.ps1

[shadowxiali]

Fix #2801 , chinese char path fail

[ras0219-msft]

Thanks for the PR!

I don't totally understand the problem this fixes, and this doesn't currently work on my machine:

D:\src\vcpkg> set-content -path foo.txt -value "" -encoding UTF
Set-Content : Cannot bind parameter 'Encoding'. Cannot convert value "UTF" to type "Microsoft.PowerShell.Commands.FileSystemCmdletProviderEncoding". Error: "The identifier name UTF cannot be processed because it is either too similar or identical to the following enumerator names: UTF8, UTF7, UTF32. Use a more specific identifier name."
At line:1 char:47
+ set-content -path foo.txt -value "" -encoding UTF
+                                               ~~~
    + CategoryInfo          : InvalidArgument: (:) [Set-Content], ParameterBindingException
    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.SetContentCommand

The created file in this case is blank regardless of the -encoding setting, so I don't see how this could possibly fix any issue. Is the issue that $copiedFilesLog has chinese characters in the path?

[shadowxiali]

sorry, the correct value is UTF8
PS C:\Users\xiali.000> set-content -path foo.txt -value "" -encoding UTF8
PS C:\Users\xiali.000>

the problem:
create new test_project in path [D:\中文目录]:
test_project.sln file in [D:\中文目录\test_project],
test_project.cpp file in[D:\中文目录\test_project\test_project],
cpp content like

#include <iostream>
#include <boost/filesystem.hpp>

int main()
{
	auto is_dir = boost::filesystem::is_directory("c:\\test");
	std::cout << "c:\\test is directory:" << is_dir << std::endl;
}

, then build, the output window will show fail like:
error MSB3030: 无法复制文件“D:\����Ŀ¼\test_project\Debug\boost_system-vc141-mt-gd-x32-1_68.dll”，原因是找不到该文件。
error MSB3030: 无法复制文件“D:\����Ŀ¼\test_project\Debug\boost_filesystem-vc141-mt-gd-x32-1_68.dll”，原因是找不到该文件。
when modify applocal.ps1 to UTF8, build will success.

[vicroms]

Hi @shadowxiali

There are some concerns regarding this change, see comments on #5301.
Explicitly, do you know if these changes introduce Byte Order Marks?

[ras0219-msft]

Thanks for this PR!