Skip to content

chore: update translations#241

Merged
deepin-bot[bot] merged 2 commits intolinuxdeepin:masterfrom
Lighto-Ku:master
Jul 3, 2025
Merged

chore: update translations#241
deepin-bot[bot] merged 2 commits intolinuxdeepin:masterfrom
Lighto-Ku:master

Conversation

@Lighto-Ku
Copy link
Contributor

@Lighto-Ku Lighto-Ku commented Jul 3, 2025

as title

Log: update translations

Summary by Sourcery

Update and finalize translation entries across multiple locale files, removing unfinished markers and correcting translated strings in English (en_US) and Traditional Chinese (zh_HK, zh_TW).

Chores:

  • Remove "unfinished" markers and complete translations in en_US locale file
  • Align Arabic placeholders back to original English strings in en_US translations
  • Refine and correct Chinese translation strings in zh_HK locale file
  • Refine and correct Chinese translation strings in zh_TW locale file

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @Lighto-Ku - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@sourcery-ai
Copy link

sourcery-ai bot commented Jul 3, 2025

Reviewer's Guide

Updates translations for en_US, zh_HK, and zh_TW locales by marking entries as complete, aligning translations with source text, and correcting localized strings for AI search, model installation, and plugin contexts.

File-Level Changes

Change Details Files
Cleaned up English (US) translations
  • Removed type="unfinished" markers from translation elements
  • Aligned translations exactly with English source strings
  • Replaced Arabic placeholders with English text for several messages
translations/dde-grand-search_en_US.ts
Corrected zh_HK translations for intelligent search and plugins
  • Updated “Full Text Search” and related descriptions to accurate Chinese terms
  • Adjusted embedding plugin and ULLM model messages
  • Fixed llmwidget labels and button text translations
translations/dde-grand-search_zh_HK.ts
Corrected zh_TW translations for intelligent search and plugins
  • Refined “全文檢索” and plugin terminology in Traditional Chinese
  • Aligned ULLM descriptions with accurate phrasing
  • Fixed llmwidget prompts, labels, and button translations
translations/dde-grand-search_zh_TW.ts

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

as title

Log: update translations
update version

Log: update changelog
@github-actions
Copy link

github-actions bot commented Jul 3, 2025

TAG Bot

TAG: 6.0.19
EXISTED: no
DISTRIBUTION: unstable

@deepin-ci-robot
Copy link

deepin pr auto review

代码审查意见:

  1. 翻译更新:代码中已经更新了多个翻译,确保了不同语言版本的翻译更加准确和一致。建议在更新翻译时,确保所有相关的翻译都已经更新,并且与源代码保持一致。

  2. 注释和文档:代码中的注释应该更加详细,特别是对于复杂的逻辑和重要的功能,应该添加更多的注释来解释代码的意图和实现方式。此外,如果代码中有一些特定的配置或者依赖关系,应该在文档中明确说明。

  3. 代码风格:代码风格应该保持一致,例如缩进、空格和括号的使用等。在代码中,有些地方使用了中文注释,有些地方使用了英文注释,建议统一使用一种语言进行注释。

  4. 错误处理:代码中应该有适当的错误处理机制,例如在安装模型或者卸载模型时,如果出现错误,应该有相应的提示信息,并且能够记录错误日志,以便于后续的调试和问题追踪。

  5. 性能优化:如果代码中有一些性能瓶颈,应该进行优化,例如减少不必要的计算,使用更高效的数据结构等。

  6. 安全性:代码中应该有适当的安全措施,例如防止SQL注入、防止XSS攻击等。如果代码中涉及到用户输入,应该进行适当的验证和过滤。

  7. 测试:代码应该有充分的测试,包括单元测试、集成测试和性能测试等。测试应该覆盖所有重要的功能,并且能够及时发现和修复问题。

  8. 版本控制:在提交代码时,应该使用合适的版本控制策略,例如使用分支进行开发,使用标签进行发布等。这样可以确保代码的版本管理更加清晰和有序。

  9. 代码审查:代码应该经过适当的代码审查,包括同行审查和代码审查工具的自动审查等。这样可以确保代码的质量和一致性,并且能够及时发现和修复问题。

  10. 文档和帮助:代码应该有适当的文档和帮助,例如使用Doxygen生成文档,提供API文档等。这样可以方便其他开发者使用和理解代码,并且能够提高代码的可维护性。

@deepin-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Johnson-zs, Lighto-Ku

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@Johnson-zs
Copy link
Contributor

/forcemerge

@deepin-bot
Copy link

deepin-bot bot commented Jul 3, 2025

This pr force merged! (status: behind)

@deepin-bot deepin-bot bot merged commit 1fa2e17 into linuxdeepin:master Jul 3, 2025
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants