A quiet workshop for JA→TH light-novel translation, in your 本屋.
Drop an EPUB into a folder. honya orders the spine, relocates illustrations, cleanses HTML into Markdown, then runs a three-agent pipeline over an OpenRouter-compatible API — keeping your glossary, character sheet and volume notes current as it goes.
A calm, literary tool for a slow craft — not a translation firehose.
honya treats a light novel the way an editor would: one volume, one chapter, one chunk at a time — with continuity carried forward and decisions written down.
You give it an EPUB. It gives you back a project folder you can read, edit and trust — Japanese on the left, タイ語 Thai on the right.
Pre-processing puts chapters in spine order, relocates the inline illustrations, and cleanses the HTML down to plain Markdown. From there, every chapter is chunked to roughly 1,000 tokens and walked through the pipeline, with the last five Thai sentences from the previous chunk injected for continuity.
honya talks to an OpenRouter-compatible API, so it needs a key. On first
launch it prompts you to paste one and saves it to ~/.config/honya, so
you're only asked once.
Tabbed, keyboard-driven, and quiet by design.
Press 1–5 in the app to move between views. Each one does a single thing well — pick a tab to see it.
The live run. A chunk gauge fills as the three agents — ◆ Orchestrator, ▲ Translator, ■ Reviewer — work the chapter, a token meter counts up, and the Thai streams in beneath the Japanese source.
Orchestrator, Translator, Reviewer — per chunk, with memory.
Each chapter is split into ~1,000-token chunks. Continuity and context travel with every chunk; the reviewer can send work back before anything is written.
Sets the table
Bundles the glossary, character sheet, project recap and style — plus the previous chunk's last five Thai sentences — then hands a clean, contextual prompt onward.
Drafts the Thai
Translates the chunk in voice, streaming tokens into the live preview so you can watch the prose arrive rather than wait on a spinner.
Approves or sends back
Checks fidelity and consistency. On approve, the Thai is appended deterministically; on reject, itemized feedback routes back for a retry.
One line to a working bookshop.
No build step. Run it, paste your OpenRouter key when prompted, and start translating.
curl https://honya.altqx.com/install.sh | bash
cargo install --git https://github.com/altqx/honya honya
Already installed? Update in place with honya update.
Built for the way translation actually gets done.
No magic, no metrics theatre. Just a set of decisions that keep a long project coherent.
Bring your own key
honya is OpenRouter-native. It prompts for a key on first launch and saves it
locally to ~/.config/honya — or read HONYA_API_KEY from the
environment. No accounts, no telemetry.
Three-agent pipeline
Orchestrator, Translator and Reviewer split the work per chunk. The reviewer can reject with itemized feedback before anything lands on disk.
EPUB pre-processing
Spine-ordered chapters, relocated illustrations, and HTML cleansed into tidy Markdown — so the agents read clean text, not markup.
Side-by-side reader
Synced JA→TH proofreading with the columns locked paragraph to paragraph, so your eye never loses its place during review.
A glossary that maintains itself
Through tool calls, the agents keep GLOSSARY, CHARACTERS and notes current as the story unfolds — terms stay consistent across volumes.
Everything is just files
PROJECT.md, GLOSSARY.md, STYLE.md and per-volume folders — readable, diffable, and yours. Edit by hand any time; honya picks up where you left it.
Drop in an EPUB. Let the 本屋 do the patient work.
Free and open source. Bring an OpenRouter-compatible key, drop in an EPUB, and let the three agents do the patient work.