Skip to content
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

New Crowdin updates #7577

Closed
wants to merge 8 commits into from
Closed

New Crowdin updates #7577

wants to merge 8 commits into from

Conversation

hero101
Copy link
Collaborator

@hero101 hero101 commented Jan 30, 2025

Summary by CodeRabbit

  • Localization

    • Updated translations for Bulgarian, German, Spanish, French, Dutch, Portuguese, and Ukrainian languages
    • Added new buttons: Upload, Notifications, Invite, Visit
    • Introduced comprehensive user role definitions across multiple languages
    • Standardized top bar and error message formatting
  • User Interface

    • Improved sign-in/sign-up text consistency
    • Enhanced error handling and validation messages
    • Added new tooltips and interface labels
  • Internationalization

    • Refined translation files for better user experience
    • Expanded language support with more detailed and accurate translations

Copy link

coderabbitai bot commented Jan 30, 2025

Walkthrough

This pull request involves comprehensive updates to translation files across multiple languages (Bulgarian, German, Spanish, French, Dutch, and Ukrainian). The changes primarily focus on enhancing localization by adding new translation keys, updating existing translations, and improving consistency across language files. Key modifications include adding new buttons (upload, invite, visit), introducing a standardized roles section, updating top bar labels, and refining error messages and user interface text.

Changes

