Skip to content

Comments

fix: (docs)remove bold formatting from speech recognition headings#415

Merged
deepin-bot[bot] merged 1 commit intolinuxdeepin:masterfrom
pppanghu77:master
Jan 19, 2026
Merged

fix: (docs)remove bold formatting from speech recognition headings#415
deepin-bot[bot] merged 1 commit intolinuxdeepin:masterfrom
pppanghu77:master

Conversation

@pppanghu77
Copy link
Contributor

@pppanghu77 pppanghu77 commented Jan 19, 2026

  • Remove bold formatting (***) from "语音听写"/"語音聽寫" headings
  • Update Chinese (zh_CN) and Traditional Chinese (zh_TW) documentation files
  • Affects both d_editor.md and p_editor.md files in the editor component

Log: fix: (docs)remove bold formatting from speech recognition headings
Bug: https://pms.uniontech.com/bug-view-344909.html

Summary by Sourcery

Documentation:

  • Remove bold formatting from the speech recognition headings in Simplified and Traditional Chinese editor documentation for both desktop and phone variants.

- Remove bold formatting (***) from "语音听写"/"語音聽寫" headings
- Update Chinese (zh_CN) and Traditional Chinese (zh_TW) documentation files
- Affects both d_editor.md and p_editor.md files in the editor component

Log: fix: (docs)remove bold formatting from speech recognition headings
Bug: https://pms.uniontech.com/bug-view-344909.html
@sourcery-ai
Copy link

sourcery-ai bot commented Jan 19, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Removes bold markdown formatting from the "speech recognition" section headings in the Simplified and Traditional Chinese editor documentation so that the headings use standard level-3 heading syntax without inline bold.

File-Level Changes

Change Details Files
Normalize the speech recognition section headings in the Simplified Chinese editor documentation by removing redundant bold formatting from the level-3 headings.
  • Update the speech recognition section heading in the d_editor documentation to use a plain level-3 heading without inline bold markers.
  • Update the speech recognition section heading in the p_editor documentation to use a plain level-3 heading without inline bold markers.
src/assets/deepin-editor/editor/zh_CN/d_editor.md
src/assets/deepin-editor/editor/zh_CN/p_editor.md
Normalize the speech recognition section headings in the Traditional Chinese editor documentation by removing redundant bold formatting from the level-3 headings.
  • Update the speech recognition section heading in the d_editor documentation to use a plain level-3 heading without inline bold markers.
  • Update the speech recognition section heading in the p_editor documentation to use a plain level-3 heading without inline bold markers.
src/assets/deepin-editor/editor/zh_TW/d_editor.md
src/assets/deepin-editor/editor/zh_TW/p_editor.md

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

@deepin-ci-robot
Copy link

deepin pr auto review

代码审查报告

修改概述

本次修改主要涉及Markdown文档中标题格式的调整,具体是将"语音听写"(简体中文)和"語音聽寫"(繁体中文)三级标题从加粗格式(### **标题**)改为普通格式(### 标题)。

审查意见

1. 语法逻辑

  • 通过:Markdown语法正确。### 表示三级标题,修改后的格式符合Markdown标准语法,不会影响文档渲染效果。

2. 代码质量

  • ⚠️ 建议:虽然语法正确,但建议保持文档格式一致性。检查整个文档中其他三级标题是否也采用相同格式(不加粗),以保持文档风格统一。

3. 代码性能

  • 通过:Markdown文档的渲染性能不受此修改影响,因为加粗和不加粗的标题在渲染时处理方式相同。

4. 代码安全

  • 通过:此修改不涉及任何安全问题,仅是文档格式调整。

额外建议

  1. 文档一致性检查

    • 建议检查整个项目中所有Markdown文档,确保同级标题格式统一
    • 可以考虑使用Markdown linter工具(如markdownlint)自动检查文档格式一致性
  2. 文档规范

    • 建议制定项目文档的Markdown格式规范,明确各级标题是否需要加粗
    • 通常情况下,Markdown标题本身已经通过#数量表示层级,不需要额外加粗
  3. 版本控制

    • 修改涉及多个文件(简体中文和繁体中文版本),确保所有语言版本保持同步更新

总结

本次修改是正确的Markdown格式调整,不会影响文档功能和渲染效果。主要建议是保持整个文档的格式一致性,并考虑制定统一的文档格式规范。

@deepin-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: lzwind, pppanghu77

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

@pppanghu77
Copy link
Contributor Author

/forcemerge

@deepin-bot
Copy link
Contributor

deepin-bot bot commented Jan 19, 2026

This pr force merged! (status: unstable)

@deepin-bot deepin-bot bot merged commit 76e350f into linuxdeepin:master Jan 19, 2026
20 of 21 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