-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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 french trad in i18n translations #9885
base: develop
Are you sure you want to change the base?
Conversation
|
@aurelien-f is attempting to deploy a commit to the medusajs Team on Vercel. A member of the Team first needs to authorize it. |
I can help here I'm french, and I'm looking for Dashboard translation :) |
Thanks, i translated all the document but if you want to check or correct some parts. Can i add you on discord ? |
Hello @aurelien-f, I already did a PR adressin this feature: #9677 |
Yes no problem |
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.
Hi @aurelien-f
Thanks for the PR, the fr.json file is missing some keys and has an unexpected key as well:
Validation failed for fr.json:
Missing required key: "edit" at /products
Unexpected key: "editProduct" at /products
You will also need to update this file: https://github.com/medusajs/medusa/blob/develop/packages/admin/dashboard/src/i18n/languages.ts to include French as an option.
And export the fr.json file from here: https://github.com/medusajs/medusa/blob/develop/packages/admin/dashboard/src/i18n/translations/index.ts
I tried to complete these missing steps but it seems I cannot commit into this PR What should I do? |
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.
Thank you very much for the contribution 💪
I ve made a few suggestions, could you have a look and let me know what you think about them please? Also, depending on what you think, they are also likely applicable to the rest of the translations 😃
"items_one": "{{count}} item", | ||
"items_other": "{{count}} items", | ||
"countSelected": "{{count}} sélectionné", | ||
"countOfTotalSelected": "{{count}} de {{total}} sélectionné", |
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.
"countOfTotalSelected": "{{count}} de {{total}} sélectionné", | |
"countOfTotalSelected": "{{count}} sur {{total}} sélectionné", |
"new": "Nouveau", | ||
"modified": "Modifié", | ||
"added": "Ajouté", | ||
"removed": "Removed", |
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.
"removed": "Removed", | |
"removed": "supprimé", |
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 would suggest adding An uppercase
Supprimé
"noSearchResults": "Aucun résultat de recherche", | ||
"noSearchResultsFor": "Aucun résultat de recherche pour <0>'{{query}}'</0>", | ||
"noRecordsTitle": "Aucun enregistrement", | ||
"noRecordsMessage": "Il n'y a pas d'enregistrements à afficher", |
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.
"noRecordsMessage": "Il n'y a pas d'enregistrements à afficher", | |
"noRecordsMessage": "Il n'y a pas d'enregistrement à afficher", |
for consistency with previous singular usage
"noRecordsMessage": "Il n'y a pas d'enregistrements à afficher", | ||
"unsavedChangesTitle": "Êtes-vous sûr de vouloir quitter ce formulaire ?", | ||
"unsavedChangesDescription": "Vous avez des modifications non enregistrées qui seront perdues si vous quittez ce formulaire.", | ||
"includesTaxTooltip": "Les prix de cette colonne sont taxés inclus.", |
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.
"includesTaxTooltip": "Les prix de cette colonne sont taxés inclus.", | |
"includesTaxTooltip": "Les prix de cette colonne sont taxes incluses.", |
I would say taxes incluses
instead of taxés inclus
which is probably a typo no?
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.
Maybe a better translation would be :
Les prix de cette colonne incluent les taxes
or
Les prix de cette colonne sont TTC (toutes taxes comprises)
What you think ?
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 like both suggestions 👍 I would prefer the first one but I let you decide
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 like both suggestions 👍 I would prefer the first one but I let you decide
I prefer the second one. Think it's more accurate but maybe not what's expected.
I Would suggest going with the first one and waiting for more opinions on the subject ^^
"unsavedChangesTitle": "Êtes-vous sûr de vouloir quitter ce formulaire ?", | ||
"unsavedChangesDescription": "Vous avez des modifications non enregistrées qui seront perdues si vous quittez ce formulaire.", | ||
"includesTaxTooltip": "Les prix de cette colonne sont taxés inclus.", | ||
"excludesTaxTooltip": "Les prix de cette colonne sont taxés exclusifs.", |
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.
"excludesTaxTooltip": "Les prix de cette colonne sont taxés exclusifs.", | |
"excludesTaxTooltip": "Les prix de cette colonne sont taxes exclues.", |
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.
Maybe a better translation would be :
Les prix de cette colonne excluent les taxes
or
Les prix de cette colonne sont HT (Hors Taxes)
What you think ?
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.
Depends on the previous comment discussion
"storeSettings": "Paramètres de la boutique" | ||
}, | ||
"settings": { | ||
"header": "Settings", |
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.
"header": "Settings", | |
"header": "Paramètres", |
}, | ||
"dataGrid": { | ||
"columns": { | ||
"view": "View", |
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.
"view": "View", | |
"view": "Vue", |
wdyt?
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.
Depending on the context maybe "Affichage" is more suitable
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 yeah, that seems better indeed 💪
} | ||
}, | ||
"errors": { | ||
"fixError": "Fix error", |
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.
"fixError": "Fix error", | |
"fixError": "Corriger les erreurs", |
wdyt?
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.
Seems singular here so I would say :
Corriger l'erreur
} | ||
}, | ||
"sales_channels": { | ||
"availableIn": "Disponible dans <0>{{x}}</0> de <1>{{y}}</1> canaux de vente" |
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.
"availableIn": "Disponible dans <0>{{x}}</0> de <1>{{y}}</1> canaux de vente" | |
"availableIn": "Disponible dans <0>{{x}}</0> canaux de vente sur <1>{{y}}</1>" |
Wouldnt this be more accurate?
"availableIn": "Disponible dans <0>{{x}}</0> de <1>{{y}}</1> canaux de vente" | ||
}, | ||
"products": { | ||
"domain": "Products", |
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.
"domain": "Products", | |
"domain": "Produits", |
Hello, i send you a new pull request.
What - Add french trad in i18n translations
Why - Offer a new language and be able to offer my clients a French language
How - I used AI and my knowledge of French to do the translation
Testing - I have not tested the changes.