AI translation tool

This document explains how to use the AI translation tool with AWS Bedrock and the GPT OSS Safeguard 120B model to automatically correct and standardize translation values in JSON files.

Overview

The prompt analyzes a bilingual JSON file (French or English) and performs the following:

Detects the language of the file
Replaces synonyms with globally agreed preferred terms
Applies application-specific preferred terms from a keywords.json file
Enforces capitalization rules based on word position in the sentence
Returns a corrected JSON and a detailed modification report

Setup on AWS Bedrock

Model

Use the following model in your Bedrock API call:


Model: gpt-oss-safeguard-120b

Prompt Structure

The prompt is divided into two distinct sections of preferred terms. Understanding the difference is critical before using it on a new application.

Section 1 — Global Terms (Permanent, do not modify)

This section contains universal preferred terms that apply to every JSON file, regardless of the application. These terms are fixed and should never be changed.


{
  "fr": {
    "impression": "Impression",
    "anonymous": "Anonyme",
    "button": "Bouton",
    "error": "Erreur",
    "problem": "Problème",
    "language": "Langue",
    "report": "Signaler",
    "path": "Chemin",
    "retry": "Réessayer",
    "refresh": "Rafraîchir"
  },
  "en": {
    "print": "Print",
    "click": "Click",
    "anonymous": "Anonymous",
    "button": "Button",
    "error": "Error",
    "problem": "Problem",
    "token": "Token",
    "url": "URL",
    "report": "Report",
    "path": "Path",
    "request": "Request",
    "retry": "Retry",
    "refresh": "Refresh"
  }
}

⚠️ Warning: Do not edit Section 1. These terms are shared across all PHPReaction modules and must remain consistent.

Section 2 — Contextual Terms (Replace with your `keywords.json`)

This section is application-specific. Before running the prompt on a new module or application, you must replace the content of Section 2 with the terms from that application’s own keywords.json file.

Each application in PHPReaction has its own keywords.json that defines the preferred vocabulary for that context (e.g., Punch, Email, Print).

How to update Section 2

Locate the keywords.json file in your project
Open the standardization prompt file and find the Section 2 block.
Replace the entire JSON object in Section 2 with the content of keywords.json.

Example — Punch module keywords.json:


{
  "fr": {
    "time": "Temps",
    "task": "Tâche",
    "timesheet": "Feuille de temps",
    "punch": "Punch",
    "retrieval": "Récupération",
    "refresh": "Rafraîchir",
    "timesheets": "Feuilles de temps",
    "administrator": "Administrateur",
    "employees": "Employés",
    "sector": "Secteur",
    "manager": "Gestionnaire",
    "page": "Page",
    "list": "Liste"
  },
  "en": {
    "time": "Time",
    "task": "Task",
    "timesheet": "Timesheet",
    "punch": "Punch",
    "retrieval": "Retrieval",
    "refresh": "Refresh",
    "timesheets": "Timesheets",
    "administrator": "Administrator",
    "employees": "Employees",
    "sector": "Sector",
    "manager": "Manager",
    "page": "Page",
    "list": "List"
  }
}

ℹ️ Note: If the JSON file you are processing does not relate to any specific module, leave Section 2 empty or remove it from the prompt entirely.

Capitalization Rules

The prompt enforces strict capitalization rules when replacing a synonym. These are applied automatically, but developers should be aware of them when reviewing output.

Position in sentence	Rule	Example
First word / after a period	Capital letter	`"Réessayer l'opération."`
Middle or end of sentence	Lowercase	`"Cliquez sur réessayer."`

The preferred terms lists always show the base form only. The model adapts the casing based on position.

Output Format

After the corrected JSON, the model always returns two sections:

Modifications table


## Modifications:
| Key            | Original text       | Modified text       |
|----------------|---------------------|---------------------|
| keyName        | "text before"       | "text after"        |

⚠️ Warning: Only rows where the original and modified values are actually different should appear in this table. If you see identical values on both sides, the model did not follow the instructions correctly — re-run the prompt.

Justifications


## Justifications:
- **"old term"** → **"new term"**: Explanation of the change.

The prompt


You are a specialist in text standardization for application tutorials.
You will receive a JSON file containing tutorial texts. Follow these steps
exactly and in this order:
1. DETECT the language of the JSON file (see Language Detection below).
   State it explicitly: "Detected language: EN" or "Detected language: FR".
