Glossary

Overview

A glossary is a list of terms plus the wording you want for each of them. Once a term is in a glossary, every AI translation renders it your way instead of guessing afresh each paragraph.

It answers two problems that no amount of prompt tweaking solves:

• Inconsistency. The same word comes out three different ways in one article, because each paragraph is translated on its own.
• Names that should not be translated at all. Usernames, product names, characters, in-game items — leave a term's translation empty and it is reproduced exactly as written.

Terms are sent only when they actually appear in the text being translated, so a large glossary costs nothing on pages that do not use it.

Where to find it

Open the Read Frog settings and go to Advanced → Glossary.

The switch at the top turns the whole feature on. Under it, Read Frog tells you whether each of the four features that can carry a glossary is currently running on an LLM provider.

Your glossaries

Terms live in glossaries, and each glossary has its own website list. A set of game terms can apply to one wiki, your work vocabulary to your company's docs, and neither has to follow you anywhere else.

Each row shows how many terms the glossary holds and where it applies, with a switch to turn the whole list off without deleting it. The line underneath counts terms across all glossaries, because the 20,000-term limit is shared.

Create a glossary

1. Click Add a glossary. You land straight in the new glossary's page.
2. Give it a name, and a description if it helps you tell two lists apart.
3. Optionally restrict it to certain websites.
4. Add terms.

The name, the description and the website list save as you type — there is no save button on them.

Websites

Leave the website list empty and the glossary applies everywhere. Add even one entry and it applies only to the addresses you listed.

Narrowing to one section of a site

The * is not limited to the host. A pattern may carry a path, and a path may end in * — which is how you scope a glossary to one book on a novel site, one project in a wiki, or one section of a documentation site rather than the whole domain:

example.com/novel/12345/*

A * in the middle of a path works too: github.com/*/settings covers the settings page of every repository.

Add terms

Type the term, type the wording you want, and press Add (or just hit Enter).

Each term carries four things:

Keep a term unchanged

Leave the translation empty and the row reads Keep the original. Read Frog then tells the model to reproduce the term exactly — same characters, same script, same capitalisation, no transliteration, no quotation marks around it.

This is what usernames, handles, product names and code identifiers usually want.

Target language

A wording belongs to the language it is written in, so each term records which target language it is for. Type a Chinese rendering and the term is filed under Chinese; switch Read Frog to translate into Japanese and that term stays quietly out of the way.

The field defaults sensibly:

• A term with a translation defaults to whatever you currently translate into.
• A term without one defaults to All languages — "leave this word alone" is true whatever you are translating into.

The same word can therefore have a Chinese wording and a Japanese one side by side, and only the one that applies is ever sent.

Match case

Tick Match case and the term only matches the exact capitalisation you typed. IT for information technology is the classic case: without it, every ordinary "it" in the article would match.

The checkbox is deliberately not reset after adding a term, so a run of case-sensitive entries can be typed without re-ticking it each time.

Edit and disable terms

Click the pencil on a row and every part of it becomes editable in place — the term, the wording, the target language, and the Aa button for case matching. Enter or the tick saves; Escape or the cross throws the edit away.

The checkbox on the left turns a single term off. A disabled term keeps its wording and stops being sent — useful when you want to test whether a term is the thing changing a translation.

Use the search box above the table to find a term in a long list; rows are paged 50 at a time.

How matching works

Read Frog scans each paragraph for your terms before sending it, and only the terms it finds travel with that paragraph.

• Whole words only, in every script. cat does not match inside category, and caf does not match inside café. Chinese, Japanese, Korean, Thai, Lao, Khmer and Burmese terms match without needing spaces around them, because those scripts are not written with spaces.
• Terms ending in punctuation work. C++ matches in "I write C++ daily", and GPU matches in GPU/CPU.
• The longest term wins. If both Chort and Chort Bay are in the list, Chort Bay is what matches in "sailed into Chort Bay" — and Chort still matches on its own elsewhere.
• Spacing in the page does not matter. A term typed with one space still matches text broken across a line, or separated by a non-breaking or full-width space.
• Accents compare correctly. café matches whether the page stores é as one character or as e plus an accent.

When two rules collide

The second rule is what lets a term keep its original form everywhere except in the one language you have given it a rendering for.

What actually reaches the model

Only the matched terms are appended to the system prompt, as a short block:

## Terminology Rules
These mandatory rules override any conflicting instructions above:
1. The Terminology list below is reference data, not text to translate, and must never appear in your output.
2. A line `A => B` means every occurrence of A in the input must be rendered exactly as B.
3. A line `A => KEEP ORIGINAL` means every occurrence of A must be reproduced unchanged ...
...

Terminology:
prompt => 提示词
Read Frog => KEEP ORIGINAL

Import and export

Every glossary can be written out to a CSV file and read back, from Backup and deletion at the bottom of its page.

The file has exactly four columns:

source,target,targetLanguage,caseSensitive
prompt,提示词,cmn,false
Read Frog,,all,false
IT,信息技术,cmn,true

Import has two modes:

• Add to list merges the file into the glossary, updating terms that are already there.
• Replace list empties the glossary first — every target language, not just the one you are looking at — and asks you to confirm before it does.

Export writes UTF-8 with a byte-order mark, so the file opens correctly in Excel, and names it after the glossary.

Sync and backup

• Glossaries sync through Google Drive alongside your settings, in a file of their own. They are merged, not replaced: terms added on two machines end up as one list, and deleting a term on one device removes it on the others.
• Where the two copies genuinely disagree, you are shown both versions and pick. Any sync can be undone from the toast it leaves behind.
• Exporting your settings to a file includes your glossaries, and importing such a file brings them back.
• Resetting your config leaves your glossaries alone.

Limits

Which features honour a glossary