Hope to add support for general file encoding editing, as I frequently use GBK encoding, and TAB characters often cause editing failures.

[expfukck]

Question

Hope to add support for general file encoding editing, as I frequently use GBK encoding, and TAB characters often cause editing failures.

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• [FEATURE]:Support multiple file encodings in built-in tools such as Read, Grep, Edit, and Write #27832: Feature request for supporting multiple file encodings in built-in tools (Read, Grep, Edit, Write) — directly overlaps with this request
• [FEATURE]:内置工具编码问题，我是用中文引擎代码只支持GBK #21631: Feature request for GBK encoding support in built-in tools — same encoding concern
• Grep tool fails with "invalid ripgrep output" when source files contain non-UTF-8 (e.g. GBK) characters #23629: Bug where Grep tool fails on non-UTF-8 (GBK) source files — same root issue
• Edit tool corrupts files with Windows-1252 (non-UTF-8) encoding #28521: Bug where Edit tool corrupts files with non-UTF-8 encoding — related editing failure with non-UTF-8 files
• Windows: bash tool cannot correctly handle cmd.exe GBK output #26882: GBK output handling issue in bash tool on Windows — same GBK encoding context

Please review these issues and consider adding a comment or upvote there instead of opening a new issue, if your concern is already covered.