Skip to content

Conversation

@JWWTSL
Copy link
Contributor

@JWWTSL JWWTSL commented Aug 7, 2025

log: Translation update

Summary by Sourcery

Add comprehensive Lao translations for the application UI and desktop entry, and update the package version to 6.5.27.1.

New Features:

  • Add Lao locale translation for the deepin-draw application
  • Add Lao translations for the desktop entry of the application

Enhancements:

  • Bump deepin-draw package version to 6.5.27.1 across all architectures

@deepin-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: JWWTSL

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

@github-actions
Copy link

github-actions bot commented Aug 7, 2025

TAG Bot

TAG: 6.5.27
EXISTED: no
DISTRIBUTION: unstable

@deepin-ci-robot
Copy link

deepin pr auto review

代码审查意见:

  1. translations/deepin-draw_lo.ts文件中,<TS version="2.1" language="en" sourcelanguage="lo">中的sourcelanguage属性应该改为sourceLanguage,以符合XML标准。
  2. translations/deepin-draw_lo.ts文件中,<context>标签的<name>属性应该使用唯一的名称,以避免潜在的冲突。
  3. translations/deepin-draw_lo.ts文件中,<message>标签的<location>属性应该包含filenameline属性,以帮助定位消息的位置。
  4. translations/deepin-draw_lo.ts文件中,<message>标签的<source><translation>属性应该使用相同的语言,以保持一致性。
  5. translations/deepin-draw_lo.ts文件中,<message>标签的<source><translation>属性应该使用UTF-8编码,以支持多语言字符。
  6. translations/desktop/desktop_lo.ts文件中,<TS version="2.1" language="lo">中的language属性应该改为lang,以符合XML标准。
  7. translations/desktop/desktop_lo.ts文件中,<context>标签的<name>属性应该使用唯一的名称,以避免潜在的冲突。
  8. translations/desktop/desktop_lo.ts文件中,<message>标签的<location>属性应该包含filenameline属性,以帮助定位消息的位置。
  9. translations/desktop/desktop_lo.ts文件中,<message>标签的<source><translation>属性应该使用相同的语言,以保持一致性。
  10. translations/desktop/desktop_lo.ts文件中,<message>标签的<source><translation>属性应该使用UTF-8编码,以支持多语言字符。

以上是代码审查意见,希望能够帮助到您。

@sourcery-ai
Copy link

sourcery-ai bot commented Aug 7, 2025

Reviewer's Guide

This PR bumps the Deepin Draw package version and introduces Lao locale translation files for the application and desktop entry.

File-Level Changes

Change Details Files
Bump package version
  • Update version from 6.5.26.1 to 6.5.27.1
arm64/linglong.yaml
linglong.yaml
loong64/linglong.yaml
Add application Lao translations
  • Introduce deepin-draw_lo.ts containing ~1223 lines of translated UI strings
translations/deepin-draw_lo.ts
Add desktop entry Lao translations
  • Add desktop_lo.ts with translated desktop metadata
translations/desktop/desktop_lo.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

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 @JWWTSL - I've reviewed your changes - here's some feedback:

  • Please double-check that the version bump to 6.5.27.1 is applied consistently in all YAML files (arm64, linglong, loong64) to avoid packaging mismatches.
  • Consider running your translation update through lupdate (or equivalent) to remove obsolete entries and highlight any missing or changed source strings.
  • Verify that the desktop_lo.ts XML declarations and attributes conform to the Desktop Entry spec so the translations load correctly.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Please double-check that the version bump to 6.5.27.1 is applied consistently in all YAML files (arm64, linglong, loong64) to avoid packaging mismatches.
- Consider running your translation update through lupdate (or equivalent) to remove obsolete entries and highlight any missing or changed source strings.
- Verify that the desktop_lo.ts XML declarations and <location> attributes conform to the Desktop Entry spec so the translations load correctly.

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.

@lzwind lzwind merged commit 29db9c9 into linuxdeepin:develop/snipe Aug 7, 2025
15 of 16 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