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

[I18N] *: export latest terms

Browse Source 
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)

Also update the tx/config to point to v18 project

X-original-commit: 5aa4151
This commit is contained in:
Tiffany Chang (tic) 2024-10-07 16:24:40 +02:00
parent 0a3c8ec10a
commit d21d77b181
13 changed files with 5125 additions and 4643 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
.tx/config
View File

@ -1,7 +1,7 @@
[main]
host = https://www.transifex.com
[o:odoo:p:odoo-17-doc:r:administration]
[o:odoo:p:odoo-18-doc:r:administration]
file_filter = locale/<lang>/LC_MESSAGES/administration.po
source_file = locale/sources/administration.pot
type = POT
@ -11,7 +11,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:applications]
[o:odoo:p:odoo-18-doc:r:applications]
file_filter = locale/<lang>/LC_MESSAGES/applications.po
source_file = locale/sources/applications.pot
type = POT
@ -21,7 +21,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:essentials]
[o:odoo:p:odoo-18-doc:r:essentials]
file_filter = locale/<lang>/LC_MESSAGES/essentials.po
source_file = locale/sources/essentials.pot
type = POT
@ -31,7 +31,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:finance]
[o:odoo:p:odoo-18-doc:r:finance]
file_filter = locale/<lang>/LC_MESSAGES/finance.po
source_file = locale/sources/finance.pot
type = POT
@ -41,7 +41,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:general]
[o:odoo:p:odoo-18-doc:r:general]
file_filter = locale/<lang>/LC_MESSAGES/general.po
source_file = locale/sources/general.pot
type = POT
@ -51,7 +51,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:hr]
[o:odoo:p:odoo-18-doc:r:hr]
file_filter = locale/<lang>/LC_MESSAGES/hr.po
source_file = locale/sources/hr.pot
type = POT
@ -61,7 +61,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:index]
[o:odoo:p:odoo-18-doc:r:index]
file_filter = locale/<lang>/LC_MESSAGES/index.po
source_file = locale/sources/index.pot
type = POT
@ -71,7 +71,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:inventory_and_mrp]
[o:odoo:p:odoo-18-doc:r:inventory_and_mrp]
file_filter = locale/<lang>/LC_MESSAGES/inventory_and_mrp.po
source_file = locale/sources/inventory_and_mrp.pot
type = POT
@ -81,7 +81,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:marketing]
[o:odoo:p:odoo-18-doc:r:marketing]
file_filter = locale/<lang>/LC_MESSAGES/marketing.po
source_file = locale/sources/marketing.pot
type = POT
@ -91,7 +91,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:productivity]
[o:odoo:p:odoo-18-doc:r:productivity]
file_filter = locale/<lang>/LC_MESSAGES/productivity.po
source_file = locale/sources/productivity.pot
type = POT
@ -101,7 +101,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:sales]
[o:odoo:p:odoo-18-doc:r:sales]
file_filter = locale/<lang>/LC_MESSAGES/sales.po
source_file = locale/sources/sales.pot
type = POT
@ -111,7 +111,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:services]
[o:odoo:p:odoo-18-doc:r:services]
file_filter = locale/<lang>/LC_MESSAGES/services.po
source_file = locale/sources/services.pot
type = POT
@ -121,7 +121,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:user_settings]
[o:odoo:p:odoo-18-doc:r:user_settings]
file_filter = locale/<lang>/LC_MESSAGES/settings.po
source_file = locale/sources/settings.pot
type = POT
@ -131,7 +131,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:studio]
[o:odoo:p:odoo-18-doc:r:studio]
file_filter = locale/<lang>/LC_MESSAGES/studio.po
source_file = locale/sources/studio.pot
type = POT
@ -141,7 +141,7 @@ replace_edited_strings = false
keep_translations = false
source_lang = en
[o:odoo:p:odoo-17-doc:r:websites]
[o:odoo:p:odoo-18-doc:r:websites]
file_filter = locale/<lang>/LC_MESSAGES/websites.po
source_file = locale/sources/websites.pot
type = POT

103
locale/sources/administration.pot
View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Project-Id-Version: Odoo 18.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-09-24 10:43+0000\n"
"POT-Creation-Date: 2024-10-07 14:21+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -758,7 +758,7 @@ msgid "The base is an Ubuntu system, where all of Odoo's required dependencies,
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:14
msgid "If your project requires additional Python dependencies, or more recent releases, you can define a :file:`requirements.txt` file in the root of your branches listing them. The platform will take care to install these dependencies in your containers. `The pip requirements specifiers <https://pip.pypa.io/en/stable/reference/pip_install/#requirement-specifiers>`_ documentation can help you write a :file:`requirements.txt` file. To have a concrete example, check out the `requirements.txt file of Odoo <https://github.com/odoo/odoo/blob/17.0/requirements.txt>`_."
msgid "If your project requires additional Python dependencies, or more recent releases, you can define a :file:`requirements.txt` file in the root of your branches listing them. The platform will take care to install these dependencies in your containers. `The pip requirements specifiers <https://pip.pypa.io/en/stable/reference/pip_install/#requirement-specifiers>`_ documentation can help you write a :file:`requirements.txt` file. To have a concrete example, check out the `requirements.txt file of Odoo <https://github.com/odoo/odoo/blob/18.0/requirements.txt>`_."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:22
@ -2885,6 +2885,8 @@ msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:181
#: ../../content/administration/odoo_sh/getting_started/settings.rst:186
#: ../../content/administration/supported_versions.rst:35
#: ../../content/administration/supported_versions.rst:36
#: ../../content/administration/supported_versions.rst:37
#: ../../content/administration/supported_versions.rst:41
#: ../../content/administration/supported_versions.rst:47
#: ../../content/administration/supported_versions.rst:53
@ -2893,9 +2895,6 @@ msgstr ""
#: ../../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 ""
@ -4350,7 +4349,7 @@ msgid "Instead of using the repository, packages for both the **Community** and
msgstr ""
#: ../../content/administration/on_premise/packages.rst:103
msgid "Odoo 17 'deb' package currently supports `Debian Buster <https://www.debian.org/releases/buster/>`_ and `Ubuntu 18.04 <https://releases.ubuntu.com/18.04>`_ or above."
msgid "Odoo 18 'deb' package currently supports `Debian Buster <https://www.debian.org/releases/buster/>`_ and `Ubuntu 18.04 <https://releases.ubuntu.com/18.04>`_ or above."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:107
@ -4366,7 +4365,7 @@ msgid "The `num2words` Python package - needed to render textual amounts - does
msgstr ""
#: ../../content/administration/on_premise/packages.rst:135
msgid "Odoo 17 'rpm' package supports Fedora 36."
msgid "Odoo 18 'rpm' package supports Fedora 36."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:137
@ -4608,7 +4607,7 @@ msgid "On Debian/Ubuntu, the following commands should install the required pack
msgstr ""
#: ../../content/administration/on_premise/source.rst:287
msgid "The `setup/debinstall.sh` script will parse the `debian/control <https://github.com/odoo/odoo/blob/17.0/debian/control>`_ file and install the found packages."
msgid "The `setup/debinstall.sh` script will parse the `debian/control <https://github.com/odoo/odoo/blob/18.0/debian/control>`_ file and install the found packages."
msgstr ""
#: ../../content/administration/on_premise/source.rst:290
@ -4950,11 +4949,22 @@ msgid "End of support"
msgstr ""
#: ../../content/administration/supported_versions.rst:34
msgid "Odoo saas~17.4"
msgid "**Odoo 18.0**"
msgstr ""
#: ../../content/administration/supported_versions.rst:38
#: ../../content/administration/supported_versions.rst:69
msgid "October 2024"
msgstr ""
#: ../../content/administration/supported_versions.rst:39
msgid "October 2027 (planned)"
msgstr ""
#: ../../content/administration/supported_versions.rst:40
msgid "Odoo SaaS 17.4"
msgstr ""
#: ../../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:48
@ -4962,24 +4972,16 @@ msgstr ""
msgid "N/A"
msgstr ""
#: ../../content/administration/supported_versions.rst:38
#: ../../content/administration/supported_versions.rst:44
msgid "July 2024"
msgstr ""
#: ../../content/administration/supported_versions.rst:40
msgid "Odoo saas~17.2"
msgstr ""
#: ../../content/administration/supported_versions.rst:44
msgid "April 2024"
msgstr ""
#: ../../content/administration/supported_versions.rst:46
msgid "Odoo saas~17.1"
msgid "Odoo SaaS 17.2"
msgstr ""
#: ../../content/administration/supported_versions.rst:50
msgid "January 2024"
msgid "April 2024"
msgstr ""
#: ../../content/administration/supported_versions.rst:52
@ -5000,83 +5002,70 @@ msgid "**Odoo 16.0**"
msgstr ""
#: ../../content/administration/supported_versions.rst:62
#: ../../content/administration/supported_versions.rst:81
msgid "October 2022"
msgstr ""
#: ../../content/administration/supported_versions.rst:63
msgid "November 2025 (planned)"
msgid "October 2025 (planned)"
msgstr ""
#: ../../content/administration/supported_versions.rst:64
msgid "**Odoo 15.0**"
msgstr ""
#: ../../content/administration/supported_versions.rst:68
msgid "October 2021"
msgstr ""
#: ../../content/administration/supported_versions.rst:69
msgid "November 2024 (planned)"
msgstr ""
#: ../../content/administration/supported_versions.rst:70
msgid "**Odoo 14.0**"
msgstr ""
#: ../../content/administration/supported_versions.rst:65
#: ../../content/administration/supported_versions.rst:66
#: ../../content/administration/supported_versions.rst:67
#: ../../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 ""
#: ../../content/administration/supported_versions.rst:68
msgid "October 2021"
msgstr ""
#: ../../content/administration/supported_versions.rst:70
msgid "**Odoo 14.0**"
msgstr ""
#: ../../content/administration/supported_versions.rst:74
msgid "October 2020"
msgstr ""
#: ../../content/administration/supported_versions.rst:76
msgid "**Odoo 13.0**"
msgstr ""
#: ../../content/administration/supported_versions.rst:80
msgid "October 2019"
msgstr ""
#: ../../content/administration/supported_versions.rst:82
msgid "Older versions"
msgstr ""
#: ../../content/administration/supported_versions.rst:86
msgid "Before 2019"
#: ../../content/administration/supported_versions.rst:80
msgid "Before 2020"
msgstr ""
#: ../../content/administration/supported_versions.rst:87
msgid "Before 2022"
#: ../../content/administration/supported_versions.rst:81
msgid "Before 2023"
msgstr ""
#: ../../content/administration/supported_versions.rst:89
#: ../../content/administration/supported_versions.rst:83
msgid "Legend"
msgstr ""
#: ../../content/administration/supported_versions.rst:91
#: ../../content/administration/supported_versions.rst:85
msgid "|green| Supported version"
msgstr ""
#: ../../content/administration/supported_versions.rst:93
#: ../../content/administration/supported_versions.rst:87
msgid "|red| End-of-support"
msgstr ""
#: ../../content/administration/supported_versions.rst:95
#: ../../content/administration/supported_versions.rst:89
msgid "N/A Never released for this platform"
msgstr ""
#: ../../content/administration/supported_versions.rst:98
#: ../../content/administration/supported_versions.rst:92
msgid "Even though we don't support older versions, you can always `upgrade from any version <https://upgrade.odoo.com/>`_."
msgstr ""

228
locale/sources/essentials.pot
View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Project-Id-Version: Odoo 18.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-09-24 10:43+0000\n"
"POT-Creation-Date: 2024-10-07 14:21+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1723,230 +1723,6 @@ msgstr ""
msgid "Odoo sends a low-credit alert to the :guilabel:`Warning Email` when the balance of credits falls below the amount listed as the :guilabel:`Threshold`."
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:3
msgid "Keyboard shortcuts"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:5
msgid "Users in Odoo can utilize several keyboard shortcuts to navigate through modules, execute actions, and manage data."
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:9
msgid "Hold :kbd:`Ctrl` to view the keyboard shortcuts assigned to each element on the interface."
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:0
msgid "A selection of keyboard shortcuts in Odoo."
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:16
msgid "Some keyboard shortcuts may not be available on different versions of Odoo or effective depending on browsers, extensions, or other individual settings."
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:20
msgid "Keyboard shortcuts by operating system"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:22
msgid "Below is a list of some of the most commonly used keyboard shortcuts within Odoo, listed by operating system."
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:29
msgid "Description"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:30
msgid "Windows / Linux"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:31
msgid "macOS"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:32
msgid "Previous breadcrumb"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:33
msgid ":kbd:`Alt` + :kbd:`B`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:34
msgid ":kbd:`Ctrl` + :kbd:`B`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:35
msgid "Create new record"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:36
msgid ":kbd:`Alt` + :kbd:`C`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:37
msgid ":kbd:`Ctrl` + :kbd:`C`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:38
msgid "Odoo Home Page"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:39
msgid ":kbd:`Alt` + :kbd:`H`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:40
msgid ":kbd:`Ctrl` + :kbd:`H`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:41
msgid "Discard changes"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:42
msgid ":kbd:`Alt` + :kbd:`J`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:43
msgid ":kbd:`Ctrl` + :kbd:`J`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:44
msgid "Save changes"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:45
msgid ":kbd:`Alt` + :kbd:`S`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:46
msgid ":kbd:`Ctrl` + :kbd:`S`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:47
msgid "Next page"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:48
msgid ":kbd:`Alt` + :kbd:`N`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:49
msgid ":kbd:`Ctrl` + :kbd:`N`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:50
msgid "Previous page"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:51
msgid ":kbd:`Alt` + :kbd:`P`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:52
msgid ":kbd:`Ctrl` + :kbd:`P`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:53
msgid "Search"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:54
msgid ":kbd:`Alt` + :kbd:`Q`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:55
msgid ":kbd:`Ctrl` + :kbd:`Q`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:56
msgid "Select menus"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:57
msgid ":kbd:`Alt` + :kbd:`1-9`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:58
msgid ":kbd:`Ctrl` + :kbd:`1-9`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:59
msgid "Create a new To-Do"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:60
msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`T`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:61
msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`T`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:62
msgid "Search a Knowledge article"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:63
msgid ":kbd:`Alt` + :kbd:`F`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:64
msgid ":kbd:`Ctrl` + :kbd:`F`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:65
msgid "Share a Knowledge article"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:66
msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`S`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:67
msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`S`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:68
msgid "Open command palette"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:69
msgid ":kbd:`Ctrl` + :kbd:`K`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:70
msgid ":kbd:`Command` + :kbd:`K`"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:73
msgid "After opening the command palette, search using the following keyboard shortcuts:"
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:75
msgid ":kbd:`/`: search for menus, applications, and modules."
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:76
msgid ":kbd:`@`: search for users."
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:77
msgid ":kbd:`#`: search for **Discuss** channels."
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:78
msgid ":kbd:`?`: search for **Knowledge** articles."
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:80
msgid "Enter a name (or term) in the search bar, or use the arrow keys to scroll through the available options. Then, click :kbd:`Ctrl` + :kbd:`Enter` to open the selected app, module, or menu in a new tab."
msgstr ""
#: ../../content/applications/essentials/keyboard_shortcuts.rst:0
msgid "The command palette in Odoo, with the menu search option selected."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:3
msgid "Reporting"
msgstr ""

3031
locale/sources/finance.pot
View File

File diff suppressed because it is too large Load Diff

