🌐 Update translations for de (update-outdated)

This PR was created automatically using LLMs.

It uses the prompt file https://github.com/fastapi/fastapi/blob/master/docs/de/llm-prompt.md.

In most cases, it's better to make PRs updating that file so that the LLM can do a better job generating the translations than suggesting changes in this PR.

@@ -189,7 +189,7 @@ [NAME_REDACTED] `### Links` im allgemeinen Prompt in `scripts/translate.py`.

 ////

-## HTML „abbr“-Elemente { #html-abbr-elements }
+## HTML-„abbr“-Elemente { #html-abbr-elements }

 //// tab | Test

@@ -56,19 +56,19 @@ from app.routers import items

 Die gleiche Dateistruktur mit Kommentaren:

-```
+```bash
 .
-├── app                  # „app“ ist ein Python-Package
-│   ├── __init__.py      # diese Datei macht „app“ zu einem „Python-Package“
-│   ├── main.py          # „main“-Modul, z. B. import app.main
-│   ├── dependencies.py  # „dependencies“-Modul, z. B. import app.dependencies
-│   └── routers          # „routers“ ist ein „Python-Subpackage“
-│   │   ├── __init__.py  # macht „routers“ zu einem „Python-Subpackage“
-│   │   ├── items.py     # „items“-Submodul, z. B. import app.routers.items
-│   │   └── users.py     # „users“-Submodul, z. B. import app.routers.users
-│   └── internal         # „internal“ ist ein „Python-Subpackage“
-│       ├── __init__.py  # macht „internal“ zu einem „Python-Subpackage“
-│       └── admin.py     # „admin“-Submodul, z. B. import app.internal.admin
+├── app                  # "app" ist ein Python-Package
+│   ├── __init__.py      # diese Datei macht "app" zu einem "Python-Package"
+│   ├── main.py          # "main"-Modul, z. B. import app.main
+│   ├── dependencies.py  # "dependencies"-Modul, z. B. import app.dependencies
+│   └── routers          # "routers" ist ein "Python-Subpackage"
+│   │   ├── __init__.py  # macht "routers" zu einem "Python-Subpackage"
+│   │   ├── items.py     # "items"-Submodul, z. B. import app.routers.items
+│   │   └── users.py     # "users"-Submodul, z. B. import app.routers.users
+│   └── internal         # "internal" ist ein "Python-Subpackage"
+│       ├── __init__.py  # macht "internal" zu einem "Python-Subpackage"
+│       └── admin.py     # "admin"-Submodul, z. B. import app.internal.admin
 ```

 ## `APIRouter` { #apirouter }
@@ -479,7 +479,7 @@ $ fastapi dev app/main.py

-und öffnen Sie die Dokumentation unter http://127.0.0.1:8000/docs.
+Und öffnen Sie die Dokumentation unter http://127.0.0.1:8000/docs.

 Sie sehen die automatische API-Dokumentation, einschließlich der Pfade aller Submodule, mit den richtigen Pfaden (und Präfixen) und den richtigen Tags:

I also compared locally with the English documents.

Added code change suggestions according to Nils' review

Good. Thanks, Yurii!

Keep.

That was addedd by [NAME_REDACTED] document.

Revert.

The LLM reverts the German translation, despite being told not to do that, see section _Content of code blocks_ at the top of `scripts/general-llm-prompt.md`:

>Do not translate the content of code blocks, except for comments in the language which the code block uses.

I am open to replace the literal quotes though, if that disturbs in code comments.

If this keeps happening we may add another example to `scripts/general-llm-prompt.md`.

Keep.

Good catch.

Keep.

In sync with section _German instructions, when to use and when not to use hyphens in words_ in `docs\de\llm-prompt.md`.

Revert.

See

> You can leave the original full phrase away, if the translated full phrase is identical or starts with the same letters as the original full phrase

in `scripts\general-llm-prompt.md`.

Undecided.

See below.

Undecided.

I once added these `abbr`s to the German docs (here and in other translated documents, once per document), to explain the meaning of _Request_ and _Response_. The LLM keeps removing them, despite being told not to, see:

> If there is an existing translation, and it has ADDITIONAL abbr elements in a sentence, and these additional abbr elements do not exist in the related sentence in the English text, then KEEP those additional abbr elements in the translation.

in `scripts/general-llm-prompt.md`.

I am fine with removing them everywhere or with keeping them everywhere. Any opinions?

Revert.

That is actually wrongly written small in the English `docs\en\docs\_llm-test.md`.

Revert.

The heading above explains how this should be translated. See also the translation schema for `<abbr title="{full phrase}: {other information}">{abbreviation}</abbr>` in `scripts\general-llm-prompt.md`.

```suggestion
* <abbr title="[NAME_REDACTED]">PSGI</abbr>
```

```suggestion
* <abbr title="[NAME_REDACTED] – Mozilla-Entwicklernetzwerk: Dokumentation für Entwickler, geschrieben von den Firefox-Leuten">MDN</abbr>
```

```suggestion
├── app                  # "app" ist ein Python-Package
│   ├── __init__.py      # diese Datei macht "app" zu einem "Python-Package"
│   ├── main.py          # "main"-Modul, z. B. import app.main
│   ├── dependencies.py  # "dependencies"-Modul, z. B. import app.dependencies
│   └── routers          # "routers" ist ein "Python-Subpackage"
│   │   ├── __init__.py  # macht "routers" zu einem "Python-Subpackage"
│   │   ├── items.py     # "items"-Submodul, z. B. import app.routers.items
│   │   └── users.py     # "users"-Submodul, z. B. import app.routers.users
│   └── internal         # "internal" ist ein "Python-Subpackage"
│       ├── __init__.py  # macht "internal" zu einem "Python-Subpackage"
│       └── admin.py     # "admin"-Submodul, z. B. import app.internal.admin
```

```suggestion
Und wir können eine Liste von `dependencies` hinzufügen, die allen *Pfadoperationen* im Router hinzugefügt und für jeden an sie gerichteten <abbr title="Request – Anfrage: Daten, die der Client zum Server sendet">Request</abbr> ausgeführt/aufgelöst werden.
```

```suggestion
Und sie wird auch beide <abbr title="Response – Antwort: Daten, die der Server zum anfragenden Client zurücksendet">Responses</abbr> in der Dokumentation haben, eine für `404` und eine für `403`.
```

```suggestion
* <abbr title="[NAME_REDACTED] von Maschinen, die so konfiguriert sind, dass sie verbunden sind und in irgendeiner Weise zusammenarbeiten.">Cluster</abbr>
```


🌐 Update translation prompts

🌐 Update translation prompts

@@ -4,213 +4,197 @@ Translate to German (Deutsch).

 Language code: de.

-
-### Definitions
-
-"hyphen"
-    The character «-»
-    Unicode U+002D (HYPHEN-MINUS)
-    Alternative names: hyphen, dash, minus sign
-
-"dash"
-    The character «–»
-    Unicode U+2013 (EN DASH)
-    German name: Halbgeviertstrich
-
-
 ### Grammar to use when talking to the reader

-Use the formal grammar (use «Sie» instead of «Du»).
-
+Use the formal grammar (use `Sie` instead of `Du`).

 ### Quotes

-1) Convert neutral double quotes («"») and English double typographic quotes («“» and «”») to German double typographic quotes («„» and «“»). Convert neutral single quotes («'») and English single typographic quotes («‘» and «’») to German single typographic quotes («‚» and «‘»). Do NOT convert «`"» to «„», do NOT convert «"`» to «“».
+1) Convert neutral double quotes (`"`) to German double typographic quotes (`„` and `“`). Convert neutral single quotes (`'`) to German single typographic quotes (`‚` and `‘`).

-Examples:
+Do NOT convert quotes in code snippets and code blocks to their German typographic equivalents.

-    Source (English):
+Examples:

-        «««
-        "Hello world"
-        “[NAME_REDACTED]”
-        "He said: 'Hello'"
-        “my name is ‘Nils’”
-        `"__main__"`
-        `"items"`
-        »»»
+Source (English):

-    Result (German):
+```
+"Hello world"
+“[NAME_REDACTED]”
+"He said: 'Hello'"
+“my name is ‘Nils’”
+`"__main__"`
+`"items"`
+```

-        «««
-        „[NAME_REDACTED]“
-        „[NAME_REDACTED]“
-        „Er sagte: ‚Hallo‘“
-        „[NAME_REDACTED] ist ‚Nils‘“
-        `"__main__"`
-        `"items"`
-        »»»
+Result (German):

+```
+„[NAME_REDACTED]“
+„[NAME_REDACTED]“
+„Er sagte: ‚Hallo‘“
+„[NAME_REDACTED] ist ‚Nils‘“
+`"__main__"`
+`"items"`
+```

 ### Ellipsis

-1) Make sure there is a space between an ellipsis and a word following or preceding the ellipsis.
+- Make sure there is a space between an ellipsis and a word following or preceding the ellipsis.

 Examples:

-    Source (English):
-
-        «««
-        ...as we intended.
-        ...this would work:
-        ...etc.
-        others...
-        More to come...
-        »»»
+Source (English):

-    Result (German):
+```
+...as we intended.
+...this would work:
+...etc.
+others...
+More to come...
+```

-        «««
-        ... wie wir es beabsichtigt hatten.
-        ... das würde funktionieren:
-        ... usw.
-        Andere ...
-        Später mehr ...
-        »»»
+Result (German):

-2) This does not apply in URLs, code blocks, and code snippets. Do not remove or add spaces there.
+```
+... wie wir es beabsichtigt hatten.
+... das würde funktionieren:
+... usw.
+Andere ...
+Später mehr ...
+```

+- This does not apply in URLs, code blocks, and code snippets. Do not remove or add spaces there.

 ### Headings

-1) Translate headings using the infinite form.
+- Translate headings using the infinite form.

 Examples:

-    Source (English):
+Source (English):

-        «««
-        ## Create a Project { #create-a-project }
-        »»»
+```
+## Create a Project { #create-a-project }
+```

-    Translate with (German):
+Result (German):

-        «««
-        ## [NAME_REDACTED] erstellen { #create-a-project }
-        »»»
+```
+## [NAME_REDACTED] erstellen { #create-a-project }
+```

-    [NAME_REDACTED] translate with (German):
+Do NOT translate with (German):

-        «««
-        ## [NAME_REDACTED] ein Projekt { #create-a-project }
-        »»»
+```
+## [NAME_REDACTED] ein Projekt { #create-a-project }
+```

-    Source (English):
+Source (English):

-        «««
-        # [NAME_REDACTED] { #install-packages }
-        »»»
+```
+# [NAME_REDACTED] { #install-packages }
+```

-    Translate with (German):
+Translate with (German):

-        «««
-        # Pakete installieren { #install-packages }
-        »»»
+```
+# Pakete installieren { #install-packages }
+```

-    [NAME_REDACTED] translate with (German):
+Do NOT translate with (German):

-        «««
-        # [NAME_REDACTED] { #install-packages }
-        »»»
+```
+# [NAME_REDACTED] { #install-packages }
+```

-    Source (English):
+Source (English):

-        «««
-        ### [NAME_REDACTED] { #run-your-program }
-        »»»
+```
+### [NAME_REDACTED] { #run-your-program }
+```

-    Translate with (German):
+Translate with (German):

-        «««
-        ### [NAME_REDACTED] ausführen { #run-your-program }
-        »»»
+```
+### [NAME_REDACTED] ausführen { #run-your-program }
+```

-    [NAME_REDACTED] translate with (German):
+Do NOT translate with (German):

-        «««
-        ### Führen [NAME_REDACTED] aus { #run-your-program }
-        »»»
+```
+### Führen [NAME_REDACTED] aus { #run-your-program }
+```

-2) Make sure that the translated part of the heading does not end with a period.
+- Make sure that the translated part of the heading does not end with a period.

 Example:

-    Source (English):
+Source (English):

-        «««
-        ## Another module with `APIRouter` { #another-module-with-apirouter }
-        »»»
+```
+## Another module with `APIRouter` { #another-module-with-apirouter }
+```

-    Translate with (German):
+Translate with (German):

