Bug Fix: Windows Unicode Encoding Issue #36
+69
−61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem Description
On Windows systems, the
search.pyscript fails with aUnicodeEncodeErrorwhen outputting Unicode characters (such as warning symbols ). This is because Windows CMD defaults to GBK encoding, which cannot handle UTF-8 Unicode characters.Solution
Added Windows-specific encoding detection and UTF-8 output wrapping to ensure proper Unicode character display on all platforms.
Changes Made
sysandioimports for encoding handlingTechnical Details
Impact
This fix ensures the skill works properly for Windows users, maintaining consistent output formatting across all platforms.
Related Issues
Fix Type: Bug Fix
Platforms Affected: Windows
Breaking Changes: None