304
locale/sources/general.pot
View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Project-Id-Version: Odoo 18.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-09-24 10:43+0000\n"
"POT-Creation-Date: 2024-10-07 14:21+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1277,30 +1277,30 @@ msgid "Activating the developer mode in the Settings app"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:33
msgid "To activate the developer mode **from anywhere in the database**, add `?debug=1` to the URL after `/web` (e.g., `https://example.odoo.com/web?debug=1#action=menu&cids=1`). To deactivate it, use `?debug=0` instead."
msgid "To activate the developer mode **from anywhere in the database**, add `?debug=1` at the end of the URL (e.g., `https://example.odoo.com/odoo?debug=1`). To deactivate it, use `?debug=0` instead."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:37
#: ../../content/applications/general/developer_mode.rst:36
msgid "Use `?debug=assets` to activate the developer mode with assets and `?debug=tests` to activate it with tests assets."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:41
#: ../../content/applications/general/developer_mode.rst:40
msgid "Open the **command palette** by pressing `Ctrl + K` or `Cmd ⌘ + K`, then type `debug` to activate the developer mode with assets or deactivate it."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:44
#: ../../content/applications/general/developer_mode.rst:43
msgid "Browser extension"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:46
#: ../../content/applications/general/developer_mode.rst:45
msgid "The `Odoo Debug <https://github.com/Droggol/OdooDebug>`_ browser extension adds an icon to toggle developer mode on or off from the browser's toolbar. It is available on the `Chrome Web Store <https://chromewebstore.google.com/detail/odoo-debug/hmdmhilocobgohohpdpolmibjklfgkbi>`_ and `Firefox Add-ons <https://addons.mozilla.org/firefox/addon/odoo-debug/>`_."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:54
#: ../../content/applications/general/developer_mode.rst:53
msgid "Developer tools and technical menu"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:56
#: ../../content/applications/general/developer_mode.rst:55
msgid "Once the developer mode is activated, the developer tools can be accessed by clicking the :icon:`fa-bug` :guilabel:`(bug)` icon. The menu contains tools useful for understanding or editing technical data, such as a view's field, filters, or actions. The options available depend on where the menu is accessed from."
msgstr ""
@ -1308,7 +1308,7 @@ msgstr ""
msgid "Accessing the developer tools"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:64
#: ../../content/applications/general/developer_mode.rst:63
msgid "Database administrators can access the technical menu from the :guilabel:`Settings` app. It contains advanced database settings, such as ones related to the database structure, security, actions, etc."
msgstr ""
@ -1739,7 +1739,7 @@ msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:241
#: ../../content/applications/general/iot/config/pos.rst:21
#: ../../content/applications/general/iot/config/troubleshooting.rst:604
#: ../../content/applications/general/iot/config/troubleshooting.rst:616
msgid "Setup"
msgstr ""
@ -4761,7 +4761,7 @@ msgid "Connect a supported receipt printer to a :abbr:`USB (Universal Serial Bus
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:43
#: ../../content/applications/general/iot/config/troubleshooting.rst:560
#: ../../content/applications/general/iot/config/troubleshooting.rst:572
msgid "Cash drawer"
msgstr ""
@ -4770,7 +4770,7 @@ msgid "The cash drawer should be connected to the printer with an RJ25 cable."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:45
#: ../../content/applications/general/iot/config/troubleshooting.rst:508
#: ../../content/applications/general/iot/config/troubleshooting.rst:520
msgid "Barcode scanner"
msgstr ""
@ -4779,7 +4779,7 @@ msgid "In order for the barcode scanner to be compatible it must end barcodes wi
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:48
#: ../../content/applications/general/iot/config/troubleshooting.rst:571
#: ../../content/applications/general/iot/config/troubleshooting.rst:583
msgid "Scale"
msgstr ""
@ -4989,230 +4989,242 @@ msgid "Epson and Star receipt printers and Zebra label printers do not need a dr
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:104
msgid "Epson configuration special case"
msgid "The printer is detected but is not recognized correctly"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:106
msgid "If the printer is not recognized correctly by Odoo and the :abbr:`IoT (Internet of Things)` box, go to the form view of the device (:menuselection:`IoT App --> Devices -->Printer Device`) and change the subtype. The three options available are: :guilabel:`Receipt Printer`, :guilabel:`Label Printer`, and :guilabel:`Office Printer`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:-1
msgid "Sub-type selection in a printer IoT device."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:116
msgid "Epson configuration special case"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:118
msgid "Most Epson printers support printing receipts in Odoo :abbr:`POS (Point of Sale)` using the `GS v 0` command. However, the following Epson printer models do not support this command:"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:109
#: ../../content/applications/general/iot/config/troubleshooting.rst:121
msgid "TM-U220"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:110
#: ../../content/applications/general/iot/config/troubleshooting.rst:122
msgid "TM-U230"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:111
#: ../../content/applications/general/iot/config/troubleshooting.rst:123
msgid "TM-P60"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:112
#: ../../content/applications/general/iot/config/troubleshooting.rst:124
msgid "TMP-P60II"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:114
#: ../../content/applications/general/iot/config/troubleshooting.rst:126
msgid "Bypass this issue by configuring the printer to use the `ESC *` command instead."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:117
#: ../../content/applications/general/iot/config/troubleshooting.rst:129
msgid "Process to force ESC * command"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:120
#: ../../content/applications/general/iot/config/troubleshooting.rst:132
msgid "Epson printer compatibility"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:122
#: ../../content/applications/general/iot/config/troubleshooting.rst:134
msgid "The first step is to check whether the printer is incompatible with `GS v 0` command."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:126
#: ../../content/applications/general/iot/config/troubleshooting.rst:138
msgid "`Epson GS v 0 documentation <https://reference.epson-biz.com/modules/ref_escpos/index.php? content_id=94>`_ for `GS v 0` compatible printers."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:128
#: ../../content/applications/general/iot/config/troubleshooting.rst:140
msgid "`Epson ESC * documentation <https://reference.epson-biz.com/modules/ref_escpos/index.php ?content_id=88>`_ for `ESC *` compatible printers."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:131
#: ../../content/applications/general/iot/config/troubleshooting.rst:143
msgid "If the printer is not compatible with the `ESC *` command then the following process is not possible. Should the printer be compatible to use the `ESC *` command to print, follow this process to configure the printer with the :abbr:`IoT (Internet of Things)` box."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:136
#: ../../content/applications/general/iot/config/troubleshooting.rst:148
msgid "IoT box configuration for ESC *"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:138
#: ../../content/applications/general/iot/config/troubleshooting.rst:150
msgid "To configure the :abbr:`IoT (Internet of Things)` box to use the `ESC *` command to print, go to the :abbr:`IoT (Internet of Things)` box homepage by navigating to :menuselection:`IoT app --> IoT Boxes`. Then click on the :guilabel:`IP address` and this will direct to the :abbr:`IoT (Internet of Things)` box homepage."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:143
#: ../../content/applications/general/iot/config/troubleshooting.rst:155
msgid "**Choosing the printer**"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:145
#: ../../content/applications/general/iot/config/troubleshooting.rst:157
msgid "Now click on the :guilabel:`Printers server` button. This will redirect the browser to the *CUPS* page. Next, go to :menuselection:`Administration --> Printers --> Add Printer`, choose the printer that should be modified, and then click :guilabel:`Continue`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:150
#: ../../content/applications/general/iot/config/troubleshooting.rst:162
msgid "If the name of the printer is still uncertain, take the following steps:"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:152
#: ../../content/applications/general/iot/config/troubleshooting.rst:164
msgid "Take note of the listed printers on the *CUPS* page."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:153
#: ../../content/applications/general/iot/config/troubleshooting.rst:165
msgid "Turn the printer off and refresh the page."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:154
#: ../../content/applications/general/iot/config/troubleshooting.rst:166
msgid "Now compare the difference with the first list to see which printer disappeared."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:155
#: ../../content/applications/general/iot/config/troubleshooting.rst:167
msgid "Turn the printer back on and refresh the page again."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:156
#: ../../content/applications/general/iot/config/troubleshooting.rst:168
msgid "Double-check the list again to see if the printer re-appears."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:157
#: ../../content/applications/general/iot/config/troubleshooting.rst:169
msgid "The printer that disappeared and reappears again on the listed printers is the name of the printer in question."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:161
#: ../../content/applications/general/iot/config/troubleshooting.rst:173
msgid "This can be :guilabel:`Unknown` under :guilabel:`Local printers`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:163
#: ../../content/applications/general/iot/config/troubleshooting.rst:175
msgid "**CUPS naming convention**"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:165
#: ../../content/applications/general/iot/config/troubleshooting.rst:177
msgid "`CUPS` will prompt the administrator for three pieces of information: the :guilabel:`Name`, :guilabel:`Description` and the :guilabel:`Location`. The last two pieces of information do not need to be specific, however, the :guilabel:`Name` should follow a particular convention to work with the `ESC *` command."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:170
#: ../../content/applications/general/iot/config/troubleshooting.rst:182
msgid "The :guilabel:`Name` should match this convention: `<printer_name>__IMC_<param_1>_<param_2>_..._<param_n>__`"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:173
#: ../../content/applications/general/iot/config/troubleshooting.rst:185
msgid "A breakdown of the naming convention:"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:175
#: ../../content/applications/general/iot/config/troubleshooting.rst:187
msgid "`printer_name`: This is the printer name. It can be any character as long as it does not contain `_`, `/`, `#`, or ` ` (space character)."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:177
#: ../../content/applications/general/iot/config/troubleshooting.rst:189
msgid "`IMC`: This stands for *Image Mode Column* (the simplified name for `ESC *`)."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:178
#: ../../content/applications/general/iot/config/troubleshooting.rst:190
msgid "`param_1`: This stands for the specific parameter:"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:180
#: ../../content/applications/general/iot/config/troubleshooting.rst:192
msgid "`SCALE<X>`: Scale of the picture (with the same aspect ratio). `X` should be an integer describing the scale percentage that should be used."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:184
#: ../../content/applications/general/iot/config/troubleshooting.rst:196
msgid "`100` is the original size, `50` is half the size, `200` is twice the size."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:186
#: ../../content/applications/general/iot/config/troubleshooting.rst:198
msgid "`LDV`: *Low Density Vertical* (will be set to *High Density Vertical* if not specified)."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:187
#: ../../content/applications/general/iot/config/troubleshooting.rst:199
msgid "`LDH`: *Low Density Horizontal* (will be set to *High Density Horizontal* if not specified)."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:190
#: ../../content/applications/general/iot/config/troubleshooting.rst:202
msgid "*Density* parameters might need to be configured in a particular way depending on the printer model."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:194
#: ../../content/applications/general/iot/config/troubleshooting.rst:206
msgid "Visit `Epson's ESC * documentation <https://reference.epson-biz.com/modules/ref_escpos/index.php?content_id=88>`_ and click on the printer model printer in the table above to see if the printer should set these parameters."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:199
#: ../../content/applications/general/iot/config/troubleshooting.rst:211
msgid "The following are examples of proper and improper name formatting:"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:201
#: ../../content/applications/general/iot/config/troubleshooting.rst:213
msgid "Proper name formatting:"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:203
#: ../../content/applications/general/iot/config/troubleshooting.rst:215
msgid "`EPSONTMm30II__IMC__`"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:204
#: ../../content/applications/general/iot/config/troubleshooting.rst:216
msgid "`EPSON_TM_U220__IMC_LDV_LDH_SCALE80__`"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:206
#: ../../content/applications/general/iot/config/troubleshooting.rst:218
msgid "Improper name formatting (this will not prevent printing, but the result might not have the expected printed output):"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:209
#: ../../content/applications/general/iot/config/troubleshooting.rst:221
msgid "`EPSON TMm 30II` -> The name cannot have spaces."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:210
#: ../../content/applications/general/iot/config/troubleshooting.rst:222
msgid "`EPSONTMm30II` -> The name itself is correct, but it will not use `ESC *`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:211
#: ../../content/applications/general/iot/config/troubleshooting.rst:223
msgid "`EPSONTMm30II__IMC` -> This name is missing the end `__`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:212
#: ../../content/applications/general/iot/config/troubleshooting.rst:224
msgid "`EPSONTMm30II__IMC_XDV__` -> The parameter `XDV` does not match any existing parameters."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:213
#: ../../content/applications/general/iot/config/troubleshooting.rst:225
msgid "`EPSONTMm30II__IMC_SCALE__` -> The parameter `SCALE` is missing the scale value."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:215
#: ../../content/applications/general/iot/config/troubleshooting.rst:227
msgid "**Finish adding a printer**"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:217
#: ../../content/applications/general/iot/config/troubleshooting.rst:229
msgid "After setting the name of the printer with the appropriate naming convention, click :guilabel:`Continue`. Next, set the :guilabel:`Make` value to :guilabel:`Raw` and for the :guilabel:`Model` value, set this to :guilabel:`Raw Queue (en)`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:221
#: ../../content/applications/general/iot/config/troubleshooting.rst:233
msgid "After completing these steps, click :guilabel:`Add Printer`. If everything was done correctly, the page should redirect to the *Banners* page."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:224
#: ../../content/applications/general/iot/config/troubleshooting.rst:236
msgid "At this point the printer should have been created, now the :abbr:`IoT (Internet of Things)` box just needs to detect it and then sync to Odoo's server (this could take a few minutes)."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:227
#: ../../content/applications/general/iot/config/troubleshooting.rst:239
msgid "**Adding the printer to Odoo PoS**"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:229
#: ../../content/applications/general/iot/config/troubleshooting.rst:241
msgid "Once the printer is visible on the Odoo database, do not forget to choose it in the :abbr:`PoS (Point of Sale)`configuration as the :abbr:`IoT (Internet of Things)` printer. Navigate to :menuselection:`Pos App --> Settings --> Connected Devices --> IoT Box --> Receipt Printer --> Save`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:235
#: ../../content/applications/general/iot/config/troubleshooting.rst:247
msgid "If the printer was set up incorrectly (it is still printing random text or the printed receipt is too big or small), then it cannot be modified via the printer name with *CUPS*. Instead, the above process can be repeated to set up another printer from scratch to create one with modified parameters."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:240
#: ../../content/applications/general/iot/config/troubleshooting.rst:252
msgid "**Example setup of the Epson TM-U220B printer using ESC**"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:245
#: ../../content/applications/general/iot/config/troubleshooting.rst:257
msgid "The following is an example of the troubleshooting process for a TM-U220B printer model using the `ESC *` command. The receipt pictured below is an example of a receipt that is printing correctly due to proper formatting (in theory):"
msgstr ""
@ -5220,7 +5232,7 @@ msgstr ""
msgid "Properly formatted receipt picture from a demo database."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:253
#: ../../content/applications/general/iot/config/troubleshooting.rst:265
msgid "Trying to print this receipt right-away prior to the proper formatting will not work as the TM-U220B printer model does not support `GS v 0`. Instead random characters will print:"
msgstr ""
@ -5228,11 +5240,11 @@ msgstr ""
msgid "Printer paper with seemingly random characters."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:260
#: ../../content/applications/general/iot/config/troubleshooting.rst:272
msgid "To properly configure formatting for the Epson TM-U220B printer model take the following steps."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:262
#: ../../content/applications/general/iot/config/troubleshooting.rst:274
msgid "After consulting Epson's website for compatibility for both of the commands: `GS v 0 <https://reference.epson-biz.com/modules/ref_escpos/index.php?content_id=94>`_ and `ESC * <https://reference.epson-biz.com/modules/ref_escpos/index.php?content_id=88>`_, it can be seen that indeed the TM-U220B is not compatible with `GS v 0`, but is compatible with `ESC *`."
msgstr ""
@ -5240,7 +5252,7 @@ msgstr ""
msgid "Epson compatibility evaluation from Epson website."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:271
#: ../../content/applications/general/iot/config/troubleshooting.rst:283
msgid "When adding the printer, *CUPS* will ask which printer should be added:"
msgstr ""
@ -5248,11 +5260,11 @@ msgstr ""
msgid "Administration menu, add printer selection."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:277
#: ../../content/applications/general/iot/config/troubleshooting.rst:289
msgid "In this case, the printer is connected via :abbr:`USB (Universal Serial Bus)` so it won' be part of the :guilabel:`Discovered Network Printers`. Instead it is likely part of the :guilabel:`Unknown` selection under :guilabel:`Local Printers`. By unplugging the printer's :abbr:`USB (Universal Serial Bus)` cable from the :abbr:`IoT (Internet of Things)` box and refreshing the page, the :guilabel:`Unknown` printer disappears. By plugging it back in, the printer reappears, so it can be said that this is the printer in question."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:284
#: ../../content/applications/general/iot/config/troubleshooting.rst:296
msgid "For the naming convention, since it needs to print using the `ESC *` command, it is imperative to add `__IMC`. Reference the printer model on `Epson's ESC * site <https://reference.epson-biz.com/modules/ref_escpos/index.php?content_id=88>`_ to find out more about the *density* parameters."
msgstr ""
@ -5260,15 +5272,15 @@ msgstr ""
msgid "Epson TM-U220 specifications on manufacturer's website."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:293
#: ../../content/applications/general/iot/config/troubleshooting.rst:305
msgid "For this particular model, TM-U220, `m` should be equal to 0 or 1. While referencing the :guilabel:`Description` below the pink box in the above picture, the `m` values could be 0, 1, 32 or 33. So in this printers case, the `m` value can NOT be 32 or 33 (otherwise there will be random characters printed)."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:298
#: ../../content/applications/general/iot/config/troubleshooting.rst:310
msgid "The table includes the numeric values: 32 and 33, they both occur if the :guilabel:`Number of bits for vertical data` is set to 24. This means that is a *High Vertical Density*. In the case of configuring the Epson TM-U220, the *Low Vertical Density* will need to be forced, as this printer model does not support *High Vertical Density* for this command `ESC *`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:303
#: ../../content/applications/general/iot/config/troubleshooting.rst:315
msgid "To add a *Low Vertical Density*, add the `LDV` parameter to the naming convention."
msgstr ""
@ -5276,7 +5288,7 @@ msgstr ""
msgid "Add a *Low Vertical Density* (the `LDV` parameter) to the naming convention."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:309
#: ../../content/applications/general/iot/config/troubleshooting.rst:321
msgid "Click :guilabel:`Continue` to proceed. Next, set the :guilabel:`Make` value to :guilabel:`Raw` and for the :guilabel:`Model` value, set this to :guilabel:`Raw Queue (en)`."
msgstr ""
@ -5284,31 +5296,31 @@ msgstr ""
msgid "Epson TM-U220 specifications on manufacturers website."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:316
#: ../../content/applications/general/iot/config/troubleshooting.rst:328
msgid "However, when trying to print with the naming convention: `EpsonTMU220B__IMC_LDV__`, it prints the receipt, but it is too big and outside the margin. To resolve this, add a new printer (and naming convention) with the `SCALE<X>` parameter to adapt to our receipt size."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:320
#: ../../content/applications/general/iot/config/troubleshooting.rst:332
msgid "Here are some examples:"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:325
#: ../../content/applications/general/iot/config/troubleshooting.rst:337
msgid "Printer Naming Convention"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:326
#: ../../content/applications/general/iot/config/troubleshooting.rst:338
msgid "`EpsonTMU220B__IMC_LDV__`"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:327
#: ../../content/applications/general/iot/config/troubleshooting.rst:339
msgid "`EpsonTMU220B__IMC_LDV_SCALE75__`"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:328
#: ../../content/applications/general/iot/config/troubleshooting.rst:340
msgid "`EpsonTMU220B__IMC_LDV_LDH__`"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:329
#: ../../content/applications/general/iot/config/troubleshooting.rst:341
msgid "`EpsonTMU220B__IMC_LDV_LDH_SCALE35__`"
msgstr ""
@ -5332,39 +5344,39 @@ msgstr ""
msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH_SCALE35__."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:347
#: ../../content/applications/general/iot/config/troubleshooting.rst:359
msgid "DYMO LabelWriter print issue"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:349
#: ../../content/applications/general/iot/config/troubleshooting.rst:361
msgid "The DYMO LabelWriter has a known issue in printing with the :abbr:`IoT (Internet of Things)` box. The OpenPrinting CUPS server installs the printer using :guilabel:`Local RAW Printer` drivers. In order to print anything, the correct :guilabel:`Make and Model` needs to be set, so the correct driver is referenced when using the device."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:354
#: ../../content/applications/general/iot/config/troubleshooting.rst:366
msgid "Additionally, a new printer needs to be added to reduce a print delay that occurs after updating the driver."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:358
#: ../../content/applications/general/iot/config/troubleshooting.rst:370
msgid "The DYMO LabelWriter 450 DUO printer is the recommended DYMO printer for use with Odoo and the :abbr:`IoT (Internet of Things)` box. It **must** already be connected to, and recognized on, the :abbr:`IoT (Internet of Things)` box."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:362
#: ../../content/applications/general/iot/config/troubleshooting.rst:374
msgid "The DYMO LabelWriter 450 DUO printer contains two printers in one: a label printer and a tape printer. Choosing the correct model (either DYMO LabelWriter 450 DUO Label (en) or DYMO LabelWriter 450 DUO Tape (en)) is crucial when configuring the following processes."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:366
#: ../../content/applications/general/iot/config/troubleshooting.rst:378
msgid "To keep things consistent, both of the following processes detail the configuration for the DYMO LabelWriter 450 DUO Label (en) model. Change the model when needed."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:372
#: ../../content/applications/general/iot/config/troubleshooting.rst:384
msgid "DYMO LabelWriter not printing"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:374
#: ../../content/applications/general/iot/config/troubleshooting.rst:386
msgid "In the case where the DYMO LabelWriter is not printing anything, a new driver needs to be installed."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:376
#: ../../content/applications/general/iot/config/troubleshooting.rst:388
msgid "First, open the OpenPrinting CUPS console by clicking :menuselection:`Printers server` at the bottom of the :abbr:`IoT (Internet of Things)` box homepage. Next, click on :menuselection:`Printers` in the top menu. Click into the printer in question, and select :guilabel:`Maintenance` in the first drop-down menu. Then, select :guilabel:`Modify Printer` in the second drop-down menu."
msgstr ""
@ -5373,7 +5385,7 @@ msgid "Modify the make and model of the DYMO LabelWriter. Maintenance and Modify
"highlighted."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:386
#: ../../content/applications/general/iot/config/troubleshooting.rst:398
msgid "Next, select the specific network connection/printer that the modification should be made on. Click :guilabel:`Continue`."
msgstr ""
@ -5381,7 +5393,7 @@ msgstr ""
msgid "Printer selection screen with Continue highlighted."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:393
#: ../../content/applications/general/iot/config/troubleshooting.rst:405
msgid "On the next page, click :guilabel:`Continue` to proceed to set the :guilabel:`Make` of the printer."
msgstr ""
@ -5389,7 +5401,7 @@ msgstr ""
msgid "Printer modification screen with Continue highlighted."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:399
#: ../../content/applications/general/iot/config/troubleshooting.rst:411
msgid "Under :guilabel:`Make` select :guilabel:`DYMO` from the menu. Click on :guilabel:`Continue` to set the :guilabel:`Model`."
msgstr ""
@ -5397,7 +5409,7 @@ msgstr ""
msgid "Setting the make page, with DYMO and continue highlighted."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:406
#: ../../content/applications/general/iot/config/troubleshooting.rst:418
msgid "On the following page, set the :guilabel:`Model` to :guilabel:`DYMO LabelWriter 450 DUO Label (en)` (or whichever DYMO printer model is being used). Click on :guilabel:`Modify Printer` to complete setting the new driver, a confirmation page will appear."
msgstr ""
@ -5405,15 +5417,15 @@ msgstr ""
msgid "Setting the printer model page with DYMO LabelWriter 450 DUO Label (en) highlighted."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:414
#: ../../content/applications/general/iot/config/troubleshooting.rst:426
msgid "After being redirected to a confirmation page, acknowledging a successful update, click on the :menuselection:`Printers` button in the top menu."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:417
#: ../../content/applications/general/iot/config/troubleshooting.rst:429
msgid "All the printers installed on the OpenPrinting CUPS server appear, including the newly updated: :guilabel:`DYMO LabelWriter 450 DUO Label` (or whichever DYMO printer model is being used). Click into the printer that was just updated."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:421
#: ../../content/applications/general/iot/config/troubleshooting.rst:433
msgid "To print a test label, click on the :guilabel:`Maintenance` drop-down menu to the left of the :guilabel:`Administration` drop-down menu, and select :guilabel:`Print Test Page`. The test label will print out with a ten-second delay if the driver update was successful."
msgstr ""
@ -5423,19 +5435,19 @@ msgid "Printing a test page from the administration drop-down menu in the OpenPr
"server."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:430
#: ../../content/applications/general/iot/config/troubleshooting.rst:442
msgid "To reduce this delay a new printer will need to be added, follow the process below."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:433
#: ../../content/applications/general/iot/config/troubleshooting.rst:445
msgid "DYMO LabelWriter print delay"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:435
#: ../../content/applications/general/iot/config/troubleshooting.rst:447
msgid "To resolve the delay issue after modifying the driver, the printer **must** be reinstalled. To reinstall the printer, open the OpenPrinting CUPS administration page by clicking :menuselection:`Printers server`, at the bottom of the :abbr:`IoT (Internet of Things)` box homepage. Then, click on :menuselection:`Administration` in the top menu, then click :guilabel:`Add a Printer`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:442
#: ../../content/applications/general/iot/config/troubleshooting.rst:454
msgid "If the DYMO LabelWriter 450 DUO printer is not printing at all, or is not recognizable (has a RAW driver type), then update the drivers on the device. See :ref:`troubleshooting/dymo/update_drivers`."
msgstr ""
@ -5443,7 +5455,7 @@ msgstr ""
msgid "Add a printer button highlighted on the Printer CUPS management page."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:450
#: ../../content/applications/general/iot/config/troubleshooting.rst:462
msgid "On the next screen, in the :guilabel:`Local Printers` section, select the :guilabel:`DYMO LabelWriter 450 DUO Label (DYMO LabelWriter 450 DUO Label)` (or whichever DYMO printer model is being used) pre-installed printer. Click :guilabel:`Continue`."
msgstr ""
@ -5451,7 +5463,7 @@ msgstr ""
msgid "Add a printer screen on OpenPrinting CUPS with DYMO LabelWriter 450 DUO Label highlighted."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:458
#: ../../content/applications/general/iot/config/troubleshooting.rst:470
msgid "On the following screen, modify the :guilabel:`Name` to something recognizable, as the original printer will still be present. Click :guilabel:`Continue` to be taken to the next screen."
msgstr ""
@ -5459,7 +5471,7 @@ msgstr ""
msgid "Rename printer page in the 'Add a Printer' flow, with the name field highlighted."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:465
#: ../../content/applications/general/iot/config/troubleshooting.rst:477
msgid "Next, choose the :guilabel:`Model`. Select :guilabel:`DYMO LabelWriter 450 DUO Label (en)` (or whichever DYMO printer model is being used), and finally, click :guilabel:`Add Printer` to complete the installation."
msgstr ""
@ -5468,11 +5480,11 @@ msgid "Choose model screen on the OpenPrinting CUPS console with model and add a
"highlighted."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:474
#: ../../content/applications/general/iot/config/troubleshooting.rst:486
msgid "After being redirected to a confirmation page, acknowledging a successful installation, click on the :menuselection:`Printers` button in the top menu."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:477
#: ../../content/applications/general/iot/config/troubleshooting.rst:489
msgid "All the printers installed on the OpenPrinting CUPS server appear, including the newly installed: :guilabel:`DYMO LabelWriter 450 DUO Label` (or whichever DYMO printer model is being used). Click into the printer that was just installed."
msgstr ""
@ -5480,47 +5492,47 @@ msgstr ""
msgid "Printer page with newly installed printer highlighted."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:485
#: ../../content/applications/general/iot/config/troubleshooting.rst:497
msgid "To print a test label, click on the :guilabel:`Maintenance` drop-down menu to the left of the :guilabel:`Administration` drop-down menu, and select :guilabel:`Print Test Page`. The test label should print out immediately (one-to-two seconds delay)."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:495
#: ../../content/applications/general/iot/config/troubleshooting.rst:507
msgid "The Zebra printer does not print anything"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:497
#: ../../content/applications/general/iot/config/troubleshooting.rst:509
msgid "Zebra printers are quite sensitive to the format of the Zebra Programming Language (ZPL) code that is printed. If nothing comes out of the printer or blank labels are printed, try changing the format of the report that is sent to the printer by accessing :menuselection:`Settings --> Technical --> User Interface --> Views` in :ref:`developer mode <developer-mode>` and look for the corresponding template."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:504
#: ../../content/applications/general/iot/config/troubleshooting.rst:516
msgid "Check out Zebra's instructions on printing :abbr:`ZPL (Zebra Programming Language)` files `here <https://supportcommunity.zebra.com/s/article/Print-a-zpl-file-using-the-Generic-Text-Printer>`_."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:511
#: ../../content/applications/general/iot/config/troubleshooting.rst:523
msgid "The characters read by the barcode scanner do not match the barcode"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:513
#: ../../content/applications/general/iot/config/troubleshooting.rst:525
msgid "By default, most barcode scanners are configured in the US QWERTY format. If the barcode scanner uses a different layout, go to the form view of the device (:menuselection:`IoT App --> Devices --> Barcode Device`) and select the correct format."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:518
#: ../../content/applications/general/iot/config/troubleshooting.rst:530
msgid "Nothing happens when a barcode is scanned"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:520
#: ../../content/applications/general/iot/config/troubleshooting.rst:532
msgid "Make sure that the correct device is selected in the :menuselection:`Point of Sale` configuration and that the barcode is configured to send an `ENTER` character (keycode 28) at the end of every barcode. To do so, navigate to :menuselection:`PoS app --> 3-Dot Menu on the PoS --> IoT Box section --> Edit`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:526
#: ../../content/applications/general/iot/config/troubleshooting.rst:538
msgid "The barcode scanner is detected as a keyboard"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:529
#: ../../content/applications/general/iot/config/troubleshooting.rst:541
msgid "Some barcode scanners do not advertise themselves as barcode scanners but as a USB keyboard instead, and will not be recognized by the :abbr:`IoT (Internet of Things)` box."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:532
#: ../../content/applications/general/iot/config/troubleshooting.rst:544
msgid "The device type can be manually changed by going to its form view (:menuselection:`IoT App --> Devices --> Barcode Device`) and activating the :guilabel:`Is scanner` option."
msgstr ""
@ -5528,15 +5540,15 @@ msgstr ""
msgid "Modifying the form view of the barcode scanner."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:540
#: ../../content/applications/general/iot/config/troubleshooting.rst:552
msgid "Barcode scanner processes barcode characters individually"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:542
#: ../../content/applications/general/iot/config/troubleshooting.rst:554
msgid "When accessing the mobile version of Odoo from a mobile device, or tablet, paired with a barcode scanner, via the :abbr:`IoT (Internet of Things)` box, the scanner may process each barcode character as an individual scan. In this case, the *Keyboard Layout* option **must** be filled out with the appropriate language of the barcode scanner on the *Barcode Scanner* form page."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:548
#: ../../content/applications/general/iot/config/troubleshooting.rst:560
msgid "Access the barcode scanner form page by navigating to :menuselection:`IoT App --> Devices --> Barcode Scanner`."
msgstr ""
@ -5544,43 +5556,43 @@ msgstr ""
msgid "Barcode scanner form page, with keyboard layout option highlighted."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:555
#: ../../content/applications/general/iot/config/troubleshooting.rst:567
msgid "The :guilabel:`Keyboard Layout` is language based, and the options available vary, depending on the device and the language of the database. For example: :guilabel:`English (UK)`, :guilabel:`English (US)`, etc."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:563
#: ../../content/applications/general/iot/config/troubleshooting.rst:575
msgid "The cash drawer does not open"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:565
#: ../../content/applications/general/iot/config/troubleshooting.rst:577
msgid "The cash drawer should be connected to the printer and the :guilabel:`Cash drawer` checkbox should be ticked in the :abbr:`PoS (Point of Sale)` configuration. To do so, navigate to :menuselection:`POS app --> 3-Dot Menu on the POS --> IoT Box section --> Edit --> Receipt Printer --> Cashdrawer checkbox`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:573
#: ../../content/applications/general/iot/config/troubleshooting.rst:585
msgid "Scales play a crucial role in the checkout process, especially for products sold by weight, rather than fixed pricing."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:577
#: ../../content/applications/general/iot/config/troubleshooting.rst:589
msgid "Set up Ariva S scales"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:579
#: ../../content/applications/general/iot/config/troubleshooting.rst:591
msgid "Odoo has determined that a specific setting in Ariva S series scales (manufactured by Mettler-Toledo, LLC.) needs modification, and a dedicated Mettler :abbr:`USB (Universal Serial Bus)`-to-proprietary RJ45 cable is required for the scale to function with Odoo's :abbr:`IoT (Internet of Things)` box."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:584
#: ../../content/applications/general/iot/config/troubleshooting.rst:596
msgid "To correctly configure the scale for recognition by the :abbr:`IoT (Internet of Things)` box, follow this setup process for the Ariva S series scales."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:588
#: ../../content/applications/general/iot/config/troubleshooting.rst:600
msgid "It is crucial to use the official Mettler :abbr:`USB (Universal Serial Bus)`-to-RJ45 cable during this process."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:592
#: ../../content/applications/general/iot/config/troubleshooting.rst:604
msgid "Cable"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:594
#: ../../content/applications/general/iot/config/troubleshooting.rst:606
msgid "The Mettler part number is 72256236 - :abbr:`USB (Universal Serial Bus)`-to-:abbr:`POS (Point of Sale)` cable. Contact Mettler, or a partner, to purchase an authentic cable. Note that **no other** cable outside of this Mettler cable works for this configuration. Using a serial-only cable attached to a serial-to-:abbr:`USB (Universal Serial Bus)` adapter is **not** effective."
msgstr ""
@ -5588,43 +5600,43 @@ msgstr ""
msgid "Authentic Mettler USB to POS cable, part number 72256236."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:606
#: ../../content/applications/general/iot/config/troubleshooting.rst:618
msgid "Refer to Mettler's Setup Guide for Ariva S series scales during the following configuration: `Ariva Checkout Scale User's Guide <https://www.mt.com/dam/RET_DOCS/Ariv.pdf>`_."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:609
#: ../../content/applications/general/iot/config/troubleshooting.rst:621
msgid "To begin, go to page 17 in the above manual for *Setup*. This guide lists potential settings for the Ariva S series scales."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:612
#: ../../content/applications/general/iot/config/troubleshooting.rst:624
msgid "Follow the instructions, along with the following process, to set the scale to setup mode. First, hold the **>T<** button for eight seconds, or until :guilabel:`CONF` appears."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:615
#: ../../content/applications/general/iot/config/troubleshooting.rst:627
msgid "Next, press **>T<** until :guilabel:`GRP 3` appears, then press **>0<** to confirm."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:617
#: ../../content/applications/general/iot/config/troubleshooting.rst:629
msgid "Under :guilabel:`3.1`, ensure the setting is set to :guilabel:`1` (USB Virtual COM ports). Press **>T<** to cycle through the options under group 3.1."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:620
#: ../../content/applications/general/iot/config/troubleshooting.rst:632
msgid "Once :guilabel:`3.1` is set to :guilabel:`1`, press **>0<** to confirm the selection. Continue to press **>0<** until :guilabel:`GRP 4` appears."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:623
#: ../../content/applications/general/iot/config/troubleshooting.rst:635
msgid "Now, press **>T<** until :guilabel:`EXIT` appears."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:626
#: ../../content/applications/general/iot/config/troubleshooting.rst:638
msgid "Do **not** make any other changes unless otherwise needed."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:628
#: ../../content/applications/general/iot/config/troubleshooting.rst:640
msgid "Once :guilabel:`EXIT` appears, press **>0<**. Following this, press **>0<** again to :guilabel:`SAVE`. Now the scale restarts."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:631
#: ../../content/applications/general/iot/config/troubleshooting.rst:643
msgid "Finally, restart the :abbr:`IoT (Internet of Things)` box to recognize the changes made on the scale's configuration. After restarting, the scale appears as `Toledo 8217`, as opposed to the previous display, where it appeared as `Adam Equipment Serial`."
msgstr ""

626
locale/sources/hr.pot
View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Project-Id-Version: Odoo 18.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-09-24 10:43+0000\n"
"POT-Creation-Date: 2024-10-07 14:21+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -246,6 +246,10 @@ msgstr ""
msgid ":doc:`appraisals/appraisal_analysis`"
msgstr ""
#: ../../content/applications/hr/appraisals.rst:177
msgid ":doc:`appraisals/skills_evolution`"
msgstr ""
#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:3
msgid "Appraisal analysis"
msgstr ""
@ -415,10 +419,12 @@ msgid "A report showing only the appraisals the user is responsible for, by stat
msgstr ""
#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:114
#: ../../content/applications/hr/appraisals/skills_evolution.rst:163
msgid ":doc:`Odoo essentials reporting <../../essentials/reporting>`"
msgstr ""
#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:115
#: ../../content/applications/hr/appraisals/skills_evolution.rst:164
msgid ":doc:`../../essentials/search`"
msgstr ""
@ -574,23 +580,23 @@ msgstr ""
msgid "**Company**: the company the employee works for. This only appears in a multi-company database."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:29
#: ../../content/applications/hr/appraisals/new_appraisals.rst:28
msgid "**Date**: the date the appraisal was requested, or is scheduled for in the future."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:30
#: ../../content/applications/hr/appraisals/new_appraisals.rst:29
msgid "**Activities**: any :doc:`activities <../../essentials/activities>` that are scheduled for the appraisal, such as *Meetings* or *Phone Calls*."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:32
#: ../../content/applications/hr/appraisals/new_appraisals.rst:31
msgid "**Manager**: the employee's manager, indicated by the profile icon in the bottom-right corner of an appraisal card."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:34
#: ../../content/applications/hr/appraisals/new_appraisals.rst:33
msgid "**Status banner**: the status of the appraisal. A banner appears if an appraisal is marked as either *Canceled* or *Done*. If no banner is present, that means the appraisal has not happened, or has not been scheduled yet."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:38
#: ../../content/applications/hr/appraisals/new_appraisals.rst:37
msgid "To view the details of any appraisal, click on the card to open the appraisal form."
msgstr ""
@ -598,83 +604,83 @@ msgstr ""
msgid "The Appraisals dashboard with each appraisal in its own box."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:45
#: ../../content/applications/hr/appraisals/new_appraisals.rst:44
msgid "Create an appraisal"
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:47
#: ../../content/applications/hr/appraisals/new_appraisals.rst:46
msgid "To create a new appraisal, click the :guilabel:`New` button in the upper-left corner of the :guilabel:`Appraisals` dashboard. Doing so reveals a blank appraisal form. After entering a name in the first blank field, proceed to enter the following information on the form:"
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:51
#: ../../content/applications/hr/appraisals/new_appraisals.rst:50
msgid ":guilabel:`Manager`: select the employee's manager from the drop-down menu. The manager is responsible for completing the *Manager's Feedback* section of the appraisal. This field auto-populates after the employee is selected, if they have a manager set on their employee profile."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:55
#: ../../content/applications/hr/appraisals/new_appraisals.rst:54
msgid ":guilabel:`Appraisal Date`: the current date is automatically entered in this field. This field is automatically updated once the appraisal is completed or cancelled, with the corresponding date of completion or cancellation."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:58
#: ../../content/applications/hr/appraisals/new_appraisals.rst:57
msgid ":guilabel:`Department`: select the employee's department from the drop-down menu. This field auto-populates after the employee is selected, if they have a department set on their employee profile."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:61
#: ../../content/applications/hr/appraisals/new_appraisals.rst:60
msgid ":guilabel:`Company`: select the employee's company from the drop-down menu. This field auto-populates after the employee is selected, if they have a company set on their employee profile."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:66
#: ../../content/applications/hr/appraisals/new_appraisals.rst:65
msgid "The only required fields for the appraisal form are the employee's name, the :guilabel:`Manager`, and the :guilabel:`Company`."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:69
#: ../../content/applications/hr/appraisals/new_appraisals.rst:68
msgid "Once the form is complete, click the :guilabel:`Confirm` button to confirm the appraisal request."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:71
#: ../../content/applications/hr/appraisals/new_appraisals.rst:70
msgid "Once confirmed, the employee receives an email stating that an appraisal was requested, and is then prompted to schedule an appraisal date."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:74
#: ../../content/applications/hr/appraisals/new_appraisals.rst:73
msgid "The status changes to :guilabel:`Confirmed`, and the :guilabel:`Employee's Feedback` section of the :guilabel:`Appraisal` tab is grayed out. The information in that section only appears after the self-assessment is published by the employee. The :guilabel:`Final Rating` field also appears once the appraisal request is confirmed."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:79
#: ../../content/applications/hr/appraisals/new_appraisals.rst:78
msgid "If there are any existing appraisals for the employee, an :guilabel:`Appraisal` smart button appears at the top of the page, listing the total number of appraisals there are for the employee."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:83
#: ../../content/applications/hr/appraisals/new_appraisals.rst:82
msgid "Ask for feedback"
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:85
#: ../../content/applications/hr/appraisals/new_appraisals.rst:84
msgid "As part of the appraisal process, the manager can request feedback on an employee from anyone in the company. Feedback is usually requested from co-workers and other people who interact with, or work with, the employee. This is to get a more well-rounded view of the employee, and aid in the manager's overall assessment."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:90
#: ../../content/applications/hr/appraisals/new_appraisals.rst:89
msgid "To request feedback, the appraisal **must** be confirmed. Once confirmed, an :guilabel:`Ask Feedback` button appears at the top of the form."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:93
#: ../../content/applications/hr/appraisals/new_appraisals.rst:92
msgid "When the :guilabel:`Ask Feedback` button is clicked, an :guilabel:`Ask Feedback` email pop-up form appears, using the :guilabel:`Appraisal: Ask Feedback` email template, which sends the :guilabel:`360 Feedback` survey."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:97
#: ../../content/applications/hr/appraisals/new_appraisals.rst:96
msgid "Enter the employees being asked to complete the survey in the :guilabel:`Recipients` field. Multiple employees may be selected."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:100
#: ../../content/applications/hr/appraisals/new_appraisals.rst:99
msgid "The email template has dynamic placeholders to personalize the message. Add any additional text to the email, if desired."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:103
#: ../../content/applications/hr/appraisals/new_appraisals.rst:102
msgid "If required, an :guilabel:`Answer Deadline` can be added, as well."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:105
#: ../../content/applications/hr/appraisals/new_appraisals.rst:104
msgid "If any attachments are needed, click the :icon:`fa-paperclip` :guilabel:`Attachments` button, and a file explorer window appears. Navigate to the file(s), select them, then click :guilabel:`Open`."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:108
#: ../../content/applications/hr/appraisals/new_appraisals.rst:107
msgid "When the email is ready to send, click :guilabel:`Send.`"
msgstr ""
@ -682,27 +688,27 @@ msgstr ""
msgid "The email pop-up when requesting feedback from other employees."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:115
#: ../../content/applications/hr/appraisals/new_appraisals.rst:114
msgid "Appraisal form"
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:117
#: ../../content/applications/hr/appraisals/new_appraisals.rst:116
msgid "Once an appraisal is confirmed, the next steps require the employee to fill out the self-assessment, after which the manager completes their assessment."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:123
#: ../../content/applications/hr/appraisals/new_appraisals.rst:122
msgid "Employee's feedback"
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:125
#: ../../content/applications/hr/appraisals/new_appraisals.rst:124
msgid "To complete their portion of feedback, employees should navigate to the main :menuselection:`Appraisals application` dashboard, where the only entries visible are appraisals for the employee, themselves, and/or anyone they manage and have to provide manager feedback for."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:129
#: ../../content/applications/hr/appraisals/new_appraisals.rst:128
msgid "Click on the appraisal to open the appraisal form. Enter responses in the :guilabel:`Employee's Feedback` section, under the :guilabel:`Appraisal` tab."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:132
#: ../../content/applications/hr/appraisals/new_appraisals.rst:131
msgid "When completed, click the :guilabel:`Not Visible to Manager` toggle (the default setting once an appraisal is confirmed). When clicked, the toggle changes to :guilabel:`Visible to Manager`."
msgstr ""
@ -710,19 +716,19 @@ msgstr ""
msgid "The feedback section for the employee with the toggle button highlighted."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:142
#: ../../content/applications/hr/appraisals/new_appraisals.rst:141
msgid "Manager's feedback"
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:144
#: ../../content/applications/hr/appraisals/new_appraisals.rst:143
msgid "After the employee has completed the :guilabel:`Employee's Feedback` section, under the :guilabel:`Appraisal` tab, it is time for the manager to fill out the :guilabel:`Manager's Feedback` section."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:148
#: ../../content/applications/hr/appraisals/new_appraisals.rst:147
msgid "The manager enters their responses in the fields in the :ref:`same manner as the employee <appraisals/employee-feedback>`."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:151
#: ../../content/applications/hr/appraisals/new_appraisals.rst:150
msgid "When the feedback section is completed, click the :guilabel:`Not Visible to Employee` toggle (the default setting once an appraisal is confirmed). When clicked, the toggle changes to :guilabel:`Visible to Employee`."
msgstr ""
@ -730,32 +736,32 @@ msgstr ""
msgid "The feedback section for both employees and managers. The toggle buttons are highlighted."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:160
#: ../../content/applications/hr/appraisals/new_appraisals.rst:159
#: ../../content/applications/hr/recruitment/add-new-applicants.rst:167
msgid "Skills tab"
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:162
#: ../../content/applications/hr/appraisals/new_appraisals.rst:161
msgid "Part of an appraisal is evaluating an employee's skills, and tracking their progress over time. The :guilabel:`Skills` tab of the appraisal form auto-populates with the skills from the :ref:`employee form <employees/skills>`, once an appraisal is confirmed."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:166
#: ../../content/applications/hr/appraisals/new_appraisals.rst:165
msgid "Each skill is grouped with like skills, and the :guilabel:`Skill Level`, :guilabel:`Progress`, and :guilabel:`Justification` are displayed for each skill."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:169
#: ../../content/applications/hr/appraisals/new_appraisals.rst:168
msgid "Update any skills, or add any new skills to the :guilabel:`Skills` tab."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:171
#: ../../content/applications/hr/appraisals/new_appraisals.rst:170
msgid "If a skill level has increased, a reason for the improved rating can be entered into the :guilabel:`Justification` field, such as `took a fluency language test` or `received Javascript certification`."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:176
#: ../../content/applications/hr/appraisals/new_appraisals.rst:175
msgid "Refer to the :ref:`Create a new employee <employees/skills>` document for detailed instructions on adding or updating a skill."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:179
#: ../../content/applications/hr/appraisals/new_appraisals.rst:178
msgid "After an appraisal is completed, and the skills have been updated, the next time an appraisal is confirmed, the updated skills populate the :guilabel:`Skills` tab."
msgstr ""
@ -763,75 +769,75 @@ msgstr ""
msgid "The skills tab of an appraisal form, all filled out."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:187
#: ../../content/applications/hr/appraisals/new_appraisals.rst:186
msgid "The :guilabel:`Skills` tab can be modified **after** the employee and their manager have met and discussed the employee's appraisal."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:190
#: ../../content/applications/hr/appraisals/new_appraisals.rst:189
msgid "This is a common situation as the manager may not have all the necessary information to properly assess and update the employee's skills before meeting."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:194
#: ../../content/applications/hr/appraisals/new_appraisals.rst:193
msgid "Private Note tab"
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:196
#: ../../content/applications/hr/appraisals/new_appraisals.rst:195
msgid "If managers want to leave notes that are only visible to other managers, they can be entered in the :guilabel:`Private Note` tab. This can be done before or after meeting with the employee to discuss the appraisal."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:200
#: ../../content/applications/hr/appraisals/new_appraisals.rst:199
msgid "The employee being evaluated does **not** have access to this tab, and the tab does **not** appear on their appraisal."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:204
#: ../../content/applications/hr/appraisals/new_appraisals.rst:203
msgid "Schedule a meeting"
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:206
#: ../../content/applications/hr/appraisals/new_appraisals.rst:205
msgid "Once both portions of an appraisal are completed (the :ref:`employee <appraisals/employee-feedback>` and :ref:`manager <appraisals/manager-feedback>` feedback sections), it is time for the employee and manager to meet and discuss the appraisal."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:210
#: ../../content/applications/hr/appraisals/new_appraisals.rst:209
msgid "A meeting can be scheduled in one of two ways: either from the *Appraisals* application dashboard, or from an individual appraisal card."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:213
#: ../../content/applications/hr/appraisals/new_appraisals.rst:212
msgid "To schedule an appraisal from the dashboard of the *Appraisals* application, first navigate to :menuselection:`Appraisals app --> Appraisals`."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:216
#: ../../content/applications/hr/appraisals/new_appraisals.rst:215
msgid "Click the :icon:`fa-clock-o` :guilabel:`(clock)` icon, beneath the appraisal date on the desired appraisal card, and a pop-up window appears. Then, click :icon:`fa-plus` :guilabel:`Schedule an activity` to create an activity from a :guilabel:`Schedule Activity` pop-up form that appears."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:220
#: ../../content/applications/hr/appraisals/new_appraisals.rst:219
msgid "Select :guilabel:`Meeting` for the :guilabel:`Activity Type` from the drop-down menu. Doing so causes the form to change, so only the :guilabel:`Activity Type` and :guilabel:`Summary` fields appear."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:224
#: ../../content/applications/hr/appraisals/new_appraisals.rst:223
msgid "Enter a brief description in the :guilabel:`Summary` field of the :guilabel:`Schedule Activity` pop-up form, such as `Annual Appraisal for (Employee)`."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:227
#: ../../content/applications/hr/appraisals/new_appraisals.rst:226
msgid "Next, click the :guilabel:`Open Calendar` button. From the calendar page that appears, navigate to, and double-click on, the desired date and time for the meeting."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:230
#: ../../content/applications/hr/appraisals/new_appraisals.rst:229
msgid "Doing so opens a :guilabel:`New Event` pop-up form. From this pop-up form, make any desired modifications, such as designating a :guilabel:`Start` time, or modifying the default :guilabel:`Title` to the meeting."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:234
#: ../../content/applications/hr/appraisals/new_appraisals.rst:233
msgid "Add the appraisee in the :guilabel:`Attendees` section, and include anyone else who should also be in the meeting, if necessary."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:237
#: ../../content/applications/hr/appraisals/new_appraisals.rst:236
msgid "To make the meeting a video call, instead of an in-person meeting, click :icon:`fa-plus` :guilabel:`Odoo meeting`, and a :guilabel:`Videocall URL` link appears in the field."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:240
#: ../../content/applications/hr/appraisals/new_appraisals.rst:239
msgid "Once all the desired changes are complete, click :guilabel:`Save & Close`."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:242
#: ../../content/applications/hr/appraisals/new_appraisals.rst:241
msgid "The meeting now appears on the calendar, and the invited parties are informed, via email."
msgstr ""
@ -839,54 +845,244 @@ msgstr ""
msgid "The meeting form with all information entered for Ronnie Hart's annual appraisal."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:248
#: ../../content/applications/hr/appraisals/new_appraisals.rst:247
msgid "The other way to schedule a meeting is from the individual appraisal form. To do this, navigate to the :menuselection:`Appraisal app` dashboard, then click on an appraisal card."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:251
#: ../../content/applications/hr/appraisals/new_appraisals.rst:250
msgid "Next, click on the :icon:`fa-calendar` :guilabel:`Meeting` smart button, and the calendar loads. Follow the same directions above to create the meeting."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:254
#: ../../content/applications/hr/appraisals/new_appraisals.rst:253
msgid "For more detailed information on how to schedule activities, refer to the :doc:`activities <../../essentials/activities>` documentation."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:258
#: ../../content/applications/hr/appraisals/new_appraisals.rst:257
msgid "If no meetings are scheduled, the :guilabel:`Meeting` smart button reads :guilabel:`No Meeting`."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:261
#: ../../content/applications/hr/appraisals/new_appraisals.rst:260
msgid "Complete an appraisal"
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:263
#: ../../content/applications/hr/appraisals/new_appraisals.rst:262
msgid "After the appraisal is complete, and both the manager and employee have met to discuss the appraisal, the appraisal can be marked as *Done*. When completed, click the :guilabel:`Mark as Done` button on the appraisal form, located in the top-left corner."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:267
#: ../../content/applications/hr/appraisals/new_appraisals.rst:266
msgid "Once the appraisal is marked as *Done*, the :guilabel:`Mark as Done` button disappears, and a :guilabel:`Reopen` button appears."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:271
#: ../../content/applications/hr/appraisals/new_appraisals.rst:270
msgid "Modifications are **not** possible once the appraisal is marked as done."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:273
#: ../../content/applications/hr/appraisals/new_appraisals.rst:272
msgid "To make any changes to an appraisal that is marked as *Done*, click the :guilabel:`Reopen` button."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:276
msgid "Then, click the :guilabel:`Confirm` button that appears, and make any modifications needed. Once all modifications are complete, click the the :guilabel:`Mark as Done` button again."
#: ../../content/applications/hr/appraisals/new_appraisals.rst:275
msgid "Then, click the :guilabel:`Confirm` button that appears, and make any modifications needed. Once all modifications are complete, click the :guilabel:`Mark as Done` button again."
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:280
#: ../../content/applications/hr/appraisals/new_appraisals.rst:279
msgid ":doc:`../appraisals/goals`"
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:281
#: ../../content/applications/hr/appraisals/new_appraisals.rst:280
msgid ":doc:`../appraisals/appraisal_analysis`"
msgstr ""
#: ../../content/applications/hr/appraisals/new_appraisals.rst:281
msgid ":doc:`../appraisals/skills_evolution`"
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:3
msgid "Skills evolution"
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:5
msgid "In Odoo's **Appraisals** app, it is possible to view employee's skills as they progress over time in the :ref:`Skills Evolution <appraisals/identify-skills-evolution>` report, also known as the *Appraisal Skills Report*."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:9
msgid "Managers can use this to see who is achieving their various skill goals set on their appraisals, who is meeting their skill deadlines, who has the highest performance in terms of skill development, and more."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:13
msgid "The *Skills Evolution* report also provides the ability to :ref:`search for employees with specific skills <appraisals/identify-skills>` at certain levels, which can be helpful for scenarios where specific skills are required."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:20
msgid "Skills evolution report"
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:22
msgid "To access this *Skills Evolution* report, navigate to :menuselection:`Appraisals app --> Reporting --> Skills Evolution`."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:25
msgid "Doing so reveals the :guilabel:`Appraisal Skills Report` page, which displays a report of all skills, grouped by employee, in alphabetical order, by default."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:29
msgid "Skill levels are **only** updated after an appraisal is marked as done. Any skill level changes from ongoing appraisals that have **not** been finalized are **not** included in this report."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:32
msgid "All the :guilabel:`Employee` lines are expanded, with all the various skill types nested below. Each individual skill type is collapsed, by default. To view the individual skills contained within a skill type, click anywhere on the skill type line to expand the data."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:36
msgid "Each skill has the following information listed:"
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:38
#: ../../content/applications/hr/attendances.rst:218
msgid ":guilabel:`Employee`: the name of the employee."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:39
msgid ":guilabel:`Skill Type`: the category the skill falls under."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:40
msgid ":guilabel:`Skill`: the specific, individual skill."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:41
msgid ":guilabel:`Previous Skill Level`: the level the employee had previously achieved for the skill."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:42
msgid ":guilabel:`Previous Skill Progress`: the previous percentage of competency achieved for the skill (based on the :guilabel:`Skill Level`)."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:44
msgid ":guilabel:`Current Skill Level`: the current level the employee has achieved for the skill."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:45
msgid ":guilabel:`Current Skill Progress`: the current percentage of competency achieved for the skill."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:46
msgid ":guilabel:`Justification`: any notes entered on the skill, explaining the progress."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:48
msgid "The color of the skill text indicates any changes from the previous appraisal. Skill levels that have increased since the last appraisal appear in green, as an *Improvement*. Skill levels that have **not** changed appear in black, as *No Change*. Skills that have regressed appear in red, as *Regression*."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:53
msgid "This report can be modified to find specific information by adjusting the :ref:`filters <search/filters>` and :ref:`groupings <search/group>` set in the search bar at the top."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1
msgid "A report showing all the skills grouped by employee."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:63
msgid "Use case: Identify employees with specific skills"
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:65
msgid "Since the :guilabel:`Appraisal Skills Report` organizes all skills by employee, it can be difficult to find employees with a specific skill at a specific level. To find these employees, a custom filter must be used."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:69
msgid "In this example, the report is modified to show employees with an expert level of Javascript knowledge. To view only those employees, first remove all active filters in the search bar."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:72
msgid "Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the search bar, then click :guilabel:`Add Custom Filter` beneath the :icon:`fa-filters` :guilabel:`Filters` column to load an :guilabel:`Add Custom Filter` pop-up window."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:76
msgid "Using the drop-down menu in the first field, select :guilabel:`Skill`. Then, keep the second field as-is, and select :guilabel:`Javascript` from the third drop-down menu in the third field."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:79
msgid "Next, click :guilabel:`New Rule`, and another line appears. In this second line, select :guilabel:`Current Skill Level` for the first drop-down field, leave the second field as-is, then select :guilabel:`Expert` for the third drop-down field."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:83
msgid "After the :guilabel:`New Rule` button is clicked, the word :guilabel:`\"any\"` in the sentence :guilabel:`Match any of the following rules:`, changes from plain text into a drop-down menu. Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon after the word :guilabel:`any`, and select :guilabel:`all`."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:88
msgid "Finally, click the :guilabel:`Add` button."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1
#: ../../content/applications/hr/appraisals/skills_evolution.rst:0
msgid "The Custom Filter pop-up with the parameters set."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:94
msgid "Now, only employees that have an :guilabel:`Expert` level for the skill :guilabel:`Javascript` appear. In this example, only :guilabel:`Marc Demo` meets these criteria."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1
msgid "The employees with expert Javascript skills."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:102
msgid "Use case: Assess highest improvement"
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:104
msgid "Another way to modify the :guilabel:`Appraisal Skills Report` is to identify the employee who has the highest amount of improved skills over a specific period of time."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:107
msgid "To view this information, first remove the default filter in the search bar. Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the search bar, then click :guilabel:`Improvement` beneath the :icon:`fa-filter` :guilabel:`Filters` column. Enabling this filter only presents skills that have improved."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:112
msgid "It is possible to view the skills that have improved over a period of time, such as a specific quarter, or month. With the search bar drop-down menu still expanded, click :guilabel:`Add Custom Filter` at the bottom of the :icon:`fa-filter` :guilabel:`Filters` column, and an :guilabel:`Add Custom Filter` pop-up window appears."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:117
msgid "Select :guilabel:`Create Date` for the first drop-down field, then select :guilabel:`is between` for the second drop-down field. Once :guilabel:`is between` is selected, a second field appears after the last field. Using the calendar selector, select the date range to apply the filter to. Once all the fields are properly formatted, click :guilabel:`Add`."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:122
msgid "The custom filter presents only the skills that have improved during the specified time period, organized by employee."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:126
msgid "To determine the employee with the most amount of improved skills for the third quarter, remove the default filter in the search bar of the :guilabel:`Appraisal Skills Report`. Next, activate the :guilabel:`Improvement` filter, then click :guilabel:`Add Custom Filter` at the bottom of the :icon:`fa-filter` :guilabel:`Filters` column."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:131
msgid "In the resulting :guilabel:`Add Custom Filter` pop-up window, select :guilabel:`Create Date` for the first drop-down field, then select :guilabel:`is between` for the second drop-down field. Two date fields appear after :guilabel:`is between` is selected."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:135
msgid "Using the calendar selector, set the first date to :guilabel:`07/01/2024` and the second date to :guilabel:`09/30/2024`, then click :guilabel:`Add`."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:138
msgid "These filters present only the skills that have improved during the third quarter (between July 1st and September 30th, 2024), organized by employee."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:144
msgid "To view the number of employees and skills in further detail, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner to view the data in a pivot table. This presents a pivot table with the employees populating the rows, and the only visible column represents the total number of improved skills."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:149
msgid "To expand more rows or columns to view which skill types had the most overall improvement, click :icon:`fa-plus-square` :guilabel:`Total` above the :guilabel:`Count` column, then click :guilabel:`Skill Type` from the resulting drop-down menu. This organizes the total improved skills by their respective skill type."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:155
msgid "In this example, it is determined that :guilabel:`Charles Reginald` had the largest improvement in the third quarter, with six improved skills. Additionally, they also had the most skill improvements for both :guilabel:`Languages` (three) and :guilabel:`Programming Languages` (two)."
msgstr ""
#: ../../content/applications/hr/appraisals/skills_evolution.rst:0
msgid "The pivot table showing the skill improvements for the third quarter."
msgstr ""
#: ../../content/applications/hr/attendances.rst:5
msgid "Attendances"
msgstr ""
@ -1114,10 +1310,6 @@ msgstr ""
msgid "Main details"
msgstr ""
#: ../../content/applications/hr/attendances.rst:218
msgid ":guilabel:`Employee`: the name of the employee."
msgstr ""
#: ../../content/applications/hr/attendances.rst:219
msgid ":guilabel:`Check In`: the date and time the employee checked in."
msgstr ""
@ -1682,6 +1874,158 @@ msgstr ""
msgid "Odoo *Employees* organizes a company's employee records, contracts, and departments."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:3
msgid "Certifications"
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:5
msgid "When jobs require specific knowledge, it is necessary to track employee certifications to ensure the necessary knowledge and certifications are in place."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:8
msgid "Certifications include classes, tests, professional seminars, and more. There are no restrictions in terms of what type of certification records can be added in Odoo."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:12
msgid "To access the *Employee Certifications* report, the **Surveys** app **must** be installed."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:15
msgid "View certifications"
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:17
msgid "To view a full list of all employee certifications, navigate to :menuselection:`Employees app --> Reporting --> Certifications`."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:20
msgid "All certifications appear in a list view, grouped by employee. Each certification entry displays the following:"
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:23
msgid ":guilabel:`Employee`: the employee's name, along with their avatar image."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:24
msgid ":guilabel:`Name`: the title of the certification."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:25
msgid ":guilabel:`Validity Start`: when the employee received the certification."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:26
msgid ":guilabel:`Validity End`: when the certification expires."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:27
msgid ":guilabel:`Certification`: the corresponding course in the **Surveys** app that was completed by the employee, if applicable."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:30
msgid "The entries are also color-coded. Current certifications that are still valid appear in black, expired certifications appear in red, and certifications that are going to expire within the next 90 days appear in orange."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:-1
msgid "The list of employee certifications."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:39
msgid "**Only** certification records with the *Display Type* set to *Certification* on their :ref:`certification form <employees/certifications-form>` appear on the :guilabel:`Employee Certifications` report. All other certifications appear in the resume section of the :doc:`employee form <new_employee>`."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:45
msgid "View certifications by expiration status"
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:47
msgid "When managing a large number of employees with a variety of certifications, it can be difficult to determine which employees need to keep necessary certifications current in the default list view. In this scenario, it is beneficial to view the certifications by expiration status."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:51
msgid "To do so, navigate to :menuselection:`Employees app --> Reporting --> Certifications`. Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar, then click :guilabel:`Add Custom Group`, revealing a drop-down menu. Click :guilabel:`Expiration Status`, then click away from the drop-down menu to close it."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:56
msgid "After doing so, all the certifications are organized by status, starting with :guilabel:`Expired` certifications, then certifications that are :guilabel:`Expiring` soon (within the next 90 days), and lastly, certifications that are still :guilabel:`Valid`."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:60
msgid "This view provides an easy way to see which employees have certifications that are going to expire soon, to determine which employees need to take action to keep their certifications current."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:-1
msgid "The list of employee certifications, grouped by status."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:70
msgid "Log a certification"
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:72
msgid "To log a certification for an employee, navigate to :menuselection:`Employees app --> Reporting --> Certifications`. Click :guilabel:`New`, and a blank certification form loads. Enter the following information on the form:"
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:76
msgid ":guilabel:`Title`: Enter a short description for the certification in this field."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:77
msgid ":guilabel:`Employee`: Using the drop-down menu, select the employee who received the certification."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:79
msgid ":guilabel:`Type`: Using the drop-down menu, select the type of certification received. This field determines where on the employee's resume the certification appears. To create a new :guilabel:`Type`, enter the type in the field, then click :guilabel:`Create \"type\"`."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:83
msgid "The default options are:"
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:85
msgid ":guilabel:`Experience`: Select this option to have the certification appear in the *Experience* section of the *Resume* tab on the :doc:`employee form <new_employee>`."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:87
msgid ":guilabel:`Education`: Select this option to have the certification appear in the *Education* section of the *Resume* tab on the :doc:`employee form <new_employee>`."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:89
msgid ":guilabel:`Internal Certification`: Select this option to have the certification appear in the *Internal Certification* section of the *Resume* tab on the :doc:`employee form <new_employee>`."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:91
msgid ":guilabel:`Completed Internal Training`: Select this option to have the certification appear in *Completed Internal Training* section of the *Resume* tab on the :doc:`employee form <new_employee>`."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:95
msgid ":guilabel:`Display Type`: Select the visibility of the certification in this field. The default options are:"
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:98
msgid ":guilabel:`Classic`: Select this option to have the certification appear in the *Resume* section of the employee form, and **not** appear on the *Employee Certifications* report."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:100
msgid ":guilabel:`Course`: Select this option to have the certification appear in the *Resume* section of the employee form, and **not** appear on the *Employee Certifications* report. Once this option is selected, a :guilabel:`Course` field appears beneath the :guilabel:`Display Type` field. Using the drop-down menu, select the course the employee took. The course is created in the **Surveys** app."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:105
msgid ":guilabel:`Certification`: Select this option to have the certification appear in the *Resume* section of the employee form, **and** appear on the *Employee Certifications* report. Once this is selected, a :guilabel:`Certification` field appears beneath the :guilabel:`Display Type` field. Using the drop-down menu, select the certification the employee took."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:110
msgid ":guilabel:`Description`: Enter a description for the certification in this field."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:111
msgid ":guilabel:`Duration`: Click into the first field, and a calendar pop-over window appears. Click on the start and end dates for the certification validity period. When the correct dates are selected, click :icon:`fa-check` :guilabel:`Apply`, and both fields are populated."
msgstr ""
#: ../../content/applications/hr/employees/certifications.rst:-1
msgid "A certification form filled out for an OSHA certificate for construction."
msgstr ""
#: ../../content/applications/hr/employees/departments.rst:3
msgid "Departments"
msgstr ""
@ -2608,6 +2952,102 @@ msgstr ""
msgid "Now, only archived employees appear on the dashboard. Click on the desired employee to open their employee form. On this form, click the :icon:`fa-gear` :guilabel:`(gear)` icon in the top-left corner, then click :guilabel:`Send HR Documents Access Link` from the resulting drop-down menu. The chatter logs that the link was sent."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:3
msgid "Employee retention report"
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:5
msgid "It is possible to determine the retention rate for a company by modifying an existing report."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:7
msgid "First, navigate to :menuselection:`Employees app --> Reporting --> Contracts` to open the :guilabel:`Employee Analysis` report. This report shows the number of all employees for the :guilabel:`Last 365 Days`, in a default :icon:`fa-line-chart` :guilabel:`Line Chart`."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:-1
msgid "The default Employees Analysis report."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:15
msgid "Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the upper-left corner, revealing a drop-down menu. Click :guilabel:`# Departure Employee` in the list, then click away from the drop-down menu to close it. Now, the report shows all the employees who were archived for the :guilabel:`Last 365 Days`."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:20
msgid "To view this information in an easier format, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the upper-right corner, and the data is presented in a pivot table."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:23
msgid "The various employees, organized by department, populate the rows. The columns display the following totals: the monthly :guilabel:`Wage`, the :guilabel:`Fuel Card` budget, total :guilabel:`Annual Employee Budget` (also referred to as the *annual salary*), the number of :guilabel:`New Employees`, as well as the number of :guilabel:`Departure Employees` (employees who left)."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:-1
msgid "The Employees Analysis report, modified to show departed employees only."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:33
msgid "Employee retention rate comparison report"
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:35
msgid "It is possible to compare data only for employees who left, compared to the total current employees, between two separate time periods. This is commonly referred to as the *employee retention rate*."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:38
msgid "To view these metrics, first open the :guilabel:`Employee Analysis` report by navigating to :menuselection:`Employees app --> Reporting --> Contracts`. Click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the upper-right corner to view the information in a pivot table."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:42
msgid "Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the upper-left corner, revealing a drop-down menu. Click :guilabel:`# New Employees`, :guilabel:`Annual Employee Budget`, :guilabel:`Fuel Card`, and :guilabel:`Wage` in the list, to deselect these metrics and hide them in the table. Then, click :guilabel:`Count` at the bottom of the list to enable that metric."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:47
msgid "Click away from the drop-down menu to close it. Now, the report shows all the employees who left the company (:guilabel:`# Departure Employee`), as well as the total number of employees (:guilabel:`Count`), for the :guilabel:`Last 365 Days`."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:51
msgid "To compare the data for the current year with the previous year, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar, revealing multiple filter and grouping options. Click :guilabel:`Last 365 Days` in the :icon:`fa-filter` :guilabel:`Filters` column, to turn off that filter. Then, click :guilabel:`Date`, and click the current year (in this example, :guilabel:`2024`) from the resulting drop-down menu."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:57
msgid "Once a selection is made beneath :guilabel:`Date` in the :icon:`fa-filter` :guilabel:`Filters` column, a :icon:`fa-adjust` :guilabel:`Comparison` column appears. Click :guilabel:`Date: Previous Year` in the new column, then click off of the drop-down menu to close it."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:62
msgid "In Odoo, in order to access the :icon:`fa-adjust` :guilabel:`Comparison` column, a specific time *other than* :guilabel:`Last 365 Days` **must** be selected. If not, the :icon:`fa-adjust` :guilabel:`Comparison` column is **not** visible."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:66
msgid "Now, the pivot table displays the total number of employees who left the company (:guilabel:`# Departure Employee`), as well as the total number of employees (:guilabel:`Count`) in the columns. These are further divided by the two different years, and also displays the :guilabel:`Variation` between the two."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:71
msgid "The rows display the departments, and lists each individual employee for each department, in the rows."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:74
msgid "For a more concise view of this report, click :icon:`fa-minus-square-o` :guilabel:`Total` above the top row of the departments and employees, to collapse the rows. Now, the table presents the total number of employees who left the company for both years, compared to the total number of employees for both years, including the difference, in a percentage."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:80
msgid "In this example, :guilabel:`3` employees out of :guilabel:`83` left in 2023, and :guilabel:`8` employees out of :guilabel:`202` left in 2024. There was a :guilabel:`166.67%` increase in the employees who left in 2024 as compared to 2023. Additionally, there was a :guilabel:`143.37%` increase in the total number of employees in 2024 as compared to 2023."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:0
msgid "The report modified to show the difference between two years of employees who left."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:89
msgid "To view more detailed rates for each department, click :icon:`fa-plus-square` :guilabel:`Total` in the single row, revealing a drop-down menu, and click :guilabel:`Department`. Click away from the drop-down to close it, and now the pivot table displays the total number of employees who left (:guilabel:`# Departure Employee`), the total number of employees (:guilabel:`Count`), and the :guilabel:`Variation` (in a percentage) for both 2023 and 2024, organized by department."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:96
msgid "In this example, it can be determined that the :guilabel:`Management` department had the best retention rate in 2024 as compared to 2023, with a :guilabel:`Variation` rate of :guilabel:`-100%`. Additionally, it can be determined that the :guilabel:`Management / Research & Development` department had the most turnover, with a :guilabel:`Variation` of :guilabel:`300%`."
msgstr ""
#: ../../content/applications/hr/employees/retention_report.rst:0
msgid "The expanded employee retention report by department."
msgstr ""
#: ../../content/applications/hr/fleet.rst:5
msgid "Fleet"
msgstr ""
@ -4181,7 +4621,7 @@ msgid ":guilabel:`Cost`: the total cost of the service, or repair."
msgstr ""
#: ../../content/applications/hr/fleet/service.rst:280
msgid ":guilabel:`Stage`: the status of the service, or repair. Options are :guilabel:`New`, :guilabel:`Running`, :guilabel:`Done`, or :guilabel:`Canceled`."
msgid ":guilabel:`Stage`: the status of the service, or repair. Options are :guilabel:`New`, :guilabel:`Running`, :guilabel:`Done`, or :guilabel:`Cancelled`."
msgstr ""
#: ../../content/applications/hr/fleet/service.rst:283
@ -4760,7 +5200,7 @@ msgid ":guilabel:`Station`: the location of where the guest checked in."
msgstr ""
#: ../../content/applications/hr/frontdesk/visitors.rst:35
msgid ":guilabel:`Status`: the status of the guest. The options are :guilabel:`Checked-In`, :guilabel:`Planned`, :guilabel:`Checked-Out`, or :guilabel:`Canceled`."
msgid ":guilabel:`Status`: the status of the guest. The options are :guilabel:`Checked-In`, :guilabel:`Planned`, :guilabel:`Checked-Out`, or :guilabel:`Cancelled`."
msgstr ""
#: ../../content/applications/hr/frontdesk/visitors.rst:37
@ -5071,7 +5511,7 @@ msgid "In Odoo's *Lunch* application, it is required to have someone manage the
msgstr ""
#: ../../content/applications/hr/lunch/management.rst:9
msgid "Orders can be :ref:`canceled <lunch/cancel>`, :ref:`sent to the vendor <lunch/send-orders>`, :ref:`confirmed <lunch/confirm-orders>` upon arrival, and :ref:`employees can be notified <lunch/notify>`, either from the :ref:`Today's Orders <lunch/todays-orders>` dashboard, or the :ref:`Control Vendors <lunch/control_vendors>` dashboard."
msgid "Orders can be :ref:`cancelled <lunch/cancel>`, :ref:`sent to the vendor <lunch/send-orders>`, :ref:`confirmed <lunch/confirm-orders>` upon arrival, and :ref:`employees can be notified <lunch/notify>`, either from the :ref:`Today's Orders <lunch/todays-orders>` dashboard, or the :ref:`Control Vendors <lunch/control_vendors>` dashboard."
msgstr ""
#: ../../content/applications/hr/lunch/management.rst:14
@ -5163,15 +5603,15 @@ msgid "All users can cancel an order, not just managers of the *Lunch* app."
msgstr ""
#: ../../content/applications/hr/lunch/management.rst:61
msgid "To cancel an order from a vendor, individual products **must** be canceled one at a time."
msgid "To cancel an order from a vendor, individual products **must** be cancelled one at a time."
msgstr ""
#: ../../content/applications/hr/lunch/management.rst:63
msgid "On the :guilabel:`Today's Orders` dashboard, a :guilabel:`✖️ Cancel` button is shown at the far-right of each product line that can be canceled. Click the :guilabel:`✖️ Cancel` button to cancel the order for that individual product."
msgid "On the :guilabel:`Today's Orders` dashboard, a :guilabel:`✖️ Cancel` button is shown at the far-right of each product line that can be cancelled. Click the :guilabel:`✖️ Cancel` button to cancel the order for that individual product."
msgstr ""
#: ../../content/applications/hr/lunch/management.rst:68
msgid "Only products with a red :guilabel:`Status` tag of :guilabel:`Ordered` can be canceled."
msgid "Only products with a red :guilabel:`Status` tag of :guilabel:`Ordered` can be cancelled."
msgstr ""
#: ../../content/applications/hr/lunch/management.rst:-1
@ -5271,7 +5711,7 @@ msgid "All orders appear in a list view, grouped alphabetically by :guilabel:`Ve
msgstr ""
#: ../../content/applications/hr/lunch/management.rst:174
msgid "Orders can be :ref:`canceled <lunch/cancel>`, :ref:`sent to the vendor <lunch/send-orders>`, :ref:`confirmed <lunch/confirm-orders>` upon arrival, and :ref:`employees can be notified <lunch/notify>` using the same method as on the :ref:`Today's Orders <lunch/todays-orders>` dashboard."
msgid "Orders can be :ref:`cancelled <lunch/cancel>`, :ref:`sent to the vendor <lunch/send-orders>`, :ref:`confirmed <lunch/confirm-orders>` upon arrival, and :ref:`employees can be notified <lunch/notify>` using the same method as on the :ref:`Today's Orders <lunch/todays-orders>` dashboard."
msgstr ""
#: ../../content/applications/hr/lunch/management.rst:-1
@ -5287,10 +5727,6 @@ msgid ":doc:`../lunch`"
msgstr ""
#: ../../content/applications/hr/lunch/management.rst:191
msgid ":doc:`orders`"
msgstr ""
#: ../../content/applications/hr/lunch/management.rst:192
msgid ":doc:`user-accounts`"
msgstr ""
@ -5509,7 +5945,7 @@ msgid "The total cost for each order is displayed on the line containing the ord
msgstr ""
#: ../../content/applications/hr/lunch/orders.rst:194
msgid "At the end of each product line with a status of :guilabel:`Ordered` or :guilabel:`Sent`, an :guilabel:`X Cancel` button appears. Click :guilabel:`X Cancel` to cancel that product order. Once a product order has been canceled, the money paid for that product is refunded, and appears in the user's account."
msgid "At the end of each product line with a status of :guilabel:`Ordered` or :guilabel:`Sent`, an :guilabel:`X Cancel` button appears. Click :guilabel:`X Cancel` to cancel that product order. Once a product order has been cancelled, the money paid for that product is refunded, and appears in the user's account."
msgstr ""
#: ../../content/applications/hr/lunch/orders.rst:199
@ -5537,7 +5973,7 @@ msgid "Entries with a negative figure listed in the :guilabel:`Amount` column re
msgstr ""
#: ../../content/applications/hr/lunch/orders.rst:221
msgid "Entries with a positive balance either represent funds added to the user's lunch account, or canceled orders that were eventually refunded to the user. These appear in a `$XX.XX` format."
msgid "Entries with a positive balance either represent funds added to the user's lunch account, or cancelled orders that were eventually refunded to the user. These appear in a `$XX.XX` format."
msgstr ""
#: ../../content/applications/hr/lunch/orders.rst:-1
@ -7834,7 +8270,7 @@ msgid "Odoo automatically checks bank account information. If there is an error
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:217
msgid "If a payment needs to be canceled or refunded, click the corresponding :guilabel:`Cancel` or :guilabel:`Refund` button, located at the top-left of the screen."
msgid "If a payment needs to be cancelled or refunded, click the corresponding :guilabel:`Cancel` or :guilabel:`Refund` button, located at the top-left of the screen."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:221
@ -8784,7 +9220,7 @@ msgid "In order to keep the employee's time off balances correct, the time off r
msgstr ""
#: ../../content/applications/hr/payroll/work_entries.rst:278
msgid "The most common scenario when this situation occurs, is when payslips are processed a day or two before the pay period ends, and an employee is unexpectedly sick on one of the last days of the pay period. The employee puts in a time off request for a day that was already processed on a payslip as a regular work day. Instead of canceling the payslip, modifying the work entries, and reissuing the paycheck, Odoo allows for those time off requests to be applied to the following pay period, instead."
msgid "The most common scenario when this situation occurs, is when payslips are processed a day or two before the pay period ends, and an employee is unexpectedly sick on one of the last days of the pay period. The employee puts in a time off request for a day that was already processed on a payslip as a regular work day. Instead of cancelling the payslip, modifying the work entries, and reissuing the paycheck, Odoo allows for those time off requests to be applied to the following pay period, instead."
msgstr ""
#: ../../content/applications/hr/payroll/work_entries.rst:285
@ -9190,7 +9626,7 @@ msgid ":guilabel:`Recruitment: Interest`: this template is used to let the appli
msgstr ""
#: ../../content/applications/hr/recruitment.rst:322
msgid ":guilabel:`Recruitment: Schedule Interview`: this template is used to let the applicant know that they have passed the :guilabel:`Initial Qualification` stage and they will be contacted to set up an interview with the recruiter. This email is automatically sent out once the applicant is in the :guilabel:`Initial Qualification` stage."
msgid ":guilabel:`Recruitment: Schedule Interview`: this template is used to let the applicant know that they have passed the :guilabel:`Initial Qualification` stage, and they will be contacted to set up an interview with the recruiter. This email is automatically sent out once the applicant is in the :guilabel:`Initial Qualification` stage."
msgstr ""
#: ../../content/applications/hr/recruitment.rst:326

1049
locale/sources/inventory_and_mrp.pot
View File

File diff suppressed because it is too large Load Diff

6
locale/sources/marketing.pot
View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Project-Id-Version: Odoo 18.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-08-21 11:43+0000\n"
"POT-Creation-Date: 2024-10-07 14:21+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -25,7 +25,7 @@ msgid "Email Marketing"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:7
msgid "The Odoo *Email Marketing* app provides drag-and-drop design tools, pre-built templates, and other interactive features to create engaging email campaigns. The *Email Marketing* app also provides| detailed reporting metrics to track the campaigns' overall effectiveness."
msgid "The Odoo *Email Marketing* app provides drag-and-drop design tools, pre-built templates, and other interactive features to create engaging email campaigns. The *Email Marketing* app also provides detailed reporting metrics to track the campaigns' overall effectiveness."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:12

2308
locale/sources/productivity.pot
View File

File diff suppressed because it is too large Load Diff

1755
locale/sources/sales.pot
View File

File diff suppressed because it is too large Load Diff

142
locale/sources/services.pot
View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Project-Id-Version: Odoo 18.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-08-21 11:43+0000\n"
"POT-Creation-Date: 2024-10-07 14:21+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -970,146 +970,110 @@ msgid "`Field Service <https://www.odoo.com/slides/slide/advanced-settings-862?
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:3
msgid "Close tickets"
msgid "Closing tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:5
msgid "Once work has been completed on a *Helpdesk* ticket in Odoo, there are several ways it can be closed."
msgid "Once work has been completed on a *Helpdesk* ticket in Odoo, there are several ways it can be closed. Manually closing solved tickets keeps the pipeline up to date, while automatically closing inactive tickets prevents unnecessary blocking issues. Allowing customers to close their own tickets minimizes confusion around whether an issue is considered solved or not. This results in increased operational capacity for support teams, and higher customer satisfaction."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:8
msgid "In addition to manually closing solved tickets, automatically closing inactive tickets keeps the pipeline up-to-date. At the same time, allowing customers to close their own tickets minimizes confusion around whether an issue is considered solved or not. This results in increased operational capacity for support teams, and higher customer satisfaction."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:14
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:12
msgid "Manually close solved tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:16
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:14
msgid "As work on a ticket progresses, it is moved along to the next stage in the pipeline. Once the issue is solved, the ticket is moved to a *folded* stage. This marks the ticket as *closed*."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:19
msgid "To fold a stage, navigate to the :menuselection:`Helpdesk` app dashboard, and click on a team to open the to reveal that team's pipeline on a separate page."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:22
msgid "From the pipeline page, hover over a stage's heading, and click the :guilabel:`⚙️ (gear)` icon that appears in the top-right corner of that stage's Kanban column."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:17
msgid "To fold a stage, navigate to the :menuselection:`Helpdesk` dashboard and click on a team to open the pipeline. Hover over a stage's heading, and then click the gear icon that appears in the top-right corner of that stage's kanban column."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:-1
msgid "View of stage on Helpdesk pipeline with emphasis on gear icon and edit stage option."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:29
msgid "From the menu that appears, select :guilabel:`Edit`. This opens the stage's settings in a pop-up window."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:26
msgid "Clicking the gear icon also displays the option to :guilabel:`Fold` the stage. This setting folds the stage *temporarily* to simplify the kanban view. This does *not* close the tickets in this stage. It also does not permanently fold the stage. If a stage needs to be folded so the tickets can be marked as closed, continue following the steps below."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:32
msgid "In the pop-up window, check the box labeled, :guilabel:`Folded in Kanban`, towards the top of the window. Then, click :guilabel:`Save & Close` to confirm the changes."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:31
msgid "From the menu that appears, select :guilabel:`Edit Stage`. This will open the stage's settings. Check the box labeled :guilabel:`Folded in Kanban` towards the top of the window, and then :guilabel:`Save & Close` to confirm the changes. Now, tickets that reach this stage will be considered as *closed*."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:35
msgid "Tickets that reach this stage are now considered: *closed*."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:-1
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
msgid "Stage settings page."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:42
msgid "Clicking the :guilabel:`⚙️ (gear)` icon also displays the option to :guilabel:`Fold` the stage. This setting folds the stage *temporarily* to simplify the Kanban view. This does **not** close the tickets in this stage. It also does **not** permanently fold the stage. If a stage needs to be folded, so the tickets can be marked as *closed*, the :guilabel:`Folded in Kanban` checkbox **must** be checked on the stage's settings."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:49
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:41
msgid "Automatically close inactive tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:51
msgid "Tickets that are inactive for a set period of time can be automatically closed. At that point, they are moved to a folded stage."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:43
msgid "Tickets that are inactive for a set period of time can be automatically closed. At that point, they will be moved to a folded stage."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:46
msgid "Go to the team's settings page by going to :menuselection:`Helpdesk --> Configuration --> Teams`. Under the :guilabel:`Self-Service` section, enable :guilabel:`Automatic Closing`."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:49
msgid "If one of the team's stages is set to be folded in the kanban view, it will be the default selection in the :guilabel:`Move to Stage` field. If the team has more than one folded stage, the stage that occurs first in the pipeline will be the default. If no stage is folded, the default selection will be the last stage in the pipeline."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:54
msgid "To have Odoo automatically close inactive tickets, go to the desired team's settings page, by navigating to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`, and selecting the desired team to configure. Under the :guilabel:`Self-Service` section, enable :guilabel:`Automatic Closing`."
msgid "The :guilabel:`After days of inactivity` field defaults to `7`, but can be adjusted if necessary."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:59
msgid "After ticking the box for :guilabel:`Automatic Closing`, three new fields appear beneath:"
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:57
msgid "The :guilabel:`After days of inactivity` field does **not** take the working calendar into account when tracking the amount of time a ticket has been inactive."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:61
msgid ":guilabel:`Move to Stage`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:62
msgid ":guilabel:`After (#) days of inactivity`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:63
msgid ":guilabel:`In Stages`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:65
msgid "If one of the team's stages is set to be folded in the Kanban view, the folded stage is the default selection in the :guilabel:`Move to Stage` field. If the team has more than one folded stage, the folded stage that occurs first in the pipeline is the default. If no stage is folded, the default selection is the last stage in the pipeline."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:70
msgid "The :guilabel:`After (#) days of inactivity` field defaults to `7`, but can be adjusted if necessary."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:74
msgid "The :guilabel:`After (#) days of inactivity` field does **not** take the working calendar into account when tracking the amount of time a ticket has been inactive."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:77
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:60
msgid "If only certain stages should be used to track days of inactivity, they can be added to the :guilabel:`In Stages` field."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:81
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:64
msgid "A team's pipeline is created with the following stages:"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:83
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:66
msgid "`New`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:84
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:67
msgid "`In Progress`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:85
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:68
msgid "`Customer Feedback`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:86
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:69
msgid "`Closed`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:88
msgid "Tickets may linger in the :guilabel:`Customer Feedback` stage, because once an issue is solved, customers may not respond immediately. At that point, the tickets can be closed automatically."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:71
msgid "Tickets can linger in the :guilabel:`Customer Feedback stage`, because once an issue is solved, customers may not respond immediately. At that point, the tickets can be closed automatically. However, tickets in the :guilabel:`New` and :guilabel:`In Progress` stages may remain inactive due to assignment or workload issues. Closing these tickets automatically would result in issues going unsolved."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:91
msgid "Tickets in the :guilabel:`New` and :guilabel:`In Progress` stages could remain inactive due to assignment or workload issues. The support team may be looking into the issue even if they are not updating the ticket directly. Closing these tickets automatically would result in issues going unsolved."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:77
msgid "Therefore, the :guilabel:`Automatic Closing` settings would be configured as below\\:\\"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:96
msgid "Therefore, the :guilabel:`Automatic Closing` settings for this team would be configured as below:"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:99
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:79
msgid ":guilabel:`Automatic Closing`: *checked*"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:100
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:80
msgid ":guilabel:`Move to Stage`: `Solved`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:101
msgid ":guilabel:`After` `7` :guilabel:`days of inactivity`"
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:81
msgid ":guilabel:`After``7`:guilabel:`days of inactivity`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:102
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:82
msgid ":guilabel:`In Stages`: `Customer Feedback`"
msgstr ""
@ -1117,36 +1081,36 @@ msgstr ""
msgid "Example of Automatic Closing settings."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:109
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:89
msgid "Allow customers to close their own tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:111
msgid "Enabling the :guilabel:`Closure by Customers` setting allows customers to close their own tickets when they determine that their issue has been resolved."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:91
msgid "Enabling the :guilabel:`Closure by Customers` setting allows customers to close their own ticket(s) when they determine that their issue has been resolved."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:114
msgid "To allow customers to close their own tickets, start by navigating to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`, and click on a team to open the team's settings page. Next, scroll to the :guilabel:`Self-Service` section, and check the box for :guilabel:`Closure by Customers`."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:94
msgid "Start by navigating to :menuselection:`Helpdesk --> Configuration --> Teams` and select a team. On the team's settings page, scroll to the :guilabel:`Self-Service` section and check the box for :guilabel:`Closure by Customers`."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:-1
msgid "Customer closing setting in Odoo Helpdesk."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:123
msgid "Once the ticket closing settings are enabled, a :guilabel:`Close Ticket` button is available for customers when they view their ticket through the customer portal."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:102
msgid "Once the ticket closing settings are enabled, a :guilabel:`Close Ticket` button will be available for customers when they view their ticket through the customer portal."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:-1
msgid "Customer view of ticket closing in Odoo Helpdesk."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:131
msgid "Customers are able to view their tickets by clicking the :guilabel:`View the ticket` link they receive by email. The link is included in the :guilabel:`Helpdesk: Ticket Received` template, which is added to the first stage of a team by default. This link does **not** require a customer to have access to the portal to view or respond to their ticket."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:110
msgid "Customers are able to view their tickets by clicking the :guilabel:`View the ticket` link they receive by email. The link is included in the :guilabel:`Request Acknowledgment` template, which is added to the first stage of a team by default. This link does not require a customer to have access to the portal to view or respond to their ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:136
msgid "Customers with access to the portal can view their tickets under :menuselection:`My Account --> Tickets`."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:115
msgid "Customers with access to the portal will be able to view their tickets under :menuselection:`My Account --> Tickets`."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:3

168
locale/sources/studio.pot
View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Project-Id-Version: Odoo 18.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-08-21 11:43+0000\n"
"POT-Creation-Date: 2024-10-07 14:21+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1814,9 +1814,9 @@ msgid "General views"
msgstr ""
#: ../../content/applications/studio/views.rst:33
#: ../../content/applications/studio/views.rst:104
#: ../../content/applications/studio/views.rst:205
#: ../../content/applications/studio/views.rst:320
#: ../../content/applications/studio/views.rst:106
#: ../../content/applications/studio/views.rst:207
#: ../../content/applications/studio/views.rst:322
msgid "The settings described below are found under the view's :guilabel:`View` tab unless specified otherwise."
msgstr ""
@ -1833,7 +1833,7 @@ msgid "To structure a form, drag and drop the :guilabel:`Tabs and Columns` eleme
msgstr ""
#: ../../content/applications/studio/views.rst:46
#: ../../content/applications/studio/views.rst:137
#: ../../content/applications/studio/views.rst:139
msgid "To prevent users from creating, editing, or deleting records, untick :guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`."
msgstr ""
@ -1842,16 +1842,20 @@ msgid "To add a button, click :guilabel:`Add a button` at the top of the form, e
msgstr ""
#: ../../content/applications/studio/views.rst:51
#: ../../content/applications/studio/views.rst:153
#: ../../content/applications/studio/views.rst:155
msgid ":guilabel:`Run a Server Action`: select the :ref:`server action <reference/actions/server>` to be executed from the dropdown list;"
msgstr ""
#: ../../content/applications/studio/views.rst:53
#: ../../content/applications/studio/views.rst:155
#: ../../content/applications/studio/views.rst:157
msgid ":guilabel:`Call a method`: specify an existing Python method already defined in Odoo."
msgstr ""
#: ../../content/applications/studio/views.rst:55
msgid "To change a button's label or style, click the button and edit its :guilabel:`Label` or :guilabel:`Class` (either `btn-primary` or `btn-secondary`) in the :guilabel:`Properties` tab."
msgstr ""
#: ../../content/applications/studio/views.rst:57
msgid "To add a smart button, click the :icon:`fa-plus-square` (:guilabel:`plus`) icon in the top-right corner of the form. Enter a :guilabel:`Label`, choose an :guilabel:`Icon`, and select a :ref:`related field <studio/fields/relational-fields/related-field>`."
msgstr ""
@ -1859,15 +1863,15 @@ msgstr ""
msgid "Sales order model's Form view"
msgstr ""
#: ../../content/applications/studio/views.rst:67
#: ../../content/applications/studio/views.rst:69
msgid "Activity"
msgstr ""
#: ../../content/applications/studio/views.rst:69
#: ../../content/applications/studio/views.rst:71
msgid "The :guilabel:`Activity` :icon:`fa-clock-o` view is used to schedule and have an overview of activities (emails, calls, etc.) linked to records."
msgstr ""
#: ../../content/applications/studio/views.rst:73
#: ../../content/applications/studio/views.rst:75
msgid "This view can only be modified within Studio by editing the XML code."
msgstr ""
@ -1875,19 +1879,19 @@ msgstr ""
msgid "Lead/Opportunity model's Activity view"
msgstr ""
#: ../../content/applications/studio/views.rst:83
#: ../../content/applications/studio/views.rst:85
msgid "Search"
msgstr ""
#: ../../content/applications/studio/views.rst:85
#: ../../content/applications/studio/views.rst:87
msgid "The :guilabel:`Search` :icon:`oi-search` view is added on top of other views to filter, group, and search records."
msgstr ""
#: ../../content/applications/studio/views.rst:88
#: ../../content/applications/studio/views.rst:90
msgid "To add custom :guilabel:`Filters` and structure them using :guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop them under :guilabel:`Filters`."
msgstr ""
#: ../../content/applications/studio/views.rst:90
#: ../../content/applications/studio/views.rst:92
msgid "To add an existing field under the search dropdown menu, go to the :guilabel:`+ Add` tab and drag and drop it under :guilabel:`Autocompletion Fields`."
msgstr ""
@ -1895,32 +1899,32 @@ msgstr ""
msgid "Project model's Search view on the Kanban view"
msgstr ""
#: ../../content/applications/studio/views.rst:101
#: ../../content/applications/studio/views.rst:103
msgid "Multiple records views"
msgstr ""
#: ../../content/applications/studio/views.rst:110
#: ../../content/applications/studio/views.rst:112
msgid "Kanban"
msgstr ""
#: ../../content/applications/studio/views.rst:112
#: ../../content/applications/studio/views.rst:114
msgid "The :guilabel:`Kanban` :icon:`oi-view-kanban` view is often used to support business flows by moving records across stages or as an alternative way to display records inside *cards*."
msgstr ""
#: ../../content/applications/studio/views.rst:116
#: ../../content/applications/studio/views.rst:118
msgid "If the :guilabel:`Kanban` view exists, it is used by default to display data on mobile devices instead of the :ref:`List view <studio/views/multiple-records/list>`."
msgstr ""
#: ../../content/applications/studio/views.rst:119
#: ../../content/applications/studio/views.rst:121
msgid "To prevent users from creating new records, untick :guilabel:`Can Create`."
msgstr ""
#: ../../content/applications/studio/views.rst:120
#: ../../content/applications/studio/views.rst:122
msgid "To create records directly within the view, in a minimalistic form, enable :guilabel:`Quick Create`."
msgstr ""
#: ../../content/applications/studio/views.rst:122
#: ../../content/applications/studio/views.rst:149
#: ../../content/applications/studio/views.rst:124
#: ../../content/applications/studio/views.rst:151
msgid "To set a default grouping for records, select a field under :guilabel:`Default Group By`."
msgstr ""
@ -1928,35 +1932,35 @@ msgstr ""
msgid "Project model's Kanban view"
msgstr ""
#: ../../content/applications/studio/views.rst:132
#: ../../content/applications/studio/views.rst:134
msgid "List"
msgstr ""
#: ../../content/applications/studio/views.rst:134
#: ../../content/applications/studio/views.rst:136
msgid "The :guilabel:`List` :icon:`oi-view-list` view is used to overview many records at once, look for records, and edit simple records."
msgstr ""
#: ../../content/applications/studio/views.rst:139
#: ../../content/applications/studio/views.rst:141
msgid "To create and edit records directly within the view, select either :guilabel:`Add record at the bottom`, :guilabel:`Add record on top` or :guilabel:`Open form view` under :guilabel:`When Creating Record`."
msgstr ""
#: ../../content/applications/studio/views.rst:144
#: ../../content/applications/studio/views.rst:146
msgid "This prevents users from opening records in :ref:`Form view <studio/views/general/form>` from the :guilabel:`List` view."
msgstr ""
#: ../../content/applications/studio/views.rst:147
#: ../../content/applications/studio/views.rst:149
msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`."
msgstr ""
#: ../../content/applications/studio/views.rst:148
#: ../../content/applications/studio/views.rst:150
msgid "To change the way records are sorted by default, select a field under :guilabel:`Sort By`."
msgstr ""
#: ../../content/applications/studio/views.rst:150
#: ../../content/applications/studio/views.rst:152
msgid "To add a button, click :guilabel:`Add a button` at the top of the list, enter a :guilabel:`Label`, and select the button's action:"
msgstr ""
#: ../../content/applications/studio/views.rst:158
#: ../../content/applications/studio/views.rst:160
msgid "To add a :icon:`oi-draggable` (:guilabel:`drag handle`) icon to reorder records manually, add an :ref:`Integer field <studio/fields/simple-fields/integer>` with the :guilabel:`Handle` widget."
msgstr ""
@ -1968,31 +1972,31 @@ msgstr ""
msgid "Sales order model's List view"
msgstr ""
#: ../../content/applications/studio/views.rst:172
#: ../../content/applications/studio/views.rst:174
msgid "Map"
msgstr ""
#: ../../content/applications/studio/views.rst:174
#: ../../content/applications/studio/views.rst:176
msgid "The :guilabel:`Map` :icon:`fa-map-marker` view is used to display records on a map. For example, it is used in the Field Service app to plan an itinerary between different tasks."
msgstr ""
#: ../../content/applications/studio/views.rst:178
#: ../../content/applications/studio/views.rst:180
msgid "A :ref:`Many2One field <studio/fields/relational-fields/many2one>` linked to the *Contact* model is required to activate the view, as the contact address is used to position records on the map."
msgstr ""
#: ../../content/applications/studio/views.rst:181
#: ../../content/applications/studio/views.rst:183
msgid "To select which kind of contact should be used on the map, select it under :guilabel:`Contact Field`."
msgstr ""
#: ../../content/applications/studio/views.rst:183
#: ../../content/applications/studio/views.rst:185
msgid "To hide the name or the address of the record, tick :guilabel:`Hide Name` or :guilabel:`Hide Address`."
msgstr ""
#: ../../content/applications/studio/views.rst:185
#: ../../content/applications/studio/views.rst:187
msgid "To add information from other fields, select them under :guilabel:`Additional Fields`."
msgstr ""
#: ../../content/applications/studio/views.rst:186
#: ../../content/applications/studio/views.rst:188
msgid "To have a route suggested between the different records, tick :guilabel:`Enable Routing` and select which field should be used to sort records for the routing."
msgstr ""
@ -2000,47 +2004,47 @@ msgstr ""
msgid "Task model's Map view"
msgstr ""
#: ../../content/applications/studio/views.rst:197
#: ../../content/applications/studio/views.rst:199
msgid "Timeline views"
msgstr ""
#: ../../content/applications/studio/views.rst:200
#: ../../content/applications/studio/views.rst:202
msgid "When you first activate one of the timeline views, you need to select which :ref:`Date <studio/fields/simple-fields/date>` or :ref:`Date & Time <studio/fields/simple-fields/date-time>` fields on your model should be used to define when the records start and stop in order to display them on the view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop Date Field` after activating the view."
msgstr ""
#: ../../content/applications/studio/views.rst:211
#: ../../content/applications/studio/views.rst:213
msgid "Calendar"
msgstr ""
#: ../../content/applications/studio/views.rst:213
#: ../../content/applications/studio/views.rst:215
msgid "The :guilabel:`Calendar` :icon:`fa-calendar` view is used to overview and manage records inside a calendar."
msgstr ""
#: ../../content/applications/studio/views.rst:216
#: ../../content/applications/studio/views.rst:218
msgid "To create records directly within the view instead of opening the :ref:`Form view <studio/views/general/form>`, enable :guilabel:`Quick Create`."
msgstr ""
#: ../../content/applications/studio/views.rst:220
#: ../../content/applications/studio/views.rst:222
msgid "This only works on specific models that can be *quick-created* using only a *name*. However, most models do not support quick creation and open the :guilabel:`Form` view to fill in the required fields."
msgstr ""
#: ../../content/applications/studio/views.rst:224
#: ../../content/applications/studio/views.rst:226
msgid "To color records on the calendar, select a field under :guilabel:`Color`. All the records sharing the same value for that field are displayed using the same color."
msgstr ""
#: ../../content/applications/studio/views.rst:228
#: ../../content/applications/studio/views.rst:230
msgid "As the number of colors is limited, the same color can end up being assigned to different values."
msgstr ""
#: ../../content/applications/studio/views.rst:231
#: ../../content/applications/studio/views.rst:233
msgid "To display events lasting the whole day at the top of the calendar, select a :ref:`Checkbox field <studio/fields/simple-fields/checkbox>` that specifies if the event lasts the whole day."
msgstr ""
#: ../../content/applications/studio/views.rst:234
#: ../../content/applications/studio/views.rst:236
msgid "To choose the default time scale used to display events, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Display Mode`."
msgstr ""
#: ../../content/applications/studio/views.rst:238
#: ../../content/applications/studio/views.rst:240
msgid "You can also use a :guilabel:`Delay Field` to display the duration of the event in hours by selecting a :ref:`Decimal <studio/fields/simple-fields/decimal>` or :ref:`Integer <studio/fields/simple-fields/integer>` field on the model which specifies the duration of the event. However, if you set an :guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken into account."
msgstr ""
@ -2048,27 +2052,27 @@ msgstr ""
msgid "Calendar Event model's Calendar view"
msgstr ""
#: ../../content/applications/studio/views.rst:252
#: ../../content/applications/studio/views.rst:254
msgid "Cohort"
msgstr ""
#: ../../content/applications/studio/views.rst:254
#: ../../content/applications/studio/views.rst:256
msgid "The :guilabel:`Cohort` :icon:`oi-view-cohort` view is used to examine the life cycle of records over a time period. For example, it is used in the Subscriptions app to view the subscriptions' retention rate."
msgstr ""
#: ../../content/applications/studio/views.rst:258
#: ../../content/applications/studio/views.rst:260
msgid "To display a measure (i.e., the aggregated value of a given field) by default on the view, select a :guilabel:`Measure Field`."
msgstr ""
#: ../../content/applications/studio/views.rst:260
#: ../../content/applications/studio/views.rst:262
msgid "To choose which time interval is used by default to group results, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Interval`."
msgstr ""
#: ../../content/applications/studio/views.rst:262
#: ../../content/applications/studio/views.rst:264
msgid "To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` :dfn:`the percentage of records staying over a period of time, it starts at 100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of records moving out over a period of time - it starts at 0% and increases with time`."
msgstr ""
#: ../../content/applications/studio/views.rst:266
#: ../../content/applications/studio/views.rst:268
msgid "To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` (from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is used."
msgstr ""
@ -2076,51 +2080,51 @@ msgstr ""
msgid "Subscription model's Cohort view"
msgstr ""
#: ../../content/applications/studio/views.rst:278
#: ../../content/applications/studio/views.rst:280
msgid "Gantt"
msgstr ""
#: ../../content/applications/studio/views.rst:280
#: ../../content/applications/studio/views.rst:282
msgid "The :guilabel:`Gantt` :icon:`fa-tasks` view is used to forecast and examine the overall progress of records. Records are represented by a bar under a time scale."
msgstr ""
#: ../../content/applications/studio/views.rst:283
#: ../../content/applications/studio/views.rst:285
msgid "To prevent users from creating or editing records, untick :guilabel:`Can Create` or :guilabel:`Can Edit`."
msgstr ""
#: ../../content/applications/studio/views.rst:285
#: ../../content/applications/studio/views.rst:287
msgid "To fill cells in gray whenever a record should not be created there (e.g., on weekends for employees), tick :guilabel:`Display Unavailability`."
msgstr ""
#: ../../content/applications/studio/views.rst:289
#: ../../content/applications/studio/views.rst:291
msgid "The underlying model must support this feature, and support for it cannot be added using Studio. It is supported for the Project, Time Off, Planning, and Manufacturing apps."
msgstr ""
#: ../../content/applications/studio/views.rst:292
#: ../../content/applications/studio/views.rst:294
msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`."
msgstr ""
#: ../../content/applications/studio/views.rst:293
#: ../../content/applications/studio/views.rst:295
msgid "To collapse multiple records in a single row, tick :guilabel:`Collapse First Level`."
msgstr ""
#: ../../content/applications/studio/views.rst:294
#: ../../content/applications/studio/views.rst:296
msgid "To choose which way records are grouped by default on rows (e.g., per employee or project), select a field under :guilabel:`Default Group by`."
msgstr ""
#: ../../content/applications/studio/views.rst:296
#: ../../content/applications/studio/views.rst:298
msgid "To define a default time scale to view records, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Scale`."
msgstr ""
#: ../../content/applications/studio/views.rst:298
#: ../../content/applications/studio/views.rst:300
msgid "To color records on the view, select a field under :guilabel:`Color`. All the records sharing the same value for that field are displayed using the same color."
msgstr ""
#: ../../content/applications/studio/views.rst:302
#: ../../content/applications/studio/views.rst:304
msgid "As the number of colors is limited, the same color can be assigned to different values."
msgstr ""
#: ../../content/applications/studio/views.rst:304
#: ../../content/applications/studio/views.rst:306
msgid "To specify with which degree of precision each time scale should be divided by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or :guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or :guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month Precision`."
msgstr ""
@ -2128,31 +2132,31 @@ msgstr ""
msgid "Planning Shift model's Gantt view"
msgstr ""
#: ../../content/applications/studio/views.rst:317
#: ../../content/applications/studio/views.rst:319
msgid "Reporting views"
msgstr ""
#: ../../content/applications/studio/views.rst:326
#: ../../content/applications/studio/views.rst:328
msgid "Pivot"
msgstr ""
#: ../../content/applications/studio/views.rst:328
#: ../../content/applications/studio/views.rst:330
msgid "The :guilabel:`Pivot` :icon:`oi-view-pivot` view is used to explore and analyze the data contained in records in an interactive manner. It is especially useful to aggregate numeric data, create categories, and drill down the data by expanding and collapsing different levels of data."
msgstr ""
#: ../../content/applications/studio/views.rst:332
#: ../../content/applications/studio/views.rst:334
msgid "To access all records whose data is aggregated under a cell, tick :guilabel:`Access records from cell`."
msgstr ""
#: ../../content/applications/studio/views.rst:334
#: ../../content/applications/studio/views.rst:336
msgid "To divide the data into different categories, select field(s) under :guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or :guilabel:`Row grouping - Second level`."
msgstr ""
#: ../../content/applications/studio/views.rst:336
#: ../../content/applications/studio/views.rst:338
msgid "To add different types of data to be measured using the view, select a field under :guilabel:`Measures`."
msgstr ""
#: ../../content/applications/studio/views.rst:338
#: ../../content/applications/studio/views.rst:340
msgid "To display a count of records that made up the aggregated data in a cell, tick :guilabel:`Display count`."
msgstr ""
@ -2160,35 +2164,35 @@ msgstr ""
msgid "Purchase Report model's Pivot view"
msgstr ""
#: ../../content/applications/studio/views.rst:349
#: ../../content/applications/studio/views.rst:351
msgid "Graph"
msgstr ""
#: ../../content/applications/studio/views.rst:351
#: ../../content/applications/studio/views.rst:353
msgid "The :guilabel:`Graph` :icon:`fa-area-chart` view is used to showcase data from records in a bar, line, or pie chart."
msgstr ""
#: ../../content/applications/studio/views.rst:354
#: ../../content/applications/studio/views.rst:356
msgid "To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` under :guilabel:`Type`."
msgstr ""
#: ../../content/applications/studio/views.rst:356
#: ../../content/applications/studio/views.rst:358
msgid "To choose a default data dimension (category), select a field under :guilabel:`First dimension` and, if needed, another under :guilabel:`Second dimension`."
msgstr ""
#: ../../content/applications/studio/views.rst:358
#: ../../content/applications/studio/views.rst:360
msgid "To select a default type of data to be measured using the view, select a field under :guilabel:`Measure`."
msgstr ""
#: ../../content/applications/studio/views.rst:360
#: ../../content/applications/studio/views.rst:362
msgid "*For Bar and Line charts only*: To sort the different data categories by their value, select :guilabel:`Ascending` (from lowest to highest value) or :guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`."
msgstr ""
#: ../../content/applications/studio/views.rst:363
#: ../../content/applications/studio/views.rst:365
msgid "*For Bar and Pie charts only*: To access all records whose data is aggregated under a data category on the chart, tick :guilabel:`Access records from graph`."
msgstr ""
#: ../../content/applications/studio/views.rst:365
#: ../../content/applications/studio/views.rst:367
msgid "*For Bar charts only*: When using two data dimensions (categories), display the two columns on top of each other by default by ticking :guilabel:`Stacked graph`."
msgstr ""

