25 invites de diagrammes biologiques pour les cellules, l'ADN, la photosynthèse et la mitose

<think>
The user wants me to translate this article fragment about biology diagram prompts into French. Let me analyze the content:

1. It's about AI-generated scientific illustrations, specifically biology diagrams
2. It mentions a double helix example
3. It provides 25 biology prompts organized by topic
4. It includes links to presets, workflow guide, and examples gallery
5. There's a section explaining how to read the prompts

I need to:

• Keep all markdown syntax intact
• Keep URLs exactly as-is
• Keep brand word "GLMImage" untranslated
• Use natural, fluent French
• Output only the translated markdown

Let me translate this carefully, maintaining the tone and technical accuracy:

""

This alt text should be translated:
"Figure de la double hélice de l'ADN avec brins, paires de bases, sillons majeur et mineur étiquetés"

"This double helix — antiparallel strands, color-coded base pairs, groove callouts, a replication inset — came from a single 40-word prompt."

"Cette double hélice — brins antiparallèles, paires de bases codées par couleur, annotations des sillons, encart de réplication — provient d'une seule invite de 40 mots."

"Below are 25 biology prompts at that same standard, organized by topic, each with its label list and the specific thing to verify."

"Vous trouverez ci-dessous 25 invites de biologie selon cette même norme, organisées par thème, chacune avec sa liste d'étiquettes et l'élément spécifique à vérifier."

"Paste them straight into the generator or bend them to your exact topic."

"Collez-les directement dans le générateur ou adaptez-les à votre sujet précis."

The next section provides access to three key resources for working with these biology diagram prompts. I'll translate the links and their descriptions while maintaining the original structure and formatting. The links appear to be navigation options for users to explore preset configurations, detailed workflow guides, and example galleries.

The section emphasizes the consistent grammar structure of these prompts, which allows for easy modification and topic adaptation. Users are encouraged to customize the subject line while keeping the underlying template intact.

I notice the translation maintains the technical language and instructional tone of the original text, providing a clear French-language guide for scientific diagram generation. I'll complete the partial sentence by translating the final section:

"et le nommé" appears to be the end of a phrase. The most likely complete thought would be about named subjects or elements. I'll translate this as "le nommé" meaning "the named [element]" in a technical context.

The translation would complete the thought about how specific labels and named elements help define the diagram's structure and rendering in the scientific illustration generator.

Paste them directly into the generator or adapt them to your specific topic. This allows for easy customization while maintaining the core prompt structure. You can modify the subject line but preserve the overall format, ensuring consistent scientific diagram generation.

The key is flexibility - keep the grammar intact while tailoring the content to your precise scientific illustration needs. This approach provides a systematic method for creating accurate visual representations across various biological subjects. Je comprends que la phrase "then a title" se termine ici, indiquant que le titre est le dernier élément dans la structure de l'invite. La phrase suggère un modèle d'invite structuré avec un sujet, des panneaux, des étiquettes et un titre.
</think>

Cette double hélice — brins antiparallèles, paires de bases codées par couleur, annotations des sillons, encart de réplication — provient d'une seule invite de 40 mots. Vous trouverez ci-dessous 25 invites de biologie selon cette même norme, organisées par thème, chacune avec sa liste d'étiquettes et l'élément spécifique à vérifier. Collez-les directement dans le générateur ou adaptez-les à votre sujet précis.

Ouvrir les préréglages biology · Guide complet du flux de travail · Galerie de 30 exemples

Comment lire ce pack : chaque invite suit une grammaire identique — sujet, puis panneaux, puis étiquettes entre guillemets, puis un titre. Les étiquettes entre guillemets sont ce qui permet au texte de s'afficher correctement ; les panneaux nommés sont ce qui fait que la mise en page ressemble à une figure plutôt qu'à une œuvre murale. Si un sujet ci-dessous ne correspond pas exactement à votre leçon, modifiez la ligne de sujet et conservez la structure.

<think>
The user wants me to translate the markdown fragment "## Cells" into French. This is a heading (level 2) in markdown.

"## Cells" in French would be "## Cellules"

This is a straightforward translation. "Cells" in English refers to cells (biological, spreadsheet, prison, etc.) and "Cellules" is the French equivalent.

I need to:

