STranslate: a WPF translation and OCR tool you extract and run

Installation is extracting an archive, not walking a wizard

The whole installation instruction is one sentence: download the latest release version and extract it to use. That is unusual enough to be the first thing a new user notices, and it says something about how the project is distributed. The README describes no installer or setup wizard. The consequence for updates is direct. A new version means a new folder, and the previous one stays where it was unless you delete it yourself. The project's own tagline in the repository description calls it ready-to-go, which is an accurate description of this distribution model rather than a marketing flourish.

The sources are two hosts for the same project: the GitHub repository for overseas users and a Gitee mirror for domestic ones.

build.ps1
post_build.ps1
src/
images/

WPF fixes the platform before anything else does

The primary language is C# and the interface framework is WPF, which is the Windows presentation stack, so the supported platform question answers itself before you read a single feature. There is no macOS build, no Linux build and no browser version published from this repository. That single fact shapes everything else about the project: the build scripts are PowerShell, the distribution is a Windows release archive, and the documentation site is written for a desktop application with a window. The two hosts in the README's Access table, GitHub for overseas users and Gitee for domestic ones, are split by region, not by platform.

Two PowerShell scripts and one source directory

The top level of the repository is unusually small, and that is informative. There is a source directory holding the project, two PowerShell scripts at the root named for building and for a step after the build, a gitignore, a .github directory, an images directory, and the usual documentation files. No solution file or project file appears at the top level, so a contributor's first move is into the source directory rather than to a root-level entry point. The two scripts are worth noting as a pair rather than individually: one runs the build and the other runs afterwards, which is the shape you use when artefacts have to be signed, bundled or copied after compilation rather than during it.

The usage guide is on the author's site, not in the tree

The README's usage section is a single link to a documentation site hosted on the author's own domain, and the same domain appears again in the author section alongside a separate blog. There is no usage document in the repository, no configuration reference and no sample file. That is a deliberate division of labour, and it works well as long as the site and the release stay in step, but it has a failure mode: a reader who clones the repository, or who has extracted an older release, has nothing local to consult. Questions go to the discussions board rather than to an issue tracker, and there is a user exchange group behind a QR code, which suggests the community channel is chat-shaped.

Two readmes, and one of them is the source of the other

The README carries a language switch in its header, offering English and a Simplified Chinese version, and the Chinese readme is a separate file at the root rather than a translation service or a generated variant. That means there are two documents describing the same project, and keeping them consistent is manual work by the maintainer. It also tells you something about where the project's users are: the author is credited under a handle, the organisation that maintains it is named separately, and the README is presented bilingually from the top. For a translator tool, a bilingual readme is not a small detail, since the audience for the documentation overlaps with the audience for the tool's output.

Changelog, privacy, conduct and a sponsor list sit in the tree

The repository carries a changelog, a privacy document, a code of conduct and a sponsor list beside the readme and the licence. That set is more governance than a two-file translation utility usually ships, and it is a fair signal about how the project intends to be run. The licence is MIT with copyright attributed to the author, and the author section names the original author and the maintaining organisation separately. On the release side the numbering is dense and current: three releases in the last few months, and the most recent push to the main branch is dated 2026-09-24. For a tool people extract and run, that cadence matters, because the person updating it is usually the person who read the changelog last time.

Support is a discussion board, a chat group and a donation link

Support is arranged in three shapes, and each says something about what the maintainer expects. Questions belong in the discussions area rather than in issues, which keeps the tracker narrow but moves support into a threaded conversation. A user exchange group is available behind a QR code for people who would rather chat, and there is an open source support link alongside a donation section offering a coffee, with WeChat and Alipay as the payment routes and a sponsor list in the repository. None of that is unusual for an independently maintained desktop tool. The gap a reader will notice is elsewhere: the README does not describe which translation services the tool calls or how they are configured, which is the first question a new user asks about a tool whose name is the feature.

Editorial conclusion

It suits a Windows user who wants a translation and OCR tool without an installer, and who is comfortable replacing a folder when a new release appears. It does not suit a macOS or Linux user, since the tool is built on a Windows presentation framework and no other platform build is published. Check four things before you rely on it: whether you use the GitHub or the Gitee host, whether the documentation site matches the version you extracted, because the usage guide is not in the repository, how you will package it if you redistribute it, given it is MIT licensed with copyright held by the author, and which translation service it is configured to call, which the README does not describe.

Frequently asked questions

Official sources

1. License: MIT
2. Project website
3. README
4. Releases
5. STranslate/STranslate on GitHub