Skip to content

Comments

improved fr.json#1750

Closed
khaledmhirsi wants to merge 3 commits intoMail-0:stagingfrom
khaledmhirsi:patch-1
Closed

improved fr.json#1750
khaledmhirsi wants to merge 3 commits intoMail-0:stagingfrom
khaledmhirsi:patch-1

Conversation

@khaledmhirsi
Copy link

@khaledmhirsi khaledmhirsi commented Jul 17, 2025

Reviewed the whole json with Grok and corrected some things manually.

Description

Made the wording consistent and more similar to existing apps:

  • instead of using "e-mail, email, mail, courrier, message", it's "courriel" when referring to an email.
  • instead of saying "les indésirables", made it "courrier indésirable"
  • added "en cours" when necessary

Type of Change

Please delete options that are not relevant.

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • 🎨 UI/UX improvement

Areas Affected

Please check all that apply:

  • Email Integration (Gmail, IMAP, etc.)
  • User Interface/Experience
  • Authentication/Authorization
  • Data Storage/Management
  • API Endpoints
  • Documentation
  • Testing Infrastructure
  • Development Workflow
  • Deployment/Infrastructure

Testing Done

Describe the tests you've done:

  • Unit tests added/updated
  • Integration tests added/updated
  • Manual testing performed
  • Cross-browser testing (if UI changes)
  • Mobile responsiveness verified (if UI changes)

Security Considerations

For changes involving data or authentication:

  • No sensitive data is exposed
  • Authentication checks are in place
  • Input validation is implemented
  • Rate limiting is considered (if applicable)

Checklist

  • I have read the CONTRIBUTING document
  • My code follows the project's style guidelines
  • I have performed a self-review of my code
  • I have commented my code, particularly in complex areas
  • I have updated the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix/feature works
  • All tests pass locally
  • Any dependent changes are merged and published

Additional Notes

It could be a great idea to have multiple versions of the same language. For example English in the US/UK/Australia is different.
For here specifically, the word spam in french is different between french (Canada) and french (France): "pourriel" != "courrier indésirable"

Screenshots/Recordings

Add screenshots or recordings here if applicable.


By submitting this pull request, I confirm that my contribution is made under the terms of the project's license.

Summary by CodeRabbit

  • Style
    • Improved clarity, consistency, and fluency of French localization throughout the mail application interface.
    • Standardized terminology for mail-related concepts and UI elements.
    • Enhanced pluralization patterns and updated error and confirmation messages for better user understanding.
    • Applied minor corrections to capitalization, spacing, and punctuation across all sections.

Reviewed the whole json with Grok and corrected some things manually.

Made the wording consistent and more similar to existing apps:
- instead of using "e-mail, email, mail, courrier, message", it's "courriel" when referring to an email.
- instead of saying "les indésirables", made it "courrier indésirable"
- added "en cours" when necessary
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 17, 2025

Walkthrough

The French localization file for the mail application is updated to enhance clarity, consistency, and fluency across UI strings. The changes standardize terminology, adjust pluralization, and refine phrasing throughout the interface, while maintaining the existing JSON schema and message keys.

Changes

File(s) Change Summary
apps/mail/messages/fr.json Refined French UI strings: standardized terminology (e.g., "courriel", "courriers indésirables"), improved phrasing, updated pluralization patterns, formalized status and error messages, and minor punctuation and spacing corrections. No structural or key changes.

Possibly related PRs

  • New Crowdin updates #474: Updates and improves French UI strings in the same localization JSON, making it closely related in scope.
  • New Crowdin updates #538: Adds a new "refresh" key to multiple locale files including French, related by targeting the same localization file but addressing different aspects.
  • New Crowdin updates #525: Modifies the French localization file focusing on removing the "favourites" entry rather than refining existing strings.

Poem

In fields of words, the rabbit hops,
Polishing French with careful stops.
"Courriel" now reigns, so clear and bright,
Plurals and phrases set just right.
UI sings with fluent grace—
Vive la langue, in every place!
🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d800cc4 and 3fd0829.

📒 Files selected for processing (1)
  • apps/mail/messages/fr.json (20 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • apps/mail/messages/fr.json

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (2)
apps/mail/messages/fr.json (2)

227-232: Simplify ‘favourites’ label

Current: « Avec étoile ».
Suggested: simply « Favoris » to match the other keys (star, unstar, addedToFavorites, etc.) and to avoid awkward phrasing.

-      "favourites": "Avec étoile",
+      "favourites": "Favoris",

560-563: Remove trailing space in “bulkStar” string

There is an extra space at the end of the value.

-      "bulkStar": "Marquage aux favoris en masse ",
+      "bulkStar": "Marquage aux favoris en masse",
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d9db7a4 and e2d00e5.

📒 Files selected for processing (1)
  • apps/mail/messages/fr.json (19 hunks)
🧰 Additional context used
🧠 Learnings (1)
apps/mail/messages/fr.json (1)
Learnt from: yaraslau-klimuk
PR: Mail-0/Zero#604
File: apps/mail/locales/en.json:366-389
Timestamp: 2025-04-06T18:28:21.659Z
Learning: The translation file for the editor's menu bar already includes an "orderedList" key with the value "Ordered List" as part of PR #604.
🔇 Additional comments (1)
apps/mail/messages/fr.json (1)

318-321: Optional: gender agreement for count-zero case

"aucune réponse" is correct (feminine réponse) ‑ good catch; no change needed.

Comment on lines +309 to 311
"defaultEmailUpdated": "Adresse e-mail par défaut mise à jour",
"failedToUpdateGmailAlias": "Échec de la mise à jour de l'alias e-mail par défaut"
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Replace residual “e-mail” with “courriel” for consistency

Several strings still read « e-mail », e.g.:

  • defaultEmailUpdated, failedToUpdateGmailAlias
  • defaultEmailAlias, selectDefaultEmail, etc.
  • “Signatures e-mail” section titles/descriptions

Since the PR goal is to standardise on courriel, update these remaining occurrences.

-      "defaultEmailUpdated": "Adresse e-mail par défaut mise à jour",
+      "defaultEmailUpdated": "Adresse courriel par défaut mise à jour",

Apply the same replacement to the other listed keys.

Also applies to: 451-453, 467-469, 490-508


🏁 Script executed:

#!/bin/bash
rg -n "e-mail" apps/mail/messages/fr.json

Length of output: 1110


Replace all remaining “e-mail” with “courriel” in apps/mail/messages/fr.json

Example diff:

-      "defaultEmailUpdated": "Adresse e-mail par défaut mise à jour",
+      "defaultEmailUpdated": "Adresse courriel par défaut mise à jour",

Please apply the same replacement to these locations in apps/mail/messages/fr.json:

  • Lines 309–310:
    • defaultEmailUpdated
    • failedToUpdateGmailAlias
  • Lines 450–452:
    • defaultEmailAlias
    • selectDefaultEmail
    • defaultEmailDescription
  • Lines 457–460:
    • title (“Connexions e-mail”)
    • description
    • disconnectTitle
    • disconnectDescription
  • Lines 466–467:
    • connectEmail
    • connectEmailDescription
  • Lines 490–491:
    • title (“Signatures e-mail”)
    • description
  • Line 589:
    • invalidEmail

Ensure every “e-mail” becomes “courriel” (plural “courriels” where appropriate).

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"defaultEmailUpdated": "Adresse e-mail par défaut mise à jour",
"failedToUpdateGmailAlias": "Échec de la mise à jour de l'alias e-mail par défaut"
},
"defaultEmailUpdated": "Adresse courriel par défaut mise à jour",
"failedToUpdateGmailAlias": "Échec de la mise à jour de l'alias e-mail par défaut"
},
🤖 Prompt for AI Agents
In apps/mail/messages/fr.json at lines 309-311, 450-452, 457-460, 466-467,
490-491, and 589, replace all occurrences of "e-mail" with "courriel" and use
"courriels" for plural forms. Update the values for keys including
defaultEmailUpdated, failedToUpdateGmailAlias, defaultEmailAlias,
selectDefaultEmail, defaultEmailDescription, title ("Connexions e-mail"),
description, disconnectTitle, disconnectDescription, connectEmail,
connectEmailDescription, title ("Signatures e-mail"), description, and
invalidEmail accordingly to reflect this change.

Comment on lines +22 to +24
"movedToSpam": "Déplacé vers les courriers indésirables",
"movingToSpam": "Déplacement vers les courriers indésirables en cours...",
"deletingMail": "Suppression du courriel en cours...",
Copy link
Contributor

@coderabbitai coderabbitai bot Jul 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Standardise “courriel(s) indésirable(s)” across the file

The text alternates between « courriers indésirables » (lines 22-23, 402-403, 527-528, 542-543) and « courriels indésirables » (lines 55-56).
Stick to one form to avoid user-visible inconsistency. Given the PR objective explicitly favours courriel, align everything to courriel(s) indésirable(s).

