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

[I18N] *: export source translations

Browse Source 
closes odoo/documentation#3740

X-original-commit: f36480fee1
Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
This commit is contained in:
Martin Trigaux 2023-03-02 07:45:16 +00:00
parent 35e4d95812
commit e4bf31cde7
11 changed files with 13683 additions and 12576 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1673
locale/sources/administration.pot
View File

File diff suppressed because it is too large Load Diff

410
locale/sources/contributing.pot
View File

File diff suppressed because it is too large Load Diff

20063
locale/sources/finance.pot
View File

File diff suppressed because it is too large Load Diff

319
locale/sources/general.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-01-02 09:09+0000\n"
"POT-Creation-Date: 2023-03-03 11:23+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"
@ -88,27 +88,27 @@ msgstr ""
msgid "On some occasions, new improvements or app features are added to :doc:`supported versions of Odoo </administration/maintain/supported_versions>`. To be able to use them, you must **upgrade** your app."
msgstr ""
#: ../../content/applications/general/apps_modules.rst:50
#: ../../content/applications/general/apps_modules.rst:51
msgid "Go to :menuselection:`Apps`, click on the *dropdown menu* of the app you want to upgrade, then on *Upgrade*."
msgstr ""
#: ../../content/applications/general/apps_modules.rst:56
#: ../../content/applications/general/apps_modules.rst:57
msgid "Uninstall apps and modules"
msgstr ""
#: ../../content/applications/general/apps_modules.rst:58
#: ../../content/applications/general/apps_modules.rst:59
msgid "Go to :menuselection:`Apps`, click on the *dropdown menu* of the app you want to uninstall, then on *Uninstall*."
msgstr ""
#: ../../content/applications/general/apps_modules.rst:64
msgid "Some apps have dependencies, meaning that one app requires another. Therefore, uninstalling one app may uninstall multiple apps and modules. Odoo warns you which dependant apps and modules are affected by it."
#: ../../content/applications/general/apps_modules.rst:65
msgid "Some apps have dependencies, meaning that one app requires another. Therefore, uninstalling one app may uninstall multiple apps and modules. Odoo warns you which dependent apps and modules are affected by it."
msgstr ""
#: ../../content/applications/general/apps_modules.rst:71
#: ../../content/applications/general/apps_modules.rst:72
msgid "To complete the uninstallation, click on *Confirm*."
msgstr ""
#: ../../content/applications/general/apps_modules.rst:74
#: ../../content/applications/general/apps_modules.rst:75
msgid "Uninstalling an app also uninstalls all its dependencies and permanently erases their data."
msgstr ""
@ -555,7 +555,7 @@ msgid "The Google Calendar checkbox in General Settings."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:108
msgid "Next, copy and paste the Client ID and the Client Secret from the Google Calender API Credentials page into their respective fields below the :guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`."
msgid "Next, copy and paste the Client ID and the Client Secret from the Google Calendar API Credentials page into their respective fields below the :guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:112
@ -1314,35 +1314,35 @@ msgstr ""
msgid "To fully test the configuration, use the `Mail-Tester <https://www.mail-tester.com/>`_ tool, which gives a full overview of the content and configuration in one sent email. Mail-Tester can also be used for other, lesser-known providers."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:171
#: ../../content/applications/general/email_communication/email_domain.rst:173
msgid "Use a default email address"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:173
#: ../../content/applications/general/email_communication/email_domain.rst:175
msgid "Access the :guilabel:`System Parameters` by activating :ref:`developer mode <developer-mode>` and going to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:176
#: ../../content/applications/general/email_communication/email_domain.rst:178
msgid "To force the email address from which emails are sent, a combination of the following keys needs to be set in the system parameters of the database:"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:179
#: ../../content/applications/general/email_communication/email_domain.rst:181
msgid "`mail.default.from`: accepts the local part or a complete email address as value"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:180
#: ../../content/applications/general/email_communication/email_domain.rst:182
msgid "`mail.default.from_filter`: accepts a domain name or a full email address as value"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:183
#: ../../content/applications/general/email_communication/email_domain.rst:185
msgid "The `mail.default.from_filter` works only for `odoo-bin` configurations, otherwise this parameter can be set using the `from_filter` field on `ir.mail_server`."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:186
#: ../../content/applications/general/email_communication/email_domain.rst:188
msgid "If the email address of the author does not match `mail.default.from_filter`, the email address is replaced by `mail.default.from` (if it contains a full email address) or a combination of `mail.default.from` and `mail.catchall.domain`."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:190
#: ../../content/applications/general/email_communication/email_domain.rst:192
msgid "If the `from_filter` contains a full email address, and if the `mail.default.from` is the same as this address, then all of the email addresses that are different from `mail.default.from` will be encapsulated in `mail.default.from`."
msgstr ""
@ -1430,39 +1430,39 @@ msgstr ""
msgid "A G Suite server can be used for any Odoo hosting type. To do so, set up the SMTP relay service. The configuration steps are explained in `Google documentation <https://support.google.com /a/answer/2956491?hl=en>`__."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:82
#: ../../content/applications/general/email_communication/email_servers.rst:84
msgid "Restriction"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:84
#: ../../content/applications/general/email_communication/email_servers.rst:86
msgid "Please note that port 25 is blocked for security reasons on Odoo Online and Odoo.sh platforms. Try using ports 465, 587, or 2525 instead."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:90
#: ../../content/applications/general/email_communication/email_servers.rst:92
msgid "Use a default \"From\" email address"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:92
#: ../../content/applications/general/email_communication/email_servers.rst:94
msgid "Sometimes, an email's \"From\" (outgoing) address can belong to a different domain, and that can be a problem."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:95
#: ../../content/applications/general/email_communication/email_servers.rst:97
msgid "For example, if a customer with the email address *mary\\@customer.example.com* responds to a message, Odoo will try to redistribute that same email to the other subscribers in the thread. However, if the domain *customer.example.com* forbids that kind of usage for security, the email that Odoo is trying to redistribute would get rejected by some recipients' email servers."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:100
#: ../../content/applications/general/email_communication/email_servers.rst:102
msgid "To avoid that problem, make sure all emails use a \"From\" address from the same authorized domain."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:102
#: ../../content/applications/general/email_communication/email_servers.rst:104
msgid "If the MTA supports `SRS (Sender Rewriting Scheme) <https://en.wikipedia.org/wiki/Sender_Rewriting _Scheme>`_, SRS can be enabled to handle these situations. However, that is more complex and requires more technical knowledge that is not meant to be covered by this documentation."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:106
#: ../../content/applications/general/email_communication/email_servers.rst:108
msgid "Instead, Odoo can be configured to do something similar by itself:"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:108
#: ../../content/applications/general/email_communication/email_servers.rst:110
msgid "Set the :guilabel:`Alias Domain` name in the :menuselection:`Settings --> General Settings --> Discuss`."
msgstr ""
@ -1470,79 +1470,79 @@ msgstr ""
msgid "Setting the domain alias configuration on Odoo."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:114
#: ../../content/applications/general/email_communication/email_servers.rst:116
msgid "Turn on :doc:`developer mode </applications/general/developer_mode>`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:115
#: ../../content/applications/general/email_communication/email_servers.rst:117
msgid "Go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:116
#: ../../content/applications/general/email_communication/email_servers.rst:118
msgid "Add one system parameter from the following list:"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:118
#: ../../content/applications/general/email_communication/email_servers.rst:120
msgid "To use the same \"From\" address for *all* outgoing messages, use the key `mail.force.smtp.from` and set that address as value (such as `outgoing@mycompany.example.com`)."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:120
#: ../../content/applications/general/email_communication/email_servers.rst:122
msgid "To keep the original \"From\" address for emails that use the same domain, but change it for emails that use a different domain, use the key `mail.dynamic.smtp.from` and set the value as the email address that should be used in those cases (such as `outgoing@mycompany.example.com` )."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:128
#: ../../content/applications/general/email_communication/email_servers.rst:130
msgid "Manage inbound messages"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:130
#: ../../content/applications/general/email_communication/email_servers.rst:132
msgid "Odoo relies on generic email aliases to fetch incoming messages."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:132
#: ../../content/applications/general/email_communication/email_servers.rst:134
msgid "**Reply messages** of messages sent from Odoo are routed to their original discussion thread (and to the inbox of all its followers) by the catchall alias (**catchall@**)."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:134
#: ../../content/applications/general/email_communication/email_servers.rst:136
msgid "**Bounced messages** are routed to **bounce@** in order to track them in Odoo. This is especially used in `Odoo Email Marketing <https://www.odoo.com/page/email-marketing>`__ to opt-out invalid recipients."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:137
#: ../../content/applications/general/email_communication/email_servers.rst:139
msgid "**Original messages**: Several business objects have their own alias to create new records in Odoo from incoming emails:"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:140
#: ../../content/applications/general/email_communication/email_servers.rst:142
msgid "Sales Channel (to create Leads or Opportunities in `Odoo CRM <https://www.odoo.com/page/ crm>`__),"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:142
#: ../../content/applications/general/email_communication/email_servers.rst:144
msgid "Support Channel (to create Tickets in `Odoo Helpdesk <https://www.odoo.com/page/helpdesk>`__),"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:143
#: ../../content/applications/general/email_communication/email_servers.rst:145
msgid "Projects (to create new Tasks in `Odoo Project <https://www.odoo.com/page /project-management>`__),"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:145
#: ../../content/applications/general/email_communication/email_servers.rst:147
msgid "Job Positions (to create Applicants in `Odoo Recruitment <https://www.odoo.com/page /recruitment>`__),"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:147
#: ../../content/applications/general/email_communication/email_servers.rst:149
msgid "etc."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:149
#: ../../content/applications/general/email_communication/email_servers.rst:151
msgid "Depending on the mail server, there might be several methods to fetch emails. The easiest and most recommended method is to manage one email address per Odoo alias in the mail server."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:152
#: ../../content/applications/general/email_communication/email_servers.rst:154
msgid "Create the corresponding email addresses in the mail server (catchall@, bounce@, sales@, etc.)."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:153
#: ../../content/applications/general/email_communication/email_servers.rst:155
msgid "Set the :guilabel:`Alias Domain` name in :menuselection:`Settings --> General Settings --> Discuss`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:155
#: ../../content/applications/general/email_communication/email_servers.rst:157
msgid "If the database's hosting type is Odoo on-premise, create an :guilabel:`Incoming Mail Server` in Odoo for each alias. This can be done from the General Settings as well. Fill out the form according to the email provider's settings. Leave the :guilabel:`Actions to Perform on Incoming Mails` field blank. Once all the information has been filled out, click on :guilabel:`TEST & CONFIRM`."
msgstr ""
@ -1550,15 +1550,15 @@ msgstr ""
msgid "Incoming mail server configuration on Odoo."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:165
#: ../../content/applications/general/email_communication/email_servers.rst:167
msgid "If the database's hosting type is Odoo Online or Odoo.sh, redirecting incoming messages to Odoo's domain name instead of the external email server is recommended. That way, incoming messages can be received without delay. Odoo Online only fetches incoming messages of external servers once every hour. Redirections for all email addresses should be set to Odoo's domain name in the email server (e.g. *catchall\\@mydomain.ext* to *catchall\\@mycompany.odoo.com*)."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:171
#: ../../content/applications/general/email_communication/email_servers.rst:173
msgid "All the aliases are customizable in Odoo. Object aliases can be edited from their respective configuration view."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:175
#: ../../content/applications/general/email_communication/email_servers.rst:177
msgid "To edit catchall and bounce aliases, first activate the :ref:`developer mode <developer-mode>`. Then, go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` to customize the aliases (*mail.catchall.alias* & *mail.bounce.alias*)."
msgstr ""
@ -1566,19 +1566,19 @@ msgstr ""
msgid "System parameters with catchall configuration in Odoo."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:183
#: ../../content/applications/general/email_communication/email_servers.rst:185
msgid "By default, inbound messages are fetched every 5 minutes in Odoo on-premise."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:186
#: ../../content/applications/general/email_communication/email_servers.rst:188
msgid "This value can be changed in :ref:`developer mode <developer-mode>`. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for :guilabel:`Mail: Fetchmail Service`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:191
#: ../../content/applications/general/email_communication/email_servers.rst:195
msgid "Utilizing the From Filter on an outgoing email server"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:193
#: ../../content/applications/general/email_communication/email_servers.rst:197
msgid "The :guilabel:`FROM Filtering` field allows for the use of a specific outgoing email server depending on the :guilabel:`From` email address or domain that Odoo is sending on behalf of. This setting can be used to improve the deliverability or sending success rate of emails sent from the database. Setting the :guilabel:`FROM Filtering` field can also be used to send from different domains in a multi-company environment. Access this field in Odoo by navigating to :menuselection:`Settings --> Custom Mail Servers --> Outgoing Mail Servers --> New`."
msgstr ""
@ -1586,47 +1586,47 @@ msgstr ""
msgid "Outgoing email server settings and the FROM filter settings."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:204
#: ../../content/applications/general/email_communication/email_servers.rst:208
msgid "When an email is sent from Odoo while the :guilabel:`FROM Filtering` field is set, an email server is chosen in the following sequence:"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:207
#: ../../content/applications/general/email_communication/email_servers.rst:211
msgid "First, Odoo searches for an email server that has the same :guilabel:`FROM Filtering` value as the :guilabel:`From` value (email address) defined in the outgoing email. For example, if the :guilabel:`From` value (email address) is `test\\@example.com`, only the email servers that have the :guilabel:`FROM Filtering` value equal to `test\\@example.com` are returned."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:211
#: ../../content/applications/general/email_communication/email_servers.rst:215
msgid "However, if no email servers are found that use the :guilabel:`From` value, then Odoo searches for an email server that has the same *domain* as the :guilabel:`From` value (email address) defined in the outgoing email. For example, if the :guilabel:`From` email address is `test\\@example.com`, only the email servers that have the :guilabel:`FROM Filtering` value equal to `example.com` are returned."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:217
#: ../../content/applications/general/email_communication/email_servers.rst:221
msgid "If no email servers are found after checking for the domain, then Odoo returns all email servers that do not have any :guilabel:`FROM Filtering` value(s) set."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:220
#: ../../content/applications/general/email_communication/email_servers.rst:224
msgid "Should this query return no results, then Odoo performs a search for an email server using the system parameter: `mail.default.from`. First, the email address listed attempts to match an email server, and then the domain attempts to find a match. If no email server is found, Odoo returns the first outgoing email server (sorted by priority)."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:226
#: ../../content/applications/general/email_communication/email_servers.rst:230
msgid "If several email servers are found, then Odoo uses the first one according to its priority. For example, if there are two email servers, one with a priority of `10` and the other with a priority of `20`, then the email server with a priority of `10` is used first."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:231
#: ../../content/applications/general/email_communication/email_servers.rst:235
msgid "Set up different dedicated servers for transactional and mass mails"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:233
#: ../../content/applications/general/email_communication/email_servers.rst:237
msgid "In Odoo a separate Mail Transfer Agent (MTA) server can be used for transactional emails and mass mailings. Example: Use Postmark or SendinBlue for transactional emails, and Amazon SES, Mailgun or Sendgrid for mass mailings."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:238
#: ../../content/applications/general/email_communication/email_servers.rst:242
msgid "A default outgoing email server is already configured. Do not create an alternative one unless a specific external outgoing email server is needed for technical reasons."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:241
#: ../../content/applications/general/email_communication/email_servers.rst:245
msgid "To do this, first activate the :ref:`developer mode <developer-mode>`, and then go to :menuselection:`Settings --> Technical --> Outgoing` email servers. There, create two email MTA server settings; one for the transactional emails and one for the mass mailing server. Make sure to give priority to the transactional server over the mass mailing server by providing a lower priority number for the transactional MTA server."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:247
#: ../../content/applications/general/email_communication/email_servers.rst:251
msgid "Now, go to :menuselection:`Email Marketing --> Settings` and enable :guilabel:`Dedicated Server`. With these settings, Odoo uses the server with the lower priority for transactional emails, and the server here selected for mass mails. Note that in this case, the domain's Sender Policy Framework (SPF) records must be set to include both transactional and mass mail servers."
msgstr ""
@ -2476,7 +2476,7 @@ msgid "Offering my own services"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:68
msgid "I am more than welcome to offer my own IAP services through Odoo Apps! It is the perfect opportunity to get recurring revenue for an ongoing service use rather than — and possibly instead of — a sole initial purchase. Please, find more information at: :doc:`In-App Purchase </developer/api/iap>`."
msgid "I am more than welcome to offer my own IAP services through Odoo Apps! It is the perfect opportunity to get recurring revenue for an ongoing service use rather than — and possibly instead of — a sole initial purchase. Please, find more information at: :doc:`/developer/howtos/provide_iap_services`."
msgstr ""
#: ../../content/applications/general/users.rst:7
@ -2697,14 +2697,14 @@ msgid ":doc:`Journals <../../finance/accounting/bank/setup/bank_accounts>`"
msgstr ""
#: ../../content/applications/general/users/companies.rst:92
msgid ":doc:`Fiscal Localizations <../../finance/accounting/fiscal_localizations/overview/fiscal_localization_packages>`"
msgid ":doc:`Fiscal Localizations <../../finance/fiscal_localizations>`"
msgstr ""
#: ../../content/applications/general/users/companies.rst:94
#: ../../content/applications/general/users/companies.rst:93
msgid ":doc:`Pricelists <../../sales/sales/products_prices/prices/pricing>`"
msgstr ""
#: ../../content/applications/general/users/companies.rst:96
#: ../../content/applications/general/users/companies.rst:95
msgid "Now, activate the *Inter-Company Transactions* option under *Settings*. With the respective company *activated* and *selected*, choose if you would like operations between companies to be synchronized at an invoice/bills level or at a sales/purchase orders level."
msgstr ""
@ -2712,11 +2712,11 @@ msgstr ""
msgid "View of the settings page emphasizing the inter company transaction field in Odoo"
msgstr ""
#: ../../content/applications/general/users/companies.rst:104
#: ../../content/applications/general/users/companies.rst:103
msgid "**Synchronize invoice/bills**: generates a bill/invoice when a company confirms a bill/invoice for the selected company."
msgstr ""
#: ../../content/applications/general/users/companies.rst:107
#: ../../content/applications/general/users/companies.rst:106
msgid "*Example:* an invoice posted on JS Store Belgium, for JS Store US, automatically creates a vendor bill on the JS Store US, from the JS Store Belgium."
msgstr ""
@ -2724,11 +2724,11 @@ msgstr ""
msgid "View of an invoice for JS Store US created on JS Store Belgium in Odoo"
msgstr ""
#: ../../content/applications/general/users/companies.rst:114
#: ../../content/applications/general/users/companies.rst:113
msgid "**Synchronize sales/purchase order**: generates a drafted purchase/sales order using the selected company warehouse when a sales/purchase order is confirmed for the selected company. If instead of a drafted purchase/sales order you rather have it validated, enable *Automatic Validation*."
msgstr ""
#: ../../content/applications/general/users/companies.rst:118
#: ../../content/applications/general/users/companies.rst:117
msgid "*Example:* when a sale order for JS Store US is confirmed on JS Store Belgium, a purchase order on JS Store Belgium is automatically created (and confirmed if the *Automatic Validation* feature was enabled)."
msgstr ""
@ -2736,19 +2736,19 @@ msgstr ""
msgid "View of the purchase created on JS Store US from JS Store Belgium in Odoo"
msgstr ""
#: ../../content/applications/general/users/companies.rst:127
#: ../../content/applications/general/users/companies.rst:126
msgid "Products have to be configured as *Can be sold* and must be shared between the companies."
msgstr ""
#: ../../content/applications/general/users/companies.rst:130
#: ../../content/applications/general/users/companies.rst:129
msgid "Remember to test all workflows as an user other than the administrator."
msgstr ""
#: ../../content/applications/general/users/companies.rst:133
#: ../../content/applications/general/users/companies.rst:132
msgid ":doc:`Multi-company Guidelines </developer/howtos/company>`"
msgstr ""
#: ../../content/applications/general/users/companies.rst:134
#: ../../content/applications/general/users/companies.rst:133
msgid ":doc:`../../finance/accounting/others/multi_currency`"
msgstr ""
@ -2972,6 +2972,111 @@ msgstr ""
msgid ":doc:`companies`"
msgstr ""
#: ../../content/applications/general/users/portal.rst:3
msgid "Portal access"
msgstr ""
#: ../../content/applications/general/users/portal.rst:5
msgid "Portal access is given to users who need the ability to view certain documents or information within an Odoo database."
msgstr ""
#: ../../content/applications/general/users/portal.rst:8
msgid "Some common use cases for providing portal access include allowing customers to read/view any or all of the following in Odoo:"
msgstr ""
#: ../../content/applications/general/users/portal.rst:11
msgid "leads/opportunities"
msgstr ""
#: ../../content/applications/general/users/portal.rst:12
msgid "quotations/sales orders"
msgstr ""
#: ../../content/applications/general/users/portal.rst:13
msgid "purchase orders"
msgstr ""
#: ../../content/applications/general/users/portal.rst:14
msgid "invoices & bills"
msgstr ""
#: ../../content/applications/general/users/portal.rst:15
msgid "projects"
msgstr ""
#: ../../content/applications/general/users/portal.rst:16
msgid "tasks"
msgstr ""
#: ../../content/applications/general/users/portal.rst:17
msgid "timesheets"
msgstr ""
#: ../../content/applications/general/users/portal.rst:18
msgid "tickets"
msgstr ""
#: ../../content/applications/general/users/portal.rst:19
msgid "signatures"
msgstr ""
#: ../../content/applications/general/users/portal.rst:20
msgid "subscriptions"
msgstr ""
#: ../../content/applications/general/users/portal.rst:23
msgid "Portal users only have read/view access, and will not be able to edit any documents in the database."
msgstr ""
#: ../../content/applications/general/users/portal.rst:27
msgid "Provide portal access to customers"
msgstr ""
#: ../../content/applications/general/users/portal.rst:29
msgid "From the main Odoo dashboard, select the :guilabel:`Contacts` application. If the contact is not yet created in the database, click on the :guilabel:`Create` button, enter the details of the contact, and then click :guilabel:`Save`. Otherwise, choose an existing contact, and then click on the :guilabel:`Action` drop-down menu located at the top-center of the interface."
msgstr ""
#: ../../content/applications/general/users/portal.rst:None
msgid "Use the Contacts application to give portal access to users"
msgstr ""
#: ../../content/applications/general/users/portal.rst:38
msgid "Then select :guilabel:`Grant portal access`. A pop-up window appears, listing three fields:"
msgstr ""
#: ../../content/applications/general/users/portal.rst:40
msgid ":guilabel:`Contact`: the recorded name of the contact in the Odoo database"
msgstr ""
#: ../../content/applications/general/users/portal.rst:41
msgid ":guilabel:`Email`: the contact's email address that they will use to log into the portal"
msgstr ""
#: ../../content/applications/general/users/portal.rst:42
msgid ":guilabel:`In Portal`: whether or not the user has portal access"
msgstr ""
#: ../../content/applications/general/users/portal.rst:44
msgid "To grant portal access, first enter the contact's :guilabel:`Email` they will use to log into the portal. Then, check the box under the :guilabel:`In Portal` column. Optionally, add text to the invitation message the contact will receive. Then click :guilabel:`Apply` to finish."
msgstr ""
#: ../../content/applications/general/users/portal.rst:None
msgid "An email address and corresponding checkbox for the contact need to be filled in before\n"
"sending a portal invitation."
msgstr ""
#: ../../content/applications/general/users/portal.rst:53
msgid "An email will be sent to the specified email address, indicating that the contact is now a portal user for that Odoo database."
msgstr ""
#: ../../content/applications/general/users/portal.rst:57
msgid "To grant portal access to multiple users at once, navigate to a company contact, then click :menuselection:`Action --> Grant portal access` to view a list of all of the company's related contacts. Check the box under the :guilabel:`In Portal` column for all the contacts that need portal access, then click :guilabel:`Apply`."
msgstr ""
#: ../../content/applications/general/users/portal.rst:63
msgid "At any time, portal access can be revoked by navigating to the contact, clicking :menuselection:`Action --> Grant portal access`, and then unselecting the checkbox under the :guilabel:`In Portal` column and clicking :guilabel:`Apply`."
msgstr ""
#: ../../content/applications/general/voip.rst:5
msgid "VoIP (Voice over Internet Protocol)"
msgstr ""
@ -3040,131 +3145,131 @@ msgstr ""
msgid "You also need to install PJSIP, you can download the source `here <http://www.pjsip.org/download.htm>`_. Once the source directory is extracted:"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:37
#: ../../content/applications/general/voip/asterisk.rst:38
msgid "**Change to the pjproject source directory:**"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:43
#: ../../content/applications/general/voip/asterisk.rst:44
msgid "**run:**"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:49
#: ../../content/applications/general/voip/asterisk.rst:50
msgid "**Build and install pjproject:**"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:57
#: ../../content/applications/general/voip/asterisk.rst:58
msgid "**Update shared library links:**"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:63
#: ../../content/applications/general/voip/asterisk.rst:64
msgid "**Verify that pjproject is installed:**"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:69
#: ../../content/applications/general/voip/asterisk.rst:70
msgid "**The result should be:**"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:86
#: ../../content/applications/general/voip/asterisk.rst:87
msgid "Asterisk"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:88
#: ../../content/applications/general/voip/asterisk.rst:89
msgid "In order to install Asterisk 13.7.0, you can download the source directly `there <http://downloads.asterisk.org/pub/telephony/asterisk/old-releases/asterisk-13.7.0.tar.gz>`_."
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:90
#: ../../content/applications/general/voip/asterisk.rst:92
msgid "Extract Asterisk:"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:96
#: ../../content/applications/general/voip/asterisk.rst:98
msgid "Enter the Asterisk directory:"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:102
#: ../../content/applications/general/voip/asterisk.rst:104
msgid "Run the Asterisk configure script:"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:108
#: ../../content/applications/general/voip/asterisk.rst:110
msgid "Run the Asterisk menuselect tool:"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:114
#: ../../content/applications/general/voip/asterisk.rst:116
msgid "In the menuselect, go to the resources option and ensure that res_srtp is enabled. If there are 3 x’s next to res_srtp, there is a problem with the srtp library and you must reinstall it. Save the configuration (press x). You should also see stars in front of the res_pjsip lines."
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:116
#: ../../content/applications/general/voip/asterisk.rst:120
msgid "Compile and install Asterisk:"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:122
#: ../../content/applications/general/voip/asterisk.rst:126
msgid "If you need the sample configs you can run 'make samples' to install the sample configs. If you need to install the Asterisk startup script you can run 'make config'."
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:125
#: ../../content/applications/general/voip/asterisk.rst:130
msgid "DTLS Certificates"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:127
#: ../../content/applications/general/voip/asterisk.rst:132
msgid "After you need to setup the DTLS certificates."
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:133
#: ../../content/applications/general/voip/asterisk.rst:138
msgid "Enter the Asterisk scripts directory:"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:139
#: ../../content/applications/general/voip/asterisk.rst:144
msgid "Create the DTLS certificates (replace pbx.mycompany.com with your ip address or dns name, replace My Super Company with your company name):"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:146
#: ../../content/applications/general/voip/asterisk.rst:152
msgid "Configure Asterisk server"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:148
#: ../../content/applications/general/voip/asterisk.rst:154
msgid "For WebRTC, a lot of the settings that are needed MUST be in the peer settings. The global settings do not flow down into the peer settings very well. By default, Asterisk config files are located in /etc/asterisk/. Start by editing http.conf and make sure that the following lines are uncommented:"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:158
#: ../../content/applications/general/voip/asterisk.rst:166
msgid "Next, edit sip.conf. The WebRTC peer requires encryption, avpf, and icesupport to be enabled. In most cases, directmedia should be disabled. Also under the WebRTC client, the transport needs to be listed as ‘ws’ to allow websocket connections. All of these config lines should be under the peer itself; setting these config lines globally might not work:"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:186
#: ../../content/applications/general/voip/asterisk.rst:197
msgid "In the sip.conf and rtp.conf files you also need to add or uncomment the lines:"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:193
#: ../../content/applications/general/voip/asterisk.rst:204
msgid "Lastly, set up extensions.conf:"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:202
#: ../../content/applications/general/voip/asterisk.rst:213
msgid "Configure Odoo VOIP"
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:204
#: ../../content/applications/general/voip/asterisk.rst:215
msgid "In Odoo, the configuration should be done in the user's preferences."
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:210
#: ../../content/applications/general/voip/asterisk.rst:221
msgid "The SIP Login/Browser's Extension is the number you configured previously in the sip.conf file (in our example: 1060)."
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:212
#: ../../content/applications/general/voip/asterisk.rst:224
msgid "The SIP Password is the secret you chose in the sip.conf file."
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:214
#: ../../content/applications/general/voip/asterisk.rst:226
msgid "The extension of your office's phone is not a required field but it is used if you want to transfer your call from Odoo to an external phone also configured in the sip.conf file."
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:217
#: ../../content/applications/general/voip/asterisk.rst:230
msgid "The configuration should also be done in the General Settings under the \"Integrations\" section."
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:222
#: ../../content/applications/general/voip/asterisk.rst:235
msgid "The PBX Server IP should be the same as the IP you define in the http.conf file."
msgstr ""
#: ../../content/applications/general/voip/asterisk.rst:224
#: ../../content/applications/general/voip/asterisk.rst:237
msgid "The WebSocket should be: ws://localhost:XXXX/ws where \"localhost\" needs to be the same as the IP defined previously and \"XXXX\" needs to be the port defined in the http.conf file."
msgstr ""

