[PATCH v3 0/2] docs/zh_CN: translate process/applying-patches.rst into Chinese
Weijie Yuan <[email protected]>
| Newsgroups | org.kernel.vger.linux-doc,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
This series adds a Simplified Chinese translation of Documentation/process/applying-patches.rst. The first patch adds the translation and includes it in the zh_CN process toctree. Its :Original: field uses the original document path directly; no translation-specific reference label is introduced. _Changes in v3_ The second patch updates existing zh_CN references to point to the new translation. In ordinary paragraphs, the absolute Documentation/...rst path is used and is handled by automarkup. The entry in process/howto.rst is a definition-list term, which automarkup does not process. It therefore uses the named :doc: form as the minimal explicit-link exception, without reintroducing a cn_applying_patches label and using :ref:. RFC: I considered the two competing preferences for cross-references. Jon recommends using a plain absolute Documentation/...rst path, while another view (I found the discussion in 2021, so I added your email addresses, thanks.) is to avoid :doc: markup where automarkup can create the link automatically. I follow both rules where they apply: the plain path is used in normal paragraphs. However, this particular entry is a definition-list term, which automarkup does not process, so the plain path is rendered as text rather than a link. The named :doc: form is therefore used only for this narrow exception, without adding a translation-specific label. (Seems to be a workaround) I would welcome guidance on one stylistic point. (Since I missed previous discussions) The surrounding entries in this definition list use :ref:, while this new entry uses the named :doc: form because it links to a whole document without a translation-specific label. Does this look out of place here? If so, I am happy to follow the preferred cross-reference style. [Words are polished by LLM, but I think it's what I want to say] Thanks! Sorry Mauro, I don't know which address you'll prefer, so I add both. --- Changes in v3: - Deal with the ref style, see above - Link to v2: https://patch.msgid.link/[email protected] Changes in v2: - Merge first two patches into one. - Remove self-ref (.. _cn.rst) and changes ref style from 'ref' to direct file name - Link to v1: https://patch.msgid.link/[email protected] To: Mauro Carvalho Chehab <[email protected]> To: Mauro Carvalho Chehab <[email protected]> To: Nícolas F. R. A. Prado <[email protected]> To: Alex Shi <[email protected]> To: Yanteng Si <[email protected]> To: Dongliang Mu <[email protected]> To: Jonathan Corbet <[email protected]> To: Shuah Khan <[email protected]> Cc: [email protected] Cc: [email protected] --- Weijie Yuan (2): docs/zh_CN: add process/applying-patches Chinese translation docs/zh_CN: link to Chinese applying-patches translation .../translations/zh_CN/admin-guide/README.rst | 2 +- .../zh_CN/process/applying-patches.rst | 390 +++++++++++++++++++++ Documentation/translations/zh_CN/process/howto.rst | 2 +- Documentation/translations/zh_CN/process/index.rst | 2 +- 4 files changed, 393 insertions(+), 3 deletions(-) Range-diff versus v2: 1: 596ec00ba7c5 = 1: 13da5addcb90 docs/zh_CN: add process/applying-patches Chinese translation 2: b3a9c4893250 ! 2: 7c156c1d41b7 docs/zh_CN: link to Chinese applying-patches translation @@ Documentation/translations/zh_CN/admin-guide/README.rst: Linux内核6.x版本 <h 并且希望跳转到6.0.3,那么在应用6.0.3补丁之前,必须首先撤销6.0.2补丁 (即patch -R)。更多关于这方面的内容,请阅读 - :ref:`Documentation/process/applying-patches.rst <applying_patches>` 。 -+ :ref:`Documentation/translations/zh_CN/process/applying-patches.rst <cn_applying_patches>` 。 ++ Documentation/translations/zh_CN/process/applying-patches.rst 。 或者,脚本 patch-kernel 可以用来自动化这个过程。它能确定当前内核版本并 应用找到的所有补丁:: @@ Documentation/translations/zh_CN/process/howto.rst: Linux内核代码中包含 的内容,可以查看这些文档。 - :ref:`Documentation/process/applying-patches.rst <applying_patches>` -+ :ref:`Documentation/translations/zh_CN/process/applying-patches.rst <cn_applying_patches>` ++ :doc:`Documentation/translations/zh_CN/process/applying-patches.rst <applying-patches>` 关于补丁是什么以及如何将它打在不同内核开发分支上的好介绍 内核还拥有大量从代码自动生成或者从 ReStructuredText(ReST) 标记生成的文档, --- base-commit: 1a0364f09c1311dad5ad1ccba7e169a412f6b547 change-id: 20260815-apply-patches-601ad9b42f27