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

[I18N] *: export translations

Browse Source 
closes odoo/documentation#6074

X-original-commit: ea123b8a3c
Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
This commit is contained in:
Martin Trigaux 2023-10-09 14:00:50 +02:00
parent a2f570fd81
commit f6a43ac7cc
8 changed files with 2469 additions and 1869 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

402
locale/sources/administration.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo saas-15.2\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-09-12 05:05+0000\n"
"POT-Creation-Date: 2023-10-09 12:00+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,299 +352,279 @@ 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-running requests such as long polling. 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:369
#: ../../content/administration/install/deploy.rst:225
#: ../../content/administration/install/deploy.rst:373
msgid "LiveChat"
msgstr ""
#: ../../content/administration/install/deploy.rst:217
msgid "In multiprocessing, a dedicated LiveChat worker is automatically started and listening on :option:`the longpolling port <odoo-bin --longpolling-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 ``/longpolling/`` to the longpolling 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:`--longpolling-port <odoo-bin --longpolling-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 ``/longpolling`` 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:343
#: ../../content/administration/install/deploy.rst:347
msgid "Odoo as a WSGI Application"
msgstr ""
#: ../../content/administration/install/deploy.rst:345
#: ../../content/administration/install/deploy.rst:349
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:351
#: ../../content/administration/install/deploy.rst:355
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:356
#: ../../content/administration/install/deploy.rst:360
msgid "Cron Workers"
msgstr ""
#: ../../content/administration/install/deploy.rst:358
msgid "To run cron jobs for an Odoo deployment as a WSGI application requires"
#: ../../content/administration/install/deploy.rst:362
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:360
msgid "A classical Odoo (run via ``odoo-bin``)"
#: ../../content/administration/install/deploy.rst:367
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:361
msgid "Connected to the database in which cron jobs have to be run (via :option:`odoo-bin -d`)"
msgstr ""
#: ../../content/administration/install/deploy.rst:363
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:371
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:376
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:375
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 HTTP requests but doesn't need a lot of processing power. All requests whose path starts with ``/longpolling`` 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:381
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 ``/longpolling`` are directed to this server, either on the :option:`--http-port <odoo-bin --http-port>` (multi-threading server) or on the :option:`--longpolling-port <odoo-bin --longpolling-port>` (multi-processing server)."
msgstr ""
#: ../../content/administration/install/deploy.rst:383
msgid "Deploy a threaded version of Odoo (instead of a process-based preforking one) and redirect only requests to URLs starting with ``/longpolling/`` to that Odoo, this is the simplest and the longpolling URL can double up as the cron instance."
msgstr ""
#: ../../content/administration/install/deploy.rst:387
msgid "Deploy an evented Odoo via ``odoo-gevent`` and proxy requests starting with ``/longpolling/`` to :option:`the longpolling port <odoo-bin --longpolling-port>`."
msgstr ""
#: ../../content/administration/install/deploy.rst:392
#: ../../content/administration/install/deploy.rst:388
msgid "Serving Static Files"
msgstr ""
#: ../../content/administration/install/deploy.rst:394
#: ../../content/administration/install/deploy.rst:390
msgid "For development convenience, Odoo directly serves all static files 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:398
#: ../../content/administration/install/deploy.rst:394
msgid "Odoo static files live in each module's ``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:402
#: ../../content/administration/install/deploy.rst:398
#: ../../content/administration/upgrade.rst:122
msgid "Todo"
msgstr ""
#: ../../content/administration/install/deploy.rst:402
#: ../../content/administration/install/deploy.rst:398
msgid "test whether it would be interesting to serve filestored attachments via this, and how (e.g. possibility of mapping ir.attachment id to filestore hash in the database?)"
msgstr ""
#: ../../content/administration/install/deploy.rst:409
#: ../../content/administration/install/deploy.rst:405
msgid "Security"
msgstr ""
#: ../../content/administration/install/deploy.rst:411
#: ../../content/administration/install/deploy.rst:407
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:415
#: ../../content/administration/install/deploy.rst:411
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:421
#: ../../content/administration/install/deploy.rst:417
msgid "When deploying an internet-facing server, please be sure to consider the following security-related topics:"
msgstr ""
#: ../../content/administration/install/deploy.rst:424
#: ../../content/administration/install/deploy.rst:420
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:427
#: ../../content/administration/install/deploy.rst:423
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:432
#: ../../content/administration/install/deploy.rst:428
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:436
#: ../../content/administration/install/deploy.rst:432
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:443
#: ../../content/administration/install/deploy.rst:439
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:449
#: ../../content/administration/install/deploy.rst:445
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:454
#: ../../content/administration/install/deploy.rst:450
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:458
#: ../../content/administration/install/deploy.rst:454
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:461
#: ../../content/administration/install/deploy.rst:457
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:468
#: ../../content/administration/install/deploy.rst:464
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:474
#: ../../content/administration/install/deploy.rst:470
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:478
#: ../../content/administration/install/deploy.rst:474
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:482
#: ../../content/administration/install/deploy.rst:478
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:486
#: ../../content/administration/install/deploy.rst:482
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:497
#: ../../content/administration/install/deploy.rst:493
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:508
#: ../../content/administration/install/deploy.rst:504
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:511
#: ../../content/administration/install/deploy.rst:507
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:510
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:518
msgid "Blocking Brute Force Attacks"
msgstr ""
@ -1007,27 +987,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 ""
@ -1602,32 +1586,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 ""
@ -2792,6 +2888,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 ""
@ -4494,10 +4594,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 ""

4
locale/sources/developer.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo saas-15.2\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-09-12 05:05+0000\n"
"POT-Creation-Date: 2023-10-09 12:00+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"
@ -20314,7 +20314,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

2911
locale/sources/finance.pot
View File

File diff suppressed because it is too large Load Diff

305
locale/sources/inventory_and_mrp.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo saas-15.2\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-09-12 05:05+0000\n"
"POT-Creation-Date: 2023-10-09 12:00+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"
@ -366,7 +366,6 @@ msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:88
#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:14
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:14
#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:16
#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:51
#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:16
@ -1288,6 +1287,7 @@ msgid "To change the day, click the :guilabel:`31`, and change it to a day withi
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:194
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:115
msgid "Then, to change the month, click :guilabel:`December` to reveal the drop-down menu, and select the desired month."
msgstr ""
@ -1352,35 +1352,123 @@ msgid "Cycle counts"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:5
msgid "In most companies, the stock is only counted once a year. That's why by default, after making an inventory adjustment in Odoo, the scheduled date for the next count is set on the 31st of December. However, for some businesses it's crucial to have an accurate inventory count at all times."
msgid "For most companies, warehouse stock only needs to be counted once a year. This is why, by default, after making an *inventory adjustment* in Odoo, the scheduled date for the next inventory count is set for the 31st of December of the current year."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:10
msgid "The goal of cycle counts is to keep critical stock levels accurate by counting more often at key locations."
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:9
msgid "However, for some businesses, it's crucial to have an accurate inventory count at all times. These companies use *cycle counts* to keep critical stock levels accurate. Cycle counting is a method by which companies count their inventory more often in certain *locations*, to ensure that their physical inventory counts match their inventory records."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:16
msgid "In Odoo, cycle counts are location-based. The frequency of the counts is defined by the storage location. To activate storage locations, go to :menuselection:`Inventory --> Configuration --> Settings --> Warehouse` and activate the :guilabel:`Storage Locations` setting. Next, click :guilabel:`Save` to apply the setting."
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:15
msgid "Activate storage locations"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:17
msgid "In Odoo, cycle counts are location-based. Therefore, the *storage locations* feature needs to be enabled before performing a cycle count."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:20
msgid "To enable this feature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Warehouse` section. Then, click the checkbox next to :guilabel:`Storage Locations`. Click :guilabel:`Save` to save all changes."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:-1
msgid "Enable Storage Locations in Odoo settings."
msgid "Enabled storage locations setting in inventory settings."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:26
msgid "Change the inventory frequency"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:28
msgid "To change a location's inventory frequency, first, go to the locations by clicking :menuselection:`Inventory --> Configuration --> Locations`."
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:29
msgid "Change inventory count frequency by location"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:31
msgid "Then, click on a location to open the location settings. Next, click on :guilabel:`Edit`. In the :guilabel:`Inventory Frequency (Days)` field, set the number of days. For example, a location that needs an inventory count every 30 days would set the :guilabel:`Inventory Frequency (Days)` value to `30`. Once the value is entered, click :guilabel:`Save` to apply the setting to the location. Now, once an inventory adjustment is applied to this location, the next scheduled count date will be automatically set based on the number of days in the :guilabel:`Inventory Frequency (Days)` setting."
msgid "Now that the storage locations setting is enabled, the inventory count frequency can be changed for specific locations created in the warehouse."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:34
msgid "To view and edit locations, navigate to :menuselection:`Inventory app --> Configuration --> Locations`. This reveals a :guilabel:`Locations` page containing every location currently created and listed in the warehouse."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:38
msgid "From this page, click into a location to reveal the settings and configuration page for that location. Click :guilabel:`Edit` to edit the location settings."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:41
msgid "Under the :guilabel:`Cyclic Inventory` section, locate the :guilabel:`Inventory Frequency (Days)` field, which should be set to `0` (if this location has not been edited previously). In this field, change the value to whichever number of days is desired."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:-1
msgid "Edit a location to change the inventory frequency."
msgid "Location frequency setting on location."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:50
msgid "A location that needs an inventory count every 30 days should have the :guilabel:`Inventory Frequency (Days)` value set to `30`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:53
msgid "Once the frequency has been changed to the desired number of days, click :guilabel:`Save` to save changes. Now, once an inventory adjustment is applied to this location, the next scheduled count date is automatically set, based on the value entered into the :guilabel:`Inventory Frequency (Days)` field."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:59
msgid "Count inventory by location"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:61
msgid "To perform a cycle count for a specific location in the warehouse, navigate to :menuselection:`Inventory app --> Operations --> Inventory Adjustments`. This reveals an :guilabel:`Inventory Adjustments` page containing all products currently in stock, with each product listed on its own line."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:66
msgid "From this page, the :guilabel:`Filters` and :guilabel:`Group By` buttons (at the top of the page, under the :guilabel:`Search...` bar), can be used to select specific locations and perform inventory counts."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:-1
msgid "Inventory adjustments page."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:74
msgid "To select a specific location and view all products within that location, click :guilabel:`Group By`, then click :guilabel:`Add Custom Group` to reveal a new drop-down menu to the right."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:77
msgid "Click :guilabel:`Location` from the drop-down menu, then click :guilabel:`Apply`. The page now displays condensed drop-down menus of each location in the warehouse that has products in stock, and a cycle count can be performed for all products in that location."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:82
msgid "In large warehouses with multiple locations and a high volume of products, it might be easier to search for the specific location desired. To do this, from the :guilabel:`Inventory Adjustments` page, click :guilabel:`Filters`. Then, click :guilabel:`Add Custom Filter` to reveal a new menu to the right. Click this menu to reveal three drop-downs."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:87
msgid "For the first field, click and select :guilabel:`Location` from the drop-down. For the second field, leave the :guilabel:`contains` value as is. For the third field, type in the name of the location that is being searched for. Click :guilabel:`Apply` for that location to appear on the page."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:-1
msgid "Applied filters and group by on inventory adjustments page."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:97
msgid "Change full inventory count frequency"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:99
msgid "While cycle counts are typically performed per location, the scheduled date for full inventory counts of everything in-stock in the warehouse can also be manually changed to push the date up sooner than the date listed."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:103
msgid "To modify the default scheduled date, go to :menuselection:`Inventory app --> Configuration --> Settings`. Then, in the :guilabel:`Operations` section, locate the :guilabel:`Annual Inventory Day and Month` setting field, which includes a drop-down that is set to `31` :guilabel:`December` by default."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:-1
msgid "Frequency field in inventory app settings."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:112
msgid "To change the day, click the `31`, and change it to a day within the range `1-31`, depending on the desired month of the year."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:118
msgid "Once all changes have been made, click :guilabel:`Save` to save all changes."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:121
msgid ":doc:`/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products`"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers.rst:5
@ -7769,6 +7857,191 @@ msgstr ""
msgid "Kits are primarily used to bundle components together for organization or sale. To manage multi-level products that require manufactured sub-components, refer to :doc:`this documentation <sub_assemblies>` on sub-assemblies."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:3
msgid "Manufacturing backorders"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:5
msgid "In some cases, the full quantity of a manufacturing order cannot be produced immediately. When this happens, Odoo *Manufacturing* allows for the manufacturing of partial quantities of the order and creates a *backorder* for the remaining amount."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:9
msgid "In the *Manufacturing* app, creating a backorder splits the original manufacturing order into two orders. The reference tag for each order is the tag used for the original order, followed by a hyphen and then an additional number to indicate that it's a backorder."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:14
msgid "A company creates a manufacturing order with the reference tag *WH/MO/00175*, for 10 units of *Product X*. After starting work on the manufacturing order, the employee working the production line realizes there are only enough components in stock to produce five units of the product."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:18
msgid "Instead of waiting for additional stock of the components, they manufacture five units and create a backorder for the remaining five. This splits the manufacturing order into two separate orders: *WH/MO/00175-001* and *WH/MO/00175-002*."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:22
msgid "Order *001* contains the five units that have been manufactured, and is immediately marked as :guilabel:`Done`. Order *002* contains the five units that still need to be manufactured and is marked as :guilabel:`In Progress`. Once the remaining components are available, the employee returns to order *002* and manufactures the remaining units before closing the order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:28
msgid "Create a manufacturing backorder"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:30
msgid "To create a backorder for part of a manufacturing order, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select a manufacturing order with a quantity of two or more or create one by clicking :guilabel:`Create`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:34
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:86
msgid "If a new manufacturing order is created, select a product from the :guilabel:`Product` drop-down menu and enter a quantity of two or more in the :guilabel:`Quantity` field, then click :guilabel:`Confirm` to confirm the order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:38
msgid "After manufacturing the quantity that is being produced immediately, enter that number in the :guilabel:`Quantity` field at the top of the manufacturing order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:-1
msgid "The quantity field on a manufacturing order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:45
msgid "Next, click :guilabel:`Validate`, and a :guilabel:`You produced less than initial demand` pop-up window appears, from which a backorder can be created. Click :guilabel:`Create Backorder` to split the manufacturing order into two separate orders, with the reference tags *WH/MO/XXXXX-001* and *WH/MO/XXXXX-002*."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:-1
msgid "The Create Backorder button on the \"You produced less than initial demand\" pop-up window."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:54
msgid "Order *001* contains the items that have been manufactured, and is closed immediately. Order *002* is the backorder that contains the items that have yet to be manufactured, and remains open, to be completed at a later date."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:58
msgid "Once the remaining units can be manufactured, navigate to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then select the backorder manufacturing order. If all of the remaining units are manufactured immediately, simply click :guilabel:`Validate` to close the order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:63
msgid "If only some of the remaining units are manufactured immediately, create another backorder for the remainder by following the steps detailed in this section."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:67
msgid "Create a backorder from tablet view"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:69
msgid "Backorders for manufacturing orders can also be created from the work order tablet view."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:72
msgid "In order to use tablet view, the *Work Orders* setting must be enabled. To enable it, navigate to :menuselection:`Manufacturing --> Configuration --> Settings`. On the :guilabel:`Settings` page, enable the checkbox next to :guilabel:`Work Orders`, then click :guilabel:`Save` to save the change. This makes the :guilabel:`Work Orders` tab appear on manufacturing orders, from which the tablet view can be opened."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:0
msgid "The Work Orders setting on the Manufacturing settings page."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:82
msgid "To create a backorder from the tablet view, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select a manufacturing order with a quantity of two or more or create one by clicking :guilabel:`Create`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:90
msgid "After confirming the manufacturing order, select the :guilabel:`Work Orders` tab and click the :guilabel:`📱 (tablet view)` button located on the line of the first work order to enter the tablet view."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:-1
msgid "The tablet view button for a work order on a manufacturing order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:97
msgid "Once in tablet view, enter the quantity being manufactured immediately in the :guilabel:`Units` field at the top left of the tablet view."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:-1
msgid "The Units field in the tablet view."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:104
msgid "The steps for the rest of the workflow depend on whether the manufacturing order being processed requires the completion of a single work order or multiple work orders."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:108
msgid "Single work order"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:110
msgid "If the manufacturing order only requires the completion of a single work order, complete the work order, then click :guilabel:`Mark As Done And Close MO`. The manufacturing order is closed and a backorder for the units that still need to be manufactured is created automatically."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:-1
msgid "The Mark As Done And Close MO button in the tablet view of a work order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:118
msgid "Once the remaining units are ready to be manufactured, navigate to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, then select the backorder manufacturing order, which is titled using the reference tag of the original backorder with *002* added to the end."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:122
msgid "On the backorder manufacturing order, select the :guilabel:`Work Orders` tab and click the :guilabel:`📱 (tablet view)` button located on the line of the work order to open the tablet view. If all of the units in the backorder will be completed immediately, simply click :guilabel:`Mark As Done And Close MO` after completing the work order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:127
msgid "If only some of the remaining units will be manufactured immediately, enter the number in the :guilabel:`Units` field at the top left of the tablet view, then click :guilabel:`Mark As Done And Close MO` to create another backorder for the remaining units. The new backorder can be processed using the steps detailed in this section."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:133
msgid "Multiple work orders"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:135
msgid "If the manufacturing order requires the completion of multiple work orders, complete the first work order, and then click :guilabel:`Record Production`. This splits the manufacturing order into two separate orders, titled *WH/MO/XXXXX-001* and *WH/MO/XXXXX-002*, with *XXXXX* being the number of the original order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:-1
msgid "The Record Production button on a work order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:144
msgid "The tablet view defaults to showing the first work order for the *002* manufacturing order. Since this manufacturing order will not be completed immediately, back out of tablet view by clicking the :guilabel:`⬅️ (back)` button twice. Doing so will take you to the *001* order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:148
msgid "To finish the *001* order, select the :guilabel:`Work Orders` tab and click the :guilabel:`tablet view` button located on the line of the next work order. Finally, complete the remaining work orders, then click :guilabel:`Mark As Done And Close MO` to close the manufacturing order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:152
msgid "Once the remaining units are ready to be manufactured, navigate to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, then select the *002* order. Select the :guilabel:`Work Orders` tab and click the :guilabel:`tablet view` button located on the line of the first work order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:157
msgid "If all of the units in the backorder will be completed immediately, simply click :guilabel:`Mark As Done And Close MO` after completing all of the work orders."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:160
msgid "If only some of the remaining units will be manufactured immediately, enter the number in the :guilabel:`Units` field at the top left of the tablet view, then click :guilabel:`Record Production` to create an additional backorder for the remaining units, with *003* at the end of its reference tag."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:165
msgid "The *002* backorder and *003* backorder can be completed by following the steps detailed in this section."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:169
msgid "It is also possible to create a backorder in the middle of a manufacturing order, when some but not all of the work orders have already been completed. Doing so marks the completed work order(s) as :guilabel:`Finished` on the backorder."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:174
msgid "A manufacturing order for four chairs requires the completion of two work orders: *Paint* and *Assemble*. While the paint step can be completed immediately for all four chairs, there are only enough screws to assemble two of them."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:178
msgid "As a result, the employee responsible for producing the chairs begins by painting all four, and marking the *Paint* work order as :guilabel:`Finished` for all of them. Then, they move on to the *Assemble* work order. They assemble two of the four chairs, enter that number in the :guilabel:`Units` field of the tablet view, and click :guilabel:`Record Production`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:183
msgid "A backorder manufacturing order is created for the remaining two chairs. On the backorder, the *Paint* work order is already marked as :guilabel:`Finished`, and only the *Assemble* work order is left to be completed."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:187
msgid "Once more screws are available, the manufacturing employee assembles the remaining chairs and clicks :guilabel:`Mark As Done And Close MO` to complete the *Assemble* work order and close the backorder manufacturing order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:3
msgid "Managing BoMs for product variants"
msgstr ""

