[I18N] Update translation terms from Transifex

2019-12-05 09:58:14 +01:00
parent 923f5804fc
commit 71d5600b85
25 changed files with 1292 additions and 1089 deletions
@@ -3,13 +3,17 @@
 # This file is distributed under the same license as the Odoo package.
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
 # 
+# Translators:
+# 演奏王 <wangwhai@qq.com>, 2019
+# 
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 12.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-11-07 15:38+0100\n"
-"PO-Revision-Date: 2018-10-19 08:15+0000\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\n"
+"PO-Revision-Date: 2019-10-03 09:46+0000\n"
+"Last-Translator: 演奏王 <wangwhai@qq.com>, 2019\n"
 "Language-Team: Chinese (China) (https://www.transifex.com/odoo/teams/41243/zh_CN/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -19,18 +23,18 @@ msgstr ""

 #: ../../getting_started/documentation.rst:5
 msgid "Basics of the QuickStart Methodology"
-msgstr ""
+msgstr "快速入门方法的基础知识"

 #: ../../getting_started/documentation.rst:7
 msgid ""
 "This document summarizes Odoo Online's services, our Success Pack "
 "implementation methodology, and best practices to get started with our "
 "product."
-msgstr ""
+msgstr "本文档总结了 Odoo Online 的服务、我们的成功包实施方法以及开始使用我们产品的最佳做法。"

 #: ../../getting_started/documentation.rst:12
 msgid "1. The SPoC (*Single Point of Contact*) and the Consultant"
-msgstr ""
+msgstr "1. SPoC（[单一联络点]）和顾问"

 #: ../../getting_started/documentation.rst:14
 msgid ""
@@ -38,7 +42,7 @@ msgid ""
 "and maintain on both sides (your side and ours) **one and only single person"
 " of contact** who will take charge and assume responsibilities regarding the"
 " project. He also has to have **the authority** in terms of decision making."
-msgstr ""
+msgstr "在您的项目范围内，强烈建议指定和维护双方（您和我们）[唯一的联系人]谁将负责并承担项目责任。在决策方面，他还必须拥有[权力]。"

 #: ../../getting_started/documentation.rst:20
 msgid ""
@@ -46,7 +50,7 @@ msgid ""
 " the beginning to the end of the project, he ensures the overall consistency"
 " of the implementation in Odoo and shares his expertise in terms of good "
 "practices."
-msgstr ""
+msgstr "[Odoo 顾问确保项目从 A 到 Z*的实施：从项目开始到结束，他确保 Odoo 实施的总体一致性，并分享他在良好做法方面的专业知识。"

 #: ../../getting_started/documentation.rst:25
 msgid ""
@@ -54,7 +58,7 @@ msgid ""
 " for the business knowledge transmission (coordinate key users intervention "
 "if necessary) and the consistency of the implementation from a business "
 "point of view (decision making, change management, etc.)"
-msgstr ""
+msgstr "[客户方面唯一的决策者（SPoC）]：他负责业务知识的传递（必要时协调关键用户的干预）和从业务角度（决策、变革）实施的一致性管理等）"

 #: ../../getting_started/documentation.rst:31
 msgid ""
@@ -65,6 +69,9 @@ msgid ""
 " meant to align on the business needs (SPoC) and to define the way those "
 "needs will be implemented in Odoo (Consultant)."
 msgstr ""
+"[会议优化]：Odoo "
+"顾问不参与从业务角度决策过程，也不参与精确的流程和公司的内部程序（除非有具体要求或例外情况）。每周举行一次或两次项目会议，旨在根据业务需求 （SPoC）"
+" 进行调整，并定义在 Odoo（顾问）中实现这些需求的方式。"

 #: ../../getting_started/documentation.rst:39
 msgid ""
@@ -77,17 +84,21 @@ msgid ""
 "platform <https://odoo.thinkific.com/courses/odoo-functional>`__ and the "
 "testing of functionalities."
 msgstr ""
+"[培训培训师方法]：Odoo 顾问向 SPoC 提供职能培训，以便他可以将这些知识传授给他的协作者。为了使这种方法取得成功，SPoC "
+"还必须通过\"Odoo 文档 "
+"<http://www.odoo.com/documentation/user/10.0/index.html>`__、\"电子学习平台 \" "
+"参与自身技能提升。<https://odoo.thinkific.com/courses/odoo-functional>`和功能测试。"

 #: ../../getting_started/documentation.rst:47
 msgid "2. Project Scope"
-msgstr ""
+msgstr "2. 项目范围"

 #: ../../getting_started/documentation.rst:49
 msgid ""
 "To make sure all the stakeholders involved are always aligned, it is "
 "necessary to define and to make the project scope evolve as long as the "
 "project implementation is pursuing."
-msgstr ""
+msgstr "为了确保所有相关利益干系人始终保持一致，只要项目实施进行，就有必要定义并使项目范围不断发展。"

 #: ../../getting_started/documentation.rst:53
 msgid ""
@@ -97,6 +108,7 @@ msgid ""
 "the needs and the resulting decision-making process are more simple and more"
 " clear."
 msgstr ""
+"[对初始项目范围的明确定义]：对初始需求的明确定义对于确保项目顺利运行至关重要。事实上，当所有利益攸关方都有着相同的愿景时，需求的演变和由此产生的决策过程就更加简单和明确。"

 #: ../../getting_started/documentation.rst:59
 msgid ""
@@ -106,6 +118,7 @@ msgid ""
 "approach also helps to identify gaps and apply corrective actions early in "
 "the implementation."
 msgstr ""
+"[逐步实施项目]：赞成在几个连贯的阶段实施，允许定期生产发布，最终用户不断接管Odoo，这证明了其随着时间的推移的有效性。这种方法还有助于识别差距，并在实施初期采取纠正措施。"

 #: ../../getting_started/documentation.rst:66
 msgid ""
@@ -118,17 +131,19 @@ msgid ""
 "should still be realized, its implementation will be carried out after an "
 "experiment of the standard in production."
 msgstr ""
+"[优先采用标准功能]：Odoo "
+"提供了一个实施轻微改进（定制）或更重要的改进（开发）的绝佳环境。不过，为了优化项目交付时间，为用户提供其新工具的长期稳定性和可伸缩性，将尽可能频繁地采用标准解决方案。理想情况下，如果软件的改进仍然应该实现，其实现将在生产标准试验后进行。"

 #: ../../getting_started/documentation.rst:80
 msgid "3. Managing expectations"
-msgstr ""
+msgstr "3. 管理期望"

 #: ../../getting_started/documentation.rst:82
 msgid ""
 "The gap between the reality of an implementation and the expectations of "
 "future users is a crucial factor. Three important aspects must be taken into"
 " account from the beginning of the project:"
-msgstr ""
+msgstr "实施的现实与未来用户的期望之间的差距是一个关键因素。从项目开始，就必须考虑到三个重要方面："

 #: ../../getting_started/documentation.rst:86
 msgid ""
@@ -139,6 +154,8 @@ msgid ""
 "at the beginning of the project to align with these topics and regularly "
 "check that this is still the case."
 msgstr ""
+"[与项目方法保持一致]：明确划分角色和责任，明确描述操作模式（验证、解决问题等）对于 Odoo "
+"实施的成功至关重要。因此，强烈建议在项目开始时花一些时间与这些主题保持一致，并定期检查情况是否仍然如此。"

 #: ../../getting_started/documentation.rst:94
 msgid ""
@@ -154,6 +171,9 @@ msgid ""
 "global relief is noted. Changes in business processes may also be proposed "
 "to pursue this same objective."
 msgstr ""
+"[专注于项目的成功，而不是理想的解决方案]：SPoC和顾问的主要目标是执行委托给他们的项目，以便提供最有效的解决方案，以满足表达的需求。这一目标有时与最终用户的理想解决方案愿景相冲突。在这种情况下，SPoC"
+" 和顾问将适用 80-20 规则：关注 80% 的表达需求，并找出成本/收益比率方面最不利目标的其余 "
+"20%（这些比例当然会随时间而变化）。因此，如果注意到全球救济，将更耗时的操纵纳入一个比较耗时的操纵将被认为是可以接受的。为了追求同样的目标，也可以提议改变业务流程。"

 #: ../../getting_started/documentation.rst:108
 msgid ""
@@ -162,20 +182,20 @@ msgid ""
 "avoid being in this delicate situation, we recommend using several types of "
 "tools\\* :"
 msgstr ""
+"[规范总是 EXPLICIT]：预期内容与交付内容之间的差距通常是项目中冲突的根源。为了避免出现这种微妙情况，我们建议使用几种类型的工具* ："

 #: ../../getting_started/documentation.rst:113
 msgid ""
 "**The GAP Analysis**: The comparison of the request with the standard "
 "features proposed by Odoo will make it possible to identify the gap to be "
 "filled by developments/customizations or changes in business processes."
-msgstr ""
+msgstr "[GAP 分析]：将请求与 Odoo 提出的标准功能进行比较，将有可能确定由开发/定制或业务流程变化填补的空白。"

 #: ../../getting_started/documentation.rst:118
 msgid ""
-"`The User Story <https://help.rallydev.com/writing-great-user-story>`__: "
-"This technique clearly separates the responsibilities between the SPoC, "
-"responsible for explaining the WHAT, the WHY and the WHO, and the Consultant"
-" who will provide a response to the HOW."
+"**The User Story**: This technique clearly separates the responsibilities "
+"between the SPoC, responsible for explaining the WHAT, the WHY and the WHO, "
+"and the Consultant who will provide a response to the HOW."
 msgstr ""

 #: ../../getting_started/documentation.rst:126
@@ -184,12 +204,14 @@ msgid ""
 "simplified version, a prototype of what is expected to agree on the main "
 "lines of expected changes."
 msgstr ""
+"概念证明简化版本，<https://en.wikipedia.org/wiki/Proof_of_concept>`__ "
+"是预期对预期变化的主要行达成一致的内容的原型。"

 #: ../../getting_started/documentation.rst:130
 msgid ""
 "**The Mockup**: In the same idea as the Proof of Concept, it will align with"
 " the changes related to the interface."
-msgstr ""
+msgstr "[模型]：在与概念证明相同的理念中，它将与与界面相关的更改保持一致。"

 #: ../../getting_started/documentation.rst:133
 msgid ""
@@ -199,16 +221,17 @@ msgid ""
 "project. We will, therefore, avoid basing our work on hypotheses without "
 "verifying its veracity beforehand."
 msgstr ""
+"在这些工具中，将完全透明地了解软件和/或其环境的可能性和局限性，以便所有项目利益相关者清楚地了解项目中可以预期/实现的内容。因此，我们将避免在事先核实其真实性的情况下，以假设为基础开展工作。"

 #: ../../getting_started/documentation.rst:139
 msgid ""
 "*This list can, of course, be completed by other tools that would more "
 "adequately meet the realities and needs of your project*"
-msgstr ""
+msgstr "[当然，这个列表可以由其他工具完成，这些工具可以更充分地满足项目的现实和需求]"

 #: ../../getting_started/documentation.rst:143
 msgid "4. Communication Strategy"
-msgstr ""
+msgstr "4. 传播战略"

 #: ../../getting_started/documentation.rst:145
 msgid ""
@@ -216,7 +239,7 @@ msgid ""
 "the tool for end users. Effective communication is therefore crucial to the "
 "success of this approach. Its optimization will, therefore, lead us to "
 "follow those principles:"
-msgstr ""
+msgstr "快速入门方法的目的是确保最终用户快速拥有该工具。因此，有效的沟通对于这种方法的成功至关重要。因此，它的优化将引导我们遵循以下原则："

 #: ../../getting_started/documentation.rst:150
 msgid ""
@@ -227,44 +250,45 @@ msgid ""
 "performed as part of the implementation for which the priority level and the"
 " manager are clearly defined."
 msgstr ""
+"[共享项目管理文档]：确保项目中的所有利益相关者都具有相同的知识水平的最佳方法是提供对项目跟踪文档的直接访问（项目管理器）。本文档将至少包含一个任务列表，作为明确定义优先级和管理器的实现的一部分。"

 #: ../../getting_started/documentation.rst:158
 msgid ""
 "The Project Organizer is a shared project tracking tool that allows both "
 "detailed tracking of ongoing tasks and the overall progress of the project."
-msgstr ""
+msgstr "项目管理器是一个共享的项目跟踪工具，允许详细跟踪正在进行的任务和项目的总体进度。"

 #: ../../getting_started/documentation.rst:162
 msgid ""
 "**Report essential information**: In order to minimize the documentation "
 "time to the essentials, we will follow the following good practices:"
-msgstr ""
+msgstr "[报告基本信息]：为了将文档时间缩短到要点，我们将遵循以下良好做法："

 #: ../../getting_started/documentation.rst:166
 msgid "Meeting minutes will be limited to decisions and validations;"
-msgstr ""
+msgstr "会议记录将限于决策和验证;"

 #: ../../getting_started/documentation.rst:168
 msgid ""
 "Project statuses will only be established when an important milestone is "
 "reached;"
