<think>
The user wants me to translate this article fragment about negative prompts for AI image generation into French. Let me translate it completely while following the rules:
- Keep all markdown syntax intact
- Keep URLs, image paths, and HTML tags exactly as-is
- Keep code blocks and inline code untranslated
- Keep "GLMImage" untranslated
- Use natural, fluent French expression
- Output only the translated markdown
Let me translate:
"## Negative Prompts for AI Image Generation: Complete Guide"
→ "## Prompts négatifs pour la génération d'images par IA : Guide complet"
"
"
→ Keep the image tag as-is, but I should translate the alt text:
""
"Negative prompts are instructions telling AI image generators what to exclude or avoid in the generated image. They work by steering the model away from unwanted elements — improving quality, fixing common issues, and refining results without rewriting your whole positive prompt."
→ "Les prompts négatifs sont des instructions qui indiquent aux générateurs d'images par IA ce qu'il faut exclure ou éviter dans l'image générée. Ils fonctionnent en orientant le modèle loin des éléments non souhaités — améliorant la qualité, corrigeant les problèmes courants et affinant les résultats sans réécrire l'ensemble de votre prompt positif."
Let me double-check the translation:
-
"Negative prompts" → "Prompts négatifs" (this is the correct technical term in French)
-
"AI image generators" → "générateurs d'images par IA"
-
"generated image" → "image générée"
-
"unwanted elements" → "éléments non souhaités"
-
"improving quality" → "améliorant la qualité"
-
"fixing common issues" → "corrigeant les problèmes courants"
-
"refining results" → "affinant les résultats"
-
"positive prompt" → "prompt positif"
This is a good, natural translation. Let me output it.
</think>
Prompts négatifs pour la génération d'images par IA : Guide complet
Les prompts négatifs sont des instructions qui indiquent aux générateurs d'images par IA ce qu'il faut exclure ou éviter dans l'image générée. Ils fonctionnent en orientant le modèle loin des éléments non souhaités — améliorant la qualité, corrigeant les problèmes courants et affinant les résultats sans réécrire l'ensemble de votre prompt positif.
<think>
I need to translate this blog fragment about negative prompts in AI image generation into natural, fluent French while keeping all markdown syntax intact.
Let me go through it carefully:
- Keep all markdown formatting (headings, lists, bold text, blockquotes, links)
- Keep URLs and paths exactly as-is
- Keep brand name "GLMImage" untranslated
- Use natural French expressions
- Translate completely, no summarizing
Let me translate section by section:
Key Takeaways
= ## Points clés
-
Negative prompts cut down common defects — extra limbs, blurry faces, watermarks, garbled text — by telling the model what to avoid. They work best alongside a strong positive prompt, not as a replacement for one.
= 1. Les prompts négatifs réduisent les défauts courants — membres supplémentaires, visages flous, filigranes, texte corrompu — en indiquant au modèle ce qu'il doit éviter. Ils fonctionnent mieux en complément d'un prompt positif fort, pas en remplacement de celui-ci. -
Target known issues, don't spray. Negatives earn their keep on recurring flaws (bad hands, watermarks, misspelled text). Stacking dozens of unrelated terms confuses the model more than it helps.
= 2. Ciblez les problèmes connus, évitez la dispersion. Les prompts négatifs sont rentables pour les défauts récurrents (mains ratées, filigranes, texte mal orthographié). Empiler des dizaines de termes sans rapport embrouille le modèle plus qu'il ne l'aide. -
The 80/20 rule holds up. Spend most of your effort on a clear, specific positive prompt; use negatives for the ~20% of refinement that fixes specific flaws. Overloading negatives degrades quality.
= 3. La règle des 80/20 s'applique. Concentrez la majeure partie de votre effort sur un prompt positif clair et précis ; utilisez les prompts négatifs pour les ~20% de perfectionnement qui corrigent des défauts spécifiques. Surcharger en prompts négatifs dégrade la qualité.
I'll explore the next part of the translation, focusing on the practical application of AI image generation. The text highlights the accessibility of free image creation through GLMImage, emphasizing its user-friendly approach to generating images without requiring sign-up. The platform automatically applies optimized negative prompts, simplifying the prompt writing process for users.
The translation maintains the original's conciseness while adapting to French linguistic nuances, preserving the core message of easy, no-commitment image generation.
</think>
Points clés
-
Les prompts négatifs réduisent les défauts courants — membres supplémentaires, visages flous, filigranes, texte corrompu — en indiquant au modèle ce qu'il doit éviter. Ils fonctionnent mieux en complément d'un prompt positif fort, pas en remplacement de celui-ci.
-
Ciblez les problèmes connus, évitez la dispersion. Les prompts négatifs sont rentables pour les défauts récurrents (mains ratées, filigranes, texte mal orthographié). Empiler des dizaines de termes sans rapport embrouille le modèle plus qu'il ne l'aide.
-
La règle des 80/20 s'applique. Concentrez la majeure partie de votre effort sur un prompt positif clair et précis ; utilisez les prompts négatifs pour les ~20% de perfectionnement qui corrigent des défauts spécifiques. Surcharger en prompts négatifs dégrade la qualité.
Essayez-le ici même — votre première image est gratuite, sans inscription nécessaire. GLMImage applique une liste négative optimisée derrière chaque flux de travail, ainsi vous rédigez le prompt positif et les exclusions viennent avec la recette.
<think>
The user wants me to translate a blog article fragment about negative prompts into French. Let me analyze what needs to be translated:
- This is a heading "## How Negative Prompts Work"
- Followed by an image with alt text "How Negative Prompts Work"
I need to translate this into natural, fluent French while:
- Keeping markdown syntax intact (## for headings)
- Keeping the image tag as-is
- Keeping "GLMImage" untranslated
- Using native French expression
The heading translates to "Comment fonctionnent les prompts négatifs" - this is a straightforward translation that sounds natural in French.
For the alt text of the image, I should translate it to French as well since it's in the alt attribute.
Let me provide the complete translation:
</think>
Comment fonctionnent les prompts négatifs
<think>
The user wants me to translate this blog fragment into French. Let me go through the rules:
- Keep ALL markdown syntax intact - I need to preserve the heading format, image syntax, tables, bold/italic, etc.
- Keep URLs and image paths exactly as-is
- Keep code blocks and inline code untranslated
- Keep "GLMImage" untranslated
- Use native, fluent French expression
- Output only the translated markdown
Let me translate this:
"The Technical Concept" = "Le concept technique"
"Negative prompts tell the AI model what concepts to avoid during generation." = "Les prompts négatifs indiquent au modèle d'IA les concepts à éviter lors de la génération."
"The model calculates:" = "Le modèle calcule :"
"Generation = Positive Prompt − Negative Prompt" = This is a formula, should I translate the words? I think the formula itself should stay but the words could be translated for French readers... Actually, in technical contexts these terms are often kept in English. But "Generation" could be translated. Let me think... "Génération = Prompt Positif − Prompt Négatif" - I'll translate "Generation" to keep it natural in French.
For the table:
- "Component" = "Composant"
- "Effect" = "Effet"
- "Positive prompt" = "Prompt positif" (or keep as is since it's technical terminology)
- "Add these elements" = "Ajoute ces éléments"
- "Negative prompt" = "Prompt négatif"
- "Exclude these elements" = "Exclut ces éléments"
- "Result" = "Résultat"
- "Combined output" = "Sortie combinée"
Let me also check the URL in the image - it ends with "--en-inline-3-v4.webp" which has "en" for English. I should keep this URL exactly as-is as per rule 2.
Now let me compose the translation:
Le concept technique
Les prompts négatifs guident le modèle d'IA en identifiant précisément les éléments à éliminer durant la création. Le modèle applique une approche soustractive, retirant systématiquement les concepts non souhaités.
La génération émerge d'un équilibre entre prompts positifs et négatifs, où chaque élément est méticuleusement incorporé ou exclu selon des critères spécifiques.
| Composant | Effet |
|---|---|
| Prompt positif | Inclus ces éléments |
| Prompt négatif | Élimine ces éléments |
| Résultat | Production finale |
Je vais adapter la formulation pour la rendre plus naturelle en français, en soulignant l'interaction subtile entre les différents composants.
</think>
Le concept technique
Les prompts négatifs indiquent au modèle d'IA les concepts à éviter lors de la génération. Le modèle calcule :
Génération = Prompt Positif − Prompt Négatif
| Composant | Effet |
|---|---|
| Prompt positif | « Ajouter ces éléments » |
| Prompt négatif | « Exclure ces éléments » |
| Résultat | Sortie combinée |
<think>
I need to translate this table about platform support into French. Let me go through it carefully:
- Keep the markdown syntax (table format, headings)
- Keep all brand names like "GLMImage", "Stable Diffusion", "Midjourney", "DALL-E 3", "FLUX.1" untranslated
- Translate the descriptive text into natural French
- Keep symbols like ✓, ✗, and the dashes as-is
- Keep all other technical terms that are commonly used across languages
Let me translate:
- "Platform Support" → "Prise en charge des plateformes"
- "Platform" → "Plateforme"
- "Negative Prompt Support" → "Support des prompts négatifs"
- "Implementation" → "Implémentation"
- "Built in" → "Intégré" or "Intégrée"
- "Per-workflow negative list applied automatically" → "Liste négative par flux appliquée automatiquement" (but "workflow" is often kept in English in French tech writing, so "par workflow" might be better)
- "Full support" → "Support complet"
- "Dedicated negative prompt field" → "Champ dédié pour les prompts négatifs"
- "Partial" → "Partiel"
- "--no parameter (limited)" → "--no parameter (limité)" - the parameter name stays, the description translates
- "No support" → "Non pris en charge"
- "Must use positive phrasing" → "Nécessite une formulation positive"
- "No native support" → "Pas de support natif"
- "Guidance-distilled; negative prompts are not applied" → "Distillé par guidance ; les prompts négatifs ne sont pas appliqués"
Let me put it all together:
Prise en charge des plateformes
| Plateforme | Support des prompts négatifs | Implémentation |
|---|---|---|
| GLMImage | ✓ Intégré | Liste négative par workflow appliquée automatiquement |
| Stable Diffusion | ✓ Support complet | Champ dédié pour les prompts négatifs |
| Midjourney | Partiel | Paramètre --no (limité) |
| DALL-E 3 | ✗ Non pris en charge | Necessite une formulation positive |
| FLUX.1 | ✗ Pas de support natif | Distillé par guidance ; les prompts négatifs ne sont pas appliqués |
I'll verify the technical terms and ensure consistency with French tech writing conventions. The translation maintains the original table structure while adapting technical terminology to natural French expressions.
For "FLUX.1", I'll keep the technical parameter name --no as is, which is standard practice in technical documentation. The parameter is already in English and typically remains unchanged across languages.
</think>
Prise en charge des plateformes
| Plateforme | Support des prompts négatifs | Implémentation |
|---|---|---|
| GLMImage | ✓ Intégré | Liste négative par workflow appliquée automatiquement |
| Stable Diffusion | ✓ Support complet | Champ dédié pour les prompts négatifs |
| Midjourney | Partiel | Paramètre --no (limité) |
| DALL-E 3 | ✗ Non pris en charge | Doit utiliser une formulation positive |
| FLUX.1 | ✗ Pas de support natif | Distillé par guidance ; les prompts négatifs ne sont pas appliqués |
<think>
I need to translate the heading "## Essential Negative Prompts" into French while keeping the markdown syntax intact.
"## Essential Negative Prompts" should become "## Prompts négatifs essentiels" in French.
- "Essential" = "essentiels" (masculine plural)
- "Negative Prompts" = "Prompts négatifs" (negative prompts is a technical term, I'll keep "prompts" as is since it's commonly used in French)
The output should be just the translated markdown, no preamble, no code fences.
</think>
Prompts négatifs essentiels
<think>
The user wants me to translate a markdown article fragment into French. Let me analyze the content:
- It's about "Universal Quality Improvers" - likely prompts or keywords used in image generation
- There are code blocks with keywords, tables, and formatting
- I need to keep markdown syntax, URLs, code blocks, and brand names intact
- I need to translate the text content into natural French
Let me translate section by section:
-
"### Universal Quality Improvers" → "### Améliorateurs de Qualité Universels"
-
"Use for Most Generations" → "À utiliser pour la plupart des générations"
-
The code block with keywords - these are technical terms that should be translated:
- "blurry" → "flou"
- "low quality" → "basse qualité"
- "distorted" → "distordu"
- "deformed" → "déformé"
- "ugly" → "laid"
- "bad anatomy" → "anatomie incorrecte"
- "poorly drawn" → "mal dessiné"
- "extra limbs" → "membres supplémentaires"
- "disfigured" → "défiguré"
- "low resolution" → "basse résolution"
- "pixelated" → "pixelisé"
- "grainy" → "granuleux"
- "artifacts" → "artéfacts"
- "watermark" → "filigrane"
- "signature" → "signature"
- "text overlay" → "texte superposé"
-
"Breakdown by Purpose" → "Détail par Objectif"
-
Table headers: "Goal" → "Objectif", "Negative Keywords" → "Mots-clés négatifs"
-
Table content needs translation for each category. Quality improvements focus on visual artifacts like blur, resolution, and grain. Anatomy-related keywords address human figure distortions. Aesthetics cover stylistic issues like ugliness and amateurishness. Clutter refers to unwanted elements like watermarks and text overlays. Style encompasses artistic representations that might deviate from realistic rendering.
-
Keywords include "dessin animé" and "anime" for style translations, ensuring precise terminology for visual generation contexts.
</think>
Améliorateurs de Qualité Universels
À utiliser pour la plupart des générations :
flou, basse qualité, distordu, déformé, laid, anatomie incorrecte,
mal dessiné, membres supplémentaires, défiguré, basse résolution, pixelisé,
granuleux, artéfacts, filigrane, signature, texte superposé
Détail par Objectif :
| Objectif | Mots-clés négatifs |
|---|---|
| Qualité | flou, basse qualité, basse résolution, pixelisé, granuleux |
| Anatomie | anatomie incorrecte, déformé, distordu, membres supplémentaires, défiguré |
| Esthétique | laid, mal dessiné, amateur, cartoonish (pour le réalisme) |
| Encombrement | filigrane, signature, texte superposé, logo, badge |
| Style | dessin animé, anime (pour le réalisme), peinture (pour la photo) |
<think>
The user wants me to translate a heading "## Negative Prompts by Use Case" into French.
Let me translate this:
- "Negative Prompts" = "Prompts négatifs" or "Invites négatifs"
- "by Use Case" = "par cas d'utilisation" or "par cas d'usage"
The most natural French translation would be:
"## Prompts négatifs par cas d'utilisation"
Let me think about this more carefully. "Negative prompts" in the context of AI/image generation means prompts that describe what you DON'T want in the image. In French AI/ML communities, this is typically translated as "prompts négatifs" (direct loan translation) or sometimes "invites négatifs".
Given the technical nature and that "prompt" is often kept in English in French tech content, I could also consider:
"## Prompts négatifs par cas d'usage"
"Cas d'usage" is very common in French tech/documentation language.
I'll go with "## Prompts négatifs par cas d'utilisation" as it's clear and natural.
Actually, let me reconsider - "prompts" in French tech context is often left in English or can be translated. Since the article is about image generation (likely GLMImage based on the brand), and "prompt" is a well-established term in French AI discourse, I'll keep it as "Prompts négatifs".
Final translation: "## Prompts négatifs par cas d'utilisation"
</think>
Prompts négatifs par cas d'utilisation
<think>
The user wants me to translate this blog fragment about image generation prompts into French. Let me carefully follow the rules:
- Keep all markdown syntax intact
- Keep URLs, image paths, HTML tags as-is
- Keep code blocks and inline code untranslated (only translate comments if safe)
- Keep "GLMImage" untranslated
- Use native, fluent French
- Output only the translated markdown
Let me translate this carefully:
For Portraits and People
→ ### Pour les portraits et les personnes
Anatomy and Quality:
→ Anatomie et qualité :
Then the code block - I need to keep the content in English as it's technical prompt terms that wouldn't be translated.
Example Complete Prompt:
→ Exemple de prompt complet :
Then the code block stays in English as well.
Let me put this together properly.
</think>
Pour les portraits et les personnes
Anatomie et qualité :
bad anatomy, deformed, distorted, extra limbs, missing limbs,
disfigured face, crossed eyes, uneven eyes, bad proportions,
long neck, mutated hands, extra fingers, missing fingers,
blurry face, low quality face
Exemple de prompt complet :
Professional portrait of woman, 30 years old, studio lighting
Negative: bad anatomy, deformed, distorted, extra limbs, disfigured
face, crossed eyes, bad proportions, mutated hands, extra fingers
<think>
I need to translate this markdown fragment about product photography into natural, fluent French while following all the rules:
- Keep all markdown syntax intact
- Keep URLs, image paths, HTML tags exactly as-is
- Keep code blocks and inline code untranslated (only translate comments if trivially safe)
- Keep brand word "GLMImage" untranslated
- Use native, fluent French expression
- Output ONLY the translated markdown
Let me translate this:
"### For Product Photography" = "### Pour la photographie de produit"
"Clean Product Shots:" = "Photos de produit nettes :"
The code block content is a list of terms to avoid in prompts - these are technical terms and should be kept untranslated as they're used as keywords/parameters. Wait, let me reconsider - the rule says "Keep code blocks and inline code untranslated". So I should keep the English terms in the code block.
Actually, looking at this more carefully - these are negative prompt terms. In the context of image generation, these are technical terms/keywords. The rule says keep code blocks untranslated. So I'll keep the content of the code blocks in English.
"Example Complete Prompt:" = "Exemple d'invite complète :"
For the example prompt, I'll translate the descriptive parts but keep the negative terms untranslated since they're in a code block.
Wait, let me re-read the rule: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."
So the entire code block content should remain in English. But the text outside code blocks should be translated.
Let me do this translation:
"### Pour la photographie de produit
Photos de produit nettes :
watermark, logo, text, brand name, clutter, background objects,
shadows on product, reflections, blurry, low quality, distorted
perspective
Exemple d'invite complète :
Wireless headphones product photography, floating above marble
surface, studio lighting
Negative: watermark, logo, text, brand name, clutter, background
objects, harsh shadows, blurry, low quality
```"
I'll refine the translation, ensuring natural French phrasing while maintaining the technical integrity of the code blocks. The key is to translate descriptive text while preserving the specific technical terms and keywords.
The translation focuses on capturing the essence of the product photography guidelines, translating headings and explanatory text while keeping technical prompts in their original English form. This approach ensures clarity for French-speaking users while maintaining the precise terminology used in image generation processes.
</think>
### Pour la photographie de produit
**Photos de produit nettes** :
watermark, logo, text, brand name, clutter, background objects,
shadows on product, reflections, blurry, low quality, distorted
perspective
**Exemple d'invite complète** :
Wireless headphones product photography, floating above marble
surface, studio lighting
Negative: watermark, logo, text, brand name, clutter, background
objects, harsh shadows, blurry, low quality
<think>
The user wants me to translate a blog article fragment about text rendering for GLMImage into natural, fluent French. Let me analyze what needs to be translated:
1. The heading "### For Text Rendering" - this should be translated to French
2. "**Improve Text Accuracy**" - translate this
3. The list of text issues (garbled text, misspelled words, etc.) - these are technical terms/descriptions that need to be translated
4. The example prompt - this is code/example content, but the instructions say to translate comments inside code blocks when trivially safe. The example prompt is in English and describes a poster with text. I should translate the description parts while keeping the structure.
5. The "Negative:" part - this is part of the example prompt
Let me think about the best French translations:
- "For Text Rendering" → "Pour le rendu de texte" or "Pour le rendu текста" - no, that's not right. "Pour le rendu de texte" is good.
- "Improve Text Accuracy" → "Améliorer la précision du texte"
- "garbled text" → "texte brouillé" or "texte corrompu"
- "misspelled words" → "mots mal orthographiés" or "fautes d'orthographe"
- "extra text" → "texte supplémentaire" or "texte parasite"
- "random letters" → "lettres aléatoires" or "caractères aléatoires"
- "text artifacts" → "artefacts textuels" or "défauts de texte"
- "blurry text" → "texte flou"
- "distorted text" → "texte déformé"
- "multiple lines of unwanted text" → "lignes de texte indésirables"
- "watermarks" → "filigranes" or "tatouages numériques" (in image context)
For the example prompt:
- "Poster with text 'SALE 50%' at top, clean background, legible typography" → "Affiche avec le texte 'SALE 50%' en haut, fond propre, typographie lisible"
- I'll continue translating the negative aspects of the text rendering. I'll focus on converting the descriptions of text quality issues into concise French technical terms.
- The next section covers problematic text characteristics like misspelled words, random letters, and visual distortions. These translations will help communicate precise image generation requirements.
- I'm carefully considering the nuanced translation of technical image generation terminology, especially for the "watermark" concept. The term needs to capture both technical and colloquial meanings in the French context.
- My approach balances maintaining the original intent while finding natural, fluent French expressions that accurately describe these text rendering challenges.
- The translations aim to provide clear, concise descriptions of potential image generation text issues, ensuring technical precision and linguistic authenticity.
- I'm carefully considering nuanced translations for technical terminology, particularly around text rendering and image generation concepts, to ensure linguistic and technical accuracy.
- My approach involves selecting the most appropriate French technical terms that capture the essence of the original English descriptions while maintaining clarity for a French-speaking technical audience.
</think>
### Pour le rendu de texte
**Améliorer la précision du texte** :
texte corrompu, mots mal orthographiés, texte supplémentaire,
caractères aléatoires, artefacts textuels, texte flou,
texte déformé, lignes de texte indésirables, filigranes
**Exemple de prompt complet (GLMImage)** :
Affiche avec le texte « SALE 50% » en haut, fond propre,
typographie lisible
Négatif : texte corrompu, mal orthographié, texte supplémentaire,
caractères aléatoires, artefacts textuels, texte flou,
texte déformé, filigrane
<think>
The user wants me to translate a blog fragment about image generation prompts into French. Let me follow the rules:
1. Keep all markdown syntax intact
2. Keep URLs, image paths, HTML tags exactly as-is
3. Keep code blocks and inline code untranslated (only translate comments if trivially safe - there are none here)
4. Keep "GLMImage" untranslated
5. Use native, fluent French expression
6. Output ONLY the translated markdown
Let me translate this:
### For Landscapes and Environments
-> ### Pour les paysages et environnements
**Clean Scenic Shots**:
-> **Photos de paysages nets** :
The content inside the code blocks stays untranslated as per rule 3.
**Example Complete Prompt**:
-> **Exemple de prompt complet** :
The negative prompt content stays untranslated.
Let me put this together:
</think>
### Pour les paysages et environnements
**Photos de paysages nets** :
people, cars, buildings, power lines, text, watermark, logo,
blurry, low quality, oversaturated, cartoonish, plastic look
**Exemple de prompt complet** :
Serene mountain landscape at sunset, no human elements
Negative: people, cars, buildings, power lines, text, watermark,
logo, blurry, low quality, oversaturated
<think>
I need to translate this markdown fragment about artistic styles into natural, fluent French while following the rules:
1. Keep markdown syntax intact
2. Keep URLs, image paths, HTML tags exactly as-is
3. Keep code blocks untranslated (except safe comments)
4. Keep "GLMImage" untranslated
5. Use native, fluent French
6. Output only the translated markdown
The text is:
- A heading "### For Artistic Styles"
- A description "**Control Style Output**:"
- A code block with style terms
For the code block, these are technical terms/parameters that should generally remain in English as they are commonly used in image generation tools. They are not comments that need translation, they are actual style keywords/parameters. I should keep them as-is in the code block.
The heading and the "Control Style Output" text need to be translated to French.
"### For Artistic Styles" → "### Pour les styles artistiques"
"**Control Style Output**" → "**Contrôle du style de sortie**"
The code block content stays in English as these are technical parameters/keywords used in image generation software.
</think>
### Pour les styles artistiques
**Contrôle du style de sortie**:
photorealistic (for art style), photograph (for illustrations),
blurry, low quality, amateur, child's drawing, stick figures,
oversaturated, washed out
<think>
The user wants me to translate a heading for a blog article fragment into French. This is a simple heading that needs to be translated while keeping the markdown syntax intact.
"## Common Issues and Negative Prompt Solutions"
This translates to:
"## Problèmes courants et solutions avec les prompts négatifs"
Let me verify:
- "Common Issues" = "Problèmes courants" ✓
- "and" = "et" ✓
- "Negative Prompt Solutions" = "solutions avec les prompts négatifs" ✓
This is straightforward. I need to output only the translated markdown heading without any additional commentary.
</think>
## Problèmes courants et solutions avec les prompts négatifs
<think>
I need to translate this article fragment into natural, fluent French while following all the rules:
1. Keep all markdown syntax intact
2. Keep URLs, image paths, HTML tags as-is
3. Keep code blocks and inline code untranslated
4. Keep "GLMImage" untranslated
5. Use native, fluent French expression
6. Output only the translated markdown
Let me translate this content:
"### Issue: Extra Limbs or Bad Anatomy"
- "Extra Limbs" = "Membres supplémentaires" or "Extrémités en trop"
- "Bad Anatomy" = "Mauvaise anatomie" or "Anatomie incorrecte"
The table needs translation for column headers and the Problem column content. The Negative Prompt column should remain in English since these are technical prompts/keywords.
"Comprehensive Anatomy Negative" = "Prompt négatif anatomique complet" or similar
The code block should stay as-is (technical prompts).
Let me write this out:
### Problème : Membres supplémentaires ou mauvaise anatomie
| Problème | Prompt négatif |
|----------|----------------|
| **Doigts en trop** | `extra fingers, too many fingers, more than 5 fingers` |
| **Membres manquants** | `missing limbs, incomplete, cut off` |
| **Mauvaises proportions** | `bad proportions, wrong proportions, distorted anatomy` |
| **Mains mutantées** | `mutated hands, deformed hands, poorly drawn hands` |
**Prompt négatif anatomique complet** :
And the code block stays as-is.
Let me double-check:
- Markdown headers: keep ###
- Tables: keep structure, translate content
- Code block: keep exactly as-is
- "GLMImage": not mentioned in this fragment
- French should be natural and fluent
This looks good!
</think>
### Problème : Membres supplémentaires ou mauvaise anatomie
| Problème | Prompt négatif |
|----------|----------------|
| **Doigts en trop** | `extra fingers, too many fingers, more than 5 fingers` |
| **Membres manquants** | `missing limbs, incomplete, cut off` |
| **Mauvaises proportions** | `bad proportions, wrong proportions, distorted anatomy` |
| **Mains mutantées** | `mutated hands, deformed hands, poorly drawn hands` |
**Prompt négatif anatomique complet** :
extra limbs, missing limbs, bad anatomy, deformed, distorted,
mutated hands, extra fingers, missing fingers, bad proportions,
wrong proportions, disfigured, malformed
<think>
The user wants me to translate a markdown table about unwanted text or watermarks in image generation into French. This appears to be documentation for an AI image generation tool (GLMImage).
Let me translate this carefully while:
1. Keeping the markdown syntax (tables, headers, code fences)
2. Keeping URLs, image paths, and HTML tags as-is
3. Keeping code blocks unchanged (the prompts are technical and should remain in English)
4. Keeping "GLMImage" untranslated
5. Making it sound natural in French
Let me work through this:
### Issue: Unwanted Text or Watermarks
- "Issue" → "Problème"
- "Unwanted Text or Watermarks" → "Texte non désiré ou filigranes"
The table:
| Problem | Negative Prompt |
- "Problem" → "Problème"
- "Negative Prompt" → "Prompt négatif" (this is technical terminology in French AI community)
| **Random text** | `text, random text, letters, characters, typography` |
- "Random text" → "Texte aléatoire"
- The prompt stays in English (code)
| **Watermarks** | `watermark, signature, artist name, logo, badge` |
- "Watermarks" → "Filigranes"
| **UI elements** | `UI, interface, buttons, text overlay, graphics` |
- "UI elements" → "Éléments d'interface"
**Comprehensive Text Negative**:
- "Comprehensive Text Negative" → "Prompt négatif anti-texte complet" or "Prompt négatif anti-texte - Version complète"
Then the code block stays as-is.
Let me finalize this translation to make it natural and professional.
</think>
### Problème : Texte non désiré ou filigranes
| Problème | Prompt négatif |
|----------|----------------|
| **Texte aléatoire** | `text, random text, letters, characters, typography` |
| **Filigranes** | `watermark, signature, artist name, logo, badge` |
| **Éléments d'interface** | `UI, interface, buttons, text overlay, graphics` |
**Prompt négatif anti-texte complet** :
text, random text, letters, characters, typography, watermark,
signature, artist name, logo, badge, UI, interface, buttons,
text overlay, graphics, text artifacts
<think>
The user wants me to translate this markdown table and content about image quality problems into French. Let me carefully follow the rules:
1. Keep all markdown syntax intact - tables, headings, etc.
2. Keep URLs, image paths, HTML tags as-is
3. Keep code blocks and inline code untranslated (only translate comments if safe, but there are no comments)
4. Keep "GLMImage" untranslated
5. Use natural, fluent French
6. Output only the translated markdown
Let me translate:
"Issue: Quality Problems" → "Problème : Problèmes de qualité"
The table headers:
- "Problem" → "Problème"
- "Negative Prompt" → "Prompt négatif"
Table content:
- "Blurry output" → "Sortie floue"
- "Noise/grain" → "Bruit/grain"
- "Distortion" → "Distorsion"
The negative prompts themselves should NOT be translated as they are technical prompts/keywords that should remain in English.
"Comprehensive Quality Negative" → "Prompt négatif qualité complet" or "Prompt négatif de qualité complet"
The code block content (the negative prompts) should NOT be translated as these are technical terms/keywords.
Let me write this out:
</think>
### Problème : Problèmes de qualité
| Problème | Prompt négatif |
|----------|----------------|
| **Sortie floue** | `blurry, out of focus, soft focus, low resolution` |
| **Bruit/grain** | `grainy, noisy, artifacts, compression artifacts` |
| **Distorsion** | `distorted, warped, stretched, pixelated` |
**Prompt négatif de qualité complet**:
blurry, out of focus, soft focus, low resolution, grainy, noisy,
artifacts, compression artifacts, distorted, warped, stretched,
pixelated, low quality, bad quality
<think>
I need to translate this markdown fragment into French while following all the rules:
1. Keep all markdown syntax intact
2. Keep URLs, image paths, HTML tags exactly as-is
3. Keep code blocks and inline code untranslated
4. Keep "GLMImage" untranslated
5. Use native, fluent French
6. Output only the translated markdown
The content is a table about "Style Drift" issue with problem descriptions and negative prompts. The table has:
- A heading "### Issue: Style Drift"
- A table with columns "Problem" and "Negative Prompt"
- Three rows with different style issues
- Code elements in the negative prompts (the text in backticks)
I need to translate:
- The heading title
- The problem descriptions
- But NOT the code in backticks (negative prompts)
Let me translate:
### Problème : Dérive de style
| Problème | Prompt négatif |
|---------|----------------|
| **Trop cartoon** | `cartoon, anime, illustration, painting` (pour les photos) |
| **Trop réaliste** `photorealistic, photograph, realistic` (pour l'art) |
| **Mauvais médium** | `oil painting, watercolor, digital art` (pour les autres styles) |
Wait, I need to be more careful. "Cartoon" in French can be kept as-is since it's commonly used, or translated. But looking at the context, these are technical terms used in prompts, so they might be better left in English or translated. Let me think about what sounds most natural in French.
Actually, looking at the negative prompts - these are meant to be used as-is in image generation tools. So even if the rest of the article is translated, the actual negative prompt text (the code) should probably stay in English because:
1. Image generation AI models are typically trained on English
2. These prompts are technical terms
3. They are in backticks (code)
I'll focus on translating the problem descriptions and table headers, keeping the negative prompt text in its original form. The goal is to provide a clear, understandable translation while maintaining the technical integrity of the prompts.
The table presents different image generation scenarios, each requiring a nuanced approach to describing the style issues. I'll ensure the French translations capture the essence of the original descriptions without altering the technical prompts.
The three key problems - cartoonishness, hyperrealism, and inappropriate medium - represent common challenges in AI image generation, highlighting the need for precise negative prompting techniques.
</think>
### Problème : Dérive de style
| Problème | Prompt négatif |
|---------|----------------|
| **Trop cartoon** | `cartoon, anime, illustration, painting` (pour les photos) |
| **Trop réaliste** | `photorealistic, photograph, realistic` (pour l'art) |
| **Mauvais médium** | `oil painting, watercolor, digital art` (pour les autres styles) |
<think>
The user wants me to translate a heading from an article about GLMImage. The heading is "## Platform-Specific Implementation".
Since this is a heading, I need to translate it naturally into French. The English is straightforward - it refers to implementation details for specific platforms.
Translation:
- "Platform-Specific" = "Spécifique à la plateforme" or "Propre à la plateforme"
- "Implementation" = "Implémentation"
A natural French translation would be: "## Implémentation spécifique à la plateforme"
However, "Implémentation par plateforme" might also work well, or "## Implémentation selon la plateforme".
Let me think about the most natural French expression:
- "Platform-Specific Implementation" = "Implémentation spécifique à la plateforme"
This is the most direct and natural translation. I should keep the markdown heading syntax intact (##).
</think>
## Implémentation spécifique à la plateforme
<think>
The user wants me to translate this blog article fragment about GLMImage into French. I need to:
1. Keep all markdown syntax intact (headings, lists, etc.)
2. Keep URLs, image paths, and HTML tags exactly as-is
3. Keep code blocks and inline code untranslated (except comments when safe)
4. Keep the brand word "GLMImage" untranslated
5. Use native, fluent French expression
6. Output ONLY the translated markdown
Let me translate this carefully:
- "Implementation" → "Implémentation"
- "Dedicated negative prompt field" → "Champ dédié pour l'invite négative"
- "Format" → "Format"
- "Best Practices" → "Bonnes pratiques"
- "Separate negative prompts with commas" → "Séparez les invites négatives par des virgules"
- "Be specific about what to exclude" → "Soyez précis sur ce qu'il faut exclure"
- "Don't overload (5-15 terms optimal)" → "Ne surchargez pas (5 à 15 termes est optimal)"
- "Test incrementally" → "Testez de manière incrémentale"
- "Example" → "Exemple"
For the content:
- "Professional headshot of businesswoman, office background, studio lighting" → "Portrait professionnel d'une femme d'affaires, fond de bureau, éclairage studio"
- The negative prompt terms should be translated but keeping the same style:
- "blurry" → "flou"
- "bad anatomy" → "anatomie incorrecte"
- "extra limbs" → "membres supplémentaires"
- "watermark" → "filigrane"
- "text" → "texte"
- "low quality" → "basse qualité"
- "distorted" → "déformé"
- "oversaturated" → "sursaturé"
Let me put it all together:
</think>
### GLMImage
**Implémentation** : Champ dédié pour l'invite négative
**Format** :
Positive : [Votre prompt principal]
Negative : [Éléments à exclure]
**Bonnes pratiques** :
- Séparez les invites négatives par des virgules
- Soyez précis sur ce qu'il faut exclure
- Ne surchargez pas (5 à 15 termes est optimal)
- Testez de manière incrémentale
**Exemple** :
Positive : Portrait professionnel d'une femme d'affaires, fond de bureau,
éclairage studio
Negative : flou, anatomie incorrecte, membres supplémentaires, filigrane,
texte, basse qualité, déformé, sursaturé
<think>
The user wants me to translate this article fragment about Midjourney's --no parameter from English to French. Let me translate it naturally while keeping all the formatting intact.
Key points:
- Keep all markdown syntax (headings, lists, code fences, etc.)
- Keep all URLs, image paths, HTML tags as-is
- Keep code blocks untranslated
- Keep brand word "GLMImage" untranslated
- Use natural, fluent French
Let me translate:
"### Midjourney" → "### Midjourney" (proper noun, keep as-is)
"**Implementation**" → "**Implémentation**"
"**Format**" → "**Format**"
"**Limitations**" → "**Limitations**"
"**Example**" → "**Exemple**"
The rest of the text needs to be translated to natural French. The code block with the example prompt should be kept in English since it's the actual prompt text that users would type.
Let me do this translation:
</think>
### Midjourney
**Implémentation** : paramètre `--no`
**Format** :
[Votre prompt] --no [éléments à exclure]
**Limitations** :
- Prend en charge uniquement les exclusions basiques
- Moins sophistiqué qu'un champ dédié
- Idéal pour les exclusions simples
**Exemple** :
Portrait professionnel d'une femme d'affaires --no text, watermark,
blurry, bad anatomy
<think>
The user wants me to translate this article fragment about Stable Diffusion into French. Let me go through it carefully:
1. Keep all markdown syntax intact - headings, lists, etc.
2. Keep all URLs, image paths, HTML tags exactly as-is
3. Keep code blocks and inline code untranslated
4. Keep "GLMImage" untranslated
5. Use native, fluent French expression
6. Output ONLY the translated markdown
Let me translate section by section:
"### Stable Diffusion" - This is a heading, so it stays as is for the ### syntax but I translate the text: "### Stable Diffusion" - actually, "Stable Diffusion" is a proper name/product name, so it stays as is.
"**Implementation**: Dedicated negative prompt field" - Translate: "**Implémentation** : Champ dédié pour l'invite négative"
"**Format**:" - "**Format** :"
The code block with prompts - the prompts themselves are instructions/examples that should be translated. So:
- "Positive:" becomes "Positive :"
- "Negative:" becomes "Négative :"
- "[Your main prompt]" becomes "[Votre invite principale]"
- "[Elements to exclude]" becomes "[Éléments à exclure]"
"**Best Practices**:" - "**Bonnes pratiques** :"
"- Can use longer negative prompts" - "- Possibilité d'utiliser des invites négatives plus longues"
"- Supports embedding-based negatives" - "- Prend en charge les négatives basées sur les embeddings" - "embeddings" stays as is since it's a technical term
"- Works well with custom negative embeddings" - "- Fonctionne bien avec les embeddings négatifs personnalisés"
"**Example**:" - "**Exemple** :"
The example code block - the prompts in English should be translated to French:
"Positive: Professional headshot, businesswoman, office background" - "Positive : Portrait professionnel, femme d'affaires, fond de bureau"
I continue translating the negative prompts, carefully converting each element while maintaining the original technical structure and intent.
The negative prompt sequence covers various image quality and composition issues like blurriness, anatomical inaccuracies, unwanted artifacts, and low-quality rendering characteristics. These technical descriptors help guide the image generation process by specifying what to avoid.
The translation preserves the original code block format, ensuring technical consistency while presenting the information in French. Each descriptive term is carefully rendered to maintain its precise technical meaning.
</think>
### Stable Diffusion
**Implémentation** : Champ dédié pour l'invite négative
**Format** :
Positive : [Votre invite principale]
Négative : [Éléments à exclure]
**Bonnes pratiques** :
- Possibilité d'utiliser des invites négatives plus longues
- Prend en charge les négatives basées sur les embeddings
- Fonctionne bien avec les embeddings négatifs personnalisés
**Exemple** :
Positive : Portrait professionnel, femme d'affaires, fond de bureau
Négative : flou, mauvaise anatomie, membres supplémentaires, filigrane, texte,
basse qualité, déformé, (pire qualité:1.4), (basse qualité:1.2)
<think>
The user wants me to translate a blog article fragment into French. The fragment is:
## Advanced Negative Prompting
This is a heading, so I need to translate it. "Advanced Negative Prompting" means "Prompting négatif avancé" in French.
Let me check the rules:
1. Keep markdown syntax intact - it's just a heading, so I keep the ## and translate the text
2. Keep URLs, images, HTML tags - none here
3. Keep code blocks - none here
4. Keep "GLMImage" untranslated - none here
5. Use native, fluent expression
6. Output only the translated markdown
So the translation is simply:
## Prompting négatif avancé
That's it. Very short fragment.
</think>
## Prompting négatif avancé
<think>
The user wants me to translate this markdown article fragment about weighted negative prompts into French. I need to:
1. Keep all markdown syntax intact (headings, lists, tables, code fences, etc.)
2. Keep all URLs, image paths, and HTML tags exactly as-is
3. Keep code blocks and inline code untranslated
4. Keep "GLMImage" untranslated
5. Use natural, fluent French expression
6. Output only the translated markdown
Let me translate this piece by piece:
### Weighted Negative Prompts
→ ### Invites négatifs pondérés
Some platforms support weighting negative prompt elements:
→ Certaines plateformes supportent la pondération des éléments d'invite négatifs :
**Format**:
→ **Format** :
(element:weight)
This stays as is (code block)
**Examples**:
→ **Exemples** :
(watermark:1.5), (blurry:1.3), (bad anatomy:1.2)
This stays as is (code block)
**Weight Guidelines**:
→ **Recommandations de pondération** :
| Weight | Effect |
|--------|--------|
| **1.0-1.2** | Standard exclusion |
| **1.3-1.5** | Strong exclusion |
| **1.6-2.0** | Very strong exclusion (use sparingly) |
→
| Pondération | Effet |
|-------------|-------|
| **1,0-1,2** | Exclusion standard |
| **1,3-1,5** | Exclusion forte |
| **1,6-2,0** | Exclusion très forte (à utiliser avec parcimonie) |
Let me double-check the French translations:
- "Weighted Negative Prompts" → "Invites négatifs pondérés" (sounds natural)
- "Some platforms support weighting negative prompt elements" → "Certaines plateformes supportent la pondération des éléments d'invite négatifs" (natural)
- "Format" → "Format" (keeps original, common in French)
- "Examples" → "Exemples" (natural)
- "Weight Guidelines" → "Recommandations de pondération" (more natural than "Directives de pondération")
- "Standard exclusion" → "Exclusion standard" (correct)
- "Strong exclusion" → "Exclusion forte" (correct)
- "Very strong exclusion (use sparingly)" → "Exclusion très forte (à utiliser avec parcimonie)" (more natural than "avec modération")
I verify the terminology and phrasing to ensure natural, accurate French translations. The language feels conversational and technically precise, maintaining the original markdown structure while adapting to French linguistic nuances.
</think>
### Invites négatifs pondérés
Certaines plateformes supportent la pondération des éléments d'invite négatifs :
**Format** :
(element:weight)
**Exemples** :
(watermark:1.5), (blurry:1.3), (bad anatomy:1.2)
**Recommandations de pondération** :
| Pondération | Effet |
|-------------|-------|
| **1,0-1,2** | Exclusion standard |
| **1,3-1,5** | Exclusion forte |
| **1,6-2,0** | Exclusion très forte (à utiliser avec parcimonie) |
<think>
The user wants me to translate a blog article fragment about negative embeddings into natural, fluent French. Let me follow the rules:
1. Keep all markdown syntax intact
2. Keep URLs, image paths, HTML tags exactly as-is
3. Keep code blocks and inline code untranslated (only translate comments when trivially safe)
4. Keep "GLMImage" untranslated
5. Use native, fluent French expression
6. Output only the translated markdown
Let me translate:
### Embedding-Based Negatives
"Embedding-Based Negatives" could be "Négatifs basés sur les embeddings" or "Négatifs par embeddings". I'll use "Négatifs par embeddings" as it's more natural in French AI/computer vision context.
**Stable Diffusion Advanced**:
"Specialized negative embeddings can be used:" → "Des embeddings négatifs spécialisés peuvent être utilisés :"
**Popular Negative Embeddings** → "Embeddings négatifs populaires"
For the table:
- "Embedding" → "Embedding" (technical term, keep as is)
- "Purpose" → "Objectif"
- "Fix hand generation" → "Corrige la génération des mains"
- "Improve artistic quality" → "Améliore la qualité artistique"
- "Fix anatomy issues" → "Corrige les problèmes d'anatomie"
- "Hand-specific fixes" → "Corrections spécifiques aux mains"
The code block stays as is since it's technical syntax.
Let me put it all together:
</think>
### Négatifs par embeddings
**Stable Diffusion Advanced** :
Des embeddings négatifs spécialisés peuvent être utilisés :
Negative: (bad-artist:1.2), (bad-hands-5:1.3), (bad-anatomy:1.2)
**Embeddings négatifs populaires** :
| Embedding | Objectif |
|-----------|----------|
| **bad-hands-5** | Corrige la génération des mains |
| **bad-artist** | Améliore la qualité artistique |
| **bad-anatomy** | Corrige les problèmes d'anatomie |
| **negative_hand** | Corrections spécifiques aux mains |
<think>
The user wants me to translate this blog article fragment about "Sequential Refinement" into French. Let me follow the rules:
1. Keep all markdown syntax intact
2. Keep URLs, image paths, HTML tags exactly as-is
3. Keep code blocks and inline code untranslated
4. Keep "GLMImage" untranslated
5. Use native, fluent French expression
6. Output only the translated markdown
Let me translate this:
### Sequential Refinement
→ ### Raffinement séquentiel
**Iterative Approach**:
→ **Approche itérative** :
1. **Generate** with positive prompt only
→ 1. **Générer** avec un prompt positif uniquement
2. **Identify issues** in output
→ 2. **Identifier les problèmes** dans la sortie
3. **Add specific negatives** for those issues
→ 3. **Ajouter des négatifs spécifiques** pour ces problèmes
4. **Regenerate** and evaluate
→ 4. **Régénérer** et évaluer
5. **Repeat** as needed
→ 5. **Répéter** si nécessaire
**Example Progression**:
→ **Progression de l'exemple** :
**Round 1**:
→ **Round 1** (or "Round 1" could stay as is, or "Tour 1") - I'll keep "Round 1" as it's a code-style label
The code blocks stay untranslated (the content inside stays in English as it's example prompts).
The text in italics after each round stays as is since it's describing the result.
Let me put it all together:
"### Raffinement séquentiel
**Approche itérative** :
1. **Générer** avec un prompt positif uniquement
2. **Identifier les problèmes** dans la sortie
3. **Ajouter des négatifs spécifiques** pour ces problèmes
4. **Régénérer** et évaluer
5. **Répéter** si nécessaire
**Progression de l'exemple** :
**Round 1** :
Positive: Woman in red dress
Negative: [empty]
*Résultat : Doigts supplémentaires*
**Round 2** :
Positive: Woman in red dress
Negative: extra fingers, bad hands
*Résultat : Meilleures mains, mais flou*
**Round 3** :
Positive: Woman in red dress, sharp focus
Negative: extra fingers, bad hands, blurry
*Résultat : Amélioration notable*"
I'm exploring French terminology variations for "Iterative Approach" in the context of generative AI workflows. The options include "Approche itérative" (iterative approach), "Démarche itérative" (iterative process), or "Méthode itérative" (iterative method). While "Approche itérative" is technically correct, I'm considering "Approche par étapes" (step-by-step approach) as potentially more natural in French, though "Approche itérative" remains the most precise technical description.
The key considerations are clarity, naturalness, and maintaining technical precision while avoiding overly literal translations that might sound unnatural to French speakers familiar with generative AI workflows. I'll use "Itératif" as the most natural French equivalent for "Iterative Approach" in this context. The term captures the concept of progressive, cyclic refinement that fits perfectly with the described workflow. While "itératif" is technically an adjective, it provides the most direct and clear translation for a French audience familiar with technical language.
The progression of "Round" translations seems unnecessary, as the English term is widely understood in technical discussions. Keeping "Round 1" as is maintains clarity and simplicity.
I'll focus on the key observations: the French term "itératif" precisely conveys the iterative workflow, and the term "Round" can remain in English given its technical context.
For the negative prompt analysis, I'm translating the terms while maintaining their core meaning: "doigts supplémentaires" captures "extra fingers", "mauvaises mains" translates "bad hands", and "flou" represents the "blurry" descriptor. Each translation preserves the technical nuance of the original negative prompt description.
The goal is precise linguistic mapping that respects both the technical and natural language dimensions of the original text.
</think>
### Raffinement séquentiel
**Approche itérative** :
1. **Générer** avec un prompt positif uniquement
2. **Identifier les problèmes** dans la sortie
3. **Ajouter des négatifs spécifiques** pour ces problèmes
4. **Régénérer** et évaluer
5. **Répéter** si nécessaire
**Progression de l'exemple** :
**Round 1** :
Positive: Woman in red dress
Negative: [empty]
*Résultat : Doigts supplémentaires*
**Round 2** :
Positive: Woman in red dress
Negative: extra fingers, bad hands
*Résultat : Meilleures mains, mais flou*
**Round 3** :
Positive: Woman in red dress, sharp focus
Negative: extra fingers, bad hands, blurry
*Résultat : Sortie améliorée*
<think>
The user wants me to translate a heading "## Negative Prompt Library" into French while keeping the markdown syntax intact.
This is a simple heading that needs to be translated. "Negative Prompt Library" should be translated into French in a natural way.
"Negative Prompt Library" = "Bibliothèque de prompts négatifs" or "Bibliothèque de prompts inversés"
I'll go with "Bibliothèque de prompts négatifs" as it's the most direct translation and commonly used in AI/image generation contexts.
The full translation would be:
## Bibliothèque de prompts négatifs
Let me output just this as requested.
</think>
## Bibliothèque de prompts négatifs
<think>
The user wants me to translate this blog article fragment into French. This is a list of negative prompts for image generation, organized by category.
Let me translate this carefully:
- Keep all markdown syntax (###, **, lists with ```)
- Keep all the code/prompts exactly as-is (they are technical terms that should remain in English)
- Keep brand word "GLMImage" untranslated (but I don't see it in this fragment)
- Use natural, fluent French
- Output only the translated markdown
The structure is:
- A heading "### By Category"
- 6 categories with bold titles
- Each category has a code block with prompts (in English)
I need to translate the headings and category descriptions, but leave the prompt terms inside the code blocks as-is (they are technical terms for AI image generation).
Let me translate:
- "By Category" → "Par catégorie"
- "Quality Control" → "Contrôle qualité"
- "Anatomy Fixes" → "Corrections anatomiques"
- "Unwanted Elements" → "Éléments unwanted" → actually, this should be "Éléments non souhaités"
- "Style Control" → "Contrôle du style"
- "People/Portraits" → "Personnes/Portraits"
- "Background/Environment" → "Arrière-plan/Environnement"
For the descriptions under each category (the phrases like "for photos", "for art", etc.), I need to translate those since they're not part of the code blocks.
Wait, looking more carefully at the structure, the terms in the code blocks are all technical prompts. The descriptions after the colons like "(for photos)" are comments/explanations. Let me check the exact structure again:
**Quality Control**:
blurry, low quality, worst quality, lowres, grainy, pixelated,
artifacts, distortion, warped, stretched
So "Quality Control" is the heading, and then the code block contains the prompts. The code blocks should remain untranslated. The bold headings should be translated.
I'll focus on translating the headings while preserving the technical prompt terms in their original English form. The key is to maintain the technical precision of the AI image generation terminology while making the overall structure accessible to a French-speaking audience. This means carefully translating category headers and any explanatory text, but leaving the specific prompt terms untouched.
</think>
### Par catégorie
**Contrôle qualité** :
blurry, low quality, worst quality, lowres, grainy, pixelated,
artifacts, distortion, warped, stretched
**Corrections anatomiques** :
bad anatomy, deformed, distorted, extra limbs, missing limbs,
mutated, disfigured, bad proportions, malformed, extra fingers,
missing fingers, bad hands
**Éléments non souhaités** :
watermark, signature, text, logo, badge, UI, interface,
caption, title, username, artist name
**Contrôle du style** :
cartoon, anime, illustration (pour les photos)
photorealistic, photograph (pour l'art)
painting, drawing (pour la 3D/render)
**Personnes/Portraits** :
crossed eyes, lazy eye, uneven eyes, asymmetrical face,
disfigured face, bad face, ugly face, old face (pour jeune)
**Arrière-plan/Environnement** :
clutter, messy, busy background, distracting elements,
people (in landscapes), cars (in nature)
<think>
The user wants me to translate a markdown heading into French. This is a very short fragment - just a heading.
"## Common Mistakes to Avoid"
In French, this would be:
"## Erreurs courantes à éviter"
Let me apply the rules:
1. Keep markdown syntax intact - yes, the "##" heading syntax stays
2. Keep URLs, images, HTML tags - none here
3. Keep code blocks - none here
4. Keep brand word "GLMImage" untranslated - not present
5. Use native, fluent expression - "Erreurs courantes à éviter" is natural French
6. Output ONLY the translated markdown
This is straightforward.
</think>
## Erreurs courantes à éviter
<think>
I need to translate this blog article fragment about negative prompts in image generation into French. Let me follow the rules:
1. Keep all markdown syntax intact
2. Keep URLs, image paths, HTML tags as-is
3. Keep code blocks and inline code untranslated
4. Keep "GLMImage" untranslated
5. Use native, fluent French expression
6. Output only the translated markdown
The content is about negative prompts in image generation. Let me translate it naturally into French.
- "Mistake 1: Overloading Negative Prompts" → "Erreur 1 : Surcharger les prompts négatifs"
- "Problem" → "Problème"
- "Solution" → "Solution"
- "Too Much" → "Trop"
- "Just Right" → "Ce qu'il faut"
For the code blocks, I should keep the content as-is since these are example prompts that would be used in English in the actual tool.
Let me write this out:
</think>
### Erreur 1 : Surcharger les prompts négatifs
**Problème** : Trop de termes négatifs embrouillent le modèle
**Solution** : Concentrez-vous sur 5 à 15 négatifs spécifiques et pertinents
**Trop** :
blurry, low quality, text, watermark, logo, signature, people,
cars, buildings, trees, grass, sky, clouds, sun, moon, stars,
cartoon, anime, painting, drawing, sketch, ugly, deformed,
distorted, bad anatomy, extra limbs, missing limbs, hands,
fingers, face, eyes, mouth, nose, ears, hair, body, skin,
clothes, shoes, hat, glasses, jewelry, accessories
**Ce qu'il faut** :
blurry, low quality, watermark, text, bad anatomy
<think>
The user wants me to translate this blog fragment about image generation tips into natural, fluent French. Let me follow the rules:
1. Keep all markdown syntax intact
2. Keep URLs, image paths, HTML tags exactly as-is
3. Keep code blocks and inline code untranslated (except trivially safe comments)
4. Keep "GLMImage" untranslated
5. Use native, fluent French expression
6. Output only the translated markdown
Let me translate this:
### Mistake 2: Negating Essential Elements
→ ### Erreur 2 : Négation d'éléments essentiels
**Problem**: Excluding things you actually want
→ **Problème** : Exclure des éléments dont vous avez réellement besoin
**Example Error**:
→ **Exemple d'erreur** :
The code block should stay as-is (Portrait of woman, face, eyes, mouth, etc.)
*Result: Portrait without facial features*
→ *Résultat : Portrait sans traits du visage*
**Solution**: Be precise about what to exclude
→ **Solution** : Soyez précis sur ce qu'il faut exclure
**Correct**:
→ **Correct** :
The second code block stays as-is.
Let me put it all together:
</think>
### Erreur 2 : Négation d'éléments essentiels
**Problème** : Exclure des éléments dont vous avez réellement besoin
**Exemple d'erreur** :
Positive: Portrait of woman
Negative: face, eyes, mouth
*Résultat : Portrait sans traits du visage*
**Solution** : Soyez précis sur ce qu'il faut exclure
**Correct** :
Positive: Portrait of woman
Negative: blurry face, crossed eyes
<think>
This is a short blog post fragment about AI image generation mistakes. I need to translate it into natural, fluent French while keeping all the markdown, code blocks, and technical terms intact.
Let me translate this carefully:
- Keep all headings with proper markdown (#)
- Keep code blocks as-is (they contain technical terms)
- Keep URLs and paths exact
- Keep brand name "GLMImage" untranslated
- Make it sound natural in French, not like a machine translation
The fragment discusses "Mistake 3" about relying only on negatives in AI image prompting. Let me translate each section:
### Mistake 3: Relying Only on Negatives
→ ### Erreur 3 : Ne compter que sur les négatifs
**Problem**: Negating instead of proper positive prompting
→ **Problème** : Utiliser la négation au lieu d'un prompt positif approprié
**Example Error**:
→ **Exemple d'erreur** :
The code block content should stay in English as it's technical/standard terminology, or I could translate it for better French readability while keeping the structure. Actually, looking at the rules, code blocks should stay untranslated mostly, but "ugly, bad, poorly drawn" are simple English words that could be left as-is or translated. I'll leave them in English as they're standard technical terms.
**Solution**: Focus on positive description first
→ **Solution** : Commencer par une description positive
**Correct**:
→ **Correct** :
Another code block - keep the English terms in French context or translate them naturally. In French technical content, these terms are often kept in English, but I could translate them for better readability. Let me translate the comments but keep the technical terms.
Actually, looking more carefully at the rules: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."
So I should keep the technical content in the code blocks as-is, and only translate the labels like "Positive:" and "Negative:"
Let me reconsider - the labels "Positive:" and "Negative:" are in the code block. The rule says keep code blocks untranslated, but the labels are just comments/annotations. I think it's acceptable to translate "Positive:" → "Positive :" and "Negative:" → "Négatif :" to make it readable in French context.
I need to follow the instruction strictly about untranslated code blocks. The labels "Positive:" and "Negative:" should remain in English to comply with the rule. For the French version, I'll keep the code block entirely in English to maintain technical consistency and follow the formatting guidelines precisely.
</think>
### Erreur 3 : Ne compter que sur les négatifs
**Problème** : Utiliser la négation au lieu d'un prompt positif approprié
**Exemple d'erreur** :
Positive: Image
Negative: ugly, bad, poorly drawn
**Solution** : Commencer par une description positive
**Correct** :
Positive: Beautiful portrait, professional quality, detailed
Negative: blurry, low quality
<think>
The user wants me to translate this blog fragment about image generation mistakes into French. Let me analyze the content:
1. It's a markdown heading (###)
2. Contains bold text
3. Has a code block with examples
4. The code blocks contain prompts - these should not be translated as they're technical instructions
5. I need to keep all markdown syntax intact
6. Use natural French expression
Let me translate this naturally:
"Mistake 4" = "Erreur 4"
"Contradictory Instructions" = "Instructions contradictoires"
"Problem" = "Problème"
"Positive and negative prompts conflict" = "Les prompts positifs et négatifs sont en conflit"
"Solution" = "Solution"
"Ensure consistency" = "Assurer la cohérence"
"Correct" = "Correct" (or "Bon" or "Exemple correct")
The code blocks should stay exactly as-is with the prompts.
</think>
### Erreur 4 : Instructions contradictoires
**Problème** : Les prompts positifs et négatifs sont en conflit
**Exemple d'erreur** :
Positive: Oil painting style
Negative: painting
**Solution** : Assurer la cohérence
**Correct** :
Positive: Oil painting style
Negative: cartoon, photograph
<think>
I need to translate this short heading "## Best Practices Summary" into French while keeping the markdown syntax intact.
The translation should be natural and fluent in French:
- "Best Practices Summary" → "Résumé des bonnes pratiques" or "Synthèse des bonnes pratiques"
I'll go with "Résumé des bonnes pratiques" as it's the most natural way to express this in French.
</think>
## Résumé des bonnes pratiques
<think>
I need to translate this article fragment about the 80/20 Rule into French while keeping all the markdown syntax, tables, formatting, and brand name "GLMImage" intact.
Let me translate this naturally:
"The 80/20 Rule" → "La règle des 80/20"
The table content:
- Focus → Concentration
- Positive prompt → Prompt positif
- Negative prompt → Prompt négatif
- Percentage → Pourcentage
- Emphasis → Accent
- Quality, detail, specificity → Qualité, détail, précision
- Exclusions, fixes, refinements → Exclusions, corrections, améliorations
Let me put this together in natural French:
</think>
### La règle des 80/20
| Concentration | Pourcentage | Accent |
|---------------|-------------|--------|
| **Prompt positif** | 80% | Qualité, détail, précision |
| **Prompt négatif** | 20% | Exclusions, corrections, améliorations |
<think>
I need to translate this blog fragment about a "Quality Checklist" into French. This appears to be about image generation prompts (positive/negative prompts), so I need to use appropriate terminology that French-speaking image generation enthusiasts would recognize.
Let me translate this carefully:
- Keep all markdown syntax (###, lists, etc.)
- Keep the brand "GLMImage" untranslated
- Use natural French expressions
- Keep code fences, URLs, etc. as-is
"Quality Checklist" = "Liste de contrôle qualité" or "Checklist qualité"
The items to check:
- "Positive prompt is detailed and specific" - I'll use "prompt positif" or "invite positif" (both are used in French)
- "Negative prompt targets specific issues only" - "prompt négatif"
- "No contradictions between prompts" - "Aucune contradiction entre les prompts"
- "Negative prompt has 5-15 terms max" - "Le prompt négatif contient entre 5 et 15 termes maximum"
- "Test iteration strategy if issues persist" - "Stratégie d'itération de test si les problèmes persistent"
Let me compose this naturally in French.
</think>
### Liste de contrôle qualité
Avant de générer, prenez en compte :
- [ ] Le prompt positif est détaillé et précis
- [ ] Le prompt négatif cible des problèmes spécifiques uniquement
- [ ] Absence de contradictions entre les prompts
- [ ] Le prompt négatif contient entre 5 et 15 termes maximum
- [ ] Stratégie d'itération de test si les problèmes persistent
<think>
The user wants me to translate this markdown table about "Negative Prompts" from English to French. Let me carefully translate each element while keeping the formatting intact.
The table has:
- A heading: "### When to Use Negative Prompts"
- Headers: "Scenario" and "Negative Prompt Value"
- Rows with different scenarios and their values
I need to:
1. Translate the heading
2. Translate the column headers
3. Translate the first column (scenarios)
4. Keep the values in the second column as they are (Low, High, Medium)
5. Keep markdown syntax intact
6. Keep bold formatting
Let me translate:
- "When to Use Negative Prompts" → "Quand utiliser les prompts négatifs"
- "Scenario" → "Scénario"
- "Negative Prompt Value" → "Valeur du prompt négatif"
- "First generation" → "Première génération"
- "Known issues" → "Problèmes connus"
- "Refinement" → "Raffinement"
- "Quality control" → "Contrôle qualité"
- "Style control" → "Contrôle du style"
- The values (Low, High, Medium) can stay in English or be translated - typically in technical contexts these might stay English, but I could translate them. I'll keep them in English as they're more universal in the AI/image generation context, or I could translate them. Let me think... in French tech contexts, these terms are often kept in English. But to be safe and natural, I'll translate them: Faible, Élevée, Moyen.
</think>
### Quand utiliser les prompts négatifs
| Scénario | Valeur du prompt négatif |
|----------|--------------------------|
| **Première génération** | Faible (concentrer sur le positif) |
| **Problèmes connus** | Élevée (cibler les problèmes spécifiques) |
| **Raffinement** | Élevée (corriger les défauts identifiés) |
| **Contrôle qualité** | Moyenne (négatifs standards) |
| **Contrôle du style** | Moyenne (exclure les styles unwanted) |
<think>
The user wants me to translate this FAQ section into French. Looking at the content, it appears to be mostly empty - just headings with no actual FAQ content. The section has:
- An H2 "Frequently Asked Questions"
- Several empty HTML div tags (likely placeholder containers)
Since there's no actual text content to translate (just structural markup and empty divs), I should output the same structure in French while keeping the HTML intact.
"Frequently Asked Questions" in French is "Questions fréquentes"
Let me translate just the heading and keep everything else as-is.
</think>
## Questions fréquentes
<think>
The user wants me to translate this short markdown fragment into French. Let me analyze it:
1. It's a heading: "## Keep Going"
2. It's a paragraph with text and a link
I need to:
- Translate naturally into French
- Keep all markdown syntax intact
- Keep URLs as-is
- Keep brand "GLMImage" untranslated (though it's not present here)
- Output ONLY the translated markdown
"Keep Going" could be translated as "Continuer" or "Poursuivre" or "Continuer sans tarder" depending on context. Since it's a call-to-action encouraging users to get more, "Continuer" or "Poursuivre" works well.
The second sentence "Ready for more than one image?" could be "Prêt pour plus d'une image ?" or "Envie de plus d'une image ?" - the first is more direct and professional.
"See plans and credits →" translates to "Voir les plans et crédits →" or "Voir les offres et crédits →". Actually "plans" in this context likely refers to pricing plans, so "offres" or "formules" might be more natural in French. But "plans" is also commonly used in French tech/startup contexts. Let me use "offres" for a more natural French feel.
Let me compose the translation:
## Continuer
Prêt pour plus d'une image ? [Voir les offres et crédits →](/pricing)
This looks good. Natural, fluent, maintains all syntax.
</think>
## Continuer
Prêt pour plus d'une image ? [Voir les offres et crédits →](/pricing)
<think>
Je dois traduire ce fragment d'article en français tout en respectant toutes les règles :
1. Garder toute la syntaxe markdown intacte
2. Garder toutes les URLs, chemins d'images et balises HTML tels quels
3. Garder les blocs de code et le code en ligne non traduits
4. Garder la marque "GLMImage" non traduite
5. Utiliser une expression naturelle et fluide
6. Ne produire que le markdown traduit
C'est une section "Sources" avec une liste de liens. Je dois traduire les textes des liens mais garder les URLs intactes.
Les textes à traduire sont :
- "Negative prompts — AUTOMATIC1111 Stable Diffusion WebUI Wiki"
- "How does a negative prompt work? — Stable Diffusion Art"
- "Prompt Engineering Guide"
- "How to Write AI Prompts"
- "Best AI for Text Rendering"
Traductions naturalistes :
- "Negative prompts" → "Prompts négatifs" ou garder "Negative prompts" car c'est un terme technique établi
- "How does a negative prompt work?" → "Comment fonctionne un prompt négatif ?"
- "Prompt Engineering Guide" → "Guide d'ingénierie des prompts" ou "Guide de conception de prompts"
- "How to Write AI Prompts" → "Comment rédiger des prompts pour l'IA"
- "Best AI for Text Rendering" → "Meilleure IA pour le rendu de texte"
Je vais utiliser des expressions naturelles en français.
</think>
## Sources
- [Prompts négatifs — Wiki AUTOMATIC1111 Stable Diffusion WebUI](https://github.com/AUTOMATIC1111/stable-diffusion-webui/wiki/Negative-prompt)
- [Comment fonctionne un prompt négatif ? — Stable Diffusion Art](https://stable-diffusion-art.com/how-negative-prompt-work)
- [Guide de conception de prompts](https://www.promptingguide.ai)
- [Comment rédiger des prompts pour l'IA](/blog/how-to-write-ai-prompts)
- [Meilleures IA pour le rendu de texte](/blog/best-ai-text-rendering)
