Make a Mixed-Language Revision Sheet Consistent
A cleaned bilingual revision sheet with one consistent term policy, unchanged mathematics, complete coverage, and a switch log for every retained English term.
Works on any free AI · Best tool: Any AI chat (ChatGPT, Claude, Gemini)
✅ How to use this effectively
- 1. Define the term policy.
- 2. Lock all maths and assessment tokens.
- 3. Review every language switch.
- 4. Compile only after the log is approved.
🔧 If it is not right, reply with this: If terminology varies, apply the approved glossary globally and list every intentional exception instead of silently mixing synonyms.
THE PROMPT
ROLE: Act as a bilingual consistency editor for mathematics revision material.
CONTEXT: Standardise [MIXED-LANGUAGE DRAFT] under [TERM POLICY] for [CLASS OR EXAM].
INPUTS — FILL EVERY PLACEHOLDER:
- [MIXED-LANGUAGE DRAFT]
- [TERM POLICY]
- [CLASS OR EXAM]
- [TERMS TO RETAIN IN ENGLISH]
SOURCE-BOUND TOOL FACTS AND EXACT URL WHITELIST:
- [OVERLEAF] Whitelist: https://www.overleaf.com/docs?encoded_snip={PERCENT_ENCODED_LATEX}. Overleaf requires a free account and sign-in before the imported project opens. Use pdflatex for the stated school-safe package set; use xelatex with fontspec only for multilingual documents. If the encoded URL exceeds 6,000 characters, output the full source plus manual paste steps instead of a broken link.
- [CODECOGS] Whitelist: https://latex.codecogs.com/png.image?{PERCENT_ENCODED_LATEX}. CodeCogs renders one equation image, not a document. Start permanent classroom PNGs with the encoded form of \dpi{150}, keep the URL short, and tell the teacher to download rather than hotlink it.
DO THIS:
1. Inventory every language switch, formula, placeholder, mark, number, unit, and section label.
2. Lock all mathematical and assessment tokens before editing prose.
3. Apply [TERM POLICY] consistently and retain only the specified English terms.
4. Preserve every paragraph, example, warning, and numbered step without summarising.
5. Produce a switch log and source-to-output coverage audit.
6. Generate XeLaTeX/fontspec output for Overleaf with free-login, XeLaTeX, font fallback, and manual-paste instructions.
WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Keep x^2-9=0 and the approved term worksheet unchanged while standardising the rest.
Expected result or check target: The formula and retained term stay exact, while all other terminology follows one policy.
check this yourself
CHECK → https://latex.codecogs.com/png.image?x%5E2-9%3D0
(paste-fallback: x^2-9=0)
Encoding note: The caret and equals sign decode from %5E and %3D to the exact locked equation.
OUTPUT FORMAT:
1. Language Inventory — all switches and variants
2. Token Lock — placeholders, notation, marks, and numbering
3. Clean Revision Sheet — complete standardised text
4. Switch Log — retained English terms and reasons
5. Coverage Audit — source section to output section
6. Overleaf Package — XeLaTeX source and fallback
QUALITY AND TOOL GUARDRAILS:
- Preserve every placeholder, notation token, number, mark value, item label, and paragraph.
- Do not summarise, delete, or reorder content while standardising language.
- Overleaf requires free login; multilingual output uses XeLaTeX and fontspec with a fallback font, never a guaranteed installed font.
- CodeCogs renders individual equations only and cannot create the whole revision sheet.
- Do not replace teacher-approved English terms unless [TERM POLICY] explicitly requires it.
- Copy every [PLACEHOLDER IN SQUARE BRACKETS] character-for-character in every template, code block and translated variant.
- Never output a desmos.com URL with parameters, a mathsolver.microsoft.com URL, an invented GeoGebra material ID, an invented DIKSHA code, an invented Khan topic path, or an unlisted quiz or simulation slug.
- Never describe an AI answer as verified. Every external check must be labelled “check this yourself” for the teacher or student to inspect personally.
- Do not invent exam facts, source citations, marks distributions, tool IDs or inaccessible links. Separate mathematical proof from computational checking.
=== TOOL-LINK OUTPUT CONTRACT — follow every rule exactly ===
1. You may output clickable links ONLY to: wolframalpha.com/input?i= · symbolab.com/solver?query= ·
geogebra.org/graphing|geometry|3d|cas?command= · math.stackexchange.com/search?q= · oeis.org/search?q= ·
artofproblemsolving.com/community/q1_ · khanacademy.org/search?page_search_query= ·
overleaf.com/docs?encoded_snip= · latex.codecogs.com/png.image? · docs.google.com/forms/...viewform?usp=pp_url
(Forms only with entry.N IDs I paste in) · plus any URL I give you or that appears in this prompt's whitelist table.
2. NEVER output: desmos.com links with query strings (they load blank), invented geogebra.org/m/ IDs, Khan topic
URLs, DIKSHA dial codes, Wolfram quiz/demo slugs not in my table, or mathsolver.microsoft.com (dead site).
3. Write queries in plain calculator syntax (x^2, sqrt(x), pi, 3/4) — never LaTeX — EXCEPT Overleaf and CodeCogs
payloads, which are LaTeX.
4. Percent-encode the query part: space→%20, +→%2B, ^→%5E, =→%3D, [→%5B, ]→%5D; in LaTeX payloads also
\→%5C, {→%7B, }→%7D, %→%25, #→%23, &→%26, newline→%0A. GeoGebra ?command= exception: encode ONLY + as %2B;
leave ( ) = ^ ; as typed.
5. One link per line, formatted exactly: CHECK → <full raw URL> (no markdown brackets, nothing after the URL).
6. Directly below every link, print: (paste-fallback: <the un-encoded query or commands>)
7. Before printing any link, silently decode your own URL and confirm it reproduces the query character-for-character;
rebuild it if not. If a URL would exceed 1,800 characters (Overleaf: 6,000), print only the paste-fallback.
8. Label every link "check this yourself" — never claim the link proves your answer is correct.
9. On phones these links must be opened in a browser, not an installed app — say this once at the end.