I know, that inconsistency is annoying, but I’m not sure we can change them yet again. Those companies usually define which labels are allowed for their login buttons. See UX: Less specific styling for Auth logins by jordanvidrine · Pull Request #16393 · discourse/discourse · GitHub for more context on this. Translations should respect those requirements as well.
Looks like there are some translations missing on Crowdin. You can search for js.login to find them.
Thank you for your reply!
I updated my message while you were writing I think. I didn’t rebuild my forum after April 18th hence the missing translations on my forum.
This one will make French-speaking users here laugh:
Thanks, DeepL!
(“Conne” is sort of a rude equivalent of “stupid” for females; “con” for males. Also “con” is a rarely used, rude term for female genitals)
Since “Connectez-vous” was already used for buttons, I added the same translation for the remaining untranslated login button strings, though I’m not sure if Github, Discord, and Twitter requires specific French translations… 
I undertook to translate the few texts from the table builder.
French is often very verbose compared to English, and overly long words or phrases can sometimes not fit the layout or be a bit tedious to read.
For table builder, I suggested “Éditeur de tableaux” or “Tableur”. The former seems clearer to me, but the latter could also be appropriate since the word “Spreadsheet” is used in one of the English strings.
I also used Tab instead of Tabulation, because FR keyboards have “Tab” written on the said key…
Questioning also for:
| EN | FR | FR alt |
|---|---|---|
| at the end of a row to insert a new row. | à la fin d’une ligne pour en insérer une nouvelle. | à la fin d’une ligne pour insérer une nouvelle ligne. |
The first translation avoids a potentially inelegant repetition of the word “ligne” (same for the string with “colonne”), although the repetition is present in the English string.
I wasn’t sure what to choose for this either:
| EN | FR | FR alt | FR alt alt |
|---|---|---|---|
| Right-click on cells to access more options in a dropdown menu. | Clic droit sur une cellule pour afficher les options disponibles. | Clic droit sur une cellule pour afficher des options supplémentaires. | Clic droit sur une cellule pour afficher des options contextuelles. |
In short, there are other things where I was a bit in the dark, if anyone wants to review my proposals 
FR and FR alt are identical, but we can see what you mean and indeed this version is better.
FR alt alt also seems more accurate to me. We don’t really care how they are displayed, we understand it well after clicking. 
I spent way too long on that one 
only to conclude that yep Tab is probably best…
did not know about ↹ !
Many thanks Coin-coin (and hellekin for the revision)
About the sidebar, if you guide lost users by phone, beware there are two “plus” in the Communauté section, one + and one Plus... 
… indeed.
bonus: that will avoid the problem of the teacher/tutor
Administrator… 
In English it’s admin, why not keep that term?
As for inclusivity, we could use the neutral gender of Alpheratz and say: administrataire.
Admin would suit me. I don’t know if this abbreviation is more used in English than in French, but it is certainly very used in French as well in IT systems, so I don’t think a forum admin would be unsettled (even if they don’t know much about IT).
I have a slight personal preference for Administration as there is room for it.
As for Administrataire, I am gradually educating myself on inclusive writing (it’s a fascinating field that leads to playing with language), I didn’t know this form.
I like it, I am for inclusivity, but if the objective of translating the interface is to have clear and immediately understandable terms, I fear that Administrataire might be a bit strange and not fully meet this objective.
By the way, it seems to me that neutralizing terms or sentence structures, like here using “Administration” instead of “Administrator”, is one form among others of inclusive writing.
I am wondering about the amount of work and the desire among translators to create a “neutral French” version.
Why is French not listed on this page? https://discourse.crowdin.com/u/projects/4
I think it’s best to ignore all translation notifications for those languages, including French, until further notice from the Discourse team.
You need to search for “French”
Did community translation resume?
Just translated a string, it seems to be back
I personally think it would be really nice to have a “per language” space, or at least a tag for translations concerning a specific language.
For my part, I generally use all my software in English, but the community I’m migrating to Discourse is French-speaking, so I use it in French.
There are translations that, in my opinion, are a bit heavy or awkward, or even sometimes ambiguous—now that I understand how to access Crowdin, I will take the time to make suggestions when I see something.
But beyond that, it seems to me that there are issues on the terminology side—at least for someone coming from outside the Discourse world. Two come to mind:
First, “post” and “message” in English both seem to have been translated as “message,” which creates ambiguity.
Second, the translation of “topic” as “sujet.” I must admit that I am not very enthusiastic about the choice of term in English, even if I understand the logic behind it. And yes, “sujet” is a good translation for “topic.”
But the problem is that the semantic field of “topic” and “sujet” is not identical. “Sujet” is much broader than “topic”; it also includes things like “subject.” It is a very common word in everyday language, much more so, in my opinion (we could look for objective data to confirm), than “topic” in English.
So in French, using “sujet” for “discussions” creates many more linguistic problems in my opinion than using “topic” in English.
I have no illusions about the possibility of changing things like this. However, it might be interesting to provide a plugin (component?) that allows for different terminology (given the laborious work it represents to change everything manually).
I haven’t read the entire thread above, so apologies if I’m rehashing things already discussed. Feel free to tell me.
At this stage, I just wanted to share these thoughts.
