[deepin-compressor] Updates for project Deepin Archive Manager

[transifex-integration]

The following localization files have been updated:

Details

Parameter	Value
Transifex Project	Deepin Archive Manager
Grouping	All Resources and Languages

Files

Source File	Translation File	Resource	Language	Type	Mode
translations/deepin-compressor.ts	translations/deepin-compressor_pt_BR.ts	translations/deepin-compressor.ts (master)	pt_BR	TRANSLATION	default

Summary by Sourcery

Documentation:

• Refresh and complete pt_BR translations for archive operations, error messages, dialogs, and settings in Deepin Archive Manager

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: transifex-integration[bot]

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

Details

Needs approval from an approver in each of these files:

• debian/deepin/OWNERS

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

[deepin-ci-robot]

Hi @transifex-integration[bot]. Thanks for your PR.

I'm waiting for a linuxdeepin member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sourcery-ai]

Reviewer's Guide

Updates the Brazilian Portuguese Qt translation file for Deepin Archive Manager, aligning terminology, filling previously unfinished strings, and adding/adjusting messages to match the current source code while preserving context and UI consistency.

File-Level Changes

Change	Details	Files
Normalize XML TS header formatting and closing tag style in the pt_BR translation file.	Condense XML declaration, DOCTYPE, and root element into a single line to match updated TS formatting output Remove trailing newline before closing to keep file consistent with generated format	translations/deepin-compressor_pt_BR.ts
Align CPU threading terminology and various archive operation status messages with the current English source strings.	Change translations of CPU-related options from core-based wording ("Núcleos") to thread-based wording ("threads") Refine several archive operation messages (compression, extraction, conversion, renaming, updating, file conflicts, damaged archives, permissions, and path issues) for accuracy and consistency with source semantics	translations/deepin-compressor_pt_BR.ts
Complete previously unfinished or missing translations and improve consistency of existing pt_BR strings across dialogs, main window, and progress pages.	Fill in missing translations such as "Rename", "Renaming", "Speed", "Select file", and various dialog labels (buttons like OK/Cancel/Replace/Skip/Merge, conflict prompts, and error messages) Standardize wording for recurring concepts (e.g., archive vs. compressed file, directory vs. folder, extraction/compression success and failure messages) Ensure all references to the app name and file operations match how they are presented elsewhere in the UI	translations/deepin-compressor_pt_BR.ts
Reorder some blocks to reflect the updated line numbers and structure of the corresponding C++ source files.	Move MainWindow-, popup dialog-, and setting dialog-related messages so that their order in the TS file matches the new source code line ordering Keep translations semantically equivalent while adjusting their position and associated metadata	translations/deepin-compressor_pt_BR.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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

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

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}