An AI translation can sound natural while changing a date, a product code, or the strength of a commitment. OGAD (Off Grid AI Desktop) can help you compare the source and translation on your computer. Select a local model to prepare a discrepancy list without uploading the documents to a cloud AI service. Use that list to guide direct checks against the original.
| Download OGAD | Desktop releases |
What would you like to do with Off Grid AI?
Want help with this workflow, or a feature you would like us to add? Email support@offgridmobileai.co with your devices and the task you want to improve.
Treat this as a comparison task
Do not begin by asking the model to produce another translation. First compare the version you already have with the source. A new fluent draft may hide the same error or introduce a different one.
Suppose a translated supplier note changes a proposed delivery date into a confirmed date and turns a part code ending in B into one ending in 8. Both changes can matter even if every paragraph reads well.
Your useful output is a list of differences with source evidence and a decision for each: correct, needs clarification, or acceptable formatting change. The model does not make the final decision for you.
Keep aligned source and target copies
Save the original text and the translation as separate files with clear version names. Number the paragraphs or sections in your working copies if that helps comparison. Do not alter the source wording while preparing the check.
For a short message, paste both versions into a fresh chat with clear labels. For a longer document, review one section at a time. A full document can exceed the model’s context, and project retrieval may select only some passages.
Keep any approved glossary or name list nearby. If the translation was revised after the source changed, confirm that both files refer to the same version before looking for errors.
Set up local review in OGAD
Install the desktop app and download a local text model capable of working with the source and target languages. Complete setup before disconnecting. Test a short comparison with known details so you can see how the model handles the pair.
Select the downloaded model in Models > Text. For a longer project, use Projects > New project, then Knowledge & settings > Knowledge base > Add files. Add readable text-based sources, wait for indexing, and open Chats > New chat.
If Include captured memory is available, turn it off for a source-only comparison and save. Projects and document chat are core features. The Projects implementation supports the source controls; it does not guarantee complete automated translation checking.
Extract exact details from the source
Ask for a first table from the original only:
List the personal and company names, product codes, dates, times, amounts, percentages, quantities, and units in this source section. Copy each exactly and include its sentence or paragraph reference. Do not normalise formats, translate names, or infer missing units.
Check that table yourself. A model can miss an item or misread a digit. Use your editor’s search and direct reading to confirm important entries.
This source inventory gives you a stable reference before the comparison. It is especially useful when names or codes appear more than once.
Compare the corresponding target section
Then ask:
Compare this checked source inventory with the corresponding translation. Show the source value, target value, and any difference. Separate a possible error from a formatting difference. If the source itself is ambiguous, mark it for clarification. Do not silently correct the translation yet.
Use a table like this:
| Detail | Source | Translation | Review decision |
|---|---|---|---|
| Part code | Exact code | Exact code found | Match or check |
| Delivery date | Exact wording | Exact wording found | Confirm meaning |
| Quantity | Number and unit | Number and unit found | Match or check |
| Condition | Relevant phrase | Corresponding phrase | Meaning preserved? |
The sample fields are a structure, not findings about your document. Fill decisions only after checking the actual text.
Handle dates and numbers carefully
Different languages use different date formats and decimal separators. A format change may be correct, but the value must remain the same.
For ambiguous dates such as 03/04, do not ask the model to choose silently. Confirm the intended date from the source owner, then use the month in words where appropriate.
Check whether a comma is a thousands separator or a decimal separator. Verify currency and units directly. Do not let the model convert measurements unless conversion is part of the task and you independently check the calculation.
Times may also need a time zone. If the source does not specify one and it matters, ask for clarification rather than inferring it from the language.
Check names and identifiers separately
Names may have approved spellings in another script or language. Use an authoritative spelling supplied by the person or organisation where available. Do not accept a new spelling merely because it looks natural.
Product codes, account references, file paths, and serial numbers usually need exact character preservation. Compare them directly. Watch for similar-looking letters and digits, spaces, and hyphens.
If you supply a name list, ask the model to use it as a check, not as permission to replace every similar word. A word can be a name in one sentence and an ordinary term in another.
Inspect conditions and negative statements
Correct numbers do not make the whole translation correct. Ask for a separate pass on words that affect the action:
Compare the source and translation for negative statements, exceptions, proposed versus confirmed dates, and words expressing obligation or possibility. Quote the corresponding phrases and flag any change in strength or meaning.
Check those passages with a fluent reviewer if the message has significant consequences. “May deliver,” “will deliver,” and “must deliver” are different commitments. A local model can help find a possible mismatch; it cannot certify the interpretation.
Back-translation may reveal a problem, but it can also reproduce the same misunderstanding. Use it as a diagnostic, not as proof.
Correct, then check the final file
Make approved corrections in your normal document tool. Repeat the exact-detail check on the final version, especially if another editing pass changed the wording.
Record unresolved questions rather than forcing a clean result. Keep the source, target version, glossary, and reviewed differences together so later updates can use the same basis.
Download OGAD and compare one short translated section. Start with names, dates, and numbers, then check the conditions around them. That gives you a practical review process with a clear route back to the source.