-msgstr ""
+msgstr "只有在达到重要流程时，才会建立项目状态;"

 #: ../../getting_started/documentation.rst:171
 msgid ""
 "Training sessions on the standard or customized solution will be organized."
-msgstr ""
+msgstr "将组织关于标准或定制解决方案的培训课程。"

 #: ../../getting_started/documentation.rst:175
 msgid "5. Customizations and Development"
-msgstr ""
+msgstr "5. 定制和开发"

 #: ../../getting_started/documentation.rst:177
 msgid ""
 "Odoo is a software known for its flexibility and its important evolution "
 "capacity. However, a significant amount of development contradicts a fast "
 "and sustainable implementation. This is the reason why it is recommended to:"
-msgstr ""
+msgstr "Odoo 是一种以灵活性和重要进化能力而闻名的软件。然而，大量的发展与快速和可持续的实施相矛盾。因此，建议："

 #: ../../getting_started/documentation.rst:182
 msgid ""
@@ -279,6 +303,8 @@ msgid ""
 "requests are dropped after a few weeks of using standard Odoo (see "
 "\"Adopting the standard as a priority\")."
 msgstr ""
+"[开发只有一个很好的理由]：在成本效益比为正时（每天节省时间等），必须始终做出开发决策。例如，最好实现重大开发，以减少日常操作的时间，而不是每季度只执行一次操作。人们普遍认为，解决方案越接近标准，迁移过程越轻越流畅，双方的维护成本就越低。此外，经验告诉我们，在使用标准"
+" Odoo 数周后，60% 的初始开发请求被丢弃（请参阅\"将标准作为优先级采用\"）。"

 #: ../../getting_started/documentation.rst:194
 msgid ""
@@ -287,18 +313,18 @@ msgid ""
 " implementation is THE right moment to accept and even be a change initiator"
 " both in terms of how the software will be used and at the level of the "
 "business processes of the company."
-msgstr ""
+msgstr "[替换，无需复制]：有一个很好的理由决定更改管理软件已经作出。在此背景下，实施时机是接受甚至改变软件使用方式和公司业务流程层面的变革时机。"

 #: ../../getting_started/documentation.rst:202
 msgid "6. Testing and Validation principles"
-msgstr ""
+msgstr "6. 测试和验证原则"

 #: ../../getting_started/documentation.rst:204
 msgid ""
 "Whether developments are made or not in the implementation, it is crucial to"
 " test and validate the correspondence of the solution with the operational "
 "needs of the company."
-msgstr ""
+msgstr "无论在实施中是否取得了发展，测试和验证解决方案与公司运营需求的对应关系都至关重要。"

 #: ../../getting_started/documentation.rst:208
 msgid ""
@@ -306,33 +332,33 @@ msgid ""
 "for delivering a solution corresponding to the defined specifications; the "
 "SPoC will have to test and validate that the solution delivered meets the "
 "requirements of the operational reality."
-msgstr ""
+msgstr "[角色分配]：在这种情况下，顾问将负责提供与规定规格相符的解决方案;SPoC 必须测试和验证交付的解决方案是否符合操作现实的要求。"

 #: ../../getting_started/documentation.rst:214
 msgid ""
 "**Change management**: When a change needs to be made to the solution, the "
 "noted gap is caused by:"
-msgstr ""
+msgstr "[变更管理]：当需要对解决方案进行更改时，注意到的差距是由以下原因造成的："

 #: ../../getting_started/documentation.rst:218
 msgid ""
 "A difference between the specification and the delivered solution - This is "
 "a correction for which the Consultant is responsible"
-msgstr ""
+msgstr "规范与交付解决方案之间的区别 - 这是顾问负责的更正"

 #: ../../getting_started/documentation.rst:220
 msgid "**or**"
-msgstr ""
+msgstr "[或]"

 #: ../../getting_started/documentation.rst:222
 msgid ""
 "A difference between the specification and the imperatives of operational "
 "reality - This is a change that is the responsibility of SPoC."
-msgstr ""
+msgstr "规范与操作现实的必要性之间的区别 - 这是 SPoC 的责任。"

 #: ../../getting_started/documentation.rst:226
 msgid "7. Data Imports"
-msgstr ""
+msgstr "7. 数据导入"

 #: ../../getting_started/documentation.rst:228
 msgid ""
@@ -342,13 +368,14 @@ msgid ""
 "prevent production from happening in time. To do this as soon as possible, "
 "it will be decided :"
 msgstr ""
+"导入事务数据历史记录是一个重要问题，必须适当地回答，以使项目顺利运行。事实上，这项任务可能非常耗时，如果其优先级没有很好地定义，则防止生产及时发生。为此尽快完成，将视其为："

 #: ../../getting_started/documentation.rst:234
 msgid ""
 "**Not to import anything**: It often happens that after reflection, "
 "importing data history is not considered necessary, these data being, "
 "moreover, kept outside Odoo and consolidated for later reporting."
-msgstr ""
+msgstr "[不导入任何内容]：通常情况下，在反射后，导入数据历史记录被认为没有必要，这些数据被保存在 Odoo 之外并合并，以便以后报告。"

 #: ../../getting_started/documentation.rst:239
 msgid ""
@@ -358,6 +385,7 @@ msgid ""
 "available from the first day of use in production is real. In this case, the"
 " import will be made before the production launch."
 msgstr ""
+"[在投入生产之前导入有限数量的数据]：当数据历史记录与正在处理的信息相关时（例如，采购订单、发票、未结项目），需要从使用的第一天起提供此信息。生产是真实的。在这种情况下，将在生产启动之前进行导入。"

 #: ../../getting_started/documentation.rst:246
 msgid ""
@@ -366,107 +394,19 @@ msgid ""
 "can be integrated into the software retrospectively. In this case, the "
 "production launch of the solution will precede the required imports."
 msgstr ""
+"[在生产启动后导入]：当数据历史记录需要与 Odoo "
+"集成，主要用于报告目的时，很明显，这些数据可以追溯性地集成到软件中。在这种情况下，解决方案的生产启动将先于所需的导入。"

 #: ../../getting_started/documentation.rst:253
 msgid "8. Support"
-msgstr ""
+msgstr "8. 支持"

 #: ../../getting_started/documentation.rst:255
 msgid ""
-"Your Odoo Online subscription includes **unlimited 24hr support at no extra "
-"cost, Monday to Friday**. Our teams are located around the world to ensure "
-"you have support, no matter your location. Your support representative could"
-" be communicating to you from San Francisco, Belgium, or India!"
+"When your project is put in production, our support teams take care of your "
+"questions or technical issues."
 msgstr ""

-#: ../../getting_started/documentation.rst:260
-msgid "What kind of support is included?"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:262
-msgid ""
-"Providing you with relevant material (guidelines, product documentation, "
-"etc...)"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:264
-msgid ""
-"Answers to issues that you may encounter in your standard Odoo database (eg."
-" “I cannot close my Point of Sale” or “I cannot find my sales KPIs?”)"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:266
-msgid "Questions related to your account, subscription, or billing"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:267
-msgid ""
-"Bug resolution (blocking issues or unexpected behaviour not due to "
-"misconfiguration or customization)"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:269
-msgid ""
-"Issues that might occur in a test database after upgrading to a newer "
-"version"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:271
-msgid ""
-"*Odoo Support does not make changes to your production database, but gives "
-"you the material and knowledge to do it yourself!*"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:274
-msgid "What kind of support is not included?"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:276
-msgid ""
-"Questions that require us to understand your business processes in order to "
-"help you implement your database"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:278
-msgid ""
-"Training on how to use our software (we will direct you to our many "
-"resources)"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:279
-msgid "Importation of documents into your database"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:280
-msgid ""
-"Guidance on which configurations to apply inside of an application or the "
-"database"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:281
-msgid ""
-"How to set up configuration models (Examples include: Inventory Routes, "
-"Payment Terms, Warehouses, etc)"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:283
-msgid ""
-"Questions or issues related to specific developments or customizations done "
-"either by Odoo or a third party (this is specific only to your database or "
-"involving code)"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:287
-msgid ""
-"You can get this type of support with a `Success Pack <https://www.odoo.com"
-"/pricing-packs>`__. With a pack, one of our consultants will analyze the way"
-" your business runs and tell you how you can get the most out of your Odoo "
-"Database. We will handle all configurations and coach you on how to use "
-"Odoo."
-msgstr ""
-
-#: ../../getting_started/documentation.rst:292
-msgid ""
-"Our support team can be contacted through our `online support form "
-"<https://www.odoo.com/help>`__."
+#: ../../getting_started/documentation.rst:258
+msgid "See :ref:`support-expectations`."
 msgstr ""