1267
locale/sources/inventory_and_mrp.pot
View File

File diff suppressed because it is too large Load Diff

1100
locale/sources/legal.pot
View File

File diff suppressed because it is too large Load Diff

711
locale/sources/marketing.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-01-31 10:25+0000\n"
"POT-Creation-Date: 2023-03-03 11:23+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"
@ -20,6 +20,593 @@ msgstr ""
msgid "Marketing"
msgstr ""
#: ../../content/applications/marketing/events.rst:5
msgid "Events"
msgstr ""
#: ../../content/applications/marketing/events.rst:8
msgid "`Odoo Tutorials: Events <https://www.odoo.com/slides/surveys-63>`_"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:3
msgid "Event essentials"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:5
msgid "Odoo Events provides event coordinators with an arsenal of planning, communications, and reporting tools to create immersive and engaging experiences for customers. Namely, staff can create and publish events on their website, sell tickets online, scan tickets with Odoo barcode, send out automated emails, and generate rich reporting data once the event accepts registrations."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:11
msgid "Kanban concepts and organization"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:13
msgid "To get started, click on the :guilabel:`Events` application on the home dashboard, which then leads to the kanban view populated with a variety of pipeline stages. Key information is listed on each event card, such as the date/time of the event, along with the number of expected (and confirmed) attendees."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:18
msgid "To create a new stage, click :guilabel:`Add a Column` and provide a befitting title to reflect the purpose of that stage."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:21
msgid "To reorganize the stages, just drag-and-drop them until they are in the correct order. Stages can also be “folded” in the kanban for a cleaner presentation, via the :guilabel:`Settings` menu to the right of each stage's title, which is represented by a gear icon."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:26
msgid "The gear icon, by default, is hidden and will appear next to the :guilabel:`+` icon when moused over."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:29
msgid "When clicked, a drop-down menu of settings will appear."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:None
msgid "Overview of events setting with the kanban view in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:36
msgid "Create a new event"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:38
msgid "To create an event, click :guilabel:`Create` from the Events dashboard. Odoo will then direct the page to a blank event template form."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:41
msgid "From the event form, fill out the necessary fields, either by choosing from existing data in the Odoo database or by creating and editing new field data. Key information to enter for the event includes:"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:45
msgid ":guilabel:`Event Name`: give the event a title."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:46
msgid ":guilabel:`Date`: includes the start and end dates/times for the event."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:47
msgid ":guilabel:`Timezone`: covers the timezone for when the event is taking place."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:48
msgid ":guilabel:`Template`: choose from a pre-built event template or build a custom one and connect it here."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:50
msgid ":guilabel:`Tags`: add tags to indicate briefly what the event is for (e.g. `tradeshow`). Tags help better organize event cards in the kanban and are useful when using search filters during reporting periods."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:53
msgid ":guilabel:`Organizer`: detail the organizer(s) for the event. This field is usually the company that owns the Odoo database, or a vendor."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:55
msgid ":guilabel:`Responsible`: name the point person who is responsible for organizing the event."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:56
msgid ":guilabel:`Website`: indicate which Odoo website(s) the event event should be published to."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:57
msgid ":guilabel:`Venue`: list the venue details here if it's a new record, or choose from an existing location."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:59
msgid ":guilabel:`Limit Registrations`: when enabled, this setting caps the attendee registrations to a specified amount"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:61
msgid ":guilabel:`Autoconfirmation`: when enabled, this setting skips the confirmation request that gets sent by email to event registrants, and automatically confirms their registration."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:64
msgid "Once the fields in the event form are set, move on to the :guilabel:`Tickets` and :guilabel:`Communication` tabs, and optionally the :guilabel:`Questions` tab if registrations should require additional information."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:69
msgid "Add and sell event tickets"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:71
msgid "Under the :guilabel:`Tickets` tab, add line items for each type of ticket the event plans to offer. Here, determine the ticket price, start/end dates for registrations, as well as the maximum number of tickets that can be sold."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:75
msgid "If selling tickets isn't necessary for the event, a simple :guilabel:`Registration` button will be displayed on the event's page by default."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:None
msgid "View of the ticket tab in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:83
msgid "Send automated emails, text, and social posts to event attendees"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:85
msgid "Under the :guilabel:`Communication` tab, configure personalized email, SMS, or social post messages to keep in touch with event attendees. For each communication, click :guilabel:`Add a line` in the :guilabel:`Communication` tab form, and then choose (or create) a communications template using the drop-down menu under the :guilabel:`Template` column."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:90
msgid "Next, define the :guilabel:`Interval` and :guilabel:`Unit` of time for how often the communication should be sent; use these time fields to specify the frequency of :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months` communications should be sent. There is also the option to send communications `Immediately` after a specified :guilabel:`Trigger` is activated."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:96
msgid "In the last column, determine the :guilabel:`Trigger` which controls how and when the communication is sent. For this action, choose between: :guilabel:`Before the event`, :guilabel:`After each registration`, or :guilabel:`After the event`."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:None
msgid "View of the communication tab in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:105
msgid "Attach a questionnaire to event registrations"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:107
msgid "Implementing a questionnaire during event sign up is an effective way to gauge the wants, needs, and interests of the event's attendees ahead of time. Questionnaires also act as informative analytics tools for reporting periods before (or after) events take place."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:111
msgid "To create a questionnaire, from the :guilabel:`Events` application, navigate to :menuselection:`Configuration --> Settings` and then enable the :guilabel:`Questions` setting."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:114
msgid "With the setting enabled, questions and answers can now be added (and recorded) under the the :guilabel:`Questions` tab back on the event form. For each question, specify if it should only be asked once with the :guilabel:`Ask once per order` checkbox, or if the question requires a :guilabel:`Mandatory Answer`, which will make the question required for registration."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:120
msgid "If the :guilabel:`Once per order` checkbox is enabled, then a single registration for 3 event attendees will show the questionnaire only once."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:123
msgid "There are two :guilabel:`Question Types` to choose from: :guilabel:`Selection` and :guilabel:`Text Input`. The :guilabel:`Selection` type, allows attendees to select an answer from pre-configured options, which are entered in the :guilabel:`Answers` tab below. The :guilabel:`Text Input` type allows attendees to write in their own answer to the question in a text box."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:None
msgid "View of an event form, open the questions tab, and add a question."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:133
msgid "Log internal notes or add ticket instructions"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:135
msgid "In the :guilabel:`Notes` tab, there is the option to add a :guilabel:`Note` and/or :guilabel:`Ticket instructions`."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:138
msgid "Under :guilabel:`Note`, internal notes can be left (such as: to-do lists, contact information, etc.) for event staff to reference. In the :guilabel:`Ticket instructions` field, helpful information for staff and attendees can be shared (like, directions to the venue, opening/closing times, etc.)"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:144
msgid "Type `/` in either text field (:guilabel:`Note` or :guilabel:`Ticket instructions`) to reveal a sub-menu of :guilabel:`Structure` options. These options provide various formatting options to ensure vital internal information is organzied for event staff to review."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:None
msgid "View of the Notes tab in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:153
msgid "Invite attendees to the event"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:155
msgid "To invite people to an event, click the :guilabel:`Invite` button located in the top left corner of the event form."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:158
msgid "Inside the invite template form, are options to sent email or SMS invites. Each message can be fully customized, and recipients can be added."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:161
msgid "Adding a :guilabel:`Subject` line for the invite message is required, but the :guilabel:`Preview Text` field is optional. The :guilabel:`Preview Text` is a catchy preview sentence meant to encourage recipients to open the email."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:166
msgid "In most cases, the :guilabel:`Preview Text` is displayed next to the subject. Keep this field empty to ensure the first characters of the email content appear, instead."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:170
msgid "Select invitees and configure recipient filters"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:172
msgid "In the middle of the invitation form, find and click the :guilabel:`Recipients` field, to reveal a drop-down menu of recipient options. These choices represent where Odoo will find the desired recipients' information."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:176
msgid "Once an option from this menu is selected (e.g. :guilabel:`Applicant`, :guilabel:`Contact`, :guilabel:`Event Registration`, :guilabel:`Lead/Opportunity`, etc.), Odoo will send the invitation to all recipients who match that initial rule. Additional rules can be added to narrow down the target recipients, by clicking :guilabel:`Add Filter`."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:None
msgid "View of the add filter button beneath the recipients field in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:185
msgid "Clicking :guilabel:`Add Filter` reveals three fields, formatted like an equation. To reveal the sub-menu options, click each field, and make the desired selections, until the preferred configuration has been acheived. The number of :guilabel:`Records` that match the rule(s) are indicated to the right of the :guilabel:`Recipients` field, in green."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:191
msgid "Some sub-menu options in the first rule field allow for a second choice to provide even more specificity."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:194
msgid "To the right of each rule, are :guilabel:`x`, :guilabel:`+`, and :guilabel:`...` icons. The :guilabel:`x` icon deletes a specific node (line) of the rule. The :guilabel:`+` icon adds a node (line) to the rule. And, the :guilabel:`...` icon adds a branch to the node. A branch means two additional, indented sub-nodes are added to the rule, providing even more specificity to the line above it."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:201
msgid "Build a custom event invite"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:203
msgid "In the :guilabel:`Mail Body` tab, there are a number of pre-configured message templates to choose from. Select the desired template, and modify every element of its design details with Odoo's drag-and-drop web builder, located on the right sidebar."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:None
msgid "View of the drag and drop building blocks used to customize event invite emails."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:212
msgid "To build an email event invite from scratch, select the :guilabel:`Plain Text` template, and Odoo will provide a blank email canvas, which can be customized either by using the front-end rich text editor that accepts slash (`/`) commands, or the XML code editor when :ref:`developer mode <developer-mode>` is engaged and the :guilabel:`</>` icon is pressed."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:218
msgid "The :guilabel:`Mail Body` tab (and template options), are only available if the event invite :guilabel:`Mailing Type` is designated as an :guilabel:`Email`. If :guilabel:`SMS` is the :guilabel:`Mailing Type`, a :guilabel:`SMS Content` tab (consisting of a blank text space), is available, instead."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:224
msgid "Modify event invite settings"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:226
msgid "The options under the :guilabel:`Settings` tab are different, depending on the specified :guilabel:`Mailing Type`."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:229
msgid "If the :guilabel:`Email` option is selected as the :guilabel:`Mailing Type`, an employee can be designated as the :guilabel:`Responsible`, meaning that person is the one responsible for this particular invite message. :guilabel:`Send From` and :guilabel:`Reply To` email aliases can be designated here, as well."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:234
msgid "Also, if any specific documents are required (or helpful) for this event invite, they can be sent along with this email, by clicking :guilabel:`ATTACH A FILE`, and adding the appropriate document(s)."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:238
msgid "If the :guilabel:`SMS` option is selected as the :guilabel:`Mailing Type`, a :guilabel:`Responsible` can be designated, and the option to :guilabel:`Include an opt-out link` is available."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:242
msgid "Send event invitations to recipients"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:244
msgid "If the selected :guilabel:`Mailing Type` is :guilabel:`Email`, there are three options to send the invite: :guilabel:`Send`, :guilabel:`Schedule`, and :guilabel:`Test`."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:247
msgid "The :guilabel:`Send` option sends the invite right away. The :guilabel:`Schedule` option reveals a pop-up, in which a scheduled date/time can be selected for the email to be sent. The :guilabel:`Test` option reveals a :guilabel:`Test Mailing` pop-up, where specific recipient email addresses can be entered for Odoo to send them the current version of the mailing for review before officially sending it out to prospective event attendees."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:253
msgid "If the selected :guilabel:`Mailing Type` is :guilabel:`SMS`, there are four options to send the invite: :guilabel:`Put in Queue`, :guilabel:`Send Now`, :guilabel:`Schedule`, and :guilabel:`Test`."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:256
msgid "The :guilabel:`Put in Queue` option schedules an SMS message to all recipients (that match the designated rules, if any) in the near future. Clicking :guilabel:`Put in Queue` reveals a pop-up, requiring confirmation. When confirmed, a blue banner appears on the event invite template form, indicating that the SMS will be sent later that day."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:262
msgid "The :guilabel:`Send Now`, :guilabel:`Schedule`, and :guilabel:`Test` options all function the same way for both :guilabel:`Mailing Type` options."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:266
msgid "Publish events"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:268
msgid "Until an event is published, it will remain hidden from public view on the website and registering for it will not be possible. To publish an event, navigate to it either from the back end of Odoo through the :guilabel:`Events` application, or access the hidden event page through the front end as either a priveliged user or administrator."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:273
msgid "If navigating from the back end, go to the event form, and click the :guilabel:`Go to Website` smart button to reach the event page on the website (on the front end). If starting from the front end, simply navigate to the event page that needs to be published."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:277
msgid "No matter the route, an event page can only be published from the front end. In the upper right corner of the event page on the website, toggle the switch from the red :guilabel:`Unpublished` status to the green :guilabel:`Published` status. Doing so instantly makes the event page accessible to the public on the website."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:None
msgid "View of a website page and the option to publish the event in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:3
msgid "Sell tickets"
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:5
msgid "Create custom ticket tiers (with various price points) for potential attendees to choose from, directly on the event template form, under the :guilabel:`Tickets` tab. Odoo simplifies the ticket-purchasing process by providing plenty of payment method options."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:10
#: ../../content/applications/marketing/events/track_manage_talks.rst:9
msgid "Configuration"
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:12
msgid "First, in order to enable the creation (and selling of) event tickets, go to :menuselection:`Configuration --> Settings`, then enable the :guilabel:`Tickets` and :guilabel:`Online Ticketing` features."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:16
msgid "The :guilabel:`Tickets` feature allows tickets to be sold for an event."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:18
msgid "The :guilabel:`Online Tickets` feature allows for the sale of tickets to occur through the website."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:21
msgid "If these options are *not* enabled, a default :guilabel:`Register` button will be available for free registrations."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:None
msgid "View of the settings page for Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:29
msgid "Sell tickets through sales orders"
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:31
msgid "In the :guilabel:`Sales` application, choose a previously-created Event Registration (as if it were a product), and add it as a product line. Upon adding the registration, a pop-up appears, which allows for the selection of a specific event (and ticket tier). That specific event ticket is then attached to the sales order."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:None
msgid "View of a sales order and option to choose the specific event in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:40
msgid "Events with tickets sold online or through sales orders have a :guilabel:`Sales Smart Button` shortcut, located at the top of the event template form (in the :guilabel:`Events` application)."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:43
msgid "Clicking the :guilabel:`Sales Smart Button` reveals a page with all the sales orders related to that event."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:None
msgid "View of an event's form and the sales smart button in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:None
msgid "View of an event form highlighting the column product under the tickets tab in Odoo\n"
"Events."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:56
msgid "Sell tickets through the website"
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:58
msgid "With tickets purchased through the website, the process is similar to creating a :guilabel:`Sales Order` with a specific :guilabel:`Registration` product. Here, tickets are added to a virtual cart, and the transaction can be completed as usual - utilizing any of the pre-configured payment methods options that have been set up on the website."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:63
msgid "The completed purchase is automatically produced in a :guilabel:`Sales Order`, which can be easily accessed in the back end of the database."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:None
msgid "View of website transaction for Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:3
msgid "Track and manage talks"
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:5
msgid "With Odoo Events, it's possible to provide attendees with the power to propose presenters to speak at events."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:11
msgid "First, go to :menuselection:`Events --> Configuration --> Settings` and enable :guilabel:`Schedule & Tracks`."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:14
msgid "When that feature is enabled, two more options become available: *Live Broadcast* and *Event Gamification*."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:17
msgid ":guilabel:`Live Broadcast` allows for the airing of tracks online through a YouTube integration."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:19
msgid ":guilabel:`Event Gamification` allows for the sharing of a quiz with your attendees, once a track (talk) is over."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:23
msgid ":guilabel:`Event Gamification` isn't necessary for tracks to appear on the event page on the website, but it can enhance the engagement and overall enjoyablity of the event for attendees."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:27
msgid "Talks, talk proposals, and agenda"
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:29
msgid "Once those two features are enabled, the following links are automatically added to the sub-header menu, located on the event page on the website: :guilabel:`Talks`, :guilabel:`Talk Proposals`, and :guilabel:`Agenda`. Any attendee can freely access these menu items and their corresponding content."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:33
msgid "The :guilabel:`Talks` link takes the attendee to a page full of all the talks for that event."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:35
msgid "The :guilabel:`Talks Proposals` link takes the attendee to a form page, where they can propose talks for the event."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:38
msgid "The :guilabel:`Agenda` link takes the attendee to a page with all the talks for the event, but in a calendar/time-slot format."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:None
msgid "View of the published website and the talks, talk proposals, and agenda in Odoo Events"
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:46
msgid "Manage talk proposals"
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:48
msgid "When attendees fill out and submit a talk proposal form on the website, a new :guilabel:`Proposal` is instantly created in the back end for the event."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:52
msgid "All talks (Proposals, Confirmed, Announced, etc.) are accessible via the :guilabel:`Tracks` smart button on the event form."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:None
msgid "View of the talks' proposals page emphasizing the column proposal in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:59
msgid "If a proposal is accepted, move the :guilabel:`Event Track` to the appropriate stage in the Kanban view (e.g. `Confirmed`, etc.). Then, go to that particular event's template form, and click the :guilabel:`Go to Website` smart button to reach that specific talk's page on the website."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:63
msgid "In the upper right corner, toggle the switch from :guilabel:`Unpublished` to :guilabel:`Published`, and the talk is instantly accessible on the website."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:67
msgid "Without publishing a talk, attendees will never be able to access it."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:None
msgid "View of the website page to publish a proposed talk for Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:74
msgid "Attendees list and attendance"
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:76
msgid "Once attendees have registered for a specific event, they are added to the :guilabel:`Attendee List` for that event, which is accessible via the :guilabel:`Attendees` smart button on the event template form, or :menuselection:`Reporting --> Attendees` and sorted by event."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:81
msgid "When an attendee arrives at the event, they will be marked as attending (:guilabel:`Confirmed Attendance`), and the status of that attendee will change to :guilabel:`Attended.`"
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:None
msgid "Overview of events with the kanban view in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:88
msgid "When analyzing an :guilabel:`Attendees list`, Odoo provides different ways to view the information. Each view option presents the same information, but in a slightly different layout. To change the view, click on the icons in the upper right hand of the screen."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:None
msgid "Various view options on the attendees list page."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:96
msgid "In the :guilabel:`Kanban` view, it can be confirmed whether the attendees have already paid or remain unpaid."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:99
msgid "The :guilabel:`List` view provides information in a more traditional list formation."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:101
msgid "The :guilabel:`Calendar` view provides a clear schedule visualization of which attendees are arriving on specific dates of the event."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:104
msgid "The :guilabel:`Graph` view provides graphical representations of that event's attendees, along with numerous filters and customizable measures for deeper analysis."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:107
msgid "The :guilabel:`Cohort` view lays out attendee data to better analyze the number of registration dates."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:111
msgid "Tickets sold through sales orders validate attendees as soon as the quotation is confirmed."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:114
msgid "Manage registrations"
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:116
msgid "Upon selecting an attendee, Odoo reveals that specific attendee's detail form."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:118
msgid "From here, event badges can be sent manually, by selecting :guilabel:`Send By Email`. The :guilabel:`Attendee` can also be marked as :guilabel:`Attended`, or the registration can be canceled altogether via the :guilabel:`Cancel Registration` button."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:None
msgid "View of an attendee form emphasizing the send by email and cancel registration in Odoo\n"
"Events."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:128
msgid "Lead Generation Rules"
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:130
msgid "With Odoo, leads can be generated from events."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:132
msgid "To create and configure a :guilabel:`Lead Generation Rule` related to events, navigate to :menuselection:`Events app --> Configuration --> Lead Generation`."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:135
msgid "On the :guilabel:`Lead Generation Rule` page, every configured :guilabel:`Lead Generation Rule` can be found, along with pertinent data related to those rules."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:None
msgid "How the Lead Generation Rule page looks in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:142
msgid "To create a new :guilabel:`Lead Generation Rule`, click :guilabel:`Create`, and fill out the :guilabel:`Lead Generation Rule` form."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:None
msgid "How the Lead Generation Rule template looks in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:149
msgid "After naming the rule, configure *how* the lead should be created (either :guilabel:`Per Attendee` or :guilabel:`Per Order`), and *when* they should be created, (when :guilabel:`Attendees are created`, when :guilabel:`Attendees are confirmed`, or when :guilabel:`Attendees attended` the event)."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:154
msgid "In the :guilabel:`For any of these Events` section, there are fields to attach this rule to any specific event categories, company, and/or event. To add even more specificity to the rule, a domain filter rule can be configured to ensure the rule only applies to a specific target audience of attendees (found in the :guilabel:`If the Attendees meet these Conditions` section)."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:159
msgid "Lastly, in the :guilabel:`Lead Default Values` section, designate a :guilabel:`Lead Type`, then assign it to a specific :guilabel:`Sales Team` (and/or :guilabel:`Salesperson`), and attach tags to the rule, if necessary."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:8
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:3
msgid "Marketing Automation"
@ -492,7 +1079,7 @@ msgstr ""
msgid "What do I need to send SMSs?"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:9
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:10
msgid "SMS Text Messaging is an In-App Purchase (IAP) service that *requires prepaid credits* to work."
msgstr ""
@ -500,162 +1087,168 @@ msgstr ""
msgid "How many types of SMSs are there?"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:14
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:15
msgid "There are 2 types: GSM7 and UNICODE."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:16
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:17
msgid "**GSM7** is the standard format, with a limit of 160 characters per message, that includes the following characters:"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:None
msgid "GSM7 in Odoo SMS Marketing"
msgid "GSM7 characters available in Odoo SMS Marketing."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:25
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:24
msgid "**UNICODE** is the format applied if a special character, that *is not* in the GSM7 list, is used. Limit per SMS: 70 characters."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:29
msgid "For GSM7 SMS the size limit is 160 characters, and for Unicode is 70. *Above these limits, the content is divided into a multi-part message* and the limit of characters is lowered to 153 for GSM7 and to 67 for Unicode. The system will inform you in real-time about the number of SMS your message represents."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:28
msgid "For GSM7 SMS the size limit is 160 characters, and for Unicode is 70. *Above these limits, the content is divided into a multi-part message* and the limit of characters is lowered to 153 for GSM7 and to 67 for Unicode. Then, in real-time, the system displays the number of SMS mailings the message represents."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:36
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:34
msgid "How much does it cost to send an SMS?"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:37
msgid "The price of an SMS depends on the destination and the length (number of characters) of the message."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:36
msgid "The price of an SMS depends on the destination and the length (number of characters) of the message. To see the **price per country, please consult**: `Odoo SMS - FAQ <https://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:39
msgid "To see the **price per country, please consult**: `Odoo SMS - FAQ <https://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:41
msgid "The number of SMSs a message represents will be always available to you in your database."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:40
msgid "The number of SMSs a message represents will always be available in the database."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:None
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:None
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:None
msgid "SMS pricing and FAQ Odoo SMS Marketing"
msgid "Number of GSM7 characters that fit in an SMS message in Odoo SMS Marketing."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:51
msgid "How do I buy credits?"
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:47
msgid "How to buy credits"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:52
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:49
msgid "Go to :menuselection:`Settings --> Buy Credits`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:59
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:None
msgid "Buying credits for SMS Marketing in Odoo settings."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:55
msgid "Or go to :menuselection:`Settings --> View my Services`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:67
msgid "If you are on Odoo Online and have the Enterprise version, you benefit from free trial credits to test the feature."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:None
msgid "Using Odoo IAP to recharge credits for SMS Marketing in Odoo settings."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:72
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:62
msgid "If Odoo Online (Saas) is being used, along with the Enterprise version, free trial credits are available to test the feature."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:66
msgid "More common questions"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:74
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "**Is there an expiration time for my credits?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:76
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "No, credits do not expire."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:79
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "**Can I send an SMS to a phone number (which is not a mobile phone) because I see the icon in front of the field “phone”?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:82
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "Only if that phone number supports SMS (e.g. SIP phones)."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:85
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "**Do I receive an invoice to buy my credits?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:87
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "Yes."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:90
msgid "**Can the recipient answer to me?**"
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "**Can the recipient answer me?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:92
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "No, it is not possible to reply to the SMS."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:95
msgid "**What happens if I send multiple SMS but I do not have enough credits to send them all?**"
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "**What happens if I send multiple SMSs at once, but I don't have enough credits to send them all?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:97
msgid "The whole transaction is counted as a single one, so no SMS will be sent until you have enough credits to send them all."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "Multiple SMS communications at once at are counted as a single transaction, so no SMSs will be sent until there are enough credits to send them all."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:101
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "**Do I have a history of the sent SMSs?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:103
msgid "Yes, the SMS is logged as a note under the chatter of the corresponding record, and a complete history of the SMSs sent is available on :ref:`developer mode <developer-mode>` under :menuselection:`Technical --> SMS`."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "A history of sent SMSs, along with all pertinent information related to its sent contacts (and the message itself), can be found in the :guilabel:`Sent` column of the main :guilabel:`SMS Marketing` dashboard (while in :guilabel:`Kanban` view)."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:108
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:91
msgid "For more detailed information, select a desired SMS from the main dashboard (in :guilabel:`Kanban` view), and click on either link in the blue banner above the SMS detail form to learn more."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "**Can I send as many SMSs I want at once?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:110
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "Yes, if you have enough credits."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:113
msgid "**If I have a number that does not exist in the list of recipients, will I lose credits?**"
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "**If an SMS is sent to a number that doesn't exist in the list of recipients, will credits be lost?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:115
msgid "Not if the phone number is in the wrong format (e.g. too many digits). Otherwise, if the SMS is sent to the wrong person or to a fake number, the credit will be lost."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "No, not if the phone number is incorrectly formatted (e.g. too many digits). However, if the SMS is sent to the wrong person (or to a fake number), the credit for that SMS will be lost."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:119
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "**What happens if I send my SMS to a paying number (e.g.: a contest to win a ticket for a festival)?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:121
msgid "The SMS will not be delivered to that kind of number, so you won’t be charged."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "The SMS will not be delivered to that kind of number, so no charges will be made."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:124
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "**Can I identify the numbers that do not exist when I send several SMSs?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:126
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "Only the ones that have an invalid format."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:129
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "**How does the GDPR regulation affect this service?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:131
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "Please find our `Privacy Policy here <https://iap.odoo.com/privacy#sms>`__."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:133
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "**Can I use my own SMS provider?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:135
msgid "Yes, but it is not possible out of the box. Our experts can help you customize your database to make it happen. Please, check our success packs `here <https://www.odoo.com/pricing-packs>`_."
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0
msgid "Yes, but it is not possible out-of-the-box. Odoo experts can help customize a database to allow for the use of a personal SMS provider. Please check our success packs `here <https://www.odoo.com/pricing-packs>`_."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:8

