Translations by Victor Yu
Victor Yu has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
| 77. |
Write blogs and attach the label "openobject" to your posts
|
|
| 2014-03-07 |
写博客，并在发表时附上“openobject”标签
|
|
| 80. |
Announce only new events, new features or new developments
|
|
| 2014-03-07 |
仅宣布新事件、新特性或新的开发（发展）。
|
|
| 81. |
Promote the work you did primarily, not the company you represent
|
|
| 2014-03-07 |
主要以你个人的名义推广你的工作，而不是代表你所在的公司。
|
|
| 82. |
Only write positive messages, not negatives ones
|
|
| 2014-03-07 |
应写下正面的消息，而避免负面的
|
|
| 87. |
Two teams have been created on launchpad:
|
|
| 2014-03-07 |
在launchpad上创建了两个团队
|
|
| 88. |
OpenERP quality teams --> they can commit on:
|
|
| 2014-03-07 |
OpenERP质量团队 --> 他们可以提交到：
|
|
| 89. |
lp:~openerp/openobject-addons/4.2
|
|
| 2014-03-07 |
lp:~openerp/openobject-addons/4.2
|
|
| 90. |
lp:~openerp/openobject-addons/trunk
|
|
| 2014-03-07 |
lp:~openerp/openobject-addons/trunk
|
|
| 91. |
lp:~openerp/openobject-addons/4.2-extra-addons
|
|
| 2014-03-07 |
lp:~openerp/openobject-addons/4.2-extra-addons
|
|
| 92. |
lp:~openerp/openobject-addons/trunk-extra-addons
|
|
| 2014-03-07 |
lp:~openerp/openobject-addons/trunk-extra-addons
|
|
| 93. |
lp:~openerp/openobject-bi/trunk-addons
|
|
| 2014-03-07 |
lp:~openerp/openobject-bi/trunk-addons
|
|
| 94. |
lp:~openerp/openobject-bi/trunk-cli
|
|
| 2014-03-07 |
lp:~openerp/openobject-bi/trunk-cli
|
|
| 95. |
lp:~openerp/openobject-bi/trunk-client-web
|
|
| 2014-03-07 |
lp:~openerp/openobject-bi/trunk-client-web
|
|
| 96. |
lp:~openerp/openobject-client/4.2
|
|
| 2014-03-07 |
lp:~openerp/openobject-client/4.2
|
|
| 97. |
lp:~openerp/openobject-client/trunk
|
|
| 2014-03-07 |
lp:~openerp/openobject-client/trunk
|
|
| 98. |
lp:~openerp/openobject-client-web/4.2
|
|
| 2014-03-07 |
lp:~openerp/openobject-client-web/4.2
|
|
| 99. |
lp:~openerp/openobject-client-web/trunk
|
|
| 2014-03-07 |
lp:~openerp/openobject-client-web/trunk
|
|
| 100. |
lp:~openerp/openobject-server/4.2
|
|
| 2014-03-07 |
lp:~openerp/openobject-server/4.2
|
|
| 101. |
lp:~openerp/openobject-server/trunk
|
|
| 2014-03-07 |
lp:~openerp/openobject-server/trunk
|
|
| 104. |
Contributors --> They can commit on:
|
|
| 2014-03-07 |
贡献者 --> 可以提交到：
|
|
| 105. |
lp:~openerp-community
|
|
| 2014-03-07 |
lp:~openerp-community
|
|
| 108. |
open a branch in launchpad
|
|
| 2014-03-15 |
在launchpad打开一个分支
|
|
| 2014-03-07 |
在launchpad开启新的分支
|
|
| 110. |
wait for approval by our quality team
|
|
| 2014-03-07 |
等待质量团队的批准
|
|
| 113. |
Get Bazaar version control to pull the source from Launchpad.
|
|
| 2014-03-15 |
取得Bazaar版本控制，从Launchpad拉源代码。
|
|
| 2014-03-07 |
取得Bazaar版本控制权，从Launchpad拉源代码。
|
|
| 114. |
To install bazaar on any ubuntu distribution, you can edit /etc/apt/sources.list by
|
|
| 2014-03-07 |
要在任何的Ubuntu分发版本安装bazaar，首先要编辑 /etc/apt/sources.list ，使用的命令是
|
|
| 115. |
and put these lines in it:
|
|
| 2014-03-07 |
输入下列几行内容：
|
|
| 117. |
To work correctly, bzr version must be at least 1.3. Check it with the command:
|
|
| 2014-03-07 |
为了能够正常使用，bzr版本至少要为 1.3。 使用这个命令来确认：
|
|
| 121. |
This is the official and proposed way to contribute on OpenERP and OpenObject.
|
|
| 2014-03-14 |
这是官方、以及推荐的参与贡献OpenERP和OpenObject的方式。
|
|
| 124. |
Once your code is good enough and follow the :ref:`coding-guidelines-link`, you can push your branch in launchpad. You may have to create an account on launchpad first, register your public key, and subscribe to the `openerp-community <https://launchpad.net/~openerp-community>`_ team. Then, you can push your branch. Suppose you want to push your addons::
|
|
| 2014-03-16 |
当您的代码足够好了，并且按照 :ref:`coding-guidelines-link` 的规范,您可以上传您的分支到launchpad。首先,您必须得创建一个launchpad的帐号，注册您的公钥,订阅 `openerp-community <https://launchpad.net/~openerp-community>` 这个组。然后您就可以上传您的分支了。假如您想上传您的插件 ::
|
|
| 142. |
If they accept your branch for integration in the official version, they will submit to the quality team that will review and merge in the official branch.
|
|
| 2014-03-16 |
如果他们接受了你的分支整合到官方版本，他们将会提交给质量组，质量组将会评审和合并到官方分支。
|
|
| 146. |
`extra-addons branch <https://code.launchpad.net/~openerp-commiter/openobject-addons/trunk-extra-addons>`_ : if your module touches a few companies
|
|
| 2014-03-16 |
附加模块分支 <https://code.launchpad.net/~openerp-commiter/openobject-addons/trunk-extra-addons>`_ ：如果你的模块适用于一部分公司。
|
|
| 148. |
We invite all our partners and contributors to work in that way so that we can easily integrate and share the work done between the different projects.
|
|
| 2014-03-16 |
我们邀请我们所有的合作伙伴和参与者以这种方式工作，让我们可以很容易地集成和共享不同项目之间所完成的工作。
|
|
| 154. |
This will download the branch on your local computer. You can then start developing on it. From time to time, you should commit the work done::
|
|
| 2014-03-16 |
这将下载指定的分支到你的本地电脑。你就可以在此基础上开始你的开发工作了。记得及时提交你完成的工作::
|
|
| 156. |
For instance, you can switch the status to "In Development" to show you are working on it and put the status to "Mature" when you'd like to have your code integrated in the official release.
|
|
| 2014-03-16 |
比如，你能够切换状态到“开发中”说明你还在开发中，或者当你想要把你的代码集成到官方版本时，设置为“成熟”。
|
|
| 161. |
The stable branch is for bugfixes
|
|
| 2014-03-16 |
稳定分支用于修正bug
|
|
| 162. |
The stable branch must be used for bugfixes. **Only bugfixes**.
|
|
| 2014-03-16 |
稳定分支必须是用于bug修复。 **仅用于bug修复(Only bugfixes)**。
|
|
| 164. |
We will periodically backport all the fixes from stable to trunk.
|
|
| 2014-03-16 |
我们将阶段性的从稳定版向trunk版本移植所有的修复。
|
|
| 165. |
Set the author's name, if it's different from the committer
|
|
| 2014-03-16 |
如果与委员会的名称不同的话，会设定作者的姓名。
|
|
| 174. |
For improvements
|
|
| 2014-03-16 |
用于改进
|
|
| 175. |
For bug fixes
|
|
| 2014-03-16 |
用于bug修复
|
|
| 177. |
For adding new resources
|
|
| 2014-03-16 |
用于增加资源
|
|
| 178. |
For removing of resources
|
|
| 2014-03-16 |
用于删除资源
|
|
| 180. |
If you are fixing the bugs use ``--fixes=lp:<bug_number>`` instead of putting the number of the bug in the commit message.
|
|
| 2014-03-16 |
如果使用 ``--fixes=lp:<bug_number>`` 修复bug，而不是使用委员会的信息中的编号。
|
|
| 181. |
Use the revision id instead of the revision number when you make reference to a revision in your commit message. You can get this revision id, by using the command ``bzr version-info``.
|
|
| 2014-03-16 |
在提交信息中引用一个修正时，使用修正识别号(id)取代版本号码。你可以用命令 ``bzr version-info`` 命令取得该修正识别号(id)。
|
|
| 182. |
How to handle translations ?
|
|
| 2014-03-16 |
如何进行翻译
|
|
| 183. |
use **[IMP]** if you translated a message in a po file
|
|
| 2014-03-16 |
在翻译包含在po文件中的信息时，使用 **[IMP]**
|
|
| 184. |
use **[ADD]** if you added an new po file
|
|
| 2014-03-16 |
如果你使用新的po文件，请使用 **[ADD]**
|
|
| 187. |
Bazaar
|
|
| 2014-03-16 |
Bazaar
|
|