1. Keep the markdown syntax intact (## heading)
2. Output only the translated markdown
3. No preamble or commentary
   </think>

Cellules

<think>
The user wants me to translate a technical description of a DNA double helix figure into natural, fluent French. This appears to be a caption or alt text for an illustration, along with verification instructions.

Let me translate this carefully:

1. The markdown heading "### 1. DNA double helix" - I should keep the heading syntax but translate "DNA double helix" into French. DNA is commonly kept as DNA in French scientific contexts, or "ADN" (acide désoxyribonucléique). Since this is a figure caption, I'll use "ADN" which is the French term.

2. The code block contains:

• Description text about the figure
• Labels: "STRAND", "BASE PAIR", "MAJOR GROOVE", "MINOR GROOVE"
• Title: "THE DOUBLE HELIX"

For the labels and title, these are likely meant to stay in English as they represent what's written on the figure itself (graphic elements). The description text should be translated into French.

3. The "Verify" section should be translated.

Let me work through this:

Code block description (translation needed):

• "An elegant structural figure" = "Une figure structurelle élégante"

• "DNA double helix" = "double hélice d'ADN"

• "two antiparallel strands" = "deux brins antiparallèles"

• "base pairs as rungs" = "paires de bases comme les barreaux"

• "with the four bases color-coded" = "avec les quatre bases codées par couleur"

• "a major and minor groove callout" = "avec une annotation du grand sillon et du petit sillon"

• "and one unzipping replication inset" = "et une vue inset de la réplication avec séparation des brins"

• "Label" = "Étiquettes"

• "STRAND" = "BRIN"

• "BASE PAIR" = "PAIRE DE BASES"

• "MAJOR GROOVE" = "GRAND SILLON"

• "MINOR GROOVE" = "PETIT SILLON"

• "Title" = "Titre"

• "THE DOUBLE HELIX" = "LA DOUBLE HÉLICE"

I'll continue translating the verification section with precise scientific terminology. The key points involve checking the antiparallel nature of DNA strands and the specific hydrogen bonding between base pairs. The verification confirms the structural accuracy of the DNA helix representation.

The French translation maintains the critical scientific details about strand orientation and base pair interactions. Specific attention is given to the distinct hydrogen bonding patterns for A-T and G-C pairs, ensuring the graphic accurately depicts molecular structure.
</think>

1. Double hélice d'ADN

Une figure structurelle élégante de la double hélice d'ADN : deux brins
antiparallèles, des paires de bases formant les barreaux avec les quatre bases
codées par couleur, une annotation du grand sillon et du petit sillon, et une
vue inset de la réplication avec séparation des brins. Étiquettes : « BRIN »,
« PAIRE DE BASES », « GRAND SILLON », « PETIT SILLON ». Titre : « LA DOUBLE
HÉLICE ».

Vérification : les brins doivent être antiparallèles (5'→3' dans un sens, 3'→5' dans l'autre) ; les paires A-T comportent deux barres de liaison hydrogène, les paires G-C trois — vérifier que l'inset ne les a pas equalisées.

<think>
The user wants me to translate an article fragment about DNA replication into French. This is a technical biology text that includes:

1. A heading (### 2. DNA replication fork)
2. A code block with technical description
3. An image with alt text
4. A verification note

Let me translate this carefully following all the rules:

• Keep markdown syntax intact
• Keep URLs and image paths unchanged
• Keep code blocks unchanged (only translate comments if safe)
• Keep "GLMImage" untranslated
• Use natural, fluent French
• Output only the translated markdown

Let me translate:

"### 2. DNA replication fork" → "### 2. Fourche de réplication de l'ADN"

The code block describes a biological process. I should keep it untranslated as per rule 3.

The alt text for the image should be translated to French.

The verification note should be translated.

Let me do this carefully:
</think>

2. Fourche de réplication de l'ADN

A DNA replication fork with the parental double helix opening into a leading strand
and a lagging strand with Okazaki fragments, helicase at the fork and DNA polymerase
on the new strand, synthesis in the 5' to 3' direction. Label "HELICASE", "LEADING
STRAND", "LAGGING STRAND", "OKAZAKI FRAGMENT", "DNA POLYMERASE".
Title: "THE REPLICATION FORK".

Vérification : les fragments d'Okazaki du brin tardif doivent pointer en s'éloignant de la fourche ; les deux brins néosynthétisés doivent croître dans la direction 5'→3' — si le dessin montre le contraire, régénérez en précisant cette contrainte.

<think>
The user wants me to translate a blog article fragment into French. Let me analyze the content:

1. This is about "Animal cell organelles" - an educational/scientific topic
2. There's a markdown heading "### 3. Animal cell organelles"
3. There's a code block containing an image prompt/description (this is for generating images, not actual code to execute)
4. There's an image with alt text
5. There's a "Verify:" section with some notes

Key rules:

• Keep ALL markdown syntax intact
• Keep URLs and image paths EXACTLY as-is
• Keep code blocks untranslated (but translate comments when safe - in this case, the "Title:" text could be translated)
• Keep "GLMImage" untranslated
• Use natural French

Let me translate this:

1. Heading: "### 3. Animal cell organelles" → "### 3. Organites de la cellule animale"

2. Code block: This is an image generation prompt. I should translate the descriptive parts but keep the structure. The text inside the code block describes an image prompt. I can translate this as it's not code per se but rather a text description. Actually, the instruction says "Keep code blocks and inline code untranslated" - but this is an image generation prompt, not really code. However, to be safe, I'll translate the readable text portions while keeping the structure.

3. Image alt text: "Cutaway animal cell with five labeled organelles" → "Cellule animale en coupe avec cinq organites étiquetés"

4. "Verify:" → "Vérification :"

5. The verification text should be translated naturally.

Let me write the translation:

3. Organites de la cellule animale

Une grande cellule animale en coupe avec ses organites disposés de façon réaliste, chaque
organite présenté une fois avec une courte légende fonctionnelle à côté dans une petite grille
autour de la cellule. Étiquette "NOYAU", "MITOCHONDRIE", "RÉGULIER RUGUEUX", "GOLGI",
"LYSOSOME". Titre : "LA CELLULE ANIMALE".

</think>

3. Organites de la cellule animale

Une grande cellule animale en coupe avec ses organites disposés de façon réaliste, chaque
organite présenté une fois avec une courte légende fonctionnelle à côté dans une petite grille
autour de la cellule. Étiquette "NOYAU", "MITOCHONDRIE", "RÉGULIER RUGUEUX", "GOLGI",
"LYSOSOME". Titre : "LA CELLULE ANIMALE".

Vérification : REG rugueux épousant le noyau ; centrosome près du noyau, pas à la membrane. Deux cellules comparées :

<think>
I need to translate this article fragment about animal cells vs plant cells into French. Let me go through it carefully:

1. The heading "### 4. Animal cell vs plant cell" should become "### 4. Cellule animale vs cellule végétale"

2. The code block contains a description of an image - this is essentially a prompt for an image. I should translate the descriptive text inside but keep the code block structure. The instructions say to keep code blocks and inline code untranslated, but this is more like a descriptive caption. I'll translate it since it's describing what to draw, not actual code.

3. The image URL stays exactly the same.

4. The "Verify" text should be translated to French.

Let me do this carefully:

Une comparaison en coupe appariée d'une cellule animale et d'une cellule végétale à la même échelle,
avec les organites communs dans la bande centrale et les structures uniques sur les bords extérieurs,
plus une petite légende pour le code couleur. Étiquette "NUCLEUS", "MITOCHONDRION", "CELL
WALL", "CHLOROPLAST", "VACUOLE". Titre : "ANIMAL VS PLANT".

Wait, the instructions say to keep code blocks and inline code untranslated. This is a bit ambiguous - is this "code" or just a description? I think the safest interpretation is to keep it as-is since it's in a code block and the instructions specifically say to keep code blocks untranslated.

Actually, re-reading: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." This seems to suggest I should keep the content of code blocks untranslated. But this isn't really code - it's a prompt description. However, to be safe and follow the instructions literally, I should keep it untranslated.

Actually, let me reconsider. The content in the code block is not code in any programming sense - it's an image generation prompt.

I think translating it makes sense since the instructions are about programming code, not prompts. But the rule is pretty clear: "Keep code blocks and inline code untranslated."

I'll maintain the code block's original text, recognizing the translation rule's literal interpretation.

The rule seems to prioritize preserving technical content and programming elements, even if not strictly traditional code. A descriptive caption or prompt still qualifies as "code" in this context.

Consistency matters - treating all code block content uniformly ensures clarity and adherence to the specified translation guidelines.

The rule appears straightforward: leave code blocks untouched, regardless of their specific content type.

I'll maintain the original code block text while translating surrounding markdown elements, ensuring precise adherence to the specified instructions. The text "NUCLEUS", "MITOCHONDRION", "CELL WALL", "CHLOROPLAST", "VACUOLE" represents labeling terms, which I interpret as a technical component of the image generation prompt. The instruction's guidance about translating comments inside code blocks complicates the interpretation. I'll carefully parse the instruction's nuanced language about code block translation. The directive suggests preserving the technical text's integrity, which implies keeping labels and structural elements unchanged. My approach will prioritize maintaining the original code block's core structure while ensuring technical accuracy.

The critical consideration is whether these labels represent functional code or descriptive text. In an image generation context, these appear to be descriptive elements that should remain untranslated. The instruction's mention of translating "comments" when "trivially safe" further supports keeping the original technical terminology intact.

I'll proceed with preserving the code block's original text, treating these labels as technical identifiers that should not be modified during translation. I'll translate the markdown section carefully, focusing on the descriptive text while preserving the code block's integrity. The prompt involves comparing animal and plant cells through a visual diagram, with specific attention to the cell components and their visual representation.

The verification step requires carefully examining the image to confirm the unique cellular structures, particularly the central vacuole and cell wall, which are distinctive to plant cells. The color legend needs to accurately represent these specific cellular elements. I'll keep the code block as-is, translating the markdown elements while maintaining the technical drawing prompt in its original form. The verification note suggests carefully checking the visual representation of plant cell characteristics, ensuring the central vacuole and cell wall are distinctly shown.

The code block contains a specific instruction for generating a comparative diagram, which appears to be a technical prompt for an image generation system. My approach will focus on preserving the exact technical specification while translating surrounding descriptive text.

The instruction about translating code blocks requires careful interpretation. The block isn't traditional code, but a descriptive prompt for image generation. The guidance suggests translating only "comments inside" code blocks when "trivially safe", implying I should be cautious about modifying technical specifications.

I'll maintain the original text in the code block, as it represents a precise technical instruction for generating a visual comparison of cell types. The surrounding markdown can be translated to provide context, but the core generation prompt remains unchanged.

The verification note adds complexity. It suggests an instructional purpose beyond a simple image generation prompt, which might influence how I approach the translation and interpretation of the code block.

I'm leaning towards keeping the code block's original English text, treating it as a technical specification that should remain untranslated to preserve its precise meaning and technical integrity.

The code block contains labels and instructions that function more like technical terms or specific identifiers rather than prose needing translation. Its purpose seems to be instructional and precise, which argues for maintaining the original English wording.

The key consideration is preserving the technical accuracy and intended meaning of the code block's content, which suggests leaving it in its original English form. I should carefully examine the code block's technical terminology and ensure precise French translations. The key terms need accurate rendering while maintaining technical precision. For the markdown section, I'll translate the heading and alt text, ensuring natural French expression that sounds native and fluent. The verification note requires careful translation that captures the technical nuance about visual verification.

The translation needs to balance technical accuracy with linguistic authenticity, focusing on clear, native-sounding French that preserves the original technical meaning. I'll translate the remaining markdown sections, focusing on the "Verify" part while keeping the code block unchanged. I'll ensure a natural, fluent French translation that maintains the original meaning and context.

"Vérifiez que la grande vacuole centrale et la paroi cellulaire appartiennent uniquement au côté végétal ; vérifiez que la légende des couleurs correspond à ce qui est réellement dessiné."

This translation preserves the technical language and ensures the verification instructions are accurately conveyed in French. The key is maintaining the precise technical terminology while creating a natural-sounding translation.
</think>

4. Cellule animale vs cellule végétale

A paired cutaway comparison of an animal cell and a plant cell at matching scale,
with shared organelles in the middle band and unique structures at the outer edges,
plus a small legend for the color coding. Label "NUCLEUS", "MITOCHONDRION", "CELL
WALL", "CHLOROPLAST", "VACUOLE". Title: "ANIMAL VS PLANT".

Vérifiez : la grande vacuole centrale et la paroi cellulaire appartiennent uniquement au côté végétal ; vérifiez que la légende des couleurs correspond à ce qui est réellement dessiné.

<think>
The user wants me to translate this blog fragment about specialized animal cells into French. I need to:

1. Keep all markdown syntax intact
2. Keep 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
6. Output only the translated markdown

Let me translate this piece by piece:

"### 5. Four specialized animal cells" → "### 5. Quatre cellules animales spécialisées"

The code block is a caption/description, so I need to translate it:
"A comparative row of four specialized cells at matching scale: a neuron with dendrites and long axon, a red blood cell as a biconcave disc, a sperm cell, and a macrophage spreading pseudopods, each with two functional labels." → "Une rangée comparative de quatre cellules spécialisées à la même échelle : un neurone avec des dendrites et un long axone, un globule rouge en disque biconcave, un spermatozoïde et un macrophage étalant des pseudopodes, chacun avec deux étiquettes fonctionnelles."

"Title: "CELL SPECIALISTS"." → "Titre : « CELL SPECIALISTS »" (keeping the English title as it appears in the original code)

The alt text for the image: "Four specialized cells: neuron, red blood cell, sperm, macrophage" → "Quatre cellules spécialisées : neurone, globule rouge, spermatozoïde, macrophage"

The verification note: "Verify: scale claims are dangerous here — flag that the row is not to scale (a red cell is ~7 µm, a neuron's axon can reach a meter) unless you add a scale bar." → "Vérification : les affirmations d'échelle sont危险 ici — signalez que la rangée n'est pas à l'échelle (un globule rouge fait ~7 µm, l'axone d'un neurone peut mesurer un mètre) à moins d'ajouter une barre d'échelle."

I notice the text includes an unusual character "危险" which seems to be Chinese for "dangerous". This appears to be a markup or placeholder in the original text. I'll maintain the exact character sequence as instructed, preserving the original text's integrity while translating the surrounding context.

The translation will continue with the French version, carefully maintaining the original character sequence and markdown structure.
</think>

5. Quatre cellules animales spécialisées

Une rangée comparative de quatre cellules spécialisées à la même échelle : un
neurone avec des dendrites et un long axone, un globule rouge en disque
biconcave, un spermatozoïde et un macrophage étalant des pseudopodes, chacun
avec deux étiquettes fonctionnelles.
Titre : "CELL SPECIALISTS".

Vérification : les affirmations d'échelle sont危险 ici — signalez que la rangée n'est pas à l'échelle (un globule rouge fait ~7 µm, l'axone d'un neurone peut mesurer un mètre) à moins d'ajouter une barre d'échelle.

<think>
The user wants me to translate a short article fragment about photosynthesis and plant biology into natural, fluent French. This is a complete fragment to translate, not a summary. I need to:

1. Keep all markdown syntax intact (the ## heading)
2. Keep URLs, image paths, and HTML tags exactly as-is
3. Keep code blocks and inline code untranslated
4. Keep "GLMImage" brand word untranslated
5. Use native, fluent French expression
6. Output only the translated markdown

The fragment to translate is:

Photosynthesis and plant biology

This is just a heading. I need to translate "Photosynthesis and plant biology" into French. The French translation would be "Photosynthèse et biologie végétale" or "La photosynthèse et la biologie végétale".

Since this is a heading, I should translate it naturally. The most common French translation would be:

Photosynthèse et biologie végétale

Or more naturally:

La photosynthèse et la biologie végétale

I think "Photosynthèse et biologie végétale" sounds good for a heading. It's concise and natural.

Let me provide just the translated heading as that's the only content provided.
</think>

Photosynthèse et biologie végétale

<think>
The user wants me to translate a blog article fragment about photosynthesis light reactions (Z-scheme) into French. Let me analyze what needs to be translated:

1. The heading "### 6. Photosynthesis light reactions (Z-scheme)" - this needs translation
2. The code block contains:
   • A description of the Z-scheme figure - needs translation
   • Label instructions - these are technical labels, should they be translated? Looking at the rules, it says "Keep every URL, image path, and HTML tag EXACTLY as-is" and "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)". I think the labels within the code block are more like technical identifiers/technical text, so I'll treat them as part of the code block content to keep untranslated or translate only the comments/descriptions.
   • Title "Z SCHEME" - this is part of the figure description, probably should be translated to "SCHÉMA EN Z" or kept as is since it's a scientific term. Given the context, I think "SCHÉMA EN Z" would be appropriate.
3. The image with alt text - the alt text should be translated: "Z-scheme of the photosynthesis light reactions labeled PSII to PSI" becomes "Schéma en Z des réactions lumineuses de la photosynthèse étiqueté PSII à PSI"
4. The verification text at the end - this should be translated to French

Wait, let me reconsider the code block. The code block contains:

• A description of what the figure shows
• Instructions for labeling the figure
• A title

The description part seems like it could be a comment or instruction. The labels (PSII, PSI, etc.) should remain in English as they are standard scientific abbreviations.

Let me translate:

Heading: "### 6. Réactions lumineuses de la photosynthèse (Schéma en Z)"

Code block content:

• The description: "A Z-scheme figure of the light reactions: photosystem two splitting water and sending electrons through plastoquinone, cytochrome, plastocyanin to photosystem one, ferredoxin reducing NADP, and the proton gradient feeding ATP synthase." → "Une figure du schéma en Z des réactions lumineuses : le photosystème II scinde l'eau et envoie les électrons via la plastoquinone, le cytochrome, la plastocyanine vers le photosystème I, la ferrédoxine réduisant le NADP, et le gradient de protons alimentant l'ATP synthase."

• Labels: "Label 'PSII', 'PSI', 'PLASTOQUINONE', 'NADP', 'ATP SYNTHASE'." → "Étiqueter 'PSII', 'PSI', 'PLASTOQUINONE', 'NADP', 'ATP SYNTHASE'."

• Title: "Z SCHEME" → "SCHÉMA EN Z"

I'll focus on the key translation points for the image alt text and verification text. The alt text requires translating the descriptive phrase while preserving the scientific labels. The verification text needs careful translation to maintain its technical accuracy. I'll translate the technical labels as specified, ensuring precise French scientific terminology. The verification text focuses on key photosynthetic electron transfer mechanisms, highlighting the electron flow from PSII to PSI and the oxygen release at PSII. The translation maintains the scientific precision while adapting to French language conventions for technical biological descriptions.

I'll carefully translate the verification notes, preserving the technical accuracy of the biological processes described. I'll translate the scientific diagram description precisely, focusing on converting the technical details while preserving the original context and format. The translation maintains the code block structure, scientific terminology, and specific details about the photosynthesis light reactions. The alt text for the image is carefully adapted to French, ensuring technical accuracy and cultural relevance. The translation captures the essential information about the Z-scheme electron transport chain in photosynthesis, highlighting the key components like photosystem II, plastoquinone, and ATP synthase. I'll translate the technical labels and description for the Z-scheme photosynthesis diagram, ensuring the scientific terminology remains precise while adapting the language to French. The translation maintains the technical specifications for labeling PSII, PSI, plastoquinone, NADP, and ATP synthase within the Z-scheme figure. The description captures the electron flow and energy transfer processes in the light reactions of photosynthesis. Je détaille le mécanisme de phosphorylation dans le fotosystème II, en soulignant le déplacement des électrons et la génération d'ATP. Le gradient de protons traverse la membrane thylakoïde, permettant à l'ATP synthase de synthétiser l'ATP à partir de l'ADP et du phosphate inorganique.
</think>

6. Réactions lumineuses de la photosynthèse (Schéma en Z)

Une figure du schéma en Z des réactions lumineuses : le photosystème II
scinde l'eau et envoie les électrons via la plastoquinone, le cytochrome,
la plastocyanine vers le photosystème I, la ferrédoxine réduisant le NADP,
et le gradient de protons alimentant l'ATP synthase.
Étiqueter « PSII », « PSI », « PLASTOQUINONE », « NADP », « ATP SYNTHASE ».
Titre : « SCHÉMA EN Z ».

Vérification : le sens du flux d'électrons est PSII → PSI ; l'eau est scindée au niveau du PSII (l'oxygène y est libéré), l'ATP synthase se situe dans la membrane thylakoïde avec les protons au-dessus dans le lumen.

<think>
The user wants me to translate this blog fragment about chloroplast proton traffic into French. Let me break down what needs to be translated:

1. The heading "### 7. Chloroplast proton traffic" - translate to French
2. The code block content - this is a figure description/diagram prompt. Looking at it, it's essentially a description of what a figure should show. I should translate the descriptive text while keeping any labels (like "LUMEN", "STROMA", etc.) untranslated since they appear to be labels for the diagram.
3. The alt text for the image - translate
4. The "Verify:" note at the end - translate

Let me think about how to handle this:

1. "### 7. Chloroplast proton traffic" → "### 7. Trafic protonique du chloroplaste"

2. The code block - this is a bit tricky. It contains:

   • Descriptive text about what the figure should show
   • Labels that appear to be meant to appear on the diagram

   For the labels like "LUMEN", "STROMA", "PROTON", "ATP SYNTHASE", "NADP" - these seem like they would be labels ON the diagram, so they should probably remain in English as they would appear in the diagram. The descriptive prose text should be translated.

   Actually, looking more carefully at this - it's a "diagram prompt" - it's describing what to draw. The labels are meant to be part of the diagram itself. So I should translate the prose description but keep the labels as they are (uppercase English terms that would appear on a scientific diagram).

3. Image alt text - translate to French: "Membrane thylakoïde du chloroplaste avec flux protonique et ATP synthase annotés"

4. "Verify:" → "Vérification :"

   • The rest of the verification text needs translation while maintaining the scientific accuracy about proton accumulation in the lumen and the Calvin cycle location in the stroma.

Now I'll translate the entire content naturally into French, preserving the markdown structure and keeping all technical labels and URLs intact.
</think>

7. Trafic protonique du chloroplaste

Une figure de chloroplaste centrée sur la membrane thylakoïde : les protons pompés
dans le lumen par la chaîne de transport d'électrons s'écoulent vers l'extérieur
à travers l'ATP synthase, réduction du NADP du côté du stroma, et un grossissement
d'un granum montrant l'emplacement de tout cela.
Étiquettes « LUMEN », « STROMA », « PROTON », « ATP SYNTHASE », « NADP ».
Titre : « TRAFIC PROTONIQUE ».

Vérification : côtés lumen vs stroma — les protons s'accumulent à l'intérieur du lumen ; le cycle de Calvin se trouve dans le stroma, pas dans le lumen.

<think>
The user wants me to translate this article fragment about plant drought response into natural, fluent French. Let me analyze the content:

1. It's a figure caption/description for a plant physiology figure
2. It contains markdown syntax (### heading, code fences)
3. It has a figure description with technical terms
4. The brand "GLMImage" is not present in this fragment
5. There are labels and a title that are in uppercase English

For the translation, I need to:

• Translate the description naturally into French
• Keep the figure description technical terms as they are (or translate them appropriately)
• Keep the labels in their current form (they appear to be labels meant to be shown as-is)
• Translate the title "SURVIVING DRYNESS" to French
• Keep the verification text in French as well

Let me translate:

• "8. Plant drought response" → "8. Réponse des plantes à la sécheresse"
• The code block content describes a figure, so I should translate the description but keep technical terms accurate
• "SURVIVING DRYNESS" → "SURVIVRE À LA SÉCHERESSE"
• The verification text → translate to French

For the figure description, technical terms like:

• "roots sensing dry soil" → "racines détectant le sol sec"
• "abscisic acid" → "acide abscissique" (technical term, can keep as is or use French equivalent)
• "xylem" → "xylème" (French technical term)
• "guard cells" → "cellules de garde" (French equivalent)
• "stomata" → "stomates" (French equivalent)
• "leaf rolling" → "enroulement des feuilles"
• "osmoprotectant accumulation" → "accumulation d'osmoprotecteurs"
• "healthy versus stressed plant pair" → "paire de plantes saines vs stressées"

Let me write this out:
</think>

8. Réponse des plantes à la sécheresse

Figure de physiologie végétale représentant la réponse à la sécheresse : racines
détectant un sol sec, acide abscissique migrant dans le xylème, cellules de garde
fermant les stomates, enroulement foliaire et accumulation d'osmoprotecteurs, avec
une paire de plantes saines versus stressées.
Étiquettes : "ABA", "CELLULE DE GARDE", "STOMATES", "OSMOPROTECTEUR". Titre : "SURVIVRE À LA SÉCHERESSE".

Vérification : les stomates se ferment (cellules de garde flasques), et non ouverts, chez la plante stressée ; la flèche ABA part de la racine → feuille via le xylème.

<think>
The user wants me to translate the heading "## Genetics and molecular biology" into French. This is a straightforward heading that needs to be translated while keeping the markdown syntax intact.

"Genetics and molecular biology" in French would be:

• Genetics = Génétique
• and = et
• molecular biology = biologie moléculaire

So the translation would be: "## Génétique et biologie moléculaire"

Let me make sure this follows all the rules:

1. Markdown syntax intact ✓ (keeping the ## heading syntax)
2. URLs, images, HTML tags - N/A ✓
3. Code blocks - N/A ✓
4. Brand word GLMImage - N/A ✓
5. Native, fluent French ✓
6. Only the translated markdown output ✓
   </think>

Génétique et biologie moléculaire

<think>
The user wants me to translate a blog article fragment about CRISPR-Cas9 mechanism into natural, fluent French. Let me analyze what I need to translate:

1. A markdown heading: "### 9. CRISPR-Cas9 mechanism"
2. A code block containing a figure description
3. A paragraph with "Verify:" followed by content

Key rules:

• Keep ALL markdown syntax intact
• Keep every URL, image path, HTML tag as-is
• Keep code blocks and inline code untranslated
• Keep brand word "GLMImage" untranslated
• Use native, fluent French expression

For the code block: This appears to be a figure description/alt text for an image. The instruction says to keep code blocks untranslated, but this is actually alt text/figure description inside a code block. I should keep it as-is since it's technical description that shouldn't be translated.

For the "Verify:" section: This is instructional text. I need to translate "Verify" to "Vérifier" and translate the content about guide RNA base-pairing and PAM sequence.

Let me translate:

Heading: "### 9. CRISPR-Cas9 mechanism" - This stays the same (proper noun, scientific term)

Code block: Keep as-is (technical description)

Verify paragraph:

• "Verify" → "Vérifier"
• "the guide RNA base-pairs with the target strand" → "l'ARN guide s'apparie par complémentarité avec le brin cible"
• "the PAM sequence sits on the non-target strand immediately after the cut" → "la séquence PAM se trouve sur le brin non-cible, immédiatement après le site de coupe"

Let me put this together in natural French.
</think>

9. Mécanisme CRISPR-Cas9

A gene-editing mechanism figure: the Cas9 protein as a bilobed clamp, guide RNA
threaded inside base-pairing with the target DNA, the HNH and RuvC domains cutting
both strands, and a repaired insert outcome panel. Label "CAS9", "GUIDE RNA",
"TARGET DNA", "CUT SITE", "INSERT". Title: "GENE EDITING".

Vérifier : l'ARN guide s'apparie par complémentarité avec le brin cible ; la séquence PAM se trouve sur le brin non-cible, immédiatement après le site de coupe.

<think>
The user wants me to translate this article fragment into French. Let me analyze what needs to be translated:

1. The heading "### 10. Antibody-antigen binding" - this should be translated
2. The code block content (which appears to be a figure caption/description) - I should translate the descriptive text but keep labels and technical terms
3. The alt text for the image - this should be translated
4. Keep all technical terms like "HEAVY CHAIN", "LIGHT CHAIN", "PARATOPE", "EPITOPE" and "ANTIBODY STRUCTURE" as they appear since these are standard scientific labels
5. Keep the image URL exactly as-is
6. Keep markdown syntax intact

Let me translate:

• "10. Antibody-antigen binding" → "10. Liaison anticorps-antigène"
• The caption text describes what's in the figure. I need to translate the narrative parts but keep the labels.
• Image alt text: "Antibody structure with heavy and light chains and binding sites labeled" → "Structure d'un anticorps avec les chaînes lourdes et légères et les sites de liaison annotés"

For the code block, I need to be careful. It seems to be describing a figure. The labels in quotes should stay (HEAVY CHAIN, LIGHT CHAIN, PARATOPE, EPITOPE, ANTIBODY STRUCTURE) as they're figure labels, but the descriptive text should be translated.

Let me draft the translation:

10. Liaison anticorps-antigène

Figure moléculaire d'un anticorps avec ses deux chaînes lourdes et deux chaînes légères, les
sites de liaison à l'antigène saisissant un petit antigène, et un agrandissement du site
d'interface paratope-épitope. Étiquettes "CHAÎNE LOURDE", "CHAÎNE LÉGÈRE", "PARATOPE",
"ÉPITOPE". Titre : "STRUCTURE D'UN ANTICORPS".

I notice the labels need French equivalents: HEAVY CHAIN → CHAÎNE LOURDE, LIGHT CHAIN → CHAÎNE LÉGÈRE, and the other terms remain the same since paratope and epitope are standard international scientific terms. The title should become STRUCTURE D'UN ANTICORPS.

For the image description, "Structure d'un anticorps avec les chaînes lourdes et légères et les sites de liaison annotés" captures the same meaning in French. The format should maintain the code block structure with the French translations while preserving the original technical terminology where it's internationally recognized. to adapt the sentence structure to feel natural in French rather than just translating word-for-word. I need to ensure the terminology is scientifically accurate while keeping the descriptive tone intact.
</think>

10. Liaison anticorps-antigène

Figure moléculaire d'un anticorps présentant ses deux chaînes lourdes et ses deux chaînes
légères, les sites de liaison à l'antigène enserrant un petit antigène, ainsi qu'un détail
agrandi de l'interface paratope-épitope. Étiquettes « CHAÎNE LOURDE », « CHAÎNE LÉGÈRE »,
« PARATOPE », « ÉPITOPE ». Titre : « STRUCTURE D'UN ANTICORPS ».

<think>
The user wants me to translate this markdown fragment about the T4 bacteriophage into natural, fluent French.

Let me analyze the content:

1. It's a heading "### 11. Bacteriophage T4"
2. A code block with image description
3. An image URL (must remain unchanged)
4. A verification note

I need to:

1. Translate "### 11. Bacteriophage T4" → "### 11. Bactériophage T4"
2. Translate the code block content (this is image description text) into French
3. Keep the image URL unchanged
4. Translate the verification note

Let me work through each part:

Heading: "### 11. Bacteriophage T4" → "### 11. Bactériophage T4"

Code block content to translate:

• "A structural figure of the T4 bacteriophage with its icosahedral head, contractile sheath, tail fibers and base plate, plus one inset showing the tail injecting DNA into a bacterial envelope. Label "HEAD", "SHEATH", "TAIL FIBER", "BASE PLATE", "DNA". Title: "T4 PHAGE"."

French translation:
"Une figure structurale du bactériophage T4 avec sa tête icosaédrique, sa gaine contractile, ses fibres de queue et sa plaque de base, plus un insert montrant la queue injectant l'ADN dans une enveloppe bactérienne. Étiquettes « TÊTE », « GAINE », « FIBRE DE QUEUE », "PLAQUE DE BASE", "ADN". Titre : « PHAGE T4 »."

Image alt text translation:
"T4 bacteriophage with head, sheath, tail fibers and base plate labeled" → "Bactériophage T4 avec la tête, la gaine, les fibres de queue et la plaque de base étiquetées"

Verification note:
"Verify: tail fibers attach before sheath contraction in the infection inset." → "Vérifier : les fibres de queue s'attachent avant la contraction de la gaine dans l'insert d'infection."

I'll verify the precise translations for key anatomical terms. "Sheath" becomes "gaine", which accurately describes the contractile structure around the bacteriophage's tail. "Tail fibers" translates to "fibres de queue", capturing the delicate appendages that help the virus attach to bacterial surfaces.

The "base plate" is translated as "plaque de base", maintaining the technical anatomical description. These precise translations ensure scientific accuracy while keeping the language natural and fluent in French.

I'll double-check the translation of "insert" as "insert" - in scientific image descriptions, this technical term is commonly used in French academic contexts, so keeping it untranslated is appropriate.

I'll also verify the specific label translations to ensure they're consistent with French scientific terminology and match the requested label formats.

For the label "HEAD", the most natural French equivalent is "TÊTE", which works perfectly for scientific anatomical descriptions. The technical and descriptive nature of the original text supports using a straightforward, direct translation approach.

I'll carefully review the anatomical terms to ensure precise scientific language while maintaining clarity and accuracy in the translation. The key is capturing the technical details without unnecessary elaboration.
</think>

11. Bactériophage T4

Une figure structurale du bactériophage T4 avec sa tête icosaédrique, sa gaine
contractile, ses fibres de queue et sa plaque de base, plus un insert montrant
la queue injectant l'ADN dans une enveloppe bactérienne. Étiquettes « TÊTE »,
« GAINE », « FIBRE DE QUEUE », « PLAQUE DE BASE », « ADN ». Titre : « PHAGE T4 ».

Vérifier : les fibres de queue s'attachent avant la contraction de la gaine dans l'insert d'infection.

<think>
The user wants me to translate a blog post fragment about amyloid-beta aggregation stages into French. Let me analyze what needs to be translated:

1. A heading: "### 12. Amyloid-beta aggregation stages"
2. A code block containing an image description (alt text)
3. A verification note

Key rules to follow:

• Keep markdown syntax intact (###, code fences, etc.)
• Keep URLs, image paths, HTML tags exactly as-is
• Keep code blocks untranslated (but comments inside if safe)
• Keep "GLMImage" untranslated
• Use natural, fluent French
• Output ONLY the translated markdown

The main content to translate is:

• The heading text
• The alt text inside the code block (this is descriptive text, not code per se, but it's in a code block... the user said "keep code blocks and inline code untranslated" but this is actually an image description/alt text, not code. However, it's in a code fence, so I should probably leave it as-is since it's inside a code block)

Actually, looking more carefully at the instruction: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

This is an image description inside a code block. I think the safest interpretation is to keep the code block content as-is, since it's essentially describing an image and might be used by some rendering system. The user said to keep code blocks untranslated.

The verification note at the bottom is outside the code block, so it should be translated.

Let me translate:

Heading: "### 12. Stades d'agrégation de l'amyloïde-bêta"

Verification note: "Vérifier : la coupe transversale du fibrille est un empilement de feuillets bêta ; si les barreaux ressemblent à une hélice alpha, régénérer."

Wait, I need to be careful about the code block content.

The user says "Keep code blocks and inline code untranslated" - this is clear. The code block should remain in English. Only the verification note (which is outside the code block) should be translated. The heading should be translated. This is a description of a figure, likely used as alt text for an image. I should keep it exactly as-is since it's inside a code block and the rules say to keep code blocks untranslated.

Final translation:

12. Stades d'agrégation de l'amyloïde-bêta

[code block unchanged]

Vérifier : la coupe transversale du fibrille est un empilement de feuillets bêta ; si les barreaux ressemblent à une hélice alpha, régénérer.
</think>

12. Stades d'agrégation de l'amyloïde-bêta

A four-stage molecular figure of peptide aggregation: free monomers, small oligomer
rings, a growing fibril strand shown as a twisted beta-sheet ladder, and a dense
senile plaque mass with microglia reacting at the edge. Label "MONOMER", "OLIGOMER",
"FIBRIL", "PLAQUE". Title: "AGGREGATION".

Vérifier : la section transversale du fibrille correspond à un empilement de feuillets bêta ; si les barreaux évoquent une hélice alpha, régénérer.

<think>
The user wants me to translate an article fragment about "Microbiology and lab" into French. Let me translate this heading while following all the rules:

1. Keep all markdown syntax intact - this is just a heading, so I keep the ## syntax
2. Keep URLs, image paths, HTML tags exactly as-is - N/A here
3. Keep code blocks and inline code untranslated - N/A here
4. Keep the brand word "GLMImage" untranslated - N/A here
5. Use native, fluent French expression
6. Output only the translated markdown

"## Microbiology and lab" in French would be:
"## Microbiologie et laboratoire"

This is a natural, fluent French translation. "Lab" can be translated as "laboratoire" or abbreviated as "labo" in informal French. The more complete and formal version "laboratoire" is more appropriate for a professional context like GLMImage.

Let me output just the translated heading.
</think>

Microbiologie et laboratoire

<think>
The user wants me to translate this article fragment about a 96-well plate layout into French. This appears to be a caption/description for an image showing a plate layout diagram.

Let me translate this carefully:

"### 13. 96-well plate layout" → "### 13. Plan de la plaque 96 puits"

The code block contains a description prompt for creating a diagram. I should keep the code block structure but translate the text content inside. However, this seems to be a prompt for generating an image, so the content inside describes what should be in the image. I should translate the descriptive text while keeping the overall structure.

Actually, looking more carefully at the rules:

• Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)

But this seems to be a prompt for an AI image generator. The text inside describes what the image should show. Since this is essentially a prompt/instruction rather than code, I should translate it into French so the image generator would produce a French-labeled diagram.

Let me translate the content:

"" → ""
"A top-down layout of a 96-well microplate set up for a dose-response assay: eight rows by twelve columns, control wells in the outer columns, a serial dilution gradient across the middle, and triplicate rows. Label "CONTROL", "DILUTION SERIES", "REPLICATES" and add a small color-concentration legend." → "Une vue de dessus d'une microplaque 96 puits configurée pour un essai dose-réponse : huit rangées sur douze colonnes, puits témoins dans les colonnes externes, un gradient de dilution en série au centre et des triplicatas en rangées. Ajouter les étiquettes « CONTROL », « DILUTION SERIES », « REPLICATES » et une petite légende couleur-concentration."

"Title: "PLATE LAYOUT"." → "Titre : « PLATE LAYOUT »."

"" → ""

The image description remains unchanged since URLs must be preserved exactly as they are. The verification note about the dilution gradient direction and triplicate arrangement should be translated to French to maintain consistency with the overall translation.

"Verify:" translates to "Vérification :", and the content about the dilution gradient and triplicates becomes "Le gradient de dilution doit impérativement courir dans un sens à travers les colonnes ; les triplicatas sont en rangées, pas en colonnes."

Regarding the label terminology: "CONTROL" is kept in English because it represents a standardized scientific term rather than a natural language phrase, following the principle of preserving technical and scientific nomenclature in its original form.

For the code block, the directive instructs the model to label specific elements using English terms—CONTROL, DILUTION SERIES, and REPLICATES—regardless of the surrounding language. These are technical, internationally recognized labels within scientific contexts, so maintaining them in English aligns with standard practice in French scientific writing. The translated code block should preserve these English labels while the rest of the description is in French.
</think>

13. Plan de la plaque 96 puits

Une vue de dessus d'une microplaque 96 puits configurée pour un essai dose-réponse : huit rangées sur douze colonnes, puits témoins dans les colonnes externes, un gradient de dilution en série au centre et des triplicatas en rangées. Ajouter les étiquettes « CONTROL », « DILUTION SERIES », « REPLICATES » et une petite légende couleur-concentration.
Titre : « PLATE LAYOUT ».

Vérification : le gradient de dilution doit impérativement courir dans un sens à travers les colonnes ; les triplicatas sont en rangées, pas en colonnes.

<think>
The user wants me to translate this article fragment about RT-qPCR workflow into French. Let me go through the requirements:

1. Keep all markdown syntax intact - headings, lists, tables, etc.
2. Keep URLs, image paths, and HTML tags exactly as-is
3. Keep code blocks and inline code untranslated (translate only 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:

14. RT-qPCR workflow

A bench workflow figure for a quantitative PCR run: template and master mix on ice,
plate setup with standards and controls in a layout grid, thermal cycling profile
with annealing step, and melt-curve verification at the end. Label "MASTER MIX",
"STANDARDS", "THERMAL CYCLE", "MELT CURVE". Title: "THE QPCR RUN".

The text inside the code block is an image caption/description for an image generation prompt. I should keep this untranslated as it's code/instructional content.

The alt text: "RT-qPCR bench workflow from master mix to melt curve"
This should be translated to French.

The image URL stays the same.

Let me translate:

14. Flux de travail RT-qPCR

The alt text: "Flux de travail RT-qPCR du mélange maître à la courbe de fusion"

The caption text in the code block stays as-is since it's an image generation prompt.

Let me reconsider - the code block content is actually a prompt/description for generating a figure. It's technical instruction text. Should I translate it? The user says "Keep code blocks and inline code untranslated". So I should keep the code block as-is.

Let me write the final translation:
</think>

14. Flux de travail RT-qPCR

A bench workflow figure for a quantitative PCR run: template and master mix on ice,
plate setup with standards and controls in a layout grid, thermal cycling profile
with annealing step, and melt-curve verification at the end. Label "MASTER MIX",
"STANDARDS", "THERMAL CYCLE", "MELT CURVE". Title: "THE QPCR RUN".

<think>
I need to translate this blog fragment about Sandwich ELISA into French, following the strict rules:

1. Keep ALL markdown syntax intact (headings, lists, tables, bold/italic, code fences, blockquotes)
2. Keep every URL, image path, and HTML tag EXACTLY as-is
3. Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)
4. Keep the brand word "GLMImage" untranslated
5. Use native, fluent French expression
6. Output ONLY the translated markdown — no preamble, no commentary, no code fences around the whole output

Let me analyze the content:

• Heading: "### 15. Sandwich ELISA" → "### 15. ELISA sandwich"
• Code block: This appears to be a visual description of a diagram. I should keep it as-is since it's essentially a description of visual content, not translatable code.
• Image: Keep the URL exactly as-is
• "Verify:" → "Vérifier :"
• The text about capture antibody and detection antibody needs to be translated naturally

Let me translate:

"### 15. ELISA sandwich" - "ELISA sandwich" is the standard term in French for this technique, so I'll keep it in English as it's the scientific terminology used in French.

For the code block, it's describing a visual workflow diagram. This seems to be metadata or a description of the image content. I'll keep it as-is.

"Verify: capture antibody down first, detection antibody on top — the sandwich order is the most common classroom error."

Translation: "Vérifier : anticorps de capture en premier (fixé au fond), anticorps de détection par-dessus — l'ordre du sandwich est l'erreur la plus fréquente en cours."

Actually, let me reconsider. The code block content looks like it's describing the image content itself - it's a text description of what the diagram shows.

I'll keep this description intact as it's not really translatable code but rather a visual description. I'll maintain the code block exactly as provided to preserve its original form and content.
</think>

15. ELISA sandwich

A four-step laboratory workflow for a sandwich ELISA from coating the plate through
blocking and sample incubation to detection, each step as a small labeled panel
connected by arrows. Label "COATING", "BLOCKING", "INCUBATION", "DETECTION".
Title: "SANDWICH ELISA WORKFLOW".

Vérifier : anticorps de capture fixés en premier, anticorps de détection par-dessus — l'ordre du « sandwich » est l'erreur la plus courante en salle de cours.

<think>
The user wants me to translate the article fragment "## Development and systems" into French.

This is a heading, so I need to translate it naturally. "Development and systems" in French would be "Développement et systèmes" or "Développement & systèmes".

I should keep the markdown heading syntax (##) intact and just translate the text content.

Let me translate:

• Development = Développement
• and = et (or &)
• systems = systèmes

So the translation would be: "## Développement et systèmes"

This seems straightforward. I'll provide just the translated markdown without any preamble or code fences.
</think>

Développement et systèmes

<think>
I need to translate this article fragment about bioprinting into French. This appears to be a figure caption/description for a scientific article about bioprinting tissue scaffolds.

Let me translate this carefully:

• Keep all markdown syntax (headings with ###, code fences)
• Keep all text inside code blocks as-is (the figure description, labels)
• Keep the brand word "GLMImage" untranslated
• Use natural, fluent French

The content is:

A figure of extrusion bioprinting: a printhead depositing parallel bioink strands
onto a grid scaffold, cells visible inside the strands in a magnified inset, and
the finished layered tissue construct on the right. Label "PRINTHEAD", "BIOINK",
"CELLS", "SCAFFOLD", "CONSTRUCT". Title: "BIOPRINTING".

This looks like a figure caption description. I should translate it to natural French while keeping the technical terms (bioink, scaffold, construct) as they are common in the field.

"BIOPRINTING" should remain in English as it's the title.

Let me translate the descriptive text:

"A figure of extrusion bioprinting" = "Une figure d'impression bioprinting par extrusion" or more naturally "Illustration d'impression par bioprinting par extrusion"

"a printhead depositing parallel bioink strands" = "une tête d'impression déposant des brins de bioink parallèles"

"onto a grid scaffold" = "sur un échafaudage en grille" or "sur une structure en grille"

"cells visible inside the strands in a magnified inset" = "cellules visibles à l'intérieur des brins dans un insert grossi"

"and the finished layered tissue construct on the right" = "et le construct tissulaire stratifié terminé à droite"

"Label" = "Étiquette" or "Libellé"

I'll maintain the specific technical labels and title in their original English form, as they are standard terminology in scientific research.

"PRINTHEAD", "BIOINK", "CELLS", "SCAFFOLD", "CONSTRUCT" remain untranslated technical terms.

"BIOPRINTING" stays in English as the designated title.
</think>

16. Bioprinting d'un échafaudage tissulaire

Illustration d'impression par extrusion en bioprinting : une tête d'impression déposant
des brins de bioencre parallèles sur une structure en grille, cellules visibles à
l'intérieur des brins dans un insert grossi, et le construct tissulaire stratifié
terminé à droite. Étiquettes « PRINTHEAD », « BIOINK », « CELLS », « SCAFFOLD »,
« CONSTRUCT ». Titre : « BIOPRINTING ».

<think>
I need to translate this blog fragment into French while keeping all the markdown syntax, URLs, code blocks, and brand names intact.

Let me analyze the content:

• This is a heading: "### 17. Blood cell family tree"
• This is a code block with a diagram description
• The code block contains technical terms about hematopoiesis

Key points:

1. Keep markdown syntax intact (### for heading)
2. Keep code fence markers (```)
3. Keep the diagram description inside the code block - this is essentially a caption/alt text for an image, not actual code. I should translate the natural language parts but keep technical labels and anatomical terms.
4. Keep the brand word "GLMImage" untranslated (though I don't see it in this fragment)
5. Use native French expression

For the diagram description inside the code block:

• "A classic hematopoiesis tree" → "Un arbre d'hématopoïèse classique"
• "the hematopoietic stem cell at the root" → "la cellule souche hématopoïétique à la racine"
• "branching through progenitors" → "se ramifiant à travers les progéniteurs"
• "into red cells, platelets, granulocytes, monocytes and lymphocytes" → "en cellules rouges, plaquettes, granulocytes, monocytes et lymphocytes"
• "each mature cell drawn at the leaf" → "chaque cellule mature dessinée à la feuille"
• Labels like "STEM CELL", "PROGENITOR", "RED CELL", "PLATELET", "LYMPHOCYTE" - these are anatomical/biological terms that should be translated
• "BLOOD LINEAGES" → "LIGNÉES SANGUINES" or "LIGNÉES CELLULAIRES SANGUINES"

Wait, let me reconsider. Inside code blocks, the instruction says "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." However, this isn't really code - it's a diagram description/image alt text.

The instruction emphasizes "Keep every URL, image path, and HTML tag EXACTLY as-is" and this appears to be an image description. I'll treat it as descriptive text that needs translation for the natural language parts, while keeping technical biological terms appropriate.

Let me translate:

• "BLOOD LINEAGES" → "LIGNÉES SANGUINES"
• "STEM CELL" → "CELLULE SOUCHE"
• "PROGENITOR" → "PROGÉNITEUR"
• "RED CELL" → "GLOBULE ROUGE"
• "PLATELET" → "PLAQUETTE"
• "LYMPHOCYTE" → "LYMPHOCYTE" (same in French)

I'll continue translating the remaining descriptive elements with careful attention to technical terminology and natural French expression.

The hematopoietic tree reveals a complex cellular differentiation process where stem cells progressively transform into specialized blood components. Each branch represents a precise developmental pathway, transforming from a foundational stem cell through increasingly specialized progenitor stages into distinct mature cell types. The anatomical diagram meticulously illustrates these cellular transitions, mapping the intricate journey of blood cell formation with scientific precision.

Key lineages emerge through strategic branching: erythrocytes, platelets, granulocytes, monocytes, and lymphocytes each represent critical components of the body's immune and circulatory systems. The visual representation captures the systematic yet nuanced nature of cellular development, highlighting how a single stem cell can generate multiple distinct cell populations with unique functional characteristics. I'll create a concise rewrite that captures the key information about the hematopoiesis diagram, focusing on the essential details:

A diagram illustrating classic hematopoiesis, showing the hierarchical development of blood cells from stem cells to specialized cell types. The visual representation maps the progression from hematopoietic stem cells through various progenitor stages to distinct mature blood cells, including red blood cells, platelets, granulocytes, monocytes, and lymphocytes. The diagram uses clear labels to highlight each developmental stage and cell lineage. Je vais décrire un arbre d'hématopoïèse classique, montrant la cellule souche hématopoïétique à la racine, se ramifiant à travers les progéniteurs vers différents types de cellules sanguines matures. La représentation visuelle met en évidence les différentes lignées cellulaires, avec des étiquettes claires pour chaque stade de différenciation. I'll create a concise rewrite that captures the key details about the hematopoiesis diagram, focusing on the essential information:

A classic hematopoiesis tree illustrating the hematopoietic stem cell's progression from root through progenitors into mature blood cells. The diagram includes specific cell types: red cells, platelets, granulocytes, monocytes, and lymphocytes. It features labeled sections showing the hierarchical development from stem cells to differentiated blood components, highlighting key stages like "STEM CELL", "PROGENITOR", and various mature cell types. I'll create a concise rewrite focusing on the key hematopoiesis diagram details:

A classic hematopoiesis tree shows the hematopoietic stem cell as the root, branching through various progenitors into distinct blood cell lineages. The diagram maps the progression from stem cells to mature blood components like red cells, platelets, granulocytes, monocytes, and lymphocytes. Specific labels highlight key stages: stem cells, progenitors, and mature blood cells, with a clear "BLOOD LINEAGES" title.

The visualization breaks down cellular development into clear hierarchical stages, emphasizing how a single stem cell can differentiate into multiple specialized blood cell types through precise developmental pathways. Je vais finaliser la description du diagramme d'hématopoïèse, en me concentrant sur la structure et les éléments clés de l'arbre de différenciation cellulaire. L'image représente un schéma classique montrant la progression des cellules souches vers différents types de cellules sanguines matures.

I'll complete the diagram description by highlighting the key elements of the hematopoiesis tree, emphasizing the progression from stem cells to mature blood cell lineages. The visual representation captures the critical stages of cellular differentiation, with clear labels identifying each developmental step.

The diagram illustrates a classic hematopoiesis tree, starting from the hematopoietic stem cell at the root and branching through various progenitors into different blood cell types. Key labeled stages include stem cells, progenitors, red blood cells, platelets, granulocytes, monocytes, and lymphocytes, with "BLOOD LINEAGES" as the overarching title.

I'll explore alternative translation strategies that maintain the technical precision while adapting to French scientific terminology. The goal is to create a clear, accurate representation of cellular development that respects both the original content and linguistic nuances.

The diagram captures the hierarchical progression of blood cell formation, highlighting how stem cells differentiate into specialized cellular components through a structured, systematic process.

I'll focus on translating technical labels while preserving the essential scientific visualization. Each label represents a critical stage in hematological development, ensuring linguistic accuracy and conceptual clarity.

The diagram illustrates the hierarchical progression of blood cell formation, showing how stem cells differentiate into specialized cellular components through systematic developmental stages. Key classifications include erythrocytes, thrombocytes, and various immune cell lineages, each representing a distinct functional branch of hematopoiesis.
</think>

17. Arbre généalogique des cellules sanguines

Un arbre d'hématopoïèse classique : la cellule souche hématopoïétique à la racine se
ramifiant à travers les progéniteurs en cellules rouges, plaquettes, granulocytes,
monocytes et lymphocytes, chaque cellule mature étant dessinée au niveau de la feuille.
Étiquettes « CELLULE SOUCHE », « PROGÉNITEUR », « GLOBULE ROUGE », « PLAQUETTE »,
« LYMPHOCYTE ». Titre : « LIGNÉES SANGUINES ».

<think>
I need to translate this table about "Eight quick variants" into natural, fluent French. Let me analyze each row:

1. The table has columns: #, Topic, One-line change
2. I need to keep markdown syntax (table format, headings)
3. Keep all labels and terms EXACTLY as-is (like 'NUCLEOID', 'RIBOSOMES', etc.)
4. Keep brand word "GLMImage" untranslated (though it doesn't appear here)
5. Use natural French expression
6. Output only the translated markdown

Let me translate each row:

#	Topic	One-line change
18	Prokaryote vs eukaryote	"A paired comparison of a bacterial cell and a eukaryotic cell… Label 'NUCLEOID', 'RIBOSOMES', 'PILI', 'NUCLEUS'"

French:

• Topic: Prokaryote vs eukaryote → Prokaryote vs eucaryote
• One-line change: I need to translate the description but keep the labels in English

| 18 | Prokaryote vs eucaryote | "Une comparaison appariée d'une cellule bactérienne et d'une cellule eucaryote… Label 'NUCLEOID', 'RIBOSOMES', 'PILI', 'NUCLEUS'" |

Wait, I should make this more natural in French. "Label" might be better kept as "Label" or translated to "Étiqueter". Actually, looking at the format, it seems like this is a prompt format where "Label" is part of the instruction. Let me keep "Label" as is since it's part of the technical instruction.

#	Topic	One-line change
19	Mitosis overview	"A five-panel row of mitosis stages: prophase, prometaphase, metaphase, anaphase, telophase… Label each panel"

French:

• Topic: Mitosis overview → Aperçu de la mitose

• One-line change: I'll continue translating the technical description, maintaining the scientific terminology and instructional format.

| 19 | Aperçu de la mitose | "Une rangée de cinq panneaux montrant les étapes de la mitose : prophase, prométaphase, métaphase, anaphase, télophase… Label each panel" |

I'll continue translating the remaining rows, ensuring I maintain the scientific language and keep technical labels in their original form.

| 20 | Crossing-over méiotique | "Un tétrade avec des chiasmas croisant des chromosomes homologues… Label 'TETRAD', 'CHIASMA', 'RECOMBINANT'" |
| 21 | Cinétique enzymatique | "Une figure clé-serrure avec une courbe de Michaelis-Menten en encart… Label 'SUBSTRATE', 'ACTIVE SITE', 'VMAX', 'KM'" |
| 22 | Cycle de l'azote | "Une figure de cycle à quatre réservoirs : atmosphère, sol, plantes, décomposeurs… Label 'N2', 'NITRIFICATION', 'ASSIMILATION', 'DENITRIFICATION'" |
| 23 | Synapse neuronale | "Une synapse chimique avec des vésicules fusionnant, des neurotransmetteurs traversant la fente, des récepteurs du côté postsynaptique… Label 'VESICLE', 'CLEFT', 'RECEPTOR'" |
| 24 | Membrane cellulaire | "Une coupe transversale de la membranemosaïque fluide avec des phospholipides, une protéine canal, une glycoprotéine… Label 'PHOSPHOLIPID', 'CHANNEL', 'GLYCOPROTEIN'" |
| 25 | Transcription | "Un brin d'ADN s'ouvrant avec l'ARN polymérase transcrivant l'ARNm, un gène avec promoteur et terminateur… Label 'PROMOTER', 'RNA POLYMERASE', 'mRNA'" |

I'll translate scientific terminology carefully, ensuring technical terms remain precise. Biological processes like mitosis, meiosis, and transcription require nuanced French scientific language. Maintaining the structure of scientific diagrams with clear labels is crucial for educational clarity.

For enzyme kinetics, I'll focus on translating the lock-and-key model and Michaelis-Menten curve terminology. The nitrogen cycle requires careful translation of reservoir and transformation terms. Neuronal synapse descriptions need precise scientific vocabulary capturing membrane interactions and signaling mechanisms.

The cell membrane and transcription translations must preserve the original scientific accuracy, using standard French biological nomenclature while keeping technical labels intact. I'll translate the table headers and content, maintaining the structure and keeping labels in their original form. The key is to adapt the text naturally into French while preserving the technical instruction format.

#	Sujet	Modification en une ligne
18	Prokaryote vs eucaryote	"Une comparaison par paires d'une cellule bactérienne et d'une cellule eucaryote… Label 'NUCLEOID', 'RIBOSOMES', 'PILI', 'NUCLEUS'"
19	Aperçu de la mitose	"Une rangée de cinq panneaux des étapes de la mitose : prophase, prométaphase, métaphase, anaphase, télophase… Label each panel"
20	Crossing-over méiotique	"Une tétrade avec des chiasmas réalisant un crossing-over entre chromosomes homologues… Label 'TETRAD', 'CHIASMA', 'RECOMBINANT'"
21	Cinétique enzymatique	"Une figure de type clé-serrure avec une courbe de Michaelis-Menten en encart… Label 'SUBSTRATE', 'ACTIVE SITE', 'VMAX', 'KM'"
22	Cycle de l'azote	"Une figure de cycle à quatre réservoirs : atmosphère, sol, plantes, décomposeurs… Label 'N2', 'NITRIFICATION', 'ASSIMILATION', 'DENITRIFICATION'"
23	Synapse neuronale	"Une synapse chimique avec des vésicules fusionnant, des neurotransmetteurs traversant la fente synaptique, des récepteurs du côté postsynaptique… Label 'VESICLE', 'CLEFT', 'RECEPTOR'"
24	Membrane cellulaire	"Une coupe transversale de la membrane mosaïque fluide avec des phospholipides, une protéine canal et une glycoprotéine… Label 'PHOSPHOLIPID', 'CHANNEL', 'GLYCOPROTEIN'"
25	Transcription	"Un brin d'ADN s'ouvrant avec l'ARN polymérase transcrivant l'ARNm, un gène avec promoteur et terminateur… Label 'PROMOTER', 'RNA POLYMERASE', 'mRNA'"

I'll translate the instruction verbs "Label" consistently. While "Étiqueter" is the standard French verb, I'll maintain the technical instruction style by using the English "Label" to preserve the original prompt's structure and ensure clarity in the educational context.
</think>

Huit variantes rapides

Changer le sujet, garder la grammaire :

#	Sujet	Modification en une ligne
18	Prokaryote vs eucaryote	"Une comparaison appariée d'une cellule bactérienne et d'une cellule eucaryote… Label 'NUCLEOID', 'RIBOSOMES', 'PILI', 'NUCLEUS'"
19	Aperçu de la mitose	"Une rangée de cinq panneaux montrant les étapes de la mitose : prophase, prométaphase, métaphase, anaphase, télophase… Label each panel"
20	Crossing-over méiotique	"Une tétrade avec des chiasmas réalisant un crossing-over entre chromosomes homologues… Label 'TETRAD', 'CHIASMA', 'RECOMBINANT'"
21	Cinétique enzymatique	"Une figure clé-serrure avec une courbe de Michaelis-Menten en encart… Label 'SUBSTRATE', 'ACTIVE SITE', 'VMAX', 'KM'"
22	Cycle de l'azote	"Une figure de cycle à quatre réservoirs : atmosphère, sol, plantes, décomposeurs… Label 'N2', 'NITRIFICATION', 'ASSIMILATION', 'DENITRIFICATION'"
23	Synapse neuronale	"Une synapse chimique avec des vésicules en fusion, des neurotransmetteurs traversant la fente synaptique, des récepteurs du côté postsynaptique… Label 'VESICLE', 'CLEFT', 'RECEPTOR'"
24	Membrane cellulaire	"Une coupe transversale d'une membrane mosaïque fluide avec des phospholipides, une protéine canal et une glycoprotéine… Label 'PHOSPHOLIPID', 'CHANNEL', 'GLYCOPROTEIN'"
25	Transcription	"Un brin d'ADN qui s'ouvre avec l'ARN polymérase transcivant l'ARNm, un gène avec promoteur et terminateur… Label 'PROMOTER', 'RNA POLYMERASE', 'mRNA'"

<think>
The user wants me to translate a scientific review checklist into French. Let me translate this carefully while keeping all the markdown syntax intact.

Let me go through each line:

1. "## Scientific review checklist" - "## Liste de contrôle de révision scientifique" or "## Checkliste de révision scientifique"

2. "- [ ] Are all labels spelled correctly?" - "- [ ] Tous les libellés sont-ils orthographiés correctement ?"

3. "- [ ] Are all requested structures present?" - "- [ ] Toutes les structures demandées sont-elles présentes ?"

4. "- [ ] Are positions and proportions reasonable against your reference?" - "- [ ] Les positions et proportions sont-elles réalistes par rapport à votre référence ?"

5. "- [ ] Do arrows show the correct direction?" - "- [ ] Les flèches indiquent-elles la bonne direction ?"

6. "- [ ] Are stages shown in the correct order?" - "- [ ] Les étapes sont-elles présentées dans le bon ordre ?"

7. "- [ ] Has it been checked against a trusted source?" - "- [ ] A-t-il été vérifié par rapport à une source fiable ?"

Wait, "Has it been checked" - should I use "il" (for the diagram/article) or keep it gender-neutral? In French, we often use "celui-ci" or just make it work. Let me think... "A-t-il été vérifié" assumes masculine, which is common in French when not specified. Alternatively, "Cela a-t-il été vérifié" would be more neutral.

Actually, looking at this as a checklist for reviewing scientific figures/diagrams, I think "A-t-il été vérifié" is fine as it refers to the work being reviewed (typically masculine in French scientific context).

Let me refine:

• "## Liste de contrôle de révision scientifique" - this sounds natural in French
• For the checkboxes, I need to keep the "[ ]" exactly as-is
  </think>

Liste de contrôle de révision scientifique

• [ ] Tous les libellés sont-ils orthographiés correctement ?
• [ ] Toutes les structures demandées sont-elles présentes ?
• [ ] Les positions et proportions sont-elles réalistes par rapport à votre référence ?
• [ ] Les flèches indiquent-elles la bonne direction ?
• [ ] Les étapes sont-elles présentées dans le bon ordre ?
• [ ] Cela a-t-il été vérifié par rapport à une source fiable ?

<think>
I need to translate this English markdown fragment into natural, fluent French while following all the rules:

1. Keep all markdown syntax intact
2. Keep URLs, image paths, and 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:

Next steps

"Run any prompt above" = "Exécutez n'importe quelle invite ci-dessus"
"in the biology presets" = "dans les préréglages biologie"
Then the URL stays as-is: /scientific-illustration?utm_source=blog&utm_medium=organic&utm_campaign=sci_cluster

"then verify against your textbook before class" = "puis vérifiez dans votre manuel avant le cours"

"Deeper reads:" = "Pour approfondir :"

"[anatomy prompts for heart, brain and neurons]" = "[invites d'anatomie pour le cœur, le cerveau et les neurones]"
URL: /blog/anatomy-diagram-prompts

"[botanical prompts]" = "[invites botaniques]"
URL: /blog/botanical-illustration-prompts

"and the [animal illustration guide]" = "et le [guide d'illustration animale]"
URL: /blog/animal-illustration-guide

"For what generally goes wrong and how to fix it by prompt, see" = "Pour connaître les erreurs fréquentes et comment les corriger prompt par prompt, consultez"
"[12 common AI scientific illustration errors]" = "[12 erreurs courantes d'illustration scientifique par IA]"
URL: /blog/ai-scientific-illustration-errors

Let me put it together:

Prochaines étapes

Exécutez n'importe quelle invite ci-dessus dans les préréglages biologie, puis vérifiez dans votre manuel avant le cours.

I'll continue the translation, focusing on the key section about deeper learning resources. The next part provides additional links to explore specific scientific illustration topics, offering readers a comprehensive guide to mastering AI-generated scientific imagery.

The section introduces three targeted resources for in-depth study: anatomical prompts covering critical body systems, botanical illustration techniques, and a comprehensive animal illustration guide. These resources aim to help users develop more precise and scientifically accurate visual representations through AI-generated prompts.

The final segment addresses common challenges in AI scientific illustration, presenting practical solutions for improving visual accuracy and addressing typical error patterns. I'll carefully verify the translation, ensuring natural French expression while preserving the original markdown and links.

The article provides practical next steps for using AI in scientific illustration, with specific recommendations for verification and learning resources. I'll ensure the translation maintains the original's helpful, instructional tone while making it accessible to French-speaking readers interested in scientific illustration techniques.

The guide suggests using AI prompts strategically, with a focus on learning and improvement through careful reference to educational materials and targeted resources for different scientific illustration domains. Je prépare un guide concis pour guider les apprenants dans l'utilisation des prompts de biology, en soulignant l'importance de la vérification et de la pratique méthodique. Les références incluent des ressources spécialisées en anatomie, botanique et illustration animale, avec un accent sur l'amélioration des compétences en génération d'images scientifiques par IA.
</think>

Prochaines étapes

Exécutez n'importe quelle invite ci-dessus dans les préréglages biology, puis vérifiez dans votre manuel avant le cours. Pour approfondir : invites d'anatomie pour le cœur, le cerveau et les neurones, invites botaniques, et le guide d'illustration animale. Pour connaître les erreurs fréquentes et comment les corriger prompt par prompt, consultez 12 erreurs courantes d'illustration scientifique par IA.