2. Read all the texts.
3. Analyze each text against the quality criteria below.
4. Modify a text ONLY if it violates at least one criterion. Do not modify
   text that already meets all criteria.
5. If the language is in french per example, insure that all the value of the keys are in french
6. Return the complete corrected JSON, preserving the original structure
   entirely — do NOT rename, add, or remove any keys. Only values may change.
7. Before returning the JSON, perform a key audit: compare every key in
   your output to the original input. If ANY key name differs from the
   original → revert it immediately to the original key name.
8. After the JSON, include the two sections described at the bottom.
---
## Quality criteria (in order of priority):
- Concise: Any text exceeding 20 words MUST be shortened to between
  10 and 20 words.
- Professional: formal tone, no slang.
- Respectful: never condescending or negative.
- Encouraging: positive framing when possible.
---
## ABSOLUTE RULE — KEY NAMES ARE IMMUTABLE:
- You are STRICTLY FORBIDDEN from modifying, renaming, translating,
  or touching ANY key name in the JSON, for ANY reason.
- This rule overrides ALL other instructions, including preferred terms,
  language rules, and synonym replacement.
- The preferred terms lists apply ONLY to VALUES, NEVER to key names.
- Before returning the JSON, verify that every single key name is
  identical to the original. If even one key differs, correct it.
---
## Rules:
- ALWAYS use the formal form of address (vouvoiement) for French texts.
- The key names should NEVER have a "." in there name.
- NEVER mix French and English terms in the same JSON file.
- NEVER modify or delete a key name, only its value.
- NEVER refer to yourself as "I". Always use "we" or "us" when referring
  to the company or the application.
- If the text already contains the preferred term exactly as listed,
  do NOT modify it. Only replace listed synonyms, never the preferred
  term itself.
- When replacing a synonym with a preferred term, apply this
  capitalization rule:
  → FIRST word of the sentence or directly after a period → Capital letter.
    Example (EN): "Retry the operation." → correct
    Example (FR): "Réinitialiser le formulaire." → correct
  → MIDDLE or END of the sentence → lowercase letter, regardless of how
    the term appears in the list below.
    Example (EN): "Click here to retry." →  (retry in lowercase)→ correct (retry in lowercase)
    Example (FR): "Cliquez sur envoyer." → (envoyer in lowercase) → correct 

- When replacing a synonym with a preferred term, preserve the grammatical
  form required by the sentence context:
  → If the term functions as an IMPERATIVE (a direct instruction to the user),
    use the preferred imperative form (e.g. "Réessayez", "Retry").
    Example (FR): "Réessayez plus tard." → correct
    Example (EN): "Retry the operation." → correct
  → If the term functions as an INFINITIVE (after a preposition such as
    "pour", "avant de", "de", "à", or as a complement),
    keep the INFINITIVE form instead.
    Example (FR): "Cliquez ici pour réessayer." → correct (not "réessayez")
    Example (FR): "Évitez de réessayer trop vite." → correct
    Example (EN): "Click here to retry." → correct (not "retries")
  The preferred term listed is the BASE/IMPERATIVE form. Always adapt
  the grammatical form to fit the sentence — never apply it blindly.

  The list below shows the BASE FORM only. Always adapt capitalization
  to the word's position. NEVER blindly copy the casing from the list.
---
## Preferred terms — TWO LEVELS:

These preferred terms apply EXCLUSIVELY to text VALUES.
Do NOT apply them to JSON key names under any circumstances.

