Should comments in the margin be translated into the body?
No. Comments in the margin should not be translated into the body. A comment is someone talking about the text: an instruction, a question, a doubt. The body is the text that will be signed, published, or obeyed. Translating a comment into the body turns a side conversation into a clause. Comments stay in the margin, in a comment, or in a query list, until the client says the comment is now a change to the source.
A contract draft carried a margin note beside a liability clause: “please soften this, legal will hate the tone.” The note was aimed at the drafter. The translated file inserted a sentence into the clause that told the reader to soften the tone because legal would hate it. The comment had been treated as source text, translated, and merged. Counsel found their own aside sitting inside the obligation. The clause now contained an instruction to the translator, addressed to the counterparty, and the duty underneath it had been blurred by a sentence that was never meant to leave the margin.
Who is speaking in a comment
The body speaks in the voice of the document: the parties, the procedure, the policy. A comment speaks in the voice of a reviewer, a lawyer, a engineer leaving a note to a colleague. Those voices do not combine. A reader of the delivered file should not be able to hear the reviewer talking. When they can, a comment has leaked.
Some comments are drafts of wording the reviewer wants inserted. They still leak if you insert them on your own guess. The words may have been a suggestion, a joke, a rejected alternative, or a question with a question mark that a model straightened into a statement. The status of the comment is a decision. It is not a sentence you promote because it was sitting nearby.
Where comments should go instead
Keep them as comments in the delivered file if the client asked for a commented round. Translate the comment into the target language only when the reviewer on the other side needs to read the note, and keep it marked as a comment, with its author. Or move the actionable ones into a query list: page, comment, what you need decided. The list is how “please soften this” becomes a question to the client, and the client’s answer becomes the edit.
A query list also stops the comment from being mistaken for source on the next version. Once it lives in the body, every later memory match will offer it as if it were the clause.
When a comment does become body text
It becomes body text when the person who owns the source accepts it as a change. They write the new sentence, or they accept a proposed sentence, and that sentence is now source. You translate that source. The comment can then be resolved and deleted, so it does not survive beside the new sentence and get translated again next week.
If the comment contradicts the clause, you do not average them. You ask which one wins. Averaging a duty with a note that says to soften it is how the aside ended up inside the obligation, sounding vaguely official and binding nobody in particular.
What about comments that are already in the target language?
Leave them as comments too, because the test is the voice of the document and not the language of the note. Resolve the aside or keep it in the margin, and do not merge it into the clause.
Should tracked changes be treated like comments?
Tracked changes are still proposals, so accept only the changes the owner has accepted. Confirm the accepted text, then translate the body that remains.
The related service page is translation services.
Quick FAQ: AI Translation Accuracy
- How accurate are AI translators? Accuracy is often high for repetitive or general content, while domain-sensitive content still needs expert review.
- How to improve AI translation quality? Use glossary control, domain prompts, QA checks, and human post-editing in one workflow.
- Where does human translation still win? Legal, medical, and high-stakes brand content usually requires human nuance and accountability.