-
-
Notifications
You must be signed in to change notification settings - Fork 322
🎈🇫🇷 Add french translation #3333
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The head ref may contain hidden characters: "\u{1F956}\u{1F1EB}\u{1F1F7}"
Conversation
frontend/lang/french.json
Outdated
| "t_time_seconds_other": "{{count}} secondes", | ||
|
|
||
| "t_frontmatter_title": "Métadonnées", | ||
| "t_frontmatter_description": "Si tu publies ce notebook sur le web, tu peux définir les paramètres ci-dessous pour fournir des métadonnées HTML. C'est utile pour les moteurs de recherche et les réseaux sociaux.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might help to add the english "frontmatter" in the description here? Up to you!
|
Looks really good!! We used the informal "you" in Dutch and German, but that's much less common in French computer language, right? |
btw these translating decisions are good to document somewhere? I've used the formal (plural) "you" in Greek, mainly because all the telcos and the banks now use informal language in apps, SMS, one time passwords etc, like we're old friends [but it's me that somehow pays 50€ for basic nerfed services, to each] and I didn't want to sound like that |
|
I documented the German comments and decisions in the corresponding PR, but if that moves to a central place, I can add them there as well. For distinctions between formal/informal (Sie/Du in German) – that is really interesting to see how that is different and developing differently in so many languages. In German it was maybe a bit strange when Ikea started to use the informal form to all its customers in the 90s, but there is an agreement, that for such short informal things – also ordering a Döner or fast food – it is ok and in Apps now common, the formal one then even sounds a bit stiff. In Norwegian, there is even a small joke, that one would use the formal form still today, but only to address the King. In practice, that is not done, the King is usually dressed in third person (so even more formal). But everything else is on the informal level. That makes sometimes English conversations here, but even more German ones, complicated. yeah so let me know when we have a common place to document the style decisions – probably also different per language – stored somewhere. |
I don't think it is that common, but taking the IKEA example, they also use the more informal 'tu' form in french. Apps such as Duolingo also use it. I can let other french Pluto users such as @gdalle chime in on this. |
|
@kellertuer That's a good idea to keep these discussions somewhere in a document! Maybe one MD document per language? Or a global style.md document? Right now, I wrote this: Pluto.jl/frontend/lang/README.md Line 122 in ecc3294
because I wanted there to be a bit of direction, but each contributor should see how to best apply that in their language/culture. |
gdalle
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome initiative! I reviewed and fixed a few things:
- Putting everything in the second person ("tu"). I think it is acceptable nowadays, and it fits with Pluto's friendly design. Personally I like to imaging Fons speaking to me when I read error messages, and Fons says "tu" ;)
- Adding inclusive writing. This doesn't exist in English but French is a gendered language with masculine word forms as the default. In technical fields like ours, it is especially important to include feminine forms as well, which can be done through this median dot "·" among other mechanisms.
- Fix a few spelling mistakes. I'm particularly surprised that the LLM consistently uses "où" for "or" instead of "ou".
As a side note, some JSON fields seem to have gone missing compared to english.json, but I didn't do an exhaustive comparison.
frontend/lang/french.json
Outdated
|
|
||
| "t_my_work": "Mon travail", | ||
| "t_newnotebook": "Créer un <strong>nouveau notebook</strong>", | ||
| "t_welcome_to_pluto": "bienvenue sur {{pluto}}", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"sur" or "dans"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
frontend/lang/french.json
Outdated
| "t_live_docs_body": "<p>Bienvenue dans la <b>documentation en direct</b>! Guardes cette petite fenêtre ouverte quand tu travailles sur le notebook, et tu auras de la documentation sur tout ce que tu tapes!</p><p>Tu peux aussi taper une recherche en haut.</p><hr><p><em>Toujours bloqué? Voici <a target=\"_blank\" href=\"https://julialang.org/about/help/\">quelques astuces</a>.</em></p>", | ||
| "t_panel_status": "Statut du processus", | ||
| "t_panel_status_short": "Statut", | ||
| "t_panel_docs": "Live Docs", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| "t_panel_docs": "Live Docs", | |
| "t_panel_docs": "Documentation", |
frontend/lang/french.json
Outdated
|
|
||
|
|
||
| "t_stop_notebook_session": "Arrêter la session", | ||
| "t_shut_down_notebook": "Éteindre le notebook", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| "t_shut_down_notebook": "Éteindre le notebook", | |
| "t_shut_down_notebook": "Éteindre le notebook", |
I don't really like that verb for something non-physical, "arrêter" might be better
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
'Arrêter' is definitely better!
| "t_frontmatter_cancel": "Annuler", | ||
| "t_frontmatter_save": "Sauvegarder", | ||
| "t_frontmatter_preview": "Aperçu", | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want t_frontmatter_language_placeholder for French too? It seems to have been forgotten
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see that key in the english json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pluto.jl/frontend/lang/english.json
Line 268 in ecc3294
| "t_frontmatter_language_placeholder": "en-US (enter a BCP 47 language tag)", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh right, I have not rebased on main 🤦
Co-authored-by: Guillaume Dalle <22795598+gdalle@users.noreply.github.com>
|
Thank you Guillaume for the review!
Very nice idea, I did not think of that.
To be fair, this one is on me (and most other grammatical mistakes) 🙈 |
|
Thanks! @Pangoraw feel free to merge when ready! @gdalle and @Pangoraw how was the localisation experience for you? Something you would add to https://github.com/fonsp/Pluto.jl/blob/main/frontend/lang/README.md ? |
|
Merging, let's fix any remaining problem in post. |


Salut! Here is my take on the french translation.
I used a similar techique as @pankgeorg (generating JSON translated output with AI and then checking it).
Try this Pull Request!
Open Julia and type: