Add use openRuyi in QEMU/virt-manager

[panglars]

No description provided.

[misaka00251]

Please run npm run write-translations -- --locale zh-Hans once and check if there's any string you need to translate.

[KevinMX]

Overall content LGTM, however seems you're mixing half and full width marks, like , and ，, () and （）.

[KevinMX]

This only applies to those who do not have EDK2 firmware packaged with their distros of choice.

Better add a note here, e.g. "此小节仅适用于发行版没有打包 EDK2 固件的发行版，若创建虚拟机时 virt-manager 提示找不到 UEFI 二进制，则请按照以下步骤操作；若没有相关提示，可跳过这一节，virt-manager 会自动使用已安装的 UEFI 固件。"

[misaka00251]

Use this:

:::warning Header

Your content here.

:::

Please also change the English version.

[KevinMX]

Please run npm run write-translations -- --locale zh-Hans once and check if there's any string you need to translate.

Tried a local build on my side and overall LGTM. We could probably add a check to our CI?

[panglars]

Please run npm run write-translations -- --locale zh-Hans once and check if there's any string you need to translate.

fixed

[KevinMX]

LGTM, but please use rebase to get rid of the merge commit.

[misaka00251]

1. For images, use image-number-<shortdescription>.extension as the filename.
2. Please add a period at the end of each sentence in your Simplified Chinese version.

[misaka00251]

I noticed that in some mixed content, there is no blank space between Chinese and English characters. Please add one for better formatting.

[misaka00251]

Use this:

:::warning Header

Your content here.

:::

Please also change the English version.

[panglars]

I noticed that in some mixed content, there is no blank space between Chinese and English characters. Please add one for better formatting.

In 2026, we should manually enable CSS property text-autospace: normal; entire website, instead of manually insert spaces.

[misaka00251]

instead of manually insert spaces

I agree text-autospace can help the rendered website, but it doesn’t replace source quality. Since Docusaurus reads Markdown as the source of truth, the Markdown should be readable and correctly formatted by itself—in PR diffs, GitHub previews, editor previews, search, and any non-site output.

We can consider text-autospace as a progressive enhancement, but the PR should still add spaces between Chinese and English/numbers in the source.