French translations

[JulianMaurin]

Bonjour 🇫🇷

Welcome to the issue that coordinates the French translation effort.

Purpose

• Avoiding several people working on the same document at the same time.

The first person who declares that he/she is working on a translation gets the responsibility to carry it out. If a PR seems to be stalled, we can discuss a transfer of responsibility here.

• Enforcing best practices

Best practices are listed later in this description. You can propose your practice at any time, ideally with a supporting source and an example.

Defining and sharing best practices will help to avoid common mistakes and will allow faster and easier reviews.

• Help and build the community

Do not hesitate to ask any questions regarding the french translation effort here. The stronger the community, the more effective we will be and the more we will enjoy.

• Provide a french translation for this awesome library (last but not least)

If you are here, you probably like FastAPI, and maybe you even speak French. Giving more people the opportunity to get started using the documentation in its native language will encourage adoption. In that spirit, let's contribute to the magic of open source in this way.

How to contribute

Review

Keep in mind that the easiest way to participate is to review the PRs. We need to avoid accumulating PRs waiting for review.

Translate

If you are not familiar with contributing to open source projects have a look at https://github.com/firstcontributions/first-contributions.

In any case, take a look at the documentation section related to the contribution and more precisely the part about the documentation.

Once you are decided to translate a document, make yourself known here by leaving a message here (eg. #1972 (comment)).

Organize

If you wish, your energy is welcome to help with the organization. Bringing together motivated people and helping them get the job done is essential. Moreover, we can surely learn a lot from the translation work of other languages that are much more advanced and we can have a significant impact if we put good processes in place that can help the whole community

Good practices

• technical terms

Technical terms do not need to be translated. It is also a question of common sense, in certain conditions English can be preferred because the French version is not in use.
See: #1972 (comment)

• punctuation and typography

For example, missing whitespace before/after punctuation. You can rely on this page to help you.
see: #1973 (comment)

• structure the PR by commit

Splitting the commit will ease the review and helps to track the change on the original documentation while the PR is open.
(see: example).

The first commit should only contain the copy of the English version of the document to the french one. With the exact same content (eg. 30f1dd6).

The second one is dedicated the index update (eg. 8ff5f7a)

And starting from this point you can start the translation. Notice that, thanks to this structure we can directly compare the two languages (eg. 3729f5b).

Also, if the English document got updated, we just have to update the first commit and the conflicts will reveal updated part of the document 🪄

Recommended tools

• https://www.deepl.com
• https://www.linguee.fr
• https://www.wordreference.com
• https://french.stackexchange.com

[JulianMaurin]

I'm starting with the docs/index.md: #1973

[Jefidev]

Hello, I would like to help with this but it is the first time I contribute to an open-source project. Could you summarize me the workflow to correctly push the update ?

[Kludex]

@Jefidev

• Post here the page you'll be translating.
• Work on it.
• Create the PR with your work.
• Developers will review.
• Fix issues/get approvals.
• Wait for enough approvals (usually 2-3 are enough based on what I've seen).
• @tiangolo will merge if everything is fine.

[Jefidev]

Thanks, So I am translating the features.md docs/features.md page

[JulianMaurin]

Hey @Jefidev , to contribute you can also review the existing PR :)
Thanks for you motivation ✌️

[JulianMaurin]

I take the docs/contributing.md 💪
cf. #2132

[Jefidev]

Hi,
Ok I will also check the PR. I just want to be clear on some convention. Do you translate python types.
For instance Dict => dictionnaires
I did it but as a programmer even if my main language is french I refer to them as Dict.

For very specific technical terms I decided to do the same thing as the Spanish translator. They translate the terms but add an note with the English technical term.

Here are the technical terms for which I cannot find a propper translation :

• In-process background tasks.
• path operations

[clemsau]

I am taking on docs/benchmarks.md.

[JulianMaurin]

I'll work on docs/fastapi-people.md :)
cf. #2232

[JulianMaurin]

The next one is: help-fastapi.md 🚀
cf. #2233

[JulianMaurin]

Hi @Jefidev

I just want to be clear on some convention. Do you translate python types.
For instance Dict => dictionnaires
I did it but as a programmer even if my main language is french I refer to them as Dict.
For very specific technical terms I decided to do the same thing as the Spanish translator. They translate the terms but add an note with the English technical term.

IMHO.
There is no reason to translate python keywords (eg. dict, package, method, ...).
In the other and, we have to translate the English word "dictionary" even when it's used in a technical context.

For the specifics technicals terms, you have to identify if there is an equivalent term in french. But most of the time when we are speaking about technical concepts, the usage of English could not be avoided.

My idea about a translated technical documentation is that it's just to make it easier for people to get into the library. We can assume that the reader will have a technical background and will not be confused by the presence of English technical terms.

[Jefidev]

Hi 😃
I did not translate the words making reference to a python keyword (as you mentioned them dict, package, etc.) or the ones that are common in programming.

For the technical terms, I decided to take a look at the Spanish translation (because it is the most advanced yet but we are coming). They decided to translate the technical terms and display the English terms when hoovering (with the <abbr> tag). I follow that convention for my features.md translation.
For example, I decided to translate Background Tasks by Tâches d'arrière plan. But I decided to keep the words path in English as they should be familiar to the people designing API.

I am keen to discuss this issue more in-depth in order to have a strong convention for the French Translation Team.

[JulianMaurin]

And now tutorial/index.md 💪
cf. #2234

[JulianMaurin]

I am keen to discuss this issue more in-depth in order to have a strong convention for the French Translation Team.

Yes, perfect. Let's confront our choices during the reviews, and report the conventions here :)
(by the way, i'll do a small break in translations for now to do some reviews 👀 )

[rjNemo]

Hello,

what is the current status of the French translation?

I would like to contribute starting with docs/alternatives.md

[cfraboulet]

Hello everyone 😊

I'll work on docs/fr/docs/index.md. I will take the previous PRs (#1973 and #4203) and combine them into a new PR in order to close the previous ones.

Edit: done (#9265) @axel584 @raphaelauv @emmrichard @rjNemo @JulianMaurin

Thanks 🙏🏻

[axel584]

It's a very good idea ! Don't hesitate to ping me for review.

[github-actions[bot]]

There's a new translation PR to be reviewed: #9265 by @frabc Good job! This is done. 🍰☕

[axel584]

Hello,
I've translated a new page : #9415

Thank you @frabc @raphaelauv @emmrichard @JulianMaurin @rjNemo

Thank 🙏

Axel

[tiangolo]

There's a new translation PR to be reviewed: #2155 by @clemsau Good job! This is done. 🍰☕

[tiangolo]

There's a new translation PR to be reviewed: #3172 by @NastasiaSaby Good job! This is done. 🍰☕

[tiangolo]

There's a new translation PR to be reviewed: #2132 by @JulianMaurin Good job! This is done. 🍰☕

[tiangolo]

There's a new translation PR to be reviewed: #4075 by @Smlep Good job! This is done. 🍰☕

[tiangolo]

There's a new translation PR to be reviewed: #2234 by @JulianMaurin Good job! This is done. 🍰☕

[tiangolo]

There's a new translation PR to be reviewed: #9908 by @axel584 Good job! This is done. 🍰☕

[tiangolo]

There's a new translation PR to be reviewed: #10154 by @s-rigaud Good job! This is done. 🍰☕

[tiangolo]

Good news everyone! 😉 There's a new translation PR to be reviewed: #11429 by @Mgcsuper. 🎉 This requires 2 approvals from native speakers to be merged. 🤓

[SlyRock]

Hi Everyone !
I'm and experienced senior PHP/JS backend developer and I've worked on a few API projects (mainly using ZF1 LARAVEL or express.js).
I'm brand new to python and FastAPI, I'd like to start my learning curve by contributing to the french translation (I'm french by the way).
I'm having a look at this PR but I'm a bit confused. There doesn't seem to be a docs/en/docs/tutorial/test.md file to compare to. I found a docs/en/docs/tutorial/testing.md file that seems to be the original content translated here. Am I missing something or did I get it right ?

Furthermore, do I have to be anointed by someone here in order to be able to approve the PR after review ? ^^

Cheers mates :)

Edit :
As go along my review I'm finding stuff that could be improved in the translation, how should I proceed with those ? Should I comment the lines or is there a way to suggest the improvements myself so they can be accepted by the author ? (I'm not really used to do this on GitHub, I've mostly worked with gitlab 😅)

[axel584]

Salut,
Bienvenu à toi.
Je ne comprends pas de quel fichier tu parles ? Pourquoi tu recherches ce fichier tutorial/test.md ?
As tu l'adresse de la page web dont tu recherches la traduction ?
Avant de commencer la traduction, n'hésite pas à annoncer à l'avance ce que tu comptes traduire. Une fois traduit, il faudra la validation de deux personnes pour qu'elle soit ensuite mergée.

Bon courage,
Axel

[SlyRock]

Bonjour Axel,
Merci pour ta réponse
Je ne cherche pas à faire une nouvelle traduction je voulais déjà démarrer par une revue (comme suggéré sur https://fastapi.tiangolo.com/contributing/) et je suis tombé sur cette PR existante.

Quand je regarde le diff je vois la traduction en français mais pas la langue originale (l'anglais je suppose). J'ai donc cherché le fichier sur la doc en anglais et je l'ai retrouvé sous un autre nom (https://github.com/tiangolo/fastapi/blob/master/docs/en/docs/tutorial/testing.md)
Le contenu correspond à la traduction en français mais je suis étonné que le nom ne soit pas le même. Je m'interroge de savoir si j'ai bien compris.

Egalement J'ai commencé à faire la revue et je vois des amélioration à proposer et je demande aussi dans mon edit quelle est la meilleure manière de proposer ces amélioration :)

Merci d'avance pour tes éclaircissements :)

[axel584]

Désolé, je ne comprends toujours pas.
Peux tu me donner l'url de la PR dont tu veux faire la revue ?

[SlyRock]

Re !
Nous sommes en train de commenter le message de Tiangolo qui annonce que cette PR est en review :
#11429

Peut-etre aurais-je du commenter sur la PR elle-même pour plus de clarté ?

[tiangolo]

There's a new translation PR to be reviewed: #11712 by @benjaminvandammeholberton Good job! This is done. 🍰☕

[benjaminvandammeholberton]

Bonjour !

Désolé, j'ai vu après coup qu'il y avait cette page de discussion. Je n'ai pas fait le premier commit avec la copie de la page en anglais. Est-ce que j'ai besoin de refaire une PR ?

Pour la review, c'est ok de faire un commentaire en indiquant les fautes d'orthographe sur les lignes concernées ?

Merci

[pe-brian]

Hello, I'm new here and I'm really excited to contribute to the french translation !
I'm very motivated.

I just proposed a PR to fix image missing for docs/async.md in the french translation.
Feel free to review.

Thanks!

[pe-brian]

I'm starting the french translation of Path Parameters and Numeric Validations.
For information, and from what I understand, according to this commit, there is no need for updating the file docs/fr/mkdocs.yml anymore.

[tiangolo]

Good news everyone! 😉 There's a new translation PR to be reviewed: #11788 by @pe-brian. 🎉 This requires 2 approvals from native speakers to be merged. 🤓