31
locale/sources/productivity.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-01-02 09:09+0000\n"
"POT-Creation-Date: 2023-03-03 11:23+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"
@ -818,7 +818,7 @@ msgstr ""
#: ../../content/applications/productivity/iot/devices/footswitch.rst:13
#: ../../content/applications/productivity/iot/devices/printer.rst:11
#: ../../content/applications/productivity/iot/devices/scale.rst:10
#: ../../content/applications/productivity/iot/devices/screen.rst:18
#: ../../content/applications/productivity/iot/devices/screen.rst:17
msgid "Connection"
msgstr ""
@ -1111,15 +1111,15 @@ msgstr ""
msgid "Access the customer display from any other computer by going to the :abbr:`IoT (Internet of Things)` Box homepage and clicking on the :guilabel:`POS Display` button."
msgstr ""
#: ../../content/applications/productivity/iot/devices/screen.rst:20
#: ../../content/applications/productivity/iot/devices/screen.rst:19
msgid "The way to connect the screen display to the :abbr:`IoT (Internet of Things)` Box differs depending on the model."
msgstr ""
#: ../../content/applications/productivity/iot/devices/screen.rst:25
#: ../../content/applications/productivity/iot/devices/screen.rst:24
msgid "IoT Box model 4"
msgstr ""
#: ../../content/applications/productivity/iot/devices/screen.rst:27
#: ../../content/applications/productivity/iot/devices/screen.rst:26
msgid "Connect up to two screens with Micro-HDMI cables on the side of the :abbr:`IoT (Internet of Things)` Box. If two screens are connected, they can display distinct content (see usage below)."
msgstr ""
@ -1164,19 +1164,19 @@ msgstr ""
msgid "The \"Distant Display\" screen name will be used if no screen is detected."
msgstr ""
#: ../../content/applications/productivity/iot/devices/screen.rst:66
#: ../../content/applications/productivity/iot/devices/screen.rst:67
msgid "Usage"
msgstr ""
#: ../../content/applications/productivity/iot/devices/screen.rst:69
#: ../../content/applications/productivity/iot/devices/screen.rst:70
msgid "Show Point of Sales orders to customers"
msgstr ""
#: ../../content/applications/productivity/iot/devices/screen.rst:71
#: ../../content/applications/productivity/iot/devices/screen.rst:72
msgid "To use the screen in the :guilabel:`Point of Sale` app, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, open the desired screen, click on :guilabel:`Edit`, and enable the :guilabel:`IoT Box Devices` feature."
msgstr ""
#: ../../content/applications/productivity/iot/devices/screen.rst:75
#: ../../content/applications/productivity/iot/devices/screen.rst:76
msgid "Now, select :guilabel:`IoT Box` in the drop-down menu and choose the screen in the :guilabel:`Customer Display` option. Then, click :guilabel:`Save`."
msgstr ""
@ -1184,15 +1184,16 @@ msgstr ""
msgid "Connect the screen display to the Point of Sale app."
msgstr ""
#: ../../content/applications/productivity/iot/devices/screen.rst:82
#: ../../content/applications/productivity/iot/devices/screen.rst:83
msgid "The screen is now available for :abbr:`PoS (Point of Sale)` sessions. A \"screen\" icon will appear in the top bar to inform the connection status with the screen."
msgstr ""
#: ../../content/applications/productivity/iot/devices/screen.rst:0
msgid "The \"screen\" icon on the Point of Sale display shows the connection status with the screen."
msgid "The \"screen\" icon on the Point of Sale display shows the connection status with the\n"
"screen."
msgstr ""
#: ../../content/applications/productivity/iot/devices/screen.rst:89
#: ../../content/applications/productivity/iot/devices/screen.rst:91
msgid "The screen will automatically show the :abbr:`PoS (Point of Sale)` orders and update when changes are performed on the order."
msgstr ""
@ -1200,11 +1201,11 @@ msgstr ""
msgid "An example of a PoS order on a screen display."
msgstr ""
#: ../../content/applications/productivity/iot/devices/screen.rst:97
#: ../../content/applications/productivity/iot/devices/screen.rst:99
msgid "Display a website"
msgstr ""
#: ../../content/applications/productivity/iot/devices/screen.rst:99
#: ../../content/applications/productivity/iot/devices/screen.rst:101
msgid "Opening the screen form view at :menuselection:`IoT --> Devices --> (screen device)` allows the user to choose a particular website URL to display on the screen with the :guilabel:`Screen URL` field."
msgstr ""
@ -1475,7 +1476,7 @@ msgid "Custom add-ins in Outlook"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:43
msgid "Enter the following URL `https://download.odoo.com/plugins/v15/outlook/manifest.xml` and press *OK*."
msgid "Enter the following URL `https://download.odoocdn.com/plugins/v15/outlook/manifest.xml` and press *OK*."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0

