Back to directory

dsh-fs-encoding

In a curated listMaintenance: Active

mrweicodes/dsh-fs-encoding

Read, write, edit, insert, grep, and undo workspace files while preserving their detected encoding.

View on GitHub
$ dsh plugin --profile web add dsh-fs-encoding

16

stars

0

forks

TypeScript

Language

MIT

License

2026-09-14

Created

2026-10-17

Last push

Read and edit legacy-encoded files in DSH: The README says edits use the original encoding by default, including GBK and Shift-JIS; enabling normalizeToUtf8 changes legacy encodings to UTF-8.

DSH integration

Native runtime

Author-claimed

Safety audit

Unaudited

Last verified

2026-10-25

License

MIT

01What can it help you accomplish?

  • Read and edit legacy-encoded files in DSH

    The README says edits use the original encoding by default, including GBK and Shift-JIS; enabling normalizeToUtf8 changes legacy encodings to UTF-8.

    DSH users working with GBK or Shift-JIS project files

02How to install into DeepSeek Harness

Installation steps

  1. 01

    Run `dsh plugin --profile web add dsh-fs-encoding` using the prebuilt npm package.

    $ dsh plugin --profile web add dsh-fs-encoding

  2. 02

    Restart `dsh web`.

    $ dsh web

Verify the integration

Not specified by the author

Rollback

  • Run `dsh plugin --profile web remove dsh-fs-encoding`, then restart `dsh web`.

03DSH integration and capability boundaries

DSH integrationNative runtime

File-encoding tools for DeepSeek Harness (DSH).

  • Explicit encoding on read

    Use `read({ file_path: "legacy.txt", encoding: "gbk" })` to read a GBK file explicitly.

  • Create files with an encoding

    New files default to UTF-8 without BOM; `write` accepts an encoding for new files.

04Who is it for? When not to use it?

Good for

  • DSH users working with GBK or Shift-JIS project files

Not for

  • BOM-less non-UTF-8 files require an explicit encoding by default; automatic guessing is not a guarantee of the correct encoding.
  • Other plugins registering the same tool names at the same scope conflict with this plugin.
  • The `write` encoding parameter applies only to new files; existing files reject it with `E_ENCODING_NOT_APPLICABLE`.

05Compatibility, maintenance and safety notes

  • BOM-less non-UTF-8 files require an explicit encoding by default; automatic guessing is not a guarantee of the correct encoding.
  • Other plugins registering the same tool names at the same scope conflict with this plugin.
  • The `write` encoding parameter applies only to new files; existing files reject it with `E_ENCODING_NOT_APPLICABLE`.
2026-09-142026-10-17Not specified by the author

README claims at the pinned source commit

06Frequently asked questions

Does this DSH plugin guess all legacy encodings automatically?

No. BOM-less non-UTF-8 files require an explicit encoding by default; guessed encodings remain probabilistic.

How do I read a GBK file in DSH?

Use `read({ file_path: "legacy.txt", encoding: "gbk" })`.

Can `write` change the encoding of an existing DSH workspace file?

Its encoding parameter is for new files only; an existing file rejects that parameter.

08Data and sources

github.coma4d31ccNot specified by the author
  • Author-claimedgithub.coma4d31cc33bd6…

    为 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness)(DSH)提供的文件编码治理插件

This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-10-25. Found an error? Submit a correction.

🏆

Best DeepSeek Harness Plugins

Twelve plugins worth installing first — picked from the whole catalog, across every category.

Advertisement

DSH Plugins is an independent community directory of DeepSeek Harness plugins. Not affiliated with or endorsed by DeepSeek. Third-party plugins are not security-audited — review the source before installing.

New DeepSeek Harness plugins, weekly. No spam.