i18n(fr): Improve translation quality#1145
Conversation
Refine French strings for better UI consistency and natural phrasing : - replace informal or literal terms with standard UI vocabulary ; - add missing context to dynamic strings ; - align singular forms with explicit wording instead of relying on [COUNT].
| "placeholder": "Rechercher", | ||
| "clear_search": "Nettoyer", | ||
| "load_more": "Charger plus de résultats", | ||
| "clear_search": "Effacer", |
There was a problem hiding this comment.
"Nettoyer" is indeed the literal translation for "clear" but feels unnatural in this UI context.
"Effacer" is the standard French term used in search inputs.
| "clear_search": "Nettoyer", | ||
| "load_more": "Charger plus de résultats", | ||
| "clear_search": "Effacer", | ||
| "load_more": "Afficher plus de résultats", |
There was a problem hiding this comment.
"Charger" "load" implies a technical action, but from the user perspective, results are being shown. "Afficher" (display) is more accurate and user-friendly for french speakers.
| "search_label": "Recherche sur ce site", | ||
| "filters_label": "Filtres", | ||
| "zero_results": "Pas de résultat pour [SEARCH_TERM]", | ||
| "zero_results": "Aucun résultat pour [SEARCH_TERM]", |
There was a problem hiding this comment.
"Pas de résultat" is correct but informal.
"Aucun résultat" is the standard phrasing used in French UI and feels more polished.
| "one_result": "[COUNT] résultat pour [SEARCH_TERM]", | ||
| "total_zero_results": "Pas de résultat", | ||
| "total_one_result": "[COUNT] résultat", | ||
| "one_result": "Un résultat pour [SEARCH_TERM]", |
There was a problem hiding this comment.
Since this string is used when there is exactly one result, using "Un" instead of [COUNT] is more natural and consistent with "zero_results" which also uses explicit wording instead of a variable.
The similar reasoning that was applied in the German translation by @randomguy-2650 in #1096 : a screen reader may also read "[COUNT] résultat" with incorrect phrasing.
| "total_zero_results": "Pas de résultat", | ||
| "total_one_result": "[COUNT] résultat", | ||
| "one_result": "Un résultat pour [SEARCH_TERM]", | ||
| "total_zero_results": "Aucun résultat", |
| "alt_search": "Pas de résultat pour [SEARCH_TERM]. Montre les résultats pour [DIFFERENT_TERM] à la place", | ||
| "search_suggestion": "Pas de résultat pour [SEARCH_TERM]. Essayer une des recherches suivantes:", | ||
| "searching": "Recherche [SEARCH_TERM]...", | ||
| "alt_search": "Aucun résultat pour [SEARCH_TERM]. Afficher les résultats pour [DIFFERENT_TERM] à la place", |
There was a problem hiding this comment.
"Montre" is correct but an informal imperative that directly addresses the user, it could feel out of place this context.
The infinitive "Afficher" is more appropriate here, as using the infinitive over the imperative is recommended for impersonal instructions, indications, similar to how instructions in documentation or recipes are written in French.
| "search_suggestion": "Pas de résultat pour [SEARCH_TERM]. Essayer une des recherches suivantes:", | ||
| "searching": "Recherche [SEARCH_TERM]...", | ||
| "alt_search": "Aucun résultat pour [SEARCH_TERM]. Afficher les résultats pour [DIFFERENT_TERM] à la place", | ||
| "search_suggestion": "Aucun résultat pour [SEARCH_TERM]. Essayez l'une des recherches suivantes :", |
There was a problem hiding this comment.
"Essayer" (infinitive) is inconsistent with the direct address used elsewhere.
"Essayez" (formal imperative) is more appropriate as it directly and politely addresses the user.
Adding the elision article "l'" is also more grammatically correct than "une des" alone, in this context.
| "searching": "Recherche [SEARCH_TERM]...", | ||
| "alt_search": "Aucun résultat pour [SEARCH_TERM]. Afficher les résultats pour [DIFFERENT_TERM] à la place", | ||
| "search_suggestion": "Aucun résultat pour [SEARCH_TERM]. Essayez l'une des recherches suivantes :", | ||
| "searching": "Recherche de [SEARCH_TERM] en cours...", |
There was a problem hiding this comment.
"Recherche [SEARCH_TERM]" is ambiguous and could be read as a noun ("Search : [SEARCH_TERM]") or an informal imperative.
"Recherche de [SEARCH_TERM] en cours" makes the ongoing action explicit and is more informative for the user.
| "results_label": "Résultats de recherche", | ||
| "keyboard_navigate": "naviguer", | ||
| "keyboard_select": "choisir", | ||
| "keyboard_select": "sélectionner", |
There was a problem hiding this comment.
"Choisir" (to choose) is less precise in UI context.
"Sélectionner" is the standard French term used in interfaces and is consistent with the overall vocabulary of the file.
Note: The infinitive is intentionally kept here, as these keyboard shortcut labels are impersonal indicators, not direct instructions addressed to the user.
| "filter_selected_many": "[COUNT] sélectionnés", | ||
| "input_hint": "Les résultats apparaîtront au fur et à mesure de la saisie", | ||
| "loading": "Chargement" | ||
| "loading": "Chargement en cours..." |
There was a problem hiding this comment.
"Chargement" alone feels rough.
"Chargement en cours..." makes the ongoing action explicit and keeps the consistency with "Recherche de [SEARCH_TERM] en cours..." used in the "searching" string.
1 participant
Refine French strings for better UI consistency and natural phrasing :
See review comments for more information on each string and why it was changed.