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 #1367

Merged
merged 6 commits into from
Oct 1, 2024
Merged

🌐 New Crowdin updates #1367

merged 6 commits into from
Oct 1, 2024

Conversation

lukevella
Copy link
Owner

@lukevella lukevella commented Sep 30, 2024

Summary by CodeRabbit

  • New Features

    • Enhanced Danish localization with new entries for meeting polls and user statistics.
    • Added pricing information to clarify subscription options.
    • Improved German localization with new entries for meeting polls and user statistics.
  • Bug Fixes

    • Confirmed existing keys for better consistency in localization.

Copy link

vercel bot commented Sep 30, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
app ⬜️ Ignored (Inspect) Visit Preview Oct 1, 2024 8:40am
landing ⬜️ Ignored (Inspect) Visit Preview Oct 1, 2024 8:40am

Copy link
Contributor

coderabbitai bot commented Sep 30, 2024

Walkthrough

The pull request introduces several enhancements to the localization files for both Danish and German languages. Key additions include new strings for meeting polls, user statistics, and pricing information, aimed at improving user experience and clarity. The overall structure of the JSON files remains intact, with no deletions or significant modifications to existing keys.

Changes

Files Change Summary
apps/landing/public/locales/da/common.json Added new key "meetingPoll": "Mødeafstemning" and confirmed existing key "when2MeetAlternative": "When2Meet alternativ."
apps/landing/public/locales/da/home.json Introduced new strings for user statistics, meeting polls, and expanded descriptions promoting Rallly.
apps/landing/public/locales/da/pricing.json Added new keys "pricingTitle": "Kom i gang gratis" and "pricingSubtitle": "Opgrader til et abonnement for at få adgang til premium-funktioner."
apps/landing/public/locales/de/common.json Added new key "meetingPoll": "Meetingumfrage" and confirmed existing key "when2MeetAlternative": "When2Meet Alternative."
apps/landing/public/locales/de/home.json Introduced new strings for user statistics, meeting polls, and updated descriptions emphasizing Rallly.
apps/landing/public/locales/de/pricing.json Added new keys "pricingTitle" and "pricingSubtitle" to enhance pricing information clarity.

Possibly related PRs

  • 🌐 New Crowdin updates #1348: Adds the key "when2MeetAlternative": "When2Meet alternatíva" in Hungarian localization, related to the Danish changes.
  • 🌐 New Crowdin updates #1347: Introduces the key "when2MeetAlternative": "When2Meet Alternative" in English localization, aligning with the Danish addition.
  • 🌐 New Crowdin updates #1243: Includes the addition of the "meetingPoll" key in Danish localization, which is also a focus of the main PR.
  • 🌐 New Crowdin updates #1163: Adds the "meetingPoll" key in English localization, corresponding to the Danish changes.
  • 🌐 New Crowdin updates #1219: Introduces the "meetingPoll" key in Swedish localization, relevant to the Danish localization updates.
  • 🌐 New Crowdin updates #1176: Includes changes to the German localization files that add new keys related to meeting scheduling, which ties back to the main PR's focus on enhancing the "meetingPoll" feature.
  • 🌐 New Crowdin updates #1152: This PR adds new keys related to meeting polls in the French localization, which is directly relevant to the main PR's updates.

Poem

🐰 In the land of code where rabbits play,
New keys have hopped in, brightening the day!
Mødeafstemning leads the way,
With stats and pricing, come join the fray!
Rallly's charm, oh what a delight,
Let's gather 'round, and plan our next flight! 🌼


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 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: 0

🧹 Outside diff range and nitpick comments (2)
apps/landing/public/locales/da/home.json (2)

42-43: LGTM with suggestion: New meta title and description for meeting polls.

The new meta title and description for meeting polls are well-translated and SEO-friendly. They effectively convey the purpose and benefit of Rallly's meeting polls.

Consider enhancing the meta description to include a unique selling point or more specific benefit of using Rallly for meeting polls. For example:

- "meetingPollMetaDescription": "Planlæg nemt møder med vores meningsmåling, hvilket sikrer alles tilgængelighed."
+ "meetingPollMetaDescription": "Planlæg nemt møder med vores professionelle og reklamefri meningsmåling, hvilket sikrer alles tilgængelighed og sparer tid."

This change would highlight Rallly's unique features (professional and ad-free) and emphasize the time-saving aspect.


Line range hint 1-43: Overall assessment: Excellent improvements to Danish localization.

The changes in this file significantly enhance the Danish localization of Rallly's landing page. The additions include:

  1. New user statistics strings
  2. Updated description for When2Meet alternative
  3. New strings for meeting poll creation
  4. New meta title and description for meeting polls

These changes provide more comprehensive information about Rallly's features and benefits, improving the user experience for Danish-speaking users. The translations are accurate, natural-sounding, and consistent with the existing content and style.

To ensure consistency across all localized versions, consider implementing a process to synchronize key features and selling points across all language files when making significant updates like these.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between d05fff6 and 7ac9081.

📒 Files selected for processing (3)
  • apps/landing/public/locales/da/common.json (1 hunks)
  • apps/landing/public/locales/da/home.json (2 hunks)
  • apps/landing/public/locales/da/pricing.json (1 hunks)
🔇 Additional comments (8)
apps/landing/public/locales/da/common.json (1)

27-28: LGTM! Translation update looks good.

The changes to the Danish localization file are consistent with the existing format and appear to be correct. The new entry "meetingPoll": "Mødeafstemning" is an appropriate translation for "Meeting Poll" in Danish.

To ensure the highest quality of localization:

  1. If not already done, consider having a native Danish speaker verify the translation of "Mødeafstemning" for "meetingPoll".
  2. Run the following script to check for any inconsistencies in the JSON structure or missing translations compared to the English version:

This script will help identify any missing or extra keys in the Danish translation compared to the English version.

✅ Verification successful

Please run the following script to accurately compare the keys of the Danish and English localization files:


Verified: The Danish and English localization files have matching structures.

The comparison confirms that the Danish common.json file has the same keys as the English version. The new entry "meetingPoll": "Mødeafstemning" is appropriately added and matches the English counterpart.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Compare the structure of the Danish and English localization files

# Find the English version of the file
english_file=$(fd -e json -p "apps/landing/public/locales/en/common.json")

if [ -z "$english_file" ]; then
  echo "Error: English localization file not found."
  exit 1
fi

# Compare the keys of both files
diff <(jq -S 'keys' apps/landing/public/locales/da/common.json) <(jq -S 'keys' "$english_file")

# If there's no output, the structures are identical
if [ $? -eq 0 ]; then
  echo "The structure of the Danish and English files match."
else
  echo "There are differences in the structure or keys between the Danish and English files."
fi

Length of output: 601


Script:

#!/bin/bash
# Description: Compare the structure of the Danish and English localization files without using process substitution

# Define temporary files
da_keys=$(mktemp)
en_keys=$(mktemp)

# Cleanup temporary files on exit
trap 'rm -f "$da_keys" "$en_keys"' EXIT

# Extract and sort keys from the Danish file
jq -S 'keys' apps/landing/public/locales/da/common.json > "$da_keys"

# Find the English version of the file
english_file=$(fd -e json -p "apps/landing/public/locales/en/common.json")

if [ -z "$english_file" ]; then
  echo "Error: English localization file not found."
  exit 1
fi

# Extract and sort keys from the English file
jq -S 'keys' "$english_file" > "$en_keys"

# Compare the keys of both files
diff "$da_keys" "$en_keys" > /dev/null

# Check the result of the diff
if [ $? -eq 0 ]; then
  echo "The structure of the Danish and English files match."
else
  echo "There are differences in the structure or keys between the Danish and English files."
fi

Length of output: 635

apps/landing/public/locales/da/pricing.json (4)

31-31: LGTM: Existing translation retained.

The annualBenefit key and its translation have been correctly retained. The use of the {count} placeholder allows for dynamic content, which is good practice.


32-32: LGTM: New pricing title added.

The new pricingTitle key has been correctly added with an appropriate Danish translation. This addition enhances the clarity of the pricing information for Danish users.


33-33: LGTM: New pricing subtitle added.

The new pricingSubtitle key has been correctly added with an appropriate Danish translation. This addition provides clear information about the benefits of upgrading, which is valuable for Danish users considering a subscription.


31-33: Summary: Localization updates enhance pricing information.

These changes improve the Danish localization of the pricing page by adding a clear title and subtitle. The additions are consistent with the PR objectives and enhance the user experience for Danish-speaking users. The retained annualBenefit key ensures continuity with existing translations.

Overall, these updates contribute positively to the internationalization efforts of the application.

apps/landing/public/locales/da/home.json (3)

13-14: LGTM: New user statistics strings added correctly.

The new strings for user statistics (registered users and created polls) are well-formatted and consistent. They use appropriate placeholders for the count and the Danish translations accurately convey the intended meaning.


39-39: LGTM: Improved When2Meet alternative description.

The updated description for the When2Meet alternative is more specific and emphasizes key features of Rallly (professional, ad-free, free). This change better positions the product and provides clearer value proposition to potential users.


40-41: LGTM: New meeting poll strings added successfully.

The new strings for meeting poll creation ("meetingPoll" and "meetingPollDescription") are well-crafted and consistent with the product's messaging. They effectively communicate the ease of use and professional quality of Rallly's meeting polls. The Danish translations accurately convey the intended meanings.

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: 1

🧹 Outside diff range and nitpick comments (4)
apps/landing/public/locales/de/common.json (1)

27-28: LGTM! Consider a minor improvement.

The new translation "Meetingumfrage" for "Meeting Poll" is correct and consistent with the existing translations. The JSON structure remains valid.

Consider using a hyphen for better readability: "Meeting-Umfrage". This is a common practice in German for compound words, especially when combining a foreign word with a German word.

-  "meetingPoll": "Meetingumfrage"
+  "meetingPoll": "Meeting-Umfrage"
apps/landing/public/locales/de/pricing.json (2)

32-33: Approved: Clear and informative pricing header additions

The new pricingTitle and pricingSubtitle entries provide clear and concise information about the pricing structure. They effectively communicate the free start option and the availability of premium features in paid plans.

For consistency with other entries in the file, consider capitalizing the first letter of each value. Here's a suggested change:

-  "pricingTitle": "Starte kostenlos",
-  "pricingSubtitle": "Wechsle auf einen kostenpflichtigen Plan, um Zugriff auf Premiumfeatures zu erhalten"
+  "pricingTitle": "Starte kostenlos",
+  "pricingSubtitle": "Wechsle auf einen kostenpflichtigen Plan, um Zugriff auf Premiumfeatures zu erhalten"

This minor adjustment would align these new entries with the capitalization style used in other parts of the file.


Line range hint 1-33: Summary: Effective enhancements to pricing information

The changes to this file successfully improve the presentation of pricing information for German-speaking users. The new pricingTitle and pricingSubtitle entries provide a clear introduction to the pricing structure, emphasizing the free start option and the availability of premium features. These additions integrate well with the existing content and enhance the overall user experience.

To further improve the localization process:

  1. Consider implementing a linting tool for JSON files to ensure consistent formatting and capitalization across all language files.
  2. Establish a glossary of common terms used in pricing to maintain consistency across different languages and updates.
  3. Implement a review process that includes native speakers to verify the naturalness and accuracy of translations.
apps/landing/public/locales/de/home.json (1)

38-38: LGTM with a suggestion: Consider consistency in address forms.

The translation is accurate and engaging. However, there's an inconsistency in the use of formal ("Sie") vs. informal ("Du") address forms throughout the file. For example, line 39 uses "Sie" while this line uses "Du".

Consider standardizing the address form throughout the file for consistency. If you decide to use the informal "Du" form, you might want to update line 39 as well:

- "when2meetAlternativeDescription": "Erstellen Sie professionelle, werbefreie Meetingumfragen kostenlos mit Rallly.",
+ "when2meetAlternativeDescription": "Erstelle professionelle, werbefreie Meetingumfragen kostenlos mit Rallly.",
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 7ac9081 and a7a6030.

📒 Files selected for processing (3)
  • apps/landing/public/locales/de/common.json (1 hunks)
  • apps/landing/public/locales/de/home.json (2 hunks)
  • apps/landing/public/locales/de/pricing.json (1 hunks)
🔇 Additional comments (5)
apps/landing/public/locales/de/pricing.json (1)

31-31: LGTM: Appropriate annual benefit description

The annualBenefit key-value pair is well-structured and provides a clear description of the annual subscription benefit. The use of the {count} placeholder allows for flexibility in specifying the number of free months.

apps/landing/public/locales/de/home.json (4)

13-13: LGTM: Accurate translation for registered users statistic.

The translation is correct and appropriately uses the compact-short number format for concise display of large numbers.


14-14: LGTM: Accurate translation for polls created statistic.

The translation is correct and consistently uses the compact-short number format, maintaining coherence with the previous statistic.


40-40: LGTM: Clear and accurate translation for meeting poll creation.

The translation effectively conveys the message about creating professional meeting polls using Rallly.


Line range hint 13-42: Overall assessment: Valuable additions to the German localization.

The new entries enhance the user interface by adding statistics about registered users and created polls, introducing a comparison with When2Meet, and providing information about meeting polls. These additions improve the user experience for German-speaking users.

A few minor points to consider:

  1. Ensure consistency in the use of formal ("Sie") vs. informal ("Du") address forms throughout the file.
  2. Fix the repeated word "wunderbare" in the meetingPollDescription.

These changes will make the German localization more polished and professional.

"when2meetAlternative": "Du verwendest noch When2Meet?",
"when2meetAlternativeDescription": "Erstellen Sie professionelle, werbefreie Meetingumfragen kostenlos mit Rallly.",
"meetingPoll": "Erstelle professionelle Meetingumfragen mit Rallly",
"meetingPollDescription": "Meetingumfragen sind eine wunderbare Möglichkeit, die Verfügbarkeit von Menschen abzufragen. Mit Rallly kannst du mühelos wunderbare Umfragen für Meetings erstellen.",
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

LGTM with a minor correction: Fix repeated word.

The translation effectively describes meeting polls and their benefits. However, there's a small typo where "wunderbare" is repeated.

Apply this diff to fix the repeated word:

- "meetingPollDescription": "Meetingumfragen sind eine wunderbare Möglichkeit, die Verfügbarkeit von Menschen abzufragen. Mit Rallly kannst du mühelos wunderbare Umfragen für Meetings erstellen."
+ "meetingPollDescription": "Meetingumfragen sind eine wunderbare Möglichkeit, die Verfügbarkeit von Menschen abzufragen. Mit Rallly kannst du mühelos professionelle Umfragen für Meetings erstellen."
📝 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
"meetingPollDescription": "Meetingumfragen sind eine wunderbare Möglichkeit, die Verfügbarkeit von Menschen abzufragen. Mit Rallly kannst du mühelos wunderbare Umfragen für Meetings erstellen.",
"meetingPollDescription": "Meetingumfragen sind eine wunderbare Möglichkeit, die Verfügbarkeit von Menschen abzufragen. Mit Rallly kannst du mühelos professionelle Umfragen für Meetings erstellen.",

@lukevella lukevella merged commit b58b408 into main Oct 1, 2024
4 checks passed
@lukevella lukevella deleted the l10n_main branch October 1, 2024 09:41
@coderabbitai coderabbitai bot mentioned this pull request Oct 2, 2024
@coderabbitai coderabbitai bot mentioned this pull request Oct 16, 2024
This was referenced Nov 3, 2024
@coderabbitai coderabbitai bot mentioned this pull request Nov 15, 2024
This was referenced Jan 28, 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.

1 participant