Translations update from Hosted Weblate

[weblate]

Translations update from Hosted Weblate for LosslessCut/LosslessCut.

Current translation status:

Summary by CodeRabbit

• New Features

  • Added new translations in Spanish, Russian, Chinese, Czech, Italian, Japanese, German, and Slovak for important user messages regarding file export limitations and operational recommendations, including warnings about file name length and simultaneous adjustments to output FPS.
  • Introduced an empty JSON object for future translations in Tamil.

• Bug Fixes

  • Improved clarity in existing translations with updated punctuation for "Examples."

• Documentation

  • Enhanced user guidance and error handling related to file operations through updated translations.

[coderabbitai]

Walkthrough

The changes in this pull request involve updates to the translation files for Spanish, Russian, Chinese, Czech, Italian, Japanese, Slovak, and German. Each language file has received new translation entries addressing user messages about file export limitations, output FPS adjustments, and fallback file naming. Additionally, minor adjustments were made to existing translations for clarity and punctuation. A new empty translation file for Tamil has also been created.

Changes

File Path	Change Summary
locales/es/translation.json	- Added translations: "File name is too long and cannot be exported."
	- Added translations: "Adjusting the output FPS and cutting at the same time will cause incorrect cuts. Consider instead doing it in two separate steps."
	- Added translations: "Fell back to default output file name."
	- Updated translation for "Examples": "Ejemplos" → "Ejemplos," (added comma)
locales/ru/translation.json	- Added translations: "File name is too long and cannot be exported."
	- Added translations: "Adjusting the output FPS and cutting at the same time will cause incorrect cuts. Consider instead doing it in two separate steps."
	- Added translations: "Fell back to default output file name."
	- Updated phrasing for metadata preservation description.
locales/zh_Hans/translation.json	- Added translations: "File name is too long and cannot be exported."
	- Added translations: "Adjusting the output FPS and cutting at the same time will cause incorrect cuts. Consider instead doing it in two separate steps."
	- Added translations: "Fell back to default output file name."
	- Minor adjustment to existing translation for customizing merged file name.
locales/cs/translation.json	- Added translations: "File name is too long and cannot be exported."
	- Added translations: "Adjusting the output FPS and cutting at the same time will cause incorrect cuts. Consider instead doing it in two separate steps."
	- Added translations: "Fell back to default output file name."
	- Updated translation for "Merge cuts": "Spojit sřihy" → "Spojit segmenty"
locales/it/translation.json	- Added translations: "File name is too long and cannot be exported."
	- Added translations: "Fell back to default output file name."
	- Added translations: "Adjusting the output FPS and cutting at the same time will cause incorrect cuts. Consider instead doing it in two separate steps."
locales/ja/translation.json	- Added translations: "You are not allowed to write the output file..."
	- Added translations: "Fell back to default output file name."
	- Added translations: "File name is too long and cannot be exported."
	- Added translations: "Adjusting the output FPS and cutting at the same time will cause incorrect cuts. Consider instead doing it in two separate steps."
locales/sk/translation.json	- Added translations: "File name is too long and cannot be exported."
	- Added translations: "Adjusting the output FPS and cutting at the same time will cause incorrect cuts. Consider instead doing it in two separate steps."
	- Added translations: "Fell back to default output file name."
locales/de/translation.json	- Added translations: "Adjusting the output FPS and cutting at the same time will cause incorrect cuts. Consider instead doing it in two separate steps."
	- Added translations: "File name is too long and cannot be exported."
	- Added translations: "Fell back to default output file name."
locales/ta/translation.json	- New file created: locales/ta/translation.json with an empty JSON object {}.

Possibly related PRs

• Translations update from Hosted Weblate #2014: The updates in the Russian translation file (locales/ru/translation.json) include new entries that address file name length limitations and warnings about incorrect cuts, directly relating to the changes made in the main PR.

🐇 In the land of code, where translations play,
New words were added to brighten the day.
For long file names, a warning we share,
Adjusting FPS? Do it with care!
With commas in place, our messages flow,
Helping users as they learn and grow! 🌟

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 623330d and 9662ea3.

📒 Files selected for processing (8)

• locales/cs/translation.json (2 hunks)
• locales/de/translation.json (1 hunks)
• locales/es/translation.json (2 hunks)
• locales/it/translation.json (1 hunks)
• locales/ja/translation.json (1 hunks)
• locales/ru/translation.json (1 hunks)
• locales/sk/translation.json (1 hunks)
• locales/zh_Hans/translation.json (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (8)

• locales/cs/translation.json
• locales/ru/translation.json
• locales/it/translation.json
• locales/zh_Hans/translation.json
• locales/ja/translation.json
• locales/sk/translation.json
• locales/de/translation.json
• locales/es/translation.json

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: test (windows-latest)

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.