File Path Change Summary
src/core/i18n/*/translation.*.json - Added new buttons: "upload", "invite", "visit", "notifications"
- Renamed topbar to topBar
- Added comprehensive roles section with multiple role definitions
- Updated release notes and error messages

Suggested labels

client, enhancement, UX

Suggested reviewers

  • bobbykolev
  • ccanos

Possibly related PRs


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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. (Beta)
  • @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.

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.

@hero101 hero101 closed this Jan 30, 2025
@hero101 hero101 deleted the develop_translations branch January 30, 2025 15:32
Copy link

@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: 37

🔭 Outside diff range comments (7)
src/core/i18n/ua/translation.ua.json (2)

Line range hint 125-177: Some button translations are missing Ukrainian localization.

The following keys still have English text and should be translated to Ukrainian:

  • "upload": "Upload"
  • "notifications": "Notifications Button"
  • "invite": "Invite"
  • "visit": "Visit"

Translation inconsistencies found in Ukrainian localization file

The following translation issues were identified:

  • Key platform terms "Space" and "Subspace" are left untranslated in multiple places
  • "Community" is inconsistently translated - sometimes as "Спільнота", sometimes left in English
  • Base terms in common section ("space", "spaces", "subspace", "subspaces") need Ukrainian translations
🔗 Analysis chain

Line range hint 1-3204: Verify translation consistency across the file.

There are several instances where similar terms are translated differently throughout the file. For example:

  • "Space" is sometimes translated and sometimes left in English
  • "Community" has different translations in different contexts

Run this script to find inconsistent translations:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Find inconsistent translations for key terms
echo "Checking 'Space' translations..."
rg -i "space.*:" -A 1
echo "Checking 'Community' translations..."
rg -i "community.*:" -A 1

Length of output: 67111


Script:

#!/bin/bash
# Search for Space/Community translations in the Ukrainian translation file
echo "Checking Space translations..."
rg -A 1 '"space":|"Space":|"SPACE":' src/core/i18n/ua/translation.ua.json

echo -e "\nChecking Community translations..."
rg -A 1 '"community":|"Community":|"COMMUNITY":' src/core/i18n/ua/translation.ua.json

echo -e "\nChecking Subspace translations..."
rg -A 1 '"subspace":|"Subspace":|"SUBSPACE":' src/core/i18n/ua/translation.ua.json

Length of output: 2241

src/core/i18n/es/translation.es.json (1)

Line range hint 125-177: Translate new button labels to Spanish.

The following button labels are in English and should be translated to Spanish for consistency:

  • "upload" → "Subir"
  • "notifications" → "Notificaciones"
  • "invite" → "Invitar"
  • "visit" → "Visitar"
-    "upload": "Upload",
+    "upload": "Subir",
-    "notifications": "Notifications Button",
+    "notifications": "Botón de notificaciones",
-    "invite": "Invite",
+    "invite": "Invitar",
-    "visit": "Visit"
+    "visit": "Visitar"
src/core/i18n/pt/translation.pt.json (1)

Line range hint 743-782: Translate remaining English text to Portuguese.

Several other strings need translation, including but not limited to:

  1. Subspace fields (lines 743-782):
- "description": "",
+ "description": "Descrição do subspace",

- "defaultTemplate": "Default Alkemio template for subspaces"
+ "defaultTemplate": "Template padrão do Alkemio para subespaços"
  1. Virtual Contributor settings (lines 2710-2724):
- "title": "Body of Knowledge",
+ "title": "Base de Conhecimento",

- "infoText": "By clicking the button below, you will make sure your Virtual Contributor is based on the latest knowledge in the Subspace.",
+ "infoText": "Ao clicar no botão abaixo, você garantirá que seu Contribuidor Virtual esteja baseado no conhecimento mais recente do Subespaço.",

- "refreshBtn": "Update Knowledge"
+ "refreshBtn": "Atualizar Conhecimento"

Also applies to: 2710-2724

src/core/i18n/de/translation.de.json (2)

Line range hint 125-177: New button translations need review.

Several new button translations are missing German translations and remain in English:

  • "upload" (line 125)
  • "notifications" (line 175)
  • "invite" (line 176)
  • "visit" (line 177)
  "buttons": {
-   "upload": "Upload",
+   "upload": "Hochladen",
    ...
-   "notifications": "Notifications Button",
+   "notifications": "Benachrichtigungen",
-   "invite": "Invite",
+   "invite": "Einladen",
-   "visit": "Visit"
+   "visit": "Besuchen"
  },

Line range hint 743-782: Subspace context fields need descriptions.

Several subspace context fields have empty descriptions that should be filled with appropriate German text.

      "displayName": {
        "title": "Title",
-       "description": "",
+       "description": "Versuchen Sie, es kurz, beschreibend und ansprechend zu halten",
        "placeholder": ""
      },
      "tagline": {
        "title": "Subspace Statement",
-       "description": "",
+       "description": "Erklären Sie in einem Satz, worum es bei diesem Subspace geht",
        "placeholder": ""
      },
      "background": {
        "title": "Current Reality",
-       "description": "",
+       "description": "Geben Sie einen kurzen Überblick darüber, wie dieser Subspace identifiziert wurde",
        "placeholder": ""
      },
      "tags": {
        "title": "Tags",
-       "description": "",
+       "description": "Geben Sie Schlüsselwörter ein, die für Ihren Subspace wichtig sind",
-       "placeholder": "",
+       "placeholder": "Geben Sie Tags ein...",
        "tooltip": "Tags"
      },
src/core/i18n/fr/translation.fr.json (1)

Line range hint 125-177: Translate English button labels to French for consistency.

Several button labels are kept in English, which is inconsistent with other translated buttons in the file. Consider using these French translations:

-    "upload": "Upload",
+    "upload": "Télécharger",
-    "notifications": "Notifications Button",
+    "notifications": "Bouton de notifications",
-    "invite": "Invite",
+    "invite": "Inviter",
-    "visit": "Visit"
+    "visit": "Visiter"
🧹 Nitpick comments (3)
src/core/i18n/nl/translation.nl.json (3)

535-543: Community guidelines messages need standardization

The success message uses "met succes" while other messages use "succesvol". Let's standardize this for consistency.

-      "saveAndDeleteContentSuccessMessage": "Community richtlijnen inhoud met succes verwijderd en opgeslagen.",
+      "saveAndDeleteContentSuccessMessage": "Community richtlijnen inhoud succesvol verwijderd en opgeslagen.",

2200-2200: Improve HTML list formatting in caption text

The HTML list in the caption text should have proper spacing for better readability in the source code.

-      "caption": "Ontdek een gevarieerd scala aan Spaces wachtend op jouw verkenning. Of je nu een ervaren lid bent of een nieuwsgierig nieuwkomer, er is hier iets voor iedereen. Laten we ons verdiepen in de details:<ol><li><strong>Leden Spaces:</strong> Dit zijn ruimtes waar je lidmaatschap al heeft.</li><li><strong>Openbare ruimten:</strong> Deze ruimten hebben zichtbare inhoud, en u kunt vragen om toe te treden.</li><li><strong>Alle ruimten:</strong> Deze categorie bevat zowel openbare als privé ruimtes. In privéruimten is alleen beperkte inhoud zichtbaar, maar u kunt nog steeds een lidmaatschap aanvragen.</li></ol>",
+      "caption": "Ontdek een gevarieerd scala aan Spaces wachtend op jouw verkenning. Of je nu een ervaren lid bent of een nieuwsgierig nieuwkomer, er is hier iets voor iedereen. Laten we ons verdiepen in de details:
+        <ol>
+          <li><strong>Leden Spaces:</strong> Dit zijn ruimtes waar je lidmaatschap al heeft.</li>
+          <li><strong>Openbare ruimten:</strong> Deze ruimten hebben zichtbare inhoud, en u kunt vragen om toe te treden.</li>
+          <li><strong>Alle ruimten:</strong> Deze categorie bevat zowel openbare als privé ruimtes. In privéruimten is alleen beperkte inhoud zichtbaar, maar u kunt nog steeds een lidmaatschap aanvragen.</li>
+        </ol>",

2909-2944: Redundant tag definitions in spaces filter config

The tag arrays contain duplicate values. Each tag is listed twice with the same value.

        "tags": [
-          "Energie Transitie",
-          "Energietransitie"
+          "Energie Transitie"
        ]

Apply similar changes to other tag arrays in the config.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c1ae78b and bbff33a.

📒 Files selected for processing (7)
  • src/core/i18n/bg/translation.bg.json (43 hunks)
  • src/core/i18n/de/translation.de.json (43 hunks)
  • src/core/i18n/es/translation.es.json (42 hunks)
  • src/core/i18n/fr/translation.fr.json (42 hunks)
  • src/core/i18n/nl/translation.nl.json (66 hunks)
  • src/core/i18n/pt/translation.pt.json (42 hunks)
  • src/core/i18n/ua/translation.ua.json (42 hunks)
🧰 Additional context used
📓 Path-based instructions (7)
src/core/i18n/bg/translation.bg.json (1)

Pattern src/**/*.json: Review the JSON files for correct syntax and structure.
Ensure that the configuration and data are accurate and follow the project's standards.
Check for sensitive data exposure and ensure that the data is properly validated.

