NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[I18N] *: export translations

Browse Source 
closes odoo/documentation#6075

X-original-commit: f6a43ac7cc
Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
This commit is contained in:
Martin Trigaux 2023-10-09 15:20:14 +02:00
parent 94af36625c
commit ae058cba51
10 changed files with 4695 additions and 3389 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

424
locale/sources/administration.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-09-12 13:54+0000\n"
"POT-Creation-Date: 2023-10-09 13:19+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -231,7 +231,7 @@ msgstr ""
#: ../../content/administration/install/deploy.rst:46
#: ../../content/administration/install/deploy.rst:58
#: ../../content/administration/install/deploy.rst:153
#: ../../content/administration/install/deploy.rst:276
#: ../../content/administration/install/deploy.rst:280
msgid "in :ref:`the configuration file <reference/cmdline/config_file>` set:"
msgstr ""
@ -266,8 +266,8 @@ msgstr ""
#: ../../content/administration/install/deploy.rst:95
#: ../../content/administration/install/deploy.rst:145
#: ../../content/administration/install/deploy.rst:231
#: ../../content/administration/install/deploy.rst:271
#: ../../content/administration/install/deploy.rst:235
#: ../../content/administration/install/deploy.rst:275
msgid "Configuration sample"
msgstr ""
@ -352,335 +352,315 @@ msgid "Builtin server"
msgstr ""
#: ../../content/administration/install/deploy.rst:182
msgid "Odoo includes built-in HTTP servers, using either multithreading or multiprocessing."
msgid "Odoo includes built-in HTTP, cron, and live-chat servers, using either multi-threading or multi-processing."
msgstr ""
#: ../../content/administration/install/deploy.rst:185
msgid "For production use, it is recommended to use the multiprocessing server as it increases stability, makes somewhat better use of computing resources and can be better monitored and resource-restricted."
msgid "The **multi-threaded** server is a simpler server primarily used for development, demonstrations, and its compatibility with various operating systems (including Windows). A new thread is spawned for every new HTTP request, even for long-lived connections such as websocket. Extra daemonic cron threads are spawned too. Due to a Python limitation (GIL), it doesn't make the best use of the hardware."
msgstr ""
#: ../../content/administration/install/deploy.rst:189
msgid "Multiprocessing is enabled by configuring :option:`a non-zero number of worker processes <odoo-bin --workers>`, the number of workers should be based on the number of cores in the machine (possibly with some room for cron workers depending on how much cron work is predicted)"
#: ../../content/administration/install/deploy.rst:191
msgid "The multi-threaded server is the default server, also for docker containers. It is selected by leaving the :option:`--workers <odoo-bin --workers>` option out or setting it to ``0``."
msgstr ""
#: ../../content/administration/install/deploy.rst:193
msgid "Worker limits can be configured based on the hardware configuration to avoid resources exhaustion"
msgstr ""
#: ../../content/administration/install/deploy.rst:196
msgid "multiprocessing mode currently isn't available on Windows"
msgstr ""
#: ../../content/administration/install/deploy.rst:199
msgid "Worker number calculation"
#: ../../content/administration/install/deploy.rst:194
msgid "The **multi-processing** server is a full-blown server primarily used for production. It is not liable to the same Python limitation (GIL) on resource usage and hence makes the best use of the hardware. A pool of workers is created upon server startup. New HTTP requests are queued by the OS until there are workers ready to process them. An extra event-driven HTTP worker for the live chat is spawned on an alternative port. Extra cron workers are spawned too. A configurable process reaper monitors resource usage and can kill/restart failed workers."
msgstr ""
#: ../../content/administration/install/deploy.rst:201
msgid "Rule of thumb : (#CPU * 2) + 1"
msgid "The multi-processing server is opt-in. It is selected by setting the :option:`--workers <odoo-bin --workers>` option to a non-null integer."
msgstr ""
#: ../../content/administration/install/deploy.rst:202
msgid "Cron workers need CPU"
msgstr ""
#: ../../content/administration/install/deploy.rst:203
msgid "1 worker ~= 6 concurrent users"
msgstr ""
#: ../../content/administration/install/deploy.rst:206
msgid "memory size calculation"
msgstr ""
#: ../../content/administration/install/deploy.rst:208
msgid "We consider 20% of the requests are heavy requests, while 80% are simpler ones"
#: ../../content/administration/install/deploy.rst:205
msgid "Because it is highly customized for Linux servers, the multi-processing server is not available on Windows."
msgstr ""
#: ../../content/administration/install/deploy.rst:209
msgid "A heavy worker, when all computed field are well designed, SQL requests are well designed, ... is estimated to consume around 1GB of RAM"
msgid "Worker number calculation"
msgstr ""
#: ../../content/administration/install/deploy.rst:210
msgid "A lighter worker, in the same scenario, is estimated to consume around 150MB of RAM"
#: ../../content/administration/install/deploy.rst:211
msgid "Rule of thumb : (#CPU * 2) + 1"
msgstr ""
#: ../../content/administration/install/deploy.rst:212
msgid "Cron workers need CPU"
msgstr ""
#: ../../content/administration/install/deploy.rst:213
msgid "1 worker ~= 6 concurrent users"
msgstr ""
#: ../../content/administration/install/deploy.rst:216
msgid "memory size calculation"
msgstr ""
#: ../../content/administration/install/deploy.rst:218
msgid "We consider 20% of the requests are heavy requests, while 80% are simpler ones"
msgstr ""
#: ../../content/administration/install/deploy.rst:219
msgid "A heavy worker, when all computed field are well designed, SQL requests are well designed, ... is estimated to consume around 1GB of RAM"
msgstr ""
#: ../../content/administration/install/deploy.rst:220
msgid "A lighter worker, in the same scenario, is estimated to consume around 150MB of RAM"
msgstr ""
#: ../../content/administration/install/deploy.rst:222
msgid "Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) + (heavy_worker_ratio * heavy_worker_ram_estimation) )"
msgstr ""
#: ../../content/administration/install/deploy.rst:215
#: ../../content/administration/install/deploy.rst:378
#: ../../content/administration/install/deploy.rst:225
#: ../../content/administration/install/deploy.rst:382
msgid "LiveChat"
msgstr ""
#: ../../content/administration/install/deploy.rst:217
msgid "In multiprocessing, a dedicated LiveChat worker is automatically started and listening on :option:`the gevent port <odoo-bin --gevent-port>` but the client will not connect to it."
msgstr ""
#: ../../content/administration/install/deploy.rst:221
msgid "Instead you must have a proxy redirecting requests whose URL starts with ``/websocket/`` to the gevent port. Other request should be proxied to the :option:`normal HTTP port <odoo-bin --http-port>`"
msgstr ""
#: ../../content/administration/install/deploy.rst:225
msgid "To achieve such a thing, you'll need to deploy a reverse proxy in front of Odoo, like nginx or apache. When doing so, you'll need to forward some more http Headers to Odoo, and activate the proxy_mode in Odoo configuration to have Odoo read those headers."
msgstr ""
#: ../../content/administration/install/deploy.rst:233
msgid "Server with 4 CPU, 8 Thread"
msgstr ""
#: ../../content/administration/install/deploy.rst:234
msgid "60 concurrent users"
msgstr ""
#: ../../content/administration/install/deploy.rst:236
msgid "60 users / 6 = 10 <- theoretical number of worker needed"
#: ../../content/administration/install/deploy.rst:227
msgid "In multi-processing, a dedicated LiveChat worker is automatically started and listens on the :option:`--gevent-port <odoo-bin --gevent-port>`. By default, the HTTP requests will keep accessing the normal HTTP workers instead of the LiveChat one. You must deploy a proxy in front of Odoo and redirect incoming requests whose path starts with ``/websocket/`` to the LiveChat worker. You must also start Odoo in :option:`--proxy-mode <odoo-bin --proxy-mode>` so it uses the real client headers (such as hostname, scheme, and IP) instead of the proxy ones."
msgstr ""
#: ../../content/administration/install/deploy.rst:237
msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker"
msgid "Server with 4 CPU, 8 Thread"
msgstr ""
#: ../../content/administration/install/deploy.rst:238
msgid "We'll use 8 workers + 1 for cron. We'll also use a monitoring system to measure cpu load, and check if it's between 7 and 7.5 ."
msgid "60 concurrent users"
msgstr ""
#: ../../content/administration/install/deploy.rst:239
msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo"
#: ../../content/administration/install/deploy.rst:240
msgid "60 users / 6 = 10 <- theoretical number of worker needed"
msgstr ""
#: ../../content/administration/install/deploy.rst:241
msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker"
msgstr ""
#: ../../content/administration/install/deploy.rst:242
msgid "We'll use 8 workers + 1 for cron. We'll also use a monitoring system to measure cpu load, and check if it's between 7 and 7.5 ."
msgstr ""
#: ../../content/administration/install/deploy.rst:243
msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo"
msgstr ""
#: ../../content/administration/install/deploy.rst:245
msgid "in :ref:`the configuration file <reference/cmdline/config_file>`:"
msgstr ""
#: ../../content/administration/install/deploy.rst:257
#: ../../content/administration/install/deploy.rst:261
msgid "HTTPS"
msgstr ""
#: ../../content/administration/install/deploy.rst:259
#: ../../content/administration/install/deploy.rst:263
msgid "Whether it's accessed via website/web client or web service, Odoo transmits authentication information in cleartext. This means a secure deployment of Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via just about any SSL termination proxy, but requires the following setup:"
msgstr ""
#: ../../content/administration/install/deploy.rst:264
#: ../../content/administration/install/deploy.rst:268
msgid "Enable Odoo's :option:`proxy mode <odoo-bin --proxy-mode>`. This should only be enabled when Odoo is behind a reverse proxy"
msgstr ""
#: ../../content/administration/install/deploy.rst:265
#: ../../content/administration/install/deploy.rst:269
msgid "Set up the SSL termination proxy (`Nginx termination example`_)"
msgstr ""
#: ../../content/administration/install/deploy.rst:266
#: ../../content/administration/install/deploy.rst:270
msgid "Set up the proxying itself (`Nginx proxying example`_)"
msgstr ""
#: ../../content/administration/install/deploy.rst:267
#: ../../content/administration/install/deploy.rst:271
msgid "Your SSL termination proxy should also automatically redirect non-secure connections to the secure port"
msgstr ""
#: ../../content/administration/install/deploy.rst:273
#: ../../content/administration/install/deploy.rst:277
msgid "Redirect http requests to https"
msgstr ""
#: ../../content/administration/install/deploy.rst:274
#: ../../content/administration/install/deploy.rst:278
msgid "Proxy requests to odoo"
msgstr ""
#: ../../content/administration/install/deploy.rst:282
#: ../../content/administration/install/deploy.rst:286
msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:"
msgstr ""
#: ../../content/administration/install/deploy.rst:352
#: ../../content/administration/install/deploy.rst:356
msgid "Odoo as a WSGI Application"
msgstr ""
#: ../../content/administration/install/deploy.rst:354
#: ../../content/administration/install/deploy.rst:358
msgid "It is also possible to mount Odoo as a standard WSGI_ application. Odoo provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. That script should be customized (possibly after copying it from the setup directory) to correctly set the configuration directly in :mod:`odoo.tools.config` rather than through the command-line or a configuration file."
msgstr ""
#: ../../content/administration/install/deploy.rst:360
#: ../../content/administration/install/deploy.rst:364
msgid "However the WSGI server will only expose the main HTTP endpoint for the web client, website and webservice API. Because Odoo does not control the creation of workers anymore it can not setup cron or livechat workers"
msgstr ""
#: ../../content/administration/install/deploy.rst:365
#: ../../content/administration/install/deploy.rst:369
msgid "Cron Workers"
msgstr ""
#: ../../content/administration/install/deploy.rst:367
msgid "To run cron jobs for an Odoo deployment as a WSGI application requires"
#: ../../content/administration/install/deploy.rst:371
msgid "Starting one of the built-in Odoo servers next to the WSGI server is required to process cron jobs. That server must be configured to only process crons and not HTTP requests using the :option:`--no-http <odoo-bin --no-http>` cli option or the ``http_enable = False`` configuration file setting."
msgstr ""
#: ../../content/administration/install/deploy.rst:369
msgid "A classical Odoo (run via ``odoo-bin``)"
#: ../../content/administration/install/deploy.rst:376
msgid "On Linux-like systems, using the multi-processing server over the multi-threading one is recommended to benefit from better hardware usage and increased stability, i.e., using the :option:`--workers=-1 <odoo-bin --workers>` and :option:`--max-cron-threads=n <odoo-bin --max-cron-threads>` cli options."
msgstr ""
#: ../../content/administration/install/deploy.rst:370
msgid "Connected to the database in which cron jobs have to be run (via :option:`odoo-bin -d`)"
msgstr ""
#: ../../content/administration/install/deploy.rst:372
msgid "Which should not be exposed to the network. To ensure cron runners are not network-accessible, it is possible to disable the built-in HTTP server entirely with :option:`odoo-bin --no-http` or setting ``http_enable = False`` in the configuration file"
msgstr ""
#: ../../content/administration/install/deploy.rst:380
msgid "The second problematic subsystem for WSGI deployments is the LiveChat: where most HTTP connections are relatively short and quickly free up their worker process for the next request, LiveChat require a long-lived connection for each client in order to implement near-real-time notifications."
msgstr ""
#: ../../content/administration/install/deploy.rst:385
msgid "This is in conflict with the process-based worker model, as it will tie up worker processes and prevent new users from accessing the system. However, those long-lived connections do very little and mostly stay parked waiting for notifications."
#: ../../content/administration/install/deploy.rst:384
msgid "Using a gevent-compatible WSGI server is required for the correct operation of the live chat feature. That server should be able to handle many simultaneous long-lived connections but doesn't need a lot of processing power. All requests whose path starts with ``/websocket/`` should be directed to that server. A regular (thread/process-based) WSGI server should be used for all other requests."
msgstr ""
#: ../../content/administration/install/deploy.rst:390
msgid "The solutions to support livechat/motifications in a WSGI application are:"
msgid "The Odoo cron server can also be used to serve the live chat requests. Just drop the :option:`--no-http <odoo-bin --no-http>` cli option from the cron server and make sure requests whose path starts with ``/websocket/`` are directed to this server, either on the :option:`--http-port <odoo-bin --http-port>` (multi-threading server) or on the :option:`--gevent-port <odoo-bin --gevent-port>` (multi-processing server)."
msgstr ""
#: ../../content/administration/install/deploy.rst:392
msgid "Deploy a threaded version of Odoo (instead of a process-based preforking one) and redirect only requests to URLs starting with ``/websocket/`` to that Odoo, this is the simplest and the websocket URL can double up as the cron instance."
msgstr ""
#: ../../content/administration/install/deploy.rst:396
msgid "Deploy an evented Odoo via ``odoo-gevent`` and proxy requests starting with ``/websocket/`` to :option:`the gevent port <odoo-bin --gevent-port>`."
msgstr ""
#: ../../content/administration/install/deploy.rst:403
#: ../../content/administration/install/deploy.rst:399
msgid "Serving static files and attachments"
msgstr ""
#: ../../content/administration/install/deploy.rst:405
#: ../../content/administration/install/deploy.rst:401
msgid "For development convenience, Odoo directly serves all static files and attachments in its modules. This may not be ideal when it comes to performances, and static files should generally be served by a static HTTP server."
msgstr ""
#: ../../content/administration/install/deploy.rst:410
#: ../../content/administration/install/deploy.rst:406
msgid "Serving static files"
msgstr ""
#: ../../content/administration/install/deploy.rst:412
#: ../../content/administration/install/deploy.rst:408
msgid "Odoo static files are located in each module's :file:`static/` folder, so static files can be served by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) in the various addons paths."
msgstr ""
#: ../../content/administration/install/deploy.rst:417
#: ../../content/administration/install/deploy.rst:413
msgid "Say Odoo has been installed via the **debian packages** for Community and Enterprise and the :option:`--addons-path <odoo-bin --addons-path>` is ``'/usr/lib/python3/dist-packages/odoo/addons'``."
msgstr ""
#: ../../content/administration/install/deploy.rst:420
#: ../../content/administration/install/deploy.rst:442
#: ../../content/administration/install/deploy.rst:416
#: ../../content/administration/install/deploy.rst:438
msgid "Using the above NGINX (https) configuration, the following location block should be added to serve static files via NGINX."
msgstr ""
#: ../../content/administration/install/deploy.rst:437
#: ../../content/administration/install/deploy.rst:433
msgid "Say Odoo has been installed via the **source**. The two git repositories for Community and Enterprise have been cloned in :file:`/opt/odoo/community` and :file:`/opt/odoo/enterprise` respectively and the :option:`--addons-path <odoo-bin --addons-path>` is ``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``."
msgstr ""
#: ../../content/administration/install/deploy.rst:459
#: ../../content/administration/install/deploy.rst:455
msgid "The actual NGINX configuration you need is highly dependent on your own installation. The two above snippets only highlight two possible configurations and may not be used as-is."
msgstr ""
#: ../../content/administration/install/deploy.rst:463
#: ../../content/administration/install/deploy.rst:459
msgid "Serving attachments"
msgstr ""
#: ../../content/administration/install/deploy.rst:465
#: ../../content/administration/install/deploy.rst:461
msgid "Attachments are files stored in the filestore which access is regulated by Odoo. They cannot be directly accessed via a static web server as accessing them requires multiple lookups in the database to determine where the files are stored and whether the current user can access them or not."
msgstr ""
#: ../../content/administration/install/deploy.rst:470
#: ../../content/administration/install/deploy.rst:466
msgid "Nevertheless, once the file has been located and the access rights verified by Odoo, it is a good idea to serve the file using the static web server instead of Odoo. For Odoo to delegate serving files to the static web server, the `X-Sendfile <https://tn123.org/mod_xsendfile/>`_ (apache) or `X-Accel <https://www.nginx.com/resources/wiki/start/topics/examples/x-accel/>`_ (nginx) extensions must be enabled and configured on the static web server. Once it is set up, start Odoo with the :option:`--x-sendfile <odoo-bin --x-sendfile>` CLI flag (this unique flag is used for both X-Sendfile and X-Accel)."
msgstr ""
#: ../../content/administration/install/deploy.rst:480
#: ../../content/administration/install/deploy.rst:476
msgid "The X-Sendfile extension for apache (and compatible web servers) does not require any supplementary configuration."
msgstr ""
#: ../../content/administration/install/deploy.rst:482
#: ../../content/administration/install/deploy.rst:478
msgid "The X-Accel extension for NGINX **does** require the following additionnal configuration:"
msgstr ""
#: ../../content/administration/install/deploy.rst:491
#: ../../content/administration/install/deploy.rst:487
msgid "In case you don't know what is the path to your filestore, start Odoo with the :option:`--x-sendfile <odoo-bin --x-sendfile>` option and navigate to the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via NGINX). This logs a warnings, the message contains the configuration you need."
msgstr ""
#: ../../content/administration/install/deploy.rst:500
#: ../../content/administration/install/deploy.rst:496
msgid "Security"
msgstr ""
#: ../../content/administration/install/deploy.rst:502
#: ../../content/administration/install/deploy.rst:498
msgid "For starters, keep in mind that securing an information system is a continuous process, not a one-shot operation. At any moment, you will only be as secure as the weakest link in your environment."
msgstr ""
#: ../../content/administration/install/deploy.rst:506
#: ../../content/administration/install/deploy.rst:502
msgid "So please do not take this section as the ultimate list of measures that will prevent all security problems. It's only intended as a summary of the first important things you should be sure to include in your security action plan. The rest will come from best security practices for your operating system and distribution, best practices in terms of users, passwords, and access control management, etc."
msgstr ""
#: ../../content/administration/install/deploy.rst:512
#: ../../content/administration/install/deploy.rst:508
msgid "When deploying an internet-facing server, please be sure to consider the following security-related topics:"
msgstr ""
#: ../../content/administration/install/deploy.rst:515
#: ../../content/administration/install/deploy.rst:511
msgid "Always set a strong super-admin admin password, and restrict access to the database management pages as soon as the system is set up. See :ref:`db_manager_security`."
msgstr ""
#: ../../content/administration/install/deploy.rst:518
#: ../../content/administration/install/deploy.rst:514
msgid "Choose unique logins and strong passwords for all administrator accounts on all databases. Do not use 'admin' as the login. Do not use those logins for day-to-day operations, only for controlling/managing the installation. *Never* use any default passwords like admin/admin, even for test/staging databases."
msgstr ""
#: ../../content/administration/install/deploy.rst:523
#: ../../content/administration/install/deploy.rst:519
msgid "Do **not** install demo data on internet-facing servers. Databases with demo data contain default logins and passwords that can be used to get into your systems and cause significant trouble, even on staging/dev systems."
msgstr ""
#: ../../content/administration/install/deploy.rst:527
#: ../../content/administration/install/deploy.rst:523
msgid "Use appropriate database filters ( :option:`--db-filter <odoo-bin --db-filter>`) to restrict the visibility of your databases according to the hostname. See :ref:`db_filter`. You may also use :option:`-d <odoo-bin -d>` to provide your own (comma-separated) list of available databases to filter from, instead of letting the system fetch them all from the database backend."
msgstr ""
#: ../../content/administration/install/deploy.rst:534
#: ../../content/administration/install/deploy.rst:530
msgid "Once your ``db_name`` and ``db_filter`` are configured and only match a single database per hostname, you should set ``list_db`` configuration option to ``False``, to prevent listing databases entirely, and to block access to the database management screens (this is also exposed as the :option:`--no-database-list <odoo-bin --no-database-list>` command-line option)"
msgstr ""
#: ../../content/administration/install/deploy.rst:540
#: ../../content/administration/install/deploy.rst:536
msgid "Make sure the PostgreSQL user (:option:`--db_user <odoo-bin --db_user>`) is *not* a super-user, and that your databases are owned by a different user. For example they could be owned by the ``postgres`` super-user if you are using a dedicated non-privileged ``db_user``. See also :ref:`setup/deploy/odoo`."
msgstr ""
#: ../../content/administration/install/deploy.rst:545
#: ../../content/administration/install/deploy.rst:541
msgid "Keep installations updated by regularly installing the latest builds, either via GitHub or by downloading the latest version from https://www.odoo.com/page/download or http://nightly.odoo.com"
msgstr ""
#: ../../content/administration/install/deploy.rst:549
#: ../../content/administration/install/deploy.rst:545
msgid "Configure your server in multi-process mode with proper limits matching your typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`."
msgstr ""
#: ../../content/administration/install/deploy.rst:552
#: ../../content/administration/install/deploy.rst:548
msgid "Run Odoo behind a web server providing HTTPS termination with a valid SSL certificate, in order to prevent eavesdropping on cleartext communications. SSL certificates are cheap, and many free options exist. Configure the web proxy to limit the size of requests, set appropriate timeouts, and then enable the :option:`proxy mode <odoo-bin --proxy-mode>` option. See also :ref:`https_proxy`."
msgstr ""
#: ../../content/administration/install/deploy.rst:559
#: ../../content/administration/install/deploy.rst:555
msgid "If you need to allow remote SSH access to your servers, make sure to set a strong password for **all** accounts, not just `root`. It is strongly recommended to entirely disable password-based authentication, and only allow public key authentication. Also consider restricting access via a VPN, allowing only trusted IPs in the firewall, and/or running a brute-force detection system such as `fail2ban` or equivalent."
msgstr ""
#: ../../content/administration/install/deploy.rst:565
#: ../../content/administration/install/deploy.rst:561
msgid "Consider installing appropriate rate-limiting on your proxy or firewall, to prevent brute-force attacks and denial of service attacks. See also :ref:`login_brute_force` for specific measures."
msgstr ""
#: ../../content/administration/install/deploy.rst:569
#: ../../content/administration/install/deploy.rst:565
msgid "Many network providers provide automatic mitigation for Distributed Denial of Service attacks (DDOS), but this is often an optional service, so you should consult with them."
msgstr ""
#: ../../content/administration/install/deploy.rst:573
#: ../../content/administration/install/deploy.rst:569
msgid "Whenever possible, host your public-facing demo/test/staging instances on different machines than the production ones. And apply the same security precautions as for production."
msgstr ""
#: ../../content/administration/install/deploy.rst:577
#: ../../content/administration/install/deploy.rst:573
msgid "If your public-facing Odoo server has access to sensitive internal network resources or services (e.g. via a private VLAN), implement appropriate firewall rules to protect those internal resources. This will ensure that the Odoo server cannot be used accidentally (or as a result of malicious user actions) to access or disrupt those internal resources. Typically this can be done by applying an outbound default DENY rule on the firewall, then only explicitly authorizing access to internal resources that the Odoo server needs to access. `Systemd IP traffic access control <http://0pointer.net/blog/ip-accounting-and-access-lists-with-systemd.html>`_ may also be useful to implement per-process network access control."
msgstr ""
#: ../../content/administration/install/deploy.rst:588
#: ../../content/administration/install/deploy.rst:584
msgid "If your public-facing Odoo server is behind a Web Application Firewall, a load-balancer, a transparent DDoS protection service (like CloudFlare) or a similar network-level device, you may wish to avoid direct access to the Odoo system. It is generally difficult to keep the endpoint IP addresses of your Odoo servers secret. For example they can appear in web server logs when querying public systems, or in the headers of emails posted from Odoo. In such a situation you may want to configure your firewall so that the endpoints are not accessible publicly except from the specific IP addresses of your WAF, load-balancer or proxy service. Service providers like CloudFlare usually maintain a public list of their IP address ranges for this purpose."
msgstr ""
#: ../../content/administration/install/deploy.rst:599
#: ../../content/administration/install/deploy.rst:595
msgid "If you are hosting multiple customers, isolate customer data and files from each other using containers or appropriate \"jail\" techniques."
msgstr ""
#: ../../content/administration/install/deploy.rst:602
#: ../../content/administration/install/deploy.rst:598
msgid "Setup daily backups of your databases and filestore data, and copy them to a remote archiving server that is not accessible from the server itself."
msgstr ""
#: ../../content/administration/install/deploy.rst:601
msgid "Deploying Odoo on Linux is strongly recommended over Windows. Should you choose nevertheless to deploy on a Windows platform, a thorough security hardening review of the server should be conducted and is outside of the scope of this guide."
msgstr ""
#: ../../content/administration/install/deploy.rst:609
msgid "Blocking Brute Force Attacks"
msgstr ""
@ -1043,27 +1023,31 @@ msgstr ""
msgid "Windows"
msgstr ""
#: ../../content/administration/install/packages.rst:150
#: ../../content/administration/install/packages.rst:151
msgid "Windows packaging is offered for the convenience of testing or running single-user local instances but production deployment is discouraged due to a number of limitations and risks associated with deploying Odoo on a Windows platform."
msgstr ""
#: ../../content/administration/install/packages.rst:155
msgid "Download the installer from the `nightly server <https://nightly.odoo.com>`_ (Community only) or the Windows installer from the `Odoo download page <https://www.odoo.com/page/download>`_ (any edition."
msgstr ""
#: ../../content/administration/install/packages.rst:153
#: ../../content/administration/install/packages.rst:158
msgid "Execute the downloaded file."
msgstr ""
#: ../../content/administration/install/packages.rst:156
#: ../../content/administration/install/packages.rst:161
msgid "On Windows 8 and later, a warning titled *Windows protected your PC* may be displayed. Click **More Info** and then **Run anyway** to proceed."
msgstr ""
#: ../../content/administration/install/packages.rst:159
#: ../../content/administration/install/packages.rst:164
msgid "Accept the `UAC <https://en.wikipedia.org/wiki/User_Account_Control>`_ prompt."
msgstr ""
#: ../../content/administration/install/packages.rst:160
#: ../../content/administration/install/packages.rst:165
msgid "Go through the installation steps."
msgstr ""
#: ../../content/administration/install/packages.rst:162
#: ../../content/administration/install/packages.rst:167
msgid "Odoo launches automatically at the end of the installation."
msgstr ""
@ -1638,32 +1622,144 @@ msgstr ""
msgid "Finally, click :guilabel:`Test Connection`. A confirmation message should appear. The Odoo database can now send safe, secure emails through Microsoft Outlook using OAuth authentication."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:192
msgid "Multiple user configuration"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:194
msgid "Each user should have a separate server set up. The :guilabel:`from-filter` should be set so that only the user's email is sent from that server. In other words, only a user with an email address that matches the set :guilabel:`from-filter` is able to use this server."
msgid "Configuration with a single outgoing mail server"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:198
msgid "After setting the :guilabel:`from-filter`, set up a fallback email account to allow for the sending of :guilabel:`notifications`. The fallback email must be configured as a :guilabel:`general transactional server`. The :guilabel:`mail.default.from` system parameter must be set to the :guilabel:`username` of the general transactional server account. For more information see :ref:`Use a default email address <email_communication/default>`."
#: ../../content/administration/maintain/azure_oauth.rst:196
msgid "Configuring a single outgoing server is the simplest configuration available for Microsoft Azure and it doesn't require extensive access rights for the users in the database."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:205
#: ../../content/administration/maintain/mailjet_api.rst:213
msgid "The :guilabel:`System Parameters` can be accessed by activating :doc:`../../applications/general/developer_mode` in the :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu."
#: ../../content/administration/maintain/azure_oauth.rst:199
msgid "A generic email address would be used to send emails for all users within the database. For example it could be structured with a `notifications` alias (`notifications@example.com`) or `contact` alias (`contact@example.com`). This address must be set as the :guilabel:`FROM Filtering` on the server. This address must also match the `{mail.default.from}@{mail.catchall.domain}` key combination in the system parameters."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:210
msgid "Configure incoming email server"
#: ../../content/administration/maintain/azure_oauth.rst:206
#: ../../content/administration/maintain/azure_oauth.rst:247
msgid "For more information on the from filter visit: :ref:`email_communication/default`."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:209
#: ../../content/administration/maintain/azure_oauth.rst:254
msgid "The :guilabel:`System Parameters` can be accessed by activating :ref:`developer-mode` in the :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:212
msgid "When using this configuration, every email that is sent from the database will use the address of the configured `notification` mailbox. However it should be noted that the name of the sender will appear but their email address will change:"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:-1
msgid "Name from real sender with static email."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:221
msgid "Single outgoing mail server configuration:"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:223
msgid "Outgoing mail server **username** (login) = `notifications@example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:224
msgid "Outgoing mail server :guilabel:`FROM Filtering` = `notifications@example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:225
#: ../../content/administration/maintain/azure_oauth.rst:279
msgid "`mail.catchall.domain` in system parameters = `example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:226
#: ../../content/administration/maintain/azure_oauth.rst:280
msgid "`mail.default.from` in system parameters = `notifications`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:229
msgid "User-specific (multiple user) configuration"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:231
msgid "In addition to a generic email server, individual email servers can be set up for users in a database. These email addresses must be set as the :guilabel:`FROM Filtering` on each individual server for this configuration to work."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:235
msgid "This configuration is the more difficult of the two Microsoft Azure configurations, in that it requires all users configured with email servers to have access rights to settings in order to establish a connection to the email server."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:240
#: ../../content/administration/odoo_sh/getting_started/branches.rst:480
msgid "Setup"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:242
msgid "Each user should have a separate email server set up. The :guilabel:`FROM Filtering` should be set so that only the user's email is sent from that server. In other words, only a user with an email address that matches the set :guilabel:`FROM Filtering` is able to use this server."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:249
msgid "A :ref:`fallback server <azure_oauth/notifications>` must be setup to allow for the sending of :guilabel:`notifications`. The :guilabel:`FROM Filtering` for this server should have the value of the `{mail.default.from}@{mail.catchall.domain}`."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:258
msgid "The configuration for this transactional email server can work alongside an outgoing mass-mailing email server. The :guilabel:`FROM Filtering` for the mass-mailing email server can remain empty, but it's require to be added in the settings of the *Email Marketing* application."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:263
msgid "For more information on setting the mass-mailing email server visit :ref:`email_communication/mass_mails`."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:267
msgid "Multiple user outgoing mail server configuration:"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:270
msgid "User #1 mailbox"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:270
msgid "Outgoing mail server #1 **username** (login) = `john@example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:271
msgid "Outgoing mail server #1 :guilabel:`FROM Filtering` = `john@example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:273
msgid "User #2 mailbox"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:273
msgid "Outgoing mail server #2 **username** (login) = `jane@example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:274
msgid "Outgoing mail server #2 :guilabel:`FROM Filtering` = `jane@example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:276
msgid "Notifications mailbox"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:276
msgid "Outgoing mail server #3 **username** (login) = `notifications@example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:277
msgid "Outgoing mail server #3 :guilabel:`FROM Filtering` = `notifications@example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:279
msgid "System Parameters"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:283
msgid "Configure incoming email server"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:285
msgid "The incoming account should be configured in a similar way to the outgoing email account. Navigate to the :guilabel:`Incoming Mail Servers` in the :guilabel:`Technical Menu` and :guilabel:`Create` a new configuration. Check or Select the button next to :guilabel:`Outlook Oauth Authentication` and enter the :guilabel:`Microsoft Outlook username`. Click on :guilabel:`Connect your Outlook account`. Odoo will state: :guilabel:`Outlook Token Valid` Now :guilabel:`Test and Confirm` the account. The account should be ready to receive email to the Odoo database."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:220
#: ../../content/administration/maintain/azure_oauth.rst:293
msgid ":doc:`../../applications/general/email_communication/email_servers`"
msgstr ""
@ -2828,6 +2924,10 @@ msgstr ""
msgid "For more information see :ref:`Using a default email address <email_communication/default>`."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:213
msgid "The :guilabel:`System Parameters` can be accessed by activating :doc:`../../applications/general/developer_mode` in the :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:217
msgid "Once the setup is complete, the Odoo database is ready to use the Mailjet email server for mass mailing or transactional emails!"
msgstr ""
@ -3559,7 +3659,7 @@ msgid "If you have originally installed Odoo with the \"tarball\" version (sourc
msgstr ""
#: ../../content/administration/maintain/update.rst:113
msgid "You will get a folder labelled with the version of the source code, for example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" and the actual source code folder named \"odoo\" (for Odoo 10 and later) or \"openerp\" for older versions. You can ignore the odoo.egg-info folder. Locate the folder where your current installation is deployed, and replace it with the newer \"odoo\" or \"openerp\" folder that was in the archive you just extracted."
msgid "You will get a folder labeled with the version of the source code, for example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" and the actual source code folder named \"odoo\" (for Odoo 10 and later) or \"openerp\" for older versions. You can ignore the odoo.egg-info folder. Locate the folder where your current installation is deployed, and replace it with the newer \"odoo\" or \"openerp\" folder that was in the archive you just extracted."
msgstr ""
#: ../../content/administration/maintain/update.rst:119
@ -4530,10 +4630,6 @@ msgstr ""
msgid "SSH"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:480
msgid "Setup"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:482
msgid "In order to use SSH, you have to set up your profile SSH public key (if it is not already done). To do so, follow these steps:"
msgstr ""

442
locale/sources/developer.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-09-12 13:54+0000\n"
"POT-Creation-Date: 2023-10-09 13:19+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1442,7 +1442,7 @@ msgstr ""
#: ../../content/developer/howtos/provide_iap_services.rst:440
#: ../../content/developer/reference/backend/reports.rst:198
#: ../../content/developer/reference/extract_api.rst:546
#: ../../content/developer/reference/extract_api.rst:509
msgid "``description``"
msgstr ""
@ -2938,7 +2938,7 @@ msgstr ""
#: ../../content/developer/howtos/website_themes/forms.rst:75
#: ../../content/developer/reference/extract_api.rst:194
#: ../../content/developer/reference/extract_api.rst:752
#: ../../content/developer/reference/extract_api.rst:712
msgid "Success"
msgstr ""
@ -5278,7 +5278,7 @@ msgstr ""
#: ../../content/developer/reference/backend/views.rst:2160
#: ../../content/developer/reference/external_api.rst:1104
#: ../../content/developer/reference/external_api.rst:1268
#: ../../content/developer/reference/extract_api.rst:569
#: ../../content/developer/reference/extract_api.rst:529
#: ../../content/developer/reference/frontend/services.rst:871
#: ../../content/developer/tutorials/web.rst:1320
msgid "``name``"
@ -5587,8 +5587,8 @@ msgstr ""
#: ../../content/developer/reference/backend/data.rst:242
#: ../../content/developer/reference/backend/views.rst:675
#: ../../content/developer/reference/extract_api.rst:171
#: ../../content/developer/reference/extract_api.rst:300
#: ../../content/developer/reference/extract_api.rst:737
#: ../../content/developer/reference/extract_api.rst:290
#: ../../content/developer/reference/extract_api.rst:697
msgid "``id``"
msgstr ""
@ -6305,7 +6305,7 @@ msgid "comma-separated list of group :term:`external identifiers`"
msgstr ""
#: ../../content/developer/reference/backend/data.rst:253
#: ../../content/developer/reference/extract_api.rst:417
#: ../../content/developer/reference/extract_api.rst:380
msgid "``page``"
msgstr ""
@ -6621,8 +6621,8 @@ msgstr ""
#: ../../content/developer/reference/backend/http.rst:64
#: ../../content/developer/reference/extract_api.rst:78
#: ../../content/developer/reference/extract_api.rst:248
#: ../../content/developer/reference/extract_api.rst:603
#: ../../content/developer/reference/extract_api.rst:244
#: ../../content/developer/reference/extract_api.rst:563
msgid "Request"
msgstr ""
@ -6632,8 +6632,8 @@ msgstr ""
#: ../../content/developer/reference/backend/http.rst:81
#: ../../content/developer/reference/extract_api.rst:165
#: ../../content/developer/reference/extract_api.rst:290
#: ../../content/developer/reference/extract_api.rst:731
#: ../../content/developer/reference/extract_api.rst:280
#: ../../content/developer/reference/extract_api.rst:691
msgid "Response"
msgstr ""
@ -9268,7 +9268,7 @@ msgid "record for the current ``user``'s company"
msgstr ""
#: ../../content/developer/reference/backend/reports.rst:35
#: ../../content/developer/reference/extract_api.rst:507
#: ../../content/developer/reference/extract_api.rst:470
msgid "``website``"
msgstr ""
@ -10338,7 +10338,7 @@ msgid "when working on a failing test, it is common to add the debug flag, then
msgstr ""
#: ../../content/developer/reference/backend/testing.rst:537
#: ../../content/developer/reference/extract_api.rst:771
#: ../../content/developer/reference/extract_api.rst:731
msgid "Integration Testing"
msgstr ""
@ -12663,7 +12663,7 @@ msgstr ""
#: ../../content/developer/reference/backend/views.rst:1295
#: ../../content/developer/reference/backend/views.rst:1305
#: ../../content/developer/reference/extract_api.rst:621
#: ../../content/developer/reference/extract_api.rst:581
msgid "``values``"
msgstr ""
@ -15218,7 +15218,7 @@ msgid "You can either use this service directly in the Accounting, Expense, or R
msgstr ""
#: ../../content/developer/reference/extract_api.rst:24
msgid "The extract API uses the JSON-RPC2_ protocol; its endpoint routes are located at `https://iap-extract.odoo.com`."
msgid "The extract API uses the JSON-RPC2_ protocol; its endpoint routes are located at `https://extract.api.odoo.com`."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:28
@ -15290,7 +15290,7 @@ msgstr ""
#: ../../content/developer/reference/extract_api.rst:69
#: ../../content/developer/reference/extract_api.rst:235
#: ../../content/developer/reference/extract_api.rst:591
#: ../../content/developer/reference/extract_api.rst:551
msgid "Routes"
msgstr ""
@ -15315,8 +15315,8 @@ msgid "|ss| /iap/expense_extract/parse |se| (deprecated)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:82
#: ../../content/developer/reference/extract_api.rst:252
#: ../../content/developer/reference/extract_api.rst:607
#: ../../content/developer/reference/extract_api.rst:248
#: ../../content/developer/reference/extract_api.rst:567
msgid "``jsonrpc`` (required)"
msgstr ""
@ -15325,33 +15325,33 @@ msgstr ""
#: ../../content/developer/reference/extract_api.rst:87
#: ../../content/developer/reference/extract_api.rst:170
#: ../../content/developer/reference/extract_api.rst:172
#: ../../content/developer/reference/extract_api.rst:249
#: ../../content/developer/reference/extract_api.rst:251
#: ../../content/developer/reference/extract_api.rst:253
#: ../../content/developer/reference/extract_api.rst:255
#: ../../content/developer/reference/extract_api.rst:257
#: ../../content/developer/reference/extract_api.rst:299
#: ../../content/developer/reference/extract_api.rst:301
#: ../../content/developer/reference/extract_api.rst:608
#: ../../content/developer/reference/extract_api.rst:610
#: ../../content/developer/reference/extract_api.rst:612
#: ../../content/developer/reference/extract_api.rst:736
#: ../../content/developer/reference/extract_api.rst:738
#: ../../content/developer/reference/extract_api.rst:289
#: ../../content/developer/reference/extract_api.rst:291
#: ../../content/developer/reference/extract_api.rst:568
#: ../../content/developer/reference/extract_api.rst:570
#: ../../content/developer/reference/extract_api.rst:572
#: ../../content/developer/reference/extract_api.rst:696
#: ../../content/developer/reference/extract_api.rst:698
msgid "see JSON-RPC2_"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:84
#: ../../content/developer/reference/extract_api.rst:254
#: ../../content/developer/reference/extract_api.rst:609
#: ../../content/developer/reference/extract_api.rst:250
#: ../../content/developer/reference/extract_api.rst:569
msgid "``method`` (required)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:86
#: ../../content/developer/reference/extract_api.rst:256
#: ../../content/developer/reference/extract_api.rst:611
#: ../../content/developer/reference/extract_api.rst:252
#: ../../content/developer/reference/extract_api.rst:571
msgid "``id`` (required)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:136
#: ../../content/developer/reference/extract_api.rst:268
#: ../../content/developer/reference/extract_api.rst:264
msgid "``params``"
msgstr ""
@ -15464,19 +15464,19 @@ msgid "The ``user_infos`` parameter is optional but it greatly improves the qual
msgstr ""
#: ../../content/developer/reference/extract_api.rst:169
#: ../../content/developer/reference/extract_api.rst:298
#: ../../content/developer/reference/extract_api.rst:735
#: ../../content/developer/reference/extract_api.rst:288
#: ../../content/developer/reference/extract_api.rst:695
msgid "``jsonrpc``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:189
#: ../../content/developer/reference/extract_api.rst:319
#: ../../content/developer/reference/extract_api.rst:747
#: ../../content/developer/reference/extract_api.rst:309
#: ../../content/developer/reference/extract_api.rst:707
msgid "``result``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:174
#: ../../content/developer/reference/extract_api.rst:259
#: ../../content/developer/reference/extract_api.rst:255
msgid "Dictionary containing the following content."
msgstr ""
@ -15489,8 +15489,8 @@ msgid "The code indicating the status of the request. \"success\" in case of suc
msgstr ""
#: ../../content/developer/reference/extract_api.rst:181
#: ../../content/developer/reference/extract_api.rst:311
#: ../../content/developer/reference/extract_api.rst:744
#: ../../content/developer/reference/extract_api.rst:301
#: ../../content/developer/reference/extract_api.rst:704
msgid "``status_msg``"
msgstr ""
@ -15504,12 +15504,12 @@ msgstr ""
#: ../../content/developer/reference/extract_api.rst:184
#: ../../content/developer/reference/extract_api.rst:189
#: ../../content/developer/reference/extract_api.rst:314
#: ../../content/developer/reference/extract_api.rst:304
msgid "Only present if the request is successful."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:186
#: ../../content/developer/reference/extract_api.rst:747
#: ../../content/developer/reference/extract_api.rst:707
msgid "``status_code`` (deprecated)"
msgstr ""
@ -15518,7 +15518,7 @@ msgid "The code indicating the status of the request. 0 in case of success. Othe
msgstr ""
#: ../../content/developer/reference/extract_api.rst:189
#: ../../content/developer/reference/extract_api.rst:627
#: ../../content/developer/reference/extract_api.rst:587
msgid "``document_id`` (deprecated)"
msgstr ""
@ -15528,22 +15528,22 @@ msgid "status"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:192
#: ../../content/developer/reference/extract_api.rst:750
#: ../../content/developer/reference/extract_api.rst:710
msgid "status_msg"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:192
#: ../../content/developer/reference/extract_api.rst:750
#: ../../content/developer/reference/extract_api.rst:710
msgid "status_code (deprecated)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:194
#: ../../content/developer/reference/extract_api.rst:752
#: ../../content/developer/reference/extract_api.rst:712
msgid "`success`"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:194
#: ../../content/developer/reference/extract_api.rst:752
#: ../../content/developer/reference/extract_api.rst:712
msgid "0"
msgstr ""
@ -15617,535 +15617,505 @@ msgid "/api/extract/invoice/1/get_result"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:238
msgid "/api/extract/invoice/1/get_result_batch"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:239
msgid "/api/extract/expense/1/get_result"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:240
msgid "/api/extract/expense/1/get_result_batch"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:241
#: ../../content/developer/reference/extract_api.rst:239
msgid "/api/extract/applicant/1/get_result"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:242
msgid "/api/extract/applicant/1/get_result_batch"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:243
msgid "|ss| /api/extract/invoice/1/get_results |se| (deprecated)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:244
#: ../../content/developer/reference/extract_api.rst:240
msgid "|ss| /iap/invoice_extract/get_result |se| (deprecated)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:245
#: ../../content/developer/reference/extract_api.rst:241
msgid "|ss| /iap/expense_extract/get_result |se| (deprecated)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:263
#: ../../content/developer/reference/extract_api.rst:259
msgid "``version`` (required)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:264
#: ../../content/developer/reference/extract_api.rst:308
#: ../../content/developer/reference/extract_api.rst:310
#: ../../content/developer/reference/extract_api.rst:312
#: ../../content/developer/reference/extract_api.rst:619
#: ../../content/developer/reference/extract_api.rst:624
#: ../../content/developer/reference/extract_api.rst:743
#: ../../content/developer/reference/extract_api.rst:745
#: ../../content/developer/reference/extract_api.rst:747
#: ../../content/developer/reference/extract_api.rst:260
#: ../../content/developer/reference/extract_api.rst:298
#: ../../content/developer/reference/extract_api.rst:300
#: ../../content/developer/reference/extract_api.rst:302
#: ../../content/developer/reference/extract_api.rst:579
#: ../../content/developer/reference/extract_api.rst:584
#: ../../content/developer/reference/extract_api.rst:703
#: ../../content/developer/reference/extract_api.rst:705
#: ../../content/developer/reference/extract_api.rst:707
msgid "|SAME_AS_PARSE|"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:265
msgid "``documents_uuids`` (required, replaces ``documents_ids``)"
#: ../../content/developer/reference/extract_api.rst:261
msgid "``documents_uuid`` (required, replaces ``documents_id``)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:266
#: ../../content/developer/reference/extract_api.rst:268
msgid "The list of ``document_id`` for which you want to get the current parsing status."
#: ../../content/developer/reference/extract_api.rst:262
msgid "The ``document_uuid`` for which you want to get the current parsing status."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:268
msgid "``documents_ids`` (deprecated)"
#: ../../content/developer/reference/extract_api.rst:264
msgid "``documents_id`` (deprecated)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:284
msgid "The code snippet shows the request to the ``/api/extract/invoice/1/get_result_batch`` route. You can use the endpoint ``/api/extract/invoice/1/get_result`` to get the result of a single document. In that case, you don't need to provide a list of ``document_uuids`` but a single ``document_uuid``."
#: ../../content/developer/reference/extract_api.rst:264
msgid "The ``document_id`` for which you want to get the current parsing status."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:292
#: ../../content/developer/reference/extract_api.rst:282
msgid "When getting the results from the parse, the detected field vary a lot depending on the type of document. Each response is a list of dictionaries, one for each document. The keys of the dictionary are the name of the field and the value is the value of the field."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:303
#: ../../content/developer/reference/extract_api.rst:293
msgid "Dictionary where each key is a document_id. For each ``document_id``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:307
#: ../../content/developer/reference/extract_api.rst:742
#: ../../content/developer/reference/extract_api.rst:297
#: ../../content/developer/reference/extract_api.rst:702
msgid "``status``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:309
#: ../../content/developer/reference/extract_api.rst:299
msgid "``status_code``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:319
#: ../../content/developer/reference/extract_api.rst:309
msgid "``results``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:319
#: ../../content/developer/reference/extract_api.rst:309
msgid "``full_text_annotation``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:319
#: ../../content/developer/reference/extract_api.rst:309
msgid "Contains the unprocessed full result from the OCR for the document"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:360
msgid "The example shows the response from the ``/api/extract/invoice/1/get_result_batch`` route. When using the ``/api/extract/invoice/1/get_result`` route (note the singularity), the response will be the value of the key associated to the invoice."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:365
msgid "Result keys are strings despite the fact that the ``document_ids`` given in the request body are integers."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:370
#: ../../content/developer/reference/extract_api.rst:333
msgid "Common fields"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:375
#: ../../content/developer/reference/extract_api.rst:338
msgid "``feature_result``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:377
#: ../../content/developer/reference/extract_api.rst:340
msgid "Each field of interest we want to extract from the document such as the total or the due date are also called **features**. An exhaustive list of all the extracted features associated to a type of document can be found in the sections below."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:381
#: ../../content/developer/reference/extract_api.rst:344
msgid "For each feature, we return a list of candidates and we spotlight the candidate our model predicts to be the best fit for the feature."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:386
#: ../../content/developer/reference/extract_api.rst:349
msgid "``selected_value`` (optional)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:387
#: ../../content/developer/reference/extract_api.rst:350
msgid "The best candidate for this feature."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:388
#: ../../content/developer/reference/extract_api.rst:351
msgid "``selected_values`` (optional)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:389
#: ../../content/developer/reference/extract_api.rst:352
msgid "The best candidates for this feature."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:391
#: ../../content/developer/reference/extract_api.rst:354
msgid "``candidates`` (optional)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:391
#: ../../content/developer/reference/extract_api.rst:354
msgid "List of all the candidates for this feature ordered by decreasing confidence score."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:401
#: ../../content/developer/reference/extract_api.rst:364
msgid "candidate"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:403
#: ../../content/developer/reference/extract_api.rst:366
msgid "For each candidate we give its representation and position in the document. Candidates are sorted by decreasing order of suitability."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:408
#: ../../content/developer/reference/extract_api.rst:371
msgid "``content``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:409
#: ../../content/developer/reference/extract_api.rst:372
msgid "Representation of the candidate."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:414
#: ../../content/developer/reference/extract_api.rst:377
msgid "``coords``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:413
#: ../../content/developer/reference/extract_api.rst:376
msgid "``[center_x, center_y, width, height, rotation_angle]``. The position and dimensions are relative to the size of the page and are therefore between 0 and 1. The angle is a clockwise rotation measured in degrees."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:417
#: ../../content/developer/reference/extract_api.rst:380
msgid "Page of the original document on which the candidate is located (starts at 0)."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:432
#: ../../content/developer/reference/extract_api.rst:395
msgid "Invoices"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:434
#: ../../content/developer/reference/extract_api.rst:397
msgid "Invoices are complex and can have a lot of different fields. The following table gives an exhaustive list of all the fields we can extract from an invoice."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:438
#: ../../content/developer/reference/extract_api.rst:544
#: ../../content/developer/reference/extract_api.rst:567
#: ../../content/developer/reference/extract_api.rst:401
#: ../../content/developer/reference/extract_api.rst:507
#: ../../content/developer/reference/extract_api.rst:527
msgid "Feature name"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:438
#: ../../content/developer/reference/extract_api.rst:544
#: ../../content/developer/reference/extract_api.rst:567
#: ../../content/developer/reference/extract_api.rst:401
#: ../../content/developer/reference/extract_api.rst:507
#: ../../content/developer/reference/extract_api.rst:527
msgid "Specifities"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:440
#: ../../content/developer/reference/extract_api.rst:403
msgid "``SWIFT_code``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:440
#: ../../content/developer/reference/extract_api.rst:403
msgid "``content`` is a dictionary encoded as a string."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:442
#: ../../content/developer/reference/extract_api.rst:405
msgid "It contains information about the detected SWIFT code (or `BIC <https://www.iso9362.org/isobic/overview.html>`_)."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:445
#: ../../content/developer/reference/extract_api.rst:408
msgid "Keys:"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:449
#: ../../content/developer/reference/extract_api.rst:412
msgid "``bic``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:450
#: ../../content/developer/reference/extract_api.rst:413
msgid "detected BIC (string)."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:451
#: ../../content/developer/reference/extract_api.rst:414
msgid "``name`` (optional)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:452
#: ../../content/developer/reference/extract_api.rst:415
msgid "bank name (string)."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:453
#: ../../content/developer/reference/extract_api.rst:416
msgid "``country_code``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:454
#: ../../content/developer/reference/extract_api.rst:417
msgid "ISO3166 alpha-2 country code of the bank (string)."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:455
#: ../../content/developer/reference/extract_api.rst:418
msgid "``city`` (optional)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:456
#: ../../content/developer/reference/extract_api.rst:419
msgid "city of the bank (string)."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:458
#: ../../content/developer/reference/extract_api.rst:421
msgid "``verified_bic``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:458
#: ../../content/developer/reference/extract_api.rst:421
msgid "True if the BIC has been found in our DB (bool)."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:460
#: ../../content/developer/reference/extract_api.rst:423
msgid "Name and city are present only if verified_bic is true."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:462
#: ../../content/developer/reference/extract_api.rst:425
msgid "``iban``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:462
#: ../../content/developer/reference/extract_api.rst:425
#: ../../content/developer/reference/extract_api.rst:427
#: ../../content/developer/reference/extract_api.rst:429
#: ../../content/developer/reference/extract_api.rst:436
#: ../../content/developer/reference/extract_api.rst:438
#: ../../content/developer/reference/extract_api.rst:440
#: ../../content/developer/reference/extract_api.rst:444
#: ../../content/developer/reference/extract_api.rst:446
#: ../../content/developer/reference/extract_api.rst:448
#: ../../content/developer/reference/extract_api.rst:458
#: ../../content/developer/reference/extract_api.rst:464
#: ../../content/developer/reference/extract_api.rst:466
#: ../../content/developer/reference/extract_api.rst:473
#: ../../content/developer/reference/extract_api.rst:475
#: ../../content/developer/reference/extract_api.rst:477
#: ../../content/developer/reference/extract_api.rst:481
#: ../../content/developer/reference/extract_api.rst:483
#: ../../content/developer/reference/extract_api.rst:485
#: ../../content/developer/reference/extract_api.rst:495
#: ../../content/developer/reference/extract_api.rst:501
#: ../../content/developer/reference/extract_api.rst:503
#: ../../content/developer/reference/extract_api.rst:505
#: ../../content/developer/reference/extract_api.rst:507
#: ../../content/developer/reference/extract_api.rst:546
#: ../../content/developer/reference/extract_api.rst:548
#: ../../content/developer/reference/extract_api.rst:550
#: ../../content/developer/reference/extract_api.rst:554
#: ../../content/developer/reference/extract_api.rst:556
#: ../../content/developer/reference/extract_api.rst:569
#: ../../content/developer/reference/extract_api.rst:571
#: ../../content/developer/reference/extract_api.rst:573
#: ../../content/developer/reference/extract_api.rst:575
#: ../../content/developer/reference/extract_api.rst:468
#: ../../content/developer/reference/extract_api.rst:470
#: ../../content/developer/reference/extract_api.rst:509
#: ../../content/developer/reference/extract_api.rst:511
#: ../../content/developer/reference/extract_api.rst:513
#: ../../content/developer/reference/extract_api.rst:517
#: ../../content/developer/reference/extract_api.rst:529
#: ../../content/developer/reference/extract_api.rst:531
#: ../../content/developer/reference/extract_api.rst:533
#: ../../content/developer/reference/extract_api.rst:535
msgid "``content`` is a string"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:464
#: ../../content/developer/reference/extract_api.rst:427
msgid "``aba``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:466
#: ../../content/developer/reference/extract_api.rst:429
msgid "``VAT_Number``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:468
#: ../../content/developer/reference/extract_api.rst:431
msgid "Depending on the value of perspective in the user_infos, this will be the VAT number of the supplier or the client. If perspective is client, it'll be the supplier's VAT number. If it's supplier, it's the client's VAT number."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:473
#: ../../content/developer/reference/extract_api.rst:436
msgid "``qr-bill``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:475
#: ../../content/developer/reference/extract_api.rst:438
msgid "``payment_ref``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:477
#: ../../content/developer/reference/extract_api.rst:440
msgid "``purchase_order``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:479
#: ../../content/developer/reference/extract_api.rst:442
msgid "Uses ``selected_values`` instead of ``selected_value``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:481
#: ../../content/developer/reference/extract_api.rst:548
#: ../../content/developer/reference/extract_api.rst:444
#: ../../content/developer/reference/extract_api.rst:511
msgid "``country``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:483
#: ../../content/developer/reference/extract_api.rst:554
#: ../../content/developer/reference/extract_api.rst:446
#: ../../content/developer/reference/extract_api.rst:517
msgid "``currency``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:485
#: ../../content/developer/reference/extract_api.rst:550
#: ../../content/developer/reference/extract_api.rst:448
#: ../../content/developer/reference/extract_api.rst:513
msgid "``date``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:487
#: ../../content/developer/reference/extract_api.rst:450
msgid "Format : *YYYY-MM-DD*"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:489
#: ../../content/developer/reference/extract_api.rst:452
msgid "``due_date``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:489
#: ../../content/developer/reference/extract_api.rst:452
msgid "Same as for ``date``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:491
#: ../../content/developer/reference/extract_api.rst:454
msgid "``total_tax_amount`` (previously ``global_taxes_amount``)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:491
#: ../../content/developer/reference/extract_api.rst:497
#: ../../content/developer/reference/extract_api.rst:499
#: ../../content/developer/reference/extract_api.rst:552
#: ../../content/developer/reference/extract_api.rst:454
#: ../../content/developer/reference/extract_api.rst:460
#: ../../content/developer/reference/extract_api.rst:462
#: ../../content/developer/reference/extract_api.rst:515
msgid "``content`` is a float"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:495
#: ../../content/developer/reference/extract_api.rst:458
msgid "``invoice_id``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:497
#: ../../content/developer/reference/extract_api.rst:460
msgid "``subtotal``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:499
#: ../../content/developer/reference/extract_api.rst:552
#: ../../content/developer/reference/extract_api.rst:462
#: ../../content/developer/reference/extract_api.rst:515
msgid "``total``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:501
#: ../../content/developer/reference/extract_api.rst:464
msgid "``supplier``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:503
#: ../../content/developer/reference/extract_api.rst:466
msgid "``client``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:505
#: ../../content/developer/reference/extract_api.rst:571
#: ../../content/developer/reference/extract_api.rst:468
#: ../../content/developer/reference/extract_api.rst:531
msgid "``email``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:512
#: ../../content/developer/reference/extract_api.rst:475
msgid "``feature_result`` for the ``invoice_lines`` feature"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:514
#: ../../content/developer/reference/extract_api.rst:477
msgid "It follows a more specific structure. It is basically a list of dictionaries where each dictionary represents an invoice line. Each value follows a :ref:`latestextract_api/get_result/feature_result` structure."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:538
#: ../../content/developer/reference/extract_api.rst:501
msgid "Expense"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:540
#: ../../content/developer/reference/extract_api.rst:503
msgid "The expenses are less complex than invoices. The following table gives an exhaustive list of all the fields we can extract from an expense report."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:556
msgid "``bill_reference``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:561
#: ../../content/developer/reference/extract_api.rst:521
msgid "Applicant"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:563
#: ../../content/developer/reference/extract_api.rst:523
msgid "This third type of document is meant for processing resumes. The following table gives an exhaustive list of all the fields we can extract from a resume."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:573
#: ../../content/developer/reference/extract_api.rst:533
msgid "``phone``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:575
#: ../../content/developer/reference/extract_api.rst:535
msgid "``mobile``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:580
#: ../../content/developer/reference/extract_api.rst:540
msgid "Validate"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:582
#: ../../content/developer/reference/extract_api.rst:542
msgid "The validation step is an optional step but is strongly recommended. By telling the system if it were right or wrong for each feature you give an important feedback. It has no direct impact but it helps the system to greatly improve its prediction accuracy for the documents you will send in the future."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:593
#: ../../content/developer/reference/extract_api.rst:553
msgid "/api/extract/invoice/1/validate"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:594
#: ../../content/developer/reference/extract_api.rst:554
msgid "/api/extract/invoice/1/validate_batch"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:595
#: ../../content/developer/reference/extract_api.rst:555
msgid "/api/extract/expense/1/validate"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:596
#: ../../content/developer/reference/extract_api.rst:556
msgid "/api/extract/expense/1/validate_batch"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:597
#: ../../content/developer/reference/extract_api.rst:557
msgid "/api/extract/applicant/1/validate"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:598
#: ../../content/developer/reference/extract_api.rst:558
msgid "/api/extract/applicant/1/validate_batch"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:599
#: ../../content/developer/reference/extract_api.rst:559
msgid "|ss| /iap/invoice_extract/validate |se| (deprecated)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:600
#: ../../content/developer/reference/extract_api.rst:560
msgid "|ss| /iap/expense_extract/validate |se| (deprecated)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:627
#: ../../content/developer/reference/extract_api.rst:587
msgid "``params`` (``/validate`` route only)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:614
#: ../../content/developer/reference/extract_api.rst:630
#: ../../content/developer/reference/extract_api.rst:574
#: ../../content/developer/reference/extract_api.rst:590
msgid "dictionary containing the following fields"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:618
#: ../../content/developer/reference/extract_api.rst:578
msgid "``document_uuid`` (required, replaces ``document_id``)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:621
#: ../../content/developer/reference/extract_api.rst:581
msgid "Contains the validation for each feature. For invoices, the field ``merged_line`` indicates if the lines were merged or not."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:628
#: ../../content/developer/reference/extract_api.rst:588
msgid "``invoice_lines`` have been merged or not."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:636
#: ../../content/developer/reference/extract_api.rst:596
msgid "``params`` (``/validate_batch`` route only)"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:636
#: ../../content/developer/reference/extract_api.rst:596
msgid "``documents``"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:635
#: ../../content/developer/reference/extract_api.rst:595
msgid "Contains the validation for each feature for each document, the ``document_uuid`` are the keys and their values is the content of the ``value`` field of the ``/validate`` route."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:682
#: ../../content/developer/reference/extract_api.rst:642
msgid "You don't have to validate all the features in order for the validation to succeed. However :ref:`/validate <extract_api/validate>` can't be called multiple times for a same document. Therefore you should validate all the features you want to validate at once."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:687
#: ../../content/developer/reference/extract_api.rst:647
msgid "validation"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:689
#: ../../content/developer/reference/extract_api.rst:649
msgid "A **validation** for a given feature is a dictionary containing the textual representation of the expected value for this given feature. This format apply for all the features except for ``invoice_lines`` which has a more complex validation format."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:700
#: ../../content/developer/reference/extract_api.rst:660
msgid "invoice_lines"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:702
#: ../../content/developer/reference/extract_api.rst:662
msgid "**lines** is a list of dictionaries. Each dictionary represents an invoice line. The dictionary keys speak for themselves. Note that there is no ``content`` for this feature."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:750
#: ../../content/developer/reference/extract_api.rst:710
msgid "`status`"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:753
#: ../../content/developer/reference/extract_api.rst:713
msgid "`error_validation_format`"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:753
#: ../../content/developer/reference/extract_api.rst:713
msgid "Validation format is incorrect"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:753
#: ../../content/developer/reference/extract_api.rst:713
msgid "12"
msgstr ""
#: ../../content/developer/reference/extract_api.rst:773
#: ../../content/developer/reference/extract_api.rst:733
msgid "You can test your integration by using *integration_token* as ``account_token`` in the :ref:`/parse <extract_api/parse>` request."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:776
#: ../../content/developer/reference/extract_api.rst:736
msgid "Using this token put you in test mode and allows you to simulate the entire flow without really parsing a document and without being billed one credit for each successful **document** parsing."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:779
#: ../../content/developer/reference/extract_api.rst:739
msgid "The only technical differences in test mode is that the document you send is not parsed by the system and that the response you get from :ref:`/get_result <extract_api/get_result>` is a hard-coded one."
msgstr ""
#: ../../content/developer/reference/extract_api.rst:783
#: ../../content/developer/reference/extract_api.rst:743
msgid "A python implementation of the full flow for invoices can be found :download:`here <extract_api/implementation.py>`."
msgstr ""
@ -21522,7 +21492,7 @@ msgid "Creating safe content using :class:`~markupsafe.Markup`"
msgstr ""
#: ../../content/developer/reference/frontend/qweb.rst:378
msgid "See the official documentation for explanations, but the big advantage of :class:`~markupsafe.Markup` is that it's a very rich type overrinding :class:`str` operations to *automatically escape parameters*."
msgid "See the official documentation for explanations, but the big advantage of :class:`~markupsafe.Markup` is that it's a very rich type overriding :class:`str` operations to *automatically escape parameters*."
msgstr ""
#: ../../content/developer/reference/frontend/qweb.rst:382

3524
locale/sources/finance.pot
View File

File diff suppressed because it is too large Load Diff

644
locale/sources/general.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-09-12 13:54+0000\n"
"POT-Creation-Date: 2023-10-09 13:19+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1604,331 +1604,643 @@ msgid "In addition, when email is received to the catchall email address, Odoo w
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:3
msgid "Email Templates"
msgid "Email templates"
msgstr ""
#: ../../content/applications/general/email_communication/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."
msgid "Email templates are saved emails that are used repeatedly to send emails from the database. They allow users to send quality communications, without having to compose the same text repeatedly."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:12
msgid "The email templates use QWeb. The composer allows you to edit emails in their final rendering, making customizations more robust as you don’t have to edit code."
#: ../../content/applications/general/email_communication/email_template.rst:8
msgid "Creating different templates that are tailored to specific situations lets users choose the right message for the right audience. This increases the quality of the message and the overall engagement rate with the customer."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:16
msgid "Defining a default reply to on your mail template"
#: ../../content/applications/general/email_communication/email_template.rst:13
msgid "Email templates in Odoo use QWeb or XML, which allows for editing emails in their final rendering, making customizations more robust, without having to edit any code whatsoever. This means that Odoo can use a Graphical User Interface (GUI) to edit emails, which edits the backend code. When the received email is read by the end user's program, different formatting an graphics will appear in the final form of it."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:18
msgid "Although the field *reply to* is available within the mail templates, **this field is only used for mass mailing** mode (this means when sending templates on what we call bulk emailing). You can send emails in bulk in almost every app that has a list view. Select the records you want and click on the action button. If you have an option to send an email, you will see a mail composer with possible values to define:"
#: ../../content/applications/general/email_communication/email_template.rst:19
msgid "Access email templates in :ref:`developer mode <developer-mode>` by navigating to :menuselection:`Settings app --> Technical menu --> Email --> Email Templates`."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:23
msgid "Editing email templates"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:25
msgid "The *powerbox* feature can be used when working with email templates. This feature provides the ability to directly edit the formatting and text in an email template, as well as the ability to add links, buttons, appointment options, or images."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:29
msgid "Additionally, the XML/HTML code of the email template can be edited directly, via the :guilabel:`</>` icon. Dynamic placeholders (referencing fields within Odoo) are also available for use in the email template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:34
msgid "Powerbox"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:36
msgid "The *powerbox* feature is an enriched text editor with various formatting, layout, and text options. It can also be used to add XML/HTML features in an email template. The powerbox feature is activated by typing a forward slash `/` in the body of the email template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:40
msgid "When a forward slash `/` is typed in the body of an email template, a drop-down menu appears with the following options:"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:43
msgid ":guilabel:`Structure`"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:45
msgid ":guilabel:`Bulleted list`: Create a simple bulleted list."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:46
msgid ":guilabel:`Numbered list`: Create a list with numbering."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:47
msgid ":guilabel:`Checklist`: Track tasks with a checklist."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:48
msgid ":guilabel:`Table`: Insert a table."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:49
msgid ":guilabel:`Separator`: Insert a horizontal rule separator."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:50
msgid ":guilabel:`Quote`: Add a blockquote section."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:51
msgid ":guilabel:`Code`: Add a code section."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:52
msgid ":guilabel:`2 columns`: Convert into two columns."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:53
msgid ":guilabel:`3 columns`: Convert into three columns."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:54
msgid ":guilabel:`4 columns`: Convert into four columns."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:56
msgid ":guilabel:`Format`"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:58
msgid ":guilabel:`Heading 1`: Big section heading."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:59
msgid ":guilabel:`Heading 2`: Medium section heading."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:60
msgid ":guilabel:`Heading 3`: Small section heading."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:61
msgid ":guilabel:`Switch direction`: Switch the text's direction."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:62
msgid ":guilabel:`Text`: Paragraph block."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:64
msgid ":guilabel:`Media`"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:66
msgid ":guilabel:`Image`: Insert an image."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:67
msgid ":guilabel:`Article`: Link an article."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:69
msgid ":guilabel:`Navigation`"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:71
msgid ":guilabel:`Link`: Add a link."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:72
msgid ":guilabel:`Button`: Add a button."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:73
msgid ":guilabel:`Appointment`: Add a specific appointment."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:74
msgid ":guilabel:`Calendar`: Schedule an appointment."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:76
msgid ":guilabel:`Widgets`"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:78
msgid ":guilabel:`3 Stars`: Insert a rating over three stars."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:79
msgid ":guilabel:`5 Stars`: Insert a rating over five stars."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:81
msgid ":guilabel:`Basic Blocks`"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:83
msgid ":guilabel:`Signature`: Insert your signature."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:85
msgid ":guilabel:`Marketing Tools`"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:87
msgid ":guilabel:`Dynamic Placeholders`: Insert personalized content."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:90
msgid "To use any of these options, click on the desired feature from the powerbox drop-down menu. To format existing text with a text-related option (e.g. :guilabel:`Heading 1`, :guilabel:`Switch direction`, etc.), highlight the text, then type in the activator key (forward slash) `/`, and select the desired option from the drop-down menu."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:0
msgid "Powerbox feature in the email template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:100
msgid ":ref:`Using dynamic placeholders <email_template/dynamic-placeholders>`"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:103
msgid "XML/HTML code editor"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:105
msgid "To access the XML/HTML editor for an email template, first enter :ref:`developer mode <developer-mode>`. Then, click the :guilabel:`</>` icon in the upper-right corner of the template, and proceed to edit the XML/HTML. To return to the standard text editor, click the :guilabel:`</>` icon again."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:-1
msgid "Composer in mass mailing mode after selecting multiple quotations."
msgid "HTML editor in the email template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:28
msgid "You can also define them by default on the template:"
#: ../../content/applications/general/email_communication/email_template.rst:115
msgid "The XML/HTML editor should be accessed with caution as this is the backend code of the template. Editing the code can cause the email template to break immediately or when upgrading the database."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:122
msgid "Dynamic placeholders"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:124
msgid "*Dynamic placeholders* reference certain fields within the Odoo database to produce unique data in the email template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:128
msgid "Many companies like to customize their emails with a personalized piece of customer information to grab attention. This can be accomplished in Odoo by referencing a field within a model by inserting a dynamic placeholder. For example, a customer's name can be referenced in the email from the :guilabel:`Customer` field on the :guilabel:`Sales Order` model. The dynamic placeholder for this field is: `{{ object.partner_id }}`."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:134
msgid "Dynamic placeholders are encoded to display fields from within the database. Dynamic placeholders can be used in the :guilabel:`Body` (:guilabel:`Content` Tab) of the email template. They can also be used in the fields present in the :guilabel:`Email Configuration` tab, the :guilabel:`Subject` of the email, and the :guilabel:`Language`."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:139
msgid "To use the dynamic placeholders in the :guilabel:`Body` of an email open the **powerbox** feature by typing in `/` into the body of the email template under the :guilabel:`Content` tab. Scroll to the bottom of the options list, to :guilabel:`Marketing Tools`. Next, select :guilabel:`Dynamic Placeholder`. Then select the dynamic placeholder from a list of available options and follow the prompts to configure it with the desired corresponding Odoo field. Each dynamic placeholder will vary in configuration."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:-1
msgid "Using dynamic placeholders in an email template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:151
msgid "Each unique combination of :guilabel:`Fields`, :guilabel:`Sub-models` and :guilabel:`Sub-fields` creates a different dynamic placeholder. Imagine it as a combination to the field that is being created."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:155
msgid "To search the available fields, simply type in the front-end name (on user-interface) of the field in the search. This will find a result from all of the available fields for the model that the email template is created for."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:160
msgid "Customizing email templates are out of the scope of Odoo Support."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:163
msgid "Rich text editor"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:165
msgid "A rich text editor toolbar can be accessed by highlighting text in the email template. This can be used to change the heading, font size/style, color, add a list type, or a link."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:-1
msgid "Rich text editor in the email template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:173
msgid "Resetting email templates"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:175
msgid "Should the email template not work because the code has been altered it can be reset to restore it back to the out-of-box default template. Simply click on the :guilabel:`Reset Template` button in the upper left-hand of the screen and the template will be reset."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:-1
msgid "Resetting the email template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:184
msgid "Default reply on email templates"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:186
msgid "Under the :guilabel:`Email Configuration` tab on an email template, there is a :guilabel:`Reply To` field. In this field, add email addresses to which replies are redirected when sending emails en masse using this template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:191
msgid "Add multiple email addresses by adding a comma `,` between the addresses or dynamic placeholders."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:-1
msgid "Reply-to field on template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:34
msgid "Because of this, setting a value in this field is useless as the value defined will be totally ignored. The default *reply-to* value is the default catchall email address to ensure a communication between your customer and your Odoo database. For more information about the way the catchall works, please check :ref:`how to manage inbound messages <email_communication/inbound_messages>`."
#: ../../content/applications/general/email_communication/email_template.rst:198
msgid "The :guilabel:`Reply To` field is **only** used for mass mailing (sending emails in bulk). Bulk emails can be sent in almost every Odoo application that has a list view option."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:40
msgid "Transactional emails and corresponding URL for each company"
#: ../../content/applications/general/email_communication/email_template.rst:201
msgid "To send mass mails, while in :guilabel:`list` view, check the boxes next to the desired records where the emails are to be sent, click the :guilabel:`Action` button (represented by a :guilabel:`⚙️ (gear)` icon), and select the desired email option from the :guilabel:`Action` drop-down menu. Email options can vary by the particular list view and application."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:42
msgid "When using Odoo, multiple events trigger the sending of automated emails. These emails are known as transactional emails and sometimes contain links pointing to your Odoo database."
#: ../../content/applications/general/email_communication/email_template.rst:206
msgid "If it is possible to send an email, a mail composer pop-up window appears, with values that can be defined and customized. This option will be available on the :guilabel:`Action` button on pages where emails can be sent in bulk---for example, on the :guilabel:`Customers` page of the CRM app. This action occurs throughout the Odoo database."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:45
msgid "By default, links generated by the database use the dynamic web.base.url key defined in the system parameters. More information about this :ref:`parameter <domain-name/web-base-url>`."
#: ../../content/applications/general/email_communication/email_template.rst:-1
msgid "Email composer in mass mailing mode with reply-to highlighted."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:48
msgid "If the website application isn't installed, the web.base.url key will always be the default parameter used to generate all the links."
#: ../../content/applications/general/email_communication/email_template.rst:216
msgid "Transactional emails and corresponding URLs"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:51
msgid "It’s important to know that this key can only have a single value, meaning that in a multi-website/company database environment, even if you have a specific domain name for each website, the links generated to share a document or within a transactional email might remain the same, whatever the website/company related to the sending of the email/document."
#: ../../content/applications/general/email_communication/email_template.rst:218
msgid "In Odoo, multiple events can trigger the sending of automated emails. These emails are known as *transactional emails*, and sometimes contain links redirecting to the Odoo database."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:56
msgid "This is not always the case as some Odoo applications have a link established in the database with the website application, meaning that in this case, if a specific domain is defined for the websites, the URL generated in the email template will use the domain defined on the corresponding website of the company."
#: ../../content/applications/general/email_communication/email_template.rst:221
msgid "By default, links generated by the database use the dynamic `web.base.url` key defined in the system parameters. For more information about this, see :ref:`system parameters <domain-name/web-base-url>`."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:62
msgid "A document shared using the documents application will always use the web.base.url key, as the document shared isn't associated with any particular website. Meaning that the URL will always be the same (the web.base.url key value), whatever the company it's shared from, this is a known limitation!"
#: ../../content/applications/general/email_communication/email_template.rst:225
msgid "If the *Website* application is not installed, the `web.base.url` key will always be the default parameter used to generate all the links."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:67
msgid "On the other hand, sales orders made by a customer on one of your Odoo e-commerce websites have a link established with the website from which the order was made. As a result, the e-mail sent for the sales orders uses the domain name defined for the corresponding website to generate the links."
#: ../../content/applications/general/email_communication/email_template.rst:229
msgid "The `web.base.url` key can only have a single value, meaning that, in a multi-website or multi-company database environment, even if there is a specific domain name for each website, the links generated to share a document (or the links within a transactional email) may remain the same, regardless of which website/company is related to the sending of the email/document."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:71
msgid "For more information about how to configure your domains, we invite you to check :doc:`our domain name documentation </administration/maintain/domain_names>`."
#: ../../content/applications/general/email_communication/email_template.rst:235
msgid "If the :guilabel:`Value` of the :guilabel:`web.base.url` system parameter is equal to `https://www.mycompany.com` and there are two separate companies in Odoo with different website URLs: `https://www.mycompany2.com` and `https://www.mycompany1.com`, the links created by Odoo to share a document, or send a transactional email, come from the domain: `https://www.mycompany.com`, regardless of which company sends the document or email."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:75
#: ../../content/applications/general/email_communication/email_template.rst:241
msgid "This is not always the case, as some Odoo applications (*eCommerce*, for example) have a link established in the database with the *Website* application. In that case, if a specific domain is defined for the website, the URL generated in the email template uses the domain defined on the corresponding website of the company."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:247
msgid "When a customer makes a purchase on an Odoo *eCommerce* website, the order has an established link with that website. As a result, the links in the confirmation email sent to the customer use the domain name for that specific website."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:252
msgid "A document shared using the *Documents* application will **always** use the `web.base.url` key, as the document shared is not associated with any particular website. This means that the URL will always be the same (the `web.base.url` key value), no matter what company it's shared from. This is a known limitation."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:257
msgid "For more information about how to configure domains, check out the :doc:`domain name documentation </administration/maintain/domain_names>`."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:261
msgid "Updating translations within email templates"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:77
msgid "Email templates are automatically translated. Changing the translations shouldn’t be necessary. However, if for a specific reason you’d like to change some of the translations, this can be done."
#: ../../content/applications/general/email_communication/email_template.rst:263
msgid "In Odoo, email templates are automatically translated for all users in the database for all of the languages installed. Changing the translations shouldn't be necessary. However, if for a specific reason, some of the translations need to be changed, it can be done."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:80
msgid "Like any modification in the code, keep in mind that modifications that aren’t done correctly (for example modifications leading to bad syntax) can break the template, as a result, the template will appear blank."
#: ../../content/applications/general/email_communication/email_template.rst:268
msgid "Like any modification in the code, if translation changes are not done correctly (for example, modifications leading to bad syntax), it can break the template, and as a result, the template will appear blank."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:84
msgid "In order to edit your translations, follow these steps from the template."
#: ../../content/applications/general/email_communication/email_template.rst:272
msgid "In order to edit translations, first enter :ref:`developer mode <developer-mode>`. Then, on the email template, click on the :guilabel:`Edit` button, and then click on the language button, represented by the initials of the language currently being used (e.g. :guilabel:`EN` for English)."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:86
msgid "Click on the edit button, then on the language button"
#: ../../content/applications/general/email_communication/email_template.rst:-1
msgid "Edit the language of a template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:0
msgid "Edit the language of a template"
#: ../../content/applications/general/email_communication/email_template.rst:281
msgid "If there aren't multiple languages installed and activated in the database, or if the user does not have administration access rights, the language button will not appear."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:92
msgid "A pop-up window with the different languages installed on the database will be displayed. From here, editing the translations will be possible. Don't forget to hit the save button to preserve your changes."
#: ../../content/applications/general/email_communication/email_template.rst:284
msgid "A pop-up window with the different languages installed on the database appears. From this pop-up, editing of translations is possible. When the desired changes have been made, click the :guilabel:`Save` button to save the changes."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:0
msgid "Translation of the body of the Application template in the different languages installed."
#: ../../content/applications/general/email_communication/email_template.rst:-1
msgid "Translation of the body of the Appointment Booked template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:293
msgid "When editing the translations, the default language set in the database appears in **bold**."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:3
msgid "FAQ"
msgid "Email issues"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:5
msgid "This document contains an explanation of the most recurring mailing concerns."
msgid "This document contains an explanation of the most recurring emailing issues in Odoo."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:7
msgid "We will start by addressing issues of outgoing emails (ex: my client has not received my email), and then, of incoming emails (ex: I do not receive responses from my customers in the database)."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:11
#: ../../content/applications/general/email_communication/faq.rst:8
msgid "Outgoing emails"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:16
msgid "What do you have to check if your email is not sent?"
#: ../../content/applications/general/email_communication/faq.rst:13
msgid "Email is not sent"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:18
msgid "The first indicator showing you that the email has not been sent is the red envelope next to the date and time of the message."
#: ../../content/applications/general/email_communication/faq.rst:15
msgid "The first indicator showing that an email has not been sent is the presence of a red :guilabel:`✉️ (envelope)` icon, next to the date and time of the message, located in the chatter."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:-1
msgid "Red envelope displayed in chatter"
msgid "Red envelope icon displayed in chatter."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:26
#: ../../content/applications/general/email_communication/faq.rst:22
msgid "Unsent emails also appear in the Odoo email queue. In :ref:`developer mode <developer-mode>`, the email queue can be accessed by going to :menuselection:`Settings app --> Technical menu --> Email --> Emails`. Unsent emails appear in turquoise, while sent emails appear in grey."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:27
msgid "Common error messages"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:31
msgid "You reached your daily limit:"
#: ../../content/applications/general/email_communication/faq.rst:32
msgid "Daily limit reached"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:-1
msgid "Warning in Odoo upon email limit reached"
msgid "Warning in Odoo upon email limit reached."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:37
msgid "Each email service provider has its own email sending limits. The limits may be daily, hourly, and sometimes even per minute. This is the same for Odoo, we have to limit our customers to prevent our e-mail servers from being blacklisted."
#: ../../content/applications/general/email_communication/faq.rst:38
msgid "Each email service provider has its own email sending limits. The limits may be daily, hourly, or sometimes, per minute. This is the same for Odoo, which limits a customer's sending to prevent Odoo's email servers from being blacklisted."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:41
#: ../../content/applications/general/email_communication/faq.rst:42
msgid "Here are the default limits for new databases:"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:43
msgid "200 emails/day for Odoo Online and Odoo.sh databases with an active subscription,"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:44
msgid "20 emails/day for one-app free databases,"
msgid "**200 emails per day** for Odoo Online and Odoo.sh databases with an active subscription."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:45
msgid "50 emails/day for trial databases,"
msgid "**20 emails per day** for one-app free databases."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:46
msgid "in case of migration, your daily limit might be reset to 50 emails a day."
msgid "**50 emails per day** for trial databases."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:48
msgid "In case you hit the limit, you can:"
#: ../../content/applications/general/email_communication/faq.rst:47
msgid "In the case of migration, the daily limit might be reset to 50 emails per day."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:50
msgid "Ask our support team to increase your daily limit. We will analyze the situation of your database depending on (non-exhaustive list):"
#: ../../content/applications/general/email_communication/faq.rst:49
msgid "If the daily limit is reached:"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:53
msgid "How many users in your database,"
#: ../../content/applications/general/email_communication/faq.rst:51
msgid "Contact the Odoo support team, who may increase the daily limit depending on the following factors:"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:54
msgid "Which apps are installed,"
msgid "How many users are in the database?"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:55
msgid "Your bounce rate: the percentage of email addresses that did not receive your emails because it was returned by a mail server on its way to the final recipient. You can contact the `support <https://www.odoo.com/help>`_."
msgid "Which apps are installed?"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:56
msgid "The bounce rate: the percentage of email addresses that did not receive emails because they were returned by a mail server on its way to the final recipient."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:59
msgid "Use your own outgoing email server to be independent of Odoo’s mail limit (please refer to :doc:`the corresponding documentation </applications/general/email_communication/email_servers>`),"
msgid "Use an external outgoing email server to be independent of Odoo's mail limit (refer to the corresponding :doc:`email documentation </applications/general/email_communication/email_servers>`)."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:61
msgid "Wait until 11pm UTC for the reset and click on the retry button: The :ref:`Developer mode <developer-mode>` must be activated. Then, go to :menuselection:`Settings --> Technical --> Emails`"
#: ../../content/applications/general/email_communication/faq.rst:62
msgid "Wait until 11 PM (UTC) for the daily limit to reset, and retry sending the email. In :ref:`developer mode <developer-mode>`, go to :menuselection:`Settings app --> Technical menu --> Email --> Emails`, then click the :guilabel:`Retry` button next to an unsent email."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:-1
msgid "Retry button of an emails"
#: ../../content/applications/general/email_communication/faq.rst:67
msgid "The daily email limit is comprehensive to the database. By default, any internal message, notification, logged note, etc. counts as an email in the daily limit if it notifies someone via email. This can be mitigated by receiving :ref:`notifications in Odoo <discuss_app/notification_preferences>`, instead of emails."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:69
msgid "The daily limit is global to your database and can rise quickly! By default an internal message, a notification, a note, etc. counts as an email in your daily limit if it notifies someone."
#: ../../content/applications/general/email_communication/faq.rst:73
msgid "SMTP error"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:72
msgid "You can mitigate this by receiving your :ref:`notifications in Odoo <discuss_app/notification_preferences>` instead of by emails."
#: ../../content/applications/general/email_communication/faq.rst:75
msgid "Simple Mail Transport Protocol (SMTP) error messages explain why an email wasn't transmitted successfully. :abbr:`SMTP (Simple Mail Transport Protocol)` is a protocol to describe the email structure, and transmits data from messages over the Internet. The error messages generated by email services are helpful tools to diagnose and troubleshoot email problems."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:76
msgid "SMTP Error"
#: ../../content/applications/general/email_communication/faq.rst:81
msgid "This is an example of a 554 SMTP permanent delivery error: `554: delivery error: Sorry, your message to ------@yahoo.com cannot be delivered. This mailbox is disabled (554.30). - mta4471.mail.bf1.yahoo.com --- Below this line is a copy of the message.`"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:78
msgid "You can find out why an email wasn't transmitted successfully by reviewing the Simple Mail Transport Protocol (SMTP) error messages. SMTP is a protocol to describe the email structure and transmit it over the Internet, and the error messages generated by email services are helpful tools to diagnose and troubleshoot email problems."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:84
msgid "No Error"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:86
msgid "Odoo is not always capable of providing information for the reason it failed. The different providers implement a personalized policy of the bounce emails and it is not always possible for Odoo to interpret it correctly."
#: ../../content/applications/general/email_communication/faq.rst:85
msgid "The debug menu can be used to investigate SMTP sending issues from a database. To access the menu, :ref:`developer mode <developer-mode>` must be activated. Once activated, navigate to the :menuselection:`Debug Menu` in the top right of the menu bar (the :guilabel:`🐞 (bug)` icon), :menuselection:`Debug Menu --> Manage Messages`"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:90
msgid "If you have this problem on a recurring basis with the same client or the same domain, please do not hesitate to contact `Odoo Support <https://www.odoo.com/help>`_ for help in finding a reason."
msgid "The :guilabel:`Manage Messages` menu opens a list of all the messages sent in a particular record. Within each message there is information on sending, including the type, and subtype, of the message."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:93
msgid "Note: in such case, one of the most common reasons is related to :ref:`SPF <email_communication/spf_compliant>` and/or :ref:`DKIM <email_communication/DKIM_compliant>` configuration."
#: ../../content/applications/general/email_communication/faq.rst:94
msgid "Other information includes to whom the message was sent, and whether Odoo received a bounce-back message from an email server."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:97
msgid "Why is my email sent late?"
#: ../../content/applications/general/email_communication/faq.rst:-1
msgid "Manage messages menu option on the debug menu."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:99
msgid "It may happen that you schedule an email campaign but it is not sent on time. We know that we use a delayed job to send emails that we consider as not urgent (Newsletters concept such as mass mailing, marketing automation, events). The system utility **cron** can be used to schedule programs to run automatically at predetermined intervals. We use that policy in order to avoid cluttering the mail servers and prioritize the communication."
#: ../../content/applications/general/email_communication/faq.rst:102
msgid "A user must be on a view in Odoo that has a chatter in order for the :guilabel:`Manage Messages` menu option to appear."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:105
msgid "The emails considered urgent (communication from one person to another one such as Sales Orders, Invoices, Purchase Orders, etc.) are sent directly."
#: ../../content/applications/general/email_communication/faq.rst:106
msgid "No error populated"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:108
msgid "Odoo is not always capable of providing information for the reason it failed. The different email providers implement a personalized policy of bounced emails, and it is not always possible for Odoo to interpret it correctly."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:112
msgid "If this is a recurring problem with the same client, or the same domain, do not hesitate to contact `Odoo Support <https://www.odoo.com/help>`_ for help in finding a reason."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:116
msgid "One of the most common reasons for an email failing to send with no error message is related to :ref:`SPF <email_communication/spf_compliant>` and/or :ref:`DKIM <email_communication/DKIM_compliant>` configuration. Also, check to make sure the `mail.bounce.alias` is defined in the *system parameters*. Access system parameters in :ref:`developer mode <developer-mode>` by navigating to :menuselection:`Settings app --> Technical menu --> Parameters --> System Parameters`."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:124
msgid "Email is sent late"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:126
msgid "Email campaigns send at a scheduled time, using a delay pre-programed in the database. Odoo uses a delayed task to send emails that are considered \"not urgent\" (newsletter formats, such as: mass mailing, marketing automation, and events). The system utility **cron** can be used to schedule programs to run automatically at predetermined intervals. Odoo uses that policy in order to avoid cluttering the mail servers and, instead, prioritizes individual communication. This **cron** is called :guilabel:`Mail: Email Queue Manager`, and can be accessed in :ref:`developer mode <developer-mode>` by going to :menuselection:`Settings app --> Technical menu --> Automation --> Scheduled Actions`."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:-1
msgid "Email scheduled to be sent later."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:112
msgid "By default, the Mass Mailing cron runs every 60 minutes. So, you should wait maximum an hour before the campaign is actually sent."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:116
msgid "Incoming emails"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:118
msgid "When you have an issue with incoming emails, there might not be an indication per se in Odoo. This is the client who tries to contact a database who will get a bounce (most of the time 550: mailbox unavailable)."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:123
msgid "Emails are not received"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:125
msgid "Depending on the platform you are using:"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:127
msgid "The **Odoo.sh** users can find their live logs on the folder :file:`~/logs/`."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:129
msgid "The folder :file:`~/logs/` (preferably accessed by the command line) of an Odoo.sh contains a list of files containing the logs of the database. The log files are created everyday at 5:00 AM UTC. The two last days are not compressed, while the older ones are, in order to gain space. The naming of the files for Today and Yesterday are :file:`odoo.log` and :file:`odoo.log.1`. For the following, they are named with their dates and compressed. See the Odoo.sh documentation about :ref:`logs <odoosh/logs>`. Use the command ``grep`` and ``zgrep`` (for the compressed ones) to search through the files."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:137
msgid "**Odoo Online** users won’t have access to their logs. However you can still contact `Odoo Support <https://www.odoo.com/help>`_ , if you have a recurring issue with the same client or domain."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:142
msgid "Get help from support"
#: ../../content/applications/general/email_communication/faq.rst:140
msgid "What is a **cron**? A cron is an action that Odoo runs in the background to execute particular code to complete a task."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:144
msgid "In order to get helped efficiently, please provide as much information as possible. Here is a list of what can be helpful:"
msgid "By default, the *Mass Mailing cron* runs every 60 minutes. This can be changed to no less than 5 minutes. However, running the action every 5 minutes would bog down the Odoo database (stress the system), so this is not recommended. To edit the mass mailing cron, select the scheduled action :guilabel:`Mail: Email Queue Manager`, and proceed to make any necessary adjustments."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:147
msgid "The **EML** of the email, stating for *Electronic Mail*, is the file format containing all the technical information required for an investigation. The documentation of your own email provider might help you on how to get your EML files. Once you get the EML of the email, adding it in the attachment of your ticket is the most efficient way for us to investigate. The support will mainly focus on redundant issues."
#: ../../content/applications/general/email_communication/faq.rst:149
msgid "Emails that are considered urgent (communication from one person to another, such as sales orders, invoices, purchase orders, etc.) are sent immediately."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:154
msgid "`Gmail documentation <https://support.google.com/mail/answer/29436>`_"
#: ../../content/applications/general/email_communication/faq.rst:153
msgid "Incoming emails"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:156
msgid "`Outlook documentation <https://support.microsoft.com/en-us/office/view-internet-message-headers-in-outlook-cd039382-dc6e-4264-ac74-c048563d212c#tab=Web>`_"
#: ../../content/applications/general/email_communication/faq.rst:155
msgid "When there is an issue with incoming emails, there might not be an indication, per se, in Odoo. It is the sending email client, who tries to contact a database, that will get a bounce-back message (most of the time a :guilabel:`550: mailbox unavailable` error message)."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:159
msgid "The exact flow you are following in order to normally receive those emails in Odoo. Here are examples of questions whose answers can be useful:"
#: ../../content/applications/general/email_communication/faq.rst:160
msgid "Email is not received"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:162
msgid "Is this simply a reply from an email going out from Odoo ?"
msgid "The steps that should be taken depend on the Odoo platform where the database is hosted."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:164
msgid "Are you using an incoming email server or somehow redirecting?"
msgid "**Odoo.sh** users can find their live logs on the folder :file:`~/logs/`."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:166
msgid "Can you provide us with an example of an email that has been correctly forwarded ?"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:168
msgid "Providing answers to the following questions:"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:170
msgid "Is it a generic issue or is it specific to a use case? If yes, which one exactly?"
msgid "Logs are a stored collection of all the tasks completed in a database. They are a text-only representation, complete with timestamps of every action taken on the Odoo database. This can be helpful to track emails leaving the database. Failure to send can also be seen by logs that indicate that the message tried to send repeatedly. Logs will show every action to the email servers from the database."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:172
msgid "Is it working as expected? In case the email is sent using Odoo, the bounce email should reach the Odoo database and display the :ref:`red envelope <red_envelop>`."
msgid "The folder :file:`~/logs/` (accessed by the command line or on the Odoo.sh dashboard) of an Odoo.sh database contains a list of files containing the logs of the database. The log files are created everyday at 5:00 AM (UTC)."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:177
msgid "The two most recent days (today and yesterday) are not compressed, while the older ones are, in order to save space. The naming of the files for today and yesterday are respectively: :file:`odoo.log` and :file:`odoo.log.1`."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:181
msgid "For the following days, they are named with their dates, and then compressed. Use the command :command:`grep` and :command:`zgrep` (for the compressed ones) to search through the files."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:185
msgid "For more information on logs and how to access them via the Odoo.sh dashboard, see :ref:`this administration documentation <odoosh/logs>`."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:188
msgid "For more information on accessing logs via the command line visit :ref:`this developer documentation <reference/cmdline/server/logging>`."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:191
msgid "**Odoo Online** users won't have access to the logs. However `Odoo Support <https://www.odoo.com/help>`_ can be contacted if there is a recurring issue with the same client or domain."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:196
msgid "Get help from Odoo support"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:198
msgid "In order to get helped efficiently, please provide as much information as possible. Here is a list of what can be helpful when reaching out to the Odoo Support team about an issue:"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:201
msgid "Send a copy of the email headers. The `.EML` file (or **headers**) of the email is the file format containing all the technical information required for an investigation. The documentation from the email provider might explain how to access the EML file/header files. Once the headers of the email are obtained, adding it into the Odoo Support ticket is the most efficient way for the Odoo Support team to investigate."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:208
msgid "`Gmail documentation on headers <https://support.google.com/mail/answer/29436>`_"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:209
msgid "`Outlook documentation on headers <https://support.microsoft.com/en-us/office/view-internet-message-headers-in-outlook-cd039382-dc6e-4264-ac74-c048563d212c#tab=Web>`_"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:212
msgid "Explain the exact flow that is being followed to normally receive those emails in Odoo. Here are examples of questions whose answers can be useful:"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:215
msgid "Is this a notification message from a reply being received in Odoo?"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:216
msgid "Is this a message being sent from the Odoo database?"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:217
msgid "Is there an incoming email server being used, or is the email somehow being redirected?"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:218
msgid "Is there an example of an email that has been correctly forwarded?"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:220
msgid "Provide answers to the following questions:"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:222
msgid "Is it a generic issue, or is it specific to a use case? If specific to a use case, which one exactly?"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:224
msgid "Is it working as expected? In case the email is sent using Odoo, the bounce email should reach the Odoo database, and display the :ref:`red envelope <red_envelop>`."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:228
msgid "The bounce system parameter needs to be set in the technical settings in order for the database to correctly receive bounce messages. To access this setting, go to :menuselection:`Settings app --> Technical menu --> Parameters --> System Parameters`. Then select the parameter name :guilabel:`mail.bounce.alias` and set the value to `bounce` if it isn't already set."
msgstr ""
#: ../../content/applications/general/export_import_data.rst:3

2346
locale/sources/inventory_and_mrp.pot
View File

File diff suppressed because it is too large Load Diff

178
locale/sources/legal.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-07-07 11:55+0000\n"
"POT-Creation-Date: 2023-10-09 13:19+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -2188,7 +2188,7 @@ msgid "4.1 Service de correction de Bugs"
msgstr ""
#: ../../content/legal/terms/i18n/enterprise_fr.rst:143
msgid "Pour la durée de ce Contrat, Odoo SA s'engage à déployer tous les efforts raisonnables pour corriger tout Bug du Logiciel ou des Modules Supplémentaires Couverts qui pourrait être signalé par le Client en suivant la procédure appropriée (généralement par le biais du formulaire en ligne ou des numéros de téléphone indiqués sur http://www.odoo.com.help, ou en cas de travail avec un Partenaire Odoo, le canal prévu par le partenaire), et de commencer à traiter ces signalements du Client dans un délai de 2 jours ouvrables."
msgid "Pour la durée de ce Contrat, Odoo SA s'engage à déployer tous les efforts raisonnables pour corriger tout Bug du Logiciel ou des Modules Supplémentaires Couverts qui pourrait être signalé par le Client en suivant la procédure appropriée (généralement par le biais du formulaire en ligne ou des numéros de téléphone indiqués sur http://www.odoo.com/help, ou en cas de travail avec un Partenaire Odoo, le canal prévu par le partenaire), et de commencer à traiter ces signalements du Client dans un délai de 2 jours ouvrables."
msgstr ""
#: ../../content/legal/terms/i18n/enterprise_fr.rst:150
@ -3382,7 +3382,7 @@ msgid "4.1 Serviço de Correção de Bugs"
msgstr ""
#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:136
msgid "Durante a vigência deste Contrato, a Odoo SA se compromete a realizar todos os esforços razoáveis para corrigir qualquer Bug do Software e Módulos Extras Cobertos relatados pelo Cliente por meio de um canal apropriado (normalmente, o formulário da Web ou os números de telefone listados em http://www.odoo.com.help, ou, ao trabalhar com um parceiro Odoo, o canal fornecido pelo parceiro) e começar a lidar com essas solicitações do Cliente em 2 dias úteis."
msgid "Durante a vigência deste Contrato, a Odoo SA se compromete a realizar todos os esforços razoáveis para corrigir qualquer Bug do Software e Módulos Extras Cobertos relatados pelo Cliente por meio de um canal apropriado (normalmente, o formulário da Web ou os números de telefone listados em http://www.odoo.com/help, ou, ao trabalhar com um parceiro Odoo, o canal fornecido pelo parceiro) e começar a lidar com essas solicitações do Cliente em 2 dias úteis."
msgstr ""
#: ../../content/legal/terms/i18n/enterprise_pt_BR.rst:142
@ -4950,6 +4950,134 @@ msgstr ""
msgid "10 Annexe A : Licence Odoo Enterprise Edition"
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:5
msgid "Allgemeine Verkaufsbedingungen"
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:9
msgid "`PDF herunterladen <https://www.odoo.com/documentation/16.0/terms_of_sale_de.pdf>`_"
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:11
msgid "Letzte Änderung: 12. September 2023."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:13
msgid "Diese Allgemeinen Verkaufsbedingungen regeln den Verkauf von Produkten und Dienstleistungen durch Odoo S.A. und seine verbundenen Unternehmen (zusammen \"Odoo SA\") an den Kunden. Für von Odoo S.A. erbrachte Dienstleistungen können zusätzliche Bedingungen gelten (z. B. der Enterprise-Abonnementvertrag). Falls diese zusätzlichen Bedingungen im Widerspruch zu den Allgemeinen Verkaufsbedingungen stehen, haben die zusätzlichen Bedingungen Vorrang vor diesen Allgemeinen Verkaufsbedingungen."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:21
msgid "Bitte lesen Sie diese Bedingungen sorgfältig durch, bevor Sie eine Bestellung bei Odoo S.A. aufgeben. Durch die Annahme einer Bestellung bei Odoo S.A. erklärt der Kunde seine Zustimmung zu diesen Bedingungen."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:25
msgid "Der Kunde verzichtet ausdrücklich auf seine eigenen Standardgeschäftsbedingungen, auch wenn diese nach diesen Standardgeschäftsbedingungen des Verkaufs erstellt wurden. Damit eine Abweichung gültig ist, muss sie im Voraus schriftlich vereinbart werden."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:30
msgid "Unsere Rechnungen sind innerhalb von 21 Arbeitstagen zahlbar, sofern auf der Rechnung oder der Bestellung keine andere Zahlungsfrist angegeben ist. Bei Nichtzahlung bis zum Fälligkeitsdatum behält sich Odoo S.A. das Recht vor, eine pauschale Verzugszinszahlung in Höhe von 15% des noch ausstehenden Betrags zu verlangen. Odoo S.A. ist berechtigt, bei verspäteter Zahlung ohne vorherige Ankündigung die Erbringung von Dienstleistungen auszusetzen."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:37
msgid "Ist eine Zahlung mehr als sechzig (60) Tage nach dem Fälligkeitsdatum noch ausstehend, behält sich Odoo S.A. das Recht vor, die Dienste eines Inkassounternehmens in Anspruch zu nehmen. Alle rechtlichen Kosten gehen zu Lasten des Kunden."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:42
msgid "In bestimmten Ländern wird nach den internen Gesetzen Quellensteuer auf den Rechnungsbetrag erhoben. Jegliche Quellensteuer ist vom Kunden an die Steuerbehörden zu zahlen. Odoo S.A. kann unter keinen Umständen in Kosten im Zusammenhang mit den Gesetzen eines Landes verwickelt werden. Der Rechnungsbetrag ist daher vollständig an Odoo S.A. zu zahlen und enthält keine Kosten im Zusammenhang mit den Gesetzen des Landes, in dem sich der Kunde befindet."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:50
msgid "Für Kunden mit globaler Präsenz erfolgt die Anwendung der Preise immer auf der Grundlage des Standorts des Kunden mit der höchsten Preisliste, sofern nicht schriftlich zum Zeitpunkt des Kaufs anders vereinbart."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:54
msgid "Monatliche Abonnements sind nur für die Nutzung auf der Cloud-Plattform (Odoo SaaS und Odoo SH) verfügbar. Die Zahlung von monatlichen Abonnements kann nur per Kreditkarte oder einem gleichwertig unterstützten automatischen Lastschriftverfahren erfolgen. Odoo S.A. behält sich das Recht vor, ein monatliches Abonnement abzulehnen, das diesen Bedingungen nicht entspricht."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:60
msgid "Odoo S.A. verpflichtet sich, sein Bestes zu tun, um die Dienstleistungen rechtzeitig gemäß den vereinbarten Zeitplänen bereitzustellen. Keine seiner Verpflichtungen kann jedoch als Verpflichtung zur Erzielung von Ergebnissen angesehen werden. Odoo S.A. kann unter keinen Umständen vom Kunden verlangt werden, als Dritter im Rahmen einer Schadensersatzklage aufzutreten, die gegen den Kunden von einem Endverbraucher eingereicht wird."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:67
msgid "Damit sie zulässig ist, muss Odoo S.A. über jede Beanstandung innerhalb von 8 Tagen nach Lieferung der Waren oder Erbringung der Dienstleistungen per Einschreiben an seinen Geschäftssitz informiert werden."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:71
msgid "Soweit gesetzlich zulässig, wird die Gesamthaftung jeder Partei zusammen mit ihren Tochtergesellschaften 50% des Gesamtbetrags, den der Kunde unter diesen Bedingungen in den 12 Monaten unmittelbar vor dem Ereignis, das zu einer solchen Klage geführt hat, gezahlt hat, nicht überschreiten. Mehrere Ansprüche vergrößern diese Begrenzung nicht."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:77
msgid "Odoo S.A. behält sich das Recht vor, diese Bedingungen jederzeit ohne vorherige Ankündigung zu ändern. Der Kunde unterliegt den zum Zeitpunkt der Zustimmung geltenden Bedingungen."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_de.rst:81
msgid "Alle unsere vertraglichen Beziehungen unterliegen ausschließlich dem belgischen Recht. Darüber hinaus unterliegt jeder Streitfall ausschließlich der Zuständigkeit der Gerichte des Arrondissements Nivelles (Belgien)."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:5
msgid "Términos Generales de Venta"
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:9
msgid "`Descargar PDF <https://www.odoo.com/documentation/16.0/terms_of_sale_es.pdf>`_"
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:11
msgid "Última revisión: 12 de septiembre de 2023."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:13
msgid "Estos Términos Generales de Venta rigen la venta de productos y servicios por parte de Odoo S.A. y sus filiales (en adelante denominadas conjuntamente \"Odoo S.A.\") al cliente. Para los servicios proporcionados por Odoo S.A., pueden aplicarse términos adicionales (por ejemplo, el Acuerdo de suscripción de Odoo Enterprise). Si estos términos adicionales son inconsistentes con los Términos Generales de Venta, prevalecerán sobre estos Términos Generales de Venta."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:20
msgid "Lea estos términos detenidamente antes de realizar un pedido a Odoo S.A. Al aceptar un pedido con Odoo S.A., el cliente manifiesta su aceptación de estos términos."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:24
msgid "El cliente renuncia explícitamente a sus propias condiciones y términos estándar, incluso si estos se redactaron después de estos términos y condiciones estándar de venta. Para que una derogación sea válida, debe acordarse expresamente por adelantado por escrito."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:29
msgid "Nuestras facturas son pagaderas en un plazo de 21 días laborables, a menos que en la factura o el pedido se indique otro plazo de pago. En caso de falta de pago en la fecha de vencimiento, Odoo S.A. se reserva el derecho de solicitar un pago de intereses fijos del 15% sobre la suma pendiente. Odoo S.A. estará autorizada a suspender la prestación de servicios sin previo aviso en caso de retraso en el pago."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:36
msgid "Si un pago aún está pendiente más de sesenta (60) días después de la fecha de vencimiento, Odoo S.A. se reserva el derecho de recurrir a los servicios de una empresa de recuperación de deudas. Todos los gastos legales serán a cargo del cliente."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:41
msgid "En algunos países se aplica la retención en la fuente sobre el monto de las facturas, de acuerdo con su legislación interna. Cualquier retención en la fuente será pagada por el cliente a las autoridades fiscales. En ningún caso Odoo S.A. podrá involucrarse en los costos relacionados con la legislación de un país. El monto de la factura, por lo tanto, será debido a Odoo S.A. en su totalidad y no incluye ningún costo relacionado con la legislación del país en el que se encuentra el cliente."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:49
msgid "Para clientes con presencia global, la tarificación aplicable siempre se basa en la ubicación del cliente con la lista de precios más alta, a menos que se especifique lo contrario por escrito en el momento de la compra."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:53
msgid "Las Suscripciones Mensuales solo están disponibles para alojamiento en la Plataforma en la Nube (Odoo SaaS y Odoo SH). El pago de las Suscripciones Mensuales solo puede realizarse con tarjeta de crédito o un método de débito automático equivalente admitido. Odoo S.A. se reserva el derecho de rechazar cualquier Suscripción Mensual que no cumpla con estas condiciones."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:59
msgid "Odoo S.A. se compromete a hacer lo posible para suministrar los servicios a tiempo de acuerdo con los plazos acordados. Sin embargo, ninguna de sus obligaciones puede considerarse como una obligación de lograr resultados. Odoo S.A. no puede, bajo ninguna circunstancia, ser requerida por el cliente para aparecer como tercero en el contexto de cualquier reclamación por daños presentada contra el cliente por un consumidor final."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:66
msgid "Para que sea admisible, Odoo S.A. debe ser notificada de cualquier reclamación mediante una carta enviada por correo certificado a su sede registrada dentro de los 8 días posteriores a la entrega de los bienes o la prestación de los servicios."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:71
msgid "En la medida máxima permitida por la ley, la responsabilidad agregada de cada parte junto con sus filiales que surja no superará el 50% del monto total pagado por el Cliente en virtud de estos términos durante los 12 meses inmediatamente anteriores a la fecha del evento que dé lugar a dicha reclamación. Múltiples reclamaciones no ampliarán esta limitación."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:77
msgid "Odoo S.A. se reserva el derecho de modificar estos términos en cualquier momento sin previo aviso. El cliente estará sujeto a los términos vigentes en el momento de la aceptación de dichos términos."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_es.rst:81
msgid "Todas nuestras relaciones contractuales estarán reguladas exclusivamente por la ley belga. Además, cualquier disputa que pueda surgir estará sujeta exclusivamente a la jurisdicción de los tribunales del distrito de Nivelles (Bélgica)."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:5
msgid "Conditions Générales de Vente"
msgstr ""
@ -4959,7 +5087,7 @@ msgid "`Download PDF <https://www.odoo.com/documentation/16.0/terms_of_sale_fr.p
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:11
msgid "Dernière modification: 20 octobre 2021."
msgid "Dernière modification: 12 septembre 2023."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:13
@ -4987,26 +5115,34 @@ msgid "Si le Client est autorisé à effectuer des paiements à terme, l’absen
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:51
msgid "Certains pays appliquent une retenue à la source sur le montant de la facture, conformément à leur législation interne. La retenue à la source sera réglée par le client, auprès de l'administration fiscale. En aucun cas, Odoo S.A. ne sera impliquée dans les coûts liés à la législation du pays. Le montant de la facture est donc dû à Odoo S.A. dans son intégralité et n’inclus pas les coûts relatifs à la législation du pays où se trouve le client. Pour les clients implantés dans plusieurs pays, les prix applicables seront toujours basés sur l'implantation géographique ayant la liste de prix la plus élevée, sauf stipulation contraire par écrit au moment de la commande."
msgid "Certains pays appliquent une retenue à la source sur le montant de la facture, conformément à leur législation interne. La retenue à la source sera réglée par le client, auprès de l'administration fiscale. En aucun cas, Odoo S.A. ne sera impliquée dans les coûts liés à la législation du pays. Le montant de la facture est donc dû à Odoo S.A. dans son intégralité et n’inclus pas les coûts relatifs à la législation du pays où se trouve le client."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:61
#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:58
msgid "Pour les clients implantés dans plusieurs pays, les prix applicables seront toujours basés sur l'implantation géographique ayant la liste de prix la plus élevée, sauf stipulation contraire par écrit au moment de la commande."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:62
msgid "Les abonnements mensuels sont uniquement disponibles pour l'hébergement sur la Plate-forme Cloud (Odoo SaaS et Odoo SH). Le paiement des abonnements mensuels ne peut être effectué que par carte de crédit ou par une méthode de prélèvement automatique équivalente prise en charge. Odoo S.A. se réserve le droit de refuser tout abonnement mensuel ne respectant pas ces conditions."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:68
msgid "Odoo S.A. s'engage à faire ses meilleurs efforts en vue de fournir en temps utile des services performants. Toutefois, aucune de ses obligations ne peut être considérée comme étant une obligation de résultat. Odoo S.A. ne peut, en aucun cas, être appelée en garantie par le client dans le cadre de demandes en dommages et intérêts formulée par le consommateur final à l'encontre du client."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:67
#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:74
msgid "Dans la limite autorisée par la loi, la responsabilité globale de chaque partie, ainsi que de ses filiales ne dépassera pas 50% du montant total réglé par le Client en vertu des présentes conditions au cours des 12 mois précédant la date de l'événement donnant lieu à une telle réclamation. Des réclamations multiples n'augmenteront pas cette limite."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:73
#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:80
msgid "Toute réclamation doit, pour être recevable, être notifiée à Odoo S.A., à son siège social, par courrier recommandé dans les 8 jours suivant la livraison des marchandises ou la prestation des services."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:77
#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:84
msgid "Odoo S.A. se réserve le droit de modifier ces conditions à n'importe quel moment et sans notification préalable. Le client est soumis aux conditions en application au moment de son acceptation de ces conditions."
msgstr ""
#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:81
#: ../../content/legal/terms/i18n/terms_of_sale_fr.rst:88
msgid "Tout litige résultant de la présente convention ressort de l’application du droit belge et est de la compétence des Tribunaux de l’arrondissement du siège social d’Odoo S.A. hormis le droit d’Odoo S.A. de porter le litige devant une autre juridiction compétente."
msgstr ""
@ -5487,7 +5623,7 @@ msgid "`Download PDF <https://www.odoo.com/documentation/16.0/terms_of_sale.pdf>
msgstr ""
#: ../../content/legal/terms/terms_of_sale.rst:11
msgid "Last revision: October 20, 2021."
msgid "Last revision: September 12, 2023."
msgstr ""
#: ../../content/legal/terms/terms_of_sale.rst:13
@ -5511,25 +5647,33 @@ msgid "If a payment is still outstanding more than sixty (60) days after the due
msgstr ""
#: ../../content/legal/terms/terms_of_sale.rst:40
msgid "Certain countries apply withholding at source on the amount of invoices, in accordance with their internal legislation. Any withholding at source will be paid by the client to the tax authorities. Under no circumstances can Odoo S.A. become involved in costs related to a country's legislation. The amount of the invoice will therefore be due to Odoo S.A. in its entirety and does not include any costs relating to the legislation of the country in which the client is located. For clients with a global presence, the applicable pricing is always based on the client location with the highest price list, unless otherwise specified in writing at the time of purchase."
msgid "Certain countries apply withholding at source on the amount of invoices, in accordance with their internal legislation. Any withholding at source will be paid by the client to the tax authorities. Under no circumstances can Odoo S.A. become involved in costs related to a country's legislation. The amount of the invoice will therefore be due to Odoo S.A. in its entirety and does not include any costs relating to the legislation of the country in which the client is located."
msgstr ""
#: ../../content/legal/terms/terms_of_sale.rst:50
#: ../../content/legal/terms/terms_of_sale.rst:48
msgid "For clients with a global presence, the applicable pricing is always based on the client location with the highest price list, unless otherwise specified in writing at the time of purchase."
msgstr ""
#: ../../content/legal/terms/terms_of_sale.rst:52
msgid "Monthly Subscriptions are only available for hosting on the Cloud Platform (Odoo SaaS and Odoo SH). Payment of Monthly Subscriptions can only be made by credit card or an equivalent supported automatic debit method. Odoo S.A. reserves the right to refuse any Monthly Subscription that does not comply with these conditions."
msgstr ""
#: ../../content/legal/terms/terms_of_sale.rst:58
msgid "Odoo S.A. undertakes to do its best to supply services in due time in accordance with the agreed timeframes. However, none of its obligations can be considered as being an obligation to achieve results. Odoo S.A. cannot, under any circumstances, be required by the client to appear as a third party in the context of any claim for damages filed against the client by an end consumer."
msgstr ""
#: ../../content/legal/terms/terms_of_sale.rst:56
#: ../../content/legal/terms/terms_of_sale.rst:64
msgid "In order for it to be admissible, Odoo S.A. must be notified of any claim by means of a letter sent by recorded delivery to its registered office within 8 days of the delivery of the goods or the provision of the services."
msgstr ""
#: ../../content/legal/terms/terms_of_sale.rst:60
#: ../../content/legal/terms/terms_of_sale.rst:68
msgid "To the maximum extent permitted by law, the aggregate liability of each party together with its affiliates arising will not exceed 50% of the total amount paid by the Customer under these terms during the 12 months immediately preceding the date of the event giving rise to such claim. Multiple claims shall not enlarge this limitation."
msgstr ""
#: ../../content/legal/terms/terms_of_sale.rst:66
#: ../../content/legal/terms/terms_of_sale.rst:74
msgid "Odoo S.A. reserves the right to modify these terms at any time without prior notice. The client will be subject to the terms in force at the time of acceptation of those terms."
msgstr ""
#: ../../content/legal/terms/terms_of_sale.rst:70
#: ../../content/legal/terms/terms_of_sale.rst:78
msgid "All our contractual relations will be governed exclusively by Belgian law. Moreover, any dispute that may arise will be subject exclusively to the jurisdiction of the courts of the Nivelles arrondissement (Belgium)."
msgstr ""

4
locale/sources/marketing.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-09-12 13:54+0000\n"
"POT-Creation-Date: 2023-10-09 13:19+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1430,7 +1430,7 @@ msgid "That's why the number of :guilabel:`Records` can be different from the nu
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:-1
msgid "Difference between real-time record count and total participants on a markeing campaign."
msgid "Difference between real-time record count and total participants on a marketing campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:51

394
locale/sources/productivity.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-09-12 13:54+0000\n"
"POT-Creation-Date: 2023-10-09 13:19+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1447,7 +1447,7 @@ msgid "Connect a supported receipt printer to a :abbr:`USB (Universal Serial Bus
msgstr ""
#: ../../content/applications/productivity/iot/config/pos.rst:43
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:149
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:391
msgid "Cash drawer"
msgstr ""
@ -1456,7 +1456,7 @@ msgid "The cash drawer should be connected to the printer with an RJ25 cable."
msgstr ""
#: ../../content/applications/productivity/iot/config/pos.rst:45
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:117
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:359
msgid "Barcode scanner"
msgstr ""
@ -1614,42 +1614,386 @@ msgid "Epson and Star receipt printers and Zebra label printers do not need a dr
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:103
msgid "The Zebra printer doesn't print anything"
msgid "Epson configuration special case"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:105
msgid "Zebra printers are quite sensitive to the format of the Zebra Programming Language (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 --> User Interface --> Views` in :ref:`developer mode <developer-mode>` and look for the corresponding template."
msgid "Most Epson printers support printing receipts in Odoo :abbr:`POS (Point of Sale)` using the `GS v 0` command. However, the following Epson printer models do not support this command:"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:112
msgid "Check out Zebra's instructions on printing :abbr:`ZPL (Zebra Programming Language)` files `here <https://supportcommunity.zebra.com/s/article/Print-a-zpl-file-using-the-Generic-Text-Printer>`_."
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:108
msgid "TM-U220"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:120
msgid "The characters read by the barcode scanner don't match the barcode"
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:109
msgid "TM-U230"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:122
msgid "By default, most barcode scanners are configured in the US QWERTY format. If the barcode scanner uses a different layout, go to the form view of the device (:menuselection:`IoT App --> Devices --> Barcode Device`) and select the correct format."
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:110
msgid "TM-P60"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:111
msgid "TMP-P60II"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:113
msgid "Bypass this issue by configuring the printer to use the `ESC *` command instead."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:116
msgid "Process to force ESC * command"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:119
msgid "Epson printer compatibility"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:121
msgid "The first step is to check whether the printer is incompatible with `GS v 0` command."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:125
msgid "`Epson GS v 0 documentation <https://reference.epson-biz.com/modules/ref_escpos/index.php? content_id=94>`_ for `GS v 0` compatible printers."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:127
msgid "Nothing happens when a barcode is scanned"
msgid "`Epson ESC * documentation <https://reference.epson-biz.com/modules/ref_escpos/index.php ?content_id=88>`_ for `ESC *` compatible printers."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:129
msgid "Make sure that the correct device is selected in the :menuselection:`Point of Sale` configuration and that the barcode is configured to send an `ENTER` character (keycode 28) at the end of every barcode. To do so, navigate to :menuselection:`PoS app --> 3-Dot Menu on the PoS --> IoT Box section --> Edit`."
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:130
msgid "If the printer is not compatible with the `ESC *` command then the following process is not possible. Should the printer be compatible to use the `ESC *` command to print, follow this process to configure the printer with the :abbr:`IoT (Internet of Things)` box."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:135
msgid "IoT box configuration for ESC *"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:137
msgid "To configure the :abbr:`IoT (Internet of Things)` box to use the `ESC *` command to print, go to the :abbr:`IoT (Internet of Things)` box homepage by navigating to :menuselection:`IoT app --> IoT Boxes`. Then click on the :guilabel:`IP address` and this will direct to the :abbr:`IoT (Internet of Things)` box homepage."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:142
msgid "**Choosing the printer**"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:144
msgid "Now click on the :guilabel:`Printers server` button. This will redirect the browser to the *CUPS* page. Next, go to :menuselection:`Administration --> Printers --> Add Printer`, choose the printer that should be modified, and then click :guilabel:`Continue`."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:149
msgid "If the name of the printer is still uncertain, take the following steps:"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:151
msgid "Take note of the listed printers on the *CUPS* page."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:152
msgid "Turn the printer off and refresh the page."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:153
msgid "Now compare the difference with the first list to see which printer disappeared."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:154
msgid "Turn the printer back on and refresh the page again."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:155
msgid "Double-check the list again to see if the printer re-appears."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:156
msgid "The printer that disappeared and reappears again on the listed printers is the name of the printer in question."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:160
msgid "This can be :guilabel:`Unknown` under :guilabel:`Local printers`."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:162
msgid "**CUPS naming convention**"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:164
msgid "`CUPS` will prompt the admin for three pieces of information: the :guilabel:`Name`, :guilabel:`Description` and the :guilabel:`Location`. The last two pieces of information do not need to be specific, however, the :guilabel:`Name` should follow a particular convention to work with the `ESC *` command."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:169
msgid "The :guilabel:`Name` should match this convention: `<printer_name>__IMC_<param_1>_<param_2>_..._<param_n>__`"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:172
msgid "A breakdown of the naming convention:"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:174
msgid "`printer_name`: This is the printer name. It can be any character as long as it does not contain `_`, `/`, `#`, or ` ` (space character)."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:176
msgid "`IMC`: This stands for *Image Mode Column* (the simplified name for `ESC *`)."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:177
msgid "`param_1`: This stands for the specific parameter:"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:179
msgid "`SCALE<X>`: Scale of the picture (with the same aspect ratio). `X` should be an integer describing the scale percentage that should be used."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:183
msgid "`100` is the original size, `50` is half the size, `200` is twice the size."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:185
msgid "`LDV`: *Low Density Vertical* (will be set to *High Density Vertical* if not specified)."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:186
msgid "`LDH`: *Low Density Horizontal* (will be set to *High Density Horizontal* if not specified)."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:189
msgid "*Density* parameters might need to be configured in a particular way depending on the printer model."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:193
msgid "Visit `Epson's ESC * documentation <https://reference.epson-biz.com/modules/ref_escpos/index.php?content_id=88>`_ and click on the printer model printer in the table above to see if the printer should set these parameters."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:198
msgid "The following are examples of proper and improper name formatting:"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:200
msgid "Proper name formatting:"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:202
msgid "`EPSONTMm30II__IMC__`"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:203
msgid "`EPSON_TM_U220__IMC_LDV_LDH_SCALE80__`"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:205
msgid "Improper name formatting (this will not prevent printing, but the result might not have the expected printed output):"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:208
msgid "`EPSON TMm 30II` -> The name can't have spaces."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:209
msgid "`EPSONTMm30II` -> The name itself is correct, but it won't use `ESC *`."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:210
msgid "`EPSONTMm30II__IMC` -> This name is missing the end `__`."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:211
msgid "`EPSONTMm30II__IMC_XDV__` -> The parameter `XDV` does not match any existing parameters."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:212
msgid "`EPSONTMm30II__IMC_SCALE__` -> The parameter `SCALE` is missing the scale value."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:214
msgid "**Finish adding a printer**"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:216
msgid "After setting the name of the printer with the appropriate naming convention, click :guilabel:`Continue`. Next, set the :guilabel:`Make` value to :guilabel:`Raw` and for the :guilabel:`Model` value, set this to :guilabel:`Raw Queue (en)`."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:220
msgid "After completing these steps, click :guilabel:`Add Printer`. If everything was done correctly, the page should redirect to the *Banners* page."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:223
msgid "At this point the printer should have been created, now the :abbr:`IoT (Internet of Things)` box just needs to detect it and then sync to Odoo's server (this could take a few minutes)."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:226
msgid "**Adding the printer to Odoo PoS**"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:228
msgid "Once the printer is visible on the Odoo database, don't forget to choose it in the :abbr:`PoS (Point of Sale)`configuration as the :abbr:`IoT (Internet of Things)` printer. Navigate to :menuselection:`Pos App --> Settings --> Connected Devices --> IoT Box --> Receipt Printer --> Save`."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:234
msgid "If the printer was set up incorrectly (it is still printing random text or the printed receipt is too big or small), then it cannot be modified via the printer name with *CUPS*. Instead, the above process can be repeated to set up another printer from scratch to create one with modified parameters."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:239
msgid "**Example setup of the Epson TM-U220B printer using ESC**"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:244
msgid "The following is an example of the troubleshooting process for a TM-U220B printer model using the `ESC *` command. The receipt pictured below is an example of a receipt that is printing correctly due to proper formatting (in theory):"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0
msgid "Properly formatted receipt picture from a demo database."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:252
msgid "Trying to print this receipt right-away prior to the proper formatting will not work as the TM-U220B printer model does not support `GS v 0`. Instead random characters will print:"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0
msgid "Printer paper with seemingly random characters."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:259
msgid "To properly configure formatting for the Epson TM-U220B printer model take the following steps."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:261
msgid "After consulting Epson's website for compatibility for both of the commands: `GS v 0 <https://reference.epson-biz.com/modules/ref_escpos/index.php?content_id=94>`_ and `ESC * <https://reference.epson-biz.com/modules/ref_escpos/index.php?content_id=88>`_, it can be seen that indeed the TM-U220B is not compatible with `GS v 0`, but is compatible with `ESC *`."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0
msgid "Epson compatibility evaluation from Epson website."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:270
msgid "When adding the printer, *CUPS* will ask which printer should be added:"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0
msgid "Administration menu, add printer selection."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:276
msgid "In this case, the printer is connected via :abbr:`USB (Universal Serial Bus)` so it won' be part of the :guilabel:`Discovered Network Printers`. Instead it is likely part of the :guilabel:`Unknown` selection under :guilabel:`Local Printers`. By unplugging the printer's :abbr:`USB (Universal Serial Bus)` cable from the :abbr:`IoT (Internet of Things)` box and refreshing the page, the :guilabel:`Unknown` printer disappears. By plugging it back in, the printer reappears, so it can be said that this is the printer in question."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:283
msgid "For the naming convention, since it will need to print using the `ESC *` command, it is imperative to add `__IMC`. Reference the printer model on `Epson's ESC * site <https://reference.epson-biz.com/modules/ref_escpos/index.php?content_id=88>`_ to find out more about the *density* parameters."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0
msgid "Epson TM-U220 specifications on manufacturer's website."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:292
msgid "For this particular model, TM-U220, `m` should be equal to 0 or 1. While referencing the :guilabel:`Description` below the pink box in the above picture, the `m` values could be 0, 1, 32 or 33. So in this printers case, the `m` value can NOT be 32 or 33 (otherwise there will be random characters printed)."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:297
msgid "The table includes the numeric values: 32 and 33, they both occur if the :guilabel:`Number of bits for vertical data` is set to 24. This means that is a *High Vertical Density*. In the case of configuring the Epson TM-U220, the *Low Vertical Density* will need to be forced, as this printer model does not support *High Vertical Density* for this command `ESC *`."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:302
msgid "To add a *Low Vertical Density*, add the `LDV` parameter to the naming convention."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0
msgid "Add a *Low Vertical Density* (the `LDV` parameter) to the naming convention."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:308
msgid "Click :guilabel:`Continue` to proceed. Next, set the :guilabel:`Make` value to :guilabel:`Raw` and for the :guilabel:`Model` value, set this to :guilabel:`Raw Queue (en)`."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0
msgid "Epson TM-U220 specifications on manufacturers website."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:315
msgid "However when trying to print with the naming convention: `EpsonTMU220B__IMC_LDV__`, it will print the receipt, but it will be too big and outside the margin. To resolve this, add a new printer (and naming convention) with the `SCALE<X>` parameter to adapt to our receipt size."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:319
msgid "Here are some examples:"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:324
msgid "Printer Naming Convention"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:325
msgid "`EpsonTMU220B__IMC_LDV__`"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:326
msgid "`EpsonTMU220B__IMC_LDV_SCALE75__`"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:327
msgid "`EpsonTMU220B__IMC_LDV_LDH__`"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:328
msgid "`EpsonTMU220B__IMC_LDV_LDH_SCALE35__`"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0
msgid "Receipt example format."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0
msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV__."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0
msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_SCALE75__."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0
msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH__."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0
msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH_SCALE35__."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:346
msgid "The Zebra printer doesn't print anything"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:348
msgid "Zebra printers are quite sensitive to the format of the Zebra Programming Language (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 --> User Interface --> Views` in :ref:`developer mode <developer-mode>` and look for the corresponding template."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:355
msgid "Check out Zebra's instructions on printing :abbr:`ZPL (Zebra Programming Language)` files `here <https://supportcommunity.zebra.com/s/article/Print-a-zpl-file-using-the-Generic-Text-Printer>`_."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:362
msgid "The characters read by the barcode scanner don't match the barcode"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:364
msgid "By default, most barcode scanners are configured in the US QWERTY format. If the barcode scanner uses a different layout, go to the form view of the device (:menuselection:`IoT App --> Devices --> Barcode Device`) and select the correct format."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:369
msgid "Nothing happens when a barcode is scanned"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:371
msgid "Make sure that the correct device is selected in the :menuselection:`Point of Sale` configuration and that the barcode is configured to send an `ENTER` character (keycode 28) at the end of every barcode. To do so, navigate to :menuselection:`PoS app --> 3-Dot Menu on the PoS --> IoT Box section --> Edit`."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:377
msgid "The barcode scanner is detected as a keyboard"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:138
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:380
msgid "Some barcode scanners do not advertise themselves as barcode scanners but as a USB keyboard instead, and will not be recognized by the :abbr:`IoT (Internet of Things)` box."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:141
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:383
msgid "The device type can be manually changed by going to its form view (:menuselection:`IoT App --> Devices --> Barcode Device`) and activating the :guilabel:`Is scanner` option."
msgstr ""
@ -1657,11 +2001,11 @@ msgstr ""
msgid "Modifying the form view of the barcode scanner."
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:152
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:394
msgid "The cash drawer does not open"
msgstr ""
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:154
#: ../../content/applications/productivity/iot/config/troubleshooting.rst:396
msgid "The cash drawer should be connected to the printer and the :guilabel:`Cash drawer` checkbox should be ticked in the :abbr:`PoS (Point of Sale)` configuration. To do so, navigate to :menuselection:`POS app --> 3-Dot Menu on the POS --> IoT Box section --> Edit --> Receipt Printer --> Cashdrawer checkbox`."
msgstr ""
@ -1950,15 +2294,13 @@ msgid "On a quality check form, the :guilabel:`Type` of check can also be specif
msgstr ""
#: ../../content/applications/productivity/iot/devices/camera.rst:58
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:66
#: ../../content/applications/productivity/iot/devices/printer.rst:70
msgid ":doc:`../../../inventory_and_mrp/manufacturing/quality_control/quality_control_points`"
msgid ":doc:`/applications/inventory_and_mrp/quality/quality_management/quality_control_points`"
msgstr ""
#: ../../content/applications/productivity/iot/devices/camera.rst:59
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:67
#: ../../content/applications/productivity/iot/devices/printer.rst:71
msgid ":doc:`../../../inventory_and_mrp/manufacturing/quality_control/quality_alerts`"
msgid ":doc:`/applications/inventory_and_mrp/quality/quality_management/quality_alerts`"
msgstr ""
#: ../../content/applications/productivity/iot/devices/camera.rst:62
@ -2101,6 +2443,14 @@ msgstr ""
msgid "On a quality check detail form, the :guilabel:`Type` of check can also be specified to :guilabel:`Measure`. Access a new quality check detail page, by navigating to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New`."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:66
msgid ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_control_points`"
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:67
msgid ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_alerts`"
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:70
msgid "Link a measurement tool to a work center in the Manufacturing app"
msgstr ""

124
locale/sources/sales.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-09-12 13:54+0000\n"
"POT-Creation-Date: 2023-10-09 13:19+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1477,10 +1477,12 @@ msgid "Windows 10 & Linux OS"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:62
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:191
msgid "Generate a self-signed certificate"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:64
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:193
msgid "Navigate to the ePOS' IP address (e.g., `https://192.168.1.25`) and force the connection by clicking :guilabel:`Advanced` and :guilabel:`Proceed to [IP address] (unsafe)`."
msgstr ""
@ -1489,35 +1491,43 @@ msgid "warning page about the connection privacy on Google Chrome"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:72
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:201
msgid "Warning page on Google Chrome, Windows 10"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:74
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:203
msgid "Then, sign in using your printer credentials to access the ePOS printer settings. To sign in, enter `epson` in the :guilabel:`ID` field and your printer serial number in the :guilabel:`Password` field."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:78
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:207
msgid "Click :guilabel:`Certificate List` in the :guilabel:`Authentication` section, and click :guilabel:`create` to generate a new **Self-Signed Certificate**. The :guilabel:`Common Name` should be automatically filled out. If not, fill it in with the printer IP address number. Select the years the certificate will be valid in the :guilabel:`Validity Period` field, click :guilabel:`Create`, and :guilabel:`Reset` or manually restart the printer."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:85
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:214
msgid "The self-signed certificate is generated. Reload the page and click :guilabel:`SSL/TLS` in the :guilabel:`Security` section to ensure **Selfsigned Certificate** is correctly selected in the :guilabel:`Server Certificate` section."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:89
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:218
msgid "Export a self-signed certificate"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:91
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:220
msgid "The export process is heavily dependent on the :abbr:`OS (Operating System)` and the browser. Start by accessing your ePOS printer settings on your web browser by navigating to its IP address (e.g., `https://192.168.1.25`). Then, force the connection as explained in the **Generate a self-signed certificate tab**."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:96
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:225
msgid "If you are using **Google Chrome**,"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:98
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:227
msgid "click :guilabel:`Not secure` next to the search bar, and :guilabel:`Certificate is not valid`;"
msgstr ""
@ -1526,19 +1536,24 @@ msgid "Connection to the printer not secure button in Google Chrome browser."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:104
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:233
msgid "go to the :guilabel:`Details` tab and click :guilabel:`Export`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:105
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:234
msgid "add `.crt` at the end of the file name to ensure it has the correct extension;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:106
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:235
msgid "select :guilabel:`Base64-encoded ASCII, single certificate`, at the bottom of the pop-up window;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:108
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:125
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:237
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:254
msgid "save, and the certificate is exported."
msgstr ""
@ -1548,14 +1563,17 @@ msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:114
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:168
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:243
msgid "If you are using **Mozilla Firefox**,"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:116
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:245
msgid "click the **lock-shaped** icon on the left of the address bar;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:117
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:246
msgid "go to :menuselection:`Connection not secure --> More information --> Security tab --> View certificate`;"
msgstr ""
@ -1564,10 +1582,12 @@ msgid "Connection is not secure button in Mozilla Firefox browser"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:123
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:252
msgid "scroll down to the :guilabel:`Miscellaneous` section;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:124
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:253
msgid "click :guilabel:`PEM (cert)` in the :guilabel:`Download` section;"
msgstr ""
@ -1661,7 +1681,7 @@ msgid "Mac OS"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:179
msgid "To secure the connection on a Mac:"
msgid "On Mac OS, you can secure the connection for all browsers by following these steps:"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:181
@ -1677,42 +1697,118 @@ msgid "reboot the printer so you can use it with any other browser."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:186
msgid "To generate and export an SSL certificate and send it to IOS devices, open **Google Chrome** or **Mozilla Firefox**. Then,"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0
msgid "Warning page about the connection privacy on Google Chrome"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0
msgid "Connection to the printer not secure button in Google Chrome"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:240
msgid "Make sure that the certificate ends with the extension `.crt`. Otherwise, some browsers might not find the file during the import process."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0
msgid "Connection is not secure button in Mozilla Firefox"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:256
msgid "Android OS"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:188
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:258
msgid "To import an SSL certificate into an Android device, first create and export it from a computer. Next, transfer the `.crt` file to the device using email, Bluetooth, or USB. Once the file is on the device,"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:192
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:262
msgid "open the settings and search for `certificate`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:193
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:263
msgid "click :guilabel:`Certificate AC` (Install from device storage);"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:194
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:264
msgid "select the certificate file to install it on the device."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:197
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:267
msgid "The specific steps for installing a certificate may vary depending on the version of Android and the device manufacturer."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:202
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:270
msgid "iOS"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:272
msgid "To import an SSL certificate into an iOS device, first create and export it from a computer. Then, transfer the `.crt` file to the device using email, Bluetooth, or any file-sharing service."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:276
msgid "Downloading this file triggers a warning pop-up window. Click :guilabel:`Allow` to download the configuration profile, and close the second pop-up window. Then,"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:279
msgid "go to the **Settings App** on the iOS device;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:280
msgid "click :guilabel:`Profile Downloaded` under the user's details box;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:281
msgid "locate the downloaded `.crt` file and select it;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:282
msgid "click :guilabel:`Install` on the top right of the screen;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:283
msgid "if a passcode is set on the device, enter the passcode;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:284
msgid "click :guilabel:`Install` on the top right of the certificate warning screen and the pop-up window;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:286
msgid "click :guilabel:`Done`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:290
msgid "The certificate is installed, but it still needs to be authenticated. To do so,"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:292
msgid "go to :menuselection:`Settings --> General --> About > Certificate Trust Settings`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:293
msgid "enable the installed certificate using the **slide button**;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:294
msgid "click :guilabel:`Continue` on the pop-up window."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:297
msgid "If you need to export SSL certificates from an operating system or web browser that has not been mentioned, search for `export SSL certificate` + `the name of your browser or operating system` in your preferred search engine."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:205
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:300
msgid "Similarly, to import SSL certificates from an unmentioned OS or browser, search for `import SSL certificate root authority` + `the name of your browser or operating system` in your preferred search engine."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:210
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:305
msgid "Check if the certificate was imported correctly"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:212
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:307
msgid "To confirm your printer's connection is secure, connect to its IP address using HTTPS. For example, navigate to `https://192.168.1.25` in your browser. If the SSL certificate has been applied correctly, you should no longer see a warning page, and the address bar should display a padlock icon, indicating that the connection is secure."
msgstr ""
@ -3307,11 +3403,11 @@ msgid "barcode setting in the Inventory application"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:21
msgid ":doc:`Set up a barcode scanner<../../../inventory_and_mrp/inventory/barcode/setup/hardware>`"
msgid ":doc:`Set up a barcode scanner </applications/inventory_and_mrp/barcode/setup/hardware>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:22
msgid ":doc:`Activate barcode scanners<../../../inventory_and_mrp/inventory/barcode/setup/software>`"
msgid ":doc:`Activate barcode scanners </applications/inventory_and_mrp/barcode/setup/software>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:24
@ -3842,7 +3938,7 @@ msgid "In addition, for your B2B clients, it is currently required to manually r
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:92
msgid "For :doc:`TaxCloud <../../../finance/accounting/taxes/taxcloud>` users: invoices created from Amazon sales orders are **not** synchronized with TaxCloud, since Amazon already includes them in its own tax report to TaxCloud."
msgid "For :doc:`TaxCloud <../../../finance/accounting/taxes/taxcloud>` users: invoices created from Amazon sales orders are **not** synchronized with TaxCloud, since Amazon already includes them in its own tax report to TaxCloud. (decommissioning TaxCloud integration in Odoo 17+)"
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector/manage.rst:97

4
locale/sources/services.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-09-12 13:54+0000\n"
"POT-Creation-Date: 2023-10-09 13:19+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1815,7 +1815,7 @@ msgid "Edit the :guilabel:`Chat Input Placeholder` to change the text that appea
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:192
msgid "Change the :guilabel:`Livechat Button Color` and and the :guilabel:`Channel Header Color` by clicking a color bubble to open the color selection window. Click the refresh icon to the right of the color bubbles to reset the colors to the default selection."
msgid "Change the :guilabel:`Livechat Button Color` and the :guilabel:`Channel Header Color` by clicking a color bubble to open the color selection window. Click the refresh icon to the right of the color bubbles to reset the colors to the default selection."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:197