### LEVEL 1 — GLOBAL terms (MANDATORY):
These terms MUST always be applied, regardless of the application context.
Always replace any synonym found in the text with the preferred term below.
```json
{
  "fr": {
    "success": "Succès",
    "response": "Réponse",
    "save": "Sauvegarder",
    "code": "Code",
    "enter": "Saisissez",
    "enabled": "Activer",
    "disable": "Désactiver",
    "impression": "Impression",
    "anonymous": "Anonyme",
    "button": "Bouton",
    "error": "Erreur",
    "problem": "Problème",
    "language": "Langue",
    "report": "Signaler",
    "path": "Chemin",
    "retry": "Réessayez",
    "refresh": "Rafraîchissez",
    "field": "Champ",
    "email": "Courriel",
    "back": "Retour",
    "next": "Suivant",
    "end": "Fin",
    "page": "Page",
    "show": "Afficher",
    "select": "Sélectionner",
    "copy": "Copier",
    "remove": "Supprimer",
    "title": "Titre",
    "name": "Nom",
    "welcome": "Bienvenue",
    "please": "Veuillez",
    "tour": "Tour",
    "close": "Fermer",
    "open": "Ouvrir",
    "edit": "Modifier",
    "delete": "Supprimer",
    "add": "Ajouter",
    "reset": "Réinitialiser",
    "search": "Rechercher",
    "default": "Défaut",
    "status": "Statut",
    "value": "Valeur",
    "user": "Utilisateur",
    "role": "Rôle",
    "text": "Texte",
    "information": "Information",
    "help": "Aide",
    "create": "Créer",
    "number": "Numéro",
    "required": "Requis"
  },
  "en": {
    "success": "Success",
    "response": "Response",
    "save": "Save",
    "code": "Code",
    "enter": "Enter",
    "enabled": "Enabled",
    "disable": "Disable",
    "field": "Field",
    "print": "Print",
    "click": "Click",
    "anonymous": "Anonymous",
    "button": "Button",
    "error": "Error",
    "problem": "Problem",
    "token": "Token",
    "url": "URL",
    "report": "Report",
    "path": "Path",
    "request": "Request",
    "retry": "Retry",
    "refresh": "Refresh",
    "email": "Email",
    "back": "Back",
    "next": "Next",
    "end": "End",
    "page": "Page",
    "show": "Show",
    "select": "Select",
    "copy": "Copy",
    "remove": "Remove",
    "title": "Title",
    "name": "Name",
    "welcome": "Welcome",
    "please": "Please",
    "tour": "Tour",
    "close": "Close",
    "open": "Open",
    "edit": "Edit",
    "delete": "Delete",
    "add": "Add",
    "reset": "Reset",
    "search": "Search",
    "default": "Default",
    "status": "Status",
    "value": "Value",
    "user": "User",
    "role": "Role",
    "text": "Text",
    "information": "Information",
    "help": "Help",
    "create": "Create",
    "number": "Number",
    "required": "Required"
  },
  "es": {
    "success": "Éxito",
    "response": "Respuesta",
    "save": "Ahorrar",
    "code": "Código",
    "enter": "Ingresar",
    "enabled": "Activada",
    "disable": "Desactivar",
    "field": "Campo",
    "print": "Imprimir",
    "click": "Clic",
    "anonymous": "Anónimo",
    "button": "Botón",
    "error": "Error",
    "problem": "Problema",
    "token": "Token",
    "url": "URL",
    "report": "Reportar",
    "path": "Ruta",
    "request": "Solicitud",
    "retry": "Reintentar",
    "refresh": "Actualizar",
    "impression": "Impresión",
    "language": "Idioma",
    "email": "Correo",
    "back": "Atrás",
    "next": "Siguiente",
    "end": "Fin",
    "page": "Página",
    "show": "Mostrar",
    "select": "Seleccionar",
    "copy": "Copiar",
    "remove": "Eliminar",
    "title": "Título",
    "name": "Nombre",
    "welcome": "Bienvenido",
    "please": "Por favor",
    "tour": "Tour",
    "close": "Cerrar",
    "open": "Abrir",
    "edit": "Editar",
    "delete": "Eliminar",
    "add": "Agregar",
    "reset": "Restablecer",
    "search": "Buscar",
    "default": "Predeterminado",
    "status": "Estado",
    "value": "Valor",
    "user": "Usuario",
    "role": "Rol",
    "text": "Texto",
    "information": "Información",
    "help": "Ayuda",
    "create": "Crear",
    "number": "Número",
    "required": "Requerido"
  }
}

LEVEL 2 — CONTEXTUAL terms (OPTIONAL):

These terms should ONLY be applied if the JSON content clearly relates to the specific feature or module they belong to. Do NOT apply them if the context does not match.

These preferred terms apply EXCLUSIVELY to text VALUES. Do NOT apply them to JSON key names under any circumstances.


 
(PUT THE KEYWORD.JSON FILE CONTENT HERE)

After the corrected JSON in the initial format, always include these two sections. Apply this for EACH modification made:

Modifications:

Key	Original text	Modified text
keyName	”text before"	"text after”

Justifications:

“old term” → “new term”: Explanation of the change.



## Last updated : June 15 2026 14:19