178
locale/sources/legal.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo saas-15.2\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-07-07 09:23+0000\n"
"POT-Creation-Date: 2023-10-09 12:00+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"
@ -1994,7 +1994,7 @@ msgid "4.1 Service de correction de Bugs"
msgstr ""
#: ../../content/legal/terms/i18n/enterprise_fr.rst:138
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:145
@ -3184,7 +3184,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
@ -4735,6 +4735,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/saas-15.2/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/saas-15.2/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 ""
@ -4744,7 +4872,7 @@ msgid "`Download PDF <https://www.odoo.com/documentation/saas-15.2/terms_of_sale
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
@ -4772,26 +4900,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 ""
@ -5264,7 +5400,7 @@ msgid "`Download PDF <https://www.odoo.com/documentation/saas-15.2/terms_of_sale
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
@ -5288,25 +5424,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 ""

380
locale/sources/productivity.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo saas-15.2\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-09-12 05:05+0000\n"
"POT-Creation-Date: 2023-10-09 12:00+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 "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 ""
@ -1439,7 +1439,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 ""
@ -1596,42 +1596,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 ""
@ -1639,11 +1983,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 ""

120
locale/sources/sales.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo saas-15.2\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-09-12 05:05+0000\n"
"POT-Creation-Date: 2023-10-09 12:00+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"
@ -1448,10 +1448,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 ""
@ -1460,35 +1462,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 ""
@ -1497,19 +1507,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 ""
@ -1519,14 +1534,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 ""
@ -1535,10 +1553,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 ""
@ -1632,7 +1652,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
@ -1648,42 +1668,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 ""
@ -3611,7 +3707,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

38
locale/sources/websites.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo saas-15.2\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-09-12 05:05+0000\n"
"POT-Creation-Date: 2023-10-09 12:00+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"
@ -136,23 +136,43 @@ msgid "Manage my products"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:3
msgid "How to display several images per product"
msgid "Multiple images per product"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:5
msgid "By default your product web page displays the main image of your product only. If you like to show your products under several angles, you can turn the image into a carrousel."
msgid "When you register several images for a product, only the first image is shown on the main products page. By clicking on the product, visitors can see additional images with the carousel view."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:11
msgid "Check *Several images per product* in :menuselection:`Website Admin --> Configuration --> Settings`."
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:-1
msgid "Showing the carousel view."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:13
msgid "Open a product detail form and upload images from *Images* tab. Hit *Create* in Edit mode to get the upload wizard."
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:12
msgid "Adding multiple images to a product"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:19
msgid "Such extra image are common to all the product variants (if any)."
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:14
msgid "Go to :menuselection:`Website --> Products`, and select a product."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:15
msgid "Go to the :guilabel:`Sales` tab, click :guilabel:`Edit`, and :guilabel:`Add a media`."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:16
msgid "Click the pencil icon to add an image, then click :guilabel:`Save & New` to add additional ones."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:17
msgid "Click :guilabel:`Save & Close` when you are done."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:-1
msgid "Creating extra product media."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:23
msgid "Such extra images are common to all the product variants (if any)."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:3