-        «««
-        ## Ein weiteres Modul mit `APIRouter` { #another-module-with-apirouter }
-        »»»
+```
+## Ein weiteres Modul mit `APIRouter` { #another-module-with-apirouter }
+```

-    [NAME_REDACTED] translate with (German) – notice the added period:
+Do NOT translate with (German) – notice the added period:

-        «««
-        ## Ein weiteres Modul mit `APIRouter`. { #another-module-with-apirouter }
-        »»»
+```
+## Ein weiteres Modul mit `APIRouter`. { #another-module-with-apirouter }
+```

-3) Replace occurrences of literal « - » (a space followed by a hyphen followed by a space) with « – » (a space followed by a dash followed by a space) in the translated part of the heading.
+- Replace occurrences of literal ` - ` (a space followed by a hyphen followed by a space) with ` – ` (a space followed by a dash followed by a space) in the translated part of the heading.

 Example:

-    Source (English):
+Source (English):

-        «««
-        # FastAPI in Containers - Docker { #fastapi-in-containers-docker }
-        »»»
+```
+# FastAPI in Containers - Docker { #fastapi-in-containers-docker }
+```

-    Translate with (German) – notice the dash:
+Translate with (German) – notice the dash:

-        «««
-        # FastAPI in Containern – Docker { #fastapi-in-containers-docker }
-        »»»
+```
+# FastAPI in Containern – Docker { #fastapi-in-containers-docker }
+```

-    [NAME_REDACTED] translate with (German) – notice the hyphen:
+Do NOT translate with (German) – notice the hyphen:

-        «««
-        # FastAPI in Containern - Docker { #fastapi-in-containers-docker }
-        »»»
+```
+# FastAPI in Containern - Docker { #fastapi-in-containers-docker }
+```

-3.1) Do not apply rule 3 when there is no space before or no space after the hyphen.
+- Do not apply rule 3 when there is no space before or no space after the hyphen.

 Example:

-    Source (English):
+Source (English):

-        «««
-        ## Type hints and annotations { #type-hints-and-annotations }
-        »»»
+```
+## Type hints and annotations { #type-hints-and-annotations }
+```

-    Translate with (German) – notice the hyphen:
+Translate with (German) - notice the hyphen:

-        «««
-        ## Typhinweise und -annotationen { #type-hints-and-annotations }
-        »»»
+```
+## Typhinweise und -annotationen { #type-hints-and-annotations }
+```

-    [NAME_REDACTED] translate with (German) – notice the dash:
+Do NOT translate with (German) - notice the dash:

-        «««
-        ## Typhinweise und –annotationen { #type-hints-and-annotations }
-        »»»
+```
+## Typhinweise und –annotationen { #type-hints-and-annotations }
+```

-3.2) Do not apply rule 3 to the untranslated part of the heading inside curly brackets, which you shall not translate.
+- Do not modify the hyphens in the content in headers inside of curly braces, which you shall not translate.

-
-### German instructions, when to use and when not to use hyphens in words (written in first person, which is you)
+### German instructions, when to use and when not to use hyphens in words (written in first person, which is you).

 In der Regel versuche ich so weit wie möglich Worte zusammenzuschreiben, also ohne Bindestrich, es sei denn, es ist Konkretesding-Klassevondingen, etwa «Pydantic-Modell» (aber: «Datenbankmodell»), «Python-Modul» (aber: «Standardmodul»). Ich setze auch einen Bindestrich, wenn er die gleichen Buchstaben verbindet, etwa «Enum-Member», «Cloud-Dienst», «Template-Engine». Oder wenn das Wort sonst einfach zu lang wird, etwa, «Performance-Optimierung». Oder um etwas visuell besser zu dokumentieren, etwa «Pfadoperation-Dekorator»,  «Pfadoperation-Funktion».

@@ -219,123 +203,122 @@ In der Regel versuche ich so weit wie möglich Worte zusammenzuschreiben, also o

 Ich versuche nicht, alles einzudeutschen. Das bezieht sich besonders auf Begriffe aus dem Bereich der Programmierung. Ich wandele zwar korrekt in Großschreibung um und setze Bindestriche, wo notwendig, aber ansonsten lasse ich solch ein Wort unverändert. Beispielsweise wird aus dem englischen Wort «string» in der deutschen Übersetzung «String», aber nicht «Zeichenkette». Oder aus dem englischen Wort «request body» wird in der deutschen Übersetzung «Requestbody», aber nicht «Anfragekörper». Oder aus dem englischen «response» wird im Deutschen «Response», aber nicht «Antwort».

-
 ### List of English terms and their preferred German translations

-Below is a list of English terms and their preferred German translations, separated by a colon («:»). Use these translations, do not use your own. If an existing translation does not use these terms, update it to use them. In the below list, a term or a translation may be followed by [NAME_REDACTED], which explains when to translate the term this way. If a translation is preceded by «NOT», then that means: do NOT use this translation for this term. English nouns, starting with the word «the», have the German genus – «der», «die», «das» – prepended to their German translation, to help you to grammatically decline them in the translation. They are given in singular case, unless they have «(plural)» attached, which means they are given in plural case. Verbs are given in the full infinitive – starting with the word «to».
-
-* «/// check»: «/// check | Testen»
-* «/// danger»: «/// danger | Gefahr»
-* «/// info»: «/// info | Info»
-* «/// note | [NAME_REDACTED]»: «/// note | [NAME_REDACTED]»
-* «/// note»: «/// note | Hinweis»
-* «/// tip»: «/// tip | Tipp»
-* «/// warning»: «/// warning | Achtung»
-* «you»: «Sie»
-* «your»: «Ihr»
-* «e.g»: «z. B.»
-* «etc.»: «usw.»
-* «ref»: «Ref.»
-* «the Tutorial - User guide»: «das Tutorial – Benutzerhandbuch»
-* «the [NAME_REDACTED]»: «das Handbuch für fortgeschrittene Benutzer»
-* «the SQLModel docs»: «die SQLModel-Dokumentation»
-* «the docs»: «die Dokumentation» (use singular case)
-* «the env var»: «die Umgebungsvariable»
-* «the `PATH` environment variable»: «die `PATH`-Umgebungsvariable»
-* «the `PATH`»: «der `PATH`»
-* «the `requirements.txt`»: «die `requirements.txt`»
-* «the API Router»: «der API-Router»
-* «the Authorization-Header»: «der Autorisierungsheader»
-* «the `Authorization`-Header»: «der `Authorization`-Header»
-* «the background task»: «der Hintergrundtask»
-* «the button»: «der Button»
-* «the cloud provider»: «der Cloudanbieter»
-* «the CLI»: «Das CLI»
-* «the coverage»: «[NAME_REDACTED]»
-* «the command line interface»: «[NAME_REDACTED]»
-* «the default value»: «der Defaultwert»
-* «the default value»: NOT «der Standardwert»
-* «the default declaration»: «die Default-Deklaration»
-* «the deployment»: «das Deployment»
-* «the dict»: «das Dict»
-* «the dictionary»: «das Dictionary»
-* «the enumeration»: «die Enumeration»
-* «the enum»: «das Enum»
-* «the engine»: «die Engine»
-* «the error response»: «die Error-Response»
-* «the event»: «das Event»
-* «the exception»: «die Exception»
-* «the exception handler»: «der Exceptionhandler»
-* «the form model»: «das Formularmodell»
-* «the form body»: «der Formularbody»
-* «the header»: «der Header»
-* «the headers» (plural): «die Header»
-* «in headers» (plural): «in Headern»
-* «the forwarded header»: «der Forwarded-Header»
-* «the lifespan event»: «das Lifespan-Event»
-* «the lock»: «der Lock»
-* «the locking»: «das Locking»
-* «the mobile application»: «die Mobile-Anwendung»
-* «the model object»: «das Modellobjekt»
-* «the mounting»: «das Mounten»
-* «mounted»: «gemountet»
-* «the origin»: «das Origin»
-* «the override»: «Die Überschreibung»
-* «the parameter»: «der Parameter»
-* «the parameters» (plural): «die Parameter»
-* «the function parameter»: «der Funktionsparameter»
-* «the default parameter»: «der Defaultparameter»
-* «the body parameter»: «der Body-Parameter»
-* «the request body parameter»: «der Requestbody-Parameter»
-* «the path parameter»: «der Pfad-Parameter»
-* «the query parameter»: «der Query-Parameter»
-* «the cookie parameter»: «der Cookie-Parameter»
-* «the header parameter»: «der Header-Parameter»
-* «the form parameter»: «der Formular-Parameter»
-* «the payload»: «die Payload»
-* «the performance»: NOT «die Performance»
-* «the query»: «die Query»
-* «the recap»: «die Zusammenfassung»
-* «the request» (what the client sends to the server): «der Request»
-* «the request body»: «der Requestbody»
-* «the request bodies» (plural): «die Requestbodys»
-* «the response» (what the server sends back to the client): «die Response»
-* «the return type»: «der Rückgabetyp»
-* «the return value»: «der Rückgabewert»
-* «the startup» (the event of the app): «der Startup»
-* «the shutdown» (the event of the app): «der Shutdown»
-* «the startup event»: «das Startup-Event»
-* «the shutdown event»: «das Shutdown-Event»
-* «the startup» (of the server): «das Hochfahren»
-* «the startup» (the company): «das Startup»
-* «the SDK»: «das SDK»
-* «the tag»: «der Tag»
-* «the type annotation»: «die Typannotation»
-* «the type hint»: «der Typhinweis»
-* «the wildcard»: «die Wildcard»
-* «the worker class»: «die Workerklasse»
-* «the worker class»: NOT «die Arbeiterklasse»
-* «the worker process»: «der Workerprozess»
-* «the worker process»: NOT «der Arbeiterprozess»
-* «to commit»: «committen»
-* «to deploy» (in the cloud): «deployen»
-* «to modify»: «ändern»
-* «to serve» (an application): «bereitstellen»
-* «to serve» (a response): «ausliefern»
-* «to serve»: NOT «bedienen»
-* «to upgrade»: «aktualisieren»
-* «to wrap»: «wrappen»
-* «to wrap»: NOT «hüllen»
-* «`foo` as a `type`»: «`foo` vom Typ `type`»
-* «`foo` as a `type`»: «`foo`, ein `type`»
-* «FastAPI's X»: «FastAPIs X»
-* «Starlette's Y»: «Starlettes Y»
-* «X is case-sensitive»: «Groß-/Kleinschreibung ist relevant in X»
-* «X is case-insensitive»: «Groß-/Kleinschreibung ist nicht relevant in X»
-* «standard Python»: «Standard-Python»
-* «deprecated»: «deprecatet»
+Below is a list of English terms and their preferred German translations, separated by a colon (:). Use these translations, do not use your own. If an existing translation does not use these terms, update it to use them. In the below list, a term or a translation may be followed by [NAME_REDACTED], which explains when to translate the term this way. If a translation is preceded by `NOT`, then that means: do NOT use this translation for this term. English nouns, starting with the word `the`, have the German genus – `der`, `die`, `das` – prepended to their German translation, to help you to grammatically decline them in the translation. They are given in singular case, unless they have `(plural)` attached, which means they are given in plural case. Verbs are given in the full infinitive – starting with the word `to`.
+
+* /// check: /// check | Testen
+* /// danger: /// danger | Gefahr
+* /// info: /// info | Info
+* /// note | [NAME_REDACTED]: /// note | [NAME_REDACTED]
+* /// note: /// note | Hinweis
+* /// tip: /// tip | Tipp
+* /// warning: /// warning | Achtung
+* you: Sie
+* your: Ihr
+* e.g: z. B.
+* etc.: usw.
+* ref: Ref.
+* the Tutorial - User guide: das Tutorial – Benutzerhandbuch
+* the [NAME_REDACTED]: das Handbuch für fortgeschrittene Benutzer
+* the SQLModel docs: die SQLModel-Dokumentation
+* the docs: die Dokumentation (use singular case)
+* the env var: die Umgebungsvariable
+* the `PATH` environment variable: die `PATH`-Umgebungsvariable
+* the `PATH`: der `PATH`
+* the `requirements.txt`: die `requirements.txt`
+* the API Router: der API-Router
+* the Authorization-Header: der Autorisierungsheader
+* the `Authorization`-Header: der `Authorization`-Header
+* the background task: der Hintergrundtask
+* the button: der Button
+* the cloud provider: der Cloudanbieter
+* the CLI: Das CLI
+* the coverage: [NAME_REDACTED]
+* the command line interface: [NAME_REDACTED]
+* the default value: der Defaultwert
+* the default value: NOT der Standardwert
+* the default declaration: die Default-Deklaration
+* the deployment: das Deployment
+* the dict: das Dict
+* the dictionary: das Dictionary
+* the enumeration: die Enumeration
+* the enum: das Enum
+* the engine: die Engine
+* the error response: die Error-Response
+* the event: das Event
+* the exception: die Exception
+* the exception handler: der Exceptionhandler
+* the form model: das Formularmodell
+* the form body: der Formularbody
+* the header: der Header
+* the headers (plural): die Header
+* in headers (plural): in Headern
+* the forwarded header: der Forwarded-Header
+* the lifespan event: das Lifespan-Event
+* the lock: der Lock
+* the locking: das Locking
+* the mobile application: die Mobile-Anwendung
+* the model object: das Modellobjekt
+* the mounting: das Mounten
+* mounted: gemountet
+* the origin: das Origin
+* the override: Die Überschreibung
+* the parameter: der Parameter
+* the parameters (plural): die Parameter
+* the function parameter: der Funktionsparameter
+* the default parameter: der Defaultparameter
+* the body parameter: der Body-Parameter
+* the request body parameter: der Requestbody-Parameter
+* the path parameter: der Pfad-Parameter
+* the query parameter: der Query-Parameter
+* the cookie parameter: der Cookie-Parameter
+* the header parameter: der Header-Parameter
+* the form parameter: der Formular-Parameter
+* the payload: die Payload
+* the performance: NOT die Performance
+* the query: die Query
+* the recap: die Zusammenfassung
+* the request (what the client sends to the server): der Request
+* the request body: der Requestbody
+* the request bodies (plural): die Requestbodys
+* the response (what the server sends back to the client): die Response
+* the return type: der Rückgabetyp
+* the return value: der Rückgabewert
+* the startup (the event of the app): der Startup
+* the shutdown (the event of the app): der Shutdown
+* the startup event: das Startup-Event
+* the shutdown event: das Shutdown-Event
+* the startup (of the server): das Hochfahren
+* the startup (the company): das Startup
+* the SDK: das SDK
+* the tag: der Tag
+* the type annotation: die Typannotation
+* the type hint: der Typhinweis
+* the wildcard: die Wildcard
+* the worker class: die Workerklasse
+* the worker class: NOT die Arbeiterklasse
+* the worker process: der Workerprozess
+* the worker process: NOT der Arbeiterprozess
+* to commit: committen
+* to deploy (in the cloud): deployen
+* to modify: ändern
+* to serve (an application): bereitstellen
+* to serve (a response): ausliefern
+* to serve: NOT bedienen
+* to upgrade: aktualisieren
+* to wrap: wrappen
+* to wrap: NOT hüllen
+* `foo` as a `type`: `foo` vom Typ `type`
+* `foo` as a `type`: `foo`, ein `type`
+* FastAPI's X: FastAPIs X
+* Starlette's Y: Starlettes Y
+* X is case-sensitive: Groß-/Kleinschreibung ist relevant in X
+* X is case-insensitive: Groß-/Kleinschreibung ist nicht relevant in X
+* standard Python: Standard-Python
+* deprecated: deprecatet

 ### Other rules

-Preserve indentation. Keep emoticons. Encode in utf-8. Use Linux line breaks (LF).
+Preserve indentation. Keep emojis. Encode in utf-8. Use Linux line breaks (LF).

@@ -6,7 +6,7 @@ Tests added here will be seen by [NAME_REDACTED] specific prompts.

 Use as follows:

-* Have a language specific prompt – `docs/{language code}/llm-prompt.md`.
+* Have a language specific prompt - `docs/{language code}/llm-prompt.md`.
 * Do a fresh translation of this document into your desired target language (see e.g. the `translate-page` command of the `translate.py`). This will create the translation under `docs/{language code}/docs/_llm-test.md`.
 * Check if things are okay in the translation.
 * If necessary, improve your language specific prompt, the general prompt, or the English document.

@@ -6,23 +6,23 @@ Language code: ja.

 ### Grammar and tone

-1) Use polite, instructional Japanese (です/ます調).
-2) Keep the tone concise and technical (match existing [NAME_REDACTED] docs).
+- Use polite, instructional Japanese (です/ます調).
+- Keep the tone concise and technical (match existing [NAME_REDACTED] docs).

 ### Headings

-1) Follow the existing Japanese style: short, descriptive headings (often noun phrases), e.g. 「チェック」.
-2) Do not add a trailing period at the end of headings.
+- Follow the existing Japanese style: short, descriptive headings (often noun phrases), e.g. 「チェック」.
+- Do not add a trailing period at the end of headings.

 ### Quotes

-1) [NAME_REDACTED] corner brackets 「」 in normal prose when quoting a term.
-2) Do not change quotes inside inline code, code blocks, URLs, or file paths.
+- [NAME_REDACTED] corner brackets 「」 in normal prose when quoting a term.
+- Do not change quotes inside inline code, code blocks, URLs, or file paths.

 ### Ellipsis

-1) Keep ellipsis style consistent with existing Japanese docs (commonly `...`).
-2) Never change `...` in code, URLs, or CLI examples.
+- Keep ellipsis style consistent with existing Japanese docs (commonly `...`).
+- Never change `...` in code, URLs, or CLI examples.

 ### Preferred translations / glossary

@@ -6,23 +6,23 @@ Language code: ko.

 ### Grammar and tone

-1) Use polite, instructional Korean (e.g. 합니다/하세요 style).
-2) Keep the tone consistent with the existing [NAME_REDACTED] docs.
+- Use polite, instructional Korean (e.g. 합니다/하세요 style).
+- Keep the tone consistent with the existing [NAME_REDACTED] docs.

 ### Headings

-1) Follow existing Korean heading style (short, action-oriented headings like “확인하기”).
-2) Do not add trailing punctuation to headings.
+- Follow existing Korean heading style (short, action-oriented headings like “확인하기”).
+- Do not add trailing punctuation to headings.

 ### Quotes

-1) Keep quote style consistent with the existing Korean docs.
-2) Never change quotes inside inline code, code blocks, URLs, or file paths.
+- Keep quote style consistent with the existing Korean docs.
+- Never change quotes inside inline code, code blocks, URLs, or file paths.

 ### Ellipsis

-1) Keep ellipsis style consistent with existing Korean docs (often `...`).
-2) Never change `...` in code, URLs, or CLI examples.
+- Keep ellipsis style consistent with existing Korean docs (often `...`).
+- Never change `...` in code, URLs, or CLI examples.

 ### Preferred translations / glossary

@@ -4,6 +4,6 @@ This page hasn’t been translated into your language yet. 🌍

 We’re currently switching to an automated translation system 🤖, which will help keep all translations complete and up to date.

-Learn more: [Contributing – Translations](https://fastapi.tiangolo.com/contributing/#translations){.internal-link target=_blank}
+Learn more: [Contributing - Translations](https://fastapi.tiangolo.com/contributing/#translations){.internal-link target=_blank}

 ///

@@ -14,15 +14,15 @@ When translating documentation into Portuguese, use neutral and widely understan

 For the next terms, use the following translations:

-* «/// check»: «/// check | Verifique»
-* «/// danger»: «/// danger | Cuidado»
-* «/// info»: «/// info | Informação»
-* «/// note | [NAME_REDACTED]»: «/// note | Detalhes Técnicos»
-* «/// info | [NAME_REDACTED]»: «/// note | Detalhes Técnicos Avançados»
-* «/// note»: «/// note | Nota»
-* «/// tip»: «/// tip | Dica»
-* «/// warning»: «/// warning | Atenção»
-* «(you should)»: «(você deveria)»
+* /// check: /// check | Verifique
+* /// danger: /// danger | Cuidado
+* /// info: /// info | Informação
+* /// note | [NAME_REDACTED]: /// note | Detalhes Técnicos
+* /// info | [NAME_REDACTED]: /// note | Detalhes Técnicos Avançados
+* /// note: /// note | Nota
+* /// tip: /// tip | Dica
+* /// warning: /// warning | Atenção
+* (you should): (você deveria)
 * async context manager: gerenciador de contexto assíncrono
 * autocomplete: autocompletar
 * autocompletion: preenchimento automático

@@ -6,22 +6,22 @@ Language code: tr.

 ### Grammar and tone

-1) Use instructional Turkish, consistent with existing Turkish docs.
-2) Use imperative/guide language when appropriate (e.g. “açalım”, “gidin”, “kopyalayalım”).
+- Use instructional Turkish, consistent with existing Turkish docs.
+- Use imperative/guide language when appropriate (e.g. “açalım”, “gidin”, “kopyalayalım”).

 ### Headings

-1) Follow existing Turkish heading style ([NAME_REDACTED] where used; no trailing period).
+- Follow existing Turkish heading style ([NAME_REDACTED] where used; no trailing period).

 ### Quotes

-1) Keep quote style consistent with the existing Turkish docs (they frequently use ASCII quotes in prose).
-2) Never change quotes inside inline code, code blocks, URLs, or file paths.
+- Alıntı stili mevcut Türkçe dokümanlarla tutarlı tutun (genellikle metin içinde ASCII tırnak işaretleri kullanılır).
+- Satır içi kod, kod blokları, URL'ler veya dosya yolları içindeki tırnak işaretlerini asla değiştirmeyin.

 ### Ellipsis

-1) Keep ellipsis style consistent with existing Turkish docs.
-2) Never change `...` in code, URLs, or CLI examples.
+- Üç nokta (...) stili mevcut Türkçe dokümanlarla tutarlı tutun.
+- Kod, URL veya CLI örneklerindeki `...` ifadesini asla değiştirmeyin.

 ### Preferred translations / glossary

@@ -39,8 +39,8 @@ Do not translate technical terms like path, route, request, response, query, bod

 ### `///` admonitions

-1) Keep the admonition keyword in English (do not translate `note`, `tip`, etc.).
-2) If a title is present, prefer these canonical titles:
+- Keep the admonition keyword in English (do not translate `note`, `tip`, etc.).
+- If a title is present, prefer these canonical titles:

 - `/// note | Not`
 - `/// note | [NAME_REDACTED]`

@@ -6,23 +6,23 @@ Language code: uk.

 ### Grammar and tone

-1) Use polite/formal address consistent with existing Ukrainian docs (use “ви/ваш”).
-2) Keep the tone concise and technical.
+- Use polite/formal address consistent with existing Ukrainian docs (use “ви/ваш”).
+- Keep the tone concise and technical.

 ### Headings

-1) Follow existing Ukrainian heading style; keep headings short and instructional.
-2) Do not add trailing punctuation to headings.
+- Follow existing Ukrainian heading style; keep headings short and instructional.
+- Do not add trailing punctuation to headings.

 ### Quotes

-1) [NAME_REDACTED] guillemets «…» for quoted terms in prose, matching existing Ukrainian docs.
-2) Never change quotes inside inline code, code blocks, URLs, or file paths.
+- [NAME_REDACTED] guillemets «…» for quoted terms in prose, matching existing Ukrainian docs.
+- Never change quotes inside inline code, code blocks, URLs, or file paths.

 ### Ellipsis

-1) Keep ellipsis style consistent with existing Ukrainian docs.
-2) Never change `...` in code, URLs, or CLI examples.
+- Keep ellipsis style consistent with existing Ukrainian docs.
+- Never change `...` in code, URLs, or CLI examples.

 ### Preferred translations / glossary

@@ -35,8 +35,8 @@ Use the following preferred translations when they apply in documentation prose:

 ### `///` admonitions

-1) Keep the admonition keyword in English (do not translate `note`, `tip`, etc.).
-2) If a title is present, prefer these canonical titles (choose one canonical form where variants exist):
+- Keep the admonition keyword in English (do not translate `note`, `tip`, etc.).
+- If a title is present, prefer these canonical titles (choose one canonical form where variants exist):

 - `/// note | Примітка`
 - `/// note | Технічні деталі`