src/core/i18n/pt/translation.pt.json (1)

Pattern src/**/*.json: Review the JSON files for correct syntax and structure.
Ensure that the configuration and data are accurate and follow the project's standards.
Check for sensitive data exposure and ensure that the data is properly validated.

src/core/i18n/ua/translation.ua.json (1)

Pattern src/**/*.json: Review the JSON files for correct syntax and structure.
Ensure that the configuration and data are accurate and follow the project's standards.
Check for sensitive data exposure and ensure that the data is properly validated.

src/core/i18n/es/translation.es.json (1)

Pattern src/**/*.json: Review the JSON files for correct syntax and structure.
Ensure that the configuration and data are accurate and follow the project's standards.
Check for sensitive data exposure and ensure that the data is properly validated.

src/core/i18n/fr/translation.fr.json (1)

Pattern src/**/*.json: Review the JSON files for correct syntax and structure.
Ensure that the configuration and data are accurate and follow the project's standards.
Check for sensitive data exposure and ensure that the data is properly validated.

src/core/i18n/nl/translation.nl.json (1)

Pattern src/**/*.json: Review the JSON files for correct syntax and structure.
Ensure that the configuration and data are accurate and follow the project's standards.
Check for sensitive data exposure and ensure that the data is properly validated.

src/core/i18n/de/translation.de.json (1)

Pattern src/**/*.json: Review the JSON files for correct syntax and structure.
Ensure that the configuration and data are accurate and follow the project's standards.
Check for sensitive data exposure and ensure that the data is properly validated.

🔇 Additional comments (15)
src/core/i18n/bg/translation.bg.json (10)

36-36: LGTM! Well-structured translation with preserved tags.

The translation maintains proper formatting and preserves all necessary HTML-like tags while conveying the message accurately in Bulgarian.


183-185: LGTM! Improved key naming consistency.

The rename from "topbar" to "topBar" improves consistency with camelCase formatting across the translation files.


450-464: LGTM! Well-structured roles section with proper translation references.

The new roles section is properly implemented with:

  • Consistent use of translation references
  • Complete coverage of platform roles
  • Proper structure and formatting

535-543: LGTM! Clear and well-structured community guidelines messages.

The new community guidelines messages are properly implemented with consistent formatting and clear key naming.


1662-1686: LGTM! Well-implemented notifications system with proper formatting.

The new in-app notifications section is properly implemented with:

  • Preserved HTML formatting
  • Correct placeholder usage
  • Clear message structure for different notification types

1748-1753: LGTM! Well-structured subEntities section with proper markdown formatting.

The translations maintain proper markdown formatting and provide clear, consistent messages.


2710-2724: LGTM! Well-implemented Virtual Contributors settings section.

The translations provide clear messages and maintain consistency throughout the settings and privacy sections.


2909-2944: LGTM! Well-structured space filter tags.

