#Translating Books
Book translation is a long project. The main challenge is not only translating each sentence, but keeping names, voice, terminology, and formatting consistent from beginning to end.
#Recommended Project Structure
- Work by chapter, scene, or section.
- Keep one glossary group for the book or series.
- Save notes for names, titles, honorifics, and style decisions.
- Translate in repeatable passes instead of trying to finish everything in one run.
- Export and inspect samples before processing the full book.
#Step-By-Step Book Workflow
- Prepare a clean source file.
- Create a project glossary with key names and terms.
- Translate one chapter as a sample.
- Review meaning and formatting in the CAT Editor.
- Add glossary terms discovered during review.
- Translate the next chapter.
- Run a consistency pass across completed chapters.
- Use AI refinement only where the draft is awkward or uneven.
- Export and inspect the final file in the expected reading app.
#Suggested Passes
| Pass | Goal | What to check |
|---|---|---|
| First pass | Create a complete draft | Meaning, missing text, obvious errors |
| Consistency pass | Stabilize the book | Names, places, titles, repeated phrases |
| Style pass | Improve readability | Dialogue, narration, register, rhythm |
| Export pass | Confirm deliverability | Formatting, chapter order, headings, footnotes |
#Chunk Sizing Strategy
Use smaller chunks when:
- The source has complex formatting.
- Your computer is slow with large batches.
- The text has many tags, footnotes, or tables.
- You want easier retries.
Use larger chunks when:
- Context matters heavily.
- The source is clean prose.
- Your hardware handles the workload comfortably.
Do not change chunk strategy in the middle of a critical review unless you are testing a specific issue.
#Production Tip
Treat each pass as a separate quality gate. Fixing terminology before style review prevents repeated rework and helps keep the final book coherent.