What version of the IDE extension are you using?
26.304.20706
What subscription do you have?
Plus
Which IDE are you using?
VS Code
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
On Windows PowerShell, Codex sometimes tells me Turkish characters are broken (for example İ, ş, ç) even though the file is actually UTF-8 and looks correct in my IDE. It seems like Codex is reading terminal rendered text and treating that as real file corruption. I need Codex to validate encoding more reliably before warning about text issues. Right now, I get incorrect encoding warnings while reviewing or editing .tsx files that contain Turkish text, and this leads to confusion and extra work.
What steps can reproduce the bug?
You can reproduce this by opening a .tsx file that contains Turkish UTF-8 text, then reading that file through Windows PowerShell output. In some cases, PowerShell shows mojibake characters (for example İ, ş, ç) and Codex treats that terminal rendering as if the source file itself is corrupted even though the file is valid UTF-8 and displays correctly in the IDE.
Example source:
example.tsx:
const label = "Hızlı Geçiş Sistemi";
Then run this in powershell:
Get-Content .\src\app\routes\pages\example.tsx
Codex may read the console output and incorrectly report Turkish character corruption as a real file issue.
What is the expected behavior?
Codex should distinguish between terminal display encoding issues and actual file encoding issues. If the source file is valid UTF-8 and renders correctly in the IDE Codex should not report character corruption. Before flagging text corruption Codex should verify file content using a reliable validation instead of relying only on PowerShell rendered output.
Additional information
Shortly: IDE text rendering is correct but the issue appears in terminal rendered output interpretation.
What version of the IDE extension are you using?
26.304.20706
What subscription do you have?
Plus
Which IDE are you using?
VS Code
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
On Windows PowerShell, Codex sometimes tells me Turkish characters are broken (for example İ, ş, ç) even though the file is actually UTF-8 and looks correct in my IDE. It seems like Codex is reading terminal rendered text and treating that as real file corruption. I need Codex to validate encoding more reliably before warning about text issues. Right now, I get incorrect encoding warnings while reviewing or editing .tsx files that contain Turkish text, and this leads to confusion and extra work.
What steps can reproduce the bug?
You can reproduce this by opening a .tsx file that contains Turkish UTF-8 text, then reading that file through Windows PowerShell output. In some cases, PowerShell shows mojibake characters (for example İ, ş, ç) and Codex treats that terminal rendering as if the source file itself is corrupted even though the file is valid UTF-8 and displays correctly in the IDE.
Example source:
example.tsx:
const label = "Hızlı Geçiş Sistemi";
Then run this in powershell:
Get-Content .\src\app\routes\pages\example.tsx
Codex may read the console output and incorrectly report Turkish character corruption as a real file issue.
What is the expected behavior?
Codex should distinguish between terminal display encoding issues and actual file encoding issues. If the source file is valid UTF-8 and renders correctly in the IDE Codex should not report character corruption. Before flagging text corruption Codex should verify file content using a reliable validation instead of relying only on PowerShell rendered output.
Additional information
Shortly: IDE text rendering is correct but the issue appears in terminal rendered output interpretation.