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:
(“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
개인적으로 언어별 공간, 혹은 최소한 특정 언어에 관한 번역에 태그를 붙일 수 있는 기능이 있으면 정말 좋겠다고 생각합니다.
저는 보통 모든 소프트웨어를 영어로 사용하지만, Discourse로 이전할 커뮤니티는 프랑스어 사용자들이다 보니 Discourse는 프랑스어로 사용하고 있습니다.
제 생각에 좀 어색하거나 서투른 번역, 심지어 모호한 번역도 몇 가지 있습니다. 이제 Crowdin에 접근하는 방법을 알게 되었으니, 뭔가 눈에 들어오면 제안을 드리기 위해 시간을 내겠습니다.
하지만 그 외에도 어휘 측면에서 문제가 되는 것들이 있는 것 같습니다. 적어도 Discourse 세계 밖에서 온 사람에게는 그렇습니다. 두 가지가 바로 떠오르는데:
첫째, 영어의 "post"와 "message"가 모두 "message"로 번역되어 있어 모호함을 초래합니다.
둘째, "topic"의 번역인 "sujet"입니다. 솔직히 영어 단어 선택 자체에 대해 크게 열광하지는 않지만, 그 뒤의 논리는 이해합니다. 그리고 네, "sujet"은 "topic"의 좋은 번역입니다.
문제는 "topic"과 "sujet"의 의미 범위가 동일하지 않다는 것입니다. "Sujet"은 "topic"보다 훨씬 더 광범위하며, 예를 들어 "subject"도 포함합니다. 제 생각에는(객관적인 데이터를 찾아 확인해 볼 수도 있겠지만) "topic"이라는 영어 단어보다 일상 언어에서 훨씬 더 흔하게 쓰이는 정말 일반적인 단어입니다.
따라서 프랑스어에서 "discussions"에 "sujet"을 사용하는 것은 영어에서 "topic"을 사용하는 것보다 언어적으로 훨씬 더 많은 문제를 일으킨다고 생각합니다.
이런 것들을 변경할 가능성에 대해 환상을 갖지는 않습니다. 대신, 모든 것을 수동으로 변경하는 데 수반되는 힘든 작업을 고려할 때, 다른 용어를 허용하는 플러그인(구성 요소?)을 제공하는 것이 흥미로울 수 있습니다.
위쪽의 전체 스레드를 읽지는 않았으므로, 이미 논의된 내용을 반복하고 있다면 용서해 주세요. 편하게 말씀해 주세요.
이 시점에서 저는 단순히 이런 생각을 공유하고 싶었습니다.
