-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add work in progress files for Fr translation #9
Conversation
Hello @shtrom , From the last version I uploaded, below my main comments: Questions API Line 180 - poor translation? Line 394 - not translated (not sure how to translate... Is it "angle"?) Lines 403 to 406 - not translated. Not sure how to translate here either. Lines 465, 466 - Not translated. Lines 500, 501: Assess API Line 128,129 - not translated. |
Hey, sorry for the delay in getting back to you.
Are we using
I think for a lot of those hard-to-translate terms, they are buttons for the calculator. We'd need to track down all the available buttons, and see what the sign actually is. I think that would help us find the correct translation.
I think we should use proper French notation, as you describe, but it might be tricky, as we'd need to extend that to code that formats numbers in the rest of the product(which I'm not sure whether we have or not).
|
Hi @shtrom ,
Yes I did this for most of the translation. Also used the latex to find more info and more accurate translation possible using https://fr.wikipedia.org/wiki/Table_de_symboles_math%C3%A9matiques for example.
Do you know who I can reach out to find out this ? Thanks |
I wonder if those two are actual geometrical objects, in which case you'd be right, or math notations (i.e., over variable names or symbols), in which case I don't know what to call them... Edit: yeah, reviving my LaTeX, all the |
AH! https://mirror.aarnet.edu.au/pub/CTAN/info/lshort/french/lshort-fr.pdf
Not everything has ready translations, but there are examples, and partial names, so we can probably play from there, e.g.,
|
languages/fr/questions-api.json
Outdated
"overrightarrow": "Flèche vers la droite au-dessus", | ||
"overleftarrow": "Flèche vers la gauche au-dessus", | ||
"overleftrightarrow": "Flèche bilatérale au-dessus", | ||
"overline": "Trait au-dessus", | ||
"dot": "Point au-dessus", |
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.
👍
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 think this is a good start. Could we perhaps remove all non-translated strings, if any (so we can grep
for them; might also be worth keeping a list of them to remember), and then merge this?
HI @shtrom , I updated both files. I have the list of non translated lines. Not sure how/where to document it though, any guideline or idea? Thanks |
Maybe just a MISSING_TRANSLATIONS file in this directory, with the name of one of the strings per line. |
@shtrom @SalimBensiali