summaryrefslogtreecommitdiff
path: root/scripts/lib/kdoc/kdoc_files.py
diff options
context:
space:
mode:
authorYanteng Si <si.yanteng@linux.dev>2025-03-28 13:06:43 +0300
committerAlex Shi <alexs@kernel.org>2025-04-10 10:38:19 +0300
commit4f0145e9ea41cc5d0f80b79a60ce39757d3b47d6 (patch)
treedc3b200d81bfa201967196fb78d2b1ff72f58eda /scripts/lib/kdoc/kdoc_files.py
parentff6dfbf73c16b1b517554626820e4058b235e9e0 (diff)
downloadlinux-4f0145e9ea41cc5d0f80b79a60ce39757d3b47d6.tar.xz
docs/zh_CN: Add how-to of Chinese translation
Many new faces keep appearing on the mailing list from time to time, and there may be many potential developers who want to participate in the Chinese translation but don't know how to get started. As more and more documents are translated, it is becoming increasingly important to improve the maintainability of Chinese documents. We have a lot of conventions, but currently these conventions are still being passed on orally. At the same time, during the review process, especially for the first few patches submitted by newbies, we have made too many repetitive comments. In order to address the above issues, I have drafted this guide, and there is still a lot that needs to be improved. Alex Shi: Fix a embedded code white space issue. Co-developed-by: Dongliang Mu <dzm91@hust.edu.cn> Signed-off-by: Dongliang Mu <dzm91@hust.edu.cn> Signed-off-by: Yanteng Si <si.yanteng@linux.dev> Link: https://lore.kernel.org/r/0443c86e10d900a4d752d103265c948360563d43.1743156287.git.si.yanteng@linux.dev Signed-off-by: Alex Shi <alexs@kernel.org>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_files.py')
0 files changed, 0 insertions, 0 deletions