[I18N] *: export pot files

And fetch matching translations
This commit is contained in:
Martin Trigaux
2021-05-18 07:16:30 +02:00
parent 8ad392222b
commit e9d06b7881
514 changed files with 290877 additions and 436984 deletions
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
-973
View File
@@ -1,973 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
# kaj nithi <kajanth.nithiy@skipthedishes.ca>, 2020
# Renaud de Colombel <rdecolombel@sgen.cfdt.fr>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
# 0169fee580ff5de3f9b7241d14f30af9_5f30934 <1948a2319336319ed4429b6139c8c1c2_916898>, 2020
# Cécile Collart <cco@odoo.com>, 2021
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-02-04 11:02+0100\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Last-Translator: Cécile Collart <cco@odoo.com>, 2021\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../discuss.rst:5
msgid "Discuss"
msgstr "Discussion"
#: ../../discuss/advanced.rst:3
msgid "Advanced"
msgstr "Avancé"
#: ../../discuss/advanced/email_servers.rst:3
msgid "How to Use my Mail Server to Send and Receive Emails in Odoo"
msgstr ""
"Comment utiliser mon serveur de messagerie pour envoyer et recevoir des "
"emails dans Odoo"
#: ../../discuss/advanced/email_servers.rst:6
msgid "If you are a user of Odoo Online or Odoo.sh..."
msgstr "Si vous êtes un utilisateur d'Odoo en ligne ou d'Odoo.sh..."
#: ../../discuss/advanced/email_servers.rst:8
msgid ""
"You have nothing to do! **Odoo sets up its own mail servers for your "
"database.** Outgoing and incoming emails work out-of-the-box!"
msgstr ""
"Vous ne devez rien faire! **Odoo configure ses propres serveurs de "
"messagerie pour votre base de données.** Les emails sortants et entrants "
"sont prêts à l'emploi!"
#: ../../discuss/advanced/email_servers.rst:11
msgid ""
"Unless you plan to send large batches of mass mailing that could require the"
" use of an external mail server, simply enjoy your new Odoo database."
msgstr ""
"À moins que vous ne prévoyez d'envoyer une quantité importante d'emails de "
"masse qui nécessiteraient l'utilisation d'un serveur de messagerie externe, "
"profitez tout simplement de votre nouvelle base de données Odoo."
#: ../../discuss/advanced/email_servers.rst:16
msgid "Scope of this documentation"
msgstr "Le but de cette documentation"
#: ../../discuss/advanced/email_servers.rst:18
msgid ""
"This document is **mainly dedicated to Odoo on-premise users** who don't "
"benefit from an out-of-the-box solution to send and receive emails in Odoo, "
"unlike `Odoo Online <https://www.odoo.com/trial>`__ & `Odoo.sh "
"<https://www.odoo.sh>`__."
msgstr ""
"Ce document est **principalement destiné aux utilisateurs d'Odoo sur site** "
"qui ne bénéficient pas d'une utilisation prête à l'emploi pour l'envoi et la"
" réception d'emails dans Odoo, à la différence d'`Odoo en ligne "
"<https://www.odoo.com/trial>`__ & `Odoo.sh <https://www.odoo.sh>`__."
#: ../../discuss/advanced/email_servers.rst:25
msgid ""
"If no one in your company is used to manage email servers, we strongly "
"recommend that you opt for those Odoo hosting solutions. Their email system "
"works instantly and is monitored by professionals. Nevertheless you can "
"still use your own email servers if you want to manage your email server's "
"reputation yourself."
msgstr ""
"Si personne dans votre entreprise n'est chargé de la gestion des serveurs de"
" messagerie, nous vous recommandons fortement d'opter pour ces solutions "
"d'hébergement Odoo. Leur système de courrier électronique fonctionne "
"instantanément et est supervisé par des professionnels. Néanmoins, si vous "
"souhaitez gérer vous-même la réputation de votre serveur de messagerie, vous"
" pouvez également utiliser vos propres serveurs."
#: ../../discuss/advanced/email_servers.rst:31
msgid ""
"You will find here below some useful information on how to integrate your "
"own email solution with Odoo."
msgstr ""
"Vous trouverez ci-dessous quelques informations utiles pour intégrer votre "
"propre solution de messagerie à Odoo. "
#: ../../discuss/advanced/email_servers.rst:34
msgid ""
"Office 365 email servers don't easily allow to send external emails from "
"hosts like Odoo. Refer to `Microsoft's documentation "
"<https://support.office.com/en-us/article/How-to-set-up-a-multifunction-"
"device-or-application-to-send-email-using-"
"Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`__ to make it work."
msgstr ""
"Les serveurs de messagerie Office 365 ne permettent pas facilement d'envoyer"
" des emails externes à partir d'hôtes comme Odoo. Reportez-vous à la "
"documentation de Microsoft <https://support.office.com/en-us/article/How-to-"
"set-up-a-multifunction-device-or-application-to-send-email-using-"
"Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`__ pour le faire "
"fonctionner."
#: ../../discuss/advanced/email_servers.rst:39
msgid "How to manage outbound messages"
msgstr "Comment gérer les messages sortants"
#: ../../discuss/advanced/email_servers.rst:40
msgid ""
"As a system admin, go to :menuselection:`Settings --> General Settings` and "
"check *External Email Servers*. Then, click *Outgoing Mail Servers* to "
"create one and reference the SMTP data of your email server. Once all the "
"information has been filled out, click on *Test Connection*."
msgstr ""
"En tant qu'administrateur système, allez sur :menuselection:`Paramètres --> "
"Paramètres généraux` et cochez *Serveurs de messagerie externe*. Puis, "
"cliquez sur *Serveurs de messagerie sortant* pour en créer un et référencer "
"les données SMTP de votre serveur de messagerie. Une fois toutes les "
"informations complétées, cliquez sur *Tester la connection*."
#: ../../discuss/advanced/email_servers.rst:45
msgid "Here is a typical configuration for a G Suite server."
msgstr "Voici la configuration typique d'un serveur G suite."
#: ../../discuss/advanced/email_servers.rst:50
msgid "Then set your email domain name in the General Settings."
msgstr ""
"Configurez ensuite votre nom de domaine de messagerie dans les paramètres "
"généraux."
#: ../../discuss/advanced/email_servers.rst:53
msgid ""
"If you get a ``[AUTHENTICATIONFAILED] Invalid credentials (Failure)`` "
"warning when you *Test Connection* on a Gmail address, activate the *Less "
"secure app access* option. A direct link can be `accessed here "
"<https://myaccount.google.com/lesssecureapps?pli=1>`_."
msgstr ""
"Si vous recevez un message d'avertissement ``[AUTHENTICATIONFAILED] (Échec) "
"Identifiants invalides`` lorsque vous effectuez une *Connection de test* "
"dans une adresse Gmail, activez l'option *Accès moins sécurisé à "
"l'application*. Un lien direct est disponible `ici "
"<https://myaccount.google.com/lesssecureapps?pli=1>`_."
#: ../../discuss/advanced/email_servers.rst:57
msgid "In addition to that, enable the IMAP setting on your Gmail account."
msgstr "Activez par ailleurs le paramètre IMAP sur votre compte Gmail."
#: ../../discuss/advanced/email_servers.rst:61
msgid "Can I use an Office 365 server"
msgstr "Puis-je utiliser un serveur Office 365?"
#: ../../discuss/advanced/email_servers.rst:62
msgid ""
"You can use an Office 365 server if you run Odoo on-premise. Office 365 SMTP"
" relays are not compatible with Odoo Online."
msgstr ""
"Vous pouvez utiliser un serveur Office 365 si vous exécutez Odoo sur site. "
"Les relais Office 365 SMTP ne sont pas compatibles sur Odoo en ligne."
#: ../../discuss/advanced/email_servers.rst:65
msgid ""
"Please refer to `Microsoft's documentation <https://support.office.com/en-"
"us/article/How-to-set-up-a-multifunction-device-or-application-to-send-"
"email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`__ to configure"
" a SMTP relay for your Odoo's IP address."
msgstr ""
"Pour configurer un relais SMTP pour votre adresse IP Odoo, référez-vous à la"
" `Documentation Microsoft <https://support.office.com/en-us/article/How-to-"
"set-up-a-multifunction-device-or-application-to-send-email-using-"
"Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`__ ."
#: ../../discuss/advanced/email_servers.rst:69
msgid "How to use a G Suite server"
msgstr "Comment utiliser un serveur G suite"
#: ../../discuss/advanced/email_servers.rst:70
msgid ""
"You can use an G Suite server for any Odoo hosting type. To do so you need "
"to setup the SMTP relay service. The configuration steps are explained in "
"`Google documentation "
"<https://support.google.com/a/answer/2956491?hl=en>`__."
msgstr ""
"Vous pouvez utiliser un serveur G Suite pour n'importe quel type "
"d'hébergement Odoo. Pour cela, vous devez configurer le service relais SMTP."
" Les étapes de configuration sont décrites dans la `Documentation Google "
"<https://support.google.com/a/answer/2956491?hl=en>`__."
#: ../../discuss/advanced/email_servers.rst:77
msgid "Be SPF-compliant"
msgstr "Être en conformité avec le système SPF"
#: ../../discuss/advanced/email_servers.rst:78
msgid ""
"In case you use SPF (Sender Policy Framework) to increase the deliverability"
" of your outgoing emails, don't forget to authorize Odoo as a sending host "
"in your domain name settings. Here is the configuration for Odoo Online:"
msgstr ""
"Si vous utilisez le système SPF (Sender Policy Framework) pour augmenter la "
"délivrabilité de votre messagerie sortante, n'oubliez pas d'autoriser Odoo "
"en tant qu'hôte expéditeur dans les paramètres de votre nom de domaine. "
"Voici la configuration pour Odoo en ligne :"
#: ../../discuss/advanced/email_servers.rst:82
msgid ""
"If no TXT record is set for SPF, create one with following definition: "
"v=spf1 include:_spf.odoo.com ~all"
msgstr ""
"Si aucun enregistrement TXT n'est configuré pour le SPF, vous devez en créer"
" un avec la définition suivante : v=spf1 include:_spf.odoo.com ~all"
#: ../../discuss/advanced/email_servers.rst:84
msgid ""
"In case a SPF TXT record is already set, add \"include:_spf.odoo.com\". e.g."
" for a domain name that sends emails via Odoo Online and via G Suite it "
"could be: v=spf1 include:_spf.odoo.com include:_spf.google.com ~all"
msgstr ""
"Si un enregistrement SPF TXT est déjà configuré, ajoutez "
"\"include:_spf.odoo.com\". par ex. pour un nom de domaine qui envoie des "
"emails via Odoo en ligne et via G Suite cela pourrait être : v=spf1 "
"include:_spf.odoo.com include:_spf.google.com ~all"
#: ../../discuss/advanced/email_servers.rst:88
msgid ""
"Find `here <https://www.mail-tester.com/spf/>`__ the exact procedure to "
"create or modify TXT records in your own domain registrar."
msgstr ""
"Vous trouverez `ici <https://www.mail-tester.com/spf/>`__ la procédure "
"exacte pour créer ou modifier des enregistrements TXT sur votre propre "
"registraire de domaine."
#: ../../discuss/advanced/email_servers.rst:91
msgid ""
"Your new SPF record can take up to 48 hours to go into effect, but this "
"usually happens more quickly."
msgstr ""
"Votre nouvel enregistrement SPF peut prendre jusqu'à 48 heures pour être "
"effectif, mais d'habitude cela se fait plus rapidement."
#: ../../discuss/advanced/email_servers.rst:94
msgid ""
"Adding more than one SPF record for a domain can cause problems with mail "
"delivery and spam classification. Instead, we recommend using only one SPF "
"record by modifying it to authorize Odoo."
msgstr ""
"L'ajout de plus d'un enregistrement SPF à votre domaine peut générer des "
"problèmes à la livraison des emails et à la classification en spams. Nous "
"vous recommandons plutôt d'utiliser un seul enregistrement SPF, en modifiant"
" celui-ci pour autoriser Odoo."
#: ../../discuss/advanced/email_servers.rst:99
msgid "Allow DKIM"
msgstr "Activer DKIM"
#: ../../discuss/advanced/email_servers.rst:100
msgid ""
"You should do the same thing if DKIM (Domain Keys Identified Mail) is "
"enabled on your email server. In the case of Odoo Online & Odoo.sh, you "
"should add a DNS \"odoo._domainkey\" CNAME record to "
"\"odoo._domainkey.odoo.com\". For example, for \"foo.com\" they should have "
"a record \"odoo._domainkey.foo.com\" that is a CNAME with the value "
"\"odoo._domainkey.odoo.com\"."
msgstr ""
"Vous devriez faire la même chose si le DKIM (Domain Keys Identified Mail) "
"est activé sur votre serveur de messagerie. Dans le cas d'Odoo en ligne et "
"d' Odoo.sh, vous devez ajouter un enregistrement DNS CNAME "
"\"odoo._domainkey\" à \"odoo._domainkey.odoo.com\". Par exemple, pour "
"\"foo.com\" ils devraient avoir un enregistrement "
"\"odoo._domainkey.foo.com\" qui est un enregistrement CNAME avec la valeur "
"\"odoo._domainkey.odoo.com\"."
#: ../../discuss/advanced/email_servers.rst:108
msgid "Restriction"
msgstr "Restriction"
#: ../../discuss/advanced/email_servers.rst:109
msgid ""
"Please note that the port 25 is blocked for security reasons. Try using 587,"
" 465 or 2525."
msgstr ""
"Veuillez noter que le port 25 est bloqué pour des raisons de sécurité. "
"Essayez d'utiliser 587, 465 ou 2525."
#: ../../discuss/advanced/email_servers.rst:112
msgid "How to manage inbound messages"
msgstr "Comment gérer les messages entrants"
#: ../../discuss/advanced/email_servers.rst:114
msgid "Odoo relies on generic email aliases to fetch incoming messages."
msgstr "Odoo recourt à des alias email pour récupérer des messages entrants."
#: ../../discuss/advanced/email_servers.rst:116
msgid ""
"**Reply messages** of messages sent from Odoo are routed to their original "
"discussion thread (and to the inbox of all its followers) by the catchall "
"alias (**catchall@**)."
msgstr ""
"**Les emails de réponse automatiques** envoyés depuis Odoo sont acheminés "
"vers leur fil de discussion original (ainsi que vers les boîtes de réception"
" de tous les followers) via l'alias catch-all (**catchall@**)."
#: ../../discuss/advanced/email_servers.rst:120
msgid ""
"**Bounced messages** are routed to **bounce@** in order to track them in "
"Odoo. This is especially used in `Odoo Email Marketing "
"<https://www.odoo.com/page/email-marketing>`__ to opt-out invalid "
"recipients."
msgstr ""
"**Les emails rejetés** sont acheminés vers **bounce@** pour qu'on puisse les"
" tracer sur Odoo. Cela est surtout utilisé pour désinscrire les "
"destinataires invalides dans le `Marketing par courrier électronique Odoo "
"<https://www.odoo.com/page/email-marketing>`__ ."
#: ../../discuss/advanced/email_servers.rst:124
msgid ""
"**Original messages**: Several business objects have their own alias to "
"create new records in Odoo from incoming emails:"
msgstr ""
"**Les emails originaux**: Plusieurs objets de gestion ont leur propre alias "
"pour créer des nouveaux enregistrements sur Odoo depuis les emails entrants "
":"
#: ../../discuss/advanced/email_servers.rst:127
msgid ""
"Sales Channel (to create Leads or Opportunities in `Odoo CRM "
"<https://www.odoo.com/page/crm>`__),"
msgstr ""
"Canal de ventes (pour créer des pistes ou des opportunités dans `Odoo CRM "
"<https://www.odoo.com/page/crm>`__),"
#: ../../discuss/advanced/email_servers.rst:129
msgid ""
"Support Channel (to create Tickets in `Odoo Helpdesk "
"<https://www.odoo.com/page/helpdesk>`__),"
msgstr ""
"Canal de support (pour créer des tickets dans `Odoo Assistance technique "
"<https://www.odoo.com/page/helpdesk>`__),"
#: ../../discuss/advanced/email_servers.rst:131
msgid ""
"Projects (to create new Tasks in `Odoo Project <https://www.odoo.com/page"
"/project-management>`__),"
msgstr ""
"Projets (pour créer des nouvelles tâches dans `Odoo Projet "
"<https://www.odoo.com/page/project-management>`__),"
#: ../../discuss/advanced/email_servers.rst:133
msgid ""
"Job Positions (to create Applicants in `Odoo Recruitment "
"<https://www.odoo.com/page/recruitment>`__),"
msgstr ""
"Postes de travail (pour créer des candidats dans `Odoo recrutement "
"<https://www.odoo.com/page/recruitment>`__),"
#: ../../discuss/advanced/email_servers.rst:135
msgid "etc."
msgstr "etc"
#: ../../discuss/advanced/email_servers.rst:137
msgid ""
"Depending on your mail server, there might be several methods to fetch "
"emails. The easiest and most recommended method is to manage one email "
"address per Odoo alias in your mail server."
msgstr ""
"Selon votre serveur de messagerie, il peut y avoir plusieurs méthodes de "
"récupération des emails. La méthode la plus facile et la plus recommandée, "
"c'est gérer une adresse email par alias Odoo dans votre serveur de "
"messagerie ."
#: ../../discuss/advanced/email_servers.rst:141
msgid ""
"Create the corresponding email addresses in your mail server (catchall@, "
"bounce@, sales@, etc.)."
msgstr ""
"Créez les adresses email correspondantes dans votre serveur de messagerie "
"(catchall@, bounce@, sales@, etc.)."
#: ../../discuss/advanced/email_servers.rst:143
msgid "Set your domain name in the General Settings."
msgstr "Configurez votre nom de domaine dans les paramètres généraux."
#: ../../discuss/advanced/email_servers.rst:148
msgid ""
"If you use Odoo on-premise, create an *Incoming Mail Server* in Odoo for "
"each alias. You can do it from the General Settings as well. Fill out the "
"form according to your email providers settings. Leave the *Actions to "
"Perform on Incoming Mails* blank. Once all the information has been filled "
"out, click on *TEST & CONFIRM*."
msgstr ""
"Si vous utilisez Odoo sur site, créez un *Serveur de messagerie entrant* "
"pour chaque alias. Vous pouvez le faire également depuis les paramètres "
"généraux. Remplissez le formulaire selon les paramètres de votre fournisseur"
" de messagerie. Laissez vide le champ *Actions à effectuer sur les emails "
"entrants*. Une fois toutes les informations renseignées, cliquez sur *TESTER"
" & CONFIRMER*."
#: ../../discuss/advanced/email_servers.rst:157
msgid ""
"If you use Odoo Online or Odoo.sh, We do recommend to redirect incoming "
"messages to Odoo's domain name rather than exclusively use your own email "
"server. That way you will receive incoming messages without delay. Indeed, "
"Odoo Online is fetching incoming messages of external servers once per hour "
"only. You should set redirections for all the email addresses to Odoo's "
"domain name in your email server (e.g. *catchall@mydomain.ext* to "
"*catchall@mycompany.odoo.com*)."
msgstr ""
"Si vous utilisez Odoo Online ou Odoo.sh, nous vous recommandons de rediriger"
" les messages entrants vers le nom de domaine d'Odoo plutôt que d'utiliser "
"exclusivement votre propre serveur de messagerie. Vous recevrez ainsi les "
"messages entrants sans délai. En effet, Odoo Online ne récupère les messages"
" entrants des serveurs externes qu'une fois par heure. Vous devez définir "
"dans votre serveur de messagerie des redirections pour toutes les adresses "
"email vers le nom de domaine d'Odoo (par ex. *catchall@mydomain.ext* vers "
"*catchall@mycompany.odoo.com*)."
#: ../../discuss/advanced/email_servers.rst:167
msgid "All the aliases are customizable in Odoo."
msgstr "Tous les alias sont personnalisables dans Odoo."
#: ../../discuss/advanced/email_servers.rst:165
msgid ""
"Object aliases can be edited from their respective configuration view. To "
"edit catchall and bounce aliases, you first need to activate the "
":doc:`Developer mode <../../general/developer_mode/activate>`."
msgstr ""
"Les alias d'objet peuvent être modifiés depuis leur écran de configuration "
"respectif. Pour mlodifier des alias catchall et bounce, vous devez d'abord "
"activer :doc:`mode Développeur <../../general/developer_mode/activate>`."
#: ../../discuss/advanced/email_servers.rst:169
msgid ""
"Then go to :menuselection:`Settings --> Technical --> Parameters --> System "
"Parameters` to customize the aliases (*mail.catchall.alias* & * "
"mail.bounce.alias*)."
msgstr ""
"Puis aller sur :menuselection:`Configuration --> Technique --> Paramètres "
"--> Paramètres système` pour personnaliser les alias (*mail.catchall.alias* "
"& * mail.bounce.alias*)."
#: ../../discuss/advanced/email_servers.rst:175
msgid ""
"By default inbound messages are fetched every 5 minutes in Odoo on-premise. "
"You can change this value in :doc:`Developer mode "
"<../../general/developer_mode/activate>`. Go to :menuselection:`Settings -->"
" Technical --> Automation --> Scheduled Actions` and look for *Mail: "
"Fetchmail Service*."
msgstr ""
#: ../../discuss/advanced/email_template.rst:3
msgid "Email Templates"
msgstr "Modèles d'emails"
#: ../../discuss/advanced/email_template.rst:5
msgid ""
"We all know writing good emails is vital to get a high response rate, but "
"you do not want to rewrite the same structure every time, do you? That is "
"where email templates come in. Without the need to rewrite the entire email "
"structure every time, you save time to focus on the content. Multiple "
"templates also let you deliver the right message to the right audience, "
"improving their overall experience with the company."
msgstr ""
#: ../../discuss/advanced/email_template.rst:12
msgid "Enable it and understand a few concepts"
msgstr "Activez-le et comprenez quelques concepts"
#: ../../discuss/advanced/email_template.rst:14
msgid ""
"The :doc:`Developer mode <../../general/developer_mode/activate>` must be "
"activated. Then, go to :menuselection:`Settings --> Technical --> "
"Templates`. A view of the existing templates is shown."
msgstr ""
#: ../../discuss/advanced/email_template.rst:18
msgid ""
"**It is highly recommended not to change the content in existing templates "
"unless the user has prior knowledge about placeholders.**"
msgstr ""
"**Il est fortement recommandé de ne pas modifier le contenu des modèles "
"existants à moins que l'utilisateur n'ait des connaissances préalables à "
"propos des espaces réservés.**"
#: ../../discuss/advanced/email_template.rst:21
msgid ""
"To add a new one, click on *Create* and choose the type of document this "
"template is used with. In the example below, the template would be sent to "
"job applicants."
msgstr ""
"Pour en ajouter un nouveau, cliquez sur *Créer* et choisissez le type de "
"document avec lequel ce modèle est utilisé. Dans l'exemple ci-dessous, le "
"modèle serait envoyé aux candidats."
#: ../../discuss/advanced/email_template.rst:30
msgid ""
"Under *Email Configuration*, fields such as *From*, *To (Emails)*, *To "
"(Partners)*, require placeholders. If the *From* field is not set, the "
"default value is the authors email alias, if configured, or email address."
msgstr ""
"Sous *Configuration des emails*, des champs tels que *De*, *À (emails)*, *À "
"(partenaires)*, nécessitent des espaces réservés. Si le champ *De* n'est pas"
" défini, la valeur par défaut est l'alias de l'adresse email de l'auteur, "
"s'il est configuré, ou l'adresse email."
#: ../../discuss/advanced/email_template.rst:32
msgid ""
"Under *Advanced Settings*, if an *Outgoing Mail Server* is not set, the one "
"with the highest priority is used."
msgstr ""
"Sous *Paramètres avancés*, si un *Serveur de courrier sortant* n'est pas "
"défini, celui avec la priorité la plus élevée est utilisé."
#: ../../discuss/advanced/email_template.rst:34
msgid ""
"The option *Auto Delete* permanently deletes the emails after they are sent,"
" saving space in your database."
msgstr ""
"L'option *Suppression automatique* supprime définitivement les emails après "
"leur envoi, économisant ainsi de l'espace dans votre base de données."
#: ../../discuss/advanced/email_template.rst:37
msgid "Writing content including placeholder expressions"
msgstr ""
#: ../../discuss/advanced/email_template.rst:39
msgid ""
"Under the tab *Dynamic Placeholder Generator*, look for the *Field* you "
"would like to use."
msgstr ""
#: ../../discuss/advanced/email_template.rst:45
msgid ""
"Next, copy the *Placeholder Expression* and paste it in the *Body* of the "
"email, under the *Content* tab, using - essentially - the *Code View*."
msgstr ""
#: ../../discuss/advanced/email_template.rst:52
msgid ""
"Deactivate the *Code View* option by simply clicking on it again, and easily"
" design the message. Click on *Preview* to check how the email looks before "
"sending it."
msgstr ""
#: ../../discuss/overview.rst:3
msgid "Overview"
msgstr "Vue d'ensemble"
#: ../../discuss/overview/get_started.rst:3
msgid "Get Started with Discuss"
msgstr "Lancez-vous sur Discuter"
#: ../../discuss/overview/get_started.rst:5
msgid ""
"Discuss allows you to bring all of your companys communication together "
"through messages, notes, and chat. Share information, projects, files, "
"prioritize tasks, and stay connected with colleagues and partners throughout"
" applications. Forge better relationships, increase productivity and "
"transparency by promoting a convenient way of communicating."
msgstr ""
"L'app Discuter vous permet de rassembler toutes les communications de votre "
"entreprise via des messages, des notes et des discussions. Partagez des "
"informations, des projets, des fichiers, hiérarchisez les tâches et restez "
"connecté avec vos collègues et partenaires d'une application à l'autre. "
"Forgez de meilleures relations, augmentez la productivité et la transparence"
" en promouvant un moyen pratique de communiquer."
#: ../../discuss/overview/get_started.rst:11
msgid "Choose your notifications preference"
msgstr "Choisissez vos préférences de notifications"
#: ../../discuss/overview/get_started.rst:13
msgid ""
"Access your *Preferences* and choose how you would like your notifications "
"to be handled."
msgstr ""
"Accédez à vos *Préférences* et choisissez la manière dont vous souhaitez que"
" vos notifications soient traitées."
#: ../../discuss/overview/get_started.rst:21
msgid ""
"By default, the field is set as *Handle by Emails* making messages, notes, "
"and notifications where you were mentioned or that you follow, to be sent "
"through email. By choosing *Handle in Odoo*, they are shown in the *Inbox*."
msgstr ""
#: ../../discuss/overview/get_started.rst:22
msgid "Messages can then be *Marked as Todo*, *Replied*, or *Marked as Read*."
msgstr ""
"Les messages peuvent alors être marqués comme *A faire*, *Répondus* ou *Lus"
" *."
#: ../../discuss/overview/get_started.rst:28
msgid ""
"The messages tagged as *Mark as Todo* are also shown in *Starred*, while the"
" ones *Marked as Read* are moved to *History*."
msgstr ""
#: ../../discuss/overview/get_started.rst:36
msgid "Start Chatting"
msgstr "Commencer à discuter"
#: ../../discuss/overview/get_started.rst:38
msgid ""
"The first time you log in to your account, OdooBot sends you a message "
"asking for permission to receive desktop notifications to chats. If "
"accepted, you receive push notifications to the messages sent to you despite"
" of where you are in Odoo."
msgstr ""
"La première fois que vous vous connectez à votre compte, OdooBot vous envoie"
" un message vous demandant la permission de recevoir des notifications pour "
"les chats. Si vous acceptez, vous recevez des notifications push pour les "
"messages qui vous sont envoyés, peu importe où vous vous trouvez dans Odoo."
#: ../../discuss/overview/get_started.rst:48
msgid ""
"To stop receiving desktop notifications, reset the notifications settings of"
" your browser."
msgstr ""
"Pour ne plus recevoir de notifications, réinitialisez les paramètres de "
"notification de votre navigateur."
#: ../../discuss/overview/get_started.rst:50
msgid ""
"To start a chat, click on *New Message* on the *Messaging Menu*, or go to "
"*Discuss* and send a *Direct Message*."
msgstr ""
"Pour démarrer un chat, cliquez sur *Nouveau message* dans le *Menu "
"Messagerie*, ou allez dans l'application *Discuter* et envoyer un *Message "
"direct*."
#: ../../discuss/overview/get_started.rst:58
msgid ""
"You can also create :doc:`public and private channels <team_communication>`."
msgstr ""
#: ../../discuss/overview/get_started.rst:61
msgid "Mentions in the chat and on the Chatter"
msgstr "Mentions dans le chat et sur le Chatter"
#: ../../discuss/overview/get_started.rst:64
msgid ""
"To mention a user within a chat or the chatter type *@user-name*; to refer "
"to a channel, type *#channel-name*."
msgstr ""
"Pour mentionner un utilisateur dans un chat ou dans le chatter, tapez "
"*@nomdelutilisateur*; pour faire référence à un canal, tapez *#nomducanal*."
#: ../../discuss/overview/get_started.rst:66
msgid ""
"A notification is sent to the user mentioned either to his *Inbox* or "
"through email, depending on his settings."
msgstr ""
"Une notification est envoyée à l'utilisateur mentionné soit dans sa *boîte "
"de réception*, soit par email, en fonction de ses paramètres."
#: ../../discuss/overview/get_started.rst:73
msgid ""
"When a user is mentioned, the search list (list of names) suggests values "
"first based on the tasks followers, and secondly on *Employees*. If the "
"record being searched does not match with either a follower or employee, the"
" scope of the search becomes all partners."
msgstr ""
"Lorsqu'un utilisateur est mentionné, la liste de recherche (liste de noms) "
"suggère des valeurs d'abord basées sur les abonnés de la tâche, puis sur "
"*Employés*. Si l'enregistrement recherché ne correspond ni à un abonné ni à "
"un employé, l'étendue de la recherche passe à tous les partenaires."
#: ../../discuss/overview/get_started.rst:78
msgid "Chat status"
msgstr "Statut du chat"
#: ../../discuss/overview/get_started.rst:80
msgid ""
"It is helpful to see what colleagues are up to and how quickly they can "
"respond to messages by checking their *Status*. The status is shown on the "
"left side of a contacts names on Discuss sidebar and on the *Messaging "
"menu*."
msgstr ""
#: ../../discuss/overview/get_started.rst:84
msgid "Green = online"
msgstr "Vert = en ligne"
#: ../../discuss/overview/get_started.rst:85
msgid "Orange = away"
msgstr "Orange = absent"
#: ../../discuss/overview/get_started.rst:86
msgid "White = offline"
msgstr "Blanc = pas en ligne"
#: ../../discuss/overview/get_started.rst:87
msgid "Airplane = out of the office"
msgstr "Avion = en congé"
#: ../../discuss/overview/get_started.rst:95
#: ../../discuss/overview/plan_activities.rst:65
msgid ":doc:`team_communication`"
msgstr ":doc:`team_communication`"
#: ../../discuss/overview/get_started.rst:96
msgid ":doc:`../advanced/email_servers`"
msgstr ":doc:`../advanced/email_servers`"
#: ../../discuss/overview/plan_activities.rst:3
msgid "Get Organized by Planning Activities"
msgstr "Soyez organisé grâce à la planification d'activités"
#: ../../discuss/overview/plan_activities.rst:5
msgid ""
"When you plan activities you minimize the risk of uncertainties, as you "
"provide clear directions for the course of your next action. In addition to "
"that, you do not leave space for wasteful activities and reduce the chance "
"of having overlapping actions between team members."
msgstr ""
"Lorsque vous planifiez des activités, vous minimisez le risque "
"d'incertitudes, tout en donnant des instructions claires pour le déroulement"
" de votre prochaine action. De plus, vous ne laissez pas de place pour des "
"activités inutiles et réduisez le risque d'avoir des actions qui se "
"chevauchent entre les membres de l'équipe."
#: ../../discuss/overview/plan_activities.rst:10
msgid "Where do I see my schedule activities?"
msgstr "Où puis-je voir mes activités programmées?"
#: ../../discuss/overview/plan_activities.rst:12
msgid ""
"Access and manage your activities wherever you are in Odoo by the "
"*Activities* menu."
msgstr ""
"Accédez et gérez vos activités où que vous soyez dans Odoo grâce au menu "
"*Activités*."
#: ../../discuss/overview/plan_activities.rst:20
msgid "Plan activities"
msgstr "Planifiez des activités"
#: ../../discuss/overview/plan_activities.rst:22
msgid ""
"Activities can be planned and managed from the chatter by clicking on "
"*Schedule activity*, or through Kanban views."
msgstr ""
"Les activités peuvent être planifiées et gérées à partir du chatter en "
"cliquant sur *Planifier une activité*, ou via les vues Kanban."
#: ../../discuss/overview/plan_activities.rst:31
msgid "Set your activity types"
msgstr "Paramétrer vos types d'activités"
#: ../../discuss/overview/plan_activities.rst:33
msgid ""
"A number of activities types are available by default in Odoo (call, email, "
"meeting, etc.). However, you can set new ones going to "
":menuselection:`Settings --> Activity types`."
msgstr ""
#: ../../discuss/overview/plan_activities.rst:42
msgid ""
"If you need to create an activity type with an available calendar, make sure"
" to create it with an *Action to Perform* set as *Meeting*."
msgstr ""
"Si vous devez créer un type d'activité avec un calendrier disponible, "
"assurez-vous de le créer avec une *Action à effectuer* définie en tant que "
"*Réunion*."
#: ../../discuss/overview/plan_activities.rst:46
msgid "Recommend next activities"
msgstr "Recommandez les prochaines activités"
#: ../../discuss/overview/plan_activities.rst:48
msgid ""
"Odoo helps you to plan a flow of activities by allowing you to set "
"*Recommended Next Activities*."
msgstr ""
"Odoo vous aide à planifier un flux d'activités en vous permettant de définir"
" des *Activités suivantes recommandées*."
#: ../../discuss/overview/plan_activities.rst:55
msgid ""
"Once the respective activity is completed, select *Done & Schedule Next* and"
" next steps are suggested to you."
msgstr ""
"Une fois l'activité respective terminée, sélectionnez *Terminé et planifier "
"la suivante* et les étapes suivantes vous sont suggérées."
#: ../../discuss/overview/plan_activities.rst:64
#: ../../discuss/overview/team_communication.rst:115
msgid ":doc:`get_started`"
msgstr ":doc:`get_started`"
#: ../../discuss/overview/team_communication.rst:3
msgid "Efficiently Communicate Using Channels"
msgstr "Communiquez efficacement à l'aide des canaux"
#: ../../discuss/overview/team_communication.rst:5
msgid ""
"You can use channels to organize discussions between individual teams, "
"departments, projects, or any other group that requires regular "
"communication. This way, you keep everyone in the loop updated with the "
"latest developments."
msgstr ""
"Vous pouvez utiliser des canaux pour organiser des discussions entre des "
"équipes individuelles, des services, des projets ou tout autre groupe "
"nécessitant une communication régulière. De cette façon, vous gardez tout le"
" monde au courant des derniers événements."
#: ../../discuss/overview/team_communication.rst:10
msgid "Public and Private channels"
msgstr "Canaux publics et privés"
#: ../../discuss/overview/team_communication.rst:12
msgid ""
"A *Public* channel can be seen by everyone, while a *Private* one is only "
"visible to users invited to it."
msgstr ""
"Un canal *Public* peut être vu par tout le monde, tandis qu'un canal *Privé*"
" n'est visible que par les utilisateurs qui y sont invités."
#: ../../discuss/overview/team_communication.rst:21
msgid ""
"A public channel is best used when many employees need to access information"
" (such as company announcements), whereas a private channel could be used "
"whenever information should be limited to specific groups (such as a "
"specific department)."
msgstr ""
"Il est mieux d'utiliser un canal public lorsque de nombreux employés ont "
"besoin d'accéder à des informations (telles que les annonces de "
"l'entreprise), alors qu'un canal privé peut être utilisé chaque fois que les"
" informations doivent être limitées à des groupes spécifiques (comme un "
"service spécifique)."
#: ../../discuss/overview/team_communication.rst:26
msgid "Configuration options"
msgstr "Options de configuration"
#: ../../discuss/overview/team_communication.rst:28
msgid ""
"You can configure a channels name, description, email alias, and privacy by"
" clicking on the *Channel Settings* icon on the sidebar."
msgstr ""
"Vous pouvez configurer le nom, la description, l'alias de l'adresse email et"
" la confidentialité d'un canal en cliquant sur l'icône *Paramètres du canal*"
" dans la barre latérale."
#: ../../discuss/overview/team_communication.rst:36
msgid "Privacy and Members"
msgstr "Confidentialité et membres"
#: ../../discuss/overview/team_communication.rst:40
msgid ""
"Changing *Who can follow the groups activities?* allows you to control "
"which groups can have access to the channel. Note that allowing *Everyone* "
"to follow a private channel lets other users view and join it, as they would"
" a public one."
msgstr ""
#: ../../discuss/overview/team_communication.rst:42
msgid ""
"If you choose *Invited people only*, go to the *Members* tab to add your "
"members, or, go to Discuss main page, select the channel and click on "
"*Invite*."
msgstr ""
#: ../../discuss/overview/team_communication.rst:49
msgid ""
"For *Selected group of users*, the option *Auto Subscribe Groups* "
"automatically add its members as followers. In other words, while "
"*Authorized Groups* limits which users can access the channel, *Auto "
"Subscribe Groups* automatically adds the user as a member as long as they "
"are part of the group."
msgstr ""
#: ../../discuss/overview/team_communication.rst:55
msgid "Use a channel as a mailing list"
msgstr ""
#: ../../discuss/overview/team_communication.rst:57
msgid ""
"Choosing to *Send messages by email* configures the channel to behave as a "
"mailing list."
msgstr ""
#: ../../discuss/overview/team_communication.rst:59
msgid ""
"Enabling this option allows you to *Moderate this channel*, meaning that "
"messages will need to be approved before being sent."
msgstr ""
#: ../../discuss/overview/team_communication.rst:66
msgid ""
"Under the *Moderation* tab choose as many moderators as you need, and if you"
" would like them to receive an *Automatic notification*."
msgstr ""
#: ../../discuss/overview/team_communication.rst:67
msgid ""
"Mark *Send guidelines to new subscribers* to automatically send instructions"
" to newcomers."
msgstr ""
#: ../../discuss/overview/team_communication.rst:73
msgid ""
"Moderators can: *Accept*, *Reject*, *Discard*, *Always Allow* or *Ban* "
"messages."
msgstr ""
"Les modérateurs peuvent: *Accepter*, *Rejeter*, *Ignorer*, *Toujours "
"autoriser* ou *Interdire* les messages."
#: ../../discuss/overview/team_communication.rst:80
msgid ""
"Members of a mailing channel receive messages through email regardless of "
"their :doc:`notification preference <get_started>`."
msgstr ""
#: ../../discuss/overview/team_communication.rst:83
msgid ""
"Once a channel is moderated, the menu *Ban List* allows you to add email "
"addresses per moderated channel to auto-ban them from sending messages."
msgstr ""
#: ../../discuss/overview/team_communication.rst:91
msgid "Quick search bar"
msgstr "Barre de recherche rapide"
#: ../../discuss/overview/team_communication.rst:93
msgid ""
"Once at least 20 channels, direct message and live chat conversations (if "
"the module is installed on your database) are pinned in the sidebar, a "
"*Quick search…* bar is displayed. It is a clever way to filter conversations"
" and quickly find the one you need."
msgstr ""
"Une fois qu'au moins 20 canaux, messages directs et conversations de chat en"
" direct (si le module est installé sur votre base de données), sont épinglés"
" dans la barre latérale, une barre *Recherche rapide…* s'affiche. C'est un "
"moyen intelligent de filtrer les conversations et de trouver rapidement "
"celle dont vous avez besoin."
#: ../../discuss/overview/team_communication.rst:103
msgid "Finding channels"
msgstr "Trouvez des canaux"
#: ../../discuss/overview/team_communication.rst:106
msgid ""
"Click on *Channels* (on the sidebar), browse through the list of public "
"channels, and join or leave them from a single screen."
msgstr ""
"Cliquez sur *Canaux* (dans la barre latérale), parcourez la liste des canaux"
" publics et rejoignez-les ou quittez-les depuis un seul écran."
#: ../../discuss/overview/team_communication.rst:108
msgid ""
"Apply filters criteria and save it for later use. The search function "
"accepts wildcards by using the underscore character *(_)* to represent a "
"single character."
msgstr ""
#: ../../discuss/overview/team_communication.rst:116
msgid ":doc:`plan_activities`"
msgstr ":doc:`plan_activities`"
File diff suppressed because it is too large Load Diff
-290
View File
@@ -1,290 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
# Eloïse Stilmant <est@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Last-Translator: Eloïse Stilmant <est@odoo.com>, 2020\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../email_marketing.rst:5
msgid "Email Marketing"
msgstr "Email Marketing"
#: ../../email_marketing/overview.rst:3
msgid "Overview"
msgstr "Vue d'ensemble"
#: ../../email_marketing/overview/mailing_lists.rst:3
msgid "Work with Mailing Lists"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:5
msgid ""
"Mailing lists can be a goldmine for your companys marketing department as "
"they can provide leads for sales, focus groups for testing new products, and"
" consumers to provide feedback on satisfaction, for example."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:10
msgid "Create mailing lists"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:12
msgid ""
"Go to :menuselection:`Mailing lists --> Mailing lists --> Create`. Enable "
"the option *Is Public* to make the list visible for users when "
"unsubscribing."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:19
msgid ""
"Once your mailing list is created, you can manually add contacts clicking on"
" *Create*. *Import* a list of contacts if you have it from a previous tool."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:23
msgid "Linking a mailing list to my website"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:26
msgid ""
"Create a mailing list called Newsletter, as you use this strategy to "
"advertise and communicate new ideas to subscribers interested in listening."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:27
msgid ""
"Go to your *Website*, add a *Newsletter* block and choose the respective "
"mailing list."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:34
msgid "Contacts"
msgstr "Contacts"
#: ../../email_marketing/overview/mailing_lists.rst:36
msgid ""
"Under :menuselection:`Mailing Lists --> Mailing List Contacts` see a list of"
" all contacts under all your mailing lists, and the ones you individually "
"created here."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:43
msgid ""
"Open a contact form to see or add different mailing lists to which the "
"contact is or will be part of."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:51
#: ../../email_marketing/overview/manage_unsubscriptions.rst:46
msgid ":doc:`send_emails`"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:3
msgid "Manage Unsubscriptions and Blacklist"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:5
msgid ""
"It is best practice, and legally required, to allow recipients to "
"unsubscribe from mailing lists as you do not want your audience to think "
"that your company is using any tactics that are dishonest or spammy."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:10
msgid "Enable the Blacklist feature"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:12
msgid ""
"Go to :menuselection:`Configuration --> Settings` and enable the option "
"*Blacklist Option when Unsubscribing*."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:19
msgid ""
"Now, once the user clicks on the *Unsubscribe* link on your email, he is "
"redirected to the following page:"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:28
msgid ""
"After clicking on the unsubscribe button when using the test feature, you "
"are sent to an error page (*error 403 - Access Denied*). If you want to be "
"sure the link is working properly, create your mass mail and send it only to"
" a personal email."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:32
msgid ""
"In addition to having the option of unsubscribing from specific mailing "
"lists, the user can also blacklist himself, meaning that he will not receive"
" *any* more emails from you."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:36
msgid ""
"The mailing list has to be configured as *Public* in order to be visible for"
" users."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:38
msgid ""
"Under :menuselection:`Configuration --> Blacklist`, blacklisted email "
"addresses are shown."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:39
msgid ""
"When opening the record, as a *Log note*, a description-history is kept."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:47
msgid ":doc:`mailing_lists`"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:3
msgid "Send Emails Marketing and Manage Campaigns"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:5
msgid ""
"Emails allow you to effectively, and at a low cost, reach a large number of "
"consumers while being able to customize your message in a way that resonates"
" with them. It is measurable, and a call-to-action oriented channel."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:10
msgid "Choose the right target and create the message"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:12
msgid "Go to :menuselection:`Mailings --> Create`."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:14
msgid ""
"Choosing *Contacts* as *Recipients* (for example), allows you to add "
"specifications to match just certain contacts, filtering your target."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:21
msgid ""
"With a trial databases, you have a limit of 50 emails per day; on Odoo SH "
"Cloud Platform the limit is 200. There is a possibility to increase these "
"numbers by contacting Odoo Support. To contact Support, `click here "
"<https://www.odoo.com/help>`_."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:25
msgid ""
"Under *Mail Body*, choose a layout and make the modifications needed by "
"dragging, dropping and double-clicking on content. Note that it is possible "
"to start from scratch selecting the *blank* template option."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:34
msgid ""
"Under *Settings*, you can assign someone else as the responsible sender if "
"you do not want it to be you. To do so, change the email address used as the"
" sender (*Send From*)."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:37
msgid ""
"With the *Reply To* radio button, you can also choose to gather answers "
"either on the respective recipients records or on a specific email address."
" Note that this option is not available if you target mailing contacts or "
"contacts as recipients."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:45
msgid "Test, send or schedule a mailing"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:53
msgid ""
"*Save*: the work is allocated in the *draft* column in the Kanban view. "
"Modifications can be made while being in this stage. The option *Discard* "
"deletes the email."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:54
msgid ""
"Click on *Test* and send your message to one, or even multiple, test "
"contacts to avoid errors."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:56
msgid ""
"*Send* triggers the email with the next run and put the work on the *queue* "
"column in the Kanban view."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:58
msgid ""
"*Schedule* allows you to choose a date and time, and puts the email in the "
"*queue* column in the Kanban view."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:61
msgid ""
"The daily limit is applied for **all emails** sent, in other words, "
"throughout all applications. Therefore, if at the end of the day you have "
"remaining ones to be sent, note that they *will not* be sent automatically "
"the next day. You need to force that by opening the email and clicking on "
"*Retry*."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:67
msgid "Manage campaigns"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:69
msgid ""
"Go to :menuselection:`Configuration --> Settings` and enable *Mailing "
"Campaigns*."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:71
msgid ""
"The campaign option is effective as it allows you to organize your marketing"
" efforts and have a centralized view of its metrics."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:72
msgid "Go to *Campaign* and click on *Create* to start one."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:80
msgid ""
"If you use the SMS and Social Marketing applications, as well as the Push "
"Notification feature, you see the option to create content for those "
"channels. You also see the *Campaign* menu within those applications. All of"
" this is possible because the applications work integrated."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:85
msgid ":doc:`../../discuss/advanced/email_servers`"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:86
msgid ":doc:`../../social_marketing/overview/campaigns`"
msgstr ""
-438
View File
@@ -1,438 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# David David <f322p3ph@yahoo.fr>, 2020
# Martin Trigaux, 2020
# Adriana Ierfino <adriana.ierfino@savoirfairelinux.com>, 2020
# Hamid Darabi, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
# Cécile Collart <cco@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Last-Translator: Cécile Collart <cco@odoo.com>, 2020\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../events.rst:5
msgid "Events"
msgstr "Événements"
#: ../../events/integrations.rst:3
msgid "Integrations"
msgstr "Intégrations"
#: ../../events/integrations/integration_sms.rst:3
msgid "Communicating about my Event using SMS Text Messages"
msgstr ""
#: ../../events/integrations/integration_sms.rst:5
msgid ""
"Using SMS as a communication strategy for your event establishes interaction"
" between organizers, attendees, speakers and further targets. It allows your"
" message to be heard whether the goal is to send out reminders, teasers or "
"to advertise."
msgstr ""
#: ../../events/integrations/integration_sms.rst:10
#: ../../events/overview/tickets.rst:9 ../../events/overview/track_talks.rst:9
msgid "Configuration"
msgstr "Configuration"
#: ../../events/integrations/integration_sms.rst:13
msgid ""
"Under *Communication* SMS is a standard feature. That means nothing needs to"
" be enabled or installed."
msgstr ""
#: ../../events/integrations/integration_sms.rst:16
msgid ""
"On the other hand, to contact the speakers of your event, you need the *SMS "
"Marketing* application installed, and to enable *Schedule & Tracks* under "
":menuselection:`Events --> Configuration --> Settings`."
msgstr ""
#: ../../events/integrations/integration_sms.rst:23
msgid ""
"The *Schedule & Tracks* feature allows you to manage the agenda and speakers"
" of your event. For more details watch: `Creating an agenda for your event "
"<https://www.odoo.com/slides/slide/create-an-agenda-for-your-"
"event-717?fullscreen=1>`_."
msgstr ""
#: ../../events/integrations/integration_sms.rst:28
msgid "Send SMSs to attendees"
msgstr ""
#: ../../events/integrations/integration_sms.rst:30
msgid ""
"Under *Communication*, the messages target is the attendees of your event."
msgstr ""
#: ../../events/integrations/integration_sms.rst:32
msgid ""
"You can choose to confirm each registration with the *Registration* "
"template, and to send a reminder shortly before the event takes place with "
"the *Reminder* template."
msgstr ""
#: ../../events/integrations/integration_sms.rst:38
msgid "To make changes in an existing template, click on the external link."
msgstr ""
#: ../../events/integrations/integration_sms.rst:45
msgid "Send SMSs to speakers and further targets"
msgstr ""
#: ../../events/integrations/integration_sms.rst:47
msgid ""
"The benefit of the integration with the *SMS Marketing* application is that "
"you can choose the target you would like your message to be delivered to. To"
" get started, click on *Contact Track Speakers*."
msgstr ""
#: ../../events/integrations/integration_sms.rst:56
msgid ""
"If *Event Track* is not your target (*Recipient*), choose the right one. "
"*Filters* are eligible here."
msgstr ""
#: ../../events/integrations/integration_sms.rst:58
msgid ""
"In the example below, the SMS would be sent to the speakers who are in the "
"stage *Proposal* on *Event Track*."
msgstr ""
#: ../../events/integrations/integration_sms.rst:65
msgid ""
"Credits are required to be able to send SMSs. For more information about "
"Pricing :doc:`click here <../../sms_marketing/pricing/pricing_and_faq>`, "
"and, about IAP Services :doc:`here "
"<../../general/in_app_purchase/in_app_purchase>`."
msgstr ""
#: ../../events/overview.rst:3
msgid "Overview"
msgstr "Vue d'ensemble"
#: ../../events/overview/create_event.rst:3
msgid "Create your First Event"
msgstr ""
#: ../../events/overview/create_event.rst:5
msgid "Some of the reasons why hosting events is essential are:"
msgstr ""
#: ../../events/overview/create_event.rst:7
msgid "To create an engaging experience with your audience;"
msgstr ""
#: ../../events/overview/create_event.rst:8
msgid "To generate word of mouth about your company;"
msgstr ""
#: ../../events/overview/create_event.rst:9
msgid "To allow networking;"
msgstr ""
#: ../../events/overview/create_event.rst:10
msgid ""
"To provide an opportunity for sales representatives to walk their prospects "
"through the product and even their pipeline."
msgstr ""
#: ../../events/overview/create_event.rst:14
msgid "Get started"
msgstr "Démarrer"
#: ../../events/overview/create_event.rst:16
msgid ""
"Under the menu *Events*, have a view of all existing events and some key "
"information, such as the number of expected and confirmed attendees."
msgstr ""
#: ../../events/overview/create_event.rst:23
msgid ""
"To start a new one, click on *Create* and fill in the form with all the "
"needed information. Enable *Website Menu* to have the menus *Introduction*, "
"*Location*, and *Register* being shown on your events website page."
msgstr ""
#: ../../events/overview/create_event.rst:31
msgid ""
"To personalize these pages, click on *Edit* to open the `website builder "
"<https://www.odoo.com/slides/slide/website-basics-643?fullscreen=1>`_, and "
"edit content by dragging and dropping blocks."
msgstr ""
#: ../../events/overview/create_event.rst:40
msgid "Tab: Tickets"
msgstr ""
#: ../../events/overview/create_event.rst:43
msgid ""
"Go to :menuselection:`Events --> Configuration --> Settings` and enable "
":doc:`Tickets and Online Ticketing <tickets>`."
msgstr ""
#: ../../events/overview/create_event.rst:46
msgid ""
"Now, under the *Tickets* Tab, add lines to include the different ticket "
"types you offer. Include the price, the start and end dates for "
"registrations, and even the maximum number of tickets that can be sold."
msgstr ""
#: ../../events/overview/create_event.rst:48
msgid ""
"The *Reserved Seats* and *Unconfirmed Seat Reservations* are counted as "
"attendees are marked as :doc:`confirmed <track_attendees>` or not."
msgstr ""
#: ../../events/overview/create_event.rst:55
msgid "Tab: Communication"
msgstr ""
#: ../../events/overview/create_event.rst:58
msgid ""
"Choose the email and/or SMS message template, as well as the frequency with "
"which you would like to communicate with your attendees under the tab "
"*Communication*."
msgstr ""
#: ../../events/overview/create_event.rst:61
msgid ""
"Create a template on the fly or choose an existing one. Define the "
"*Interval* (2, 7, 15..) for the *Unit* (days, hours, weeks, etc.), and the "
"*Trigger* action (after registration, after the event, etc.)."
msgstr ""
#: ../../events/overview/create_event.rst:68
msgid "Tab: Questions"
msgstr ""
#: ../../events/overview/create_event.rst:70
msgid ""
"Go to :menuselection:`Configuration --> Settings` and enable *Questions*."
msgstr ""
#: ../../events/overview/create_event.rst:72
msgid ""
"Now, under the tab *Questions*, edit your questions and answers, choosing if"
" you would like your questionnaire to be asked per order or per "
"registration."
msgstr ""
#: ../../events/overview/create_event.rst:75
msgid ""
"Example of a registration for 3 attendees: if enabling the option *Ask each "
"attendee*, the questionnaire is shown 3 times, meaning that answers can vary"
" for each attendee; if *Ask each attendee* is not enabled, the questionnaire"
" is shown once, resulting in a global answer."
msgstr ""
#: ../../events/overview/create_event.rst:81
msgid ""
"Once your event is *Confirmed*, you can manage attendees badges, and mark "
"the event as *Finished*. Events marked as *Finished* can be *Set to draft*, "
"putting the event back to an *Unconfirmed* stage from which it can be edited"
" and used again."
msgstr ""
#: ../../events/overview/create_event.rst:90
msgid "Publish your event"
msgstr "Publiez votre événement"
#: ../../events/overview/create_event.rst:92
msgid "*Go to Website* and turn *Published* on."
msgstr ""
#: ../../events/overview/create_event.rst:99
msgid ":doc:`track_attendees`"
msgstr ""
#: ../../events/overview/create_event.rst:100
#: ../../events/overview/track_attendees.rst:45
msgid ":doc:`tickets`"
msgstr ""
#: ../../events/overview/create_event.rst:101
#: ../../events/overview/track_attendees.rst:46
msgid ":doc:`track_talks`"
msgstr ""
#: ../../events/overview/tickets.rst:3
msgid "Selling Tickets"
msgstr ""
#: ../../events/overview/tickets.rst:5
msgid ""
"If you automate processes, you save time. If you give attendees multiple "
"payment options to choose from, you allow flexibility and open margins for "
"more registrations to happen."
msgstr ""
#: ../../events/overview/tickets.rst:11
msgid ""
"Go to :menuselection:`Configuration --> Settings` and activate *Tickets* and"
" *Online Ticketing*."
msgstr ""
#: ../../events/overview/tickets.rst:13
msgid ""
"*Tickets* allow tickets to be sold "
":ref:`events/create_event/through_sales_orders`. *Online Ticketing* allows "
"the sale of tickets to happen "
":ref:`events/create_event/through_the_website`."
msgstr ""
#: ../../events/overview/tickets.rst:22
msgid "Through Sales Orders"
msgstr ""
#: ../../events/overview/tickets.rst:24
msgid ""
"On the *Sales* application, choose the event product you created and add it "
"as a product line. A window pops-up, allowing you to choose the event for "
"which you want to create the sales order."
msgstr ""
#: ../../events/overview/tickets.rst:32
msgid ""
"Remember to create a product form for the event registration, under "
"*Product*, in the *Sales* application, and to add that same product under "
"your events form."
msgstr ""
#: ../../events/overview/tickets.rst:43
msgid "Through the Website"
msgstr ""
#: ../../events/overview/tickets.rst:45
msgid ""
"On the website, once tickets are added to the cart, the user can continue "
"the transaction choosing among the payment methods you chose to have "
"available."
msgstr ""
#: ../../events/overview/tickets.rst:53
msgid ":doc:`../../general/payment_acquirers/payment_acquirers`"
msgstr ""
#: ../../events/overview/track_attendees.rst:3
msgid "Track your Attendees"
msgstr ""
#: ../../events/overview/track_attendees.rst:5
msgid ""
"Attendees are at the heart of your event. Keeping track of their number and "
"managing their registration and attendance is necessary for planning and "
"analyzing reasons."
msgstr ""
#: ../../events/overview/track_attendees.rst:9
msgid "Attendees list and attendance"
msgstr ""
#: ../../events/overview/track_attendees.rst:11
msgid ""
"Once attendees have registered or bought their tickets, they are added to "
"the *Attendees* list."
msgstr ""
#: ../../events/overview/track_attendees.rst:12
msgid ""
"Tickets sold through sales orders validate attendees as soon as the "
"quotation is confirmed."
msgstr ""
#: ../../events/overview/track_attendees.rst:18
msgid ""
"The check mark button is used to confirm the registration. Once a "
"registration is confirmed, attendance can be marked."
msgstr ""
#: ../../events/overview/track_attendees.rst:26
msgid "Bagdes and cancellations"
msgstr ""
#: ../../events/overview/track_attendees.rst:28
msgid ""
"On the attendees form, choose to send badges manually by clicking on *Send "
"By Email*. *Cancel Registration* to have that attendee being moved to the "
"*Cancelled* stage."
msgstr ""
#: ../../events/overview/track_attendees.rst:36
msgid ""
"To see a list of your canceled attendees, under *Filters*, add a *Custom "
"Filter* choosing *Status > is > Cancelled*."
msgstr ""
#: ../../events/overview/track_attendees.rst:44
#: ../../events/overview/track_talks.rst:49
msgid ":doc:`../integrations/integration_sms`"
msgstr ""
#: ../../events/overview/track_talks.rst:3
msgid "Track and Manage Talks"
msgstr ""
#: ../../events/overview/track_talks.rst:5
msgid ""
"Allow partners to submit talk proposals so they can share their knowledge "
"and expertise. Good speakers and talks are what make your event great."
msgstr ""
#: ../../events/overview/track_talks.rst:11
msgid ""
"Go to :menuselection:`Events --> Configuration --> Settings` and enable "
"*Schedule & Tracks*."
msgstr ""
#: ../../events/overview/track_talks.rst:14
msgid ""
"Now, in your event's form, once *Website menu* is enabled, the options "
"*Tracks on Website* and *Track Proposals on Website* become available. "
"Enabling them adds the menus *Talks*, *Talk Proposals*, and *Agenda* to your"
" website."
msgstr ""
#: ../../events/overview/track_talks.rst:20
msgid ""
"Besides having the ability to suggest their own talks, the website now "
"allows users to see a list of the whole agenda and scheduled talks."
msgstr ""
#: ../../events/overview/track_talks.rst:28
msgid ""
"To handle tracks internally and not have the menus *Talks*, *Talk "
"Proposals*, and *Agenda* online, use the menu *Tracks* individually."
msgstr ""
#: ../../events/overview/track_talks.rst:32
msgid "Publishing speaker proposals"
msgstr ""
#: ../../events/overview/track_talks.rst:34
msgid ""
"Once partners have filled in the appropriate form and submitted their "
"proposals, a new *Proposal* is instantly created under the menu *Track*."
msgstr ""
#: ../../events/overview/track_talks.rst:41
msgid ""
"If the proposal is accepted and can go online, simply open its form and "
"click on *Go to Website*. From the website page, turn *Published* on."
msgstr ""
-437
View File
@@ -1,437 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Cécile Collart <cco@odoo.com>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
# 0169fee580ff5de3f9b7241d14f30af9_5f30934 <1948a2319336319ed4429b6139c8c1c2_916898>, 2020
# Ludvig Auvens <lau@odoo.com>, 2021
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-02-04 11:02+0100\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Last-Translator: Ludvig Auvens <lau@odoo.com>, 2021\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../expense/expense.rst:5
msgid "Expenses"
msgstr "Dépenses"
#: ../../expense/expense.rst:8
msgid "How to set expense types"
msgstr "Comment configurer les types de dépenses"
#: ../../expense/expense.rst:9
msgid ""
"The first step to track expenses is to configure the expense types (managed "
"as products in Odoo) that your company allows, from the *Configuration* "
"menu. When a specific expense is reimbursed at a fixed price, set a cost on "
"the product. Otherwise keep the cost at 0.0 and employees will report the "
"real cost per expense."
msgstr ""
"La première étape pour faire le suivi de vos dépenses est la configuration "
"des types de dépenses (gérés comme produits dans Odoo) autorisées par votre "
"entreprise, depuis le menu *Configuration*. Lorsqu'une dépense spécifique "
"est remboursée à un prix fixe, définissez un coût pour le produit. Sinon, "
"maintenez le coût à 0,0 et les employés indiqueront le coût réel par "
"dépense."
#: ../../expense/expense.rst:17
msgid "Here are some examples to configure:"
msgstr "Voici quelques exemples de configuration :"
#: ../../expense/expense.rst:19
msgid "Restaurant:"
msgstr "Restaurant :"
#: ../../expense/expense.rst:21 ../../expense/expense.rst:27
msgid "Cost: 0.00 (the cost of the ticket will be recorded on every expense)"
msgstr "Coût : 0.00 (le coût du ticket sera enregistré sur chaque dépense)."
#: ../../expense/expense.rst:22
msgid "Travel with Personal Car:"
msgstr "Déplacement avec une voiture personnelle :"
#: ../../expense/expense.rst:24
msgid "Cost: 0.30 (the price per mile reimbursed by the company is fixed)"
msgstr ""
"Coût : 0.30 (le prix du kilomètre remboursé par l'entreprise est fixe)."
#: ../../expense/expense.rst:25
msgid "Hotel:"
msgstr "Hôtel :"
#: ../../expense/expense.rst:29
msgid "Others:"
msgstr "Autres :"
#: ../../expense/expense.rst:31
msgid "Cost: 0.0"
msgstr "Côut: 0.0"
#: ../../expense/expense.rst:33
msgid ""
"Don't forget to set an expense tax on each expense type (and an account if "
"you use Odoo Accounting). It's usually a good practice to use a tax that is "
"configured with :ref:`Tax Included in Price <taxes/included-in-price>`. That"
" way, employees report expenses with prices including taxes, which is "
"usually the expected behaviour."
msgstr ""
#: ../../expense/expense.rst:41
msgid ""
"The *Sales* app allows you to specify unit of measures for your expense "
"types (units, miles, nights, etc.). Go to :menuselection:`Sales --> "
"Configuration --> Settings` and check *Some products may be sold/purchased "
"in different units of measure (advanced)*."
msgstr ""
"L'application *Ventes* vous permet de spécifier l'unité de mesures pour les "
"types de dépenses (unités, kilomètres, nuits, etc.). Allez à "
":menuselection:`Ventes --> Configuration --> Paramètres` et vérifiez "
"*Certains produits peuvent être vendus/achetés dans différentes unités de "
"mesures (avancé)*."
#: ../../expense/expense.rst:48
msgid "How to record expenses"
msgstr "Comment enregistrer les dépenses"
#: ../../expense/expense.rst:51
msgid "Manually"
msgstr "Manuellement"
#: ../../expense/expense.rst:53
msgid ""
"As an employee (Employee in user access rights), you can record expenses "
"from :menuselection:`My Expenses --> Expenses to Submit`."
msgstr ""
"En tant qu'employé (employé en droits d'accès), vous pouvez enregistrer vos "
"dépenses depuis :menuselection:`Mes dépenses --> Dépenses à soumettre`."
#: ../../expense/expense.rst:59
msgid ""
"Select the related product and enter either the total amount you paid (with "
"Quantity = 1) or the unit price if Quantity is countable (e.g. number of "
"hotel nights)."
msgstr ""
"Sélectionnez le produit concerné et introduisez soit le montant total que "
"vous avez payé (avec Quantité = 1) soit le prix unitaire si la quantité est "
"comptabilisable (par ex. le nombre de nuits d'hôtel)."
#: ../../expense/expense.rst:62
msgid "Enter the expense date."
msgstr "Entrez la date de la dépense."
#: ../../expense/expense.rst:63
msgid ""
"Choose if you paid the bill on your own (and expect to be reimbursed) or if "
"the company paid directly (e.g. if you used a company's credit card)."
msgstr ""
"Indiquez si vous avez payé la facture vous-même (et souhaitez être "
"remboursé) ou si l'entreprise l'a payée directement (par ex. si vous avez "
"utilisé la carte de crédit de l'entreprise)."
#: ../../expense/expense.rst:65
msgid ""
"Set the bill reference, add some notes if requested and attach a photo/scan "
"of the receipt from the discussion thread. That will help the manager and "
"the accountant validate it."
msgstr ""
"Définissez la référence de la facture, ajoutez quelques notes si nécessaire "
"et joignez une photo ou scan du reçu provenant du fil de discussion. Cela "
"aidera le responsable et le comptable à valider votre demande."
#: ../../expense/expense.rst:73
msgid "In one click from emails"
msgstr "En un clic depuis les emails"
#: ../../expense/expense.rst:74
msgid ""
"Let your employees record their expenses from a simple email. Make a "
"snapshot of the receipt and send it by email, or simply forward a bill!"
msgstr ""
"Permettez à vos employés d'enregistrer leurs dépenses depuis un simple "
"email. Faites une capture d'écran du reçu et envoyez-la par mail ou "
"transmettez simplement une facture!"
#: ../../expense/expense.rst:77
msgid ""
"The only thing to do is setting up an email alias in "
":menuselection:`Expenses --> Configuration --> Settings` (e.g. *expenses* "
"@mycompany.odoo.com). For security purposes, only authenticated employee "
"emails (cfr. *Work Email* in employee detail form) are accepted."
msgstr ""
"Tout ce dont vous avez à faire c'est configurer l'alias de l'email dans "
":menuselection:`Dépenses --> Configuration --> Paramètres` (par ex. "
"*dépenses* @mycompany.odoo.com). Pour des raisons de sécurité, seuls les "
"emails provenant d'employés authentifiés sont acceptés (cfr. *Email "
"professionnel* dans le formulaire de renseignement sur les employés)."
#: ../../expense/expense.rst:83
msgid ""
"The expense product is set automatically if the mail subject contains the "
"product's internal reference in first position. Type the expense amount in "
"the mail subject to set it on the expense too (e.g. Ref001 Food 100€)."
msgstr ""
#: ../../expense/expense.rst:88
msgid "How to submit expenses to managers"
msgstr "Comment soumettre des dépenses aux responsables"
#: ../../expense/expense.rst:90
msgid ""
"When you are ready to submit your expenses to your manager (e.g. at the end "
"of a business trip, or once a month), go to the menu :menuselection:`My "
"Expenses --> Expenses to Submit`. Select all expenses from the list view and"
" click on :menuselection:`Action --> Submit to Manager`. Save the newly "
"created expense report (i.e. set of expenses), and wait for your manager to "
"approve it."
msgstr ""
"Dès que vous êtes prêt à soumettre vos notes de frais à votre responsable "
"(par ex. à la fin d'un voyage d'affaires, ou une fois par mois), allez au "
"menu :menuselection:`Mes notes de frais --> Notes de frais à soumettre`. "
"Sélectionnez toutes les dépenses de la liste et cliquez sur "
":menuselection:`Action --> Soumettre au responsable`. Enregistrez le nouveau"
" rapport que vous venez de créer (c-à-d la série de dépenses) et attendez "
"l'approbation de votre responsable."
#: ../../expense/expense.rst:100
msgid ""
"You can also submit expenses one by one from the *Submit to Manager* button "
"on the form view of an expense."
msgstr ""
"Vous pouvez également soumettre vos notes de frais une par une depuis le "
"bouton *Soumettre au responsable* dans la vue formulaire d'une dépense."
#: ../../expense/expense.rst:103
msgid ""
"All your submitted expense reports can be found in :menuselection:`Expenses "
"--> My Expenses --> Expense Reports`."
msgstr ""
"Tous vous rapports de dépenses soumis se trouvent dans "
":menuselection:`Dépenses --> Mes dépenses --> Rapports de dépenses`."
#: ../../expense/expense.rst:108
msgid "How to approve expenses"
msgstr "Comment approuver les dépenses"
#: ../../expense/expense.rst:110
msgid ""
"HR and team managers get an overview of all expense reports to validate from"
" the top menu :menuselection:`To Approve --> Expense Reports to Approve`. "
"Such users must have at least *Officers* access rights for *Expenses*."
msgstr ""
"L'équipe RH et l'équipe de responsables ont accès à un aperçu de tous les "
"rapports de dépenses à valider à partir du menu principal :menuselection:`À "
"approuver --> Rapports de dépenses à approuver`. Ces utilisateurs doivent "
"avoir au moins des droits d'accès *Administrateurs* pour les *Dépenses*."
#: ../../expense/expense.rst:117
msgid ""
"They can review expense reports, approve or reject them, as well as "
"providing feedback thanks to the integrated communication tool."
msgstr ""
"Grâce à l'outil de communication intégrée, ils peuvent revoir les rapports "
"de dépenses, les approuver ou les rejeter, et également faire des "
"commentaires."
#: ../../expense/expense.rst:123
msgid ""
"As a team manager you can easily find the expense reports of your team "
"members. You need to be set as manager in the detail form of those "
"employees."
msgstr ""
"En tant que responsable vous pouvez facilement avoir accès aux rapports de "
"dépenses des membres de votre équipe. Pour cela, vous devez être défini "
"comme responsable dans le formulaire de renseignement de vos employés."
#: ../../expense/expense.rst:131
msgid "How to post expenses in accounting"
msgstr "Comment publier des dépenses dans la comptabilité"
#: ../../expense/expense.rst:133
msgid ""
"Once expense reports approved by managers, the accounting department goes to"
" :menuselection:`Expenses --> Accountant --> Expense Reports To Post` to "
"check accounts, products and taxes. They can click *Post Journal Entries* to"
" post related journal entries into your books. To do so, the user must have "
"following access rights:"
msgstr ""
"Pour vérifier les comptes, les produits et les taxes, le service comptable "
"doit, une fois les rapports de dépenses approuvés par les responsables, "
"aller à :menuselection:`Dépenses --> Comptabilité --> Rapports de dépenses à"
" publier`. Pour publier les écritures comptables correspondantes dans vos "
"livres, ils peuvent cliquer sur *Publier les écritures comptables*. Pour ce "
"faire, ils doivent disposer des droits d'accès suivants :"
#: ../../expense/expense.rst:139
msgid "Accounting: Accountant or Adviser"
msgstr "Comptabilité : comptable ou conseiller"
#: ../../expense/expense.rst:140
msgid "Expenses: Manager"
msgstr "Dépenses : responsable"
#: ../../expense/expense.rst:143
msgid ""
"To post an expense, a *Home Address* must be set on the employee. If you get"
" a related blocking message when posting, click the employee, go to "
"*Personal Information* tab and select/create the contact of your employee in"
" the address book. A contact has been automatically created if this person "
"is using Odoo."
msgstr ""
"Pour publier une dépense, il faut qu'une *adresse privée* soit configurée "
"pour lemployé. Si vous recevez un message d'erreur lors de la publication, "
"cliquez sur employé, allez à l'onglet *Données privées* et "
"sélectionnez/créez un contact pour l'employé dans le répertoire. Si la "
"personne en question utilise Odoo, un contact sera automatiquement créé."
#: ../../expense/expense.rst:150
msgid "How to reimburse employees"
msgstr "Comment rembourser les employés"
#: ../../expense/expense.rst:152
msgid ""
"You can now see all the expense reports to reimburse in "
":menuselection:`Expenses --> Accountant --> Expense Reports To Pay`. To "
"record the payment or pay by check, click *Register a Payment*."
msgstr ""
"Vous avez désormais accès à tous les rapports de dépenses à rembourser dans "
":menuselection:`Dépenses --> Comptabilité --> Rapports de dépenses à payer`."
" Pour enregistrer le paiement ou payer par chèque, cliquez sur *Enregistrer "
"un paiement*."
#: ../../expense/expense.rst:156
msgid "See how you can easily manage the payment process in Odoo:"
msgstr ""
"Pour savoir comment gérer facilement le processus de paiement dans Odoo :"
#: ../../expense/expense.rst:158
msgid ":doc:`../accounting/payables/pay/check`"
msgstr ":doc:`../accounting/payables/pay/check`"
#: ../../expense/expense.rst:159
msgid ":doc:`../accounting/payables/pay/sepa`"
msgstr ":doc:`../accounting/payables/pay/sepa`"
#: ../../expense/expense.rst:163
msgid "How to re-invoice expenses to your customers"
msgstr "Comment refacturer des dépenses à vos clients ?"
#: ../../expense/expense.rst:165
msgid ""
"If you track expenses on customer projects, you can charge them back to your"
" customers automatically."
msgstr ""
"Si vous faites le suivi des dépenses dans vos projets clients, vous pouvez "
"facturer automatiquement vos clients."
#: ../../expense/expense.rst:169
msgid "Setup"
msgstr "Configuration"
#: ../../expense/expense.rst:171
msgid "Enable **Customer Billing** in the Expenses settings"
msgstr "Activez la **Facturation client** dans les paramètres des dépenses."
#: ../../expense/expense.rst:173
msgid ""
"Go to the product configuration menu and set the invoicing method on all "
"your Expense types:"
msgstr ""
"Allez au menu de configuration du produit et configurez le mode de "
"facturation sur tous vos types de dépenses :"
#: ../../expense/expense.rst:176
msgid ""
"Ordered quantities : it will invoice expenses based on the ordered quantity"
msgstr ""
"Quantités commandées : les dépenses seront facturées selon la quantité "
"commandé."
#: ../../expense/expense.rst:179
msgid ""
"Delivered quantities :it will invoice expenses based on the expenses "
"quantity"
msgstr ""
"Quantités livrées : les dépenses seront facturées selon la quantité livrée."
#: ../../expense/expense.rst:182
msgid "At cost: will invoice expenses at their real cost."
msgstr "Au coût : les dépenses seront facturés selon leur coût réel."
#: ../../expense/expense.rst:184
msgid ""
"At sales price: will invoice based on a fixed sales price set on the sale "
"order."
msgstr ""
"Au prix de vente : la facturation se fera sur la base du prix de vente "
"indiqué sur le bon de commande."
#: ../../expense/expense.rst:191
msgid "Create an order"
msgstr "Créer une commande"
#: ../../expense/expense.rst:193
msgid ""
"As a salesman, create and confirm a Sales Order for the services delivered "
"to your customer. If you don't put any expense in the order, it will be "
"added automatically once posted by the accountant."
msgstr ""
"En tant que vendeur, créez et confirmez des ordres de vente pour les "
"services fournis à vos clients. Si vous n'ajoutez aucune dépense sur l'ordre"
" de vente, cela se fera automatiquement lors de sa publication par le "
"comptable."
#: ../../expense/expense.rst:198
msgid "Link the expense to the Sale Order."
msgstr "Relier la dépense à l'ordre de vente"
#: ../../expense/expense.rst:204
msgid "Submit, validate and post expenses"
msgstr "Soumettre, valider et afficher les dépenses"
#: ../../expense/expense.rst:206
msgid ""
"As a manager, make sure the analytic account is set on every expense line on"
" approving expenses reports. Click the line to add one if missing. Employees"
" are already able to set one when submitting."
msgstr ""
"En tant que responsable, assurez-vous que le compte analytique est configuré"
" sur chaque ligne des rapports des dépenses approuvées. S'il en manque une, "
"cliquez sur la ligne pour l'ajouter. Les employés peuvent déjà les "
"configurer lorsqu'ils les soumettent."
#: ../../expense/expense.rst:213
msgid "As an accountant, post journal entries."
msgstr "En tant que comptable, publiez les écritures du journal."
#: ../../expense/expense.rst:216
msgid "Invoice expenses"
msgstr "Facturez les dépenses"
#: ../../expense/expense.rst:218
msgid ""
"Now you can invoice the order. It shows up in :menuselection:`Sales --> "
"Invoicing --> Sales` to Invoice. The expenses have been added automatically "
"in the order lines. Such items show up in blue (i.e. to invoice)."
msgstr ""
"Vous pouvez à présent facturer l'ordre de vente. Elle apparaît dans "
":menuselection:`Ventes --> Facturation --> Ventes` À facturer. Les dépenses "
"ont automatiquement été ajoutées aux lignes de commande. Ces postes "
"apparaissent en bleu (c'est à dire à facturer)."
#: ../../expense/expense.rst:226
msgid "e (i.e. to invoice)."
msgstr "e (par ex. à facturer)."
-23
View File
@@ -1,23 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-11-22 13:16+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Eloïse Stilmant <est@odoo.com>, 2017\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../expenses.rst:5
msgid "Expenses"
msgstr "Notes de frais"
File diff suppressed because it is too large Load Diff
-115
View File
@@ -1,115 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Cécile Collart <cco@odoo.com>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
# Moka Tourisme <hello@mokatourisme.fr>, 2021
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-02-04 11:02+0100\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Last-Translator: Moka Tourisme <hello@mokatourisme.fr>, 2021\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../fsm.rst:5
msgid "Field Service"
msgstr "Services sur Site"
#: ../../fsm/helpdesk.rst:3
msgid "Helpdesk"
msgstr "Assistance technique"
#: ../../fsm/helpdesk/plan_onsite.rst:3
msgid "Plan onsite interventions from helpdesk tickets"
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:4
msgid ""
"The integration with the Helpdesk app lets your helpdesk team manage "
"intervention requests directly. Planning field service tasks from tickets "
"speeds up your processes."
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:8
msgid "Configure the helpdesk team"
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:9
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`. Select"
" a team and enable *Onsite Interventions*."
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:16
msgid ""
"The helpdesk tickets of the team now display the *Plan Intervention* button."
" Click on it to create a new task under your field service project."
msgstr ""
#: ../../fsm/sales.rst:3
msgid "Sales"
msgstr "Ventes"
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:3
msgid "Create onsite interventions from sales orders"
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:4
msgid ""
"Allowing your sales team to open onsite interventions creates a seamless "
"experience for your customers. They can receive a quotation they first have "
"to approve before the work even starts."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:8
msgid "Configure a product"
msgstr "Configurez un article"
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:9
msgid ""
"Go to :menuselection:`Field Service --> Configuration --> Products` and "
"create or edit a product."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:11
msgid ""
"Under the *General Information* tab, select *Service* as *Product Type*."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:13
msgid ""
"Under the *Sales* tab, select *Timesheets on tasks* as *Service Invoicing "
"Policy*."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:15
msgid "Select *Create a task in an existing project* as *Service Tracking*."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:17
msgid "Select your *Project*."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:19
msgid ""
"If you use them, select your *Worksheet Template* and then click on *Save*."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:25
msgid ""
"From the *Sales* app, create a quotation with the product and confirm it. A "
"task is automatically set up under your Field Service project. It is "
"directly accessible from the sales order."
msgstr ""
File diff suppressed because it is too large Load Diff
-474
View File
@@ -1,474 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Vincent Luba <vincent@biz-4-africa.com>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
# Priscilla (prs) Odoo <prs@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Last-Translator: Priscilla (prs) Odoo <prs@odoo.com>, 2020\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../getting_started/documentation.rst:5
msgid "Basics of the QuickStart Methodology"
msgstr "Les bases de la méthodologie QuickStart."
#: ../../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 ""
"Ce document reprend les services d'Odoo Online, notre méthodologie "
"d'implémentation de Success Pack et les pratiques les plus conseillées afin "
"de commencer à utiliser notre produit."
#: ../../getting_started/documentation.rst:12
msgid "The SPoC (*Single Point of Contact*) and the Consultant"
msgstr "Le SPoC (*Point de contact unique*) et le consultant"
#: ../../getting_started/documentation.rst:14
msgid ""
"Within the context of your project, it is highly recommended to designate "
"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 ""
"Dans le cadre de votre projet, il est vivement recommandé de désigner et de "
"maintenir des deux côtés (du vôtre et du nôtre) **une seule et unique "
"personne de contact** (en anglais : Single Point of Contact ou SPoC), qui se"
" chargera de votre projet et qui en sera responsable. Il/Elle aura également"
" **l'autorité** en termes de prise de décision."
#: ../../getting_started/documentation.rst:20
msgid ""
"**The Odoo Consultant ensures the project implementation from A to Z**: From"
" 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 ""
"**Les consultants assurent l'implémentation du projet de A à Z** : Du début "
"à la fin du projet, il/elle assurera la cohérence globale de "
"l'implémentation sur Odoo et partagera son expertise en termes de bonnes "
"pratiques. "
#: ../../getting_started/documentation.rst:25
msgid ""
"**One and only decision maker on the client side (SPoC)**: He is responsible"
" 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 ""
"**Un seul et unique décisionnaire du côté client (SPoC)** : Il s'agit de la "
"personne responsable de transmettre les connaissances de l'activité ( "
"coordonner les interventions des utilisateurs clés si nécessaire) et de la "
"cohérence de la mise en oeuvre d'un point de vue professionnel (prise de "
"décision, gestion des changements, etc.)"
#: ../../getting_started/documentation.rst:31
msgid ""
"**Meetings optimization**: The Odoo consultant is not involved in the "
"process of decision making from a business point of view nor to precise "
"processes and company's internal procedures (unless a specific request or an"
" exception). Project meetings, who will take place once or twice a week, are"
" meant to align on the business needs (SPoC) and to define the way those "
"needs will be implemented in Odoo (Consultant)."
msgstr ""
"**Optimisation des réunions** : Le Consultant Odoo n'est pas impliqué dans "
"le processus de prise de décision d'un point de vue professionnel ni dans la"
" précision des processus ou procédures internes à l'entreprise (sauf si "
"demande spécifique ou exception). Les réunions de projet, qui auront lieu "
"une à deux fois par semaine, ont pour but de s'aligner sur les besoins de "
"l'entreprise (SPoC) et de définir la manière dont ces besoins seront "
"implémentés sur Odoo (Consultant)."
#: ../../getting_started/documentation.rst:39
msgid ""
"**Train the Trainer approach**: The Odoo consultant provides functional "
"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 :doc:`Odoo documentation <../index>`, `The elearning "
"platform <https://odoo.com/learn>`_ and the testing of functionalities."
msgstr ""
"**L'approche formation des formateurs** : Le consultant Odoo donne une "
"formation fonctionnelle au point de contact unique pour que celui-ci puisse "
"transmettre ce savoir-faire à ses collaborateurs. Pour que cette approche "
"soit réussie, la personne désignée comme point de contact unique doit "
"également être impliquée dans une démarche de développement personnel de ses"
" compétences par l'auto-apprentissage via la :doc:`Odoo documentation "
"<../index>`, `La plateforme de formation en ligne <https://odoo.com/learn>`_"
" et le test des fonctionnalités."
#: ../../getting_started/documentation.rst:49
msgid "Project Scope"
msgstr "Étendue du projet"
#: ../../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 ""
"Afin de s'assurer que tous les intervenants impliqués suivent la même "
"direction, il est nécessaire de définir et de faire évoluer la portée du "
"projet tant que l'implémentation du projet se poursuit."
#: ../../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. "
"Indeed, when all the stakeholders share the same vision, the evolution of "
"the needs and the resulting decision-making process are more simple and more"
" clear."
msgstr ""
#: ../../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"
" by the end users have demonstrated its effectiveness over time. This "
"approach also helps to identify gaps and apply corrective actions early in "
"the implementation."
msgstr ""
#: ../../getting_started/documentation.rst:68
msgid ""
"**Adopting standard features as a priority**: Odoo offers a great "
"environment to implement slight improvements (customizations) or more "
"important ones (developments). Nevertheless, adoption of the standard "
"solution will be preferred as often as possible in order to optimize project"
" delivery times and provide the user with a long-term stability and fluid "
"scalability of his new tool. Ideally, if an improvement of the software "
"should still be realized, its implementation will be carried out after an "
"experiment of the standard in production."
msgstr ""
#: ../../getting_started/documentation.rst:82
msgid "Managing expectations"
msgstr "Gestion des attentes"
#: ../../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 ""
"L'écart entre la réalité d'une implémentation et les attentes des futurs "
"utilisateurs est un facteur crucial. Trois aspects importants devraient être"
" pris en compte dès le début du projet :"
#: ../../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,"
" problem-solving, etc.) are crucial to the success of an Odoo "
"implementation. It is therefore strongly advised to take the necessary time "
"at the beginning of the project to align with these topics and regularly "
"check that this is still the case."
msgstr ""
#: ../../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"
" in order to provide the most effective solution to meet the needs "
"expressed. This goal can sometimes conflict with the end user's vision of an"
" ideal solution. In that case, the SPoC and the consultant will apply the "
"80-20 rule: focus on 80% of the expressed needs and take out the remaining "
"20% of the most disadvantageous objectives in terms of cost/benefit ratio "
"(those proportions can of course change over time). Therefore, it will be "
"considered acceptable to integrate a more time-consuming manipulation if a "
"global relief is noted. Changes in business processes may also be proposed "
"to pursue this same objective."
msgstr ""
"**Concentrez-vous sur la réussite du projet, et non pas sur la solution "
"idéale** : L'objectif principal du SPoC et du consultant est de mener à bien"
" le projet qui leur est confié afin de trouver la solution la plus efficace "
"pour répondre aux besoins exprimés. Cet objectif peut parfois aller à "
"l'encontre de la vision que se fait l'utilisateur final d'une solution "
"idéale. Dans ce cas, le SPoC et le consultant appliqueront la règle des "
"80-20 : se concentrer sur 80% des besoins exprimés et retirer les 20% "
"restants des objectifs les plus défavorables en termes de rapport "
"coût/bénéfice (ces proportions peuvent bien sûr changer au fil du temps). "
"Par conséquent, si un allègement global est constaté, il sera jugé "
"acceptable d'intégrer une manipulation plus chronophage. Des changements "
"dans les processus opérationnels peuvent également être proposées pour "
"poursuivre ce même objectif."
#: ../../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 "
"avoid being in this delicate situation, we recommend using several types of "
"tools\\* :"
msgstr ""
#: ../../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 ""
"**L'analyse des gaps** : La comparaison entre la requête et les "
"fonctionnalités standard proposées par Odoo permettra d'identifier le manque"
" à combler par des développements/personnalisations ou des changements des "
"processus opérationnels."
#: ../../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 ""
"**L'Histoire de l'utilisateur**: Cette technique sépare clairement les "
"responsabilités entre le SPoC, responsable d'expliquer le QUOI, le POURQUOI "
"et le QUI, et le consultant qui fournira une réponse au COMMENT."
#: ../../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 ""
"`La démonstration de faisabilité "
"<https://en.wikipedia.org/wiki/Proof_of_concept>`__ Une version simplifiée, "
"un prototype de ce qui est attendu pour arriver à un accord sur les grandes "
"lignes des changements attendus."
#: ../../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 ""
"**La maquête** : Dans la même idée que la démonstration de faisabilité, elle"
" viendra saligner aux changements liés à l'interface."
#: ../../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 "
"stakeholders have a clear idea of what can be expected/achieved in the "
"project. We will, therefore, avoid basing our work on hypotheses without "
"verifying its veracity beforehand."
msgstr ""
#: ../../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 ""
"*Cette liste peut, évidemment, être complétée avec d'autres outils qui "
"correspondraient plus adéquatement à la réalité des besoins de votre "
"projet.*"
#: ../../getting_started/documentation.rst:145
msgid "Communication Strategy"
msgstr "Stratégies de communication"
#: ../../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 "
"success of this approach. Its optimization will, therefore, lead us to "
"follow those principles:"
msgstr ""
#: ../../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 "
"provide direct access to the project's tracking document (Project "
"Organizer). This document will contain at least a list of tasks to be "
"performed as part of the implementation for which the priority level and the"
" manager are clearly defined."
msgstr ""
#: ../../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: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:168
msgid "Meeting minutes will be limited to decisions and validations;"
msgstr ""
"Le compte-rendu des réunions sera limité aux décisions et aux validations;"
#: ../../getting_started/documentation.rst:170
msgid ""
"Project statuses will only be established when an important milestone is "
"reached;"
msgstr ""
"Les statut des projets ne seront définis que lorsqu'une étape importante "
"sera franchie."
#: ../../getting_started/documentation.rst:173
msgid ""
"Training sessions on the standard or customized solution will be organized."
msgstr ""
"Des sessions de formation sur la solution classique ou personnalisée seront "
"organisées."
#: ../../getting_started/documentation.rst:177
msgid "Customizations and Development"
msgstr "Customisations et développements"
#: ../../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: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,"
" etc.). For example, it will be preferable to realize a significant "
"development in order to reduce the time of a daily operation, rather than an"
" operation to be performed only once a quarter. It is generally accepted "
"that the closer the solution is to the standard, the lighter and more fluid "
"the migration process, and the lower the maintenance costs for both parties."
" In addition, experience has shown us that 60% of initial development "
"requests are dropped after a few weeks of using standard Odoo (see "
"\"Adopting the standard as a priority\")."
msgstr ""
#: ../../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"
" 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 ""
"**Remplacer, sans dupliquer** : La décision de changer le logiciel de "
"gestion a été prise pour une bonne raison. Dans ce contexte, le moment de la"
" mise en œuvre est LE bon moment pour accepter et même être un initiateur de"
" changement tant au niveau de la manière dont le logiciel sera utilisé qu'au"
" niveau des processus d'affaires de l'entreprise."
#: ../../getting_started/documentation.rst:204
msgid "Testing and Validation principles"
msgstr "Principes de test et de validation"
#: ../../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:210
msgid ""
"**Role distribution**: In this context, the Consultant will be responsible "
"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 ""
"**Répartition des rôles** : Dans ce contexte, le consultant sera chargé "
"d'apporter une solution qui correspond aux spécifications définies et le "
"SpoC devra tester et valider la solution livrée pour vérifier si elle répond"
" aux exigences de la réalité opérationnelle."
#: ../../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 ""
"**Gestion des changements** : Lorsqu'un changement doit être apporté à la "
"solution, l'écart est causé par :"
#: ../../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 ""
"La différence entre le cahier des charges et la solution livrée. Cette "
"modification est sous la responsabilité du consultant. "
#: ../../getting_started/documentation.rst:223
msgid "**or**"
msgstr "**ou**"
#: ../../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 ""
"La différence entre les spécifications et les impératifs de la réalité "
"opérationnelle. Cette modification est sous la responsabilité du SPoC. "
#: ../../getting_started/documentation.rst:229
msgid "Data Imports"
msgstr "Importation de données"
#: ../../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, "
"this task can be time-consuming and, if its priority is not well defined, "
"prevent production from happening in time. To do this as soon as possible, "
"it will be decided :"
msgstr ""
#: ../../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:242
msgid ""
"**To import a limited amount of data before going into production**: When "
"the data history relates to information being processed (purchase orders, "
"invoices, open projects, for example), the need to have this information "
"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: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 "
"can be integrated into the software retrospectively. In this case, the "
"production launch of the solution will precede the required imports."
msgstr ""
#: ../../getting_started/documentation.rst:256
msgid "Support"
msgstr "Assistance"
#: ../../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 ""
"Lorsque votre projet est mis en production, nos équipes de support prennent "
"vos questions ou problèmes techniques en charge."
#: ../../getting_started/documentation.rst:261
msgid "See :ref:`support-expectations`."
msgstr "Voir :ref:`support-expectations`."
-893
View File
@@ -1,893 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# David David <f322p3ph@yahoo.fr>, 2020
# ShevAbam, 2020
# Olivier Lenoir <olivier.lenoir@free.fr>, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
# Eloïse Stilmant <est@odoo.com>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
# Martin Trigaux, 2021
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-02-04 11:02+0100\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Last-Translator: Martin Trigaux, 2021\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../helpdesk.rst:5
msgid "Helpdesk"
msgstr "Assistance technique"
#: ../../helpdesk/advanced.rst:3
msgid "Advanced"
msgstr "Avancé"
#: ../../helpdesk/advanced/after_sales.rst:3
msgid "After Sales Features"
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:5
msgid ""
"As your business grows, having the right tool to support your helpdesk team "
"on recording, tracking and managing issues raised easy and efficiently, is "
"key. Odoos Helpdesk application allows you to generate credit notes, manage"
" returns, products, repairs, grant coupons, and even plan onsite "
"interventions from a tickets page."
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:11
msgid "Set up the after sales services"
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:13
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and "
"enable the after sales options: *Refunds, Returns, Coupons, Repairs and "
"Onsite Interventions*."
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:20
msgid "Generate credit notes from tickets"
msgstr "Générez des notes de crédit depuis les tickets"
#: ../../helpdesk/advanced/after_sales.rst:22
msgid ""
"You can use a credit note to refund a customer or adjust the amount due. For"
" that, simply go to your ticket page, click on *Refund* and select the "
"corresponding *Invoice*. Clicking on *Reverse* generates a credit note, and "
"you can *Post* it while still being in the *Helpdesk* app."
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:30
msgid "Allow product returns from tickets"
msgstr "Autoriser les retours d'articles depuis les tickets"
#: ../../helpdesk/advanced/after_sales.rst:32
msgid ""
"The process of a product return from your customer back to your warehouse is"
" taken into action when, at the ticket page, you choose the option *Return*."
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:39
msgid "Grant coupons from tickets"
msgstr "Offrez des bons de réduction depuis les tickets "
#: ../../helpdesk/advanced/after_sales.rst:41
msgid ""
"First, be sure to have your *Coupon Program* planned in the *Sales* or "
"*Website* application. Then, in *Helpdesk*, open your ticket, click on "
"*Coupon*, and choose the respective one."
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:48
msgid "Repairs from tickets"
msgstr "Générer des réparations depuis les tickets"
#: ../../helpdesk/advanced/after_sales.rst:50
msgid ""
"Clicking on *Repair* option, on your ticket page, a new repair order form is"
" shown. Fill in the information as needed and choose the next step."
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:57
msgid "Plan onsite interventions from tickets"
msgstr "Générer des interventions sur site depuis les tickets"
#: ../../helpdesk/advanced/after_sales.rst:59
msgid ""
"At the ticket's page click on *Plan Intervention*, and set up your onsite "
"intervention exactly the same way as if you were on the *Field Service* "
"application."
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:67
msgid ""
"`Coupons <https://www.odoo.com/slides/slide/coupon-"
"programs-640?fullscreen=1>`_"
msgstr ""
"`Bons de réduction <https://www.odoo.com/slides/slide/coupon-"
"programs-640?fullscreen=1>`_"
#: ../../helpdesk/advanced/after_sales.rst:68
msgid ":doc:`../../manufacturing/repair/repair`"
msgstr ""
#: ../../helpdesk/advanced/close_tickets.rst:3
msgid "Allow Customers to Close their Tickets"
msgstr ""
#: ../../helpdesk/advanced/close_tickets.rst:5
msgid ""
"Allowing customers to close their tickets gives them autonomy and minimize "
"misunderstandings about when an issue is considered solved, or not. It makes"
" communication and actions more efficient."
msgstr ""
"Le fait d'autoriser les clients à clôturer eux-mêmes leurs tickets, leur "
"donne une autonomie et minimise les malentendus liés au fait qu'un problème "
"est considéré comme résolu ou pas. En plus, cela rend la communication et "
"les actions plus efficaces."
#: ../../helpdesk/advanced/close_tickets.rst:9
msgid "Configure the feature"
msgstr "Configuration de la fonctionnalité"
#: ../../helpdesk/advanced/close_tickets.rst:11
msgid ""
"To configure the feature go to :menuselection:`Helpdesk --> Settings --> "
"Helpdesk Teams --> Edit` and enable *Ticket closing*."
msgstr ""
"Pour configurer cette fonctionnalité, allez sur :menuselection:`Assistance "
"technique --> Paramètres --> Équipes d'assistance technique --> Éditer` et "
"activez *Clôture du ticket*."
#: ../../helpdesk/advanced/close_tickets.rst:18
msgid ""
"In order to designate to which stage the ticket migrates to once it is "
"closed, go to :menuselection:`Helpdesk --> Overview --> Tickets`."
msgstr ""
#: ../../helpdesk/advanced/close_tickets.rst:25
msgid ""
"You can either create a new Kanban stage or work with an existing one. For "
"both scenarios, go to :menuselection:`Helpdesk --> Settings --> Edit Stage` "
"and enable *Closing Stage*."
msgstr ""
#: ../../helpdesk/advanced/close_tickets.rst:32
msgid ""
"If a closing stage is not specified, by default, the ticket is moved to the "
"last stage; contrarily, if you have more than one stage set as closing, the "
"ticket is put in the first one."
msgstr ""
#: ../../helpdesk/advanced/close_tickets.rst:36
msgid "The Costumer Portal"
msgstr "Le Portail du client"
#: ../../helpdesk/advanced/close_tickets.rst:38
msgid ""
"Now, once the user logs into his Portal, the option *Close this ticket* is "
"available."
msgstr ""
#: ../../helpdesk/advanced/close_tickets.rst:45
msgid "Get reports on tickets closed by costumers"
msgstr "Recevoir des rapports sur les tickets clôturés par le client"
#: ../../helpdesk/advanced/close_tickets.rst:47
msgid ""
"To do an analysis of the tickets that have been closed by costumers go to "
":menuselection:`Helpdesk --> Reporting --> Tickets --> Filters --> Add "
"Custom filter --> Closed by partner --> Applied`."
msgstr ""
#: ../../helpdesk/overview.rst:3
msgid "Overview"
msgstr "Vue d'ensemble"
#: ../../helpdesk/overview/forum_and_elearning.rst:3
msgid "Forum and eLearning"
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:6
msgid "Forum"
msgstr "Forum"
#: ../../helpdesk/overview/forum_and_elearning.rst:8
msgid ""
"To go above and beyond email, live chat, web forms, and phone lines, offer "
"your customers a support forum. This way, customers might become more "
"attached to your company as they would be investing time to get into details"
" of your business. You also encourage the exchange of experiences and "
"knowledge, supporting the feeling of belonging to a community (your "
"community!)."
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:14
#: ../../helpdesk/overview/forum_and_elearning.rst:52
#: ../../helpdesk/overview/ratings.rst:10
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:11
msgid "Set up"
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:16
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Team` and "
"enable *Help Center*."
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:23
msgid ""
"Create, or edit a forum by clicking on the external link. Among the editing "
"options, choose if you would like the *Forum Mode* to be *Questions*: only "
"one answer is allowed per question or *Discussions*: multiple answers are "
"allowed per question."
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:31
msgid ""
"From now on, logged in users can start their discussions. To keep track of "
"posts, go to :menuselection:`Website --> Forum --> Posts`."
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:38
msgid ""
"Turn tickets into forum posts by simply clicking on *Share on the Forum* on "
"the ticket's page."
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:45
msgid "eLearning"
msgstr "eLearning"
#: ../../helpdesk/overview/forum_and_elearning.rst:47
msgid ""
"In addition to a forum, offer online courses. When doing so, you link your "
"customers and users needs and questions to useful content, helping to boost"
" efficiency as they can also find their answers there."
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:54
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and "
"enable *eLearning*."
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:61
msgid ""
"Once the structure and content of your course are ready, *Publish* it by "
"clicking on *Unpublished*."
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:67
msgid ""
"To keep track of your course statistics, go to *eLearning* and *View "
"Course*."
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:73
msgid "Todo"
msgstr "À faire"
#: ../../helpdesk/overview/forum_and_elearning.rst:73
msgid ""
"DETAILS/INFO SHOULD COME FROM ELEARNING DOCS. THEREFORE, LINK DOCS ONCE "
"AVAILABLE!"
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:3
msgid "Getting Started"
msgstr "Commencer"
#: ../../helpdesk/overview/getting_started.rst:5
msgid ""
"Helpdesk teams provide your customers with support to queries or errors they"
" might encounter while using your product/service. Therefore, a successful "
"scheme where you can organize multiple teams with their customized pipeline,"
" visibilities settings, and ticket traceability is essential."
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:10
msgid "Set up teams"
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:12
msgid ""
"To modify or create teams, go to :menuselection:`Helpdesk --> Configuration "
"--> Helpdesk Teams`."
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:14
msgid ""
"Setting up multiple teams allows you to group tickets by your channels "
"(example: BE/US), or by your support services' types (example: IT, "
"accounting, admin, etc.)."
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:21
msgid "Teams productivity and visibility"
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:23
msgid ""
"Teams can have individual *Assignment Methods* to ensure that tickets get "
"redirected to the right person:"
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:26
msgid ""
"*Manually*: tickets are manually assigned, allowing employees to manage "
"their own workload and target tickets they are experts at;"
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:28
msgid ""
"*Random*: tickets are randomly assigned and everyone gets the same amount. "
"This method ensures that all tickets are handled as the assignment happens "
"automatically;"
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:30
msgid ""
"*Balanced*: tickets are assigned to the person with the least amount of "
"tickets so that everyone fairly gets the same amount. Thereby, you ensure "
"that all tickets get to be taken care of."
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:40
msgid ""
"For the *Random* and *Balanced* assignment methods, you can set the *Team "
"Members* among whom tickets are assigned. Leave the field empty to include "
"all employees (with the proper access rights)."
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:43
msgid ""
"The *Team Visibility* feature allows you to specify who can see and access "
"the teams tickets. Therefore, tickets with sensible information are only "
"seen by the right people. Leave the field empty to include all employees "
"(with the proper access rights)."
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:46
msgid "Set up stages and share it among teams"
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:48
msgid ""
"To set up stages, go to :menuselection:`Helpdesk --> Configuration --> "
"Stages`. Then, create and/or edit stages as you need and set specific teams "
"to use certain stages under *Team*."
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:55
msgid ""
"Stages can be shared between one or multiple teams, allowing you to adapt "
"the pipeline to your individual needs. They also apply a visibility and "
"access rule, as other teams are not able to see or use the stage."
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:64
msgid ":doc:`../../general/odoo_basics/add_user`"
msgstr ""
#: ../../helpdesk/overview/ratings.rst:3
msgid "Ratings"
msgstr "Évaluations"
#: ../../helpdesk/overview/ratings.rst:5
msgid ""
"Allow customers to rate their experience with your helpdesk teams to "
"strengthen your credibility and gain their trust. Reviews can also influence"
" a customers decision and open space for feedback that can help you improve"
" the quality of your services."
msgstr ""
#: ../../helpdesk/overview/ratings.rst:12
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and "
"enable *Ratings on tickets*. The feature automatically adds a default email "
"template on the non-folded *closing stage(s)* of that team."
msgstr ""
#: ../../helpdesk/overview/ratings.rst:21
msgid ""
"To edit the email template and the stage(s) set as the closing ones, go to "
"the Kanban view of your helpdesk team and click on *Settings*, then on *Edit"
" Stage*."
msgstr ""
#: ../../helpdesk/overview/ratings.rst:28
msgid ""
"Now, once a ticket reaches the stage(s) designated as the *Closing Stage*, "
"an email is sent to the customer."
msgstr ""
#: ../../helpdesk/overview/ratings.rst:35
msgid ""
"Ratings can be seen on the chatter of each ticket, under the *See Customer "
"Satisfaction* link on the main dashboard, and through *Reporting*."
msgstr ""
#: ../../helpdesk/overview/ratings.rst:39
msgid "Ratings visible on the customer portal"
msgstr ""
#: ../../helpdesk/overview/ratings.rst:41
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and "
"enable *Display Rating on Customer Portal*. Now, by clicking on the helpdesk"
" teams name on their ticket, customers can see its ratings."
msgstr ""
#: ../../helpdesk/overview/ratings.rst:51
msgid ":doc:`../../portal/my_odoo_portal`"
msgstr ""
#: ../../helpdesk/overview/ratings.rst:52
#: ../../helpdesk/overview/receiving_tickets.rst:88
#: ../../helpdesk/overview/sla.rst:47
msgid ":doc:`../advanced/close_tickets`"
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:3
msgid "Start Receiving Tickets"
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:5
msgid ""
"Offering a variety of channels from where your customers can contact you "
"grants them flexibility and the right to choose the best one for themselves."
" And, in order to make sure inquiries across all channels get addressed, it "
"is essential to have a solution where all interactions come in one place."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:11
msgid "Channels options to submit tickets"
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:13
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, and "
"enable the following features as you want them to be available to your "
"users."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:21
msgid "Email Alias"
msgstr "Alias d'email"
#: ../../helpdesk/overview/receiving_tickets.rst:24
msgid ""
"Let your customers submit tickets by sending an email to your support email "
"address. The subject line of the email becomes the title of the ticket and "
"the content is shown in the Chatter."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:26
msgid ""
"Select *Configure domain name* to be redirected to *Settings* and, from "
"there, enable *External Email Servers* to determine or change your *Alias "
"Domain*."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:35
msgid ""
"Using your own email server is required to send and receive emails in Odoo "
"Community and Enterprise. Online users benefit from a ready-to-use email "
"server."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:39
msgid "Website Form"
msgstr "Formulaire du Site Web"
#: ../../helpdesk/overview/receiving_tickets.rst:41
msgid ""
"Allow your customers to submit a ticket by filling in a form through your "
"website."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:42
msgid ""
"Once the feature is activated, get redirected to your website by clicking on"
" *Go to Website*."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:49
msgid ""
"From the website page customize the form as you like. Then, publish it by "
"clicking on *Unpublished*."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:56
msgid "Live Chat"
msgstr "Live Chat"
#: ../../helpdesk/overview/receiving_tickets.rst:59
msgid ""
"Through live interactions with your website visitors, helpdesk tickets can "
"be instantly created and redirected to the right person."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:61
msgid ""
"Click on your helpdesk team's name - for the example below: *Customer Care* "
"- and :doc:`set up your channel <../../livechat/overview/get_started>`."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:68
msgid ""
"Now, your operators can create tickets by using the :doc:`command "
"<../../livechat/overview/responses>` */helpdesk (subject_of_ticket)*."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:72
msgid "Prioritize tickets"
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:74
msgid ""
"Use the stars to prioritize your tickets. The most urgent ones appear at the"
" top of your list on the Kanban view."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:77
msgid "1 star = *Low priority*"
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:78
msgid "2 stars = *High priority*"
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:79
msgid "3 stars = *Urgent*"
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:87
#: ../../helpdesk/overview/reports.rst:60
msgid ":doc:`sla`"
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:89
msgid ":doc:`../../discuss/advanced/email_servers`"
msgstr ""
#: ../../helpdesk/overview/reports.rst:3
msgid "Reports for a Better Support"
msgstr ""
#: ../../helpdesk/overview/reports.rst:5
msgid ""
"An efficient customer service solution should have a built-in reporting "
"option. Reports allow you to track trends, identify areas for improvement, "
"manage employees workloads and, most importantly, meet your customers "
"expectations."
msgstr ""
#: ../../helpdesk/overview/reports.rst:10
msgid "Cases"
msgstr ""
#: ../../helpdesk/overview/reports.rst:12
msgid "Some examples of the reports Odoo Helpdesk can generate include:"
msgstr ""
#: ../../helpdesk/overview/reports.rst:14
msgid "The number of tickets *grouped by* team and ticket type."
msgstr ""
#: ../../helpdesk/overview/reports.rst:17
msgid ""
"In this manner, you are able to evaluate which ticket types have been the "
"most frequent ones, plus the workload of your teams."
msgstr ""
#: ../../helpdesk/overview/reports.rst:19
msgid ""
"Apply *Time Ranges* if you would like to make comparisons to a *Previous "
"Period* or a *Previous Year*."
msgstr ""
#: ../../helpdesk/overview/reports.rst:25
msgid "The number of tickets closed per day, per team."
msgstr ""
#: ../../helpdesk/overview/reports.rst:27
msgid ""
"Get an overview of how many requests each team is closing per day in order "
"to measure their performance. Identify productivity levels to understand how"
" many requests they are able to handle."
msgstr ""
#: ../../helpdesk/overview/reports.rst:35
msgid ""
"Filter it by *Assignee* to see Key Performance Indicators (KPI) per agent."
msgstr ""
#: ../../helpdesk/overview/reports.rst:37
msgid ""
"The number of hours tickets are taking to be solved, grouped by team and "
"ticket type."
msgstr ""
#: ../../helpdesk/overview/reports.rst:39
msgid ""
"Check if your expectations are met by *measuring* the *Time to close "
"(hours)*. Your customers not only expect fast responses but they also want "
"their issues to be handled quickly."
msgstr ""
#: ../../helpdesk/overview/reports.rst:48
msgid "Save filters"
msgstr ""
#: ../../helpdesk/overview/reports.rst:50
msgid ""
"Save the filters you use the most and avoid having to reconstruct them every"
" time they are needed. To do so, set the groups, filters, and measures "
"needed. Then, go to *Favorites*."
msgstr ""
#: ../../helpdesk/overview/reports.rst:59
msgid ":doc:`receiving_tickets`"
msgstr ""
#: ../../helpdesk/overview/sla.rst:3
msgid "Service Level Agreements (SLA)"
msgstr ""
#: ../../helpdesk/overview/sla.rst:5
msgid ""
"Service Level Agreements (SLA) are commitments you make with your customers "
"to outline how a service is delivered. It bolsters trust between you and "
"your customers as it makes clear what needs to be done, to what standard, "
"and when."
msgstr ""
#: ../../helpdesk/overview/sla.rst:10
msgid "Create your policies"
msgstr ""
#: ../../helpdesk/overview/sla.rst:13
msgid ""
"First, enable the feature on the settings of the team you would like "
"policies to be applied, going to :menuselection:`Helpdesk --> Configuration "
"--> Helpdesk Teams`."
msgstr ""
#: ../../helpdesk/overview/sla.rst:15
msgid ""
"Create your policies through the teams settings page or go to "
":menuselection:`Helpdesk --> Configuration --> SLA Policies`."
msgstr ""
#: ../../helpdesk/overview/sla.rst:23
msgid ""
"Choose to which **Team** the policy is relevant and the **Minimum Priority**"
" a ticket needs to have for the policy to be applied."
msgstr ""
#: ../../helpdesk/overview/sla.rst:27
msgid ""
"**Target** is the stage a ticket needs to reach within the period defined to"
" satisfy the SLA. The period is based on the tickets creation date, and a "
"deadline is set on the tickets form once it matches an SLA policy rule. If "
"a ticket has more than one policy applied to it, the closest deadline of all"
" SLAs is the one considered."
msgstr ""
#: ../../helpdesk/overview/sla.rst:29
msgid ""
"When a ticket has satisfied an SLA policy, the SLA tag appears in green and "
"the deadline field is not shown anymore."
msgstr ""
#: ../../helpdesk/overview/sla.rst:37
msgid "SLA Analysis"
msgstr ""
#: ../../helpdesk/overview/sla.rst:39
msgid ""
"Go to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`. Apply"
" *Filters* and *Group by* to identify tickets that should be prioritized and"
" keep track of upcoming deadlines."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice.rst:3
msgid "Timesheet and Invoice"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:3
msgid "Invoice Time Spent on Tickets (Prepaid Support Services)"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:5
msgid ""
"Have the option to work with prepaid support services, meaning that a sales "
"order and a corresponding invoice are issued and, once the service is done, "
"you can deduct the time spent. Odoo allows it to happen because the "
"applications are fully integrated, resulting in faster responses to your "
"customer needs."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:14
msgid "Step 1: Set up a helpdesk team"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:17
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, create"
" or edit an existing team, and enable *Timesheet on Ticket* and *Time "
"Reinvoicing*."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:20
msgid ""
"Select or create a project under *Timesheet on Ticket*. The selected/created"
" is the one at which employees timesheet on by default. However, it can be "
"ultimately modified on each ticket."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:28
msgid "Step 2: Set up a service"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:31
msgid ""
"Go to :menuselection:`Sales --> Configuration --> Settings` and enable "
"*Units of Measure* to optionally be able to choose *hours* (for example) as "
"the unit of measure of your service."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:33
msgid ""
"Then, go to :menuselection:`Sales --> Products --> Products`, create or edit"
" an existing one, and set its *Product Type* as *Service*."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:40
msgid ""
"Now, select the invoicing management you would like to have under the "
"*Sales* tab. We recommend the following configuration:"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:47
msgid ""
"This configuration ensures that the customer is invoiced by the number of "
"hours predicted in the sales order, meaning that less or extra hours "
"recorded are not taken into account. It also ensures that every time a sales"
" order is confirmed, a new task is created under the right project, "
"automating the process."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:53
msgid ""
"We recommend setting up a specific project, as it was done for this flow "
"example. The important thing to remember is that the sales order item needs "
"to be set on the corresponding project or task, in order to reinvoice the "
"time spent on a ticket."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:58
msgid "Prevision an invoice and record time"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:61
msgid "Step 1: Place an order"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:63
msgid ""
"Go to :menuselection:`Sales --> Orders --> Orders` and create one for the "
"helpdesk service product you have previously set up, with the customer who "
"needs the ticket to be opened. Set the number of hours needed to assist the "
"customer and *Confirm* the order."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:72
msgid "Step 2: Invoice the customer"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:74
msgid "In *Sales*, select the respective sales order to *Create Invoice*."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:82
msgid "Step 3: Link the task to the ticket"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:84
msgid ""
"Now, in *Helpdesk*, create or edit the respective ticket and link it to the "
"task created by the confirmation of the sales order."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:92
msgid "Step 4: Record the time spent"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:94
msgid ""
"Still on the respective helpdesk ticket, record the hours performed under "
"the *Timesheets* tab."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:100
msgid ""
"Note that the hours recorded on the ticket form are shown on the *Delivered*"
" column in the sales order."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:108
msgid ""
"Hours recorded on the ticket are automatically shown in *Timesheets* and on "
"the dedicated task."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:111
msgid ":doc:`reinvoice_from_project`"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:112
msgid ":doc:`../../inventory/management/products/uom`"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:3
msgid "Invoice Time Spent on Tickets (Postpaid Support Services)"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:5
msgid ""
"Directly pull the billable time you have tracked on your helpdesk tickets "
"into sales orders and invoices through a project task. It gives you more "
"control over what you charge your client, and it is more efficient."
msgstr ""
"Ajoutez directement le temps à facturer que vous avez enregistré sur vos "
"tickets d'assistance dans les bons de commande et les factures, via une "
"tâche de projet. Cela vous donne plus de contrôle sur ce que vous facturez à"
" votre client, et c'est plus efficace."
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:10
msgid "Configuration"
msgstr "Configuration"
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:13
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk team --> Edit`"
" and enable the options *Timesheet on Ticket* and *Time Reinvoicing*."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:15
msgid ""
"Under *Timesheet on Ticket*, choose the *Project* to which tickets (and "
"timesheets) will be linked by default. Open its *External link* to enable "
"the feature *Bill from tasks*."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:22
msgid "Create a sales order and an invoice"
msgstr "Créez un bon de commande et une facture"
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:24
msgid ""
"Now, once you have recorded the time you spent on the helpdesk ticket, under"
" the *Timesheets* tab, access the task clicking on its name."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:31
msgid "*Create Sales Order* and proceed to create the invoice."
msgstr "*Créez un bon de commande* et lancez la facturation."
+4 -12
View File
@@ -1,19 +1,15 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# Copyright (C) Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Richard Mathot <rim@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-02-04 11:02+0100\n"
"POT-Creation-Date: 2021-05-18 07:12+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Last-Translator: Richard Mathot <rim@odoo.com>, 2020\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"
@@ -21,10 +17,6 @@ msgstr ""
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../index.rst:7 ../../index.rst:7
msgid "Index"
#: ../../content/index.rst:3
msgid "Odoo Documentation"
msgstr ""
#: ../../index.rst:3
msgid "Odoo User Documentation"
msgstr "Documentation utilisateur Odoo"
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
-919
View File
@@ -1,919 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Florian Hatat, 2020
# Nacim ABOURA <nacim.aboura@gmail.com>, 2020
# Eloïse Stilmant <est@odoo.com>, 2020
# Laura Piraux <lap@odoo.com>, 2020
# Gunther Clauwaert <gclauwae@hotmail.com>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
# Martin Trigaux, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-11-02 12:05+0100\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../iot.rst:5
msgid "Internet of Things (IoT)"
msgstr "Internet des objets (IoT)"
#: ../../iot/config.rst:3
msgid "Configuration"
msgstr "Configuration"
#: ../../iot/config/connect.rst:3
msgid "Connect an IoT Box to your database"
msgstr "Connectez une IoT Box à votre base de données"
#: ../../iot/config/connect.rst:5
msgid "Install the Internet of Things (IoT) App on your Odoo Database."
msgstr ""
"Installez l'application Internet des objets (IoT) sur votre base de données "
"Odoo."
#: ../../iot/config/connect.rst:10
msgid "Go in the IoT App and click on Connect on the IoT Boxes page."
msgstr ""
"Allez dans l'application IoT et cliquez sur Connecter sur la page des IoT "
"Box."
#: ../../iot/config/connect.rst:15
msgid "Follow the steps to connect your IoT Box."
msgstr "Pour connecter votre IoT Box, suivez les étapes :"
#: ../../iot/config/connect.rst:21
msgid "Ethernet Connection"
msgstr "Connexion Ethernet"
#: ../../iot/config/connect.rst:23
msgid ""
"Connect to the IoT Box all the devices that have to be connected with cables"
" (ethernet, usb devices, etc.)."
msgstr ""
"Connectez à votre IoT Box tous les appareils qui doivent être connectés par "
"câble (ethernet, périphériques USB, etc.)."
#: ../../iot/config/connect.rst:26
msgid "Power on the IoT Box."
msgstr "Mettez l'IoT Box sous tension."
#: ../../iot/config/connect.rst:28
msgid ""
"Read the Pairing Code from a screen or a receipt printer connected to the "
"IoT Box."
msgstr ""
#: ../../iot/config/connect.rst:32
msgid "Input the Pairing Code and click on the Pair button."
msgstr ""
#: ../../iot/config/connect.rst:35
msgid ""
"Recent changes in modern web browsers forced us to modify the connection "
"wizard. If your screen is different from the screenshots, make sure that the"
" ``iot_pairing`` module is installed."
msgstr ""
#: ../../iot/config/connect.rst:40
msgid "WiFi Connection"
msgstr "Connexion Wi-Fi"
#: ../../iot/config/connect.rst:42
msgid "Power on the IoT Box"
msgstr "Mettez l'IoT Box sous tension"
#: ../../iot/config/connect.rst:44
msgid "Copy the token"
msgstr "Copiez votre jeton"
#: ../../iot/config/connect.rst:48
msgid ""
"Connect to the IoT Box WiFi Network (make sure there is no ethernet cable "
"plugged in your computer)."
msgstr ""
"Connectez-vous au réseau Wi-Fi de l'IoT Box (assurez-vous qu'aucun câble "
"n'est connecté à votre ordinateur)."
#: ../../iot/config/connect.rst:53
msgid ""
"You will be redirected to the IoT Box Homepage (if it doesn't work, connect "
"to the IP address of the box). Give a name to your IoT Box (not required) "
"and paste the token, then click on next."
msgstr ""
"Vous allez être redirigé vers la page d'accueil de l'IoT Box (si cela ne "
"fonctionne pas, connectez-vous à l'adresse IP de la Box). Donnez un nom à "
"votre IoT Box (pas obligatoire) et insérez le jeton, puis cliquez sur "
"suivant."
#: ../../iot/config/connect.rst:60
msgid ""
"If you are on Runbot, do not forget to add the -all or -base in the token "
"(e.g. this token **http://375228-saas-11-5-iot-"
"f3f920.runbot16.odoo.com\\|4957098401** should become "
"**http://375228-saas-11-5-iot-f3f920-all.runbot16.odoo.com\\|4957098401**)."
msgstr ""
"Si vous êtes sur Runbot, n'oubliez pas d'ajouter le -all ou -base dans le "
"jeton (par ex. ce jeton **http://375228-saas-11-5-iot-"
"f3f920.runbot16.odoo.com\\|4957098401** doit devenir "
"**http://375228-saas-11-5-iot-f3f920-all.runbot16.odoo.com\\|4957098401**)."
#: ../../iot/config/connect.rst:66
msgid ""
"Choose the WiFi network you want to connect with (enter the password if "
"there is one) and click on Submit. Wait a few seconds before being "
"redirected to your database."
msgstr ""
"Choisissez le réseau Wi-Fi auquel vous voulez vous connecter (entrez le mot "
"de passe s'il y en a un) et cliquez sur Envoyer. Vous serez redirigé vers "
"votre base de données en quelques secondes."
#: ../../iot/config/connect.rst:72
msgid "You should now see the IoT Box."
msgstr "L'IoT Box devrait maintenant s'afficher."
#: ../../iot/config/connect.rst:78
msgid "IoT Box Schema"
msgstr "Schéma de l'IoT Box"
#: ../../iot/config/flash_sdcard.rst:3
msgid "Flashing your SD Card"
msgstr "Flasher votre carte SD"
#: ../../iot/config/flash_sdcard.rst:5
msgid ""
"In some case, you may need to reflash your IoT Boxs SD Card to benefit from"
" our latest updates."
msgstr ""
"Dans certains cas, vous devrez peut-être reflasher la carte SD de votre IoT "
"Box pour bénéficier de nos dernières mises à jour."
#: ../../iot/config/flash_sdcard.rst:9
msgid "Upgrade from the IoT Box homepage"
msgstr ""
#: ../../iot/config/flash_sdcard.rst:11
msgid ""
"Go to the IoT Box homepage, click on *Update*, next to the version number. "
"If a new version of the IoT Box image is available, you will see a *Upgrade "
"to ___* button a the bottom of the page, the IoT Box will then flash itself "
"to the new version of the IoT Box. All of your configurations will be saved."
msgstr ""
#: ../../iot/config/flash_sdcard.rst:18
msgid ""
"This process can take more than 30 minutes. Do not turn off or unplug the "
"IoT Box as it would leave it in an inconsistent state."
msgstr ""
#: ../../iot/config/flash_sdcard.rst:25
msgid "Upgrade with Etcher"
msgstr ""
#: ../../iot/config/flash_sdcard.rst:27
msgid ""
"Go to Balenas website and download `Etcher <https://www.balena.io/>`__. "
"Its a free and open-source utility used for burning image files. Install "
"and launch it. Download the latest image from `nightly "
"<http://nightly.odoo.com/master/iotbox/>`__."
msgstr ""
#: ../../iot/config/flash_sdcard.rst:32
msgid ""
"Then, open *Etcher* and select *Flash from file*, find the image you just "
"downloaded. Insert the IoT Box SD card into your computer and select it. "
"Click on *Flash* and wait for the process to finish."
msgstr ""
#: ../../iot/config/pos.rst:3
msgid "Use the IoT Box for the PoS"
msgstr "Utilisez l'IoT Box pour le PdV"
#: ../../iot/config/pos.rst:9
msgid "Prerequisites"
msgstr "Prérequis"
#: ../../iot/config/pos.rst:11
msgid "Before starting, make sure you have the following:"
msgstr "Avant de commencer, assurez-vous d'avoir :"
#: ../../iot/config/pos.rst:13
msgid "An IoT Box, with its power adapter."
msgstr ""
#: ../../iot/config/pos.rst:15
msgid "A computer or tablet with an up-to-date web browser"
msgstr "Un ordinateur ou une tablette avec un navigateur web à jour;"
#: ../../iot/config/pos.rst:17
msgid ""
"A running SaaS or Odoo instance with the Point of Sale and IoT apps "
"installed"
msgstr ""
"Une instance Saas ou Odoo avec le Point de ventes et l'application IoT "
"installés;"
#: ../../iot/config/pos.rst:20
msgid "A local network setup with DHCP (this is the default setting)"
msgstr "Un réseau local configuré avec DHCP (c'est le réglage par défaut);"
#: ../../iot/config/pos.rst:22
msgid "An RJ45 Ethernet Cable (optional, WiFi is built in)"
msgstr "Un câble Ethernet RJ45 (en option, le Wi-Fi est intégré)."
#: ../../iot/config/pos.rst:24
msgid ""
"Any of the supported hardware (receipt printer, barcode scanner, cash "
"drawer, payment terminal, scale, customer display, etc.). The list of "
"supported hardware can be found on the `POS Hardware page "
"<https://www.odoo.com/page/point-of-sale-hardware>`__"
msgstr ""
#: ../../iot/config/pos.rst:30
msgid "Set Up"
msgstr "Configuration"
#: ../../iot/config/pos.rst:32
msgid ""
"To connect hardware to the PoS, the first step is to connect an IoT Box to "
"your database. For this, follow this :doc:`documentation <connect>`."
msgstr ""
"Pour pouvoir connecter un matériel à votre PdV, vous devez d'abord connecter"
" une IoT Box à votre base de données. Pour ce faire, allez à "
":doc:`documentation <connect>`."
#: ../../iot/config/pos.rst:36
msgid "Then, you have to connect the peripheral devices to your IoT Box."
msgstr "Vous devez ensuite connecter les périphériques à votre IoT Box."
#: ../../iot/config/pos.rst:38
msgid ""
"**Printer**: Connect a supported receipt printer to a USB port or to the "
"network and power it on."
msgstr ""
#: ../../iot/config/pos.rst:41
msgid ""
"**Cash drawer**: The cash drawer should be connected to the printer with an "
"RJ25 cable."
msgstr ""
"**Tiroir caisse**: Le tiroir caisse devrait être connecté à l'imprimante "
"avec un cable RJ25."
#: ../../iot/config/pos.rst:44
msgid ""
"**Barcode scanner**: Connect your barcode scanner. In order for your barcode"
" scanner to be compatible it must end barcodes with an Enter character "
"(keycode 28). This is most likely the default configuration of your barcode "
"scanner."
msgstr ""
#: ../../iot/config/pos.rst:49
msgid "**Scale**: Connect your scale and power it on."
msgstr ""
"**Balance**: Connectez votre balance électronique et mettez la en marche."
#: ../../iot/config/pos.rst:51
msgid ""
"**Customer Display**: Connect a monitor to the IoT Box using an HDMI cable. "
"You can also access the Customer Display from any other computer by "
"accessing the IoT Box homepage and clicking on the *POS Display* button."
msgstr ""
#: ../../iot/config/pos.rst:56
msgid ""
"**Payment terminal**: The connection process depends on the terminal, please"
" refer to the :doc:`payment terminals documentation "
"<../../point_of_sale/payment>`."
msgstr ""
#: ../../iot/config/pos.rst:60
msgid ""
"Once it's done, you can connect the IoT Box to your PoS. For this, go in "
":menuselection:`Point of Sale --> Configuration --> PoS`, tick *IoT Box* and"
" select the devices you want to use in this Point of Sale. Save the changes."
msgstr ""
#: ../../iot/config/pos.rst:68
msgid "Set up is done, you can launch a new PoS Session."
msgstr ""
"La configuration est faite, vous pouvez lancer votre nouvelle session PdV."
#: ../../iot/config/troubleshooting.rst:3
msgid "Troubleshooting"
msgstr "Dépannage"
#: ../../iot/config/troubleshooting.rst:6
msgid "IoT Box Connection"
msgstr ""
#: ../../iot/config/troubleshooting.rst:9
msgid "I can't find the pairing code to connect my IoT Box"
msgstr ""
#: ../../iot/config/troubleshooting.rst:11
msgid ""
"The pairing code should be printed on receipt printers connected to the IoT "
"Box and should also be displayed on connected monitors."
msgstr ""
#: ../../iot/config/troubleshooting.rst:14
msgid "The pairing code doesn't show under the following circumstances:"
msgstr ""
#: ../../iot/config/troubleshooting.rst:16
msgid "The IoT Box is already connected to an Odoo database;"
msgstr ""
#: ../../iot/config/troubleshooting.rst:18
msgid "The IoT Box is not connected to the Internet;"
msgstr ""
#: ../../iot/config/troubleshooting.rst:20
msgid ""
"The code is only valid for 5 minutes after the IoT Box has started. It's "
"automatically removed from connected displays when this delay has expired;"
msgstr ""
#: ../../iot/config/troubleshooting.rst:23
msgid ""
"The version of the IoT Box image is too old. It should use version 20.06 or "
"more recent. If your IoT Box image is from an earlier version, then you will"
" have to reflash the SD card of your IoT Box to update the image (see "
":doc:`Flashing your SD Card <flash_sdcard>`)"
msgstr ""
#: ../../iot/config/troubleshooting.rst:28
msgid ""
"If you are not in any of the cases listed above, make sure that the IoT Box "
"has correctly started, by checking that a fixed green LED is showing next to"
" the micro-USB port."
msgstr ""
#: ../../iot/config/troubleshooting.rst:33
msgid "I've connected my IoT Box but it's not showing in my database"
msgstr ""
#: ../../iot/config/troubleshooting.rst:35
msgid ""
"When you connect an IoT Box to a database, the IoT Box might restart, if "
"that is the case, it might take up to one minute before appearing in your "
"database. If after some time the IoT is still not showing, make sure that "
"your database can be reached from the IoT Box and that your server doesn't "
"use a multi-database environment."
msgstr ""
#: ../../iot/config/troubleshooting.rst:42
msgid "My IoT Box is connected to my database, but cannot be reached"
msgstr ""
#: ../../iot/config/troubleshooting.rst:44
msgid ""
"Make sure that the IoT Box and the device running the browser are located on"
" the same network as the IoT Box cannot be reached from outside the local "
"network."
msgstr ""
#: ../../iot/config/troubleshooting.rst:49
msgid "Printer"
msgstr "Imprimante"
#: ../../iot/config/troubleshooting.rst:52
msgid "My printer is not detected"
msgstr ""
#: ../../iot/config/troubleshooting.rst:54
msgid ""
"If one of your printers doesn't show up in your devices list, go to the IoT "
"Box homepage and make sure that it is listed under *Printers*."
msgstr ""
#: ../../iot/config/troubleshooting.rst:60
msgid ""
"If your printer is not present on the IoT Box homepage, hit *Printers "
"Server*, go to the *Administration* tab and click on *Add Printer*. If you "
"can't find your printer in the list, it's probably not connected properly."
msgstr ""
#: ../../iot/config/troubleshooting.rst:66
msgid "My printer outputs random text"
msgstr ""
#: ../../iot/config/troubleshooting.rst:68
msgid ""
"For most printers, the correct driver should be automatically detected and "
"selected. However, in some cases, the automatic detection mechanism might "
"not be enough, and if no driver is found the printer might print random "
"characters."
msgstr ""
#: ../../iot/config/troubleshooting.rst:73
msgid ""
"The solution is to manually select the corresponding driver. On the IoT Box "
"homepage, click on *Printers Server*, go to the *Printers* tab and select "
"the printer in the list. In the Administration dropdown, click on *Modify "
"Printer*. Follow the steps and select the Make and Model corresponding to "
"your printer."
msgstr ""
#: ../../iot/config/troubleshooting.rst:83
msgid ""
"Epson and Star receipt printers and Zebra label printers do not need a "
"driver to work. Make sure that no driver is selected for those printers."
msgstr ""
#: ../../iot/config/troubleshooting.rst:88
msgid "My Zebra Printer doesn't print anything"
msgstr ""
#: ../../iot/config/troubleshooting.rst:90
msgid ""
"Zebra printers are quite sensitive to the format of the ZPL code that is "
"printed. If nothing comes out of the printer or blank labels are printed, "
"try changing the format of the report that is sent to the printer by "
"accessing :menuselection:`Settings ~~> Technical ~~> Views` in developer "
"mode and look for the corresponding template."
msgstr ""
#: ../../iot/config/troubleshooting.rst:97
msgid "Barcode Scanner"
msgstr "Lecteur de code-barres"
#: ../../iot/config/troubleshooting.rst:100
msgid "The characters read by the barcode scanner don't match the barcode"
msgstr ""
#: ../../iot/config/troubleshooting.rst:102
msgid ""
"By default, we assume that your barcode scanner is configured in US QWERTY. "
"This is the default configuration of most barcode readers. If your barcode "
"scanner uses a different layout, please go to the form view of your device "
"and select the correct one."
msgstr ""
#: ../../iot/config/troubleshooting.rst:108
msgid "Nothing happens when a barcode is scanned"
msgstr ""
#: ../../iot/config/troubleshooting.rst:110
msgid ""
"Make sure that the correct device is selected in your Point of Sale "
"configuration and that your barcode is configured to send an ENTER character"
" (keycode 28) at the end of every barcode."
msgstr ""
#: ../../iot/config/troubleshooting.rst:115
msgid "The barcode scanner is detected as a keyboard"
msgstr ""
#: ../../iot/config/troubleshooting.rst:117
msgid ""
"Some poorly built barcode scanners do not advertise themselves as barcode "
"scanners but as a USB keyboard instead, and will not be recognized by the "
"IoT Box."
msgstr ""
#: ../../iot/config/troubleshooting.rst:121
msgid ""
"You can manually change the device type by going to its form view and "
"activating the *Is scanner* option."
msgstr ""
#: ../../iot/config/troubleshooting.rst:128
msgid "Cashdrawer"
msgstr "Tiroir-caisse"
#: ../../iot/config/troubleshooting.rst:131
msgid "The cashdrawer does not open"
msgstr "Le tiroir-caisse ne s'ouvre pas"
#: ../../iot/config/troubleshooting.rst:133
msgid ""
"The cashdrawer should be connected to the printer and the *Cashdrawer* "
"checkbox should be ticked in the POS configuration."
msgstr ""
#: ../../iot/devices.rst:3
msgid "Devices"
msgstr "Périphériques"
#: ../../iot/devices/camera.rst:3
msgid "Connect a Camera"
msgstr "Connectez un appareil photo"
#: ../../iot/devices/camera.rst:5
msgid ""
"When using your *IoT Box* in Odoo, you could need to use a camera. As it can"
" be done in a few steps, this device is really easy to configure. Then, you "
"can use it in your manufacturing process and link it to a control point. "
"Doing so will allow you to take pictures when you reach the chosen quality "
"control point."
msgstr ""
"Lorsque vous utilisez votre *IoT Box* dans Odoo, vous pourriez avoir besoin "
"d'utiliser un appareil photo. La configuration de cet appareil est très "
"simple, et elle peut se faire en quelques étapes. Vous pourrez alors "
"l'utiliser dans votre processus de fabrication et le relier à un point de "
"contrôle. Ainsi, vous pourrez prendre des photos lorsque vous atteindrez le "
"point de contrôle de la qualité choisi."
#: ../../iot/devices/camera.rst:12 ../../iot/devices/footswitch.rst:13
#: ../../iot/devices/printer.rst:11
msgid "Connection"
msgstr "Connexion"
#: ../../iot/devices/camera.rst:14
msgid ""
"To connect the camera to the *IoT Box*, simply connect the two by cable."
msgstr ""
#: ../../iot/devices/camera.rst:17
msgid ""
"If your camera is a `*supported one* <https://www.odoo.com/page/iot-"
"hardware>`__, there is no need to set up anything as it will be detected as "
"soon as it is connected."
msgstr ""
"Si votre appareil photo est `*compatible* <https://www.odoo.com/page/iot-"
"hardware>`__, vous ne devrez rien configurer car l'appareil sera détecté dès"
" sa connexion."
#: ../../iot/devices/camera.rst:25
msgid "Link a Camera to a Quality Control Point"
msgstr "Connectez un appareil photo à un point de contrôle de la qualité"
#: ../../iot/devices/camera.rst:28 ../../iot/devices/measurement_tool.rst:34
msgid "With the Manufacturing app"
msgstr "Avec l'application Fabrication"
#: ../../iot/devices/camera.rst:30
msgid ""
"In your *Quality app*, you can setup the device on a *Quality Control "
"Point*. Go to the *Control Points* menu, under *Quality Control* and open "
"the control point you want to link with the camera."
msgstr ""
"Dans votre *Application qualité*, vous pouvez configurer le périphérique sur"
" un *Point de contrôle de la qualité*. Allez dans le menu *Points de "
"contrôle*, sous *Contrôle de la qualité* et ouvrez le point de contrôle que "
"vous souhaitez relier à l'appareil photo."
#: ../../iot/devices/camera.rst:34
msgid ""
"Now, you can edit the control point and select the device from the dropdown "
"list. Now, hit save."
msgstr ""
"Vous pouvez ensuite modifier le point de contrôle et sélectionner le "
"périphérique depuis la liste déroulante. Appuyez ensuite sur enregistrer."
#: ../../iot/devices/camera.rst:40
msgid ""
"Then, your camera can be used with the picked *Control Point*. During the "
"manufacturing process, reaching the *Quality Control Point* you chose before"
" will allow you to take a picture."
msgstr ""
"Votre appareil photo peut alors être utilisé avec le *point de contrôle* "
"choisi. Au cours du processus de fabrication, atteindre le *Point de "
"contrôle de la qualité* que vous avez choisi auparavant vous permettra de "
"prendre une photo."
#: ../../iot/devices/footswitch.rst:3
msgid "Connect a Footswitch"
msgstr "Connectez une pédale de commande"
#: ../../iot/devices/footswitch.rst:5
msgid ""
"When working, it is always better to have your two hands available. Using "
"Odoos *IoT Box* and a footswitch will allow it."
msgstr ""
"Lorsqu'on travaille, il est toujours mieux d'avoir les mains libres. "
"L'utilisation de l'*IoT Box d'Odoo* avec une pédale de commande vous en "
"donne la possibilité."
#: ../../iot/devices/footswitch.rst:8
msgid ""
"In fact, you will be able to go from one screen to another and perform "
"actions by using your foot and the footswitch. Really convenient, it can be "
"configured in a few steps."
msgstr ""
#: ../../iot/devices/footswitch.rst:15
msgid ""
"Connecting the footswitch to the *IoT Box* is easy, you just have to connect"
" the two by cable."
msgstr ""
#: ../../iot/devices/footswitch.rst:18
msgid ""
"If your footswitch is a `supported one <https://www.odoo.com/page/iot-"
"hardware>`__, there is no need to set up anything since it will be "
"automatically detected when connected."
msgstr ""
"Si votre pédale à commande `*compatible* <https://www.odoo.com/page/iot-"
"hardware>`__, vous ne devrez rien configurer car l'appareil sera "
"automatiquement détecté dès sa connexion."
#: ../../iot/devices/footswitch.rst:26
msgid "Link a Footswitch to a Workcenter"
msgstr "Reliez une pédale à commande à un Poste de travail"
#: ../../iot/devices/footswitch.rst:28
msgid ""
"To link the footswitch to an action, it needs to be configured on a "
"workcenter. Go to the workcenter you want to use the footswitch in and add "
"the device in the *IoT Triggers* tab. Then, you can link it to an action and"
" also add a key to trigger it."
msgstr ""
"Pour relier la pédale à commande à une action, elle doit être configurée sur"
" un poste de travail. Allez au poste de travail dans lequel vous voulez "
"utiliser la pédale à commande et ajoutez le périphérique dans l'onglet "
"*Déclencheurs de l'IoT*. Vous pouvez alors le lier à une action et ajouter "
"une clé pour le déclencher."
#: ../../iot/devices/footswitch.rst:36
msgid ""
"Note that the one that is first in the list will be chosen. So, the order "
"matters! In the picture above, using the footswitch will, for example, "
"automatically skip the current part of the process you work on."
msgstr ""
"Notez que c'est le premier de la liste qui sera choisi. Donc, l'ordre a son "
"importance ! Dans l'image ci-dessus, l'utilisation de la pédale de commande "
"permet, par exemple, de passer automatiquement la partie en cours du "
"processus sur lequel vous travaillez."
#: ../../iot/devices/footswitch.rst:41
msgid ""
"When you are on the work order screen, a status button indicates if you are "
"correctly connected to the footswitch."
msgstr ""
"Lorsque vous êtes sur l'écran de commande du poste de travail, un bouton "
"d'état vous indique si vous êtes correctement connecté à la pédale de "
"commande."
#: ../../iot/devices/measurement_tool.rst:3
msgid "Connect a Measurement Tool"
msgstr "Connectez un outil de mesure"
#: ../../iot/devices/measurement_tool.rst:5
msgid ""
"With Odoos *IoT Box*, it is possible to connect measurement tools to your "
"database. Find the list of supported devices here: `Supported devices "
"<https://www.odoo.com/page/iot-hardware>`__,."
msgstr ""
"Avec l'*IoT Box d'Odoo*, il est possible de connecter des outils de mesure à"
" votre base de données. Trouvez la liste des appareils compatibles ici: "
"`Appareils compatibles <https://www.odoo.com/page/iot-hardware>`__,."
#: ../../iot/devices/measurement_tool.rst:10
msgid "Connect in USB"
msgstr "Se connecter en USB"
#: ../../iot/devices/measurement_tool.rst:12
msgid ""
"To add a device connected by USB, just plug the USB cable in the *IoT Box*, "
"and the device should appear in your Odoo database."
msgstr ""
#: ../../iot/devices/measurement_tool.rst:19
msgid "Connect in Bluetooth"
msgstr "Se connecter via le bluetooth"
#: ../../iot/devices/measurement_tool.rst:21
msgid ""
"Activate the Bluetooth on your device (see your device manual for further "
"explanation) and the IoT Box will automatically try to connect to the "
"device."
msgstr ""
"Activez le Bluetooth sur votre appareil (voir le manuel de votre appareil "
"pour plus d'explications) et l'IoT Box essaiera automatiquement de se "
"connecter à l'appareil."
#: ../../iot/devices/measurement_tool.rst:25
msgid "Here is an example of what it should look like:"
msgstr "Voici un exemple de ce à quoi ça doit ressembler :"
#: ../../iot/devices/measurement_tool.rst:31
msgid "Link a measurement tool to a quality control point"
msgstr "Reliez un outil de mesure à un point de contrôle de la qualité"
#: ../../iot/devices/measurement_tool.rst:36
msgid ""
"In your *Quality app*, you can setup a device on your *Quality Control "
"Points*. To do so, go to the *Control Points* menu, under *Quality Control* "
"and open the control point to which you want to assign a measurement tool."
msgstr ""
"Dans votre *Application qualité*, vous pouvez configurer le périphérique sur"
" vos *Points de contrôle de la qualité*. Pour cela, allez dans le menu "
"*Points de contrôle*, sous *Contrôle de la qualité* et ouvrez le point de "
"contrôle que vous souhaitez relier à l'outil de mesure."
#: ../../iot/devices/measurement_tool.rst:41
msgid ""
"Now, you can edit the control point and choose the device from the dropdown "
"list. Then, hit save."
msgstr ""
"Vous pouvez ensuite modifier le point de contrôle et sélectionner le "
"périphérique depuis la liste déroulante. Appuyez ensuite sur enregistrer."
#: ../../iot/devices/measurement_tool.rst:47
msgid ""
"Now, your measurement tool is linked to the chosen *Control Point*. The "
"value, which needs to be changed manually, will be automatically updated "
"while the tool is being used."
msgstr ""
"Votre outils de mesure est maintenant relié au ¨*Point de contrôle* choisi. "
"La valeur, qui doit être modifiée manuellement, sera automatiquement mise à "
"jour lorsque l'appareil sera utilisé."
#: ../../iot/devices/printer.rst:3
msgid "Connect a Printer"
msgstr "Connectez une imprimante"
#: ../../iot/devices/printer.rst:5
msgid ""
"When using your *IoT Box* in Odoo, you could need to use a printer. Doing so"
" is easy and convenient as it can be done in a few steps. Then, you can use "
"it to print receipts, orders or even reports in different Odoo apps."
msgstr ""
"Lorsque vous utilisez votre *IoT Box* dans Odoo, vous pourriez avoir besoin "
"d'une imprimante. C'est facile et pratique et cela peut se faire en quelques"
" étapes. Vous pourrez ainsi l'utiliser pour imprimer des reçus, des "
"commandes ou même des rapports dans différentes applications Odoo."
#: ../../iot/devices/printer.rst:13
msgid ""
"The IoT Box supports printers connected through USB, network or Bluetooth. "
"`Supported printers <https://www.odoo.com/page/iot-hardware>`__ will be "
"detected automatically and will appear in the *Devices* list of your IoT "
"app."
msgstr ""
#: ../../iot/devices/printer.rst:18
msgid "The printer can take up to two minutes to appear in your devices list."
msgstr ""
"L'imprimante peut prendre jusqu'à deux minutes avant d'apparaître dans la "
"liste de vos périphériques."
#: ../../iot/devices/printer.rst:24
msgid "Link the Printer"
msgstr "Reliez l'imprimante"
#: ../../iot/devices/printer.rst:27
msgid "To Work Orders"
msgstr "À des ordres de travail"
#: ../../iot/devices/printer.rst:29
msgid ""
"You can link *Work Orders* to printers via a *Quality Control Point* to "
"print labels for manufactured products."
msgstr ""
"Vous pouvez relier des *Ordres de travail* à des imprimantes via le *Point "
"de contrôle de la qualité* pour imprimer des étiquettes pour les produits "
"fabriqués."
#: ../../iot/devices/printer.rst:32
msgid ""
"To do so, you need to create a *Quality Control Point* from the *Quality* "
"app. Then, you can select the correct manufacturing operation and the work "
"order operation. In type, choose *Print Label* and hit save."
msgstr ""
"Pour ce faire, vous devez créer un *Point de contrôle de la qualité* depuis "
"l'application *Qualité*. Vous pouvez ensuite choisir les opérations de "
"production et de commande de travail souhaitées. Dans type, sélectionnez "
"*Imprimer l'étiquette* puis enregistrez."
#: ../../iot/devices/printer.rst:40
msgid ""
"Now, each time you reach the quality control point for the chosen product, a"
" *Print Label* button will appear."
msgstr ""
"Désormais, chaque fois que vous atteignez le point de contrôle de la qualité"
" pour le produit choisi, un bouton *Imprimer l'étiquette* apparaîtra."
#: ../../iot/devices/printer.rst:47
msgid "To Reports"
msgstr "À des rapports"
#: ../../iot/devices/printer.rst:49
msgid ""
"You can also link a type of report to a certain printer. In the *IoT* app, "
"go to the *Devices* menu and select the printer you want to set up."
msgstr ""
"Vous pouvez également relier un type de rapport à une imprimante donnée. "
"Dans l'application *IoT*, allez au menu *Périphériques* et sélectionnez "
"l'imprimante que vous voulez configurer."
#: ../../iot/devices/printer.rst:56
msgid "Now, go to the *Printer Reports* tab."
msgstr "Allez à présent dans l'onglet *Rapport de l'imprimante*."
#: ../../iot/devices/printer.rst:61
msgid ""
"Hit edit and then, click on *Add a line*. In the window that shows up, check"
" all the types of reports that should be linked to this printer. Click on "
"select and save."
msgstr ""
"Cliquez sur éditer, puis sur *Ajouter une ligne*. Dans la fenêtre qui "
"s'affiche, cochez tous les types de rapports qui doivent être reliés à cette"
" imprimante. Cliquez sur sélectionner et enregistrer."
#: ../../iot/devices/printer.rst:68
msgid ""
"Now, each time you click on *Print* in the control panel, instead of "
"downloading a PDF, it will send it to the selected printer and automatically"
" print it."
msgstr ""
"Désormais, à chaque fois que vous cliquez sur *Imprimer* dans le panneau de "
"commande, le rapport ne sera pas téléchargé en format PDF, mais "
"automatiquement envoyé vers l'imprimante sélectionnée et imprimé."
#: ../../iot/devices/printer.rst:73
msgid "Print Receipts from the PoS"
msgstr "Imprimez des reçus depuis le PdV"
#: ../../iot/devices/printer.rst:75
msgid ""
"You can link a printer to your *Point of Sale* app so you can print receipts"
" directly from your *PoS*."
msgstr ""
"Vous pouvez relier une imprimante à votre application *Point de ventes* pour"
" pouvoir imprimer des reçus directement depuis votre *PdV*. "
#: ../../iot/devices/printer.rst:78
msgid ""
"Doing so is really easy. Go to your *Point of Sale* app and open your *Point"
" of Sale* settings, under *Configuration*. There, click on *Edit* and check "
"the *IoT Box* feature. Then, choose your *Receipt Printer* from the "
"dropdown."
msgstr ""
#: ../../iot/devices/printer.rst:86
msgid ""
"Now, you will be able to print different kinds of tickets from your *POS*: "
"**receipts**, **sale details** and **bills**."
msgstr ""
#: ../../iot/devices/printer.rst:89
msgid ""
"Receipts are printed once the order is validated. The process is automated "
"when you enable the feature in your *PoS* configuration."
msgstr ""
#: ../../iot/devices/printer.rst:92
msgid ""
"Sales details can be printed by clicking on the printer icon on the navbar "
"at the top of the *PoS*. It will print the details of the sales of the "
"current day."
msgstr ""
"Les détails des ventes de la journée peuvent être imprimés en cliquant sur "
"l'icône de l'imprimante sur la barre de navigation en haut du *PdV*. "
#: ../../iot/devices/printer.rst:99
msgid ""
"As for the bill, it is only available in restaurant mode. In your restaurant"
" settings, activate *Print Bills* and a *Bill* button will appear in the "
"left panel of the *PoS*."
msgstr ""
#: ../../iot/devices/printer.rst:107
msgid "Print Orders in the kitchen"
msgstr "Imprimer des commandes dans la cuisine"
#: ../../iot/devices/printer.rst:109
msgid "In restaurant mode, you can send order tickets to the kitchen."
msgstr ""
"En mode restaurant, vous pouvez envoyer des reçus de commandes vers la "
"cuisine."
#: ../../iot/devices/printer.rst:111
msgid ""
"To do so, go to the *PoS* app and open your *PoS* settings. Then, tick "
"*Order Printer*."
msgstr ""
"Pour ce faire, allez dans l'application *PdV* et ouvrez les paramètres de "
"votre *PdV*. Puis cochez *Imprimante de commandes*."
#: ../../iot/devices/printer.rst:117
msgid ""
"Now, go to the *Printers* menu. Hit create, select the printer from the "
"dropdown and, in the *Printer Product Categories* field, choose all the "
"categories of products that should be printed on this printer."
msgstr ""
#: ../../iot/devices/printer.rst:124
msgid ""
"In the *PoS*, when you add or remove a product from one of the selected "
"categories, the button *Order* will be green. If you click on it, the IoT "
"Box will print a receipt on the corresponding printer."
msgstr ""
-276
View File
@@ -1,276 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
# Aurélien Pillevesse <aurelienpillevesse@hotmail.fr>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Fernanda Marques <fem@odoo.com>, 2020\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../livechat/overview.rst:3
msgid "Overview"
msgstr "Vue d'ensemble"
#: ../../livechat/overview/get_started.rst:3
msgid "Get Started with Live Chat"
msgstr ""
#: ../../livechat/overview/get_started.rst:5
msgid ""
"Live Chat has the highest satisfaction rating of any communication tool. It "
"allows fast responses and it is accessible and convenient, as your customers"
" can keep doing what they are doing while interacting with you. Remember: "
"your customers want to talk to you, so let's make it easy."
msgstr ""
#: ../../livechat/overview/get_started.rst:10
msgid "Set up"
msgstr ""
#: ../../livechat/overview/get_started.rst:12
msgid ""
"Once *Live Chat* is installed on your database, if your website was created "
"with Odoo, the application is automatically added to it. All that is left to"
" do is to go to :menuselection:`Website --> Configuration --> Settings --> "
"Live Chat`."
msgstr ""
#: ../../livechat/overview/get_started.rst:21
msgid ""
"Select the channel to be linked to your website or create one on the fly."
msgstr ""
#: ../../livechat/overview/get_started.rst:27
msgid "For both scenarios, under:"
msgstr ""
#: ../../livechat/overview/get_started.rst:30
msgid ""
"- **Operators**: add agents to respond to the chat requests. Add as many as "
"you like, and keep in mind that operators that do not show any activity in "
"Odoo for more than 30min are considered disconnected."
msgstr ""
#: ../../livechat/overview/get_started.rst:33
msgid ""
"- **Options**: set the default text to be shown on the live chat button; an "
"automated welcome message to be seen by visitors when a conversation is "
"initiated, and the text that prompts the user to initiate a chat."
msgstr ""
#: ../../livechat/overview/get_started.rst:36
msgid ""
"- **Channel Rules**: choose an action for a given URL, and/or per country. "
"In the example below, the chat window automatically pops-up 3 seconds after "
"users (from any country) land on the contact us page."
msgstr ""
#: ../../livechat/overview/get_started.rst:43
msgid ""
"GeoIP, which refers to the process of finding a computer terminals "
"geographical location by its IP address, must be installed on your server. "
"Otherwise, under *Channel Rules*, countries are not taken into account."
msgstr ""
#: ../../livechat/overview/get_started.rst:48
msgid "External options"
msgstr ""
#: ../../livechat/overview/get_started.rst:51
msgid ""
"If your website was not created with Odoo, you can find the code to be added"
" to your own, under the *Widget* tab."
msgstr ""
#: ../../livechat/overview/get_started.rst:52
msgid ""
"Odoo also offers an URL you can send to users so they can have access to a "
"single live chat page."
msgstr ""
#: ../../livechat/overview/get_started.rst:59
msgid "Managing chat requests"
msgstr ""
#: ../../livechat/overview/get_started.rst:61
msgid ""
"Conversations initiated by visitors pop up as a direct message, and are "
"shown in *Discuss*. Therefore, inquiries can be answered wherever you are in"
" Odoo."
msgstr ""
#: ../../livechat/overview/get_started.rst:69
msgid ""
"Conversations are dispatched based on the current workload of the online "
"operators."
msgstr ""
#: ../../livechat/overview/get_started.rst:72
msgid "Leave or join a channel"
msgstr ""
#: ../../livechat/overview/get_started.rst:74
msgid ""
"Go to :menuselection:`Website --> Configuration --> Settings`, access your "
"channel under *Live Chat*, and *Join Channel* or *Leave Channel*."
msgstr ""
#: ../../livechat/overview/get_started.rst:82
#: ../../livechat/overview/responses.rst:48
msgid ":doc:`ratings`"
msgstr ""
#: ../../livechat/overview/get_started.rst:83
#: ../../livechat/overview/ratings.rst:45
msgid ":doc:`responses`"
msgstr ""
#: ../../livechat/overview/ratings.rst:3
msgid "Ratings"
msgstr "Évaluations"
#: ../../livechat/overview/ratings.rst:5
msgid ""
"Giving users the opportunity to rate their interactions can help you "
"improving the experience you offer. That means staying on top of your "
"customers' needs, besides keeping track of your operators performances."
msgstr ""
#: ../../livechat/overview/ratings.rst:10
msgid "Customer Rating"
msgstr "Évaluation de la clientèle"
#: ../../livechat/overview/ratings.rst:12
msgid ""
"Once the user chooses to close the chat window, he can rate his interaction."
msgstr ""
#: ../../livechat/overview/ratings.rst:14
msgid ""
"If the user is *Not satisfied* or *Highly dissatisfied*, a field allowing "
"for an explanation is shown."
msgstr ""
#: ../../livechat/overview/ratings.rst:15
msgid "A copy of the conversation can also be sent by email."
msgstr ""
#: ../../livechat/overview/ratings.rst:22
msgid "The rating is shown on the chat window itself for the operator."
msgstr ""
#: ../../livechat/overview/ratings.rst:28
msgid "And under :menuselection:`Report --> Customer Ratings`."
msgstr ""
#: ../../livechat/overview/ratings.rst:35
msgid "Make the rating public"
msgstr ""
#: ../../livechat/overview/ratings.rst:37
msgid ""
"Go to :menuselection:`Website --> Configuration --> Settings`, access your "
"channel form, click on *Go to Website* and on *Unpublished*, to publish the "
"rating of that channel on your website."
msgstr ""
#: ../../livechat/overview/responses.rst:3
msgid "Commands and Canned Responses"
msgstr ""
#: ../../livechat/overview/responses.rst:5
msgid ""
"Using canned responses can help you save time and have a previous, well-"
"thought response, to some of your most common questions and comments."
msgstr ""
#: ../../livechat/overview/responses.rst:9
msgid "Use commands"
msgstr "Utilisez des commandes"
#: ../../livechat/overview/responses.rst:11
msgid ""
"Commands are shortcuts that do specific actions within the chat window:"
msgstr ""
#: ../../livechat/overview/responses.rst:13
msgid "**/help**: shows a help message."
msgstr ""
#: ../../livechat/overview/responses.rst:14
msgid "**/helpdesk**: creates a helpdesk ticket."
msgstr ""
#: ../../livechat/overview/responses.rst:15
msgid "**/helpdesk_search**: searches for a helpdesk ticket."
msgstr ""
#: ../../livechat/overview/responses.rst:16
msgid "**/history**: shows the last 15 visited pages."
msgstr ""
#: ../../livechat/overview/responses.rst:17
msgid "**/lead**: creates a new lead."
msgstr ""
#: ../../livechat/overview/responses.rst:18
msgid "**/leave**: leaves the channel."
msgstr ""
#: ../../livechat/overview/responses.rst:0
msgid ""
"- For *helpdesk tickets*: make sure the application is installed on your "
"database and the option *Live Chat* under :menuselection:`Helpdesk --> "
"Configuration --> Helpdesk Teams` is enabled."
msgstr ""
#: ../../livechat/overview/responses.rst:0
msgid ""
"- For *leads*: the *CRM* application must be installed on your database."
msgstr ""
#: ../../livechat/overview/responses.rst:26
msgid ""
"To access the ticket or lead created from the chat, click on the shortcut "
"link."
msgstr ""
#: ../../livechat/overview/responses.rst:33
msgid ""
"Helpdesk tickets created from the chat automatically add the conversation as"
" a description of the ticket. The same goes for the creation of a lead."
msgstr ""
#: ../../livechat/overview/responses.rst:37
msgid "Send canned responses"
msgstr "Envoyez des réponses toutes prêtes"
#: ../../livechat/overview/responses.rst:40
msgid ""
"Canned responses allow you to have a full piece of text being placed when "
"you type a shortcut word. To create them, go to :menuselection:`Live Chat "
"--> Configuration --> Canned Responses`."
msgstr ""
#: ../../livechat/overview/responses.rst:41
msgid ""
"To use them during a conversation, simply type **:** followed by the "
"shortcut word you created."
msgstr ""
File diff suppressed because it is too large Load Diff
+596
View File
@@ -0,0 +1,596 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2021
# Richard Mathot <rim@odoo.com>, 2021
# Hamid Darabi, 2021
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2021
# Cécile Collart <cco@odoo.com>, 2021
# Fernanda Marques <fem@odoo.com>, 2021
# Priscilla (prs) Odoo <prs@odoo.com>, 2021
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-05-18 07:12+0200\n"
"PO-Revision-Date: 2021-05-18 05:18+0000\n"
"Last-Translator: Priscilla (prs) Odoo <prs@odoo.com>, 2021\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../content/applications/marketing.rst:3
msgid "Marketing"
msgstr "Marketing"
#: ../../content/applications/marketing/marketing_automation.rst:3
msgid "Marketing Automation"
msgstr "Automatisation du Marketing"
#: ../../content/applications/marketing/marketing_automation/advanced.rst:3
msgid "Advanced"
msgstr "Avancé"
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:3
msgid "Understanding Metrics"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:4
msgid ""
"Metrics are values that help you measure progress and can be a powerful way "
"of linking your employees to goals."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:9
msgid ""
"When you create a workflow in Odoo, its visual content already shows metrics"
" in a graph form and in numbers."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:10
msgid "Lets consider the example below:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:19
msgid ""
"The *Target* - business object - is *Lead/Opportunity* and was narrowed down"
" to the ones whose *Tag Name* contain the description “Product”, and have an"
" email address set."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:20
msgid "A total number of 20 records match the criteria."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:28
msgid ""
"Out of those 20 records, 25 have become participants, in other words, they "
"have matched the criteria."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:36
msgid ""
"Every time the system runs, updating numbers and triggering actions, it will"
" look at the *Target* model and check if new records have been added or "
"modified, keeping the flow up-to-date."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:41
msgid ""
"The filter here is applied to *all* activities. Leads that lose the tag in "
"the meantime will be excluded from later activities."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:45
msgid ""
"*Records* is a real-time number, therefore while the workflow is running, "
"changes in opportunity records can be made - delete, add, adjustment - "
"updating the number of records, but not changing the number of participants,"
" as the metric *will not* exclude opportunities that have been set as "
"participants before. It will just add new ones. For this reason, the number "
"of *Records* can be different from the number of *Participants*."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0
msgid ""
"You can also have filters applied to activities individually, under "
"*Domain*. A useful feature to specify an individual filter that will only be"
" performed if the records satisfied both filters, the activity and its "
"domain one."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0
msgid ""
"Example: for an activity sending an SMS, you could make sure a phone number "
"is set to avoid triggering a SMS that would never be sent and crash."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:64
msgid ""
"*Success* is the number of times the searching for participants - that match"
" the filter(s) of that activity - was performed successfully in relation to "
"the total number of participants."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:65
msgid ""
"If a participant does not match the conditions, it will be added to "
"*Rejected*."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:71
msgid ""
"Hovering over the graph, you can see the number of successful and rejected "
"participants, per day, for the last 15 days."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:75
msgid ""
"Every time a new record is added to the *Target* model, it will be "
"automatically added to the workflow, and, it will start the workflow from "
"the beginning (parent action)."
msgstr ""
#: ../../content/applications/marketing/sms_marketing.rst:3
msgid "SMS Marketing"
msgstr "Marketing par SMS"
#: ../../content/applications/marketing/sms_marketing/pricing.rst:3
msgid "Pricing and FAQ"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:3
msgid "SMS Pricing and FAQ"
msgstr "Tarification SMS et FAQ"
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:6
msgid "What do I need to send SMSs?"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:7
msgid ""
"SMS Text Messaging is an In-App Purchase (IAP) service that *requires "
"prepaid credits* to work."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:11
msgid "How many types of SMSs are there?"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:12
msgid "There are 2 types: GSM7 and UNICODE."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:14
msgid ""
"**GSM7** is the standard format, with a limit of 160 characters per message,"
" that includes the following characters:"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:23
msgid ""
"**UNICODE** is the format applied if a special character, that *is not* in "
"the GSM7 list, is used. Limit per SMS: 70 characters."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:27
msgid ""
"For GSM7 SMS the size limit is 160 characters, and for Unicode is 70. *Above"
" these limits, the content is divided into a multi-part message* and the "
"limit of characters is lowered to 153 for GSM7 and to 67 for Unicode. The "
"system will inform you in real-time about the number of SMS your message "
"represents."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:34
msgid "How much does it cost to send an SMS?"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:35
msgid ""
"The price of an SMS depends on the destination and the length (number of "
"characters) of the message."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:37
msgid ""
"To see the **price per country, please consult**: `Odoo SMS - FAQ <https"
"://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:39
msgid ""
"The number of SMSs a message represents will be always available to you in "
"your database."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:49
msgid "How do I buy credits?"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:50
msgid "Go to :menuselection:`Settings --> Buy Credits`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:57
msgid "Or go to :menuselection:`Settings --> View my Services`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:65
msgid ""
"If you are on Odoo Online (SAAS) and have the Enterprise version, you "
"benefit from free trial credits to test the feature."
msgstr ""
"Si vous êtes sur Odoo Online (SAAS) et disposez de la version Entreprise, "
"vous bénéficiez de crédits d'essai gratuits pour tester cette "
"fonctionnalité."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:70
msgid "More common questions"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:72
msgid "**Is there an expiration time for my credits?**"
msgstr "**Est-ce que mes crédits expirent-ils?**"
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:74
msgid "No, credits do not expire."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:77
msgid ""
"**Can I send an SMS to a phone number (which is not a mobile phone) because "
"I see the icon in front of the field “phone”?**"
msgstr ""
"**Puis-je envoyer un SMS vers un numéro (qui n'est pas un mobile) parce que "
"je vois l'icône devant le champ “téléphone”?**"
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:80
msgid "Only if that phone number supports SMS (e.g. SIP phones)."
msgstr ""
"Uniquement si ce numéro de téléphone prend en charge les SMS (par ex. les "
"téléphones SIP)."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:83
msgid "**Do I receive an invoice to buy my credits?**"
msgstr "**Est-ce que je reçois une facture pour acheter mes crédits?**"
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:85
msgid "Yes."
msgstr "Oui."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:88
msgid "**Can the recipient answer to me?**"
msgstr "**Le destinataire peut-il me répondre?**"
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:90
msgid "No, it is not possible to reply to the SMS."
msgstr "Non, il est impossible de répondre à un SMS."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:93
msgid ""
"**What happens if I send multiple SMS but I do not have enough credits to "
"send them all?**"
msgstr ""
"**Que se passe-t-il si je veux envoyer des SMS multiples mais que je n'ai "
"pas suffisament de crédits?**"
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:95
msgid ""
"The whole transaction is counted as a single one, so no SMS will be sent "
"until you have enough credits to send them all."
msgstr ""
"L'ensemble de la transaction est compté comme une seule, de sorte qu'aucun "
"SMS ne sera envoyé tant que vous n'aurez pas suffisamment de crédits pour "
"les envoyer tous."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:99
msgid "**Do I have a history of the sent SMSs?**"
msgstr "**Ai-je un historique des SMS envoyés?**"
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:101
msgid ""
"Yes, the SMS is logged as a note under the chatter of the corresponding "
"record, and a complete history of the SMSs sent is available on "
":doc:`Developer mode </applications/general/developer_mode/activate>` under "
":menuselection:`Technical --> SMS`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:107
msgid "**Can I send as many SMSs I want at once?**"
msgstr "**Puis-je envoyer autant de SMS que je veux en une fois?**"
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:109
msgid "Yes, if you have enough credits."
msgstr "Oui, si vous avez suffisamment de crédits."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:112
msgid ""
"**If I have a number that does not exist in the list of recipients, will I "
"lose credits?**"
msgstr ""
"**Est-ce que je perds des crédits si j'ai un numéro qui n'est pas dans la "
"liste des destinataires?**"
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:114
msgid ""
"Not if the phone number is in the wrong format (e.g. too many digits). "
"Otherwise, if the SMS is sent to the wrong person or to a fake number, the "
"credit will be lost."
msgstr ""
"Non, si le numéro de téléphone n'est pas dans le bon format (par ex. trop de"
" chiffres). Autrement, si le SMS est envoyé à la mauvaise personne ou à un "
"faux numéro, votre crédit sera débité."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:118
msgid ""
"**What happens if I send my SMS to a paying number (e.g.: a contest to win a"
" ticket for a festival)?**"
msgstr ""
"**Que se passe-t-il si j'envoie un SMS à un numéro payant (par ex.: un "
"concours pour gagner un ticket pour un festival)?**"
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:120
msgid ""
"The SMS will not be delivered to that kind of number, so you wont be "
"charged."
msgstr ""
"Les SMS ne sont pas envoyés à ce type de numéro, vous ne serez donc pas "
"débité."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:123
msgid ""
"**Can I identify the numbers that do not exist when I send several SMSs?**"
msgstr ""
"**Puis-je identifier les numéros inexistant lorsque j'envoie plusieurs "
"SMS?**"
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:125
msgid "Only the ones that have an invalid format."
msgstr "Uniquement ceux qui ont un format invalide."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:128
msgid "**How does the GDPR regulation affect this service?**"
msgstr "**Comment le règlement RGPD affect-il ce service?**"
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:130
msgid ""
"Please find our `Privacy Policy here <https://iap.odoo.com/privacy#sms>`__."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:132
msgid "**Can I use my own SMS provider?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:134
msgid ""
"Yes, but it is not possible out of the box. Our experts can help you "
"customize your database to make it happen. Please, check our success packs "
"`here <https://www.odoo.com/pricing-packs>`_."
msgstr ""
#: ../../content/applications/marketing/survey.rst:3
msgid "Survey"
msgstr "Sondage"
#: ../../content/applications/marketing/survey/overview.rst:3
msgid "Overview"
msgstr "Vue d'ensemble"
#: ../../content/applications/marketing/survey/overview/create.rst:3
msgid "Get Started with Surveys"
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:5
msgid ""
"Surveys can be used for a range of purposes that can go from collecting "
"customer feedback, evaluate the success of an event, measure how pleased "
"customers are with your products/services, gauge whether employees are happy"
" and satisfied with their work environment, and even to find out what your "
"market is thinking."
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:11
msgid "Get started"
msgstr "Démarrer"
#: ../../content/applications/marketing/survey/overview/create.rst:13
msgid ""
"When creating your survey, choose a *Title* and *Category*. The *Category* "
"field is used to know in which context the survey is being conducted, as "
"different applications might use it for different purposes such as "
"recruitment, certification, or employee appraisal."
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:22
msgid "Tab: Questions"
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:24
msgid "Add sections and questions by clicking on the respective links."
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:27
msgid ""
"On the *Sections and Questions* form, once the question type is chosen and "
"the answer added, under the tab *Options*, enable *Mandatory Answer*, and "
"set an *Error message* to be shown when the user tries to submit the survey "
"without answering the respective question."
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:29
msgid ""
"Depending on the *Question Type*, the tab *Options* aggregates extra and "
"different possibilities. Examples:"
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:31
msgid ""
"*Single Line Text Box* - can choose a minimum and maximum text length "
"(number of characters - spaces do not count), and its error message."
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:33
msgid ""
"*Multiple choice: multiple answers allowed*: choose between radio buttons or"
" a dropdown menu list, and if you would like to have a comment field. If the"
" user select an answer and type a comment, the values are separately "
"recorded. Or, enable the comment field to be displayed as an answer choice, "
"with which a text type field is displayed."
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:37
msgid ""
"*Matrix Type*: choose if you would like to have one or multiple choices per "
"row."
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:44
msgid "Tab: Description"
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:46
msgid ""
"Write a *Description* to be displayed under the title of the survey's "
"homepage."
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:53
msgid "Click on *Edit* to personalize your pages with the website builder."
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:56
msgid "Tab: Options"
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:58
msgid ""
"Under the tab *Options*, choose the *Layout* of your questions. If choosing "
"*One page per section* or *One page per question*, an option *Back Button* "
"becomes available, which allows the user to go back pages."
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:67
msgid "Test and share the survey"
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:70
msgid ""
"Once your Survey is ready, *Test* it to avoid *Sharing* it with potential "
"errors. As answers get collected, click on *Answers* to access all the "
"details of the respondent and his answers."
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:72
msgid ""
"By default, a filter *Except Test Entries* is applied to keep the list of "
"entries clean with only real participants."
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:79
msgid ""
"Another way to access detailed answers is by going to "
":menuselection:`Participations --> Participations`."
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:80
msgid "Click on *See results* to be redirected to an analytical page."
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:87
#: ../../content/applications/marketing/survey/overview/time_random.rst:34
msgid ":doc:`scoring`"
msgstr ""
#: ../../content/applications/marketing/survey/overview/create.rst:88
#: ../../content/applications/marketing/survey/overview/scoring.rst:35
msgid ":doc:`time_random`"
msgstr ""
#: ../../content/applications/marketing/survey/overview/scoring.rst:3
msgid "Scoring Surveys"
msgstr ""
#: ../../content/applications/marketing/survey/overview/scoring.rst:5
msgid ""
"To measure your respondents performance, knowledge of a subject, or overall"
" satisfaction, attach points to the answers of specific questions. The "
"points are summed up to give your respondent a final score."
msgstr ""
#: ../../content/applications/marketing/survey/overview/scoring.rst:9
msgid ""
"On your surveys form, click on *Add a question* and, under the tab "
"*Options*, choose between *Scoring with answers at the end* or *Scoring "
"without answers at the end*. Now, on your questions form, set the right "
"answer and score."
msgstr ""
#: ../../content/applications/marketing/survey/overview/scoring.rst:17
msgid ""
"Set the percentage score the user needs to achieve to have successfully "
"taken the survey. If enabling *Certificate*, choose its template. The "
"certification is automatically sent by email to the users who successfully "
"finish it."
msgstr ""
#: ../../content/applications/marketing/survey/overview/scoring.rst:25
msgid ""
"Enable *Login required* to be able to *Give Badges*. Badges are related to "
"the eLearning section of your website. Besides the logged-in user, visitors "
"of the website that access the page *Courses* can also see the granted "
"badges."
msgstr ""
#: ../../content/applications/marketing/survey/overview/time_random.rst:3
msgid "Time and Randomize Questions"
msgstr ""
#: ../../content/applications/marketing/survey/overview/time_random.rst:6
msgid "Time Limit"
msgstr "Limite de temps"
#: ../../content/applications/marketing/survey/overview/time_random.rst:10
msgid ""
"On timed surveys, respondents need to complete the survey within a certain "
"period of time. It can be used to ensure that all respondents get the same "
"amount of time to find the answers, or to decrease the chance of having them"
" looking at external resources."
msgstr ""
#: ../../content/applications/marketing/survey/overview/time_random.rst:11
msgid "Set the *Time limit* under the tab *Options*."
msgstr ""
#: ../../content/applications/marketing/survey/overview/time_random.rst:17
msgid ""
"A timer is shown on the pages so the user can keep track of the remaining "
"time. Surveys not \\ submitted by the *Time limit* do not have their answers"
" saved."
msgstr ""
#: ../../content/applications/marketing/survey/overview/time_random.rst:21
msgid "Selection"
msgstr "Sélection"
#: ../../content/applications/marketing/survey/overview/time_random.rst:25
msgid ""
"When you randomize a survey, you allow for the questions to be shuffled in a"
" random order every time someone opens the questionnaire. This can be useful"
" to avoid having respondents looking at each others' answers."
msgstr ""
#: ../../content/applications/marketing/survey/overview/time_random.rst:27
msgid ""
"To do so, under the tab *Options*, enable *Randomized per section*. Now, "
"under the tab *Questions*, set how many of the questions in that section "
"should be taken into account during the shuffling."
msgstr ""
@@ -1,378 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
# Florent de Labarre <florent@iguanayachts.com>, 2020
# Cécile Collart <cco@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-02-04 11:02+0100\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Cécile Collart <cco@odoo.com>, 2020\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../marketing_automation.rst:5
msgid "Marketing Automation"
msgstr "Automatisation du Marketing"
#: ../../marketing_automation/advanced.rst:3
msgid "Advanced"
msgstr "Avancé"
#: ../../marketing_automation/advanced/understanding_metrics.rst:3
msgid "Understanding Metrics"
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:4
msgid ""
"Metrics are values that help you measure progress and can be a powerful way "
"of linking your employees to goals."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:9
msgid ""
"When you create a workflow in Odoo, its visual content already shows metrics"
" in a graph form and in numbers."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:10
msgid "Lets consider the example below:"
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:19
msgid ""
"The *Target* - business object - is *Lead/Opportunity* and was narrowed down"
" to the ones whose *Tag Name* contain the description “Product”, and have an"
" email address set."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:20
msgid "A total number of 20 records match the criteria."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:28
msgid ""
"Out of those 20 records, 25 have become participants, in other words, they "
"have matched the criteria."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:36
msgid ""
"Every time the system runs, updating numbers and triggering actions, it will"
" look at the *Target* model and check if new records have been added or "
"modified, keeping the flow up-to-date."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:41
msgid ""
"The filter here is applied to *all* activities. Leads that lose the tag in "
"the meantime will be excluded from later activities."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:45
msgid ""
"*Records* is a real-time number, therefore while the workflow is running, "
"changes in opportunity records can be made - delete, add, adjustment - "
"updating the number of records, but not changing the number of participants,"
" as the metric *will not* exclude opportunities that have been set as "
"participants before. It will just add new ones. For this reason, the number "
"of *Records* can be different from the number of *Participants*."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:0
msgid ""
"You can also have filters applied to activities individually, under "
"*Domain*. A useful feature to specify an individual filter that will only be"
" performed if the records satisfied both filters, the activity and its "
"domain one."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:0
msgid ""
"Example: for an activity sending an SMS, you could make sure a phone number "
"is set to avoid triggering a SMS that would never be sent and crash."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:64
msgid ""
"*Success* is the number of times the searching for participants - that match"
" the filter(s) of that activity - was performed successfully in relation to "
"the total number of participants."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:65
msgid ""
"If a participant does not match the conditions, it will be added to "
"*Rejected*."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:71
msgid ""
"Hovering over the graph, you can see the number of successful and rejected "
"participants, per day, for the last 15 days."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:75
msgid ""
"Every time a new record is added to the *Target* model, it will be "
"automatically added to the workflow, and, it will start the workflow from "
"the beginning (parent action)."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:79
msgid ":doc:`../overview/automate_actions`"
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:80
msgid ":doc:`../overview/segment`"
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:81
msgid ":doc:`../overview/test`"
msgstr ""
#: ../../marketing_automation/overview.rst:3
msgid "Overview"
msgstr "Vue d'ensemble"
#: ../../marketing_automation/overview/automate_actions.rst:3
msgid "Automate Actions and Create a Workflow"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:4
msgid ""
"Automated workflows are a sign that you are building intelligent, data-"
"driven, multifaceted campaigns to enable the delivery of the right message, "
"to the right prospects, at the right time. It also speeds up processes and "
"creates a seamless experience for employees."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:9
msgid "Segment and create a campaign"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:10
msgid "Go to :menuselection:`Campaigns --> Create`."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:12
msgid ""
"In the example below, the *Marketing Automation* application is fully "
"integrated with *Contacts*."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:14
msgid ""
"But it can also be integrated with other apps like CRM, as long as they are "
"installed in your database."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:23
msgid ""
"Depending on the criteria, the *target model updates itself* while the "
"campaign is running. That means that every new record that meets the "
"criteria will be added to the workflow."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:25
msgid ""
"Example: a campaign starts for leads that have no salesman assigned. If at "
"some point, those leads get to have a salesman assigned to it, the campaign "
"will stop running."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:29
msgid "Create a parent activity and start to build a workflow"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:30
msgid "Click on *Add new activity*."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:37
msgid ""
"*Trigger* is the field to set for the activity to start to de deployed."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:39
msgid ""
"Adopt an *Expiry Duration* if you would like to stop actions from being "
"executed after a certain amount of time and in subsequence to the trigger."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:42
msgid ""
"Under *Domain* you can narrow down your target, even more, applying filters "
"for this specific activity."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:47
msgid "Add Child Activities"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:48
msgid ""
"A *child activity* is an action that will take place based on a condition."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:50
msgid ""
"You can either create or add a child activity if on the previous one: the "
"email was opened or not, the email was replied or not, the link was clicked "
"or not, the email bounced back."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:59
#: ../../marketing_automation/overview/test.rst:53
msgid ":doc:`segment`"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:3
msgid "Segment the Database with Filters"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:4
msgid "Filters let you reach a granular level of detail in your records."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:7
msgid "How to work with filters"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:8
msgid ""
"When working with filters, you will see that some of the rules have an arrow"
" button next to it, informing you that the parameter has more variables "
"within it."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:18
msgid ""
"More than one parameter line - *node* (+) - can be added under what is "
"called a *branch* (...)."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:19
msgid "To exclude a *node* or a *branch*, click on *Delete node* (x)."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:27
msgid ""
"Every time a new branch is created, you can choose if you would like the "
"records to match *all* criteria of the upcoming rules, or *any*, meaning one"
" rule or the other."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:32
msgid "Use cases"
msgstr "Cas d'utilisation"
#: ../../marketing_automation/overview/segment.rst:34
msgid ""
"**Scenario**: narrow the target down to new opportunities in the pipeline."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:39
msgid "**Scenario**: narrow the target down to suppliers."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:44
msgid ""
"**Scenario**: narrow the leads down to the ones that contain a certain tag "
"name."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:49
msgid ""
"**Scenario**: narrow the target down to the attendees of a specific event "
"that purchase a specific category of ticket."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:55
msgid "**Scenario**: narrow the target down to the employees who have kids."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:60
msgid ""
"**Scenario**: narrow the target down to records with a helpdesk ticket "
"solved."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:66
#: ../../marketing_automation/overview/test.rst:52
msgid ":doc:`automate_actions`"
msgstr ""
#: ../../marketing_automation/overview/test.rst:3
msgid "Launch a Test and Start a Campaign"
msgstr ""
#: ../../marketing_automation/overview/test.rst:4
msgid ""
"Before starting a campaign, launching a test allows you to run the workflow "
"on a test contact and view the sequence of events in action, avoiding "
"mistakes."
msgstr ""
#: ../../marketing_automation/overview/test.rst:8
msgid "Launch a test"
msgstr "Lancer un test"
#: ../../marketing_automation/overview/test.rst:9
msgid "Click on *Launch a test*."
msgstr ""
#: ../../marketing_automation/overview/test.rst:12
msgid ""
"Once you have selected the test contact, *Run* the parent activity and the "
"subsequent ones as needed. *Run* and *Stop* activities individually. To stop"
" the whole workflow click on *Stop*."
msgstr ""
#: ../../marketing_automation/overview/test.rst:22
msgid ""
"Launching a test does not add data to your metrics with the purpose of not "
"introducing wrong inputs to reports."
msgstr ""
#: ../../marketing_automation/overview/test.rst:27
msgid "Start and stop a workflow"
msgstr ""
#: ../../marketing_automation/overview/test.rst:28
msgid ""
"Click on *Start* to run the workflow, and on *Stop* to interrupt it. The "
"interruption and new start can happen at any moment. The current status will"
" be shown on the status bar."
msgstr ""
#: ../../marketing_automation/overview/test.rst:38
msgid "Participants and their specific workflow"
msgstr ""
#: ../../marketing_automation/overview/test.rst:39
msgid ""
"*Participants* are all the records that have ever been involved in the "
"campaign."
msgstr ""
#: ../../marketing_automation/overview/test.rst:47
msgid ""
"If you click on *Participants* and open a record, you will find the specific"
" activities the record went/are/will go through, as well as when the "
"workflow was triggered to him. If you wish to cancel an activity click on "
"*Cancel*."
msgstr ""
-48
View File
@@ -1,48 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Richard Mathot <rim@odoo.com>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Fernanda Marques <fem@odoo.com>, 2020\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../mobile/firebase.rst:5
msgid "Mobile"
msgstr "Mobile"
#: ../../mobile/firebase.rst:8
msgid "Push Notifications"
msgstr "Notifications Push"
#: ../../mobile/firebase.rst:10
msgid ""
"As of Odoo 12.0, 13.0 or above, there is no more complex configuration to "
"enable push notifications in the mobile app."
msgstr ""
"Depuis Odoo 12.0 ou supérieure, plus aucune configuration n'est nécessaire "
"pour activer les notifications \"push\" dans l'application mobile."
#: ../../mobile/firebase.rst:13
msgid ""
"Simply go to :menuselection:`Settings --> General Settings --> Odoo Cloud "
"Notification (OCN)` and make sure that **Push Notifications** is checked."
msgstr ""
"Allez simplement à :menuselection:`Paramètres --> Paramètres généraux --> "
"Odoo Cloud Notification (OCN)` et assurez-vous que les **Notifications "
"push** sont activées."
-159
View File
@@ -1,159 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
# Alexandra Jubert <aju@odoo.com>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Fernanda Marques <fem@odoo.com>, 2020\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../planning.rst:5
msgid "Planning"
msgstr "Planification"
#: ../../planning/overview.rst:3
msgid "Overview"
msgstr "Vue d'ensemble"
#: ../../planning/overview/duplicate_a_planning.rst:3
msgid "Create a Schedule and Make Encoding Easier"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:5
msgid ""
"Organize regular schedules or forecast projects in a long term basis. Create"
" shifts to manage your tasks, assign employees, and stay organized at a high"
" level."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:9
msgid "Organize your team by roles"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:11
msgid ""
"Go to :menuselection:`Configuration --> Roles --> Create`. Optionally, go to"
" the *Employees* application, select the respective employee, and under "
"*Work Information* select the *Default Planning Role*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:20
msgid "Make shifts recurrent"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:22
msgid ""
"While creating a shift, select *Repeat* and configure as needed, saving you "
"from the need of re-planning it."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:30
msgid ""
"Repeated shifts are generated for the next six months. A modification is "
"possible in :doc:`Developer mode <../../general/developer_mode/activate>`, "
"from *Settings*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:38
msgid "To duplicate a shift in the Gantt view, press CTRL + drag and drop."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:41
msgid "Save shifts as templates"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:43
msgid ""
"If creating a shift on the fly and know you might use that template in the "
"future, click on *Save as a Template*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:51
msgid ""
"To create a template in advance, go to :menuselection:`Configuration --> "
"Shifts Templates --> Create`."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:55
msgid "Duplicate a planning from the previous week"
msgstr "Dupliquez un planning de la semaine précédente"
#: ../../planning/overview/duplicate_a_planning.rst:57
msgid ""
"When in the Gantt view, either under *Schedule by Employee, Role or "
"Project*, instead of re-planning shifts that have been planned before, "
"simply click on *Copy Previous Week*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:65
msgid ""
"The integration with the *Time off* and *Employee* applications, show you "
"grayed cells to the days when the employee does not work and is on vacation "
"time, for example."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:3
msgid "Send Planned Shifts and Give Employees Autonomy Over Shifts"
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:5
msgid ""
"If you are not on top of your tasks and shifts you might fall behind, losing"
" productivity. Allowing your employees to have a say over shifts helps you "
"to be on top of your workload, and gives them flexibility."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:10
msgid "Publish and send the planned week by email"
msgstr "Publiez et envoyez le planning par email"
#: ../../planning/overview/send_planned_shifts.rst:12
msgid ""
"Once you have your shifts planned, click on *Send Schedule*. Select *Include"
" Open shift* if you would like the *Unassigned* shifts to be seen."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:19
msgid ""
"Choose if you just want to *Publish* or *Publish and Send*. If you *Publish "
"and Send*, employees get an email that redirects them to their planned "
"tasks:"
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:26
msgid ""
"Employees will not be able to see shifts until they have been published."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:29
msgid "Let employees unassign themselves from shifts"
msgstr "Laissez vos employés se désassigner eux-mêmes des postes"
#: ../../planning/overview/send_planned_shifts.rst:31
msgid ""
"Go to *Configuration* and enable *Allow Unassignment*. From now on, when an "
"employee opens his tasks, he can indicate his unavailability clicking on *I "
"am unavailable*. The shift will be opened again, allowing someone else to "
"take it."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:44
msgid "Employees have portal access; users have access to the database."
msgstr ""
File diff suppressed because it is too large Load Diff
-246
View File
@@ -1,246 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Richard Mathot <rim@odoo.com>, 2020
# Anthony Chaussin <chaussin.anthony@gmail.com>, 2021
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-02-04 11:02+0100\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Anthony Chaussin <chaussin.anthony@gmail.com>, 2021\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../portal/my_odoo_portal.rst:6 ../../portal/my_odoo_portal.rst:9
msgid "My Odoo Portal"
msgstr "Portail \"My Odoo\""
#: ../../portal/my_odoo_portal.rst:11
msgid ""
"In this section of the portal, you will find all the communications between "
"you and Odoo: documents such as quotations, sales orders, invoices and "
"subscriptions."
msgstr ""
"Dans cette section du portail, vous trouverez toutes les communications "
"entre vous et Odoo : les documents comme les devis, bons de commande, "
"factures et abonnements."
#: ../../portal/my_odoo_portal.rst:15
msgid ""
"To access this section, you have to log with your username and password to "
"`Odoo <https://www.odoo.com/my/home>`_. If you are already logged in, just "
"click on your name on the top-right corner and select \"My Account\"."
msgstr ""
"Pour accéder à cette section, vous devez vous connecter avec votre nom "
"d'utilisateur et votre mot de passe à `Odoo "
"<https://www.odoo.com/my/home>`_. Si vous êtes déjà connecté, il vous suffit"
" de cliquer sur votre nom en haut à droite et de sélectionner \"Mon "
"compte\"."
#: ../../portal/my_odoo_portal.rst:23
msgid "Quotations"
msgstr "Devis"
#: ../../portal/my_odoo_portal.rst:25
msgid ""
"Here you will find all the quotations sent to you by Odoo. For example, a "
"quotation can be generated for you after adding an application or a user to "
"your database or if your contract has to be renewed."
msgstr ""
"Vous trouverez ici toutes les devis qui vous ont été envoyés par Odoo. Par "
"exemple, un devis peut être généré pour vous après avoir ajouté une "
"application ou un utilisateur à votre base de données ou si votre contrat "
"doit être renouvelé."
#: ../../portal/my_odoo_portal.rst:32
msgid ""
"The *Valid Until* column shows the date through which the quotation is "
"valid; after that date, the quotation will be \"Expired\". By clicking on "
"the quotation, you will see all the details of the offer, such as the "
"pricing and other useful information."
msgstr ""
"La colonne *Valide jusqu'au* indique la date jusqu'à laquelle le devis est "
"valable ; après cette date, le devis sera \"Expiré\". En cliquant sur le "
"devis, vous verrez tous les détails de l'offre, tels que le prix et d'autres"
" informations utiles."
#: ../../portal/my_odoo_portal.rst:39
msgid ""
"If you want to accept the quotation, just click \"Accept & Pay,\" and the "
"quote will get confirmed. If you don't want to accept it, or you need to ask"
" for some modifications, click on \"Ask Changes Reject.\""
msgstr ""
"Si vous souhaitez accepter le devis, il vous suffit de cliquer sur "
"\"Accepter et payer\", et le devis sera confirmé. Si vous ne voulez pas "
"l'accepter, ou si vous devez demander des modifications, cliquez sur "
"\"Demander des modifications Rejeter\"."
#: ../../portal/my_odoo_portal.rst:44
msgid "Sales Orders"
msgstr "Bons de commandes"
#: ../../portal/my_odoo_portal.rst:46
msgid ""
"All your purchases within Odoo (Upsells, Themes, Applications, etc.) will be"
" registered under this section."
msgstr ""
"Tous vos achats au sein d'Odoo (Upsells, Themes, Applications, etc.) seront "
"enregistrés sous cette section."
#: ../../portal/my_odoo_portal.rst:52
msgid ""
"By clicking on the sale order, you can review the details of the products "
"purchased and process the payment."
msgstr ""
"En cliquant sur l'ordre de vente, vous pouvez consulter les détails des "
"articles achetés et effectuer le paiement."
#: ../../portal/my_odoo_portal.rst:56
msgid "Invoices"
msgstr "Factures"
#: ../../portal/my_odoo_portal.rst:58
msgid ""
"All the invoices of your subscriptions and/or sales orders will be shown in "
"this section. The tag before the Amount Due will indicate if the invoice has"
" been paid."
msgstr ""
"Toutes les factures de vos abonnements et/ou de vos commandes seront "
"indiquées dans cette section. L'étiquette précédant le montant dû indiquera "
"si la facture a été payée."
#: ../../portal/my_odoo_portal.rst:65
msgid ""
"Just click on the invoice if you wish to see more information, pay the "
"invoice, or download a PDF version of the document."
msgstr ""
"Il vous suffit de cliquer sur la facture si vous souhaitez obtenir plus "
"d'informations, payer la facture ou télécharger une version PDF du document."
#: ../../portal/my_odoo_portal.rst:69
msgid "Tickets"
msgstr "Tickets"
#: ../../portal/my_odoo_portal.rst:71
msgid ""
"When you submit a ticket through `Odoo Support <https://www.odoo.com/help>`,"
" a ticket will be created. Here you can find all the tickets that you have "
"opened, the conversations between you and our Agents, and the statuses and "
"IDs (# Ref) of the tickets."
msgstr ""
"Lorsque vous soumettez un ticket par l'intermédiaire de `Odoo Support "
"<https://www.odoo.com/help>`, un ticket sera créé. Vous trouverez ici tous "
"les tickets que vous avez ouverts, les conversations entre vous et nos "
"agents, ainsi que les statuts et les identifiants (# Ref) des tickets."
#: ../../portal/my_odoo_portal.rst:79
msgid "Subscriptions"
msgstr "Abonnements"
#: ../../portal/my_odoo_portal.rst:81
msgid ""
"You can access your subscriptions with Odoo from this section. The first "
"page shows you the subscriptions that you have and their status."
msgstr ""
"Vous pouvez accéder à vos abonnements avec Odoo à partir de cette section. "
"La première page vous montre les abonnements que vous avez et leur statut."
#: ../../portal/my_odoo_portal.rst:87
msgid ""
"By clicking on the subscription you will access all the details regarding "
"your plan: the number of applications purchased, the billing information, "
"and the payment method."
msgstr ""
"En cliquant sur l'abonnement, vous aurez accès à tous les détails concernant"
" votre forfait : le nombre d'applications achetées, les informations de "
"facturation et le mode de paiement."
#: ../../portal/my_odoo_portal.rst:91
msgid ""
"To change the payment method, click on \"Change Payment Method\" and enter "
"the new credit card details."
msgstr ""
"Pour modifier le mode de paiement, cliquez sur \"Modifier le mode de "
"paiement\" et saisissez les nouvelles données de la carte de crédit."
#: ../../portal/my_odoo_portal.rst:97
msgid ""
"If you want to remove the credit cards that are saved, you can do so by "
"clicking on \"Manage your payment methods\" at the bottom of the page. Click"
" \"Delete\" to delete the payment method."
msgstr ""
"Si vous souhaitez supprimer les cartes de crédit qui sont enregistrées, vous"
" pouvez le faire en cliquant sur \"Gérer vos modes de paiement\" en bas de "
"la page. Cliquez sur \"Supprimer\" pour supprimer le mode de paiement."
#: ../../portal/my_odoo_portal.rst:105
msgid ""
"At the date of the next invoice, if there is no payment information provided"
" or if your credit card has expired, the status of your subscription will "
"change to \"To Renew\". You will then have 7 days to provide a valid method "
"of payment. After this delay, the subscription will be closed, and you will "
"no longer be able to access the database."
msgstr ""
"À la date de la prochaine facture, si aucune information de paiement n'est "
"fournie ou si votre carte de crédit a expiré, le statut de votre abonnement "
"passera à \"À renouveler\". Vous aurez alors 7 jours pour fournir un moyen "
"de paiement valable. Passé ce délai, l'abonnement sera fermé et vous ne "
"pourrez plus accéder à la base de données."
#: ../../portal/my_odoo_portal.rst:111
msgid "Success Packs"
msgstr "Success Packs"
#: ../../portal/my_odoo_portal.rst:112
msgid ""
"With a Success Pack/Partner Success Pack, you are assigned an expert to "
"provide unique personalized assistance to help you customize your solution "
"and optimize your workflows as part of your initial implementation. These "
"hours never expire, allowing you to utilize them whenever you need support."
msgstr ""
"Avec un Success Pack/Partner Success Pack, un expert vous est attribué pour "
"vous fournir une assistance personnalisée unique afin de vous aider à "
"personnaliser votre solution et à optimiser vos flux de travail dans le "
"cadre de votre mise en œuvre initiale. Ces heures n'expirent jamais, ce qui "
"vous permet de les utiliser chaque fois que vous avez besoin d'aide."
#: ../../portal/my_odoo_portal.rst:118
msgid ""
"If you need information about how to manage your database see "
":ref:`db_online`"
msgstr ""
"Si vous avez besoin d'informations sur la façon de gérer votre base de "
"données, voir :ref:`db_online`"
#: ../../portal/my_odoo_portal.rst:121
msgid "Delete your Odoo.com account"
msgstr ""
#: ../../portal/my_odoo_portal.rst:123
msgid ""
"In order to delete your Odoo.com account, you have to reach out to our "
"`Support Services <https://www.odoo.com/help>`_."
msgstr ""
#: ../../portal/my_odoo_portal.rst:126
msgid "If you want to delete one of your databases, see :ref:`db_online`"
msgstr ""
#: ../../portal/my_odoo_portal.rst:129
msgid ""
"If you wish instead to formally request the deletion of all the information "
"connected to your email address as per the European Union General Data "
"Protection Regulation (GDPR), please send an email to privacy@odoo.com."
msgstr ""
-26
View File
@@ -1,26 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Richard Mathot <rim@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Richard Mathot <rim@odoo.com>, 2020\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../practical.rst:3
msgid "Practical Information"
msgstr "Informations pratiques"
File diff suppressed because it is too large Load Diff
-144
View File
@@ -1,144 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-02-04 11:02+0100\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Martin Trigaux, 2020\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../project.rst:5
msgid "Project"
msgstr "Projet"
#: ../../project/planning.rst:3
msgid "Planning"
msgstr "Planification"
#: ../../project/planning/forecast.rst:3
msgid "Forecast Resources Across Projects"
msgstr ""
#: ../../project/planning/forecast.rst:5
msgid ""
"Allocate the needed time for specific tasks under a planned shift. Once that"
" is done, analyse Key Performance Indicators (KPIs), so you can evaluate "
"your employees performance and workload, besides the progress of your "
"projects/tasks when comparing the planned and effective hours."
msgstr ""
#: ../../project/planning/forecast.rst:10
msgid "Allocate times under shifts"
msgstr ""
#: ../../project/planning/forecast.rst:12
msgid ""
"When planning a shift, in the *Planning* application, create a project and a"
" task on the fly, or simply select the one you want."
msgstr ""
#: ../../project/planning/forecast.rst:20
msgid ""
"*Allocated Time (%)* allows you to define the percentage of time you would "
"like your employee to work on that specific task during his shift. See that "
"information in hours on *Allocated hours*."
msgstr ""
#: ../../project/planning/forecast.rst:22
msgid ""
"The calculation shows you how many hours out of the total shift time (*End "
"date* - *Start date*) are spent by the employee on that task."
msgstr ""
#: ../../project/planning/forecast.rst:24
msgid ""
"On :menuselection:`Project --> Planning --> By Project`, immediately see the"
" total number of employees allocated per project."
msgstr ""
#: ../../project/planning/forecast.rst:31
msgid "Compare forecast hours with the effective ones"
msgstr ""
#: ../../project/planning/forecast.rst:33
msgid ""
"Now, once the employee has timesheeted his hours in the task, go to "
"*Project* and with the *View list*, under *All Tasks*, conveniently see the "
"*Planned Hours* compared to the *Remaining Hours*, and a calculation of the "
"*Progress*."
msgstr ""
#: ../../project/planning/forecast.rst:42
msgid "Reminder: the option *Timesheets* has to be enabled on your project."
msgstr ""
#: ../../project/tasks.rst:3
msgid "Tasks"
msgstr "Tâches"
#: ../../project/tasks/email_alias.rst:3
msgid "Create Project's Tasks from an Email Alias"
msgstr ""
#: ../../project/tasks/email_alias.rst:5
msgid ""
"When you already have an email address that customers know from the top of "
"their heads, changing it is the last thing you want to do. Instead, link "
"that address to your project and transform those conversations into "
"structured work. It automatically creates a task in the first stage of a "
"project."
msgstr ""
#: ../../project/tasks/email_alias.rst:11
msgid "Set up an incoming email server"
msgstr ""
#: ../../project/tasks/email_alias.rst:14
msgid ""
"On the *Settings* application, enable *External Email Servers* and define "
"the incoming email alias you would like to use."
msgstr ""
#: ../../project/tasks/email_alias.rst:15
msgid "**For more information**: :doc:`../../discuss/advanced/email_servers`"
msgstr ""
#: ../../project/tasks/email_alias.rst:18
msgid "Configure the email alias in your project"
msgstr ""
#: ../../project/tasks/email_alias.rst:22
msgid ""
"Now that you have the incoming email server set up, go to "
":menuselection:`Project --> Configuration --> Projects --> Edit`. Under the "
"*Emails* tab, define the wanted email alias and choose the policy to receive"
" a message."
msgstr ""
#: ../../project/tasks/email_alias.rst:23
msgid "In addition, you can now directly set it when creating a new project."
msgstr ""
#: ../../project/tasks/email_alias.rst:30
msgid ""
"All the recipients of the email (To/Cc/Bcc) are automatically added as "
"followers of the task."
msgstr ""
#: ../../project/tasks/email_alias.rst:32
msgid "The email can be seen under the name of your project on the dashboard."
msgstr ""
-884
View File
@@ -1,884 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2021
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-02-11 09:05+0100\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Martin Trigaux, 2021\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../purchase.rst:5
msgid "Purchase"
msgstr "Achats"
#: ../../purchase/advanced.rst:3
msgid "Advanced"
msgstr "Avancé"
#: ../../purchase/advanced/analyze.rst:3
msgid "Analyze the performance of your purchases"
msgstr ""
#: ../../purchase/advanced/analyze.rst:5
msgid ""
"If your company regularly purchases products, you have several reasons to "
"track and analyze your performance. The insights gathered can help you to "
"better forecast and plan your future orders. For example, you can assess if "
"your business is dependent on particular vendors, and the data can help you "
"negotiate discounts on prices."
msgstr ""
#: ../../purchase/advanced/analyze.rst:11
msgid "Generate customized reports"
msgstr ""
#: ../../purchase/advanced/analyze.rst:13
msgid ""
"Go to *Reporting* to access the purchase analysis. Simply by accessing the "
"reporting dashboard, you can get a quick overview of your actual "
"performance. By default, the reporting dashboard displays a line chart "
"presenting the untaxed amount of your purchase orders per day, and below it,"
" key metrics and a pivot table."
msgstr ""
#: ../../purchase/advanced/analyze.rst:22
msgid ""
"While the data initially presented is useful, there are several tools and "
"features you can use to get even more insights on your purchases."
msgstr ""
#: ../../purchase/advanced/analyze.rst:26
msgid "Use filters to select the data you need"
msgstr ""
#: ../../purchase/advanced/analyze.rst:28
msgid ""
"Odoo offers several default filters you can use and combine by clicking on "
"*Filters*. When you select one or several filters, Odoo looks for all the "
"orders that match at least one of the filters you have chosen and populates "
"the chart, key metrics, and pivot table with the data. The pre-configured "
"filters are:"
msgstr ""
#: ../../purchase/advanced/analyze.rst:33
msgid "All *Requests for Quotation*"
msgstr ""
#: ../../purchase/advanced/analyze.rst:35
msgid "All *Purchase Orders*, except canceled ones"
msgstr ""
#: ../../purchase/advanced/analyze.rst:37
msgid ""
"*Confirmation Date Last Year* includes all orders that were confirmed the "
"previous year, canceled purchase orders included"
msgstr ""
#: ../../purchase/advanced/analyze.rst:40
msgid ""
"*Order Date* includes all orders - request for quotations and purchases "
"orders (canceled ones included) - depending on their date of creation"
msgstr ""
#: ../../purchase/advanced/analyze.rst:43
msgid ""
"*Confirmation Date* includes all confirmed orders, canceled ones included, "
"depending on their date of confirmation"
msgstr ""
#: ../../purchase/advanced/analyze.rst:47
msgid ""
"When you have to select a period, you can use multiple years, and, with at "
"least one year selected, multiple quarters and the three most recent months."
msgstr ""
#: ../../purchase/advanced/analyze.rst:51
msgid ""
"If you use the *Order Date* or *Confirmation Date* filters, the *Comparison*"
" feature appears next to *Filters*. It enables you to compare the period you"
" filtered with the previous one."
msgstr ""
#: ../../purchase/advanced/analyze.rst:59
msgid "Add custom filters"
msgstr ""
#: ../../purchase/advanced/analyze.rst:61
msgid ""
"Thanks to the 31 filtering options to choose from, the possibilities of your"
" customizing your dataset are almost limitless. Go to "
":menuselection:`Filters --> Add Custom Filter`, specify the condition the "
"filtering option should meet (e.g. *is equal to*, *contains*, etc.), and "
"click on *Apply*. If you want to select orders matching several conditions "
"simultaneously (*and* operator), repeat the process to add another custom "
"filter. If you want to use the *or* operator, don't click on *Apply*, and "
"click on *Add a condition* instead. Once you have added all the desired "
"filtering options, click on *Apply*."
msgstr ""
#: ../../purchase/advanced/analyze.rst:74
msgid ""
"To avoid having to recreate custom filters every time, save them by clicking"
" on :menuselection:`Favorites --> Save current search --> Save`. The "
"customized search filter can then be accessed by clicking on *Favorites* or "
"can even be set as the default filter when you open the reporting dashboard."
msgstr ""
#: ../../purchase/advanced/analyze.rst:80
msgid "Measure exactly what you need"
msgstr ""
#: ../../purchase/advanced/analyze.rst:82
msgid ""
"Before selecting what you want to measure, you need to decide whether you "
"prefer using the graph view or the pivot view. By default, the dashboard "
"presents both views. However, the measures you select won't be applied to "
"both views. You can access each view separately by clicking on the icons at "
"the top right of the dashboard."
msgstr ""
#: ../../purchase/advanced/analyze.rst:92
msgid "Visualize your data"
msgstr ""
#: ../../purchase/advanced/analyze.rst:94
msgid ""
"You can transform the main graph in just a click by selecting one of the "
"three charts: bar, line or pie. Fourteen different measures are available, "
"but you can only use one at a time. However, you can group the measure using"
" one or several of the 19 *Groups*."
msgstr ""
#: ../../purchase/advanced/analyze.rst:102
msgid ""
"For bar and line charts, the selected measure is your y-axis, and the first "
"group you select is used to create the x-axis. Adding more group adds "
"additional lines (line chart) or transforms your bar chart into a stacked "
"bar chart. For pie charts, the more groups you select, the more slices are "
"displayed."
msgstr ""
#: ../../purchase/advanced/analyze.rst:108
msgid "Explore your data"
msgstr ""
#: ../../purchase/advanced/analyze.rst:110
msgid ""
"The pivot table view enables you to explore your data in great detail. "
"Unlike the graph view, the pivot table enables you to add several measures "
"at the same time. By clicking on *Measures* or on the **+** sign in the "
"*Total* column, you can add as many as you want, each assigned to a new "
"column. By clicking on the **+** sign in the *Total* row, you can add "
"*Groups*. If you click on a group's **+** sign, you can add a sub-group, and"
" so on."
msgstr ""
#: ../../purchase/advanced/analyze.rst:121
msgid ""
"You can insert your pivot table's data directly in the Spreadsheet app or "
"export it as an Excel file."
msgstr ""
#: ../../purchase/manage_deals.rst:3
msgid "Manage deals"
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:3
msgid "Purchase agreements: blanket orders and calls for tenders"
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:5
msgid ""
"There are two main types of purchase agreements preconfigured in Odoo: "
"blanket orders and call for tenders."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:8
msgid ""
"Blanket orders are long-term agreements between a company and a vendor to "
"deliver products on a recurring basis with predetermined pricing. Your "
"company should consider using them when you frequently purchase the same "
"products from the same vendor in varying quantities and/or at different "
"times. Among their many benefits, you can save time as the ordering process "
"is simplified, and money thanks to more advantageous bulk pricing."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:14
msgid ""
"Calls for tenders use a special procedure to request offers from multiple "
"vendors at the same time. While public sector organizations are often "
"legally bound to release calls for tenders when they want to purchase goods "
"or services, private organizations can also use them to get the best deal "
"among several vendors."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:20
msgid "Enable purchase agreements"
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:22
msgid ""
"From the Purchase app, go to :menuselection:`Configuration --> Settings` and"
" activate *Purchase Agreements*."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:30
msgid "Configure or create new types of purchase agreements"
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:32
msgid ""
"Before you start using purchase agreements, make sure they are configured "
"the way you want by going to :menuselection:`Configuration --> Purchase "
"Agreement Types`. From there, you can edit the way blanket orders and calls "
"for tenders or *Create* a new type of purchase agreement. You can configure "
"the:"
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:37
msgid "Agreement Type: the name you want to give to the agreement."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:39
msgid ""
"Agreement Selection Type: you can either select multiple offers using "
"*Select multiple RFQ (non-exclusive)*, which is the default setting for both"
" blanket orders and calls for tenders, or a single offer using *Select only "
"one RFQ (exclusive)*, which is sometimes needed for calls for tenders where "
"you only want to select a single vendor."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:44
msgid ""
"Lines: generally, you would always want to select *Use lines of agreement*, "
"which are the different product lines you can configure when you set up your"
" purchase agreement. However, you can select *Do not create RfQ lines "
"automatically* if you don't want your requests for quotations to be pre-"
"filled in with that information."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:49
msgid ""
"Quantities: if you use lines of agreements, you can also specify "
"independently if the products' quantities should be used to pre-fill new "
"requests for quotations. The default option for blanket orders is *Set "
"quantities manually*, while for calls for tenders are set to *Use quantities"
" of agreement*."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:59
msgid "Set up a blanket order"
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:61
msgid ""
"Go to :menuselection:`Orders --> Purchase Agreements` and click on *Create*."
" Select *Blanket Order* as your *Agreement Type*. Next, select the vendor. "
"The other fields aren't mandatory, but you usually want to define an "
"*Agreement Deadline* after which the blanket order won't be valid anymore."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:65
msgid ""
"Next, add the products you want to order and their price. Note that you can "
"also add a *Quantity* for each product, for example, if you have agreed with"
" your vendor to order a specific minimum quantity each time or in total. If "
"you have configured your blanked order to *Set quantities manually*, this is"
" only used for informational purposes."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:74
msgid ""
"You can also write any *Terms and Conditions* at the bottom of the "
"agreement. Once you are satisfied with your blanket order, click on "
"*Confirm*. Its status then changes from *Draft* to *Ongoing* and it's ready "
"to be used."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:79
msgid "Create requests for quotation from the blanket order"
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:81
msgid ""
"You can now create new quotations from the blanket order whenever you need "
"it by clicking on *New Quotation*. Odoo automatically fills in requests for "
"quotation with the information initially defined when you set up the blanket"
" order. Depending on the way you configured the *Purchase Agreement Type*, "
"product lines can also be pre-filled."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:86
msgid ""
"From here, you can quickly view all the requests for quotations made under "
"that blanket order by clicking on *RFQs/Orders*."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:94
msgid ""
"You can also create a *Request for Quotation* the usual way and then link it"
" to an existing *Blanket Order*."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:98
msgid "Blanket orders and replenishment"
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:100
msgid ""
"Blanket orders can be used for :doc:`automated replenishment "
"<../../purchase/products/reordering>`, as once a blanket order is confirmed,"
" a new vendor line is added to your product. Make sure the related vendor is"
" in the first position if you have several vendors linked to your product."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:109
msgid "Set up a call for tenders"
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:111
msgid ""
"Go to :menuselection:`Orders --> Purchase Agreements` and click on *Create*."
" Select *Call for Tenders* as your *Agreement Type*. The other fields aren't"
" mandatory, but you can add the date you want to be delivered and set an "
"agreement deadline. You usually don't want to select a vendor for calls for "
"tenders as you are looking to get quotations from multiple vendors."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:116
msgid ""
"Next, add the products you want to order and in what quantity. For calls for"
" tenders, you typically don't add a price, as the vendors should give you "
"their best quote."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:119
msgid ""
"You can also write any *Terms and Conditions* at the bottom of the "
"agreement. Once you are ready, click on *Confirm*."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:127
msgid "Requests quotations from the call for tenders"
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:129
msgid ""
"You can now request new quotations from the call for tenders. Click on *New "
"Quotation* and select one of your vendors you want to invite to the call for"
" tenders. Product lines should also be pre-filled in, depending on how you "
"configured the *Purchase Agreement Type*. Click on *Send by email* to send "
"it to the vendor. Go back to the call for tenders and repeat this process "
"for each vendor."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:139
msgid ""
"Once you have sent a request for quotation to every vendor and receiving "
"their quotes, click on *Validate* to proceed to the bid selection. Next, "
"click on the RFQs/Orders smart button to view all your vendors' quotations."
msgstr ""
#: ../../purchase/manage_deals/agreements.rst:147
msgid ""
"Click on each request for quotation to add the price communicated by your "
"vendors manually. When that's done, select the most advantageous offer and "
"click on *Confirm Order*. This automatically closes the call for tenders. "
"You can now proceed with the purchase order as you would for a regular one."
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:3
msgid "Control and know when vendor bills should be paid"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:5
msgid ""
"With Odoo, you can define how your vendor bills are controlled. For each "
"purchase order, you can decide when the related vendor bill should be paid: "
"either before or after you have received your products. You can also check "
"at a glance what is the billing status of each purchase order."
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:9
msgid ""
"With the 3-way matching feature, Odoo compares the information appearing on "
"the *Purchase Order*, the *Vendor Bill* and the *Receipt*, and lets you know"
" if you should pay the bill. This way you can avoid paying incorrect or "
"fraudulent vendor bills."
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:14
msgid "Vendor bills default control policy"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:16
msgid ""
"As a first step, open your Purchase app and go to "
":menuselection:`Configuration --> Settings` to set the default bill control "
"policy for all the products created onwards."
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:23
msgid ""
"By selecting *On ordered quantities*, you can create a vendor bill as soon "
"as you confirm an order. The quantities mentioned in the purchase order are "
"used to generate the draft bill."
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:26
msgid ""
"If you choose *On received quantities* instead, you can only create one once"
" you have at least received some of the products you have ordered. The "
"quantities you have received are used to generate the draft bill. If you try"
" to create one without having received any product, you get an error "
"message."
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:36
msgid "Change a specific product's control policy"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:38
msgid ""
"If you want to modify a specific product's control policy, go to "
":menuselection:`Products --> Products`, open it, click on *Edit* and go to "
"the *Purchase tab*. There you can change a product's default bill control "
"policy."
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:47
msgid "View a purchase order's billing status"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:49
msgid ""
"Once you confirm an order, you can view its *Billing Status* by going to the"
" *Other Information* tab."
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:56
msgid ""
"Below you can find a list of the different *Billing Status*, and when they "
"are displayed, depending on the products' bill control policy."
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:60
msgid "**Billing status**"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:60
msgid "**Conditions**"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:62
msgid "*On received quantities*"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:62
msgid "*On ordered quantities*"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:64
msgid "*Nothing to Bill*"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:64
msgid "PO confirmed; no products received"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:64
msgid "*(Not applicable)*"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:66
msgid "*Waiting Bills*"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:66
msgid "All/some products received; bill not created"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:66
msgid "PO confirmed"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:68
msgid "*Fully Billed*"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:68
msgid "All/some products received; draft bill created"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:68
msgid "Draft bill created"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:72
msgid "Determine when to pay with 3-way matching"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:74
msgid ""
"First, go to :menuselection:`Configuration --> Settings` and activate *3-way"
" matching*."
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:81
msgid ""
"3-way matching is intended to work with the bill control policy set to *On "
"received quantities*."
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:84
msgid "Should I pay the vendor bill?"
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:86
msgid ""
"With the feature activated, your vendor bills now display the *Should Be "
"Paid* field under the *Other info* tab."
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:93
msgid ""
"As you can't create a bill until you have received your products - and if "
"you haven't received all of them, Odoo only includes the products you have "
"received in the draft bill - the *Should Be Paid* status is set to *Yes* "
"when you create one."
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:97
msgid ""
"If you edit a draft bill to increase the billed quantity, change the price, "
"or add other products, the *Should Be Paid* status is set to *Exception*. It"
" means Odoo notices the discrepancy, but that you might have a valid reason "
"to have done so."
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:101
msgid ""
"Once the payment has been registered and mentions *Paid*, the *Should Be "
"Paid* status is set to *No*."
msgstr ""
#: ../../purchase/manage_deals/control_bills.rst:109
msgid ""
"The *Should Be Paid* status is set automatically by Odoo. However, you can "
"change the status manually when you are viewing a bill in edit mode."
msgstr ""
#: ../../purchase/products.rst:3
msgid "Products"
msgstr "Articles"
#: ../../purchase/products/reordering.rst:3
msgid "Dont run out of stock with reordering rules"
msgstr ""
#: ../../purchase/products/reordering.rst:5
msgid ""
"To make sure you never run out of stock, you can define *Reordering Rules* "
"on products. Thanks to them, Odoo can help you replenish your stock "
"automatically when it reaches set quantities or whenever a sales order is "
"created."
msgstr ""
#: ../../purchase/products/reordering.rst:9
msgid "You need to install the *Inventory app* to use reordering rules."
msgstr ""
#: ../../purchase/products/reordering.rst:12
msgid "Configure your storable product"
msgstr ""
#: ../../purchase/products/reordering.rst:14
msgid ""
"Open or create a product with its *Product Type* set to *Storable Product*."
msgstr ""
#: ../../purchase/products/reordering.rst:20
msgid ""
"As you are purchasing this product from a vendor, go to the product's "
"*Purchase tab* and add a vendor by clicking on *Add a line*. You can add "
"multiple vendors, but make sure to order them correctly, since reordering "
"rules always use the first vendor in a list. You can add a price, but it "
"isn't necessary for the reordering rule to work. In addition, you can add a "
"minimum quantity you must order to benefit from that price."
msgstr ""
#: ../../purchase/products/reordering.rst:27
msgid ""
"If the quantity Odoo has to reorder doesn't match the minimum quantity "
"specified, Odoo selects the next vendor on your list. If you don't have "
"another vendor on your list, the reordering rule won't work. For that "
"purpose, you can add the same vendor multiple times with different prices "
"for different quantities."
msgstr ""
#: ../../purchase/products/reordering.rst:37
msgid ""
"By default, a draft purchase order is created. However, if you have enabled "
"*Purchase Agreements*, you can *Propose a call for tenders* instead as shown"
" in the image above. For more information, see "
":doc:`../manage_deals/agreements`"
msgstr ""
#: ../../purchase/products/reordering.rst:41
msgid ""
"Next, make sure the correct route is selected under the Inventory tab of "
"your product. If you created your product within the Purchase app, the *Buy*"
" route is selected by default. If you are looking to dropship your product, "
"select *Dropship*."
msgstr ""
#: ../../purchase/products/reordering.rst:50
msgid "Set up your reordering rule"
msgstr ""
#: ../../purchase/products/reordering.rst:52
msgid "Open your product and click on the *Reordering Rules* button."
msgstr ""
#: ../../purchase/products/reordering.rst:58
msgid ""
"Once you are on the product's reordering rules page, click on *Create*."
msgstr ""
#: ../../purchase/products/reordering.rst:61
msgid ""
"You can access and create reordering rules from :menuselection:`Inventory "
"--> Configuration --> Reordering Rules` and from :menuselection:`Inventory "
"--> Operations --> Replenishment`. By default, the replenishment view "
"presents a summary of all the products that you might need to purchase to "
"fulfill your sales orders. From there, you can ask Odoo with a single click "
"to order a product once or automate all orders for that product, future "
"orders included."
msgstr ""
#: ../../purchase/products/reordering.rst:68
msgid "Define quantities"
msgstr ""
#: ../../purchase/products/reordering.rst:70
msgid ""
"You can set a **minimum quantity** your stock should always have. Once set, "
"if your stock goes below the minimum quantity, and if you selected the Buy "
"route, a request for quotation is automatically generated to reach that "
"minimum quantity, plus any additional quantity needed to fill in a sales "
"order for example."
msgstr ""
#: ../../purchase/products/reordering.rst:75
msgid ""
"If you set a **maximum quantity**, every time the product has to be "
"replenished, enough products are reordered to reach the maximum quantity."
msgstr ""
#: ../../purchase/products/reordering.rst:78
msgid ""
"If you want to order only the exact quantity needed to fill in a sales order"
" for example, set both both the minimum and maximum quantity to **zero**. "
"The quantity mentioned in the sales order is then used by the reordering "
"rule."
msgstr ""
#: ../../purchase/products/reordering.rst:82
msgid ""
"You can also add a **quantity multiple** to only order products in batches "
"of a certain quantity. Click on the optional columns drop-down menu, and "
"select *Multiple Quantity* to show the column. Bear in mind that you might "
"go over the maximum quantity you set if your rule includes a quantity "
"multiple, as Odoo orders enough products to reach the maximum quantity and "
"respect the set quantity multiple."
msgstr ""
#: ../../purchase/products/reordering.rst:92
msgid ""
"If you selected multiple routes for the same product under its Inventory "
"tab, make sure to select your *Preferred Route* on your reordering rule by "
"clicking on the optional columns drop-down menu, adding the *Preferred "
"Route* column, and selecting the right route."
msgstr ""
#: ../../purchase/products/uom.rst:3
msgid "Purchase in different units of measure than sales"
msgstr ""
#: ../../purchase/products/uom.rst:5
msgid ""
"When you purchase a product, it may happen that your vendor uses a different"
" unit of measure than you do when you sell it. This can cause confusion "
"between sales and purchase representatives. It is also time-consuming to "
"convert measures manually every time. With Odoo, you can configure your "
"product once and let Odoo handle the conversion."
msgstr ""
#: ../../purchase/products/uom.rst:10
msgid "Consider the following examples:"
msgstr ""
#: ../../purchase/products/uom.rst:12
msgid ""
"You purchase orange juice from an American vendor, and they use **gallons**."
" However, your customers are European and use **liters**."
msgstr ""
#: ../../purchase/products/uom.rst:15
msgid ""
"You buy curtains from a vendor in the form of **rolls** and you sell pieces "
"of the rolls to your customers using **square meters**."
msgstr ""
#: ../../purchase/products/uom.rst:19
msgid "Enable units of measure"
msgstr ""
#: ../../purchase/products/uom.rst:21
msgid ""
"Open your Sales app and go to :menuselection:`Configuration --> Settings`. "
"Under Product Catalog, enable *Units of Measure*."
msgstr ""
#: ../../purchase/products/uom.rst:29
msgid "Specify sales and purchase units of measure"
msgstr ""
#: ../../purchase/products/uom.rst:32
msgid "Standard units of measure"
msgstr ""
#: ../../purchase/products/uom.rst:34
msgid ""
"A variety of units of measure are available by default in your database. "
"Each belongs to one of the five pre-configured units of measure categories: "
"*Length / Distance*, *Unit*, *Volume*, *Weight* and *Working Time*."
msgstr ""
#: ../../purchase/products/uom.rst:39
msgid ""
"You can create your new units of measure and units of measure categories "
"(see next section)."
msgstr ""
#: ../../purchase/products/uom.rst:41
msgid ""
"To specify different units of measures for sales and purchases, open the "
"Purchase app and go to :menuselection:`Products --> Products`. Create a "
"product or select an existing one. Under the product's *General Information*"
" tab, first select the *Unit of Measure* to be used for sales (as well as "
"for other apps such as inventory). Then, select the *Purchase Unit of "
"Measure* to be used for purchases."
msgstr ""
#: ../../purchase/products/uom.rst:47
msgid ""
"Back to the first example, if you purchase orange juice from your vendor in "
"**gallons** and sell it to your customers in **liters**, first select *L* "
"(liters) as the *Unit of Measure*, and *gal (US)* (gallons) as the *Purchase"
" Unit of Measure*, then click on *Save*."
msgstr ""
#: ../../purchase/products/uom.rst:56
msgid "Create new units of measure and units of measure categories"
msgstr ""
#: ../../purchase/products/uom.rst:58
msgid ""
"Sometimes you need to create your own units and categories, either because "
"the measure is not pre-configured in Odoo or because the units do not relate"
" with each other (e.g. kilos and centimeters)."
msgstr ""
#: ../../purchase/products/uom.rst:62
msgid ""
"If you take the second example where you buy curtains from a vendor in the "
"form of **rolls** and you sell pieces of the rolls using **square meters**, "
"you need to create a new *Units of Measure Category* in order to relate both"
" units of measure."
msgstr ""
#: ../../purchase/products/uom.rst:66
msgid ""
"To do so, go to :menuselection:`Configuration --> Units of Measure "
"Categories`. Click on *Create* and name the category."
msgstr ""
#: ../../purchase/products/uom.rst:73
msgid ""
"The next step is to create the two units of measures. To do so, go to "
":menuselection:`Configuration --> Units of Measure`."
msgstr ""
#: ../../purchase/products/uom.rst:76
msgid ""
"First, create the unit of measure used as the reference point for converting"
" to other units of measure inside the category by clicking on *Create*. Name"
" the unit and select the units of measure category you just created. For the"
" *Type*, select *Reference Unit of Measure for this category type*. Enter "
"the *Rounding Precision* you would like to use. The quantity computed by "
"Odoo is always a multiple of this value."
msgstr ""
#: ../../purchase/products/uom.rst:82
msgid ""
"In the example, as you cannot purchase less than 1 roll and won't use "
"fractions of a roll as a unit of measure, you can enter 1."
msgstr ""
#: ../../purchase/products/uom.rst:89
msgid ""
"If you use a *Rounding Precision* inferior to 0.01, a warning message might "
"appear stating that it is higher than the *Decimal Accuracy* and that it "
"might cause inconsistencies. If you wish to use a *Rounding Precision* lower"
" than 0.01, first :doc:`activate the Developer Mode "
"<../../general/developer_mode/activate>`, then go to "
":menuselection:`Settings --> Technical --> Database Structure --> Decimal "
"Accuracy`, select *Product Unit of Measure* and edit *Digits* accordingly. "
"For example, if you want to use a rounding precision of 0.00001, set "
"*Digits* to 5."
msgstr ""
#: ../../purchase/products/uom.rst:96
msgid ""
"Next, create a second unit of measure, name it, and select the same units of"
" measure category as your reference unit. As *Type*, select *Smaller* or "
"*Bigger than the reference Unit of Measure*, depending on your situation."
msgstr ""
#: ../../purchase/products/uom.rst:100
msgid ""
"As the curtain roll equals to 100 square meters, you should select "
"*Smaller*."
msgstr ""
#: ../../purchase/products/uom.rst:102
msgid ""
"Next, you need to enter the *Ratio* between your reference unit and the "
"second one. If the second unit is smaller, the *Ratio* should be greater "
"than 1. If the second unit is larger, the ratio should be smaller than 1."
msgstr ""
#: ../../purchase/products/uom.rst:106
msgid "For your curtain roll, the ratio should be set to 100."
msgstr ""
#: ../../purchase/products/uom.rst:112
msgid ""
"You can now configure your product just as you would using Odoo's standard "
"units of measure."
msgstr ""
-467
View File
@@ -1,467 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Cécile Collart <cco@odoo.com>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Fernanda Marques <fem@odoo.com>, 2020\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../quality.rst:5
msgid "Quality"
msgstr "Qualité"
#: ../../quality/alert.rst:3
msgid "Alert"
msgstr "Alerte"
#: ../../quality/alert/alert_mo.rst:3
msgid "Generate a Quality Alert from a Manufacturing Order"
msgstr ""
#: ../../quality/alert/alert_mo.rst:5
msgid ""
"Speaking of manufacturing orders, you have two different situations to "
"consider in Odoo. Those two will result in two different processes:"
msgstr ""
#: ../../quality/alert/alert_mo.rst:8
msgid "You work with a simple manufacturing flow;"
msgstr ""
#: ../../quality/alert/alert_mo.rst:10
msgid "You work with a complex manufacturing flow that includes routings."
msgstr ""
#: ../../quality/alert/alert_mo.rst:13
msgid "Simple manufacturing flow"
msgstr ""
#: ../../quality/alert/alert_mo.rst:15
msgid ""
"If you work with simple manufacturing orders, the *Quality Alerts* will be "
"launched from the manufacturing order itself. When manufacturing a product "
"for which you need to process quality controls, a button *Quality Alert* "
"will appear on the top of your manufacturing order."
msgstr ""
#: ../../quality/alert/alert_mo.rst:23
msgid ""
"By clicking on the button, you can specify the quality problem that arose "
"during the process."
msgstr ""
#: ../../quality/alert/alert_mo.rst:29
msgid ""
"If one of the quality checks failed, the button will be highlighted on the "
"document. If not, the button wont be highlighted."
msgstr ""
#: ../../quality/alert/alert_mo.rst:36 ../../quality/checks/quality_mo.rst:50
msgid "Manufacturing Flow with Routings"
msgstr ""
#: ../../quality/alert/alert_mo.rst:38
msgid ""
"If you work with routings defined on your manufacturing orders, the quality "
"alerts will be launched directly from the work orders on which the quality "
"checks took place."
msgstr ""
#: ../../quality/alert/alert_mo.rst:48
msgid ""
"Then, a button *Quality Alert* will be available from the work order view. "
"When you click on the button, you can specify the quality problem that "
"appeared during the process."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:3
msgid "Generate a Quality Alert from a Transfer"
msgstr ""
#: ../../quality/alert/alert_transfer.rst:6
msgid "Use the Quality Alert"
msgstr "Utilisez l'alerte qualité"
#: ../../quality/alert/alert_transfer.rst:8
msgid ""
"Every time you perform some *Quality Checks* on a transfer, a *Quality "
"Alert* button appears. You can always use it. The button is automatically "
"highlighted once you have a failed quality check for the transfer."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:16
msgid ""
"If you click on that *Quality Alert* button, you can specify what was the "
"problem with the product."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:22
msgid ""
"The *Quality Alert* that is created from the transfer can be found via the "
"button appearing on the top right corner of the transfer."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:28
msgid ""
"You can also access all your *Quality Alerts* via the menu, accessible under"
" *Control*."
msgstr ""
#: ../../quality/checks.rst:3
msgid "Checks"
msgstr "Chèques"
#: ../../quality/checks/quality_mo.rst:3
msgid "Perform Quality Checks on Manufacturing Orders"
msgstr ""
#: ../../quality/checks/quality_mo.rst:5
msgid ""
"There are two different situations to consider and that will differ in Odoo "
"processes:"
msgstr ""
#: ../../quality/checks/quality_mo.rst:8
msgid "You work with simple manufacturing flows;"
msgstr ""
#: ../../quality/checks/quality_mo.rst:10
msgid ""
"You work with complex manufacturing flows that are represented by the use of"
" routings in Odoo."
msgstr ""
#: ../../quality/checks/quality_mo.rst:13
msgid "Simple Manufacturing Flow"
msgstr ""
#: ../../quality/checks/quality_mo.rst:16
#: ../../quality/checks/quality_mo.rst:53
#: ../../quality/checks/quality_transfers.rst:6
msgid "Create the Quality Control Point"
msgstr "Créez le point de contrôle qualité"
#: ../../quality/checks/quality_mo.rst:18
msgid ""
"To create a quality control point, open the quality app and go to "
":menuselection:`Control --> Control Points`. There, hit create. Make sure to"
" select *Manufacturing* as operation and choose the type of quality check "
"you want to perform."
msgstr ""
#: ../../quality/checks/quality_mo.rst:27
#: ../../quality/checks/quality_mo.rst:69
#: ../../quality/checks/quality_transfers.rst:17
msgid "Process the Quality Check"
msgstr ""
#: ../../quality/checks/quality_mo.rst:29
msgid ""
"Once your *Quality Control Point* has been created, you can create a "
"manufacturing order for your product. Now, and before marking the "
"manufacturing as done, you can register the *Quality Checks*."
msgstr ""
#: ../../quality/checks/quality_mo.rst:39
msgid ""
"Once you have performed your quality checks, you can find them via the "
"*Quality Checks* button available on the manufacturing order form."
msgstr ""
#: ../../quality/checks/quality_mo.rst:46
msgid ""
"If you want to access all your quality checks, you can do this by opening "
"the quality checks menu, under quality control."
msgstr ""
#: ../../quality/checks/quality_mo.rst:55
msgid ""
"If you want to create a *Quality Control Point*, open the *Quality* app and "
"go to :menuselection:`Control --> Control Points`. Then, click on create. "
"Make sure to select *Manufacturing* as operation and select the work order "
"operation on which the quality check should be performed."
msgstr ""
#: ../../quality/checks/quality_mo.rst:64
msgid ""
"Choosing the work order operation is necessary if you want the quality "
"checks to be performed in the work orders. After that, you can choose the "
"type of quality check."
msgstr ""
#: ../../quality/checks/quality_mo.rst:71
msgid ""
"Once your *Quality Control Point* has been configured, create a "
"manufacturing order for your product. You have to plan it if you want to "
"generate the necessary work orders."
msgstr ""
#: ../../quality/checks/quality_mo.rst:78
msgid ""
"Now, process the work order and your quality check will appear. In this "
"example, the quality check requests to enter the serial number of the Table "
"Top component."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:3
msgid "Perform Quality Checks on Transfers"
msgstr ""
#: ../../quality/checks/quality_transfers.rst:8
msgid ""
"To create a *Quality Control Point*, open the *Quality* application. Then, "
"go to :menuselection:`Quality Control --> Control Points --> Create`. Now, "
"you can define the quality control point you want to apply to a specific "
"product. Dont forget to select a transfer operation type."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:19
msgid ""
"Lets say that we will receive a laptop. First, create a planned receipt for"
" the product. Then, on the receipt, you will see a *Quality Checks* button "
"that appears to proceed to the quality check you configured before."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:27
msgid ""
"By clicking on it, the instruction set on the quality control point will be "
"displayed and will require the check value."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:33
msgid ""
"Once the quality check is done, you can find it linked to the corresponding "
"transfer and access it by clicking on the button."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:39
msgid ""
"But, if the quality check failed, the stat button will appear in red "
"(instead of green) and Odoo will suggest you to create a *Quality Alert* by "
"highlighting the corresponding button."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:46
msgid ""
"The quality checks can also be found in the *Quality* application by opening"
" the *Quality Checks* menu, under *Quality Control*."
msgstr ""
#: ../../quality/control.rst:3
msgid "Control"
msgstr "Contrôle"
#: ../../quality/control/control_points.rst:3
msgid "Define Quality Control Points"
msgstr "Définissez des points de contrôle qualité"
#: ../../quality/control/control_points.rst:5
msgid ""
"Quality is an important factor when it comes to products or services. "
"Nowadays, quality has become the differentiating factor for all goods and "
"services. It is vital for businesses to deliver products that meet or exceed"
" expectations. It also helps minimize waste."
msgstr ""
#: ../../quality/control/control_points.rst:10
msgid ""
"That is why most manufacturers would not think of eliminating the quality "
"control from their manufacturing process. After all, removing quality "
"controls would dramatically increase the number of defective products that "
"the company then has to rework or scrap."
msgstr ""
#: ../../quality/control/control_points.rst:15
msgid ""
"Then, using business applications to ensure data quality is important. With "
"Odoo insuring the rear, any major problem can be avoided before occurring!"
msgstr ""
#: ../../quality/control/control_points.rst:20
msgid "Quality Control Points"
msgstr "Points de contrôle de la qualité"
#: ../../quality/control/control_points.rst:22
msgid ""
"To create a *Quality Control Point*, go to :menuselection:`Quality --> "
"Quality Control --> Control Points`. Once there, define the product on which"
" the quality control point should take place. The operation at which it "
"takes place also is to be defined here."
msgstr ""
#: ../../quality/control/control_points.rst:27
msgid ""
"The *Quality Control Points* take place during transfers or during the "
"manufacturing process of the products. If working with routings on *Bill of "
"Materials*, you have to precise at which step of the manufacturing process "
"the quality control point needs to be applied."
msgstr ""
#: ../../quality/control/control_points.rst:32
msgid ""
"The *Control Type* defines at which frequency the quality checks should take"
" place:"
msgstr ""
#: ../../quality/control/control_points.rst:35
msgid ""
"**All operations**: all the operations automatically generate quality checks"
" to perform;"
msgstr ""
#: ../../quality/control/control_points.rst:38
msgid ""
"**Randomly**: the quality checks only perform on x% of the operation. The "
"percentage needs to be defined on the control point;"
msgstr ""
#: ../../quality/control/control_points.rst:41
msgid ""
"**Periodically**: the quality checks are performed periodically. The "
"periodicity is based on the defined period (once a day, once a week)."
msgstr ""
#: ../../quality/control/control_points.rst:50
msgid "Quality Control Point Types"
msgstr "Types de point de contrôle de la qualité"
#: ../../quality/control/control_points.rst:52
msgid ""
"Now, one thing remains to be configured: the type of quality check. There "
"are several types that can be used: text, take a picture, pass-fail, take a "
"measure, register consumed material, register by-product, and print label."
msgstr ""
#: ../../quality/control/control_points.rst:58
msgid ""
"Some types are available only with the manufacturing application installed."
msgstr ""
#: ../../quality/control/control_points.rst:62
msgid "Text"
msgstr "Texte"
#: ../../quality/control/control_points.rst:64
msgid ""
"This control point type allows giving instructions to workers during the "
"transfer or during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:80
msgid "Take a Picture"
msgstr "Prendre une photo"
#: ../../quality/control/control_points.rst:82
msgid ""
"This control point type asks to take a picture of the product applied in a "
"transfer or when manufacturing it."
msgstr ""
#: ../../quality/control/control_points.rst:98
msgid ""
"This process can be simplified by using a connected :doc:`camera "
"<../../iot/devices/measurement_tool>`."
msgstr ""
#: ../../quality/control/control_points.rst:102
msgid "Pass-Fail"
msgstr ""
#: ../../quality/control/control_points.rst:104
msgid ""
"*Pass-Fail* requires to specify if the products pass or fail specific "
"criteria. It can be applied for both transfers or manufacturing orders."
msgstr ""
#: ../../quality/control/control_points.rst:111
msgid ""
"For this kind of type, there is the possibility to define a failure message "
"giving instructions to follow in case of failure."
msgstr ""
#: ../../quality/control/control_points.rst:127
msgid "Take a Measure"
msgstr ""
#: ../../quality/control/control_points.rst:129
msgid ""
"Taking measures requires to enter the products measurements during a "
"transfer or during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:132
msgid ""
"To use it, it necessary to specify the norm for your products measurements,"
" but also a tolerance threshold. Doing so, all the products with good "
"measures can are automatically accepted."
msgstr ""
#: ../../quality/control/control_points.rst:140
msgid ""
"As for *Pass-Fail*, this type allows defining a failure message that gives "
"instructions to the worker."
msgstr ""
#: ../../quality/control/control_points.rst:156
msgid ""
"This process can be simplified by using connected :doc:`measurement tools "
"<../../iot/devices/camera>`."
msgstr ""
#: ../../quality/control/control_points.rst:159
msgid "Register Consumed Materials"
msgstr ""
#: ../../quality/control/control_points.rst:161
msgid ""
"When using *Register Consumed Materials*, it is required to register the "
"components serial/lot numbers during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:165
#: ../../quality/control/control_points.rst:182
msgid "This type is only available when working with routings."
msgstr ""
#: ../../quality/control/control_points.rst:176
msgid "Register By-Products"
msgstr ""
#: ../../quality/control/control_points.rst:178
msgid ""
"With *Register By-Products*, it is required to register the serial/lot "
"number of the by-products that are manufactured."
msgstr ""
#: ../../quality/control/control_points.rst:193
msgid "Print Label"
msgstr ""
#: ../../quality/control/control_points.rst:195
msgid ""
"*Print Label*, as its name points out, allows printing labels to add to the "
"product during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:207
msgid ""
"This process can be simplified by using a connected :doc:`printer "
"<../../iot/devices/printer>`."
msgstr ""
-23
View File
@@ -1,23 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-11-22 13:16+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Florian Hatat <mininet@wanadoo.fr>, 2017\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../recruitment.rst:5
msgid "Recruitment"
msgstr "Recrutement"
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
+272
View File
@@ -0,0 +1,272 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2021
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2021
# Fernanda Marques <fem@odoo.com>, 2021
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-05-18 07:12+0200\n"
"PO-Revision-Date: 2021-05-18 05:18+0000\n"
"Last-Translator: Fernanda Marques <fem@odoo.com>, 2021\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../content/applications/settings.rst:3
msgid "Settings"
msgstr "Configuration"
#: ../../content/applications/settings/users_and_features.rst:6
msgid "Users and Features"
msgstr "Utilisateurs et fonctionnalités"
#: ../../content/applications/settings/users_and_features.rst:8
msgid ""
"As the administrator of your database, you are responsible for its usage. "
"This includes the Apps you install as well as the number of users currently "
"in use."
msgstr ""
"En tant qu'administrateur de votre base de données, vous êtes responsable de"
" son utilisation. Cela inclut les Applications que vous installez, ainsi que"
" le nombre d'utilisateurs qui les utilisent."
#: ../../content/applications/settings/users_and_features.rst:12
msgid ""
"Odoo is many things (ERP, CMS, CRM application, e-Commerce backend, etc.) "
"but it is *not* a smartphone. You should apply caution when adding/removing "
"features (especially Apps) on your database since this may impact your "
"subscription amount significantly (or switch you from a free account to a "
"paying one on our online platform)."
msgstr ""
"Odoo est beaucoup de choses (ERP, CMS, CRM application, site de "
"eCommerce,etc...) mais ce n'est *pas* un smartphone. Vous devez faire preuve"
" de prudence lorsque vous ajouter/supprimez des fonctionnalités (en "
"particulier les applications) à votre base de données, car cela pourrait "
"influer sur le montant de votre abonnement de manière significative (ou vous"
" faire passer d'un compte gratuit à un payant sur notre plate-forme en "
"ligne)."
#: ../../content/applications/settings/users_and_features.rst:18
msgid ""
"This page contains some information as to how you can manage your Odoo "
"instances. Before carrying any of these procedures, we **strongly** advise "
"to test them on a duplicate of your database first. That way, if something "
"goes wrong, your day-to-day business is not impacted."
msgstr ""
"Cette page contient quelques informations sur la façon de gérer votre "
"instance Odoo. Avant d'appliquer ces procédures nous vous recommandons "
"**fortement** des les tester d'abord sur un double de votre base de données."
" De cette façon, si quelque chose se passe mal, votre activité quotidienne "
"n'en sera pas affectée."
#: ../../content/applications/settings/users_and_features.rst:23
msgid ""
"You can find guides on how to duplicate your databases both for :ref:`online"
" <duplicate_online>` and :ref:`on premise <duplicate_premise>` "
"installations."
msgstr ""
"Vous pouvez trouver des instruction sur la manière de dupliquer vos bases de"
" données à la fois pour les installations :ref:`en ligne <duplicate_online>`"
" et :ref:`sur site <duplicate_premise>`."
#: ../../content/applications/settings/users_and_features.rst:27
msgid ""
"If you have questions about the content of this page or if you encounter an "
"issue while carrying out these procedures, please contact us through our "
"`support form <https://www.odoo.com/help>`__."
msgstr ""
"Si vous avez des questions sur le contenu de cette page ou si vous "
"rencontrez un problème lors de l'exécution de ces procédures, contactez-nous"
" via notre `formulaire d'assistance <https://www.odoo.com/help>`__."
#: ../../content/applications/settings/users_and_features.rst:33
msgid "Deactivating Users"
msgstr "Désactivation d'Utilisateurs"
#: ../../content/applications/settings/users_and_features.rst:35
msgid ""
"Make sure you have sufficient **administrative rights** if you want to "
"change the status of any of your users."
msgstr ""
"Assurez-vous que vous disposez des **permissions** suffisantes si vous "
"voulez changer le statut de l'un de vos utilisateurs."
#: ../../content/applications/settings/users_and_features.rst:38
msgid ""
"In your Odoo instance, click on **Settings**. You will have a section "
"showing you the active users on your database. Click on **Manage Users.**"
msgstr ""
"Sur votre instance Odoo, cliquez sur **Paramètres**. Vous verrez apparaître "
"une section reprenant les utilisateurs actifs de votre base de données. "
"Cliquez sur **Gérer les utilisateurs.**"
#: ../../content/applications/settings/users_and_features.rst:42
#: ../../content/applications/settings/users_and_features.rst:79
msgid "|settings|"
msgstr "|settings|"
#: ../../content/applications/settings/users_and_features.rst:42
msgid "|browse_users|"
msgstr "|browse_users|"
#: ../../content/applications/settings/users_and_features.rst:45
msgid "You'll then see the list of your users."
msgstr "Vous verrez alors la liste de vos utilisateurs."
#: ../../content/applications/settings/users_and_features.rst:50
msgid ""
"The pre-selected filter *Internal Users* shows your paying users (different "
"from the *Portal Users* which are free). If you remove this filter, you'll "
"get all your users (the ones you pay for and the portal ones)"
msgstr ""
"Le filtre pré-sélectionné *Utilisateurs Internes* montre vos utilisateurs "
"payants (pas les *Utilisateurs du Portail* qui sont gratuits). Si vous "
"supprimez ce filtre, vous obtiendrez tous les utilisateurs (les payants et "
"ceux du portail)"
#: ../../content/applications/settings/users_and_features.rst:55
msgid ""
"In your list of users, click on the user you want to deactivate. As soon as "
"you are on the userform, click on the Action drop down menu, and then click "
"on Archive."
msgstr ""
"Dans votre liste d'utilisateurs cliquez sur l'utilisateur que vous souhaitez"
" désactiver. Une fois sur le formulaire utilisateur, cliquez sur le menu de "
"la liste déroulante Action, puis cliquez sur Archiver."
#: ../../content/applications/settings/users_and_features.rst:63
msgid "The user is now deactivated."
msgstr "L'utilisateur est maintenant désactivé."
#: ../../content/applications/settings/users_and_features.rst:65
msgid "**Never** deactivate the main user (*admin*)"
msgstr "Ne désactivez **jamais** l'utilisateur principal (*admin*)"
#: ../../content/applications/settings/users_and_features.rst:68
msgid "Uninstalling Apps"
msgstr "Désinstallation d'Applications"
#: ../../content/applications/settings/users_and_features.rst:70
msgid ""
"Make sure you first test what you are about to do on a :ref:`duplicate "
"<duplicate_online>` of your database before making any changes (*especially*"
" installing/uninstalling apps)."
msgstr ""
"Assurez-vous d'abord de tester ce que vous allez faire sur une "
":ref:`duplication` <duplicate_online>` de votre base de données avant de "
"faire des modifications (*surtout* l'installation/désinstallation "
"d'applications)."
#: ../../content/applications/settings/users_and_features.rst:74
msgid ""
"In your Odoo instance click on **Settings**; in this app, you will be able "
"to see how many applications you have installed. Click on **Browse Apps** to"
" access the list of your installed applications."
msgstr ""
"Dans votre instance Odoo cliquez sur **Configuration**; dans ce module, vous"
" verrez le nombre d'applications que vous avez installées. Cliquez sur "
"**Parcourir les applications** pour accéder à la liste des applications."
#: ../../content/applications/settings/users_and_features.rst:79
msgid "|browse_apps|"
msgstr "|browse_apps|"
#: ../../content/applications/settings/users_and_features.rst:82
msgid ""
"In your applications' dashboard, you will see all the icons of your "
"applications. Click on the application you want to uninstall. Then, on the "
"form of the application, click on **Uninstall**."
msgstr ""
"Dans le tableau de bord de vos applications, vous verrez toutes les icônes "
"de vos applications. Cliquez sur l'application que vous souhaitez "
"désinstaller. Puis, sur la fiche de l'application, cliquez sur "
"**Désinstaller**."
#: ../../content/applications/settings/users_and_features.rst:89
msgid ""
"Some applications have dependencies, like Invoicing, eCommerce, etc. "
"Therefore, the system will give you a warning message to advise you of what "
"is about to be removed. If you uninstall your application, all its "
"dependencies will be uninstalled as well (and the data in them will "
"permanently disappear). If you are sure you still want to uninstall it, then"
" click **Confirm**."
msgstr ""
"Certaines applications ont des dépendances, comme Facturation, eCommerce, "
"etc... Par conséquent, le système vous avertira pour vous informer de ce qui"
" est sur le point d'être retiré. Si vous désinstallez votre application, "
"toutes ses dépendances seront également désinstallées (et les données "
"qu'elles contiennent vont disparaître également de façon irréversible). Si "
"vous êtes sûr que vous voulez toujours la désinstaller, alors cliquez sur "
"**Confirmer**."
#: ../../content/applications/settings/users_and_features.rst:96
msgid ""
"Last, after having checked the warning message (if any), click **Confirm**."
msgstr ""
"Enfin, après avoir vérifié le message d'avertissement (le cas échéant), "
"cliquez sur **Confirmer**."
#: ../../content/applications/settings/users_and_features.rst:101
msgid "You have finished uninstalling your application."
msgstr "Vous avez terminé la désinstallation de votre application."
#: ../../content/applications/settings/users_and_features.rst:104
msgid "Good to know"
msgstr "Bon à savoir"
#: ../../content/applications/settings/users_and_features.rst:106
msgid ""
"**Uninstalling apps, managing users, etc. is up to you**: no one else can "
"know if your business flow is broken better than you. If we were to "
"uninstall applications for you, we would never be able to tell if relevant "
"data had been removed or if one of your business flow was broken because we "
"*do not know how you work* and therefore cannot validate these kinds of "
"operations."
msgstr ""
"**Désinstaller des applications, gérer les utilisateurs, etc... c'est à vous"
" de le faire**: personne mieux que vous ne peut savoir si les activités de "
"votre entreprise sont interrompues. Si nous devions désinstaller des "
"applications pour vous, nous ne serions jamais en mesure de dire si des "
"données pertinentes ont été supprimées ou si l'une de vos activités a été "
"interrompue, parce que nous *ne savons pas comment vous travaillez* et ne "
"pouvons donc pas valider ce types d'opérations."
#: ../../content/applications/settings/users_and_features.rst:112
msgid ""
"**Odoo Apps have dependencies**: this means that you may need to install "
"modules that you do not actively use to access some features of Odoo you "
"might need. For example, the Website Builder app is needed to be able to "
"show your customer their Quotes in a web page. Even though you might not "
"need or use the Website itself, it is needed for the Online Quotes feature "
"to work properly."
msgstr ""
"**Les Applications Odoo ont des dépendances** : cela signifie que vous "
"devrez peut-être installer des modules que vous n'utilisez pas activement "
"pour accéder à certaines fonctionnalités d'Odoo dont vous avez besoin. Par "
"exemple, l'application Construction de site web est requise pour pouvoir "
"montrer à vos clients des devis sur une page internet. Même si vous n'avez "
"pas besoin du site Web lui-même, il est requis pour que la fonctionnalité "
"Offres en ligne fonctionne correctement."
#: ../../content/applications/settings/users_and_features.rst:119
msgid ""
"**Always test app installation/removal on a duplicate** (or on a free trial "
"database): that way you can know what other apps may be required, etc. This "
"will avoid surprises when uninstalling or when receiving your invoices."
msgstr ""
"**Tester toujours l'installation/la suppression d'application sur une "
"copie** (ou sur une base de données d'essai gratuit) : de cette façon, vous "
"pouvez savoir quelles autres applications peuvent être nécessaires, etc... "
"Cela évitera des surprises lors de la désinstallation ou lors de la "
"réception de vos factures d'abonnement."
-152
View File
@@ -1,152 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2021
# Nathan Grognet <ngr@odoo.com>, 2021
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-02-04 11:02+0100\n"
"PO-Revision-Date: 2021-02-04 10:31+0000\n"
"Last-Translator: Nathan Grognet <ngr@odoo.com>, 2021\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../sign.rst:5
msgid "Sign"
msgstr "Signature"
#: ../../sign/overview.rst:3
msgid "Overview"
msgstr "Vue d'ensemble"
#: ../../sign/overview/signature_validity.rst:3
msgid "Validity of electronic signatures"
msgstr ""
#: ../../sign/overview/signature_validity.rst:5
msgid ""
"The legal validity of electronic signatures generated by Odoo depends on the"
" legislation of your country. Companies doing business abroad should "
"consider electronic signature laws of other countries as well."
msgstr ""
#: ../../sign/overview/signature_validity.rst:10
msgid "In the European Union"
msgstr ""
#: ../../sign/overview/signature_validity.rst:12
msgid ""
"The `eIDAS regulation <http://data.europa.eu/eli/reg/2014/910/oj>`_ "
"establishes the framework for electronic signatures in all `27 member states"
" of the European Union <https://europa.eu/european-union/about-"
"eu/countries_en>`_."
msgstr ""
#: ../../sign/overview/signature_validity.rst:16
msgid "It distinguishes three types of electronic signatures:"
msgstr ""
#: ../../sign/overview/signature_validity.rst:18
msgid "Electronic signatures"
msgstr ""
#: ../../sign/overview/signature_validity.rst:19
msgid "Advanced electronic signatures"
msgstr ""
#: ../../sign/overview/signature_validity.rst:20
msgid "Qualified electronic signatures"
msgstr ""
#: ../../sign/overview/signature_validity.rst:22
msgid ""
"Odoo generates the first type, regular electronic signatures, and these "
"signatures can produce legal effects in the EU, as the regulation states "
"that “an electronic signature shall not be denied legal effect and "
"admissibility as evidence in legal proceedings solely on the grounds that it"
" is in an electronic form or that it does not meet the requirements for "
"qualified electronic signatures.”"
msgstr ""
#: ../../sign/overview/signature_validity.rst:27
msgid ""
"Note that electronic signatures may not be automatically recognized as "
"valid. You may need to bring supporting evidence of a signatures validity."
msgstr ""
#: ../../sign/overview/signature_validity.rst:31
msgid "In the United States of America"
msgstr ""
#: ../../sign/overview/signature_validity.rst:33
msgid ""
"The `ESIGN Act (Electronic Signatures in Global and National Commerce Act) "
"<https://www.fdic.gov/regulations/compliance/manual/10/X-3.1.pdf>`_, at the "
"interstate and international levels, and the `UETA (Uniform Electronic "
"Transactions Act) <https://www.uniformlaws.org/committees/community-"
"home/librarydocuments?communitykey=2c04b76c-2b7d-4399-977e-"
"d5876ba7e034&tab=librarydocuments>`_, at the state level, provide the legal "
"framework for electronic signatures. Note that `Illinois "
"<https://www.ilga.gov/legislation/ilcs/ilcs5.asp?ActID=89&>`_ and `New York "
"<https://its.ny.gov/electronic-signatures-and-records-act-esra>`_ have not "
"adopted the UETA, but similar acts instead."
msgstr ""
#: ../../sign/overview/signature_validity.rst:42
msgid ""
"Overall, to be recognized as valid, electronic signatures have to meet five "
"criteria:"
msgstr ""
#: ../../sign/overview/signature_validity.rst:44
msgid ""
"A signer must show a clear intent to sign. For example, using a mouse to "
"draw a signature can show intent. The signer must also have the option to "
"opt-out of electronically signing a document."
msgstr ""
#: ../../sign/overview/signature_validity.rst:47
msgid ""
"A signer must first express or imply their consent to conduct business "
"electronically."
msgstr ""
#: ../../sign/overview/signature_validity.rst:48
msgid ""
"The signature must be clearly attributed. In Odoo, metadata, such as the "
"signers IP address, is added to the signature, which can be used as "
"supporting evidence."
msgstr ""
#: ../../sign/overview/signature_validity.rst:50
msgid ""
"The signature must be associated with the document being signed, for "
"example, by keeping a record detailing how the signature was captured."
msgstr ""
#: ../../sign/overview/signature_validity.rst:52
msgid ""
"Electronically signed documents need to be retained and available for later "
"reference by all parties involved, for example, by providing the signer "
"either a fully-executed copy or the option to download a copy."
msgstr ""
#: ../../sign/overview/signature_validity.rst:57
msgid ""
"The information provided here does not constitute legal advice; it is "
"provided for general informational purposes only. As laws governing "
"electronic signatures evolve rapidly, we cannot guarantee that the "
"information is up to date. We advise you to should contact a local attorney "
"to obtain legal advice."
msgstr ""
-605
View File
@@ -1,605 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Richard Mathot <rim@odoo.com>, 2020
# Hamid Darabi, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
# Cécile Collart <cco@odoo.com>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-02-04 11:02+0100\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Fernanda Marques <fem@odoo.com>, 2020\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../sms_marketing.rst:5
msgid "SMS Marketing"
msgstr "Marketing par SMS"
#: ../../sms_marketing/overview.rst:3
msgid "Overview"
msgstr "Vue d'ensemble"
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:3
msgid "Contact Lists and Blacklist"
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:5
msgid ""
"Creating your own list of contacts, or importing it, is useful when you want"
" to create specific groups of people, such as the subscribers of your "
"newsletter. It is also the best way to get started if you are coming from "
"another system and already have built an audience. It makes the SMS "
"distribution easier."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:11
msgid "Contact lists"
msgstr "Listes de contact"
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:13
msgid "Go to :menuselection:`Contacts lists --> Contacts lists --> Create`."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:16
msgid ""
"Choose a name for your *Mailing list*, and activate the option *Is Public* "
"if you would like to make the mailing list accessible to your recipients in "
"the unsubscription page (allowing users to update their subscription "
"preferences)."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:22
msgid "History with the Log Notes"
msgstr "L'historique avec les notes du journal de bord "
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:25
msgid ""
"A record of the mailings sent is kept on the recipient's chatter (whether it"
" is a contact or an opportunity, for example)."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:28
msgid ""
"This is important as you and team members can easily keep track and see a "
"history of the interactions with your contacts or prospects. Example: your "
"sales representative can easily find out which SMS mailing promotions a "
"customer has received or not."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:35
msgid "Blacklist"
msgstr "Liste de blocage"
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:38
msgid ""
"If you are coming from another software and have a list of clients who have "
"already asked to be blacklisted, you can import those entries to your "
"database."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:39
msgid ""
"For that, go to :menuselection:`Configuration --> Phone Blacklist --> "
"Import`."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:3
msgid "Integrations and Templates"
msgstr "Intégrations et modèles"
#: ../../sms_marketing/overview/integrations_and_template.rst:5
msgid ""
"Using SMS to reach people can be a strategy not just used for advertisement "
"purposes, but also as a reminder of events or issued invoices to your "
"costumers, for example."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:9
msgid "Campaigns"
msgstr "Campagnes"
#: ../../sms_marketing/overview/integrations_and_template.rst:11
msgid ""
"First, make sure to have the necessary feature activated. Go to the "
":menuselection:`Email Marketing app --> Configuration --> Settings` and "
"enable *Mailing Campaigns*."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:17
msgid ""
"Now, the menu *Campaigns* is also available on the *SMS Marketing* app, "
"allowing you to manage and have an overview of your SMS mailings under "
"campaigns."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:23
msgid ""
"This feature is especially useful if you have aggregated campaigns, as you "
"have a global reporting view. In addition to that, you can create stages in "
"your Kanban view to better organize the work being done."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:31
msgid "Sending SMSs through the Contacts app"
msgstr "Envoyer des SMS via l'application Contacts"
#: ../../sms_marketing/overview/integrations_and_template.rst:34
msgid ""
"Sending SMSs through the contacts form is available by default in Odoo. It "
"makes your work easier if you need to send an SMS to a specific contact, for"
" example."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:36
msgid ""
"For that, go to the *Contacts* app, select the contact and click on the "
"*SMS* icon next to the phone number."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:41
msgid ""
"If you would like to send a message to multiple contacts at once, choose the"
" *List View*, select all the contacts needed, and under *Action* select "
"*Send SMS*."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:48
msgid "Set up SMS templates"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:50
msgid ""
"To set up *SMS Templates*, activate the :doc:`Developer mode "
"<../../general/developer_mode/activate>`, then go to "
":menuselection:`Technical --> SMS Templates`."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:60
msgid ""
"Use *Dynamic Placeholders* to adapt automatically the content of the SMS to "
"the context."
msgstr ""
"Utilisez des *espaces réserves* pour adapter automatiquement le contenu du "
"SMS au contexte."
#: ../../sms_marketing/overview/integrations_and_template.rst:63
msgid "SMS Text Messaging is available throughout Odoo:"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:65
msgid "*CRM*: send SMSs to your leads and opportunities."
msgstr "*CRM*: envoyez des SMS à vos pistes et opportunités."
#: ../../sms_marketing/overview/integrations_and_template.rst:66
msgid "*Subscription*: alert customers about their subscription."
msgstr "*Abonnement* : prévenez les clients sur leur abonnement."
#: ../../sms_marketing/overview/integrations_and_template.rst:67
msgid "*Accounting*: send payment reminders."
msgstr "*Comptabilité* : envoyer des rappels de paiement."
#: ../../sms_marketing/overview/integrations_and_template.rst:68
msgid "*Marketing Automation*: automate your SMS marketing campaigns."
msgstr ""
"*Automatisation du marketing* : automatisez vos campagnes de marketing SMS."
#: ../../sms_marketing/overview/integrations_and_template.rst:69
msgid ""
"*Inventory*: send an automatic confirmation when a delivery order is done."
msgstr ""
"*Inventaire* : envoyez une confirmation automatique lorsque un bon de "
"livraison est généré. "
#: ../../sms_marketing/overview/integrations_and_template.rst:70
msgid ""
"*Sign*: receive a validation code to verify your identity before signing a "
"document online."
msgstr ""
"*Signer* : recevez un code de validation pour vérifier votre identité avant "
"de signer un document en ligne."
#: ../../sms_marketing/overview/integrations_and_template.rst:71
msgid ""
"*SEPA debit payment provider*: send a verification code to your customers."
msgstr ""
"*Le fournisseur de prélèvement automatique SEPA* : envoie un code de "
"vérification à vos clients."
#: ../../sms_marketing/overview/integrations_and_template.rst:72
msgid ""
"*Studio*: send an SMS according to your needs by using automated actions."
msgstr ""
"*Studio* : envoie un SMS en fonction de vos besoins via des actions "
"automatisées."
#: ../../sms_marketing/overview/integrations_and_template.rst:75
msgid ""
"For more information about SMS integrations in Odoo and a list of frequently"
" asked questions, go to :doc:`../pricing/pricing_and_faq`."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:79
msgid ":doc:`../../social_marketing/overview/campaigns`"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:80
msgid ":doc:`../../discuss/advanced/email_template`"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:3
msgid "Build, Send and Get Reports from a SMS Mailing"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:5
msgid ""
"Using SMS Marketing as part of your communication strategies can empower you"
" to expand your markets, considering that in some countries emails are not "
"very used or used at all. It also helps to boost conversion rates, as this "
"strategy has a high open-rate percentage among people who use smartphones."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:11
msgid "Get started"
msgstr "Démarrer"
#: ../../sms_marketing/overview/sms_mailing_reports.rst:13
msgid "Go to :menuselection:`SMS Marketing --> Create`."
msgstr "Allez à :menuselection:`Marketing SMS --> Créer`."
#: ../../sms_marketing/overview/sms_mailing_reports.rst:18
msgid ""
"Specify a *subject* name to help you remembering what the mailing is about."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:20
msgid ""
"Under *Recipients*, choose to whom you would like the SMS to be sent. If you"
" choose *Contact*, all your Odoo contacts (vendor, customers, etc.) receive "
"your SMS."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:22
msgid ""
"From there, you can refine your recipient list with the *add filter* option."
" In the example below, the message would be sent to the contacts living in "
"Belgium."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:27
msgid ""
"The *Mailing list* option, on the other hand, allows you to choose the "
"specific mailing lists you created to group specific contacts. You are "
"allowed to select multiple ones."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:34
msgid ""
"Under the *SMS Content* tab, links can be included and Odoo automatically "
"generates *link trackers* in order to generate data about these links."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:36
msgid ""
"Under *Settings* you have the option *Include opt-out link*. If activated, "
"the contact is able to unsubscribe from the mailing list."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:43
msgid ""
"In the *Link Tracker* menu under *Configuration*, you can see the history of"
" your sent links, access them and look at statistics."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:50
msgid "Double-check that you have the phone number of your contacts saved."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:53
msgid "Send a mailing"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:57
msgid ""
"Once you have your mailing created, you must choose when you would like it "
"to be delivered:"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:59
msgid ""
"*Put in Queue*: the mailing is triggered with the next automatic run. "
"Interesting option if you do not need the message to be sent at a specific "
"time."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:61
msgid ""
"*Send Now*: sends the message immediately. Use this option if the recipient "
"list is not excessive."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:62
msgid ""
"*Schedule*: allows you to choose a day and time. Best option for mailings "
"that you would like to send during a specific event, to promote an offer "
"while it is active, or to simply plan your content strategy in advance."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:65
msgid ""
"*Test*: allows you to send an SMS to one or multiple numbers for test "
"purposes. Check, for example, if the link provided lands on the right page "
"while making sure they are responsive. If sending it to multiple numbers, "
"you must remember to use a comma between them."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:70
msgid "Visualize reports"
msgstr "Visualisez vos rapports"
#: ../../sms_marketing/overview/sms_mailing_reports.rst:72
msgid ""
"Under the *Reporting* menu apply filters, measures, and adopt different "
"layouts to do analyses of the performance of your SMS mailings."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:79
msgid ""
"You can also check the price to send an SMS for your country by clicking on "
"the *Information* icon."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:86
msgid ""
"**Buy Credits:** in order to take advantage of the app and its features, "
"make sure you have purchased credits. For more information: "
":doc:`../pricing/pricing_and_faq`."
msgstr ""
#: ../../sms_marketing/pricing.rst:3
msgid "Pricing and FAQ"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:3
msgid "SMS Pricing and FAQ"
msgstr "Tarification SMS et FAQ"
#: ../../sms_marketing/pricing/pricing_and_faq.rst:6
msgid "What do I need to send SMSs?"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:7
msgid ""
"SMS Text Messaging is an In-App Purchase (IAP) service that *requires "
"prepaid credits* to work."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:11
msgid "How many types of SMSs are there?"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:12
msgid "There are 2 types: GSM7 and UNICODE."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:14
msgid ""
"**GSM7** is the standard format, with a limit of 160 characters per message,"
" that includes the following characters:"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:23
msgid ""
"**UNICODE** is the format applied if a special character, that *is not* in "
"the GSM7 list, is used. Limit per SMS: 70 characters."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:27
msgid ""
"For GSM7 SMS the size limit is 160 characters, and for Unicode is 70. *Above"
" these limits, the content is divided into a multi-part message* and the "
"limit of characters is lowered to 153 for GSM7 and to 67 for Unicode. The "
"system will inform you in real-time about the number of SMS your message "
"represents."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:34
msgid "How much does it cost to send an SMS?"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:35
msgid ""
"The price of an SMS depends on the destination and the length (number of "
"characters) of the message."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:37
msgid ""
"To see the **price per country, please consult**: `Odoo SMS - FAQ <https"
"://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:39
msgid ""
"The number of SMSs a message represents will be always available to you in "
"your database."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:49
msgid "How do I buy credits?"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:50
msgid "Go to :menuselection:`Settings --> Buy Credits`."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:57
msgid "Or go to :menuselection:`Settings --> View my Services`."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:65
msgid ""
"If you are on Odoo Online (SAAS) and have the Enterprise version, you "
"benefit from free trial credits to test the feature."
msgstr ""
"Si vous êtes sur Odoo Online (SAAS) et disposez de la version Entreprise, "
"vous bénéficiez de crédits d'essai gratuits pour tester cette "
"fonctionnalité."
#: ../../sms_marketing/pricing/pricing_and_faq.rst:70
msgid "More common questions"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:72
msgid "**Is there an expiration time for my credits?**"
msgstr "**Est-ce que mes crédits expirent-ils?**"
#: ../../sms_marketing/pricing/pricing_and_faq.rst:74
msgid "No, credits do not expire."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:77
msgid ""
"**Can I send an SMS to a phone number (which is not a mobile phone) because "
"I see the icon in front of the field “phone”?**"
msgstr ""
"**Puis-je envoyer un SMS vers un numéro (qui n'est pas un mobile) parce que "
"je vois l'icône devant le champ “téléphone”?**"
#: ../../sms_marketing/pricing/pricing_and_faq.rst:80
msgid "Only if that phone number supports SMS (e.g. SIP phones)."
msgstr ""
"Uniquement si ce numéro de téléphone prend en charge les SMS (par ex. les "
"téléphones SIP)."
#: ../../sms_marketing/pricing/pricing_and_faq.rst:83
msgid "**Do I receive an invoice to buy my credits?**"
msgstr "**Est-ce que je reçois une facture pour acheter mes crédits?**"
#: ../../sms_marketing/pricing/pricing_and_faq.rst:85
msgid "Yes."
msgstr "Oui."
#: ../../sms_marketing/pricing/pricing_and_faq.rst:88
msgid "**Can the recipient answer to me?**"
msgstr "**Le destinataire peut-il me répondre?**"
#: ../../sms_marketing/pricing/pricing_and_faq.rst:90
msgid "No, it is not possible to reply to the SMS."
msgstr "Non, il est impossible de répondre à un SMS."
#: ../../sms_marketing/pricing/pricing_and_faq.rst:93
msgid ""
"**What happens if I send multiple SMS but I do not have enough credits to "
"send them all?**"
msgstr ""
"**Que se passe-t-il si je veux envoyer des SMS multiples mais que je n'ai "
"pas suffisament de crédits?**"
#: ../../sms_marketing/pricing/pricing_and_faq.rst:95
msgid ""
"The whole transaction is counted as a single one, so no SMS will be sent "
"until you have enough credits to send them all."
msgstr ""
"L'ensemble de la transaction est compté comme une seule, de sorte qu'aucun "
"SMS ne sera envoyé tant que vous n'aurez pas suffisamment de crédits pour "
"les envoyer tous."
#: ../../sms_marketing/pricing/pricing_and_faq.rst:99
msgid "**Do I have a history of the sent SMSs?**"
msgstr "**Ai-je un historique des SMS envoyés?**"
#: ../../sms_marketing/pricing/pricing_and_faq.rst:101
msgid ""
"Yes, the SMS is logged as a note under the chatter of the corresponding "
"record, and a complete history of the SMSs sent is available on "
":doc:`Developer mode <../../general/developer_mode/activate>` under "
":menuselection:`Technical --> SMS`."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:107
msgid "**Can I send as many SMSs I want at once?**"
msgstr "**Puis-je envoyer autant de SMS que je veux en une fois?**"
#: ../../sms_marketing/pricing/pricing_and_faq.rst:109
msgid "Yes, if you have enough credits."
msgstr "Oui, si vous avez suffisamment de crédits."
#: ../../sms_marketing/pricing/pricing_and_faq.rst:112
msgid ""
"**If I have a number that does not exist in the list of recipients, will I "
"lose credits?**"
msgstr ""
"**Est-ce que je perds des crédits si j'ai un numéro qui n'est pas dans la "
"liste des destinataires?**"
#: ../../sms_marketing/pricing/pricing_and_faq.rst:114
msgid ""
"Not if the phone number is in the wrong format (e.g. too many digits). "
"Otherwise, if the SMS is sent to the wrong person or to a fake number, the "
"credit will be lost."
msgstr ""
"Non, si le numéro de téléphone n'est pas dans le bon format (par ex. trop de"
" chiffres). Autrement, si le SMS est envoyé à la mauvaise personne ou à un "
"faux numéro, votre crédit sera débité."
#: ../../sms_marketing/pricing/pricing_and_faq.rst:118
msgid ""
"**What happens if I send my SMS to a paying number (e.g.: a contest to win a"
" ticket for a festival)?**"
msgstr ""
"**Que se passe-t-il si j'envoie un SMS à un numéro payant (par ex.: un "
"concours pour gagner un ticket pour un festival)?**"
#: ../../sms_marketing/pricing/pricing_and_faq.rst:120
msgid ""
"The SMS will not be delivered to that kind of number, so you wont be "
"charged."
msgstr ""
"Les SMS ne sont pas envoyés à ce type de numéro, vous ne serez donc pas "
"débité."
#: ../../sms_marketing/pricing/pricing_and_faq.rst:123
msgid ""
"**Can I identify the numbers that do not exist when I send several SMSs?**"
msgstr ""
"**Puis-je identifier les numéros inexistant lorsque j'envoie plusieurs "
"SMS?**"
#: ../../sms_marketing/pricing/pricing_and_faq.rst:125
msgid "Only the ones that have an invalid format."
msgstr "Uniquement ceux qui ont un format invalide."
#: ../../sms_marketing/pricing/pricing_and_faq.rst:128
msgid "**How does the GDPR regulation affect this service?**"
msgstr "**Comment le règlement RGPD affect-il ce service?**"
#: ../../sms_marketing/pricing/pricing_and_faq.rst:130
msgid ""
"Please find our `Privacy Policy here <https://iap.odoo.com/privacy#sms>`__."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:132
msgid "**Can I use my own SMS provider?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:134
msgid ""
"Yes, but it is not possible out of the box. Our experts can help you "
"customize your database to make it happen. Please, check our success packs "
"`here <https://www.odoo.com/pricing-packs>`_."
msgstr ""
-362
View File
@@ -1,362 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
# Cécile Collart <cco@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:42+0000\n"
"Last-Translator: Cécile Collart <cco@odoo.com>, 2020\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../social_marketing.rst:5
msgid "Social Marketing"
msgstr "Marketing social"
#: ../../social_marketing/overview.rst:3
msgid "Overview"
msgstr "Vue d'ensemble"
#: ../../social_marketing/overview/campaigns.rst:3
msgid "Connecting to my Marketplace with Campaigns"
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:5
msgid ""
"Whether your goal is to sell a new product, explain the value of your "
"services or advertise your event, a campaign helps you to connect with your "
"marketplace. They normally involve multiple channels, so it is fundamental "
"to have a solution with which you can plan, execute, track, and analyze your"
" content."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:10
msgid "Go to :menuselection:`Social Marketing --> Campaigns --> Create`."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:16
msgid ""
"As you create content, tabs for that specific channel are shown. The "
"overview of the campaign displays global metrics such as:"
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:19
msgid ""
"*Revenue*: number of users who, from a link in your content, finished a "
"transaction (paid)."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:20
msgid ""
"*Quotations*: number of users who, from a link in your content, have started"
" but not finished a transaction (did not pay)."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:22
msgid ""
"*Leads*: users who have filled out your contact form, from a link in your "
"content."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:25
msgid ""
"To be able to *Send New Mailing*, make sure the feature is enabled in the "
"*Email Marketing* application, under :menuselection:`Email Marketing --> "
"Configuration --> Settings`. To be able to *Send SMS*, the *SMS Marketing* "
"application must be installed on your database."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:30
msgid ""
"*Social Marketing* works integrated with other applications such as *Sales*,"
" *Invoicing*, *CRM* and *Website*."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:34
#: ../../social_marketing/overview/manage_social.rst:77
msgid ":doc:`./push_notifications`"
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:35
#: ../../social_marketing/overview/push_notifications.rst:66
msgid ":doc:`./manage_social`"
msgstr ""
#: ../../social_marketing/overview/livechat.rst:3
msgid "Interact with Customers and Visitors with Live Chat"
msgstr ""
#: ../../social_marketing/overview/livechat.rst:5
msgid ""
"One of the ways you can build stronger relationships with your customers is "
"by making yourself available through live chat. Live chats can have a big "
"impact not just on your customer service, but also on sales performance, as "
"it gives users a chance of having real-time, fast, and effective "
"interaction."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:11
msgid "Configuration"
msgstr "Configuration"
#: ../../social_marketing/overview/livechat.rst:13
msgid ""
"Go to :menuselection:`Website --> Configuration --> Settings --> Live Chat` "
"select the appropriate channel, and set it up."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:20
msgid ""
"Under *Channel Rules*, choose when the chat pop-up appears, and an action "
"for a given URL and/or country. Note that to take the country into account, "
"GeoIP must be installed on your server."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:24
msgid "The *Live Chat* application must be installed on your database."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:27
msgid "Monitor your visitors"
msgstr ""
#: ../../social_marketing/overview/livechat.rst:29
msgid ""
"Under the *Visitors* menu, see the visitors that landed on one of your "
":ref:`social_marketing/website_tracked_pages` online or offline."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:34
msgid ""
"You can send emails (if an email address has been saved), send SMSs (if a "
"phone number has been saved), send a push notification (if the user has "
"subscribed to it), and even send a live chat request that will be received "
"by the user once they move to a tracked page."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:36
msgid ""
"Open a record to see details including the visited pages, and the first and "
"last date and time the user was connected."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:43
msgid ""
"Your online visitors will be authenticated if they are linked to a lead or "
"an existing partner."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:44
msgid ""
"If you do not use the *Website* app, you can add a live chat widget to your "
"own website."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:49
msgid "Websites tracked pages"
msgstr ""
#: ../../social_marketing/overview/livechat.rst:51
msgid ""
"To define which pages are tracked, on the *Website* application, go to "
":menuselection:`Website --> Configuration --> Pages` and enable the option "
"*Track*, on the respective pages."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:60
msgid ":doc:`../../livechat/overview/get_started`"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:3
msgid "Manage Social Media Pages and Create Content"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:5
msgid ""
"Once you are present on social media platforms, it is important to keep them"
" up-to-date. However, that might feel like a full-time job. Having a "
"solution that allows you to create, schedule, keep track, engage with your "
"audience and measure results saves you time and helps you to successfully "
"execute your online strategy, from posts to results."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:12
msgid "Add accounts and create your feed"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:14
msgid ""
"Click on *Add Stream* and grant the required permissions to add your "
"accounts."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:21
msgid "You can link a Facebook page for which you are the admin."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:23
msgid ""
"You are then redirected to your *Feed* and a column with the publications is"
" automatically added."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:25
msgid ""
"You can then add new accounts and/or streams, such as Facebook mentions, and"
" customize your Kanban view."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:31
msgid ""
"Adding social media accounts to your feed will also link KPIs. To get "
"redirected to the statistics page of the social account, click on "
"*Insights*."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:39
msgid "Link a LinkedIn account"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:41
msgid ""
"Go to :menuselection:`Social Marketing --> Configuration --> Social Media`."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:48
msgid ""
"LinkedIn is in Beta Version, therefore, the feed is not available. Only the "
"creation of content."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:51
msgid "Publish content"
msgstr "Publiez du contenu"
#: ../../social_marketing/overview/manage_social.rst:53
msgid ""
"Click on :menuselection:`Social Marketing --> Feed --> New Post`, or go to "
":menuselection:`Social Marketing --> Posts → Create`."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:60
msgid "Choose to upload your post right away or to schedule it."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:61
msgid "Saving your post will apply a draft status to it."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:64
msgid "Overview and plan your posts with a calendar view"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:67
msgid ""
"Through the calendar view, besides having an overview of your planned day, "
"week or month, also see your drafted, scheduled and published posts."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:68
msgid "Drag and drop (scheduled posts) to change their scheduled date."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:70
msgid ""
"Double-click on a date to create a post directly from the *Calendar view*, "
"and click on an existing one to edit it."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:78
#: ../../social_marketing/overview/push_notifications.rst:67
msgid ":doc:`./campaigns`"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:79
msgid ":doc:`./livechat`"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:3
msgid "Use Web Push Notifications"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:5
msgid ""
"Web Push Notifications deliver messages to your users device without the "
"need to be on your website, or for them to give personal information. They "
"can be used to inform your users about news, articles and content posted, "
"practical messages like traffic and weather updates, flight information, "
"sales alerts, coupons, and product updates."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:11
msgid "Ask users for permission"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:13
msgid ""
"In the *Website* application go to :menuselection:`Website --> Configuration"
" --> Settings` and enable *Web Push Notifications*."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:20
msgid ""
"Choose your message, icon, and delay time (which is the wait time for the "
"permission request to be shown once the user lands on your page)."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:28
msgid "Send notifications"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:31
msgid "Individually"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:33
msgid "You can send individual messages through the menu *Visitors*."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:40
msgid "To a group"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:42
msgid ""
"Target a bigger segment by selecting multiple visitors in the *View List* "
"(e.g.: all visitors that visited your Homepage)."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:50
msgid ""
"Visitors records are kept under *Visitors* for a week, before getting "
"archived."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:53
msgid "By rules"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:55
msgid ""
"Or go to :menuselection:`Social Marketing --> Posts --> Create`. Under *Web "
"Notification options*, apply filters to send your message to the records "
"that match the rules you set."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:63
msgid "The feature only works with Odoo Website application."
msgstr ""
-941
View File
@@ -1,941 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# fr trans <e2ffr05@hotmail.com>, 2020
# Martin Trigaux, 2020
# 5cad1b0f1319985f8413d48b70c3c192_b038c35, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-11-02 12:05+0100\n"
"PO-Revision-Date: 2020-09-22 14:42+0000\n"
"Last-Translator: Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../studio.rst:5
msgid "Studio"
msgstr "Studio"
#: ../../studio/concepts.rst:3
msgid "Concepts"
msgstr "Concepts"
#: ../../studio/concepts/understanding_automated_actions.rst:3
msgid "Understanding Automated Actions"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:6
msgid ""
"Automated actions are used to trigger actions. They are based on conditions "
"and happen on top of Odoos default business logic."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:9
msgid ""
"Examples of automated actions include: creating a next activity upon a "
"quote's confirmation; adding a user as a follower of a confirmed invoice if "
"its total is higher than a certain amount; or preventing a lead from "
"changing stage if a field is not filled in."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:16
msgid ""
"Let's understand how to properly define *when* an automated action runs and "
"*how* to create one:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:18
msgid ""
"The first step is to choose the :doc:`Model <understanding_general>` on "
"which the action is applied."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:19
msgid ""
"The **Trigger** field defines the event that causes the automated action to "
"happen:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:21
msgid ""
"*On Creation*: when a new record is created. Note that the record is created"
" once saved for the first time."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:23
msgid ""
"*On Update*: when the record is updated. Note that the update happens once "
"the record is saved."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:24
msgid ""
"*On Creation & Update*: on the creation and/or on the update of a record "
"once the form is saved."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:25
msgid "*On Deletion*: on the removal of a record under the condition set."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:26
msgid ""
"*Based on Form Modification*: when the value of the specified *Trigger* "
"field is changed in the interface (user sees the changes before saving the "
"record). Note that this action can only be used with the *Execute Python "
"Code* action type."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:29
msgid ""
"*Based on Timed Condition*: a delay happens after a specific date/time. Set "
"a *Delay after trigger date* if you need a delay to happen before the "
"*Trigger Date*. Example: to send a reminder 15min before a meeting. If the "
"date/time is not set on the form of the model chosen, the date/time "
"considered is the one of the creation/update of the record."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:34
msgid "For every Trigger option, **conditions** can be applied, such as:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:36
msgid ""
"*Before Update Domain*: if designated, this condition must be satisfied "
"before the record is updated."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:38
msgid ""
"*Apply on*: if designated, this condition must be satisfied before executing"
" the action rule (*Action To Do*), and after the update."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:41
msgid ""
"The **Active** option is to be turned off when the rule should be hidden and"
" not executed."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:43
msgid ""
"Under **Action To Do** choose the type of server action that must be "
"executed once records meet the *Trigger* conditions:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:45
msgid ""
"*Execute Python Code*: a block of code is executed. A *Help* tab with the "
"variables that can be used is available."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:47
msgid "*Create New Record*: a new record with new values is created."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:48
msgid "*Update a Record*: updates the record that triggered the action."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:49
msgid ""
"*Execute several actions*: defines an action that triggers other server "
"actions."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:50
msgid ""
"*Send Email*: an automatic :doc:`email "
"<../../discuss/advanced/email_template>` is sent."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:51
msgid "*Add Followers*: followers are notified of changes in the task."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:52
msgid ""
"*Create Next Activity*: creates an activity such as: *Call*, *Email*, "
"*Reminder*."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:53
msgid ""
"*Send SMS Text Message*: sends an :doc:`SMS "
"<../../sms_marketing/pricing/pricing_and_faq>`."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:56
msgid "Example"
msgstr "Exemple"
#: ../../studio/concepts/understanding_automated_actions.rst:58
msgid ""
"This is the process of which the update of the *Email* field on the "
"Lead/Opportunity *Model*, with a *Trigger Condition* set to *On Update*, "
"goes through:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:65
msgid "The user creates the record without an email address set."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:66
msgid "The user updates the record defining an email address."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:67
msgid ""
"Once the change is saved, the automation checks if any of the *Watched "
"Fields* are being updated (for the example: field name *email_from* (Email)."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:69
msgid ""
"If true, it checks if the record matches the *Before Update Domain* (for the"
" example: *email is not set*)."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:71
msgid ""
"If true, it checks (*after the update*) whether the record matches the "
"*Apply on* domain (for the example: *email is set*)."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:73
msgid "If true, the chosen *Action To Do* is performed on the record."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:76
msgid ":doc:`understanding_general`"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:77
msgid ":doc:`../use_cases/automated_actions`"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:3
msgid "Understanding General Concepts"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:7
msgid ""
"Odoo Studio is a toolbox that allows you to add models or adapt "
"functionalities on top of Odoos standard behavior without coding knowledge."
" You can also create custom views and modify existing ones without having to"
" get into the XML code."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:11
msgid ""
"Even for experienced developers, typing out code requires time. By using "
"Odoo Studio, you can quickly get your models up and going and focus on the "
"crucial parts of your application. The result is a user-friendly solution "
"that makes customizations and designing new applications easy with or "
"without programming skills."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:15
msgid "Getting started"
msgstr "Commencer"
#: ../../studio/concepts/understanding_general.rst:17
msgid ""
"One you start using Odoo Studio, you automatically create a new *module* "
"that contains all your modifications. These modifications can be done on "
"existing screens (*views*), by adding new *fields* in existing applications,"
" or by creating an entirely new *model*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:22
msgid "What is a Module?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:25
msgid ""
"An Odoo **Module** can contain a number of elements, such as: business "
"objects (models), object views, data files, web controllers, and static web "
"data. An application is a collection of modules."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:29
msgid ""
"In object-oriented programming, models usually represent a concept from the "
"real world. Example: Odoo has models for Sales Orders, Users, Countries, "
"etc. If you were to build an application to manage Real Estate sales, a "
"model that represents the Properties for sale would probably be your first "
"step."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:38
msgid "What is a Model (also called Object)?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:40
msgid ""
"A **Model** determines the logical structure of a database and fundamentally"
" determines in which manner data can be stored, organized, and manipulated. "
"In other words, a model is a table of information that can be bridged with "
"other tables."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:45
msgid "What are Fields?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:47
msgid ""
"**Fields** compose models. It is where a record (a piece of data) is "
"registered."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:49
msgid ""
"Example: on the Real Estate application, fields on the Properties model "
"would include the price, address, a picture, a link to the current owner, "
"etc."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:50
msgid ""
"There are 2 main types of fields in Odoo: *basic (or scalar) fields* and "
"*relational fields*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:53
msgid ""
"Basic fields represent simple values, like numbers or text. Relational "
"fields represent relations between models. So, if you have a model for "
"*Customers* and another one for *Properties*, you would use a relational "
"field to link each Property to its Customer."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:56
msgid "Relational Fields in detail"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:59
msgid ""
"**Relational Fields** provide the option to link the data of one model with "
"the data of another model."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:60
msgid ""
"In Odoo, relational field types are: *One2many*, *Many2one*, *Many2many*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:66
msgid ""
"An **One2many** field is a *one-way* direction of selecting *multiple* "
"records from a table."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:68
msgid ""
"Example: a Sales Order can contain multiple Sales Order Lines, which also "
"contain multiple fields of information."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:69
msgid ""
"A **Many2one** field is a *one-way* direction of selecting *one* record from"
" a table."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:70
msgid ""
"Example: you can have many product categories, but each product can only "
"belong to one category."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:71
msgid ""
"A **Many2many** field is a *two-way* direction of selecting records from a "
"table."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:72
msgid "Example: multiple tags can be added to a leads form."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:75
msgid "An *One2many* field must have a *Many2one* related to it."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:78
msgid "What are Views?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:80
msgid ""
"**Views** define how records are displayed. They are specified in XML which "
"means that they can be edited independently from the models that they "
"represent. There are various types of views in Odoo, and each of them "
"represents a mode of visualization. Some examples are: *form*, *list*, "
"*kanban*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:85
msgid "What is a Menu?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:87
msgid ""
"A **Menu** is a button that executes and action. In Odoo Studio, to create "
"menus (models) and rearrange their hierarchy, click on *Edit Menu*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:95
msgid "`Studio Basics <https://www.odoo.com/fr_FR/slides/studio-31>`_"
msgstr ""
#: ../../studio/how_to.rst:3
msgid "How To"
msgstr ""
#: ../../studio/how_to/export_import.rst:3
msgid "Export and Import Modules"
msgstr ""
#: ../../studio/how_to/export_import.rst:5
msgid ""
"When you do customizations in Odoo Studio, a new module is created in your "
"database, making it easy to use Studio for prototyping."
msgstr ""
#: ../../studio/how_to/export_import.rst:8
msgid ""
"To export these customizations, activate Studio on the main dashboard and, "
"under the menu *Customizations*, click on *Export*. The default filename is "
"*customizations.zip*."
msgstr ""
#: ../../studio/how_to/export_import.rst:16
msgid ""
"The module created contains the definition of custom models and fields, as "
"well as the UI elements of any customization in an XML format."
msgstr ""
#: ../../studio/how_to/export_import.rst:18
msgid ""
"To import and install the customizations in another instance, connect to the"
" destination database, activate Studio and, under *Customizations*, click on"
" *Import*."
msgstr ""
#: ../../studio/how_to/export_import.rst:25
msgid ""
"Studio does not know which apps are customized (because the same view can be"
" modified on different apps), therefore, it *does not* add the underlying "
"modules as dependencies of the exported module. In other words, the "
"applications installed on the source database should be installed on the "
"destination database."
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:3
msgid "Customizing the Rainbow Man"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:5
msgid ""
"The Rainbow Man in Odoo is an animation shown once the user completes "
"certain tasks and clicks on certain buttons. It is a way to make the "
"software fun to use, and rewarding, for employees."
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:13
msgid ""
"On most buttons in Odoo, such as *Send by Email*, *Confirm* or *Cancel*, "
"once they are selected in Studio, under their *Properties*, the *Rainbow "
"Man* effect can be applied."
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:14
msgid "By default, the feature is active:"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:16
msgid "when opportunities are marked as won;"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:17
msgid "when users empty their inboxes;"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:18
msgid "when the user finishes a tour;"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:19
msgid "when the user finishes doing reconciliations."
msgstr ""
#: ../../studio/how_to/reports.rst:3
msgid "Customizing Reports"
msgstr ""
#: ../../studio/how_to/reports.rst:9
msgid ""
"Odoo uses HTML and CSS technologies to create reports. HTML is a markup "
"language that uses tags, also called elements. It is the core of any webpage"
" because it provides its basic structure. CSS interacts with HTML elements "
"to add style to the page, establishing how the HTML is shown to the user. "
"Odoos reports also use Bootstraps grid layout, which is the containers, "
"rows, and columns to align content, and support Odoo's website themes."
msgstr ""
#: ../../studio/how_to/reports.rst:11
msgid ""
"When creating a new report, choose the purpose of it and if you would like "
"the report to include header and footer (company logo, name, address, phone,"
" email address, etc.)."
msgstr ""
#: ../../studio/how_to/reports.rst:17
msgid ""
"Under the tab **Add**, you find the fields to be dragged and dropped to the "
"view. *Fields*, *Data tables*, *Subtotal & Total*, and *Address Book* are "
"dynamic elements (meaning that they need a :doc:`one2many or a many2many "
"<../concepts/understanding_general>` related object). *Text*, *Title Block*,"
" *Image*, and *Text in Cell* are static elements."
msgstr ""
#: ../../studio/how_to/reports.rst:26
msgid ""
"Once the element is added to the view, select it to see its **Options**. The"
" first section shows the hierarchy of the selected object and its "
"properties, allowing you to individually edit them. Fields with related "
"objects have their directives shown on *Field Expression*."
msgstr ""
#: ../../studio/how_to/reports.rst:34
msgid ""
"Under **Visible if**, define the rule(s) to set visibility conditions to "
"fields."
msgstr ""
#: ../../studio/how_to/reports.rst:36
msgid ""
"Example: if choosing to display a product image, you could set a visibility "
"rule to only display the ones that are *set* in the product form, avoiding "
"having a plain icon when they are not set."
msgstr ""
#: ../../studio/how_to/reports.rst:40
msgid ""
"**Visible for** is used to set which :doc:`groups "
"<../../general/odoo_basics/add_user>` can have access to specific elements "
"in the report. **Limit visibility to groups**, under *Report*, sets the "
"visibility of the report to specifics groups, meaning that users belonging "
"to other groups do not see the same final document."
msgstr ""
#: ../../studio/how_to/reports.rst:46
msgid ""
"Under the **Report** tab, name your report, choose the paper format, and if "
"the report should be added to the *Print* menu list on its respective "
"document form."
msgstr ""
#: ../../studio/how_to/reports.rst:53
msgid ""
"If activating the :doc:`Developer mode "
"<../../general/developer_mode/activate>`, additional fields such as *Class* "
"under *Options*, and *Reload from attachment* under *Report*, become "
"visible."
msgstr ""
#: ../../studio/how_to/reports.rst:56
msgid ""
"*Class*: add custom CSS classes to the selected element (e.g. Bootstrap "
"classes such as *text-danger*)."
msgstr ""
#: ../../studio/how_to/reports.rst:59
msgid ""
"*Reload from attachment*: saves the report as an attachment of the document "
"when printed. When the report is reprinted, it re-downloads that attachment "
"instead of re-printing it. This means that if the underlying record (e.g. "
"Invoice) changes when compared to the first impression, the report does not "
"reflect the changes because they were done after the attachment was created."
" This is typically useful for reports linked to documents that should not "
"change, such as Invoices."
msgstr ""
#: ../../studio/how_to/reports.rst:67
msgid ""
"Actions in Odoo Studio can be undone until you *Close* the toolbox. Once you"
" have closed Studio, changes can not be undone anymore."
msgstr ""
#: ../../studio/use_cases.rst:3
msgid "Use Cases"
msgstr "Cas d'utilisation"
#: ../../studio/use_cases/automated_actions.rst:3
msgid "Advanced Use Cases: Automated Actions"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:5
msgid ""
"**Case scenario 1: when a Belgian lead is created, a 3-stars priority should"
" be automatically applied.**"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:8
msgid "Under *Automations*, click on *Create* and set the following rules:"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:10
msgid "*Model*: Lead/Opportunity"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:11
msgid "*Active*: On"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:12
msgid "*Trigger*: On Creation & Update"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:13
msgid "*Apply on*: Country > Country Name = Belgium"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:14
#: ../../studio/use_cases/filters_status_bar.rst:53
msgid "*Action To Do*: Update the Record"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:15
msgid "*Data to Write*: Lead/Opportunity > Value > 3"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:22
msgid ""
"Check :doc:`this doc <filters_status_bar>` in order to have another "
"automated action example."
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:25
msgid ":doc:`../concepts/understanding_automated_actions`"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:26
#: ../../studio/use_cases/filters_status_bar.rst:61
#: ../../studio/use_cases/models_fields.rst:138
#: ../../studio/use_cases/views.rst:28
msgid ":doc:`../concepts/understanding_general`"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:3
msgid "Advanced Use Cases: Filters and Status Bar"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:5
msgid ""
"**Case scenario 1: on Sales, set a filter on Belgian customers and define it"
" as the default one (the user should still be able to unset the filter).**"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:8
msgid ""
"On your customers page, use *Filters* > *Add Custom Filter* to group "
"customers by country. Now, under *Favorites*, *Save Current Search* enabling"
" *Use by default* and *Save*."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:15
msgid ""
"On *Filter Rules* in Studio mode, select the respective filter and enable "
"*Default Filter*."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:21
msgid ""
"**Case scenario 2: add a status bar on the product form to manage its life "
"cycle. Set the values: Prototype, In use and Deprecated. By default, "
"the Kanban view must be grouped by status.**"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:26
msgid ""
"On your product form, *Add a pipeline status bar* and name its values. "
"Status bars are *selection* fields that give you the ability to follow a "
"specific flow. They are useful to show you the progress that has been made."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:28
msgid ""
"On the *Views* menu, access *Kanban* and, under its *View* options, set the "
"*Default Group by* as *Pipeline status bar*."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:34
msgid ""
"Now, open your product form and set the right status for that product. As "
"you move products throughout stages (also through the products form), "
"stages are shown in the Kanban view."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:38
msgid ""
"To make modifications in the pipeline status bar, for example, remember to "
"go back to *Form View*."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:44
msgid ""
"**Case scenario 2.a: when a product goes from In use to Deprecate, set "
"its cost to 0€.**"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:46
msgid ""
"Create an :doc:`automated action "
"<../concepts/understanding_automated_actions>` with the selected values:"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:49
msgid "*Model*: Product Template"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:50
msgid "*Trigger*: On Update"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:51
msgid "*First Domain*: Pipeline status bar = In use"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:52
msgid "*Second Domain*: Pipeline status bar = Deprecated"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:54
msgid "*Data to Write*: Cost (Product Template) > Value > 0"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:3
msgid "Advanced Use Cases: Creating Models and Adding Fields"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:5
msgid ""
"**Case scenario 1: on the leads form, if the chosen country is France, show"
" a field 'Pay by check?'**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:8
msgid ""
"On your leads form, add a *Related Field* to *Country > Country Name*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:10
msgid ""
"Now, add a *Checkbox* field and define its invisibility options as *Country*"
" (carefully select the one just created) *> is not = > France.*"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:11
msgid "You can now hide the related field created (*Country*) if you wish."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:19
msgid ""
"Another approach is to use the countrys ID. To do so, go to "
":menuselection:`Contacts --> Configuration --> Countries`, select France "
"(for example), and on the URL check its *ID*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:21
msgid ""
"The related field invisibility path should now be *Country* (carefully "
"select the one just created) *> is not = > 75*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:22
msgid "Again, hide the related field with the countrys ID if you prefer."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:28
msgid ""
"**Case scenario 2: create a model called 'Properties' and add fields called:"
" company, value, name, address, active, image.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:31
msgid ""
"From the dashboard, (optionally) start a new module. Then, click on *Edit "
"Menu* and start a *New Menu* (model). Set your menu name and *Confirm*. Now,"
" on its form, drag & drop the necessary fields."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:39
msgid ""
"**Case scenario 2.a: now, you would like to have a model called 'Regions' to"
" which each property must be linked. And, on 'Regions', you would like to "
"see the properties for each region.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:43
msgid ""
"Go to *Edit Menu > New Menu* and create your menu, calling it *Regions*. Add"
" the necessary fields on its form by dragging & dropping them."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:45
msgid ""
"Now, in the form view of *Properties*, add a *Many2one* field with a "
"relation to your model *Region*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:48
msgid ""
"The *Existing Fields* are the ones that are on the current model but not yet"
" in the view."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:60
msgid ""
"Now, go to the model *Regions*, select the form view, and add a status "
"button selecting *Regions (Properties)* as your relational field."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:62
msgid ""
"*Status buttons* are computed fields, meaning that they count the numbers of"
" records on the related model, and allow you to access them."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:69
msgid ""
"When searching for relations, click on *Search more* and filter it by "
"*Custom*. This way you avoid creating duplicates."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:76
msgid ""
"**Case scenario 2.b: in the model 'Properties', show all the tags as "
"checkboxes instead of tags.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:78
msgid ""
"Once the field *Tags* is added to the form, select it and, under its "
"*Properties > Widgets*, choose *Checkboxes*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:85
msgid ""
"**Case scenario 3: on the leads form, add a selection field with the "
"values:'Tags' & 'List' & 'Checkboxes'. According to the value of the field, "
"show tags as many2many_tags, many2many_radio, or many2many(_list).**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:89
msgid ""
"In your form view, add a *Tags* field and relate it to *Partners Tag*. Under"
" *Properties*, define its *Widget* as *Many2many*. Do the same process "
"another 2 times for *Checkboxes* and *Tags*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:96
msgid "Now, add a *Selection* field and the necessary values."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:99
msgid ""
"Continue by selecting your *Tags* fields, one by one, to set their "
"*Invisible* options according to their *Widget*. In the example below, the "
"invisibility rule for the *Partner Tags* is set as: *Select Tag type > is "
"not = > Tags.*"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:105
msgid ""
"**Case scenario 4: on a quotations form, add a selection field called "
"'Manager Validation' with the values: Accepted and Refused. Only a sales"
" manager can see it, and the field should be set as mandatory if the untaxed"
" amount is higher than 500€.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:109
msgid ""
"On your quotation form, add a *Selection* field with the values *Accepted* "
"and *Refused*. Set its *Required* condition as *Untaxed Amount > 500* and "
"the *Limit visibility to groups* as *Sales / Administrator* or managers."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:117
msgid "**Case scenario 5: change the tooltip of a field for all views.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:119
msgid ""
"Activate the :doc:`Developer mode <../../general/developer_mode/activate>` "
"and open Studio."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:122
msgid ""
"Select the necessary field and, under *Properties*, click on *More* to write"
" your tooltip message on *Field Help*. The tooltip message is the "
"explanatory message shown when the user hovers the field. The message here "
"written is displayed on all views forms where the field is added."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:129
msgid ""
"The *Field Help* message can only be applied to *new* fields. If you would "
"like to change/apply a tooltip for a specific field, use the *Help Tooltip* "
"option under *Properties*."
msgstr ""
#: ../../studio/use_cases/views.rst:3
msgid "Advanced Use Cases: Views"
msgstr ""
#: ../../studio/use_cases/views.rst:5
msgid ""
"**Case scenario 1: in Sales, show orders in a Kanban View instead of a List "
"View.**"
msgstr ""
#: ../../studio/use_cases/views.rst:7
msgid ""
"From the Sales page, access Studio and, under *Views*, set the *Kanban* "
"option as the default one."
msgstr ""
#: ../../studio/use_cases/views.rst:14
msgid ""
"**Case scenario 2: allow for the list of leads to be edited inline without "
"having to switch to the form view.**"
msgstr ""
#: ../../studio/use_cases/views.rst:19
msgid ""
"On the *List View*, under *View* > *Editable*, choose between *New record on"
" top* or *New record at the bottom*. This way, besides defining the order in"
" which new records are displayed in the view, you are able to edit them."
msgstr ""
#: ../../studio/use_cases/views.rst:21
msgid ""
"If the field is left blank, no editing is possible and records are shown "
"based on your column preferences on the lead's page (front-end)."
msgstr ""
-532
View File
@@ -1,532 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Richard Mathot <rim@odoo.com>, 2020
# William Henrotin <whe@odoo.com>, 2020
# Vincent Luba <vincent@biz-4-africa.com>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
# romrik_, 2020
# Priscilla (prs) Odoo <prs@odoo.com>, 2020
# amsodoo <ams@odoo.com>, 2020
# Jonathan Castillo <jcs@odoo.com>, 2021
# Anthony Chaussin <chaussin.anthony@gmail.com>, 2021
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-02-04 11:02+0100\n"
"PO-Revision-Date: 2020-09-22 14:42+0000\n"
"Last-Translator: Anthony Chaussin <chaussin.anthony@gmail.com>, 2021\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../support.rst:5
msgid "Support"
msgstr "Assistance"
#: ../../support/supported_versions.rst:7
msgid "Supported versions"
msgstr "Versions supportées"
#: ../../support/supported_versions.rst:10
msgid ""
"Odoo provides support and bug fixing **for the 3 last major versions** of "
"Odoo."
msgstr ""
"Odoo assure le support et la résolution de bugs **pour les 3 dernières "
"versions majeures** d'Odoo."
#: ../../support/supported_versions.rst:12
msgid ""
"Users hosted on **Odoo Online** may use intermediary versions (sometimes "
"called *SaaS versions*) that are supported as well. These versions are not "
"published for Odoo.sh or On-Premise installations."
msgstr ""
"Les utilisateurs hébergés sur **Odoo Online** peuvent utiliser des versions "
"intermédiaires (parfois appelées *versions SaaS*) qui sont également prises "
"en charge. Ces versions ne sont pas publiées pour les installations Odoo.sh "
"ou On-Premise."
#: ../../support/supported_versions.rst:18
msgid "What's the support status of my Odoo?"
msgstr "Ma version d'Odoo est-elle supportée ?"
#: ../../support/supported_versions.rst:20
msgid "This matrix shows the support status of every version."
msgstr "Cette matrice montre le statut de support de chaque version."
#: ../../support/supported_versions.rst:22
msgid "**Major releases are in bold type.**"
msgstr "**Les versions majeures sont indiquées en gras.**"
#: ../../support/supported_versions.rst:25
msgid "Odoo Online"
msgstr "Odoo Online"
#: ../../support/supported_versions.rst:25
msgid "Odoo.sh"
msgstr "Odoo.sh"
#: ../../support/supported_versions.rst:25
msgid "On-Premise"
msgstr "On-Premise"
#: ../../support/supported_versions.rst:25
msgid "Release date"
msgstr "Date de publication"
#: ../../support/supported_versions.rst:27
msgid "**Odoo 14.0**"
msgstr "**Odoo 14.0**"
#: ../../support/supported_versions.rst:27
#: ../../support/supported_versions.rst:27
#: ../../support/supported_versions.rst:27
#: ../../support/supported_versions.rst:29
#: ../../support/supported_versions.rst:31
#: ../../support/supported_versions.rst:31
#: ../../support/supported_versions.rst:31
#: ../../support/supported_versions.rst:33
#: ../../support/supported_versions.rst:35
#: ../../support/supported_versions.rst:35
#: ../../support/supported_versions.rst:35
msgid "|green|"
msgstr "|green|"
#: ../../support/supported_versions.rst:27
msgid "October 2020"
msgstr "Octobre 2020"
#: ../../support/supported_versions.rst:29
msgid "Odoo 13.saas~4"
msgstr ""
#: ../../support/supported_versions.rst:29
#: ../../support/supported_versions.rst:29
#: ../../support/supported_versions.rst:33
#: ../../support/supported_versions.rst:33
#: ../../support/supported_versions.rst:37
#: ../../support/supported_versions.rst:37
#: ../../support/supported_versions.rst:41
#: ../../support/supported_versions.rst:41
#: ../../support/supported_versions.rst:43
#: ../../support/supported_versions.rst:43
#: ../../support/supported_versions.rst:47
#: ../../support/supported_versions.rst:47
#: ../../support/supported_versions.rst:49
#: ../../support/supported_versions.rst:51
#: ../../support/supported_versions.rst:51
#: ../../support/supported_versions.rst:53
msgid "N/A"
msgstr "N/D"
#: ../../support/supported_versions.rst:29
#: ../../support/supported_versions.rst:33
msgid "August 2019"
msgstr "Août 2019"
#: ../../support/supported_versions.rst:31
msgid "**Odoo 13.0**"
msgstr "**Odoo 13.0**"
#: ../../support/supported_versions.rst:31
msgid "October 2019"
msgstr "Octobre 2019"
#: ../../support/supported_versions.rst:33
msgid "Odoo 12.saas~3"
msgstr "Odoo 12.saas~3"
#: ../../support/supported_versions.rst:35
msgid "**Odoo 12.0**"
msgstr "**Odoo 12.0**"
#: ../../support/supported_versions.rst:35
msgid "October 2018"
msgstr "Octobre 2018"
#: ../../support/supported_versions.rst:35
msgid "*End-of-support is planned for October 2021*"
msgstr ""
#: ../../support/supported_versions.rst:37
msgid "Odoo 11.saas~3"
msgstr "Odoo 11.saas~3"
#: ../../support/supported_versions.rst:37
#: ../../support/supported_versions.rst:39
#: ../../support/supported_versions.rst:39
#: ../../support/supported_versions.rst:41
#: ../../support/supported_versions.rst:43
#: ../../support/supported_versions.rst:45
#: ../../support/supported_versions.rst:45
#: ../../support/supported_versions.rst:47
#: ../../support/supported_versions.rst:49
#: ../../support/supported_versions.rst:51
#: ../../support/supported_versions.rst:53
msgid "|orange|"
msgstr "|orange|"
#: ../../support/supported_versions.rst:37
msgid "April 2018"
msgstr "Avril 2018"
#: ../../support/supported_versions.rst:39
msgid "**Odoo 11.0**"
msgstr "**Odoo 11.0**"
#: ../../support/supported_versions.rst:39
#: ../../support/supported_versions.rst:45
#: ../../support/supported_versions.rst:49
#: ../../support/supported_versions.rst:53
msgid "|red|"
msgstr "|red|"
#: ../../support/supported_versions.rst:39
msgid "October 2017"
msgstr "Octobre 2017"
#: ../../support/supported_versions.rst:41
msgid "Odoo 10.saas~15"
msgstr "Odoo 10.saas~15"
#: ../../support/supported_versions.rst:41
msgid "March 2017"
msgstr "Mars 2017"
#: ../../support/supported_versions.rst:43
msgid "Odoo 10.saas~14"
msgstr "Odoo 10.saas~14"
#: ../../support/supported_versions.rst:43
msgid "January 2017"
msgstr "Janvier 2017"
#: ../../support/supported_versions.rst:45
msgid "**Odoo 10.0**"
msgstr "**Odoo 10.0**"
#: ../../support/supported_versions.rst:45
msgid "October 2016"
msgstr "Octobre 2016"
#: ../../support/supported_versions.rst:47
msgid "Odoo 9.saas~11"
msgstr "Odoo 9.saas~11"
#: ../../support/supported_versions.rst:47
msgid "May 2016"
msgstr "Mai 2016"
#: ../../support/supported_versions.rst:49
msgid "**Odoo 9.0**"
msgstr "**Odoo 9.0**"
#: ../../support/supported_versions.rst:49
msgid "October 2015"
msgstr "Octobre 2015"
#: ../../support/supported_versions.rst:51
msgid "Odoo 8.saas~6"
msgstr "Odoo 8.saas~6"
#: ../../support/supported_versions.rst:51
msgid "February 2015"
msgstr "Février 2015"
#: ../../support/supported_versions.rst:53
msgid "**Odoo 8.0**"
msgstr "**Odoo 8.0**"
#: ../../support/supported_versions.rst:53
msgid "September 2014"
msgstr "Septembre 2014"
#: ../../support/supported_versions.rst:59
msgid "|green| Supported version"
msgstr "|green| Version supportée"
#: ../../support/supported_versions.rst:61
msgid "|red| End-of-support"
msgstr "|red| Fin du support"
#: ../../support/supported_versions.rst:63
msgid "N/A Never released for this platform"
msgstr "N/D Jamais publié pour cette plateforme"
#: ../../support/supported_versions.rst:65
msgid ""
"|orange| Some of our older customers may still run this version on our Odoo "
"Online servers, we provide help only on blocking issues and advise you to "
"upgrade."
msgstr ""
"|orange| Certains de nos anciens clients pourraient encore travailler avec "
"cette version sur nos serveurs Odoo Online, nous fournissons alors de l'aide"
" uniquement pour les problèmes bloquants et vous conseillons de migrer vers "
"une version plus récente."
#: ../../support/supported_versions.rst:67
msgid "🏁 Future version, not released yet"
msgstr "🏁 Prochaine version, pas encore publiée"
#: ../../support/supported_versions.rst:80
msgid "I run an older version of Odoo/OpenERP/TinyERP"
msgstr "J'utilise une ancienne version d'Odoo/OpenERP/TinyERP"
#: ../../support/supported_versions.rst:82
msgid ""
"OpenERP 7.0, 6.1, 6.0 and 5.0 is not supported anymore, on any platform."
msgstr ""
"OpenERP 7.0, 6.1, 6.0 et 5.0 ne sont plus supportés, quelle que soit la "
"plateforme."
#: ../../support/supported_versions.rst:84
msgid ""
"TinyERP 4.0, 3.0, 2.0 and 1.0 is not supported anymore, on any platform."
msgstr ""
"TinyERP 4.0, 3.0, 2.0 et 1.0 ne sont plus supportés, quelle que soit la "
"plateforme."
#: ../../support/supported_versions.rst:86
msgid ""
"You should consider `upgrading <https://upgrade.odoo.com/>`_ your database."
msgstr ""
"Vous devriez `migrer <https://upgrade.odoo.com/>`_ votre base de données "
"vers une version plus récente."
#: ../../support/what_can_i_expect.rst:8
msgid "What can I expect from the support service?"
msgstr "Que puis-je attendre du service de Support ?"
#: ../../support/what_can_i_expect.rst:12
msgid "5 days a week"
msgstr "5 jours par semaine"
#: ../../support/what_can_i_expect.rst:14
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!"
msgstr ""
"Votre abonnement Odoo Online inclut **un support illimité 24h/24 sans coût "
"supplémentaire, du lundi au vendredi**. Nos équipes se situent dans le monde"
" entier afin d'assurer que vous puissiez bénéficier du support, peut importe"
" où vous vous trouvez. Votre agent de support peut vous joindre depuis la "
"Belgique, San Francisco ou l'Inde !"
#: ../../support/what_can_i_expect.rst:19
msgid ""
"Our support team can be contacted through our `online support form "
"<https://www.odoo.com/help>`__."
msgstr ""
"Notre équipe Support est joignable via notre `formulaire de support en ligne"
" <https://www.odoo.com/help>`__."
#: ../../support/what_can_i_expect.rst:23
msgid "What kind of support is included?"
msgstr "Qu'est ce qui est inclus dans le Support ?"
#: ../../support/what_can_i_expect.rst:25
msgid ""
"Providing you with relevant material (guidelines, product documentation, "
"etc...)"
msgstr ""
"Vous fournir des informations pertinentes (consignes, documentation sur le "
"produit, etc...)"
#: ../../support/what_can_i_expect.rst:27
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 ""
"Des réponses aux problèmes que vous pourriez rencontrer dans votre base de "
"données standard Odoo (ex : “Je ne parviens pas à fermer mon Point de Vente”"
" ou “Je ne trouve pas mes KPIs de vente”)"
#: ../../support/what_can_i_expect.rst:29
msgid "Questions related to your account, subscription, or billing"
msgstr "Des questions liées à votre compte, abonnement ou facturation"
#: ../../support/what_can_i_expect.rst:30
msgid ""
"Bug resolution (blocking issues or unexpected behaviour not due to "
"misconfiguration or customization)"
msgstr ""
"Résolution de bugs (problèmes bloquants ou comportement inattendus non dûs à"
" une mauvaise configuration ou personnalisation)"
#: ../../support/what_can_i_expect.rst:32
msgid ""
"Issues that might occur in a test database after upgrading to a newer "
"version"
msgstr ""
"Les problèmes qui pourraient survenir dans une base de données test après "
"une migration vers une version plus récente"
#: ../../support/what_can_i_expect.rst:34
msgid ""
"*Odoo Support does not make changes to your production database without your"
" agreement and gives you the material and knowledge to do it yourself!*"
msgstr ""
"*Odoo Support n'apporte aucune modification à votre base de données de "
"production sans votre accord et vous donne le matériel et les connaissances "
"nécessaires pour le faire vous-même!*"
#: ../../support/what_can_i_expect.rst:39
msgid "What kind of support is not included?"
msgstr "Qu'est ce qui n'est pas inclus dans le Support ?"
#: ../../support/what_can_i_expect.rst:41
msgid ""
"Questions that require us to understand your business processes in order to "
"help you implement your database"
msgstr ""
"Les questions qui nous demandent de comprendre les flux de travail de votre "
"entreprise afin de vous aider à vous implémenter votre base de données"
#: ../../support/what_can_i_expect.rst:43
msgid ""
"Training on how to use our software (we will direct you to our many "
"resources)"
msgstr ""
"D'éventuelles formations à l'utilisation de notre logiciel (nous vous "
"dirigerons vers nos différentes ressources)"
#: ../../support/what_can_i_expect.rst:44
msgid "Import of documents into your database"
msgstr "L'importation de documents vers votre base de données"
#: ../../support/what_can_i_expect.rst:45
msgid ""
"Guidance on which configurations to apply inside of an application or the "
"database"
msgstr ""
"Des instructions sur les configurations à appliquer au sein d'un module ou "
"d'une base de données"
#: ../../support/what_can_i_expect.rst:46
msgid ""
"How to set up configuration models (Examples include: Inventory Routes, "
"Payment Terms, Warehouses, etc)"
msgstr ""
"Comment mettre en place des modèles de configuration (ex : les routes "
"d'inventaires, les délais de paiement, entrepôts, etc)"
#: ../../support/what_can_i_expect.rst:48
msgid "Any intervention on your own servers/deployments of Odoo"
msgstr "Toute intervention sur votre propre serveur/déploiements d'Odoo"
#: ../../support/what_can_i_expect.rst:49
msgid ""
"Any intervention on your own third party account (Ingenico, Authorize, UPS, "
"etc)"
msgstr ""
"Toute intervention sur vos compte tiers (Ingenico, Authorize, UPS, etc)"
#: ../../support/what_can_i_expect.rst:50
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 ""
"Les questions ou problèmes liés à un développement ou une customisation "
"spécifique réalisée Odoo ou une partie tierce (qui est spécifique seulement "
"à votre base de données ou impliquant le code)"
#: ../../support/what_can_i_expect.rst:54
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 ""
"Vous pouvez bénéficier de ce type de Support avec un `Success Pack "
"<https://www.odoo.com/pricing-packs>`__. Avec un pack, l'un de nos "
"consultants analysera la manière dont votre entreprise fonctionne et vous "
"dira comment tirer le maximum de votre base de données Odoo. Nous nous "
"occuperons de toutes les configurations ainsi que de vous former à utiliser "
"Odoo."
#: ../../support/where_can_i_get_support.rst:6
msgid "Where to find help?"
msgstr "Où trouver de l'aide ?"
#: ../../support/where_can_i_get_support.rst:10
msgid "Odoo Enterprise"
msgstr "Odoo Entreprise"
#: ../../support/where_can_i_get_support.rst:12
msgid ""
"Users who have a valid Odoo Enterprise subscription may always contact our "
"support teams through our `support form <https://www.odoo.com/help>`_, no "
"matter the hosting type you chose (Odoo Online, Odoo.sh or on your own "
"server)."
msgstr ""
"Les utilisateurs qui ont un abonnement Odoo Entreprise valide peuvent "
"toujours contacter nos équipes Support via notre `formulaire de support "
"<https://www.odoo.com/help>`_, peu importe le type d'hébergement que vous "
"choisissez (Odoo en ligne, Odoo.sh ou sur votre propre serveur)."
#: ../../support/where_can_i_get_support.rst:16
msgid "Please include in your request:"
msgstr "Merci d'inclure votre demande : "
#: ../../support/where_can_i_get_support.rst:18
msgid "your subscription number"
msgstr "votre numéro d'abonnement"
#: ../../support/where_can_i_get_support.rst:19
msgid ""
"the URL of your database if your database is hosted by Odoo (Odoo Online or "
"Odoo.sh)"
msgstr ""
"l'URL de votre base de données si votre base de données est hébergée par "
"Odoo (Odoo en ligne ou Odoo.sh)."
#: ../../support/where_can_i_get_support.rst:21
msgid "Our agents will get back to you as soon as possible."
msgstr "Nos agents reviendront vers vous dès que possible."
#: ../../support/where_can_i_get_support.rst:25
msgid "Odoo Community"
msgstr "Odoo Community"
#: ../../support/where_can_i_get_support.rst:27
msgid "*Odoo Community users don't get access to the support service.*"
msgstr ""
"*Les utilisateurs d'Odoo Community n'ont pas accès au service de Support.*"
#: ../../support/where_can_i_get_support.rst:29
msgid "Here are some resources that might help you:"
msgstr "Voici des ressources qui pourraient vous aider :"
#: ../../support/where_can_i_get_support.rst:31
msgid "Our `documentation pages <https://www.odoo.com/page/docs>`_."
msgstr "Nos `pages de documentation <https://www.odoo.com/page/docs>`_."
#: ../../support/where_can_i_get_support.rst:32
msgid ""
"Ask your question on the `community forum "
"<https://www.odoo.com/forum/help-1>`_."
msgstr ""
"Posez vos questions sur le `forum de la communauté "
"<https://www.odoo.com/forum/help-1>`_, en anglais."
#: ../../support/where_can_i_get_support.rst:33
msgid ""
"`Buy Odoo Enterprise "
"<https://www.odoo.com/documentation/14.0/setup/enterprise.html>`_ to get the"
" support and bugfix services."
msgstr ""
-242
View File
@@ -1,242 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Hamid Darabi, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
# Priscilla Sanchez <prs@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:42+0000\n"
"Last-Translator: Priscilla Sanchez <prs@odoo.com>, 2020\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../survey.rst:5
msgid "Survey"
msgstr "Sondage"
#: ../../survey/overview.rst:3
msgid "Overview"
msgstr "Vue d'ensemble"
#: ../../survey/overview/create.rst:3
msgid "Get Started with Surveys"
msgstr ""
#: ../../survey/overview/create.rst:5
msgid ""
"Surveys can be used for a range of purposes that can go from collecting "
"customer feedback, evaluate the success of an event, measure how pleased "
"customers are with your products/services, gauge whether employees are happy"
" and satisfied with their work environment, and even to find out what your "
"market is thinking."
msgstr ""
#: ../../survey/overview/create.rst:11
msgid "Get started"
msgstr "Démarrer"
#: ../../survey/overview/create.rst:13
msgid ""
"When creating your survey, choose a *Title* and *Category*. The *Category* "
"field is used to know in which context the survey is being conducted, as "
"different applications might use it for different purposes such as "
"recruitment, certification, or employee appraisal."
msgstr ""
#: ../../survey/overview/create.rst:22
msgid "Tab: Questions"
msgstr ""
#: ../../survey/overview/create.rst:24
msgid "Add sections and questions by clicking on the respective links."
msgstr ""
#: ../../survey/overview/create.rst:27
msgid ""
"On the *Sections and Questions* form, once the question type is chosen and "
"the answer added, under the tab *Options*, enable *Mandatory Answer*, and "
"set an *Error message* to be shown when the user tries to submit the survey "
"without answering the respective question."
msgstr ""
#: ../../survey/overview/create.rst:29
msgid ""
"Depending on the *Question Type*, the tab *Options* aggregates extra and "
"different possibilities. Examples:"
msgstr ""
#: ../../survey/overview/create.rst:31
msgid ""
"*Single Line Text Box* - can choose a minimum and maximum text length "
"(number of characters - spaces do not count), and its error message."
msgstr ""
#: ../../survey/overview/create.rst:33
msgid ""
"*Multiple choice: multiple answers allowed*: choose between radio buttons or"
" a dropdown menu list, and if you would like to have a comment field. If the"
" user select an answer and type a comment, the values are separately "
"recorded. Or, enable the comment field to be displayed as an answer choice, "
"with which a text type field is displayed."
msgstr ""
#: ../../survey/overview/create.rst:37
msgid ""
"*Matrix Type*: choose if you would like to have one or multiple choices per "
"row."
msgstr ""
#: ../../survey/overview/create.rst:44
msgid "Tab: Description"
msgstr ""
#: ../../survey/overview/create.rst:46
msgid ""
"Write a *Description* to be displayed under the title of the survey's "
"homepage."
msgstr ""
#: ../../survey/overview/create.rst:53
msgid "Click on *Edit* to personalize your pages with the website builder."
msgstr ""
#: ../../survey/overview/create.rst:56
msgid "Tab: Options"
msgstr ""
#: ../../survey/overview/create.rst:58
msgid ""
"Under the tab *Options*, choose the *Layout* of your questions. If choosing "
"*One page per section* or *One page per question*, an option *Back Button* "
"becomes available, which allows the user to go back pages."
msgstr ""
#: ../../survey/overview/create.rst:67
msgid "Test and share the survey"
msgstr ""
#: ../../survey/overview/create.rst:70
msgid ""
"Once your Survey is ready, *Test* it to avoid *Sharing* it with potential "
"errors. As answers get collected, click on *Answers* to access all the "
"details of the respondent and his answers."
msgstr ""
#: ../../survey/overview/create.rst:72
msgid ""
"By default, a filter *Except Test Entries* is applied to keep the list of "
"entries clean with only real participants."
msgstr ""
#: ../../survey/overview/create.rst:79
msgid ""
"Another way to access detailed answers is by going to "
":menuselection:`Participations --> Participations`."
msgstr ""
#: ../../survey/overview/create.rst:80
msgid "Click on *See results* to be redirected to an analytical page."
msgstr ""
#: ../../survey/overview/create.rst:87
#: ../../survey/overview/time_random.rst:34
msgid ":doc:`scoring`"
msgstr ""
#: ../../survey/overview/create.rst:88 ../../survey/overview/scoring.rst:35
msgid ":doc:`time_random`"
msgstr ""
#: ../../survey/overview/scoring.rst:3
msgid "Scoring Surveys"
msgstr ""
#: ../../survey/overview/scoring.rst:5
msgid ""
"To measure your respondents performance, knowledge of a subject, or overall"
" satisfaction, attach points to the answers of specific questions. The "
"points are summed up to give your respondent a final score."
msgstr ""
#: ../../survey/overview/scoring.rst:9
msgid ""
"On your surveys form, click on *Add a question* and, under the tab "
"*Options*, choose between *Scoring with answers at the end* or *Scoring "
"without answers at the end*. Now, on your questions form, set the right "
"answer and score."
msgstr ""
#: ../../survey/overview/scoring.rst:17
msgid ""
"Set the percentage score the user needs to achieve to have successfully "
"taken the survey. If enabling *Certificate*, choose its template. The "
"certification is automatically sent by email to the users who successfully "
"finish it."
msgstr ""
#: ../../survey/overview/scoring.rst:25
msgid ""
"Enable *Login required* to be able to *Give Badges*. Badges are related to "
"the eLearning section of your website. Besides the logged-in user, visitors "
"of the website that access the page *Courses* can also see the granted "
"badges."
msgstr ""
#: ../../survey/overview/time_random.rst:3
msgid "Time and Randomize Questions"
msgstr ""
#: ../../survey/overview/time_random.rst:6
msgid "Time Limit"
msgstr "Limite de temps"
#: ../../survey/overview/time_random.rst:10
msgid ""
"On timed surveys, respondents need to complete the survey within a certain "
"period of time. It can be used to ensure that all respondents get the same "
"amount of time to find the answers, or to decrease the chance of having them"
" looking at external resources."
msgstr ""
#: ../../survey/overview/time_random.rst:11
msgid "Set the *Time limit* under the tab *Options*."
msgstr ""
#: ../../survey/overview/time_random.rst:17
msgid ""
"A timer is shown on the pages so the user can keep track of the remaining "
"time. Surveys not \\ submitted by the *Time limit* do not have their answers"
" saved."
msgstr ""
#: ../../survey/overview/time_random.rst:21
msgid "Selection"
msgstr "Sélection"
#: ../../survey/overview/time_random.rst:25
msgid ""
"When you randomize a survey, you allow for the questions to be shuffled in a"
" random order every time someone opens the questionnaire. This can be useful"
" to avoid having respondents looking at each others' answers."
msgstr ""
#: ../../survey/overview/time_random.rst:27
msgid ""
"To do so, under the tab *Options*, enable *Randomized per section*. Now, "
"under the tab *Questions*, set how many of the questions in that section "
"should be taken into account during the shuffling."
msgstr ""
-86
View File
@@ -1,86 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-02-04 11:02+0100\n"
"PO-Revision-Date: 2020-09-22 15:13+0000\n"
"Last-Translator: Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020\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"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../timesheets.rst:5
msgid "Timesheets"
msgstr "Feuilles de temps"
#: ../../timesheets/overview.rst:3
msgid "Overview"
msgstr "Vue d'ensemble"
#: ../../timesheets/overview/time_off.rst:3
msgid "Create Timesheets upon Time Off Validation"
msgstr ""
#: ../../timesheets/overview/time_off.rst:5
msgid ""
"Odoo automatically timesheets on project/tasks upon time off requests. This "
"allows for better overall control over the validation of timesheets, as it "
"does not leave place for forgetfulness and questions after hours that have "
"not been timesheeted by the employee."
msgstr ""
#: ../../timesheets/overview/time_off.rst:9
msgid ""
"Activate the :doc:`Developer mode <../../general/developer_mode/activate>`, "
"go to *Timesheets*, and change the *Project* and *Task* set by default, if "
"you like."
msgstr ""
#: ../../timesheets/overview/time_off.rst:16
msgid ""
"Go to :menuselection:`Time Off --> Configuration --> Time Off Types`. Select"
" or create the needed type, and decide if you would like the requests to be "
"validated or not."
msgstr ""
#: ../../timesheets/overview/time_off.rst:26
msgid ""
"Now, once the employee has requested his time off and the request has been "
"validated (or not, depending on the setting chosen), the time is "
"automatically allocated on *Timesheets*, under the respective project and "
"task."
msgstr ""
#: ../../timesheets/overview/time_off.rst:27
msgid ""
"On the example below, the user requested *Paid Time off* from July 13th to "
"15th."
msgstr ""
#: ../../timesheets/overview/time_off.rst:33
msgid ""
"Considering that validation is not required, the requested time off is "
"automatically displayed in *Timesheets*. If validation is necessary, the "
"time is automatically allocated after the responsible person for validating "
"does it so."
msgstr ""
#: ../../timesheets/overview/time_off.rst:41
msgid ""
"Click on the magnifying glass, hovering over the concerned cell, to access "
"all the aggregated data on that cell (day), and see details regarding the "
"project/task."
msgstr ""
File diff suppressed because it is too large Load Diff