[go: up one dir, main page]
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.

Sign up for GitHub

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

Jump to bottom

Translations update from Hosted Weblate #2233

Open
wants to merge 7 commits into
base: master
Choose a base branch
from
Open

Translations update from Hosted Weblate #2233

wants to merge 7 commits into from

Conversation

weblate
Copy link
Contributor
@weblate weblate commented Nov 1, 2024 •
edited by coderabbitai bot
Loading

Translations update from Hosted Weblate for LosslessCut/LosslessCut.

Current translation status:

Weblate translation status

Summary by CodeRabbit

  • New Features

    • Added new translations in Spanish, Russian, Chinese, Czech, Italian, Japanese, 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.

  • Bug Fixes

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

@weblate weblate force-pushed the weblate-losslesscut-losslesscut branch from fcce9c4 to 361996a Compare November 1, 2024 11:18
@coderabbitai coderabbitai
Copy link
coderabbitai bot commented Nov 1, 2024 •
edited
Loading

Walkthrough

The changes in this pull request involve updates to the translation files for Spanish, Russian, Chinese, Czech, Italian, Japanese, and Slovak. Each language file has received three 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.

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."
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: "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."
- Added translations: "You are not allowed to write the output file..."
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."

Possibly related PRs

  • Translations update from Hosted Weblate #2010: The changes in the Czech (locales/cs/translation.json), Italian (locales/it/translation.json), and Japanese (locales/ja/translation.json) translation files include new entries and modifications that directly relate to file name length restrictions and warnings about adjusting output FPS while cutting, which are also present in the main PR's Spanish translations.
  • Translations update from Hosted Weblate #2014: The updates in the Russian (locales/ru/translation.json) and Chinese (locales/zh_Hans/translation.json) translation files include similar new entries regarding file name length and FPS adjustments, aligning with 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

📥 Commits

Reviewing files that changed from the base of the PR and between 7145007 and 92c2e0e.

📒 Files selected for processing (7)
  • locales/cs/translation.json (1 hunks)
  • locales/es/translation.json (1 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 (5)
  • locales/cs/translation.json
  • locales/it/translation.json
  • locales/ja/translation.json
  • locales/sk/translation.json
  • locales/zh_Hans/translation.json
🔇 Additional comments (2)
locales/ru/translation.json (1)

923-926: LGTM! The translations are accurate and well-phrased.

The new translations:

  • Maintain technical precision while using natural Russian language
  • Correctly preserve the meaning of the original messages
  • Use appropriate Russian grammar and punctuation
locales/es/translation.json (1)

906-909: LGTM! The Spanish translations are accurate and well-formatted.

The new translations:

  • Maintain the original meaning
  • Use natural Spanish language constructs
  • Keep technical terms appropriately
  • Follow proper JSON formatting with commas

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

gallegonovato and others added 7 commits November 11, 2024 07:56
@weblate
Translated using Weblate (Spanish)
f8f6aaa 
Currently translated at 100.0% (767 of 767 strings)

Translation: LosslessCut/LosslessCut
Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
@Kuzmich55 @weblate
Translated using Weblate (Russian)
1e9b59b 
Currently translated at 100.0% (767 of 767 strings)

Translation: LosslessCut/LosslessCut
Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/ru/
@taozi1996 @weblate
Translated using Weblate (Chinese (Simplified Han script))
b2abac3 
Currently translated at 100.0% (767 of 767 strings)

Translation: LosslessCut/LosslessCut
Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/zh_Hans/
@bovirus @weblate
Translated using Weblate (Italian)
3a4adb9 
Currently translated at 100.0% (767 of 767 strings)

Translation: LosslessCut/LosslessCut
Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/it/
@weblate
Translated using Weblate (Japanese)
9e3b163 
Currently translated at 100.0% (767 of 767 strings)

Translation: LosslessCut/LosslessCut
Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/ja/
@slrslr @weblate
Translated using Weblate (Czech)
42fd036 
Currently translated at 100.0% (767 of 767 strings)

Translation: LosslessCut/LosslessCut
Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/cs/
@weblate
Translated using Weblate (Slovak)
92c2e0e 
Currently translated at 100.0% (767 of 767 strings)

Translation: LosslessCut/LosslessCut
Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/sk/
@weblate weblate force-pushed the weblate-losslesscut-losslesscut branch from 7145007 to 92c2e0e Compare November 11, 2024 06:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@weblate @Kuzmich55 @taozi1996 @bovirus @slrslr