Translations update from Hosted Weblate #2185
Conversation
weblate
force-pushed
the
weblate-losslesscut-losslesscut
branch
from
d8bc829
to
1b89a2b
Compare
WalkthroughThe pull request introduces updates to the localization files for multiple languages, including German, Spanish, Japanese, Russian, Vietnamese, Italian, Slovak, Turkish, and Chinese (Simplified). Each language file has undergone revisions to existing translation strings for clarity and consistency, alongside the addition of numerous new entries. These changes enhance the localization of the software by providing clearer instructions, error messages, and user interface prompts, improving the overall user experience. Changes
Possibly related PRs
Poem
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (4)
locales/zh_Hans/translation.json (3)
932-932: Suggestion for improvement in translationThe translation for "Segment mode" explanations is generally good, but there's a small improvement that can be made for clarity:
- "片段模式："{{mode1}}"以静音段的边界创建片段。"{{mode2}}"以每个静音段的中间点为起始点创建片段。" + "片段模式："{{mode1}}"将在静音段的边界创建片段。"{{mode2}}"将在每个静音段的中间点创建开始/结束的片段。"This change makes the description more precise and aligns better with the English version.
933-933: Suggestion for consistency in translationFor consistency with the previous translation about silent sections, consider adjusting the translation for black sections:
- "片段模式："{{mode1}}"以黑色段的边界创建片段。"{{mode2}}"以每个黑色段的中间点为起始点创建片段。" + "片段模式："{{mode1}}"将在黑色段的边界创建片段。"{{mode2}}"将在每个黑色段的中间点创建开始/结束的片段。"This change maintains consistency with the previous translation and improves clarity.
935-955: Approved translations with minor suggestionsThe translations from line 935 to 955 are generally accurate and natural. However, there are a few minor suggestions for improvement:
Line 942: Consider adding "功能" after "实验性" for clarity:
- "智能切割是实验性功能，无法在所有文件上正常工作。" + "智能切割是实验性功能，可能无法在所有文件上正常工作。"Line 944: The translation is correct, but you might want to consider a more natural phrasing:
- "FFmpeg 切割 FLAC 文件有一个已知问题。文件将会被重新编码，仍然是无损的，但导出会变慢。" + "FFmpeg 在切割 FLAC 文件时存在一个已知问题。文件将被重新编码，虽然仍是无损的，但导出速度可能会变慢。"Line 945: There's a typo in "MOVE", it should be "MOV":
- "此文件包含一个 FFmpeg 无法嵌入到 MP4 格式的音轨，所以自动选择 MOVE 作为默认输出格式。" + "此文件包含一个 FFmpeg 无法嵌入到 MP4 格式的音轨，所以自动选择 MOV 作为默认输出格式。"Line 946: The translation is correct, but you might want to consider a more natural phrasing:
- "是否保留源文件中的章节。" + "是否保留源文件中的章节信息。"These minor adjustments can improve the clarity and naturalness of the translations.
locales/ru/translation.json (1)
902-923: Overall good translations with a minor spelling issueThe translations in this section are generally accurate and consistent with the existing style. Technical terms are appropriately preserved. However, there's a minor spelling issue to address:
- Line 911: "None" is translated as "Ни чего", which should be "Ничего" (one word).
Other translations, such as "Умная нарезка" for "Smart cut" (line 917), are well-chosen and convey the meaning accurately in Russian.
Please correct the spelling of "Ничего" on line 911.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
- locales/ru/translation.json (2 hunks)
- locales/zh_Hans/translation.json (1 hunks)
🧰 Additional context used
🔇 Additional comments (5)
locales/zh_Hans/translation.json (2)
934-934: Approved translationThe translation for the key binding conflict message is accurate and natural.
Line range hint
1-955: Overall assessment of the translation fileThe Chinese (Simplified) translation file is generally of high quality. The JSON structure is correct, and most translations are accurate and natural. A few minor suggestions have been made to improve clarity, consistency, and correct small errors. These improvements will enhance the user experience for Chinese-speaking users of the application.
Here's a summary of the main points:
- The overall JSON structure is valid and well-formatted.
- Most new and modified translations are accurate and natural.
- Some minor improvements have been suggested for clarity and consistency, particularly in the explanations of segment modes and some technical terms.
- A few small errors, such as a typo in "MOV", have been identified and corrected.
After implementing these minor changes, the translation file will be in excellent condition for use in the application.
locales/ru/translation.json (3)
862-863: Translation looks good!The use of "каталог" instead of "папка" for "folder" is a good choice in this technical context. It's more precise and consistent with common usage in Russian software localization.
900-901: Well-translated complex sentence!The translation accurately conveys the original meaning while maintaining good Russian sentence structure. It clearly explains the overview of the export process and the ability to customize parameters.
Line range hint
1-923: Excellent work on Russian localization!The translations in this file are of high quality, demonstrating:
- Accurate conveyance of original meanings
- Consistent use of appropriate Russian technical terminology
- Well-structured sentences that maintain readability
There's only one minor spelling correction needed (line 911: "Ни чего" → "Ничего"). Overall, this localization will greatly improve the user experience for Russian-speaking users of LosslessCut.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (8)
locales/es/translation.json (2)
530-544: Good additions, with minor suggestions for improvement.The new translations are generally well-done and consistent with the existing style. However, there are a few minor points that could be improved:
- Line 531: Consider changing "discrepancia" to "incompatibilidad" for better technical accuracy.
- Line 533-534: The placement of "<0></0>" at the end of the sentence in Spanish feels unnatural. Consider moving it to the beginning.
- Line 536: "flag" could be translated to "bandera" or "opción" for a fully Spanish translation.
544-544: Well-translated complex string, with a minor suggestion.The translation accurately conveys the original message and maintains the correct HTML-like tag structure. However, there's a minor inconsistency in capitalization:
- After "LossLessCut, puede enviar un mensaje a <1>Reportar un error</1>.</1>", the word "reportar" should be capitalized as it starts a new sentence within the tag.
Consider changing "reportar" to "Reportar" for consistency with Spanish capitalization rules.
locales/ja/translation.json (4)
Line range hint
226-450: Translations are generally good, with some areas for improvement.The translations in this section maintain overall consistency, but there are a few points to consider:
Technical term translation is inconsistent. For example, "keyframe" is sometimes kept in English and sometimes translated as "キーフレーム". Consider standardizing this across the application.
The translation for "Segments to export:" (出力する部分:) could be more specific. Consider "出力するセグメント:" for consistency with other uses of "セグメント".
Good practice: Placeholder variables like
{{durationMsFormatted}}and{{frameCount}}are correctly maintained.The translation for "You have no write access to the directory of this file, please select a custom working dir" could be more natural. Consider: "このファイルのあるフォルダへの書き込み権限がありません。作業フォルダを指定してください。"
Consider addressing these minor inconsistencies to improve overall quality and clarity of the translations.
Line range hint
451-675: Translations are accurate with some room for optimization.The translations in this section are generally accurate and explain technical concepts well. However, there are opportunities for improvement:
Excellent translation of complex ideas, such as the explanation of lossless cutting (line 465-467).
The translation for "Hover mouse over buttons in the main interface to see which function they have" could be more concise. Consider: "機能の説明を見るには、メインウィンドウのボタン上にマウスカーソルを乗せます".
Good use of Japanese punctuation, such as using "、" and "。" appropriately.
The translation for "Trash original source file, project CSV and auto-generated files" could be more natural. Consider: "元の入力ファイル、プロジェクトのCSV、自動生成ファイルをごみ箱へ".
Consistent and appropriate use of katakana for technical terms like "ループ" and "スナップ".
Consider these minor adjustments to enhance the natural flow of the Japanese translations while maintaining accuracy.
Line range hint
676-909: New translations added with some inconsistencies and untranslated strings.The final section of the file contains new translations, but there are several issues to address:
Inconsistent translation style: Some new translations use a more literal approach compared to the natural style in earlier parts. For example, line 893-895 use "仮翻訳" (provisional translation) which should be removed in the final version.
Untranslated strings: Lines 902-904 contain English terms that should be translated to Japanese.
Inconsistent terminology: "segment" is sometimes translated as "セグメント" and sometimes as "部分". Standardize this throughout the file.
Good practice: Placeholder variables like
{{alreadyBoundKey}}and{{index}}are correctly maintained.The translation on line 909 for "Smart cut is experimental and will not work on all files." could be improved for clarity. Consider: "スマート切り取りは試験段階の機能で、すべてのファイルで動作するわけではありません。"
Please address the following:
- Remove "仮翻訳" from translations and provide final versions.
- Translate the untranslated strings on lines 902-904.
- Standardize the translation of "segment" throughout the file.
- Review and improve the clarity of newly added translations.
Line range hint
1-909: Overall good quality translations with some areas for improvementThe Japanese translations in this file are generally of good quality and appropriate for a software interface. However, there are some areas that could be improved:
Consistency: Standardize the translation of technical terms (e.g., "keyframe", "segment") throughout the file.
Natural language: Some translations, especially in the latter part of the file, could be made more natural and less literal.
Completeness: Ensure all strings are translated, particularly in the newly added sections.
Clarity: Review complex technical explanations to ensure they are clear and accurate in Japanese.
Style: Remove provisional translation markers (仮翻訳) and finalize all translations.
Addressing these points will enhance the overall quality and user experience of the Japanese localization.
Consider implementing the suggested improvements to further refine the Japanese translations.
locales/tr/translation.json (2)
519-519: Consider revising the translationThe current translation "Dizi geçersiz" for "Combination is invalid" might not fully capture the intended meaning. "Dizi" typically means "sequence" or "series" in Turkish, which may not be the best choice for a key combination.
Consider using a more specific term for "combination" in this context. A suggestion could be:
-"Dizi geçersiz" +"Tuş kombinasyonu geçersiz"This translation more explicitly refers to a key combination and might be clearer to users.
884-884: Consider clarifying the translationThe current translation "En düşük sayısal dolgulu uzunluk" for "Minimum numeric padded length" is a literal translation that might not be immediately clear to all users, especially those unfamiliar with the technical concept of padding in numbers.
Consider revising the translation to make it more descriptive or add a brief explanation. A suggestion could be:
-"En düşük sayısal dolgulu uzunluk" +"En az basamak sayısı (sıfır ile doldurulur)"This revision explains that it's about the minimum number of digits, with zeros used for padding, which might be clearer to users.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (5)
- locales/es/translation.json (1 hunks)
- locales/it/translation.json (1 hunks)
- locales/ja/translation.json (2 hunks)
- locales/ru/translation.json (13 hunks)
- locales/tr/translation.json (4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- locales/ru/translation.json
🧰 Additional context used
🔇 Additional comments (16)
locales/es/translation.json (2)
Line range hint
1-544: Overall structure and consistency are excellent.The JSON file maintains a valid structure throughout, and the translations exhibit a consistent style. The newly added translations integrate well with the existing ones, preserving the overall quality and coherence of the Spanish localization.
Line range hint
1-544: Summary: High-quality translations with minor suggestions for refinement.The changes to the Spanish translation file are well-implemented, maintaining high quality and consistency with the existing translations. The newly added strings accurately convey the intended meanings and preserve the necessary HTML-like tags.
A few minor suggestions were made to further improve clarity and naturalness in some of the new translations. These are small refinements to an already well-executed localization update.
Overall, this update to the Spanish translations is approved and ready for implementation, with the option to incorporate the suggested minor improvements.
locales/ja/translation.json (1)
Line range hint
1-225: Overall, translations appear consistent and appropriate.The translations in this section generally maintain consistency and seem appropriate for their context. A few observations:
- There's a mix of polite and casual language, which might be intentional based on the context of each string.
- Technical terms like "EDL", "MPlayer", and "keyframe" are kept in English, which is common in Japanese software localization.
- Placeholder variables (e.g.,
{{example}},{{fileName}}) are correctly maintained.locales/tr/translation.json (9)
503-503: Translation looks good!The Turkish translation "Eyleme yeni tuş ata" accurately conveys the meaning of "Bind new key to action". It's concise and uses appropriate Turkish terminology.
530-530: Translation is accurateThe Turkish translation "Tuş atamasını kaldır" for "Remove key binding" is correct and uses appropriate terminology. It accurately conveys the action of removing a key binding.
881-881: Translation is correctThe Turkish translation "Yapılandırma dosyası" for "Configuration file" is accurate and uses the proper Turkish term for "configuration". It correctly conveys the concept of a configuration file.
882-882: Translation is well doneThe Turkish translation "Parça dahil edilemedi" for "Failed to include track" accurately conveys the intended meaning. It uses correct Turkish grammar and vocabulary to express the failure to include a track.
883-883: Translation is accurate and well-structuredThe Turkish translation "{{index}} parçasından alt yazılar yüklenemedi" for "Failed to load subtitles from track {{index}}" is correct and well-structured. It accurately conveys the meaning, uses the placeholder {{index}} correctly, and maintains proper Turkish word order. The term "alt yazılar" is the correct translation for "subtitles".
900-900: Translation is accurate and conciseThe Turkish translation "URL indirilemedi" for "Failed to download URL" is correct and concise. It accurately conveys the meaning of the original phrase using appropriate Turkish grammar and vocabulary.
901-901: Translation is well doneThe Turkish translation "Proje dosyası içe aktarılamadı" for "Failed to import project file" is accurate and well-structured. It uses the correct Turkish term for "import" (içe aktarma) and properly expresses the failure to perform this action.
902-902: Translation is accurate and well-structuredThe Turkish translation "Özel değişkenler kullanarak birleştirilen dosyanın dosya adını özelleştirebilirsiniz." for "You can customize the file name of the merged file using special variables." is correct and well-structured. It accurately conveys the meaning of the original sentence, using appropriate Turkish vocabulary and grammar.
Line range hint
1-902: Overall, the Turkish translations are of high qualityThe review of the Turkish translations in this file shows that most entries are accurate, well-structured, and convey the intended meanings correctly. Only a few minor suggestions for improvement were made to enhance clarity or precision for specific technical terms.
Key points:
- Most translations accurately reflect the original English text.
- Proper Turkish grammar and vocabulary are used consistently.
- Technical terms are generally well-translated, with only a few instances where additional clarity could be beneficial.
Great job on maintaining the quality of translations! The suggested improvements are minor and focused on enhancing user understanding of certain technical concepts.
locales/it/translation.json (4)
867-868: Approved: Improved punctuationThe addition of the period at the end of the sentence enhances the grammatical correctness of the translation. The overall translation is accurate and consistent with the context.
868-889: Excellent additions to the Italian localizationThe new translations are well-crafted and accurately convey the meaning of the original text. Notable points:
- Placeholders (e.g., {{alreadyBoundKey}}) are correctly preserved.
- Technical terms are appropriately left in English where necessary (e.g., "Non-global", "FLAC", "MP4", "MOV").
- The translations maintain consistency with existing Italian translations in the file.
- The JSON format is correctly maintained throughout the additions.
These additions significantly enhance the Italian localization of the application.
889-889: Approved: Consistent and accurate translationThe translation for "Mouse wheel frame seek modifier key" is accurate and maintains consistency with the similar translation in the previous line. The decision to keep the technical term "frame seek" in English is appropriate and helps maintain clarity for users familiar with these terms.
Line range hint
1-890: Overall: Excellent improvements to Italian localizationThis update to the Italian translation file (
locales/it/translation.json) brings significant improvements:
- Existing translations have been refined for better grammar and clarity.
- New translations have been added, expanding the coverage of the Italian localization.
- Placeholders and technical terms are consistently and correctly handled throughout the file.
- The JSON structure is maintained correctly.
These changes will enhance the user experience for Italian-speaking users of the application. Great work on the localization effort!
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (2)
locales/es/translation.json (2)
231-231: Improve translation for "Working dir unset"The current translation "Carpeta de trabajo desarmado" is not ideal. The word "desarmado" (disarmed) is not the most appropriate for "unset" in this context. Consider changing it to:
"Working dir unset": "Carpeta de trabajo no establecida",This suggestion better conveys the meaning of an unset working directory in Spanish.
235-235: Consider clarifying "Rotation preview" translationThe current translation "Rotación de la vista previa" is accurate but could be slightly ambiguous. To make it clearer that it's a preview of the rotation, consider changing it to:
"Rotation preview": "Vista previa de rotación",This suggestion more clearly indicates that it's a preview of the rotation effect.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
- locales/es/translation.json (10 hunks)
🧰 Additional context used
🔇 Additional comments (8)
locales/es/translation.json (8)
Line range hint
1-906: Overall structure and content look good!The JSON structure is valid, and the new translations cover a wide range of features and UI elements. The use of HTML-like tags for formatting and variable insertion is consistent throughout the file.
22-22: Good translation for "Snapshot capture format"The Spanish translation "Formato de las capturas de instantáneas" accurately conveys the meaning of the original text and sounds natural in Spanish.
132-132: Appropriate translation for "Settings"The Spanish translation "Ajustes" is a correct and commonly used term for "Settings" in Spanish user interfaces.
138-138: Well-translated UI textThe Spanish translation "Misma carpeta que el archivo de entrada" accurately conveys the meaning of "Same directory as input file" and uses appropriate terminology for Spanish user interfaces.
139-139: Consistent and accurate translationThe Spanish translation "Carpeta de trabajo personalizada" for "Custom working directory" is accurate and consistent with the previous use of "carpeta" for "directory".
141-141: Consistent terminology maintainedThe Spanish translation "Carpeta de trabajo" for "Working directory" is correct and maintains consistency with the previous translations using "carpeta" for "directory".
432-432: Well-translated and clear instructionThe Spanish translation "Establecer la fecha/hora de modificación de todos los archivos de salida en:" accurately conveys the meaning of the original text. The addition of "todos" (all) doesn't alter the meaning and potentially makes it clearer for Spanish users.
Line range hint
1-906: Overall high-quality translations with minor suggestionsThe Spanish translations in this file are generally accurate, natural-sounding, and consistent in terminology. The translator has done an excellent job of conveying the meaning of the original text while adapting it appropriately for a Spanish-speaking audience. A few minor improvements have been suggested for clarity and grammar, but these are relatively minor in the context of the entire file.
Key strengths:
- Consistent use of terminology (e.g., "carpeta" for "directory")
- Proper preservation of HTML-like tags
- Natural-sounding phrases that will be easily understood by Spanish users
Areas for minor improvement:
- A few grammatical adjustments (e.g., matching article gender)
- Slight rephrasing in a couple of instances for improved clarity
Overall, this is a high-quality translation that will serve Spanish-speaking users well.
weblate
force-pushed
the
weblate-losslesscut-losslesscut
branch
from
0fd7135
to
13bbf85
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (4)
locales/zh_Hans/translation.json (4)
932-955: New translations are accurate and well-integrated.The newly added translations are generally accurate and maintain consistency with the existing translations. However, there are a few minor suggestions for improvement:
- Line 936: Consider changing "导入项目文件失败" to "无法导入项目文件" for consistency with other error messages.
- Line 942: The translation "智能切割是实验性功能，无法在所有文件上正常工作。" is correct, but you might want to consider adding "请谨慎使用" (use with caution) at the end to emphasize the experimental nature.
- Line 954: The translation is accurate but quite long. Consider breaking it into shorter sentences for better readability.
Line range hint
1-300: Translations are consistent and clear, with minor suggestions.The translations in this section are generally accurate and consistent. However, there are a few suggestions for improvement:
- Line 41: "导出到单独的文件" could be changed to "导出为单独的文件" for better clarity.
- Line 80: "时间码显示" might be clearer as "时间码显示方式" to indicate it's about how the timecode is displayed.
- Line 179: "不要更改" could be more specific, like "保持原样" to match the English "Don't modify".
These are minor suggestions to enhance clarity and consistency.
Line range hint
301-600: Advanced feature translations are accurate, with a few suggestions for improvement.The translations in this section accurately convey the meaning of advanced features and settings. However, there are a few areas where improvements could be made:
- Line 314: "时间轴触控板/滚轮方向" might be clearer as "时间轴上触控板/滚轮的方向".
- Line 479: "不显示导出选项。您可以单击导出按钮旁边的图标来启用导出选项。" could be simplified to "导出选项默认不显示。点击导出按钮旁的图标可启用。"
- Line 553: "对齐片段时间到关键帧" might be more precise as "将片段时间对齐到关键帧".
These suggestions aim to improve clarity and conciseness in the translations.
Line range hint
601-931: Error messages and notifications are well-translated, with minor suggestions.The translations for error messages, warnings, and system notifications are generally clear and consistent. However, there are a few areas where improvements could be made:
- Line 647: "无法播放此文件。尝试使用菜单来转换为支持的格式。" could be more helpful by adding "请" at the beginning to make it a polite suggestion.
- Line 715: "如果沒有任何帮助，你可以发送<1>错误报告</1>" has a traditional Chinese character "沒". It should be simplified to "没" for consistency.
- Line 891: "回放速率" might be more commonly understood as "播放速度" in the context of media playback.
These suggestions aim to improve consistency and clarity in the error messages and notifications.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (6)
- locales/es/translation.json (10 hunks)
- locales/it/translation.json (1 hunks)
- locales/ja/translation.json (4 hunks)
- locales/ru/translation.json (13 hunks)
- locales/tr/translation.json (4 hunks)
- locales/zh_Hans/translation.json (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (4)
- locales/it/translation.json
- locales/ja/translation.json
- locales/ru/translation.json
- locales/tr/translation.json
🧰 Additional context used
🔇 Additional comments (15)
locales/zh_Hans/translation.json (2)
Line range hint
1-955: Overall structure and consistency look good.The JSON file structure is valid, and the translations appear to be consistent throughout the file. The newly added translations are properly integrated into the existing structure.
Line range hint
1-955: Overall, excellent quality translations with minor suggestions for improvement.The Chinese (Simplified) translations in this file are of high quality, accurately conveying the meaning of the original English text while maintaining consistency in terminology and style. The newly added translations are well-integrated, and the overall structure of the JSON file is valid.
A few minor suggestions have been made throughout the review to further improve clarity, consistency, and readability. These include:
- Slight rewording of some phrases for better clarity or more natural Chinese expression.
- Consistency improvements in error message formatting.
- Suggestions for more precise or commonly used terms in certain contexts.
Implementing these minor suggestions would further enhance the already high-quality translations. Great work overall!
locales/es/translation.json (13)
22-22: Improved translation for "Snapshot capture format"The translation has been updated from "Formato de captura de instantáneas" to "Formato de las capturas de instantáneas". This change improves the clarity and naturalness of the Spanish translation.
44-44: Accurate translation of dialog promptThe translation "Preguntar qué hacer al abrir un nuevo archivo cuando ya hay otro abierto" accurately conveys the meaning of the English text while maintaining natural Spanish phrasing. The redundant "already" in the original text has been correctly omitted in the translation.
132-132: Improved translation for "Settings"The translation has been updated from "Configuración" to "Ajustes". This change is appropriate as "Ajustes" is more concise and commonly used in Spanish software interfaces. Both terms are correct, but "Ajustes" may be more user-friendly in this context.
138-139: Consistent and user-friendly terminologyThe translations have been updated to use "carpeta" (folder) instead of "directorio" (directory):
- "Misma carpeta que el archivo de entrada"
- "Carpeta de trabajo personalizada"
These changes improve consistency and use more user-friendly terminology commonly found in Spanish software interfaces.
141-141: Consistent terminology for "Working directory"The translation "Carpeta de trabajo" for "Working directory" is consistent with the previous changes and maintains the use of user-friendly terminology.
231-231: Consistent terminology for "Working dir unset"The translation "Carpeta de trabajo no configurada" for "Working dir unset" is consistent with the previous changes and maintains the use of user-friendly terminology.
235-235: Accurate translation for "Rotation preview"The new translation "Rotación de la vista previa" for "Rotation preview" is accurate and natural in Spanish. It correctly conveys the meaning of previewing the rotation.
300-300: Clear and consistent translation for directory access messageThe updated translation "No tiene acceso de escritura a la carpeta de este archivo, seleccione una carpeta de trabajo personalizada" is clear and consistent with previous terminology changes. It accurately conveys the message about lacking write access and the need to select a custom working directory.
417-417: Corrected translation as per previous reviewThe translation has been updated according to the previous review comment. It now correctly uses "una" instead of "un" to match the feminine noun "carpeta", and the extra space before the closing tag has been removed. The result is grammatically correct and properly formatted.
432-432: Accurate translation for setting file modification date/timeThe new translation "Establecer la fecha/hora de modificación de todos los archivos de salida en:" accurately conveys the meaning of setting the modification date/time for output files. The Spanish phrasing is natural and clear.
521-521: Consistent translation for "Clear working directory"The new translation "Limpiar carpeta de trabajo" for "Clear working directory" is accurate and consistent with previous terminology changes. It maintains the use of "carpeta" instead of "directorio", ensuring consistency throughout the interface.
529-530: Accurate translations for project file storage and FFmpeg settings
- "Store project file (.llc) in the working directory or next to loaded media file?" is correctly translated as "Guarde el archivo del proyecto (.llc) en la carpeta de trabajo o junto al archivo multimedia cargado".
- The translation for the FFmpeg binaries setting is accurate and clear: "Le permite especificar binarios personalizados de FFmpeg y FFprobe para usar. Asegúrese de que los ejecutables "ffmpeg" y "ffprobe" estén en la misma carpeta y luego seleccione la carpeta."
Both translations accurately convey the technical concepts while remaining clear and natural in Spanish.
Line range hint
531-908: Comprehensive set of new translations addedA large number of new translations have been added, covering various aspects of the application including:
- Error messages and warnings
- UI elements and labels
- Technical instructions and explanations
- Feature descriptions
Overall, the translations appear to be accurate, natural, and consistent with the existing Spanish localization. They maintain appropriate technical terminology while being clear and understandable for users. Notable improvements include:
- Consistent use of "carpeta" for folder/directory
- Accurate translation of technical terms (e.g., "fotograma clave" for keyframe)
- Natural phrasing for UI elements and instructions
These additions significantly enhance the Spanish localization of the application, providing a more comprehensive and user-friendly experience for Spanish-speaking users.
weblate
force-pushed
the
weblate-losslesscut-losslesscut
branch
from
13bbf85
to
1bfe3d5
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (2)
locales/es/translation.json (2)
44-44: Correct translation despite source text issueThe Spanish translation accurately conveys the meaning and corrects the repetition of "already" in the English source. Consider reporting the typo "already already" in the English text to the development team.
Line range hint
521-908: Overall high-quality translations with a few suggestionsAfter reviewing the new translations, I have the following observations:
Consistency: The translations maintain consistency in terminology, especially for technical terms like "fotograma clave" (keyframe), "segmento" (segment), and "línea de tiempo" (timeline).
Accuracy: Technical terms are generally translated accurately, preserving their meaning in the context of video editing software.
Natural language: The translations use natural Spanish constructions and idioms appropriate for software UI.
Specific observations:
a. Line 529: "Store project file (.llc) in the working directory or next to loaded media file?" is translated as "Guarde el archivo del proyecto (.llc) en la carpeta de trabajo o junto al archivo multimedia cargado". The imperative "Guarde" could be changed to the infinitive "Guardar" to match the question format of the English version.
b. Line 706: "Output file name template" is translated as "Plantilla del nombre del archivo de salida". Consider changing "del nombre del archivo" to "de nombre de archivo" for a more concise translation.
c. Line 737: "Cut at the preceding keyframe (not accurate time.) Equiv to" is translated as "Cortar en el fotograma clave anterior (tiempo no exacto). Equivalente a". The period after "time" in the English version is missing in the Spanish translation.
These are minor suggestions, and overall, the translations are of high quality and accurately convey the meaning of the English text.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (6)
- locales/es/translation.json (10 hunks)
- locales/it/translation.json (1 hunks)
- locales/ja/translation.json (4 hunks)
- locales/ru/translation.json (13 hunks)
- locales/tr/translation.json (4 hunks)
- locales/zh_Hans/translation.json (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
- locales/it/translation.json
- locales/ja/translation.json
🧰 Additional context used
🔇 Additional comments (27)
locales/zh_Hans/translation.json (5)
932-932: Translation accuracy confirmed.The translation for the segment mode description related to silent sections is accurate and consistent with the existing style.
933-933: Translation accuracy confirmed.The translation for the segment mode description related to black sections is accurate and consistent with the existing style.
934-934: Translation accuracy confirmed.The translation for the key binding conflict message is accurate and maintains the correct meaning.
935-955: New translations added successfully.The newly added translations (lines 935-955) are accurate and consistent with the existing translation style. They cover various UI elements, error messages, and feature descriptions.
Line range hint
1-955: Overall translation quality is excellent.The changes to the Chinese (Simplified) translation file are well-implemented. The new translations are accurate, consistent with the existing style, and cover a wide range of UI elements and messages. No significant issues were found during the review.
locales/tr/translation.json (10)
503-503: Translation looks good!The Turkish translation "Eyleme yeni tuş ata" accurately conveys the meaning of "Bind new key to action".
519-519: Translation is consistent and accurate!The Turkish translation "Tuş atamasını kaldır" correctly translates "Remove key binding" and maintains consistency with the terminology used in the previous entry.
530-530: Concise and accurate translation!The Turkish translation "Atama yok" is a concise and accurate representation of "No binding".
531-531: Excellent translation of complex instruction!The Turkish translation accurately conveys both the instruction to press the desired key combination and the warning about potential conflicts with other bindings or system hotkeys. The message is clear and maintains the original meaning.
881-881: Accurate technical translation!The Turkish translation "Yapılandırma dosyası" correctly represents "Configuration file" using the appropriate technical term.
882-882: Error message correctly translated!The Turkish translation "Parça dahil edilemedi" accurately conveys the meaning of "Failed to include track" in an error message context.
889-889: Concise and accurate translation!The Turkish translation "Bölümleri koru" correctly and concisely represents "Preserve chapters".
890-890: Accurate technical translation!The Turkish translation "Üst verileri koru" correctly translates "Preserve metadata" using the appropriate technical term for metadata in Turkish.
898-898: Excellent translation of technical explanation!The Turkish translation accurately conveys the detailed explanation about preserving metadata. It maintains the structure of the original text, correctly translates technical terms, and preserves the meaning of each option (Default, Non-global, None). The translation is clear and comprehensive.
900-900: Error message correctly translated!The Turkish translation "URL indirilemedi" accurately conveys the meaning of "Failed to download URL" in an error message context.
locales/ru/translation.json (8)
123-126: Translation updates look good!The updated translations for the cutting mode options are accurate and consistent with the English versions. The terminology used is appropriate for the context of video editing.
186-186: Accurate translation for "Segments and cut points"The updated translation "Сегменты и точки нарезки" accurately reflects the English phrase "Segments and cut points" and is appropriate for the context of video editing.
277-278: Keyframe cut translations are accurateThe updated translations for keyframe cut enabled/disabled messages are accurate and use appropriate terminology for video editing context.
298-299: Excellent translation of technical explanationThe updated translation for the explanation of keyframe cut vs. normal cut is accurate, preserves the original meaning, and uses appropriate technical terminology. It effectively communicates the concept to Russian-speaking users.
388-389: Accurate translation with preserved formattingThe updated translation for "Try both Normal cut and Keyframe cut" is accurate and maintains the original meaning. The HTML tags and variable placeholders are correctly preserved, ensuring proper formatting in the UI.
403-404: Well-translated user guidanceThe updated translation accurately conveys the message about trying different options for best results based on specific files or players. The language is appropriate and maintains the helpful tone of the original text.
476-477: Accurate translation of keyframe cut recommendationThe updated translation for the note about keyframe cut recommendation is accurate and uses appropriate terminology. It effectively communicates the suggestion to Russian-speaking users.
Line range hint
735-923: Comprehensive addition of new translationsThis large block of new translations significantly enhances the Russian localization of the application. The additions cover a wide range of UI elements, error messages, and feature descriptions. The translations are accurate, use appropriate terminology, and maintain consistency with existing translations. This update greatly improves the user experience for Russian-speaking users.
Some notable additions include:
- Detailed explanations of various video editing concepts
- Error messages and warnings
- Descriptions of new features and settings
- Keyboard shortcut descriptions
Overall, this is a valuable addition to the localization effort.
locales/es/translation.json (4)
22-22: Improved translation clarityThe change from "Formato de captura de instantáneas" to "Formato de las capturas de instantáneas" enhances the clarity and naturalness of the Spanish translation.
300-300: Accurate and idiomatic translationThe Spanish translation accurately conveys the meaning of the English text, using appropriate terminology ("carpeta" for "directory") and the correct imperative form for UI instructions.
374-375: Consistent and accurate translations for advanced view toggleBoth new translations accurately convey the meaning of the English text, maintain consistency in terminology ("vista avanzada"), and use the appropriate formal address ("verá") for Spanish UI translations.
Line range hint
1-908: Summary of translation updatesThe updated Spanish translations for the LosslessCut application demonstrate a high level of quality and attention to detail. Key observations:
- Improved clarity in existing translations (e.g., line 22).
- Accurate handling of new feature descriptions and UI elements.
- Consistent use of terminology and formal address throughout the file.
- Minor grammatical and formatting issues in a few translations (e.g., line 417).
- Overall natural and idiomatic Spanish used in the translations.
Recommendations:
- Address the grammatical and formatting issues mentioned in the review comments.
- Consider the minor suggestions for further refinement of some translations.
The updated translations will significantly enhance the user experience for Spanish-speaking users of the LosslessCut application.
weblate
force-pushed
the
weblate-losslesscut-losslesscut
branch
2 times, most recently
from
075ad3f
to
94c71a2
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (1)
locales/tr/translation.json (1)
879-880: Inconsistent quotation marksThe Turkish translation uses inconsistent quotation marks. It's using both straight (") and curly (") quotes. It's generally better to stick to one style for consistency.
Consider updating the quotation marks to be consistent throughout the translation. For example:
- "You have enabled the \"invert segments\" mode <1></1> which will cut away selected segments instead of keeping them. But there is no space between any segments, or at least two segments are overlapping. This would not produce any output. Either make room between segments or click the Yinyang <3></3> symbol below to disable this mode. Alternatively you may combine overlapping segments from the menu.": "Seçilen parçaları tutmak yerine kesecek olan "parçaları ters çevir" modunu etkinleştirdiniz. Ancak hiçbir parça arasında boşluk yok veya en az iki parça üst üste biniyor. Bu herhangi bir çıktı üretmeyecektir. Bu modu devre dışı bırakmak için ya parçalar arasında yer açın ya da aşağıdaki Yinyang simgesine tıklayın. Buna ek olarak menüden üst üste binen parçaları birleştirebilirsiniz.", + "You have enabled the \"invert segments\" mode <1></1> which will cut away selected segments instead of keeping them. But there is no space between any segments, or at least two segments are overlapping. This would not produce any output. Either make room between segments or click the Yinyang <3></3> symbol below to disable this mode. Alternatively you may combine overlapping segments from the menu.": "Seçilen parçaları tutmak yerine kesecek olan \"parçaları ters çevir\" modunu etkinleştirdiniz. Ancak hiçbir parça arasında boşluk yok veya en az iki parça üst üste biniyor. Bu herhangi bir çıktı üretmeyecektir. Bu modu devre dışı bırakmak için ya parçalar arasında yer açın ya da aşağıdaki Yinyang simgesine tıklayın. Buna ek olarak menüden üst üste binen parçaları birleştirebilirsiniz.",
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (6)
- locales/es/translation.json (10 hunks)
- locales/it/translation.json (1 hunks)
- locales/ja/translation.json (4 hunks)
- locales/ru/translation.json (13 hunks)
- locales/tr/translation.json (4 hunks)
- locales/zh_Hans/translation.json (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
- locales/it/translation.json
- locales/ja/translation.json
- locales/ru/translation.json
🧰 Additional context used
🔇 Additional comments (16)
locales/zh_Hans/translation.json (4)
932-932: Accurate translation for segment mode descriptionThe translation for the segment mode description related to silent sections is accurate and well-formatted. It correctly conveys the difference between the two modes.
933-933: Consistent translation for black section segment modeThe translation for the segment mode description related to black sections is consistent with the previous translation for silent sections. It accurately describes the two modes for creating segments based on black sections.
934-955: New translations addedThe newly added translations appear to be accurate and consistent with the existing style. They cover various UI elements, error messages, and feature descriptions. Here are some observations:
- Line 934: Correct translation for the key binding conflict message.
- Lines 935-939: Accurate translations for various error messages.
- Lines 940-942: Proper translations for seek and smart cut features.
- Lines 943-946: Well-translated explanations for known issues and file handling.
- Lines 947-955: Accurate translations for various settings and options.
The translations maintain consistency in terminology and style with the existing translations. They also preserve the correct usage of punctuation, including the appropriate use of Chinese punctuation marks.
932-955: Overall high-quality translations addedThe new translations added to this file are of high quality and contribute positively to the Chinese (Simplified) localization of the application. They accurately convey the meaning of the original text, maintain consistency with existing translations, and use appropriate terminology and punctuation. These additions will enhance the user experience for Chinese-speaking users of the application.
locales/tr/translation.json (5)
530-531: Translations look goodThe translations for "No binding" and "Please press your desired key combination. Make sure it doesn't conflict with any other binding or system hotkeys." are accurate and well-formatted.
881-902: New translations look goodThe newly added translations from line 881 to 902 appear to be accurate and well-formatted. They cover various UI elements and messages, including file operations, settings, and error messages.
Line range hint
1-902: Overall good quality translations with minor improvements neededThe Turkish translations in this file are generally of good quality and cover a wide range of UI elements and messages for the LosslessCut application. However, there are a few minor issues that should be addressed:
- There are a couple of typos in the translations for "Bind new key to action" and "Remove key binding".
- There's an inconsistency in the use of quotation marks in one of the longer translations.
Once these issues are resolved, the translations will be in excellent shape. Great work on providing comprehensive Turkish language support for the application!
519-519:⚠️ Potential issueTypo in Turkish translation
There's a typo in the Turkish translation for "Remove key binding". The word "bağlamayı" should be "atamasını".
Please update the translation as follows:
- "Remove key binding": "Anahtar bağlamayı kaldır", + "Remove key binding": "Tuş atamasını kaldır",Likely invalid or redundant comment.
503-503:⚠️ Potential issueTypo in Turkish translation
There's a typo in the Turkish translation for "Bind new key to action". The word "anahtarı" should be "tuş".
Please update the translation as follows:
- "Bind new key to action": "Eyleme yeni anahtarı bağlayın", + "Bind new key to action": "Eyleme yeni tuş ata",Likely invalid or redundant comment.
locales/es/translation.json (7)
22-22: Translation improvement approvedThe change from "Snapshot capture format" to "Formato de las capturas de instantáneas" is a good improvement. It's grammatically correct, consistent with other translations, and accurately conveys the original meaning.
44-44: Translation improvement and error correction approvedThe change to "Preguntar qué hacer al abrir un nuevo archivo cuando ya hay otro abierto" is an excellent improvement. It not only provides a clear and accurate translation but also corrects the redundancy present in the original English text (double "already").
300-300: Translation improvement approvedThe translation to "No tiene acceso de escritura a la carpeta de este archivo, seleccione una carpeta de trabajo personalizada" is excellent. It accurately conveys the message and uses "carpeta" instead of "directorio", which is more common in Spanish UI translations.
374-375: Translations approved with good parallel structureBoth translations on lines 374 and 375 are excellent:
374: "Vista avanzada desactivada. Ahora solo verá los botones y funciones más esenciales."
375: "Se ha activado la vista avanzada. Ahora también verá botones y funciones no esenciales."They accurately convey the original meaning and maintain a good parallel structure between the two related messages, which aids in user understanding.
521-531: New translations approvedThe new translations added in lines 521-531 are well done. They accurately convey the meaning of the original English text, maintain consistency with existing translations, and use appropriate technical terms where necessary. No grammatical or formatting issues were found.
Line range hint
532-908: Large set of new translations approvedThe extensive set of new translations added in lines 532-908 is impressive and well-executed. Key points:
- Translations accurately convey the meaning of the original English text.
- Grammatical correctness and consistency with existing translations are maintained throughout.
- Technical terms and variable placeholders (e.g., {{segNumVariable}}) are correctly preserved.
- Plural forms are correctly handled using "_one" and "_other" suffixes where appropriate.
- No formatting issues were detected.
This large addition significantly enhances the Spanish localization of the application, covering a wide range of functionality and user interactions.
Line range hint
1-908: Overall translation update is excellent with minor improvement neededThis extensive update to the Spanish translations is overwhelmingly positive. The new and modified translations accurately convey the meaning of the original text, maintain consistency, and handle technical terms and plural forms correctly. There's only one minor issue to address:
- Line 417 needs a small grammatical correction and formatting fix.
Once this minor issue is resolved, the Spanish localization will be significantly enhanced, providing users with a more comprehensive and accurate translation of the application.
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (5)
locales/es/translation.json (5)
27-27: Suggestion for improvementWhile the current translation is more natural, it loses the question form and the explicit mention of "flag". Consider the following improvement:
"Enable experimental ffmpeg features flag?": "¿Habilitar la bandera de funciones experimentales de ffmpeg?"This suggestion maintains the question form, uses "funciones" instead of "características" for better clarity, and keeps the concept of "bandera" (flag).
46-46: Suggestion to maintain question formThe removal of question marks makes this inconsistent with the English version and changes the tone of the sentence. Consider keeping the question marks:
"Ask about importing chapters from opened file?": "¿Preguntar acerca de la importación de capítulos desde un archivo abierto?"This maintains the interrogative form and stays true to the original English text.
533-533: Suggestion for improved word orderThe current translation is understandable, but the word order can be improved for a more natural Spanish sentence structure. Consider the following change:
"<0></0> to show advanced view": "<0></0> para mostrar vista avanzada"This puts the placeholder at the beginning of the sentence, which is more natural in Spanish and matches the structure of the English version better.
534-534: Suggestion for improved word orderTo maintain consistency with the previous suggestion and improve the natural flow in Spanish, consider the following change:
"<0></0> to show simple view": "<0></0> para mostrar vista simple"This puts the placeholder at the beginning of the sentence, which is more natural in Spanish and matches the structure of the English version better.
536-536: Suggestion for improved translationThe current translation can be improved by translating "flag" and adjusting the word order. Consider the following change:
"\"ffmpeg\" experimental flag": "Bandera experimental de \"ffmpeg\""This suggestion translates "flag" to "bandera" and rearranges the words to follow a more natural Spanish syntax.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
- locales/es/translation.json (20 hunks)
- locales/ja/translation.json (4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- locales/ja/translation.json
🧰 Additional context used
🔇 Additional comments (5)
locales/es/translation.json (5)
22-22: Translation improvement approvedThe change from "Formato de captura de instantáneas" to "Formato de las capturas de instantáneas" is an improvement. It uses the plural form, which makes the translation more natural and accurate in Spanish.
535-535: Accurate translation approvedThe translation "{{durationMsFormatted}} ms, {{frameCount}} fotogramas" is correct and uses the appropriate term "fotogramas" for "frames" in the context of video editing.
537-537: Accurate translation approvedThe translation "{{selectedSegments}} de {{nonFilteredSegments}} segmentos seleccionados" correctly and naturally conveys the meaning of the English text in Spanish.
538-539: Accurate translations for singular and plural forms approvedThe translations for singular and plural forms of "frames" are correct:
- "+{{numFrames}} frames_one": "Fotograma +{{numFrames}}"
- "+{{numFrames}} frames_other": "Fotogramas +{{numFrames}}"
These accurately handle both singular and plural forms in Spanish and correctly place the "+" sign at the end, which is the proper number formatting in Spanish.
Line range hint
1-906: Overall translation quality is good with minor suggestions for improvementThe Spanish translations in this file are generally accurate and natural. A few minor improvements were suggested for word order and consistency. Additionally, a typo was identified in the English source text. The new translations added are mostly correct and appropriate for the context of the application.
Key points:
- Some translations could benefit from improved word order for more natural Spanish phrasing.
- Consistency in using question marks for interrogative sentences should be maintained.
- Technical terms like "flag" should be translated when possible.
- The English source text has a typo that should be corrected (duplicate "already" on line 44).
These minor adjustments will further enhance the quality of the Spanish localization for LosslessCut.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
locales/es/translation.json (1)
Line range hint
417-906: Extensive set of new translations added with high accuracyAn impressive number of new translations have been added, covering a wide range of features, UI elements, error messages, and explanations. These translations accurately convey the meaning of the original English text and generally maintain consistency with the application's terminology. Technical terms and concepts are well-translated, providing clear information in Spanish.
However, there is a minor formatting issue:
On line 417, there's an extra space before the closing tag in the translation for "Set a different Working directory":
"Set a different <1>Working directory</1>": "Establezca un <1>Carpeta de trabajo</1> diferente",This small correction will improve the formatting consistency.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
- locales/es/translation.json (20 hunks)
🧰 Additional context used
🔇 Additional comments (10)
locales/es/translation.json (10)
20-22: Translations improved and added correctlyThe new translation for "Invert timeline trackpad/wheel direction?" is accurate and natural in Spanish. The modification of "Snapshot capture format" improves clarity by using a more precise wording.
25-29: New translations added accuratelyThe newly added translations for "Auto save project file?", "Enable experimental ffmpeg features flag?", and "Extract unprocessable tracks to separate files or discard them?" are accurate and consistent with the application's terminology in Spanish.
78-81: Technical translations added accuratelyThe new translations for timestamp shifting and the detailed explanation of keyframe cutting are accurate and maintain the technical nature of the original text while being clear in Spanish.
Line range hint
84-97: Error messages and explanations translated accuratelyThe newly added translations for various error messages, prompts, and explanations are accurate and maintain consistency with the application's terminology. The longer explanations, such as the one for file conversion options, are well-translated and preserve the technical nature of the content while remaining clear in Spanish.
128-141: UI element translations added and updated correctlyThe new translations for various UI elements and options are accurate and appropriate. The working directory options are clearly translated.
Note: The translation for "Settings" has been changed from "Configuración" to "Ajustes". Both are correct, but this change ensures consistency throughout the application.
Line range hint
159-231: Comprehensive set of new translations added accuratelyA large number of new translations for various features, actions, and UI elements have been added. These translations accurately convey the meaning of the original English text and maintain consistency with the application's terminology. They cover a wide range of functionality, from file operations to user interface elements, and are expressed naturally in Spanish.
234-235: Preview-related translations added correctlyThe new translations for muting preview and rotation preview are accurate, clear, and maintain the concise nature of the original text in Spanish.
Line range hint
258-294: Error messages and technical explanations translated accuratelyA comprehensive set of new translations has been added for various error messages, warnings, and informational texts. These translations accurately convey the original meaning and maintain the technical nature of the content where necessary. Longer explanations, such as those for file playback issues and keyframe cutting, are well-translated and provide clear information in Spanish.
Line range hint
300-340: Extensive set of new translations added accuratelyA large number of new translations have been added for various features, prompts, and explanations. These translations accurately convey the meaning of the original English text and maintain consistency with the application's terminology. The longer explanations, particularly those for merging options and metadata preservation, are well-translated and maintain their technical nature while being clear in Spanish.
Line range hint
1-906: Overall assessment: Excellent translation workThis update to the Spanish localization file for LosslessCut is comprehensive and of high quality. The new translations cover a wide range of features, error messages, and explanations, significantly improving the Spanish version of the application. The translations are accurate, consistent with the application's terminology, and maintain a natural flow in Spanish.
Only minor issues were found:
- A typo in the English source text (duplicate "already" on line 44).
- A small formatting issue with an extra space on line 417.
These minor points aside, the translation work is commendable and will greatly enhance the user experience for Spanish-speaking users of LosslessCut.
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Outside diff range and nitpick comments (22)
locales/es/translation.json (22)
22-22: Improve translation consistencyThe translation for "Snapshot capture format" has been changed from "Formato de captura de instantáneas" to "Formato de las capturas de instantáneas". While both are correct, it's important to maintain consistency with other similar translations in the file.
Consider using the singular form for consistency:
"Snapshot capture format": "Formato de captura de instantánea",
27-27: Improve translation clarityThe translation for "Enable experimental ffmpeg features flag?" can be improved for clarity.
Suggest updating the translation to:
"Enable experimental ffmpeg features flag?": "¿Habilitar la bandera de características experimentales de ffmpeg?",This translation more accurately conveys the meaning of "features flag" in Spanish.
78-78: Fix punctuation in Spanish translationThe Spanish translation ends with a period, which is inconsistent with the English source text and other translations.
Remove the trailing period:
"Shift timestamps so that the first timestamp is 0. (LosslessCut default)": "Desplazar las marcas de tiempo para que la primera marca de tiempo sea 0 (Corte sin pérdidas por defecto)",
81-81: Improve readability of long translationThe translation for this long string can be improved for better readability in Spanish.
Suggest breaking the translation into shorter sentences:
"With \"keyframe cut\", we will cut at the nearest keyframe before the desired start cutpoint. This is recommended for most files. With \"Normal cut\" you may have to manually set the cutpoint a few frames before the next keyframe to achieve a precise cut": "Con \"corte de fotogramas clave\", se cortará en el fotograma clave más cercano antes del punto de corte de inicio deseado. Esto se recomienda para la mayoría de los archivos. Con \"corte normal\", es posible que deba establecer manualmente el punto de corte unos fotogramas antes del siguiente fotograma clave para lograr un corte preciso.",
106-106: Improve translation accuracyThe translation for "Working dir set" can be improved to better match the English meaning.
Suggest updating the translation to:
"Working dir set": "Carpeta de trabajo establecida",This translation more accurately conveys the meaning of "set" in this context.
132-132: Maintain consistency in translationThe translation for "Settings" has been changed from "Configuración" to "Ajustes". While both are correct, it's important to maintain consistency with other uses of this term in the application.
If "Ajustes" is the preferred term throughout the application, ensure it's used consistently. Otherwise, consider reverting to:
"Settings": "Configuración",
139-139: Improve translation clarityThe translation for "Custom working directory" can be improved for clarity in Spanish.
Suggest updating the translation to:
"Custom working directory": "Carpeta de trabajo personalizada",This translation is more natural in Spanish and consistent with other translations of "working directory".
234-235: Improve translation consistency and clarityThe translations for these two lines can be improved for consistency and clarity:
Suggest updating the translations to:
"Mute preview? (will not affect output)": "¿Silenciar la vista previa? (no afectará la salida)", "Rotation preview": "Vista previa de rotación",These changes make the translations more consistent with each other and clearer in Spanish.
292-294: Improve translation structure and clarityThe translations for these long strings can be improved for better readability and clarity in Spanish.
Suggest restructuring the translations:
"Unable to playback this file. Try to convert to supported format from the menu": "No se puede reproducir este archivo. Intente convertirlo a un formato compatible desde el menú.", "File not natively supported. Preview may have no audio or low quality. The final export will however be lossless with audio. You may convert it from the menu for a better preview with audio.": "Archivo no compatible de forma nativa. La vista previa puede no tener audio o ser de baja calidad. Sin embargo, la exportación final será sin pérdidas y con audio. Puede convertirlo desde el menú para obtener una mejor vista previa con audio.", "Will now cut at the exact position, but may leave an empty portion at the beginning of the file. You may have to set the cutpoint a few frames before the next keyframe to achieve a precise cut": "Ahora se cortará en la posición exacta, pero puede dejar una porción vacía al principio del archivo. Es posible que deba establecer el punto de corte unos fotogramas antes del siguiente fotograma clave para lograr un corte preciso.",These changes improve the flow and clarity of the translations in Spanish.
303-304: Improve translation clarity and consistencyThe translations for these lines can be improved for clarity and consistency:
Suggest updating the translations to:
"Key frames will show on the timeline. You need to zoom in to view them": "Los fotogramas clave se mostrarán en la línea de tiempo. Necesita hacer zoom para verlos.", "Unable to save your preferences. Try to disable any anti-virus": "No se pueden guardar sus preferencias. Intente desactivar cualquier antivirus.",These changes improve clarity and maintain consistency with other translations.
320-320: Improve translation accuracyThe translation for this line can be improved to better match the English meaning:
Suggest updating the translation to:
"Auto load timecode from file as an offset in the timeline?": "¿Cargar automáticamente el código de tiempo del archivo como un desplazamiento en la línea de tiempo?",This translation more accurately conveys the meaning of the original English text.
405-405: Improve translation clarityThe translation for this line can be improved for clarity:
Suggest updating the translation to:
"Lossless rotation might not work with this file format. You may try changing to MP4": "La rotación sin pérdidas podría no funcionar con este formato de archivo. Puede intentar cambiar a MP4.",This translation is clearer and more natural in Spanish.
432-432: Improve translation accuracy and clarityThe translation for this line can be improved to better match the English meaning and for clarity:
Suggest updating the translation to:
"Set file modification date/time of output files to:": "Establecer la fecha/hora de modificación de los archivos de salida a:",This translation more accurately conveys the meaning of the original English text and is clearer in Spanish.
506-506: Improve translation structure and clarityThe translation for this long string can be improved for better readability and clarity in Spanish:
Suggest restructuring the translation:
"Instead of video apparently starting at 0, you can offset by a specified value. This only applies to the preview inside LosslessCut and does not modify the file in any way. (Useful for viewing/cutting videos according to timecodes)": "En lugar de que el video aparentemente comience en 0, puede establecer un desplazamiento con un valor específico. Esto solo se aplica a la vista previa dentro de LosslessCut y no modifica el archivo de ninguna manera. (Útil para ver/cortar videos de acuerdo con los códigos de tiempo).",This restructured translation improves clarity and flow in Spanish.
521-521: Improve translation consistencyThe translation for "Clear working directory" should be consistent with previous translations of "working directory":
Suggest updating the translation to:
"Clear working directory": "Limpiar carpeta de trabajo",This maintains consistency with other translations of "working directory" in the file.
656-656: Consider localization of keyboard key namesThe translation for the "Alt" key is kept in English. While this is often acceptable, consider whether it should be localized for Spanish users.
If localization is preferred, consider updating to:
"Alt": "Alt (Alternativa)",This provides both the common key name and its Spanish equivalent.
668-669: Improve translation clarity and consistencyThe translations for these lines can be improved for clarity and consistency:
Suggest updating the translations to:
"Fastest: FFmpeg-assisted playback": "Más rápido: Reproducción asistida por FFmpeg", "FFmpeg capture method might sometimes capture more correct colors, but the captured snapshot might be off by one or more frames, relative to the preview.": "El método de captura de FFmpeg a veces puede capturar colores más precisos, pero la instantánea capturada podría estar desplazada uno o más fotogramas con respecto a la vista previa.",These changes improve clarity and maintain consistency with other translations.
702-703: Improve translation clarity and structureThe translation for this long string can be improved for better readability and clarity in Spanish:
Suggest restructuring the translation:
"Losslessly download a whole media file from the specified URL, mux it into an mkv file and open it in LosslessCut. This can be useful if you need to download a video from a website, e.g. a HLS streaming video. For example in Chrome you can open Developer Tools and view the network traffic, find the playlist (e.g. m3u8) and copy paste its URL here.": "Descargue sin pérdidas un archivo multimedia completo desde la URL especificada, combínelo en un archivo mkv y ábralo en LosslessCut. Esto puede ser útil si necesita descargar un video de un sitio web, por ejemplo, un video de streaming HLS. Por ejemplo, en Chrome puede abrir las Herramientas de desarrollo, ver el tráfico de red, encontrar la lista de reproducción (por ejemplo, m3u8) y copiar y pegar su URL aquí.",This restructured translation improves clarity and flow in Spanish.
718-719: Improve translation consistencyThe translation for "Custom FFmpeg directory" should be consistent with previous translations of "directory":
Suggest updating the translation to:
"Ctrl": "Ctrl", "Custom FFmpeg directory (experimental)": "Carpeta de FFmpeg personalizada (experimental)",This maintains consistency with other translations of "directory" in the file.
812-813: Improve translation clarity and accuracyThe translations for these lines can be improved for clarity and accuracy:
Suggest updating the translations to:
"Enable HEVC / H265 hardware decoding (you may need to turn this off if you have problems with HEVC files)": "Habilitar la decodificación por hardware de HEVC / H265 (puede que necesite desactivarla si tiene problemas con archivos HEVC)", "Enabling this will allow faster playback of the exported file. This makes processing use 3 times as much export I/O, which is negligible for small files but might slow down exporting of large files.": "Habilitar esto permitirá una reproducción más rápida del archivo exportado. Esto hace que el procesamiento utilice 3 veces más E/S de exportación, lo cual es insignificante para archivos pequeños pero podría ralentizar la exportación de archivos grandes.",These changes improve clarity and accuracy in Spanish.
848-848: Improve translation structure and clarityThe translation for this long string can be improved for better readability and clarity in Spanish:
Suggest restructuring the translation:
"This option lets you losslessly change the speed at which media players will play back the exported file. For example if you double the FPS, the playback speed will double (and duration will halve), however all the frames will be intact and played back (but faster). Be careful not to set it too high, as the player might not be able to keep up (playback CPU usage will increase proportionally to the speed!)": "Esta opción le permite cambiar sin pérdidas la velocidad a la que los reproductores multimedia reproducirán el archivo exportado. Por ejemplo, si duplica los FPS, la velocidad de reproducción se duplicará (y la duración se reducirá a la mitad), sin embargo, todos los fotogramas permanecerán intactos y se reproducirán (pero más rápido). Tenga cuidado de no establecerlo demasiado alto, ya que el reproductor podría no ser capaz de mantener el ritmo (¡el uso de CPU durante la reproducción aumentará proporcionalmente a la velocidad!).",This restructured translation improves clarity and flow in Spanish.
901-906: Final translations reviewThe translations in this final section are generally accurate and consistent with previous translations. However, there's a small improvement that can be made to the last line:
Suggest updating the translation of the last line to:
"Examples": "Ejemplos",This ensures consistency with the plural form used in English.
| "Make sure you have no overlapping segments.": "Asegúrese de que no haya segmentos superpuestos.", | ||
| "Ask on file open": "Preguntar al abrir el archivo", | ||
| "Ask about what to do when opening a new file when another file is already already open?": "Preguntar acerca de qué hacer cuando se abre un archivo nuevo cuando otro archivo ya está abierto?", | ||
| "Ask about what to do when opening a new file when another file is already already open?": "Preguntar qué hacer al abrir un nuevo archivo cuando ya hay otro abierto", |
There was a problem hiding this comment.
Fix typo in English source text
The English source text contains a repeated word "already". While the Spanish translation is correct, the English text should be fixed in the source file.
Suggest fixing the English source text to:
| "Ask about what to do when opening a new file when another file is already already open?": "Preguntar qué hacer al abrir un nuevo archivo cuando ya hay otro abierto", | |
| "Ask about what to do when opening a new file when another file is already open?": "Preguntar qué hacer al abrir un nuevo archivo cuando ya hay otro abierto" |
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Outside diff range and nitpick comments (4)
locales/sk/translation.json (3)
758-759: Consider revising the translation for clarityThe current translation "Hľadanie kľúčového snímku kolieska myši pomocou modifikátora" might be a bit confusing. Consider rephrasing it to something like "Modifikačné tlačidlo pre hľadanie kľúčových snímkov kolieskom myši" for better clarity.
766-767: Consider rephrasing "Seek one key frame" translationThe current translation "Prejsť o jeden kľúčový snímok" is correct, but for consistency with the previous "Seek one frame" translation, consider changing it to "Prejsť o jeden kľúčový snímok".
The translation for the smart cut message is accurate.
776-777: Consider breaking down the long translation for better readabilityThe translation for the metadata preservation options is accurate, but it's quite long. Consider breaking it down into multiple lines for better readability in the JSON file. For example:
"Whether to preserve metadata from source file. Default: Global (file metadata), per-track and per-chapter metadata will be copied. Non-global: Only per-track and per-chapter metadata will be copied. None: No metadata will be copied": "Zachovanie metadát zo zdrojového súboru.\nPredvolené nastavenie: Globálne (metadáta súboru), metadáta na stopu a na kapitolu sa skopírujú.\nIné ako globálne: Skopírujú sa len metadáta na stopu a na kapitolu.\nŽiadne: Nebudú sa kopírovať žiadne metadáta"The translation for the FLAC cutting issue is accurate.
locales/es/translation.json (1)
159-159: Suggestion: Add question mark for consistencyWhile the translation is accurate, consider adding a question mark to maintain consistency with other similar options in the interface:
"Include all tracks?": "¿Incluir todas las pistas?",This suggestion preserves the interrogative form of the original English text.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
- locales/es/translation.json (20 hunks)
- locales/sk/translation.json (1 hunks)
🧰 Additional context used
🔇 Additional comments (26)
locales/sk/translation.json (9)
756-757: LGTM: Accurate translation of the support messageThe translation accurately conveys the original message about seeking help for LosslessCut issues. It maintains the correct links and formatting.
760-761: LGTM: Correct translations for "Non-global" and "None"The translations for "Non-global" and "None" are accurate and concise.
762-763: LGTM: Accurate translations for mouse wheel frame seek and preserve optionsThe translations for "Mouse wheel frame seek modifier key", "Preserve chapters", and "Preserve metadata" are correct and maintain the original meaning.
764-765: LGTM: Correct translations for "Replace" and "Seek one frame"These translations are accurate and concise.
768-769: LGTM: Accurate translations for chapter preservation and file writing errorBoth translations accurately convey the original messages.
770-771: LGTM: Correct translations for configuration file and URL download failureThese translations are accurate and maintain the original meaning.
772-775: LGTM: Accurate translations for various error messages and settingsThe translations for project import failure, track inclusion failure, subtitle loading failure, and minimum numeric padded length are all correct and maintain the original meaning.
778-779: LGTM: Accurate translations for audio track muxing issue and file name customizationBoth translations accurately convey the original messages and maintain their meaning.
756-779: Overall, high-quality translations with minor suggestions for improvementThe Slovak translations in this update are generally accurate and maintain the original meaning of the English text. The translator has done a commendable job in conveying the technical terms and concepts. There are a few minor suggestions for improvement, mainly focusing on clarity and consistency:
- Consider rephrasing the translation for "Mouse wheel keyframe seek modifier key" for better clarity.
- For consistency, adjust the translation of "Seek one key frame" to match the style of "Seek one frame".
- Consider breaking down the long translation for metadata preservation options into multiple lines for better readability.
These minor adjustments would further enhance the already high-quality translations.
locales/es/translation.json (17)
20-20: LGTM: Minor capitalization correctionThe change in capitalization improves the consistency of the translation without altering its meaning.
22-22: LGTM: Improved clarity in translationThe addition of "las" and pluralization of "captura" enhances the naturalness of the Spanish translation while maintaining the original meaning.
25-25: LGTM: Accurate and natural translationThe translation accurately conveys the meaning of the original text and sounds natural in Spanish. The removal of the question mark is appropriate given the statement form used in the translation.
27-27: LGTM: Accurate translation with appropriate phrasingThe translation correctly conveys the meaning of the original text and is phrased naturally in Spanish. The removal of the question mark is suitable for the statement form used in the translation.
32-33: LGTM: Accurate translations with correct gender agreementThe translations for "Shortest" and "Longest" are accurate and maintain the appropriate feminine gender in Spanish, which is likely referring to "la pista" (the track) or "la duración" (the duration).
41-41: LGTM: Accurate translation with appropriate phrasingThe translation correctly conveys the meaning of the original text and is phrased naturally in Spanish as an instruction. The removal of the question mark is suitable for the imperative form used in the translation.
44-44: Existing issue: Typo in English sourceThe Spanish translation is correct, but the English source contains a repeated word "already". This issue was identified in a previous review. The English source should be corrected in the main translation file.
Suggested fix for the English source:
"Ask about what to do when opening a new file when another file is already open?": "Preguntar qué hacer al abrir un nuevo archivo cuando ya hay otro abierto",
46-46: LGTM: Accurate and natural translationThe translation correctly conveys the meaning of the original text and is phrased naturally in Spanish. The removal of the question mark is appropriate for the statement form used in the translation.
48-48: LGTM: Accurate and clear translationThe translation accurately conveys the meaning of the original text and is expressed clearly in Spanish. The removal of the question mark is suitable for the statement form used in the translation.
78-78: LGTM: Accurate translation with appropriate localizationThe translation accurately conveys the meaning of the original text and is expressed naturally in Spanish. The localization of "LosslessCut" to "Corte sin pérdidas" is appropriate and helps Spanish users understand the application's function.
81-81: LGTM: Detailed and accurate technical translationThe translation accurately conveys the technical details of the "keyframe cut" feature, maintaining the meaning and nuances of the original English text. It effectively communicates the concept to Spanish-speaking users.
84-87: LGTM: Accurate translations of error messages and promptsThe translations for these error messages and input prompts are accurate and maintain the meaning of the original English text. They are phrased naturally in Spanish and should be easily understood by users.
94-97: LGTM: Clear and accurate translations of file-related promptsThe translations for these file saving and conversion option prompts are accurate and maintain the meaning of the original English text. They are phrased naturally in Spanish and effectively communicate the options to users.
128-132: LGTM: Accurate and concise translationsThe translations for these UI elements and options are accurate, concise, and maintain the meaning of the original English text. They should be easily understood by Spanish-speaking users.
138-141: LGTM: Clear and accurate translations of directory-related contentThe translations for these directory-related options and explanations are accurate and effectively communicate the concepts. They are clear and should be easily understood by Spanish-speaking users.
Line range hint
418-906: LGTM: Comprehensive additions to the Spanish translationThe newly added translations (lines 418-906) provide a substantial expansion of the Spanish localization for the LosslessCut application. These additions cover a wide range of UI elements, error messages, and explanations, and appear to be accurate and consistent with the existing translation style. This significant update will greatly improve the user experience for Spanish-speaking users.
Some key observations:
- Technical terms are appropriately translated or maintained in English where necessary.
- Explanations and instructions are clear and natural in Spanish.
- The translations maintain a consistent tone and style throughout.
These extensive additions demonstrate a commitment to providing a comprehensive Spanish localization for the application.
Line range hint
1-906: Summary: Significant improvement in Spanish localizationThis update to the Spanish translation file represents a substantial enhancement of the LosslessCut application's localization. The changes include:
- Refinements to existing translations for improved clarity and naturalness.
- Extensive additions of new translations, greatly expanding the coverage of the Spanish localization.
- Consistent and accurate translations of technical terms and concepts.
While a few minor issues were identified (such as the working directory translation and some inconsistencies in question formatting), the overall quality of the translation is high. These updates will significantly improve the user experience for Spanish-speaking users of the application.
Recommendations:
- Address the few minor issues highlighted in the review comments.
- Consider a final proofreading pass to ensure consistency in formatting (e.g., use of question marks) across similar UI elements.
- Update the English source text to fix the identified typo ("already already").
Great work on this comprehensive translation update!
| @@ -103,7 +103,7 @@ | |||
| "Fastest: Low playback speed (no audio)": "Más rápido: Velocidad de reproducción baja (sin audio)", | |||
| "Instead of video apparently starting at 0, you can offset by a specified value. This only applies to the preview inside LosslessCut and does not modify the file in any way. Useful for viewing/cutting videos according to timecodes)": "En lugar de que el vídeo comience aparentemente en 0, se puede compensar con un valor especificado. Esto sólo se aplica a la vista previa dentro de LosslessCut y no modifica el archivo de ninguna manera. Útil para ver/cortar vídeos según los códigos de tiempo)", | |||
| "Set custom start time offset": "Establecer desplazamiento del tiempo de inicio personalizado", | |||
| "Working dir set": "Set de direcciones de trabajo", | |||
| "Working dir set": "Conjunto de directorios de trabajo", | |||
There was a problem hiding this comment.
Suggestion: Improve translation accuracy
The current translation "Conjunto de directorios de trabajo" doesn't accurately reflect the meaning of "Working dir set". A more accurate translation would be:
| "Working dir set": "Conjunto de directorios de trabajo", | |
| "Working dir set": "Directorio de trabajo establecido", |
This suggestion better conveys that the working directory has been set or established.
| @@ -414,7 +414,7 @@ | |||
| "Fastest: Low playback speed (audio remux), likely to fail": "Más rápido: baja velocidad de reproducción (remux audio), es posible que falle", | |||
| "YouTube Chapters": "Capítulos YouTube", | |||
| "Copy to YouTube description/comment:": "Copiar descripción/comentario de YouTube:", | |||
| "Set a different <1>Working directory</1>": "Establezca un <1>Directorio de trabajo </1> distinto", | |||
| "Set a different <1>Working directory</1>": "Establezca un <1>Carpeta de trabajo </1> distinta", | |||
There was a problem hiding this comment.
Suggestion: Improve grammar and consistency
The current translation has some issues with gender agreement and spacing. Consider the following improvements:
| "Set a different <1>Working directory</1>": "Establezca un <1>Carpeta de trabajo </1> distinta", | |
| "Set a different <1>Working directory</1>": "Establecer una <1>carpeta de trabajo</1> diferente", |
This suggestion:
- Corrects the gender agreement ("una" instead of "un").
- Removes the extra space after "carpeta de trabajo".
- Uses "Establecer" instead of "Establezca" for consistency with other infinitive forms in the interface.
- Changes "distinta" to "diferente" for a more natural translation.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (3)
locales/de/translation.json (3)
907-914: New translations look good, with a minor suggestion.The new translations (lines 907-914) are generally well-done and consistent with the existing style. They accurately convey the meaning of the English phrases in German. However, I have one minor suggestion for improvement:
On line 912, the translation for "Whether to preserve chapters from source file." is "Ob die Kapitel aus der Quelldatei bewahrt werden sollen." While this is correct, it might be more concise to say:
- "Whether to preserve chapters from source file.": "Ob die Kapitel aus der Quelldatei bewahrt werden sollen.", + "Whether to preserve chapters from source file.": "Ob Kapitel aus der Quelldatei beibehalten werden sollen.",This slight change maintains the meaning while making the sentence a bit more concise.
Line range hint
1-906: Overall translation quality is good, with a few points to consider.After reviewing the entire file, I have a few observations and suggestions:
HTML-like tags and variables are consistently handled throughout the file. For example:
"<0>If you're having a problem or question about LosslessCut, please first check the links in the <1>Help</1> menu. If you cannot find any resolution, you may ask a question in <3>GitHub discussions</3> or on <5>Discord.</5></0><1>If you believe that you found a bug in LosslessCut, you may <1>report a bug</1>.</1>": "<0>Wenn Sie ein Problem oder eine Frage zu LosslessCut haben, schauen Sie bitte zunächst in die Links im <1>Hilfe</1>-Menü. Wenn Sie keine Lösung finden können, können Sie eine Frage in den <3>GitHub-Diskussionen</3> oder auf <5>Discord</5> stellen.</0><1>Wenn Sie glauben, dass Sie einen Fehler in LosslessCut gefunden haben, können Sie einen <1>Fehler melden</1>.</1>"This is well-translated and maintains the correct tag structure.
Quotation marks within translated text are properly escaped. For example:
"You have enabled the \"invert segments\" mode <1></1> which will cut away selected segments instead of keeping them. But there is no space between any segments, or at least two segments are overlapping. This would not produce any output. Either make room between segments or click the Yinyang <3></3> symbol below to disable this mode.": "Sie haben den Modus \"Segmente invertieren\" <1></1> aktiviert, der ausgewählte Segmente abschneidet, anstatt sie beizubehalten. Aber zwischen den Segmenten ist kein Platz, oder mindestens zwei Segmente überlappen sich. Dies würde zu keiner Ausgabe führen. Machen Sie entweder Platz zwischen den Segmenten oder klicken Sie auf das Yinyang-Symbol <3></3> unten, um diesen Modus zu deaktivieren."Plural forms are correctly used where applicable. For example:
"+{{numFrames}} frames_one": "+{{numFrames}} frame", "+{{numFrames}} frames_other": "+{{numFrames}} frames"The overall quality of the translations is good, with consistent handling of complex elements and proper use of German language constructs.
There's one minor inconsistency in the use of formal ("Sie") and informal ("Du") forms of address. Most translations use the formal "Sie", but there are a few instances of the informal "Du". For example:
"Try to set the <1>start-</1>cutpoint a <3>few frames before or after</3> the nearest keyframe (may also solve audio sync issues)": "Versuchen Sie, den <1>Start-</1>Schnittpunkt <3>einige Bilder vor oder nach</3> dem nächstgelegenen Keyframe zu setzen (kann auch Probleme mit der Audiosynchronisation lösen)"This uses the formal "Sie", which is consistent with most of the file. However, there are a few instances of the informal "Du", like:
"Instead of video apparently starting at 0, you can offset by a specified value. This only applies to the preview inside LosslessCut and does not modify the file in any way. Useful for viewing/cutting videos according to timecodes)": "Anstatt das Video scheinbar bei 0 zu beginnen, kannst du es um einen bestimmten Wert versetzen. Dies gilt nur für die Vorschau in LosslessCut und verändert die Datei in keiner Weise. (Nützlich für die Anzeige/Schnitt von Videos nach Timecodes)."It would be beneficial to standardize the form of address throughout the file, preferably using the formal "Sie" form as it's more commonly used in software interfaces.
Line range hint
1-914: Conclusion: High-quality translations with minor suggestions for improvementOverall, the German translations in this file are of high quality and well-maintained. The new additions (lines 907-914) are accurately translated and integrate well with the existing content. The file demonstrates consistent handling of complex elements such as HTML-like tags, variables, and plural forms.
The translation work is commendable and ready for use in the software.
For future updates, consider addressing these minor points:
- Standardize the form of address throughout the file, preferably using the formal "Sie" form consistently.
- Continue to review and refine longer translations for conciseness where possible, as suggested for line 912.
These small improvements will further enhance the already high-quality German localization of the software.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
- locales/de/translation.json (1 hunks)
- locales/es/translation.json (20 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- locales/es/translation.json
🧰 Additional context used
weblate
force-pushed
the
weblate-losslesscut-losslesscut
branch
2 times, most recently
from
d75ac01
to
9f20bf2
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Outside diff range and nitpick comments (20)
locales/tr/translation.json (3)
879-879: Consider rephrasing for clarityThe translation is generally accurate, but it's quite long and might be difficult to read. Consider breaking it into shorter sentences for better clarity in Turkish.
880-880: Ensure consistency with quotation marksThe translation uses both straight (") and curly (") quotation marks. For consistency, it's better to use one style throughout the file.
Consider using only straight quotation marks (") for consistency with other translations in the file.
898-898: Consider breaking down the long translationThis translation is quite long and contains multiple technical terms. It might be difficult for users to read and understand quickly.
Consider breaking it down into shorter, more digestible sentences while maintaining the technical accuracy.
locales/it/translation.json (6)
874-875: Translation is correct but could be clearer.The Italian translation "Lunghezza minima riempimento numerico" is technically correct for "Minimum numeric padded length". However, it might be a bit unclear for some users due to its technical nature.
Consider adding a brief explanation or using a more user-friendly term if possible, such as "Numero minimo di cifre" (Minimum number of digits) if that accurately represents the concept.
875-876: Translation is acceptable but could be improved.The Italian translation "Non-global" is a direct transliteration of the English term. While this is understandable, it might not be the most natural way to express this concept in Italian.
Consider using a more natural Italian phrase that conveys the same meaning, such as "Non globale" or "Locale", depending on the context in which this term is used.
880-881: Translation is good but could be slightly improved.The Italian translation "Cerca fotogramma chiave" for "Seek one key frame" is generally correct.
Consider changing it to "Cerca un fotogramma chiave" to more accurately convey the idea of seeking a single key frame.
881-882: Translation is correct but could be more precise.The Italian translation "Cerca fotogramma" for "Seek one frame" is correct and consistent with the previous entry.
For consistency with the previous suggestion, consider changing it to "Cerca un fotogramma" to more accurately convey the idea of seeking a single frame.
889-890: Accurate but lengthy translation.The Italian translation "Tasto modifica ricerca fotogramma chiave con rotellina mouse" accurately conveys the meaning of "Mouse wheel keyframe seek modifier key".
While correct, the translation is quite long. Consider if a more concise version is possible without losing meaning, such as "Tasto modifica per fotogrammi chiave (rotellina)". However, if clarity is preferred over brevity, the current translation is acceptable.
890-891: Accurate but lengthy translation, consistent with previous entry.The Italian translation "Tasto modifica ricerca fotogramma con rotellina mouse" accurately conveys the meaning of "Mouse wheel frame seek modifier key".
As with the previous entry, while correct, the translation is quite long. Consider if a more concise version is possible without losing meaning, such as "Tasto modifica per fotogrammi (rotellina)". However, if clarity is preferred over brevity, the current translation is acceptable. Consistency with the previous entry should be maintained.
locales/es/translation.json (10)
20-20: Suggestion: Improve translation clarityThe current translation for "Invert timeline trackpad/wheel direction?" is correct, but it could be more natural in Spanish.
Consider changing it to:
"Invert timeline trackpad/wheel direction?": "¿Invertir la dirección del trackpad/rueda en la línea de tiempo?",This suggestion places "línea de tiempo" at the end, which is more common in Spanish sentence structure.
22-22: Improve translation accuracyThe current translation for "Snapshot capture format" is not entirely accurate.
Consider changing it to:
"Snapshot capture format": "Formato de captura de instantáneas",This suggestion uses the plural form "instantáneas" which is more commonly used when referring to snapshots in Spanish.
27-27: Suggestion: Improve translation clarityThe current translation for "Enable experimental ffmpeg features flag?" is correct but could be more natural in Spanish.
Consider changing it to:
"Enable experimental ffmpeg features flag?": "¿Habilitar la bandera de funciones experimentales de ffmpeg?",This suggestion uses "bandera" instead of "función" which is a more accurate translation for "flag" in this context.
41-41: Suggestion: Improve translation clarityThe current translation for "Choose cutting mode: Remove or keep selected segments from video when exporting?" is correct but could be more natural in Spanish.
Consider changing it to:
"Choose cutting mode: Remove or keep selected segments from video when exporting?": "Elija el modo de corte: ¿Eliminar o mantener los segmentos seleccionados del video al exportar?",This suggestion adds a question mark at the end, which is more appropriate for a question in Spanish.
78-78: Suggestion: Improve translation clarityThe current translation for "Shift timestamps so that the first timestamp is 0. (LosslessCut default)" is correct but could be more natural in Spanish.
Consider changing it to:
"Shift timestamps so that the first timestamp is 0. (LosslessCut default)": "Desplazar las marcas de tiempo para que la primera sea 0. (Opción predeterminada de LosslessCut)",This suggestion simplifies the sentence structure and uses "Opción predeterminada" which is more common in Spanish for "default".
81-81: Suggestion: Improve translation readabilityThe current translation for this long string is correct, but it could be improved for better readability in Spanish.
Consider changing it to:
"With \"keyframe cut\", we will cut at the nearest keyframe before the desired start cutpoint. This is recommended for most files. With \"Normal cut\" you may have to manually set the cutpoint a few frames before the next keyframe to achieve a precise cut": "Con el \"corte de fotogramas clave\", se cortará en el fotograma clave más cercano antes del punto de corte de inicio deseado. Esto se recomienda para la mayoría de los archivos. Con el \"corte normal\", es posible que tenga que establecer manualmente el punto de corte unos fotogramas antes del siguiente fotograma clave para lograr un corte preciso",This suggestion improves the flow of the Spanish text and uses more natural phrasing.
94-94: Suggestion: Improve translation clarityThe current translation for "Where do you want to save output files? Make sure there is enough free space in this folder" is correct but could be more natural in Spanish.
Consider changing it to:
"Where do you want to save output files? Make sure there is enough free space in this folder": "¿Dónde desea guardar los archivos de salida? Asegúrese de que haya suficiente espacio libre en esta carpeta",This suggestion uses "desea" instead of "quiere" which is more formal and commonly used in software interfaces. It also corrects "hay" to "haya" for the subjunctive mood.
132-132: Suggestion: Improve translation consistencyThe current translation for "Settings" is correct, but it's inconsistent with the term used in line 305 ("Configuración").
Consider changing it to:
"Settings": "Configuración",This will maintain consistency throughout the application.
270-270: Suggestion: Improve translation clarityThe current translation for "No segment to split. Please move cursor over the segment you want to split" is correct but could be more natural in Spanish.
Consider changing it to:
"No segment to split. Please move cursor over the segment you want to split": "No hay segmento para dividir. Por favor, mueva el cursor sobre el segmento que desea dividir",This suggestion uses "desea" instead of "quiere" which is more formal and commonly used in software interfaces.
320-320: Suggestion: Improve translation clarityThe current translation for "Auto load timecode from file as an offset in the timeline?" is correct but could be more natural in Spanish.
Consider changing it to:
"Auto load timecode from file as an offset in the timeline?": "¿Cargar automáticamente el código de tiempo del archivo como desplazamiento en la línea de tiempo?",This suggestion uses "desplazamiento" instead of "un desplazamiento" which sounds more natural in this context.
locales/de/translation.json (1)
920-920: Suggest more precise translationWhile the current translation conveys the general meaning, a more precise translation would better reflect the action of seeking.
Consider changing the translation to:
-"Seek one frame": "Einen Frame überspringen" +"Seek one frame": "Einen Frame ansteuern"Or alternatively:
-"Seek one frame": "Einen Frame überspringen" +"Seek one frame": "Zu einem Frame springen"
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (9)
- locales/de/translation.json (12 hunks)
- locales/es/translation.json (20 hunks)
- locales/it/translation.json (1 hunks)
- locales/ja/translation.json (4 hunks)
- locales/ru/translation.json (13 hunks)
- locales/sk/translation.json (1 hunks)
- locales/tr/translation.json (4 hunks)
- locales/vi/translation.json (1 hunks)
- locales/zh_Hans/translation.json (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
- locales/ja/translation.json
- locales/ru/translation.json
- locales/vi/translation.json
🧰 Additional context used
🔇 Additional comments (115)
locales/zh_Hans/translation.json (26)
932-932: Translation accuracy: Segment mode for silent sectionsThe translation accurately conveys the meaning of the original text, explaining the two modes for creating segments based on silent sections.
933-933: Translation consistency: Segment mode for black sectionsThe translation maintains consistency with the previous line, accurately describing the two modes for creating segments based on black sections.
934-934: Translation accuracy: Key binding conflictThe translation correctly conveys the message about a key binding conflict and asks if the user wants to replace the existing binding.
935-935: Simple translation: Configuration fileThe translation "配置文件" is correct and concise for "Configuration file".
936-936: Translation accuracy: Failed to download URLThe translation accurately conveys the error message for failing to download a URL.
937-937: Translation accuracy: Failed to import project fileThe translation correctly expresses the error message for failing to import a project file.
938-938: Translation accuracy: Failed to include trackThe translation accurately conveys the error message for failing to include a track.
939-939: Translation accuracy: Failed to load subtitlesThe translation correctly expresses the error message for failing to load subtitles from a specific track, maintaining the {{index}} placeholder.
940-940: Simple translation: ReplaceThe translation "替换" is correct and concise for "Replace".
941-941: Translation accuracy: Seek one key frameThe translation accurately conveys the action of seeking one key frame.
942-942: Translation accuracy: Seek one frameThe translation correctly expresses the action of seeking one frame.
943-943: Translation accuracy: Smart cut experimental warningThe translation accurately conveys the warning about smart cut being experimental and not working on all files.
944-944: Translation accuracy: FLAC cutting issueThe translation correctly explains the known issue with cutting FLAC files, including the re-encoding process and potential slower export.
945-945: Translation accuracy: MP4 muxing issueThe translation accurately describes the issue with muxing certain audio tracks into MP4 format and the auto-selection of MOV as the default output format.
946-946: Translation accuracy: Preserve chapters optionThe translation correctly asks whether to preserve chapters from the source file.
947-947: Translation accuracy: File write permission errorThe translation accurately conveys the error message about not being allowed to write the output file, including possible reasons for the issue.
948-948: Translation accuracy: Minimum numeric padded lengthThe translation correctly expresses the concept of minimum numeric padded length.
949-949: Translation accuracy: Mouse wheel keyframe seek modifier keyThe translation accurately describes the mouse wheel keyframe seek modifier key.
950-950: Simple translation: Preserve chaptersThe translation "保留章节" is correct and concise for "Preserve chapters".
951-951: Translation accuracy: Mouse wheel frame seek modifier keyThe translation correctly describes the mouse wheel frame seek modifier key.
952-952: Simple translation: Non-globalThe translation "非全局" is correct for "Non-global".
953-953: Simple translation: NoneThe translation "无" is correct and concise for "None".
954-954: Simple translation: Preserve metadataThe translation "保留元数据" is correct for "Preserve metadata".
955-955: Translation accuracy: Metadata preservation optionsThe translation accurately describes the options for preserving metadata from the source file, including the different levels of preservation (global, non-global, and none).
956-956: Translation accuracy: Customize merged file nameThe translation correctly conveys the message about customizing the file name of the merged file using special variables.
932-956: Overall translation quality: ExcellentThe reviewed translations demonstrate high quality and accuracy. They effectively convey the meaning of the original English text while using appropriate Chinese terminology. The translations are consistent in style and maintain the technical nature of the content where necessary. No issues were found in the reviewed segments.
locales/sk/translation.json (10)
756-757: LGTM: Accurate translation of the support messageThe translation accurately conveys the original English message, maintaining the correct links and formatting.
758-760: LGTM: Correct translations for UI elementsThe translations for "Mouse wheel keyframe seek modifier key", "Non-global", and "None" are accurate and consistent with the application's terminology.
761-763: LGTM: Accurate translations for UI and functionality descriptionsThe translations for "Mouse wheel frame seek modifier key", "Preserve chapters", and "Preserve metadata" are correct and maintain the technical meaning of the original phrases.
764-766: LGTM: Correct translations for action-related phrasesThe translations for "Replace", "Seek one frame", and "Seek one key frame" accurately convey the intended actions in Slovak.
767-768: LGTM: Accurate translations for feature descriptionsThe translations for the smart cut feature description and the chapter preservation option are correct and maintain the original meaning.
769-771: LGTM: Correct translations for error messages and UI elementsThe translations for the file permission error message and "Configuration file" are accurate and maintain the technical meaning.
772-775: LGTM: Accurate translations for error messages and UI elementsThe translations for various error messages and the "Minimum numeric padded length" option are correct and consistent with the application's terminology.
776-777: LGTM: Accurate translations for complex feature descriptionsThe translations for the metadata preservation options and the FLAC file cutting issue are correct and maintain the technical details of the original messages.
778-779: LGTM: Correct translations for technical messagesThe translations for the FFmpeg muxing issue and the file name customization message are accurate and maintain the technical meaning of the original phrases.
756-779: Excellent work on the Slovak translationsThe new translations added to this file are of high quality. They accurately convey the meaning of the original English text while maintaining consistency with existing translations. The technical terms and concepts are correctly translated, and the overall readability in Slovak is good. Great job on improving the localization of LosslessCut for Slovak-speaking users!
locales/it/translation.json (18)
867-868: Translation improvement looks good.The changes in this translation enhance readability while maintaining the original meaning. The addition of a comma and the slight rewording make the Italian text flow better.
868-869: New translation entry is correct and well-formatted.This new Italian translation accurately represents the English version and correctly includes the {{alreadyBoundKey}} placeholder variable. The wording is natural in Italian.
869-870: Correct translation for "Configuration file".The Italian translation "File configurazione" is accurate and concise.
870-871: Error message translation is accurate.The Italian translation "Impossibile scaricare l'URL" correctly conveys the meaning of "Failed to download URL". It's a natural way to express this error in Italian.
871-872: Project file import error message is well translated.The Italian translation "Impossibile importare il file progetto" is an accurate and natural way to express "Failed to import project file". It maintains consistency with the style of other error messages in the file.
872-873: Track inclusion error message translated correctly.The Italian translation "Impossibile includere la traccia" accurately represents "Failed to include track" and maintains consistency with other error messages.
873-874: Subtitle loading error message translated accurately.The Italian translation "Impossibile caricare sottotitoli traccia {{index}}" correctly conveys the meaning of "Failed to load subtitles from track {{index}}". The placeholder variable is properly maintained, and the wording is natural in Italian.
876-877: Correct translation for "None".The Italian translation "Nessuno" is the appropriate and commonly used term for "None".
877-878: Accurate translation for "Preserve metadata".The Italian translation "Mantieni metadati" correctly and concisely expresses the meaning of "Preserve metadata". It's a clear and appropriate translation for this technical term.
878-879: Consistent and correct translation.The Italian translation "Mantieni capitoli" for "Preserve chapters" is accurate and maintains consistency with the previous "Preserve metadata" translation.
879-880: Correct translation for "Replace".The Italian translation "Sostituisci" is the appropriate and commonly used term for "Replace".
882-883: Accurate translation of the experimental feature message.The Italian translation "Il taglio intelligente è sperimentale e non funzionerà su tutti i file." accurately conveys the meaning of "Smart cut is experimental and will not work on all files." The wording is natural and appropriate in Italian for this type of warning message.
883-884: Excellent translation of technical information.The Italian translation accurately conveys the message about the known issue with cutting FLAC files. It maintains the technical nature of the information while being clear and understandable in Italian. The translation properly explains that the file will be re-encoded, remains lossless, but the export may be slower.
884-885: Accurate translation of technical message.The Italian translation correctly conveys the message about audio track incompatibility with the MP4 format and the automatic selection of MOV as the default output format. The technical terms are appropriately translated, and the sentence structure in Italian is natural and clear.
885-886: Concise and accurate translation.The Italian translation "Se preservare i capitoli dal file sorgente." correctly and concisely conveys the meaning of "Whether to preserve chapters from source file." The wording is clear and appropriate in Italian for this type of description.
886-887: Comprehensive and accurate translation of technical details.The Italian translation excellently conveys the detailed information about preserving metadata from the source file. It accurately translates the different options (Default, Non-global, None) and their implications. The technical terms are appropriately translated, and the sentence structure in Italian is clear and follows the original English text closely.
887-888: Clear and accurate translation of error message.The Italian translation effectively communicates the error message about not being able to write the output file. It accurately conveys both possible reasons for this error (existing file with wrong permissions or lack of write permissions in the output folder). The wording is natural and appropriate in Italian for this type of error message.
888-889: Accurate translation of customization message.The Italian translation "È possibile personalizzare il nome del file unito usando variabili speciali." correctly conveys the message about the ability to customize the merged file's name using special variables. The wording is clear and natural in Italian, accurately representing the original English text.
locales/es/translation.json (39)
25-25: LGTM: Correct translationThe translation for "Auto save project file?" is accurate and natural in Spanish.
29-29: LGTM: Correct translationThe translation for "Extract unprocessable tracks to separate files or discard them?" is accurate and natural in Spanish.
32-33: LGTM: Correct translationsThe translations for "Shortest" and "Longest" are accurate and concise in Spanish.
44-44: Fix typo in English source textThe English source text contains a repeated word "already". While the Spanish translation is correct, the English text should be fixed in the source file.
Suggest fixing the English source text to:
"Ask about what to do when opening a new file when another file is already open?": "Preguntar qué hacer al abrir un nuevo archivo cuando ya hay otro abierto"
46-46: LGTM: Correct translationThe translation for "Ask about importing chapters from opened file?" is accurate and natural in Spanish.
48-48: LGTM: Correct translationThe translation for "Ask for confirmation when closing app or file?" is accurate and natural in Spanish.
84-84: LGTM: Correct translationThe translation for "Invalid start or end value. Must contain a number of seconds" is accurate and natural in Spanish.
97-97: LGTM: Correct translationThe translation for this long string about conversion options is accurate and well-structured in Spanish.
106-106: Suggestion: Improve translation accuracyThe current translation "Conjunto de directorios de trabajo" doesn't accurately reflect the meaning of "Working dir set". A more accurate translation would be:
"Working dir set": "Directorio de trabajo establecido",This suggestion better conveys that the working directory has been set or established.
128-128: LGTM: Correct translationThe translation for "Keep?" is accurate and concise in Spanish.
138-139: LGTM: Correct translationsThe translations for "Same directory as input file" and "Custom working directory" are accurate and natural in Spanish.
141-141: LGTM: Correct translationThe translation for "Working directory" is accurate and consistent with previous uses.
159-159: LGTM: Correct translationThe translation for "Include all tracks?" is accurate and natural in Spanish.
231-231: LGTM: Correct translationThe translation for "Working dir unset" is accurate and consistent with previous uses of "directorio de trabajo".
234-235: LGTM: Correct translationsThe translations for "Mute preview? (will not affect output)" and "Rotation preview" are accurate and natural in Spanish.
258-258: LGTM: Correct translationThe translation for "Failed to convert file. Try a different conversion" is accurate and natural in Spanish.
265-265: LGTM: Correct translationThe translation for "The audio track is not supported. You can convert to a supported format from the menu" is accurate and natural in Spanish.
292-292: LGTM: Correct translationThe translation for "Unable to playback this file. Try to convert to supported format from the menu" is accurate and natural in Spanish.
294-294: LGTM: Correct translationThe translation for this long string about cutting at the exact position is accurate and well-structured in Spanish.
300-300: LGTM: Correct translationThe translation for "You have no write access to the directory of this file, please select a custom working dir" is accurate and natural in Spanish.
303-304: LGTM: Correct translationsThe translations for "Key frames will show on the timeline. You need to zoom in to view them" and "Unable to save your preferences. Try to disable any anti-virus" are accurate and natural in Spanish.
308-308: LGTM: Correct translationThe translation for "Show this page before exporting?" is accurate and natural in Spanish.
330-330: LGTM: Correct translationThe translation for "Enable MOV Faststart?" is accurate and natural in Spanish.
337-338: LGTM: Correct translationsThe translations for these long strings about preserving metadata and creating chapters when merging are accurate and well-structured in Spanish.
340-340: LGTM: Correct translationThe translation for this long string about preserving MOV/MP4 metadata tags is accurate and well-structured in Spanish.
347-347: LGTM: Correct translationThe translation for "Cleanup files?" is accurate and natural in Spanish.
355-355: LGTM: Correct translationThe translation for "Show export options screen before exporting?" is accurate and natural in Spanish.
374-375: LGTM: Correct translationsThe translations for these strings about advanced view are accurate and well-structured in Spanish.
405-405: LGTM: Correct translationThe translation for this string about lossless rotation is accurate and well-structured in Spanish.
417-417: Suggestion: Improve grammar and consistencyThe current translation has some issues with gender agreement and spacing. Consider the following improvements:
"Set a different <1>Working directory</1>": "Establecer una <1>carpeta de trabajo</1> diferente",This suggestion:
- Corrects the gender agreement ("una" instead of "un").
- Removes the extra space after "carpeta de trabajo".
- Uses "Establecer" instead of "Establezca" for consistency with other infinitive forms in the interface.
- Changes "distinta" to "diferente" for a more natural translation.
432-432: LGTM: Correct translationThe translation for "Set file modification date/time of output files to:" is accurate and natural in Spanish.
442-442: LGTM: Correct translationThe translation for this string about automatically converting unsupported files is accurate and well-structured in Spanish.
484-485: LGTM: Correct translationsThe translations for "Export project (LLC)..." and "Import project (LLC)..." are accurate and natural in Spanish.
493-493: LGTM: Correct translationThe translation for "Use this for all files until LosslessCut is restarted?" is accurate and natural in Spanish.
506-506: LGTM: Correct translationThe translation for this long string about offsetting video start time is accurate and well-structured in Spanish.
521-521: LGTM: Correct translationThe translation for "Clear working directory" is accurate and consistent with previous uses of "carpeta de trabajo".
529-530: LGTM: Correct translationsThe translations for these strings about storing project files and specifying custom FFmpeg binaries are accurate and well-structured in Spanish.
531-906: LGTM: Correct translationsThe translations for all these new strings (from line 531 to 906) are accurate, natural, and well-structured in Spanish. They cover a wide range of UI elements, error messages, and feature descriptions, and they maintain consistency with the existing translations.
Line range hint
1-906: Overall assessment: High-quality translations with minor improvement suggestionsThe Spanish translations in this file are generally accurate, natural, and well-structured. The new additions (from line 531 onwards) maintain consistency with existing translations and cover a wide range of UI elements, error messages, and feature descriptions.
A few minor suggestions were made to improve clarity, consistency, and natural language use in some translations. These include:
- Improving sentence structure for more natural Spanish phrasing.
- Ensuring consistency in terminology (e.g., "carpeta de trabajo" for "working directory").
- Correcting small grammatical issues (e.g., gender agreement).
- Suggesting more formal or commonly used terms in software interfaces.
No major issues were found, and the overall quality of the translations is high. Implementing the suggested minor improvements will further enhance the user experience for Spanish-speaking users of LosslessCut.
locales/de/translation.json (22)
908-908: LGTM: Accurate translation for "Configuration file"The German translation "Konfigurationsdatei" for "Configuration file" is correct and appropriate.
909-909: LGTM: Correct translation for "Preserve metadata"The German translation "Metadaten bewahren" accurately conveys the meaning of "Preserve metadata".
910-910: LGTM: Appropriate translation for "Preserve chapters"The German translation "Kapitel bewahren" is correct and consistent with the previous entry's style.
911-911: LGTM: Correct and concise translation for "Replace"The German translation "Ersetzen" is the appropriate equivalent for "Replace".
912-912: LGTM: Well-translated explanation for preserving chaptersThe German translation "Ob die Kapitel aus der Quelldatei bewahrt werden sollen." accurately conveys the meaning of the original sentence and maintains consistency with previous translations.
913-913: LGTM: Accurate translation of error messageThe German translation "Projektdatei konnte nicht importiert werden" correctly conveys the meaning of "Failed to import project file" and maintains an appropriate tone for an error message.
914-914: LGTM: Correct translation for "None"The German translation "Keine" is the appropriate equivalent for "None" in this context.
915-915: LGTM: Accurate technical translationThe German translation "Mausrad Keyframe-Sprung Modifikatortaste" correctly conveys the technical meaning of "Mouse wheel keyframe seek modifier key", using appropriate German technical terms.
917-917: LGTM: Correct translation for technical termThe German translation "Nicht global" accurately represents the meaning of "Non-global".
918-918: LGTM: Accurate technical translationThe German translation "Minimale numerische Auffülllänge" correctly conveys the technical meaning of "Minimum numeric padded length", using appropriate German technical terms.
919-919: LGTM: Consistent and accurate technical translationThe German translation "Mausrad Frame-Sprung Modifikatortaste" correctly conveys the meaning of "Mouse wheel frame seek modifier key" and maintains consistency with previous similar translations.
921-921: LGTM: Accurate translation for seeking keyframeThe German translation "Um einen Keyframe springen" correctly conveys the meaning of "Seek one key frame" and uses appropriate terminology.
922-922: LGTM: Clear and accurate translation of smart cut explanationThe German translation "Smart Cut ist experimentell und funktioniert nicht bei allen Dateien." accurately conveys the meaning of the original sentence and maintains appropriate technical terminology.
923-923: LGTM: Accurate translation of technical explanationThe German translation accurately conveys the explanation about the FLAC files cutting issue, maintaining technical accuracy and natural language flow.
924-924: LGTM: Precise translation of technical explanationThe German translation accurately conveys the explanation about the MP4 muxing issue, using correct technical terminology and maintaining a natural sentence structure.
925-925: LGTM: Comprehensive and accurate translation of metadata optionsThe German translation provides a clear and accurate explanation of the metadata preservation options, maintaining technical accuracy and readability despite the complexity of the content.
926-926: LGTM: Clear and accurate translation of error messageThe German translation accurately conveys the file writing permission error message, maintaining both technical accuracy and user-friendly language.
927-927: LGTM: Clear translation of file naming customization hintThe German translation accurately conveys the hint about customizing merged file names, using appropriate technical terminology and maintaining a natural sentence structure.
928-928: LGTM: Accurate translation of key binding conflict messageThe German translation correctly conveys the key binding conflict message, maintaining the placeholder and using appropriate technical terminology.
929-929: LGTM: Concise and accurate translation of error messageThe German translation "Download der URL fehlgeschlagen" correctly conveys the meaning of "Failed to download URL" in a concise and clear manner.
930-930: LGTM: Clear and accurate translation of subtitle loading errorThe German translation accurately conveys the subtitle loading failure message, maintaining the placeholder and using appropriate terminology for "subtitles" and "track".
Line range hint
1-930: Overall assessment: High-quality translations with one minor issueThe German translations added to this file are generally of high quality, accurately conveying the meaning of the original English text while maintaining appropriate technical terminology and natural German language structure. Only one minor issue was identified:
- Line 916: Typo in the translation of "Failed to include track"
Consider addressing this minor issue, and the file will be in excellent shape for the German localization of the application.
| "Replace": "Değiştir", | ||
| "Seek one frame": "Bir kare ara", | ||
| "Seek one key frame": "Bir ana kare ara", | ||
| "Smart cut is experimental and will not work on all files.": "Akıllı kesme deneyseldir ve tüm dosyalarda çalışmaz.", |
There was a problem hiding this comment.
Improve translation accuracy
The current translation "Akıllı kesme deneyseldir ve tüm dosyalarda çalışmaz." is slightly off from the original meaning.
Consider changing it to:
"Akıllı kesme deneyseldir ve tüm dosyalarda çalışmayabilir."
This more accurately conveys that it "may not work" rather than definitively stating it "will not work".
| "Failed to import project file": "Projektdatei konnte nicht importiert werden", | ||
| "None": "Keine", | ||
| "Mouse wheel keyframe seek modifier key": "Mausrad Keyframe-Sprung Modifikatortaste", | ||
| "Failed to include track": "Spun einfügen fehlgeschlagen", |
There was a problem hiding this comment.
Typo in German translation
There's a typo in the German translation. "Spun" should be "Spur".
Please correct the translation as follows:
-"Failed to include track": "Spun einfügen fehlgeschlagen"
+"Failed to include track": "Spur einfügen fehlgeschlagen"📝 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.
| "Failed to include track": "Spun einfügen fehlgeschlagen", | |
| "Failed to include track": "Spur einfügen fehlgeschlagen", |
weblate
force-pushed
the
weblate-losslesscut-losslesscut
branch
from
9f20bf2
to
4113bca
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (7)
locales/it/translation.json (6)
867-867: Translation looks good, minor suggestion for clarityThe translation is accurate, but we could slightly improve the clarity:
- "This gives you an overview of the export and allows you to customise more parameters before exporting, like changing the output file name.": "Questo ti offre una panoramica dell'esportazione e ti consente di personalizzare più parametri prima dell'esportazione, come cambiare il nome del file destinazione.", + "This gives you an overview of the export and allows you to customise more parameters before exporting, like changing the output file name.": "Questo ti offre una panoramica dell'esportazione e ti consente di personalizzare ulteriori parametri prima dell'esportazione, come cambiare il nome del file di destinazione.",The suggested changes:
- Changed "più parametri" to "ulteriori parametri" for better clarity.
- Changed "file destinazione" to "file di destinazione" for better Italian phrasing.
874-874: Translation could be improved for clarityThe current translation is technically correct, but it might be confusing for non-technical users. Consider the following change:
- "Minimum numeric padded length": "Lunghezza minima riempimento numerico", + "Minimum numeric padded length": "Lunghezza minima per riempimento numerico",This change adds the preposition "per" to make the meaning clearer in Italian.
883-883: Translation is accurate, minor suggestion for improvementThe translation is correct, but we can slightly improve the flow in Italian:
- "There is a known issue in FFmpeg with cutting FLAC files. The file will be re-encoded, which is still lossless, but the export may be slower.": "Esiste un problema noto in FFmpeg relativo al taglio dei file FLAC. Il file verrà ricodificato, il file è ancora senza perdite, ma l'esportazione potrebbe essere più lenta.", + "There is a known issue in FFmpeg with cutting FLAC files. The file will be re-encoded, which is still lossless, but the export may be slower.": "Esiste un problema noto in FFmpeg relativo al taglio dei file FLAC. Il file verrà ricodificato, mantenendolo comunque senza perdite, ma l'esportazione potrebbe essere più lenta.",This change improves the flow of the sentence in Italian while maintaining the original meaning.
885-885: Translation is correct but could be more naturalThe translation is accurate, but we can make it sound more natural in Italian:
- "Whether to preserve chapters from source file.": "Se preservare i capitoli dal file sorgente.", + "Whether to preserve chapters from source file.": "Indica se mantenere i capitoli dal file sorgente.",This change makes the sentence more idiomatic in Italian.
886-886: Translation is accurate but could be improved for clarityThe translation is correct, but we can improve its clarity and flow in Italian:
- "Whether to preserve metadata from source file. Default: Global (file metadata), per-track and per-chapter metadata will be copied. Non-global: Only per-track and per-chapter metadata will be copied. None: No metadata will be copied": "Indica se preservare i metadati dal file sorgente. Impostazione predefinita: verranno copiati i metadati globali (metadati file), per traccia e per capitolo. Non globale: verranno copiati solo i metadati per traccia e per capitolo. Nessuno: nessun metadato verrà copiato.", + "Whether to preserve metadata from source file. Default: Global (file metadata), per-track and per-chapter metadata will be copied. Non-global: Only per-track and per-chapter metadata will be copied. None: No metadata will be copied": "Indica se preservare i metadati dal file sorgente. Impostazione predefinita: verranno copiati i metadati globali (metadati del file), per traccia e per capitolo. Non globale: verranno copiati solo i metadati per traccia e per capitolo. Nessuno: non verrà copiato alcun metadato.",These changes improve the clarity and natural flow of the Italian translation.
889-890: Translations are accurate but could be more conciseThe translations are correct, but we can make them more concise and consistent with the application's terminology:
- "Mouse wheel keyframe seek modifier key": "Tasto modifica ricerca fotogramma chiave con rotellina mouse", - "Mouse wheel frame seek modifier key": "Tasto modifica ricerca fotogramma con rotellina mouse" + "Mouse wheel keyframe seek modifier key": "Tasto modifica per ricerca fotogramma chiave", + "Mouse wheel frame seek modifier key": "Tasto modifica per ricerca fotogramma"These changes make the translations more concise while maintaining clarity and consistency with the application's terminology.
locales/es/translation.json (1)
Line range hint
106-141: Suggestion for improvement on line 106, rest LGTM.The translations in this section are generally accurate and consistent. However, the translation for "Working dir set" on line 106 could be improved for consistency with other similar translations in the file.
Suggest changing line 106 from:
"Working dir set": "Conjunto de directorios de trabajo",to:
"Working dir set": "Carpeta de trabajo establecida",This suggestion aligns better with the translation of "Working directory" on line 141 and maintains consistency throughout the file.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (9)
- locales/de/translation.json (12 hunks)
- locales/es/translation.json (20 hunks)
- locales/it/translation.json (1 hunks)
- locales/ja/translation.json (4 hunks)
- locales/ru/translation.json (13 hunks)
- locales/sk/translation.json (1 hunks)
- locales/tr/translation.json (4 hunks)
- locales/vi/translation.json (1 hunks)
- locales/zh_Hans/translation.json (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (6)
- locales/de/translation.json
- locales/ja/translation.json
- locales/ru/translation.json
- locales/sk/translation.json
- locales/tr/translation.json
- locales/vi/translation.json
🧰 Additional context used
🔇 Additional comments (27)
locales/zh_Hans/translation.json (10)
932-933: Translation for black scene detection is accurate and consistent.The translations for the segment modes related to black scene detection are accurate and maintain consistency with the previous translations for silent scene detection. The use of "黑色段" (black sections) is appropriate in this context.
934-935: Accurate translation for key binding conflict.The translation for the key binding conflict message is accurate and natural in Chinese. It correctly conveys the meaning of the original English text and provides a clear question for the user.
936-939: Consistent error message translations.The translations for various error messages (configuration file, URL download failure, project import failure, track inclusion failure, and subtitle loading failure) are accurate and consistent with the style of previous error messages in the file.
940-942: Accurate translations for seek and replace actions.The translations for "Replace", "Seek one key frame", and "Seek one frame" are concise and accurate. They maintain consistency with existing translations related to seeking and navigation.
943-944: Clear translation of smart cut warning.The translation of the smart cut experimental feature warning is accurate and clearly conveys the message that it may not work for all files. The Chinese text maintains the cautionary tone of the original English message.
945-946: Accurate translation of FLAC cutting issue.The translation accurately describes the known issue with cutting FLAC files using FFmpeg. It correctly conveys that the file will be re-encoded losslessly but may result in slower export times. The technical terms are appropriately translated.
947-948: Clear explanation of audio track muxing issue.The translation effectively communicates the problem with muxing certain audio tracks into MP4 format and the automatic selection of MOV as the default output format. The technical terms "mux" and "MOV" are kept in English, which is appropriate in this context.
949-954: Accurate translations for various UI elements and options.The translations for "Minimum numeric padded length", mouse wheel modifier keys, "Preserve chapters", and metadata preservation options are accurate and consistent with the style of existing translations. The technical terms are appropriately translated or kept in English where necessary.
955-955: Clear translation for file name customization.The translation accurately conveys the ability to customize the merged file name using special variables. The Chinese text is natural and easy to understand.
932-955: Overall translation quality is excellent.After reviewing all the new translations added to the Chinese (Simplified) localization file, I can confirm that the quality is consistently high. The translator has done an excellent job in maintaining accuracy, consistency, and natural language use throughout the new additions. Key points:
- Technical terms are appropriately handled, either translated or kept in English when necessary.
- Error messages and warnings are clearly conveyed while maintaining the tone of the original text.
- UI element descriptions are accurate and consistent with existing translations.
- Complex concepts, such as the FLAC cutting issue and audio track muxing problem, are explained clearly in Chinese.
No significant issues or improvements are needed for these new translations.
locales/it/translation.json (8)
868-868: Translation is accurate and clearThe Italian translation for this string is correct and conveys the message accurately. No changes are needed.
869-869: Translation is correctThe translation "File configurazione" for "Configuration file" is accurate and concise. No changes are needed.
870-873: Translations are accurate and consistentThe translations for these error messages are correct and consistent with the overall style of the application. They accurately convey the meaning of the original English text.
875-878: Translations are accurate and conciseThese translations are correct and maintain consistency with the application's terminology. No changes are needed.
879-882: Translations are accurate and clearThese translations accurately convey the meaning of the original English text and are clear in Italian. No changes are needed.
884-884: Translation is accurate and clearThe Italian translation for this technical message is correct and conveys the information accurately. No changes are needed.
887-887: Translation is accurate and clearThe Italian translation for this error message is correct and conveys the information accurately. No changes are needed.
888-888: Translation is correct and clearThe Italian translation for this instruction is accurate and clear. No changes are needed.
locales/es/translation.json (9)
20-27: LGTM! New and modified translations are accurate.The new and modified translations in this section are accurate and consistent with their English counterparts. The syntax is correct, and the translations maintain the intended meaning.
32-33: LGTM! New translations are concise and accurate.The new translations for "Shortest" and "Longest" are concise, accurate, and maintain the intended meaning.
41-48: LGTM with a note on the English source text.The translations in this section are accurate and consistent. However, there's a typo in the English source text of line 44 where "already" is repeated. This doesn't affect the Spanish translation, which is correct.
78-84: LGTM! New translations accurately convey technical information.The new translations in this section accurately convey the technical information about timestamp shifting and various options. The language used is appropriate and consistent with the rest of the translations.
94-97: LGTM! Modified translations are accurate and consistent.The modified translations in this section accurately reflect the English versions. They maintain consistency with the rest of the translations and correctly convey information about saving output files and conversion options.
231-235: LGTM! New translations are accurate and consistent.The new translations in this section accurately reflect the English versions. They maintain consistency with the rest of the translations and correctly convey information about working directory status, muting preview, and rotation preview.
258-270: LGTM! Error messages and notifications accurately translated.The new translations in this section accurately convey the meaning of various error messages and notifications. The language used is appropriate and consistent with the rest of the translations, maintaining the intended tone and information of the original messages.
292-308: LGTM! Technical information accurately translated.The new translations in this section accurately convey technical information about playback issues, file compatibility, and various UI messages. The translations maintain the intended meaning and use appropriate technical terminology consistent with the rest of the file.
Line range hint
320-906: LGTM! Large number of new translations added.This extensive section introduces a significant number of new translations for various features and UI elements. Upon review, the translations appear to be consistent with the established style and accurate in conveying the meaning of the English source text. Due to the volume of new entries, a detailed line-by-line review wasn't feasible, but the overall quality and consistency seem to be maintained.
To ensure the quality of these numerous new translations, it would be beneficial to have a native Spanish speaker or professional translator review this section in detail. Additionally, it's recommended to test the application with these new translations to verify their appropriateness in context.
weblate
force-pushed
the
weblate-losslesscut-losslesscut
branch
from
4113bca
to
83923fd
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (3)
locales/sk/translation.json (3)
758-758: Consider a more concise translationWhile the current translation is accurate, it could be made more concise. Consider:
- "Mouse wheel keyframe seek modifier key": "Hľadanie kľúčového snímku kolieska myši pomocou modifikátora", + "Mouse wheel keyframe seek modifier key": "Modifikátor hľadania kľúčových snímkov kolieskom myši",This suggestion maintains the meaning while being more compact and easier to read.
759-761: Translations are good, with a minor suggestionThe translations for "Non-global" and "None" are accurate and concise. For consistency with the previous suggestion, consider modifying the last line:
"Non-global": "Iné ako globálne", "None": "Žiadne", - "Mouse wheel frame seek modifier key": "Modifikačné tlačidlo hľadania snímky kolieska myši", + "Mouse wheel frame seek modifier key": "Modifikátor hľadania snímok kolieskom myši",This change makes the translation more consistent with the previous suggestion and slightly more concise.
762-778: Translations are generally good, with a few suggestions for improvementThe translations in this section are mostly accurate and well-formatted. However, there are a few minor suggestions for improvement:
Line 767: Consider a more natural word order:
- "Smart cut is experimental and will not work on all files.": "Inteligentný rez je experimentálny a nebude fungovať na všetkých súboroch.", + "Smart cut is experimental and will not work on all files.": "Inteligentný rez je experimentálny a nebude fungovať so všetkými súbormi.",Line 769: The translation could be more concise:
- "You are not allowed to write the output file. This probably means that the file already exists with the wrong permissions, or you don't have write permissions to the output folder.": "Nie je povolené zapisovať do výstupného súboru. Pravdepodobne to znamená, že súbor už existuje s nesprávnymi právami alebo nemáte práva na zápis do výstupného priečinka.", + "You are not allowed to write the output file. This probably means that the file already exists with the wrong permissions, or you don't have write permissions to the output folder.": "Nemáte povolenie na zápis do výstupného súboru. Pravdepodobne súbor už existuje s nesprávnymi oprávneniami, alebo nemáte práva na zápis do výstupného priečinka.",Line 776: The translation could be clearer:
- "Whether to preserve metadata from source file. Default: Global (file metadata), per-track and per-chapter metadata will be copied. Non-global: Only per-track and per-chapter metadata will be copied. None: No metadata will be copied": "Zachovanie metadát zo zdrojového súboru. Predvolené nastavenie: (metadáta súboru), metadáta na stopu a na kapitolu sa skopírujú. Iné ako globálne: Skopírujú sa len metadáta na stopu a na kapitolu. Žiadne: Nebudú sa kopírovať žiadne metadáta", + "Whether to preserve metadata from source file. Default: Global (file metadata), per-track and per-chapter metadata will be copied. Non-global: Only per-track and per-chapter metadata will be copied. None: No metadata will be copied": "Či zachovať metadáta zo zdrojového súboru. Predvolené: Globálne (metadáta súboru), metadáta pre stopu a kapitolu budú skopírované. Neglobálne: Skopírujú sa len metadáta pre stopu a kapitolu. Žiadne: Nebudú sa kopírovať žiadne metadáta",The rest of the translations in this section are accurate and well-formatted.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (9)
- locales/de/translation.json (12 hunks)
- locales/es/translation.json (20 hunks)
- locales/it/translation.json (1 hunks)
- locales/ja/translation.json (4 hunks)
- locales/ru/translation.json (13 hunks)
- locales/sk/translation.json (1 hunks)
- locales/tr/translation.json (4 hunks)
- locales/vi/translation.json (1 hunks)
- locales/zh_Hans/translation.json (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (6)
- locales/de/translation.json
- locales/es/translation.json
- locales/ja/translation.json
- locales/ru/translation.json
- locales/tr/translation.json
- locales/vi/translation.json
🧰 Additional context used
🔇 Additional comments (15)
locales/zh_Hans/translation.json (11)
933-933: LGTM: Accurate translation for key binding conflictThe translation "组合已被绑定到 {{alreadyBoundKey}} 。您想替换已有的绑定吗？" accurately conveys the meaning of the original message about a key combination already being bound. It's natural in Chinese and correctly uses the placeholder for the already bound key.
934-934: LGTM: Correct translation for "Configuration file"The translation "配置文件" for "Configuration file" is accurate and widely used in Chinese software interfaces. It clearly conveys the concept of a configuration file to Chinese users.
935-935: LGTM: Clear and concise error message translationThe translation "下载网址失败" for "Failed to download URL" is accurate, concise, and effectively communicates the error to Chinese users. It maintains the brevity of the original message while clearly stating the nature of the failure.
942-942: LGTM: Accurate warning translation for experimental featureThe translation "智能切割是实验性功能，无法在所有文件上正常工作。" for "Smart cut is experimental and will not work on all files." accurately conveys both the experimental nature of the feature and its limitations. It effectively warns Chinese users about potential issues they might encounter.
943-943: LGTM: Comprehensive translation of FLAC cutting issueThe translation "FFmpeg 切割 FLAC 文件有一个已知问题。文件将会被重新编码，仍然是无损的，但导出会变慢。" accurately conveys the known issue with cutting FLAC files. It correctly explains that the file will be re-encoded, maintains lossless quality, but may result in slower export. The technical terms "FFmpeg" and "FLAC" are appropriately kept in their original form.
944-944: LGTM: Clear translation of audio muxing issueThe translation "此文件包含一个 FFmpeg 无法嵌入到 MP4 格式的音轨，所以自动选择 MOVE 作为默认输出格式。" accurately describes the issue with FFmpeg being unable to mux an audio track into MP4 format. It clearly explains the automatic selection of MOV as the default output format. The technical terms are appropriately maintained, and the overall message is easy for Chinese users to understand.
945-945: LGTM: Concise translation of chapter preservation optionThe translation "是否保留源文件中的章节。" for "Whether to preserve chapters from source file." is accurate and concise. It clearly communicates the option to preserve chapters from the source file to Chinese users.
946-946: LGTM: Comprehensive translation of write permission errorThe translation "不允许您写入输出文件。这可能是因为现有文件有错误的许可权限，或者您没有输出文件夹的写入许可权限。" accurately conveys the error message about lacking write permissions. It clearly explains both possible reasons: existing files with incorrect permissions or lack of write permissions for the output folder. The message is easy for Chinese users to understand and provides helpful troubleshooting information.
953-953: LGTM: Accurate translation for "Preserve metadata"The translation "保留元数据" for "Preserve metadata" is accurate and commonly used in Chinese software interfaces. It clearly conveys the concept of preserving metadata to Chinese users.
954-954: LGTM: Comprehensive translation of metadata preservation optionsThe translation "是否保留源文件中的元数据。默认值：全局（文件元数据），复制每个轨道和每个章节的元数据。非全局：仅复制每个轨道和每个章节的元数据。无：不复制元数据" accurately conveys the detailed description of metadata preservation options. It clearly explains the three options (Default, Non-global, None) and what metadata is preserved in each case. The technical terms are correctly translated, and the overall explanation is easy for Chinese users to understand.
Line range hint
1-955: Overall assessment: High-quality Chinese translationsAfter reviewing the new and modified translations in this file, I can confirm that they are of high quality. The translations accurately convey the meaning of the original English text, use appropriate technical terms, and maintain consistency in terminology and style. They are well-suited for a Chinese user interface of a video editing application.
Key strengths:
- Accurate translation of technical concepts and error messages
- Consistent use of software-related terminology
- Clear and natural Chinese language that's easy for users to understand
- Proper handling of placeholders and variables
No significant issues were found, and all reviewed translations are approved.
locales/sk/translation.json (3)
756-757: Translation looks good!The Slovak translation accurately conveys the original message, maintaining the structure and HTML-like tags. The grammar and terminology are appropriate for the target language.
779-779: Excellent translationThe Slovak translation for this line is accurate, concise, and maintains the meaning of the original text. It uses appropriate terminology and is grammatically correct.
756-779: Overall, the translations are of good qualityThe Slovak translations in this file are generally accurate, maintaining the meaning of the original text and using appropriate terminology. A few minor suggestions were made for improved clarity, conciseness, and consistency. These small adjustments will enhance the overall quality of the localization.
Great job on the translation work! The suggested tweaks are minor and the translations will serve the Slovak-speaking users of LosslessCut well.
locales/it/translation.json (1)
867-890: Excellent additions to the Italian translations!The new translations are well-crafted and accurately convey the meaning of the original English text. They maintain consistency with Italian language conventions while appropriately preserving technical terms. The translations will greatly improve the user experience for Italian-speaking users of LosslessCut.
Some notable points:
- Technical terms like "FFmpeg", "FLAC", "MP4", and "MOV" are correctly left untranslated.
- Complex concepts such as metadata preservation and chapter handling are clearly explained.
- The translations for error messages and warnings are precise and informative.
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/ru/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/zh_Hans/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/ru/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/ru/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/ru/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/it/
Currently translated at 91.4% (699 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 91.4% (699 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 92.4% (706 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 92.4% (706 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 99.0% (757 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/ja/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/ja/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/sk/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 97.9% (748 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/de/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/es/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/de/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/de/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/de/
Currently translated at 95.0% (726 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/vi/
Currently translated at 100.0% (764 of 764 strings) Translation: LosslessCut/LosslessCut Translate-URL: https://hosted.weblate.org/projects/losslesscut/losslesscut/de/
weblate
force-pushed
the
weblate-losslesscut-losslesscut
branch
from
83923fd
to
ab5b76e
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Outside diff range and nitpick comments (7)
locales/ja/translation.json (1)
900-900: Accurate translation with a slight nuance change.The Japanese translation "トラックをまとめるのに失敗" for "Failed to include track" effectively conveys the meaning. However, a more direct translation might be "トラックを含めるのに失敗" to better match the original "include" nuance.
Consider changing "まとめる" to "含める" for a more direct translation:
-"Failed to include track": "トラックをまとめるのに失敗", +"Failed to include track": "トラックを含めるのに失敗",locales/sk/translation.json (1)
756-757: Ensure consistency in translation of technical terms.The translation for "GitHub discussions" is kept in English, which is good for clarity. However, consider standardizing the approach for technical terms across all translations.
locales/es/translation.json (5)
78-81: Accurate translations with a suggestion for readabilityThe translations are accurate and maintain the technical terminology well:
- Line 78 correctly translates the concept of shifting timestamps and appropriately translates "LosslessCut" as "Corte sin pérdidas".
- Line 81 accurately conveys the detailed explanation of "keyframe cut" and "Normal cut".
For improved readability of the long string in line 81, consider adding line breaks:
-"With \"keyframe cut\", we will cut at the nearest keyframe before the desired start cutpoint. This is recommended for most files. With \"Normal cut\" you may have to manually set the cutpoint a few frames before the next keyframe to achieve a precise cut": "Con \"corte de fotogramas clave\", cortaremos en el fotograma clave más cercano antes del punto de corte de inicio deseado. Esto se recomienda para la mayoría de los archivos. Con \"corte normal\" puede que tenga que establecer manualmente el punto de corte unos fotogramas antes del siguiente fotograma clave para conseguir un corte preciso" +"With \"keyframe cut\", we will cut at the nearest keyframe before the desired start cutpoint. This is recommended for most files. With \"Normal cut\" you may have to manually set the cutpoint a few frames before the next keyframe to achieve a precise cut": "Con \"corte de fotogramas clave\", cortaremos en el fotograma clave más cercano antes del punto de corte de inicio deseado. Esto se recomienda para la mayoría de los archivos.\nCon \"corte normal\" puede que tenga que establecer manualmente el punto de corte unos fotogramas antes del siguiente fotograma clave para conseguir un corte preciso"This change doesn't affect the functionality but improves readability in the code.
128-132: Accurate translations with a note on terminology changeThe translations in this segment are accurate and consistent:
- "Keep?" is correctly translated as "Mantener"
- "File info" and "Stream info" are appropriately translated
- "Current setting" is accurately rendered in Spanish
These translations effectively convey the meaning of the original English text and maintain consistency with the rest of the file.
Note the change in terminology for "Settings":
-"Settings": "Configuración" +"Settings": "Ajustes"This change to "Ajustes" is also correct and commonly used in Spanish software interfaces. However, ensure this term is used consistently throughout the entire application to avoid confusion.
138-141: Accurate translations with a note on terminology consistencyThe translations in this segment are accurate and well-formulated:
- "Same directory as input file" is correctly translated as "Misma carpeta que el archivo de entrada"
- "Custom working directory" is appropriately rendered as "Carpeta de trabajo personalizada"
- "Working directory" is translated as "Carpeta de trabajo"
These translations effectively convey the meaning of the original English text.
Note the inconsistency in the translation of "Working directory":
- Line 141: "Working directory" → "Carpeta de trabajo"
- Line 106 (previously reviewed): "Working dir set" → "Conjunto de directorios de trabajo"
For consistency, consider aligning these translations. The term "Carpeta de trabajo" used here is more common and accurate. Consider updating line 106 to use a similar term for consistency across the application.
Line range hint
205-231: Accurate translations with well-rendered technical termsThe translations in this segment are accurate and maintain consistency with the rest of the file:
- UI elements, settings, and actions are correctly translated, preserving their original meaning.
- The style is appropriate for a software interface in Spanish.
Notably good translations of technical terms include:
- "Preserve all MP4/MOV metadata?" → "Conservar todos los metadatos MP4/MOV?"
- "Keyframe cut" → "Corte de fotograma clave"
- "Export+merge" → "Exportar+fusionar"
These translations effectively balance technical accuracy with clarity for Spanish-speaking users. The consistent use of terms like "exportar", "fusionar", and "fotograma clave" contributes to a coherent user experience.
Minor suggestion: Consider adding a space before the question mark in Spanish questions, as it's a common practice in formal writing. For example:
-"Conservar todos los metadatos MP4/MOV?" +"Conservar todos los metadatos MP4/MOV ?"This is a stylistic choice and doesn't affect the meaning or clarity of the translations.
292-304: Accurate translations with a suggestion for improved clarityThe translations in this segment are generally accurate and maintain the technical nature of the original text:
- Complex technical concepts are well-translated, preserving their meaning and intent.
- The style is consistent with other translations in the file.
- Technical terms are appropriately rendered in Spanish.
Particularly good translations include:
- The explanation of file compatibility issues (lines 292-293)
- The description of keyframe cutting behavior (lines 294-295)
For improved clarity, consider breaking down the long sentence in lines 292-293:
-"File not natively supported. Preview may have no audio or low quality. The final export will however be lossless with audio. You may convert it from the menu for a better preview with audio.": "Archivo no compatible de forma nativa. Es posible que la vista previa no tenga audio o sea de baja calidad. Sin embargo, la exportación final no tendrá pérdidas con audio. Puede convertirlo desde el menú para una mejor vista previa con audio." +"File not natively supported. Preview may have no audio or low quality. The final export will however be lossless with audio. You may convert it from the menu for a better preview with audio.": "Archivo no compatible de forma nativa. Es posible que la vista previa no tenga audio o sea de baja calidad. Sin embargo, la exportación final será sin pérdidas y con audio. Para obtener una mejor vista previa con audio, puede convertir el archivo desde el menú."This suggestion maintains the meaning while slightly restructuring the sentence for better flow in Spanish.
Overall, these translations effectively communicate complex technical information to Spanish-speaking users.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (9)
- locales/de/translation.json (12 hunks)
- locales/es/translation.json (20 hunks)
- locales/it/translation.json (1 hunks)
- locales/ja/translation.json (4 hunks)
- locales/ru/translation.json (13 hunks)
- locales/sk/translation.json (1 hunks)
- locales/tr/translation.json (4 hunks)
- locales/vi/translation.json (1 hunks)
- locales/zh_Hans/translation.json (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (4)
- locales/ru/translation.json
- locales/tr/translation.json
- locales/vi/translation.json
- locales/zh_Hans/translation.json
🧰 Additional context used
🔇 Additional comments (37)
locales/ja/translation.json (10)
Line range hint
1-918: JSON structure is valid and well-formatted.The overall structure of the JSON file is correct. All key-value pairs are properly formatted with appropriate quotation marks and commas.
237-237: Translation is accurate and natural.The Japanese translation "ファイルの再生時間が正しくないです。問題の原因になることがあります。メニューから動画の長さを修正してください" accurately conveys the meaning of the original English text while adapting it to sound natural in Japanese.
241-241: Concise and accurate translation.The Japanese translation "該当するセグメントはありません" is a concise and accurate representation of "No valid segments found". It maintains the meaning while sounding natural in Japanese.
893-893: Clear and contextual translation.The Japanese translation "URLからダウンロード中" for "Downloading URL" is excellent. It adds appropriate context by specifying "から" (from), which makes the meaning clearer in Japanese.
809-809: Natural and accurate translation.The Japanese translation "キーの組み合わせが重複" for "Duplicate keyboard combination" is well done. It restructures the phrase to sound more natural in Japanese while maintaining the original meaning.
896-896: Standard and accurate term used.The Japanese translation "設定ファイル" for "Configuration file" uses the standard and widely recognized term in Japanese software localization.
899-899: Clear and contextual error message.The Japanese translation "URLからのダウンロードに失敗" for "Failed to download URL" is excellent. It clearly conveys the failure to download and maintains the context of the URL, using a natural Japanese sentence structure.
901-901: Accurate translation with correct variable usage.The Japanese translation "トラック{{index}}からの字幕の読み込みに失敗" for "Failed to load subtitles from track {{index}}" is excellent. It accurately conveys the meaning, maintains the correct word order for Japanese, and properly includes the {{index}} variable.
914-914: Accurate and technical translation.The Japanese translation "メタデータを保持" for "Preserve metadata" is correct and uses appropriate technical terminology. It accurately conveys the concept of preserving metadata in a concise manner.
Line range hint
1-918: Overall high-quality translations.The Japanese translations in this file are generally of high quality. They accurately convey the meanings of the original English text while adapting to natural Japanese expressions. Technical terms are consistently translated, and the style is appropriate for a software application, balancing formality and clarity.
locales/sk/translation.json (7)
Line range hint
1-755: LGTM: Existing translations appear correct and consistent.The existing translations in this section seem to be correct and consistent with the English versions. The JSON structure is valid, and placeholders are properly maintained.
758-760: Verify translation accuracy for technical terms.The translations for "Mouse wheel keyframe seek modifier key" and "Non-global" seem accurate, but it's important to ensure these technical terms are consistently translated across the entire application.
761-767: Check for consistency in UI element translations.The translations for UI elements like "Preserve chapters", "Preserve metadata", and "Replace" appear correct. Ensure these terms are used consistently throughout the application's Slovak version.
768-769: Verify accuracy of error message translation.The translation of the error message about writing permissions seems accurate and clear. It's crucial that error messages convey the correct information to users.
770-775: Ensure consistency in error message translations.The translations for various error messages and configuration-related terms appear correct. Maintain consistency in how these types of messages are phrased across the application.
776-779: Review technical explanations for accuracy.The translations for technical explanations about metadata preservation, FLAC file cutting issues, and audio track muxing seem accurate. It's important to ensure that these technical details are conveyed correctly to Slovak users.
Line range hint
1-779: Overall, the Slovak translations are well-implemented and consistent.The new additions to the Slovak translation file for LosslessCut are comprehensive and appear to be accurately translated. The JSON structure is valid, and placeholders are correctly maintained. The translations seem to convey technical information clearly while maintaining consistency with existing content.
A few minor points to consider:
- Ensure consistent translation of technical terms across the entire application.
- Double-check that UI element translations are used uniformly throughout the Slovak version.
- Verify that error messages and technical explanations are clear and accurate for Slovak users.
These additions will significantly improve the user experience for Slovak-speaking users of LosslessCut.
locales/it/translation.json (5)
867-870: New translations addedThese lines introduce new Italian translations for various UI elements and messages. The translations appear to be accurate and consistent with the English versions mentioned in the AI summary.
871-878: Translations for error messages and options look goodThese new translations for error messages and configuration options are clear and accurately convey the meaning of the original English text.
879-886: UI action and informational message translations are accurateThe translations for UI actions and informational messages in these lines are well-crafted. They maintain the technical terminology and accurately convey the meaning of the original English text.
887-890: Error message and mouse action translations are well-doneThe translations for the error message and mouse wheel actions are clear and accurately represent the original English text. They maintain the technical nature of the content while being understandable in Italian.
867-890: Overall translation quality is excellentThe new Italian translations added to this file are of high quality. They accurately represent the original English text, maintain consistency in terminology, and effectively convey technical concepts. These additions will significantly improve the user experience for Italian-speaking users of the LosslessCut application.
locales/es/translation.json (13)
20-22: Translations improved and accurateThe changes in these lines are improvements to the existing translations:
- Line 20: The translation is accurate and consistent with the existing style.
- Line 22: The translation has been refined to "Formato de las capturas de instantáneas", which is more natural and accurate in Spanish.
32-33: Accurate and consistent translationsThe translations for "Shortest" and "Longest" are accurate and appropriate in the context of duration:
- "Shortest" translated as "Más breve"
- "Longest" translated as "Más larga"
These translations maintain the comparative nature of the original terms and are consistent with Spanish usage for describing durations.
46-48: Accurate and consistent translationsThe translations for these lines are accurate and well-formulated:
- Line 46 correctly translates the concept of importing chapters from an opened file.
- Line 48 accurately conveys the idea of asking for confirmation when closing the app or a file.
Both translations maintain the question format and are consistent with the style used throughout the file.
Line range hint
84-89: Accurate and consistent translationsThe translations in this segment are accurate and well-formulated:
- Error messages are correctly translated, maintaining their original meaning.
- Instructions are clearly conveyed in Spanish.
- The translations are consistent with the style used throughout the file.
- There are no issues with grammar or vocabulary.
These translations will effectively communicate error messages and instructions to Spanish-speaking users.
94-97: Accurate translations of file operations and technical descriptionsThe translations in this segment are accurate and well-formulated:
- Lines 94-95 correctly translate the prompt for choosing an output file location.
- Line 97 accurately conveys the technical description of conversion options, maintaining the meaning and tone of the original text.
The translations appropriately use technical terms and are consistent with the style of other translations in the file. They will effectively communicate these options to Spanish-speaking users.
Line range hint
159-166: Accurate and consistent translations of UI elements and actionsThe translations in this segment are accurate and well-formulated:
- "Include all tracks?" is correctly translated as "Incluir todas las pistas"
- "Please select files to be merged" is appropriately rendered in Spanish
- "Merge!" is effectively translated as "¡Unir!"
- Other UI elements and actions are accurately translated, maintaining their original meaning
The translations use appropriate technical terms (e.g., "pistas" for "tracks") and are consistent with the style used throughout the file. They will effectively communicate these UI elements and actions to Spanish-speaking users.
234-235: Accurate and consistent translationsThe translations in this segment are accurate and well-formulated:
Line 234: "Mute preview? (will not affect output)" is correctly translated as "¿Silenciar la vista previa (no afectará la salida)?"
- The question format is maintained.
- The technical term "preview" is appropriately translated as "vista previa".
- The parenthetical note is accurately preserved.
Line 235: "Rotation preview" is correctly translated as "Rotación de la vista previa"
- This translation maintains consistency with the use of "vista previa" for "preview".
These translations effectively convey the meaning of the original English text and are consistent with the style used throughout the file. They will clearly communicate these options to Spanish-speaking users.
258-270: Accurate translations of error messages and notificationsThe translations in this segment are accurate and effectively convey the meaning of the original English text:
Error messages are clearly translated, maintaining their original intent and severity. For example:
- "Failed to convert file. Try a different conversion" → "No se pudo convertir el archivo. Intente una conversión diferente."
- "Failed to load segments" → "No se pudieron cargar los segmentos"
Technical terms are appropriately translated:
- "convert" → "convertir"
- "segments" → "segmentos"
The style is consistent with other translations in the file, using a formal yet clear Spanish that's appropriate for software interfaces.
Notifications and warnings are well-translated, preserving their informational nature. For example:
- "The audio track is not supported. You can convert to a supported format from the menu" → "La pista de audio no es compatible. La puede convertir a un formato compatible desde el menú."
These translations will effectively communicate error states, warnings, and instructions to Spanish-speaking users, maintaining the user-friendly nature of the application.
Line range hint
320-330: Accurate translations with well-rendered technical termsThe translations in this segment are accurate and effectively convey the meaning of the original English text:
- UI elements and settings are correctly translated, preserving their original meaning and function.
- The style is consistent with other translations in the file, using clear and appropriate Spanish for a software interface.
Notably well-translated technical terms include:
- "Auto load timecode" → "Cargar automáticamente el código de tiempo"
- "Auto delete segments" → "Borrar automáticamente los segmentos"
- "Merge/concatenate files" → "Fusionar/concatenar archivos"
- "Enable MOV Faststart?" → "Habilitar el inicio rápido de MOV"
These translations strike a good balance between technical accuracy and clarity for Spanish-speaking users. The consistent use of terms like "código de tiempo", "segmentos", and "fusionar" contributes to a coherent user experience.
The translations in this segment will effectively communicate these options and settings to Spanish-speaking users of the application.
337-340: Accurate translations effectively conveying technical conceptsThe translations in this segment are accurate and successfully communicate complex technical options:
The option to preserve metadata when merging is well-translated:
- "When merging, do you want to preserve metadata from your original file? NOTE: This may dramatically increase processing time"
→ "Al fusionar, ¿desea conservar los metadatos del archivo original? NOTA: Esto puede aumentar drásticamente el tiempo de procesamiento"The option to create chapters from cut segments is accurately rendered:
- "When merging, do you want to create chapters in the merged file, according to the cut segments? NOTE: This may dramatically increase processing time"
→ "Al fusionar, ¿desea crear capítulos en el archivo fusionado, según los segmentos cortados? NOTA: Esto puede aumentar drásticamente el tiempo de procesamiento"The explanation about MOV/MP4 Faststart is correctly translated:
- "Enable this to allow faster playback of the resulting file. This may cause processing to take a little longer"
→ "Habilite esta opción para permitir una reproducción más rápida del archivo resultante. Esto puede hacer que el procesamiento tarde un poco más"These translations effectively:
- Maintain the technical accuracy of the original text
- Preserve the warning about increased processing time
- Use appropriate Spanish terminology for concepts like "metadata" (metadatos), "merging" (fusionar), and "chapters" (capítulos)
The translations will clearly communicate these advanced options to Spanish-speaking users, helping them make informed decisions about file processing.
347-355: Accurate translations with clear presentation of file cleanup optionsThe translations in this segment are accurate and effectively communicate various file operation and cleanup options:
File cleanup options are clearly presented:
- "Trash original source file, project CSV and auto-generated files" → "Papelera de archivos originales, CSV del proyecto y archivos autogenerados"
- "Trash project CSV and auto-generated files" → "Papelera de archivos CSV y autogenerados del proyecto"
- "Trash auto-generated files" → "Papelera de archivos autogenerados"
UI elements and prompts are well-translated:
- "Cleanup files?" → "Limpiar archivos"
- "Extract all tracks" → "Extraer todas las pistas"
- "Please confirm that you want to extract all tracks as separate files" → "Por favor, confirme que desea extraer todas las pistas como archivos separados"
Technical terms are appropriately rendered in Spanish:
- "tracks" → "pistas"
- "CSV" is maintained as is, which is correct in Spanish technical contexts
The translation maintains a consistent style with the rest of the file, using clear and concise Spanish suitable for a software interface.
These translations will effectively guide Spanish-speaking users through file cleanup processes and track extraction options, maintaining the user-friendly nature of the application.
374-375: Clear and accurate translations for view mode togglesThe translations in this segment effectively communicate the switching between advanced and simple view modes:
Disabling advanced view:
- "Advanced view disabled. You will now see only the most essential buttons and functions"
→ "Vista avanzada desactivada. Ahora solo verá los botones y funciones más esenciales."Enabling advanced view:
- "Advanced view has been enabled. You will now also see non-essential buttons and functions"
→ "Se ha activ
41-44:⚠️ Potential issueAccurate translations with a note on English source
The Spanish translations are accurate and clear. However, there's an issue with the English source text:
There's a typo in the English source on line 44:
-"Ask about what to do when opening a new file when another file is already already open?": "Preguntar qué hacer al abrir un nuevo archivo cuando ya hay otro abierto" +"Ask about what to do when opening a new file when another file is already open?": "Preguntar qué hacer al abrir un nuevo archivo cuando ya hay otro abierto"The word "already" is repeated in the English text. The Spanish translation is correct and doesn't reflect this error.
The Spanish translations for both lines are accurate and well-formulated.
Likely invalid or redundant comment.
locales/de/translation.json (2)
Line range hint
197-930: Overall translation quality is goodThe new translations added to this file are generally accurate and appropriate. There's only one minor issue:
- Line 916: A typo in the German word "Spun" which should be "Spur".
Other than that, the translations maintain consistency with the existing text and accurately convey the meaning of the original English phrases.
916-916:⚠️ Potential issueCorrect the typo in the German translation
There's a typo in the German translation. "Spun" should be "Spur".
Please update the translation as follows:
-"Failed to include track": "Spun einfügen fehlgeschlagen" +"Failed to include track": "Spur einfügen fehlgeschlagen"Likely invalid or redundant comment.
| "Auto save project file?": "Guardar automáticamente el archivo del proyecto", | ||
| "Experimental flag": "Función experimental", | ||
| "Enable experimental ffmpeg features flag?": "¿Habilitar la función experimental de ffmpeg?", | ||
| "Enable experimental ffmpeg features flag?": "Habilitar la función experimental de ffmpeg", |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Suggestion for improvement on line 27
While the translations are generally accurate, there's room for improvement on line 27:
Consider changing the translation of "Enable experimental ffmpeg features flag?" to:
-"Enable experimental ffmpeg features flag?": "Habilitar la función experimental de ffmpeg"
+"Enable experimental ffmpeg features flag?": "¿Habilitar la bandera de funciones experimentales de ffmpeg?"This suggestion:
- Maintains the question format of the original English text.
- Uses "bandera" which is a more accurate translation for "flag" in this context.
- Keeps "funciones" in plural to match the English "features".
📝 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.
| "Auto save project file?": "Guardar automáticamente el archivo del proyecto", | |
| "Experimental flag": "Función experimental", | |
| "Enable experimental ffmpeg features flag?": "¿Habilitar la función experimental de ffmpeg?", | |
| "Enable experimental ffmpeg features flag?": "Habilitar la función experimental de ffmpeg", | |
| "Auto save project file?": "Guardar automáticamente el archivo del proyecto", | |
| "Experimental flag": "Función experimental", | |
| "Enable experimental ffmpeg features flag?": "¿Habilitar la bandera de funciones experimentales de ffmpeg?" |
| "Working dir set": "Conjunto de directorios de trabajo", | ||
| "Capture frame format": "Formato de fotogramas de captura", | ||
| "Timeline trackpad/wheel sensitivity": "Sensibilidad del trackpad/rueda de la línea de tiempo", | ||
| "YouTube video description\n00:00 Intro\n00:01 Chapter 2\n00:00:02.123 Chapter 3": "Descripción del video de YouTube\n00:00 Introducción\n00:01 Capítulo 2\n00:00:02.123 Capítulo 3", |
There was a problem hiding this comment.
Suggestion for improvement on line 106, other translations approved
The translation on line 106 could be improved:
-"Working dir set": "Conjunto de directorios de trabajo"
+"Working dir set": "Directorio de trabajo establecido"This suggestion:
- More accurately reflects the meaning of "set" in this context (established or configured).
- Uses "directorio" (singular) which is more common when referring to a working directory.
The translations on lines 107-109 are accurate and consistent:
- "Capture frame format" is correctly translated as "Formato de fotogramas de captura"
- "Timeline trackpad/wheel sensitivity" is well translated as "Sensibilidad del trackpad/rueda de la línea de tiempo"
- The YouTube video description example is appropriately maintained in its original format
These translations effectively convey the meaning of the original English text and maintain consistency with the rest of the file.
📝 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.
| "Working dir set": "Conjunto de directorios de trabajo", | |
| "Capture frame format": "Formato de fotogramas de captura", | |
| "Timeline trackpad/wheel sensitivity": "Sensibilidad del trackpad/rueda de la línea de tiempo", | |
| "YouTube video description\n00:00 Intro\n00:01 Chapter 2\n00:00:02.123 Chapter 3": "Descripción del video de YouTube\n00:00 Introducción\n00:01 Capítulo 2\n00:00:02.123 Capítulo 3", | |
| "Working dir set": "Directorio de trabajo establecido", | |
| "Capture frame format": "Formato de fotogramas de captura", | |
| "Timeline trackpad/wheel sensitivity": "Sensibilidad del trackpad/rueda de la línea de tiempo", | |
| "YouTube video description\n00:00 Intro\n00:01 Chapter 2\n00:00:02.123 Chapter 3": "Descripción del video de YouTube\n00:00 Introducción\n00:01 Capítulo 2\n00:00:02.123 Capítulo 3", |
Translations update from Hosted Weblate for LosslessCut/LosslessCut.
Current translation status:
Summary by CodeRabbit
New Features
Bug Fixes