Diff (sample for the first occurrences):

-      "movedToSpam": "Déplacé vers les courriers indésirables",
-      "movingToSpam": "Déplacement vers les courriers indésirables en cours...",
+      "movedToSpam": "Déplacé vers les courriels indésirables",
+      "movingToSpam": "Déplacement vers les courriels indésirables en cours...",

Do the same for all remaining instances.

Also applies to: 54-58, 402-403, 527-528, 542-543


🏁 Script executed:

#!/bin/bash
# List all occurrences of “courriers” and “courriels” in the French messages file
rg -n '"courrier' apps/mail/messages/fr.json

Length of output: 46


🏁 Script executed:

#!/bin/bash
# Locate the French translation file and list all occurrences of both variants
file=$(find . -type f -path '*/apps/mail/messages/fr.json' -print -quit)
echo "Inspecting: $file"
rg -n '"courriers indésirables"' "$file"
rg -n '"courriels indésirables"' "$file"

Length of output: 322


🏁 Script executed:

#!/bin/bash
# Search for occurrences of courriers, courriels, and indésirables in the French messages file
rg -n courriers apps/mail/messages/fr.json
rg -n courriels apps/mail/messages/fr.json
rg -n indésirables apps/mail/messages/fr.json

Length of output: 3890


Standardiser l’usage de « courriel(s) indésirable(s) » dans fr.json

Les occurrences de « courriers indésirables » alternent avec « courriels indésirables ». Pour cohérence (la PR privilégie « courriel »), remplacez toutes les instances de « courriers indésirables » par « courriels indésirables ».

Points à corriger (exemples de clés et lignes) :

  • movedToSpam / movingToSpam (l. 22-23)
  • deleteAllSpam / deletingAllSpam (l. 54-55)
  • confirmDeleteSpam (l. 58)
  • goToSpam (l. 83 et 542)
  • moveToSpam (l. 220 et 333)
  • spam (libellé du dossier, l. 402)

Diff d’exemple pour les premières lignes :

-      "movedToSpam": "Déplacé vers les courriers indésirables",
-      "movingToSpam": "Déplacement vers les courriers indésirables en cours...",
+      "movedToSpam": "Déplacé vers les courriels indésirables",
+      "movingToSpam": "Déplacement vers les courriels indésirables en cours...",

Appliquez ce même remplacement partout dans apps/mail/messages/fr.json.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"movedToSpam": "Déplacé vers les courriers indésirables",
"movingToSpam": "Déplacement vers les courriers indésirables en cours...",
"deletingMail": "Suppression du courriel en cours...",
"movedToSpam": "Déplacé vers les courriels indésirables",
"movingToSpam": "Déplacement vers les courriels indésirables en cours...",
"deletingMail": "Suppression du courriel en cours...",
🤖 Prompt for AI Agents
In apps/mail/messages/fr.json from lines 22 to 542, replace all occurrences of
"courriers indésirables" with "courriels indésirables" to maintain consistency
with the preferred term "courriel" used throughout the file. This includes keys
such as movedToSpam, movingToSpam, deleteAllSpam, deletingAllSpam,
confirmDeleteSpam, goToSpam, moveToSpam, and the spam folder label. Perform a
global search and replace for the phrase to ensure uniform terminology.

Copy link
Author

@khaledmhirsi khaledmhirsi Jul 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Coderabbit start speaking french lol

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@khaledmhirsi Haha, good catch! 😄

I switched to French in my previous comment because I was reviewing the French localization file (fr.json) and providing feedback about French terminology consistency. I was probably trying to be contextually appropriate since we were discussing French translations.

However, you're right to point that out - it's better to keep code review feedback in English for accessibility, even when reviewing localization files. That way everyone on the team can understand the feedback regardless of the target language being localized.

The substance of my feedback remains the same though: there's an inconsistency between "courriers indésirables" and "courriels indésirables" throughout the file that should be standardized to "courriels indésirables" to match the PR's objective of using "courriel" consistently.

🐰
/| /|
( ✌️ )
|(_)|

khaledmhirsi and others added 2 commits July 17, 2025 23:15
Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
@MrgSub
Copy link
Collaborator

MrgSub commented Jul 18, 2025

@maxprilutskiy is our i18n source of truth

@github-actions
Copy link
Contributor

github-actions bot commented Aug 7, 2025

This PR has merge conflicts and has been open for more than 3 days. It will be automatically closed. Please resolve the conflicts and reopen the PR if you'd like to continue working on it.

@github-actions github-actions bot closed this Aug 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants