Bring UTF-8 back to x86 kit
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- c
- Domain
- build-system, operating-systems
Research direction
Start by locating the x86 kit integration for utf8.manifest and utf8.rc, then compare it with the conforming manifest and resource definitions shown in the issue. Build the x86 kit and verify that an executable using the manifest reports UTF-8 as its active code page on Windows XP and newer Windows versions.
Written by the indexing model from the issue text.
Description
The UTF-8 feature was disabled in x86 kit because Windows XP won't load exe files with the UTF-8 manifest. (#58)
After some investigation, I dramatically found that Microsoft gave a non-conforming manifest in their document for UTF-8 code page.
The correct info is available here. With the conforming manifest, the exe does work on Windows XP.
utf8.manifest
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1"
xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">
<asmv3:application>
<asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2019/WindowsSettings">
<activeCodePage>UTF-8</activeCodePage>
</asmv3:windowsSettings>
</asmv3:application>
</assembly>
utf8.rc
#include <winuser.h>
CREATEPROCESS_MANIFEST_RESOURCE_ID RT_MANIFEST "utf8.manifest"
test.c
#include <stdio.h>
#include <windows.h>
int main()
{
printf("Current code page: %u\n", GetACP());
}
To compile:
windres utf8.rc -O coff -o utf8.o
gcc test.c utf8.o -o test.exe
- Dominant language
- C
- Stars
- 4.8k
- Forks
- 381
- Avg merge
- 45m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from skeeto/w64devkit
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in skeeto/w64devkit
Similar issues
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
hapostgres/pg_auto_failover#1190 ·
-
docs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
P3 sonic-vpp
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sonic-net/sonic-buildimage#29662 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
spack/spack-packages#6586 ·