Compare commits

...

52 Commits

Author SHA1 Message Date
Antoine Vandevenne (anv) a0472c95e5 [IMP] supported_versions: release 18.0
closes odoo/documentation#11118

Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-10-01 06:17:50 +00:00
Tiffany Chang (tic) e75d2dd7dd [I18N] *: export latest terms
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#11078

Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-09-24 07:29:12 +00:00
Julian Roussieau f53cdc64cb [ADD] odoo.sh: a new role tester is added.
Before odoo.sh had two types of role, `user` and `admin`. A third role, `tester`,
was added between the two, and the user role was renamed `developer`.

closes odoo/documentation#11056

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-09-19 15:23:57 +00:00
Odoo Translation Bot 07ed964f7c [I18N] Update translation terms from Transifex 2024-09-15 02:41:48 +02:00
Loredana Perazzo fea2d1270d [IMP] POS: move replicated title into one page
task-3973404

Must come back in 16.0 & 17.0

closes odoo/documentation#11009

Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-09-13 14:30:37 +00:00
Loredana Perazzo 7b841f6eee [IMP] l10n: add 17.0 blackbox certif in table
task-4131387

closes odoo/documentation#11011

Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-09-13 13:26:35 +00:00
Loredana Perazzo c6af8e28fd [IMP] POS: add information about POS categories
task-3984698

Still have to come back in 16 (restrict and start categories) and
saas-17.4 (point of sale tab in product form)

closes odoo/documentation#11003

Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-09-13 11:09:24 +00:00
Audrey (auva) 56b2bb18cb [IMP] contributing/documentation: update documentation guidelines
task-3709518

closes odoo/documentation#10675

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-09-13 09:32:12 +00:00
Odoo Translation Bot 39638b4566 [I18N] Update translation terms from Transifex 2024-09-08 02:42:29 +02:00
Carsten Wolff (cawo) 2a5e686783 [IMP] upgrade: add a note about on-prem script requirements
We often get questions from customers about errors they see running the
upgrade-script, which are caused by restrictions of their environment. Add a
note that mentions the most important requirements to maybe avoid some of these
questions.

closes odoo/documentation#10888

Signed-off-by: Carsten Wolff (cawo) <cawo@odoo.com>
2024-09-05 09:38:00 +00:00
xpl-odoo fcf0b645d1 [IMP] upgrade: better introduce the upgrade process
closes odoo/documentation#10893

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-09-02 07:26:37 +00:00
Odoo Translation Bot 5e63d71f0c [I18N] Update translation terms from Transifex 2024-09-01 02:42:47 +02:00
Odoo Translation Bot ff9cc87e6c [I18N] Update translation terms from Transifex 2024-08-25 02:41:13 +02:00
Tiffany Chang (tic) 9aaa73934d [I18N] *: export latest terms
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#10814

Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-08-20 15:42:41 +00:00
Stanislas Sobieski ca18df8f27 [IMP] odoo.sh: ip changes
closes odoo/documentation#10763

Signed-off-by: Stanislas Sobieski (sts) <sts@odoo.com>
2024-08-19 14:35:41 +00:00
Antoine Vandevenne (anv) 0e3c58de53 [IMP] supported_versions: release saas-17.4
closes odoo/documentation#10789

Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-08-19 09:47:39 +00:00
Louis Wicket (wil) 1725552c89 [FIX] change the display name of Korean to KR in the switcher
According to feedback from our Korean translator,the abbreviation for
Korean is usually KR instead of KO.

This commit updates the name of the language as displayed in the
language switcher.

closes odoo/documentation#10777

Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-08-19 08:43:50 +00:00
Odoo Translation Bot ff96106480 [I18N] Update translation terms from Transifex 2024-08-18 02:41:05 +02:00
Felicious c6e16b3666 [IMP] inventory: costing chart
closes odoo/documentation#10612

Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: kekiss <karaekiss@yahoo.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-08-12 23:28:32 +00:00
Odoo Translation Bot 497d10928e [I18N] Update translation terms from Transifex 2024-08-11 02:40:26 +02:00
Odoo Translation Bot cc0847d887 [I18N] *: fetch 15.0 translations from Transifex 2024-08-06 06:30:44 +00:00
Odoo Translation Bot 1ff56fa577 [I18N] *: fetch 15.0 translations from Transifex 2024-08-06 04:15:44 +00:00
Odoo Translation Bot 0ae7f9666d [I18N] *: fetch 15.0 translations from Transifex 2024-08-06 03:30:44 +00:00
Odoo Translation Bot 688f97bbb3 [I18N] *: fetch 15.0 translations from Transifex 2024-08-06 02:45:43 +00:00
Odoo Translation Bot 2a1b2db60a [I18N] *: fetch 15.0 translations from Transifex 2024-08-06 02:00:44 +00:00
Antoine Vandevenne (anv) 2be7fa1c98 [FIX] developer/reference/data: fix typo in data file example
The attribute of `record` data operations should be `id` and not `name`.

closes odoo/documentation#10599

Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-08-05 15:21:57 +00:00
Odoo Translation Bot bfc47b6c2c [I18N] *: fetch 15.0 translations from Transifex 2024-08-05 07:26:22 +00:00
Odoo Translation Bot bf8e335017 [I18N] *: fetch 15.0 translations from Transifex 2024-08-05 05:47:06 +00:00
masi-odoo 8a0a028f91 [IMP] accounting/l10n_cl: Fiscal PDF report image
Adds image of accepted invoice PDF report with the fiscal elements needed. It replaces the last image used, which had sensitive information of a third party company.

Link to image: https://drive.google.com/file/d/1JYymyUVz_3q6bBg-yrgM_i6Di9gLcqOc/view?usp=sharing

closes odoo/documentation#10434

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-08-01 11:48:15 +00:00
Ricardo Gomes Rodrigues c04c6700f4 [IMP] accounting: add name to hashed fields
This has been done in https://github.com/odoo/odoo/commit/1dcd071b27779e7d6d8f536c7dce7002d27212ba

closes odoo/documentation#9928

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-08-01 11:48:14 +00:00
Antoine Vandevenne (anv) 747e1bab14 [FIX] contributing/development: fix doc reference to tutorials.rst
closes odoo/documentation#10469

Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-07-31 10:21:53 +00:00
xmo-odoo 811b442fcc [FIX] contributing: remove smart quotes
There have been several new odooers who've hit legal/cla mismatches, and after
investigation their email address would be smart quoted in git (e.g.
`<“uid@example.org”>`).

That the documentation itself uses smart quotes is highly suspicious, it would
make sense that new developers just pasted the provided command, updated it to
match, and didn't even notice the quotes were wrong: `git` is perfectly happy
with it, only on reading it back can you realise it's wrong and the guide
doesn't say anything about *that*.

So fix the quotes in the doc, and hopefully that'll resolve the issue.

closes odoo/documentation#10440

Signed-off-by: Xavier Morel (xmo) <xmo@odoo.com>
2024-07-30 10:10:42 +00:00
Felicious a2ce8821f6 [ADD] inventory: storage categories
closes odoo/documentation#10169

Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: pabr-odoo <pabr@odoo.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-07-26 20:04:16 +00:00
Sam Lieber (sali) 97a43ea94e [FIX] accounting/l10n_cl: remove company image
closes odoo/documentation#10387

Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2024-07-26 17:24:46 +00:00
bve-odoo 1f7c0a9b2e [FIX] microsoft_outlook: redirect URL error if not matching
_compute_outlook_uri is using get_base_url, providing the
web.base.url of the database that is subject to changed as
stated on the website documentation: if the user logging-in
is using another URL to connect to the db, and has the
Administration/Settings access right (res.groups: base.group_system)

opw-4056377

closes odoo/documentation#10303

Signed-off-by: Baptiste Vergote (bve) <bve@odoo.com>
2024-07-26 09:27:07 +00:00
Tiffany Chang (tic) 3e8daa8014 [I18N] *: export latest terms
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#10302

Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-07-23 09:10:37 +00:00
Odoo Translation Bot 7439ec721f [I18N] *: export 15.0 source terms 2024-07-20 02:37:02 +00:00
Odoo Translation Bot 71a3dac1e4 [I18N] Update translation terms from Transifex 2024-07-14 02:40:22 +02:00
Odoo Translation Bot 60eb05fecf [I18N] Update translation terms from Transifex 2024-07-07 02:40:27 +02:00
Felicious 4a527db915 [IMP] inventory: bpost customer accounts
closes odoo/documentation#10067

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-07-05 18:51:45 +00:00
“Dallas” 0e783b0dfa [FIX] german localization: Fixed broken GoBD link
If merged, this commit will replace the broken GoBD link with the correct link.

task ID: 4034487

closes odoo/documentation#10074

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-07-04 09:05:57 +00:00
Odoo Translation Bot d13a635d67 [I18N] Update translation terms from Transifex 2024-06-30 02:40:28 +02:00
Odoo Translation Bot 499ead0b98 [I18N] Update translation terms from Transifex 2024-06-23 02:40:34 +02:00
Adrien Widart (awt) 37ca3f1917 [IMP] supported_versions: end of saas-16.4
closes odoo/documentation#9884

Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2024-06-21 15:36:42 +00:00
XPL 51323fba44 [IMP] upgrade: remove ticket go-live mention
The phrase is confusing and leads customers to contact support to carry out
the upgrade for them.

closes odoo/documentation#9880

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-06-21 09:57:56 +00:00
Tiffany Chang (tic) 89c308cad4 [I18N] *: export latest terms
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#9879

Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-06-21 09:57:56 +00:00
guillaume gallant (guga) 3d5ff64bab [IMP] point_of_sale: improve text and replace pictures for Vantiv
task-3005157

closes odoo/documentation#9704

Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-06-20 09:18:45 +00:00
sovi-odoo 8b45c6692f [IMP] accounting/l10n: tell users to install l10n_fr_invoice_addr
In Odoo 15.0, an extra module is necessary to conform to the french
legislation. This will tell users to install it.

task-3856826

closes odoo/documentation#9820

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-06-17 09:13:59 +00:00
Odoo Translation Bot ba0319e9df [I18N] Update translation terms from Transifex 2024-06-16 02:40:29 +02:00
Audrey (auva) f9ab7b716b [FIX] voip: broken contact link
Changed https://www.axivox.com/contact into https://www.axivox.com/en/contact
as it didn't exist (anymore).

closes odoo/documentation#9757

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-06-11 08:10:07 +00:00
Odoo Translation Bot 4d51a12b1c [I18N] Update translation terms from Transifex 2024-06-09 02:40:34 +02:00
Felicious 91a2973306 [ADD] inventory: bpost
closes odoo/documentation#9637

Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: hojo-odoo <123424465+hojo-odoo@users.noreply.github.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-06-07 17:43:24 +00:00
173 changed files with 58511 additions and 22478 deletions
+3 -8
View File
@@ -211,17 +211,12 @@ sphinx.transforms.i18n.docname_to_domain = (
# is populated. If a version is passed to `versions` but is not listed here, it will not be shown.
versions_names = {
'master': "Master",
'18.0': "Odoo 18",
'saas-17.4': "Odoo Online",
'saas-17.2': "Odoo Online",
'saas-17.1': "Odoo Online",
'17.0': "Odoo 17",
'saas-16.4': "Odoo Online",
'saas-16.3': "Odoo Online",
'saas-16.2': "Odoo Online",
'saas-16.1': "Odoo Online",
'16.0': "Odoo 16",
'saas-15.2': "Odoo Online",
'15.0': "Odoo 15",
'14.0': "Odoo 14",
}
# The language names that should be shown in the language switcher, if the config option `languages`
@@ -232,7 +227,7 @@ languages_names = {
'es': 'ES',
'fr': 'FR',
'it': 'IT',
'ko': 'KO',
'ko': 'KR',
'nl': 'NL',
'pt_BR': 'PT',
'ro': 'RO',
+1 -1
View File
@@ -46,7 +46,7 @@ Trigger a database upgrade.
.. seealso::
For more information about the upgrade process, check out the :ref:`Odoo Online upgrade
documentation <upgrade/request-test-database>`.
documentation <upgrade-request-test>`.
.. _odoo_online/duplicate:
@@ -29,3 +29,32 @@ We advise that:
- Your scheduled actions should be
`idempotent <https://stackoverflow.com/a/1077421/3332416>`_: they must not
cause side-effects if they are started more often than expected.
.. _ip-address-change:
How can I automate tasks when an IP address change occurs?
----------------------------------------------------------
**Odoo.sh notifies project administrators of IP address changes.**
Additionally, when the IP address of a production instance changes, an HTTP `GET` request is made
to the path `/_odoo.sh/ip-change` with the new IP address included as a query string parameter
(`new`), along with the previous IP address as an additional parameter (`old`).
This mechanism allows custom actions to be applied in response to the IP address change
(e.g., sending an email, contacting a firewall API, configuring database objects, etc.)
For security reasons, the `/_odoo.sh/ip-change` route is accessible only internally by the platform
itself and returns a `403` response if accessed through any other means.
Here is a pseudo-implementation example:
.. code-block:: python
class IPChangeController(http.Controller):
@http.route('/_odoo.sh/ip-change', auth='public')
def ip_change(self, old=None, new=None):
_logger.info("IP address changed from %s to %s", old, new)
# Then perform whatever action required for your use case, e.g., update an
# ir.config_parameter, send an email, contact an external firewall service's API, ...
return 'ok'
@@ -33,17 +33,17 @@ Manage the Github users who can access your project.
.. image:: settings/interface-settings-collaborators.png
:align: center
There are two levels of users:
There are three levels of users:
* Admin: has access to all features of Odoo.sh.
* User: does not have access to the project settings nor to the production and staging databases.
- :guilabel:`Admin`: has access to all features of an Odoo.sh project.
The user group is meant for developers who can make modifications in your code but are not allowed
to access the production data. Users of this group cannot connect to the production and staging
databases using the *1-click connect* feature, but they can of course use their regular account on
these databases if they have one, using their regular credentials.
- :guilabel:`Tester`: has access to the *Staging* and *Development* databases and their tooling.
This role is for users conducting User Acceptance Tests. Testers can work with copies of
production data but cannot access the production database through the Odoo.sh tooling.
In addition, they cannot use the webshell nor have access to the server logs.
- :guilabel:`Developer`: has access only to the *Development* databases and their tooling. This
role is for developers who propose code modifications but are not allowed to access production
and staging databases through the Odoo.sh tooling.
.. list-table::
:header-rows: 1
@@ -51,83 +51,145 @@ In addition, they cannot use the webshell nor have access to the server logs.
* -
-
- User
- Developer
- Tester
- Admin
* - Development
- History
- |green|
- |green|
- |green|
* -
- 1-click connect
- |green|
- |green|
- |green|
* -
- Logs
- |green|
- |green|
- |green|
* -
- Shell/SSH
- |green|
- |green|
- |green|
* -
- Mails
- |green|
- |green|
* -
- Upgrade
- |green|
- |green|
* -
- Settings
- |green|
- |green|
* - Production & Staging
- |green|
* - Staging
- History
- |green|
- |green|
- |green|
* -
- 1-click connect
-
- |green|
- |green|
* -
- Logs
-
- |green|
- |green|
* -
- Shell/SSH
-
- |green|
- |green|
* -
- Mails
-
- |green|
- |green|
* -
- Monitoring
-
- |green|
- |green|
* -
- Backups
-
-
- |green|
* -
- Upgrade
-
- |green|
- |green|
* -
- Settings
- |green|\*
-
- |green|
- |green|
* - Production
- History
- |green|
- |green|
- |green|
* -
- 1-click connect
-
-
- |green|
* -
- Logs
-
-
- |green|
* -
- Shell/SSH
-
-
- |green|
* -
- Mails
-
-
- |green|
* -
- Monitoring
-
-
- |green|
* -
- Backups
-
-
- |green|
* -
- Upgrade
-
-
- |green|
* -
- Settings
-
-
- |green|
* - Status
-
- |green|
- |green|
- |green|
* - Settings
-
-
-
- |green|
.. note::
\* Only in staging branches
.. warning::
Those roles only apply to the usage of Odoo.sh. It is important to reflect the user roles
attribution within the repository on GitHub. Please refer to the GitHub documentation section on
`Managing a branch protection rule <https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule>`_
for detailed guidance.
.. |green| raw:: html
@@ -149,10 +211,7 @@ Allow public access to your development builds.
.. image:: settings/interface-settings-public.png
:align: center
If activated, this option exposes the Builds page publicly, allowing visitors to connect to your
development builds.
In addition, visitors have access to the logs, shell and mails of your development builds.
If activated, this option exposes the Builds page publicly, allowing visitors to view logs of development builds.
Production and staging builds are excluded, visitors can only see their status.
+20 -56
View File
@@ -31,90 +31,54 @@ This matrix shows the support status of every version.
- On-Premise
- Release date
- End of support
* - Odoo saas~17.2
* - **Odoo 18.0**
- |green|
- |green|
- |green|
- October 2024
- October 2027 (planned)
* - Odoo SaaS 17.4
- |green|
- N/A
- N/A
- July 2024
-
* - Odoo SaaS 17.2
- |green|
- N/A
- N/A
- April 2024
-
* - Odoo saas~17.1
- |green|
- N/A
- N/A
- January 2024
-
* - **Odoo 17.0**
- |green|
- |green|
- |green|
- November 2023
- October 2026 (planned)
* - Odoo saas~16.4
- |green|
- N/A
- N/A
- August 2023
-
* - Odoo saas~16.3
- |red|
- N/A
- N/A
- June 2023
-
* - Odoo saas~16.2
- |red|
- N/A
- N/A
- March 2023
-
* - Odoo saas~16.1
- |red|
- N/A
- N/A
- February 2023
-
* - **Odoo 16.0**
- |green|
- |green|
- |green|
- October 2022
- November 2025 (planned)
* - Odoo saas~15.2
- |red|
- N/A
- N/A
- March 2022
- January 2023
* - Odoo saas~15.1
- |red|
- N/A
- N/A
- February 2022
- July 2022
- October 2025 (planned)
* - **Odoo 15.0**
- |green|
- |green|
- |green|
- |red|
- |red|
- |red|
- October 2021
- November 2024 (planned)
- October 2024
* - **Odoo 14.0**
- |red|
- |red|
- |red|
- October 2020
- November 2023
* - **Odoo 13.0**
- |red|
- |red|
- |red|
- October 2019
- October 2022
* - Older versions
- |red|
- |red|
- |red|
- Before 2019
- Before 2022
- Before 2020
- Before 2023
.. admonition:: Legend
+107 -80
View File
@@ -2,31 +2,55 @@
Upgrade
=======
An upgrade is the process of moving your database from an older version to a newer :doc:`supported
version <supported_versions>` (e.g., Odoo 14.0 to Odoo 16.0). Frequently upgrading is essential as
each version comes with new and improved features, bug fixes, and security patches.
An upgrade involves moving a database from an older version to a newer supported version (e.g., from
Odoo 15.0 to Odoo 17.0). Regular upgrades are crucial as each version offers new features, bug
fixes, and security patches. Using a :doc:`supported version <supported_versions>` is strongly
recommended. Each major version is supported for three years.
.. _upgrade_faq/rolling_release:
Depending on the hosting type and Odoo version used, a database upgrade can be **mandatory**.
.. tabs::
.. group-tab:: Odoo Online
- If a database is on a **major version** (e.g., 15.0, 16.0, 17.0), an upgrade is mandatory
every two years.
- If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade is mandatory
a few weeks after the next version is released. Minor versions are usually released every
three months.
.. group-tab:: Odoo.sh
After the initial three years of support, you will have another two years to complete the
upgrade. You will be notified when an upgrade is required.
.. image:: upgrade/odoo-sh-message.png
:alt: The "unsupported version" popup on Odoo.sh.
.. group-tab:: On-premise
You can stay on the same version indefinitely, even if it is not recommended. Note that the
smaller the version gap, the easier the upgrade should be.
.. spoiler:: Automatic upgrades: Odoo Online's Rolling Release process
The Rolling Release process allows Odoo Online customers to upgrade their database directly from
a message prompt sent to the database administrator as soon as a new version is released. The
invitation to upgrade is only sent if no issues are detected during the automatic tests.
You will receive a notification in your database a few weeks before a mandatory upgrade will be
automatically carried out. You are in control of the process as long as the deadline is not
reached.
.. image:: upgrade/rr-upgrade-message.png
:alt: The upgrade message prompt on the top right of the database
It is strongly recommended to manually :ref:`test the upgrade first <upgrade/test_your_db>`.
Clicking :guilabel:`I want to test first` redirects to `the database manager
<https://www.odoo.com/my/databases/>`_, where it is possible to request an upgraded test database
and check it for any discrepancies.
Concretely, Odoos Upgrade Team performs a silent test upgrade of every database that should be
upgraded. If the test is successful and lasts less than 20 minutes, you can directly trigger the
upgrade from the database. If the test fails, you can test an upgrade using the `database manager
<https://www.odoo.com/my/databases>`_.
It is **not** recommended to click :guilabel:`Upgrade Now` without testing first, as it
immediately triggers the live production database upgrade.
When you are invited to upgrade, it is strongly recommended to :ref:`request an upgraded test
database <upgrade-request-test>` first and spend time :ref:`testing <upgrade-testing>` it.
If the Rolling Release process detects an issue with the upgrade, it will be deactivated until
the issue is resolved.
An automatic upgrade to the next version will be triggered if no action is taken before the
specified due date.
An upgrade does not cover:
@@ -39,46 +63,44 @@ An upgrade does not cover:
.. warning::
If your database contains a **custom module**, you must first upgrade its source code to be
compatible with the new version of Odoo **before upgrading**.
.. TODOUPG : once the page for developers is published, uncomment and link
.. :doc:`first upgrade its source code </developer/reference/upgrade>`
.. _upgrade-nutshell:
Upgrading in a nutshell
-----------------------
=======================
#. Request an upgraded test database (see :ref:`obtaining an upgraded test database
<upgrade/request-test-database>`).
<upgrade-request-test>`).
#. Thoroughly test the upgraded database (see :ref:`testing the new version of the database
<upgrade/test_your_db>`).
<upgrade-testing>`).
#. Report any issue encountered during the testing to Odoo via the `support page
<https://odoo.com/help?stage=migration>`__.
#. Report any issue encountered during the testing to Odoo by going to the `Support page and
selecting "An issue related to my future upgrade (I am testing an upgrade)"
<https://www.odoo.com/help?stage=migration>`_.
#. (If applicable) : upgrade the source code of your custom module to be compatible with the new
#. (If applicable): upgrade the source code of your custom module to be compatible with the new
version of Odoo.
#. Once all issues are resolved and you are confident that the upgraded database can be used as
your main database without any issues, plan the upgrade of your production database.
#. Request the upgrade for the production database, rendering it unavailable for the time it takes
to complete the process (see :ref:`upgrading the production database <upgrade/upgrade-prod>`).
to complete the process (see :ref:`upgrading the production database <upgrade-production>`).
#. Report any issue encountered during the upgrade to Odoo via the `support page
<https://odoo.com/help?stage=post_upgrade>`__.
#. Report any issue encountered during the upgrade to Odoo by going to the `Support page and
selecting "An issue related to my upgrade (production)"
<https://www.odoo.com/help?stage=post_upgrade>`_.
.. TODOUPG: Once the page for developers is published, put this at 4)
.. (see :ref:`upgrading customizations <upgrade/upgrading_customizations>`).
.. _upgrade/request-test-database:
.. _upgrade-request-test:
Obtaining an upgraded test database
-----------------------------------
===================================
The `Upgrade page <https://upgrade.odoo.com/>`_ is the main platform for requesting an upgraded
The `Upgrade page <https://upgrade.odoo.com>`_ is the main platform for requesting an upgraded
database. However, depending on the hosting type, you can upgrade from the command line
(on-premise), the `Odoo Online database manager <https://odoo.com/my/databases>`_, or your `Odoo.sh
project <https://odoo.sh/project>`_.
(on-premise), the Odoo Online `database manager <https://www.odoo.com/my/databases>`_, or your
`Odoo.sh project <https://www.odoo.sh/project>`_.
.. note::
The Upgrade platform follows the same `Privacy Policy <https://www.odoo.com/privacy>`_ as the
@@ -90,7 +112,7 @@ project <https://odoo.sh/project>`_.
.. group-tab:: Odoo Online
Odoo Online databases can be manually upgraded via the `database manager
<https://odoo.com/my/databases>`_.
<https://www.odoo.com/my/databases>`_.
The database manager displays all databases associated with the user's account. Databases
not on the most recent version of Odoo display an arrow in a circle icon next to their name,
@@ -124,8 +146,7 @@ project <https://odoo.sh/project>`_.
.. image:: upgrade/odoo-sh-staging.png
:alt: Odoo.sh project and tabs
The **latest production daily automatic backup** is then sent to the `upgrade platform
<https://upgrade.odoo.com>`_.
The **latest production daily automatic backup** is then sent to the Upgrade platform.
Once the upgrade platform is done upgrading the backup and uploading it on the branch, it is
put in a **special mode**: each time a **commit is pushed** on the branch, a **restore
@@ -141,12 +162,6 @@ project <https://odoo.sh/project>`_.
skipped, the upgraded database is built as soon as it is transferred from the upgrade
platform, and the upgrade mode is exited.
.. TODOUPG : once the page for developers is published, uncomment
.. Check out the :doc:`upgrade for developers'
.. documentation </developer/reference/upgrade>` for more information. In
.. addition, if a module is not needed after an upgrade, :ref:`you can
.. remove customizations <upgrade/remove_customizations>`.
.. group-tab:: On-premise
The standard upgrade process can be initiated by entering the following command line on the
@@ -156,6 +171,21 @@ project <https://odoo.sh/project>`_.
$ python <(curl -s https://upgrade.odoo.com/upgrade) test -d <your db name> -t <target version>
.. note::
This command has some requirements on the environment it runs in:
- Some external commands that must be provided by the operating system, normally found in
any Linux distribution (including WSL). An error will be displayed if one or several of
them are missing.
- The system user that executes the command needs to be configured with access to the
database. Please refer to the PostgreSQL documentation of the `client environment
<https://www.postgresql.org/docs/current/libpq-envars.html>`_ or the `client password
file <https://www.postgresql.org/docs/current/libpq-pgpass.html>`_ for this requirement.
- The script needs to be able to reach one or multiple servers of the upgrade platform
both on TCP port 443 and to any random TCP port in the range between 32768 and 60999.
This can be in conflict with your restrictive firewall and may need an exception added
to the firewall configuration.
The following command can be used to display the general help and the main commands:
.. code-block:: console
@@ -163,7 +193,7 @@ project <https://odoo.sh/project>`_.
$ python <(curl -s https://upgrade.odoo.com/upgrade) --help
An upgraded test database can also be requested via the `Upgrade page
<https://upgrade.odoo.com/>`_.
<https://upgrade.odoo.com>`_.
.. note::
- For security reasons, only the person who submitted the upgrade request can download it.
@@ -184,22 +214,20 @@ project <https://odoo.sh/project>`_.
.. note::
You can request multiple test databases if you wish to test an upgrade more than once.
.. _upgrade/upgrade_report:
.. note::
When an upgrade request is completed, an upgrade report is attached to the successful upgrade
email, and it becomes available in the Discuss app for users who are part of the "Administration
/ Settings" group. This report provides important information about the changes introduced by
the new version.
.. _upgrade/test_your_db:
.. _upgrade-testing:
Testing the new version of the database
---------------------------------------
=======================================
It is essential to spend some time testing the upgraded test database to ensure that you are not
stuck in your day-to-day activities by a change in views, behavior, or an error message once the
upgrade goes live.
It is essential to test the upgraded test database to ensure that you are not stuck in your
day-to-day activities by a change in views, behavior, or an error message once the upgrade goes
live.
.. note::
Test databases are neutralized, and some features are disabled to prevent them from impacting the
@@ -254,9 +282,8 @@ working correctly and to get more familiar with the new version.
This list is **not** exhaustive. Extend the example to your other apps based on your use of Odoo.
If you face an issue while testing your upgraded test database, you can request the assistance of
Odoo via the `support page <https://odoo.com/help?stage=migration>`__ by selecting the option
related to testing the upgrade. In any case, it is essential to report any
problem encountered during the testing to fix it before upgrading your production database.
Odoo by going to the `Support page and selecting "An issue related to my future upgrade (I am
testing an upgrade)" <https://www.odoo.com/help?stage=migration>`_.
You might encounter significant differences with standard views, features, fields, and models during
testing. Those changes cannot be reverted on a case-by-case basis. However, if a change introduced
@@ -274,15 +301,13 @@ module to make it compatible with the new version of Odoo.
- Server actions in the action menu on form views, as well as by selecting multiple records on
list views
.. _upgrade/upgrade-prod:
.. _upgrade-production:
Upgrading the production database
---------------------------------
=================================
Once the :ref:`tests <upgrade/test_your_db>` are completed and you are confident that the upgraded
database can be used as your main database without any issues, it is time to plan the go-live day. It
can be planned in coordination with Odoo's upgrade support analysts, reachable via the `support page
<https://odoo.com/help>`__.
Once the :ref:`tests <upgrade-testing>` are completed and you are confident that the upgraded
database can be used as your main database without any issues, it is time to plan the go-live day.
Your production database will be unavailable during its upgrade. Therefore, we recommend planning
the upgrade at a time when the use of the database is minimal.
@@ -293,21 +318,21 @@ still successful, especially if it takes a long time to finish. Fully rehearsing
process the day before upgrading the production database is also recommended.
.. important::
- Going into production without first testing may lead to:
Going into production without first testing may lead to:
- Users failing to adjust to the changes and new features
- Business interruptions (e.g., no longer having the possibility to validate an action)
- Poor customer experience (e.g., an eCommerce website that does not work correctly)
- Users failing to adjust to the changes and new features
- Business interruptions (e.g., no longer having the possibility to validate an action)
- Poor customer experience (e.g., an eCommerce website that does not work correctly)
The process of upgrading a production database is similar to upgrading a test database with a few
exceptions.
The process of upgrading a production database is similar to upgrading a test database, but with a
few exceptions.
.. tabs::
.. group-tab:: Odoo Online
The process is similar to :ref:`obtaining an upgraded test database
<upgrade/request-test-database>`, except for the purpose option, which must be set to
<upgrade-request-test>`, except for the purpose option, which must be set to
:guilabel:`Production` instead of :guilabel:`Test`.
.. warning::
@@ -317,8 +342,8 @@ exceptions.
.. group-tab:: Odoo.sh
The process is similar to :ref:`obtaining an upgraded test database
<upgrade/request-test-database>` on the :guilabel:`Production` branch.
The process is similar to :ref:`obtaining an upgraded test database <upgrade-request-test>` on
the :guilabel:`Production` branch.
.. image:: upgrade/odoo-sh-prod.png
:alt: View from the upgrade tab
@@ -336,8 +361,6 @@ exceptions.
The update of your custom modules must be successful to complete the entire upgrade process.
Make sure the status of your staging upgrade is :guilabel:`successful` before trying it in
production.
.. TODOUPG : once the page for developers is published, uncomment
.. More information on how to upgrade your custom modules can be found in the :ref:`upgrading customizations documentation <upgrade/upgrading_customizations>`.
.. group-tab:: On-premise
@@ -349,7 +372,8 @@ exceptions.
$ python <(curl -s https://upgrade.odoo.com/upgrade) production -d <your db name> -t <target version>
An upgraded production database can also be requested via the `Upgrade page
<https://upgrade.odoo.com/>`_.
<https://upgrade.odoo.com>`_.
Once the database is uploaded, any modification to your production database will **not** be
present on your upgraded database. This is why we recommend not using it during the upgrade
process.
@@ -359,15 +383,14 @@ exceptions.
a filestore. Therefore, the upgraded database filestore must be merged with the production
filestore before deploying the new version.
In case of an issue with your production database, you can request the assistance of Odoo via the
`support page <https://odoo.com/help?stage=post_upgrade>`__ by selecting the option related to
the upgrade in production.
In case of an issue with your production database, you can request the assistance of Odoo by going
to the `Support page and selecting "An issue related to my future upgrade (I am testing an upgrade)"
<https://www.odoo.com/help?stage=migration>`_.
.. _upgrade/sla:
.. _upgrade-sla:
Service-level agreement (SLA)
-----------------------------
=============================
With Odoo Enterprise, upgrading a database to the most recent version of Odoo is **free**, including
any support required to rectify potential discrepancies in the upgraded database.
@@ -376,8 +399,10 @@ Information about the upgrade services included in the Enterprise Licence is ava
:ref:`Odoo Enterprise Subscription Agreement <upgrade>`. However, this section clarifies what
upgrade services you can expect.
.. _upgrade-sla-covered:
Upgrade services covered by the SLA
===================================
-----------------------------------
Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or self-hosted (On-Premise) can
benefit from upgrade services at all times for:
@@ -391,8 +416,10 @@ benefit from upgrade services at all times for:
Upgrade services are limited to the technical conversion and adaptation of a database (standard
modules and data) to make it compatible with the version targeted by the upgrade.
.. _upgrade-sla-not-covered:
Upgrade services not covered by the SLA
=======================================
---------------------------------------
The following upgrade-related services are **not** included:
Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 20 KiB

After

Width:  |  Height:  |  Size: 14 KiB

@@ -7,7 +7,7 @@ inalterable**, meaning that once an entry has been posted, it can no longer be c
To do so, Odoo can use the **SHA-256 algorithm** to create a unique fingerprint for each posted
entry. This fingerprint is called a hash. The hash is generated by taking an entry's essential data
(the values of the `date`, `journal_id`, `company_id`, `debit`, `credit`, `account_id`, and
(the values of the `name`, `date`, `journal_id`, `company_id`, `debit`, `credit`, `account_id`, and
`partner_id` fields), concatenating it, and inputting it to the SHA-256 hash function, which then
outputs a fixed size (256-bit) string of characters. The hash function is deterministic (:dfn:`the
same input always creates the same output`): any minor modification to the original data would
@@ -35,14 +35,14 @@ The Odoo POS system is certified for the major versions of databases hosted on *
- Odoo Online
- Odoo.sh
- On-Premise
* - Odoo 17.0
- Certified
- Certified
- Not certified
* - Odoo 16.0
- Certified
- Certified
- Not certified
* - Odoo 15.2
- Not certified
- Not certified
- Not certified
* - Odoo 15.0
- Certified
- Certified
@@ -474,11 +474,10 @@ Invoice PDF Report
~~~~~~~~~~~~~~~~~~
Once the invoice is accepted and validated by the SII and the PDF is printed, it includes the
fiscal elements that indicate that the document is fiscally valid:
fiscal elements that indicate that the document is fiscally valid.
.. image:: chile/Chile22.png
:align: center
:alt: Barcode and fiscal elements in the invoice report.
.. image:: chile/accepted-invoice-fiscal-information.png
:alt: Fiscal elements and barcode printed in accepted invoices.
.. important::
If you are hosted in Odoo SH or On-Premise, you should manually install the ``pdf417gen``
Binary file not shown.

Before

Width:  |  Height:  |  Size: 69 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 69 KiB

@@ -2,6 +2,11 @@
France
======
.. important::
You must :doc:`install <../../general/apps_modules>` the **France - Adding Mandatory Invoice
Mentions (Decree no. 2022-1299)** (`l10n_fr_invoice_addr`) module to comply with the `local
legislation <https://www.legifrance.gouv.fr/jorf/id/JORFTEXT000046383394>`_.
.. _france/fec:
FEC - Fichier des Écritures Comptables
@@ -172,7 +172,7 @@ German Tax Accounting Standards: Odoo's guide to GoBD Compliance
**GoBD** stands for `Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern,
Aufzeichnungen und Unterlagen in elektronischer Form sowie zum Datenzugriff
<https://www.bundesfinanzministerium.de/Content/DE/Downloads/BMF_Schreiben/Weitere_Steuerthemen/Abgabenordnung/2019-11-28-GoBD.pdf>`_.
<https://ao.bundesfinanzministerium.de/ao/2021/Anhaenge/BMF-Schreiben-und-gleichlautende-Laendererlasse/Anhang-64/anhang-64.html>`_.
In short, it is a **guideline for the proper management and storage of books, records, and documents
in electronic form, as well as for data access**, that is relevant for the German tax authority, tax
declaration, and balance sheet.
@@ -34,14 +34,14 @@ registration`. On the :guilabel:`Register an application` screen, rename the :gu
and personal Microsoft accounts (e.g. Skype, Xbox)`.
Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the platform, and then input
`https://<odoo base url>/microsoft_outlook/confirm` in the :guilabel:`URL` field. The Odoo base URL
is the canonical domain at which your Odoo instance can be reached in the URL field.
`https://<web base url>/microsoft_outlook/confirm` in the :guilabel:`URL` field. The `web.base.url`
is subject to change depending on the URL used to log in to the database.
.. example::
*mydatabase.odoo.com*, where *mydatabase* is the actual prefix of the database's subdomain,
assuming it's hosted on Odoo.com
.. note::
The documentation about the :ref:`web.base.url <domain-name/web-base-url>` explains how to freeze
a unique URL. It is also possible to add different redirect URLs on the Microsoft app.
After the URL has been added to the field, :guilabel:`Register` the application so it is created.
After the URL has been added to the field, :guilabel:`Register` the application, so it is created.
API permissions
---------------
@@ -82,27 +82,184 @@ Costing method
From the product category's configuration page, choose the desired :guilabel:`Costing Method`:
- :guilabel:`Standard Price`: the default costing method in Odoo. The cost of the product is
manually defined on the product form, and this cost is used to compute the valuation. Even if the
purchase price on a purchase order differs, the valuation will still use the cost defined on the
product form.
- :guilabel:`Average Cost (AVCO)`: calculates the valuation of a product based on the average cost
of that product, divided by the total number of available stock on-hand. With this costing method,
inventory valuation is *dynamic*, and constantly adjusts based on the purchase price of products.
.. note::
When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing Method`, changing the
numerical value in the :guilabel:`Cost` field for products in the respective product category
creates a new record in the *Inventory Valuation* report to adjust the value of the product.
The :guilabel:`Cost` amount will then automatically update based on the average purchase price
both of inventory on hand and the costs accumulated from validated purchase orders.
.. tabs::
- :guilabel:`First In First Out (FIFO)`: tracks the costs of incoming and outgoing items in
real-time and uses the real price of the products to change the valuation. The oldest purchase
price is used as the cost for the next good sold until an entire lot of that product is sold. When
the next inventory lot moves up in the queue, an updated product cost is used based on the
valuation of that specific lot. This method is arguably the most accurate inventory valuation
method for a variety of reasons, however, it is highly sensitive to input data and human error.
.. tab:: Standard Price
The default costing method in Odoo. The cost of the product is manually defined on the product
form, and this cost is used to compute the valuation. Even if the purchase price on a purchase
order differs, the valuation is the cost defined on the product form.
.. list-table::
:header-rows: 1
:stub-columns: 1
* - Operation
- Unit Cost
- Qty On Hand
- Incoming Value
- Inventory Value
* -
- $10
- 0
-
- $0
* - Receive 8 products for $10/unit
- $10
- 8
- 8 * $10
- $80
* - Receive 4 products for $16/unit
- $10
- 12
- 4 * $10
- $120
* - Deliver 10 products
- $10
- 2
- -10 * $10
- $20
* - Receive 2 products for $9/unit
- $10
- 4
- 2 * $10
- $40
.. tab:: Average Cost (AVCO)
Calculates the valuation of a product based on the average cost of that product, divided by
the total number of available stock on-hand. With this costing method, inventory valuation is
*dynamic*, and constantly adjusts based on the purchase price of products.
.. list-table::
:header-rows: 1
:stub-columns: 1
* - Operation
- Unit Cost
- Qty On Hand
- Incoming Value
- Inventory Value
* -
- $0
- 0
-
- $0
* - Receive 8 products for $10/unit
- $10
- 8
- 8 * $10
- $80
* - Receive 4 products for $16/unit
- $12
- 12
- 4 * $16
- $144
* - Deliver 10 products
- $12
- 2
- -10 * $12
- $24
* - Receive 2 products for $6/unit
- $9
- 4
- 2 * $6
- $36
How are unit cost and inventory value calculated at each step?
- When receiving four products for $16 each:
- Inventory value is calculated by adding the previous inventory value with the incoming
value: :math:`$80 + (4 * $16) = $144`.
- Unit cost is calculated by dividing the inventory value by the quantity on-hand:
:math:`$144 / 12 = $12`.
- When delivering ten products, the average unit cost is used to calculate the inventory
value, regardless of the purchase price of the product. Therefore, inventory value is
:math:`$144 + (-10 * $12) = $24`.
- Receive two products for $6 each:
- Inventory value: :math:`$24 + (2 * $6) = $36`
- Unit cost: :math:`$36 / 4 = $9`
.. note::
When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing Method`, changing
the numerical value in the *Cost* field for products in the respective product category
creates a new record in the *Inventory Valuation* report to adjust the value of the
product. The *Cost* amount is then automatically updated, based on the average purchase
price of both the inventory on-hand and the costs accumulated from validated purchase
orders.
.. tab:: First In First Out (FIFO)
Tracks the costs of incoming and outgoing items in real-time, and uses the real price of the
products to change the valuation. The oldest purchase price is used as the cost for the next
good sold, until an entire lot of that product is sold. When the next inventory lot moves up
in the queue, an updated product cost is used based on the valuation of that specific lot.
This method is arguably the most accurate inventory valuation method for a variety of reasons,
but it is highly sensitive to input data and human error.
.. list-table::
:header-rows: 1
:stub-columns: 1
* - Operation
- Unit Cost
- Qty On Hand
- Incoming Value
- Inventory Value
* -
- $0
- 0
-
- $0
* - Receive 8 products for $10/unit
- $10
- 8
- 8 * $10
- $80
* - Receive 4 products for $16/unit
- $12
- 12
- 4 * $16
- $144
* - Deliver 10 products
- $16
- 2
- | -8 * $10
| -2 * $16
- $32
* - Receive 2 products for $6/unit
- $11
- 4
- 2 * $6
- $44
How are unit cost and inventory value calculated at each step?
- When receiving four products for $16 each:
- Inventory value is calculated by adding the previous inventory value to the incoming
value: :math:`$80 + (4 * $16) = $144`.
- Unit cost is calculated by dividing the inventory value by the quantity on-hand:
:math:`$144 / 12 = $12`.
- When delivering ten products, eight units were purchased for $10, and two units were
purchased for $16.
- First, the incoming value is calculated by multiplying the on-hand quantity by the
purchased price: :math:`(-8 * $10) + (-2 * $16) = -112`.
- The inventory value is calculated by subtracting the incoming value from the previous
inventory value: :math:`$144 - $112 = $32`.
- Unit cost is calculated by dividing the inventory value by the remaining quantity:
:math:`$32 / 2 = $16`.
- When receiving two products for $6, inventory value is :math:`$32 + $12 = $44`. Unit cost is
:math:`$44 / 4 = $11`.
.. warning::
Changing the costing method greatly impacts inventory valuation. It is highly recommended to
@@ -10,3 +10,4 @@ Putaway & Removal Strategies
strategies/putaway
strategies/removal
strategies/storage_category
@@ -93,83 +93,3 @@ match is found:
:align: center
:alt: Some examples of putaway rules.
Storage categories
==================
A *storage category* is an extra location attribute. Storage categories allow the user to define
the quantity of products that can be stored in the location, and how the location will be selected
with putaway rules.
Configuration
-------------
To enable storage categories, go to :menuselection:`Inventory app --> Configuration --> Settings`,
and activate the :guilabel:`Storage Categories` feature in the :guilabel:`Warehouse` section. Then,
click :guilabel:`Save`.
.. important::
The :guilabel:`Storage Locations` feature **must** be enabled to enable :guilabel:`Storage
Categories`.
Define storage category
-----------------------
To create a storage category, go to :menuselection:`Inventory app --> Configuration --> Storage
Categories` and click :guilabel:`Create`.
On the storage category form, type a name for the :guilabel:`Storage Category` field.
Options are available to limit the capacity by weight, by product, or by package type. The
:guilabel:`Allow New Product` field defines when the location is considered available to store a
product:
- :guilabel:`If location is empty`: a product can be added there only if the location is empty.
- :guilabel:`If products are the same`: a product can be added there only if the same product is
already there.
- :guilabel:`Allow mixed products`: several different products can be stored in this location at
the same time.
.. example::
Create putaway rules for pallet-stored items and ensure real-time storage capacity checks by
creating the `High Frequency pallets` storage category.
Name the :guilabel:`Storage Category`, and select :guilabel:`If all products are same` in the
:guilabel:`Allow New Product` field.
Then, define package capacity in the :guilabel:`Capacity by Package` tab, specifying the number
of packages for the designated :guilabel:`Package Type` and setting a maximum of `2.00` `Pallets`
for a specific location.
.. image:: putaway/storage-category.png
:align: center
:alt: Create a storage category on the page.
Once the storage category settings are saved, the storage category can be linked to a location.
To do that, navigate to the location by going to :menuselection:`Inventory app --> Configuration -->
Locations`, and select the location. Click :guilabel:`Edit` and select the created category in the
:guilabel:`Storage Category` field.
.. example::
Assign the `High Frequency pallets` storage category to the `WH/Stock/pallets/PAL 1`
sub-location.
.. image:: putaway/location-storage-category.png
:align: center
:alt: When a Storage Category is created, it can be linked to a warehouse location.
Storage categories in putaway rules
-----------------------------------
To continue the example from above, apply the `High Frequency Pallets` on the `PAL1` and `PAL2`
locations and :ref:`rework the putaway rules <inventory/routes/putaway-rule>` as follows:
Assume one pallet of lemonade cans is received:
- If PAL1 and PAL2 are empty, the pallet will be redirected to WH/Stock/Pallets/PAL1.
- If PAL1 is full, the pallet will be redirected to WH/Stock/Pallets/PAL2.
- If PAL1 and 2 are full, the pallet will be redirected to WH/Stock/Pallets.
.. image:: putaway/smart-putaways.png
:align: center
:alt: Storage Categories used in a variety of putaway rules.
@@ -0,0 +1,176 @@
==================
Storage categories
==================
A *storage category* is used with :doc:`putaway rules <putaway>`, as an extra location attribute to
automatically propose optimal storage locations for products.
Follow these steps to complete the setup:
#. :ref:`Enable the Storage Category feature <inventory/routes/enable-storage-categories>`
#. :ref:`Define a storage category <inventory/routes/define-storage>` with specific limitations
#. Assign a :ref:`category to storage locations <inventory/routes/assign-location>`
#. Add the storage category as an attribute to a :ref:`putaway rule
<inventory/routes/set-putaway-attribute>`
.. seealso::
:doc:`putaway`
.. note::
Assigning categories to storage locations tells Odoo these locations meet specific
requirements, such as temperature or accessibility. Odoo then evaluates these locations, based on
defined capacity, and recommends the best one on the warehouse transfer form.
.. _inventory/routes/enable-storage-categories:
Configuration
=============
To enable storage categories, go to :menuselection:`Inventory app --> Configuration --> Settings`.
Then, in the :guilabel:`Warehouse` section, ensure the :guilabel:`Storage Locations` and
:guilabel:`Multi-Step Routes` features are enabled.
Next, activate the :guilabel:`Storage Categories` feature. Finally, click :guilabel:`Save`.
.. image:: storage_category/enable-categories.png
:align: center
:alt: Show the Storage Categories feature.
.. _inventory/routes/define-storage:
Define storage category
=======================
A storage category with specific limitations **must** be created first, before it is applied to
locations, in order to decide the optimal storage location.
To create a storage category, go to :menuselection:`Inventory app --> Configuration --> Storage
Categories`, and click :guilabel:`Create`.
On the storage category form, type a name for the category in the :guilabel:`Storage Category`
field.
Options are available to limit capacity by weight, product, and package type.
.. note::
Weight limits can be combined with capacity by package or product (e.g. a maximum of one hundred
products with a total weight of two hundred kilograms).
While it is possible to limit capacity by product and package type at the same location, it may
be more practical to store items in different amounts across various locations, as shown in this
example of :ref:`capacity by package <inventory/routes/set-capacity-package>`.
The :guilabel:`Allow New Product` field defines when the location is considered available to store a
product:
- :guilabel:`If location is empty`: a product can be added there only if the location is empty.
- :guilabel:`If products are the same`: a product can be added there only if the same product is
already there.
- :guilabel:`Allow mixed products`: several different products can be stored in this location at
the same time.
.. tip::
When clicked, the :guilabel:`Location` smart button shows which storage locations the category
has been assigned to.
Capacity by weight
------------------
On a storage category form (:menuselection:`Inventory app --> Configuration --> Storage
Categories`), set a maximum product weight in the :guilabel:`Max Weight` field. This limit applies
to each location assigned this storage category.
Capacity by product
-------------------
In the :guilabel:`Capacity by Product` tab, click :guilabel:`Add a Line` to input items, and enter
their capacities in the :guilabel:`Quantity` field.
.. example::
Ensure only a maximum of five `Large Cabinets` and two `Corner Desk Right Sit` are stored at a
single storage location, by specifying those amounts in the :guilabel:`Capacity by Product` tab
of a storage category form.
.. image:: storage_category/capacity-by-product.png
:align: center
:alt: Show storage category limiting by product count.
.. _inventory/routes/set-capacity-package:
Capacity by package
-------------------
For companies using :doc:`packages <../../management/products/usage>`, it becomes possible to ensure
real-time storage capacity checks, based on package types (e.g., crates, bins, boxes, etc.).
.. important::
Enable the :guilabel:`Packages` feature in :menuselection:`Inventory app --> Configuration -->
Settings` to show the :guilabel:`Capacity by Package` tab.
.. example::
Create putaway rules for pallet-stored items, by creating the `High Frequency pallets` storage
category.
In the :guilabel:`Capacity by Package` tab, specify the number of packages for the designated
:guilabel:`Package Type`, and set a maximum of `2.00` `Pallets` for a specific location.
.. image:: storage_category/storage-category.png
:align: center
:alt: Create a storage category on the page.
.. _inventory/routes/assign-location:
Assign to location
==================
Once the storage category is created, assign it to a location. Navigate to the location by going to
:menuselection:`Inventory app --> Configuration --> Locations`, and select the desired location.
Then, select the created category in the :guilabel:`Storage Category` field.
.. example::
Assign the `High Frequency pallets` storage category (which limits pallets stored at any location
to two pallets) to the `WH/Stock/pallets/PAL 1` sub-location.
.. image:: storage_category/location-storage-category.png
:align: center
:alt: When a Storage Category is created, it can be linked to a warehouse location.
.. _inventory/routes/set-putaway-attribute:
Putaway rule
============
With the :ref:`storage category <inventory/routes/define-storage>` and :ref:`location
<inventory/routes/assign-location>` set up, create the :doc:`putaway rule <putaway>` by navigating
to :menuselection:`Inventory app --> Configuration --> Putaway Rules`.
Click the :guilabel:`Create` button to create the putaway rule. In the :guilabel:`Having Category`
field of the new putaway rule form, select the storage category.
.. example::
Continuing the example from above, the `High Frequency Pallets` storage category is assigned to
the putaway rule directing pallets of lemonade to locations with the `High Frequency Pallets`
storage category :ref:`assigned to them <inventory/routes/assign-location>`.
.. image:: storage_category/smart-putaways.png
:align: center
:alt: Storage Categories used in a variety of putaway rules.
Use case: limit capacity by package
===================================
To limit the capacity of a storage location by a specific number of packages, :ref:`create a storage
category with a Capacity By Package <inventory/routes/set-capacity-package>`.
Continuing the example from above, the `High Frequency Pallets` storage category is assigned to the
`PAL1` and `PAL2` locations.
Then, :ref:`putaway rules <inventory/routes/putaway-rule>` are set, so that any pallets received in
the warehouse are directed to be stored in `PAL1` and `PAL2` locations.
Depending on the number of pallets on-hand at each of the storage locations, when one pallet of
lemonade cans is received, the following scenarios happen:
- If `PAL1` and `PAL2` are empty, the pallet is redirected to `WH/Stock/Pallets/PAL1`.
- If `PAL1` is full, the pallet is redirected to `WH/Stock/Pallets/PAL2`.
- If `PAL1` and `PAL2` are full, the pallet is redirected to `WH/Stock/Pallets`.
Binary file not shown.

After

Width:  |  Height:  |  Size: 9.6 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

@@ -10,5 +10,6 @@ Shipping Setup
setup/delivery_method
setup/third_party_shipper
setup/bpost
setup/ups_credentials
setup/dhl_credentials
@@ -0,0 +1,110 @@
=================
Bpost integration
=================
Set up the *Bpost* shipping connector in Odoo to manage Bpost shipments to clients directly within
Odoo. To configure it, complete these steps:
#. Create a Bpost account.
#. Get the :ref:`Account ID and passphrase <inventory/shipping/Bpost-account>`.
#. Set up the shipping method in Odoo.
Upon completion, it is possible to calculate the cost of shipping, based on package size and weight,
have the charges applied directly to a Bpost business account, and automatically print Bpost
tracking labels through Odoo.
.. seealso::
- :doc:`third_party_shipper`
- :doc:`delivery_method`
- :doc:`dhl_credentials`
- :doc:`ups_credentials`
Bpost account setup
===================
To begin, go to the `Bpost website <https://parcel.bpost.be/en/home/business>`_ to create, or log
into, the company's Bpost business account. When creating the Bpost account, have the company's VAT
number and mobile phone number ready.
Follow the website's steps to complete registration, and sign up for shipping services. Doing so
submits a request to enter a contractual business relationship between the company and Bpost.
.. important::
Odoo **cannot** be integrated with `non-business Bpost
<https://bpost.freshdesk.com/support/solutions/articles/174847-account-id-and-passphrase>`_
accounts.
After completing the setup, get the Bpost account ID and passphrase, by navigating to the
:guilabel:`Shipping Manager` menu item.
.. _inventory/shipping/bpost-account:
On the :guilabel:`Shipping Manager` page, go to the :guilabel:`Admin` tab, then the
:guilabel:`General Settings` tab, to find the :guilabel:`Account ID` and :guilabel:`Passphrase`
needed to configure Odoo's shipping method.
.. image:: bpost/credentials.png
:align: center
:alt: In the *Admin* tab, show the Account ID and Passphrase.
Configure Bpost shipping method
===============================
With those necessary credentials, configure the Bpost shipping method in Odoo by going to
:menuselection:`Inventory app --> Configuration --> Shipping Methods`.
On the :guilabel:`Shipping Methods` page, click :guilabel:`Create`.
In the :guilabel:`Provider` field, select :guilabel:`Bpost` from the drop-down menu. Doing so
reveals the :guilabel:`Bpost Configuration` tab at the bottom of the form, where the Bpost
credentials can be entered.
For details on configuring the other fields on the shipping method, such as :guilabel:`Delivery
Product`, refer to the :doc:`Configure third-party carrier <third_party_shipper>` documentation.
.. note::
To generate Bpost :doc:`shipping labels <../operation/labels>` through Odoo, ensure the
:guilabel:`Integration Level` option is set to :guilabel:`Get Rate and Create Shipment`.
In the :guilabel:`Bpost Configuration` tab, complete the following fields:
- :guilabel:`Bpost Account Number` (required field): enter the company's unique :ref:`account ID
<inventory/shipping/bpost-account>` from the Bpost website.
- :guilabel:`Passphrase` (required field): enter the :ref:`passphrase
<inventory/shipping/bpost-account>` from the Bpost website.
- :guilabel:`Bpost Delivery Nature`: select either :guilabel:`Domestic` or :guilabel:`International`
shipping services. Choosing :guilabel:`Domestic` shows the :guilabel:`Options` section, while
:guilabel:`International` enables the :guilabel:`Bpost Shipment Type` and :guilabel:`Bpost Parcel
Return Instructions` fields.
- :guilabel:`Bpost Package Type`: select the type of shipping service from the drop-down menu.
For `domestic delivery
<https://help.shipmondo.com/en/articles/6092265-bpost-belgium-parcel-types-and-requirements>`_,
the options are: :guilabel:`bpack 24h Pro`, :guilabel:`bpack 24h business`, or :guilabel:`bpack
Bus`.
For `international delivery <https://www.bpost.be/en/business-parcels-send/international>`_, the
options are: :guilabel:`bpack World Express Pro`, :guilabel:`bpack World Business`, or
:guilabel:`bpack Europe Business`.
- :guilabel:`Bpost Shipment Type` (required field): for international deliveries, declare the type
of goods in the package as :guilabel:`SAMPLE`, :guilabel:`GIFT`, :guilabel:`GOODS`,
:guilabel:`DOCUMENTS`, or :guilabel:`OTHER`.
- :guilabel:`Bpost Parcel Return Address`: return address when an international shipment fails to
deliver. Select from the drop-down menu: :guilabel:`Destroy`, :guilabel:`Return to sender by air`,
or :guilabel:`Return to sender by road`.
- :guilabel:`Label Type`: choose :guilabel:`A6` or :guilabel:`A4` label sizes from the drop-down
menu.
- :guilabel:`Label Format`: choose :guilabel:`PDF` or :guilabel:`PNG` from the drop-down menu.
For domestic deliveries, these features are available in the :guilabel:`Options` section:
- Enable the :guilabel:`Delivery on Saturday` feature to include Saturdays as possible delivery
dates. Depending on the :guilabel:`Bpost Package Type` selected, this option might incur
additional costs to the company.
- Enable the :guilabel:`Generate Return Label` feature to automatically print a return label upon
validating the delivery order.
.. image:: bpost/bpost.png
:align: center
:alt: Show Bpost shipping method.
Binary file not shown.

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

@@ -9,9 +9,9 @@ Odoo VoIP (Voice over Internet Protocol) can be set up to work together with `Ax
<https://www.axivox.com/>`_. In that case, an Asterisk server is **not** necessary, as the
infrastructure is hosted and managed by Axivox.
To use this service, `contact Axivox <https://www.axivox.com/contact/>`_ to open an account. Before
doing so, verify that Axivox covers the company's area, along with the areas the company's users
wish to call.
To use this service, `contact Axivox <https://www.axivox.com/en/contact/>`_ to open an account.
Before doing so, verify that Axivox covers the company's area, along with the areas the company's
users wish to call.
Configuration
=============
@@ -7,8 +7,8 @@ Configuration
.. _configuration/settings:
Access POS settings
===================
Access the POS settings
=======================
To access the general POS settings, go to :menuselection:`Point of Sale --> Configuration -->
Settings`.
@@ -27,6 +27,36 @@ and select a product to open the product form. In the :guilabel:`Sales` tab, ena
.. image:: configuration/pos-available.png
:alt: Making a product available in your POS.
PoS product categories
======================
Configuration
-------------
POS product categories allow users to categorize products and get a more structured and clean
POS interface.
To manage PoS categories, go to :menuselection:`Point of Sale --> Configuration --> PoS Product
Categories`. To add a new category, click :guilabel:`Create`. Then, name it in the
:guilabel:`Category Name` field.
To associate a category with a parent category, fill in the :guilabel:`Parent Category` field. A
parent category groups one or more child categories.
.. example::
.. image:: configuration/parent-categories.png
:alt: The PoS product categories grouped by parent categories
Assign PoS product categories
-----------------------------
Go to :menuselection:`Point of Sale --> Products --> Products` and open a product form. Then, go to
the :guilabel:`Sales` tab and fill in the :guilabel:`Category` field under the :guilabel:`Point of
Sale` section.
.. image:: configuration/form-pos-category.png
:alt: Sales tab of a product form to add a PoS product category
.. toctree::
:titlesonly:
Binary file not shown.

After

Width:  |  Height:  |  Size: 6.8 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 20 KiB

@@ -29,6 +29,20 @@ Then, follow the corresponding documentation to configure your device:
Once the terminal is configured, you can :doc:`create the corresponding payment method and add it to
the POS <../payment_methods>`.
Pay with a payment terminal
===========================
When processing a payment, select the terminal's payment method. Check the amount and
click on :guilabel:`Send`. Once the payment is successful, the status changes to :guilabel:`Payment
Successful`.
.. note::
- | In case of connection issues between Odoo and the payment terminal, force the payment by
clicking on :guilabel:`Force Done`, which allows you to validate the order.
| This option is only available after receiving an error message informing you that the
connection failed.
- To cancel the payment request, click on :guilabel:`Cancel`.
.. toctree::
:titlesonly:
@@ -84,17 +84,3 @@ Terminal Identifier <adyen/identifier>`, and :guilabel:`Adyen Merchant Account`.
Once the payment method is created, you can select it in your POS settings. To do so, go to the
:ref:`POS' settings <configuration/settings>`, click :guilabel:`Edit`, and add the payment method
under the :guilabel:`Payments` section.
Pay with a payment terminal
===========================
When processing a payment, select :guilabel:`Adyen` as the payment method. Check the amount and
click on :guilabel:`Send`. Once the payment is successful, the status changes to :guilabel:`Payment
Successful`.
.. note::
- | In case of connection issues between Odoo and the payment terminal, force the payment by
clicking on :guilabel:`Force Done`, which allows you to validate the order.
| This option is only available after receiving an error message informing you that the
connection failed.
- To cancel the payment request, click on :guilabel:`cancel`.
@@ -50,33 +50,3 @@ Then, select your terminal device in the :guilabel:`Payment Terminal Device` fie
Once the payment method is created, you can select it in your POS settings. To do so, go to the
:ref:`POS' settings <configuration/settings>`, click :guilabel:`Edit`, and add the payment method
under the :guilabel:`Payments` section.
Pay with a payment terminal
===========================
In your *PoS interface*, when processing a payment, select a *Payment
Method* using a payment terminal. Check that the amount in the tendered
column is the one that has to be sent to the payment terminal and click
on *Send*. When the payment is successful, the status will change to
*Payment Successful*.
.. image:: ingenico/payment_terminal_05.png
:align: center
If you want to cancel the payment request, click on cancel. You can
still retry to send the payment request.
If there is any issue with the payment terminal, you can still force the
payment using the *Force Done*. This will allow you to validate the
order in Odoo even if the connection between the terminal and Odoo has
issues.
.. note::
This option will only be available if you received an error message
telling you the connection failed.
Once your payment is processed, on the payment record, youll find the
type of card that has been used and the transaction ID.
.. image:: ingenico/payment_terminal_06.png
:align: center
Binary file not shown.

Before

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 7.8 KiB

@@ -32,26 +32,3 @@ Back in :menuselection:`Point of Sale --> Configuration --> Payment Methods`, cl
.. image:: six/new-payment-method.png
:align: center
:alt: Create a new payment method for the SIX payment terminal.
Pay with a Payment Terminal
===========================
In the :abbr:`PoS (Point of Sale)` interface, at the moment of the payment, select a payment method
using a payment terminal. Verify that the amount in the tendered column is the one that has to be
sent to the payment terminal and click on :guilabel:`Send`. To cancel the payment request, click on
:guilabel:`Cancel`.
.. image:: six/pos-send-payment.png
:align: center
:alt: The PoS interface.
When the payment is done, the status will change to :guilabel:`Payment Successful`. If needed,
reverse the last transaction by clicking on :guilabel:`Reverse`.
.. image:: six/pos-reverse-payment.png
:align: center
:alt: The Reverse button on the PoS interface.
If there is any issue with the payment terminal, you can still force the payment using the
:guilabel:`Force Done` button. This will allow you to validate the order in Odoo even if there are
connection issues between the payment terminal and Odoo.
Binary file not shown.

Before

Width:  |  Height:  |  Size: 10 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 11 KiB

@@ -6,8 +6,8 @@ Connecting a Vantiv payment terminal allows you to offer a fluid payment flow to
ease the work of your cashiers.
.. note::
Please note MercuryPay only operates with US and Canadian banks, making
this procedure only suitable for North American businesses.
Please note MercuryPay only operates with US and Canadian banks, making this procedure only
suitable for North American businesses.
.. warning::
Vantiv card readers should be purchased exclusively from Vantiv, as certain Vantiv terminals
@@ -16,35 +16,23 @@ ease the work of your cashiers.
Configuration
=============
Configure the Payment Method
Configure the payment method
----------------------------
First, go in the general settings of the POS app, and activate the
Vantiv setting.
Enable the payment terminal in the :guilabel:`Payment Terminals` section :ref:`of the application
settings <configuration/settings>`.
.. image:: vantiv/vantiv_01.png
:align: center
Then, go to :menuselection:`Point of Sale --> Configuration --> Payment Methods`, and :doc:`create
the related payment method <../../payment_methods>`. Set the journal type as :guilabel:`Bank` and
select :guilabel:`Vantiv` in the :guilabel:`Use a Payment Terminal` field.
Back in :menuselection:`Point of Sale --> Configuration --> Point of Sale`, go in the
payments section and access your payment methods. Create a new payment
method for Vantiv, select the payment terminal option Vantiv, and create
new Vantiv credentials.
Type the name you want to give to your :guilabel:`Vantiv Credentials` and click :guilabel:`Create
and edit`. Enter your :guilabel:`Merchant ID` and :guilabel:`Merchant Password`, then click
:guilabel:`Save & Close`.
.. image:: vantiv/vantiv_02.png
:align: center
.. image:: vantiv/vantiv-method.png
:alt: Vantiv payment method
To create new Vantiv credentials, fill in your merchant ID and password,
then save. Make sure the credentials you just created are selected, then
save the payment method.
.. image:: vantiv/vantiv_03.png
:align: center
Pay with a Payment Terminal
===========================
In your PoS interface, at the moment of the payment, select your Vantiv
payment method and… thats all.
.. image:: vantiv/vantiv_04.png
:align: center
Once the payment method is created, you can select it in your POS settings. To do so, go to the
:ref:`POS' settings <configuration/settings>`, click :guilabel:`Edit`, and add the payment method
under the :guilabel:`Payments` section.
Binary file not shown.

After

Width:  |  Height:  |  Size: 10 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 9.0 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 82 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 15 KiB

@@ -86,21 +86,3 @@ under the :guilabel:`Payments` section.
- Configure the cashier terminal if you have both a customer and a cashier terminal.
- To avoid blocking the terminal, check the initial configuration beforehand.
- Set a fixed IP to your IoT Boxs router to prevent losing the connexion.
Pay with a payment terminal
===========================
When processing a payment, select *Worldline* as payment method. Check the amount and click on
*Send*. Once the payment is successful, the status changes to *Payment Successful*.
Once your payment is processed, the type of card used and the transaction ID appear on the payment
record.
.. image:: worldline/worldline-payment.png
:align: center
.. note::
* In case of connexion issues between Odoo and the payment terminal, force the payment by
clicking on *Force Done*, which allows you to validate the order. This option is only available
after receiving an error message informing you that the connection failed.
* To cancel the payment request, click on **cancel**.
Binary file not shown.

Before

Width:  |  Height:  |  Size: 63 KiB

@@ -1 +0,0 @@
At the bottom of the page, check the mergeability status and address any issues.
@@ -1,7 +0,0 @@
Configure Git to identify yourself as the author of your future contributions. Enter the same email
address you used to register on GitHub.
.. code-block:: console
$ git config --global user.name “Your Name”
$ git config --global user.email “youremail@example.com”
@@ -1,2 +0,0 @@
`Generate a new SSH key and register it on your GitHub account
<https://docs.github.com/en/authentication/connecting-to-github-with-ssh>`_.
@@ -1,3 +0,0 @@
First, you need to `create a GitHub account <https://github.com/join>`_. Odoo uses GitHub to manage
the source code of its products, and this is where you will make your changes and submit them for
review.
+19 -6
View File
@@ -28,15 +28,25 @@ The instructions below help you prepare your environment for making local change
and then push them to GitHub. Skip this section and go to
:ref:`contributing/development/first-contribution` if you have already completed this step.
#. .. include:: create_github_account.rst
#. .. include:: configure_github_account.rst
#. First, you need to `create a GitHub account <https://github.com/join>`_. Odoo uses GitHub to
manage the source code of its products, and this is where you will make your changes and submit
them for review.
#. `Generate a new SSH key and register it on your GitHub account
<https://docs.github.com/en/authentication/connecting-to-github-with-ssh>`_.
#. Go to `github.com/odoo/odoo <https://github.com/odoo/odoo>`_ and click on the :guilabel:`Fork`
button in the top right corner to create a fork (:dfn:`your own copy`) of the repository on your
account. Do the same with `github.com/odoo/enterprise <https://github.com/odoo/enterprise>`_ if
you have access to it. This creates a copy of the codebase to which you can make changes without
affecting the main codebase. Skip this step if you work at Odoo.
#. .. include:: install_git.rst
#. .. include:: configure_git_authorship.rst
#. Configure Git to identify yourself as the author of your future contributions. Enter the same
email address you used to register on GitHub.
.. code-block:: console
$ git config --global user.name "Your Name"
$ git config --global user.email "youremail@example.com"
#. :doc:`Install Odoo from the sources <../administration/on_premise/source>`. Make sure to fetch
the sources through Git with SSH.
#. Configure Git to push changes to your fork(s) rather than to the main codebase. If you work at
@@ -84,7 +94,7 @@ Make your first contribution
.. important::
- Odoo development can be challenging for beginners. We recommend you to be knowledgeable enough
to code a small module before contributing. If that is not the case, take some time to go
through the :doc:`developer tutorials </developer/howtos>` to fill in the gaps.
through the :doc:`developer tutorials </developer/tutorials>` to fill in the gaps.
- Some steps of this guide require to be comfortable with Git. Here are some `tutorials
<https://www.atlassian.com/git/tutorials>`_ and an `interactive training
<https://learngitbranching.js.org/>`_ if you are stuck at some point.
@@ -155,7 +165,10 @@ navigate to the directory where you installed Odoo from sources and follow the g
#. Tick the :guilabel:`Allow edits from maintainer` checkbox. Skip this step if you work at Odoo.
#. Complete the description and click on the :guilabel:`Create pull request` button again.
#. .. include:: check_mergeability_status.rst
#. .. include:: handle_reviews.rst
#. At the bottom of the page, check the mergeability status and address any issues.
#. As soon as your :abbr:`PR (Pull Request)` is ready for merging, a member of the Odoo team
is automatically assigned for review. If the reviewer has questions or remarks, they will
post them as comments and you will be notified by email. Those comments must be resolved
for the contribution to go forward.
#. Once your changes are approved, the review merges them and they become available for all Odoo
users after the next code update!
+57 -51
View File
@@ -8,29 +8,26 @@ Documentation
:titlesonly:
documentation/content_guidelines
documentation/rst_cheat_sheet
documentation/rst_guidelines
This introductory guide will help you acquire the tools and knowledge you need to write
documentation, whether you plan to make a minor content change or document an application from
scratch.
This introductory guide will help you acquire the tools and knowledge needed to contribute to the
documentation.
Read the :ref:`introduction to the reStructuredText language <contributing/documentation/rst-intro>`
if you are not familiar with it. Then, there are two courses of action to start contributing to the
documentation:
- **For minor changes**, such as adding a paragraph or fixing a typo, we recommend **using the
GitHub interface**. This is the easiest and fastest way to submit changes, and it is suitable for
non-technical people. Jump directly to the :ref:`contributing/documentation/first-contribution`
section to get started.
- **For more complex changes**, such as adding a new page, it is necessary to **use Git** and work
from a local copy of the documentation. Follow the instructions in the
:ref:`contributing/documentation/setup` section first to prepare your environment.
.. seealso::
:doc:`Discover other ways to contribute to Odoo <../contributing>`
Read the :ref:`introduction to the reStructuredText language <contributing/documentation/rst-intro>`
if you are not familiar with it. Then, you have two courses of action to start contributing to the
documentation, depending on whether you want to propose minor changes to existing content or you
instead want to work on significant changes to new and existing content.
- **For minor changes**, for example, adding a paragraph or fixing a typo, we recommend **using the
GitHub interface**. This is the easiest and fastest way to submit your changes, and it is suitable
for non-technical people. Jump directly to the
:ref:`contributing/documentation/first-contribution` section to get started.
- **For more complex changes**, it is necessary to **use Git** and work from a local copy of the
documentation. Follow the instructions in the :ref:`contributing/documentation/setup` section to
first prepare your environment.
.. _contributing/documentation/rst-intro:
reStructuredText (RST)
@@ -38,24 +35,13 @@ reStructuredText (RST)
The documentation is written in **reStructuredText** (RST), a `lightweight markup language
<https://en.wikipedia.org/wiki/Lightweight_markup_language>`_ consisting of regular text augmented
with markup, which allows including headings, images, notes, and so on. This might seem a bit
abstract, but there is no need to worry; :abbr:`RST (reStructuredText)` is not hard to learn,
especially if you intend to make minor changes to the content.
If you need to learn about a specific markup, head over to our :doc:`cheat sheet for RST
<documentation/rst_cheat_sheet>`; it contains all the information you should ever need for the
documentation of Odoo.
with markup, which allows including headings, images, notes, and so on. :abbr:`RST
(reStructuredText)` is easy to use, even if you are not familiar with it.
.. important::
We kindly ask you to observe a set of :doc:`content <documentation/content_guidelines>` and
Be mindful of our :doc:`content <documentation/content_guidelines>` and
:doc:`RST <documentation/rst_guidelines>` guidelines as you write documentation. This ensures
that you stay consistent with the rest of the documentation and facilitates the approval of your
content changes as the Odoo team reviews them.
.. seealso::
- :doc:`documentation/content_guidelines`
- :doc:`documentation/rst_cheat_sheet`
- :doc:`documentation/rst_guidelines`
that the documentation stays consistent and facilitates the approval of changes by the Odoo team.
.. _contributing/documentation/setup:
@@ -67,14 +53,23 @@ documentation and then push them to GitHub. Skip this section and go to
:ref:`contributing/documentation/first-contribution` if you have already completed this step or want
to make changes from the GitHub interface.
#. .. include:: create_github_account.rst
#. .. include:: configure_github_account.rst
#. First, `create a GitHub account <https://github.com/join>`_. Odoo uses GitHub to manage the
source code of its products, and this is where you will submit your changes.
#. `Generate a new SSH key and register it on your GitHub account
<https://docs.github.com/en/authentication/connecting-to-github-with-ssh>`_.
#. Go to `github.com/odoo/documentation <https://github.com/odoo/documentation>`_ and click on the
:guilabel:`Fork` button in the top right corner to create a fork (:dfn:`your own copy`) of the
repository on your account. This creates a copy of the codebase to which you can make changes
without affecting the main codebase. Skip this step if you work at Odoo.
#. .. include:: install_git.rst
#. .. include:: configure_git_authorship.rst
#. Configure Git to identify yourself as the author of your future contributions. Enter the same
email address you used to register on GitHub.
.. code-block:: console
$ git config --global user.name "Your Name"
$ git config --global user.email "youremail@example.com"
#. Clone the sources with Git and navigate into the local repository.
.. code-block:: console
@@ -109,7 +104,7 @@ to make changes from the GitHub interface.
$ git config commit.template %CD%\commit_template.txt
#. Install the latest release of `Python <https://wiki.python.org/moin/BeginnersGuide/Download>`_
and `pip <https://pip.pypa.io/en/stable/installation/>`_ on your machine.
and `pip <https://pip.pypa.io/en/stable/installation/>`_.
#. Install the Python dependencies of the documentation with pip.
.. code-block:: console
@@ -149,18 +144,20 @@ to make changes from the GitHub interface.
<https://www.technewstoday.com/install-and-use-make-in-windows>`_.
#. `Install pngquant <https://pngquant.org/>`_.
#. That's it! You are ready to :ref:`make your first contribution
#. You are now ready to :ref:`make your first contribution
<contributing/documentation/first-contribution>` with Git.
.. _contributing/documentation/first-contribution:
Make your first contribution
============================
Contributing to the documentation
=================================
.. tabs::
.. tab:: Contribute from the GitHub interface
#. .. include:: create_github_account.rst
#. First, `create a GitHub account <https://github.com/join>`_. Odoo uses GitHub to manage the
source code of its products, and this is where you will submit your changes.
#. Verify that you are browsing the documentation in the version that you intend to change.
The version can be selected from the dropdown in the top menu.
#. Head to the page that you want to change and click on the :guilabel:`Edit on GitHub` button
@@ -194,9 +191,14 @@ Make your first contribution
Odoo.
#. Review the summary that you wrote about your changes and click on the :guilabel:`Create
pull request` button again.
#. .. include:: check_mergeability_status.rst
#. .. include:: handle_reviews.rst
#. .. include:: documentation/changes_approved.rst
#. At the bottom of the page, check the mergeability status and address any issues.
#. As soon as your :abbr:`PR (Pull Request)` is ready for merging, a member of the Odoo team
is automatically assigned for review. If the reviewer has questions or remarks, they will
post them as comments and you will be notified by email. Those comments must be resolved
for the contribution to go forward.
#. Once your changes are approved, the reviewer merges them and they appear online the next
day.
.. tab:: Contribute with Git
@@ -230,7 +232,7 @@ Make your first contribution
#. Make the desired changes while taking care of following the :doc:`content
<documentation/content_guidelines>` and :doc:`RST <documentation/rst_guidelines>`
guidelines.
#. Compress all PNG images that you added or modified.
#. Compress all PNG images that were added or modified.
.. code-block:: console
@@ -239,9 +241,9 @@ Make your first contribution
#. Write a `redirect rule
<https://github.com/odoo/documentation/tree/{BRANCH}/redirects/MANUAL.md>`_ for every RST
file that your renamed.
#. Build the documentation with :command:`make`. Then, open :file:`_build/index.html` in your
web browser to browse the documentation with your changes.
file that were renamed.
#. Build the documentation with :command:`make`. Then, open :file:`_build/index.html` in a web
browser to browse the documentation with your changes.
.. tip::
Use :command:`make help` to learn about other useful commands.
@@ -254,7 +256,7 @@ Make your first contribution
$ git add .
$ git commit
#. Push your change to your fork, for which we added the remote alias `dev`.
#. Push your changes to your fork, for which we added the remote alias `dev`.
.. example::
@@ -285,6 +287,10 @@ Make your first contribution
Odoo.
#. Complete the description and click on the :guilabel:`Create pull request` button again.
#. .. include:: check_mergeability_status.rst
#. .. include:: handle_reviews.rst
#. .. include:: documentation/changes_approved.rst
#. At the bottom of the page, check the mergeability status and address any issues.
#. As soon as your :abbr:`PR (Pull Request)` is ready for merging, a member of the Odoo team
is automatically assigned for review. If the reviewer has questions or remarks, they will
post them as comments and you will be notified by email. Those comments must be resolved
for the contribution to go forward.
#. Once your changes are approved, the reviewer merges them and they appear online the next
day.
@@ -1 +0,0 @@
Once your changes are approved, the reviewer merges them and they appear online the next day!
@@ -2,228 +2,294 @@
Content guidelines
==================
To give the community the best documentation possible, we listed here a few guidelines, tips and
tricks that will make your content shine at its brightest! While we encourage you to adopt your own
writing style, some rules still apply to give the reader more clarity and comprehension.
While we encourage you to adopt your own writing style, some rules still apply to maintain clarity
and ensure readers can easily understand the content.
.. important::
We strongly recommend to read the :doc:`rst_guidelines` and the main :doc:`../documentation`
pages before contributing.
.. _contributing/content/organization:
Documentation organization
==========================
When writing documentation about a given topic, keep pages within the same folder organized.
For most topics, a single page should do the job. Place it in the appropriate section of the
documentation (e.g., content related to the CRM app goes under :menuselection:`User Docs --> Sales
--> CRM`) and follow the :ref:`document structure <contributing/content/structure>` guidelines.
For more complex topics, several pages may be needed to cover all their aspects. Usually, you will
find yourself adding documentation to a topic that is already partially covered. In that case,
either create a new page and place it at the same level as other related pages or add new sections
to an existing page. When documenting a complex topic from scratch, organize the content across
several child pages that are referenced on that directory's parent page (the :abbr:`TOC (Table Of
Contents)` page); whenever possible, write content on the parent page and not only on the child
pages. Make the parent page accessible from the navigation menu by using the
:ref:`show-content <contributing/rst/document-metadata>` metadata directive.
.. note::
We strongly recommend contributors to carefully read the other documents related to this section
of the documentation. Good knowledge of the ins and outs of **RST writing** is required to write
and submit your contribution. Note that it also affects your writing style itself.
Avoid duplicating content whenever possible; if a topic is already documented on another page,
:ref:`reference <contributing/rst/hyperlinks>` that existing information instead of repeating it.
- :doc:`../documentation`
- :doc:`rst_cheat_sheet`
- :doc:`rst_guidelines`
.. important::
When deleting or moving a `.rst` file, update the corresponding text file in the
:file:`redirects` folder based on your branch's version (e.g., :file:`17.0.txt`). To do so, add a
new line at the bottom of the relevant section (e.g., `# applications/sales`). On this line,
first, add the redirection entry point with the old file location, followed by a space, and then
add the exit point with the new or relevant file location. For example, if moving the file
:file:`unsplash.rst` from :file:`applications/websites/website/configuration` to
:file:`applications/general/integrations`, add the following entry under the section
`# applications/websites`:
.. _contributing/writing-style:
.. code-block:: text
applications/websites/website/configuration/unsplash.rst applications/general/integrations/unsplash.rst
.. _contributing/content/structure:
Document structure
==================
Use different **heading levels** to organize text by sections and sub-sections. Headings are not
only displayed in the document but also on the navigation menu (only the H1) and on the "On this
page" sidebar (all H2 to H6).
+---------------------------------------------------------------------------------------+
| | **H1: Page title** |
| | The *page title* gives readers a quick and clear understanding of what the content |
| is about. |
| |
| The *content* in this section describes the upcoming content from a **business point |
| of view**, and should not put the emphasis on Odoo, as this is documentation and not |
| marketing. |
| |
| Under the page title (H1), start with a **lead paragraph**, which helps the reader |
| make sure that they've found the right page, then explain the **business aspects of |
| this topic** in the following paragraphs. |
+-----+---------------------------------------------------------------------------------+
| | | **H2: Section title (configuration)** |
| | | This first H2 section is about the configuration of the feature, or the |
| | prerequisites to achieve a specific goal. |
+-----+---------------------------------------------------------------------------------+
| | | **H2: Section title (main sections)** |
| | | Create as many main sections as you have actions or features to distinguish. |
+-----+-----+---------------------------------------------------------------------------+
| | | | **H3: Subsection** |
| | | | Subsections are perfect for assessing very specific points. |
+-----+-----+---------------------------------------------------------------------------+
| | **H2: Next Section** |
+-----+---------------------------------------------------------------------------------+
To write good titles and headings:
- **Be concise**: **avoid sentences**, questions, and titles starting with "how to".
- **Do not use pronouns** in your titles, especially 2nd person (*you/your*).
- Use **sentence case**. This means you capitalize only:
- the first word of the title or heading;
- the first word after a colon;
- proper nouns (brands, product and service names, etc.).
.. note::
- Most titles and headings generally refer to a concept and do *not* represent the name of a
feature or a model.
- Do not capitalize the words of an acronym if they do not entail a proper noun.
- Verbs in headings are fine since they often describe an action.
.. seealso::
- :ref:`RST cheat sheet: headings <contributing/rst/headings>`
- :ref:`RST cheat sheet: markups <contributing/rst/markups>`
.. _contributing/content/writing-style:
Writing style
=============
**Writing for documentation** isn't the same as writing for a blog or another medium. Readers are
more likely to skim read until they've found the information they are looking for. Keep in mind that
the user documentation is a place to inform and describe, not to convince and promote.
Writing for documentation is not the same as writing for a blog or another medium. Readers are
more likely to skim through content to find the information they need. Keep in mind that the
documentation is a place to **inform and describe**, not to convince and promote.
.. _contributing/consistency:
.. tip::
Avoid using *you* as much as possible by opting for the imperative mood where appropriate.
However, do not complicate sentences just to avoid addressing the reader directly.
.. example::
| **Good example:**
| Select the appropriate option from the dropdown menu.
| **Bad example:**
| You can select the appropriate option from the dropdown menu.
.. _contributing/content/spelling:
Spelling
--------
Use American English spelling and grammar throughout the documentation.
.. _contributing/content/consistency:
Consistency
-----------
*Consistency is key to everything.*
Make sure that your writing style remains **consistent**. If you modify an existing text, try to
match the existing tone and presentation, or rewrite it to match your own style.
Make sure that the writing style remains **consistent**. When modifying existing content, try to
match the existing tone and presentation or rewrite it to match your own style.
.. _contributing/grammatical-tenses:
.. _contributing/content/capitalization:
Capitalization
--------------
- Use sentence case in :ref:`titles <contributing/content/structure>`.
- Capitalize app names, e.g., **Odoo Sales**, the **Sales** app, etc.
- Capitalize labels (such as fields and buttons) as they appear in Odoo. If a label is in all caps,
convert it to sentence case.
- Capitalize the first letter after a colon if it is a complete sentence.
- Avoid capitalizing common nouns, such as "sales order" and "bill of materials", unless you
reference a label or a model.
.. _contributing/content/grammatical-tenses:
Grammatical tenses
------------------
In English, descriptions and instructions require the use of a **Present Tense**, while a *future
tense* is appropriate only when a specific event is to happen ulteriorly. This logic might be
different in other languages.
- | Good example (present):
| *Screenshots are automatically resized to fit the content block's width.*
- | Bad example (future):
| *When you take a screenshot, remember that it will be automatically resized to fit the content
block's width.*
.. _contributing/paragraphing:
Paragraphing
------------
A paragraph comprises several sentences that are linked by a shared idea. They usually are two to
six lines long.
In English, a new idea implies a new paragraph, rather than having a *line break* as it is common to
do in some other languages. *Line breaks* are useful for layout purposes but shouldn't be used as a
grammatical way of separating ideas.
.. seealso::
- :ref:`RST cheat sheet: Break the line but not the paragraph <contributing/line-break>`
.. _contributing/titles:
Titles and headings
-------------------
To write good titles and headings:
- **Be concise.**
- **Avoid sentences**, unnecessary verbs, questions, and titles starting with "how to."
- **Don't use pronouns** in your titles, especially 2nd person (*your*).
- Use **sentence case**. This means you capitalize only:
- the first word of the title or heading
- the first word after a colon
- proper nouns (brands, product and service names, etc.)
.. note::
- Most titles and headings generally refer to a concept and do *not* represent the name of a
feature or a model.
- Do not capitalize the words of an acronym if they don't entail a proper noun.
- Verbs in headings are fine since they often describe an action.
In English, descriptions and instructions usually require the use of the **present tense**, while
the *future tense* is appropriate only when a specific event is to happen ulteriorly.
.. example::
- **Titles** (H1)
- Quotation templates
- Lead mining
- Resupply from another warehouse
- Synchronize Google Calendar with Odoo
- Batch payments: SEPA Direct Debit (SDD)
- Digitize vendor bills with optical character recognition (OCR)
| **Good example (present):**
| Screenshots are automatically resized to fit the content block's width.
- **Headings** (H2, H3)
| **Bad example (future):**
| When you take a screenshot, remember that it will be automatically resized to fit the content
block's width.
- Project stages
- Email alias
- Confirm the quotation
- Generate SEPA Direct Debit XML files to submit payments
.. _contributing/content/lists:
.. _contributing/document-structure:
Lists
=====
Document structure
==================
Lists help organize information in a clear and concise manner and improve readability. They are
used to highlight important details, guide the reader through steps in a systematic way, etc.
Use different **heading levels** to organize your text by sections and sub-sections. Your headings
are not only displayed in the document but also on the navigation menu (only the H1) and on the
"On this page" sidebar (all H2 to H6).
Use numbered lists when the sequence matters, e.g., instructions, procedures, or steps that must be
performed in a particular order.
+---------------------------------------------------------------------------------------+
| | **H1: Page title** |
| | Your *page title* gives your reader a quick and clear understanding of what your |
| content is about. |
| |
| The *content* in this section describes the upcoming content from a **business point |
| of view**, and shouldn't put the emphasis on Odoo, as this is documentation and not |
| marketing. |
| |
| Start first with a **lead paragraph**, which helps the reader make sure that they've |
| found the right page, then explain the **business aspects of this topic** in the |
| following paragraphs. |
+-----+---------------------------------------------------------------------------------+
| | | **H2: Section title (configuration)** |
| | | This first H2 section is about the configuration of the feature, or the |
| | prerequisites to achieve a specific goal. To add a path, make sure you |
| | use the ``:menuselection:`` specialized directive (see link below). |
| | |
| | | Example: |
| | | To do so, go to ``:menuselection:`App name --> Menu --> Sub-menu```, and |
| | enable the XYZ feature. |
+-----+---------------------------------------------------------------------------------+
| | | **H2: Section title (main sections)** |
| | | Create as many main sections as you have actions or features to distinguish. |
| | The title can start with a verb, but try to avoid using "Create ...". |
+-----+-----+---------------------------------------------------------------------------+
| | | | **H3: Subsection** |
| | | | Subsections are perfect for assessing very specific points. The title |
| | | can be in the form of a question, if appropriate. |
+-----+-----+---------------------------------------------------------------------------+
| | **H2: Next Section** |
+-----+---------------------------------------------------------------------------------+
Use bulleted lists when the sequence of items does not matter, e.g., lists of features, fields,
options, etc.
.. tip::
- Use inline text for explanations or when there are three or fewer list items.
- Combine bulleted and numbered lists using :ref:`nested lists <contributing/rst/nested-list>`
where appropriate.
- Consider grouping simple steps within the same list item, e.g.: Go to :menuselection:`Website
--> Site --> Pages` and click :guilabel:`New`.
- Only use a period at the end of the list item if it forms a complete sentence.
.. example::
**Bulleted list**
The following fields are available on the :guilabel:`Replenishment` report:
- :guilabel:`Product`: the product that requires a replenishment
- :guilabel:`Location`: the specific location where the product is stored
- :guilabel:`Warehouse`: the warehouse where the product is stored
- :guilabel:`On Hand`: the amount of product currently available
**Numbered list**
To create a new website page, proceed as follows:
#. - Either open the **Website** app, click :guilabel:`+ New` in the top-right corner, then
select :guilabel:`Page`;
- Or go to :menuselection:`Website --> Site --> Pages` and click :guilabel:`New`.
#. Enter a :guilabel:`Page Title`; this title is used in the menu and the page's URL.
#. Click :guilabel:`Create`.
#. Customize the page's content and appearance using the website builder, then click
:guilabel:`Save`.
.. seealso::
- :ref:`RST cheat sheet: headings <contributing/headings>`
- :ref:`RST cheat sheet: markups <contributing/markups>`
:ref:`RST cheat sheet: lists <contributing/rst/lists>`
.. _contributing/organizing-documentation:
Icons
=====
Organizing the documentation
============================
Use :ref:`icons <contributing/rst/icons>` in instructions to help readers identify user interface
elements and reduce the need for lengthy explanations. Accompany every icon with a descriptor
in brackets.
When writing documentation about a given topic, try to keep pages within the same folder organized.
.. example::
Once the developer mode is activated, the developer tools can be accessed by clicking the
:icon:`fa-bug` (:guilabel:`bug`) icon.
For most topics, a single page should do the job. Place it in the appropriate section of the
documentation (e.g., content related to the CRM app go under :menuselection:`Applications
-> Sales -> CRM`) and follow the :ref:`document structure <contributing/document-structure>`
guidelines.
.. seealso::
:ref:`RST cheat sheet: icons <contributing/rst/icons>`
For more complex topics, you may need several pages to cover all their aspects. Usually, you will
find yourself adding documentation to a topic that is already partially covered. In that case,
either create a new page and place it at the same level as other related pages or add new sections
to an existing page. If you are documenting a complex topic from scratch, organize your content
between one parent page (the :abbr:`TOC (Tree Of Contents)` page) and several child pages. Whenever
possible, write content on the parent page and not only on the child pages. Make the parent page
accessible from the navigation menu by using the :ref:`show-content
<contributing/document-metadata>` metadata directive.
.. _contributing/content-images:
.. _contributing/content/images:
Images
======
Adding a few images to illustrate your text helps the readers to understand and memorize your
content. However, avoid adding too many images: it isn't necessary to illustrate all steps and
features, and it may overload your page.
Adding a few images to illustrate text helps the readers understand and memorize the content.
However, images should never replace text: written instructions should be complete and clear on
their own, without relying on visual aids. Use images sparingly, for example, to highlight a
particular point or clarify an example.
.. important::
Don't forget to :ref:`compress your PNG files with pngquant
<contributing/documentation/first-contribution>`.
Do not forget to `compress your PNG files with pngquant <https://pngquant.org>`_.
.. _contributing/screenshots:
.. _contributing/content/screenshots:
Screenshots
-----------
Screenshots are automatically resized to fit the content block's width. This implies that
screenshots can't be too wide, else they would appear very small on-screen. Therefore, we recommend
to avoid to take screenshots of a full screen display of the app, unless it is relevant to do so.
Screenshots are automatically resized to fit the content block's width. This implies that if they
are too wide, they are not readable on lower-resolution screens. We recommend avoiding full-screen
screenshots of the app unless absolutely necessary and making sure images are no wider than a range
of 768-933 pixels.
A few tips to improve your screenshots:
Here are a few tips to improve your screenshots:
#. **Zoom** in your browser. We recommend a 110% zoom for better results.
#. **Resize** your browser's width, either by *resizing the window* itself or by opening the
*browser's developer tools* (press the ``F12`` key) and resizing the width.
#. **Select** the relevant area, rather than keeping the full window.
#. If necessary, you can **edit** the screenshot to remove unnecessary fields and to narrow even
more Odoo's display.
*browser's developer tools* and resizing the width.
#. **Select** the relevant area rather than keeping the entire window.
#. **Remove** unnecessary information and **resize** columns when applicable.
.. image:: content_guidelines/screenshot-tips.gif
:align: center
:alt: Three tips to take good screenshots for the Odoo documentation.
.. important::
Do not use markups such as rectangles or arrows on screenshots. Instead, crop the image to
highlight the most relevant information, and ensure that text instructions are clear and
self-explanatory without relying on images.
.. note::
Resizing the window's width is the most important step to do as Odoo's responsive design
automatically resizes all fields to match the window's width.
.. example::
**Good example (resized browser, no unnecessary columns, adjusted columns' width, cropped):**
.. _contributing/media-files:
.. image:: content_guidelines/quotations-list-reduced.png
:alt: Cropped screenshot
**Bad example (full-width screenshot):**
.. image:: content_guidelines/quotations-list-full.png
:alt: Full-width screenshot
.. _contributing/content/media-files:
Media files
-----------
A **media filename**:
- is written in **lower-case letters**
- is **relevant** to the media's content. (E.g., :file:`screenshot-tips.gif`.)
- separates its words with a **hyphen** ``-`` (E.g., :file:`awesome-filename.png`.)
- is written in **lower-case letters**;
- is **relevant** to the media's content. (e.g., :file:`screenshot-tips.gif`);
- separates its words with a **hyphen** `-` (e.g., :file:`awesome-filename.png`).
Each document has its own folder in which the media files are located. The folder's name must be the
same as the document's filename.
Each RST file has its own folder for storing media files. The folder's name must be the same as the
RST file's name.
For example, the document :file:`doc_filename.rst` refers to two images that are placed in the
folder ``doc_filename``.
@@ -238,12 +304,12 @@ folder ``doc_filename``.
.. note::
Previously, image filenames would mostly be named with numbers (e.g., :file:`feature01.png`) and
placed in a single ``media`` folder. While it is advised not to name your *new* images in that
fashion, it is also essential **not to rename unchanged files**, as doing this would double the
weight of renamed image files on the repository. They will eventually all be replaced as the
placed in a single :file:`media` folder. While it is advised not to name your *new* images in
that fashion, it is also essential **not to rename unchanged files**, as doing this would double
the weight of renamed image files on the repository. They will eventually all be replaced as the
content referencing those images is updated.
.. _contributing/alt-tags:
.. _contributing/content/alt-tags:
ALT tags
--------
@@ -251,14 +317,22 @@ ALT tags
An **ALT tag** is a *text alternative* to an image. This text is displayed if the browser fails to
render the image. It is also helpful for users who are visually impaired. Finally, it helps
search engines, such as Google, to understand what the image is about and index it correctly, which
improves the :abbr:`SEO (Search Engine Optimization)` significantly.
improves :abbr:`SEO (Search Engine Optimization)`.
Good ALT tags are:
- **Short** (one line maximum)
- **Not a repetition** of a previous sentence or title
- A **good description** of the action happening on the image
- Easily **understandable** if read aloud
- **Short** (one line maximum);
- **Not a repetition** of a previous sentence or title;
- A **good description** of the action happening in the image;
- Easily **understandable** if read aloud.
.. example::
An appropriate ALT tag for the following screenshot would be *Activating the developer mode in
the Settings app*.
.. image:: content_guidelines/settings.png
:alt: Activating the developer mode in the Settings app
.. seealso::
- :ref:`RST cheat sheet: image directive <contributing/image>`
:ref:`RST cheat sheet: images <contributing/rst/images>`
Binary file not shown.

After

Width:  |  Height:  |  Size: 83 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 2.0 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.1 KiB

File diff suppressed because it is too large Load Diff
Binary file not shown.

Before

Width:  |  Height:  |  Size: 13 KiB

File diff suppressed because it is too large Load Diff
Binary file not shown.

After

Width:  |  Height:  |  Size: 5.9 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 7.6 KiB

-4
View File
@@ -1,4 +0,0 @@
As soon as your :abbr:`PR (Pull Request)` is ready for merging, a member of the Odoo team will be
automatically assigned for review. If the reviewer has questions or remarks, they will post them as
comments and you will be notified by email. Those comments must be resolved for the contribution to
go forward.
+1 -1
View File
@@ -175,7 +175,7 @@ values).
<odoo>
<data noupdate="1">
<record name="partner_1" model="res.partner">
<record id="partner_1" model="res.partner">
<field name="name">Odude</field>
</record>
File diff suppressed because it is too large Load Diff
+194 -13
View File
@@ -629,10 +629,14 @@ msgid ""
"contact is a repository of vital business information, facilitating "
"communication and business transactions."
msgstr ""
"Die *Kontakte*-App wird auf allen Odoo-Datenbanken installiert. Kontakte "
"werden für Kunden erstellt, mit denen das Unternehmen über Odoo Geschäfte "
"macht. Ein Kontakt ist ein Datensatz für wichtige Geschäftsinformationen, "
"die die Kommunikation und geschäftliche Transaktionen erleichtern."
#: ../../content/applications/essentials/contacts.rst:10
msgid "Contact form"
msgstr ""
msgstr "Kontaktformular"
#: ../../content/applications/essentials/contacts.rst:12
msgid ""
@@ -640,10 +644,14 @@ msgid ""
"click :guilabel:`Create`. A new form appears where various contact "
"information can be added."
msgstr ""
"Um einen neuen Kontakt zu erstellen, navigieren Sie zur "
":menuselection:`Kontakte-App` und klicken auf :guilabel:`Neu`. Es erscheint "
"ein neues Formular, in das Sie verschiedene Kontaktinformationen eingeben "
"können."
#: ../../content/applications/essentials/contacts.rst:16
msgid "Contact type"
msgstr ""
msgstr "Kontakttyp"
#: ../../content/applications/essentials/contacts.rst:18
msgid ""
@@ -651,6 +659,10 @@ msgid ""
"contacts. Select either :guilabel:`Individual` or :guilabel:`Company`, "
"depending on the type of contact that is being added."
msgstr ""
"Odoo erlaubt sowohl Kontakte in Form von :guilabel:`Einzelpersonen` als auch"
" :guilabel:`Unternehmen`. Wählen Sie entweder :guilabel:`Einzelperson` oder "
":guilabel:`Unternehmen`, je nachdem, welche Art von Kontakt Sie hinzufügen "
"möchten."
#: ../../content/applications/essentials/contacts.rst:22
msgid "Name"
@@ -662,6 +674,9 @@ msgid ""
":guilabel:`Company`. This is how the name appears throughout the database. "
"This field is **mandatory**."
msgstr ""
"Geben Sie zunächst den Namen der :guilabel:`Einzelperson` oder des "
":guilabel:`Unternehmens` ein. So wird der Name in der Datenbank angezeigt. "
"Dieses Feld ist ein **Pflichtfeld**."
#: ../../content/applications/essentials/contacts.rst:28
msgid ""
@@ -669,6 +684,10 @@ msgid ""
"linked to it. After selecting :guilabel:`Individual`, a new "
":guilabel:`Company Name...` field appears below the first name field."
msgstr ""
"Mit Kontakte vom Typ :guilabel:`Einzelpersonen` können Kontakte vom Typ "
":guilabel:`Unternehmen` verknüpft sein. Nachdem Sie :guilabel:`Einzelperson`"
" ausgewählt haben, erscheint ein neues Feld :guilabel:`Unternehmensname...` "
"unterhalb des Feldes für den Vornamen."
#: ../../content/applications/essentials/contacts.rst:33
msgid "Address"
@@ -679,6 +698,8 @@ msgid ""
"Next, enter the :guilabel:`Address` of the :guilabel:`Company` or "
":guilabel:`Individual`."
msgstr ""
"Als nächstes geben Sie die :guilabel:`Adresse` des :guilabel:`Unternehmens` "
"oder der :guilabel:`Einzelperson` ein."
#: ../../content/applications/essentials/contacts.rst:38
msgid ""
@@ -688,32 +709,43 @@ msgid ""
":guilabel:`Delivery Address`, :guilabel:`Other Address`, and "
":guilabel:`Private Address`."
msgstr ""
"Wenn Sie die Option :guilabel:`Einzelperson` gewählt haben, können Sie den "
"*Typ der Adresse* aus einem Dropdown-Menü auswählen. Zu den Optionen für "
"dieses Dropdown-Menü gehören: :guilabel:`Kontakt`, "
":guilabel:`Rechnungsadresse`, :guilabel:`Lieferadresse`, :guilabel:`Andere "
"Adresse` und :guilabel:`Private Adresse`."
#: ../../content/applications/essentials/contacts.rst:44
msgid "Additional fields"
msgstr ""
msgstr "Zusätzliche Felder"
#: ../../content/applications/essentials/contacts.rst:46
msgid ""
"Additional details are included on the initial form. The following fields "
"are available:"
msgstr ""
"Das ursprüngliche Formular enthält zusätzliche Angaben. Die folgenden Felder"
" sind verfügbar:"
#: ../../content/applications/essentials/contacts.rst:48
msgid ":guilabel:`VAT`: Value Added Tax number."
msgstr ""
msgstr ":guilabel:`USt-IdNr.`: Umsatzsteuer-Identifikationsnummer."
#: ../../content/applications/essentials/contacts.rst:49
msgid ""
":guilabel:`Citizen Identification`: citizen or government identification "
"number (only available on :guilabel:`Individual`)."
msgstr ""
":guilabel:`ID`: Bürger- oder Regierungsidentifikationsnummer (nur verfügbar "
"bei :guilabel:`Einzelperson`)."
#: ../../content/applications/essentials/contacts.rst:51
msgid ""
":guilabel:`Job Position`: list the job position of the "
":guilabel:`Individual` (only available on :guilabel:`Individual`)."
msgstr ""
":guilabel:`Stelle`: Geben Sie die Stelle der :guilabel:`Einzelperson` an "
"(nur für :guilabel:`Einzelperson` verfügbar)."
#: ../../content/applications/essentials/contacts.rst:53
msgid ""
@@ -721,6 +753,10 @@ msgid ""
"an SMS, or WhatsApp message by hovering over the field on the saved form, "
"and clicking the desired option."
msgstr ""
":guilabel:`Telefon`: Geben Sie die Telefonnummer (mit Landesvorwahl) an. "
"Tätigen Sie einen Anruf, senden Sie eine SMS oder eine WhatsApp-Nachricht, "
"indem Sie mit dem Mauszeiger über das Feld im gespeicherten Formular fahren "
"und auf die gewünschte Option klicken."
#: ../../content/applications/essentials/contacts.rst:55
msgid ""
@@ -728,16 +764,22 @@ msgid ""
"call, send an SMS, or WhatsApp message by hovering over the field on the "
"saved form, and clicking on the desired option."
msgstr ""
":guilabel:`Mobil`: Geben Sie die Mobiltelefonnummer (mit Landesvorwahl) an. "
"Tätigen Sie einen Anruf, senden Sie eine SMS oder eine WhatsApp-Nachricht, "
"indem Sie mit dem Mauszeiger über das Feld im gespeicherten Formular fahren "
"und auf die gewünschte Option klicken."
#: ../../content/applications/essentials/contacts.rst:57
msgid ":guilabel:`Email`: enter the email address with the domain."
msgstr ""
msgstr ":guilabel:`E-Mail`: Geben Sie die E-Mail-Adresse mit der Domain an."
#: ../../content/applications/essentials/contacts.rst:58
msgid ""
":guilabel:`Website`: enter the full website address, starting with `http` or"
" `https`."
msgstr ""
":guilabel:`Website`: Geben Sie die vollständige Website-Adresse an, "
"beginnend mit `http` oder `https`."
#: ../../content/applications/essentials/contacts.rst:59
msgid ""
@@ -745,6 +787,9 @@ msgid ""
":guilabel:`Miss`, :guilabel:`Mister`, :guilabel:`Professor`, or create a new"
" one directly from this field."
msgstr ""
":guilabel:`Anrede`: Wählen Sie :guilabel:`Doktor`, :guilabel:`Frau`, "
":guilabel:`Fräulein`, :guilabel:`Herr`, :guilabel:`Professor`, oder "
"erstellen Sie einen neuen Titel direkt aus diesem Feld."
#: ../../content/applications/essentials/contacts.rst:61
msgid ""
@@ -753,6 +798,11 @@ msgid ""
"the new tag in the field, and click :guilabel:`Create` from the resulting "
"drop-down menu."
msgstr ""
":guilabel:`Stichwörter`: Geben Sie vorkonfigurierte Stichwörter ein, indem "
"Sie sie in das Feld eingeben oder auf das Dropdown-Menü klicken und einen "
"auswählen. Um ein neues Stichwort zu erstellen, geben Sie das neue Stichwort"
" in das Feld ein und klicken auf :guilabel:`Neu` aus dem sich öffnenden "
"Dropdown-Menü."
#: ../../content/applications/essentials/contacts.rst:66
msgid "Contacts & Addresses tab"
@@ -765,6 +815,11 @@ msgid ""
"associated with a :guilabel:`Company` and related addresses. For example, a "
"specific contact person for the company can be listed here."
msgstr ""
"Am unteren Rand des Kontaktformulars befinden sich mehrere Reiter. Im Reiter"
" :guilabel:`Kontakte & Adressen` können Kontakte hinzugefügt werden, die mit"
" einem :guilabel:`Unternehmen` und den dazugehörigen Adressen verbunden "
"sind. Hier kann zum Beispiel eine bestimmte Kontaktperson für das "
"Unternehmen aufgeführt werden."
#: ../../content/applications/essentials/contacts.rst:72
msgid ""
@@ -773,6 +828,11 @@ msgid ""
":guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create "
"Contact` pop-up form, in which additional addresses can be configured."
msgstr ""
"Sowohl zu :guilabel:`Einzelperson` als auch zu :guilabel:`Unternehmen` "
"können Sie mehrere Adressen hinzufügen. Klicken Sie dazu auf "
":guilabel:`Hinzufügen` im Reiter :guilabel:`Kontakte & Adressen`. Daraufhin "
"öffnet sich ein Pop-up-Formular :guilabel:`Kontakt erstellen`, in dem Sie "
"zusätzliche Adressen konfigurieren können."
#: ../../content/applications/essentials/contacts.rst-1
msgid "Add a contact/address to the contact form."
@@ -784,6 +844,9 @@ msgid ""
" :guilabel:`Other Address` field at the top to reveal a drop-down menu of "
"address-related options."
msgstr ""
"Klicken Sie im Pop-up-Formular :guilabel:`Kontakt erstellen` zunächst oben "
"auf das Standardfeld :guilabel:`Andere Adresse`, um ein Drop-down-Menü mit "
"adressbezogenen Optionen zu öffnen."
#: ../../content/applications/essentials/contacts.rst:83
msgid "Select any of the following options:"
@@ -838,12 +901,18 @@ msgid ""
"Once an option is selected, enter the corresponding contact information that"
" should be used for the specified address type."
msgstr ""
"Sobald Sie eine Option ausgewählt haben, geben Sie die entsprechenden "
"Kontaktinformationen ein, die für den angegebenen Adresstyp verwendet werden"
" sollen."
#: ../../content/applications/essentials/contacts.rst:98
msgid ""
"Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, "
"along with the :guilabel:`Phone` and/or :guilabel:`Mobile` numbers below."
msgstr ""
"Fügen Sie unten den :guilabel:`Namen des Kontakts`, die :guilabel:`Adresse`,"
" die :guilabel:`E-Mail` sowie die :guilabel:`Telefon`- und/oder die "
":guilabel:`Mobil`-nummer ein."
#: ../../content/applications/essentials/contacts.rst:101
msgid ""
@@ -851,12 +920,18 @@ msgid ""
"address type has been selected. This is similar to the "
":guilabel:`Individual` contact."
msgstr ""
"Legen Sie die :guilabel:`Stelle` fest, die erscheint, wenn der Adresstyp "
":guilabel:`Kontakt` ausgewählt wurde. Dies ist ähnlich wie der Kontakt "
":guilabel:`Einzelperson`."
#: ../../content/applications/essentials/contacts.rst:104
msgid ""
"To add a note, click on the text field next to :guilabel:`Notes`, and write "
"anything that is applicable to the customer or contact."
msgstr ""
"Um eine Notiz hinzuzufügen, klicken Sie auf das Textfeld neben "
":guilabel:`Notizen`, und schreiben Sie alles, was auf den Kunden oder "
"Kontakt zutrifft."
#: ../../content/applications/essentials/contacts.rst:107
msgid ""
@@ -864,6 +939,10 @@ msgid ""
":guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save "
"the address, and immediately input another one."
msgstr ""
"Klicken Sie dann auf :guilabel:`Speichern & Schließen`, um die Adresse zu "
"speichern und das Fenster :guilabel:`Kontakt erstellen` zu schließen. Oder "
"klicken Sie auf :guilabel:`Speichern & Neu`, um die Adresse zu speichern und"
" sofort eine neue einzugeben."
#: ../../content/applications/essentials/contacts.rst:111
msgid "Sales & Purchase tab"
@@ -874,6 +953,9 @@ msgid ""
"Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the "
"*Sales*, *Purchase*, **or** *Point of Sale* applications are installed."
msgstr ""
"Als nächstes folgt der Reiter :guilabel:`Verkauf & Einkauf`, der nur "
"erscheint, wenn die Apps *Verkauf*, *Einkauf*, **oder** *Kassensystem* "
"installiert sind."
#: ../../content/applications/essentials/contacts.rst:116
msgid ""
@@ -881,6 +963,9 @@ msgid ""
"Purchases` tab. Select a :guilabel:`Fiscal Position` from the drop-down "
"menu."
msgstr ""
"Die :guilabel:`Steuerposition` können Sie auf der Registerkarte "
":guilabel:`Verkauf & Einkauf` einstellen. Wählen Sie eine "
":guilabel:`Steuerposition` aus dem Dropdown-Menü."
#: ../../content/applications/essentials/contacts.rst:120
msgid "Sales section"
@@ -893,6 +978,11 @@ msgid ""
"drop-down field, and select one. Create a new :guilabel:`Salesperson` by "
"typing the user's name, and making the appropriate selection."
msgstr ""
"Unter der Überschrift :guilabel:`Verkauf` können Sie einem Kontakt einen "
"bestimmten :guilabel:`Vertriebsmitarbeiter` zuweisen. Klicken Sie dazu auf "
"das Dropdown-Feld :guilabel:`Vertriebsmitarbeiter`, und wählen Sie einen "
"aus. Erstellen Sie ein neues :guilabel:`Vertriebsmitarbeiter`, indem Sie den"
" Namen des Benutzers eingeben und die entsprechende Auswahl treffen."
#: ../../content/applications/essentials/contacts.rst:126
msgid ""
@@ -902,16 +992,25 @@ msgid ""
"or :guilabel:`Create` a new one. Select the :guilabel:`Pricelist` drop-down "
"menu to choose the appropriate :guilabel:`Pricelist`."
msgstr ""
"Bestimmte :guilabel:`Zahlungsbedingungen` oder eine bestimmte "
":guilabel:`Preisliste` können bei Bedarf ebenfalls festgelegt werden. "
"Klicken Sie auf das Dropdown-Menü neben :guilabel:`Zahlungsbedingungen` und "
"ändern Sie es in eine der vorgewählten :guilabel:`Zahlungsbedingungen` oder "
":guilabel:`Erstellen` eine neue. Wählen Sie das Dropdown-Menü "
":guilabel:`Preisliste`, um die entsprechende :guilabel:`Preisliste` "
"auszuwählen."
#: ../../content/applications/essentials/contacts.rst:131
msgid ""
"Click into the :guilabel:`Delivery Method` field to select an option from "
"the drop-down menu."
msgstr ""
"Klicken Sie in das Feld :guilabel:`Liefermethode`, um eine Option aus dem "
"Dropdown-Menü auszuwählen."
#: ../../content/applications/essentials/contacts.rst:134
msgid "Point Of Sale section"
msgstr ""
msgstr "Abschnitt „Kassensystem“"
#: ../../content/applications/essentials/contacts.rst:136
msgid ""
@@ -919,10 +1018,14 @@ msgid ""
"that can be used to identify the contact. Use the :guilabel:`Loyalty Points`"
" field to track points the user won as part of a *Loyalty Program*."
msgstr ""
"Geben Sie unter der Überschrift :guilabel:`Kassensystem` einen "
":guilabel:`Barcode` ein, der zur Identifizierung des Kontakts verwendet "
"werden kann. Verwenden Sie das Feld :guilabel:`Treuepunkte`, um die Punkte "
"zu erfassen, die der Benutzer im Rahmen eines *Treueprogramms* gewonnen hat."
#: ../../content/applications/essentials/contacts.rst:141
msgid "Purchase section"
msgstr ""
msgstr "Abschnitt „Einkauf“"
#: ../../content/applications/essentials/contacts.rst:143
msgid ""
@@ -930,10 +1033,13 @@ msgid ""
"preferred :guilabel:`Payment Method` here. A :guilabel:`Receipt Reminder` "
"can be set here, as well."
msgstr ""
"Geben Sie hier :guilabel:`Zahlungsbedingungen`, :guilabel:`1099 Box` "
"Informationen und eine bevorzugte :guilabel:`Zahlungsmethode` an. Auch eine "
":guilabel:`Eingangserinnerung` kann hier eingestellt werden."
#: ../../content/applications/essentials/contacts.rst:147
msgid "Misc section"
msgstr ""
msgstr "Abschnitt „Sonstige“"
#: ../../content/applications/essentials/contacts.rst:149
msgid ""
@@ -948,10 +1054,22 @@ msgid ""
"from the drop-down menu. Use the :guilabel:`SLA Policies` field to assign a "
"*Helpdesk* SLA policy to this contact."
msgstr ""
"Unter der Überschrift :guilabel:`Sonstige verwenden Sie das Feld "
":guilabel:`Referenz`, um zusätzliche Informationen zu diesem Kontakt "
"hinzuzufügen. Wenn dieser Kontakt nur für ein Unternehmen in einer Datenbank"
" mit mehreren Unternehmen zugänglich sein soll, wählen Sie es aus der "
"Dropdown-Liste des Feldes :guilabel:`Unternehmen` aus. Verwenden Sie das "
"Dropdown-Menü :guilabel:`Website`, um die Veröffentlichung dieses Kontakts "
"auf eine Website zu beschränken (wenn Sie mit einer Datenbank mit mehreren "
"Websites arbeiten). Wählen Sie ein oder mehrere :guilabel:`Website-"
"Stichwörter`, um die veröffentlichten Kunden auf der Seite `/Kunden` zu "
"filtern. Wählen Sie eine :guilabel:`Branche` für diesen Kontakt aus dem "
"Dropdown-Menü. Verwenden Sie das Feld :guilabel:`SLA-Richtlinien`, um diesem"
" Kontakt eine SLA-Richtlinie für *Kundendienst* zuzuweisen."
#: ../../content/applications/essentials/contacts.rst:159
msgid "Accounting tab"
msgstr ""
msgstr "Reiter „Buchhaltung“"
#: ../../content/applications/essentials/contacts.rst:161
msgid ""
@@ -959,12 +1077,19 @@ msgid ""
"installed. Here, a user can add any related :guilabel:`Bank Accounts`, or "
"set default :guilabel:`Accounting entries`."
msgstr ""
"Der Reiter :guilabel:`Buchhaltung` erscheint, wenn die *Buchhaltungsapp* "
"installiert ist. Hier kann ein Benutzer alle zugehörigen "
":guilabel:`Bankkonten` hinzufügen oder Standards für :guilabel:`Buchungen` "
"festlegen."
#: ../../content/applications/essentials/contacts.rst:164
msgid ""
"Under the :guilabel:`Miscellaneous` heading, use the :guilabel:`LEI` field "
"to enter a Legal Entity Identifier, if necessary."
msgstr ""
"Verwenden Sie unter der Überschrift :guilabel:`Sonstiges` das Feld "
":guilabel:`LEI`, um einen Legal Entity Identifier einzugeben, falls "
"erforderlich."
#: ../../content/applications/essentials/contacts.rst:168
msgid "Internal Notes tab"
@@ -976,10 +1101,13 @@ msgid ""
"tab, where notes can be left on this contact form, just like on the contact "
"form noted above."
msgstr ""
"Nach dem Reiter :guilabel:`Buchhaltung` folgt der Reiter :guilabel:`Interne "
"Notizen`, auf der Sie Notizen zu diesem Kontaktformular hinterlassen können,"
" genau wie bei dem oben genannten Kontaktformular."
#: ../../content/applications/essentials/contacts.rst:174
msgid "Partner Assignment tab"
msgstr ""
msgstr "Reiter „Partnerzuweisung“"
#: ../../content/applications/essentials/contacts.rst:176
msgid ""
@@ -992,7 +1120,7 @@ msgstr ""
#: ../../content/applications/essentials/contacts.rst:182
msgid "Membership tab"
msgstr ""
msgstr "Reiter „Mitgliedschaft“"
#: ../../content/applications/essentials/contacts.rst:184
msgid ""
@@ -1004,13 +1132,15 @@ msgstr ""
#: ../../content/applications/essentials/contacts.rst:189
msgid "Smart buttons"
msgstr ""
msgstr "Intelligente Schaltflächen"
#: ../../content/applications/essentials/contacts.rst:191
msgid ""
"At the top of the contact form, there are some additional options available,"
" known as *smart buttons*."
msgstr ""
"Am oberen Rand des Kontaktformulars stehen Ihnen einige zusätzliche Optionen"
" zur Verfügung, die so genannten *intelligenten Schaltflächen*."
#: ../../content/applications/essentials/contacts.rst:194
msgid ""
@@ -1018,6 +1148,9 @@ msgid ""
" created on other apps. Odoo integrates information from every single app, "
"so there are many smart buttons."
msgstr ""
"Hier zeigt Odoo eine Vielzahl von Datensätzen zu diesem Kontakt an, die in "
"anderen Apps erstellt wurden. Odoo integriert Informationen aus jeder "
"einzelnen App, daher gibt es viele intelligente Schaltflächen."
#: ../../content/applications/essentials/contacts.rst:198
msgid ""
@@ -1025,12 +1158,17 @@ msgid ""
"the opportunities related to this customer from the *CRM* app are "
"accessible."
msgstr ""
"Es gibt zum Beispiel eine intelligente Schaltfläche "
":guilabel:`Verkaufschancen`, über die Sie auf alle Verkaufschancen zugreifen"
" können, die mit diesem Kunden aus der *CRM*-App verbunden sind."
#: ../../content/applications/essentials/contacts.rst:202
msgid ""
"If the corresponding applications are installed, their related smart buttons"
" appear automatically on a contact form."
msgstr ""
"Wenn die entsprechenden Apps installiert sind, erscheinen die zugehörigen "
"intelligenten Schaltflächen automatisch in einem Kontaktformular."
#: ../../content/applications/essentials/contacts.rst:205
msgid ""
@@ -1042,6 +1180,14 @@ msgid ""
":guilabel:`Invoiced` information, :guilabel:`Vendor Bills`, and the "
":guilabel:`Partner Ledger` connected to this contact."
msgstr ""
"Ein Benutzer kann alle :guilabel:`Meetings`, :guilabel:`Verkäufe`, "
":guilabel:`Kassenaufträge`, :guilabel:`Abonnements`, :guilabel:`Aufgaben` "
"von Projekten sehen, und die intelligente Schaltfläche :guilabel:`Mehr` "
"zeigt über ein Dropdown-Menü weitere Optionen an. Ein Benutzer kann sogar "
"schnell auf :guilabel:`Einkäufe`, :guilabel:`Kundendienst`-Aufgaben, "
":guilabel:`Pünktlichkeitsrate` für Lieferungen, "
":guilabel:`Abgerechnet`-Informationen, :guilabel:`Lieferantenrechnungen` und"
" das mit diesem Kontakt verbundene :guilabel:`Partnerbuch` zugreifen."
#: ../../content/applications/essentials/contacts.rst:211
msgid ""
@@ -1049,16 +1195,22 @@ msgid ""
" smart buttons, like this, should there be any outstanding/on-file for this "
"contact."
msgstr ""
"Lieferungen, Dokumente, Treuekarten und Lastschriften sind *auch* mit "
"intelligenten Schaltflächen wie dieser verknüpft, falls für diesen Kontakt "
"noch etwas aussteht oder gespeichert ist."
#: ../../content/applications/essentials/contacts.rst:214
msgid ""
"If the contact is a partner, the user can visit their partner page on the "
"Odoo-built website by clicking the :guilabel:`Go to Website` smart button."
msgstr ""
"Wenn es sich bei dem Kontakt um einen Partner handelt, kann der Benutzer "
"dessen Partnerseite auf der von Odoo erstellten Website besuchen, indem er "
"auf die intelligente Schaltfläche :guilabel:`Zur Website` klickt."
#: ../../content/applications/essentials/contacts.rst:218
msgid "Archive contacts"
msgstr ""
msgstr "Kontakte archivieren"
#: ../../content/applications/essentials/contacts.rst:220
msgid ""
@@ -1067,12 +1219,18 @@ msgid ""
":guilabel:`Action` menu at the top of the contact form, and click "
":guilabel:`Archive`."
msgstr ""
"Wenn ein Benutzer beschließt, dass er diesen Kontakt nicht mehr aktiv haben "
"möchte, kann der Datensatz archiviert werden. Gehen Sie dazu zum Menü "
":icon:`fa-cog` :guilabel:`Aktion` am oberen Rand des Kontaktformulars und "
"klicken Sie auf :guilabel:`Archivieren`."
#: ../../content/applications/essentials/contacts.rst:224
msgid ""
"Then, click :guilabel:`OK` from the resulting :guilabel:`Confirmation` pop-"
"up window."
msgstr ""
"Klicken Sie dann im daraufhin erscheinenden Pop-up-Fenster "
":guilabel:`Bestätigung` auf :guilabel:`OK`."
#: ../../content/applications/essentials/contacts.rst:226
msgid ""
@@ -1080,6 +1238,10 @@ msgid ""
"top, they do not show up in the main contacts page, but they can still be "
"searched for with the :guilabel:`Archived` filter."
msgstr ""
"Wenn dieser Kontakt erfolgreich archiviert wurde, was durch ein Banner am "
"oberen Rand angezeigt wird, wird er nicht auf der Hauptseite der Kontakte "
"angezeigt, aber Sie können immer noch mit dem Filter :guilabel:`Archiviert` "
"nach ihm suchen."
#: ../../content/applications/essentials/contacts.rst:230
msgid ""
@@ -1089,18 +1251,28 @@ msgid ""
"doing so, the :guilabel:`Archived` banner is removed, and the contact is "
"restored."
msgstr ""
"Die *Archivierung* eines Kontakts kann *aufgehoben* werden, wenn der "
"Benutzer beschließt, wieder mit ihm zu arbeiten. Klicken Sie dazu einfach "
"erneut auf das Menü :icon:`fa-cog` :guilabel:`Aktion` am oberen Rand des "
"archivierten Kontaktformulars und klicken Sie auf :guilabel:`Archivierung "
"aufheben`. Daraufhin wird das Banner :guilabel:`Archiviert` entfernt und der"
" Kontakt wird wiederhergestellt."
#: ../../content/applications/essentials/contacts.rst:236
msgid ""
":doc:`Add different addresses in CRM "
"<../sales/sales/send_quotations/different_addresses>`"
msgstr ""
":doc:`Mehrere Adressen in CRM hinzufügen "
"<../sales/sales/send_quotations/different_addresses>`"
#: ../../content/applications/essentials/contacts.rst:237
msgid ""
"`Odoo's eLearning Contacts tutorial "
"<https://www.odoo.com/slides/slide/contacts-2527?fullscreen=1>`_"
msgstr ""
"`Odoos Tutorial zu E-Learning-Kontakten "
"<https://www.odoo.com/slides/slide/contacts-2527?fullscreen=1>`_"
#: ../../content/applications/essentials/export_import_data.rst:3
msgid "Export and import data"
@@ -2684,6 +2856,11 @@ msgid ""
":guilabel:`Contacts` section. Under the :guilabel:`Contacts` section, where "
"it says :guilabel:`Odoo IAP`, click :guilabel:`View My Services`."
msgstr ""
"Gehen Sie zunächst zur :menuselection:`Einstellungen-App` und geben Sie "
"`IAP` in die Leiste :guilabel:`Suchen ...` ein. Alternativ können Sie auch "
"zum Abschnitt :guilabel:`Kontakte` scrollen. Unter dem Abschnitt "
":guilabel:`Kontakte`, unter :guilabel:`Odoo IAP`, klicken Sie auf "
":guilabel:`Meine Services ansehen`."
#: ../../content/applications/essentials/in_app_purchase.rst-1
msgid ""
@@ -2743,6 +2920,10 @@ msgid ""
":guilabel:`Search...` bar. Under the :guilabel:`Contacts` section, where it "
"says :guilabel:`Odoo IAP`, click :guilabel:`View My Services`."
msgstr ""
"Gehen Sie zur :menuselection:`Einstellungen-App` und geben Sie `IAP` in die "
"Leiste :guilabel:`Suchen ...` ein. Unter dem Abschnitt :guilabel:`Kontakte`,"
" unter :guilabel:`Odoo IAP`, klicken Sie auf :guilabel:`Meine Services "
"ansehen`."
#: ../../content/applications/essentials/in_app_purchase.rst:180
msgid ""
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
+2
View File
@@ -5039,6 +5039,8 @@ msgid ""
"To learn more about mailing lists and contacts, check out "
":doc:`mailing_lists_blacklists`."
msgstr ""
"Um mehr über Mailinglisten und Kontakte zu erfahren, lesen Sie bitte "
":doc:`mailing_lists_blacklists`."
#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1
msgid "View of the mailing list page in the SMS marketing application."
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
+2 -2
View File
@@ -1257,7 +1257,7 @@ msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:64
msgid ":doc:`/applications/general/users`"
msgstr ""
msgstr ":doc:`/applications/general/users`"
#: ../../content/applications/services/helpdesk/overview/ratings.rst:3
msgid "Ratings"
@@ -1335,7 +1335,7 @@ msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:88
#: ../../content/applications/services/helpdesk/overview/sla.rst:195
msgid ":doc:`../advanced/close_tickets`"
msgstr ""
msgstr ":doc:`../advanced/close_tickets`"
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:3
msgid "Start Receiving Tickets"
+2
View File
@@ -2890,6 +2890,8 @@ msgstr ""
msgid ""
"reCAPTCHA v3 may not be compliant with local data protection regulations."
msgstr ""
"reCAPTCHA v3 ist möglicherweise nicht mit den lokalen "
"Datenschutzbestimmungen konform."
#: ../../content/applications/websites/website/configuration/recaptcha.rst:12
msgid ""
+218 -233
View File
@@ -24,7 +24,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-05-28 08:57+0000\n"
"POT-Creation-Date: 2024-08-20 14:22+0000\n"
"PO-Revision-Date: 2022-03-18 14:59+0000\n"
"Last-Translator: Fernanda Alvarez, 2024\n"
"Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n"
@@ -815,7 +815,7 @@ msgstr ":guilabel:`Tablero de aplicaciones`"
#: ../../content/administration/odoo_online.rst:3
#: ../../content/administration/supported_versions.rst:29
#: ../../content/administration/upgrade.rst:90
#: ../../content/administration/upgrade.rst:307
#: ../../content/administration/upgrade.rst:305
msgid "Odoo Online"
msgstr "Odoo en línea"
@@ -1132,7 +1132,7 @@ msgstr ":doc:`odoo_accounts`"
#: ../../content/administration/odoo_sh.rst:5
#: ../../content/administration/supported_versions.rst:30
#: ../../content/administration/upgrade.rst:120
#: ../../content/administration/upgrade.rst:318
#: ../../content/administration/upgrade.rst:316
msgid "Odoo.sh"
msgstr "Odoo.sh"
@@ -1575,6 +1575,51 @@ msgstr ""
"<https://stackoverflow.com/a/1077421/3332416>`_: no deben causar efectos "
"secundarios al activarse con mayor frecuencia de la esperada."
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:36
msgid "How can I automate tasks when an IP address change occurs?"
msgstr ""
"¿Cómo puedo automatizar tareas cuando ocurre un cambio de dirección IP?"
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:38
msgid ""
"**Odoo.sh notifies project administrators of IP address changes.** "
"Additionally, when the IP address of a production instance changes, an HTTP "
"`GET` request is made to the path `/_odoo.sh/ip-change` with the new IP "
"address included as a query string parameter (`new`), along with the "
"previous IP address as an additional parameter (`old`)."
msgstr ""
"**Odoo.sh le notifica a los administradores del proyecto si hay cambios en "
"la dirección IP.** Además, cuando la dirección IP de una instancia de "
"producción cambia, se realiza una petición HTTP `GET` en la ruta "
"`/_odoo.sh/ip-change` con la nueva dirección IP incluida como un parámetro "
"de cadena de consulta (`new`), junto con la dirección IP anterior como un "
"parámetro adicional (`old`)."
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:43
msgid ""
"This mechanism allows custom actions to be applied in response to the IP "
"address change (e.g., sending an email, contacting a firewall API, "
"configuring database objects, etc.)"
msgstr ""
"Este mecanismo permite que pueda aplicar acciones personalizadas como "
"respuesta al cambio de dirección IP (por ejemplo, enviar un correo "
"electrónico, contactar una API de firewall, configurar objetos de la base de"
" datos, etc.)."
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:46
msgid ""
"For security reasons, the `/_odoo.sh/ip-change` route is accessible only "
"internally by the platform itself and returns a `403` response if accessed "
"through any other means."
msgstr ""
"Por motivos de seguridad, solo es posible acceder a la ruta `/_odoo.sh/ip-"
"change` desde la plataforma y devuelve la respuesta `403` si intenta acceder"
" por otros medios."
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:49
msgid "Here is a pseudo-implementation example:"
msgstr "Este es un ejemplo de pseudo-implementación:"
#: ../../content/administration/odoo_sh/advanced/submodules.rst:6
#: ../../content/administration/odoo_sh/getting_started/settings.rst:170
msgid "Submodules"
@@ -3711,9 +3756,9 @@ msgid ""
"synchronization (Calendars, files hosting, ...)."
msgstr ""
"Esto es para prevenir que su nueva base de datos importada realice acciones "
"que puedan impactar su proceso de producción, como el envío de correos "
"pendientes, envíos masivos o sincronización de servicios de terceros "
"(calendarios, alojamiento de archivos, etc...)."
"que puedan afectar su proceso de producción, como enviar correos pendientes,"
" procesar envíos masivos o sincronizar servicios de terceros (calendarios, "
"alojamiento de archivos, etc...)."
#: ../../content/administration/odoo_sh/getting_started/create.rst:190
msgid ""
@@ -4965,15 +5010,15 @@ msgstr "Admin"
#: ../../content/administration/supported_versions.rst:35
#: ../../content/administration/supported_versions.rst:41
#: ../../content/administration/supported_versions.rst:47
#: ../../content/administration/supported_versions.rst:48
#: ../../content/administration/supported_versions.rst:49
#: ../../content/administration/supported_versions.rst:53
#: ../../content/administration/supported_versions.rst:77
#: ../../content/administration/supported_versions.rst:78
#: ../../content/administration/supported_versions.rst:79
#: ../../content/administration/supported_versions.rst:95
#: ../../content/administration/supported_versions.rst:96
#: ../../content/administration/supported_versions.rst:97
#: ../../content/administration/supported_versions.rst:54
#: ../../content/administration/supported_versions.rst:55
#: ../../content/administration/supported_versions.rst:59
#: ../../content/administration/supported_versions.rst:60
#: ../../content/administration/supported_versions.rst:61
#: ../../content/administration/supported_versions.rst:65
#: ../../content/administration/supported_versions.rst:66
#: ../../content/administration/supported_versions.rst:67
msgid "|green|"
msgstr "|green|"
@@ -5271,7 +5316,7 @@ msgstr ""
#: ../../content/administration/on_premise.rst:5
#: ../../content/administration/upgrade.rst:150
#: ../../content/administration/upgrade.rst:342
#: ../../content/administration/upgrade.rst:340
msgid "On-premise"
msgstr "Local"
@@ -5808,11 +5853,11 @@ msgid ""
" ``www.mycompany.com`` or ``mycompany.co.uk``, but not for "
"``www2.mycompany.com`` or ``helpdesk.mycompany.com``."
msgstr ""
"Mostrar solo las bases de datos que coinciden con el primer subdominio "
"después de ``www``: por ejemplo, la base de datos \"miempresa\" se enseñará "
"si la solicitud entreante se envió a ``www.miempresa.com`` or "
"``miempresa.co.uk``, pero no para ``www2.miempresa.com`` o "
"``serviciodeasistencia.miempresa.com``."
"Para mostrar solo las bases de datos que coinciden con el primer subdominio "
"después de ``www``. Por ejemplo, la base de datos \"mycompany\" aparecesi"
" la solicitud entrante se envió a ``www.mycompany.com`` o a "
"``mycompany.co.uk``, pero no para ``www2.mycompany.com`` o "
"``helpdesk.mycompany.com``."
#: ../../content/administration/on_premise/deploy.rst:67
msgid ""
@@ -6923,9 +6968,9 @@ msgstr ""
#: ../../content/administration/on_premise/source.rst:176
#: ../../content/administration/on_premise/source.rst:204
#: ../../content/administration/on_premise/source.rst:235
#: ../../content/administration/on_premise/source.rst:320
#: ../../content/administration/on_premise/source.rst:389
#: ../../content/administration/on_premise/source.rst:452
#: ../../content/administration/on_premise/source.rst:324
#: ../../content/administration/on_premise/source.rst:393
#: ../../content/administration/on_premise/source.rst:456
msgid "Windows"
msgstr "Windows"
@@ -6946,8 +6991,8 @@ msgstr ""
#: ../../content/administration/on_premise/source.rst:195
#: ../../content/administration/on_premise/source.rst:224
#: ../../content/administration/on_premise/source.rst:267
#: ../../content/administration/on_premise/source.rst:380
#: ../../content/administration/on_premise/source.rst:442
#: ../../content/administration/on_premise/source.rst:384
#: ../../content/administration/on_premise/source.rst:446
msgid "Linux"
msgstr "Linux"
@@ -7558,7 +7603,7 @@ msgstr ""
"PostgreSQL:"
#: ../../content/administration/on_premise/packages.rst:57
#: ../../content/administration/on_premise/source.rst:412
#: ../../content/administration/on_premise/source.rst:416
msgid ""
"`wkhtmltopdf` is not installed through **pip** and must be installed "
"manually in `version 0.12.5 "
@@ -7844,9 +7889,9 @@ msgstr "Clonar con SSH"
#: ../../content/administration/on_premise/source.rst:182
#: ../../content/administration/on_premise/source.rst:209
#: ../../content/administration/on_premise/source.rst:249
#: ../../content/administration/on_premise/source.rst:343
#: ../../content/administration/on_premise/source.rst:401
#: ../../content/administration/on_premise/source.rst:463
#: ../../content/administration/on_premise/source.rst:347
#: ../../content/administration/on_premise/source.rst:405
#: ../../content/administration/on_premise/source.rst:467
msgid "Mac OS"
msgstr "Mac OS"
@@ -8042,27 +8087,35 @@ msgstr ""
#: ../../content/administration/on_premise/source.rst:276
msgid ""
"For Debian-based systems, the packages are listed in the `debian/control "
"<https://github.com/odoo/odoo/blob/15.0/debian/control>`_ file of the Odoo "
"sources."
msgstr ""
"Para sistemas basados en Debian, los paquetes se enumeran en el archivo "
"`debian/control <https://github.com/odoo/odoo/blob/15.0/debian/control>`_ de"
" la fuente de Odoo."
#: ../../content/administration/on_premise/source.rst:279
msgid ""
"On Debian/Ubuntu, the following commands should install the required "
"packages:"
msgstr ""
"En Debian/Ubunto, los siguientes comandos instalarán los paquetes "
"requeridos:"
#: ../../content/administration/on_premise/source.rst:283
msgid ""
"The `setup/debinstall.sh` script will parse the `debian/control "
"<https://github.com/odoo/odoo/blob/15.0/debian/control>` file and install "
"the found packages."
msgstr ""
"El script `setup/debinstall.sh` analizará el archivo `debian/control "
"<https://github.com/odoo/odoo/blob/15.0/debian/control>`_ e instalará los "
"paquetes que encuentre."
#: ../../content/administration/on_premise/source.rst:286
msgid "Install with pip"
msgstr "Instalación con pip"
#: ../../content/administration/on_premise/source.rst:288
#: ../../content/administration/on_premise/source.rst:289
msgid ""
"Using pip may lead to security issues and broken dependencies; only do this "
"if you know what you are doing."
msgstr ""
"El uso de pip podría ocasionar errores de seguridad y dependencias "
"incumplidas. Solo haga esto si conoce el procedimiento con exactitud. "
#: ../../content/administration/on_premise/source.rst:292
msgid ""
"As some of the Python packages need a compilation step, they require system "
"libraries to be installed."
@@ -8070,7 +8123,7 @@ msgstr ""
"Como algunos de los paquetes de Python necesitan un paso de compilación, es "
"necesario instalar las bibliotecas del sistema."
#: ../../content/administration/on_premise/source.rst:291
#: ../../content/administration/on_premise/source.rst:295
msgid ""
"On Debian/Ubuntu, the following command should install these required "
"libraries:"
@@ -8078,7 +8131,7 @@ msgstr ""
"En Debian/Ubuntu, este comando debería de instalar todas las bibliotecas "
"necesarias:"
#: ../../content/administration/on_premise/source.rst:297
#: ../../content/administration/on_premise/source.rst:301
msgid ""
"Odoo dependencies are listed in the :file:`requirements.txt` file located at"
" the root of the Odoo Community directory."
@@ -8087,7 +8140,7 @@ msgstr ""
":file:`requirements.txt` que se encuentra en el directorio raíz de la "
"versión Community de Odoo."
#: ../../content/administration/on_premise/source.rst:301
#: ../../content/administration/on_premise/source.rst:305
msgid ""
"The Python packages in :file:`requirements.txt` are based on their "
"stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo "
@@ -8101,9 +8154,9 @@ msgstr ""
" 2.8.0 en Debian Bullseye y 2.6.0 en Ubuntu Focal. La versión más baja se "
"elige en el archivo :file:`requirements.txt`."
#: ../../content/administration/on_premise/source.rst:308
#: ../../content/administration/on_premise/source.rst:330
#: ../../content/administration/on_premise/source.rst:349
#: ../../content/administration/on_premise/source.rst:312
#: ../../content/administration/on_premise/source.rst:334
#: ../../content/administration/on_premise/source.rst:353
msgid ""
"It can be preferable not to mix Python module packages between different "
"instances of Odoo or with the system. However, it is possible to use "
@@ -8115,7 +8168,7 @@ msgstr ""
"<https://pypi.org/project/virtualenv/>`_ para crear entornos de Python "
"aislados."
#: ../../content/administration/on_premise/source.rst:312
#: ../../content/administration/on_premise/source.rst:316
msgid ""
"Navigate to the path of the Odoo Community installation "
"(:file:`CommunityPath`) and run **pip** on the requirements file to install "
@@ -8125,7 +8178,7 @@ msgstr ""
"(:file:`CommunityPath`) y ejecute **pip** en el archivo de requerimientos "
"para instalar los requerimientos para el usuario actual"
#: ../../content/administration/on_premise/source.rst:322
#: ../../content/administration/on_premise/source.rst:326
msgid ""
"Before installing the dependencies, download and install the `Build Tools "
"for Visual Studio <https://visualstudio.microsoft.com/downloads/>`_. Select "
@@ -8137,8 +8190,8 @@ msgstr ""
"seleccione **herramientas de creación C++** en la pestaña de **Carga de "
"trabajo** e instálelo."
#: ../../content/administration/on_premise/source.rst:326
#: ../../content/administration/on_premise/source.rst:345
#: ../../content/administration/on_premise/source.rst:330
#: ../../content/administration/on_premise/source.rst:349
msgid ""
"Odoo dependencies are listed in the `requirements.txt` file located at the "
"root of the Odoo Community directory."
@@ -8146,7 +8199,7 @@ msgstr ""
"Las dependencias de Odoo están enlistadas en el archivo `requirements.txt` "
"que se encuentra en el directorio raíz de la versión Community de Odoo."
#: ../../content/administration/on_premise/source.rst:334
#: ../../content/administration/on_premise/source.rst:338
msgid ""
"Navigate to the path of the Odoo Community installation (`CommunityPath`) "
"and run **pip** on the requirements file in a terminal **with Administrator "
@@ -8156,7 +8209,7 @@ msgstr ""
"ejecute **pip** en el campo de requisitos en una terminal **con privilegios "
"de administrador**:"
#: ../../content/administration/on_premise/source.rst:353
#: ../../content/administration/on_premise/source.rst:357
msgid ""
"Navigate to the path of the Odoo Community installation (`CommunityPath`) "
"and run **pip** on the requirements file:"
@@ -8164,7 +8217,7 @@ msgstr ""
"Vaya a la ruta de su instalación de Odoo Community (`CommunityPath`) y "
"ejecute **pip** en el archivo de requisitos:"
#: ../../content/administration/on_premise/source.rst:363
#: ../../content/administration/on_premise/source.rst:367
msgid ""
"Non-Python dependencies must be installed with a package manager (`Homebrew "
"<https://brew.sh/>`_, `MacPorts <https://www.macports.org>`_)."
@@ -8173,17 +8226,17 @@ msgstr ""
" de paquetes (`Homebrew <https://brew.sh/>`_, `MacPorts "
"<https://www.macports.org>`_)."
#: ../../content/administration/on_premise/source.rst:366
#: ../../content/administration/on_premise/source.rst:370
msgid "Download and install the **Command Line Tools**:"
msgstr "Descargue e instale las **Herramientas de líneas de comando**:"
#: ../../content/administration/on_premise/source.rst:372
#: ../../content/administration/on_premise/source.rst:376
msgid "Use the package manager to install non-Python dependencies."
msgstr ""
"Use el administrador de paquetes para instalar dependencias que no sean de "
"Python."
#: ../../content/administration/on_premise/source.rst:375
#: ../../content/administration/on_premise/source.rst:379
msgid ""
"For languages using a **right-to-left interface** (such as Arabic or "
"Hebrew), the `rtlcss` package is required."
@@ -8191,22 +8244,22 @@ msgstr ""
"Para idiomas que funcionan con una interfaz de **izquierda a derecha** (como"
" las interfaces de árabe y hebreo) se necesita el paquete `rtlcss`:"
#: ../../content/administration/on_premise/source.rst:382
#: ../../content/administration/on_premise/source.rst:386
msgid "Download and install **nodejs** and **npm** with a package manager."
msgstr ""
"Descargue e instale **nodejs** y **npm** con su administrador de paquetes."
#: ../../content/administration/on_premise/source.rst:383
#: ../../content/administration/on_premise/source.rst:392
#: ../../content/administration/on_premise/source.rst:405
#: ../../content/administration/on_premise/source.rst:387
#: ../../content/administration/on_premise/source.rst:396
#: ../../content/administration/on_premise/source.rst:409
msgid "Install `rtlcss`:"
msgstr "Instale `rtlcss`:"
#: ../../content/administration/on_premise/source.rst:391
#: ../../content/administration/on_premise/source.rst:395
msgid "Download and install `nodejs <https://nodejs.org/en/download>`_."
msgstr "Descargue e instale `nodejs <https://nodejs.org/en/download/>`_."
#: ../../content/administration/on_premise/source.rst:398
#: ../../content/administration/on_premise/source.rst:402
msgid ""
"Edit the system environment's variable `PATH` to add the folder where "
"`rtlcss.cmd` is located (typically: "
@@ -8216,7 +8269,7 @@ msgstr ""
"donde se encuentre `rtlcss.cmd` (usualmente: "
"file:`C:\\\\Users\\\\<user>\\\\AppData\\\\Roaming\\\\npm\\\\`)."
#: ../../content/administration/on_premise/source.rst:403
#: ../../content/administration/on_premise/source.rst:407
msgid ""
"Download and install **nodejs** with a package manager (`Homebrew "
"<https://brew.sh/>`_, `MacPorts <https://www.macports.org>`_)."
@@ -8224,11 +8277,11 @@ msgstr ""
"Descargue e instale **nodejs** con un administrador de paquetes (`Homebrew "
"<https://brew.sh/>`_, `MacPorts <https://www.macports.org>`_)."
#: ../../content/administration/on_premise/source.rst:420
#: ../../content/administration/on_premise/source.rst:424
msgid "Running Odoo"
msgstr "Ejecutar Odoo"
#: ../../content/administration/on_premise/source.rst:422
#: ../../content/administration/on_premise/source.rst:426
msgid ""
"Once all dependencies are set up, Odoo can be launched by running `odoo-"
"bin`, the command-line interface of the server. It is located at the root of"
@@ -8238,7 +8291,7 @@ msgstr ""
"ejecutando `odoo-bin`, la interfaz de la línea de comando del servidor. Se "
"encuentra en la raíz del directorio de Odoo Community."
#: ../../content/administration/on_premise/source.rst:425
#: ../../content/administration/on_premise/source.rst:429
msgid ""
"To configure the server, either specify :ref:`command-line arguments "
"<reference/cmdline/server>` or a :ref:`configuration file "
@@ -8248,7 +8301,7 @@ msgstr ""
" de comando <reference/cmdline/server>` o un :ref:`archivo de configuración "
"<reference/cmdline/config>`."
#: ../../content/administration/on_premise/source.rst:429
#: ../../content/administration/on_premise/source.rst:433
msgid ""
"For the Enterprise edition, add the path to the `enterprise` add-ons to the "
"`addons-path` argument. Note that it must come before the other paths in "
@@ -8259,26 +8312,26 @@ msgstr ""
"antes que otras rutas en `addons-path` para que los complementos se carguen "
"correctamente."
#: ../../content/administration/on_premise/source.rst:433
#: ../../content/administration/on_premise/source.rst:437
msgid "Common necessary configurations are:"
msgstr "Estas son las configuraciones necesarias más comunes:"
#: ../../content/administration/on_premise/source.rst:435
#: ../../content/administration/on_premise/source.rst:439
msgid "PostgreSQL user and password."
msgstr "Usuario y contraseña de PostgreSQL"
#: ../../content/administration/on_premise/source.rst:436
#: ../../content/administration/on_premise/source.rst:440
msgid "Custom addon paths beyond the defaults to load custom modules."
msgstr ""
"Rutas personalizadas para complementos adicionales que sirvan para cargar "
"los módulos personalizados."
#: ../../content/administration/on_premise/source.rst:438
#: ../../content/administration/on_premise/source.rst:442
msgid "A typical way to run the server would be:"
msgstr "Una forma típica de ejecutar el servidor sería:"
#: ../../content/administration/on_premise/source.rst:449
#: ../../content/administration/on_premise/source.rst:470
#: ../../content/administration/on_premise/source.rst:453
#: ../../content/administration/on_premise/source.rst:474
msgid ""
"Where `CommunityPath` is the path of the Odoo Community installation, and "
"`mydb` is the name of the PostgreSQL database."
@@ -8286,7 +8339,7 @@ msgstr ""
"Donde `CommunityPath` es la ruta de la instalación de Odoo Community y "
"`mydb` es la base de datos de PostgreSQL."
#: ../../content/administration/on_premise/source.rst:459
#: ../../content/administration/on_premise/source.rst:463
msgid ""
"Where `CommunityPath` is the path of the Odoo Community installation, "
"`dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password, "
@@ -8296,7 +8349,7 @@ msgstr ""
"`dbuser` es el inicio de sesión de PostgreSQL, `dbpassword` es la contraseña"
" de PostgreSQL y `mydb` es la base de datos de PostgreSQL."
#: ../../content/administration/on_premise/source.rst:473
#: ../../content/administration/on_premise/source.rst:477
msgid ""
"After the server has started (the INFO log `odoo.modules.loading: Modules "
"loaded.` is printed), open http://localhost:8069 in a web browser and log "
@@ -8309,7 +8362,7 @@ msgstr ""
"administrador base: utilice `admin` como correo electrónico y, de nuevo, "
"`admin` como contraseña."
#: ../../content/administration/on_premise/source.rst:478
#: ../../content/administration/on_premise/source.rst:482
msgid ""
"From there, create and manage new :doc:`users "
"<../../applications/general/users>`."
@@ -8317,7 +8370,7 @@ msgstr ""
"Ahí podrá crear y gestionar nuevos :doc:`usuarios "
"<../../applications/general/users>`."
#: ../../content/administration/on_premise/source.rst:479
#: ../../content/administration/on_premise/source.rst:483
msgid ""
"The user account used to log into Odoo's web interface differs from the "
":option:`--db_user <odoo-bin -r>` CLI argument."
@@ -8325,7 +8378,7 @@ msgstr ""
"La cuenta de usuario que usa para iniciar sesión en la interfaz del sitio "
"web de Odoo es diferente al argumento CLI :option:`--db_user <odoo-bin -r>`."
#: ../../content/administration/on_premise/source.rst:483
#: ../../content/administration/on_premise/source.rst:487
msgid ""
":doc:`The list of CLI arguments for odoo-bin </developer/reference/cli>`"
msgstr ""
@@ -8738,196 +8791,133 @@ msgid "End of support"
msgstr "Fin del soporte"
#: ../../content/administration/supported_versions.rst:34
msgid "Odoo saas~17.2"
msgstr "Odoo saas~17.2"
msgid "Odoo saas~17.4"
msgstr "Odoo saas~17.4"
#: ../../content/administration/supported_versions.rst:36
#: ../../content/administration/supported_versions.rst:37
#: ../../content/administration/supported_versions.rst:42
#: ../../content/administration/supported_versions.rst:43
#: ../../content/administration/supported_versions.rst:54
#: ../../content/administration/supported_versions.rst:55
#: ../../content/administration/supported_versions.rst:60
#: ../../content/administration/supported_versions.rst:61
#: ../../content/administration/supported_versions.rst:66
#: ../../content/administration/supported_versions.rst:67
#: ../../content/administration/supported_versions.rst:72
#: ../../content/administration/supported_versions.rst:73
#: ../../content/administration/supported_versions.rst:84
#: ../../content/administration/supported_versions.rst:85
#: ../../content/administration/supported_versions.rst:90
#: ../../content/administration/supported_versions.rst:91
#: ../../content/administration/supported_versions.rst:48
#: ../../content/administration/supported_versions.rst:49
msgid "N/A"
msgstr "N/A"
#: ../../content/administration/supported_versions.rst:38
msgid "July 2024"
msgstr "Julio de 2024"
#: ../../content/administration/supported_versions.rst:40
msgid "Odoo saas~17.2"
msgstr "Odoo saas~17.2"
#: ../../content/administration/supported_versions.rst:44
msgid "April 2024"
msgstr "Abril de 2024"
#: ../../content/administration/supported_versions.rst:40
#: ../../content/administration/supported_versions.rst:46
msgid "Odoo saas~17.1"
msgstr "Odoo saas~17.1"
#: ../../content/administration/supported_versions.rst:44
#: ../../content/administration/supported_versions.rst:50
msgid "January 2024"
msgstr "Enero de 2024"
#: ../../content/administration/supported_versions.rst:46
#: ../../content/administration/supported_versions.rst:52
msgid "**Odoo 17.0**"
msgstr "**Odoo 17.0**"
#: ../../content/administration/supported_versions.rst:50
#: ../../content/administration/supported_versions.rst:105
#: ../../content/administration/supported_versions.rst:56
#: ../../content/administration/supported_versions.rst:75
msgid "November 2023"
msgstr "Noviembre de 2023"
#: ../../content/administration/supported_versions.rst:51
#: ../../content/administration/supported_versions.rst:57
msgid "October 2026 (planned)"
msgstr "Octubre de 2026 (planeado)"
#: ../../content/administration/supported_versions.rst:52
msgid "Odoo saas~16.4"
msgstr "Odoo saas~16.4"
#: ../../content/administration/supported_versions.rst:56
msgid "August 2023"
msgstr "Agosto de 2023"
#: ../../content/administration/supported_versions.rst:58
msgid "Odoo saas~16.3"
msgstr "Odoo saas~16.3"
#: ../../content/administration/supported_versions.rst:59
#: ../../content/administration/supported_versions.rst:65
#: ../../content/administration/supported_versions.rst:71
#: ../../content/administration/supported_versions.rst:83
#: ../../content/administration/supported_versions.rst:89
#: ../../content/administration/supported_versions.rst:101
#: ../../content/administration/supported_versions.rst:102
#: ../../content/administration/supported_versions.rst:103
#: ../../content/administration/supported_versions.rst:107
#: ../../content/administration/supported_versions.rst:108
#: ../../content/administration/supported_versions.rst:109
#: ../../content/administration/supported_versions.rst:113
#: ../../content/administration/supported_versions.rst:114
#: ../../content/administration/supported_versions.rst:115
msgid "|red|"
msgstr "|red|"
#: ../../content/administration/supported_versions.rst:62
msgid "June 2023"
msgstr "Junio de 2023"
#: ../../content/administration/supported_versions.rst:64
msgid "Odoo saas~16.2"
msgstr "Odoo saas~16.2"
#: ../../content/administration/supported_versions.rst:68
msgid "March 2023"
msgstr "Marzo de 2023"
#: ../../content/administration/supported_versions.rst:70
msgid "Odoo saas~16.1"
msgstr "Odoo saas~16.1"
#: ../../content/administration/supported_versions.rst:74
msgid "February 2023"
msgstr "Febrero de 2023"
#: ../../content/administration/supported_versions.rst:76
msgid "**Odoo 16.0**"
msgstr "**Odoo 16.0**"
#: ../../content/administration/supported_versions.rst:80
#: ../../content/administration/supported_versions.rst:111
#: ../../content/administration/supported_versions.rst:62
#: ../../content/administration/supported_versions.rst:81
msgid "October 2022"
msgstr "Octubre de 2022"
#: ../../content/administration/supported_versions.rst:81
#: ../../content/administration/supported_versions.rst:63
msgid "November 2025 (planned)"
msgstr "Noviembre de 2025 (planeado)"
#: ../../content/administration/supported_versions.rst:82
msgid "Odoo saas~15.2"
msgstr "Odoo saas~15.2"
#: ../../content/administration/supported_versions.rst:86
msgid "March 2022"
msgstr "Marzo de 2022"
#: ../../content/administration/supported_versions.rst:87
msgid "January 2023"
msgstr "Enero de 2023"
#: ../../content/administration/supported_versions.rst:88
msgid "Odoo saas~15.1"
msgstr "Odoo saas~15.1"
#: ../../content/administration/supported_versions.rst:92
msgid "February 2022"
msgstr "Febrero de 2022"
#: ../../content/administration/supported_versions.rst:93
msgid "July 2022"
msgstr "Julio de 2022"
#: ../../content/administration/supported_versions.rst:94
#: ../../content/administration/supported_versions.rst:64
msgid "**Odoo 15.0**"
msgstr "**Odoo 15.0**"
#: ../../content/administration/supported_versions.rst:98
#: ../../content/administration/supported_versions.rst:68
msgid "October 2021"
msgstr "Octubre de 2021"
#: ../../content/administration/supported_versions.rst:99
#: ../../content/administration/supported_versions.rst:69
msgid "November 2024 (planned)"
msgstr "Noviembre de 2024 (planeado)"
#: ../../content/administration/supported_versions.rst:100
#: ../../content/administration/supported_versions.rst:70
msgid "**Odoo 14.0**"
msgstr "**Odoo 14.0**"
#: ../../content/administration/supported_versions.rst:104
#: ../../content/administration/supported_versions.rst:71
#: ../../content/administration/supported_versions.rst:72
#: ../../content/administration/supported_versions.rst:73
#: ../../content/administration/supported_versions.rst:77
#: ../../content/administration/supported_versions.rst:78
#: ../../content/administration/supported_versions.rst:79
#: ../../content/administration/supported_versions.rst:83
#: ../../content/administration/supported_versions.rst:84
#: ../../content/administration/supported_versions.rst:85
msgid "|red|"
msgstr "|red|"
#: ../../content/administration/supported_versions.rst:74
msgid "October 2020"
msgstr "Octubre de 2020"
#: ../../content/administration/supported_versions.rst:106
#: ../../content/administration/supported_versions.rst:76
msgid "**Odoo 13.0**"
msgstr "**Odoo 13.0**"
#: ../../content/administration/supported_versions.rst:110
#: ../../content/administration/supported_versions.rst:80
msgid "October 2019"
msgstr "Octubre de 2019"
#: ../../content/administration/supported_versions.rst:112
#: ../../content/administration/supported_versions.rst:82
msgid "Older versions"
msgstr "Versiones anteriores"
#: ../../content/administration/supported_versions.rst:116
#: ../../content/administration/supported_versions.rst:86
msgid "Before 2019"
msgstr "Anterior a 2019"
#: ../../content/administration/supported_versions.rst:117
#: ../../content/administration/supported_versions.rst:87
msgid "Before 2022"
msgstr "Anterior a 2022"
#: ../../content/administration/supported_versions.rst:119
#: ../../content/administration/supported_versions.rst:89
msgid "Legend"
msgstr "Leyenda"
#: ../../content/administration/supported_versions.rst:121
#: ../../content/administration/supported_versions.rst:91
msgid "|green| Supported version"
msgstr "|green| Versión con soporte"
#: ../../content/administration/supported_versions.rst:123
#: ../../content/administration/supported_versions.rst:93
msgid "|red| End-of-support"
msgstr "|red| Fin del soporte"
#: ../../content/administration/supported_versions.rst:125
#: ../../content/administration/supported_versions.rst:95
msgid "N/A Never released for this platform"
msgstr "N/A Nunca hubo para esta plataforma"
#: ../../content/administration/supported_versions.rst:128
#: ../../content/administration/supported_versions.rst:98
msgid ""
"Even though we don't support older versions, you can always `upgrade from "
"any version <https://upgrade.odoo.com/>`_."
@@ -9234,7 +9224,7 @@ msgid ""
"`upgrade platform <https://upgrade.odoo.com>`_."
msgstr ""
"El **respaldo automático diario más reciente de producción** se envía a la "
"`plataforma de actualización <https://www.upgrade.odoo.com>`_."
"`plataforma de actualización <https://upgrade.odoo.com>`_."
#: ../../content/administration/upgrade.rst:130
msgid ""
@@ -9649,18 +9639,13 @@ msgstr "Actualizar la base de datos de producción"
msgid ""
"Once the :ref:`tests <upgrade/test_your_db>` are completed and you are "
"confident that the upgraded database can be used as your main database "
"without any issues, it is time to plan the go-live day. It can be planned in"
" coordination with Odoo's upgrade support analysts, reachable via the "
"`support page <https://odoo.com/help>`__."
"without any issues, it is time to plan the go-live day."
msgstr ""
"Una vez que terminó de realizar las :ref:`pruebas <upgrade/test_your_db>` y "
"está seguro de que puede utilizar la base de datos actualizada como su base "
"de datos principal sin ningún problema, es momento de planificar las "
"acciones que llevará a cabo el día de la activación. Puede planificarlas en "
"colaboración con los analistas de soporte de actualización de Odoo, "
"contáctelos a través de la `página de soporte <https://odoo.com/help>`__."
"Una vez que se completen las :ref:`pruebas <upgrade/test_your_db>` y confíe "
"que la base de datos actualizada se puede usar como su base de datos "
"principal sin problema, es hora de planear el día del lanzamiento."
#: ../../content/administration/upgrade.rst:287
#: ../../content/administration/upgrade.rst:285
msgid ""
"Your production database will be unavailable during its upgrade. Therefore, "
"we recommend planning the upgrade at a time when the use of the database is "
@@ -9670,7 +9655,7 @@ msgstr ""
"Le recomendamos que realice la actualización en un momento en que el uso de "
"la base de datos es mínimo."
#: ../../content/administration/upgrade.rst:290
#: ../../content/administration/upgrade.rst:288
msgid ""
"As the standard upgrade scripts and your database are constantly evolving, "
"it is also recommended to frequently request another upgraded test database "
@@ -9686,16 +9671,16 @@ msgstr ""
"proceso de actualización un día antes de actualizar la base de datos de "
"producción."
#: ../../content/administration/upgrade.rst:296
#: ../../content/administration/upgrade.rst:294
msgid "Going into production without first testing may lead to:"
msgstr ""
"Empezar a usar la producción sin hacer pruebas primero puede ocasionar: "
#: ../../content/administration/upgrade.rst:298
#: ../../content/administration/upgrade.rst:296
msgid "Users failing to adjust to the changes and new features"
msgstr "Que los usuarios no se ajusten a los cambios y nuevas funciones."
#: ../../content/administration/upgrade.rst:299
#: ../../content/administration/upgrade.rst:297
msgid ""
"Business interruptions (e.g., no longer having the possibility to validate "
"an action)"
@@ -9703,7 +9688,7 @@ msgstr ""
"Que haya interrupciones en las actividades empresariales (por ejemplo, ya no"
" contar con la posibilidad de validar una acción)."
#: ../../content/administration/upgrade.rst:300
#: ../../content/administration/upgrade.rst:298
msgid ""
"Poor customer experience (e.g., an eCommerce website that does not work "
"correctly)"
@@ -9711,7 +9696,7 @@ msgstr ""
"Que los clientes tengan una mala experiencia de usuario (por ejemplo, si un "
"sitio web de comercio electrónico deja de funcionar de manera adecuada)."
#: ../../content/administration/upgrade.rst:302
#: ../../content/administration/upgrade.rst:300
msgid ""
"The process of upgrading a production database is similar to upgrading a "
"test database with a few exceptions."
@@ -9719,7 +9704,7 @@ msgstr ""
"El proceso de actualización de una base de datos de producción es parecido a"
" la actualización de una base de datos de prueba salvo algunas excepciones."
#: ../../content/administration/upgrade.rst:309
#: ../../content/administration/upgrade.rst:307
msgid ""
"The process is similar to :ref:`obtaining an upgraded test database "
"<upgrade/request-test-database>`, except for the purpose option, which must "
@@ -9730,7 +9715,7 @@ msgstr ""
"de la opción relacionada al propósito, debe seleccionar "
":guilabel:`Producción` en lugar de :guilabel:`Prueba`."
#: ../../content/administration/upgrade.rst:314
#: ../../content/administration/upgrade.rst:312
msgid ""
"Once the upgrade is requested, the database will be unavailable until the "
"upgrade is finished. Once the process is completed, it is impossible to "
@@ -9740,7 +9725,7 @@ msgstr ""
" hasta que termine la actualización. Una vez que el proceso haya finalizado,"
" es imposible volver a la versión anterior."
#: ../../content/administration/upgrade.rst:320
#: ../../content/administration/upgrade.rst:318
msgid ""
"The process is similar to :ref:`obtaining an upgraded test database "
"<upgrade/request-test-database>` on the :guilabel:`Production` branch."
@@ -9753,7 +9738,7 @@ msgstr ""
msgid "View from the upgrade tab"
msgstr "Vista desde la pestaña de actualizar "
#: ../../content/administration/upgrade.rst:326
#: ../../content/administration/upgrade.rst:324
msgid ""
"The process is **triggered as soon as a new commit is made** on the branch. "
"This allows the upgrade process to be synchronized with the deployment of "
@@ -9766,7 +9751,7 @@ msgstr ""
"Si no hay módulos personalizados, el proceso de actualización se activa de "
"inmediato."
#: ../../content/administration/upgrade.rst:332
#: ../../content/administration/upgrade.rst:330
msgid ""
"The database is unavailable throughout the process. If anything goes wrong, "
"the platform automatically reverts the upgrade, as it would be for a regular"
@@ -9779,7 +9764,7 @@ msgstr ""
"exitoso, se crea una copia de seguridad de la base de datos antes de la "
"actualización."
#: ../../content/administration/upgrade.rst:336
#: ../../content/administration/upgrade.rst:334
msgid ""
"The update of your custom modules must be successful to complete the entire "
"upgrade process. Make sure the status of your staging upgrade is "
@@ -9790,7 +9775,7 @@ msgstr ""
"actualización de prueba sea :guilabel:`éxitosa` antes de intentarlo en la "
"producción. "
#: ../../content/administration/upgrade.rst:344
#: ../../content/administration/upgrade.rst:342
msgid ""
"The command to upgrade a database to production is similar to the one of "
"upgrading a test database except for the argument `test`, which must be "
@@ -9800,7 +9785,7 @@ msgstr ""
"comando para actualizar una base de prueba, solo debe reemplazar el "
"argumento `test` por `production`:"
#: ../../content/administration/upgrade.rst:351
#: ../../content/administration/upgrade.rst:349
msgid ""
"An upgraded production database can also be requested via the `Upgrade page "
"<https://upgrade.odoo.com/>`_. Once the database is uploaded, any "
@@ -9815,7 +9800,7 @@ msgstr ""
"actualizada. Por este motivo le recomendamos que no la use durante el "
"proceso de actualización."
#: ../../content/administration/upgrade.rst:358
#: ../../content/administration/upgrade.rst:356
msgid ""
"When requesting an upgraded database for production purposes, the copy is "
"submitted without a filestore. Therefore, the upgraded database filestore "
@@ -9827,7 +9812,7 @@ msgstr ""
"almacenados de la base de datos actualizada deben fusionarse con los que "
"corresponden a producción antes de implementar la nueva versión."
#: ../../content/administration/upgrade.rst:362
#: ../../content/administration/upgrade.rst:360
msgid ""
"In case of an issue with your production database, you can request the "
"assistance of Odoo via the `support page "
@@ -9839,11 +9824,11 @@ msgstr ""
"<https://odoo.com/help?stage=post_upgrade>`__, solo debe seleccionar la "
"opción relacionada con la actualización en producción."
#: ../../content/administration/upgrade.rst:370
#: ../../content/administration/upgrade.rst:368
msgid "Service-level agreement (SLA)"
msgstr "Acuerdo de nivel de servicio (SLA, por sus siglas en inglés) "
#: ../../content/administration/upgrade.rst:372
#: ../../content/administration/upgrade.rst:370
msgid ""
"With Odoo Enterprise, upgrading a database to the most recent version of "
"Odoo is **free**, including any support required to rectify potential "
@@ -9853,7 +9838,7 @@ msgstr ""
"es **gratis** e incluye cualquier tipo de soporte requerido para rectificar "
"posibles discrepancias en la base de datos actualizada. "
#: ../../content/administration/upgrade.rst:375
#: ../../content/administration/upgrade.rst:373
msgid ""
"Information about the upgrade services included in the Enterprise Licence is"
" available in the :ref:`Odoo Enterprise Subscription Agreement <upgrade>`. "
@@ -9864,11 +9849,11 @@ msgstr ""
"Enterprise <upgrade>`. Sin embargo, esta sección aclara qué servicios de "
"actualización puede esperar."
#: ../../content/administration/upgrade.rst:380
#: ../../content/administration/upgrade.rst:378
msgid "Upgrade services covered by the SLA"
msgstr "Servicios de actualización que cubre el SLA "
#: ../../content/administration/upgrade.rst:382
#: ../../content/administration/upgrade.rst:380
msgid ""
"Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or "
"self-hosted (On-Premise) can benefit from upgrade services at all times for:"
@@ -9877,11 +9862,11 @@ msgstr ""
"línea y Odoo.sh) o que se alojan a si mismas (Local) se pueden beneficiar de"
" los servicios de actualización en todo momento para: "
#: ../../content/administration/upgrade.rst:385
#: ../../content/administration/upgrade.rst:383
msgid "the upgrade of all **standard applications**;"
msgstr "actualizar todas las **aplicaciones estándar**;"
#: ../../content/administration/upgrade.rst:386
#: ../../content/administration/upgrade.rst:384
msgid ""
"the upgrade of all **customizations created with the Studio app**, as long "
"as Studio is still installed and the respective subscription is still "
@@ -9891,7 +9876,7 @@ msgstr ""
" siempre y cuando Studio siga instalado y la suscripción correspondiente "
"siga activa; y "
#: ../../content/administration/upgrade.rst:388
#: ../../content/administration/upgrade.rst:386
msgid ""
"the upgrade of all **developments and customizations covered by a "
"maintenance of customizations subscription**."
@@ -9899,7 +9884,7 @@ msgstr ""
"actualizar todos los **desarrollos y personalizaciones que cubre una "
"suscripción de mantenimiento para las personalizaciones**. "
#: ../../content/administration/upgrade.rst:391
#: ../../content/administration/upgrade.rst:389
msgid ""
"Upgrade services are limited to the technical conversion and adaptation of a"
" database (standard modules and data) to make it compatible with the version"
@@ -9909,23 +9894,23 @@ msgstr ""
"adaptación de una base de datos (módulos estándar y datos) para hacerlos "
"compatibles con la versión objetivo de la actualización. "
#: ../../content/administration/upgrade.rst:395
#: ../../content/administration/upgrade.rst:393
msgid "Upgrade services not covered by the SLA"
msgstr "Servicios de actualización que no cubre el SLA"
#: ../../content/administration/upgrade.rst:397
#: ../../content/administration/upgrade.rst:395
msgid "The following upgrade-related services are **not** included:"
msgstr ""
"Los siguientes servicios relacionados con la actualización **no** incluyen: "
#: ../../content/administration/upgrade.rst:399
#: ../../content/administration/upgrade.rst:397
msgid ""
"the **cleaning** of pre-existing data and configurations while upgrading;"
msgstr ""
"la **limpieza** de datos y configuraciones pre-existentes al momento de "
"actualizar; "
#: ../../content/administration/upgrade.rst:400
#: ../../content/administration/upgrade.rst:398
msgid ""
"the upgrade of **custom modules created in-house or by third parties**, "
"including Odoo partners;"
@@ -9933,7 +9918,7 @@ msgstr ""
"la actualización de **módulos personalizados creados internamente o por "
"externos**, incluyendo partners de Odoo; "
#: ../../content/administration/upgrade.rst:401
#: ../../content/administration/upgrade.rst:399
msgid ""
"lines of **code added to standard modules**, i.e., customizations created "
"outside the Studio app, code entered manually, and :ref:`automated actions "
@@ -9944,16 +9929,16 @@ msgstr ""
"manualmente y :ref:`acciones automatizadas usando código Python "
"<studio/automated-actions/action>`; y"
#: ../../content/administration/upgrade.rst:404
#: ../../content/administration/upgrade.rst:402
msgid "**training** on using the upgraded version's features and workflows."
msgstr ""
"**capacitación** para usar las funciones de la versión actualizada y flujos "
"de trabajo. "
#: ../../content/administration/upgrade.rst:407
#: ../../content/administration/upgrade.rst:405
msgid ":doc:`Odoo.sh documentation <odoo_sh>`"
msgstr ":doc:`documentación de Odoo.sh <odoo_sh>`"
#: ../../content/administration/upgrade.rst:408
#: ../../content/administration/upgrade.rst:406
msgid ":doc:`Supported Odoo versions <supported_versions>`"
msgstr ":doc:`Versiones compatibles de Odoo <supported_versions>`"
+268 -102
View File
@@ -7,11 +7,11 @@
# Josep Anton Belchi, 2024
# Braulio D. López Vázquez <bdl@odoo.com>, 2024
# Pablo Rojas <rojaspablo88@gmail.com>, 2024
# Patricia Gutiérrez Capetillo <pagc@odoo.com>, 2024
# Wil Odoo, 2024
# Fernanda Alvarez, 2024
# Iran Villalobos López, 2024
# Lucia Pacheco, 2024
# Patricia Gutiérrez Capetillo <pagc@odoo.com>, 2024
# Fernanda Alvarez, 2024
#
#, fuzzy
msgid ""
@@ -20,7 +20,7 @@ msgstr ""
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-05-28 08:57+0000\n"
"PO-Revision-Date: 2024-04-04 12:26+0000\n"
"Last-Translator: Lucia Pacheco, 2024\n"
"Last-Translator: Fernanda Alvarez, 2024\n"
"Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -213,11 +213,10 @@ msgid ""
"has an activity scheduled, the clock icon may be replaced by a :guilabel:`📞 "
"(phone)` or an :guilabel:`✉️ (envelope)` icon."
msgstr ""
"Seleccione el registro donde se planeará la actividad. Haga clic en el icono"
" :guilabel:`🕘 (reloj)` y luego en :guilabel:`Planear una actividad`. Si el "
"registro ya tiene una actividad planeada, es posible que, en lugar del el "
"icono del reloj, aparezca el icono de guilabel:`📞 (teléfono)` o de "
":guilabel:`✉️ (sobre)`."
"Seleccione el registro en el que planeará la actividad. Haga clic en el "
"icono :guilabel:`🕘 (reloj)` y luego en :guilabel:`Programar una actividad`. "
"Si el registro ya tiene una actividad planeada, es probable que aparezca el "
"icono :guilabel:`📞 (teléfono)` o :guilabel:`✉️ (sobre)` en lugar del reloj."
#: ../../content/applications/essentials/activities.rst:0
msgid "List view of the CRM pipeline and the option to schedule an activity."
@@ -485,8 +484,8 @@ msgid ""
"be altered before the activity is scheduled or saved."
msgstr ""
"La información en los campos :guilabel:`Usuario predeterminado` y "
":guilabel:`Resumen predeterminado` se incluye en la actividad creada. Sin "
"embargo, se pueden alterar antes de que la actividad se programe o se "
":guilabel:`Resumen predeterminado` se incluye en la actividad creada, pero "
"puede alterar estos campos antes de que la actividad se programe o se "
"guarde."
#: ../../content/applications/essentials/activities.rst:181
@@ -629,10 +628,14 @@ msgid ""
"contact is a repository of vital business information, facilitating "
"communication and business transactions."
msgstr ""
"La aplicación *Contactos* está instalada de forma predeterminada en todas "
"las bases de datos de Odoo. Los contactos se crean para clientes con los que"
" trabaja con Odoo. Un contacto es un repositorio de información empresarial "
"vital con la que facilita la comunicación y las transacciones empresariales."
#: ../../content/applications/essentials/contacts.rst:10
msgid "Contact form"
msgstr ""
msgstr "Formulario de contacto"
#: ../../content/applications/essentials/contacts.rst:12
msgid ""
@@ -640,10 +643,13 @@ msgid ""
"click :guilabel:`Create`. A new form appears where various contact "
"information can be added."
msgstr ""
"Para crear un nuevo contacto vaya a :menuselection:`la aplicación Contactos`"
" y haga clic en :guilabel:`Crear`. Aparecerá un nuevo formulario donde podrá"
" agregar información de contacto."
#: ../../content/applications/essentials/contacts.rst:16
msgid "Contact type"
msgstr ""
msgstr "Tipo de contacto"
#: ../../content/applications/essentials/contacts.rst:18
msgid ""
@@ -651,6 +657,9 @@ msgid ""
"contacts. Select either :guilabel:`Individual` or :guilabel:`Company`, "
"depending on the type of contact that is being added."
msgstr ""
"Odoo es compatible con contactos :guilabel:`individuales` y de "
":guilabel:`empresa`. Seleccione ya sea :guilabel:`individual` o "
":guilabel:`empresa`, dependiendo del tipo de contacto que está agregando."
#: ../../content/applications/essentials/contacts.rst:22
msgid "Name"
@@ -662,6 +671,9 @@ msgid ""
":guilabel:`Company`. This is how the name appears throughout the database. "
"This field is **mandatory**."
msgstr ""
"Primero escriba el nombre de :guilabel:`la persona` o :guilabel:`la "
"empresa`, que será como verá el nombre en toda la base de datos. Este es un "
"campo *obligatorio*."
#: ../../content/applications/essentials/contacts.rst:28
msgid ""
@@ -669,6 +681,9 @@ msgid ""
"linked to it. After selecting :guilabel:`Individual`, a new "
":guilabel:`Company Name...` field appears below the first name field."
msgstr ""
"Puede vincular una :guilabel:`empresa` a un contacto :guilabel:`individual`."
" Después de seleccionar :guilabel:`Individual` aparecerá un nuevo campo "
":guilabel:`Nombre de la empresa...` debajo del campo de nombre."
#: ../../content/applications/essentials/contacts.rst:33
msgid "Address"
@@ -679,6 +694,8 @@ msgid ""
"Next, enter the :guilabel:`Address` of the :guilabel:`Company` or "
":guilabel:`Individual`."
msgstr ""
"Después, ingrese la :guilabel:`dirección` de la :guilabel:`empresa` o "
":guilabel:`individual`."
#: ../../content/applications/essentials/contacts.rst:38
msgid ""
@@ -688,32 +705,43 @@ msgid ""
":guilabel:`Delivery Address`, :guilabel:`Other Address`, and "
":guilabel:`Private Address`."
msgstr ""
"Si selecciona la opción :guilabel:`Individual`, puede seleccionar el *tipo "
"de dirección* desde un menú desplegable con las opciones: "
":guilabel:`Contacto`, :guilabel:`Dirección de facturación`, "
":guilabel:`Dirección de entrega`, :guilabel:`Otras direcciones` y "
":guilabel:`Direcciones privadas`."
#: ../../content/applications/essentials/contacts.rst:44
msgid "Additional fields"
msgstr ""
msgstr "Campos adicionales"
#: ../../content/applications/essentials/contacts.rst:46
msgid ""
"Additional details are included on the initial form. The following fields "
"are available:"
msgstr ""
"Detalles adicionales incluidos en el formulario inicial, los campos "
"disponibles son:"
#: ../../content/applications/essentials/contacts.rst:48
msgid ":guilabel:`VAT`: Value Added Tax number."
msgstr ""
msgstr ":guilabel:`RFC`: RFC, CUIT, NIT, RUT, TIN, RUC, CIF, NIF, etc."
#: ../../content/applications/essentials/contacts.rst:49
msgid ""
":guilabel:`Citizen Identification`: citizen or government identification "
"number (only available on :guilabel:`Individual`)."
msgstr ""
":guilabel:`Citizen Identification`: número de identificación del gobierno "
"(solo disponible en :guilabel:`Individual`)."
#: ../../content/applications/essentials/contacts.rst:51
msgid ""
":guilabel:`Job Position`: list the job position of the "
":guilabel:`Individual` (only available on :guilabel:`Individual`)."
msgstr ""
":guilabel:`Puesto de trabajo`: el puesto de trabajo del "
":guilabel:`Individual` (solo disponible en :guilabel:`Individual`)."
#: ../../content/applications/essentials/contacts.rst:53
msgid ""
@@ -721,6 +749,10 @@ msgid ""
"an SMS, or WhatsApp message by hovering over the field on the saved form, "
"and clicking the desired option."
msgstr ""
":guilabel:`Teléfono`: número telefónico (con cualquier código de país). "
"Realice llamadas, envíe mensajes de texto o de WhatsApp solo pasando el "
"cursos por encima del campo en el formulario guardado y haga clic en la "
"opción deseada."
#: ../../content/applications/essentials/contacts.rst:55
msgid ""
@@ -728,16 +760,24 @@ msgid ""
"call, send an SMS, or WhatsApp message by hovering over the field on the "
"saved form, and clicking on the desired option."
msgstr ""
":guilabel:`Teléfono celular`: número de teléfono móvil (con cualquier código"
" de país). Realice llamadas, envíe mensajes de texto o de WhatsApp solo "
"pasando el cursos por encima del campo en el formulario guardado y haga clic"
" en la opción deseada."
#: ../../content/applications/essentials/contacts.rst:57
msgid ":guilabel:`Email`: enter the email address with the domain."
msgstr ""
":guilabel:`Correo electrónico`: ingrese el correo electrónico con el "
"dominio."
#: ../../content/applications/essentials/contacts.rst:58
msgid ""
":guilabel:`Website`: enter the full website address, starting with `http` or"
" `https`."
msgstr ""
":guilabel:`Sitio web`: escriba la dirección del sitio web completa, "
"empezando por `http` o `https`."
#: ../../content/applications/essentials/contacts.rst:59
msgid ""
@@ -745,6 +785,9 @@ msgid ""
":guilabel:`Miss`, :guilabel:`Mister`, :guilabel:`Professor`, or create a new"
" one directly from this field."
msgstr ""
":guilabel:`Título`: seleccione :guilabel:`Doctor`, :guilabel:`Sra.`, "
":guilabel:`Srita.`, :guilabel:`Sr.`, :guilabel:`Profesor`, o cree un título "
"nuevo directamente desde este campo."
#: ../../content/applications/essentials/contacts.rst:61
msgid ""
@@ -753,6 +796,10 @@ msgid ""
"the new tag in the field, and click :guilabel:`Create` from the resulting "
"drop-down menu."
msgstr ""
":guilabel:`Etiquetas`: escriba en el campo e ingrese las etiquetas "
"preconfiguradas, o haga clic en el menú desplegable y seleccione una. Para "
"crear una nueva escriba la nueva etiqueta en el campo y haga clic en "
":guilabel:`Crear` en el menú desplegable resultante."
#: ../../content/applications/essentials/contacts.rst:66
msgid "Contacts & Addresses tab"
@@ -765,6 +812,11 @@ msgid ""
"associated with a :guilabel:`Company` and related addresses. For example, a "
"specific contact person for the company can be listed here."
msgstr ""
"En la parte inferior del formulario de contrato hay varias pestañas. En la "
"pestaña :guilabel:`Contactos y direcciones` puede agregar contactos que "
"están asociados a la :guilabel:`Empresa` y sus direcciones relacionadas. Por"
" ejemplo, aquí puede enlistar una persona de contacto específica para la "
"empresa."
#: ../../content/applications/essentials/contacts.rst:72
msgid ""
@@ -773,6 +825,11 @@ msgid ""
":guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create "
"Contact` pop-up form, in which additional addresses can be configured."
msgstr ""
"Puede agregar varias direcciones en los contactos :guilabel:`Individual` y "
":guilabel:`Empresa`. Para hacerlo seleccione :guilabel:`Añadir`, ubicado en "
"la pestaña :guilabel:`Contactos y direcciones`. Al hacerlo, aparecerá el "
"formulario emergente :guilabel:`Crear contacto`, en el que podrá establecer "
"direcciones adicionales."
#: ../../content/applications/essentials/contacts.rst-1
msgid "Add a contact/address to the contact form."
@@ -784,6 +841,9 @@ msgid ""
" :guilabel:`Other Address` field at the top to reveal a drop-down menu of "
"address-related options."
msgstr ""
"En el formulario emergente :guilabel:`Crear contacto`, haga clic en el campo"
" predeterminado :guilabel:`Otra dirección` para ver el menú desplegable con "
"opciones relacionadas a las direcciones."
#: ../../content/applications/essentials/contacts.rst:83
msgid "Select any of the following options:"
@@ -837,12 +897,18 @@ msgid ""
"Once an option is selected, enter the corresponding contact information that"
" should be used for the specified address type."
msgstr ""
"Una vez que seleccione una opción deberá introducir la información de "
"contacto correspondiente que debe utilizarse para el tipo de dirección "
"específica."
#: ../../content/applications/essentials/contacts.rst:98
msgid ""
"Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, "
"along with the :guilabel:`Phone` and/or :guilabel:`Mobile` numbers below."
msgstr ""
"Agregue el :guilabel:`Nombre de contacto`, :guilabel:`Dirección`, "
":guilabel:`Correo electrónico` y los números de :guilabel:`teléfono` o "
":guilabel:`Celular` debajo."
#: ../../content/applications/essentials/contacts.rst:101
msgid ""
@@ -850,12 +916,17 @@ msgid ""
"address type has been selected. This is similar to the "
":guilabel:`Individual` contact."
msgstr ""
"Configure el :guilabel:`Puesto de trabajo`, que aparece si el tipo de "
"dirección de :guilabel:`Contacto` se seleccionó. Es smiliar que al contacto "
":guilabel:`Individual`."
#: ../../content/applications/essentials/contacts.rst:104
msgid ""
"To add a note, click on the text field next to :guilabel:`Notes`, and write "
"anything that is applicable to the customer or contact."
msgstr ""
"Para agregar una nota, haga clic en el cuadro de texto a un lado de "
":guilabel:`Notas` y escriba lo que sea aplicable al cliente o contacto."
#: ../../content/applications/essentials/contacts.rst:107
msgid ""
@@ -863,6 +934,10 @@ msgid ""
":guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save "
"the address, and immediately input another one."
msgstr ""
"A continuación, haga clic en :guilabel:`Guardar y cerrar` para guardar la "
"dirección y cerrar la ventana :guilabel:`Crear contacto`. O haga clic en "
":guilabel:`Guardar y nuevo` para guardar la dirección e introducir una nueva"
" inmediatamente."
#: ../../content/applications/essentials/contacts.rst:111
msgid "Sales & Purchase tab"
@@ -873,6 +948,8 @@ msgid ""
"Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the "
"*Sales*, *Purchase*, **or** *Point of Sale* applications are installed."
msgstr ""
"Sigue la pestaña :guilabel:`Ventas y compra`, que solo aparecerá si tiene "
"instaladas las aplicaciones *Ventas*, *Compra* o *Punto de venta*."
#: ../../content/applications/essentials/contacts.rst:116
msgid ""
@@ -880,6 +957,8 @@ msgid ""
"Purchases` tab. Select a :guilabel:`Fiscal Position` from the drop-down "
"menu."
msgstr ""
"Puede configurar la :guilabel:`posición fiscal` en la pestaña "
":guilabel:`Ventas y compra` tab desde el menú desplegable."
#: ../../content/applications/essentials/contacts.rst:120
msgid "Sales section"
@@ -892,6 +971,10 @@ msgid ""
"drop-down field, and select one. Create a new :guilabel:`Salesperson` by "
"typing the user's name, and making the appropriate selection."
msgstr ""
"En el encabezado :guilabel:`Ventas` puede asignar un :guilabel:`Vendedor` a "
"un contacto, solo haga clic en el menú desplegable y seleccione uno. Para "
"crear un :guilabel:`Vendedor` escriba el nombre de usuario y haga la "
"selección apropiada."
#: ../../content/applications/essentials/contacts.rst:126
msgid ""
@@ -901,16 +984,24 @@ msgid ""
"or :guilabel:`Create` a new one. Select the :guilabel:`Pricelist` drop-down "
"menu to choose the appropriate :guilabel:`Pricelist`."
msgstr ""
"Si lo necesita también puede configurar :guilabel:`Términos de pago` o "
":guilabel:`Listas de precios`. Haga clic en el menú desplegable a un lado de"
" :guilabel:`Términos de pago` y cámbielo a uno de los :guilabel:`Términos de"
" pago` preseleccionados, o :guilabel:`cree` uno nuevo. Seleccione el menú "
"desplegable de la :guilabel:`Lista de precios` para elegir una "
":guilabel:`Lista de precios` apropiada."
#: ../../content/applications/essentials/contacts.rst:131
msgid ""
"Click into the :guilabel:`Delivery Method` field to select an option from "
"the drop-down menu."
msgstr ""
"Haga clic en el campo :guilabel:`Método de entrega` para seleccionar una "
"opción desde el menú desplegable."
#: ../../content/applications/essentials/contacts.rst:134
msgid "Point Of Sale section"
msgstr ""
msgstr "Sección del punto de venta"
#: ../../content/applications/essentials/contacts.rst:136
msgid ""
@@ -918,10 +1009,14 @@ msgid ""
"that can be used to identify the contact. Use the :guilabel:`Loyalty Points`"
" field to track points the user won as part of a *Loyalty Program*."
msgstr ""
"En el encabezado :guilabel:`Punto de venta` ingrese el :guilabel:`Código de "
"barras` con el que puede identificar el contacto. Use el campo "
":guilabel:`Puntos de lealtad` para rastrear los puntos que el usuario ganó "
"como parte del *Programa de lealtad*."
#: ../../content/applications/essentials/contacts.rst:141
msgid "Purchase section"
msgstr ""
msgstr "Sección de compra"
#: ../../content/applications/essentials/contacts.rst:143
msgid ""
@@ -929,10 +1024,13 @@ msgid ""
"preferred :guilabel:`Payment Method` here. A :guilabel:`Receipt Reminder` "
"can be set here, as well."
msgstr ""
"Aquí debe especificar los :guilabel:`términos de pago` y el "
":guilabel:`método de pago`. También puede enviar un :guilabel:`Recordatorio "
"de entrega`."
#: ../../content/applications/essentials/contacts.rst:147
msgid "Misc section"
msgstr ""
msgstr "Sección varios"
#: ../../content/applications/essentials/contacts.rst:149
msgid ""
@@ -947,6 +1045,17 @@ msgid ""
"from the drop-down menu. Use the :guilabel:`SLA Policies` field to assign a "
"*Helpdesk* SLA policy to this contact."
msgstr ""
"Use el campo :guilabel:`Referencia` de la sección :guilabel:`Varios` para "
"agregar cualquier información adicional para este contacto. Si este "
"contacto solo debe estar disponible para una de las empresas en una base de "
"datos multiempresa, use el campo :guilabel:`Empresa` para seleccionarla. Use"
" el menú desplegable :guilabel:`Sitio web` publicar este contacto en un solo"
" sitio web (en caso de que la base de datos tenga varios). Seleccione una o "
"más :guilabel:`etiquetas de sitio web` para facilitar el filtrado de los "
"clientes publicados en la página web `/clientes`. Seleccione un "
":guilabel:`sector` para este contacto con el menú desplegable "
"correspondiente y use el campo :guilabel:`Políticas SLA` para asignar una "
"política de SLA de *Soporte al cliente*."
#: ../../content/applications/essentials/contacts.rst:159
msgid "Accounting tab"
@@ -958,12 +1067,17 @@ msgid ""
"installed. Here, a user can add any related :guilabel:`Bank Accounts`, or "
"set default :guilabel:`Accounting entries`."
msgstr ""
"La pestaña :guilabel:`Contabilidad` aparece cuando se instala la aplicación "
"*Contabilidad*. Aquí un usuario puede agregar :guilabel:`Cuentas bancarias` "
"relacionadas o configurar :guilabel:`asientos contables`."
#: ../../content/applications/essentials/contacts.rst:164
msgid ""
"Under the :guilabel:`Miscellaneous` heading, use the :guilabel:`LEI` field "
"to enter a Legal Entity Identifier, if necessary."
msgstr ""
"En el encabezado :guilabel:`varios` use el campo :guilabel:`LEI` para "
"ingresar el identificador de entidad jurídica si es necesario"
#: ../../content/applications/essentials/contacts.rst:168
msgid "Internal Notes tab"
@@ -975,10 +1089,12 @@ msgid ""
"tab, where notes can be left on this contact form, just like on the contact "
"form noted above."
msgstr ""
"Después de la pestaña :guilabel:`Contabilidad` está la pestaña "
":guilabel:`Notas internas` donde puede dejar notas para esta contacto."
#: ../../content/applications/essentials/contacts.rst:174
msgid "Partner Assignment tab"
msgstr ""
msgstr "Pestaña de Asignación de partner"
#: ../../content/applications/essentials/contacts.rst:176
msgid ""
@@ -988,10 +1104,14 @@ msgid ""
"configurations. These are **only** present when the *Enterprise Resellers* "
"module is installed."
msgstr ""
"Esta pestaña incluye por defecto la sección :guilabel:`Geolocalización` y "
"otras opciones de contacto :guilabel:`Activación de contacto` y "
":guilabel:`Revisión de contacto`. Estas opciones solo se verán si tiene el "
"módulo *Revendedores de enterprise* instalado."
#: ../../content/applications/essentials/contacts.rst:182
msgid "Membership tab"
msgstr ""
msgstr "Pestaña de membresía"
#: ../../content/applications/essentials/contacts.rst:184
msgid ""
@@ -1000,16 +1120,21 @@ msgid ""
"should be noted that this tab only appears when the *Members* applications "
"is installed."
msgstr ""
"Esta pestaña puede se útil para gestionar las membresías que tenga este "
"contacto en específico. Esta pestaña solo aparecerá si tiene la aplicación "
"*Miembros* instalada."
#: ../../content/applications/essentials/contacts.rst:189
msgid "Smart buttons"
msgstr ""
msgstr "Botones inteligentes"
#: ../../content/applications/essentials/contacts.rst:191
msgid ""
"At the top of the contact form, there are some additional options available,"
" known as *smart buttons*."
msgstr ""
"En la parte superior del formulario de contacto hay opciones adicionales "
"disponibles conocidas como *botones inteligentes*."
#: ../../content/applications/essentials/contacts.rst:194
msgid ""
@@ -1017,6 +1142,9 @@ msgid ""
" created on other apps. Odoo integrates information from every single app, "
"so there are many smart buttons."
msgstr ""
"Aquí, Odoo muestra muchos registros relacionados a este contacto que se "
"hayan creado en otra aplicación. Odoo integra información de todas las "
"aplicaciones, así que hay varios botones inteligentes."
#: ../../content/applications/essentials/contacts.rst:198
msgid ""
@@ -1024,12 +1152,18 @@ msgid ""
"the opportunities related to this customer from the *CRM* app are "
"accessible."
msgstr ""
"Por ejemplo, está el botón inteligente :guilabel:`Oportunidades`, donde "
"puede acceder a todas las oportunidades relacionadas a este cliente de la "
"aplicación *CRM*."
#: ../../content/applications/essentials/contacts.rst:202
msgid ""
"If the corresponding applications are installed, their related smart buttons"
" appear automatically on a contact form."
msgstr ""
"Si tiene las aplicaciones correspondientes instaladas, sus botones "
"inteligentes relacionados aparecerán de forma automática en el formulario de"
" contacto."
#: ../../content/applications/essentials/contacts.rst:205
msgid ""
@@ -1041,6 +1175,14 @@ msgid ""
":guilabel:`Invoiced` information, :guilabel:`Vendor Bills`, and the "
":guilabel:`Partner Ledger` connected to this contact."
msgstr ""
"Los usuarios pueden ver las :guilabel:`reuniones`, :guilabel:`ventas`, "
":guilabel:`órdenes del PdV`, :guilabel:`suscripciones` y :guilabel:`tareas` "
"de proyecto. Además, el botón inteligente :guilabel:`Más` muestra otras "
"opciones en un menú desplegable. También es posible acceder con rapidez a "
":guilabel:`compras`, tareas de :guilabel:`soporte al cliente`, "
":guilabel:`tasas de puntualidad` de las entregas, información de "
":guilabel:`facturación`, :guilabel:`facturas de proveedores` y el "
":guilabel:`libro mayor de clientes` asociado a este contacto."
#: ../../content/applications/essentials/contacts.rst:211
msgid ""
@@ -1048,16 +1190,21 @@ msgid ""
" smart buttons, like this, should there be any outstanding/on-file for this "
"contact."
msgstr ""
"Las entregas, documentos, tarjetas de lealtad y domiciliaciones bancarias "
"*también* cuentan con sus respectivos botones inteligentes en caso de que "
"aplique para este contacto."
#: ../../content/applications/essentials/contacts.rst:214
msgid ""
"If the contact is a partner, the user can visit their partner page on the "
"Odoo-built website by clicking the :guilabel:`Go to Website` smart button."
msgstr ""
"El usuario puede visitar la página del contacto en el sitio web creado con "
"Odoo si hace clic en el botón inteligente :guilabel:`Ir a sitio web`."
#: ../../content/applications/essentials/contacts.rst:218
msgid "Archive contacts"
msgstr ""
msgstr "Archivar contactos"
#: ../../content/applications/essentials/contacts.rst:220
msgid ""
@@ -1066,12 +1213,18 @@ msgid ""
":guilabel:`Action` menu at the top of the contact form, and click "
":guilabel:`Archive`."
msgstr ""
"Si un usuario decide que ya no quiere tener este contacto activo es posible "
"archivar el registro. Para hacerlo, vaya al menú :icon:`fa-cog` "
":guilabel:`Acción` en la parte superior del formulario de contacto y haga "
"clic en :guilabel:`Archivar`."
#: ../../content/applications/essentials/contacts.rst:224
msgid ""
"Then, click :guilabel:`OK` from the resulting :guilabel:`Confirmation` pop-"
"up window."
msgstr ""
"Después, haga clic en :guilabel:`De acuerdo` en la ventana emergente de "
":guilabel:`confirmación`."
#: ../../content/applications/essentials/contacts.rst:226
msgid ""
@@ -1079,6 +1232,9 @@ msgid ""
"top, they do not show up in the main contacts page, but they can still be "
"searched for with the :guilabel:`Archived` filter."
msgstr ""
"Cuando haya archivado el contacto se agregará un listón en la parte superior"
" y ya no aparecerán en la página principal de contactos, pero los puede "
"encontrar con el filtro :guilabel:`Archivado`."
#: ../../content/applications/essentials/contacts.rst:230
msgid ""
@@ -1088,18 +1244,26 @@ msgid ""
"doing so, the :guilabel:`Archived` banner is removed, and the contact is "
"restored."
msgstr ""
"Para *desarchivar* un contacto solo haga clic en el menú de :icon:`fa-cog` "
":guilabel:`acción` otra vez en la parte superior del contacto afirmado y "
"haga clic en :guilabel:`Desarchivar`. El listón que tenía antes se quitará y"
" el contacto estará restaurado."
#: ../../content/applications/essentials/contacts.rst:236
msgid ""
":doc:`Add different addresses in CRM "
"<../sales/sales/send_quotations/different_addresses>`"
msgstr ""
":doc:`Agregar varias direcciones a CRM "
"<../sales/sales/send_quotations/different_addresses>`"
#: ../../content/applications/essentials/contacts.rst:237
msgid ""
"`Odoo's eLearning Contacts tutorial "
"<https://www.odoo.com/slides/slide/contacts-2527?fullscreen=1>`_"
msgstr ""
"`Tutorial de contactos en eLearning de Odoo "
"<https://www.odoo.com/slides/slide/contacts-2527?fullscreen=1>`_"
#: ../../content/applications/essentials/export_import_data.rst:3
msgid "Export and import data"
@@ -1152,13 +1316,13 @@ msgid ""
"corresponding record. Finally, click on :guilabel:`⚙️ Action`, and then "
":guilabel:`Export`."
msgstr ""
"Con Odoo, los valores se pueden exportar desde cualquier campo en cualquier "
"registro. Para hacerlo, active la vista de lista (icono de :guilabel:`"
"(tres líneas horizontales)`) en los artículos que quiere exportar y después "
"seleccione los registros que se deben exportar. Para seleccionar un "
"registro, marque la casilla de verificación a un lado del registro "
"correspondiente. Finalmente, haga clic en el botón :guilabel:`⚙️ Acción` y "
"luego en :guilabel:`Exportar`."
"Odoo permite exportar los valores desde cualquier campo en cualquier "
"registro. Para hacerlo, active la vista de lista (icono :guilabel:`≣ (cuatro"
" líneas horizontales)`) en los artículos que necesita exportar y después "
"seleccione los registros que debe exportar. Para seleccionar un registro, "
"seleccione la casilla ubicada junto al registro correspondiente y, por "
"último, haga clic en el botón :icon:`fa-cog` :guilabel:`Acciones` y luego en"
" :guilabel:`Exportar`."
#: ../../content/applications/essentials/export_import_data.rst-1
msgid "View of the different things to enable/click to export data."
@@ -1188,12 +1352,12 @@ msgid ""
"works like a filter. Leaving the box unticked, gives many more field options"
" because it shows all the fields, not just the ones that can be imported."
msgstr ""
"Con la opción de :guilabel:`Deseo actualizar datos (exportación compatible "
"con importación)` habilitada, el sistema solo muestra los campos que se "
"pueden importar. Esto es muy útil en caso de que quiera actualizar registros"
" existentes. Funciona como una especie de filtro, si no selecciona la "
"casilla tiene más opciones de campo porque muestra todos los campos, no solo"
" los que se pueden importar."
"Si la opción :guilabel:`Deseo actualizar datos (exportación compatible con "
"importación)` está habilitada, el sistema solo muestra los campos que se "
"pueden importar. Esto es muy útil en caso de que necesite actualizar los "
"registros existentes, pues funciona como una especie de filtro. Si no "
"selecciona la casilla habrá más opciones de campo porque aparecerán todos "
"los campos, no solo los que se pueden importar."
#: ../../content/applications/essentials/export_import_data.rst:42
msgid ""
@@ -1288,9 +1452,9 @@ msgid ""
"times where data needs to be updated in bulk. The following documentation "
"covers how to import data into an Odoo database."
msgstr ""
"Importar datos a Odoo es muy útil sobre todo durante la implementación, o en"
" momentos cuando los datos necesitan actualizarse en lote. La documentación "
"siguiente habla sobre cómo importar datos a una base de datos de Odoo."
"Importar datos a Odoo es muy útil, sobre todo durante la implementación o "
"cuando necesita actualizar los datos en lote. La siguiente documentación "
"menciona cómo importar datos a una base de datos de Odoo."
#: ../../content/applications/essentials/export_import_data.rst:75
msgid ""
@@ -2067,11 +2231,11 @@ msgid ""
"additional row that does not have any information in the fields relative to "
"the order."
msgstr ""
"Si una empresa quiere importar una orden de venta con varias líneas de "
"orden, se **debe** reservar en el archivo :abbr:`CSV (Comma-separated "
"Values)` para cada línea de la orden. La primera línea de la orden se "
"importa en la misma hilera que la información relativa a la orden. Las "
"líneas adicionales necesitan una hilera adicional que no tenga ninguna "
"Si una empresa desea importar una orden de venta con varias líneas de orden "
"es **necesario** que reserven una fila específica en el archivo :abbr:`CSV "
"(Valores separados por comas)` para cada línea de la orden. La primera línea"
" de la orden se importa en la misma fila que la información relacionada a la"
" orden. Las líneas adicionales necesitan otras filas que no tengan "
"información en los campos relacionados a esa orden."
#: ../../content/applications/essentials/export_import_data.rst:379
@@ -2295,11 +2459,11 @@ msgid ""
"list of services is available on the `Odoo IAP Catalog "
"<https://iap.odoo.com/iap/all-in-app-services>`_."
msgstr ""
"Las compras dentro de la aplicación (conocidas como IAP) son servicios "
"opcionales que mejoran las bases de datos de Odoo y cada uno de ellos "
"proporciona sus propias funciones. Consulte la lista completa de servicios "
"en el `catálogo de IAP de Odoo <https://iap.odoo.com/iap/all-in-app-"
"services>`_."
"Las compras dentro de la aplicación (conocidas como IAP por sus siglas en "
"inglés) son servicios opcionales que mejoran las bases de datos de Odoo y "
"cada uno de ellos proporciona sus propias funciones. Consulte la lista "
"completa de servicios en el `catálogo de IAP de Odoo "
"<https://iap.odoo.com/iap/all-in-app-services>`_."
#: ../../content/applications/essentials/in_app_purchase.rst-1
msgid "The IAP catalog with various services available on IAP.Odoo.com."
@@ -2317,8 +2481,8 @@ msgstr ""
"El servicio de :guilabel:`SMS` envía mensajes de texto a sus contactos "
"directo desde la base de datos. El servicio de :guilabel:`digitalización de "
"documentos` digitaliza facturas de proveedores, gastos y currículums "
"escaneados o en formato PDF con reconocimiento óptico de caracteres (OCR) e "
"inteligencia artificial (IA)."
"escaneados o en formato PDF con reconocimiento óptico de caracteres (OCR, "
"por sus siglas en inglés) e inteligencia artificial (IA)."
#: ../../content/applications/essentials/in_app_purchase.rst:20
msgid ""
@@ -2327,11 +2491,11 @@ msgid ""
"each service requires its own prepaid credits, and when they run out, users "
"**must** :ref:`buy more <iap/buying_credits>` in order to keep using it."
msgstr ""
"**No** es necesario que configure los servicios de |IAP| antes de usarlos. "
"Los usuarios de Odoo pueden hacer clic en el servicio en la aplicación para "
"activarlo. Sin embargo, cada servicio necesita de sus propios créditos "
"prepagados, y cuando se agotan, los usuarios **deben** :ref:`comprar más "
"<iap/buying_credits>` para seguir utilizándolos."
"**No** necesita configurar los servicios de |IAP| antes de usarlos, puede "
"solo hacer clic en el servicio dentro de la aplicación de Odoo para "
"activarlo. Sin embargo, cada servicio necesita de créditos prepagados y "
"**debe** :ref:`comprar más <iap/buying_credits>` si se acaban para poder "
"seguir utilizándolos."
#: ../../content/applications/essentials/in_app_purchase.rst:25
msgid ""
@@ -2340,11 +2504,11 @@ msgid ""
"includes demo/training databases, educational databases, and one-app-free "
"databases."
msgstr ""
"Los usuarios de Odoo Enterprise con una suscripción válida obtendrán "
"Los usuarios de Odoo Enterprise que tengan una suscripción válida obtendrán "
"créditos gratuitos para probar las funciones de compras dentro de la "
"aplicación antes de que decidan comprar más créditos para la base de datos. "
"Esto incluye bases de datos de demostración y capacitación, bases de datos "
"educativas y bases de datos gratuitas de una sola aplicación."
"aplicación antes de decidir si desean comprar más créditos para la base de "
"datos. Esto incluye bases de datos de demostración y capacitación, bases de "
"datos educativas y bases de datos gratuitas de una sola aplicación."
#: ../../content/applications/essentials/in_app_purchase.rst:32
msgid "IAP services"
@@ -2355,12 +2519,13 @@ msgid ""
"|IAP| services are provided by Odoo, as well as third-parties, and have a "
"wide range of uses."
msgstr ""
"Tanto Odoo como externos proporcionan los servicios de |IAP|, y tienen una "
"amplia variedad de usos."
"Odoo y proveedores de servicios externos proporcionan los servicios de "
"compras dentro de la aplicación y tienen una gran variedad de usos."
#: ../../content/applications/essentials/in_app_purchase.rst:36
msgid "The following |IAP| services are offered by Odoo:"
msgstr "Odoo ofrece los siguientes servicios de |IAP|:"
msgstr ""
"Odoo ofrece los siguientes servicios como compras dentro de la aplicación:"
#: ../../content/applications/essentials/in_app_purchase.rst:38
msgid ""
@@ -2402,7 +2567,7 @@ msgid ""
"post, worldwide."
msgstr ""
":guilabel:`Correo postal`: envía facturas de clientes y reportes de "
"seguimiento por correo postal por todo el mundo."
"seguimiento por correo postal a todo el mundo."
#: ../../content/applications/essentials/in_app_purchase.rst:45
msgid ""
@@ -2410,10 +2575,10 @@ msgid ""
"Odoo *Sign* to provide their identity using the *itsme®* identity platform, "
"which is available in Belgium and the Netherlands."
msgstr ""
":guilabel:`Identifíquese con itsme®️ para firmar sus documentos`: solicítele"
" a los signatarios de *Firma electrónica* de Odoo que proporcionen su "
"identidad a través de la plataforma de identidad *itsme‍®*. Solo está "
"disponible en Bélgica y los Países Bajos."
":guilabel:`Identifíquese con itsme®️ para firmar sus documentos`: solicite "
"que los signatarios de *Firma electrónica* de Odoo proporcionen su identidad"
" a través de la plataforma de identidad *itsme‍®*. Solo está disponible en "
"Bélgica y los Países Bajos."
#: ../../content/applications/essentials/in_app_purchase.rst:49
msgid ""
@@ -2421,9 +2586,10 @@ msgid ""
"developers other than Odoo), visit the `Odoo IAP Catalog "
"<https://iap.odoo.com/iap/all-in-app-services>`_."
msgstr ""
"Visite el `catálogo de IAP de Odoo <https://iap.odoo.com/iap/all-in-app-"
"services>`_ para obtener más información sobre los servicios disponibles por"
" el momento (los ofrecen desarrolladores externos a Odoo)."
"Visite el `catálogo de compras dentro de la aplicación de Odoo "
"<https://iap.odoo.com/iap/all-in-app-services>`_ para obtener más "
"información sobre los servicios disponibles por el momento (los ofrecen "
"desarrolladores externos a Odoo)."
#: ../../content/applications/essentials/in_app_purchase.rst:53
msgid "Use IAP services"
@@ -2435,10 +2601,10 @@ msgid ""
"require users to configure any settings. To use a service, simply interact "
"with it wherever it appears in the database."
msgstr ""
"Los servicios de |IAP| están integrados con Odoo de forma automática y "
"**no** es necesario que los usuarios configuren ningún ajuste. Para utilizar"
" un servicio solo deberá interactuar con el desde cualquier lugar de la base"
" de datos."
"Los servicios de compras dentro de la aplicación están integrados con Odoo "
"de forma automática y **no** es necesario que los usuarios hagan ajustes "
"adicionales. Para utilizar un servicio solo deberá interactuar con él desde "
"cualquier lugar de la base de datos."
#: ../../content/applications/essentials/in_app_purchase.rst:59
msgid ""
@@ -2469,7 +2635,7 @@ msgid ""
"following steps:"
msgstr ""
"Los siguientes pasos describen una de las maneras de utilizar el servicio "
"*SMS* de |IAP| con Odoo:"
"*SMS* de compras dentro de la aplicación con Odoo:"
#: ../../content/applications/essentials/in_app_purchase.rst:69
msgid ""
@@ -2478,8 +2644,8 @@ msgid ""
"or :guilabel:`Mobile` field of the contact form."
msgstr ""
"Vaya a la aplicación :menuselection:`Contactos` y haga clic en un contacto "
"con un número telefónico disponible en el campo :guilabel:`Teléfono` o "
":guilabel:`Celular` del formulario de contacto."
"que tenga un número de teléfono móvil configurado en los campos "
":guilabel:`Teléfono` o :guilabel:`Celular` del formulario de contacto."
#: ../../content/applications/essentials/in_app_purchase.rst:73
msgid ""
@@ -2487,7 +2653,7 @@ msgid ""
":guilabel:`Phone` or :guilabel:`Mobile` fields. Click the :guilabel:`📱 SMS` "
"icon, and a :guilabel:`Send SMS Text Message` pop-up window appears."
msgstr ""
"Busque el icono :guilabel:`📱 SMS` que aparecen de lado derecho de los campos"
"Busque el icono :guilabel:`📱 SMS` que aparece del lado derecho de los campos"
" :guilabel:`Teléfono` o :guilabel:`Celular`. Al hacer clic en el icono "
":guilabel:`📱 SMS` aparece la ventana emergente :guilabel:`Enviar mensaje de "
"texto SMS`."
@@ -2500,9 +2666,9 @@ msgid ""
"form."
msgstr ""
"Escriba un mensaje en el campo :guilabel:`Mensaje` de la ventana emergente, "
"haga clic en el botón :guilabel:`Enviar SMS`. Odoo enviará el mensaje, vía "
"SMS, al contacto y registrará lo que envió en el *chatter* del formulario "
"del contacto."
"haga clic en el botón :guilabel:`Enviar SMS`. Odoo enviará el mensaje vía "
"SMS al contacto y registrará lo que envió en el *chatter* del formulario del"
" contacto."
#: ../../content/applications/essentials/in_app_purchase.rst:81
msgid ""
@@ -2511,10 +2677,10 @@ msgid ""
"not enough credits to send the message, Odoo prompts the user to purchase "
"more."
msgstr ""
"Los créditos prepagados para el servicio *SMS* de |IAP| se restan en "
"automático de los créditos existentes una vez que se env el mensaje SMS. "
"Odoo le solicitará al usuario que compre más créditos en caso de que no haya"
" suficientes para enviar el mensaje."
"Los créditos prepagados para el servicio *SMS* de |IAP| se restarán de los "
"créditos existentes una vez que se envíe el mensaje SMS. Odoo le solicitará "
"al usuario que compre más créditos en caso de que no cuente con los "
"necesarios para enviar el mensaje."
#: ../../content/applications/essentials/in_app_purchase.rst:86
msgid ""
@@ -2524,7 +2690,7 @@ msgid ""
msgstr ""
"Consulte la siguiente documentación para obtener más información sobre cómo "
"utilizar varios servicios de |IAP| e instrucciones más detalladas "
"relacionadas con la funcionalidad de SMS en Odoo:"
"relacionadas con las funciones de SMS en Odoo:"
#: ../../content/applications/essentials/in_app_purchase.rst:89
msgid ":doc:`Lead mining <../sales/crm/acquire_leads/lead_mining>`"
@@ -2547,7 +2713,7 @@ msgstr ""
#: ../../content/applications/essentials/in_app_purchase.rst:97
msgid "IAP credits"
msgstr "Créditos de compras dentro de la aplicación"
msgstr "Créditos para compras dentro de la aplicación"
#: ../../content/applications/essentials/in_app_purchase.rst:99
msgid ""
@@ -2556,11 +2722,11 @@ msgid ""
"enough credits left to continue using a service. Email alerts can also be "
"set up for when :ref:`credits are low <in_app_purchase/low-credits>`."
msgstr ""
"Cada que utiliza un servicio de |IAP| gasta los créditos prepagados para ese"
" servicio. Odoo le solicitará comprar más créditos cuando no cuenta con "
"suficientes para seguir utilizando un servicio. También pueden configurar "
"alertas por correo electrónico para cuando le :ref:`queden pocos créditos "
"<in_app_purchase/low-credits>`."
"Cada que utiliza un servicio que requiere de |IAP|, entonces gasta los "
"créditos prepagados para ese servicio. Odoo le solicitará comprar más "
"créditos cuando no cuente con suficientes para seguir utilizando un "
"servicio. También es posible configurar alertas por correo electrónico para "
"cuando le :ref:`queden pocos créditos <in_app_purchase/low-credits>`."
#: ../../content/applications/essentials/in_app_purchase.rst:103
msgid ""
@@ -2568,9 +2734,9 @@ msgid ""
"<https://iap.odoo.com/iap/all-in-app-services>`_, and pricing is specific to"
" each service."
msgstr ""
"Los créditos se compran en *paquetes* con el `catálogo de IAP de Odoo "
"<https://iap.odoo.com/iap/all-in-app-services>`_ y los precios son "
"específicos para cada servicio."
"Los créditos se compran con los *paquetes* que aparecen en el `catálogo de "
"IAP de Odoo <https://iap.odoo.com/iap/all-in-app-services>`_. Los precios "
"son específicos para cada servicio."
#: ../../content/applications/essentials/in_app_purchase.rst:107
msgid ""
@@ -2578,7 +2744,7 @@ msgid ""
"packs available, in denominations of:"
msgstr ""
"El `servicio de SMS <https://iap.odoo.com/iap/in-app-services/1>`_ cuenta "
"con cuatro paquetes disponibles en las siguientes denominaciones:"
"con cuatro paquetes disponibles con los siguientes precios:"
#: ../../content/applications/essentials/in_app_purchase.rst:110
msgid ":guilabel:`Starter Pack`: 10 credits"
@@ -2626,8 +2792,8 @@ msgid ""
"If there are not enough credits to perform a task, the database "
"automatically prompts the purchase of more credits."
msgstr ""
"De forma automática, la base de datos le solicitará comprar más créditos si "
"no cuenta con suficientes para realizar una tarea."
"La base de datos le solicitará comprar más créditos en automático si no "
"cuenta con los suficientes para realizar una tarea."
#: ../../content/applications/essentials/in_app_purchase.rst:132
msgid ""
@@ -2669,9 +2835,9 @@ msgid ""
"it says :guilabel:`Odoo IAP`, click :guilabel:`View My Services`."
msgstr ""
"Vaya a la aplicación :menuselection:`Ajustes` y escriba `Compras dentro de "
"la aplicación` en la :guilabel:`barra de búsqueda` o diríjase a la sección "
":guilabel:`Contactos`. Si va a la sección :guilabel:`Contactos` section, "
"busque :guilabel:`Compras dentro de la aplicación de Odoo` y haga clic en "
"la aplicación` en la :guilabel:`barra de búsqueda`, o diríjase a la sección "
":guilabel:`Contactos`. Si va a la sección :guilabel:`Contactos`, busque "
":guilabel:`Compras dentro de la aplicación de Odoo` y haga clic en "
":guilabel:`Ver mis servicios`."
#: ../../content/applications/essentials/in_app_purchase.rst-1
@@ -2742,8 +2908,8 @@ msgid ""
msgstr ""
"Vaya a la aplicación :menuselection:`Ajustes` y escriba `Compras dentro de "
"la aplicación` en la :guilabel:`barra de búsqueda`. En la sección "
":guilabel:`Contactos` section, busque :guilabel:`Compras dentro de la "
"aplicación de Odoo` y haga clic en :guilabel:`Ver mis servicios`."
":guilabel:`Contactos`, busque :guilabel:`Compras dentro de la aplicación de "
"Odoo` y haga clic en :guilabel:`Ver mis servicios`."
#: ../../content/applications/essentials/in_app_purchase.rst:180
msgid ""
File diff suppressed because it is too large Load Diff
+118 -122
View File
@@ -28,7 +28,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-05-28 08:57+0000\n"
"POT-Creation-Date: 2024-08-20 14:22+0000\n"
"PO-Revision-Date: 2021-11-02 08:47+0000\n"
"Last-Translator: Fernanda Alvarez, 2024\n"
"Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n"
@@ -623,12 +623,11 @@ msgid ""
" by un-ticking the checkbox, and clicking :guilabel:`Save`. See the section "
"on :ref:`digest-emails/deactivate`."
msgstr ""
"Para desactivar los correos electrónicos de resumen vaya a "
":menuselection:`Ajustes --> sección de Estadísticas`. Después, para "
"desactivar la función :guilabel:`Correos electrónicos de resumen` solo tiene"
" que desmarcar la casilla de verificación junto a ella y hacer clic en "
":guilabel:`Guardar`. Obtenga más información en la sección :ref:`digest-"
"emails/deactivate`."
"Vaya a :menuselection:`Ajustes --> sección Estadísticas` para desactivar los"
" correos de resumen. Después, desmarque la casilla junto a la opción "
":guilabel:`Correos electrónicos de resumen` para deshabilitar esta función y"
" haga clic en :guilabel:`Guardar`. Consulte :ref:`digest-emails/deactivate` "
"para obtener más información."
#: ../../content/applications/general/companies/digest_emails.rst:39
msgid "Customize default digest email"
@@ -903,7 +902,7 @@ msgstr ":guilabel:`Tiempo de respuesta (seg)`"
#: ../../content/applications/general/companies/digest_emails.rst:138
msgid ":guilabel:`Helpdesk`"
msgstr ":guilabel:`Servicio de asistencia`"
msgstr ":guilabel:`Soporte al cliente`"
#: ../../content/applications/general/companies/digest_emails.rst:138
msgid ":guilabel:`Tickets Closed`"
@@ -1905,9 +1904,9 @@ msgid ""
msgstr ""
"Para editar traducciones, primero habilite el :ref:`modo de desarrollador "
"<developer-mode>`. En la plantilla de correo electrónico, haga clic en el "
"botón :guilabel:`editar` y luego haga clic en el botón de idioma, "
"representado por las iniciales del idioma que se utiliza en ese momento (por"
" ejemplo, guilabel:`EN` para inglés)."
"botón :guilabel:`Editar` y luego haga clic en el botón de idioma, "
"representado por las iniciales del idioma que utiliza en ese momento (por "
"ejemplo, :guilabel:`EN` para inglés)."
#: ../../content/applications/general/companies/email_template.rst-1
msgid "Edit the language of a template."
@@ -2105,7 +2104,7 @@ msgstr "Comunicación por correo electrónico"
#: ../../content/applications/general/email_communication/azure_oauth.rst:3
msgid "Connect Microsoft Outlook 365 to Odoo using Azure OAuth"
msgstr "Conecte Microsoft Outlook 365 a Odoo con Azure OAuth"
msgstr "Conectar Microsoft Outlook 365 a Odoo con Azure OAuth"
#: ../../content/applications/general/email_communication/azure_oauth.rst:5
msgid ""
@@ -2158,13 +2157,13 @@ msgid ""
" Next, navigate to the section labeled :guilabel:`Manage Microsoft Entra ID`"
" (formally *Azure Active Directory*)."
msgstr ""
"Primero, vaya al `portal de Microsoft Azure <https://portal.azure.com/>`_. "
"Inicie sesión con la cuenta de :guilabel:`Microsoft Outlook Office 365` si "
"Primero vaya al `portal de Microsoft Azure <https://portal.azure.com/>`_. "
"Inicie sesión con su cuenta de :guilabel:`Microsoft Outlook Office 365` si "
"tiene una, de lo contrario inicie sesión con su :guilabel:`cuenta personal "
"de Microsoft`. Necesitará un usuario con acceso de administrador a los "
"ajustes de Azure para conecta y configurar los siguientes ajustes. Luego, "
"vaya a la sección llamada :guilabel:`Gestionar ID de Microsoft Entra (antes"
" *Directorio activo de Azure)."
"ajustes de Azure para conectar y configurar los siguientes ajustes. Luego, "
"vaya a la sección llamada :guilabel:`Gestionar ID de Microsoft Entra` (antes"
" *Directorio activo de Azure*)."
#: ../../content/applications/general/email_communication/azure_oauth.rst:30
msgid ""
@@ -2176,42 +2175,44 @@ msgid ""
"directory - Multitenant) and personal Microsoft accounts (e.g. Skype, "
"Xbox)`."
msgstr ""
"Ahora, haga clic en :guilabel:`Agregar (+)` en la parte superior del menú y "
"seleccione :guilabel:`Registro de aplicación`. En la pantalla de "
":guilabel:`Registre una aplicación`, cambie el nombre en :guilabel:`Nombre` "
"a `Odoo` o algo que pueda reconocer. En la sección :guilabel:`Tipos de "
"cuentas compatibles`, seleccione guilabel:`Cuentas en cualquier directorio "
"organizacional (directorio Microsoft Entra ID - Multitenant) y cuentas de "
"Microsoft personales (por ejemplo, Skype, Xbox)`."
"Ahora haga clic en :guilabel:`Agregar (+)` en la parte superior del menú y "
"seleccione :guilabel:`Registro de aplicación`. En la pantalla "
":guilabel:`Registre una aplicación` cambie el :guilabel:`nombre` a `Odoo` o "
"a algún otro que pueda reconocer. En la sección :guilabel:`Tipos de cuentas "
"compatibles` seleccione :guilabel:`Cuentas en cualquier directorio "
"organizacional (cualquier inquilino - multiinquilino de Microsoft Entra) y "
"cuentas de Microsoft personales (por ejemplo, Skype, Xbox)`."
#: ../../content/applications/general/email_communication/azure_oauth.rst:36
msgid ""
"Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the "
"platform, and then input `https://<odoo base url>/microsoft_outlook/confirm`"
" in the :guilabel:`URL` field. The Odoo base URL is the canonical domain at "
"which your Odoo instance can be reached in the URL field."
"platform, and then input `https://<web base url>/microsoft_outlook/confirm` "
"in the :guilabel:`URL` field. The `web.base.url` is subject to change "
"depending on the URL used to log in to the database."
msgstr ""
"En la sección :guilabel:`Redirect URL` (redericción de URL) seleccione la "
"plataforma :guilabel:`Web` y después ponga `https://<odoo base "
"url>/microsoft_outlook/confirm` en el campo :guilabel:`URL`. La URL base de "
"Odoo es el dominio canónico en el que su instancia de Odoo puede ser "
"contactada en el campo URL."
"En la sección :guilabel:`URL de redirección` seleccione :guilabel:`Web` como"
" la plataforma y luego escriba `https://<web base "
"url>/microsoft_outlook/confirm` en el campo :guilabel:`URL`. La "
"`web.base.url` puede variar según la URL utilizada para iniciar sesión en la"
" base de datos."
#: ../../content/applications/general/email_communication/azure_oauth.rst:41
msgid ""
"*mydatabase.odoo.com*, where *mydatabase* is the actual prefix of the "
"database's subdomain, assuming it's hosted on Odoo.com"
"The documentation about the :ref:`web.base.url <domain-name/web-base-url>` "
"explains how to freeze a unique URL. It is also possible to add different "
"redirect URLs on the Microsoft app."
msgstr ""
"*mydatabase.odoo.com*, donde *mydatabase* es el prefijo del subdominio de la"
" base de datos, asumiendo que está alojada en Odoo.com."
"La documentación sobre :ref:`web.base.url <domain-name/web-base-url>` "
"explica cómo fijar una URL única. Además, es posible agregar diferentes URL "
"de redirección en la aplicación de Microsoft."
#: ../../content/applications/general/email_communication/azure_oauth.rst:44
msgid ""
"After the URL has been added to the field, :guilabel:`Register` the "
"application so it is created."
"application, so it is created."
msgstr ""
"Una vez que se agregó la URL al campo, :guilabel:`registre` la aplicación "
"para crearla."
"Una vez que haya agregado la URL al campo, :guilabel:`registre` la "
"aplicación para crearla. "
#: ../../content/applications/general/email_communication/azure_oauth.rst:47
msgid "API permissions"
@@ -2320,12 +2321,11 @@ msgid ""
"users/groups, click :guilabel:`Select`, and then :guilabel:`Assign` them to "
"the application."
msgstr ""
"En :guilabel:`usuarios` o :guilabel:`grupos`, haga clic en :guilabel:`None "
"Selected` (ninguno seleccionado) y agrege los usuarios o el grupo de "
"usuarios que enviará correos desde :guilabel:`la cuenta de Microsoft` en "
"Odoo. :guilabel:`Agregue` a los usuarios o grupos, haga clic en "
"guilabel:`Select` (seleccionar) y después :guilabel:`Assign` (asígnelos) a "
"la aplicación."
"En :guilabel:`usuarios` o :guilabel:`grupos`, haga clic en "
":guilabel:`Ninguno seleccionado` y agregue los usuarios o el grupo de "
"usuarios que enviará correos desde la :guilabel:`cuenta de Microsoft` en "
"Odoo. :guilabel:`Agregue` a los usuarios y grupos, haga clic en "
":guilabel:`Seleccionar` y después :guilabel:`asígnelos` a la aplicación."
#: ../../content/applications/general/email_communication/azure_oauth.rst:94
msgid "Create credentials"
@@ -2843,7 +2843,7 @@ msgstr ":doc:`email_servers`"
#: ../../content/applications/general/email_communication/email_domain.rst:3
msgid "Configure DNS records to send emails in Odoo"
msgstr "Configure los registros DNS para enviar correos en Odoo"
msgstr "Configurar registros DNS para enviar correos en Odoo"
#: ../../content/applications/general/email_communication/email_domain.rst:6
msgid "SPAM labels overview"
@@ -2902,10 +2902,9 @@ msgid ""
"ticket <https://www.odoo.com/help>`_ and the support team will work to get "
"the servers removed from the blacklist."
msgstr ""
"Si el servidor de correo de Odoo aparece en una lista negra, notifíquenos "
"mediante un `ticket de soporte nuevo <https://www.odoo.com/help>`_ y el "
"equipo de soporte técnico trabajará para que el servidor ya no esté en la "
"lista negra."
"Si el servidor de correo de Odoo aparece en una lista de exclusión deberá "
"enviarnos `un nuevo ticket de soporte <https://www.odoo.com/help>`_ para que"
" nuestro equipo de soporte trabaje en eliminarlo de esa lista. "
#: ../../content/applications/general/email_communication/email_domain.rst:28
msgid ""
@@ -3968,18 +3967,18 @@ msgid ""
"is added on the contact under :guilabel:`Blacklisted Email Addresses` on the"
" :guilabel:`Email Marketing Configuration Menu`."
msgstr ""
"Los **mensajes devueltos** se utilizan como ruta de retorno. Esto es "
"especialmente útil en la aplicación `Marketing por correo electrónico de "
"Odoo <https://www.odoo.com/page/email-marketing>`__. En este caso, los "
"rebotes se excluyen de acuerdo a si el correo ha sido devuelto demasiadas "
"veces (5) en el último mes y si las devoluciones tienen una semana de "
"separación entre ellas. Esto se hace para evitar agregar a alguien a la "
"lista negra debido a un error en el servidor de correo. Si se cumplen estas "
"condiciones, entonces el correo electrónico se considera inválido y se "
"agrega a la lista negra. Se agrega una nota de registro en el contacto, en "
"la sección :guilabel:`direcciones de correo electrónico incluidas en la "
"lista negra` en el :guilabel:`menú de configuración de Marketing por correo "
"electrónico`."
"Los **mensajes devueltos** se utilizan como ruta de devolución. Esto es muy "
"útil en la aplicación `Marketing por correo electrónico de Odoo "
"<https://www.odoo.com/page/email-marketing>`__. En este caso, las "
"devoluciones pasan a la lista de exclusión si la dirección ha devuelto "
"varios mensajes (5) en el último mes y si entre cada devolución ha pasado "
"una semana. Esta acción tiene la finalidad de evitar la inclusión en esta "
"lista en caso de que se trate de un error del servidor de correo. Si se "
"cumplen las primeras condiciones, entonces el correo no es válido y formará "
"parte de la lista de exclusión. El contacto tendrá una nota de registro en "
"la sección :guilabel:`Direcciones de correo electrónico incluidas en la "
"lista de exclusión` en el :guilabel:`menú de configuración de Marketing por "
"correo electrónico`."
#: ../../content/applications/general/email_communication/email_servers.rst:222
msgid ""
@@ -4015,8 +4014,8 @@ msgid ""
"Support channel (to create *Tickets* in `Odoo Helpdesk "
"<https://www.odoo.com/page/helpdesk>`_)"
msgstr ""
"Canal de soporte (para crear *tickets* en la aplicación `Servicio de "
"asistencia de Odoo <https://www.odoo.com/page/helpdesk>`_)"
"Canal de soporte (para crear *tickets* en la aplicación `Soporte al cliente "
"de Odoo <https://www.odoo.com/page/helpdesk>`_)"
#: ../../content/applications/general/email_communication/email_servers.rst:231
msgid ""
@@ -4819,9 +4818,9 @@ msgid ""
"email should reach the Odoo database, and display the :ref:`red envelope "
"<red_envelop>`."
msgstr ""
"¿Funciona como debería? Is it working as expected? In case the email is sent"
" using Odoo, the bounce email should reach the Odoo database, and display "
"the :ref:`red envelope <red_envelop>`."
"¿Funciona como debería? En caso de que utilice Odoo para enviar el correo, "
"el correo devuelto debe llegar a la base de datos de Odoo y aparecer con un "
":guilabel:`sobre rojo <red_envelop>`."
#: ../../content/applications/general/email_communication/faq.rst:228
msgid ""
@@ -4839,7 +4838,7 @@ msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:3
msgid "Connect Gmail to Odoo using Google OAuth"
msgstr "Conectar Gmail con Odoo mediante Google OAuth"
msgstr "Conectar Gmail a Odoo con Google OAuth"
#: ../../content/applications/general/email_communication/google_oauth.rst:5
msgid ""
@@ -5144,10 +5143,10 @@ msgid ""
msgstr ""
"Después, vaya a :menuselection:`Ajustes --> Ajustes generales` y asegúrese "
"de que la casilla de :guilabel:`servidores de correo electrónico "
"personalizados` o :guilabel:servidores de correo electrónico externos` en la"
" sección :guilabel:`Conversaciones` esté seleccionada. Aparecerá una nueva "
"opción para las :guilabel:`credenciales de Gmail` o para :guilabel:`usar un "
"servidor de Gmail`. Luego, copie y pegue el :guilabel:`ID de cliente` y el "
"personalizados` o :guilabel:`servidores de correo electrónico externos` en "
"la sección :guilabel:`Conversaciones` esté seleccionada. Aparecerá una nueva"
" opción para las :guilabel:`credenciales de Gmail` o para :guilabel:`usar un"
" servidor de Gmail`. Luego, copie y pegue el :guilabel:`ID de cliente` y el "
":guilabel:`secreto de cliente` en sus respectivos campos y "
":guilabel:`guarde` los ajustes."
@@ -5158,7 +5157,7 @@ msgid ""
":guilabel:`Outgoing Email Servers` link."
msgstr ""
"Para configurar la cuenta externa de Gmail, regrese a la parte superior de "
"los ajustes para los :guilabel:` servidores de correo electrónico "
"los ajustes para los :guilabel:`servidores de correo electrónico "
"personalizados` y haga clic en el enlace :guilabel:`Servidores de correo "
"saliente` ."
@@ -5173,9 +5172,9 @@ msgid ""
"server, and fill in the :guilabel:`Name`, :guilabel:`Description`, and the "
"email :guilabel:`Username` (if required)."
msgstr ""
"Luego, haga clic en :guilabel:`nuevo` para crear un servidor de correo "
"Luego, haga clic en :guilabel:`Nuevo` para crear un servidor de correo "
"electrónico y complete el :guilabel:`nombre`, la :guilabel:`descripción` y "
"el correo en el :guilabel:`nombre de usuario` (si es necesario)."
"el :guilabel:`nombre de usuario` (si es necesario)."
#: ../../content/applications/general/email_communication/google_oauth.rst:139
msgid ""
@@ -5989,7 +5988,7 @@ msgstr "Generar tareas en cualquier proyecto de Odoo."
#: ../../content/applications/general/integrations/mail_plugins.rst:18
msgid "Creating tickets in the Helpdesk app."
msgstr "Crear tickets en la aplicación Servicio de asistencia."
msgstr "Crear tickets en la aplicación Soporte al cliente. "
#: ../../content/applications/general/integrations/mail_plugins.rst:19
msgid "Searching and storing insights on your contacts."
@@ -7067,11 +7066,10 @@ msgid ""
"previously copied *token* into the :guilabel:`Server Token` field, and then "
"click on :guilabel:`Next`."
msgstr ""
"Al conectarse al WiFi de la caja IoT, un navegador le redirigirá "
"automáticamente al asistente de :menuselection:`configuración de la caja "
"IoT`. Asigne un nombre a la caja IoT y pegue el *token* previamente copiado "
"en el campo :guilabel:`Token del servidor`, y haga clic en :guilabel: "
"`Siguiente`."
"Al conectarse al Wi-Fi de la caja IoT, un navegador le redirigirá en "
"automático al asistente de :menuselection:`configuración de la caja IoT`. "
"Asígnele un nombre, en el campo :guilabel:`Token del servidor` pegue el "
"*token* que copió y haga clic en :guilabel:`Siguiente`."
#: ../../content/applications/general/iot/config/connect.rst-1
msgid "Enter the server token into the IoT box."
@@ -8360,7 +8358,7 @@ msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:161
msgid "This can be :guilabel:`Unknown` under :guilabel:`Local printers`."
msgstr ""
"Puede aparecer como :guilabel:`Desconocido` en :guilabel: `Impresoras "
"Puede aparecer como :guilabel:`Desconocido` en :guilabel:`Impresoras "
"locales`."
#: ../../content/applications/general/iot/config/troubleshooting.rst:163
@@ -9316,12 +9314,11 @@ msgid ""
"on the POS --> IoT Box section --> Edit --> Receipt Printer --> Cashdrawer "
"checkbox`."
msgstr ""
"La caja registradora debe estar conectada a la impresora y la casilla de "
"verificación :guilabel:`Caja registradora` debe estar seleccionada en la "
"configuración del :abbr:`PdV (Punto de venta)`. Para hacerlo, vaya a la "
"aplicación :menuselection:`Punto de venta --> menú con tres puntos en el PdV"
" --> sección Caja IoT --> Editar --> Impresora de recibos --> casilla Caja "
"registradora`."
"La caja registradora debe estar conectada a la impresora y la casilla "
":guilabel:`Caja registradora` debe estar seleccionada en la configuración "
"del :abbr:`PdV (Punto de venta)`. Para hacerlo, vaya a :menuselection:`Punto"
" de venta --> menú con 3 puntos en el PdV --> sección Caja IoT --> Editar "
"--> Impresora de recibos --> casilla Caja registradora`."
#: ../../content/applications/general/iot/config/troubleshooting.rst:573
msgid ""
@@ -9999,13 +9996,12 @@ msgid ""
"here, add the device in the :guilabel:`IoT Triggers` tab, in the "
":guilabel:`Device` column, by clicking :guilabel:`Add a Line`."
msgstr ""
"Para vincular una cámara a una acción, primero necesita configurarla en un "
"Para vincular una cámara a una acción, primero debe configurarla en un "
"centro de trabajo. Vaya a :menuselection:`Fabricación --> Configuración --> "
"Centros de trabajo`. Luego, vaya al :guilabel:`Centro de trabajo` que desee "
"y en donde usará la cámara para mostrar el formulario detallado de ese "
"centro de trabajo específico. Luego, agregue el dispositivo en la pestaña "
":guilabel:`Activadores de IoT `, en la columna :guilabel:`Dispositivos` y "
"haga clic en :guilabel:`Agregar una línea`. "
"Centros de trabajo` y diríjase al :guilabel:`centro de trabajo` deseado en "
"el que la usará para abrir su formulario de detalles. Luego, agregue el "
"dispositivo en la pestaña :guilabel:`Activadores de IoT` en la columna "
":guilabel:`Dispositivos` y haga clic en :guilabel:`Agregar una línea`. "
#: ../../content/applications/general/iot/devices/camera.rst:70
msgid ""
@@ -10345,11 +10341,11 @@ msgid ""
"trigger* during the manufacturing process, or added onto a quality control "
"point or a quality check."
msgstr ""
"La instalación de una impresora se puede hacer en unos cuantos pasos muy "
"fáciles. La impresora se puede usar para imprimir recibos, etiquetas, "
"órdenes o incluso reportes de diferentes aplicaciones de Odoo. Además, puede"
" asignar las acciones de una impresora como *acciones en un activador* "
"durante los procesos de fabricación, o agregarlas a un punto de control o "
"Instalar una impresora es muy fácil y toma solo un par de pasos. La "
"impresora se puede usar para imprimir recibos, etiquetas, órdenes o incluso "
"reportes de diferentes aplicaciones de Odoo. Además, puede asignar las "
"acciones de una impresora como *acciones en un activador* durante los "
"procesos de fabricación, así como agregarlas a un punto de control o "
"revisión de calidad. "
#: ../../content/applications/general/iot/devices/printer.rst:13
@@ -11907,9 +11903,9 @@ msgid ""
":guilabel:`Share Group`, if this group was created to set access rights for "
"sharing data with some users."
msgstr ""
"Ingrese un :guilabel:`Nombre` para el grupo y marque la casilla de "
"verificación a un lado de :guilabel:`Compartir grupo`, si este grupo se creó"
" para configurar permisos de acceso para compartir datos con otros usuarios."
"Escriba un :guilabel:`nombre` para el grupo y seleccione la casilla junto a "
":guilabel:`Compartir grupo` en caso de que haya creado el grupo para "
"configurar permisos de acceso para compartir datos con otros usuarios."
#: ../../content/applications/general/users/access_rights.rst:83
msgid ""
@@ -11925,10 +11921,10 @@ msgid ""
"group. In each tab, click :guilabel:`Add a line` to add a new row for users "
"or rules, and click the :guilabel:`❌ (remove)` icon to remove a row."
msgstr ""
"El formulario de grupo contiene varias pestañas para gestionar todos los "
"elementos del grupo. En cada pestaña, haga clic en :guilabel:`Agregar una "
"línea` para agregar una nueva hilera para usuarios o reglas y haga clic en "
"el icono :guilabel:`❌ (eliminar)` para eliminar una hilera."
"El formulario de grupo incluye varias pestañas para gestionar todos sus "
"elementos. En cada pestaña, haga clic en :guilabel:`Agregar una línea` para "
"agregar una nueva fila para usuarios o reglas y haga clic en el icono "
":guilabel:`❌ (eliminar)` para eliminarla."
#: ../../content/applications/general/users/access_rights.rst-1
msgid "Tabs in the Groups form to modify the settings of the group."
@@ -12255,11 +12251,11 @@ msgid ""
"longer be able to be duplicated, renamed, or otherwise managed from the "
"Odoo.com portal."
msgstr ""
"Las bases de datos que estén alojadas en Odoo.com no pueden iniciar sesión "
"con OAuth si el usuario es el dueño o administrador de la base de datos; si "
"esto ocurre, la base de datos se desvinculará de su cuenta de Odoo.com. Si "
"configura OAuth para ese usuario, ya no podrá duplicar, cambiar el nombre, o"
" gestionar esa base de datos desde el portal de Odoo.com."
"Las bases de datos que estén alojadas en Odoo.com **no** deben iniciar "
"sesión con OAuth si el usuario es el propietario o administrador de la base "
"de datos. Si esto ocurre, la base de datos se desvinculará de su cuenta de "
"Odoo.com. Si configura OAuth para ese usuario, ya no podrá duplicar, cambiar"
" el nombre o gestionar esa base de datos desde el portal de Odoo.com."
#: ../../content/applications/general/users/azure.rst:18
msgid ":doc:`../../productivity/calendar/outlook`"
@@ -12338,7 +12334,7 @@ msgid ""
" the center of the page."
msgstr ""
"Luego, vaya a la sección con el nombre :guilabel:`Gestionar Microsoft Entra "
"ID ` (antes conocido como *Azure Active Directory*). Por lo general, la "
"ID` (antes conocido como *Azure Active Directory*). Por lo general, la "
"ubicación de este enlace se encuentra en el centro de la página. "
#: ../../content/applications/general/users/azure.rst:55
@@ -12670,9 +12666,9 @@ msgid ""
"The *Google Sign-In Authentication* is a useful function that allows Odoo "
"users to sign in to their database with their Google account."
msgstr ""
"La *autenticación de inicio de sesión de Odoo* es una función útil que "
"permite que los usuarios de Odoo inicien sesión en su base de datos desde su"
" cuenta de Goole."
"La *autenticación de inicio de sesión de Google* es una función útil que "
"permite que los usuarios de Odoo inicien sesión en su base de datos con su "
"cuenta de Google."
#: ../../content/applications/general/users/google.rst:8
msgid ""
@@ -12691,11 +12687,11 @@ msgid ""
"longer be able to be duplicated, renamed or otherwise managed from the "
"Odoo.com portal."
msgstr ""
"Las bases de datos alojadas en Odoo.com no deben usar el inicio se sesión de"
" Oauth si es el propietario o administrador de la misma, pues podría "
"desvincular la base de datos de su cuenta de Odoo.com. Si Oauth está "
"establecido para ese usuario, la base de datos ya no se podrá duplicar, "
"renombrar o administrar desde el portal de Odoo.com. "
"Las bases de datos que estén alojadas en Odoo.com **no** deben iniciar "
"sesión con OAuth si el usuario es el propietario o administrador de la base "
"de datos. Si esto ocurre, la base de datos se desvinculará de su cuenta de "
"Odoo.com. Si configura OAuth para ese usuario, ya no podrá duplicar, cambiar"
" el nombre o gestionar esa base de datos desde el portal de Odoo.com."
#: ../../content/applications/general/users/google.rst:19
msgid ":doc:`../email_communication/google_oauth`"
@@ -13086,8 +13082,8 @@ msgid ""
"LDAP Authentication checkbox highlighted in the integrations settings on "
"Odoo."
msgstr ""
"La casilla de verificación Autenticación LDAP resaltada en los ajustes de "
"integraciones dentro de Odoo."
"La casilla Autenticación LDAP resaltada en los ajustes de integraciones "
"dentro de Odoo."
#: ../../content/applications/general/users/ldap.rst-1
msgid "Create highlighted in the LDAP server settings."
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
+78 -80
View File
@@ -127,7 +127,7 @@ msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:43
msgid "Default kanban view and stages"
msgstr "Vista kanban y etapas predeterminadas"
msgstr "Vista de kanban predeterminada y etapas"
#: ../../content/applications/marketing/email_marketing.rst:45
msgid ""
@@ -428,9 +428,9 @@ msgid ""
"features are: :guilabel:`Mailing Campaigns`, :guilabel:`Blacklist Option "
"when Unsubscribing`, and :guilabel:`Dedicated Server`."
msgstr ""
"En la página :guilabel:`Ajustes`, hay tres funciones disponibles. Las "
"funciones son: :guilabel:`Campañas de correo`, :guilabel:`Opción de lista "
"negra al darse de baja` y :guilabel:`Servidor especializado`."
"En la página :guilabel:`Ajustes` hay tres funciones disponibles, estas son: "
":guilabel:`Campañas de correo`, :guilabel:`Opción de lista de exclusión al "
"darse de baja` y :guilabel:`Servidor dedicado`."
#: ../../content/applications/marketing/email_marketing.rst:163
msgid ""
@@ -445,9 +445,9 @@ msgid ""
":guilabel:`Blacklist Option when Unsubscribing`: allows recipients to "
"blacklist themselves from future mailings during the unsubscribing process."
msgstr ""
":guilabel:`Opción de lista negra al darse de baja`: permite a los "
"destinatarios incluirse a sí mismos en una lista negra de futuros envíos "
"durante el proceso de baja."
":guilabel:`Opción de lista de exclusión al darse de baja`: Permite que los "
"destinatarios se incluya en una lista de exclusión de futuros envíos durante"
" el proceso de cancelar su suscripción."
#: ../../content/applications/marketing/email_marketing.rst:166
msgid ""
@@ -1314,11 +1314,11 @@ msgid ""
" added to a single contact's detail form."
msgstr ""
"Una vez que los contactos estén en la base de datos, haga clic en el "
"formulario detallado del contacto deseado y agregue la lista de correo "
"preferida en la pestaña :guilabel:`Lista de correo` (en la parte inferior "
"del formulario detallado del contacto) haciendo clic en :guilabel:`Agregar "
"línea`, y seleccionando la lista de correo deseada. Puede agregar varias "
"listas de correo a un solo formulario detallado de contacto. "
"formulario de detalles del contacto deseado y agregue la lista de correo "
"preferida a pestaña :guilabel:`Lista de correo` (se encuentra en la parte "
"inferior del formulario). Haga clic en :guilabel:`Agregar una línea` y "
"seleccione la lista de correo deseada. Puede agregar varias listas de correo"
" a los formularios. "
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1
msgid ""
@@ -1374,7 +1374,7 @@ msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:76
msgid "Link a mailing list to website (Newsletter blocks)"
msgstr ""
"Vincular una lista de correo al sitio web (bloques de boletín de noticias)"
"Vincular una lista de correo al sitio web (bloques de boletín informativo)"
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:78
msgid ""
@@ -1545,18 +1545,18 @@ msgid ""
"to :guilabel:`Blacklist Options when Unsubscribing`, and click "
":guilabel:`Save`."
msgstr ""
"Lo primero es habilitar la función *lista negra*. Para hacerlo, vaya a la "
"aplicación :menuselection:`Marketing por correo electrónico --> "
"Configuración --> Ajustes`, habilite la :guilabel:`opción de lista negra al "
"darse de baja`, y haga clic en :guilabel:`guardar`."
"Primero debe habilitar la función *Lista de exclusión*. Para ello, vaya a "
":menuselection:`Marketing por correo electrónico --> Configuración --> "
"Ajustes`, habilite la :guilabel:`opción de lista de exclusión al darse de "
"baja` y haga clic en :guilabel:`Guardar`."
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1
msgid ""
"View of the blacklist feature in the Settings page of the Odoo Email "
"Marketing app."
msgstr ""
"Vista de la función de lista negra en la página de ajustes de la aplicación "
"de Marketing por correo electrónico"
"Vista de la función de lista de exclusión en la página de ajustes de la "
"aplicación Marketing por correo electrónico de Odoo."
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:20
msgid ""
@@ -1591,9 +1591,9 @@ msgid ""
"lists, the recipient can also *Blacklist* themselves, meaning they will not "
"receive *any* more emails."
msgstr ""
"Además de poder *cancelar su suscripción* desde ciertos correos, los "
"recipientes también podrán añadirse a la *lista negra*, lo que evitará que "
"vuelvan a recibir correos."
"Además de poder *cancelar su suscripción* de ciertas listas de correo, el "
"destinatario también puede incluirse en la *lista de exclusión* por su "
"cuenta, lo que significa que ya no recibirá *ningún* correo electrónico."
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:36
msgid ""
@@ -1609,15 +1609,15 @@ msgid ""
":menuselection:`Email Marketing app --> Configuration --> Blacklisted Email "
"Addresses`."
msgstr ""
"Para ver la lista completa de direcciones de correo electrónico incluidas en"
" la lista negra, vaya a la :menuselection:`aplicación de Correo electrónico "
"--> Configuración --> Direcciones de correo electrónico incluidas en la "
"lista negra`."
"Para ver la lista completa de direcciones de correo que forman parte de la "
"lista de exclusión, vaya a :menuselection:`Marketing por correo electrónico "
"--> Configuración --> Direcciones de correo electrónico incluidas en la "
"lista de exclusión`."
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1
msgid "View of the blacklisted email addresses page in Odoo Email Marketing."
msgstr ""
"Vista de la página de correos electrónicos de la lista negra en la "
"Vista de la página de correos electrónicos de la lista de exclusión en la "
"aplicación Marketing por correo electrónico de Odoo."
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:45
@@ -1625,15 +1625,14 @@ msgid ""
"When a blacklisted record is selected from this page, Odoo reveals a "
"separate page with that blacklisted recipient's contact information."
msgstr ""
"Cuando se selecciona un correo de la lista negra en esta página, Odoo abrirá"
" una nueva pestaña con la información de contacto del destinatario de la "
"lista negra."
"Al seleccionar un registro en la lista de exclusión desde esta página, Odoo "
"abre otra con la información de contacto del destinatario excluido."
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1
msgid "View of a blacklisted contact detail form in Odoo Email Marketing."
msgstr ""
"Vista de un formulario de detalles de contacto en lista negra en la "
"aplicación Marketing por correo electrónico de Odoo."
"Vista de un formulario de detalles de contacto en la lista de exclusión en "
"la aplicación Marketing por correo electrónico de Odoo."
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:52
msgid ""
@@ -1641,14 +1640,14 @@ msgid ""
"informing the user when that recipient blacklisted themselves (via a "
":guilabel:`Mail Blacklist created` log note)."
msgstr ""
"La página cuenta con un :guilabel:`chatter` en el que aparecerá un mensaje "
"con la fecha y hora en la que el usuario se registró en la lista negra "
"(mediante una nota de registro con la leyenda :guilabel:` Lista negra del "
"correo creada`)."
"El :guilabel:`chatter` de esta página hay un mensaje con fecha y hora que le"
" informa al usuario acerca del momento en que ese destinatario se incluyó en"
" la lista de exclusión (mediante una nota de registro :guilabel:`Exclusión "
"del correo creada`)."
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:56
msgid "Unblacklist contacts"
msgstr "Quitar a contactos de la lista negra"
msgstr "Eliminar contactos de la lista de exclusión"
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:58
msgid ""
@@ -1656,8 +1655,8 @@ msgid ""
"upper-left corner to remove the contact from the blacklist, allowing them to"
" receive mailings once again."
msgstr ""
"Para *quitar contactos de la lista negra*, haga clic en el botón "
":guilabel:`Quitar de la lista negra`, esto evitará que el contacto vuelva a "
"Para *eliminar contactos de la lista de exclusión*, haga clic en el botón "
":guilabel:`Eliminar de la lista de exclusión` y el contacto volverá a "
"recibir correos."
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:61
@@ -1667,18 +1666,18 @@ msgid ""
"field, in which a reason can be entered, explaining why this particular "
"contact was removed from the blacklist."
msgstr ""
"Si hace clic en :guilabel:`Quitar de la lista negra`, aparece una pestaña "
"emergente en la que verá la dirección de correo específica y el campo "
":guilabel:`Motivo`; en este campo debe escribir el motivo por el cuál se "
"removió al contacto de la lista negra."
"Al hacer clic en :guilabel:`Eliminar de la lista de exclusión` aparece una "
"ventana emergente con la dirección de correo específica y el campo "
":guilabel:`Motivo`, allí debe escribir el motivo por el que eliminó al "
"contacto de la lista de exclusión."
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1
msgid ""
"View of the unblacklist pop-up window in the Odoo Email Marketing "
"application."
msgstr ""
"Vista de la ventana emergente para quitar contactos de la lista negra en la "
"aplicación Marketing por correo electrónico."
"Vista de la ventana emergente para eliminar contactos de la lista de "
"exclusión en la aplicación Marketing por correo electrónico de Odoo. "
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:69
msgid ""
@@ -1686,7 +1685,7 @@ msgid ""
"that particular contact from the blacklist."
msgstr ""
"Después de completar los campos, haga clic en :guilabel:`Confirmar` para "
"eliminar oficialmente ese contacto específico de la lista negra."
"eliminar a ese contacto en específico de la lista de exclusión."
#: ../../content/applications/marketing/events.rst:5
msgid "Events"
@@ -2570,7 +2569,7 @@ msgstr "Vista de la transacción en el sitio web."
#: ../../content/applications/marketing/events/track_manage_talks.rst:3
msgid "Track and manage talks"
msgstr "Seguimiento y gestión de las pláticas"
msgstr "Seguimiento y gestión de las sesiones"
#: ../../content/applications/marketing/events/track_manage_talks.rst:5
msgid ""
@@ -5193,8 +5192,8 @@ msgid ""
"An employee can be designated as the :guilabel:`Responsible` in the "
":guilabel:`Tracking` section of the :guilabel:`Settings` tab, as well."
msgstr ""
"También se puede determinar a un empleado como :guilabel:`Responsable` en la"
" sección :guilabel:`seguimiento` de la pestaña :guilabel:`Ajustes`."
"También puede seleccionar a un empleado como :guilabel:`responsable` en la "
"sección :guilabel:`Seguimiento` de la pestaña :guilabel:`Ajustes`."
#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1
msgid "SMS Settings tab."
@@ -5280,9 +5279,9 @@ msgid ""
"down menu)."
msgstr ""
"Por ejemplo, mientras la vista predeterminada es :guilabel:`gráfico`, los "
"datos de los :abbr:`SMS (servicio de mensajes cortos)` se visualizan como "
"datos de los :abbr:`SMS (servicio de mensajes cortos)` aparecen en "
"diferentes gráficos y tablas que se pueden ordenar y agrupar de varias "
"maneras (p. ej., el menú desplegable guilabel:`Medidas`)."
"maneras (por ejemplo, el menú desplegable :guilabel:`Medidas`)."
#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1
msgid "Reporting page in SMS Marketing."
@@ -5585,10 +5584,9 @@ msgid ""
"(in :guilabel:`Kanban` view), and click on either link in the blue banner "
"above the SMS detail form to learn more."
msgstr ""
"Para obtener información más detallada, seleccione el SMS que desee en el "
"tablero principal (en la vista :guilabel:`kanban` y haga clic en cualquiera "
"de los enlaces en el banner azul sobre el formulario de detalles de SMS para"
" obtener más información."
"Para obtener información más detallada, seleccione un SMS en el tablero "
"principal (en la vista de :guilabel:`kanban`) y haga clic en cualquiera de "
"los enlaces del recuadro azul arriba del formulario de detalles de SMS."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "**Can I send as many SMSs I want at once?**"
@@ -5711,10 +5709,10 @@ msgid ""
":menuselection:`Campaigns` from the header menu. Doing so reveals a separate"
" page with every campaign in a default kanban view."
msgstr ""
"Para acceder a una vista general completa de todas las campañas de marketing"
" social, abra la aplicación :menuselection:`Marketing social` y haga clic en"
" :menuselection:`Campañas` desde el menú superior, se mostrará una página "
"distinta con cada campaña en una vista kanban predeterminada."
"Abra la aplicación :menuselection:`Marketing social` para acceder a una "
"vista general completa de todas las campañas y, en el menú superior, haga "
"clic en :menuselection:`Campañas`. Aparecerá una página distinta con las "
"campañas en la vista de kanban predeterminada."
#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst-1
#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst-1
@@ -5728,9 +5726,9 @@ msgid ""
":guilabel:`gear icon` to the left of the :guilabel:`+ (plus sign)` - located"
" to the right of the stage title."
msgstr ""
"Cada *etapa* en la vista kanban se puede editar haciendo clic en el "
"Cada *etapa* en la vista de kanban se puede editar al hacer clic en el "
":guilabel:`icono de engranaje` del lado izquierdo del :guilabel:`+ (signo de"
" más)` - situado a la derecha del título de la etapa."
" más)` que se encuentra a la derecha del título de la etapa."
#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:29
msgid ""
@@ -5750,9 +5748,9 @@ msgid ""
"column can be restored by clicking the folded version of it on the main "
":guilabel:`Campaigns` dashboard in the default kanban view."
msgstr ""
"Hacer clic en :guilabel:`Plegar` minimiza la columna de esa etapa "
"específica. Se puede restaurar haciendo clic en la versión plegada en el "
"tablero principal de :guilabel:`Campañas` en la vista kanban predeterminada."
"Hacer clic en :guilabel:`Plegar` minimiza la columna de esa etapa en "
"específico. Para restaurarla, haga clic en la versión plegada en el tablero "
"principal de :guilabel:`Campañas` en la vista de kanban predeterminada."
#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:41
msgid ""
@@ -5810,11 +5808,11 @@ msgid ""
"can also be created by clicking :guilabel:`Create` in the upper-left corner "
"of the :guilabel:`Campaigns` dashboard."
msgstr ""
"En el tablero de :guilabel:`Campañas` puede crear una nueva haciendo clic en"
" el signo de agregado rápido :guilabel:`+ (signo de más)` ubicado en la "
"esquina superior derecha de cada etapa en el flujo, visible en la vista "
"kanban. También puede crear una campaña haciendo clic en :guilabel:`nuevo` "
"en la esquina superior izquierda del mismo tablero."
"En el tablero :guilabel:`Campañas` puede crear una campaña nueva al hacer "
"clic en el signo de agregado rápido :guilabel:`+ (signo de más)` que se "
"encuentra en la esquina superior derecha de cada etapa en el flujo, visible "
"en la vista de kanban. También puede crear una campaña al hacer clic en "
":guilabel:`Nuevo` en la esquina superior izquierda del mismo tablero."
#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:67
msgid ""
@@ -5836,10 +5834,10 @@ msgid ""
":guilabel:`Tags` can be entered. When all modifications are complete, click "
":guilabel:`Add` to add the campaign to the database."
msgstr ""
"Ingrese aquí el :guilabel:`nombre de la campaña`, el :guilabel:`responsable`"
" y las :guilabel:`etiquetas`. Cuando termine de escribir todas las "
"modificaciones, haga clic en :guilabel:`Agregar` para añadir la campaña a la"
" base de datos."
"Aquí escriba el :guilabel:`nombre de la campaña`, la persona "
":guilabel:`responsable` y las :guilabel:`etiquetas`. Cuando termine de "
"realizar todas las modificaciones, haga clic en :guilabel:`Agregar` para "
"añadir la campaña a la base de datos."
#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:78
msgid "Edit social marketing campaigns"
@@ -5879,9 +5877,9 @@ msgid ""
":guilabel:`⋮ (three dots)` drop-down menu on the desired campaign, and "
"select :guilabel:`Edit`."
msgstr ""
"En el tablero de :guilabel:`Campañas` desde la vista kanban, seleccione el "
"Desde la vista de kanban del tablero de :guilabel:`Campañas` seleccione el "
"menú desplegable :guilabel:`⋮ (tres puntos)` en la campaña deseada y después"
" presione :guilabel:`Editar`."
" seleccione :guilabel:`Editar`."
#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:91
msgid ""
@@ -7707,11 +7705,11 @@ msgid ""
" external resources (e.g. web search), and reduces the survey to a \"closed "
"book\" testing environment."
msgstr ""
"Durante una encuesta con tiempo límite, los participantes deben terminarla "
"dentro de un periodo de tiempo establecido. Un caso de uso muy común en el "
"que se usa el tiempo límite es para reducir la propabilidad de que el "
"participante busque las respuestas en otro lado (por ejemplo, en internet), "
"y establce la encuesta como un ambiente de prueba a \"libro cerrado\". "
"Si la encuesta cuenta con tiempo límite es necesario que los participantes "
"la completen dentro del periodo establecido. Un caso de uso muy común en el "
"que se usa el tiempo límite es para reducir la probabilidad de que el "
"participante busque las respuestas en otro lado (por ejemplo, en internet) y"
" hace que sea una prueba a \"libro cerrado\". "
#: ../../content/applications/marketing/surveys/time_random.rst:16
msgid ""
+44 -48
View File
@@ -15,8 +15,8 @@
# Wil Odoo, 2024
# Martin Trigaux, 2024
# Lucia Pacheco, 2024
# Patricia Gutiérrez Capetillo <pagc@odoo.com>, 2024
# Braulio D. López Vázquez <bdl@odoo.com>, 2024
# Patricia Gutiérrez Capetillo <pagc@odoo.com>, 2024
# Fernanda Alvarez, 2024
#
#, fuzzy
@@ -24,7 +24,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-04-29 08:05+0000\n"
"POT-Creation-Date: 2024-06-21 08:31+0000\n"
"PO-Revision-Date: 2021-11-02 08:49+0000\n"
"Last-Translator: Fernanda Alvarez, 2024\n"
"Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n"
@@ -90,9 +90,9 @@ msgid ""
" enter a country and agree to the Terms of Service. Select a country from "
"the drop-down list and agree to the :abbr:`ToS (Terms of Service)`."
msgstr ""
"Si esta es la primera vez que visita esta página, Google le pedirá que "
"ingrese a un país y acepte los Términos de servicio. Seleccione un país de "
"la lista y acepte los :guilabel;`Términos de servicio`."
"Si es la primera vez que visita esta página, Google le pedirá que seleccione"
" un país y acepte los términos de servicio. Elija un país de la lista y "
"acepte los :guilabel:`términos`."
#: ../../content/applications/productivity/calendar/google.rst:26
msgid ""
@@ -1475,10 +1475,10 @@ msgid ""
"left side of a contact's name on the :guilabel:`Discuss` sidebar, on the "
"*messaging menu* and when listed in the *chatter*."
msgstr ""
"Es útil ver qué están haciendo sus colegas y qué tan rápido pueden responder"
" a los mensajes, por eso debe verificar su *estado*. El estado se muestra en"
" el lado izquierdo de el nombre de un contacto en la barra lateral "
"de:guilabel:`Discusiones`, en el *menú de mensajería* y en el *chatter*."
"Los *estados* son útiles para ver qué están haciendo sus compañeros y qué "
"tan rápido pueden responder a los mensajes. Estos aparecen del lado "
"izquierdo del nombre de un contacto en la barra lateral de "
":guilabel:`Conversaciones`, en el *menú de mensajería* y en el *chatter*."
#: ../../content/applications/productivity/discuss.rst:91
msgid "Green = online"
@@ -2455,12 +2455,12 @@ msgid ""
"information is up to date or not. We advise contacting a local attorney for "
"legal advice regarding electronic signature compliance and validity."
msgstr ""
"La información proporcionada aquí no representa un asesoramiento legal; se "
"proporciona únicamente con fines informativos generales. Puesto que las "
"leyes que rigen la firma electrónica evolucionan con rapidez, no podemos "
"garantizar que la información esté actualizada. Le aconsejamos que se ponga "
"en contacto con un abogado local para obtener asesoramiento legal sobre el "
"cumplimiento y la validez de la firma electrónica."
"La siguiente información no tiene valor legal, solo se proporciona con fines"
" informativos generales. Dado que las leyes que rigen las firmas "
"electrónicas cambian con rapidez, no podemos garantizar que toda la "
"información esté actualizada. Le recomendamos contactar a un abogado local "
"para que pueda recibir asesoramiento legal sobre el cumplimiento y la "
"validez de las firmas electrónicas."
#: ../../content/applications/productivity/sign.rst:79
msgid "Field Types"
@@ -2526,8 +2526,8 @@ msgstr ""
msgid ""
"**Checkbox**: users can tick a box (e.g.,to mark their approval or consent)."
msgstr ""
"**Casilla de verificación**: los usuarios pueden seleccionar una casilla "
"(por ejemplo, para indicar su autorización o consentimiento)."
"**Casilla**: Los usuarios pueden seleccionar una casilla (para indicar su "
"aprobación o consentimiento)."
#: ../../content/applications/productivity/sign.rst:97
msgid "**Selection**: users choose a single option from a variety of options."
@@ -2621,14 +2621,14 @@ msgstr ""
#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:12
msgid ""
"To use this service, `contact Axivox <https://www.axivox.com/contact/>`_ to "
"open an account. Before doing so, verify that Axivox covers the company's "
"area, along with the areas the company's users wish to call."
"To use this service, `contact Axivox <https://www.axivox.com/en/contact/>`_ "
"to open an account. Before doing so, verify that Axivox covers the company's"
" area, along with the areas the company's users wish to call."
msgstr ""
"Para usar este servicio `contacte a Axivox "
"<https://www.axivox.com/contact/>`_ para abrir una cuenta. Antes de hacerlo,"
" compruebe que Axivox tenga cobertura en su área y en las zonas a las que "
"desea llamar."
"<https://www.axivox.com/en/contact.php>`_ para abrir una cuenta. Antes de "
"hacerlo, compruebe que Axivox tenga cobertura en su área y en las zonas a "
"las que desea llamar."
#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:17
#: ../../content/applications/productivity/voip/onsip.rst:33
@@ -2899,7 +2899,7 @@ msgstr ""
#: ../../content/applications/productivity/voip/axivox/call_queues.rst:48
msgid ":guilabel:`Call all available agents`"
msgstr ":guilabel:Llamar a todos los agentes disponibles`"
msgstr ":guilabel:`Llamar a todos los agentes disponibles`"
#: ../../content/applications/productivity/voip/axivox/call_queues.rst:49
msgid ""
@@ -4003,9 +4003,9 @@ msgid ""
"the :guilabel:`Timeout` on the :guilabel:`receptionist` pop-up window that "
"appears."
msgstr ""
"Después de agregar un elemento de :guilabel:`Asistente virtual` al plan de "
"marcación, conecte los puntos finales apropiados y haga doble clic en el "
"elemento para configurar un :guilabel:`Límite de tiempo en la ventana "
"Después de agregar un elemento de :guilabel:`asistente virtual` al plan de "
"marcación, conecte los puntos de conexión apropiados y haga doble clic en el"
" elemento para configurar un :guilabel:`límite` de tiempo en la ventana "
"emergente de :guilabel:`recepcionista` que aparece."
#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:115
@@ -4891,9 +4891,8 @@ msgid ""
"To add a new dial plan from the :guilabel:`Dial plan` page, click the green "
"button labeled, :guilabel:`Add a new dial plan`."
msgstr ""
"Para agregar un nuevo plan de marcación desde la página :guilabel:`Dial "
"plans` (plan de marcación) haga clic en el botón verde llamado guilabel:`Add"
" a new dial plan` (agregar un nuevo plan de marcación)."
"Para agregar un nuevo plan desde la página :guilabel:`Planes de marcación` "
"haga clic en el botón verde :guilabel:`Agregar un nuevo plan de marcación`."
#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:35
msgid ""
@@ -5617,11 +5616,10 @@ msgid ""
"Order the rules as necessary, and select the checkbox to supersede all other"
" rules, if needed."
msgstr ""
"Para ello, basta con escribir `0044` en el campo :guilabel:`Destination "
"prefix` (Prefijo de destino) y seleccionar el número que empieza por el "
"prefijo de país `+44`. Ordene las reglas según sea necesario, y seleccione "
"la casilla de verificación para reemplazar todas las demás reglas, si es "
"necesario."
"Para ello, escriba `0044` en el campo :guilabel:`Prefijo de destino` y "
"seleccione el número que inicia con el prefijo de país `+44`. Ordene las "
"reglas según sea necesario y seleccione la casilla para anular el resto de "
"las reglas en caso si lo requiere."
#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:0
msgid "Advanced options for the default outgoing number."
@@ -7156,8 +7154,8 @@ msgid ""
"accent is used by the computerized speaker."
msgstr ""
"El texto se lee en el mismo idioma en el que está escrito en el campo "
":guilabel:`Texto`. Si el idioma en el campo :guilabel:`Voz`es distinto, "
"entonces la voz computarizada utilizará un acento."
":guilabel:`Texto`. La voz computarizada utilizará un acento si el idioma en "
"el campo :guilabel:`Voz` es distinto."
#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:224
msgid ""
@@ -7829,7 +7827,7 @@ msgstr ""
"Para configurar la base de datos de Odoo y que se conecte a los servicios de"
" OnSIP, primero vaya a :menuselection:`Aplicaciones` desde el tablero "
"principal de Odoo. Luego, elimine el filtro predeterminado `Aplicaciones` de"
" la barra :guilabel:`Buscar...` y busque `VoIP OnSIP`."
" la :guilabel:`barra de búsqueda` y escriba `VoIP OnSIP`."
#: ../../content/applications/productivity/voip/onsip.rst:39
msgid "Next, install the :guilabel:`VOIP OnSIP` module."
@@ -7851,11 +7849,10 @@ msgid ""
":guilabel:`Asterisk (VoIP)` fields. Then, proceed to fill in those three "
"fields with the following information:"
msgstr ""
"Después de instalar el módulo *VOIP OnSIP*, vaya a la "
":menuselection:`aplicación Ajustes`, diríjase a la parte de abajo hasta la "
"sección :guilabel:`Integraciones` y localice los campos :guilabel:`Asterisk "
"(VoIP)`. Luego, proceda a completar esos tres campos con la siguiente "
"información:"
"Después de instalar el módulo *VOIP OnSIP* vaya a :menuselection:`Ajustes`, "
"busque la sección :guilabel:`Integraciones` y localice los campos "
":guilabel:`Asterisk (VoIP)`. Luego complete esos tres campos con la "
"siguiente información:"
#: ../../content/applications/productivity/voip/onsip.rst:52
msgid ""
@@ -8322,8 +8319,8 @@ msgid ""
" with the following Odoo apps: *CRM*, *Project*, and *Helpdesk*."
msgstr ""
"La pestaña :guilabel:`Siguientes actividades` del widget de teléfono *VoIP* "
"está integrado con las aplicaciones *CRM*, *Proyecto* y *Servicio de "
"asistencia* de Odoo."
"está integrado con las aplicaciones *CRM*, *Proyecto* y *Soporte al cliente*"
" de Odoo."
#: ../../content/applications/productivity/voip/transfer_forward.rst:87
msgid ""
@@ -8435,9 +8432,8 @@ msgstr ""
"Acérquese al administrador de la :abbr:`VoIP (Voz sobre protocolo de "
"internet)` para conocer la extensión de un usuario. En caso de que el "
"usuario tenga permisos de acceso a *ajustes* en *Administración*, vaya a "
":menuselection:`aplicación Ajustes --> Administrar usuarios --> seleccione "
"el usuario --> Preferencias --> VoIP --> Nombre de usuario VoIP / Número de "
"extensión`."
":menuselection:`Ajustes --> Administrar usuarios --> seleccione el usuario "
"--> Preferencias --> VoIP --> Nombre de usuario VoIP / Número de extensión`."
#: ../../content/applications/productivity/voip/transfer_forward.rst:130
msgid ""
+160 -157
View File
@@ -31,7 +31,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-05-28 08:57+0000\n"
"POT-Creation-Date: 2024-06-21 08:31+0000\n"
"PO-Revision-Date: 2021-11-02 08:49+0000\n"
"Last-Translator: Fernanda Alvarez, 2024\n"
"Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n"
@@ -125,8 +125,8 @@ msgid ""
"Configuration --> Settings` and check the box labeled, :guilabel:`Leads`. "
"Then, click :guilabel:`Save`."
msgstr ""
"Para activar la función de *leads*, vaya a :menuselection:`aplicación CRM "
"--> Configuración --> Ajustes`, seleccione la casilla con el nombre "
"Para activar la función de *leads*, vaya a :menuselection:`CRM --> "
"Configuración --> Ajustes`, seleccione la casilla con el nombre "
":guilabel:`Leads` y luego haga clic en :guilabel:`Guardar`."
#: ../../content/applications/sales/crm/acquire_leads/convert.rst-1
@@ -154,12 +154,12 @@ msgid ""
"team from the list to open the record, and uncheck the :guilabel:`Leads` "
"box. Once done, click :guilabel:`Save`."
msgstr ""
"Una vez habilitó la función de *leads*, esta se aplica de forma "
"Una vez que habilitó la función de *leads* esta se aplica de forma "
"predeterminada a todos los equipos de ventas. Para desactivar los leads en "
"un equipo específico, vaya a la :menuselection:`aplicación CRM --> "
"Configuración --> Equipos de ventas`. Seleccione un equipo de la lista para "
"abrir su registro, desmarque la casilla :guilabel:`Leads` y luego haga clic "
"en :guilabel:`Guardar`."
"un equipo específico, vaya a :menuselection:`CRM --> Configuración --> "
"Equipos de ventas`, seleccione un equipo de la lista para abrir su registro,"
" desmarque la casilla :guilabel:`Leads` y luego haga clic en "
":guilabel:`Guardar`."
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:35
msgid "Convert a lead into an opportunity"
@@ -323,7 +323,7 @@ msgid ""
"Lead` smart button. Click the :guilabel:`☰ (three vertical lines)` icon to "
"change to list view."
msgstr ""
"Después de confirmar que los leads y las oportunidades deben fusionarse "
"Después de confirmar que los leads y las oportunidades deben fusionarse, "
"regrese a la vista de kanban con las migas de pan o haga clic en el botón "
"inteligente :guilabel:`Lead similar`. Haga clic en el icono :guilabel:`☰ "
"(tres líneas verticales)` para cambiar a la vista de lista."
@@ -849,11 +849,11 @@ msgid ""
"credits for the database. This includes demo/training databases, educational"
" databases, and one-app-free databases."
msgstr ""
"Los usuarios de Odoo Enterprise con una suscripción válida obtendrán "
"Los usuarios de Odoo Enterprise que tengan una suscripción válida obtendrán "
"créditos gratuitos para probar las funciones de compras dentro de la "
"aplicación antes de que decidan comprar más créditos para la base de datos. "
"Esto incluye bases de datos de demostración y capacitación, bases de datos "
"educativas y bases de datos gratuitas de una sola aplicación."
"aplicación antes de decidir si quieren comprar más créditos para la base de "
"datos. Esto incluye bases de datos de demostración y capacitación, bases de "
"datos educativas y bases de datos gratuitas de una sola aplicación."
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:92
msgid ":doc:`/applications/essentials/in_app_purchase`"
@@ -1746,8 +1746,8 @@ msgid ""
"be altered before the activity is scheduled or saved."
msgstr ""
"La información en los campos :guilabel:`Usuario predeterminado` y "
":guilabel:`Resumen predeterminado` se incluye en la actividad creada. Sin "
"embargo, se pueden alterar antes de que la actividad se programe o se "
":guilabel:`Resumen predeterminado` se incluye en la actividad creada, pero "
"puede alterar estos campos antes de que la actividad se programe o se "
"guarde."
#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:93
@@ -2569,11 +2569,11 @@ msgid ""
" chosen, select the checkbox to the left of each desired opportunity/lead to"
" be restored."
msgstr ""
"Después, seleccione el icono de tres líneas :guilabel:`☰ (lista)` en la "
"esquina superior derecha para activar la vista de lista. Al hacer esto, "
"todos los leads del :guilabel:`Flujo` se mostrarán en forma de lista. "
"Seleccione la casilla de verificación a la izquierda de cada lead u "
"oportunidad que quiere restaurar."
"Después seleccione la opción de vista de lista, está representada por el "
"icono de tres líneas :guilabel:`☰ (lista)` ubicado en la esquina superior "
"derecha. Al hacer esto, todos los leads del :guilabel:`flujo` aparecerán en "
"forma de lista, luego seleccione la casilla ubicada a la izquierda de cada "
"oportunidad o lead que desea restaurar."
#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:108
msgid ""
@@ -2865,9 +2865,9 @@ msgid ""
"variables used to calculate the probability of success can be customized in "
"the settings."
msgstr ""
"El puntaje predictivo de leads siempre está activo en el *CRM* de Odoo. Sin "
"embargo, las variantes que se usan para calcular la probabilidad de éxito se"
" pueden personalizar en ajustes."
"La puntuación predictiva de leads siempre está habilitada en el *CRM* de "
"Odoo y puede personalizar las variables utilizadas para calcular la "
"probabilidad de éxito en los ajustes."
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:49
msgid ""
@@ -2876,9 +2876,9 @@ msgid ""
":guilabel:`Predictive Lead Scoring`, click on the :guilabel:`Update "
"Probabilities` button."
msgstr ""
"Para personalizar las variantes que se usan en la puntuación predictiva de "
"leads, vaya a :menuselection:`CRM --> Configuración --> Ajustes`. En "
":guilabel:`Puntuación predictiva de leads` haga clic en el botón "
"Para personalizar las variables utilizadas en la puntuación predictiva de "
"leads, vaya a :menuselection:`CRM --> Configuración --> Ajustes`. Busque "
":guilabel:`Puntuación predictiva de leads` y haga clic en el botón "
":guilabel:`Actualizar probabilidades`."
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:53
@@ -2994,9 +2994,9 @@ msgid ""
"for that opportunity. The probability will no longer update automatically as"
" the opportunity moves through each stage of the pipeline."
msgstr ""
"Si usted cambia la probabilidad, se dejarán de hacer actualizaciones "
"automáticas de probabilidad para la misma. La probabilidad ya no se "
"actualizará de forma automática conforme la oportunidad avance en el flujo."
"Al cambiar la probabilidad de forma manual eliminará sus actualizaciones "
"automáticas de probabilidad. La probabilidad ya no se actualizará en "
"automático a medida que la oportunidad avanza en el flujo. "
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:92
msgid ""
@@ -3025,10 +3025,10 @@ msgid ""
"probability of success to prioritize those that are more likely to result in"
" deals."
msgstr ""
"En el *CRM* de Odoo es posible asignar leads y oportunidades según reglas "
"específicas. Se deben crear reglas de asignación que tomen en cuenta la "
"probabilidad de éxito del lead para darle prioridad a aquellos que tienen "
"más probabilidad de ser exitosos."
"La aplicación *CRM* de Odoo puede asignar leads y oportunidades a sus "
"equipos de ventas y vendedores gracias a reglas específicas. Cree reglas de "
"asignación que tomen en cuenta la probabilidad de éxito de los leads para "
"priorizar aquellos que tienen más posibilidades de ser exitosos. "
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:106
msgid "Configure rule-based assignment"
@@ -3050,11 +3050,10 @@ msgid ""
":guilabel:`Repeatedly`, meaning Odoo will automatically trigger the "
"assignment according to the chosen time period."
msgstr ""
"Puede configurar la función de asignación según las reglas para que funcione"
" de manera :guilabel:`manual`, esto significa que el usuario tendrá que "
"activar la asignación de forma manual. También puede elegir la configuración"
" :guilabel:`repetidamente`, así Odoo activará la asignación por sí mismo "
"según el tiempo que usted le ponga."
"Es posible configurar la función Asignación por reglas para que se active de"
" forma :guilabel:`manual`, es decir, un usuario de Odoo deberá activar la "
"asignación manualmente. También puede elegir :guilabel:`repetidamente` para "
"que Odoo active la asignación en automático según el periodo que elija."
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:115
msgid ""
@@ -3062,10 +3061,10 @@ msgid ""
":guilabel:`Running` section. Then, customize how often Odoo will trigger the"
" automatic assignment in the :guilabel:`Repeat every` section."
msgstr ""
"Para configurar la asignación automática de leads, seleccione "
"guilabel:`Repetidadmente` para la sección :guilabel:`En proceso`. Después, "
"podrá personalizar qué tan seguido se activará la asignación automática de "
"leads en la sección :guilabel:`Repetir cada`."
"En la sección :guilabel:`En proceso` seleccione :guilabel:`Repetidamente` "
"para configurar la asignación automática de leads. Después podrá "
"personalizar qué tan seguido Odoo activará la asignación automática de leads"
" en la sección :guilabel:`Repetir cada`."
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1
msgid "The Rule-Based Assignment setting in CRM settings."
@@ -3078,11 +3077,11 @@ msgid ""
"the :guilabel:`Rule-Based Assignment` settings (or using the "
":guilabel:`Assign Leads` button on the sales team configuration page)."
msgstr ""
"Si configuró la asignación según las reglas para que se ejecute "
":guilabel:`Repetidamente`, todavía puede activar la asignación manualmente. "
"Para hacerlo, haga clic en el icono de flechas circulares en los ajustes de "
":guilabel:`Asignación según las reglas`, o con el botón :guilabel:`Asignar "
"leads` que se encuentra en la página de configuración del equipo de ventas."
"Si la asignación por reglas se ejecutará :guilabel:`repetidamente` también "
"podrá activarla de forma manual con el icono de flechas circulares que se "
"encuentra en los ajustes de :guilabel:`Asignación por reglas` (o con el "
"botón :guilabel:`Asignar leads` en la página de configuración del equipo de "
"ventas)."
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:128
msgid "Configure assignment rules"
@@ -3095,10 +3094,10 @@ msgid ""
" To get started, navigate to :menuselection:`CRM --> Configuration --> Sales"
" Teams`, and select a sales team."
msgstr ""
"Después, configure las *reglas de asignación* para cada equipo de ventas o "
"vendedor. Estas reglas determinan qué leads se asignan a qué persona. Para "
"empezar, vaya a :menuselection:`CRM --> Configuración --> Equipo de ventas` "
"y seleccione un equipo de ventas."
"Después configure las *reglas de asignación* para cada equipo de ventas o "
"vendedor, estas determinan los leads que Odoo le asigna a cada persona. "
"Para ello, vaya a :menuselection:`CRM --> Configuración --> Equipos de "
"ventas` y seleccione uno."
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:134
msgid ""
@@ -3705,50 +3704,46 @@ msgid "Epson TM-L90-i"
msgstr "Epson TM-L90-i"
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:35
msgid "Epson TM-T20II-i"
msgstr "Epson TM-T20II-i"
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:36
msgid "Epson TM-T70-i"
msgstr "Epson TM-T70-i"
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:37
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:36
msgid "Epson TM-T82II-i"
msgstr "Epson TM-T82II-i"
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:38
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:37
msgid "Epson TM-T83II-i"
msgstr "Epson TM-T83II-i"
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:39
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:38
msgid "Epson TM-U220-i"
msgstr "Epson TM-U220-i"
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:40
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:39
msgid "Epson TM-m10"
msgstr "Epson TM-m10"
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:41
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:40
msgid "Epson TM-P20 (Wi-Fi® model)"
msgstr "Epson TM-P20 (modelo Wi-Fi®)"
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:42
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:41
msgid "Epson TM-P60II (Receipt: Wi-Fi® model)"
msgstr "Epson TM-P60II (para recibos, modelo Wi-Fi®)"
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:43
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:42
msgid "Epson TM-P60II (Peeler: Wi-Fi® model)"
msgstr "Epson TM-P60II (modelo Peeler Wi-Fi®)"
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:44
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:43
msgid "Epson TM-P80 (Wi-Fi® model)"
msgstr "Epson TM-P80 (modelo Wi-Fi®)"
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:47
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:46
msgid "ePOS printers with IoT Box integration"
msgstr "Impresoras ePOS con integración a la caja IoT"
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:49
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:48
msgid ""
"The following printers require an :doc:`IoT Box "
"</applications/general/iot/devices/printer>` to be compatible with Odoo:"
@@ -3756,17 +3751,17 @@ msgstr ""
"Las siguientes impresoras necesitan una :doc:`caja IoT "
"</applications/general/iot/devices/printer>` para ser compatibles con Odoo:"
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:52
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:51
msgid "Epson TM-T20 family (incompatible ePOS software)"
msgstr ""
"La familia de impresoras Epson TM-T20 (el software ePOS es incompatible)"
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:53
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:52
msgid "Epson TM-T88 family (incompatible ePOS software)"
msgstr ""
"La familia de impresoras Epson TM-T88 (el software ePOS es incompatible)"
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:54
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:53
msgid "Epson TM-U220 family (incompatible ePOS software)"
msgstr ""
"La familia de impresoras Epson TM-U220 (el software ePOS es incompatible)"
@@ -4170,16 +4165,16 @@ msgid ""
"open Safari and navigate to your printer's IP address. Doing so leads to a "
"warning page;"
msgstr ""
"abra Safari y vaga a la dirección IP de su impresora. Esto lo dirigirá a una"
" página de advertencia;"
"Abra Safari y vaya a la dirección IP de su impresora. Esta acción le "
"redirigirá a una página de advertencia."
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:157
msgid ""
"on the warning page, go to :menuselection:`Show Details --> visit this "
"website --> Visit Website`, validate;"
msgstr ""
"en la página de advertencia, vaya a :menuselection:`Mostrar detalles --> "
"visite este sitio web --> Visitar sitio web, valídelo;"
"En la página de advertencia vaya a :menuselection:`Mostrar detalles --> "
"Visitar este sitio web --> Visitar sitio web` y valídelo."
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:159
msgid "reboot the printer so you can use it with any other browser."
@@ -4591,6 +4586,7 @@ msgstr ":doc:`payment_methods/terminals`."
#: ../../content/applications/sales/point_of_sale/payment_methods.rst:25
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:84
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:50
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:36
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:76
msgid ""
"Once the payment method is created, you can select it in your POS settings. "
@@ -4629,8 +4625,7 @@ msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst-1
msgid "checkbox in the settings to enable a payment terminal"
msgstr ""
"casilla de verificación en los ajustes para habilitar su terminal de pago"
msgstr "Casilla en los ajustes para habilitar la terminal de pago"
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:21
msgid "Then, follow the corresponding documentation to configure your device:"
@@ -4846,6 +4841,7 @@ msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:73
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:41
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:20
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:67
msgid "Configure the payment method"
msgstr "Configure el método de pago"
@@ -4875,6 +4871,7 @@ msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:89
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:55
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:41
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:91
msgid "Pay with a payment terminal"
msgstr "Pagar con una terminal de pago"
@@ -5115,7 +5112,6 @@ msgstr ""
"con esta integración."
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:19
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:20
msgid "Configure the Payment Method"
msgstr "Configure el método de pago"
@@ -5150,7 +5146,6 @@ msgid "Create a new payment method for the SIX payment terminal."
msgstr "Crear un nuevo método de pago para la terminal de pago de SIX."
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:37
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:44
msgid "Pay with a Payment Terminal"
msgstr "Pague con una terminal de pago"
@@ -5230,41 +5225,49 @@ msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:22
msgid ""
"First, go in the general settings of the POS app, and activate the Vantiv "
"setting."
"Enable the payment terminal in the :guilabel:`Payment Terminals` section "
":ref:`of the application settings <configuration/settings>`."
msgstr ""
"Primero vaya a los ajustes generales de la aplicación de PdV y active los "
"ajustes de Vantiv."
"Active la terminal de pago en la sección :guilabel:`Terminales de pago` de "
":ref:`los ajustes de la aplicación <configuration/settings>`."
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:28
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:25
msgid ""
"Back in :menuselection:`Point of Sale --> Configuration --> Point of Sale`, "
"go in the payments section and access your payment methods. Create a new "
"payment method for Vantiv, select the payment terminal option Vantiv, and "
"create new Vantiv credentials."
"Then, go to :menuselection:`Point of Sale --> Configuration --> Payment "
"Methods`, and :doc:`create the related payment method "
"<../../payment_methods>`. Set the journal type as :guilabel:`Bank` and "
"select :guilabel:`Vantiv` in the :guilabel:`Use a Payment Terminal` field."
msgstr ""
"Regrese a :menuselection:`Punto de venta --> Configuración --> Punto de "
"venta`, vaya a la sección de pagos y acceda a sus métodos de pagos. Cree un "
"nuevo método de pago para Vantiv, seleccione la opción de terminal de pago "
"Vantiv y cree nuevas credenciales para Vantiv."
"Después vaya a :menuselection:`Punto de venta --> Configuración --> Métodos "
"de pago` y :doc:`cree el método de pago relacionado "
"<../../payment_methods>`. Establezca el tipo de diario como "
":guilabel:`Banco` y seleccione :guilabel:`Vantiv` en el campo "
":guilabel:`Usar una terminal de pago`."
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:36
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:29
msgid ""
"To create new Vantiv credentials, fill in your merchant ID and password, "
"then save. Make sure the credentials you just created are selected, then "
"save the payment method."
"Type the name you want to give to your :guilabel:`Vantiv Credentials` and "
"click :guilabel:`Create and edit`. Enter your :guilabel:`Merchant ID` and "
":guilabel:`Merchant Password`, then click :guilabel:`Save & Close`."
msgstr ""
"Para crear nuevas credenciales de Vantiv llene su ID y contraseña de "
"comerciante y luego guarde. Asegúrese de que las credenciales que creó están"
" seleccionadas y guarde el método de pago."
"Ingrese el nombre que le quiere dear a las :guilabel:`Credenciales Vantiv` y"
" haga clic en :guilabel:`Crear y editar`. Ingrese su :guilabel:`ID de "
"comerciante` y su :guilabel:`Contraseña de comerciante` y después haga clic"
" en :guilabel:`Guardar y cerrar`."
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:46
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst-1
msgid "Vantiv payment method"
msgstr "Método de pago Vantiv"
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:43
msgid ""
"In your PoS interface, at the moment of the payment, select your Vantiv "
"payment method and… thats all."
"When processing a payment, select the related payment method. Check the "
"amount and click on :guilabel:`Send`. Once the payment is successful, the "
"status changes to :guilabel:`Payment Successful`."
msgstr ""
"Al momento del pago, en su interfaz de PdV seleccione el método de pago "
"Vantiv y... eso es todo."
"Al procesar un pago, seleccione el método de pago relacionado. Revise el "
"importe y haga clic en :guilabel:`Enviar`. En cuanto se realice el pago, el "
"estado cambia a :guilabel:`Pago exitoso`."
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:3
msgid "Worldline"
@@ -5931,9 +5934,9 @@ msgid ""
"Sale --> Configuration --> Point of sale` and select your PoS interface. "
"Under the Pricing features, select *Loyalty Program*"
msgstr ""
"Para activar la función *Programa de lealtad*, vaya a: menuselection: `Punto"
" de venta -> Configuración-> Punto de venta ` y seleccione su interfaz de "
"PdV. En las funciones de precios, seleccione * Programa de lealtad*"
"Vaya a :menuselection:`Punto de venta --> Configuración --> Punto de venta` "
"para activar la función *Programa de lealtad*. Seleccione su interfaz de PdV"
" y en las funciones de precios elija *Programa de lealtad*."
#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:19
msgid "From there you can create and edit your loyalty programs."
@@ -6019,13 +6022,13 @@ msgid ""
"dynamically using percentage discounts or more complex formulas in addition "
"to setting fixed prices."
msgstr ""
"La opción que debe de activar para tener reglas de precio simples fijas por "
"producto es :ref:`Múltiples precios por producto <pricelists/simple>`. "
"Seleccione :ref:`Reglas de precio avanzadas (descuentos, fórmulas) "
"<pricelists/advanced>` para aplicar reglas de precios a varios productos al "
"mismo tiempo y para que el cálculo de los precios sea dinámico con "
"descuentos porcentuales o fórmulas más complejas, además de configurar "
"precios fijos."
"La opción :ref:`Varios precios por producto <pricelists/simple>` es la "
"opción predeterminada de las listas de precios y establece reglas simples de"
" precios fijos por producto. Seleccione la opción :ref:`Reglas avanzadas de "
"precios (descuentos, fórmulas) <pricelists/advanced>` si desea aplicar "
"reglas de precios a varios productos a la vez, además de que le permitirá "
"calcular los precios de forma dinámica con descuentos porcentuales o "
"fórmulas más complejas y establecer precios fijos."
#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst-1
msgid "Enabling pricelists in the general P0S settings"
@@ -6060,7 +6063,7 @@ msgstr ""
#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:42
msgid "Multiple prices per product"
msgstr "Múltiples precios por producto"
msgstr "Varios precios por producto"
#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:44
msgid ""
@@ -6069,11 +6072,11 @@ msgid ""
"products or their variants depending, if necessary, on one or several "
"conditions. To add a new price rule to a pricelist:"
msgstr ""
"Cuando configura una lista de precios para que use la opción "
":guilabel:`Múltiples listas de precio por producto` podrá usar varios "
"precios fijos para diferentes productos o sus variantes dependiendo, si es "
"necesario, en una o más condiciones. Para agregar una nueva regla a una "
"lista de precios:"
"Cuando configura sus listas de precios para que usen la opción "
":guilabel:`Varios precios por producto` podrá usar distintos precios fijos "
"para diferentes productos o sus variantes tomando en cuenta una o más "
"condiciones, solo en caso de que sea necesario. Para agregar una nueva regla"
" a una lista de precios:"
#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:48
msgid ""
@@ -6145,8 +6148,8 @@ msgid ""
":guilabel:`Fixed Price` to set a new fixed price (similarly to the "
":guilabel:`Multiple prices per product` option)."
msgstr ""
":guilabel:`Precio fijo` para configurar un precio fijo nuevo (similar a la "
"opción :guilabel:`Múltiples precios por producto`."
":guilabel:`Precio fijo` para establecer un nuevo precio fijo (similar a la "
"opción :guilabel:`Varios precios por producto`)."
#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:73
msgid ""
@@ -6193,8 +6196,8 @@ msgid ""
"To have the final price end with `.99`, set the :guilabel:`Rounding Method` "
"to `1.00` and the :guilabel:`Extra Fee` to `-0.01`."
msgstr ""
"Para que el precio final termine con `.99` configure el :guilabel:`Método de"
" redondeo` a `1.00 y la :guilabel:`Tarifa adicional` a `-0.01`."
"Para que el precio final termine con `.99` configure el :guilabel:`método de"
" redondeo` a `1.00` y la :guilabel:`tarifa adicional` a `-0.01`."
#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:89
msgid ""
@@ -7351,7 +7354,7 @@ msgid ""
" products are ready` to ship all the products at once."
msgstr ""
"Defina la :guilabel:`Política de envío`. Si los productos pueden entregarse "
"por separado seleccione guilabel:`Lo antes posible` o :guilabel:`Cuando "
"por separado seleccione :guilabel:`Lo antes posible` o :guilabel:`Cuando "
"todos los productos estén listos` si desea enviar todos los productos al "
"mismo tiempo."
@@ -8884,11 +8887,11 @@ msgid ""
":guilabel:`eBay` tab or under the :guilabel:`Product name`). Select "
":guilabel:`Save` if necessary."
msgstr ""
"Para agregar un anuncio de eBay a los productos en Odoo, primero vaya a la "
":menuselection:`aplicación Ventas --> Productos --> Productos` y seleccione "
"el producto correspondiente. Haga clic en :guilabel:`Vender en eBay` (ya sea"
" en la pestaña :guilabel:`eBay` o en el :guilabel:`nombre del producto`) y "
"luego presione :guilabel:`Guardar` si es necesario."
"Para agregar un anuncio de eBay a los productos en Odoo, primero vaya a "
":menuselection:`Ventas --> Productos --> Productos` y seleccione el "
"correspondiente. Haga clic en :guilabel:`Vender en eBay` (ya sea en la "
"pestaña :guilabel:`eBay` o en el :guilabel:`nombre del producto`) y luego "
"presione :guilabel:`Guardar` si es necesario."
#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:86
msgid ""
@@ -9024,8 +9027,8 @@ msgid ""
" app --> Products --> Product` and selecting the individual product."
msgstr ""
"Haga clic en :guilabel:`Publicar artículo en eBay` en el menú superior de la"
" plantilla de producto. Puede acceder a la plantilla de producto desde la "
":menuselection:`aplicación Ventas --> Productos --> Producto`, luego deberá "
" plantilla de producto. Puede acceder a la plantilla de producto desde "
":menuselection:`Ventas --> Productos --> Producto` y luego deberá "
"seleccionar uno."
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:14
@@ -9045,8 +9048,8 @@ msgid ""
msgstr ""
"Haga clic en :guilabel:`Enlazar a un anuncio vigente de eBay` en el menú "
"superior de la plantilla de producto. Puede acceder a la plantilla de "
"producto desde la :menuselection:`aplicación Ventas --> Producto --> "
"Producto`, luego deberá seleccionar uno."
"producto desde :menuselection:`Ventas --> Producto --> Producto` y luego "
"deberá seleccionar uno."
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:22
msgid ""
@@ -9077,8 +9080,8 @@ msgid ""
"Access the product template by navigating to :menuselection:`Sales app --> "
"Products --> Product` and selecting the individual product."
msgstr ""
"Acceda a la plantilla de producto desde la :menuselection:`aplicación Ventas"
" --> Productos --> Producto`, luego seleccione el producto correspondiente."
"Acceda a la plantilla de producto desde :menuselection:`Ventas --> Productos"
" --> Producto`, luego seleccione el producto correspondiente."
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:40
msgid ""
@@ -9219,8 +9222,8 @@ msgid ""
msgstr ""
"Los códigos de barras están disponibles en la plantilla del producto, en la "
"pestaña :guilabel:`Información general`. Primero acceda a la plantilla del "
"producto, vaya a la :menuselection:`aplicación Ventas --> Productos --> "
"Producto` y seleccione el producto correspondiente."
"producto, vaya a :menuselection:`Ventas --> Productos --> Producto` y "
"seleccione el producto correspondiente."
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:99
msgid "Listing with item specifics"
@@ -9278,12 +9281,12 @@ msgid ""
"Invoices`."
msgstr ""
"Los usuarios pueden optar por crear y registrar facturas por lotes. Para "
"hacerlo, vaya a Cotizaciones en la vista de lista desde la "
":menuselection:`aplicación Ventas --> Órdenes --> Cotizaciones`. Seleccione "
"el icono de vista de lista que está ubicado en la esquina superior derecha, "
"pase el cursor sobre los iconos para abrir el nombre de cada uno. Luego, "
"seleccione las casillas a la izquierda para las cuales debe crear facturas y"
" vaya al menú :guilabel:`Acción` o al ⚙️ [icono de engranaje]. Haga clic en "
"hacerlo, vaya a Cotizaciones en la vista de lista desde "
":menuselection:`Ventas --> Órdenes --> Cotizaciones`. Seleccione el icono de"
" vista de lista que está ubicado en la esquina superior derecha, pase el "
"cursor sobre los iconos para abrir el nombre de cada uno. Luego, seleccione "
"las casillas a la izquierda para las cuales debe crear facturas y vaya al "
"menú :guilabel:`Acción` o al ⚙️ [icono de engranaje]. Haga clic en "
":guilabel:`Crear facturas`."
#: ../../content/applications/sales/sales/ebay_connector/manage.rst:124
@@ -9330,9 +9333,9 @@ msgid ""
"the :guilabel:`Amount` and enter a :guilabel:`Statement` date in. Click on "
":guilabel:`Create and edit`."
msgstr ""
"Vaya al :guilabel:`tablero de Contabilidad` desde la "
":menuselection:`aplicación Contabilidad --> Tablero --> Banco`. Cree una "
":guilabel:`nueva` transacción y establezca la :guilabel:`Etiqueta` como "
"Vaya al :guilabel:`tablero de Contabilidad` desde "
":menuselection:`Contabilidad --> Tablero --> Banco`. Cree una "
":guilabel:`nueva` transacción y establezca la :guilabel:`etiqueta` como "
"`Ventas de eBay`. Complete el :guilabel:`Importe` e ingrese una fecha de "
":guilabel:`estado de cuenta`. Haga clic en :guilabel:`Crear y editar`."
@@ -9793,9 +9796,9 @@ msgid ""
" the deletion/closure notifications configuration."
msgstr ""
"Genere un token de notificación de cierre o eliminación de cuenta de "
"mercado. Para comenzar, vaya a la :menuselection:`aplicación Ventas --> "
"Configuración --> Ajustes`. En la sección de :guilabel:`eBay` cambie el modo"
" a :guilabel:`Producción` e ingrese valores de texto aleatorios para la "
"mercado. Para comenzar, vaya a :menuselection:`Ventas --> Configuración --> "
"Ajustes`. En la sección de :guilabel:`eBay` cambie el modo a "
":guilabel:`Producción` e ingrese valores de texto aleatorios para la "
":guilabel:`Clave de certificado de producción`. Luego, haga clic en el botón"
" :guilabel:`Generar token` en la sección de :guilabel:`Notificaciones de "
"eliminación o cierre de la cuenta de eBay Marketplace`. Este token se "
@@ -9921,11 +9924,11 @@ msgid ""
"Settings`, in the :guilabel:`eBay Marketplace Account Deletion/Closure "
"Notifications` field."
msgstr ""
"A continuación, ingrese la URL del punto extremo de notificación de "
"eliminación de cuenta de mercado proporcionada por Odoo. Este punto extremo "
"HTTP se encuentra en Odoo, solo vaya a la :menuselection:`aplicación Ventas "
"--> Configuración --> Ajustes` y luego al campo :guilabel:`Notificaciones de"
" eliminación o cierre de la cuenta de eBay Marketplace`."
"Después escriba la URL del punto de conexión de notificación de eliminación "
"de cuenta de mercado proporcionada por Odoo. Este punto de conexión HTTP se "
"encuentra en Odoo, solo vaya a :menuselection:`Ventas --> Configuración --> "
"Ajustes` y luego al campo :guilabel:`Notificaciones de eliminación o cierre "
"de la cuenta de eBay Marketplace`."
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:217
msgid ""
@@ -10276,9 +10279,9 @@ msgid ""
"Configuration --> Settings --> eBay`) and paste the following credentials "
"from eBay into the corresponding fields in Odoo."
msgstr ""
"Regrese a los ajustes de eBay en Odoo (:menuselection:`aplicación Ventas -->"
" Configuración --> Ajustes --> eBay`) y pegue las siguientes credenciales de"
" eBay en los campos correspondientes en Odoo."
"Regrese a los ajustes de eBay en Odoo (:menuselection:`Ventas --> "
"Configuración --> Ajustes --> eBay`) y pegue las siguientes credenciales de "
"eBay en los campos correspondientes en Odoo."
#: ../../content/applications/sales/sales/ebay_connector/setup.rst:358
msgid "Platform"
@@ -10802,8 +10805,8 @@ msgid ""
"If :guilabel:`Delivered quantities` is chosen as the invoicing policy, an "
"invoice will **not** be able to be created."
msgstr ""
"Si elige :guilabel:`Cantidades entregadas` como política de facturación, "
"**no** podrá crear una factura."
"**No** podrá crear una factura si selecciona :guilabel:`Cantidades "
"entregadas` como política de facturación. "
#: ../../content/applications/sales/sales/invoicing/down_payment.rst:56
msgid "Request a 50% down payment"
+180 -188
View File
@@ -257,7 +257,7 @@ msgstr ""
#: ../../content/applications/services/field_service/onsite_interventions.rst:34
msgid "From helpdesk tickets"
msgstr "Desde los tickets del servicio de asistencia"
msgstr "Desde los tickets de soporte al cliente"
#: ../../content/applications/services/field_service/onsite_interventions.rst:36
msgid ""
@@ -265,29 +265,28 @@ msgid ""
"helpdesk team manage intervention requests directly. Planning field service "
"tasks from tickets speeds up your processes."
msgstr ""
"La integración con la aplicación :doc:`Servicio de asistencia <../helpdesk>`"
" su equipo de soporte podrá gestionar solicitudes de intervención "
"directamente. Además, el que pueda planear tareas del servicio externo "
"agilizará su proceso."
"La integración con la aplicación :doc:`Soporte al cliente <../helpdesk>` "
"permite que su equipo gestione las solicitudes de intervención, además de "
"que podrá planear tareas de servicio externo para agilizar sus procesos."
#: ../../content/applications/services/field_service/onsite_interventions.rst:40
msgid "Configure the helpdesk team"
msgstr "Configurar el equipo de servicio de asistencia"
msgstr "Configurar el equipo de soporte al cliente"
#: ../../content/applications/services/field_service/onsite_interventions.rst:42
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`. Select"
" a team and enable :guilabel:`Onsite Interventions`."
msgstr ""
"Vaya a :menuselection:`Servicio de asistencia --> Configuración --> Equipos "
"de servicio de asistencia`. Seleccione un equipo y elija "
":guilabel:`Intervenciones in situ`."
"Vaya a :menuselection:`Soporte al cliente --> Configuración --> Equipos de "
"soporte al cliente`. Seleccione un equipo y elija :guilabel:`Intervenciones "
"in situ`."
#: ../../content/applications/services/field_service/onsite_interventions.rst-1
msgid "Onsite interventions settings in Odoo Helpdesk"
msgstr ""
"Ajustes de las intervenciones in situ dentro del servicio de asistencia de "
"Odoo."
"Función de intervenciones presenciales en la aplicación Soporte al cliente "
"de Odoo."
#: ../../content/applications/services/field_service/onsite_interventions.rst:49
msgid ""
@@ -295,24 +294,24 @@ msgid ""
"Intervention` button. Click on it to create a new task under your field "
"service project."
msgstr ""
"Los tickets del servicio de asistencia ahora vienen con un botón para "
":guilabel:`Planear intervención`. Haga cic aquí para crear una nueva tarea "
"en el proyecto de servicio externo."
"Los tickets de soporte al cliente incluyen el botón :guilabel:`Planear "
"intervención`. Haga clic en ese botón para crear una nueva tarea en el "
"proyecto de servicio externo."
#: ../../content/applications/services/field_service/onsite_interventions.rst-1
msgid "Plan intervention from helpdesk tickets in Odoo Helpdesk"
msgstr ""
"Planeación de intervención desde los tickets del servicio de asistencia de "
"Odoo."
"Planeación de una intervención desde los tickets de soporte al cliente de la"
" aplicación Soporte al cliente de Odoo."
#: ../../content/applications/services/helpdesk.rst:8
msgid "Helpdesk"
msgstr "Servicio de asistencia"
msgstr "Soporte al cliente"
#: ../../content/applications/services/helpdesk.rst:11
msgid "`Odoo Tutorials: Helpdesk <https://www.odoo.com/slides/helpdesk-51>`_"
msgstr ""
"`Tutoriales de Odoo: Servicio de asistencia "
"`Tutoriales de Odoo: Soporte al cliente "
"<https://www.odoo.com/slides/helpdesk-51>`_"
#: ../../content/applications/services/helpdesk/advanced.rst:5
@@ -331,13 +330,12 @@ msgid ""
" returns, products, repairs, grant coupons, and even plan onsite "
"interventions from a tickets page."
msgstr ""
"Una de las cuestiones claves que tomar en cuenta conforme su empresa crece "
"es tener las herramientas adecuadas para ayudar a su servicio de asistencia "
"a registrar, rastrear y manejar los problemas que surjan de manera fácil y "
"efectiva. La aplicación de Servicio de Asistencia de Odoo le permite generar"
" notas de crédito, gestionar devoluciones, productos, reparaciones, otorgar "
"cupones e incluso planear intervenciones in situ desde la página de un "
"ticket."
"A medida que su empresa crece es indispensable que cuente con la herramienta"
" adecuada para ayudar a su equipo de soporte al cliente a registrar, dar "
"seguimiento y gestionar problemas de manera fácil y eficiente. La aplicación"
" Soporte al cliente de Odoo le permite generar notas de crédito, gestionar "
"devoluciones, productos, reparaciones, otorgar cupones e incluso planificar "
"intervenciones presenciales desde la página de un ticket."
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:11
msgid "Set up the after sales services"
@@ -349,9 +347,9 @@ msgid ""
"enable the after sales options: *Refunds, Returns, Coupons, Repairs and "
"Onsite Interventions*."
msgstr ""
"Vaya a :menuselection:`Serivicio de asistencia --> Configuración --> Equipos"
" de servicios de asistencia` y permita las opciones posventa: *reembolso, "
"devoluciones, cupones, reparaciones, intervenciones in situ*."
"Vaya a :menuselection:`Soporte al cliente --> Configuración --> Equipos de "
"soporte al cliente` y habilite las opciones posventa: *reembolso, "
"devoluciones, cupones, reparaciones e intervenciones in situ*."
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:20
msgid "Generate credit notes from tickets"
@@ -365,10 +363,10 @@ msgid ""
"you can *Post* it while still being in the *Helpdesk* app."
msgstr ""
"Puede usar una nota de crédito para reembolsar a un cliente o ajustar la "
"cantidad debida. Para esto, simplemente vaya a la página del ticket, haga "
"clic en *Reembolsar* y seleccione la *factura* correspondiente. Si hace clic"
" en *revertir* se generará una nota de crédito y puede publicarla sin salir "
"de la aplicación de *Servicio de asistencia*."
"cantidad debida. Para ello, vaya a la página del ticket, haga clic en "
"*Reembolsar* y seleccione la *factura* correspondiente. Al hacer clic en "
"*revertir* generará una nota de crédito y puede *registrarla* sin salir de "
"la aplicación *Soporte al cliente*."
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:30
msgid "Allow product returns from tickets"
@@ -393,8 +391,8 @@ msgid ""
"*Coupon*, and choose the respective one."
msgstr ""
"Primero, asegúrese de tener su *programa de cupones* planeado en la "
"aplicación de *Ventas* o *Sitio web*. Después, en el *servicio de "
"asistencia*, haga clic en *cupón* y elija el cupón respectivo."
"aplicación *Ventas* o *Sitio web*. Después, en *Soporte al cliente*, haga "
"clic en *Cupón* y elija el correspondiente."
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:48
msgid "Repairs from tickets"
@@ -457,14 +455,15 @@ msgid ""
"Helpdesk Teams` and choose the appropriate team. Then click :guilabel:`Edit`"
" and enable :guilabel:`Ticket closing` by checking the field box."
msgstr ""
"Vaya a :menuselection:`Servicio de asistencia --> Configuración --> Equipos "
"de servicio de asistencia` y seleccione el equipo correspondiente. Después "
"haga clic en :guilabel:`Editar` y active :guilabel:`Cierre de tickets` al "
"hacer clic en la casilla del campo."
"Vaya a :menuselection:`Soporte al cliente --> Configuración --> Equipos de "
"soporte al cliente` y seleccione el equipo correspondiente. Después haga "
"clic en :guilabel:`Editar` y seleccione la casilla del campo "
":guilabel:`Cierre de tickets` para habilitar la función. "
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
msgid "Ticket closing feature in Odoo Helpdesk."
msgstr "Función de cierre de tickets en Servicio de asistencia de Odoo"
msgstr ""
"Función de cierre de tickets en la aplicación Soporte al cliente de Odoo."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:19
msgid ""
@@ -472,9 +471,9 @@ msgid ""
"to the ticket pipeline by going to :menuselection:`Helpdesk --> Overview` "
"and clicking :guilabel:`Tickets` on the team's card."
msgstr ""
"Si desea determinar la fase a la que pasará el ticket una vez cerrado, vaya "
"a :menuselection:`Servicio de asistencia --> Información general` y haga "
"clic en :guilabel:`Tickets` en la tarjeta del equipo."
"Para determinar la fase a la que pasará el ticket una vez cerrado, vaya a "
":menuselection:`Soporte al cliente --> Información general` y haga clic en "
":guilabel:`Tickets` en la tarjeta del equipo."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:23
msgid ""
@@ -510,7 +509,9 @@ msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
msgid "Customer view of ticket closing in Odoo Helpdesk."
msgstr "Vista de cierre de ticket en Servicio de asistencia"
msgstr ""
"Vista del cliente al cerrar un ticket en la aplicación Soporte al cliente de"
" Odoo."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:40
msgid "Get reports on tickets closed by customers"
@@ -524,19 +525,19 @@ msgid ""
" the custom filter parameters to :guilabel:`Closed by partner` and "
":guilabel:`is true`. Finally, click :guilabel:`Apply`."
msgstr ""
"Para analizar los tickets que han cerrado los clientes, vaya a "
":menuselection:`Servicio de asistencia --> Reportes --> Tickets`. A "
"continuación, haga clic en el menú :guilabel:`Filtros` y seleccione "
":guilabel:`Añadir filtro personalizado`. A continuación, establezca los "
"parámetros del filtro personalizado en :guilabel:`Cerrado por cliente` y "
":guilabel:`verdadero`. Por último, haga clic en :guilabel:`Aplicar`."
"Para analizar los tickets cerrados por los clientes, vaya a "
":menuselection:`Soporte al cliente --> Reportes --> Tickets`, haga clic en "
"el menú :guilabel:`Filtros` y elija :guilabel:`Agregar filtro "
"personalizado`. Establezca los parámetros del filtro personalizado en "
":guilabel:`Cerrado por cliente` y :guilabel:`Verdadero`. Por último, haga "
"clic en :guilabel:`Aplicar`."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
msgid ""
"Filter for tickets closed by customers on Odoo Helpdesk's reporting page."
msgstr ""
"Filtro por tickets cerrados por los clientes en la página de Servicio de "
"asistencia."
"Filtrar por tickets cerrados por los clientes en la página de reportes de la"
" aplicación Soporte al cliente de Odoo. "
#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:3
msgid "Track and bill time"
@@ -550,12 +551,12 @@ msgid ""
"applications, customers can be charged once the work is completed, or before"
" it has even begun."
msgstr ""
"La aplicación *Servicio de asistencia* permite que los equipos puedan llevar"
" seguimiento de la cantidad de horas que usan para trabajar en un ticket y "
"La aplicación *Soporte al cliente* permite que los equipos puedan llevar "
"seguimiento de la cantidad de horas que usan para trabajar en un ticket y "
"que puedan facturar ese tiempo al cliente. A través de integraciones con las"
" aplicaciones *Ventas*, *Hojas de horas*, *Proyecto* y *Contabilidad* es "
"posible cobrarle a los clientes una vez que el trabajo se ha completado, o "
"incluso antes de que haya comenzado."
" aplicaciones *Ventas*, *Hojas de horas*, *Proyecto* y *Contabilidad* podrá "
"cobrarle a los clientes una vez que haya realizado el trabajo o incluso "
"antes de que haya comenzado."
#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:11
msgid ""
@@ -588,9 +589,9 @@ msgid ""
"Before a customer can be invoiced for support services, the *Track & Bill "
"Time* features **must** be enabled on each *Helpdesk* team individually."
msgstr ""
"Antes de que pueda facturar a un cliente por los servicios de soporte, las "
"funciones de *Seguimiento y facturación del tiempo* se **deben** activar en "
"cada equipo del *Servicio de asistencia* de forma adicional."
"Antes de que se pueda facturar a un cliente por los servicios de soporte, la"
" función *Seguimiento y facturación del tiempo* **debe** estar habilitada en"
" cada equipo de *servicio al cliente*."
#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:25
msgid "Enable track and bill time on a team"
@@ -605,9 +606,9 @@ msgid ""
" page."
msgstr ""
"Para ver y habilitar las funciones de *seguimiento y facturación del tiempo*"
" en un equipo de *Servicio de asistencia*, primero vaya a "
":menuselection:`Servicio de asistencia --> Configuración --> Equipos de "
"servicio de asistencia`. Seleccione un equipo de la lista o :doc:`cree uno "
" en un equipo de *soporte al cliente*, primero vaya a "
":menuselection:`Soporte al cliente --> Configuración --> Equipos de soporte "
"al cliente`. Seleccione un equipo de la lista o :doc:`cree uno "
"<../overview/getting_started>`. Esta acción abrirá la página de ajustes de "
"un equipo."
@@ -672,8 +673,8 @@ msgid ""
"The settings page of a Helpdesk team with the track and bill time settings "
"enabled."
msgstr ""
"La página de ajustes de un equipo de Servicio de asistencia con la función "
"de seguimiento de tiempo y facturación activada."
"La página de ajustes de un equipo de soporte al cliente con la función de "
"seguimiento de tiempo y facturación activada."
#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:57
msgid "Configure service products"
@@ -899,7 +900,7 @@ msgstr ""
#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:144
msgid "Create helpdesk ticket for prepaid services"
msgstr "Crear un ticket de servicio de asistencia para servicios prepagados"
msgstr "Crear un ticket de soporte al cliente para servicios prepagados"
#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:146
msgid ""
@@ -909,7 +910,7 @@ msgid ""
":guilabel:`Create` to create a new ticket."
msgstr ""
"Para crear un ticket para servicios prepagados, vaya a "
":menuselection:`Servicio de asistencia` y haga clic en el botón "
":menuselection:`Soporte al cliente` y haga clic en el botón "
":menuselection:`Tickets` de la tarjeta del equipo deseado para abrir su "
"flujo. Haga clic en :guilabel:`Crear` para crear un ticket."
@@ -950,16 +951,15 @@ msgstr ""
#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:162
msgid "Track hours on helpdesk ticket"
msgstr "Registrar horas en un ticket de servicio de asistencia"
msgstr "Registrar horas en un ticket de soporte al cliente"
#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:164
msgid ""
"Time spent working on a *Helpdesk* ticket is tracked on the *Timesheets* tab"
" on the specific ticket."
msgstr ""
"El tiempo que se utiliza en trabajar en un ticket de *Servicio de "
"asistencia* se registra en la pestaña *Hojas de horas* del ticket "
"específico."
"El tiempo que se utiliza en trabajar en un ticket de *soporte al cliente* se"
" registra en la pestaña *Hojas de horas* del ticket específico."
#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:166
msgid ""
@@ -988,7 +988,7 @@ msgid ""
"The timesheets tab of a Helpdesk ticket keeping track of the number of hours remaining on a\n"
"sales order."
msgstr ""
"La pestaña de hojas de horas de un ticket de Servicio de asistencia que lleva registro del número de horas restantes\n"
"La pestaña de hojas de horas de un ticket de soporte al cliente que lleva registro del número de horas restantes\n"
"en una orden de venta."
#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:179
@@ -1079,7 +1079,7 @@ msgstr ""
#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:212
msgid "Create a helpdesk ticket for time-tracked services"
msgstr ""
"Crear un ticket de servicio de asistencia para servicios de los que lleva "
"Crear un ticket de soporte al cliente para servicios de los que lleva "
"registro del tiempo"
#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:214
@@ -1088,9 +1088,9 @@ msgid ""
":menuselection:`Helpdesk app`, and select the appropriate team for which "
"these services apply."
msgstr ""
"Para registrar una entrada en las *hojas de horas* para servicios de los que"
" lleva registro del tiempo, vaya a :menuselection:`Servicio de asistencia` y"
" seleccione el equipo apropiado para el que se aplican estos servicios."
"Para registrar una entrada en las *hojas de horas* para los servicios de los"
" que lleva registro del tiempo vaya a :menuselection:`Soporte al cliente` y "
"seleccione el equipo apropiado para el que aplican estos servicios."
#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:217
msgid ""
@@ -1273,16 +1273,16 @@ msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Team` and "
"enable *Help Center*."
msgstr ""
"Vaya a :menuselection:`Servicio de asistencia --> Configuración --> Equipo "
"de servicio de asistencia` y active el *Centro de asistencia*."
"Vaya a :menuselection:`Soporte al cliente --> Configuración --> Equipo de "
"soporte al cliente` y habilite el *Centro de ayuda*."
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst-1
msgid ""
"Overview of the settings page of a helpdesk team emphasizing the help center feature in\n"
"Odoo Helpdesk"
msgstr ""
"Vista general de la página de configuración de un equipo de servicio de asistencia destacando la función del centro de ayuda en\n"
"Servicio de asistencia"
"Vista general de la página de ajustes de un equipo de soporte al cliente destacando la función del centro de ayuda en\n"
"la aplicación Soporte al cliente de Odoo. "
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:23
msgid ""
@@ -1299,8 +1299,8 @@ msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst-1
msgid "Overview of a forums settings page in Odoo Helpdesk"
msgstr ""
"Vista general de la página de ajustes del foro en la aplicación Servicio de "
"asistencia de Odoo."
"Vista general de la página de ajustes del foro en la aplicación Soporte al "
"cliente de Odoo."
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:31
msgid ""
@@ -1318,7 +1318,7 @@ msgid ""
"Helpdesk"
msgstr ""
"Vista general de la página de foros de un sitio web para mostrar los que "
"están disponibles en el Servicio de asistencia de Odoo"
"están disponibles en el soporte al cliente de Odoo."
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:38
msgid ""
@@ -1348,16 +1348,16 @@ msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and "
"enable *eLearning*."
msgstr ""
"Vaya a :menuselection:`Servicio de asistencia --> Configuración --> Equipos "
"del servicio de asistencia` y active el *eLearning*."
"Vaya a :menuselection:`Soporte al cliente --> Configuración --> Equipos de "
"soporte al cliente` y habilite *eLearning*."
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst-1
msgid ""
"Overview of the settings page of a customer care team emphasizing the feature elearning in\n"
"Odoo Helpdesk"
msgstr ""
"Vista general de la página de configuración de un equipo de cliente destacando la función del centro de ayuda en\n"
"Servicio de asistencia"
"Vista general de la página de ajustes de un equipo de atención al cliente destacando la función de eLearning\n"
"en la aplicación Soporte al cliente de Odoo. "
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:61
msgid ""
@@ -1370,8 +1370,8 @@ msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst-1
msgid "View of a course being published for Odoo Helpdesk"
msgstr ""
"Vista la publicación de un curso desde la aplicación Servicio de asistencia "
"de Odoo"
"Vista de la publicación de un curso desde la aplicación Soporte al cliente "
"de Odoo."
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:67
msgid ""
@@ -1384,8 +1384,8 @@ msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst-1
msgid "View of the elearning applications dashboard for Odoo Helpdesk"
msgstr ""
"Vista del tablero de aplicaciones de eLearning en Servicio de asistencia de "
"Odoo"
"Vista del tablero de aplicaciones de eLearning en la aplicación Soporte al "
"cliente de Odoo. "
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:73
msgid "Todo"
@@ -1410,11 +1410,10 @@ msgid ""
"scheme where you can organize multiple teams with their customized pipeline,"
" visibilities settings, and ticket traceability is essential."
msgstr ""
"Los equipos del servicio de asistencia apoyan a sus clientes con consultas o"
" errores que puedan surgir al usar su producto o servicio. Por lo tanto, es "
"esencial contar con un esquema en el que pueda organizar varios equipos con "
"sus flujos personalizados, ajustes de visibilidad y la trazabilidad del "
"ticket."
"Los equipos de soporte al cliente ayudan con consultas o errores que puedan "
"surgir al usar su producto o servicio. Por lo tanto, es muy importante que "
"cuente con un esquema en el que pueda organizar varios equipos con flujos "
"personalizados, ajustes de visibilidad y trazabilidad de los tickets."
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:10
msgid "Set up teams"
@@ -1425,8 +1424,8 @@ msgid ""
"To modify or create teams, go to :menuselection:`Helpdesk --> Configuration "
"--> Helpdesk Teams`."
msgstr ""
"Para modificar o crear equipos vaya a :menuselection:`Servicio de asistencia"
" --> Configuración --> Equipos del servicio de asistencia`."
"Para modificar o crear equipos vaya a :menuselection:`Soporte al cliente -->"
" Configuración --> Equipos de soporte al cliente`."
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:14
msgid ""
@@ -1441,8 +1440,8 @@ msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1
msgid "View of the helpdesk teams page in Odoo Helpdesk"
msgstr ""
"Vista de la página de equipos del servicio de asistencia en la aplicación "
"Servicio de asistencia de Odoo."
"Vista de la página de equipos de soporte al cliente en la aplicación Soporte"
" al cliente de Odoo."
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:21
msgid "Teams productivity and visibility"
@@ -1490,8 +1489,8 @@ msgid ""
"View of a helpdesk team settings page emphasizing the productivity and visibility features\n"
"in Odoo Helpdesk"
msgstr ""
"Vista de la página de ajustes del equipo de servicio de asistencia, se destacan las funciones de productividad y visibilidad \n"
"en la aplicación Servicio de asistencia de Odoo."
"Vista de la página de ajustes del equipo de soporte al cliente, se destacan las funciones de productividad y visibilidad \n"
"en la aplicación Soporte al cliente de Odoo."
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:40
msgid ""
@@ -1527,18 +1526,17 @@ msgid ""
"Stages`. Then, create and/or edit stages as you need and set specific teams "
"to use certain stages under *Team*."
msgstr ""
"Para establecer etapas, vaya a :menuselection:`Servicio de asistencia--> "
"Configuración --> Etapas`. Posteriormente, cree y/o edite las etapas que "
"necesite y establezca equipos específicos para que usen ciertas etapas en "
"*Equipo*."
"Para establecer etapas, vaya a :menuselection:`Soporte al cliente --> "
"Configuración --> Etapas`. Después cree o edite las etapas que necesite y, "
"en *Equipo*, establezca equipos específicos para que las usen. "
#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1
msgid ""
"View of a stages setting page emphasizing the option to add teams in Odoo "
"Helpdesk"
msgstr ""
"Vista de la página de ajustes de una etapa destacando la opción de añadir "
"equipos en Servicio de asistencia"
"Vista de la página de ajustes de equipos de soporte al cliente, destacan las"
" opciones para agregar equipos en la aplicación Soporte al cliente de Odoo. "
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:55
msgid ""
@@ -1554,8 +1552,7 @@ msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1
msgid "View of a teams kanban view in Odoo Helpdesk"
msgstr ""
"Vista de kanban de un equipo en la aplicación de Servicio de asistencia de "
"Odoo"
"Vista de kanban de un equipo en la aplicación Soporte al cliente de Odoo."
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:64
msgid ":doc:`/applications/general/users`"
@@ -1572,11 +1569,10 @@ msgid ""
" a customers decision and open space for feedback that can help you improve"
" the quality of your services."
msgstr ""
"Permita a los clientes calificar su experiencia con sus equipos de Servicio "
"de asistencia para fortalecer su credibilidad y ganarse su confianza. Las "
"reseñas también pueden influir en la decisión de un cliente y tener un "
"espacio abierto a la retroalimentación puede ayudarle a mejorar la calidad "
"de sus servicios."
"Permita que los clientes califiquen la experiencia que tuvieron con sus "
"equipos de soporte para fortalecer su credibilidad y ganarse su confianza. "
"Las reseñas también pueden influir en la decisión de un cliente y aceptar "
"retroalimentación puede ayudarle a mejorar la calidad de sus servicios."
#: ../../content/applications/services/helpdesk/overview/ratings.rst:12
msgid ""
@@ -1584,19 +1580,18 @@ msgid ""
"enable *Ratings on tickets*. The feature automatically adds a default email "
"template on the non-folded *closing stage(s)* of that team."
msgstr ""
"Vaya a :menuselection:`Servicio de asistencia --> Configuración --> Equipos "
"de servicio de asistencia` y habilite la función de *Calificación de "
"tickets*. Esta función agrega automáticamente una plantilla de correo "
"electrónico determinada en la *etapa o etapas de cierre* sin plegar de ese "
"equipo."
"Vaya a :menuselection:`Soporte al cliente --> Configuración --> Equipos de "
"soporte al cliente` y habilite la función *Calificación de tickets*. Esta "
"función agrega una plantilla de correo electrónico predeterminada de manera "
"automática a la *etapa o etapas de cierre* sin plegar de ese equipo."
#: ../../content/applications/services/helpdesk/overview/ratings.rst-1
msgid ""
"Overview of the settings page of a helpdesk team emphasizing the rating on ticket feature\n"
"in Odoo Helpdesk"
msgstr ""
"Vista general de la página de ajustes de un equipo de servicio de asistencia, con énfasis en la función de calificación de ticket\n"
"en la aplicación de Servicio de asistencia de Odoo"
"Vista general de la página de ajustes de un equipo de soporte al cliente, destaca la función de calificación de ticket\n"
"en la aplicación Soporte al cliente de Odoo."
#: ../../content/applications/services/helpdesk/overview/ratings.rst:21
msgid ""
@@ -1604,18 +1599,18 @@ msgid ""
"the Kanban view of your helpdesk team and click on *Settings*, then on *Edit"
" Stage*."
msgstr ""
"Para editar la plantilla de correo electrónico y la etapa o etapas "
"establecidas como de cierre, vaya a la vista de kanban de su equipo de "
"Servicio de asistencia y haga clic en *Ajustes* y luego en *Editar etapa*."
"Para editar la plantilla de correo electrónico y la etapa establecida como "
"de cierre, vaya a la vista de kanban de su equipo de soporte al cliente, "
"haga clic en *Ajustes* y luego en *Editar etapa*."
#: ../../content/applications/services/helpdesk/overview/ratings.rst-1
msgid ""
"Overview of a helpdesk team kanban view emphasizing the menu edit stage in "
"Odoo Helpdesk"
msgstr ""
"Vista general de la vista de kanban de un equipo de servicio de asistencia, "
"con énfasis en la opción de menú \"Editar etapa\" en la aplicación de "
"Servicio de asistencia"
"Vista general de la vista de kanban de un equipo de soporte al cliente, "
"destaca la opción de menú \"Editar etapa\" en la aplicación Soporte al "
"cliente de Odoo. "
#: ../../content/applications/services/helpdesk/overview/ratings.rst:28
msgid ""
@@ -1630,7 +1625,7 @@ msgid ""
"View of a standard helpdesk customer review email template for Odoo Helpdesk"
msgstr ""
"Vista de una plantilla estándar de correo electrónico de reseña de cliente "
"de servicio de asistencia en la aplicación de Servicio de asistencia de Odoo"
"de soporte al cliente en la aplicación Soporte al cliente de Odoo. "
#: ../../content/applications/services/helpdesk/overview/ratings.rst:35
msgid ""
@@ -1650,19 +1645,18 @@ msgid ""
"enable *Display Rating on Customer Portal*. Now, by clicking on the helpdesk"
" teams name on their ticket, customers can see its ratings."
msgstr ""
"Vaya a :menuselection:`Servicio de asistencia --> Configuración --> Equipos "
"de Servicio de asistencia` y habilite la función *Mostrar las valoraciones "
"en el portal del cliente*. Ahora, al hacer clic en el nombre del equipo de "
"Servicio de asistencia en el ticket, los clientes pueden ver sus "
"valoraciones."
"Vaya a :menuselection:`Soporte al cliente --> Configuración --> Equipos de "
"soporte al cliente` y habilite la función *Mostrar las valoraciones en el "
"portal del cliente*. Los clientes podrán ver su calificación al hacer clic "
"en el nombre del equipo de soporte al cliente en el ticket."
#: ../../content/applications/services/helpdesk/overview/ratings.rst-1
msgid ""
"View of the helpdesk ticket from a users portal emphasizing the link to the helpdesk team\n"
"in Odoo Helpdesk"
msgstr ""
"Vista del ticket de servicio de asistencia del portal de usuario, con énfasis en el enlace del equipo de servicio de asistencia\n"
"en la aplicación de Servicio de asistencia de Odoo"
"Vista del ticket de soporte al cliente del portal de usuario, destaca el enlace al equipo de soporte al cliente\n"
"en la aplicación Soporte al cliente de Odoo."
#: ../../content/applications/services/helpdesk/overview/ratings.rst:51
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:88
@@ -1697,18 +1691,17 @@ msgid ""
"enable the following features as you want them to be available to your "
"users."
msgstr ""
"Vaya a :menuselection:`Servicio de asistencia --> Configuración --> Equipos "
"de servicio de asistencia`, y habilite las siguientes funciones ya que desea"
" que estén disponibles para sus usuarios."
"Vaya a :menuselection:`Soporte al cliente --> Configuración --> Equipos de "
"soporte al cliente` y habilite las siguientes funciones para que los "
"usuarios puedan acceder a ellas. "
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1
msgid ""
"View of a helpdesk teams setting page emphasizing the channels options in "
"Odoo Helpdesk"
msgstr ""
"Vista de la página de ajustes de equipos de servicio de asistencia, con "
"énfasis en las opciones de canales en la aplicación de Servicio de "
"asistencia de Odoo"
"Vista de la página de ajustes de equipos de soporte al cliente, destacan las"
" opciones de canales en la aplicación Soporte al cliente de Odoo. "
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:21
msgid "Email Alias"
@@ -1739,8 +1732,8 @@ msgid ""
"View of the settings page of a helpdesk team emphasizing the email alias feature\n"
"in Odoo Helpdesk"
msgstr ""
"Vista de la página de ajustes de un equipo de servicio de asistencia, con énfasis en la función de seudónimo de correo electrónico\n"
"en la aplicación de Servicio de asistencia de Odoo"
"Vista de la página de ajustes de un equipo de soporte al cliente, destaca la función de seudónimo de correo electrónico\n"
"en la aplicación Soporte al cliente de Odoo. "
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:35
msgid ""
@@ -1778,8 +1771,8 @@ msgid ""
"View of the settings page of a helpdesk team emphasizing the Go to Website button in\n"
"Odoo Helpdesk"
msgstr ""
"Vista de la página de ajustes de un equipo de servicio de asistencia, con énfasis en el botón de Ir al sitio web\n"
"en la aplicación de Servicio de asistencia de Odoo"
"Vista de la página de ajustes de un equipo de soporte al cliente, destaca el botón Ir al sitio web\n"
"en la aplicación Soporte al cliente de Odoo. "
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:49
msgid ""
@@ -1792,8 +1785,8 @@ msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1
msgid "View of the website form to submit a ticket for Odoo Helpdesk"
msgstr ""
"Vista del formulario de sitio web para enviar un ticket a la aplicación de "
"Servicio de asistencia de Odoo"
"Vista del formulario de sitio web para enviar un ticket a la aplicación "
"Soporte al cliente de Odoo. "
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:56
msgid "Live Chat"
@@ -1804,26 +1797,26 @@ msgid ""
"Through live interactions with your website visitors, helpdesk tickets can "
"be instantly created and redirected to the right person."
msgstr ""
"Mediante las interacciones en vivo con los visitantes de su sitio web, los "
"tickets de Servicio de asistencia se pueden crear y redireccionar a la "
"persona adecuada de forma instantánea."
"Las interacciones en vivo con los visitantes de su sitio web le permiten "
"crear tickets de soporte al cliente se pueden crear y redireccionarlos a la "
"persona adecuada al instante. "
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:61
msgid ""
"Click on your helpdesk team's name - for the example below: *Customer Care* "
"- and :doc:`set up your channel </applications/websites/livechat>`."
msgstr ""
"Haga clic en el nombre de su equipo de Servicio de asistencia, por ejemplo: "
"*Atención al cliente* y :doc:`configure su canal "
"</applications/websites/livechat>`."
"Haga clic en el nombre de su equipo de soporte al cliente, en el siguiente "
"ejemplo es *Atención al cliente*, y :doc:`configure su canal "
"</applications/websites/livechat/overview/get_started>`."
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1
msgid ""
"View of the settings page of a helpdesk team emphasizing the live chat features and links\n"
"in Odoo Helpdesk"
msgstr ""
"Vista de la página de ajustes de un equipo de servicio de asistencia, con énfasis en la función de chat en vivo y sus enlaces\n"
"en la aplicación de Servicio de asistencia"
"Vista de la página de ajustes de un equipo de soporte al cliente, destaca la función de chat en vivo y sus enlaces\n"
"en la aplicación Soporte al cliente de Odoo. "
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:68
msgid ""
@@ -1831,8 +1824,8 @@ msgid ""
"</applications/websites/livechat/responses>` */helpdesk "
"(subject_of_ticket)*."
msgstr ""
"Ahora sus operadores podrán crear tickets gracias al :doc:`comando "
"</applications/websites/livechat/responses>` */serviciodeasistencia "
"Ahora los operadores pueden crear tickets con el :doc:`comando "
"</applications/websites/livechat/responses>` */helpdesk "
"(asunto_del_ticket)*."
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:72
@@ -1863,8 +1856,8 @@ msgstr "3 estrellas = *Urgente*"
msgid ""
"View of a teams kanban view and the prioritized tasks in Odoo Helpdesk"
msgstr ""
"Vista de kanban del equipo y sus tareas con prioridad en la aplicación de "
"Servicio de asistencia de Odoo"
"Vista de kanban del equipo y sus tareas prioritarias en la aplicación "
"Soporte al cliente de Odoo. "
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:87
#: ../../content/applications/services/helpdesk/overview/reports.rst:60
@@ -1898,8 +1891,8 @@ msgstr "Casos"
#: ../../content/applications/services/helpdesk/overview/reports.rst:12
msgid "Some examples of the reports Odoo Helpdesk can generate include:"
msgstr ""
"Algunos ejemplos de los reportes que la aplicación Servicio de asistencia "
"puede generar son:"
"Estos son algunos ejemplos de los reportes que puede generar con la "
"aplicación Soporte al cliente de Odoo:"
#: ../../content/applications/services/helpdesk/overview/reports.rst:14
msgid "The number of tickets *grouped by* team and ticket type."
@@ -1925,8 +1918,8 @@ msgstr ""
msgid ""
"View of a helpdesk ticket analysis by team and ticket type in Odoo Helpdesk"
msgstr ""
"Vista del análisis de tickets de servicio de asistencia por equipo y por "
"tipo de ticket en la aplicación de Servicio de asistencia"
"Vista del análisis de tickets de soporte al cliente por equipo y por tipo de"
" ticket en la aplicación Soporte al cliente de Odoo. "
#: ../../content/applications/services/helpdesk/overview/reports.rst:25
msgid "The number of tickets closed per day, per team."
@@ -1946,8 +1939,8 @@ msgstr ""
msgid ""
"View of a helpdesk ticket analysis by team and close date in Odoo Helpdesk"
msgstr ""
"Vista del análisis de tickets de servicio de asistencia por equipo y por "
"fecha de cierre en la aplicación de Servicio de asistencia de Odoo"
"Vista del análisis de tickets de soporte al cliente por equipo y por fecha "
"de cierre en la aplicación Soporte al cliente de Odoo. "
#: ../../content/applications/services/helpdesk/overview/reports.rst:35
msgid ""
@@ -1979,8 +1972,8 @@ msgid ""
"View of helpdesk ticket analysis of the hours to close by ticket type and team in\n"
"Odoo Helpdesk"
msgstr ""
"Vista del análisis de tickets de servicio de asistencia de las horas para cerrar el ticket por tipo de ticket y equipo\n"
"en la aplicación de Servicio de asistencia"
"Vista del análisis de tickets de soporte al cliente de las horas para cerrar el ticket por tipo de ticket y equipo\n"
"en la aplicación Soporte al cliente de Odoo. "
#: ../../content/applications/services/helpdesk/overview/reports.rst:48
msgid "Save filters"
@@ -2001,8 +1994,8 @@ msgid ""
"View of helpdesk ticket analysis emphasizing the option to add a filter as a favorite one\n"
"in Odoo Helpdesk"
msgstr ""
"Vista del análisis de tickets de servicio de asistencia, con énfasis en la opción de agregar un filtro como favorito\n"
"en la aplicación de Servicio de asistencia"
"Vista del análisis de tickets de soporte al cliente, destaca la opción de agregar un filtro como favorito\n"
"en la aplicación Soporte al cliente de Odoo. "
#: ../../content/applications/services/helpdesk/overview/reports.rst:59
msgid ":doc:`receiving_tickets`"
@@ -2030,8 +2023,8 @@ msgid ""
"The *SLA Policies* feature **must** be enabled on newly-created *Helpdesk* "
"teams."
msgstr ""
"La función *Políticas de SLA* **debe** estar habilitada en los equipos "
"recién creados del *Servicio de asistencia*."
"La función *Políticas de SLA* **debe** estar habilitada en los equipos de "
"*soporte al cliente* recién creados."
#: ../../content/applications/services/helpdesk/overview/sla.rst:12
msgid ""
@@ -2039,8 +2032,8 @@ msgid ""
"Configuration --> Helpdesk Teams`. Click on a team to open that team's "
"configuration page."
msgstr ""
"Para habilitar la función, vaya a :menuselection:`Servicio de asistencia -->"
" Configuración --> Equipos de servicio de asistencia` y haga clic en uno "
"Para habilitar la función, vaya a :menuselection:`Soporte al cliente --> "
"Configuración --> Equipos de soporte al cliente` y haga clic en uno para "
"abrir la página de configuración de ese equipo."
#: ../../content/applications/services/helpdesk/overview/sla.rst:15
@@ -2059,8 +2052,8 @@ msgstr ""
msgid ""
"The configuration page for a Helpdesk team with the SLA feature enabled."
msgstr ""
"La página de configuración de un equipo de Servicio de asistencia con la "
"función SLA habilitada."
"La página de configuración de un equipo de soporte al cliente con la función"
" SLA habilitada."
#: ../../content/applications/services/helpdesk/overview/sla.rst:24
msgid "Create SLA policy"
@@ -2071,8 +2064,8 @@ msgid ""
"To create a new policy, go to :menuselection:`Helpdesk app --> Configuration"
" --> SLA Policies`, and click :guilabel:`Create`."
msgstr ""
"Para crear una nueva política vaya a :menuselection:`Servicio de asistencia "
"--> Configuración --> Políticas SLA` y haga clic en :guilabel:`Crear`."
"Para crear una nueva política vaya a :menuselection:`Soporte al cliente --> "
"Configuración --> Políticas SLA` y haga clic en :guilabel:`Crear`."
#: ../../content/applications/services/helpdesk/overview/sla.rst:29
msgid ""
@@ -2081,8 +2074,8 @@ msgid ""
"Policies` smart button at the top of the team's settings page, and click "
":guilabel:`Create`."
msgstr ""
"Otra forma de hacerlo es ir a :menuselection:`Servicio de asistencia --> "
"Configuración --> Equipos de servicio de asistencia` y hacer clic en uno. "
"Otra forma de hacerlo es ir a :menuselection:`Soporte al cliente --> "
"Configuración --> Equipos de soporte al cliente` y hacer clic en uno. "
"Después haga clic en el botón inteligente :guilabel:`Políticas SLA` ubicado "
"en la parte superior de la página de ajustes del equipo y haga clic en "
":guilabel:`Crear`."
@@ -2128,8 +2121,8 @@ msgid ""
":guilabel:`Helpdesk Team`: a policy can only be applied to one team. *This "
"field is required.*"
msgstr ""
":guilabel:`Equipo de servicio de asistencia`: la política solo se puede "
"aplicar a un equipo. *Este campo es obligatorio*."
":guilabel:`Equipo de soporte al cliente`: La política solo se puede aplicar "
"a un equipo. *Este campo es obligatorio.*"
#: ../../content/applications/services/helpdesk/overview/sla.rst:48
msgid ""
@@ -2294,7 +2287,7 @@ msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:105
msgid "A Helpdesk ticket with two SLA tags attached."
msgstr "Un ticket de Servicio de asistencia con dos etiquetas SLA adjuntas."
msgstr "Un ticket de soporte al cliente con dos etiquetas SLA adjuntas."
#: ../../content/applications/services/helpdesk/overview/sla.rst:105
msgid ""
@@ -2302,9 +2295,9 @@ msgid ""
" has been satisfied, so the tag has turned green. The other policy is in "
"progress."
msgstr ""
"Este ticket de Servicio de asistencia tiene dos políticas SLA aplicadas. Una"
" de las políticas se ha cumplido, así que su etiqueta ahora es de color "
"verde. La otra política está en curso."
"Este ticket de soporte al cliente tiene dos políticas SLA aplicadas. Una de "
"las políticas se ha cumplido, así que su etiqueta ahora es de color verde. "
"La otra política está en curso."
#: ../../content/applications/services/helpdesk/overview/sla.rst:109
msgid ""
@@ -2319,8 +2312,7 @@ msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:0
msgid "A Helpdesk ticket with emphasis on the deadline field."
msgstr ""
"Un ticket de Servicio de asistencia. El campo de fecha límite está "
"destacado."
"Un ticket de soporte al cliente. El campo de fecha límite está destacado."
#: ../../content/applications/services/helpdesk/overview/sla.rst:117
msgid ""
@@ -2352,7 +2344,7 @@ msgstr ""
"El reporte de *análisis del estado del SLA* lleva el registro de qué tan "
"rápido se cumple un :abbr:`SLA (Acuerdo de nivel de servicio)`, así como el "
"rendimiento de cada miembro del equipo. Puede acceder al reporte y a su "
"respectiva tabla dinámica desde :menuselection:`Servicio de asistencia --> "
"respectiva tabla dinámica desde :menuselection:`Soporte al cliente --> "
"Reportes --> Análisis del estado del SLA`."
#: ../../content/applications/services/helpdesk/overview/sla.rst:131
+6 -6
View File
@@ -52,12 +52,12 @@ msgid ""
"subscription amount significantly (or switch you from a free account to a "
"paying one on our online platform)."
msgstr ""
"Odoo puede ser muchas cosas (ERP, CMS, aplicación CRM, comercio electrónico,"
" etc.) pero *no* es un teléfono inteligente. Debe tomar precauciones al "
"añadir/eliminar características (especialmente Aplicaciones) en su base de "
"datos ya que esto puede impactar en el monto de la suscripción "
"significativamente (o cambiarle de una cuenta gratuita a una de paga en "
"nuestra plataforma en línea)."
"Odoo puede ser muchas cosas (ERP, CMS, una aplicación CRM, backend para "
"comercio electrónico, etc.) pero *no* es un teléfono inteligente. Debe tener"
" ciertas precauciones al agregar o eliminar funciones (en especial "
"Aplicaciones) a su base de datos, ya que esto puede afectar el monto de la "
"suscripción de forma considerable (o cambiar su cuenta gratuita por una de "
"paga en nuestra plataforma en línea)."
#: ../../content/applications/settings/users_and_features.rst:18
msgid ""
+15 -17
View File
@@ -931,16 +931,15 @@ msgstr "Ejemplos de los campos de fecha y hora con diferentes widgets"
#: ../../content/applications/studio/fields.rst:198
msgid "Checkbox (`boolean`)"
msgstr "Casilla de verificación (`boolean`)"
msgstr "Casilla (`boolean`)"
#: ../../content/applications/studio/fields.rst:200
msgid ""
"The :guilabel:`Checkbox` field is used when a value should only be true or "
"false, indicated by checking or unchecking a checkbox."
msgstr ""
"El campo :guilabel:`Casilla de verificación` se utiliza cuando un valor solo"
" puede ser verdadero o falso, y se indica al marcar o desmarcar una casilla "
"de verificación."
"El campo :guilabel:`Casilla` se utiliza cuando un valor solo puede ser "
"verdadero o falso y esto se indica al seleccionar o desmarcar una casilla."
#: ../../content/applications/studio/fields.rst:203
msgid ""
@@ -960,7 +959,7 @@ msgstr ""
#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Checkbox fields with different widgets"
msgstr "Ejemplos de campos de casilla de verificación con diferentes widgets"
msgstr "Ejemplos de campos de casilla con diferentes widgets"
#: ../../content/applications/studio/fields.rst:215
msgid "Selection (`selection`)"
@@ -1349,8 +1348,8 @@ msgstr "Diagrama que muestra relaciones many2many"
msgid ""
":guilabel:`Checkboxes`: users can select several values using checkboxes."
msgstr ""
":guilabel:`Casillas de verificación`: los usuarios pueden seleccionar varios"
" valores utilizando las casillas de verificación."
":guilabel:`Casillas`: Los usuarios pueden seleccionar varios valores con las"
" casillas."
#: ../../content/applications/studio/fields.rst:414
msgid ""
@@ -1378,12 +1377,12 @@ msgid ""
"fields/many2many>`."
msgstr ""
"El campo :guilabel:`Etiquetas` se utiliza para mostrar varios valores de "
"otro modelo, también conocidas como *etiquetas*. Este tipo de campo es un "
"campo :ref:`Many2Many <studio/fields/relational-fields/many2many>` que "
"cuenta con el widget :guilabel:`Etiquetas` seleccionado de forma "
"predeterminada. Por lo tanto, los widgets :guilabel:`Casillas de "
"verificación` y :guilabel:`Many2Many` tienen los mismos propósitos que los "
"descritos en :ref:`Many2Many <studio/fields/relational-fields/many2many>`."
"otro modelo con forma redonda también conocidos como *etiquetas*. Este tipo "
"de campo es un :ref:`campo Many2Many <studio/fields/relational-"
"fields/many2many>` que cuenta con el widget :guilabel:`Etiquetas` "
"seleccionado de forma predeterminada. Por lo tanto, los widgets "
":guilabel:`Casillas` y :guilabel:`Many2Many` tienen la misma finalidad que "
"la descrita en :ref:`Many2Many <studio/fields/relational-fields/many2many>`."
#: ../../content/applications/studio/fields.rst:430
msgid ""
@@ -3069,10 +3068,9 @@ msgid ""
" :ref:`Checkbox field <studio/fields/simple-fields/checkbox>` that specifies"
" if the event lasts the whole day."
msgstr ""
"Para mostrar los eventos que duran todo un día en la parte superior del "
"calendario, seleccione la :ref:`Casilla de verificación "
"<studio/fields/simple-fields/checkbox>` que especifica que el evento dura "
"todo el día."
"Para que los eventos que duran todo el día aparezcan en la parte superior "
"del calendario seleccione la :ref:`casilla <studio/fields/simple-"
"fields/checkbox>` que especifica la duración correspondiente. "
#: ../../content/applications/studio/views.rst:223
msgid ""
+13 -13
View File
@@ -1427,11 +1427,11 @@ msgstr "**/help**: muestra un mensaje de ayuda."
#: ../../content/applications/websites/livechat/responses.rst:14
msgid "**/helpdesk**: creates a helpdesk ticket."
msgstr "**/helpdesk**: crea un ticket de servicio de asistencia."
msgstr "**/helpdesk**: crea un ticket de soporte al cliente."
#: ../../content/applications/websites/livechat/responses.rst:15
msgid "**/helpdesk_search**: searches for a helpdesk ticket."
msgstr "**/helpdesk_search**: busca un ticket de servicio de asistencia."
msgstr "**/helpdesk_search**: busca un ticket de soporte al cliente. "
#: ../../content/applications/websites/livechat/responses.rst:16
msgid "**/history**: shows the last 15 visited pages."
@@ -1451,10 +1451,10 @@ msgid ""
"database and the option *Live Chat* under :menuselection:`Helpdesk --> "
"Configuration --> Helpdesk Teams` is enabled."
msgstr ""
"- Para *tickets de servicio de asistencia*: asegúrese de que la aplicación "
"está instalada en su base de datos y que la opción de *Chat en vivo* en "
":menuselection:`Servicio de asistencia --> Configuración --> Equipos del "
"servicio de asistencia` esté habilitada."
"- Para *tickets de soporte al cliente*: asegúrese de que la aplicación está "
"instalada en su base de datos y que la opción *Chat en vivo* en "
":menuselection:`Soporte al cliente --> Configuración --> Equipos de soporte "
"al cliente` esté habilitada."
#: ../../content/applications/websites/livechat/responses.rst:0
msgid ""
@@ -1474,17 +1474,17 @@ msgstr ""
msgid ""
"View of the chat window with a helpdesk ticket created in Odoo Live Chat"
msgstr ""
"Vista de la ventana de chat abierta con un ticket de servicio de asistencia "
"creado en el Chat en vivo de Odoo"
"Vista de la ventana de chat con un ticket de soporte al cliente creado en la"
" aplicación Chat en vivo de Odoo. "
#: ../../content/applications/websites/livechat/responses.rst:33
msgid ""
"Helpdesk tickets created from the chat automatically add the conversation as"
" a description of the ticket. The same goes for the creation of a lead."
msgstr ""
"Los tickets de servicio de asistencia que se crearon a partir del chat "
"agregan automáticamente la conversación como la descripción del ticket. Lo "
"mismo pasa en la creación de leads."
"Los tickets de soporte al cliente creados con el chat agregan la "
"conversación como la descripción del ticket de forma automática, lo mismo "
"pasa al crear un lead."
#: ../../content/applications/websites/livechat/responses.rst:37
msgid "Send canned responses"
@@ -3047,8 +3047,8 @@ msgid ""
"To manage specific prices by websites, you can activate *Multiple Sales "
"Prices per Product* in Website settings."
msgstr ""
"Para gestionar precios específicos por sitio web, puede activar la función "
"*múltiples precios por producto* en los ajustes de Sitio web."
"Si desea gestionar precios específicos por sitio web puede activar la "
"función *Varios precios por producto* en los ajustes de Sitio web."
#: ../../content/applications/websites/website/configuration/multi_website.rst:268
msgid ""
File diff suppressed because it is too large Load Diff
+4 -3
View File
@@ -10,6 +10,7 @@
# Emmanuel Chaumery, 2024
# Wil Odoo, 2024
# Jolien De Paepe, 2024
# Manon Rondou, 2024
#
#, fuzzy
msgid ""
@@ -18,7 +19,7 @@ msgstr ""
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-05-28 08:57+0000\n"
"PO-Revision-Date: 2024-04-04 12:26+0000\n"
"Last-Translator: Jolien De Paepe, 2024\n"
"Last-Translator: Manon Rondou, 2024\n"
"Language-Team: French (https://app.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -612,11 +613,11 @@ msgstr ""
#: ../../content/applications/essentials/activities.rst:238
msgid ":doc:`/applications/productivity/discuss`"
msgstr ""
msgstr ":doc:`/applications/productivity/discuss`"
#: ../../content/applications/essentials/activities.rst:239
msgid ":doc:`/applications/productivity/discuss/team_communication`"
msgstr ""
msgstr ":doc:`/applications/productivity/discuss/team_communication`"
#: ../../content/applications/essentials/contacts.rst:3
msgid "Contacts"
File diff suppressed because it is too large Load Diff
+80 -20
View File
@@ -18,15 +18,16 @@
# Renaud de Colombel <rdecolombel@sgen.cfdt.fr>, 2024
# Jolien De Paepe, 2024
# Wil Odoo, 2024
# Manon Rondou, 2024
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-05-28 08:57+0000\n"
"POT-Creation-Date: 2024-08-20 14:22+0000\n"
"PO-Revision-Date: 2021-11-02 08:47+0000\n"
"Last-Translator: Wil Odoo, 2024\n"
"Last-Translator: Manon Rondou, 2024\n"
"Language-Team: French (https://app.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -1986,31 +1987,23 @@ msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:36
msgid ""
"Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the "
"platform, and then input `https://<odoo base url>/microsoft_outlook/confirm`"
" in the :guilabel:`URL` field. The Odoo base URL is the canonical domain at "
"which your Odoo instance can be reached in the URL field."
"platform, and then input `https://<web base url>/microsoft_outlook/confirm` "
"in the :guilabel:`URL` field. The `web.base.url` is subject to change "
"depending on the URL used to log in to the database."
msgstr ""
"Dans la section :guilabel:`URL de redirection`, sélectionnez :guilabel:`Web`"
" en tant que plateforme et ensuite saisissez `https://<odoo base "
"url>/microsoft_outlook/confirm` dans le champ :guilabel:`URL`. L'URL de base"
" d'Odoo est le domaine canonique auquel votre instance Odoo peut être "
"atteinte dans le champ URL."
#: ../../content/applications/general/email_communication/azure_oauth.rst:41
msgid ""
"*mydatabase.odoo.com*, where *mydatabase* is the actual prefix of the "
"database's subdomain, assuming it's hosted on Odoo.com"
"The documentation about the :ref:`web.base.url <domain-name/web-base-url>` "
"explains how to freeze a unique URL. It is also possible to add different "
"redirect URLs on the Microsoft app."
msgstr ""
"*mydatabase.odoo.com*, où *mydatabase* est le préfixe actuel du sous-domaine"
" de la base de données, en supposant qu'elle soit hébergée sur Odoo.com"
#: ../../content/applications/general/email_communication/azure_oauth.rst:44
msgid ""
"After the URL has been added to the field, :guilabel:`Register` the "
"application so it is created."
"application, so it is created."
msgstr ""
"Après avoir ajouté l'URL au champ, cliquez sur :guilabel:`S'inscrire` pour "
"inscrire l'application."
#: ../../content/applications/general/email_communication/azure_oauth.rst:47
msgid "API permissions"
@@ -3275,6 +3268,12 @@ msgid ""
"<https://www.odoo.sh>`_. Incoming and outgoing servers must be configured "
"for on-premise databases."
msgstr ""
"Ce document est **principalement dédié aux utilisateurs d'Odoo sur serveur**"
" qui ne bénéficient pas d'une solution prête à l'emploi pour envoyer et "
"recevoir des e-mails dans Odoo, contrairement à `Odoo Online "
"<https://www.odoo. com/trial>`_ et `Odoo.sh <https://www.odoo.sh>`_. Les "
"serveurs de messagerie entrants et sortants doivent être configurés pour les"
" bases de données sur serveur."
#: ../../content/applications/general/email_communication/email_servers.rst:31
msgid ""
@@ -3357,14 +3356,22 @@ msgid ""
"external email server. Once all the information has been filled out, click "
":guilabel:`Test Connection`."
msgstr ""
"En tant qu'administrateur du système, allez à :menuselection:`Paramètres -->"
" Paramètres généraux --> Discussion` dans Odoo et activez l'option "
":guilabel:`Serveurs de messagerie personnalisés`. Cliquez ensuite sur "
":guilabel:`Enregistrer`. Ensuite, cliquez sur :guilabel:`Serveurs de "
"messagerie sortants` et sur :guilabel:`Créer` pour créer un nouvel "
"enregistrement de serveur de messagerie sortant dans Odoo. Référencez les "
"données SMTP du serveur de messagerie externe. Une fois que toutes les "
"informations ont été complétées, cliquez sur :guilabel:`Test de connexion`."
#: ../../content/applications/general/email_communication/email_servers.rst:68
msgid ":doc:`google_oauth`"
msgstr ""
msgstr ":doc:`google_oauth`"
#: ../../content/applications/general/email_communication/email_servers.rst:69
msgid ":doc:`azure_oauth`"
msgstr ""
msgstr ":doc:`azure_oauth`"
#: ../../content/applications/general/email_communication/email_servers.rst:72
msgid ""
@@ -3643,6 +3650,10 @@ msgid ""
" and Amazon SES, Mailgun, Sendgrid or :doc:`Mailjet <mailjet_api>` for mass "
"mailings."
msgstr ""
"Dans Odoo, vous pouvez utiliser un serveur de messagerie séparé pour les "
"emails transactionnels et les envois de masse. Par exemple, utilisez "
"Postmark ou SendinBlue pour les emails transactionnels, et Amazon SES, "
"Mailgun, Sendgrid ou :doc:`Mailjet <mailjet_api>` pour les envois de masse."
#: ../../content/applications/general/email_communication/email_servers.rst:184
msgid ""
@@ -3710,6 +3721,14 @@ msgid ""
"not have another action attached to it like other aliases might, it is only "
"used to collect replies."
msgstr ""
"Les **réponses** aux messages envoyés depuis Odoo sont acheminées vers le "
"fil de discussion d'origine (et vers la boîte de réception de tous ses "
"abonnés) par l'alias du modèle, s'il y en a un, ou par l'alias catchall "
"(**catchall@**). Les réponses aux messages de modèles qui n'ont pas d'alias "
"personnalisé utiliseront l'alias catchall (`catchall@mycompany.odoo.com`). "
"L'adresse catchall, cependant, n'est pas associée à une autre action, "
"contrairement à d'autres alias ; elle est uniquement utilisée pour collecter"
" des réponses."
#: ../../content/applications/general/email_communication/email_servers.rst:214
msgid ""
@@ -3877,6 +3896,13 @@ msgid ""
"a change is made then the system will not recognize the old alias, and the "
"reply will not be received."
msgstr ""
"Pour modifier les alias catchall et bounce, activez d'abord le :ref:`mode "
"développeur <developer-mode>`. Allez ensuite aux :menuselection:`Paramètres "
"--> Technique --> Paramètres --> Paramètres système` pour personnaliser les "
"alias (`mail.catchall.alias` & `mail.bounce.alias`). Ces changements doivent"
" être effectués avant que la base de données ne soit mise en service. Si un "
"client répond après un changement, le système ne reconnaîtra pas l'ancien "
"alias et la réponse ne sera pas reçue."
#: ../../content/applications/general/email_communication/email_servers.rst:270
msgid ""
@@ -3899,7 +3925,7 @@ msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:278
msgid "Allow alias domain system parameter"
msgstr ""
msgstr "Autoriser les paramètres système de l'alias de domaine"
#: ../../content/applications/general/email_communication/email_servers.rst:280
msgid ""
@@ -3908,6 +3934,11 @@ msgid ""
"the :ref:`developer mode <developer-mode>`. Then, go to "
":menuselection:`Settings app --> Technical --> Email section --> Aliases`."
msgstr ""
"Les alias entrants sont définis dans la base de données Odoo pour créer des "
"entrées à partir d'e-mails entrants. Pour voir les alias définis dans la "
"base de données Odoo, activez d'abord le mode développeur :ref:`. "
"<developer-mode>`. Ensuite, allez dans :menuselection:`Paramètres --> "
"Technique --> Section email --> Alias`."
#: ../../content/applications/general/email_communication/email_servers.rst:284
msgid ""
@@ -3917,6 +3948,13 @@ msgid ""
"create a ticket, lead, opportunity, etc., eliminates false positives where "
"email addresses with only the prefix alias (not the domain) are present."
msgstr ""
"Le paramètre système suivant, `mail.catchall.domain.allowed`, Le paramètre "
"système suivant, `mail.catchall.domain.allowed`, défini avec des valeurs de "
"domaine d'alias autorisées, séparées par des virgules, permet de filtrer les"
" e-mails correctement adressés à des alias. En définissant le(s) domaine(s) "
"pour lesquels l'alias peut créer un ticket, une piste, une opportunité, "
"etc., cela permet d'éliminer les faux positifs lorsque les adresses e-mail "
"ne contiennent que le préfixe de l'alias (et non le domaine)."
#: ../../content/applications/general/email_communication/email_servers.rst:289
msgid ""
@@ -3925,6 +3963,11 @@ msgid ""
"incoming email address. This is true in the sender, recipient, and :abbr:`CC"
" (Carbon Copy)` email addresses of an incoming email."
msgstr ""
"Dans certains cas, la base de données Odoo affiche des correspondances "
"lorsqu'un e-mail contient le même préfixe d'alias et un domaine différent "
"dans l'adresse e-mail entrante C'est le cas pour les adresses e-mail "
"d''expéditeurs, de destinataires et :abbr:`CC (\"Copie carbone\") d'e-mails "
"entrants."
#: ../../content/applications/general/email_communication/email_servers.rst:294
msgid ""
@@ -3934,6 +3977,12 @@ msgid ""
"email as the full `commercial` alias (with a different domain), and "
"therefore, creates a ticket/lead/opportunity/etc."
msgstr ""
"Lorsqu'Odoo reçoit des e-mails dont l'expéditeur, le destinataire ou "
"l'adresse e-mail :abbr:`CC (Copie carbone) contient le préfixe d'alias "
"`commercial` (par exemple commercial@gmail.com, commercial@odoo.net), la "
"base de données le considère à tort l'e-mail comme l'alias complet "
"`commercial` (avec un domaine différent), et crée donc un "
"ticket/piste/opportunité/etc."
#: ../../content/applications/general/email_communication/email_servers.rst:299
msgid ""
@@ -3943,6 +3992,11 @@ msgid ""
" Parameters`. Click :guilabel:`Create`. Then, type in "
"`mail.catchall.domain.allowed` for the :guilabel:`Key` field."
msgstr ""
"Pour ajouter le paramètre système `mail.catchall.domain.allowed`, activez "
"tout d'abord le :ref:`mode développeur <developer-mode>`. Ensuite, allez "
"dans :menuselection:`Paramètres --> Technique --> Paramètres --> Paramètres "
"système`. Cliquez sur :guilabel:`Nouveau`. Puis saisissez "
"`mail.catchall.domain.allowed` pour le champ :guilabel:`Clé`."
#: ../../content/applications/general/email_communication/email_servers.rst:304
msgid ""
@@ -3950,12 +4004,18 @@ msgid ""
"comma(s) (if plural domains). Manually :guilabel:`Save`, and the system "
"parameter takes immediate effect."
msgstr ""
"Ensuite, pour le champ :guilabel:`Valeur`, ajoutez le(s) domaine(s) "
"séparé(s) par une virgule ( dans le cas de plusieurs domaines). "
":guilabel:`Sauvegardez` manuellement pour que le paramètre système soit "
"immédiatement appliqué."
#: ../../content/applications/general/email_communication/email_servers.rst-1
msgid ""
"mail.catchall.domain.allowed system parameter set with key and value "
"highlighted."
msgstr ""
"Ensemble de paramètres système mail.catchall.domain.allowed avec clé et "
"valeur mises en évidence."
#: ../../content/applications/general/email_communication/faq.rst:3
msgid "Email issues"
+3 -2
View File
@@ -7,6 +7,7 @@
# Martin Trigaux, 2024
# Wil Odoo, 2024
# Jolien De Paepe, 2024
# Manon Rondou, 2024
#
#, fuzzy
msgid ""
@@ -15,7 +16,7 @@ msgstr ""
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-05-28 08:57+0000\n"
"PO-Revision-Date: 2024-04-04 12:26+0000\n"
"Last-Translator: Jolien De Paepe, 2024\n"
"Last-Translator: Manon Rondou, 2024\n"
"Language-Team: French (https://app.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -4899,7 +4900,7 @@ msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:101
msgid "Pivot table"
msgstr ""
msgstr "Tableau croisé dynamique"
#: ../../content/applications/hr/payroll/reporting.rst:103
msgid ""
File diff suppressed because it is too large Load Diff
+4 -4
View File
@@ -18,7 +18,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-04-29 08:05+0000\n"
"POT-Creation-Date: 2024-06-21 08:31+0000\n"
"PO-Revision-Date: 2021-11-02 08:49+0000\n"
"Last-Translator: Jolien De Paepe, 2024\n"
"Language-Team: French (https://app.transifex.com/odoo/teams/41243/fr/)\n"
@@ -2415,9 +2415,9 @@ msgstr ""
#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:12
msgid ""
"To use this service, `contact Axivox <https://www.axivox.com/contact/>`_ to "
"open an account. Before doing so, verify that Axivox covers the company's "
"area, along with the areas the company's users wish to call."
"To use this service, `contact Axivox <https://www.axivox.com/en/contact/>`_ "
"to open an account. Before doing so, verify that Axivox covers the company's"
" area, along with the areas the company's users wish to call."
msgstr ""
#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:17

Some files were not shown because too many files have changed in this diff Show More