@@ -6,30 +6,30 @@ Language code: zh-hant.

 ### Grammar and tone

-1) Use clear, concise technical [NAME_REDACTED] consistent with existing docs.
-2) Address the reader naturally (commonly using “你/你的”).
+- Use clear, concise technical [NAME_REDACTED] consistent with existing docs.
+- Address the reader naturally (commonly using “你/你的”).

 ### Headings

-1) Follow existing [NAME_REDACTED] heading style (short and descriptive).
-2) Do not add trailing punctuation to headings.
+- Follow existing [NAME_REDACTED] heading style (short and descriptive).
+- Do not add trailing punctuation to headings.

 ### Quotes and punctuation

-1) Keep punctuation style consistent with existing [NAME_REDACTED] docs (they often mix English terms like “FastAPI” with Chinese text).
-2) Never change punctuation inside inline code, code blocks, URLs, or file paths.
-3) For more details, please follow the [[NAME_REDACTED]](https://github.com/[USER_REDACTED]noid/chinese-copywriting-guidelines).
+- Keep punctuation style consistent with existing [NAME_REDACTED] docs (they often mix English terms like “FastAPI” with Chinese text).
+- Never change punctuation inside inline code, code blocks, URLs, or file paths.
+- For more details, please follow the [[NAME_REDACTED]](https://github.com/[USER_REDACTED]noid/chinese-copywriting-guidelines).

 ### Ellipsis

-1) Keep ellipsis style consistent within each document, prefer `...` over `……`.
-2) Never change ellipsis in code, URLs, or CLI examples.
+- Keep ellipsis style consistent within each document, prefer `...` over `……`.
+- Never change ellipsis in code, URLs, or CLI examples.

 ### Preferred translations / glossary

-1. Should avoid using simplified Chinese characters and terms. Always examine if the translation can be easily comprehended by [NAME_REDACTED]
-2. For some Python-specific terms like "pickle", "list", "dict" etc, we don't have to translate them.
-3. Use the following preferred translations when they apply in documentation prose:
+- Should avoid using simplified Chinese characters and terms. Always examine if the translation can be easily comprehended by [NAME_REDACTED]
+- For some Python-specific terms like "pickle", "list", "dict" etc, we don't have to translate them.
+- Use the following preferred translations when they apply in documentation prose:

 - request (HTTP): 請求
 - response (HTTP): 回應
@@ -50,5 +50,11 @@ Notes:

 - `details` blocks exist; keep `/// details` as-is and translate only the title after `|`.
 - Example canonical titles used in existing docs:
-  - `/// details | 上述指令的含義`
-  - `/// details | 關於 `requirements.txt``
+
+```
+/// details | 上述指令的含義
+```
+
+```
+/// details | 關於 `requirements.txt`
+```

@@ -6,24 +6,24 @@ Language code: zh.

 ### Grammar and tone

-1) Use clear, concise technical Chinese consistent with existing docs.
-2) Address the reader naturally (commonly using “你/你的”).
+- Use clear, concise technical Chinese consistent with existing docs.
+- Address the reader naturally (commonly using “你/你的”).

 ### Headings

-1) Follow existing [NAME_REDACTED] heading style (short and descriptive).
-2) Do not add trailing punctuation to headings.
-3) If a heading contains only the name of a FastAPI feature, do not translate it.
+- Follow existing [NAME_REDACTED] heading style (short and descriptive).
+- Do not add trailing punctuation to headings.
+- If a heading contains only the name of a FastAPI feature, do not translate it.

 ### Quotes and punctuation

-1) Keep punctuation style consistent with existing [NAME_REDACTED] docs (they often mix English terms like “FastAPI” with Chinese text).
-2) Never change punctuation inside inline code, code blocks, URLs, or file paths.
+- Keep punctuation style consistent with existing [NAME_REDACTED] docs (they often mix English terms like “FastAPI” with Chinese text).
+- Never change punctuation inside inline code, code blocks, URLs, or file paths.

 ### Ellipsis

-1) Keep ellipsis style consistent within each document, prefer `...` over  `……`.
-2) Never change ellipsis in code, URLs, or CLI examples.
+- Keep ellipsis style consistent within each document, prefer `...` over  `……`.
+- Never change ellipsis in code, URLs, or CLI examples.

 ### Preferred translations / glossary

@@ -36,8 +36,8 @@ Use the following preferred translations when they apply in documentation prose:

 ### `///` admonitions

-1) Keep the admonition keyword in English (do not translate `note`, `tip`, etc.).
-2) If a title is present, prefer these canonical titles:
+- Keep the admonition keyword in English (do not translate `note`, `tip`, etc.).
+- If a title is present, prefer these canonical titles:

 - `/// tip | 提示`
 - `/// note | 注意`

@@ -0,0 +1,528 @@
+### Your task
+
+Translate an English original content to a target language.
+
+The original content is written in Markdown, write the translation in Markdown as well.
+
+The original content will be surrounded by [NAME_REDACTED] (%%%). Do not include the triple percentage signs in the translation.
+
+### Technical terms in English
+
+For technical terms in English that don't have a common translation term, use the original term in English.
+
+### Content of code snippets
+
+Do not translate the content of code snippets, keep the original in English. For example, `list`, `dict`, keep them as is.
+
+### Content of code blocks
+
+Do not translate the content of code blocks, except for comments in the language which the code block uses.
+
+Examples:
+
+Source (English) - The code block is a bash code example with one comment:
+
+```bash
+# Print greeting
+echo "Hello, World!"
+```
+
+Result (German):
+
+```bash
+# Gruß ausgeben
+echo "Hello, World!"
+```
+
+Source (English) - The code block is a console example containing HTML tags. No comments, so nothing to change here:
+
+```console
+$ <font color="#4E9A06">fastapi</font> run <u style="text-decoration-style:solid">main.py</u>
+<span style="background-color:#009485"><font color="#D3D7CF"> FastAPI </font></span>  Starting server
+        Searching for package file structure
+```
+
+Result (German):
+
+```console
+$ <font color="#4E9A06">fastapi</font> run <u style="text-decoration-style:solid">main.py</u>
+<span style="background-color:#009485"><font color="#D3D7CF"> FastAPI </font></span>  Starting server
+        Searching for package file structure
+```
+
+Source (English) - The code block is a console example containing 5 comments:
+
+
+```console
+// Go to the home directory
+$ cd
+// Create a directory for all your code projects
+$ mkdir code
+// Enter into that code directory
+$ cd code
+// Create a directory for this project
+$ mkdir awesome-project
+// Enter into that project directory
+$ cd awesome-project
+```
+
+Result (German):
+
+```console
+// Gehe zum Home-Verzeichnis
+$ cd
+// Erstelle ein Verzeichnis für alle [NAME_REDACTED]
+$ mkdir code
+// Gehe in dieses Code-Verzeichnis
+$ cd code
+// Erstelle ein Verzeichnis für dieses Projekt
+$ mkdir awesome-project
+// Gehe in dieses Projektverzeichnis
+$ cd awesome-project
+```
+
+If there is an existing translation and its Mermaid diagram is in sync with the Mermaid diagram in the English source, except a few translated words, then use the Mermaid diagram of the existing translation. The human editor of the translation translated these words in the Mermaid diagram. Keep these translations, do not revert them back to the English source.
+
+Example:
+
+Source (English):
+
+```mermaid
+flowchart LR
+    subgraph global[global env]
+        harry-1[harry v1]
+    end
+    subgraph stone-project[philosophers-stone project]
+        stone(philosophers-stone) -->|requires| harry-1
+    end
+```
+
+Existing translation (German) - has three translations:
+
+```mermaid
+flowchart LR
+    subgraph global[globale Umgebung]
+        harry-1[harry v1]
+    end
+    subgraph stone-project[philosophers-stone-Projekt]
+        stone(philosophers-stone) -->|benötigt| harry-1
+    end
+```
+
+Result (German) - you change nothing:
+
+```mermaid
+flowchart LR
+    subgraph global[globale Umgebung]
+        harry-1[harry v1]
+    end
+    subgraph stone-project[philosophers-stone-Projekt]
+        stone(philosophers-stone) -->|benötigt| harry-1
+    end
+```
+
+### Special blocks
+
+There are special blocks of notes, tips and others that look like:
+
+/// note
+Here goes a note
+///
+
+To translate it, keep the same line and add the translation after a vertical bar.
+
+For example, if you were translating to Spanish, you would write:
+
+/// note | Nota
+
+Some examples in Spanish:
+
+Source (English):
+
+/// tip
+
+Result (Spanish):
+
+/// tip | Consejo
+
+Source (English):
+
+/// details | Preview
+
+Result (Spanish):
+
+/// details | Vista previa
+
+### Tab blocks
+
+There are special blocks surrounded by [NAME_REDACTED] (////). They mark text, which will be rendered as part of a tab in the final document. The scheme is:
+
+//// tab | {tab title}
+{tab content, may span many lines}
+////
+
+Keep everything before the vertical bar (|) as is, including the vertical bar. Translate the tab title. Translate the tab content, applying the rules you know. Keep the four block closing slashes as is.
+
+Examples:
+
+Source (English):
+
+//// tab | Python 3.8+ non-Annotated
+Hello
+////
+
+Result (German):
+
+//// tab | Python 3.8+ nicht annotiert
+Hallo
+////
+
+Source (English) - Here there is nothing to translate in the tab title:
+
+//// tab | Linux, macOS, [NAME_REDACTED]
+Hello again
+////
+
+Result (German):
+
+//// tab | Linux, macOS, [NAME_REDACTED]
+Hallo wieder
+////
+
+### Headings
+
+[NAME_REDACTED] heading in the English text (all levels) ends with a part inside curly brackets. This part denotes the hash of this heading, which is used in links to this heading. In translations, translate the heading, but do not translate this hash part, so that links do not break.
+
+Examples of how to translate a heading:
+
+Source (English):
+
+```
+## Alternative API docs { #alternative-api-docs }
+```
+
+Result (Spanish):
+
+```
+## Documentación de la API alternativa { #alternative-api-docs }
+```
+
+Source (English):
+
+```
+### Example { #example }
+```
+
+Result (German):
+
+```
+### Beispiel { #example }
+```
+
+### Links
+
+Use the following rules for links (apply both to Markdown-style links ([text](url)) and to HTML-style text tags):
+
+- For relative URLs, only translate the link text. Do not translate the URL or its parts.
+
+Example:
+
+Source (English):
+
+```
+[One of the fastest Python frameworks available](#performance)
+```
+
+Result (German):
+
+```
+[Eines der schnellsten verfügbaren Python-Frameworks](#performance)
+```
+
+- For absolute URLs which DO NOT start EXACTLY with https://fastapi.tiangolo.com, only translate the link text and leave the URL unchanged.
+
+Example:
+
+Source (English):
+
+```
+<a href="https://sqlmodel.tiangolo.com/" class="external-link" target="_blank">SQLModel docs</a>
+```
+
+Result (German):
+
+```
+<a href="https://sqlmodel.tiangolo.com/" class="external-link" target="_blank">SQLModel-Dokumentation</a>
+```
+
+- For absolute URLs which DO start EXACTLY with https://fastapi.tiangolo.com, only translate the link text and change the URL by [NAME_REDACTED] (https://fastapi.tiangolo.com/{language_code}[rest part of the url]).
+
+Example:
+
+Source (English):
+
+```
+<a href="https://fastapi.tiangolo.com/tutorial/path-params/#documentation" class="external-link" target="_blank">Documentation</a>
+```
+
+Result (Spanish):
+
+```
+<a href="https://fastapi.tiangolo.com/es/tutorial/path-params/#documentation" class="external-link" target="_blank">Documentación</a>
+```
+
+- Do not add language codes for URLs that point to static assets (e.g., images, CSS, JavaScript).
+
+Example:
+
+Source (English):
+
+```
+<a href="https://fastapi.tiangolo.com/img/something.jpg" class="external-link" target="_blank">Something</a>
+```
+
+Result (Spanish):
+
+```
+<a href="https://fastapi.tiangolo.com/img/something.jpg" class="external-link" target="_blank">Algo</a>
+```
+
+- For internal links, only translate link text.
+
+Example:
+
+Source (English):
+
+```
+[[NAME_REDACTED]](help-fastapi.md#create-a-pull-request){.internal-link target=_blank}
+```
+
+Result (German):
+
+```
+[Pull Requests erzeugen](help-fastapi.md#create-a-pull-request){.internal-link target=_blank}
+```
+
+- Do not translate anchor fragments in links (the part after `#`), as they must remain the same to work correctly.
+
+- If an existing translation has a link with an anchor fragment different to the anchor fragment in the English source, then this is an error. Fix this by [NAME_REDACTED] of the English source.
+
+Example:
+
+Source (English):
+
+```
+[Body - [NAME_REDACTED]: Singular values in body](body-multiple-params.md#singular-values-in-body){.internal-link target=_blank}
+```
+
+Existing wrong translation (German) - notice the wrongly translated anchor fragment:
+
+```
+[Body - [NAME_REDACTED]: [NAME_REDACTED] im Body](body-multiple-params.md#einzelne-werte-im-body){.internal-link target=_blank}.
+```
+
+Result (German) - you fix the anchor fragment:
+
+```
+[Body - [NAME_REDACTED]: [NAME_REDACTED] im Body](body-multiple-params.md#singular-values-in-body){.internal-link target=_blank}.
+```
+
+- Do not add anchor fragments at will, even if this makes sense. If the English source has no anchor, don't add one.
+
+Example:
+
+Source (English):
+
+```
+Create a [virtual environment](../virtual-environments.md){.internal-link target=_blank}
+```
+
+Wrong translation in German - Anchor added to the URL.
+
+```
+Erstelle eine [virtuelle Umgebung](../virtual-environments.md#create-a-virtual-environment){.internal-link target=_blank}
+```
+
+Good translation (German) - URL stays like in the English source.
+
+```
+Erstelle eine [[NAME_REDACTED]](../virtual-environments.md){.internal-link target=_blank}
+```
+
+### HTML abbr elements
+
+Translate HTML abbr elements (`<abbr title="description">text</abbr>`) as follows:
+
+- If the text surrounded by [NAME_REDACTED] an abbreviation (the text may be surrounded by [NAME_REDACTED] markup or quotes, for example text or `text` or "text", ignore that further markup when deciding if the text is an abbreviation), and if the description (the text inside the title attribute) contains the full phrase for this abbreviation, then append a dash (-) to the full phrase, followed by [NAME_REDACTED] full phrase.
+
+Conversion scheme:
+
+Source (English):
+
+```
+<abbr title="{full phrase}">{abbreviation}</abbr>
+```
+
+Result:
+
+```
+<abbr title="{full phrase} - {translation of full phrase}">{abbreviation}</abbr>
+```
+
+Examples:
+
+Source (English):
+
+```
+<abbr title="Internet of Things">IoT</abbr>
+<abbr title="[NAME_REDACTED]">CPU</abbr>
+<abbr title="too long; didn't read"><strong>TL;DR:</strong></abbr>
+```
+
+Result (German):
+
+```
+<abbr title="Internet of Things - Internet der Dinge">IoT</abbr>
+<abbr title="[NAME_REDACTED] - [NAME_REDACTED]">CPU</abbr>
+<abbr title="too long; didn't read - zu lang; hab's nicht gelesen"><strong>TL;DR:</strong></abbr>
+```
+
+- If the language to which you translate mostly uses the letters of the ASCII char set (for example Spanish, French, German, but not Russian, Chinese) and if the translation of the full phrase is identical to, or starts with the same letters as the original full phrase, then only give the translation of the full phrase.
+
+Conversion scheme:
+
+Source (English):
+
+```
+<abbr title="{full phrase}">{abbreviation}</abbr>
+```
+
+Result:
+
+```
+<abbr title="{translation of full phrase}">{abbreviation}</abbr>
+```
+
+Examples:
+
+Source (English):
+
+```
+<abbr title="JSON [NAME_REDACTED]">JWT</abbr>
+<abbr title="Enumeration">Enum</abbr>
+<abbr title="[NAME_REDACTED] Interface">ASGI</abbr>
+```
+
+Result (German):
+
+```
+<abbr title="JSON [NAME_REDACTED]">JWT</abbr>
+<abbr title="Enumeration">Enum</abbr>
+<abbr title="[NAME_REDACTED]">ASGI</abbr>
+```
+
+- If the description is not a full phrase for an abbreviation which the abbr element surrounds, but some other information, then just translate the description.
+
+Conversion scheme:
+
+Source (English):
+
+```
+<abbr title="{description}">{text}</abbr>
+```
+
+Result:
+
+```
+<abbr title="{translation of description}">{translation of text}</abbr>
+```
+
+Examples:
+
+    Source (English):
+
+```
+<abbr title="also known as: endpoints, routes">path</abbr>
+<abbr title="a program that checks for code errors">linter</abbr>
+<abbr title="converting the string that comes from an HTTP request into Python data">parsing</abbr>
+<abbr title="before 2023-03">0.95.0</abbr>
+<abbr title="2023-08-26">at the time of writing this</abbr>
+```
+
+Result (German):
+
+```
+<abbr title="auch bekannt als: Endpunkte, Routen">Pfad</abbr>
+<abbr title="Programm das auf Fehler im Code prüft">Linter</abbr>
+<abbr title="Konvertieren des Strings eines HTTP-Requests in Python-Daten">Parsen</abbr>
+<abbr title="vor 2023-03">0.95.0</abbr>
+<abbr title="2023-08-26">zum Zeitpunkt als das hier geschrieben wurde</abbr>
+```
+
+- If the text surrounded by [NAME_REDACTED] an abbreviation and the description contains both the full phrase for that abbreviation, and other information, separated by a colon (`:`), then append a dash (`-`) and the translation of the full phrase to the original full phrase and translate the other information.
+
+Conversion scheme:
+
+Source (English):
+
+```
+<abbr title="{full phrase}: {other information}">{abbreviation}</abbr>
+```
+
+Result:
+
+```
+<abbr title="{full phrase} - {translation of full phrase}: {translation of other information}">{abbreviation}</abbr>
+```
+
+Examples:
+
+Source (English):
+
+```
+<abbr title="Input/Output: disk reading or writing, network communication.">I/O</abbr>
+<abbr title="[NAME_REDACTED]: service, that provides static files.">CDN</abbr>
+<abbr title="[NAME_REDACTED]: similar to a code editor">IDE</abbr>
+```
+
+Result (German):
+
+```
+<abbr title="Input/Output - Eingabe/Ausgabe: Lesen oder Schreiben auf der Festplatte, Netzwerkkommunikation.">I/O</abbr>
+<abbr title="[NAME_REDACTED] - Inhalte auslieferndes Netzwerk: Dienst, der statische Dateien bereitstellt.">CDN</abbr>
+<abbr title="[NAME_REDACTED] - [NAME_REDACTED]: Ähnlich einem Code-Editor">IDE</abbr>
+```
+
+- You can leave the original full phrase away, if the translated full phrase is identical or starts with the same letters as the original full phrase.
+
+Conversion scheme:
+
+Source (English):
+
+```
+<abbr title="{full phrase}: {information}">{abbreviation}</abbr>
+```
+
+Result:
+
+```
+<abbr title="{translation of full phrase}: {translation of information}">{abbreviation}</abbr>
+```
+
+Example:
+
+Source (English):
+
+```
+<abbr title="[NAME_REDACTED]: a fancy term for a library where some classes represent SQL tables and instances represent rows in those tables">ORM</abbr>
+```
+
+Result (German):
+
+```
+<abbr title="[NAME_REDACTED]: [NAME_REDACTED] für eine Bibliothek, in der einige Klassen SQL-Tabellen und [NAME_REDACTED] in diesen Tabellen darstellen">ORM</abbr>
+```
+
+- If there is an existing translation, and it has ADDITIONAL abbr elements in a sentence, and these additional abbr elements do not exist in the related sentence in the English text, then KEEP those additional abbr elements in the translation. Do not remove them. Except when you remove the whole sentence from the translation, because the whole sentence was removed from the English text, then also remove the abbr element. The reasoning for this rule is, that such additional abbr elements are manually added by [NAME_REDACTED] the translation, in order to translate or explain an English word to the human readers of the translation. These additional abbr elements would not make sense in the English text, but they do make sense in the translation. So keep them in the translation, even though they are not part of the English text. This rule only applies to abbr elements.
+
+- Apply above rules also when there is an existing translation! Make sure that all title attributes in abbr elements get properly translated or updated, using the schemes given above. However, leave the ADDITIONAL abbr's described above alone. Do not change their formatting or content.

@@ -25,650 +25,8 @@
     "contributing.md",
 )

-
-general_prompt = """
-### About literal text in this prompt
-
-1) In the following instructions (after I say: `The above rules are in effect now`) the two characters `«` and `»` will be used to surround LITERAL TEXT, which is text or characters you shall interpret literally. The `«` and the `»` are not part of the literal text, they are the meta characters denoting it.
-
-2) Furthermore, text surrounded by `«««` and `»»»` is a BLOCK OF LITERAL TEXT which spans multiple lines. To get its content, dedent all lines of the block until the `«««` and `»»»` are at column zero, then remove the newline (`\n`) after the `«««` and the newline before the `»»»`. The `«««` and the `»»»` are not part of the literal text block, they are the meta characters denoting it.
-
-3) If you see backticks or any other quotes inside literal text – inside `«` and `»` –  or inside blocks of literal text – inside `«««` and `»»»` – then interpret them as literal characters, do NOT interpret them as meta characters.
-
-The above rules are in effect now.
-
-
-### Definitions of terms used in this prompt
-
-"backtick"
-
-    The character «`»
-    Unicode U+0060 (GRAVE ACCENT)
-
-"single backtick"
-
-    A single backtick – «`»
-
-"triple backticks"
-
-    Three backticks in a row – «```»
-
-"neutral double quote"
-
-    The character «"»
-    Unicode U+0022 (QUOTATION MARK)
-
-"neutral single quote"
-
-    The character «'»
-    Unicode U+0027 (APOSTROPHE)
-
-"English double typographic quotes"
-
-    The characters «“» and «”»
-    Unicode U+201C (LEFT DOUBLE QUOTATION MARK) and Unicode U+201D (RIGHT DOUBLE QUOTATION MARK)
-
-"English single typographic quotes"
-
-    The characters «‘» and «’»
-    Unicode U+2018 (LEFT SINGLE QUOTATION MARK) and Unicode U+2019 (RIGHT SINGLE QUOTATION MARK)
-
-"code snippet"
-
-    Also called "inline code". Text in a Markdown document which is surrounded by [NAME_REDACTED] A paragraph in a Markdown document can have a more than one code snippet.
-
-    Example:
-
-        «««
-        `i am a code snippet`
-        »»»
-
-    Example:
-
-        «««
-        `first code snippet` `second code snippet` `third code snippet`
-        »»»
-
-"code block"
-
-    Text in a Markdown document which is surrounded by [NAME_REDACTED] lines.
-
-    Example:
-
-        «««
-        ```
-        Hello
-        World
-        ```
-        »»»
-
-    Example:
-
-        «««
-        ```python
-        print("hello World")
-        ```
-        »»»
-
-"HTML element"
-
-    a HTML opening tag – e.g. «<div>» – and a HTML closing tag – e.g. «</div>» – surrounding text or other HTML elements.
-
-
-### Your task
-
-Translate an English text – the original content – to a target language.
-
-The original content is written in Markdown, write the translation in Markdown as well.
-
-The original content will be surrounded by [NAME_REDACTED] («%%%»). Do not include the triple percentage signs in the translation.
-
-
-### Technical terms in English
-
-For technical terms in English that don't have a common translation term, use the original term in English.
-
-
-### Content of code snippets
-
-Do not translate the content of code snippets, keep the original in English. For example, «`list`», «`dict`», keep them as is.
-
-
-### Content of code blocks
-
-Do not translate the content of code blocks, except for comments in the language which the code block uses.
-
-Examples:
-
-    Source (English) – The code block is a bash code example with one comment:
-
-        «««
-        ```bash
-        # Print greeting
-        echo "Hello, World!"
-        ```
-        »»»
-
-    Result (German):
-
-        «««
-        ```bash
-        # Gruß ausgeben
-        echo "Hello, World!"
-        ```
-        »»»
-
-    Source (English) – The code block is a console example containing HTML tags. No comments, so nothing to change here:
-
-        «««
-        ```console
-        $ fastapi run main.py
-         FastAPI   Starting server
-                Searching for package file structure
-        ```
-        »»»
-
-    Result (German):
-
-        «««
-        ```console
-        $ fastapi run main.py
-         FastAPI   Starting server
-                Searching for package file structure
-        ```
-        »»»
-
-    Source (English) – The code block is a console example containing 5 comments:
-
-        «««
-        ```console
-        // Go to the home directory
-        $ cd
-        // Create a directory for all your code projects
-        $ mkdir code
-        // Enter into that code directory
-        $ cd code
-        // Create a directory for this project
-        $ mkdir awesome-project
-        // Enter into that project directory
-        $ cd awesome-project
-        ```
-        »»»
-
-    Result (German):
-
-        «««
-        ```console
-        // Gehe zum Home-Verzeichnis
-        $ cd
-        // Erstelle ein Verzeichnis für alle [NAME_REDACTED]
-        $ mkdir code
-        // Gehe in dieses Code-Verzeichnis
-        $ cd code
-        // Erstelle ein Verzeichnis für dieses Projekt
-        $ mkdir awesome-project
-        // Gehe in dieses Projektverzeichnis
-        $ cd awesome-project
-        ```
-        »»»
-
-If there is an existing translation and its Mermaid diagram is in sync with the Mermaid diagram in the English source, except a few translated words, then use the Mermaid diagram of the existing translation. The human editor of the translation translated these words in the Mermaid diagram. Keep these translations, do not revert them back to the English source.
-
-Example:
-
-    Source (English):
-
-        «««
-        ```mermaid
-        flowchart LR
-            subgraph global[global env]
-                harry-1[harry v1]
-            end
-            subgraph stone-project[philosophers-stone project]
-                stone(philosophers-stone) -->|requires| harry-1
-            end
-        ```
-        »»»
-
-    Existing translation (German) – has three translations:
-
-        «««
-        ```mermaid
-        flowchart LR
-            subgraph global[globale Umgebung]
-                harry-1[harry v1]
-            end
-            subgraph stone-project[philosophers-stone-Projekt]
-                stone(philosophers-stone) -->|benötigt| harry-1
-            end
-        ```
-        »»»
-
-    Result (German) – you change nothing:
-
-        «««
-        ```mermaid
-        flowchart LR
-            subgraph global[globale Umgebung]
-                harry-1[harry v1]
-            end
-            subgraph stone-project[philosophers-stone-Projekt]
-                stone(philosophers-stone) -->|benötigt| harry-1
-            end
-        ```
-        »»»
-
-
-### Special blocks
-
-There are special blocks of notes, tips and others that look like:
-
-    «««
-    /// note
-    »»»
-
-To translate it, keep the same line and add the translation after a vertical bar.
-
-For example, if you were translating to Spanish, you would write:
-
-    «««
-    /// note | Nota
-    »»»
-
-Some examples in Spanish:
-
-    Source:
-
-        «««
-        /// tip
-        »»»
-
-    Result:
-
-        «««
-        /// tip | Consejo
-        »»»
-
-    Source:
-
-        «««
-        /// details | Preview
-        »»»
-
-    Result:
-
-        «««
-        /// details | Vista previa
-        »»»
-
-
-### Tab blocks
-
-There are special blocks surrounded by [NAME_REDACTED] («////»). They mark text, which will be rendered as part of a tab in the final document. The scheme is:
-
-    //// tab | {tab title}
-    {tab content, may span many lines}
-    ////
-
-Keep everything before the vertical bar («|») as is, including the vertical bar. Translate the tab title. Translate the tab content, applying the rules you know. Keep the four block closing slashes as is.
-
-Examples:
-
-    Source (English):
-
-        «««
-        //// tab | Python 3.8+ non-Annotated
-        Hello
-        ////
-        »»»
-
-    Result (German):
-
-        «««
-        //// tab | Python 3.8+ nicht annotiert
-        Hallo
-        ////
-        »»»
-
-    Source (English) – Here there is nothing to translate in the tab title:
-
-        «««
-        //// tab | Linux, macOS, [NAME_REDACTED]
-        Hello again
-        ////
-        »»»
-
-    Result (German):
-
-        «««
-        //// tab | Linux, macOS, [NAME_REDACTED]
-        Hallo wieder
-        ////
-        »»»
-
-
-### Headings
-
-[NAME_REDACTED] heading in the English text (all levels) ends with a part inside curly brackets. This part denotes the hash of this heading, which is used in links to this heading. In translations, translate the heading, but do not translate this hash part, so that links do not break.
-
-Examples of how to translate a heading:
-
-    Source (English):
-
-        «««
-        ## Alternative API docs { #alternative-api-docs }
-        »»»
-
-    Result (Spanish):
-
-        «««
-        ## Documentación de la API alternativa { #alternative-api-docs }
-        »»»
-
-    Source (English):
-
-        «««
-        ### Example { #example }
-        »»»
-
-    Result (German):
-
-        «««
-        ### Beispiel { #example }
-        »»»
-
-
-### Links
-
-Use the following rules for links (apply both to Markdown-style links ([text](url)) and to HTML-style  tags):
-
-1) For relative URLs, only translate link text. Do not translate the URL or its parts
-
-Example:
-
-    Source (English):
-
-        «««
-        [One of the fastest Python frameworks available](#performance)
-        »»»
-
-    Result (German):
-
-        «««
-        [Eines der schnellsten verfügbaren Python-Frameworks](#performance)
-        »»»
-
-2) For absolute URLs which DO NOT start EXACTLY with «https://fastapi.tiangolo.com», only translate link text and leave the URL unchanged.
-
-Example:
-
-    Source (English):
-
-        «««
-        SQLModel docs
-        »»»
-
-    Result (German):
-
-        «««
-        SQLModel-Dokumentation
-        »»»
-
-3) For absolute URLs which DO start EXACTLY with «https://fastapi.tiangolo.com», only translate link text and change the URL by [NAME_REDACTED] («https://fastapi.tiangolo.com/{language_code}[rest part of the url]»).
-
-Example:
-
-    Source (English):
-
-        «««
-        Documentation
-        »»»
-
-    Result (Spanish):
-
-        «««
-        Documentación
-        »»»
-
-3.1) Do not add language codes for URLs that point to static assets (e.g., images, CSS, JavaScript).
-
-Example:
-
-    Source (English):
-
-        «««
-        Something
-        »»»
-
-    Result (Spanish):
-
-        «««
-        Algo
-        »»»
-
-4) For internal links, only translate link text.
-
-Example:
-
-    Source (English):
-
-        «««
-        [[NAME_REDACTED]](help-fastapi.md#create-a-pull-request){.internal-link target=_blank}
-        »»»
-
-    Result (German):
-
-        «««
-        [Pull Requests erzeugen](help-fastapi.md#create-a-pull-request){.internal-link target=_blank}
-        »»»
-
-5) Do not translate anchor fragments in links (the part after «#»), as they must remain the same to work correctly.
-
-5.1) If an existing translation has a link with an anchor fragment different to the anchor fragment in the English source, then this is an error. Fix this by [NAME_REDACTED] of the English source.
-
-Example:
-
-    Source (English):
-
-        «««
-        [Body - [NAME_REDACTED]: Singular values in body](body-multiple-params.md#singular-values-in-body){.internal-link target=_blank}
-        »»»
-
-    Existing wrong translation (German) – notice the wrongly translated anchor fragment:
-
-        «««
-        [Body – [NAME_REDACTED]: [NAME_REDACTED] im Body](body-multiple-params.md#einzelne-werte-im-body){.internal-link target=_blank}.
-        »»»
-
-    Result (German) – you fix the anchor fragment:
-
-        «««
-        [Body – [NAME_REDACTED]: [NAME_REDACTED] im Body](body-multiple-params.md#singular-values-in-body){.internal-link target=_blank}.
-        »»»
-
-5.2) Do not add anchor fragments at will, even if this makes sense. If the English source has no anchor, don't add one.
-
-Example:
-
-    Source (English):
-
-        «««
-        Create a [virtual environment](../virtual-environments.md){.internal-link target=_blank}
-        »»»
-
-    Wrong translation (German) – Anchor added to the URL.
-
-        «««
-        Erstelle eine [virtuelle Umgebung](../virtual-environments.md#create-a-virtual-environment){.internal-link target=_blank}
-        »»»
-
-    Good translation (German) – URL stays like in the English source.
-
-        «««
-        Erstelle eine [[NAME_REDACTED]](../virtual-environments.md){.internal-link target=_blank}
-        »»»
-
-
-### HTML abbr elements
-
-Translate HTML abbr elements («text») as follows:
-
-1) If the text surrounded by [NAME_REDACTED] an abbreviation (the text may be surrounded by [NAME_REDACTED] markup or quotes, for example «text» or «`text`» or «"text"», ignore that further markup when deciding if the text is an abbreviation), and if the description (the text inside the title attribute) contains the full phrase for this abbreviation, then append a dash («–») to the full phrase, followed by [NAME_REDACTED] full phrase.
-
-Conversion scheme:
-
-    Source (English):
-
-        {abbreviation}
-
-    Result:
-
-        {abbreviation}
-
-Examples:
-
-    Source (English):
-
-        «««
-        IoT
-        CPU
-        TL;DR:
-        »»»
-
-    Result (German):
-
-        «««
-        IoT
-        CPU
-        TL;DR:
-        »»»
-
-1.1) If the language to which you translate mostly uses the letters of the ASCII char set (for example Spanish, French, German, but not Russian, Chinese) and if the translation of the full phrase is identical to, or starts with the same letters as the original full phrase, then only give the translation of the full phrase.
-
-Conversion scheme:
-
-    Source (English):
-
-        {abbreviation}
-
-    Result:
-
-        {abbreviation}
-
-Examples:
-
-    Source (English):
-
-        «««
-        JWT
-        Enum
-        ASGI
-        »»»
-
-    Result (German):
-
-        «««
-        JWT
-        Enum
-        ASGI
-        »»»
-
-2) If the description is not a full phrase for an abbreviation which the abbr element surrounds, but some other information, then just translate the description.
-
-Conversion scheme:
-
-    Source (English):
-
-        {text}
-
-    Result:
-
-        {translation of text}
-
-Examples:
-
-    Source (English):
-
-        «««
-        path
-        linter
-        parsing
-        0.95.0
-        at the time of writing this
-        »»»
-
-    Result (German):
-
-        «««
-        Pfad
-        Linter
-        Parsen
-        0.95.0
-        zum Zeitpunkt als das hier geschrieben wurde
-        »»»
-
-
-3) If the text surrounded by [NAME_REDACTED] an abbreviation and the description contains both the full phrase for that abbreviation, and other information, separated by a colon («:»), then append a dash («–») and the translation of the full phrase to the original full phrase and translate the other information.
-
-Conversion scheme:
-
-    Source (English):
-
-        {abbreviation}
-
-    Result:
-
-        {abbreviation}
-
-Examples:
-
-    Source (English):
-
-        «««
-        I/O
-        CDN
-        IDE
-        »»»
-
-    Result (German):
-
-        «««
-        I/O
-        CDN
-        IDE
-        »»»
-
-3.1) Like in rule 2.1, you can leave the original full phrase away, if the translated full phrase is identical or starts with the same letters as the original full phrase.
-
-Conversion scheme:
-
-    Source (English):
-
-        {abbreviation}
-
-    Result:
-
-        {abbreviation}
-
-Example:
-
-    Source (English):
-
-        «««
-        ORM
-        »»»
-
-    Result (German):
-
-        «««
-        ORM
-        »»»
-
-4) If there is an existing translation, and it has ADDITIONAL abbr elements in a sentence, and these additional abbr elements do not exist in the related sentence in the English text, then KEEP those additional abbr elements in the translation. Do not remove them. Except when you remove the whole sentence from the translation, because the whole sentence was removed from the English text, then also remove the abbr element. The reasoning for this rule is, that such additional abbr elements are manually added by [NAME_REDACTED] the translation, in order to translate or explain an English word to the human readers of the translation. These additional abbr elements would not make sense in the English text, but they do make sense in the translation. So keep them in the translation, even though they are not part of the English text. This rule only applies to abbr elements.
-
-5) Apply above rules also when there is an existing translation! Make sure that all title attributes in abbr elements get properly translated or updated, using the schemes given above. However, leave the ADDITIONAL abbr's from rule 4 alone. Do not change their formatting or content.
-
-"""
+general_prompt_path = Path(__file__).absolute().parent / "llm-general-prompt.md"
+general_prompt = general_prompt_path.read_text(encoding="utf-8")

 app = typer.Typer()

There appears to be a typo. The filename should be `general-llm-prompt.md`.


🌐 Update LLM prompt instructions file for French

🌐 Update LLM prompt instructions file for [NAME_REDACTED] was generated by [NAME_REDACTED] the review in https://github.com/fastapi/fastapi/pull/14580 and asking the LLM to generate instructions to account for those cases.

[USER_REDACTED], your input would be great here. 🙌

@@ -6,123 +6,127 @@ Language code: fr.

 ### Grammar to use when talking to the reader

-Use the formal grammar (use «vous» instead of «tu»).
+Use the formal grammar (use `vous` instead of `tu`).

-### Quotes
+Additionally, in instructional sentences, prefer the present tense for obligations:
+
+- Prefer `vous devez …` over `vous devrez …`, unless the English source explicitly refers to a future requirement.
+
+- When translating “make sure (that) … is …”, prefer the indicative after `vous assurer que` (e.g. `Vous devez vous assurer qu'il est …`) instead of the subjunctive (e.g. `qu'il soit …`).

-1) Convert neutral double quotes («"») and English double typographic quotes («“» and «”») to French guillemets (««» and «»»).
+### Quotes

-2) In the French docs, guillemets are written without extra spaces: use «texte», not « texte ».
+- Convert neutral double quotes (`"`) to French guillemets (`«` and `»`).

-3) Do not convert quotes inside code blocks, inline code, paths, URLs, or anything wrapped in backticks.
+- Do not convert quotes inside code blocks, inline code, paths, URLs, or anything wrapped in backticks.

 Examples:

-    Source (English):
+Source (English):

-        «««
-        "Hello world"
-        “[NAME_REDACTED]”
-        "He said: 'Hello'"
-        "The module is `__main__`"
-        »»»
+```
+"Hello world"
+“[NAME_REDACTED]”
+"He said: 'Hello'"
+"The module is `__main__`"
+```

-    Result (French):
+Result (French):

-        «««
-        «Hello world»
-        «[NAME_REDACTED]»
-        «He said: 'Hello'»
-        «The module is `__main__`»
-        »»»
+```
+"Hello world"
+“[NAME_REDACTED]”
+"He said: 'Hello'"
+"The module is `__main__`"
+```

 ### Ellipsis

-1) Make sure there is a space between an ellipsis and a word following or preceding the ellipsis.
+- Make sure there is a space between an ellipsis and a word following or preceding the ellipsis.

 Examples:

-    Source (English):
+Source (English):

-        «««
-        ...as we intended.
-        ...this would work:
-        ...etc.
-        others...
-        More to come...
-        »»»
+```
+...as we intended.
+...this would work:
+...etc.
+others...
+More to come...
+```

-    Result (French):
+Result (French):

-        «««
-        ... comme prévu.
-        ... cela fonctionnerait :
-        ... etc.
-        D'autres ...
-        La suite ...
-        »»»
+```
+... comme prévu.
+... cela fonctionnerait :
+... etc.
+D'autres ...
+La suite ...
+```

-2) This does not apply in URLs, code blocks, and code snippets. Do not remove or add spaces there.
+- This does not apply in URLs, code blocks, and code snippets. Do not remove or add spaces there.

 ### Headings

-1) Prefer translating headings using the infinitive form (as is common in the existing French docs): «Créer…», «Utiliser…», «Ajouter…».
-
-2) For headings that are instructions written in imperative in English (e.g. “Go check …”), keep them in imperative in French, using the formal grammar (e.g. «Allez voir …»).
+- Prefer translating headings using the infinitive form (as is common in the existing French docs): `Créer…`, `Utiliser…`, `Ajouter…`.

-3) Keep heading punctuation as in the source. In particular, keep occurrences of literal « - » (space-hyphen-space) as « - » (the existing French docs use a hyphen here).
+- For headings that are instructions written in imperative in English (e.g. `Go check …`), keep them in imperative in French, using the formal grammar (e.g. `Allez voir …`).

 ### French instructions about technical terms

-Do not try to translate everything. In particular, keep common programming terms when that is the established usage in the French docs (e.g. «framework», «endpoint», «plug-in», «payload»). Use French where the existing docs already consistently use French (e.g. «requête», «réponse»).
+Do not try to translate everything. In particular, keep common programming terms (e.g. `framework`, `endpoint`, `plug-in`, `payload`).

 Keep class names, function names, modules, file names, and CLI commands unchanged.

 ### List of English terms and their preferred French translations

-Below is a list of English terms and their preferred French translations, separated by a colon («:»). Use these translations, do not use your own. If an existing translation does not use these terms, update it to use them.
+Below is a list of English terms and their preferred French translations, separated by a colon (:). Use these translations, do not use your own. If an existing translation does not use these terms, update it to use them.
+
+- /// note | [NAME_REDACTED]»: /// note | Détails techniques
+- /// note: /// note | Remarque
+- /// tip: /// tip | Astuce
+- /// warning: /// warning | Alertes
+- /// check: /// check | Vérifications
+- /// info: /// info

-* «/// note | [NAME_REDACTED]»: «/// note | Détails techniques»
-* «/// note»: «/// note | Remarque»
-* «/// tip»: «/// tip | Astuce»
-* «/// warning»: «/// warning | Attention»
-* «/// check»: «/// check | vérifier»
-* «/// info»: «/// info»
+- the docs: les documents
+- the documentation: la documentation

-* «the docs»: «les documents»
-* «the documentation»: «la documentation»
+- Exclude from OpenAPI: Exclusion d'OpenAPI

-* «framework»: «framework» (do not translate to «cadre»)
-* «performance»: «performance»
+- framework: framework (do not translate to cadre)
+- performance: performance

-* «type hints»: «annotations de type»
-* «type annotations»: «annotations de type»
+- type hints: annotations de type
+- type annotations: annotations de type

-* «autocomplete»: «autocomplétion»
-* «autocompletion»: «autocomplétion»
+- autocomplete: autocomplétion
+- autocompletion: autocomplétion

-* «the request» (what the client sends to the server): «la requête»
-* «the response» (what the server sends back to the client): «la réponse»
+- the request (what the client sends to the server): la requête
+- the response (what the server sends back to the client): la réponse

-* «the request body»: «le corps de la requête»
-* «the response body»: «le corps de la réponse»
+- the request body: le corps de la requête
+- the response body: le corps de la réponse

-* «path operation»: «opération de chemin»
-* «path operations» (plural): «opérations de chemin»
-* «path operation function»: «fonction de chemin»
-* «path operation decorator»: «décorateur d'opération de chemin»
+- path operation: chemin d'accès
+- path operations (plural): chemins d'accès
+- path operation function: fonction de chemin d'accès
+- path operation decorator: décorateur de chemin d'accès

-* «path parameter»: «paramètre de chemin»
-* «query parameter»: «paramètre de requête»
+- path parameter: paramètre de chemin
+- query parameter: paramètre de requête

-* «the `Request`»: «`Request`» (keep as code identifier)
-* «the `Response`»: «`Response`» (keep as code identifier)
+- the `Request`: `Request` (keep as code identifier)
+- the `Response`: `Response` (keep as code identifier)

-* «deployment»: «déploiement»
-* «to upgrade»: «mettre à niveau»
+- deployment: déploiement
+- to upgrade: mettre à niveau

-* «deprecated»: «déprécié»
-* «to deprecate»: «déprécier»
+- deprecated: déprécié
+- to deprecate: déprécier

-* «cheat sheet»: «aide-mémoire»
-* «plug-in»: «plug-in»
+- cheat sheet: aide-mémoire
+- plug-in: plug-in

Very good changes. Minimal edits to be applied

We specifically mention to not change the quotes inside code blocks. Why do we do it here?

I would recommend "Alertes" instead of "Attention".
"Alerte" is a very broad term comparable to "heads up".
"Attention", which by [NAME_REDACTED] "warning" carries a heavy meaning; closer to "BE CAREFUL!!" (Caps included)

Vérifications*

Oh, you're totally right, thanks for catching it!

Perfect, thanks!


🐛 Fix using `Json[list[str]]` type (issue #10997)

Fixes Form() not working with Pydantic `Json[T]` types when T is a sequence type (list, set, tuple).

Closes #10997

When using `Form()` with `Json[list[str]]`, FastAPI incorrectly treated it as a sequence field and used `getlist()`, wrapping the JSON string in a list. This caused Pydantic to fail parsing with:
```
TypeError: JSON input should be string, bytes or bytearray
```

**Before fix:**
```python
# Client sends
data = {"items": '["abc", "def"]'}  # JSON string

# FastAPI incorrectly does
value = values.getlist("items")  # ['["abc", "def"]']  ❌
```

**After fix:**
```python
# FastAPI correctly does
value = values.get("items")  # '["abc", "def"]'  ✅
```

This fix enables legitimate use cases like file uploads with JSON metadata:

```python
[USER_REDACTED].post("/upload")
def upload(
    file: UploadFile,
    tags: Annotated[Json[list[str]], Form()]
):
    return {"file": file.filename, "tags": tags}
```

Pydantic v1 support for `Json[T]` with `Form()` is not included in this PR because `metadata` attribute does not exist in Pydantic v1's `FieldInfo`.

## Related
- Issue #10997

@@ -51,7 +51,7 @@
 from fastapi.security.oauth2 import SecurityScopes
 from fastapi.types import DependencyCacheKey
 from fastapi.utils import create_model_field, get_path_param_names
-from pydantic import BaseModel
+from pydantic import BaseModel, Json
 from pydantic.fields import FieldInfo
 from starlette.background import BackgroundTasks as StarletteBackgroundTasks
 from starlette.concurrency import run_in_threadpool
@@ -726,11 +726,19 @@ def _validate_value_with_model_field(
         return v_, []

+def _is_json_field(field: ModelField) -> bool:
+    return any(type(item) is Json for item in field.field_info.metadata)
+
+
 def _get_multidict_value(
     field: ModelField, values: Mapping[str, Any], alias: Union[str, None] = None
 ) -> Any:
     alias = alias or get_validation_alias(field)
-    if is_sequence_field(field) and isinstance(values, (ImmutableMultiDict, Headers)):
+    if (
+        (not _is_json_field(field))
+        and is_sequence_field(field)
+        and isinstance(values, (ImmutableMultiDict, Headers))
+    ):
         value = values.getlist(alias)
     else:
         value = values.get(alias, None)

@@ -0,0 +1,63 @@
+import json
+from typing import Annotated
+
+from fastapi import Cookie, FastAPI, Form, Header, Query
+from fastapi.testclient import TestClient
+from pydantic import Json
+
+app = FastAPI()
+
+
+[USER_REDACTED].post("/form-json-list")
+def form_json_list(items: Annotated[Json[list[str]], Form()]) -> list[str]:
+    return items
+
+
+[USER_REDACTED].get("/query-json-list")
+def query_json_list(items: Annotated[Json[list[str]], Query()]) -> list[str]:
+    return items
+
+
+[USER_REDACTED].get("/header-json-list")
+def header_json_list(x_items: Annotated[Json[list[str]], Header()]) -> list[str]:
+    return x_items
+
+
+[USER_REDACTED].get("/cookie-json-list")
+def cookie_json_list(items: Annotated[Json[list[str]], Cookie()]) -> list[str]:
+    return items
+
+
+client = TestClient(app)
+
+
+def test_form_json_list():
+    response = client.post(
+        "/form-json-list", data={"items": json.dumps(["abc", "def"])}
+    )
+    assert response.status_code == 200, response.text
+    assert response.json() == ["abc", "def"]
+
+
+def test_query_json_list():
+    response = client.get(
+        "/query-json-list", params={"items": json.dumps(["abc", "def"])}
+    )
+    assert response.status_code == 200, response.text
+    assert response.json() == ["abc", "def"]
+
+
+def test_header_json_list():
+    response = client.get(
+        "/header-json-list", headers={"x-items": json.dumps(["abc", "def"])}
+    )
+    assert response.status_code == 200, response.text
+    assert response.json() == ["abc", "def"]
+
+
+def test_cookie_json_list():
+    client.cookies.set("items", json.dumps(["abc", "def"]))
+    response = client.get("/cookie-json-list")
+    assert response.status_code == 200, response.text
+    assert response.json() == ["abc", "def"]
+    client.cookies.clear()

[USER_REDACTED], thanks for your interest!

The idea looks good to me.
Please, take a look at my suggestions.

---

**UPD:** I think this will fix `Json[list[str]]` not only for `Form` parameters, but for other types of parameters (`Query`, `Header`, etc..) as well.
[USER_REDACTED], could you please check it and add tests for other types of parameters?

LGTM!

Currently (on `master` branch) tests for `Query`, `Form` and `Header` fail. Test for `Cookie` passes, but I think we should keep it for consistency.

[USER_REDACTED], thank you for quick updates!

Great job! Thank you! 🙌

I was convinced of not supporting this (reading the issue), but this implementation is simple and clean enough that I think it makes sense to have it. Thanks! 🚀

This will be available in FastAPI 0.128.2, released in the next few hours. 🎉

```suggestion
    return any(isinstance(item, Json) for item in field.field_info.metadata)
```

FastAPI dropped the support of Pydantic V1 recently.
We can now simplify this.
Also, we should use `isinstance` to check type

```suggestion
    if (
        (not _is_json_field(field))
        and is_sequence_field(field)
        and isinstance(values, (ImmutableMultiDict, Headers))
    ):
```

```suggestion
```
I think we don't need this test

Could you please explain why you used `dict` here, not `list`?
With `dict` this test passes on `master` branch.

You're right! After investigating, I found that Cookie was never affected by [NAME_REDACTED], they skip `getlist()` path.
I've removed the Cookie test. The three remaining tests (Form/Query/Header) properly cover the bug fix.

I mean for Query you use `Json[list[str]]`, but for Cookie `Json[dict[str, str]]` (`list` vs `dict`).

What if you declare cookie endpoint as:

```py
[USER_REDACTED].get("/cookie-json-list")
def cookie_json_list(
    items: Annotated[Json[list[str]], Cookie()],
) -> list[str]:
    return items
```
?

I think this should also fail on `master` branch and be fixed by [NAME_REDACTED]

I thought the same, but when I tested on master, it passed 😶
```bash
==================================================================== test session starts ====================================================================
...
tests/test_form_json_type.py::test_form_json_list FAILED                                                                                [ 25%]
tests/test_form_json_type.py::test_query_json_list FAILED                                                                                [ 50%]
tests/test_form_json_type.py::test_header_json_list FAILED                                                                                [ 75%]
tests/test_form_json_type.py::test_cookie_json_list PASSED                                                                                [100%]
```
Looks like cookies don't go through the getlist() path.
cookie values are plain dict, not ImmutableMultiDict or Headers, so they skip that.

u can check by [NAME_REDACTED]
```python
import json
from typing import Annotated

from fastapi import Cookie, FastAPI
from fastapi.testclient import TestClient
from pydantic import Json

app = FastAPI()

[USER_REDACTED].get("/cookie-json-list")
def cookie_json_list(
    session: Annotated[Json[list[str]], Cookie()],
) -> list[str]:
    return session

client = TestClient(app)

def test_cookie_json_list():
    client.cookies.set("session", json.dumps(["user", "test1", "role", "admin"]))
    response = client.get("/cookie-json-list")
    assert response.status_code == 200, response.text
    assert response.json() == ["user", "test1", "role", "admin"]
```

Interesting... Thanks for clarifying this!

I would still add this test with `Annotated[Json[list[str]], Cookie()]` for consistency.
And, we need to update the name of test module to reflect that it's not only for `Form`

Done! Added Cookie test consistent with other types and renamed the file to `test_json_type.py`.

Great! Thank you!


📝 Update more docs with Python 3.8 to Python 3.9

@@ -257,7 +257,7 @@ commons: Annotated[CommonQueryParams, Depends()]

 ////

-//// tab | Python 3.8 nicht annotiert
+//// tab | Python 3.9+ nicht annotiert

 /// tip | Tipp

@@ -239,7 +239,7 @@ A PR should have a specific use case that it is solving.
 * If the PR is for a feature, it should have docs.
     * Unless it's a feature we want to discourage, like support for a corner case that we don't want users to use.
 * The docs should include a source example file, not write Python directly in Markdown.
-* If the source example(s) file can have different syntax for Python 3.8, 3.9, 3.10, there should be different versions of the file, and they should be shown in tabs in the docs.
+* If the source example(s) file can have different syntax for different Python versions, there should be different versions of the file, and they should be shown in tabs in the docs.
 * There should be tests testing the source example.
 * Before the PR is applied, the new tests should fail.
 * After applying the PR, the new tests should pass.

@@ -257,7 +257,7 @@ commons: Annotated[CommonQueryParams, Depends()]

 ////

-//// tab | Python 3.8 sin `Annotated`
+//// tab | Python 3.9+ sin `Annotated`

 /// tip | Consejo

@@ -257,7 +257,7 @@ commons: Annotated[CommonQueryParams, Depends()]

 ////

-//// tab | Python 3.8 non-Annotated
+//// tab | Python 3.9+ non-Annotated

 /// tip | Dica

@@ -47,7 +47,7 @@ For the next terms, use the following translations:
 * list (as in Python list): list
 * [NAME_REDACTED]: Aprendizado de Máquina
 * media type: media type (do not translate to "tipo de mídia")
-* non-Annotated: non-Annotated (do not translate non-Annotated when it comes after a Python version.e.g., “Python 3.8+ non-Annotated”)
+* non-Annotated: non-Annotated (do not translate non-Annotated when it comes after a Python version.e.g., “Python 3.10+ non-Annotated”)
 * operation IDs: IDs de operação
 * path (as in URL path): path
 * path operation: operação de rota

@@ -257,7 +257,7 @@ commons: Annotated[CommonQueryParams, Depends()]

 ////

-//// tab | Python 3.8 non-Annotated
+//// tab | Python 3.9+ non-Annotated

 /// tip | Подсказка

Why not 3.9+ here ?

This is just an example of what to translate or what not to, the Python version doesn't have much importance here. :nerd_face:

I'm updating it just so that it doesn't show up in search looking for `Python 3.8`.

Thank you for the clarification


🔧 Add LLM prompt file for [NAME_REDACTED], generated from the existing translations

---

This will be used to update existing translations and generate new ones.

@@ -0,0 +1,54 @@
+### Target language
+
+Translate to [NAME_REDACTED] (繁體中文).
+
+Language code: zh-hant.
+
+### Grammar and tone
+
+1) Use clear, concise technical [NAME_REDACTED] consistent with existing docs.
+2) Address the reader naturally (commonly using “你/你的”).
+
+### Headings
+
+1) Follow existing [NAME_REDACTED] heading style (short and descriptive).
+2) Do not add trailing punctuation to headings.
+
+### Quotes and punctuation
+
+1) Keep punctuation style consistent with existing [NAME_REDACTED] docs (they often mix English terms like “FastAPI” with Chinese text).
+2) Never change punctuation inside inline code, code blocks, URLs, or file paths.
+3) For more details, please follow the [[NAME_REDACTED]](https://github.com/[USER_REDACTED]noid/chinese-copywriting-guidelines).
+
+### Ellipsis
+
+1) Keep ellipsis style consistent within each document, prefer `...` over `……`.
+2) Never change ellipsis in code, URLs, or CLI examples.
+
+### Preferred translations / glossary
+
+1. Should avoid using simplified Chinese characters and terms. Always examine if the translation can be easily comprehended by [NAME_REDACTED]
+2. For some Python-specific terms like "pickle", "list", "dict" etc, we don't have to translate them.
+3. Use the following preferred translations when they apply in documentation prose:
+
+- request (HTTP): 請求
+- response (HTTP): 回應
+- path operation: 路徑操作
+- path operation function: 路徑操作函式
+
+The translation can optionally include the original English text only in the first occurrence of each page (e.g. "路徑操作 (path operation)") if the translation is hard to be comprehended by [NAME_REDACTED] readers.
+
+### `///` admonitions
+
+1) Keep the admonition keyword in English (do not translate `note`, `tip`, etc.).
+2) [NAME_REDACTED] docs currently omit titles in `///` blocks; that is OK.
+3) If a generic title is present, prefer these canonical titles:
+
+- `/// note | 注意`
+
+Notes:
+
+- `details` blocks exist; keep `/// details` as-is and translate only the title after `|`.
+- Example canonical titles used in existing docs:
+  - `/// details | 上述指令的含義`
+  - `/// details | 關於 `requirements.txt``

add some common rules that i frequently use.
I believe it's enough as a starter.

```suggestion
### Preferred translations / glossary

1. Should avoid using simplified Chinese characters and terms. Always examine if the translation can be easily comprehended by [NAME_REDACTED]
2. For some Python-specific terms like "pickle", "list", "dict" etc, we don't have to translate them.
3. Use the following preferred translations when they apply in documentation prose:
```

```suggestion
3) For more details, please follow the [[NAME_REDACTED]](https://github.com/[USER_REDACTED]noid/chinese-copywriting-guidelines).

```

```suggestion
- path operation function: 路徑操作函式

The translation can optinoally includes the original English text only in the first occurence of each page (e.g. "路徑操作 (path operation)") if the translation is hard to be comprehended by [NAME_REDACTED] readers.
```

Perfect, I added this as well :raised_hands:


@@ -0,0 +1,46 @@
+### Target language
+
+Translate to [NAME_REDACTED] (简体中文).
+
+Language code: zh.
+
+### Grammar and tone
+
+1) Use clear, concise technical Chinese consistent with existing docs.
+2) Address the reader naturally (commonly using “你/你的”).
+
+### Headings
+
+1) Follow existing [NAME_REDACTED] heading style (short and descriptive).
+2) Do not add trailing punctuation to headings.
+3) If a heading contains only the name of a FastAPI feature, do not translate it.
+
+### Quotes and punctuation
+
+1) Keep punctuation style consistent with existing [NAME_REDACTED] docs (they often mix English terms like “FastAPI” with Chinese text).
+2) Never change punctuation inside inline code, code blocks, URLs, or file paths.
+
+### Ellipsis
+
+1) Keep ellipsis style consistent within each document, prefer `...` over  `……`.
+2) Never change ellipsis in code, URLs, or CLI examples.
+
+### Preferred translations / glossary
+
+Use the following preferred translations when they apply in documentation prose:
+
+- request (HTTP): 请求
+- response (HTTP): 响应
+- path operation: 路径操作
+- path operation function: 路径操作函数
+
+### `///` admonitions
+
+1) Keep the admonition keyword in English (do not translate `note`, `tip`, etc.).
+2) If a title is present, prefer these canonical titles:
+
+- `/// tip | 提示`
+- `/// note | 注意`
+- `/// warning | 警告`
+- `/// info | 信息`
+- `/// danger | 危险`

LGTM

When translating English technical documentation into Chinese, LLMs often translate headings that consist entirely of program keywords, class names, function names, and similar identifiers into Chinese. Given the popularity of FastAPI and the fact that current LLM models already have knowledge of it, one can consider explicitly instructing the model, for example:

```suggestion
3) If a heading contains only the name of a FastAPI feature, do not translate it.

```

Awesome, thanks for the feedback! I just added it.

I think it's:
```
- `/// note | 注`
```

How About:

```
- `/// note | 注意`
```

Although this is not its full literal meaning, it works in most contexts and reads more elegantly.
虽然字面意思并不止如此，但这在大多数语境下成立并且更加优雅。

Thank you! I updated it this way. :raised_hands: