Help make Phi Browser feel native in your language.
Phi is an open-source, local-first AI browser for macOS. This repository is the single home for every user-visible string in the Phi product family: the browser itself, its AI chat surfaces, the memory features, and the Sentinel local AI manager, all folded into one catalog you can translate without knowing anything about the codebase.
| Source strings | 3,719 (English, every one with translator context) |
| Languages | 8, all seeded to 100% |
| Seed quality | Machine-translated under a curated glossary, then independently audited per language (98 to 100% audit pass rates) |
| What we need from you | Human polish. Machine seeds are a starting point; native speakers make them feel right |
| Locale | Language | Locale | Language | |
|---|---|---|---|---|
de |
Deutsch | ko |
한국어 | |
es |
Español | nl |
Nederlands | |
fr |
Français | zh-Hans |
简体中文 | |
ja |
日本語 | zh-Hant |
繁體中文 |
Want a language that isn't listed? Open an issue and make the case; the pipeline adds locales cheaply.
source/holds the canonical English catalog, split into five sections so you can work on the part of Phi you care about:browser(the browser itself: menus, settings, windows, pages),chat(the AI chat surfaces),memory(the memory features and the new tab),sentinel(the local AI manager and the agent features), andshared(strings that appear in more than one section). Each entry has amessageand adescriptionbeginning with aLocation:line naming the section(s) where it appears, followed by translator context: what the string does, and what any placeholder will contain. Source files are generated by the pipeline; they never change here.translations/<locale>/<section>.jsonholds your language, mirrored by section. This is where contributions go. Translate one section fully or one string in passing; both are welcome.- Every translation is tracked against the exact English text it translated. If the English changes later, the outdated translation is automatically dropped from the shipping product (falling back to English) until someone re-translates it. A missing translation is always better than a wrong one, so never pad a file just to raise the numbers.
- Merged translations flow back into the actual apps through an automated pipeline: your git commit here ends up in the Phi Browser build, credited to you.
Two paths, both land as normal git commits under your name:
- Pull requests, right now. Edit your language's file, run
node tools/validate.js, open a PR. Format rules live in CONTRIBUTING.md. If you can read a JSON file, you're qualified. - Weblate, live at i18n.phibrowser.com. A friendly web UI with the full catalog, a shared glossary, and translator context for every string. Browse without an account; sign in with a Phi Account or e-mail to translate. Contributions are reviewed periodically and merged into this repository, credited to you.
Every PR is validated automatically (JSON validity, no unknown keys, placeholder integrity) and reviewed by a human before merging. Machine-seeded strings are fair game for wholesale rewriting; that is exactly the contribution we want.
Everything here is dedicated to the public domain under CC0 1.0. Your credit lives permanently in git history and the contributors graph.