Translation into Turkish and French

[0xwitty]

I translated the files into Turkish and French.

Summary by CodeRabbit

• New Features

  • Updated French and Turkish translations for various terms in the header and footer sections, enhancing localization for French and Turkish-speaking users.
  • Improved user interface with accurate translations for terms like "About," "Subscribe," and "Community."

• Bug Fixes

  • Corrected localization errors in the French and Turkish language files to ensure proper display of terms.

[netlify]

👷 Deploy request for kleros-website pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	40abe5d

[coderabbitai]

Walkthrough

The changes involve significant updates to the localization files for French (fr.json) and Turkish (tr.json). In the French file, numerous terms in the header and footer sections have been translated from English to French, enhancing the user interface for French-speaking users. The Turkish file has also undergone a comprehensive update, with all footer entries translated into Turkish, improving clarity and accessibility for Turkish-speaking users.

Changes

File	Change Summary
src/intl/fr.json	Updated translations for various keys in the header and footer sections, including terms like "dapps" to "applications décentralisées" and "About" to "À propos".
src/intl/tr.json	Comprehensive localization update with translations for footer terms, including "About" to "Hakkımızda" and "Subscribe" to "Abone Ol".

Poem

In fields of code where rabbits play,
We hop and dance, come what may.
Translations bloom, both near and far,
French and Turkish, our shining stars!
With every word, we share the cheer,
For every user, we hold dear! 🐇✨

---

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
• Mastodon
• Reddit
• LinkedIn

🪧 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 or @coderabbitai title 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.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)

src/intl/tr.json (2)

26-26: Consider expanding the FAQ abbreviation.

While "SSS" is correct, consider adding the full form "Sıkça Sorulan Sorular" in parentheses for better clarity: "faq": "SSS (Sıkça Sorulan Sorular)"

---

28-28: Consider using a more localized email placeholder format.

The current email placeholder uses "[email protected]". Consider using a more Turkish-specific format:

-    "subscribe-placeholder": "[email protected]",
+    "subscribe-placeholder": "[email protected]",

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 5ec7c4c and 40abe5d.

📒 Files selected for processing (2)

• src/intl/fr.json (1 hunks)
• src/intl/tr.json (1 hunks)

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

• src/intl/fr.json

🔇 Additional comments (2)

src/intl/tr.json (2)

10-25: LGTM! Translations are accurate and consistent.

The translations maintain proper Turkish language conventions and accurately convey the meaning of technical terms.

---

29-32: LGTM! Action buttons and copyright notice are properly translated.

The translations for subscription button, primary/secondary actions, and copyright notice are accurate and maintain proper Turkish language conventions.