A product by AZF Desenvolvimento

In development

AI-assisted book translation with context and control.

Literary Translator organizes EPUB and text-based PDF translation into a chapter-based workflow, with a book-specific glossary, progress tracking, and EPUB export.

See the workflow

Workflow illustration. Workflow illustration: source text, glossary, translation, and per-chapter progress. Illustrative example; not a screenshot of the application.

A book is not a pile of loose passages

Translating a book passage by passage takes organization: keeping the same names and terms from start to finish, tracking what is already done, and rebuilding the file at the end without losing the structure of the original.

Literary Translator brings that work into one trackable workflow, from uploading the file to the new EPUB.

How it works

Five steps, from the source file to the translated EPUB.

  1. Upload the book

    Upload an EPUB or a text-based PDF.

  2. Prepare and adjust

    Prepare the chapters and adjust the book glossary.

  3. Translate

    Run the translation with the configured AI provider.

  4. Follow progress

    Track chapters and segments; pause and resume whenever needed.

  5. Export

    Export the new EPUB, leaving the original file untouched.

This page only explains the workflow; it does not operate the application.

Features

What the documented workflow offers today.

  • Book-specific glossary

    Define how names, places, and recurring terms should appear. The glossary accompanies the passages sent to the model to guide consistency.

  • Context between segments

    Each batch is translated together with the text translated immediately before it, to help keep tone continuous. It is not the full context of the book.

  • Care for structure

    Italics, links, and other inline elements are protected during translation. The exported EPUB goes through a structural check and checks that flag possible problems.

  • Per-chapter progress

    See progress by chapter and inspect the translated segments, including any that failed.

  • Pause and resume

    Translation runs in the background. You can stop and continue where you left off, without redoing what is already translated.

  • EPUB export

    The result is a new EPUB in the target language. The original file stays as it was uploaded.

Technology

Configurable AI providers

Literary Translator is self-hosted and does not depend on a single AI vendor. The provider is chosen in configuration.

  • Ollama (local models)
  • OpenAI
  • OpenAI-compatible endpoints
  • Anthropic

AI and Claude integration

The architecture supports multiple AI providers, including Anthropic. Claude can translate segments using the book glossary and a preceding context window.

This describes what the architecture supports, not a partnership or production use.

Available and planned

Documented in the implementation

  • EPUB and text-based PDF upload
  • Chapter and segment preparation
  • Book-specific glossary
  • Translation with a configurable provider
  • Progress tracking
  • Pause and resume
  • EPUB export

Planned stages

  • Additional book analysis
  • Polishing of the translated text
  • Additional review

Limits to keep in mind

  • Scanned PDFs without text are not accepted: OCR would be required.
  • Size and structure checks do not measure semantic or literary quality.
  • AI output can contain errors and needs human review before any publication.
  • EPUB metadata is updated and converted PDFs receive typographic adjustments; the exported file is not identical to the original.
  • Whether processing is local or external depends on the configured provider.

Frequently asked questions

Which formats are supported?

EPUB and text-based PDF. A PDF is converted to EPUB.

Does it accept scanned books?

Not in the documented workflow; OCR would be required.

Can I keep names and terms?

Yes, through the glossary. It is applied to the prompts to guide consistency, without guaranteeing identical results in every passage.

Is the original changed?

No. Export produces a separate EPUB.

Can I interrupt the translation?

Yes. Processing can be paused and resumed.

Is the translation perfect?

No. AI output can contain errors and needs human review before publication.

Is processing local?

It depends on the provider. Local models and external services are both supported.

Can I use it publicly yet?

This site presents a project in development and does not confirm public access to the application.

About

Literary Translator is a project by AZF Desenvolvimento, created by André Augusto Zaguette Fernandes to organize AI-assisted book translation into a workflow with context, terminology consistency, and control over processing.