Bonjour, this is the issue to track and coordinate the French translations.
Feel free to add a comment here to indicate the page you plan to translate 馃摎
Thanks 鉂わ笍
I'm starting with the docs/index.md: https://github.com/tiangolo/fastapi/pull/1973
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 ?
@Jefidev
Thanks, So I am translating the features.md docs/features.md page
Hey @Jefidev , to contribute you can also review the existing PR :)
Thanks for you motivation :v:
I take the docs/contributing.md 馃挭
cf. https://github.com/tiangolo/fastapi/pull/2132
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 :
I am taking on docs/benchmarks.md.
I'll work on docs/fastapi-people.md :)
cf. https://github.com/tiangolo/fastapi/pull/2232
The next one is: help-fastapi.md 馃殌
cf. https://github.com/tiangolo/fastapi/pull/2233
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.
Hi :smiley:
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.
And now tutorial/index.md 馃挭
cf. https://github.com/tiangolo/fastapi/pull/2234
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 馃憖 )
Most helpful comment
Hi :smiley:
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 myfeatures.mdtranslation.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.