Skip to content

🌐 Update translations for fr (update-outdated)#14580

Closed
tiangolo wants to merge 8 commits intomasterfrom
translate-fr-update-outdated-78abe3ae
Closed

🌐 Update translations for fr (update-outdated)#14580
tiangolo wants to merge 8 commits intomasterfrom
translate-fr-update-outdated-78abe3ae

Conversation

@tiangolo
Copy link
Member

🌐 Update translations for fr (update-outdated)

@github-actions github-actions bot added the lang-all Translations label Dec 21, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 21, 2025

📝 Docs preview

Last commit 12b1d19 at: https://24856eac.fastapitiangolo.pages.dev

Modified Pages

@codspeed-hq
Copy link

codspeed-hq bot commented Dec 21, 2025

CodSpeed Performance Report

Merging this PR will not alter performance

Comparing translate-fr-update-outdated-78abe3ae (12b1d19) with master (f2687dc)

Summary

✅ 20 untouched benchmarks
⏩ 40 skipped benchmarks1

Footnotes

  1. 40 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

@tiangolo tiangolo added awaiting-review lang-fr French translations labels Dec 21, 2025
Copy link

@Pyth3rEx Pyth3rEx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The pull is overall good quality tho a few things don't specifically make total sense or could be lightly improved.

# Codes HTTP supplémentaires { #additional-status-codes }

Par défaut, **FastAPI** renverra les réponses à l'aide d'une structure de données `JSONResponse`, en plaçant la réponse de votre *chemin d'accès* à l'intérieur de cette `JSONResponse`.
Par défaut, **FastAPI** renverra les réponses à l'aide d'une structure de données `JSONResponse`, en plaçant la réponse de votre *opération de chemin* à l'intérieur de cette `JSONResponse`.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unless there is a common saying "operation de chemin" which I have missed, the older "chemin d'acces" saying seems clearer.

Dans OpenAPI, les chemins sont des ressources, tels que /users/ ou /items/, exposées par votre API, et les opérations sont les méthodes HTTP utilisées pour manipuler ces chemins, telles que GET, POST ou DELETE. Les operationId sont des chaînes uniques facultatives utilisées pour identifier une opération d'un chemin. Vous pouvez définir l'OpenAPI `operationId` à utiliser dans votre *opération de chemin* avec le paramètre `operation_id`.
Vous pouvez définir l'OpenAPI `operationId` à utiliser dans votre *opération de chemin* avec le paramètre `operation_id`.

Vous devez vous assurer qu'il est unique pour chaque opération.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the correct grammar for this sentence as it is a general truth.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, we should revert change in this line, right?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes please

{* ../../docs_src/path_operation_advanced_configuration/tutorial001.py hl[6] *}
{* ../../docs_src/path_operation_advanced_configuration/tutorial001_py39.py hl[6] *}

### Utilisation du nom *path operation function* comme operationId

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Utilisation du nom" is more professional

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should also try to keep it close to the original version, which is

Using the *path operation function* name as the operationId

So, do you think we should revert change, keep change or just adjust new version?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would recommend reverting for this one.

/// tip | Astuce

Si vous appelez manuellement `app.openapi()`, vous devez mettre à jour les `operationId` avant.
Si vous appelez manuellement `app.openapi()`, vous devez mettre à jour les `operationId` avant cela.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uneeded


///

## Exclusion d'OpenAPI

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Old saying is more professional

Copy link
Member

@YuriiMotov YuriiMotov Dec 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I translate Exclusion d'OpenAPI using online translator, it's something like Exclusion of OpenAPI.
At the same time Exclure d'OpenAPI is translated as Exclude from OpenAPI (that is in line with the original header in English).

Original is: Exclude from OpenAPI

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As a native french speaker, Exclusion d'OpenAPI is the proper saying for a documentation

Vous pouvez limiter les lignes utilisées de la docstring d'une *fonction d'opération de chemin* pour OpenAPI.

L'ajout d'un `\f` (un caractère d'échappement "form feed") va permettre à **FastAPI** de tronquer la sortie utilisée pour OpenAPI à ce stade.
L'ajout d'un `\f` (un caractère d'échappement «form feed») fait que **FastAPI** tronque la sortie utilisée pour OpenAPI à cet endroit.
Copy link

@Pyth3rEx Pyth3rEx Dec 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be a combination of both. I propose:

L'ajout d'un `\f` (un caractère d'échappement «form feed») permet à **FastAPI** de tronquer la sortie utilisée pour OpenAPI à cet endroit.

Copy link

@Pyth3rEx Pyth3rEx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some more very minor stuff

# Tests de performance { #benchmarks }

Les tests de performance de TechEmpower montrent que les applications **FastAPI** tournant sous Uvicorn comme <a href="https://www.techempower.com/benchmarks/#section=test&runid=7464e520-0dc2-473d-bd34-dbdfd7e85911&hw=ph&test=query&l=zijzen-7" class="external-link" target="_blank">étant l'un des frameworks Python les plus rapides disponibles</a>, seulement inférieur à Starlette et Uvicorn (tous deux utilisés au cœur de FastAPI). (*)
Des tests de performance indépendants de TechEmpower montrent que les applications **FastAPI** exécutées sous Uvicorn sont <a href="https://www.techempower.com/benchmarks/#section=test&runid=7464e520-0dc2-473d-bd34-dbdfd7e85911&hw=ph&test=query&l=zijzen-7" class="external-link" target="_blank">parmi les frameworks Python les plus rapides disponibles</a>, seulement derrière Starlette et Uvicorn eux‑mêmes (tous deux utilisés en interne par FastAPI).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct phrasing:
Des tests de performance indépendants de TechEmpower montrent que les applications **FastAPI** exécutées sous Uvicorn sont <a href="https://www.techempower.com/benchmarks/#section=test&runid=7464e520-0dc2-473d-bd34-dbdfd7e85911&hw=ph&test=query&l=zijzen-7" class="external-link" target="_blank">parmi les frameworks Python les plus rapides disponibles</a>, seulement inférieur à Starlette et Uvicorn eux‑mêmes (tous deux utilisés en interne par FastAPI).

@github-actions github-actions bot added the conflicts Automatically generated when a PR has a merge conflict label Jan 11, 2026
@github-actions
Copy link
Contributor

This pull request has a merge conflict that needs to be resolved.

@tiangolo
Copy link
Member Author

I regenerated the French translations after updating the LLM prompt, the new PR is here: #14723

I'll close this one so we can continue there.

@tiangolo tiangolo closed this Jan 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved-1 conflicts Automatically generated when a PR has a merge conflict lang-all Translations lang-fr French translations

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants