[I18N] Update translation terms from Transifex

This commit is contained in:
Odoo Translation Bot
2020-09-27 01:31:33 +02:00
parent e218ae4991
commit 5004122011
216 changed files with 179389 additions and 110130 deletions
+56 -58
View File
@@ -8,8 +8,8 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -29,7 +29,7 @@ msgid ""
msgstr ""
#: ../../getting_started/documentation.rst:12
msgid "1. The SPoC (*Single Point of Contact*) and the Consultant"
msgid "The SPoC (*Single Point of Contact*) and the Consultant"
msgstr ""
#: ../../getting_started/documentation.rst:14
@@ -72,24 +72,22 @@ msgid ""
"training to the SPoC so that he can pass on this knowledge to his "
"collaborators. In order for this approach to be successful, it is necessary "
"that the SPoC is also involved in its own rise in skills through self-"
"learning via the `Odoo documentation "
"<http://www.odoo.com/documentation/user/10.0/index.html>`__, `The elearning "
"platform <https://odoo.thinkific.com/courses/odoo-functional>`__ and the "
"testing of functionalities."
msgstr ""
#: ../../getting_started/documentation.rst:47
msgid "2. Project Scope"
"learning via the :doc:`Odoo documentation <../index>`, `The elearning "
"platform <https://odoo.com/learn>`_ and the testing of functionalities."
msgstr ""
#: ../../getting_started/documentation.rst:49
msgid "Project Scope"
msgstr ""
#: ../../getting_started/documentation.rst:51
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 ""
#: ../../getting_started/documentation.rst:53
#: ../../getting_started/documentation.rst:55
msgid ""
"**A clear definition of the initial project scope**: A clear definition of "
"the initial needs is crucial to ensure the project is running smoothly. "
@@ -98,7 +96,7 @@ msgid ""
" clear."
msgstr ""
#: ../../getting_started/documentation.rst:59
#: ../../getting_started/documentation.rst:61
msgid ""
"**Phasing the project**: Favoring an implementation in several coherent "
"phases allowing regular production releases and an evolving takeover of Odoo"
@@ -107,7 +105,7 @@ msgid ""
"the implementation."
msgstr ""
#: ../../getting_started/documentation.rst:66
#: ../../getting_started/documentation.rst:68
msgid ""
"**Adopting standard features as a priority**: Odoo offers a great "
"environment to implement slight improvements (customizations) or more "
@@ -119,18 +117,18 @@ msgid ""
"experiment of the standard in production."
msgstr ""
#: ../../getting_started/documentation.rst:80
msgid "3. Managing expectations"
#: ../../getting_started/documentation.rst:82
msgid "Managing expectations"
msgstr ""
#: ../../getting_started/documentation.rst:82
#: ../../getting_started/documentation.rst:84
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 ""
#: ../../getting_started/documentation.rst:86
#: ../../getting_started/documentation.rst:88
msgid ""
"**Align with the project approach**: Both a clear division of roles and "
"responsibilities and a clear description of the operating modes (validation,"
@@ -140,7 +138,7 @@ msgid ""
"check that this is still the case."
msgstr ""
#: ../../getting_started/documentation.rst:94
#: ../../getting_started/documentation.rst:96
msgid ""
"**Focus on the project success, not on the ideal solution**: The main goal "
"of the SPoC and the Consultant is to carry out the project entrusted to them"
@@ -155,7 +153,7 @@ msgid ""
"to pursue this same objective."
msgstr ""
#: ../../getting_started/documentation.rst:108
#: ../../getting_started/documentation.rst:110
msgid ""
"**Specifications are always EXPLICIT**: Gaps between what is expected and "
"what is delivered are often a source of conflict in a project. In order to "
@@ -163,34 +161,34 @@ msgid ""
"tools\\* :"
msgstr ""
#: ../../getting_started/documentation.rst:113
#: ../../getting_started/documentation.rst:115
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 ""
#: ../../getting_started/documentation.rst:118
#: ../../getting_started/documentation.rst:120
msgid ""
"**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
#: ../../getting_started/documentation.rst:128
msgid ""
"`The Proof of Concept <https://en.wikipedia.org/wiki/Proof_of_concept>`__ A "
"simplified version, a prototype of what is expected to agree on the main "
"lines of expected changes."
msgstr ""
#: ../../getting_started/documentation.rst:130
#: ../../getting_started/documentation.rst:132
msgid ""
"**The Mockup**: In the same idea as the Proof of Concept, it will align with"
" the changes related to the interface."
msgstr ""
#: ../../getting_started/documentation.rst:133
#: ../../getting_started/documentation.rst:135
msgid ""
"To these tools will be added complete transparency on the possibilities and "
"limitations of the software and/or its environment so that all project "
@@ -199,17 +197,17 @@ msgid ""
"verifying its veracity beforehand."
msgstr ""
#: ../../getting_started/documentation.rst:139
#: ../../getting_started/documentation.rst:141
msgid ""
"*This list can, of course, be completed by other tools that would more "
"adequately meet the realities and needs of your project*"
msgstr ""
#: ../../getting_started/documentation.rst:143
msgid "4. Communication Strategy"
#: ../../getting_started/documentation.rst:145
msgid "Communication Strategy"
msgstr ""
#: ../../getting_started/documentation.rst:145
#: ../../getting_started/documentation.rst:147
msgid ""
"The purpose of the QuickStart methodology is to ensure quick ownership of "
"the tool for end users. Effective communication is therefore crucial to the "
@@ -217,7 +215,7 @@ msgid ""
"follow those principles:"
msgstr ""
#: ../../getting_started/documentation.rst:150
#: ../../getting_started/documentation.rst:152
msgid ""
"**Sharing the project management documentation**: The best way to ensure "
"that all stakeholders in a project have the same level of knowledge is to "
@@ -227,45 +225,45 @@ msgid ""
" manager are clearly defined."
msgstr ""
#: ../../getting_started/documentation.rst:158
#: ../../getting_started/documentation.rst:160
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 ""
#: ../../getting_started/documentation.rst:162
#: ../../getting_started/documentation.rst:164
msgid ""
"**Report essential information**: In order to minimize the documentation "
"time to the essentials, we will follow the following good practices:"
msgstr ""
#: ../../getting_started/documentation.rst:166
#: ../../getting_started/documentation.rst:168
msgid "Meeting minutes will be limited to decisions and validations;"
msgstr ""
#: ../../getting_started/documentation.rst:168
#: ../../getting_started/documentation.rst:170
msgid ""
"Project statuses will only be established when an important milestone is "
"reached;"
msgstr ""
#: ../../getting_started/documentation.rst:171
#: ../../getting_started/documentation.rst:173
msgid ""
"Training sessions on the standard or customized solution will be organized."
msgstr ""
#: ../../getting_started/documentation.rst:175
msgid "5. Customizations and Development"
#: ../../getting_started/documentation.rst:177
msgid "Customizations and Development"
msgstr ""
#: ../../getting_started/documentation.rst:177
#: ../../getting_started/documentation.rst:179
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 ""
#: ../../getting_started/documentation.rst:182
#: ../../getting_started/documentation.rst:184
msgid ""
"**Develop only for a good reason**: The decision to develop must always be "
"taken when the cost-benefit ratio is positive (saving time on a daily basis,"
@@ -279,7 +277,7 @@ msgid ""
"\"Adopting the standard as a priority\")."
msgstr ""
#: ../../getting_started/documentation.rst:194
#: ../../getting_started/documentation.rst:196
msgid ""
"**Replace, without replicate**: There is a good reason for the decision to "
"change the management software has been made. In this context, the moment of"
@@ -288,18 +286,18 @@ msgid ""
"business processes of the company."
msgstr ""
#: ../../getting_started/documentation.rst:202
msgid "6. Testing and Validation principles"
#: ../../getting_started/documentation.rst:204
msgid "Testing and Validation principles"
msgstr ""
#: ../../getting_started/documentation.rst:204
#: ../../getting_started/documentation.rst:206
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 ""
#: ../../getting_started/documentation.rst:208
#: ../../getting_started/documentation.rst:210
msgid ""
"**Role distribution**: In this context, the Consultant will be responsible "
"for delivering a solution corresponding to the defined specifications; the "
@@ -307,33 +305,33 @@ msgid ""
"requirements of the operational reality."
msgstr ""
#: ../../getting_started/documentation.rst:214
#: ../../getting_started/documentation.rst:216
msgid ""
"**Change management**: When a change needs to be made to the solution, the "
"noted gap is caused by:"
msgstr ""
#: ../../getting_started/documentation.rst:218
#: ../../getting_started/documentation.rst:220
msgid ""
"A difference between the specification and the delivered solution - This is "
"a correction for which the Consultant is responsible"
msgstr ""
#: ../../getting_started/documentation.rst:220
#: ../../getting_started/documentation.rst:223
msgid "**or**"
msgstr ""
#: ../../getting_started/documentation.rst:222
#: ../../getting_started/documentation.rst:225
msgid ""
"A difference between the specification and the imperatives of operational "
"reality - This is a change that is the responsibility of SPoC."
msgstr ""
#: ../../getting_started/documentation.rst:226
msgid "7. Data Imports"
#: ../../getting_started/documentation.rst:229
msgid "Data Imports"
msgstr ""
#: ../../getting_started/documentation.rst:228
#: ../../getting_started/documentation.rst:231
msgid ""
"Importing the history of transactional data is an important issue and must "
"be answered appropriately to allow the project running smoothly. Indeed, "
@@ -342,14 +340,14 @@ msgid ""
"it will be decided :"
msgstr ""
#: ../../getting_started/documentation.rst:234
#: ../../getting_started/documentation.rst:237
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 ""
#: ../../getting_started/documentation.rst:239
#: ../../getting_started/documentation.rst:242
msgid ""
"**To import a limited amount of data before going into production**: When "
"the data history relates to information being processed (purchase orders, "
@@ -358,7 +356,7 @@ msgid ""
" import will be made before the production launch."
msgstr ""
#: ../../getting_started/documentation.rst:246
#: ../../getting_started/documentation.rst:249
msgid ""
"**To import after production launch**: When the data history needs to be "
"integrated with Odoo mainly for reporting purposes, it is clear that these "
@@ -366,16 +364,16 @@ msgid ""
"production launch of the solution will precede the required imports."
msgstr ""
#: ../../getting_started/documentation.rst:253
msgid "8. Support"
#: ../../getting_started/documentation.rst:256
msgid "Support"
msgstr ""
#: ../../getting_started/documentation.rst:255
#: ../../getting_started/documentation.rst:258
msgid ""
"When your project is put in production, our support teams take care of your "
"questions or technical issues."
msgstr ""
#: ../../getting_started/documentation.rst:258
#: ../../getting_started/documentation.rst:261
msgid "See :ref:`support-expectations`."
msgstr ""