Cadre d'évaluation et d'optimisation de l'ingénierie des prompts

Diagnostic Analysis * Strengths: The prompt is clear in its core instruction to translate into French while preserving specific elements. It explicitly lists what must be preserved (placeholders, brand names, param flags, code/JSON keys, quoted text) and sets structural rules (1:1, no em-dashes, preserve diacritics). The output constraint (only translation, no preamble) is unambiguous. * Weaknesses: The prompt does not specify the source language, though it implies English-to-French. It does not define how to handle untranslatable or ambiguous terms beyond the listed categories. It lacks guidance on tone (formal/informal) or register. It does not address edge cases like mixed-language text, nested placeholders, or conflicting preservation rules (e.g., a brand name that is also a common French word). * Hidden assumptions: The source text is in English; the target is standard French (not regional variants like Canadian French); placeholders follow the [X]/{x} pattern exactly; quoted text is in-image and should be kept verbatim; the translation should be literal rather than localized. * Misinterpretation risks: "Preserve VERBATIM" could be over-applied to all text, not just listed categories. "Quoted in-image text" might be confused with quotation marks in the body text. The instruction to avoid em-dashes could lead to replacing them with hyphens or commas inconsistently. * Unstated dependencies: The prompt assumes the user has a source text with the specified elements; it does not define what to do if no placeholders exist or if the text is entirely code. It assumes the translator has sufficient context to translate technical terms correctly. Scope Definition * In-scope: Translation of the provided text into French; preservation of all listed elements (placeholders, brand/model names, param flags, code/JSON keys, quoted in-image text); maintenance of original structure (1:1); use of hyphens instead of em-dashes; preservation of diacritics. * Out-of-scope: Translation of non-listed elements (e.g., general prose) is not exempt from translation; no localization or cultural adaptation; no explanation or commentary; no reformatting beyond the 1:1 structure. * Boundary conditions: The prompt applies only to the given text; if the text contains elements outside the listed categories, they must be translated normally. If a placeholder conflicts with a brand name (e.g., [X] is a brand), the placeholder takes precedence. If quoted text contains placeholders, both are preserved. Precision Rewrite Translate the provided text into French. Follow these rules strictly: 1. Preserve verbatim all placeholders in the format [X] or {x}, including brackets and braces. 2. Preserve verbatim all brand and model names (e.g., Nike, iPhone 15). 3. Preserve verbatim all parameter flags (e.g., --ar, 85mm, 4K, 24fps). 4. Preserve verbatim all code/JSON keys and structure (e.g., "key": "value"). 5. Preserve verbatim all text enclosed in quotation marks that represents in-image text (e.g., "Hello World"). 6. Maintain a 1:1 structural correspondence: each sentence, paragraph, or line in the source must map to one in the target. 7. Use hyphens ( - ) instead of em-dashes (-) in the translation. 8. Preserve all diacritical marks in the source text (e.g., é, ü, ç) in the translation. 9. Translate all other text (prose, descriptions, non-listed terms) into natural, standard French. 10. Output only the translation. Do not include any preamble, explanations, or formatting outside the translated text. Alternative Variants * Version A (Minimal): Translate to French. Preserve placeholders ([X], {x}), brand names, param flags (--ar, 85mm, 4K, 24fps), code/JSON keys, and quoted in-image text verbatim. Keep structure 1:1. Use ' - ' not em-dashes. Preserve diacritics. Output only the translation. * Version B (Detailed): Step 1: Identify all placeholders, brand names, param flags, code/JSON keys, and quoted in-image text. Step 2: Translate all other text into French, maintaining the original sentence structure and paragraph breaks. Step 3: Replace translated text into the original structure, ensuring placeholders and preserved elements remain unchanged. Step 4: Replace any em-dashes with hyphens. Step 5: Verify diacritics are intact. Step 6: Output the final translation with no additional text. Stress Test * Failure scenario 1: Source text contains a brand name that is also a common French word (e.g., "Apple" as a fruit vs. brand). Root cause: Ambiguity in preservation rule. Example: "The apple fell" vs. "Apple released a new phone." The prompt does not clarify if brand names are always preserved regardless of context. Mitigation: Add a rule that brand names are preserved only when clearly used as brand identifiers (e.g., capitalized, in product context). * Failure scenario 2: Source text has nested placeholders like "[{x}]" or "{[X]}". Root cause: The prompt specifies formats but not nesting. Example: "Value: [{param}]" - the translator might preserve only the inner or outer brackets. Mitigation: State that nested placeholders are preserved in full, including all brackets and braces. * Failure scenario 3: Quoted text is not in-image but a direct quote in prose. Root cause: "Quoted in-image text" is ambiguous. Example: He said, "Go now." - the translator might preserve "Go now" verbatim, but it should be translated. Mitigation: Clarify that only text explicitly marked as in-image (e.g., in a caption or screenshot description) is preserved; regular quotes are translated. * Failure scenario 4: Em-dash appears in a placeholder or code key. Root cause: The rule to replace em-dashes conflicts with preservation rules. Example: "--ar" is a param flag, but the rule might replace the double hyphen. Mitigation: Specify that preservation rules take precedence over the em-dash rule; only em-dashes in translated prose are replaced. * Failure scenario 5: Source text contains diacritics in a placeholder (e.g., {café}). Root cause: The rule to preserve diacritics might be over-applied, but placeholders must be verbatim. Example: {café} should stay as is, but the translator might alter it. Mitigation: Clarify that diacritics in preserved elements are kept as-is, and diacritics in translated text are preserved from the source. Final Optimized Prompt Translate the provided text into French. Apply these rules in order of priority: 1. Preserve verbatim all placeholders in the format [X] or {x}, including nested forms like [{x}] or {[X]}. Do not translate or alter any characters within these. 2. Preserve verbatim all brand and model names (e.g., Nike, iPhone 15) when used as proper nouns (capitalized or in product context). If a name is used generically (e.g., "apple" as fruit), translate it normally. 3. Preserve verbatim all parameter flags (e.g., --ar, 85mm, 4K, 24fps), including any hyphens or symbols. 4. Preserve verbatim all code/JSON keys and structure (e.g., "key": "value"), including quotes, colons, and brackets. 5. Preserve verbatim all text explicitly marked as in-image (e.g., in a description like "the image shows 'Hello World'"). Do not preserve regular quoted speech or prose; translate those normally. 6. Maintain a 1:1 structural correspondence: each sentence, paragraph, or line in the source must map to one in the target. 7. Use hyphens ( - ) instead of em-dashes (-) in the translated prose. Do not alter em-dashes within preserved elements (placeholders, flags, code). 8. Preserve all diacritical marks in the source text (e.g., é, ü, ç) in the translation, including within preserved elements. 9. Translate all other text into natural, standard French, maintaining the original tone and register. 10. Output only the translation. Do not include any preamble, explanations, or formatting outside the translated text. Acceptance Criteria The final prompt MUST: * Be explicit and unambiguous: Yes, it defines priority order and clarifies ambiguous cases (brand names, nested placeholders, quoted text). * Clearly define output format and structure: Yes, it specifies 1:1 mapping and output-only translation. * Minimize interpretation variance: Yes, it provides concrete examples and priority rules. * Include all necessary constraints (tone, scope, format, limits): Yes, it covers tone (natural French), scope (translation of non-listed elements), format (1:1), and limits (no extra output). * Handle edge cases or explicitly bound them: Yes, it addresses nested placeholders, generic brand names, regular quotes, and em-dashes in preserved elements. * Be reusable and self-contained: Yes, it can be applied to any text with the specified elements without additional context. Evaluation Rubric (Score 1–5 for each with brief justification) * Clarity: 5 - The prompt is direct, with numbered rules and examples. * Specificity: 5 - It defines exact formats, priority order, and edge cases. * Determinism: 4 - The priority order reduces variance, but some judgment is needed for brand name context (generic vs. proper noun). * Robustness (edge cases): 5 - It explicitly handles nesting, generic names, quotes, and em-dash conflicts. * Output Control: 5 - It strictly limits output to the translation and defines structure. Assumption Policy * Assumptions made: Source text is in English; target is standard French; placeholders are literal strings; "in-image text" is explicitly marked in the source; the translator has basic knowledge of French grammar and vocabulary. * Missing information: The prompt does not specify the source language (assumed English) or the exact context of "in-image text" (assumed marked). If these are incorrect, the user should clarify. * Proceeding: The prompt proceeds with these assumptions, which are stated for transparency. Output Constraints * Expected output length: Same as source text length (1:1 structure). * Format: Plain text, no bullets, no headers, no additional commentary. * Avoid unnecessary verbosity: The translation should be concise and natural, matching the source's style. Default Behaviors * If multiple valid interpretations exist (e.g., brand name vs. generic word), choose the most conservative: preserve the name only if clearly a proper noun; otherwise translate. * If uncertainty remains (e.g., whether text is in-image), state the assumption before proceeding (but in this case, the prompt assumes it is marked). * Prefer clarity over brevity: The prompt is detailed to ensure reliability, even if longer. Self-Check and Refinement * Verify the final prompt meets ALL acceptance criteria: Yes, it is explicit, defines format, minimizes variance, includes constraints, handles edge cases, and is reusable. * Identify any remaining ambiguity: The term "in-image text" still relies on the source marking it; if not marked, the translator must infer. This is a minor risk. * Refine once more: Add a note: "If in-image text is not explicitly marked, treat all quoted text as regular prose and translate it." This closes the gap. * Corrected final version: The prompt above is updated with this note in rule 5: "If in-image text is not explicitly marked, treat all quoted text as regular prose and translate it."