Skip to content

Add UZ (Uzbekistan) locale #6528

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

p4sdev
Copy link

@p4sdev p4sdev commented Jun 21, 2025

πŸ’» ε˜ζ›΄η±»εž‹ | Change Type

  • feat
  • fix
  • refactor
  • perf
  • style
  • test
  • docs
  • ci
  • chore
  • build

πŸ”€ ε˜ζ›΄θ―΄ζ˜Ž | Description of Change

πŸ“ θ‘₯充俑息 | Additional Information

Summary by CodeRabbit

  • New Features

    • Added full Uzbek language support for the application interface.
    • Introduced new Russian translations for image generation and style selection features, including updated prompts and labels.
  • Improvements

    • Updated Russian translations for URL command prompts to enhance clarity and consistency.

Copy link

vercel bot commented Jun 21, 2025

Someone is attempting to deploy a commit to the NextChat Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Jun 21, 2025

Walkthrough

The changes update Russian translations for certain URL command prompts, add extensive new Russian localization strings for image generation features, and introduce a comprehensive Uzbek localization file covering all application UI elements and features.

Changes

File(s) Change Summary
app/locales/ru.ts Updated URLCommand translation strings; added new SdPanel and Sd translation objects for image features.
app/locales/uz.ts Added new file with complete Uzbek language translations for all application UI and features.

Poem

A bunny hops with joy anew,
Uzbek words now join the view!
Russian prompts are crisp and bright,
Image panels set just right.
Across the fields of code we run,
Languages many, but purpose oneβ€”
To make the world more fun! πŸ‡πŸŒ

✨ Finishing Touches
  • πŸ“ Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❀️ 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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: 3

πŸ“œ Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 673f907 and ff54555.

β›” Files ignored due to path filters (2)
  • package-lock.json is excluded by !**/package-lock.json
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
πŸ“’ Files selected for processing (2)
  • app/locales/ru.ts (1 hunks)
  • app/locales/uz.ts (1 hunks)
πŸ”‡ Additional comments (3)
app/locales/ru.ts (3)

589-592: Good translation improvements.

The updates to use "ΠΈΠ· URL" instead of "ΠΈΠ· ссылки" and "ΠŸΡ€ΠΈΠΌΠ΅Π½ΠΈΡ‚ΡŒ?" instead of "автоматичСски Π·Π°ΠΏΠΎΠ»Π½ΠΈΡ‚ΡŒ?" make the Russian translations more precise and user-friendly.


593-623: Well-structured Stable Diffusion translations.

The SdPanel section provides comprehensive and accurate Russian translations for the Stable Diffusion interface. The style translations are appropriate and consistent with Russian technical terminology.


624-647: Comprehensive Stable Diffusion management translations.

The Sd section provides well-translated Russian strings for Stable Diffusion image management features. The status messages and action labels are clear and consistent with the overall localization quality.

Comment on lines +171 to +636
Placeholder: "Google AI API Key",
},

Endpoint: {
Title: "Endpoint Address",
SubTitle: "Example: ",
},

ApiVersion: {
Title: "API Version (specific to gemini-pro)",
SubTitle: "Select a specific API version",
},
GoogleSafetySettings: {
Title: "Google Safety Settings",
SubTitle: "Select a safety filtering level",
},
},
},

Model: "Model",
CompressModel: {
Title: "Summary Model",
SubTitle: "Model used to compress history and generate title",
},
Temperature: {
Title: "Temperature",
SubTitle: "A larger value makes the more random output",
},
TopP: {
Title: "Top P",
SubTitle: "Do not alter this value together with temperature",
},
MaxTokens: {
Title: "Max Tokens",
SubTitle: "Maximum length of input tokens and generated tokens",
},
PresencePenalty: {
Title: "Presence Penalty",
SubTitle:
"A larger value increases the likelihood to talk about new topics",
},
FrequencyPenalty: {
Title: "Frequency Penalty",
SubTitle:
"A larger value decreasing the likelihood to repeat the same line",
},
TTS: {
Enable: {
Title: "Enable TTS",
SubTitle: "Enable text-to-speech service",
},
Autoplay: {
Title: "Enable Autoplay",
SubTitle:
"Automatically generate speech and play, you need to enable the text-to-speech switch first",
},
Model: "Model",
Voice: {
Title: "Voice",
SubTitle: "The voice to use when generating the audio",
},
Speed: {
Title: "Speed",
SubTitle: "The speed of the generated audio",
},
Engine: "TTS Engine",
},
Realtime: {
Enable: {
Title: "Realtime Chat",
SubTitle: "Enable realtime chat feature",
},
Provider: {
Title: "Model Provider",
SubTitle: "Switch between different providers",
},
Model: {
Title: "Model",
SubTitle: "Select a model",
},
ApiKey: {
Title: "API Key",
SubTitle: "API Key",
Placeholder: "API Key",
},
Azure: {
Endpoint: {
Title: "Endpoint",
SubTitle: "Endpoint",
},
Deployment: {
Title: "Deployment Name",
SubTitle: "Deployment Name",
},
},
Temperature: {
Title: "Randomness (temperature)",
SubTitle: "Higher values result in more random responses",
},
},
Copy link
Contributor

Choose a reason for hiding this comment

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

πŸ› οΈ Refactor suggestion

Complete the Uzbek translations for the Settings section.

The Settings section (lines 171-636) contains English text instead of Uzbek translations. This is inconsistent with the rest of the file and the purpose of creating an Uzbek locale.

Consider translating these sections to Uzbek to provide a complete localized experience, or document if keeping certain technical sections in English is intentional.

πŸ€– Prompt for AI Agents
In app/locales/uz.ts from lines 171 to 636, the Settings section currently
contains English text instead of Uzbek translations, which breaks localization
consistency. Translate all the English strings in this section into Uzbek to
provide a complete localized experience. If any technical terms or specific
labels should remain in English intentionally, document those exceptions clearly
in comments.

},
};

export default en;
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

Update export statement to match the corrected variable name.

The export should reference uz instead of en to match the corrected variable name.

-export default en;
+export default uz;
πŸ“ 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
export default en;
-export default en;
+export default uz;
πŸ€– Prompt for AI Agents
In app/locales/uz.ts at line 872, the export statement incorrectly exports `en`
instead of `uz`. Update the export statement to export the variable `uz` to
match the corrected variable name used in the file.

// if you are adding a new translation, please use PartialLocaleType instead of LocaleType

const isApp = !!getClientConfig()?.isApp;
const en: LocaleType = {
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

Fix the variable name for Uzbek locale.

The locale object is named en but this is an Uzbek locale file. It should be named uz to match the language code.

-const en: LocaleType = {
+const uz: LocaleType = {
πŸ€– Prompt for AI Agents
In app/locales/uz.ts at line 8, rename the locale object variable from `en` to
`uz` to correctly reflect that this is the Uzbek locale file and maintain
consistency with the language code.

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