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

Add Turkish Language Translation Update tr.json #298

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mdqst
Copy link

@mdqst mdqst commented Nov 28, 2024

Description:

This update introduces the Turkish language translation for the platform. All key sections, including headers, footers, and user-facing text, have been carefully translated to ensure clarity and cultural appropriateness.

Why this matters:

  1. Broader Accessibility: By including Turkish, we make the platform accessible to millions of new users in Turkey and Turkish-speaking communities worldwide.
  2. Enhanced Inclusivity: Supporting multiple languages fosters inclusivity, helping users interact with the platform in their native language.
  3. Improved User Experience: Clear and accurate translations reduce confusion and make the platform easier to navigate for Turkish speakers.

Your feedback on this translation would be greatly appreciated! If further refinements are needed, I’m happy to adjust.

Summary by CodeRabbit

  • New Features
    • Enhanced localization for Turkish-speaking users with updated translations in the footer section.
    • Key terms such as "About," "Research," and "Community" now reflect accurate Turkish equivalents.

Copy link

netlify bot commented Nov 28, 2024

👷 Deploy request for kleros-website pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit e8e8bbd

Copy link
Contributor

coderabbitai bot commented Nov 28, 2024

Walkthrough

The pull request involves a series of translations from English to Turkish in the JSON file src/intl/tr.json. The updates focus on the footer section, providing Turkish equivalents for various terms commonly used in the application. This localization effort aims to improve accessibility for Turkish-speaking users.

Changes

File Change Summary
src/intl/tr.json Translated multiple terms from English to Turkish, including "About" to "Hakkında" and others.

Poem

In the land of words so bright,
A rabbit hops with pure delight.
Translations dance, a joyful cheer,
Turkish terms now loud and clear!
From "About" to "Kitap" they play,
Hopping forth to greet the day! 🐇✨


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 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.

Copy link

sonarcloud bot commented Nov 28, 2024

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 (1)
src/intl/tr.json (1)

19-21: Consider adding tooltips for technical terms

The translations for technical terms like "Emanet" (Escrow), "Kuratörlük" (Curate), and "Burs" (Fellowship) are correct, but some Turkish users might benefit from additional context or tooltips explaining these terms in the UI.

Would you like me to help create a separate translation key structure for tooltips?

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between cc46db1 and e8e8bbd.

📒 Files selected for processing (1)
  • src/intl/tr.json (1 hunks)
🔇 Additional comments (2)
src/intl/tr.json (2)

27-31: LGTM! Well-structured call-to-action translations

The translations for subscription and action buttons are clear, natural, and maintain the call-to-action intent in Turkish. The email placeholder is also appropriately localized.


Line range hint 1-34: LGTM! Valid JSON structure

The JSON structure is well-maintained with proper nesting and no syntax issues. All required commas and brackets are in place.

"whitepaper": "White Paper",
"yellowpaper": "Yellow Paper",
"research": "Research",
"about": "Hakkında",
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

Resolve inconsistency in "About" translation

The header uses "Hakkımızda" while the footer uses "Hakkında" for "About". While both are correct, consistency should be maintained across the application.

-    "about": "Hakkında",
+    "about": "Hakkımızda",
📝 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
"about": "Hakkında",
"about": "Hakkımızda",

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