The space filter tags are properly implemented with consistent translations across multiple languages.


3132-3139: LGTM! Well-implemented document handling section.

The translations provide clear information about supported file formats and size limits while maintaining consistent structure.


Line range hint 125-177: Verify if "upload" should be translated to Bulgarian.

While "invite" and "visit" were added, "upload" remains in English. Consider translating it to Bulgarian for consistency with other button translations.

src/core/i18n/nl/translation.nl.json (5)

125-125: New button translations look good!

The new button translations are consistent with the platform's terminology and correctly translated to Dutch:

  • "upload": "Upload"
  • "notifications": "Notificatie Knop"
  • "invite": "Nodig uit"
  • "visit": "Bezoek"

Also applies to: 175-177


183-185: Consistent key naming convention update

The key rename from "topbar" to "topBar" follows camelCase convention, improving consistency.


450-464: Comprehensive roles section with accurate translations

The new roles section provides clear Dutch translations for all platform roles, including administrative roles like GLOBAL_ADMIN and specialized roles like PLATFORM_BETA_TESTER.


1050-1061: Virtual Contributors dialog translations are complete

The translations for the Virtual Contributors invite dialog are comprehensive and maintain consistent terminology.


1662-1686: In-app notifications translations are complete and accurate

The translations for in-app notifications cover all notification types and maintain consistent terminology.

Comment on lines +450 to +464
"roles": {
"ADMIN": "$t(common.admin)",
"LEAD": "$t(common.lead)",
"HOST": "$t(common.host)",
"MEMBER": "$t(common.member)",
"ASSOCIATE": "Associate",
"OWNER": "Owner",
"GLOBAL_ADMIN": "Global Admin",
"GLOBAL_SUPPORT": "Support Admin",
"GLOBAL_LICENSE_MANAGER": "License Manager",
"GLOBAL_COMMUNITY_READER": "Community Manager",
"GLOBAL_SPACES_READER": "Spaces Reader",
"PLATFORM_BETA_TESTER": "Beta Tester",
"PLATFORM_VC_CAMPAIGN": "VC Early Access"
},
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Roles section contains untranslated values.

Several role names are left in English and should be translated to Ukrainian:

  • "ASSOCIATE": "Associate"
  • "OWNER": "Owner"
  • "GLOBAL_ADMIN": "Global Admin"
  • "GLOBAL_SUPPORT": "Support Admin"
  • "GLOBAL_LICENSE_MANAGER": "License Manager"
  • "GLOBAL_COMMUNITY_READER": "Community Manager"
  • "GLOBAL_SPACES_READER": "Spaces Reader"
  • "PLATFORM_BETA_TESTER": "Beta Tester"
  • "PLATFORM_VC_CAMPAIGN": "VC Early Access"

