Commit 214cf4c2 authored by Boyuan Yang's avatar Boyuan Yang

chinese: Bugs/Reporting: more translations

CVS version numbers

chinese/Bugs/Reporting.wml: 1.22 -> 1.23
parent 8c09d5c9
......@@ -280,27 +280,26 @@ Source: <var>foopackage</var>
</pre>
<p>
the equivalent of <code>Package:</code> for bugs present in the source
package of foopackage; for most bugs in most packages you don't want
to use this option.
<code>Package:</code> 头的等价形式,用于指出在名为 foopackage
的源码包内存在的缺陷;对于大多数软件包中的缺陷,您大概没有必要使用这个选项。
</p>
<h2><a name="control">控制指令</a></h2>
<pre>
Control: <var>control commands</var>
Control: <var>具体控制指令</var>
</pre>
<p>
Allows for any of the commands which must be sent to
<code>control@bugs.debian.org</code> to work when sent to <code>submit@bugs.debian.org</code> or
<code>nnn@bugs.debian.org</code>. -1 initially refers to the current
bug (that is, the bug created by a mail to submit@ or the bug
messaged with nnn@). Please see <a href="server-control">the
server control documentation</a> for more information on the
control commands which are valid.</p>
使得所有本应由 <code>control@bugs.debian.org</code>
接收的控制指令可以同样由发送至 <code>submit@bugs.debian.org</code>
或者 <code>nnn@bugs.debian.org</code> 的邮件等效地被服务器处理。
指令中出现的 -1 将代指当前缺陷报告编号(即,发送至 submit@
的邮件即将创建的缺陷报告编号或发送至 nnn@ 的邮件中的编号)。
请浏览<a href="server-control">BTS服务器控制指令文档</a>以了解具体的可用控制指令。
</p>
<p>For example, the following pseudoheader in a message sent
to <code>12345@bugs.debian.org</code>:</p>
<p>例如,下面给出了发送至 <code>12345@bugs.debian.org</code>
的邮件中的伪信头示例:</p>
<pre>
Control: retitle -1 this is the title
......@@ -309,33 +308,31 @@ Control: summary -1 0
Control: forward -1 https://bugs.debian.org/nnn
</pre>
<p>would cause 12345 to be retitled, its severity changed, summary set,
and marked as forwarded.</p>
<p>将使得编号为 12345 的缺陷报告得到更名、其严重等级被修改、其简介信息得到设置并
标记为已转发。</p>
<h2>X-Debbugs- 信头</h2>
<p>Finally, if your
<acronym title="Mail User Agent" lang="en">MUA</acronym>
doesn't allow you to edit the headers, you can
set the various <code>X-Debbugs-</code> headers in the
<a href="#pseudoheader">pseudo-headers</a>.</p>
<p>除此之外,如果您的
<acronym title="邮件用户代理" lang="zh">MUA</acronym>
不允许您编辑信头,您可以在<a href="#pseudoheader">伪信头</a>区域设置各个 <code>X-Debbugs-</code>
项以等效实现原信头的功能。</p>
<h1>额外信息</h1>
<h2>Different submission addresses (minor or mass bug reports)</h2>
<h2>不同的提交地址(用于不严重的问题或批量缺陷报告)</h2>
<p>If a bug report is minor, for example, a documentation typo or a trivial
build problem, please adjust the severity appropriately and send it to
<code>maintonly@bugs.debian.org</code> instead of <code>submit@bugs.debian.org</code>.
<code>maintonly</code> will forward the report to the package maintainer
only, it won't forward it to the BTS mailing lists.</p>
<p>如果某个报告所涉及到的问题都是小问题,例如文档中的一处错字或是平凡的构建问题,
请考虑将其严重等级适当进行设置(选用低等级),并将报告发送至
<code>maintonly@bugs.debian.org</code> 而非 <code>submit@bugs.debian.org</code>。
<code>maintonly</code> 将只会把报告转发至软件包维护者,它不会将其转发到
BTS 邮件列表中。</p>
<p>If you're submitting many reports at once, you should definitely use
<code>maintonly@bugs.debian.org</code> so that you don't cause too much redundant
traffic on the BTS mailing lists. Before submitting many similar bugs you
may also want to post a summary on <code>debian-bugs-dist</code>.</p>
<p>如果您打算同时提交许多报告,您肯定应当使用 <code>maintonly@bugs.debian.org</code>
来避免为 BTS 邮件列表带来瞬时大量的流量。
在提交许多相似的问题报告之前,也请考虑在 <code>debian-bugs-dist</code>
邮件列表上发布一份概述信息。</p>
<p>If wish to report a bug to the bug tracking system that's already been
sent to the maintainer, you can use <code>quiet@bugs.debian.org</code>. Bugs sent to
......@@ -380,7 +377,7 @@ contain error messages which should be read and acted upon.</p>
match FROM_DAEMON.</p>
<h2>Bug reports against unknown packages</h2>
<h2>向未知软件包提交的缺陷报告</h2>
<p>If the bug tracking system doesn't know who the maintainer of the
relevant package is it will forward the report to
......@@ -408,7 +405,7 @@ grep)</code></p>
installed by using <code>dpkg --list</code> or <code>dpkg --status</code>.
</p>
<p>For example:</p>
<p>例如:</p>
<pre>
$ which apt-get
/usr/bin/apt-get
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment