From: Yanteng Si <si.yanteng@linux.dev>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-doc@vger.kernel.org,
Alex Shi <alexs@kernel.org>, Dongliang Mu <dzm91@hust.edu.cn>
Subject: Re: [lwn:docs-next 37/72] htmldocs: Warning: Documentation/translations/zh_CN/how-to.rst references a file that doesn't exist: Documentation/xxx/xxx.rst
Date: Fri, 16 May 2025 18:01:48 +0800 [thread overview]
Message-ID: <dcb8c986-b6ec-4803-aa88-2ef2670a6b10@linux.dev> (raw)
In-Reply-To: <202505160627.WtzIIpL6-lkp@intel.com>
Hi robot,
在 5/16/25 7:04 AM, kernel test robot 写道:
> Warning: Documentation/translations/zh_CN/how-to.rst references a file that doesn't exist: Documentation/xxx/xxx.rst
I didn't reproduce this warning locally. It seems to be a difference
between different versions of Sphinx.
Could you please provide your Sphinx version?
^^^^^^^^^^^^^^^^^
+译文格式要求
+------------
+
+ - 每行长度最多不超过40个字符
+ - 每行长度请保持一致
+ - 标题的下划线长度请按照一个英文一个字符、一个中文两个字符与标题对齐
+ - 其它的修饰符请与英文文档保持一致
+
+此外在译文的头部,您需要插入以下内容::
+
+ .. SPDX-License-Identifier: GPL-2.0
+ .. include:: ../disclaimer-zh_CN.rst #您需要了解该文件的路径,根
+ 据您实际翻译的文档灵活调整
+
+ :Original: Documentation/xxx/xxx.rst #替换为您翻译的英文文档路径
+
+ :翻译:
+
+ 司延腾 Yanteng Si <si.yanteng@linux.dev> #替换为您自己的联系方式
+
+翻译技巧
+--------
+
+中文文档有每行40字符限制,因为一个中文字符等于2个英文字符。但是社区并没有
^^^^^^^^^^^^^^^^^^^
I think my grammar is fine. Does anyone know what's going on?
Thanks,
Yanteng
next prev parent reply other threads:[~2025-05-16 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 23:04 [lwn:docs-next 37/72] htmldocs: Warning: Documentation/translations/zh_CN/how-to.rst references a file that doesn't exist: Documentation/xxx/xxx.rst kernel test robot
2025-05-16 10:01 ` Yanteng Si [this message]
2025-05-19 2:24 ` Alex Shi
2025-05-19 3:11 ` Philip Li
2025-05-19 3:34 ` Randy Dunlap
2025-05-19 3:57 ` Dongliang Mu
2025-05-19 4:13 ` Philip Li
2025-05-19 4:12 ` Philip Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dcb8c986-b6ec-4803-aa88-2ef2670a6b10@linux.dev \
--to=si.yanteng@linux.dev \
--cc=alexs@kernel.org \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.