mt/basque

[gitlocalize-app]

initial machine translation

See review request for strings.json on GitLocalize

Summary by CodeRabbit

• New Features
  • Introduced localized strings for the Open Voice OS installation process in Basque, enhancing user experience with clear instructions and options.
  • Added interactive button labels and guidance for installation, configuration, and usage of the system.

[coderabbitai]

Walkthrough

The pull request introduces a new localization file, translations/eu-es/strings.json, which provides a complete set of strings for the Open Voice OS installation process in Basque. This file includes user interaction prompts, installation guidance, and various scripts that detail the setup and configuration options available to users.

Changes

Files	Change Summary
translations/eu-es/strings.json	Introduced a new localization file for Basque, containing strings for user interaction and installation guidance.

Possibly related PRs

• Update Italian translation #131: The changes in this PR involve updates to localization strings in the channels.sh, detection.sh, and other related scripts, similar to the new Basque localization introduced in the main PR, which also focuses on enhancing user experience through localized strings for the installation process.

Suggested labels

translation

Poem

🐇 In the land of Basque, we now share,
Strings for installation, with love and care.
"Hurrengoa" and "Bai" lead the way,
Guiding users through their day.
With every click, a voice so bright,
Open Voice OS, a joyful sight! 🌟

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between c3f13ac and de47488.

📒 Files selected for processing (1)

• translations/eu-es/strings.json (1 hunks)

🔇 Additional comments (10)

translations/eu-es/strings.json (10)

2-7: LGTM: Common UI button translations look good.

The translations for common UI buttons in the "misc.sh" section are accurate and concise. The JSON structure is correct, and the content is appropriate for its context.

---

8-11: Verify the availability of the stable channel.

The translation in the "channels.sh" section is accurate. However, there's a potential inconsistency in the content:

"content": "Open Voice OS bi kaleratze kanal nagusi ditu:\n\n  - egonkorra (gomendatua baina oraindik ez dago eskuragarri)\n  - garapena\n\n..."

The text states that the stable channel is recommended but not yet available. This information might be outdated or confusing for users. Please verify if this accurately reflects the current state of the Open Voice OS release channels.

If the stable channel is now available, consider updating this section to reflect the current status.

---

12-15: LGTM: System information template is well-translated.

The "detection.sh" section accurately translates the template for displaying system information. The use of variables (e.g., ${DISTRO_NAME^}, $DISTRO_VERSION) is correct and consistent with the English version. The JSON structure and content are appropriate.

---

16-22: LGTM: Feature descriptions are well-translated.

The "features.sh" section provides accurate and clear translations for the GUI and skills features of Open Voice OS. The JSON structure is correct, with separate keys for different feature descriptions. The content effectively communicates the options available to users during the installation process.

---

23-26: Verify the wake word in example commands.

The "finish.sh" section is well-translated and maintains a friendly tone. However, there's a potential issue with the wake word used in the example commands:

"content": "...\n\n  - Hey Mycroft, zer ordu da?\n  - Hey Mycroft, zein da tenperatura?\n  - Hey Mycroft, nork egin zaitu?\n  ..."

The use of "Hey Mycroft" as the wake word might not be appropriate for Open Voice OS. Please verify if this is the correct wake word for the system, and update it if necessary to match the actual wake word used in Open Voice OS.

Apart from this potential wake word issue, the translation is accurate and effectively communicates the completion of the installation process.

---

27-49: LGTM: Installation process sections are well-translated.

The sections for "methods.sh", "profiles.sh", "satellite.sh", and "summary.sh" are accurately translated and maintain a clear structure. The content effectively communicates the various options and steps in the installation process, including:

1. Installation methods (Docker vs. Python virtual environment)
2. Profile options (Master, Satellite, Listener, Server)
3. Satellite configuration steps
4. Installation summary

The JSON structure is correct, and the translations provide clear explanations for each step of the process.

---

50-53: LGTM: Telemetry explanation is well-translated.

The "telemetry.sh" section provides an accurate and informative translation of the telemetry data collection process. The content effectively communicates:

1. The purpose and importance of telemetry data
2. The anonymous nature of data collection
3. How the data will be used to improve the software
4. A link to more detailed information about the collected data

The JSON structure is correct, and the translation maintains the informative and transparent tone of the original text.

---

54-57: LGTM: Raspberry Pi tuning explanation is well-translated.

The "tuning.sh" section provides a clear and concise translation of the Raspberry Pi tuning process. The content effectively communicates:

1. The purpose of tuning for Raspberry Pi hardware
2. The benefits of the tuning process (improved performance, reduced resource usage)
3. The recommendation to enable tuning

The JSON structure is correct, and the translation accurately conveys the importance of this step for Raspberry Pi users.

---

58-65: LGTM: Uninstall and welcome sections are well-translated.

The "uninstall.sh" and "welcome.sh" sections are accurately translated and maintain the appropriate tone for each context:

1. Uninstall section:

   • Clearly explains the detection of an existing Open Voice OS instance
   • Lists packages that won't be removed during uninstallation
   • Asks for confirmation to proceed with uninstallation

2. Welcome section:

   • Provides a friendly and encouraging introduction to Open Voice OS
   • Effectively communicates the ease of installation and the benefits of the system

The JSON structure is correct for both sections, and the translations accurately convey the intended messages.

---

1-66: Overall assessment: High-quality Basque translations with minor suggestions for improvement.

The translations/eu-es/strings.json file provides comprehensive and accurate Basque translations for the Open Voice OS installation process. The translations effectively communicate the various steps, features, and options of the installation process while maintaining appropriate tones for different sections.

Key strengths:

1. Consistent and correct JSON structure throughout the file
2. Clear and concise translations for UI elements and technical terms
3. Effective communication of complex concepts (e.g., telemetry, tuning)

Minor suggestions for improvement:

1. Verify the availability of the stable channel in the "channels.sh" section
2. Confirm the correct wake word in the "finish.sh" section

These minor issues do not significantly impact the overall quality of the translations. Once addressed, this file will serve as an excellent resource for Basque-speaking users installing Open Voice OS.

---

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

[JarbasAl]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.