18
locale/sources/websites.pot
View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Project-Id-Version: Odoo 18.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-08-21 11:43+0000\n"
"POT-Creation-Date: 2024-10-07 14:21+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -5398,7 +5398,7 @@ msgid "Open the Cloudflare Turnstile page, copy the :guilabel:`Secret Key`, and
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:72
#: ../../content/applications/websites/website/configuration/spam_protection.rst:127
#: ../../content/applications/websites/website/configuration/spam_protection.rst:128
#: ../../content/applications/websites/website/configuration/translate.rst:60
msgid "Click :guilabel:`Save`."
msgstr ""
@ -5476,10 +5476,14 @@ msgid "Open the Google reCAPTCHA page, copy the :guilabel:`Secret key`, and past
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:124
msgid "Change the default :guilabel:`Minimum score` (`0.50`) if necessary, using a value between `1.00` and `0.00`. The higher the threshold is, the more difficult it is to pass the reCAPTCHA, and vice versa."
msgid "Change the default :guilabel:`Minimum score` (`0.70`) if necessary, using a value between `1.00` and `0.00`. The higher the threshold is, the more difficult it is to pass the reCAPTCHA, and vice versa. Out of the 11 levels, only the following four score levels are available by default: `0.1`, `0.3`, `0.7` and `0.9`."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:129
#: ../../content/applications/websites/website/configuration/spam_protection.rst:131
msgid "`Interpret reCAPTCHA scores - Google documentation <https://cloud.google.com/recaptcha/docs/interpret-assessment-website#interpret_scores>`_"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:133
msgid "You can notify visitors that reCAPTCHA protects a form. To do so, open the website editor and navigate to the form. Then, click somewhere on the form, and on the right sidebar's :guilabel:`Customize` tab, toggle :guilabel:`Show reCAPTCHA Policy` found under the :guilabel:`Form` section."
msgstr ""
@ -5487,7 +5491,7 @@ msgstr ""
msgid "reCAPTCHA policy message displayed on a form"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:138
#: ../../content/applications/websites/website/configuration/spam_protection.rst:142
msgid "If the reCAPTCHA check fails, the following error message is displayed:"
msgstr ""
@ -5495,7 +5499,7 @@ msgstr ""
msgid "Google reCAPTCHA verification error message"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:144
#: ../../content/applications/websites/website/configuration/spam_protection.rst:148
msgid "Analytics and additional settings are available on `Google's reCAPTCHA administration page <https://www.google.com/recaptcha/admin/>`_. For example, you can receive email alerts if Google detects suspicious traffic on your website or view the percentage of suspicious requests, which could help you determine the right minimum score."
msgstr ""