can't read code file with GB2312

[CDSR-JY]

App Version

3.19

API Provider

OpenAI Compatible

Model Used

qwen3

🔁 Steps to Reproduce

can't read code file with GB2312.

💥 Outcome Summary

[read_file for 'dp_table.c'] Result:

dp_table.cError reading file: Cannot read text for file type: .c

[read_file for 'dp_table.c'] Result:

The tool execution failed with the following error:

Error reading file: {"name":"Error","message":"Cannot read text for file type: .c","stack":"Error: Cannot read text for file type: .c\n\tat ese (c:\Users\1002412\.vscode\extensions\rooveterinaryinc.roo-cline-3.19.0\dist\extension.js:2875:2626)\n\tat async TVn

📄 Relevant Logs or Errors (Optional)

[dosubot]

Hi @CDSR-JY! I'm Dosu and I’m helping the Roo-Code team.

Based on the available documentation, Roo Code does not provide specific support or troubleshooting steps for reading files with GB2312 encoding. The error message you encountered—"Cannot read text for file type: .c"—suggests that the extension is unable to process .c files with this encoding. There are no documented settings or configurations in Roo Code to adjust file encoding handling, nor are there alternative methods or tools within Roo Code explicitly designed for GB2312 encoding. Previous updates have addressed some general encoding issues (such as unreadable characters at the beginning of files), but not specifically for GB2312 or .c files (source).

As a workaround, you may need to convert your .c file from GB2312 to UTF-8 using an external tool or text editor before reading it with Roo Code. The documentation does not mention built-in support for encoding conversion or provide general troubleshooting steps for this scenario.

If you need further assistance or if this is a critical workflow, you may want to consider converting your files to UTF-8 as a standard practice before using them with Roo Code.

To reply, just mention my name @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[CDSR-JY]

Most of my project code files are in GB2312 encoding. Will there be support for reading files in this format in the future?@dosu.

[daniel-lxs]

This issue is related to handling non-UTF-8 file encodings, similar to #3555. PR #3554 aims to fix this and will likely resolve this issue.