hb-introduction-hierarchy.po文件请求校验

0 views
Skip to first unread message

Guanqun Lu

unread,
Nov 21, 2007, 2:03:48 AM11/21/07
to Gentoo-China
看到大家没有什么校验啊。呵呵。
可能和我直接发最终版本上来,不方便校验有关。
所以这里我直接发po文件上来,大家同时看着中文和英文,方便对照。

Any comments are welcomed. ;-)

-----------8<------hierarchy.po----------------

msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2007-10-23 16:26+0000\n"
"PO-Revision-Date: 2007-10-23 16:27+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <L...@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"

# type: Content of: <sections><version>
#: hb-introduction-hierarchy.xml:9
#, no-wrap
msgid "1.0.2"
msgstr "1.0.2"

# type: Content of: <sections><date>
#: hb-introduction-hierarchy.xml:10
#, no-wrap
msgid "2006-05-04"
msgstr "2006-05-04"

# type: Content of: <sections><section><title>
#: hb-introduction-hierarchy.xml:13
msgid "Introduction"
msgstr "介绍"

# type: Content of: <sections><section><body><p>
#: hb-introduction-hierarchy.xml:17
msgid ""
"This section aims to explain the Gentoo development hierarchy and gives "
"developers an insight to how Gentoo Linux development management is "
"structured."
msgstr ""
"本节旨在分析Gentoo的开发架构并且帮助开发者了解Gentoo Linux开发管理是如何构成的。"

# type: Content of: <sections><section><title>
#: hb-introduction-hierarchy.xml:26
msgid "A short history of Gentoo's management structure"
msgstr "Gentoo管理结构的历史简介"

# type: Content of: <sections><section><body><p>
#: hb-introduction-hierarchy.xml:30
msgid ""
"The first attempt to come up with a management structure to solve problems "
"with coordination and communication issues was made in 2003 with the "
"structure described in <uri "
"link=\"http://www.gentoo.org/proj/en/glep/glep-0004.xml\">GLEP 4</uri>. As "
"Gentoo grew larger over the time, some problems with the management "
"structure were discovered and a new one was needed to solve these issues. "
"<uri link=\"http://www.gentoo.org/proj/en/glep/glep-0039.html\">GLEP "
"39</uri> describes both the reasons behind this as well as the outcome of "
"the discussion."
msgstr ""
"第一次尝试来建立一个管理结构来解决合作和交流的问题是在2003年,管理结构在<uri "
"link=\"http://www.gentoo.org/proj/en/glep/glep-0004.xml\">GLEP 4</uri>中被讨论。"
"当Gentoo不断地壮大,我们发现了一些和管理结构有关的问题,同时新的建议被采纳来解决这些问题。"
"<uri link=\"http://www.gentoo.org/proj/en/glep/glep-0039.html\">GLEP "
"39</uri>描述了在这背后的原因和这次讨论的结果。"

# type: Content of: <sections><section><title>
#: hb-introduction-hierarchy.xml:44
msgid "Current Management structure according to GLEP 39"
msgstr "按照GLEP 39规范的当前管理结构"

# type: Content of: <sections><section><body><p>
#: hb-introduction-hierarchy.xml:48
msgid ""
"A project is a group of developers working towards a goal (or a set of "
"goals)."
msgstr ""
"所谓项目就是为了一个目的(或一些目的)而一同工作的一群开发者。"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:53
msgid ""
"A project exists if it has a web page at <uri "
"link=\"http://www.gentoo.org/proj/en/\">www.gentoo.org/proj/en/&lt;project "
"name&gt;</uri> that is maintained. (\"Maintained\" means that the "
"information on the page is factually correct and not out-of-date.) If the "
"webpage isn't maintained, it is presumed dead."
msgstr ""
"只要一个项目存在,那么在<uri "
"link=\"http://www.gentoo.org/proj/en/\">www.gentoo.org/proj/en/&lt;project "
"name&gt;</uri>上就会有相应的网页被维护(\"维护\"意味着页面上的信息是正确的并且没有过期)。"
"如果网页没有被维护,那么就可以认为这个项目死了。"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:60
msgid ""
"It may have one or many leads, and the leads are selected by the members of "
"the project. This selection must occur at least once every 12 months and may "
"occur at any time."
msgstr ""
"一个项目可能有一个或多个领导者。领导者由这个项目的成员推选出来。"
"每12个月必须至少选举一次,选举可以随时举行。"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:65
msgid ""
"It may have zero or more sub-projects. Sub-projects are just projects that "
"provide some additional structure, and their web pages are in the project's "
"space."
msgstr ""
"一个项目可能没有或者有多个子项目。子项目是提供一些附加结构的项目,它们的网页也放置在主项目的空间上。"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:69
msgid "Not everything (or everyone) needs a project."
msgstr "并不是每件事(或每个人)都需要有一个项目。"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:70
msgid "Projects need not be long-term."
msgstr "项目没有必要一定是长期的。"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:71
msgid "Projects may well conflict with other projects. That's okay."
msgstr "一个项目可能与其他的项目发生冲突。这也没有关系。"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:73
msgid ""
"Any dev may create a new project just by creating a new page (or, more "
"realistically, directory and page) in "
"<path>gentoo/xml/htdocs/proj/en</path>."
msgstr ""
"任何开发者都可以建立一个项目,只需要在<path>gentoo/xml/htdocs/proj/en</path>"
"下建立一个新的页面(更准确地说是目录和网页)就可以了。"

# type: Content of: <sections><section><body><p>
#: hb-introduction-hierarchy.xml:80
msgid "Global issues will be decided by an elected Gentoo council."
msgstr "全球的事务由选举出来的Gentoo议会来决定。"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:85
msgid ""
"There will be a set number of council members. (For the first election that "
"number was set to 7 by acclamation.)"
msgstr ""
"议会成员的数量是固定的。(在第一次的选举中,这个数字被确定为7个人,并被大家强烈地赞同。)"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:89
msgid ""
"Council members will be chosen by a general election of all devs once per "
"year."
msgstr ""
"议会成员每年都由所有开发者全民选举产生。"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:92
msgid "The council must hold an open meeting at least once per month."
msgstr ""
"议会至少每个月必须召开一次公开会议。"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:94
msgid ""
"Council decisions are by majority vote of those who show up (or their "
"proxies)."
msgstr ""
"议会的决定由参加者(或者他们的代理人)投票决定,采取少数服从多数的原则。"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:98
msgid ""
"If a council member (or their appointed proxy) fails to show up for two "
"consecutive meetings, they are marked as a slacker."
msgstr ""
"如果一个议会成员(或者他们指定的代理人)没有参加两次连续的会议,他们便被标识为懒惰者(slacker)。"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:102
msgid ""
"If a council member who has been marked a slacker misses any further meeting "
"(or their appointed proxy doesn't show up), they lose their position and a "
"new election is held to replace that person. The newly elected council "
"member gets a 'reduced' term so that the yearly elections still elect a full "
"group."
msgstr ""
"如果一个已经被标识为懒惰者的议会成员错过了另外一次会议(或者他们指定的代理人也没有出现),那么"
"他们将失去这个职位,同时一个新的选举将被举行以接替这个人。这个新产生的议会成员的任期会缩短,"
"因为一年一度的选举还会重新选举出新的成员。"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:109
msgid ""
"Council members who have previously been booted for excessive slacking may "
"stand for future elections, including the election for their replacement. "
"They should, however, justify their reasons for slacking and should expect "
"to have it pointed out if they don't do so themselves."
msgstr ""
"以前由于过渡的懒惰而被踢出去的议会成员可以竞争以后的选举,包括寻找他们的接班人的那次选举。"
"当然,他们应该为他们成为懒惰者而进行辩护,并且应当知道这一点会被人指出来,如果他们自己不指出的话。"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:114
msgid "The 'slacker' marker is reset when a member is elected."
msgstr "当一个成员被选举出来的时候,这个懒惰者的标志被重置了。"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:116
msgid ""
"If any meeting has less than 50% attendance by council members, a new "
"election for all places must be held within a month. The 'one year' is then "
"reset from that point."
msgstr ""
"如果任何一个会议有少于一半的议会成员参加,那么一个新的选举必须在一个月之内举行。年度的选举时间"
"便从这个时候开始计算。"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:120
msgid "Disciplinary actions may be appealed to the council."
msgstr "如果你不满给你的惩戒措施,你可以向议会上诉。"

# type: Content of: <sections><section><body><ul><li>
#: hb-introduction-hierarchy.xml:122
msgid ""
"A proxy must not be an existing council member, and any single person may "
"not be a proxy for more than one council member at any given meeting."
msgstr ""
"一位代理人一定不能是现在的议会成员,而且在一个会议中,任何一个人不能当多于一个人的代理人。"

# type: Content of: <sections><section><title>
#: hb-introduction-hierarchy.xml:130
msgid "Consequences of Gentoo's management structure"
msgstr "Gentoo管理结构的影响"

# type: Content of: <sections><section><body><p>
#: hb-introduction-hierarchy.xml:134
msgid ""
"As a consequence of the new management structure, global decisions will be "
"made by the elected council. This should give Gentoo a general direction - "
"smaller issues affecting only a project or two should be decided inside the "
"projects involved, probably with input from other developers. The council "
"should be a fair representation of the developer base as every developer is "
"able to vote, so interests should be represented in a fair way. If the "
"council does a bad job and the developer base is unhappy with its work, the "
"council can be voted out."
msgstr ""
"作为新的管理结构的结果,全球事务由选举出来的议会决定。这给了Gentoo一个大概的方向——"
"只影响一两个项目的小事务应该在所涉及的项目组内决定,也许还可以听取其他开发者的意见。"
"议会应当成为一个公平的代表,因为每一个开发者都能够投票,所以利益应该以一种公平的方式来表现。"
"如果议会做得很糟糕,而且大多数开发者对他们的工作不满意,这个议会可以被投票免去。"

# type: Content of: <sections><section><body><p>
#: hb-introduction-hierarchy.xml:144
msgid ""
"Decisions within a project can be made by the people inside the project "
"itself, of course coordination between the projects is necessary. The "
"(sub-)project leads are usually responsible for doing this."
msgstr ""
"一个项目内部的决定由在项目内的人员自行决定,当然不同项目之间的合作是必要的。"
"(子)项目的领导者通常对此负责。"

# type: Content of: <sections><section><body><p>
#: hb-introduction-hierarchy.xml:150
msgid ""
"Most projects have an Operational and Strategic lead, but basically it is up "
"to the project what positions are created and how they are called - this "
"also applies to sub-projects."
msgstr ""
"大多数的项目都有一个操作和策略领导者(Operational and Strategic lead),但是基本上"
"这应当由项目来决定哪些职位该被创建并且是如何称呼的——这种规则同样适用于子项目。"

# type: Content of: <sections><section><body><p>
#: hb-introduction-hierarchy.xml:156
msgid ""
"Some projects appoint a contact person for communication to another project "
"e.g. a developer within the forums project who is responsible for "
"communication with the infrastracture project."
msgstr ""
"一些项目指定了一位联系人用来和其他项目进行交流,比如:"
"在论坛项目中的一位开发者负责与基础架构项目的沟通。"

# type: Content of: <sections><section><body><p>
#: hb-introduction-hierarchy.xml:162
msgid ""
"All in all, the current structure has no clear list of responsibilities the "
"project leads are supposed to satisfy. They are chosen by the members of the "
"project, the practical responsibility of a lead is \"whatever the members "
"require\", and if that isn't satisfied, the members can get a new lead (if "
"they can find somebody to take the job!)."
msgstr ""
"从各方面来说,当前的管理结构没有明确表明项目领导者的职责明细。项目领导者由项目的成员选出来,"
"通常的职责是满足\"任何成员所需\",如果这项职责没有完成,成员可以选举出一个新的领导者(如果"
"他们可以找到一位接替者!)。"

--
Guanqun

Zhang Le

unread,
Nov 21, 2007, 1:43:01 PM11/21/07
to gentoo...@googlegroups.com
On Nov 21, 2007 3:03 PM, Guanqun Lu <guanq...@gmail.com> wrote:
>
> 看到大家没有什么校验啊。呵呵。
> 可能和我直接发最终版本上来,不方便校验有关。
> 所以这里我直接发po文件上来,大家同时看着中文和英文,方便对照。

这样更好了,不过不是一定要这样做

> Any comments are welcomed. ;-)

大家可以都来看看
审校不是只能由一两个人来做
如果翻译的不好,整个社区都面上无光

最近我在翻译内核文档 CodingStyle
给大家做个榜样
大家可以看看过往的邮件
http://zh-kernel.org/pipermail/linux-kernel/2007-September/thread.html#631
http://zh-kernel.org/pipermail/linux-kernel/2007-November/thread.html#1397
http://zh-kernel.org/pipermail/linux-kernel/2007-November/thread.html#1653

--
Zhang Le, Robert
http://r0bertz.blogspot.com
http://zh.gentoo-wiki.com
http://savannah.nongnu.org/projects/pgubook
http://groups.google.com/group/gentoo-china
http://groups.google.com/group/szlug

Guanqun Lu

unread,
Nov 21, 2007, 11:52:33 PM11/21/07
to robert....@gmail.com, gentoo...@googlegroups.com
On Thu, 22 Nov 2007 02:43:01 +0800
"Zhang Le" <robert....@gmail.com> wrote:

> On Nov 21, 2007 3:03 PM, Guanqun Lu <guanq...@gmail.com> wrote:
> >
> > 看到大家没有什么校验啊。呵呵。
> > 可能和我直接发最终版本上来,不方便校验有关。
> > 所以这里我直接发po文件上来,大家同时看着中文和英文,方便对照。
>
> 这样更好了,不过不是一定要这样做

可能稍微方便些吧。呵呵。

>
> > Any comments are welcomed. ;-)
>
> 大家可以都来看看
> 审校不是只能由一两个人来做
> 如果翻译的不好,整个社区都面上无光

说得好!

看过的。翻译得不错。

--
Guanqun

Reply all
Reply to author
Forward
0 new messages