In UTF-8 codepage, local language is broken in favorites menu, file name change in file list pane

[JKyle]

System: Windows 10 Home x64 19042.746
XYplorer: 21.50.0100

First of all, this issue has been around for a long time since I set the system codepage to UTF-8(65001) in Region Settings as follows:



So, my environment settings are as follows: (Powershell command)

Code: Select all

Get-WinSystemLocale; Get-WinDefaultInputMethodOverride; [Text.Encoding]::Default | select EncodingName,CodePage

LCID Name DisplayName
---- ---- -----------
1042 ko-KR 한국어(대한민국)

InputMethodTip : 0412:{A028AE76-01B1-46C2-99C4-ACD9858AE02F}{B5FE1F02-D5F2-4445-9C03-C568F23C99A1}
Description : 한국어(대한민국) - Microsoft 입력기

EncodingName : Unicode (UTF-8)
CodePage : 65001

This change raises two issues.

1. Some localized folder names are broken in Favorites menu.

• Renaming a file name in the local language in the file list pane breaks the language input.

Only via the Rename menu can I change the file name without a problem.

[admin]

Hello and welcome to the club!

Thanks for the report. The case is interesting and tricky!

1) I don't have control over the menu since it is owned by Windows. When I find the time I will replace it by a menu of my own making. This will also fix the issue.

2) Does it help if you tick "Configuration | General | Sort and Rename | Rename | Hide extensions from rename edit box"?

Don

[JKyle]

Hi. Sorry about the late reply. I've been sort'a busy.

1) I don't have control over the menu since it is owned by Windows. When I find the time I will replace it by a menu of my own making. This will also fix the issue.

Thanks.

2) Does it help if you tick "Configuration | General | Sort and Rename | Rename | Hide extensions from rename edit box"?

Unfortunately, no.

[admin]

Strange. Do others using Korean have similar problems with the rename box?

[JKyle]

Strange. Do others using Korean have similar problems with the rename box?

I haven't tested others, but Windows File Explorer has no problem at all.
Do you have any other in mind?

[admin]

No, I meant other (Korean) users of XYplorer, not other file managers.

BTW, I googled "Beta: Use Unicode UTF-8 for worldwide language support" and it looks like others have problems with it as well. After all it says "Beta" so the feature is not yet fully developed.

[JKyle]

Yeah. AFAIK, Windows seems to have problems in dealing with UTF-8 internally.
Wiki document about Windows Unicode.

Maybe this document about UTF-8 may help.

Some programs resolve this ANSI vs UTF-8 issues by incorporating an external UTF-8 manifest.
If you have time, this discussion may help.

For reference, I'm attaching a sample manifest code:

Code: Select all

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel>
      </requestedPrivileges>
    </security>
  </trustInfo>
  <assemblyIdentity type="win32" name="..." version="6.0.0.0"></assemblyIdentity>
  <application>
    <windowsSettings>
      <activeCodePage xmlns="http://schemas.microsoft.com/SMI/2019/WindowsSettings">UTF-8</activeCodePage>
    </windowsSettings>
  </application>
  <dependency>
    <dependentAssembly>
      <assemblyIdentity type="Win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="*" publicKeyToken="6595b64144ccf1df" language="*"></assemblyIdentity>
    </dependentAssembly>
  </dependency>
</assembly>

However, I guess the "broken local language input in file list pane in codepage UTF-8" issue has something more complicated.
I know I have to live with it even if it's not fixed now.
But I guess this issue should be resolved in the end considering UTF-8 is the ultimate codepage Windows is migrating to.

[admin]

I agree.