Translate an entire book from English to French
For those who have never used Claude Code, even if the “black window where you type commands” (the terminal) intimidates you. Task: For those who have never used Claude Code, even if the “black window where you type commands” (the terminal) intimidates you. No coding skills needed: just know how to type text. 1. If you’ve already translated a book with chatGPT or claude.ai, you know the struggle Claude translates well, everyone agrees. So you open claude.ai, paste a passage, it gives you a nice translation, you copy it into Word. For a short excerpt, perfect. But translating an entire book that way, after a few chapters, it goes downhill. First, the endless copy-paste. Each passage is a paste-and-copy routine. For a book of several hundred pages, that’s thousands of back-and-forths, not to mention botched pastes, forgotten passages, mixed-up order. The clever ones think that instead of pasting bits, just throw the whole file .txt at once. But that creates other problems. One: the chat window has a length limit, a file too big isn’t fully taken into account, silently truncated without you knowing. Two: even if it swallows it, Claude doesn’t translate the whole book in one go; it translates a bit then suggests “continue for the rest,” and each “continue” is a chance to skip an entire paragraph or drift in tone from what came before. In the end, you get a long translation full of gaps, and cross-checking it against the original takes longer than translating yourself. Worse, each conversation has its own memory. Today you tell it “this character uses informal speech, this term translates like this.” Tomorrow, new conversation, it’s forgotten everything. You have to repeat it all, every time fearing you’ll forget a rule set the day before. Hence the worst mistake when translating a long book: loss of consistency. In chapter 2 a term is translated one way, in chapter 9 another, unintentionally. The tone, formal at the start, gradually dilutes into colloquial speech. A careful reader will feel the book derailing, while you can no longer remember what you decided over the weeks. Finally, the longer the discussion, the more Claude runs out of steam. Stretch a conversation over ten chapters and toward the end, it gets confused, loses the thread, quality drops without you understanding why. The problem isn’t that Claude translates poorly. It translates very well. The problem is that claude.ai isn’t built for a long-term project. Claude Code is. 2. What changes with Claude Code? Imagine claude.ai as an excellent translator locked in a room with no window, with no book in sight. You have to read each passage aloud to it, then hand-copy what it dictates. And every time you call, it’s forgotten the previous translation. Claude Code is the same translator, but sitting at your desk. The book is in front of them. Next to it, the glossary you’ve built, and a “translation rules” sheet pinned on the wall they re-read before picking up the pen each time. The difference: Claude Code works directly on your computer’s files, not through a chat window. It opens chapter files itself, writes the translation into a file itself, consults the glossary you keep in the folder itself. Concretely: The three items in the right-hand column are the key to a translation that’s both polished and consistent: a brief file that Claude rereads before each translation, a glossary that keeps terms consistent, and an automatic proofreading pass that catches mistakes you’d otherwise miss even after an hour of checking. 3. Don’t be afraid of the terminal (the “black window”): setup in ten minutes Claude Code runs in a terminal, that window where you type commands instead of clicking. It looks intimidating, but in reality, most of the time you’re typing in French like you’d send a message to tell it what to do. A real command sounds pretty ordinary, like: Translate livre-complet.txt into French following the rules in regles-traduction.md, then save the result as livre-fr.txt. Installation only needs to be done once: Open the terminal. Windows: Start button, type Terminal, open it. Mac: open the Terminal. Install Node.js (the foundation for running Claude Code): go to nodejs.org, download the LTS version, install it like any other software. Install Claude Code : type this exact line and press Enter. npm install -g @anthropic-ai/claude-code Start it up : navigate to the folder created specifically for the book translation, type claude --dangerously-skip-permissions The first time, it’ll guide you through logging in with your Claude account. That’s it.; tools: Claude Code. Human role: The original post does not say how a person stayed involved.; limitations: Requires a paid Claude Pro subscription (approx. €17/month) and Node.js installation. The process is time-consuming due to session quota limits, requiring users to wait hours for resets. The use of `--dangerously-skip-permissions` bypasses safety checks, posing security risks if the source files are untrusted. Human validation is critical for tone and terminology decisions, as the tool cannot independently judge literary quality..
Tools
Published on Agent Work Atlas:
Overview
For those who have never used Claude Code, even if the “black window where you type commands” (the terminal) intimidates you.
Workflow
For those who have never used Claude Code, even if the “black window where you type commands” (the terminal) intimidates you. No coding skills needed: just know how to type text. 1. If you’ve already translated a book with chatGPT or claude.ai, you know the struggle Claude translates well, everyone agrees. So you open claude.ai, paste a passage, it gives you a nice translation, you copy it into Word. For a short excerpt, perfect. But translating an entire book that way, after a few chapters, it goes downhill. First, the endless copy-paste. Each passage is a paste-and-copy routine. For a book of several hundred pages, that’s thousands of back-and-forths, not to mention botched pastes, forgotten passages, mixed-up order. The clever ones think that instead of pasting bits, just throw the whole file .txt at once. But that creates other problems. One: the chat window has a length limit, a file too big isn’t fully taken into account, silently truncated without you knowing. Two: even if it swallows it, Claude doesn’t translate the whole book in one go; it translates a bit then suggests “continue for the rest,” and each “continue” is a chance to skip an entire paragraph or drift in tone from what came before. In the end, you get a long translation full of gaps, and cross-checking it against the original takes longer than translating yourself. Worse, each conversation has its own memory. Today you tell it “this character uses informal speech, this term translates like this.” Tomorrow, new conversation, it’s forgotten everything. You have to repeat it all, every time fearing you’ll forget a rule set the day before. Hence the worst mistake when translating a long book: loss of consistency. In chapter 2 a term is translated one way, in chapter 9 another, unintentionally. The tone, formal at the start, gradually dilutes into colloquial speech. A careful reader will feel the book derailing, while you can no longer remember what you decided over the weeks. Finally, the longer the discussion, the more Claude runs out of steam. Stretch a conversation over ten chapters and toward the end, it gets confused, loses the thread, quality drops without you understanding why. The problem isn’t that Claude translates poorly. It translates very well. The problem is that claude.ai isn’t built for a long-term project. Claude Code is. 2. What changes with Claude Code? Imagine claude.ai as an excellent translator locked in a room with no window, with no book in sight. You have to read each passage aloud to it, then hand-copy what it dictates. And every time you call, it’s forgotten the previous translation. Claude Code is the same translator, but sitting at your desk. The book is in front of them. Next to it, the glossary you’ve built, and a “translation rules” sheet pinned on the wall they re-read before picking up the pen each time. The difference: Claude Code works directly on your computer’s files, not through a chat window. It opens chapter files itself, writes the translation into a file itself, consults the glossary you keep in the folder itself. Concretely: The three items in the right-hand column are the key to a translation that’s both polished and consistent: a brief file that Claude rereads before each translation, a glossary that keeps terms consistent, and an automatic proofreading pass that catches mistakes you’d otherwise miss even after an hour of checking. 3. Don’t be afraid of the terminal (the “black window”): setup in ten minutes Claude Code runs in a terminal, that window where you type commands instead of clicking. It looks intimidating, but in reality, most of the time you’re typing in French like you’d send a message to tell it what to do. A real command sounds pretty ordinary, like: Translate livre-complet.txt into French following the rules in regles-traduction.md, then save the result as livre-fr.txt. Installation only needs to be done once: Open the terminal. Windows: Start button, type Terminal, open it. Mac: open the Terminal. Install Node.js (the foundation for running Claude Code): go to nodejs.org, download the LTS version, install it like any other software. Install Claude Code : type this exact line and press Enter. npm install -g @anthropic-ai/claude-code Start it up : navigate to the folder created specifically for the book translation, type claude --dangerously-skip-permissions The first time, it’ll guide you through logging in with your Claude account. That’s it.
Reported result
The author reported that the system maintained consistency across chapters by re-reading local files, avoiding the drift common in long chat sessions. They successfully ran the translation overnight, with the tool automatically pausing and resuming from the last saved line when hitting token limits. No specific quality metrics or error rates were provided, but the author claimed the process eliminated manual copy-pasting and ensured no sentences were lost or duplicated.
Human role
The original post does not say how a person stayed involved.
Limitations
Requires a paid Claude Pro subscription (approx. €17/month) and Node.js installation. The process is time-consuming due to session quota limits, requiring users to wait hours for resets. The use of `--dangerously-skip-permissions` bypasses safety checks, posing security risks if the source files are untrusted. Human validation is critical for tone and terminology decisions, as the tool cannot independently judge literary quality.
Try it
I need to translate a book from [Source Language] to [Target Language] using Claude Code. First, create a folder named [Project Name] and place the full text file [filename.txt] inside. Install Node.js and Claude Code if not present. Start Claude Code in this folder. Paste this startup prompt: 'I want to translate [filename.txt] to [Target Language]. Phase 1: Skim the book, ask me clarifying questions about tone and terminology, propose a plan, and create auxiliary files (CLAUDE.md, glossaire.md, regles-traduction.md) based on my answers. Do not translate yet.' Wait for my validation. Once approved, type 'continue' to start translation. Ensure Claude saves progress to files after each section. If interrupted, type 'continue' to resume from the last saved line. Review the first chapter manually for quality before proceeding. Output the final translation in [output_folder].
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.