🌐 New Crowdin updates

lukevella commented 2 weeks ago

Summary by CodeRabbit

New Features
- Enhanced localization support for meeting scheduling with new entries for meeting polls and alternatives.
- Added functionalities for finalizing, duplicating, and extending the lifetime of polls.
- Introduced error handling for image uploads.
- New pricing information added to enhance user understanding of subscription options.
- Added statistics tracking for registered users and created polls.
Bug Fixes
- Updated descriptions for file size limitations to ensure consistency.
- Modified German localization for consistency in language use.

vercel[bot] commented 2 weeks ago

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

2 Skipped Deployments

coderabbitai[bot] commented 2 weeks ago

Walkthrough

The pull request introduces updates to localization JSON files, enhancing support for meeting scheduling terminology. New key-value pairs are added across four files: common.json, home.json, app.json, and pricing.json. These changes include entries for meeting polls, descriptions, error messages related to image uploads, and pricing information, ensuring a more comprehensive localization experience.

Changes

File Path	Change Summary
`apps/landing/public/locales/eu/common.json`	- Added: `"when2MeetAlternative": "When2Meet-en alternatiba"`
	- Added: `"meetingPoll": "Bileraren galdetegia"`
`apps/landing/public/locales/eu/home.json`	- Added: `"statsUsersRegistered": "{count, number, ::compact-short}+ erregistratutako erabiltzaileak"`
	- Added: `"statsPollsCreated": "{count, number, ::compact-short}+ inkestak sortu dira"`
	- Added: `"when2meetAlternative": "Oraindik erabiltzen duzu When2Meet?"`
	- Added: `"when2meetAlternativeDescription": "Sortu iragarkirik gabeko bilera-galdetegiak dohainik Rallly-rekin."`
	- Added: `"when2meetAlternativeMetaTitle": "When2Meet-en alternatibarik onena: Rallly"`
	- Added: `"when2meetAlternativeMetaDescription": "Bilatu bilerak antolatzeko modu hobe bat Rallly-rekin, When2Meet-en doako alternatiba nagusia. Erabiltzeko erraza eta doakoa."`
	- Added: `"meetingPoll": "Sortu bilera profesionalen galdetegiak Rallly-rekin"`
	- Added: `"meetingPollDescription": "Bilera-galdetegiak jendearen prestutasuna lortzeko modu bikaina dira. Rallly-k bilera-galdetegi ederrak erraz sortzeko aukera ematen dizu."`
	- Added: `"meetingPollMetaTitle": "Bilera-galdetegia"`
	- Added: `"meetingPollMetaDescription": "Antolatu bilerak erraz gure galdetegia funtzioarekin, guztion prestutasuna ziurtatuz."`
`apps/web/public/locales/eu/app.json`	- Added: `"errorUploadPicture": "Ezin izan da igo"`
	- Added: `"errorUploadPictureDescription": "Arazo bat izan da zure argazkia igotzen. Saiatu berriro geroago."`
	- Added: `"featureNameFinalize": "Amaitu galdetegia"`
	- Added: `"featureNameDuplicate": "Bikoiztu galdetegia"`
	- Added: `"featureNameExtendedPollLifetime": "Galdetegiaren bizitza luzatua"`
	- Modified: `"fileTooLargeDescription": "Igo 2 MB baino txikiagoa den fitxategi bat."`
`apps/landing/public/locales/eu/pricing.json`	- Added: `"pricingTitle": "Hasi doan"`
	- Added: `"pricingSubtitle": "Bertsio-berritu ordainpeko plan batera premium eginbideetarako sarbidea izateko"`
	- Unchanged: `"annualBenefit": "{count} hilabete doan"`

Possibly related PRs

#1091: This PR adds entries related to scheduling polls, which aligns with the main PR's focus on enhancing localization for meeting tools.
#1138: Similar to the main PR, this PR includes new entries for scheduling and polling features, indicating a direct connection in terms of functionality.
#1199: This PR adds new key-value pairs "when2MeetAlternative" and "meetingPoll" to the common.json file, which are directly related to the changes made in the main PR that also introduces similar keys in the same file.
#1347: This PR introduces the key "when2MeetAlternative" in the common.json file and adds "meetingPoll" in the home.json file, both of which are relevant to the changes in the main PR that enhance localization for scheduling tools.
#1348: This PR adds "when2MeetAlternative" and "meetingPoll" entries in the Hungarian localization files, which aligns with the main PR's focus on enhancing localization support for meeting-related terminology.
#1367: This PR introduces the key "meetingPoll" in the Danish localization files, which is directly related to the changes in the main PR that also adds similar keys for meeting polls.
#1370: This PR adds "meetingPollMetaDescription" in the German localization file, which is relevant to the main PR's focus on enhancing meeting-related localization entries.
#1414: This PR adds "when2MeetAlternative" and "meetingPoll" entries in the Chinese localization files, which are directly related to the changes made in the main PR.

🐇 In the meadow, changes sprout,
New keys for meetings, there's no doubt!
Polls and prompts, all in a row,
With every entry, our features grow.
Hopping forward, we celebrate,
Localization magic, it's truly great! 🌼

📜 Recent review details

**Configuration used: CodeRabbit UI** **Review profile: CHILL**

📥 Commits

Reviewing files that changed from the base of the PR and between c68247c90e24ef0984604d1db36993ac0fe60175 and 20bcf102307435597399927aa7ff8c66b85fbbae.

📒 Files selected for processing (2)

* `apps/landing/public/locales/eu/home.json` (2 hunks) * `apps/web/public/locales/de/app.json` (1 hunks)

✅ Files skipped from review due to trivial changes (1)

* apps/web/public/locales/de/app.json

🔇 Additional comments (4)

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

`13-14`: **LGTM! Stats entries are well-formatted.** The new stats entries correctly use ICU MessageFormat for number formatting and maintain consistent translation style. --- `35-35`: **LGTM! Self-hosting blog entry is correct.** The entry maintains correct product name spelling and appropriate translation. --- `36-39`: **Product name spelling issue persists.** The previous review comment about the product name spelling is still valid. The name should be "Rallly" (with 3 l's) instead of "Rally". --- `40-43`: **Product name spelling issue persists.** The previous review comment about the product name spelling is still valid. The name should be "Rallly" (with 3 l's) instead of "Rally".

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

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

lukevella / rallly