Translation History

Translation History records the local cache of text translations. Every successful text translation — main window, mini window, selection translation, or the translation that follows a screenshot OCR — is written here. It serves two purposes: repeated translations resolve instantly, and past results stay searchable.

How the Cache Works

• Hit condition: same engine + same language pair + identical source text
• A hit returns the stored translation without calling the service, and without spending credits
• With "Auto detect", the key is "auto + target language + source text + engine"
• Only misses actually call the engine; the result is cached immediately on success

Interface

Record List

Each row shows the index, source text (with a language tag; auto when detected), target text (with its language tag), engine, and timestamp.

Search and Filters

• Keyword: searches source or target text, with matches highlighted
• Source language: "Auto detect (auto)" or a specific language
• Target language
• Engine: options come from the current statistics
• Changing a filter requires pressing Search or Enter

Statistics

Translation statistics (top right) shows:

• Records for today / this week / this month / all time
• Total source characters
• Active days
• Distribution by engine, source language, target language, language pair, day and month

Clearing the Cache

Clear all cache deletes every text translation record — including records outside the current filter — and cannot be undone. Afterwards, repeated text calls the service again and the statistics reset to zero.

Storage and Privacy

1. Data lives in the local SQLite database and travels with Data backup
2. Nothing expires automatically; records remain until you clear them
3. Records contain the source and target text — clear the cache after handling sensitive content

FAQ

Q: Can I export the history?

A: Not currently — no text, Excel or TMX export. To keep content as reusable assets, maintain it in a memory via TMX or Excel import.

Q: Does history take much space?

A: Each record stores only the two texts plus a little metadata. Check the record count in the statistics and clear when needed.

Q: Why isn't a translation I just did in the list?

A: Check that it succeeded (failures are not stored). Note that project segments never enter the text cache, so they never appear here.

Q: Can I sync history across devices?

A: There is no cloud sync. Export the database via Settings → Network & advanced → Data backup and import it on the other device.

Q: Does clearing the cache affect project translations?

A: No. Only the text translation cache is removed; projects, files, segment translations, memories and termbases are untouched.

Q: Can history be used as a translation memory?

A: No. They are separate: history is a text cache, while a memory is a structured corpus with language pairs, used for matching and pre-translation inside projects.