Comment on lines +1662 to +1686
"inAppNotifications": {
"action": {
"read": "Mark as read",
"unread": "Mark as unread",
"delete": "Delete Notification"
},
"type": {
"COLLABORATION_CALLOUT_PUBLISHED": {
"subject": "{{spaceName}} - New {{calloutType}} is published \"{{calloutName}}\", have a look!",
"description": "{{contributorName}} published a new {{calloutType}} in {{spaceType}}: {{spaceName}}, with name: {{calloutName}}."
},
"COMMUNICATION_USER_MENTION": {
"subject": "{{commenterName}} mentioned you in a comment on {{calloutName}}:",
"description": ""
},
"COMMUNITY_NEW_MEMBER": {
"subject": "{{spaceName}} - Welcome to the Community!",
"description": "Thank you for joining {{spaceName}}!<br /> You can now start contributing to the various posts and whiteboards, further deepen your knowledge about this topic, and connect with other Contributors."
},
"COMMUNITY_NEW_MEMBER_ADMIN": {
"subject": "{{memberType}} \"{{memberName}}\" joined {{spaceName}}",
"description": "The {{memberType}} {{memberName}} has joined {{spaceName}}, of which you are an admin."
}
},
"emptyInbox": "No pending notifications"
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

In-app notifications section needs Ukrainian translations.

The entire notifications section is in English and should be translated to Ukrainian:

  • Action texts ("Mark as read", "Mark as unread", "Delete Notification")
  • Notification types and their subjects/descriptions

Comment on lines +2020 to +2022
"private": "<b>Private:</b> This space is visible to everyone on the platform, but the content is only visible to members. Please note that both the information in the profile and the context are publicly visible.",
"publicSubspace": "<b>Public:</b> This Subspace and all its contents are visible to everyone who has access to the Space it belongs to. If the Space itself is public, this Subspace and its contents will be visible to all users, including those outside the Space.",
"privateSubspace": "<b>Private:</b> This Subspace is visible to all members of the Space, but its contents are restricted and can only be accessed by members of the Subspace. No application required: All Space members can directly join, without you having to review their application."
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Visibility settings need Ukrainian translations.

The visibility descriptions are in English and should be translated to Ukrainian:

  • Private/Public space descriptions
  • Private/Public subspace descriptions

Comment on lines +3192 to +3204
"chooseCommunity": {
"title": "Hello, {{vcName}}!",
"description": "Your Virtual Contributor is ready! To start interacting, your Virtual Contributor should be added to a Space. Select one below, or continue without. In that case you will have to add the VC manually through the Community tab of a Space.",
"label": "Space",
"selectSpacesPlaceholder": "Select a Space",
"noSpacesPlaceholder": "No Spaces available",
"cancelAddToCommunity": "Proceed without membership",
"addToCommunity": "Add and go to Space",
"createAndAddToCommunity": "Create, add, and go to Space",
"confirm": {
"title": "Continue without Space membership",
"description": "A Virtual Contributor can only interact within a Space. Are you sure you want to proceed without adding them to a Space? You can still invite the Virtual Contributor later through the Space’s Community tab."
}
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Choose community section requires Ukrainian translations.

The entire section for choosing community is in English and should be translated to Ukrainian, including:

  • Titles and descriptions
  • Placeholders and button texts
  • Confirmation dialog content

Comment on lines +183 to +184
"topBar": {
"sign-in": "Log In | Sign Up"
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Inconsistent translation for sign-in text.

The "sign-in" key under "topBar" is in English while other authentication-related texts are in Ukrainian.

-    "sign-in": "Log In | Sign Up"
+    "sign-in": "Увійти | Зареєструватись"
📝 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
"topBar": {
"sign-in": "Log In | Sign Up"
"topBar": {
"sign-in": "Увійти | Зареєструватись"

Comment on lines +535 to +543
"saveAndDeleteContentSuccessMessage": "Community guidelines content removed and saved successfully.",
"updatedSuccessfully": "Community guidelines updated successfully.",
"adminsOnly": "Since there are no Community Guidelines specified, this block is only visible for admins and leads.",
"communityGuidelinesRedirect": "Click here to update the Community Guidelines in the Space settings.",
"confirmationDialog": {
"title": "Updating Community Guidelines",
"description": "Are you sure you want to replace your existing Community Guidelines? This action cannot be undone."
}
},
"deleteCommunityGuidelines": "Delete Community Guidelines"
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Translate community guidelines messages to French.

Community guidelines messages are in English and should be translated to French.

-      "saveAndDeleteContentSuccessMessage": "Community guidelines content removed and saved successfully.",
+      "saveAndDeleteContentSuccessMessage": "Le contenu des directives communautaires a été supprimé et enregistré avec succès.",
-      "updatedSuccessfully": "Community guidelines updated successfully.",
+      "updatedSuccessfully": "Les directives communautaires ont été mises à jour avec succès.",
-      "adminsOnly": "Since there are no Community Guidelines specified, this block is only visible for admins and leads.",
+      "adminsOnly": "Comme aucune directive communautaire n'est spécifiée, ce bloc n'est visible que pour les administrateurs et les responsables.",
-      "communityGuidelinesRedirect": "Click here to update the Community Guidelines in the Space settings.",
+      "communityGuidelinesRedirect": "Cliquez ici pour mettre à jour les directives communautaires dans les paramètres de l'espace.",
-      "title": "Remove Community Guidelines Content",
+      "title": "Supprimer le contenu des directives communautaires",
-      "content": "Are you sure you want to remove the Community Guidelines? This action cannot be undone."
+      "content": "Êtes-vous sûr de vouloir supprimer les directives communautaires ? Cette action ne peut pas être annulée."

Also applies to: 606-608

Comment on lines +183 to +184
"topBar": {
"sign-in": "Log In | Sign Up"
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Restore French translation for sign-in text.

The sign-in text was changed to English, breaking the localization consistency.

-    "sign-in": "Log In | Sign Up"
+    "sign-in": "Connexion | Inscription"
📝 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
"topBar": {
"sign-in": "Log In | Sign Up"
"topBar": {
"sign-in": "Connexion | Inscription"

Comment on lines +450 to +464
"roles": {
"ADMIN": "$t(common.admin)",
"LEAD": "$t(common.lead)",
"HOST": "$t(common.host)",
"MEMBER": "$t(common.member)",
"ASSOCIATE": "Associate",
"OWNER": "Owner",
"GLOBAL_ADMIN": "Global Admin",
"GLOBAL_SUPPORT": "Support Admin",
"GLOBAL_LICENSE_MANAGER": "License Manager",
"GLOBAL_COMMUNITY_READER": "Community Manager",
"GLOBAL_SPACES_READER": "Spaces Reader",
"PLATFORM_BETA_TESTER": "Beta Tester",
"PLATFORM_VC_CAMPAIGN": "VC Early Access"
},
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Translate role names to French for consistency.

Role names should be translated to French to maintain localization consistency.

-      "ASSOCIATE": "Associate",
+      "ASSOCIATE": "Associé",
-      "OWNER": "Owner",
+      "OWNER": "Propriétaire",
-      "GLOBAL_ADMIN": "Global Admin",
+      "GLOBAL_ADMIN": "Administrateur global",
-      "GLOBAL_SUPPORT": "Support Admin",
+      "GLOBAL_SUPPORT": "Administrateur du support",
-      "GLOBAL_LICENSE_MANAGER": "License Manager",
+      "GLOBAL_LICENSE_MANAGER": "Gestionnaire de licences",
-      "GLOBAL_COMMUNITY_READER": "Community Manager",
+      "GLOBAL_COMMUNITY_READER": "Gestionnaire de communauté",
-      "GLOBAL_SPACES_READER": "Spaces Reader",
+      "GLOBAL_SPACES_READER": "Lecteur d'espaces",
-      "PLATFORM_BETA_TESTER": "Beta Tester",
+      "PLATFORM_BETA_TESTER": "Testeur bêta",
-      "PLATFORM_VC_CAMPAIGN": "VC Early Access"
+      "PLATFORM_VC_CAMPAIGN": "Accès anticipé VC"
📝 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
"roles": {
"ADMIN": "$t(common.admin)",
"LEAD": "$t(common.lead)",
"HOST": "$t(common.host)",
"MEMBER": "$t(common.member)",
"ASSOCIATE": "Associate",
"OWNER": "Owner",
"GLOBAL_ADMIN": "Global Admin",
"GLOBAL_SUPPORT": "Support Admin",
"GLOBAL_LICENSE_MANAGER": "License Manager",
"GLOBAL_COMMUNITY_READER": "Community Manager",
"GLOBAL_SPACES_READER": "Spaces Reader",
"PLATFORM_BETA_TESTER": "Beta Tester",
"PLATFORM_VC_CAMPAIGN": "VC Early Access"
},
"roles": {
"ADMIN": "$t(common.admin)",
"LEAD": "$t(common.lead)",
"HOST": "$t(common.host)",
"MEMBER": "$t(common.member)",
"ASSOCIATE": "Associé",
"OWNER": "Propriétaire",
"GLOBAL_ADMIN": "Administrateur global",
"GLOBAL_SUPPORT": "Administrateur du support",
"GLOBAL_LICENSE_MANAGER": "Gestionnaire de licences",
"GLOBAL_COMMUNITY_READER": "Gestionnaire de communauté",
"GLOBAL_SPACES_READER": "Lecteur d'espaces",
"PLATFORM_BETA_TESTER": "Testeur bêta",
"PLATFORM_VC_CAMPAIGN": "Accès anticipé VC"
},

Comment on lines +1662 to +1686
"inAppNotifications": {
"action": {
"read": "Mark as read",
"unread": "Mark as unread",
"delete": "Delete Notification"
},
"type": {
"COLLABORATION_CALLOUT_PUBLISHED": {
"subject": "{{spaceName}} - New {{calloutType}} is published \"{{calloutName}}\", have a look!",
"description": "{{contributorName}} published a new {{calloutType}} in {{spaceType}}: {{spaceName}}, with name: {{calloutName}}."
},
"COMMUNICATION_USER_MENTION": {
"subject": "{{commenterName}} mentioned you in a comment on {{calloutName}}:",
"description": ""
},
"COMMUNITY_NEW_MEMBER": {
"subject": "{{spaceName}} - Welcome to the Community!",
"description": "Thank you for joining {{spaceName}}!<br /> You can now start contributing to the various posts and whiteboards, further deepen your knowledge about this topic, and connect with other Contributors."
},
"COMMUNITY_NEW_MEMBER_ADMIN": {
"subject": "{{memberType}} \"{{memberName}}\" joined {{spaceName}}",
"description": "The {{memberType}} {{memberName}} has joined {{spaceName}}, of which you are an admin."
}
},
"emptyInbox": "No pending notifications"
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Translate notification messages to French.

Notification messages are in English and should be translated to French.

-      "read": "Mark as read",
+      "read": "Marquer comme lu",
-      "unread": "Mark as unread",
+      "unread": "Marquer comme non lu",
-      "delete": "Delete Notification"
+      "delete": "Supprimer la notification"
-          "subject": "{{spaceName}} - New {{calloutType}} is published \"{{calloutName}}\", have a look!",
+          "subject": "{{spaceName}} - Nouveau {{calloutType}} publié \"{{calloutName}}\", jetez un coup d'œil !",
-          "description": "{{contributorName}} published a new {{calloutType}} in {{spaceType}}: {{spaceName}}, with name: {{calloutName}}."
+          "description": "{{contributorName}} a publié un nouveau {{calloutType}} dans {{spaceType}} : {{spaceName}}, avec le nom : {{calloutName}}."
-          "subject": "{{commenterName}} mentioned you in a comment on {{calloutName}}:",
+          "subject": "{{commenterName}} vous a mentionné dans un commentaire sur {{calloutName}} :",
-          "subject": "{{spaceName}} - Welcome to the Community!",
+          "subject": "{{spaceName}} - Bienvenue dans la communauté !",
-          "description": "Thank you for joining {{spaceName}}!<br /> You can now start contributing to the various posts and whiteboards, further deepen your knowledge about this topic, and connect with other Contributors."
+          "description": "Merci d'avoir rejoint {{spaceName}} !<br /> Vous pouvez maintenant commencer à contribuer aux différentes publications et tableaux blancs, approfondir vos connaissances sur ce sujet et vous connecter avec d'autres contributeurs."
-          "subject": "{{memberType}} \"{{memberName}}\" joined {{spaceName}}",
+          "subject": "{{memberType}} \"{{memberName}}\" a rejoint {{spaceName}}",
-          "description": "The {{memberType}} {{memberName}} has joined {{spaceName}}, of which you are an admin."
+          "description": "Le {{memberType}} {{memberName}} a rejoint {{spaceName}}, dont vous êtes administrateur."
-      "emptyInbox": "No pending notifications"
+      "emptyInbox": "Aucune notification en attente"
📝 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
"inAppNotifications": {
"action": {
"read": "Mark as read",
"unread": "Mark as unread",
"delete": "Delete Notification"
},
"type": {
"COLLABORATION_CALLOUT_PUBLISHED": {
"subject": "{{spaceName}} - New {{calloutType}} is published \"{{calloutName}}\", have a look!",
"description": "{{contributorName}} published a new {{calloutType}} in {{spaceType}}: {{spaceName}}, with name: {{calloutName}}."
},
"COMMUNICATION_USER_MENTION": {
"subject": "{{commenterName}} mentioned you in a comment on {{calloutName}}:",
"description": ""
},
"COMMUNITY_NEW_MEMBER": {
"subject": "{{spaceName}} - Welcome to the Community!",
"description": "Thank you for joining {{spaceName}}!<br /> You can now start contributing to the various posts and whiteboards, further deepen your knowledge about this topic, and connect with other Contributors."
},
"COMMUNITY_NEW_MEMBER_ADMIN": {
"subject": "{{memberType}} \"{{memberName}}\" joined {{spaceName}}",
"description": "The {{memberType}} {{memberName}} has joined {{spaceName}}, of which you are an admin."
}
},
"emptyInbox": "No pending notifications"
"inAppNotifications": {
"action": {
"read": "Marquer comme lu",
"unread": "Marquer comme non lu",
"delete": "Supprimer la notification"
},
"type": {
"COLLABORATION_CALLOUT_PUBLISHED": {
"subject": "{{spaceName}} - Nouveau {{calloutType}} publié \"{{calloutName}}\", jetez un coup d'œil !",
"description": "{{contributorName}} a publié un nouveau {{calloutType}} dans {{spaceType}} : {{spaceName}}, avec le nom : {{calloutName}}."
},
"COMMUNICATION_USER_MENTION": {
"subject": "{{commenterName}} vous a mentionné dans un commentaire sur {{calloutName}} :",
"description": ""
},
"COMMUNITY_NEW_MEMBER": {
"subject": "{{spaceName}} - Bienvenue dans la communauté !",
"description": "Merci d'avoir rejoint {{spaceName}} !<br /> Vous pouvez maintenant commencer à contribuer aux différentes publications et tableaux blancs, approfondir vos connaissances sur ce sujet et vous connecter avec d'autres contributeurs."
},
"COMMUNITY_NEW_MEMBER_ADMIN": {
"subject": "{{memberType}} \"{{memberName}}\" a rejoint {{spaceName}}",
"description": "Le {{memberType}} {{memberName}} a rejoint {{spaceName}}, dont vous êtes administrateur."
}
},
"emptyInbox": "Aucune notification en attente"

Comment on lines +2710 to +2724
"title": "Body of Knowledge",
"infoText": "By clicking the button below, you will make sure your Virtual Contributor is based on the latest knowledge in the Subspace.",
"refreshBtn": "Update Knowledge"
},
"privacy": {
"title": "Privacy",
"description": "Private Virtual Contributor Knowledge",
"tooltip1": "Public: When users visit {{vcName}}'s profile, they can see the content of its body of knowledge.",
"tooltip2": "Private: Only the account admins can see the content of the body of knowledge."
}
},
"knowledgeBase": {
"noAccess": {
"title": "Private Virtual Contributor Knowledge",
"description": "You don't have access to the knowledge base of this Virtual Contributor. Please contact the owner of the Virtual Contributor for more information."
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Translate Virtual Contributors settings to French.

Virtual Contributors settings messages are in English and should be translated to French.

-          "title": "Body of Knowledge",
+          "title": "Base de connaissances",
-          "infoText": "By clicking the button below, you will make sure your Virtual Contributor is based on the latest knowledge in the Subspace.",
+          "infoText": "En cliquant sur le bouton ci-dessous, vous vous assurez que votre contributeur virtuel est basé sur les dernières connaissances de l'espace.",
-          "refreshBtn": "Update Knowledge"
+          "refreshBtn": "Mettre à jour les connaissances"
-          "title": "Privacy",
+          "title": "Confidentialité",
-          "description": "Private Virtual Contributor Knowledge",
+          "description": "Connaissances privées du contributeur virtuel",
-          "tooltip1": "Public: When users visit {{vcName}}'s profile, they can see the content of its body of knowledge.",
+          "tooltip1": "Public : Lorsque les utilisateurs visitent le profil de {{vcName}}, ils peuvent voir le contenu de sa base de connaissances.",
-          "tooltip2": "Private: Only the account admins can see the content of the body of knowledge."
+          "tooltip2": "Privé : Seuls les administrateurs du compte peuvent voir le contenu de la base de connaissances."
-          "title": "Private Virtual Contributor Knowledge",
+          "title": "Connaissances privées du contributeur virtuel",
-          "description": "You don't have access to the knowledge base of this Virtual Contributor. Please contact the owner of the Virtual Contributor for more information."
+          "description": "Vous n'avez pas accès à la base de connaissances de ce contributeur virtuel. Veuillez contacter le propriétaire du contributeur virtuel pour plus d'informations."
📝 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
"title": "Body of Knowledge",
"infoText": "By clicking the button below, you will make sure your Virtual Contributor is based on the latest knowledge in the Subspace.",
"refreshBtn": "Update Knowledge"
},
"privacy": {
"title": "Privacy",
"description": "Private Virtual Contributor Knowledge",
"tooltip1": "Public: When users visit {{vcName}}'s profile, they can see the content of its body of knowledge.",
"tooltip2": "Private: Only the account admins can see the content of the body of knowledge."
}
},
"knowledgeBase": {
"noAccess": {
"title": "Private Virtual Contributor Knowledge",
"description": "You don't have access to the knowledge base of this Virtual Contributor. Please contact the owner of the Virtual Contributor for more information."
"title": "Base de connaissances",
"infoText": "En cliquant sur le bouton ci-dessous, vous vous assurez que votre contributeur virtuel est basé sur les dernières connaissances de l'espace.",
"refreshBtn": "Mettre à jour les connaissances"
},
"privacy": {
"title": "Confidentialité",
"description": "Connaissances privées du contributeur virtuel",
"tooltip1": "Public : Lorsque les utilisateurs visitent le profil de {{vcName}}, ils peuvent voir le contenu de sa base de connaissances.",
"tooltip2": "Privé : Seuls les administrateurs du compte peuvent voir le contenu de la base de connaissances."
}
},
"knowledgeBase": {
"noAccess": {
"title": "Connaissances privées du contributeur virtuel",
"description": "Vous n'avez pas accès à la base de connaissances de ce contributeur virtuel. Veuillez contacter le propriétaire du contributeur virtuel pour plus d'informations."

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.

1 participant