285
locale/sources/sales.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-01-31 10:25+0000\n"
"POT-Creation-Date: 2023-03-03 11:23+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"
@ -67,7 +67,7 @@ msgstr ""
#: ../../content/applications/sales/point_of_sale/restaurant/split.rst:10
#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:10
#: ../../content/applications/sales/point_of_sale/shop/cash_rounding.rst:17
#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:8
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:6
#: ../../content/applications/sales/rental.rst:20
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:13
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:23
@ -1830,7 +1830,7 @@ msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:19
#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:36
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:65
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:63
msgid "Configure the payment method"
msgstr ""
@ -1920,7 +1920,7 @@ msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:80
#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:53
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:88
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:86
msgid "Pay with a payment terminal"
msgstr ""
@ -2097,7 +2097,7 @@ msgid "Worldline"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:9
msgid "Please note that Worldline is currently only available in Belgium."
msgid "Please note that Worldline is currently only available in the Benelux."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:17
@ -2113,30 +2113,26 @@ msgid "From your terminal, click on :menuselection:`\".\" --> 3 --> stop --> 3 -
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:31
msgid "Here are some useful :ref:`tips <worldline/yomani-info>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:34
msgid "Set the IP address"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:36
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:33
msgid "From your terminal, click on :menuselection:`\".\" --> 3 --> stop --> 3 --> 0 --> 9`. Enter the technician password **\"1235789\"** and click on :menuselection:`OK --> 4 --> 9`. Then, click on :menuselection:`Change --> TCP/IP` (*TCP physical configuration* screen) :menuselection:`--> OK --> OK` (*TCP Configuration client* screen)."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:41
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:38
msgid "Finally, set up the hostname and port number."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:44
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:41
msgid "Hostname"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:47
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:44
msgid "To set up the hostname, enter your IoT box's IP address' sequence numbers and press **OK** at each \".\" until you reach the colon symbol."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:48
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:45
msgid "Then, press **OK** twice."
msgstr ""
@ -2148,59 +2144,59 @@ msgstr ""
msgid "On the *Hostname screen*, type :menuselection:`10 --> OK --> 30 --> OK --> 19 --> OK --> 4 --> OK --> OK`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:56
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:53
msgid "Your IoT box's IP address is available in your IoT Box application's database."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:59
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:56
msgid "Port number"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:61
msgid "On the *Port number* screen, enter **\"9001\"** and click on :menuselection:`OK` (*ECR protocol SSL no*) :menuselection:`--> OK`. Click on **Stop** three times; the terminal automatically restarts."
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:58
msgid "On the *Port number* screen, enter **9001** (or **9050** for Windows) and click on :menuselection:`OK` (*ECR protocol SSL no*) :menuselection:`--> OK`. Click on **Stop** three times; the terminal automatically restarts."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:67
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:65
msgid "From the Point of Sale application, go to :menuselection:`Configuration --> Settings --> Payment terminals` and activate the *Worldline* payment terminal."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:73
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:71
msgid "Then, go to :menuselection:`Configuration --> Payment methods` and create a new payment method for *Worldline*. Select the payment terminal *Worldline* and your payment terminal device on your *Payment Method form*."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:80
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:78
msgid "Technician password: `1235789`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:81
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:79
msgid "To reach Wordline's technical assistance, call `02 727 61 11` and choose \"merchant\". Your call is automatically transferred to the desired service."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:83
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:81
msgid "Configure the cashier terminal if you have both a customer and a cashier terminal."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:84
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:82
msgid "To avoid blocking the terminal, check the initial configuration beforehand."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:85
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:83
msgid "Set a fixed IP to your IoT Box’s router to prevent losing the connexion."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:90
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:88
msgid "When processing a payment, select *Worldline* as payment method. Check the amount and click on *Send*. Once the payment is successful, the status changes to *Payment Successful*."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:93
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:91
msgid "Once your payment is processed, the type of card used and the transaction ID appear on the payment record."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:100
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:98
msgid "In case of connexion issues between Odoo and the payment terminal, force the payment by clicking on *Force Done*, which allows you to validate the order. This option is only available after receiving an error message informing you that the connection failed."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:104
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:101
msgid "To cancel the payment request, click on **cancel**."
msgstr ""
@ -2765,36 +2761,48 @@ msgstr ""
msgid "Now, you can open the order and have a summary of the sold products."
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:3
msgid "Reprint Receipts"
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:3
msgid "Receipts"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:5
msgid "Use the *Reprint receipt* feature if you have the need to reprint a ticket."
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:8
msgid "Set up receipts by going to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, selecting a POS, and scrolling down to the :guilabel:`Bills & Receipts` section."
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:10
msgid "To activate *Reprint Receipt*, go to :menuselection:`Point of Sale --> Configuration --> Point of sale`. and select your PoS interface."
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:11
msgid "To **customize** the **header** and **footer**, activate :guilabel:`Header & Footer` and fill in both fields with the information to be printed on the receipts."
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:13
msgid "Under the Bills & Receipts category, you will find *Reprint Receipt* option."
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:14
msgid "To **print receipts** automatically once the payment is registered, enable the :guilabel:`Automatic Receipt Printing` setting."
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:17
msgid "In order to allow the option reprint receipt, you need to activate the receipt printer."
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:None
msgid "pos receipt"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:23
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:22
msgid ":doc:`../restaurant/bill_printing`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:23
msgid ":doc:`../restaurant/split`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:26
msgid "Reprint a receipt"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:25
msgid "On your PoS interface, you now have a *Reprint receipt* button."
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:28
msgid "From the POS interface, click :guilabel:`Orders`, open the dropdown selection menu next to the search bar, and change the default :guilabel:`All active orders` filter to :guilabel:`Paid`. Then, select the corresponding order and click :guilabel:`Print Receipt`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/reprint.rst:30
msgid "When you use it, you can then reprint your last receipt."
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:None
msgid "print receipt button from the backend"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:37
msgid "You can filter the list of orders using the search bar. Type in your reference and click :guilabel:`Receipt Number`, :guilabel:`Date`, or :guilabel:`Customer`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:3
@ -3046,115 +3054,6 @@ msgstr ""
msgid "`Odoo Tutorials: Sales Tutorials <https://www.odoo.com/slides/sales-17>`_"
msgstr ""
#: ../../content/applications/sales/sales/advanced.rst:5
msgid "Advanced Topics"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:3
msgid "Portal access"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:5
msgid "Portal access is given to users who need the ability to view certain documents or information within an Odoo database."
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:8
msgid "Some common use cases for providing portal access include allowing customers to read/view any or all of the following in Odoo:"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:11
msgid "leads/opportunities"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:12
msgid "quotations/sales orders"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:13
msgid "purchase orders"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:14
msgid "invoices & bills"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:15
msgid "projects"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:16
msgid "tasks"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:17
msgid "timesheets"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:18
msgid "tickets"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:19
msgid "signatures"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:20
msgid "subscriptions"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:23
msgid "Portal users only have read/view access, and will not be able to edit any documents in the database."
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:27
msgid "Provide portal access to customers"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:28
msgid "From the main Odoo dashboard, select the :guilabel:`Contacts` application. If the contact is not yet created in the database, click on the :guilabel:`Create` button, enter the details of the contact, and then click :guilabel:`Save`. Otherwise, choose an existing contact, and then click on the :guilabel:`Action` drop-down menu located at the top-center of the interface."
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:None
msgid "Use the Contacts application to give portal access to users"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:37
msgid "Then select :guilabel:`Grant portal access`. A pop-up window appears, listing three fields:"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:39
msgid ":guilabel:`Contact`: the recorded name of the contact in the Odoo database"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:40
msgid ":guilabel:`Email`: the contact's email address that they will use to log into the portal"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:41
msgid ":guilabel:`In Portal`: whether or not the user has portal access"
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:43
msgid "To grant portal access, first enter the contact's :guilabel:`Email` they will use to log into the portal. Then, check the box under the :guilabel:`In Portal` column. Optionally, add text to the invitation message the contact will receive. Then click :guilabel:`Apply` to finish."
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:None
msgid "An email address and corresponding checkbox for the contact need to be filled in before\n"
"sending a portal invitation."
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:52
msgid "An email will be sent to the specified email address, indicating that the contact is now a portal user for that Odoo database."
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:56
msgid "To grant portal access to multiple users at once, navigate to a company contact, then click :menuselection:`Action --> Grant portal access` to view a list of all of the company's related contacts. Check the box under the :guilabel:`In Portal` column for all the contacts that need portal access, then click :guilabel:`Apply`."
msgstr ""
#: ../../content/applications/sales/sales/advanced/portal.rst:62
msgid "At any time, portal access can be revoked by navigating to the contact, clicking :menuselection:`Action --> Grant portal access`, and then unselecting the checkbox under the :guilabel:`In Portal` column and clicking :guilabel:`Apply`."
msgstr ""
#: ../../content/applications/sales/sales/amazon_connector.rst:5
msgid "Amazon Connector"
msgstr ""
@ -4351,147 +4250,147 @@ msgstr ""
msgid "Odoo has a powerful pricelist feature to support a pricing strategy tailored to your business. A pricelist is a list of prices or price rules that Odoo searches to determine the suggested price. You can set several criteria to use a specific price: periods, min. sold quantity (meet a minimum order quantity and get a price break), etc."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:9
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:10
msgid "As pricelists only suggest prices, they can be overridden by vendors completing sales orders. Choose your pricing strategy from :menuselection:`Sales --> Settings`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:18
msgid "*A single sale price per product :* doesn't let you adapt prices, it use default product price ;"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:19
msgid "*Different prices per customer segment :* you will set several prices per products ;"
msgid "*A single sale price per product:* doesn't let you adapt prices, it use default product price ;"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:20
msgid "*Advanced pricing based on formula :* will let you apply discounts, margins and roundings."
msgid "*Different prices per customer segment:* you will set several prices per products ;"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:23
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:21
msgid "*Advanced pricing based on formula:* will let you apply discounts, margins and roundings."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:24
msgid "Several prices per product"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:25
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:26
msgid "To apply several prices per product, select *Different prices per customer segment* in :menuselection:`Sales --> Settings`. Then open the *Sales* tab in the product detail form. You can settle following strategies."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:30
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:31
msgid "Prices per customer segment"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:32
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:33
msgid "Create pricelists for your customer segments: e.g. registered, premium, etc."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:37
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:38
msgid "The default pricelist applied to any new customer is *Public Pricelist*. To segment your customers, open the customer detail form and change the *Sale Pricelist* in the *Sales & Purchases* tab."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:45
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:46
msgid "Temporary prices"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:47
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:48
msgid "Apply deals for bank holidays, etc. Enter start and end dates dates."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:53
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:54
msgid "Make sure you have default prices set in the pricelist outside of the deals period. Otherwise you might have issues once the period over."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:57
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:58
msgid "Prices per minimum quantity"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:63
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:64
msgid "The prices order does not matter. The system is smart and applies first prices that match the order date and/or the minimal quantities."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:67
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:68
msgid "Discounts, margins, roundings"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:69
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:70
msgid "*Advanced pricing based on formula* allows to set price change rules. Changes can be relative to the product list/catalog price, the product cost price, or to another pricelist. Changes are calculated via discounts or surcharges and can be forced to fit within floor (minimum margin) and ceilings (maximum margins). Prices can be rounded to the nearest cent/dollar or multiple of either (nearest 5 cents, nearest 10 dollars)."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:76
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:77
msgid "Once installed go to :menuselection:`Sales --> Configuration --> Pricelists` (or :menuselection:`Website Admin --> Catalog --> Pricelists` if you use e-Commerce)."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:84
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:85
msgid "Each pricelist item can be associated to either all products, to a product internal category (set of products) or to a specific product. Like in second option, you can set dates and minimum quantities."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:91
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:92
msgid "Once again the system is smart. If a rule is set for a particular item and another one for its category, Odoo will take the rule of the item."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:93
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:94
msgid "Make sure at least one pricelist item covers all your products."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:95
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:96
msgid "There are 3 modes of computation: fix price, discount & formula."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:100
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:101
msgid "Here are different price settings made possible thanks to formulas."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:103
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:104
msgid "Discounts with roundings"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:105
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:106
msgid "e.g. 20% discounts with prices rounded up to 9.99."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:111
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:112
msgid "Costs with markups (retail)"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:113
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:114
msgid "e.g. sale price = 2*cost (100% markup) with $5 of minimal margin."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:119
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:120
msgid "Prices per country"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:120
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:122
msgid "Pricelists can be set by countries group. Any new customer recorded in Odoo gets a default pricelist, i.e. the first one in the list matching the country. In case no country is set for the customer, Odoo takes the first pricelist without any country group."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:123
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:126
msgid "The default pricelist can be replaced when creating a sales order."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:125
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:128
msgid "You can change the pricelists sequence by drag & drop in list view."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:128
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:131
msgid "Compute and show discount % to customers"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:130
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:133
msgid "In case of discount, you can show the public price and the computed discount % on printed sales orders and in your eCommerce catalog. To do so:"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:132
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:136
msgid "Check *Allow discounts on sales order lines* in :menuselection:`Sales --> Configuration --> Settings --> Quotations & Sales --> Discounts`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:133
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:138
msgid "Apply the option in the pricelist setup form."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:140
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:145
msgid ":doc:`currencies`"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:141
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:146
msgid ":doc:`/applications/websites/ecommerce/maximizing_revenue/pricing`"
msgstr ""
@ -4890,7 +4789,7 @@ msgid "With the above product template, there are 15 different t-shirt variants
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:137
msgid "To deactivate a particular product variant, go to :menuselection:`Sales --> Products --> Products` and select the relevant product. Next, click on the :guilabel:`Configure Variants` button, open the relevant product variant attribute value form (in this example, the :guilabel:`White Color` attribute), and then click on :guilabel:`Edit`."
msgid "To deactivate a particular product variant, go to :menuselection:`Sales --> Products --> Products` and select the relevant product. Next, click on the :guilabel:`Configure` button next to the relevant attribute value. Then select the relevant value (in this example, the :guilabel:`White Color` attribute), and then click on :guilabel:`Edit`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:142

26
locale/sources/services.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-01-31 10:25+0000\n"
"POT-Creation-Date: 2023-03-03 11:23+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"
@ -37,15 +37,15 @@ msgstr ""
msgid "Plan onsite interventions from helpdesk tickets"
msgstr ""
#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:4
#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:5
msgid "The integration with the Helpdesk app lets your helpdesk team manage intervention requests directly. Planning field service tasks from tickets speeds up your processes."
msgstr ""
#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:8
#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:9
msgid "Configure the helpdesk team"
msgstr ""
#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:9
#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:11
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`. Select a team and enable *Onsite Interventions*."
msgstr ""
@ -53,7 +53,7 @@ msgstr ""
msgid "Onsite interventions setting in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:16
#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:18
msgid "The helpdesk tickets of the team now display the *Plan Intervention* button. Click on it to create a new task under your field service project."
msgstr ""
@ -69,23 +69,23 @@ msgstr ""
msgid "Create onsite interventions from sales orders"
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:4
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:5
msgid "Allowing your sales team to open onsite interventions creates a seamless experience for your customers. They can receive a quotation they first have to approve before the work even starts."
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:8
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:9
msgid "Configure a product"
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:9
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:11
msgid "Go to :menuselection:`Field Service --> Configuration --> Products` and create or edit a product."
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:11
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:13
msgid "Under the *General Information* tab, select *Service* as *Product Type*."
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:13
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:14
msgid "Under the *Sales* tab, select *Timesheets on tasks* as *Service Invoicing Policy*."
msgstr ""
@ -93,11 +93,11 @@ msgstr ""
msgid "Select *Create a task in an existing project* as *Service Tracking*."
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:17
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:16
msgid "Select your *Project*."
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:19
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:17
msgid "If you use them, select your *Worksheet Template* and then click on *Save*."
msgstr ""
@ -105,7 +105,7 @@ msgstr ""
msgid "Product configuration to create tasks from sales orders in Odoo Field Service"
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:25
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:23
msgid "From the *Sales* app, create a quotation with the product and confirm it. A task is automatically set up under your Field Service project. It is directly accessible from the sales order."
msgstr ""

374
locale/sources/websites.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-01-02 09:09+0000\n"
"POT-Creation-Date: 2023-03-03 11:23+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"
@ -1180,679 +1180,679 @@ msgstr ""
msgid "Keywords"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:40
#: ../../content/applications/websites/website/optimize/seo.rst:41
msgid "In order to write quality content and boost your traffic, Odoo provides a ``<keyword>`` finder. Those keywords are the searches you want to head towards your website. For each keyword, you see how it is used in the content (H1, H2, page title, page description, page content) and what are the related searches in Google. The more keywords are used the better."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:50
#: ../../content/applications/websites/website/optimize/seo.rst:51
msgid "If your website is in multiple languages, you can use the Promote tool for every language of a single page and set specific title, description and search tags."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:55
#: ../../content/applications/websites/website/optimize/seo.rst:56
msgid "Content is King"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:57
#: ../../content/applications/websites/website/optimize/seo.rst:58
msgid "When it comes to SEO, content is usually king. Odoo provides several modules to help you build your website content:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:60
#: ../../content/applications/websites/website/optimize/seo.rst:61
msgid "**Odoo Blogs**: write great contents."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:62
#: ../../content/applications/websites/website/optimize/seo.rst:63
msgid "**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their content is automatically indexed on the web page. Example: `odoo.com/slides/public-channel-1 <https://www.odoo.com/slides/public-channel-1>`_"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:66
#: ../../content/applications/websites/website/optimize/seo.rst:67
msgid "**Odoo Forum**: let your community create contents for you. Example: `odoo.com/forum/1 <https://odoo.com/forum/1>`_ (accounts for 30% of Odoo.com landing pages)"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:70
#: ../../content/applications/websites/website/optimize/seo.rst:71
msgid "**Odoo Mailing List Archive**: publish mailing list archives on your website. Example: `odoo.com/groups/community-59 <https://www.odoo.com/groups/community-59>`_ (1000 pages created per month)"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:76
#: ../../content/applications/websites/website/optimize/seo.rst:77
msgid "The 404 page is a regular page, that you can edit like any other page in Odoo. That way, you can build a great 404 page to redirect to the top content of your website when visitors get lost in invalid URLs."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:81
#: ../../content/applications/websites/website/optimize/seo.rst:82
msgid "Use Social Networks"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:83
#: ../../content/applications/websites/website/optimize/seo.rst:84
msgid "Social media is built for mass sharing. If lots of people share your content on social media, then it's likely more people will link to it, and links are a huge factor for SEO ranking."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:87
#: ../../content/applications/websites/website/optimize/seo.rst:88
msgid "Odoo embeds several tools to share content through social media:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:90
#: ../../content/applications/websites/website/optimize/seo.rst:91
msgid "Social Network"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:92
#: ../../content/applications/websites/website/optimize/seo.rst:93
msgid "Odoo allows to link all your social network accounts in your website footer. All you have to do is to refer all your accounts in your company settings."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:99
#: ../../content/applications/websites/website/optimize/seo.rst:100
msgid "Social Share"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:101
#: ../../content/applications/websites/website/optimize/seo.rst:102
msgid "Drop the building block *Share* on any page you want your visitors to share. By clicking the icon, they are prompted to share the page in their social media wall."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:108
#: ../../content/applications/websites/website/optimize/seo.rst:109
msgid "Most social media use a picture of the picture to decorate the share post. Odoo uses the website logo by default but you can choose any other image of your page in the Promote tool."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:116
#: ../../content/applications/websites/website/optimize/seo.rst:117
msgid "Facebook Page"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:118
#: ../../content/applications/websites/website/optimize/seo.rst:119
msgid "Drop the building block *Facebook Page* to display a widget of your Facebook business page and encourage visitors to follow it. You can display the timeline, the next events and the messages."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:123
#: ../../content/applications/websites/website/optimize/seo.rst:124
msgid "Twitter Scroller"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:125
#: ../../content/applications/websites/website/optimize/seo.rst:126
msgid "Display the Twitter feeds with customer satifaction on your website. This will increase the number of tweets and shares."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:129
#: ../../content/applications/websites/website/optimize/seo.rst:130
msgid "Test Your Website"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:131
#: ../../content/applications/websites/website/optimize/seo.rst:132
msgid "You can compare how your website rank, in terms of SEO, against Odoo using WooRank free services: `woorank.com <https://www.woorank.com>`_"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:136
#: ../../content/applications/websites/website/optimize/seo.rst:137
msgid "URLs Handling"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:138
#: ../../content/applications/websites/website/optimize/seo.rst:139
msgid "This section sheds some light on how Odoo makes URLs SEO-friendly."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:141
#: ../../content/applications/websites/website/optimize/seo.rst:142
msgid "URLs Structure"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:143
#: ../../content/applications/websites/website/optimize/seo.rst:144
msgid "A typical Odoo URL will look like this:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:145
#: ../../content/applications/websites/website/optimize/seo.rst:146
msgid "https://www.mysite.com/fr\\_FR/shop/product/my-great-product-31"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:147
#: ../../content/applications/websites/website/optimize/seo.rst:148
msgid "With the following components:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:149
#: ../../content/applications/websites/website/optimize/seo.rst:150
msgid "**https://** = Protocol"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:151
#: ../../content/applications/websites/website/optimize/seo.rst:152
msgid "**www.mysite.com** = your domain name"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:153
#: ../../content/applications/websites/website/optimize/seo.rst:154
msgid "**/fr\\_FR** = page language. This part of the URL is removed if the visitor browses the main language of the website Thus, the main version of this page is: https://www.mysite.com/shop/product/my-great-product-31"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:158
#: ../../content/applications/websites/website/optimize/seo.rst:159
msgid "**/shop/product** = every module defines its own namespace (/shop is for the catalog of the eCommerce module, /shop/product is for a product page)."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:162
#: ../../content/applications/websites/website/optimize/seo.rst:163
msgid "**my-great-product** = by default, this is the slugified title of the product this page refers to. But you can customize it for SEO purposes. A product named \"Pain carré\" will be slugified to \"pain-carre\". Depending on the namespace, this could be different objects (blog post, page title, forum post, forum comment, product category, etc.)."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:169
#: ../../content/applications/websites/website/optimize/seo.rst:170
msgid "**-31** = the unique ID of the product"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:171
#: ../../content/applications/websites/website/optimize/seo.rst:172
msgid "Note that any dynamic component of an URL can be reduced to its ID. As an example, the following URLs all do a 301 redirect to the above URL:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:174
#: ../../content/applications/websites/website/optimize/seo.rst:175
msgid "https://www.mysite.com/fr\\_FR/shop/product/31 (short version)"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:176
#: ../../content/applications/websites/website/optimize/seo.rst:177
msgid "http://mysite.com/fr\\_FR/shop/product/31 (even shorter version)"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:178
#: ../../content/applications/websites/website/optimize/seo.rst:179
msgid "http://mysite.com/fr\\_FR/shop/product/other-product-name-31 (old product name)"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:181
#: ../../content/applications/websites/website/optimize/seo.rst:182
msgid "Some URLs have several dynamic parts, like this one (a blog category and a post):"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:184
#: ../../content/applications/websites/website/optimize/seo.rst:185
msgid "https://www.odoo.com/blog/company-news-5/post/the-odoo-story-56"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:186
#: ../../content/applications/websites/website/optimize/seo.rst:187
msgid "In the above example:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:188
#: ../../content/applications/websites/website/optimize/seo.rst:189
msgid "*Company News* is the title of the blog"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:190
#: ../../content/applications/websites/website/optimize/seo.rst:191
msgid "*The Odoo Story* is the title of a specific blog post"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:192
#: ../../content/applications/websites/website/optimize/seo.rst:193
msgid "When an Odoo page has a pager, the page number is set directly in the URL (does not have a GET argument). This allows every page to be indexed by search engines. Example:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:196
#: ../../content/applications/websites/website/optimize/seo.rst:197
msgid "https://www.odoo.com/blog/page/3"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:199
#: ../../content/applications/websites/website/optimize/seo.rst:200
msgid "Changes in URLs & Titles"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:201
#: ../../content/applications/websites/website/optimize/seo.rst:202
msgid "When the URL of a page changes (e.g. a more SEO friendly version of your product name), you don't have to worry about updating all links:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:204
#: ../../content/applications/websites/website/optimize/seo.rst:205
msgid "Odoo will automatically update all its links to the new URL."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:206
#: ../../content/applications/websites/website/optimize/seo.rst:207
msgid "If external websites still points to the old URL, a 301 redirect will be done to route visitors to the new address of the page."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:209
#: ../../content/applications/websites/website/optimize/seo.rst:210
msgid "As an example, this URL:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:211
#: ../../content/applications/websites/website/optimize/seo.rst:212
msgid "http://mysite.com/shop/product/old-product-name-31"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:213
#: ../../content/applications/websites/website/optimize/seo.rst:214
msgid "Will automatically redirect to:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:215
#: ../../content/applications/websites/website/optimize/seo.rst:216
msgid "http://mysite.com/shop/product/new-and-better-product-name-31"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:217
#: ../../content/applications/websites/website/optimize/seo.rst:218
msgid "In short, just change the title of a blog post or the name of a product, and the changes will apply automatically everywhere in your website. The old link still functions when used by external websites, via a 301 redirect, maintaining the SEO link juice."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:223
#: ../../content/applications/websites/website/optimize/seo.rst:224
msgid "HTTPS"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:225
#: ../../content/applications/websites/website/optimize/seo.rst:226
msgid "Search engines boost ranking of secure HTTPS/SSL websites. So, by default all Odoo Online instances are fully based on HTTPS. If the visitor accesses your website through a non HTTPS url, it gets a 301 redirect to its HTTPS equivalent."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:231
#: ../../content/applications/websites/website/optimize/seo.rst:232
msgid "Links: Nofollow Strategy"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:233
#: ../../content/applications/websites/website/optimize/seo.rst:234
msgid "The more a page is linked from external and quality websites, the better it is for your SEO."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:236
#: ../../content/applications/websites/website/optimize/seo.rst:237
msgid "Here are Odoo strategies to manage links:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:238
#: ../../content/applications/websites/website/optimize/seo.rst:239
msgid "Every link you add to your website is \"dofollow\", which means that this link will contribute to the SEO Juice for the linked page."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:242
#: ../../content/applications/websites/website/optimize/seo.rst:243
msgid "Every link posted by a contributor (forum post, blog comment, etc.) that links to your own website is \"dofollow\" too."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:245
#: ../../content/applications/websites/website/optimize/seo.rst:246
msgid "But every link posted by a contributor that links to an external website is \"nofollow\". In that way, you do not run the risk of people posting links on your website to third-party websites which have a bad reputation."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:250
#: ../../content/applications/websites/website/optimize/seo.rst:251
msgid "Note that, when using the forum, contributors having a lot of Karma can be trusted. In such case, their links will not have any ``rel=\"nofollow\"`` attribute."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:255
#: ../../content/applications/websites/website/optimize/seo.rst:256
msgid "Multi-Language Support"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:258
#: ../../content/applications/websites/website/optimize/seo.rst:259
msgid "Multi-Language URLs"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:260
#: ../../content/applications/websites/website/optimize/seo.rst:261
msgid "If you run a website in multiple languages, the same content will be available in different URLs, depending on the language used:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:263
#: ../../content/applications/websites/website/optimize/seo.rst:264
msgid "https://www.mywebsite.com/shop/product/my-product-1 (main language, English here)"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:265
#: ../../content/applications/websites/website/optimize/seo.rst:266
msgid "https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1 (French version)"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:267
#: ../../content/applications/websites/website/optimize/seo.rst:268
msgid "In this example, fr\\_FR is the language of the page. You can even have several variations of the same language: pt\\_BR (Portuguese from Brazil) , pt\\_PT (Portuguese from Portugal)."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:272
#: ../../content/applications/websites/website/optimize/seo.rst:273
msgid "Language Annotation"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:274
#: ../../content/applications/websites/website/optimize/seo.rst:275
msgid "To let search engines know that the second URL is the French translation of the first URL, Odoo will add an HTML link element in the header. In the HTML <head> section of the main version, Odoo automatically adds a link element pointing to the translated versions of that webpage;"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:279
#: ../../content/applications/websites/website/optimize/seo.rst:280
msgid "<link rel=\"alternate\" hreflang=\"fr\" href=\"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1\"/>"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:282
#: ../../content/applications/websites/website/optimize/seo.rst:283
msgid "With this approach:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:284
#: ../../content/applications/websites/website/optimize/seo.rst:285
msgid "Search engines will redirect to the right language according to the visitor language."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:287
#: ../../content/applications/websites/website/optimize/seo.rst:288
msgid "You do not get penalized by search engines if your page is not translated yet. Indeed, it's not a duplicated content, but a different version of the same content."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:292
#: ../../content/applications/websites/website/optimize/seo.rst:293
msgid "Language Detection"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:294
#: ../../content/applications/websites/website/optimize/seo.rst:295
msgid "When a visitor lands for the first time on your website (e.g. yourwebsite.com/shop), they may automatically be redirected to a translated version according to their browser language preference (e.g. yourwebsite.com/fr\\_FR/shop)."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:299
#: ../../content/applications/websites/website/optimize/seo.rst:300
msgid "Next time, it keeps a cookie of the current language to avoid any redirection."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:302
#: ../../content/applications/websites/website/optimize/seo.rst:303
msgid "To force a visitor to stick to the default language, you can use the code of the default language in your link, example: yourwebsite.com/en\\_US/shop. This will always land visitors to the English version of the page, without using the browser language preferences."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:309
#: ../../content/applications/websites/website/optimize/seo.rst:310
msgid "Page Speed"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:312
#: ../../content/applications/websites/website/optimize/seo.rst:313
msgid "Introduction"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:314
#: ../../content/applications/websites/website/optimize/seo.rst:315
msgid "The time to load a page is an important criteria for search engines. A faster website not only improves your visitor's experience, but gives you a better page ranking. Some studies have shown that, if you divide the time to load your pages by two (e.g. 2 seconds instead of 4 seconds), the visitor abandonment rate is also divided by two. (25% to 12.5%). One extra second to load a page could `cost $1.6b to Amazon in sales <http://www.fastcompany.com/1825005/how-one-second-could-cost-amazon-16-billion-sales>`__."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:325
#: ../../content/applications/websites/website/optimize/seo.rst:326
msgid "Fortunately, Odoo does all the magic for you. Below, you will find the tricks Odoo uses to speed up your page loading time. You can compare how your website ranks using these two tools:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:329
#: ../../content/applications/websites/website/optimize/seo.rst:330
msgid "`Google Page Speed <https://developers.google.com/speed/pagespeed/insights/>`__"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:331
#: ../../content/applications/websites/website/optimize/seo.rst:332
msgid "`Pingdom Website Speed Test <http://tools.pingdom.com/fpt/>`__"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:334
#: ../../content/applications/websites/website/optimize/seo.rst:335
msgid "Images"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:336
#: ../../content/applications/websites/website/optimize/seo.rst:337
msgid "When you upload new images, Odoo automatically compresses them to reduce their sizes (lossless compression for .PNG and .GIF and lossy compression for .JPG)."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:340
#: ../../content/applications/websites/website/optimize/seo.rst:341
msgid "From the upload button, you have the option to keep the original image unmodified if you prefer to optimize the quality of the image rather than performance."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:348
#: ../../content/applications/websites/website/optimize/seo.rst:349
msgid "Odoo compresses images when they are uploaded to your website, not when requested by the visitor. Thus, it's possible that, if you use a third-party theme, it will provide images that are not compressed efficiently. But all images used in Odoo official themes have been compressed by default."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:354
#: ../../content/applications/websites/website/optimize/seo.rst:355
msgid "When you click on an image, Odoo shows you the Alt and title attributes of the ``<img>`` tag. You can click on it to set your own title and Alt attributes for the image."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:361
#: ../../content/applications/websites/website/optimize/seo.rst:362
msgid "When you click on this link, the following window will appear:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:366
#: ../../content/applications/websites/website/optimize/seo.rst:367
msgid "Odoo's pictograms are implemented using a font (`Font Awesome <https://fortawesome.github.io/Font-Awesome/icons/>`__ in most Odoo themes). Thus, you can use as many pictograms as you want in your page, they will not result in extra requests to load the page."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:375
#: ../../content/applications/websites/website/optimize/seo.rst:376
msgid "Static Resources: CSS"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:377
#: ../../content/applications/websites/website/optimize/seo.rst:378
msgid "All CSS files are pre-processed, concatenated, minified, compressed and cached (server-side and browser-side). The result:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:380
#: ../../content/applications/websites/website/optimize/seo.rst:381
msgid "only one CSS file request is needed to load a page"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:382
#: ../../content/applications/websites/website/optimize/seo.rst:383
msgid "this CSS file is shared and cached amongst pages, so that when the visitor clicks on another page, the browser doesn't have to even load a single CSS resource."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:386
#: ../../content/applications/websites/website/optimize/seo.rst:387
msgid "this CSS file is optimized to be small"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:388
#: ../../content/applications/websites/website/optimize/seo.rst:389
msgid "**Pre-processed:** The CSS framework used by Odoo is Bootstrap. Although a theme might use another framework, most of `Odoo themes <https://www.odoo.com/apps/themes>`__ extend and customize Bootstrap directly. Since Odoo supports Less and Sass, you can modify CSS rules instead of overwriting them through extra CSS lines, resulting in a smaller file."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:395
#: ../../content/applications/websites/website/optimize/seo.rst:396
msgid "**Concatenated:** every module or library you might use in Odoo has its own set of CSS, Less or Sass files (eCommerce, blogs, themes, etc.). Having several CSS files is great for the modularity, but not good for the performance because most browsers can only perform 6 requests in parallel resulting in lots of files loaded in series. The latency time to transfer a file is usually much longer than the actual data transfer time, for small files like .JS and .CSS. Thus, the time to load CSS resources depends more on the number of requests to be done than the actual file size."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:405
#: ../../content/applications/websites/website/optimize/seo.rst:406
msgid "To address this issue, all CSS / Less / Sass files are concatenated into a single .CSS file to send to the browser. So a visitor has **only one .CSS file to load** per page, which is particularly efficient. As the CSS is shared amongst all pages, when the visitor clicks on another page, the browser does not even have to load a new CSS file!"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:412
#: ../../content/applications/websites/website/optimize/seo.rst:413
msgid "**Both files in the <head>**"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:412
#: ../../content/applications/websites/website/optimize/seo.rst:413
msgid "**What the visitor gets (only one file)**"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:414
#: ../../content/applications/websites/website/optimize/seo.rst:415
msgid "/\\* From bootstrap.css \\*/"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:414
#: ../../content/applications/websites/website/optimize/seo.rst:415
#: ../../content/applications/websites/website/optimize/seo.rst:421
#: ../../content/applications/websites/website/optimize/seo.rst:447
#: ../../content/applications/websites/website/optimize/seo.rst:416
#: ../../content/applications/websites/website/optimize/seo.rst:422
#: ../../content/applications/websites/website/optimize/seo.rst:448
msgid ".text-muted {"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:415
#: ../../content/applications/websites/website/optimize/seo.rst:422
#: ../../content/applications/websites/website/optimize/seo.rst:448
#: ../../content/applications/websites/website/optimize/seo.rst:416
#: ../../content/applications/websites/website/optimize/seo.rst:423
#: ../../content/applications/websites/website/optimize/seo.rst:449
msgid "color: #666;"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:416
#: ../../content/applications/websites/website/optimize/seo.rst:417
msgid "color: #777;"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:416
#: ../../content/applications/websites/website/optimize/seo.rst:417
msgid "background: yellow"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:417
#: ../../content/applications/websites/website/optimize/seo.rst:418
msgid "background: yellow;"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:417
#: ../../content/applications/websites/website/optimize/seo.rst:418
#: ../../content/applications/websites/website/optimize/seo.rst:423
#: ../../content/applications/websites/website/optimize/seo.rst:449
#: ../../content/applications/websites/website/optimize/seo.rst:419
#: ../../content/applications/websites/website/optimize/seo.rst:424
#: ../../content/applications/websites/website/optimize/seo.rst:450
msgid "}"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:420
#: ../../content/applications/websites/website/optimize/seo.rst:421
msgid "/\\* From my-theme.css \\*/"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:426
#: ../../content/applications/websites/website/optimize/seo.rst:427
msgid "The CSS sent by Odoo includes all CSS / Less / Sass of all pages / modules. By doing this, additional page views from the same visitor will not have to load CSS files at all. But some modules might include huge CSS/Javascript resources that you do not want to prefetch at the first page because they are too big. In this case, Odoo splits this resource into a second bundle that is loaded only when the page using it is requested. An example of this is the backend that is only loaded when the visitor logs in and accesses the backend (/web)."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:436
#: ../../content/applications/websites/website/optimize/seo.rst:437
msgid "If the CSS file is very big, Odoo will split it into two smaller files to avoid the 4095 selectors limit per sheet of Internet Explorer. But most themes fit below this limit."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:440
#: ../../content/applications/websites/website/optimize/seo.rst:441
msgid "**Minified:** After being pre-processed and concatenated, the resulting CSS is minified to reduce its size."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:444
#: ../../content/applications/websites/website/optimize/seo.rst:445
msgid "**Before minification**"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:444
#: ../../content/applications/websites/website/optimize/seo.rst:445
msgid "**After minification**"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:446
#: ../../content/applications/websites/website/optimize/seo.rst:447
msgid "/\\* some comments \\*/"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:446
#: ../../content/applications/websites/website/optimize/seo.rst:447
msgid ".text-muted {color: #666}"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:452
#: ../../content/applications/websites/website/optimize/seo.rst:453
msgid "The final result is then compressed, before being delivered to the browser."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:455
#: ../../content/applications/websites/website/optimize/seo.rst:456
msgid "Then, a cached version is stored server-side (so we do not have to pre-process, concatenate, minify at every request) and browser-side (so the same visitor will load the CSS only once for all pages they visit)."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:461
#: ../../content/applications/websites/website/optimize/seo.rst:462
msgid "Static Resources: Javascript"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:463
#: ../../content/applications/websites/website/optimize/seo.rst:464
msgid "As with CSS resources, Javascript resources are also concatenated, minified, compressed and cached (server-side and browser-side)."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:466
#: ../../content/applications/websites/website/optimize/seo.rst:467
msgid "Odoo creates three Javascript bundles:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:468
#: ../../content/applications/websites/website/optimize/seo.rst:469
msgid "One for all pages of the website (including code for parallax effects, form validation, etc.)"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:471
#: ../../content/applications/websites/website/optimize/seo.rst:472
msgid "One for common Javascript code shared among frontend and backend (Bootstrap)"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:474
#: ../../content/applications/websites/website/optimize/seo.rst:475
msgid "One for backend specific Javascript code (Odoo Web Client interface for your employees using Odoo)"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:477
#: ../../content/applications/websites/website/optimize/seo.rst:478
msgid "Most visitors of your website will only need the first two bundles, resulting in a maximum of two Javascript files to load to render one page. As these files are shared across all pages, further clicks by the same visitor will not load any other Javascript resource."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:483
#: ../../content/applications/websites/website/optimize/seo.rst:484
msgid "If you work on :ref:`developer mode <developer-mode>`, the CSS and Javascript are neither concatenated, nor minified. Thus, it's much slower. But it allows you to easily debug with the Chrome debugger as CSS and Javascript resources are not transformed from their original versions."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:488
#: ../../content/applications/websites/website/optimize/seo.rst:489
msgid "CDN"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:490
#: ../../content/applications/websites/website/optimize/seo.rst:491
msgid "If you activate the CDN feature in Odoo, static resources (Javascript, CSS, images) are loaded from a Content Delivery Network. Using a Content Delivery Network has three advantages:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:494
#: ../../content/applications/websites/website/optimize/seo.rst:495
msgid "Load resources from a nearby server (most CDN have servers in main countries around the globe)"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:497
#: ../../content/applications/websites/website/optimize/seo.rst:498
msgid "Cache resources efficiently (no computation resources usage on your own server)"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:500
#: ../../content/applications/websites/website/optimize/seo.rst:501
msgid "Split the resource loading on different services allowing to load more resources in parallel (since the Chrome limit of 6 parallel requests is by domain)"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:504
#: ../../content/applications/websites/website/optimize/seo.rst:505
msgid "You can configure your CDN options from the **Website Admin** app, using the Configuration menu. Here is an example of configuration you can use:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:511
#: ../../content/applications/websites/website/optimize/seo.rst:512
msgid "HTML Pages"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:513
#: ../../content/applications/websites/website/optimize/seo.rst:514
msgid "The HTML pages can be compressed, but this is usually handled by your web server (NGINX or Apache)."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:516
#: ../../content/applications/websites/website/optimize/seo.rst:517
msgid "The Odoo Website builder has been optimized to guarantee clean and short HTML code. Building blocks have been developed to produce clean HTML code, usually using Bootstrap and the HTML editor."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:520
#: ../../content/applications/websites/website/optimize/seo.rst:521
msgid "As an example, if you use the color picker to change the color of a paragraph to the primary color of your website, Odoo will produce the following code:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:524
#: ../../content/applications/websites/website/optimize/seo.rst:525
msgid "``<p class=\"text-primary\">My Text</p>``"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:526
#: ../../content/applications/websites/website/optimize/seo.rst:527
msgid "Whereas most HTML editors (such as CKEditor) will produce the following code:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:529
#: ../../content/applications/websites/website/optimize/seo.rst:530
msgid "``<p style=\"color: #AB0201\">My Text</p>``"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:532
#: ../../content/applications/websites/website/optimize/seo.rst:533
msgid "Responsive Design"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:534
#: ../../content/applications/websites/website/optimize/seo.rst:535
msgid "Websites that are not mobile-friendly are negatively impacted in search engine rankings. All Odoo themes rely on Bootstrap to render efficiently according to the device: desktop, tablet or mobile."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:541
#: ../../content/applications/websites/website/optimize/seo.rst:542
msgid "As all Odoo modules share the same technology, absolutely all pages in your website are mobile friendly."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:545
#: ../../content/applications/websites/website/optimize/seo.rst:546
msgid "Browser Caching"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:547
#: ../../content/applications/websites/website/optimize/seo.rst:548
msgid "Javascript, images and CSS resources have an URL that changes dynamically when their content change. As an example, all CSS files are loaded through this URL: `localhost:8069/web/content/457-0da1d9d/web.assets\\_common.0.css <http://localhost:8069/web/content/457-0da1d9d/web.assets_common.0.css>`__. The ``457-0da1d9d`` part of this URL will change if you modify the CSS of your website."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:554
#: ../../content/applications/websites/website/optimize/seo.rst:555
msgid "This allows Odoo to set a very long cache delay (XXX) on these resources: XXX secs, while being updated instantly if you update the resource."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:559
#: ../../content/applications/websites/website/optimize/seo.rst:560
msgid "Scalability"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:561
#: ../../content/applications/websites/website/optimize/seo.rst:562
msgid "In addition to being fast, Odoo is also more scalable than traditional CMS and eCommerce (Drupal, Wordpress, Magento, Prestashop)."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:564
#: ../../content/applications/websites/website/optimize/seo.rst:565
msgid "Here is the slide that summarizes the scalability of Odoo Website & eCommerce."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:570
#: ../../content/applications/websites/website/optimize/seo.rst:571
msgid "Search Engines Files"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:573
#: ../../content/applications/websites/website/optimize/seo.rst:574
msgid "Sitemap"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:575
#: ../../content/applications/websites/website/optimize/seo.rst:576
msgid "The sitemap points out pages to index to search engine robots. Odoo generates a ``/sitemap.xml`` file automatically for you. For performance reasons, this file is cached and updated every 12 hours."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:579
#: ../../content/applications/websites/website/optimize/seo.rst:580
msgid "By default, all URLs will be in a single ``/sitemap.xml`` file, but if you have a lot of pages, Odoo will automatically create a Sitemap Index file, respecting the `sitemaps.org protocol <http://www.sitemaps.org/protocol.html>`__ grouping sitemap URL's in 45000 chunks per file."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:585
#: ../../content/applications/websites/website/optimize/seo.rst:586
msgid "Every sitemap entry has 4 attributes that are computed automatically:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:587
#: ../../content/applications/websites/website/optimize/seo.rst:588
msgid "``<loc>`` : the URL of a page"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:589
#: ../../content/applications/websites/website/optimize/seo.rst:590
msgid "``<lastmod>`` : last modification date of the resource, computed automatically based on related object. For a page related to a product, this could be the last modification date of the product or the page."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:594
#: ../../content/applications/websites/website/optimize/seo.rst:595
msgid "``<priority>`` : modules may implement their own priority algorithm based on their content (example: a forum might assign a priority based on the number of votes on a specific post). The priority of a static page is defined by it's priority field, which is normalized (16 is the default)."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:601
#: ../../content/applications/websites/website/optimize/seo.rst:602
msgid "Structured Data Markup"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:603
#: ../../content/applications/websites/website/optimize/seo.rst:604
msgid "Structured Data Markup is used to generate Rich Snippets in search engine results. It is a way for website owners to send structured data to search engine robots; helping them understand your content and create well-presented search results."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:608
#: ../../content/applications/websites/website/optimize/seo.rst:609
msgid "Google supports a number of rich snippets for content types, including: Reviews, People, Products, Businesses, Events and Organizations."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:611
#: ../../content/applications/websites/website/optimize/seo.rst:612
msgid "Odoo implements micro data as defined in the `schema.org <http://schema.org>`__ specification for events, eCommerce products, forum posts and contact addresses. This allows your product pages to be displayed in Google using extra information like the price and rating of a product:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:621
#: ../../content/applications/websites/website/optimize/seo.rst:622
msgid "robots.txt"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:623
#: ../../content/applications/websites/website/optimize/seo.rst:624
msgid "When indexing your website, search engines take a first look at the general indexing rules of the ``/robots.txt`` file (allowed robots, sitemap path, etc.). Odoo automatically creates it. Its content is:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:627
#: ../../content/applications/websites/website/optimize/seo.rst:628
msgid "User-agent: \\* Sitemap: https://www.odoo.com/sitemap.xml"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:630
#: ../../content/applications/websites/website/optimize/seo.rst:631
msgid "It means that all robots are allowed to index your website and there is no other indexing rule than specified in the sitemap to be found at following address."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:634
#: ../../content/applications/websites/website/optimize/seo.rst:635
msgid "You can customize the file *robots* in :ref:`developer mode <developer-mode>` from *Settings --> Technical --> User Interface --> Views* (exclude robots, exclude some pages, redirect to a custom Sitemap). Make the Model Data of the view *Non Updatable* to not reset the file after system upgrades."
msgstr ""
@ -2181,11 +2181,11 @@ msgid "To manage specific prices by websites, you can activate *Multiple Sales P
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:266
msgid "Then, go to :menuselection:`Website --> Products --> Pricelists` to create additional pricelists. See :doc:`../../ecommerce/maximizing_revenue/pricing`."
msgid "Then, go to :menuselection:`Website --> Products --> Pricelists` to create additional pricelists. You can also choose to have a pricelist available *only* on a specific website."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:269
msgid "If you need help. Select a website to make a pricelist only available on this website."
#: ../../content/applications/websites/website/publish/multi_website.rst:270
msgid ":doc:`../../ecommerce/maximizing_revenue/pricing`."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:275
@ -2273,7 +2273,7 @@ msgid "If you can't/don't want to locate the geoip database in ``/usr/share/GeoI
msgstr ""
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:36
msgid ":doc:`CLI documentation </developer/cli>`."
msgid ":doc:`CLI documentation </developer/reference/cli>`."
msgstr ""
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:39
@ -2284,39 +2284,39 @@ msgstr ""
msgid "How To Test GeoIP Geolocation In Your Odoo Website"
msgstr ""
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:45
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:46
msgid "Go to your website. Open the web page that you want to test ``GeoIP``."
msgstr ""
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:46
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:47
msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`."
msgstr ""
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:47
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:48
msgid "Add the following piece of XML in the page :"
msgstr ""
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:53
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:54
msgid "You should end up with a dictionary indicating the location of the IP address."
msgstr ""
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:59
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:60
msgid "If the curly braces are empty ``{}``, it can be for any of the following reasons :"
msgstr ""
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:61
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:62
msgid "The browsing IP address is the localhost (``127.0.0.1``) or a local area network one (``192.168.*.*``)"
msgstr ""
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:62
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:64
msgid "If a reversed proxy is used, make sure to configure it correctly. See :option:`proxy mode <odoo-bin --proxy-mode>`"
msgstr ""
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:63
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:66
msgid "``geoip2`` is not installed or the GeoIP database file wasn't found"
msgstr ""
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:64
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:67
msgid "The GeoIP database was unable to resolve the given IP address"
msgstr ""