Windows Non-ASCII Path Workarounds

Core Workflow

1. Capture the exact failing path and error string.
2. Verify the path really exists before blaming encoding.
3. Check whether the path contains Chinese or other non-ASCII characters.
4. If the failure is path-sensitive, create an ASCII-only working copy inside the current workspace.
5. Rerun the failing operation against the ASCII copy.
6. Apply the library-specific workaround only after the existence check is clean.
7. Copy or rename the final artifact back to a user-friendly name only after the workflow succeeds.

Proven Fixes