diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index 04d6d0156..82a4c3f13 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-08-18 08:00+0000\n" +"POT-Creation-Date: 2025-09-29 07:37+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -2902,18 +2902,14 @@ msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:181 #: ../../content/administration/odoo_sh/getting_started/settings.rst:186 #: ../../content/administration/supported_versions.rst:35 -#: ../../content/administration/supported_versions.rst:41 -#: ../../content/administration/supported_versions.rst:47 -#: ../../content/administration/supported_versions.rst:53 +#: ../../content/administration/supported_versions.rst:36 +#: ../../content/administration/supported_versions.rst:37 #: ../../content/administration/supported_versions.rst:59 #: ../../content/administration/supported_versions.rst:60 #: ../../content/administration/supported_versions.rst:61 -#: ../../content/administration/supported_versions.rst:77 -#: ../../content/administration/supported_versions.rst:78 -#: ../../content/administration/supported_versions.rst:79 -#: ../../content/administration/supported_versions.rst:83 -#: ../../content/administration/supported_versions.rst:84 -#: ../../content/administration/supported_versions.rst:85 +#: ../../content/administration/supported_versions.rst:65 +#: ../../content/administration/supported_versions.rst:66 +#: ../../content/administration/supported_versions.rst:67 msgid "|green|" msgstr "" @@ -4984,50 +4980,64 @@ msgid "End of support" msgstr "" #: ../../content/administration/supported_versions.rst:34 +msgid "**Odoo 19.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:38 +#: ../../content/administration/supported_versions.rst:75 +msgid "September 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:39 +msgid "September 2028 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:40 msgid "Odoo SaaS 18.4" msgstr "" -#: ../../content/administration/supported_versions.rst:36 -#: ../../content/administration/supported_versions.rst:37 +#: ../../content/administration/supported_versions.rst:41 +#: ../../content/administration/supported_versions.rst:47 +#: ../../content/administration/supported_versions.rst:53 +#: ../../content/administration/supported_versions.rst:71 +#: ../../content/administration/supported_versions.rst:72 +#: ../../content/administration/supported_versions.rst:73 +#: ../../content/administration/supported_versions.rst:77 +#: ../../content/administration/supported_versions.rst:78 +#: ../../content/administration/supported_versions.rst:79 +#: ../../content/administration/supported_versions.rst:83 +#: ../../content/administration/supported_versions.rst:84 +#: ../../content/administration/supported_versions.rst:85 +msgid "|red|" +msgstr "" + #: ../../content/administration/supported_versions.rst:42 #: ../../content/administration/supported_versions.rst:43 #: ../../content/administration/supported_versions.rst:48 #: ../../content/administration/supported_versions.rst:49 #: ../../content/administration/supported_versions.rst:54 #: ../../content/administration/supported_versions.rst:55 -#: ../../content/administration/supported_versions.rst:66 -#: ../../content/administration/supported_versions.rst:67 -#: ../../content/administration/supported_versions.rst:72 -#: ../../content/administration/supported_versions.rst:73 msgid "N/A" msgstr "" -#: ../../content/administration/supported_versions.rst:38 +#: ../../content/administration/supported_versions.rst:44 msgid "July 2025" msgstr "" -#: ../../content/administration/supported_versions.rst:40 +#: ../../content/administration/supported_versions.rst:46 msgid "Odoo SaaS 18.3" msgstr "" -#: ../../content/administration/supported_versions.rst:44 +#: ../../content/administration/supported_versions.rst:50 msgid "May 2025" msgstr "" -#: ../../content/administration/supported_versions.rst:46 +#: ../../content/administration/supported_versions.rst:52 msgid "Odoo SaaS 18.2" msgstr "" -#: ../../content/administration/supported_versions.rst:50 -msgid "March 2025" -msgstr "" - -#: ../../content/administration/supported_versions.rst:52 -msgid "Odoo SaaS 18.1" -msgstr "" - #: ../../content/administration/supported_versions.rst:56 -msgid "January 2025" +msgid "March 2025" msgstr "" #: ../../content/administration/supported_versions.rst:58 @@ -5035,104 +5045,71 @@ msgid "**Odoo 18.0**" msgstr "" #: ../../content/administration/supported_versions.rst:62 -#: ../../content/administration/supported_versions.rst:69 -#: ../../content/administration/supported_versions.rst:75 -#: ../../content/administration/supported_versions.rst:93 +#: ../../content/administration/supported_versions.rst:81 msgid "October 2024" msgstr "" #: ../../content/administration/supported_versions.rst:63 -msgid "October 2027 (planned)" +msgid "September 2027 (planned)" msgstr "" #: ../../content/administration/supported_versions.rst:64 -msgid "Odoo SaaS 17.4" -msgstr "" - -#: ../../content/administration/supported_versions.rst:65 -#: ../../content/administration/supported_versions.rst:71 -#: ../../content/administration/supported_versions.rst:89 -#: ../../content/administration/supported_versions.rst:90 -#: ../../content/administration/supported_versions.rst:91 -#: ../../content/administration/supported_versions.rst:95 -#: ../../content/administration/supported_versions.rst:96 -#: ../../content/administration/supported_versions.rst:97 -msgid "|red|" -msgstr "" - -#: ../../content/administration/supported_versions.rst:68 -msgid "July 2024" -msgstr "" - -#: ../../content/administration/supported_versions.rst:70 -msgid "Odoo SaaS 17.2" -msgstr "" - -#: ../../content/administration/supported_versions.rst:74 -msgid "April 2024" -msgstr "" - -#: ../../content/administration/supported_versions.rst:76 msgid "**Odoo 17.0**" msgstr "" -#: ../../content/administration/supported_versions.rst:80 +#: ../../content/administration/supported_versions.rst:68 msgid "November 2023" msgstr "" -#: ../../content/administration/supported_versions.rst:81 -msgid "October 2026 (planned)" +#: ../../content/administration/supported_versions.rst:69 +msgid "September 2026 (planned)" msgstr "" -#: ../../content/administration/supported_versions.rst:82 +#: ../../content/administration/supported_versions.rst:70 msgid "**Odoo 16.0**" msgstr "" -#: ../../content/administration/supported_versions.rst:86 +#: ../../content/administration/supported_versions.rst:74 msgid "October 2022" msgstr "" -#: ../../content/administration/supported_versions.rst:87 -msgid "October 2025 (planned)" -msgstr "" - -#: ../../content/administration/supported_versions.rst:88 +#: ../../content/administration/supported_versions.rst:76 msgid "**Odoo 15.0**" msgstr "" -#: ../../content/administration/supported_versions.rst:92 +#: ../../content/administration/supported_versions.rst:80 msgid "October 2021" msgstr "" -#: ../../content/administration/supported_versions.rst:94 +#: ../../content/administration/supported_versions.rst:82 msgid "Older versions" msgstr "" -#: ../../content/administration/supported_versions.rst:98 +#: ../../content/administration/supported_versions.rst:86 msgid "Before 2021" msgstr "" -#: ../../content/administration/supported_versions.rst:99 +#: ../../content/administration/supported_versions.rst:87 msgid "Before 2024" msgstr "" -#: ../../content/administration/supported_versions.rst:101 +#: ../../content/administration/supported_versions.rst:89 msgid "Legend" msgstr "" -#: ../../content/administration/supported_versions.rst:103 +#: ../../content/administration/supported_versions.rst:91 msgid "|green| Supported version" msgstr "" -#: ../../content/administration/supported_versions.rst:105 +#: ../../content/administration/supported_versions.rst:93 msgid "|red| End-of-support" msgstr "" -#: ../../content/administration/supported_versions.rst:107 +#: ../../content/administration/supported_versions.rst:95 msgid "N/A Never released for this platform" msgstr "" -#: ../../content/administration/supported_versions.rst:110 +#: ../../content/administration/supported_versions.rst:98 msgid "Even though we don't support older versions, you can always `upgrade from any version `_." msgstr "" diff --git a/locale/sources/finance.pot b/locale/sources/finance.pot index ddce0296c..1e7458679 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-08-18 08:00+0000\n" +"POT-Creation-Date: 2025-09-29 07:37+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1377,7 +1377,7 @@ msgid "Thanks to the bank :doc:`reconciliation models `, msgstr "" #: ../../content/applications/finance/accounting/bank/reconciliation.rst:15 -msgid "`Odoo Tutorials: Bank reconciliation `_" +msgid "`Odoo Tutorials: Bank reconciliation `_" msgstr "" #: ../../content/applications/finance/accounting/bank/reconciliation.rst:17 @@ -2931,59 +2931,43 @@ msgstr "" msgid ":doc:`../../fiscal_localizations`" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:68 -msgid "National e-invoicing format" -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:70 -msgid "Depending on your company's country (e.g., :doc:`Italy <../../fiscal_localizations/italy>`, :doc:`Spain <../../fiscal_localizations/spain>`, :doc:`Mexico <../../fiscal_localizations/mexico>`, etc.), it may be required to issue e-invoicing documents in a specific format for all invoices. In this case, define a default e-invoicing format for the sales journal." -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:75 -msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, open the sales journal, go to the :guilabel:`Advanced Settings` tab, and enable the formats needed for this journal." -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:81 -msgid "Customer-specific e-invoicing format" -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:83 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:65 msgid "By default, the format available in the :ref:`send window ` depends on the customer's country." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:86 -msgid "To define a specific e-invoicing format for a customer, go to :menuselection:`Accounting --> Customers --> Customers`, open the customer form, go to the :guilabel:`Accounting` tab, and select the appropriate :guilabel:`Format` in the :guilabel:`Electronic invoicing` section." +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:68 +msgid "To define a specific e-invoicing format for a customer, go to :menuselection:`Accounting --> Customers --> Customers`, access the customer form, go to the :guilabel:`Accounting` tab, and select the appropriate :guilabel:`Format` in the :guilabel:`Customer invoices` section." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:93 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:75 msgid "E-invoice generation" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:95 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:77 msgid "From a confirmed invoice, click :guilabel:`Send & Print`. In the :guilabel:`Send` window, enable the relevant e-invoicing format option (e.g., :guilabel:`BIS Billing 3.0`), then click :guilabel:`Send & Print` to generate and attach the corresponding e-invoicing XML file." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:102 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:84 msgid "Peppol" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:104 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:86 msgid "The `Peppol `_ network ensures the exchange of documents and information between companies and governmental authorities. It is primarily used for electronic invoicing, and its access points (connectors to the Peppol network) allow companies to send electronic documents such as customer invoices and credit notes and receive documents like vendor bills and refunds." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:109 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:91 msgid "In this case, Odoo acts as both an **access point** and an :abbr:`SMP (Service Metadata Publisher)` and enables electronic invoicing transactions without the need to send invoices or bills by email or post." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:114 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:96 msgid "Make sure to :ref:`install ` the :guilabel:`Peppol` module (`account_peppol`)." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:115 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:97 msgid "Peppol registration is **free** and available in Odoo Community." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:116 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:98 msgid "Supported formats for sending documents include **BIS Billing 3.0, XRechnung CIUS, and NLCIUS**." msgstr "" @@ -2995,133 +2979,51 @@ msgstr "" msgid "Andorra, Albania, Austria, Bosnia and Herzegovina, Belgium, Bulgaria, Switzerland, Cyprus, Czech Republic, Germany, Denmark, Estonia, Spain, Finland, France, United Kingdom, Greece, Croatia, Hungary, Ireland, Iceland, Italy, Liechtenstein, Lithuania, Luxembourg, Latvia, Monaco, Montenegro, North Macedonia, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Sweden, Slovenia, Slovakia, San Marino, Turkey, Holy See (Vatican City State)" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:128 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:110 msgid "Registration" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:130 -msgid "To register to Peppol, go to :menuselection:`Accounting --> Configuration --> Settings` and scroll to the :guilabel:`PEPPOL Electronic Document Invoicing` section." +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:112 +msgid "To register on Peppol, go to :menuselection:`Accounting --> Configuration --> Settings`, scroll to the :guilabel:`PEPPOL Electronic Document Invoicing` section, and fill in the following information:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:133 -msgid "By default, Peppol is set to demo mode in Odoo. :ref:`Demo ` mode simulates Peppol transactions without affecting real data, while :ref:`production ` mode is used in production environments." -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:141 -msgid "Demo mode" -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:143 -msgid "Registering in demo mode allows for a complete simulation of the Peppol workflow in Odoo, including invoice sending and receiving and bill receiving. However, no communication with the Peppol network occurs, so actions like partner verification are not performed." -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:147 -msgid "The following fields in the :guilabel:`PEPPOL Electronic Document Invoicing` section are usually prefilled with demo data. Update or complete them as needed:" -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:150 -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:196 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:116 msgid ":guilabel:`Peppol EAS`: Peppol Electronic Address Scheme, which usually depends on the company's country. This field is often prefilled with your country's most commonly used EAS code. For example, the preferred EAS code for most companies in Belgium is `0208`." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:153 -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:199 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:119 msgid ":guilabel:`Peppol Endpoint`: usually a Company Registry number or a VAT number" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:154 -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:200 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:120 msgid ":guilabel:`Mobile Number`, including the country code (e.g., `+32` in Belgium)" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:155 -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:201 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:121 msgid ":guilabel:`Primary contact email`" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:157 -msgid "To set the demo mode, click :guilabel:`Validate registration (Demo)`. The :guilabel:`Application status` is then :guilabel:`Active (Demo)`." -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:161 -#: ../../content/applications/finance/payment_providers.rst:208 -msgid "Test mode" -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:163 -msgid "For **advanced users only**, running tests on Peppol's test network is possible using the test mode. The server allows users to register on Peppol and to send/receive test invoices with other participants. To do so, follow these steps:" -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:167 -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:187 -msgid "Deregister from the demo mode: Go to the :guilabel:`PEPPOL Electronic Document Invoicing` section in the :guilabel:`Settings` and click :guilabel:`Deregister from Peppol`." -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:169 -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:189 -msgid "Enable :ref:`developer mode `, open the Settings app, then go to :menuselection:`Settings --> Technical --> System Parameters` and search for :guilabel:`account_peppol.edi.mode`." -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:172 -msgid "Open the parameter and change the :guilabel:`Value` to `test`." -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:173 -msgid "Go back to the :guilabel:`PEPPOL Electronic Document Invoicing` section in the :guilabel:`Settings` and click :guilabel:`Validate registration (Test)`." -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:175 -msgid "Update the :guilabel:`Mobile Number` and click :guilabel:`Verify mobile number`." -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:176 -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:220 -msgid "A text message containing a code is sent to the mobile number provided to finalize the verification process." -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:178 -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:222 -msgid "Enter the code and click :guilabel:`Confirm`." -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:183 -#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:132 -msgid "Production mode" -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:185 -msgid "To switch from the demo mode to the production mode, follow these steps:" -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:192 -msgid "Open the parameter and change the :guilabel:`Value` to `prod`." -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:193 -msgid "Go back to the :guilabel:`Peppol Electronic Document Invoicing` section in the :guilabel:`Settings` and fill in the following information:" -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:202 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:122 msgid ":guilabel:`Migration key`: If you are migrating from another access point, copy the key from the previous provider." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:205 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:125 msgid "Click :guilabel:`Validate registration`." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:208 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:128 msgid "`Peppol EAS - European Commision `_" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:209 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:129 msgid "`Peppol endpoint - OpenPeppol eDEC Code Lists `_ (open the \"Participant Identifier Schemes\" as HTML page)" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:212 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:132 msgid "To request and receive a verification code, follow these steps:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:214 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:134 msgid "Click :guilabel:`Verify phone number` in the :guilabel:`PEPPOL Electronic Document Invoicing` section." msgstr "" @@ -3129,11 +3031,15 @@ msgstr "" msgid "phone validation request verification" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:223 -msgid "The registration is then pending activation." +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:140 +msgid "A text message containing a code is sent to the mobile number provided to finalize the verification process." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:224 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:142 +msgid "Enter the code and click :guilabel:`Confirm`. The registration is then pending activation." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:143 msgid "Select another purchase journal in the :guilabel:`Incoming Invoices Journal` field if necessary." msgstr "" @@ -3141,7 +3047,7 @@ msgstr "" msgid "Pending application" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:229 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:148 msgid "The registration should be automatically activated, and the :guilabel:`Application status` should be updated within a day." msgstr "" @@ -3149,87 +3055,103 @@ msgstr "" msgid "active application" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:235 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:154 msgid "All invoices and vendor bills can then be sent directly using Peppol." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:238 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:157 +msgid "To update the :guilabel:`Primary contact email`, modify it and click :guilabel:`Update contact details`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:159 +msgid "If you are using an access point from a previous provider, make sure to deregister from it first, then register with your new access point, unless it's Hermes (BOSA). If using Hermes (BOSA), no action is needed; the migration is handled automatically." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:164 msgid "To manually trigger the scheduled action used to check the Peppol registration status, enable :ref:`developer mode `, open the Settings app, go to :menuselection:`Settings --> Technical --> Scheduled actions`, and search for :guilabel:`Peppol: update participant status`. Open the scheduled action, then click :guilabel:`Run Manually`." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:246 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:168 +msgid "To try Peppol without sending real data, use the demo mode by setting the :guilabel:`account_peppol.edi.mode` system parameter to `demo`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:170 +msgid "For advanced testing on Peppol's dedicated test network, use the test mode by setting the :guilabel:`account_peppol.edi.mode` system parameter to `test`. This option is intended for experienced users only." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:177 msgid "Contact verification" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:248 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:179 msgid "Before sending an invoice to a contact using Peppol, make sure the contact is registered as a Peppol participant. To do so, follow these steps:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:251 -msgid "Go to :menuselection:`Accounting --> Customers --> Customers` and open the customer's form." +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:182 +msgid "Go to :menuselection:`Accounting --> Customers --> Customers` and access the customer's form." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:252 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:183 msgid "In the :guilabel:`Accounting tab`, check the following information in the :guilabel:`Electronic Invoicing` section:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:255 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:186 msgid ":guilabel:`Format`: :guilabel:`BIS Billing 3.0`, :guilabel:`XRechnung CIUS`, or :guilabel:`NLCIUS`." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:257 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:188 msgid ":guilabel:`Peppol e-address (EAS)`: Select the relevant EAS code in the dropdown list." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:258 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:189 msgid ":guilabel:`Peppol Endpoint`: Enter the customer's endpoint identifier." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:260 -msgid "Click :guilabel:`Verify`. If the contact is found on the Peppol network, its :guilabel:`Peppol endpoint validity` is marked as :guilabel:`Valid`." +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:191 +msgid "Click :guilabel:`Verify`. Its :guilabel:`Peppol endpoint validity` is marked as :guilabel:`Valid` if the contact is found on the Peppol network." msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:0 msgid "verify contact registration" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:267 -msgid "While Odoo prefills both the EAS code and the endpoint number based on the information available for a contact, it is recommended to verify these details directly with the contact." +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:198 +msgid "While Odoo prefills both the EAS code and the endpoint number based on the information available for a contact, verifying these details with the contact is recommended." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:273 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:204 msgid "Send invoices" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:275 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:206 msgid "To set Peppol as a default format for sending invoices, go to :menuselection:`Accounting --> Configuration --> Settings`. In the :guilabel:`Customer Invoices` section, enable the :guilabel:`Peppol format` option and :guilabel:`Save`." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:279 -msgid "Posted invoices sent via Peppol are marked as :guilabel:`Ready to send` in the invoice's :guilabel:`Peppol status` field." +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:210 +msgid "Posted invoices to be sent via Peppol are marked as :guilabel:`Ready to send` in the invoice's :guilabel:`Peppol status` field." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:283 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:214 msgid "All invoices that are ready to be sent via Peppol can be viewed in the following ways:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:285 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:216 msgid "In the :guilabel:`Invoices` list view, use the :icon:`oi-settings-adjust` (:guilabel:`adjust settings`) button to add the :guilabel:`Peppol status` column or apply the :guilabel:`Peppol Ready` filter in the search bar." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:288 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:219 msgid "In the Accounting dashboard, click :guilabel:`Peppol ready invoices` on the relevant sales journal." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:291 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:222 msgid "To send the invoice to the customer via Peppol, click :guilabel:`Send & Print` on the confirmed invoice form. In the :guilabel:`Send` window, enable both the country-specific format (e.g., :guilabel:`BIS Billing 3.0`) and :guilabel:`Send via PEPPOL` options, then click :guilabel:`Send & Print`." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:297 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:228 msgid ":ref:`Multiple invoices ` can also be sent in batches via Peppol." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:299 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:230 msgid "Once the invoices are sent via Peppol, their :guilabel:`Peppol status` is changed to :guilabel:`Processing`." msgstr "" @@ -3237,11 +3159,11 @@ msgstr "" msgid "Peppol message status" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:305 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:236 msgid "The status is updated to :guilabel:`Done` once the invoices have been successfully delivered to the contact's access point." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:309 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:240 msgid "To manually trigger the scheduled action used to check the invoices' status, go to the Accounting dashboard and click :guilabel:`Fetch Peppol invoice status` on the corresponding sales journal." msgstr "" @@ -3249,15 +3171,15 @@ msgstr "" msgid "Fetch invoice Peppol status" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:319 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:250 msgid "Receive vendor bills" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:321 -msgid "New documents received via Peppol are checked daily. Any received documents are automatically imported, and corresponding vendor bills are created as drafts, appearing in the vendor bills list view." +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:252 +msgid "New documents received via Peppol are checked multiple times a day. Received documents are automatically imported into the purchase journal set in the :guilabel:`PEPPOL Electronic Document Invoicing` section, and corresponding vendor bills are created as drafts and appear in the vendor bills list view." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:326 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:258 msgid "To manually trigger the scheduled action to retrieve incoming Peppol documents, go to the Accounting dashboard and click :guilabel:`Fetch from Peppol` on the main Peppol purchase journal." msgstr "" @@ -3265,6 +3187,18 @@ msgstr "" msgid "Fetch bills from Peppol" msgstr "" +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:267 +msgid "Peppol deregistration from Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:269 +msgid "Only one Peppol receiver registration can be active for each Peppol endpoint identifier at a time. To stop using Odoo as the Peppol access point, e.g., to switch to another provider or reconfigure the registration for a new database, you must first deregister from Peppol. To do so, go to :menuselection:`Accounting --> Configuration --> Settings`, scroll down to the :guilabel:`PEPPOL Electronic Invoicing` section, click :guilabel:`Remove from Peppol`, and confirm." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:275 +msgid "Once removed, the Peppol registration is deleted from the database, and documents can no longer be sent or received via Peppol in Odoo." +msgstr "" + #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:3 msgid "EPC QR codes" msgstr "" @@ -31001,6 +30935,10 @@ msgstr "" msgid "When using **retention** or **withholding an amount** in a customer invoice, the tax used to retain the amount needs to be specified." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:132 +msgid "Production mode" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:134 msgid "When ready for production, change the :ref:`API mode ` to :guilabel:`Production` and click :guilabel:`Save`." msgstr "" @@ -34288,6 +34226,10 @@ msgstr "" msgid "Once you have enabled the payment provider, it is automatically published on your website. If you wish to unpublish it, click the :guilabel:`Published` button. Customers cannot make payments through an unpublished provider, but they can still manage :dfn:`(delete and assign to a subscription)` their existing tokens linked to such a provider." msgstr "" +#: ../../content/applications/finance/payment_providers.rst:208 +msgid "Test mode" +msgstr "" + #: ../../content/applications/finance/payment_providers.rst:210 msgid "If you wish to try the payment provider as a test, set the :guilabel:`State` field in the payment provider form to :guilabel:`Test mode`, then enter your provider's test/sandbox credentials in the :guilabel:`Credentials` tab." msgstr "" diff --git a/locale/sources/general.pot b/locale/sources/general.pot index 38ae40050..d2d5a6464 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-07-15 08:44+0000\n" +"POT-Creation-Date: 2025-09-29 07:37+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -5495,47 +5495,63 @@ msgid "`Zebra's instructions on printing ZPL files ` or :ref:`Windows virtual IoT's ` homepage and/or in the list of :guilabel:`Devices` on the :ref:`IoT system's form `, the cause is usually the CUPS auto-discovery feature. This feature allows to list all detected printers together with all available drivers, creating one entry for each printer–driver pair." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:462 +msgid "Simply select the entry that works best and ignore the others." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:465 +msgid "Workarounds exist to disable the CUPS auto-discovery feature." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:468 msgid "Barcode scanner issues" msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:457 +#: ../../content/applications/general/iot/devices/printer.rst:471 msgid "The characters read by the barcode scanner do not match the barcode" msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:459 +#: ../../content/applications/general/iot/devices/printer.rst:473 msgid "By default, most barcode scanners are configured in the US QWERTY format. If the barcode scanner uses a different layout, go to :menuselection:`IoT --> Devices` and click the barcode device's card. Then, select the correct language in the :guilabel:`Keyboard Layout` field." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:464 -#: ../../content/applications/general/iot/devices/printer.rst:494 +#: ../../content/applications/general/iot/devices/printer.rst:478 +#: ../../content/applications/general/iot/devices/printer.rst:508 msgid "The :guilabel:`Keyboard Layout` is language-specific, with available options varying based on the device and the language of the database (e.g., :guilabel:`English (UK)`, :guilabel:`English (US)`, etc.)." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:469 +#: ../../content/applications/general/iot/devices/printer.rst:483 msgid "Nothing happens when a barcode is scanned" msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:471 +#: ../../content/applications/general/iot/devices/printer.rst:485 msgid "Make sure the correct device is selected in the :doc:`Point of Sale settings ` (when applicable) and the barcode is configured to send an `ENTER` character (keycode 28) at the end of every barcode." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:476 +#: ../../content/applications/general/iot/devices/printer.rst:490 msgid "The barcode scanner is detected as a keyboard" msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:479 +#: ../../content/applications/general/iot/devices/printer.rst:493 msgid "Some barcode scanners are identified as USB keyboards rather than barcode scanners and are not recognized by IoT systems." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:482 +#: ../../content/applications/general/iot/devices/printer.rst:496 msgid "To change the device type manually, go to :menuselection:`IoT --> Devices` and click the barcode device's card. Then, enable :guilabel:`Is scanner`." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:486 +#: ../../content/applications/general/iot/devices/printer.rst:500 msgid "The barcode scanner processes barcode characters individually" msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:488 +#: ../../content/applications/general/iot/devices/printer.rst:502 msgid "When accessing the mobile version of Odoo from a mobile device or tablet paired with a barcode scanner via the IoT system, the scanner might interpret each character in a barcode as a separate scan. To resolve this, go to :menuselection:`IoT --> Devices` and click the barcode device's card. Then, select the correct language in the :guilabel:`Keyboard Layout` field." msgstr "" diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index 710601600..ae91e7087 100644 --- a/locale/sources/inventory_and_mrp.pot +++ b/locale/sources/inventory_and_mrp.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-07-15 08:44+0000\n" +"POT-Creation-Date: 2025-09-29 07:37+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -14818,30 +14818,50 @@ msgid "Replenish on order (MTO)" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:13 -msgid "*Replenish on order*, also known as *MTO* (make to order), is a replenishment strategy that creates a draft order for a product every time it is required to fulfill a sales order (SO), or when it is needed as a component in a manufacturing order (MO)." +msgid "*Replenish on order*, also known as *MTO* (make to order), is a replenishment strategy that creates a draft order every time a product is needed to fulfill a sales order (SO) or as a component in a manufacturing order (MO)." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:17 -msgid "For products that are purchased from a vendor, a request for quotation (RFQ) is created to replenish the product, while an |MO| is created for products that are manufactured. The creation of an |RFQ| or |MO| occurs every time an |SO| or |MO| that requires the product is confirmed, regardless of the current stock level of the product being ordered." +msgid "For :doc:`purchased products <../../../purchase/manage_deals/rfq>`, Odoo creates a |RFQ|" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:23 -msgid "In order to use the |MTO| route, the :guilabel:`Multi-Step Routes` feature must be enabled. To do so, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and tick the checkbox next to :guilabel:`Multi-Step Routes`, under the :guilabel:`Warehouse` heading." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:18 +msgid "For :doc:`manufactured products <../../../manufacturing/basic_setup/configure_manufacturing_product>`, it creates a |MO|" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:21 +msgid "If stock is available, no |RFQ| or |MO| is generated and the sale proceeds normally. Otherwise, the |RFQ| or |MO| is generated and directly linked to the originating |SO| through a smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:24 +msgid "This approach offers clear traceability, since each |RFQ| or |MO| is tied back to its demand." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:27 -msgid "Finally, click :guilabel:`Save` to save the change." +msgid "The |RFQ| or |MO| generated by |MTO| is designed to fulfill the originating |SO|. These documents should normally be confirmed or adjusted rather than cancelled. If the demand changes, update the document instead of cancelling it." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:32 +msgid "If an |RFQ| or |MO| is cancelled, Odoo does not automatically generate a replacement. A new replenishment document must be created manually, but it **cannot** be linked back to the original |SO| through the smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:36 +msgid "Finally, click :guilabel:`Save` to save the change." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:41 msgid "Unarchive MTO route" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:34 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:43 +msgid "In order to use the |MTO| route, the :guilabel:`Multi-Step Routes` feature must be enabled. To do so, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and tick the checkbox next to :guilabel:`Multi-Step Routes`, under the :guilabel:`Warehouse` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:47 msgid "By default, Odoo sets the |MTO| route as *archived*. This is because |MTO| is a somewhat niche workflow that is only used by certain companies. However, it is easy to unarchive the route in just a few simple steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:51 msgid "To do so, begin by navigating to :menuselection:`Inventory app --> Configuration --> Routes`. On the :guilabel:`Routes` page, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon on the right side of the search bar, and click the :guilabel:`Archived` filter to enable it." msgstr "" @@ -14849,7 +14869,7 @@ msgstr "" msgid "The archived filter on the Routes page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:46 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:59 msgid "After enabling the :guilabel:`Archived` filter, the :guilabel:`Routes` page shows all routes which are currently archived. Tick the checkbox next to :guilabel:`Replenish on Order (MTO)`, then click the :icon:`fa-cog` :guilabel:`Actions` button to reveal a drop-down menu. From the drop-down menu, select :guilabel:`Unarchive`." msgstr "" @@ -14857,23 +14877,23 @@ msgstr "" msgid "The unarchive action on the Routes page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:55 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:68 msgid "Finally, remove the :guilabel:`Archived` filter from the search bar. The :guilabel:`Routes` page now shows all unarchived routes, including :guilabel:`Replenish on Order (MTO)`, which is selectable on the *Inventory* tab of each product page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:60 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:73 msgid "Configure product for MTO" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:75 msgid "With the |MTO| route unarchived, products can now be properly configured to use replenish on order. To do so, begin by going to :menuselection:`Inventory app --> Products --> Products`, then select an existing product, or click :guilabel:`New` to configure a new one." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:66 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:79 msgid "On the product page, select the :guilabel:`Inventory` tab and enable the :guilabel:`Replenish on Order (MTO)` route in the :guilabel:`Routes` section, along with the :guilabel:`Buy` or :guilabel:`Manufacture` route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:84 msgid "The :guilabel:`Replenish on Order (MTO)` route **does not** work unless another route is selected as well. This is because Odoo needs to know how to replenish the product when an order is placed for it (buy or manufacture it)." msgstr "" @@ -14881,79 +14901,87 @@ msgstr "" msgid "Select the MTO route and a second route on the Inventory tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:79 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:92 msgid "If the product is purchased from a vendor to fulfill |SOs|, enable the :guilabel:`Can be Purchased` checkbox under the product name. Doing so makes the :guilabel:`Purchase` tab appear alongside the other tabs below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:83 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:96 msgid "Click the :guilabel:`Purchase` tab and specify a :guilabel:`Vendor` and the :guilabel:`Price` they sell the product for." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:87 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:100 msgid "Specifying a vendor is essential for this workflow, because Odoo cannot generate an |RFQ| without knowing who the product is purchased from." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:103 msgid "If the product is manufactured, make sure it has a bill of materials (BOM) configured for it. To do so, click the :guilabel:`Bill of Materials` smart button at the top of the screen, then click :guilabel:`New` on the :guilabel:`Bill of Materials` page to configure a new |BOM| for the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:95 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:108 msgid "For a full overview of |BOM| creation, see the documentation on :doc:`bills of materials <../../../manufacturing/basic_setup/bill_configuration>`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:112 msgid "Replenish using MTO" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:101 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:114 msgid "After configuring a product to use the |MTO| route, a replenishment order is created for it every time an |SO| or |MO| including the product is confirmed. The type of order created depends on the second route selected in addition to |MTO|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:105 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:118 msgid "For example, if *Buy* was the second route selected, then a |PO| is created upon confirmation of an |SO|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:109 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:122 msgid "When the |MTO| route is enabled for a product, a replenishment order is always created upon confirmation of an |SO| or |MO|. This is the case, even if there is enough stock of the product on-hand to fulfill the |SO|, without buying or manufacturing additional units of it." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:113 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:126 msgid "While the |MTO| route can be used in unison with the *Buy* or *Manufacture* routes, the *Buy* route is used as the example for this workflow. Begin by navigating to the :menuselection:`Sales` app, then click :guilabel:`New`, which opens a blank quotation form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:130 msgid "On the blank quotation form, add a :guilabel:`Customer`. Then, click :guilabel:`Add a product` under the :guilabel:`Order Lines` tab, and enter a product configured to use the *MTO* and *Buy* routes. Click :guilabel:`Confirm`, and the quotation is turned into an |SO|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:121 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:134 msgid "A :guilabel:`Purchase` smart button now appears at the top of the page. Clicking it opens the |RFQ| associated with the |SO|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:124 -msgid "Click :guilabel:`Confirm Order` to confirm the |RFQ|, and turn it into a |PO|. A purple :guilabel:`Receive Products` button now appears above the |PO|. Once the products are received, click :guilabel:`Receive Products` to open the receipt order, and click :guilabel:`Validate` to enter the products into inventory." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:137 +msgid "After receiving approval from the vendor that they can meet the demand by the :guilabel:`Expected Arrival` date, click :guilabel:`Confirm Order` to turn it into a |PO|. A purple :guilabel:`Receive Products` button now appears above the |PO|. Once the products are received, click :guilabel:`Receive Products` to open the receipt order, and click :guilabel:`Validate` to enter the products into inventory." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:129 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:143 msgid "Return to the |SO| by clicking the :guilabel:`SO` breadcrumb, or by navigating to :menuselection:`Sales app --> Orders --> Orders`, and selecting the|SO|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:132 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:146 msgid "Finally, click the :guilabel:`Delivery` smart button at the top of the order to open the delivery order. Once the products have been shipped to the customer, click :guilabel:`Validate` to confirm the delivery." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:137 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:151 +msgid "Cancelling an SO with an MTO product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:153 +msgid "When a |SO| is cancelled, and it had created an |RFQ| or |MO|, the related delivery order is cancelled automatically. However, the |RFQ| or |MO| themselves are **not** cancelled. Instead, a warning appears in their chatter noting the |SO| cancellation. These documents remain active, so the user can either cancel them manually or repurpose the replenishment for another order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:159 msgid "For information on workflows that include the |MTO| route, see the following documentation:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:139 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:161 msgid ":doc:`resupply_warehouses`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:140 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:162 msgid ":doc:`../../../manufacturing/subcontracting/subcontracting_basic`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:141 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:163 msgid ":doc:`../../../manufacturing/advanced_configuration/sub_assemblies`" msgstr "" @@ -21756,14 +21784,14 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:82 #: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:121 #: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:133 -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:129 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:131 msgid "On the |MO|, select the :guilabel:`Work Orders` tab, and then click the :guilabel:`Open Work Order (external link icon)` button on the line of the work order to be processed. On the resulting :guilabel:`Work Orders` pop-up window, click the :guilabel:`Open Shop Floor` button to open the *Shop Floor* module." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:87 #: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:80 #: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:126 -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:138 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:140 msgid "When accessed from a specific work order, the *Shop Floor* module opens to the page for the work center where the order is configured to be processed, and isolates the work order's card so that no other cards are shown." msgstr "" @@ -26672,26 +26700,30 @@ msgid ":guilabel:`Take a Picture` requires a picture to be attached to the check msgstr "" #: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:53 -msgid ":guilabel:`Pass - Fail` is used when the product being checked must meet a certain criteria to pass the check." +msgid ":guilabel:`Print label` opens a pop-up from which labels can be printed. This step can be customized to provide instructions about where to add the labels on a product." msgstr "" #: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:55 -msgid "Selecting :guilabel:`Measure` causes a :guilabel:`Measure` input field to appear, in which a measurement must be entered before the check can be completed." +msgid ":guilabel:`Pass - Fail` is used when the product being checked must meet a certain criteria to pass the check." msgstr "" #: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:57 +msgid "Selecting :guilabel:`Measure` causes a :guilabel:`Measure` input field to appear, in which a measurement must be entered before the check can be completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:59 msgid "Selecting :guilabel:`Worksheet` causes a :guilabel:`Quality Template` drop-down field to appear. Use it to select a quality worksheet that must be filled out to complete the check." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:60 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:62 msgid "In the :guilabel:`Team` field, select the quality team that is responsible for the quality check. In the :guilabel:`Company` field, select the company that owns the product being inspected." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:63 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:65 msgid "On the :guilabel:`Notes` tab at the bottom of the form, enter any relevant instructions in the :guilabel:`Instructions` text entry box (ex. 'Attach a picture of the product'). In the :guilabel:`Notes` text entry box, enter any relevant information about the quality check (who created it, why it was created, etc.)." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:68 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:70 msgid "Finally, if the check is being processed immediately, click the :guilabel:`Pass` button at the top left of the screen if the check passes, or the :guilabel:`Fail` button if the check fails." msgstr "" @@ -26699,43 +26731,43 @@ msgstr "" msgid "A quality check form filled out for a Pass - Fail check." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:76 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:78 msgid "Process quality check" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:78 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:80 msgid "Quality checks can be processed directly on the quality check's page, or from a manufacturing or inventory order for which a check is required. Alternatively, if a quality check is created for a specific work order operation, the check is processed in the *Shop Floor* module." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:83 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:85 msgid "It is not possible to manually create a single quality check that is assigned to a specific work order operation. Quality checks for work order operations can only be created by a |QCP|. See the documentation on :ref:`Quality Control Points ` for information about how to configure a |QCP| that will create quality checks for a specific work order operation." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:90 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:92 msgid "Quality check page" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:92 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:94 msgid "To process a quality check from the check's page, begin by navigating to :menuselection:`Quality --> Quality Control --> Quality Checks`, then select the check to process. Follow the instructions for how to complete the check, listed in the :guilabel:`Instructions` field of the :guilabel:`Notes` tab at the bottom of the page." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:97 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:99 msgid "If the quality check passes, click the :guilabel:`Pass` button at the top of the page. If the check fails, click the :guilabel:`Fail` button, instead." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:101 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:103 msgid "Quality check on order" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:103 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:105 msgid "To process a quality check on an order, select a manufacturing or inventory order (receipt, delivery, return, etc.), for which a check is required. Manufacturing orders can be selected by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and clicking on an order. Inventory orders can be selected by navigating to :menuselection:`Inventory`, clicking the :guilabel:`# To Process` button on an operation card, and selecting an order." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:109 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:111 msgid "On the selected inventory or manufacturing order, a purple :guilabel:`Quality Checks` button appears at the top of the order. Click the button to open the :guilabel:`Quality Check` pop-up window, which shows all of the quality checks required for that order." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:113 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:115 msgid "Follow the instructions that appear on the :guilabel:`Quality Check` pop-up window. If a Pass - Fail check is being processed, complete the check by clicking :guilabel:`Pass` or :guilabel:`Fail` at the bottom of the pop-up window. For all other quality check types, a :guilabel:`Validate` button appears instead. Click it to complete the check." msgstr "" @@ -26743,43 +26775,43 @@ msgstr "" msgid "The \"Quality Check\" pop-up window on a manufacturing order." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:123 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:125 msgid "Quality check on work order" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:125 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:127 msgid "To process a quality check for a work order, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select an |MO| that includes a work order for which a quality check is required." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:135 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:137 msgid "For a full guide to the Shop Floor module, see the :doc:`Shop Floor overview <../../manufacturing/shop_floor/shop_floor_overview>` documentation." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:142 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:144 msgid "Process the work order's steps until the quality check step is reached. Click on the step to open a pop-up window that details how the check should be completed. After following the instructions, click :guilabel:`Validate` to complete the check. Alternatively, if a *Pass - Fail* check is being processed, click either the :guilabel:`Pass` or :guilabel:`Fail` button." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:147 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:149 msgid "It is also possible to complete a quality check by clicking the checkbox on the right side of the step. Doing so automatically marks the check as *Passed*." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:151 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:153 msgid "The specific steps for processing a quality check depend upon the type of check being conducted. For information about processing each type of quality check, see the associated documentation:" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:154 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:156 msgid ":doc:`../quality_check_types/instructions_check`" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:155 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:157 msgid ":doc:`../quality_check_types/pass_fail_check`" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:156 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:158 msgid ":doc:`../quality_check_types/measure_check`" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:157 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:159 msgid ":doc:`../quality_check_types/picture_check`" msgstr "" diff --git a/locale/sources/marketing.pot b/locale/sources/marketing.pot index f2dd2c08a..6244acf8f 100644 --- a/locale/sources/marketing.pot +++ b/locale/sources/marketing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-08-18 08:00+0000\n" +"POT-Creation-Date: 2025-09-29 07:37+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -6691,43 +6691,47 @@ msgstr "" msgid "Copy the :guilabel:`Account SID` and :guilabel:`Auth Token`" msgstr "" -#: ../../content/applications/marketing/sms_marketing/twilio.rst:45 -msgid "Beware that sending SMS to some countries (such as the US or Canada) might require a registration. This can only be done by you, and not by Odoo. Please check out `Twilio's Help Center `_" +#: ../../content/applications/marketing/sms_marketing/twilio.rst:46 +msgid "In case of a testing account, you will only be able to send SMS to phones that you have verified within `Twilio's console `_." msgstr "" -#: ../../content/applications/marketing/sms_marketing/twilio.rst:51 -msgid "Setup Odoo to use Twilio" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/twilio.rst:53 -msgid ":ref:`Install ` the :guilabel:`Twilio SMS` module (`sms_twilio`)" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/twilio.rst:54 -msgid "In Odoo, go to :menuselection:`Settings --> General Settings --> Contacts --> Send SMS`, select :guilabel:`Twilio` in the list of options, and save your change." +#: ../../content/applications/marketing/sms_marketing/twilio.rst:50 +msgid "Sending SMS to some countries (such as the US or Canada) might require a registration. This can only be done by you, and not by Odoo. Please check out `Twilio's Help Center `_." msgstr "" #: ../../content/applications/marketing/sms_marketing/twilio.rst:56 -msgid "Go back to that option, and click :guilabel:`Manage Twilio Connection`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/twilio.rst:57 -msgid "Paste the copied credentials accordingly" +msgid "Setup Odoo to use Twilio" msgstr "" #: ../../content/applications/marketing/sms_marketing/twilio.rst:58 -msgid "Click on :guilabel:`Reload numbers`" +msgid ":ref:`Install ` the :guilabel:`Twilio SMS` module (`sms_twilio`)" msgstr "" #: ../../content/applications/marketing/sms_marketing/twilio.rst:59 -msgid "Your newly bought phone number should appear in the list" +msgid "In Odoo, go to :menuselection:`Settings --> General Settings --> Contacts --> Send SMS`, select :guilabel:`Twilio` in the list of options, and save your change." msgstr "" -#: ../../content/applications/marketing/sms_marketing/twilio.rst:60 -msgid "You can use the testing section to send an SMS" +#: ../../content/applications/marketing/sms_marketing/twilio.rst:61 +msgid "Go back to that option, and click :guilabel:`Manage Twilio Connection`" msgstr "" #: ../../content/applications/marketing/sms_marketing/twilio.rst:62 +msgid "Paste the copied credentials accordingly" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/twilio.rst:63 +msgid "Click on :guilabel:`Reload numbers`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/twilio.rst:64 +msgid "Your newly bought phone number should appear in the list" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/twilio.rst:65 +msgid "You can use the testing section to send an SMS" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/twilio.rst:67 msgid "You can have multiple numbers (for instance once per country, or one per campaign), in that case, you can reorder the numbers. By default, when sending an SMS to a client, Odoo will select the number whose country is the same as the client. If none matches, Odoo will use the first number available from the list respecting the order you have chosen." msgstr "" diff --git a/locale/sources/websites.pot b/locale/sources/websites.pot index ffac2ebed..1aadd8fee 100644 --- a/locale/sources/websites.pot +++ b/locale/sources/websites.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-06-11 13:44+0000\n" +"POT-Creation-Date: 2025-09-29 07:37+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1911,300 +1911,380 @@ msgstr "" msgid "`Odoo Tutorials: eLearning `_" msgstr "" -#: ../../content/applications/websites/elearning.rst:19 +#: ../../content/applications/websites/elearning.rst:21 msgid "Courses" msgstr "" -#: ../../content/applications/websites/elearning.rst:21 -msgid "By going to :menuselection:`eLearning --> Courses --> Courses`, you can get an overview of all your courses." +#: ../../content/applications/websites/elearning.rst:23 +msgid "To get an overview of all courses, go to :menuselection:`eLearning --> Courses --> Courses`." msgstr "" -#: ../../content/applications/websites/elearning.rst:24 -msgid "Click on a course title to edit your course on the back end. Click on :guilabel:`View course` to access your course on the front end." +#: ../../content/applications/websites/elearning.rst:25 +msgid "Click on a course card to edit the course on the back end. Click :guilabel:`View course` to access the course on the front end." msgstr "" -#: ../../content/applications/websites/elearning.rst:28 +#: ../../content/applications/websites/elearning.rst:31 msgid "Course creation" msgstr "" -#: ../../content/applications/websites/elearning.rst:30 -msgid "Click :guilabel:`New` to create a new course. When the page pops up, you can add your :guilabel:`Course Title` and one or more :guilabel:`Tags` to describe your course. You can add an image to illustrate your course by hovering your mouse on the camera placeholder image and clicking on the edit icon. Four tabs allow you to edit your course further: :ref:`Content `, :ref:`Description `, :ref:`Options `, and :ref:`Karma `." +#: ../../content/applications/websites/elearning.rst:33 +msgid "Click :guilabel:`New` to create a new course. In the form that opens, add a :guilabel:`Course Title` and one or more :guilabel:`Tags` to categorize the course and :ref:`allow users to filter courses based on their tags `. To add an image to illustrate the course, hover your mouse on the camera placeholder image and click on :icon:`fa-pencil` :guilabel:`(Edit)`." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:39 +msgid "Four tabs allow you to edit your course further: :ref:`Content `, :ref:`Description `, :ref:`Options `, and :ref:`Karma `." msgstr "" #: ../../content/applications/websites/elearning.rst:-1 msgid "Create your elearning course." msgstr "" -#: ../../content/applications/websites/elearning.rst:44 +#: ../../content/applications/websites/elearning.rst:49 msgid "Content tab" msgstr "" -#: ../../content/applications/websites/elearning.rst:46 -msgid "This tab allows you to manage your course content. Click on :guilabel:`Add Section` to divide your course into different sections. Click on :guilabel:`Add Content` to create :ref:`content `. Click on :guilabel:`Add Certification` to assess the level of understanding of your attendees, certify their skills, and motivate them. **Certification** is part of the :doc:`Surveys <../marketing/surveys/create>` app." +#: ../../content/applications/websites/elearning.rst:51 +msgid "This tab allows you to manage the course content. Click :guilabel:`Add Section` to divide the course into different sections. Click :guilabel:`Add Content` to create :ref:`content items `. Click :guilabel:`Add Certification` to assess the attendees' level of understanding, certify their skills, and motivate them. **Certification** is part of the :doc:`Surveys <../marketing/surveys/create>` app." msgstr "" -#: ../../content/applications/websites/elearning.rst:55 -#: ../../content/applications/websites/elearning.rst:204 +#: ../../content/applications/websites/elearning.rst:60 +#: ../../content/applications/websites/elearning.rst:266 msgid "Description tab" msgstr "" -#: ../../content/applications/websites/elearning.rst:57 -msgid "You can add a short description or information related to your course in the :guilabel:`Description` tab. It appears under your course title on your website." +#: ../../content/applications/websites/elearning.rst:62 +msgid "You can add a short description or information related to the course in the :guilabel:`Description` tab. It appears under the course title on your website." msgstr "" #: ../../content/applications/websites/elearning.rst:-1 msgid "Add a description to your course." msgstr "" -#: ../../content/applications/websites/elearning.rst:67 +#: ../../content/applications/websites/elearning.rst:71 #: ../../content/applications/websites/livechat.rst:94 msgid "Options tab" msgstr "" -#: ../../content/applications/websites/elearning.rst:69 -msgid "In the :guilabel:`Options` tab, different configurations are available: :ref:`Course `, :ref:`Communication `, :ref:`Access rights `, and :ref:`Display `." +#: ../../content/applications/websites/elearning.rst:73 +msgid "In the :guilabel:`Options` tab, different configurations are available: :ref:`Course `, :ref:`Communication `, :ref:`Access rights `, and :ref:`Display `." msgstr "" #: ../../content/applications/websites/elearning.rst:-1 msgid "Overview of the Options tab" msgstr "" -#: ../../content/applications/websites/elearning.rst:80 +#: ../../content/applications/websites/elearning.rst:84 msgid "Course" msgstr "" -#: ../../content/applications/websites/elearning.rst:82 -msgid "Assign a :guilabel:`Responsible` user for your course. If you have multiple websites, use the :guilabel:`Website` field to only display the course on the selected website." -msgstr "" - -#: ../../content/applications/websites/elearning.rst:88 -msgid "Communication" -msgstr "" - -#: ../../content/applications/websites/elearning.rst:90 -msgid ":guilabel:`Allow Reviews`: tick the box to allow attendees to like and comment on your content and to submit reviews on your course;" +#: ../../content/applications/websites/elearning.rst:86 +msgid "Assign a :guilabel:`Responsible` user for the course. If you have multiple websites, use the :guilabel:`Website` field to display the course only on the selected website." msgstr "" #: ../../content/applications/websites/elearning.rst:92 -msgid ":guilabel:`Forum`: add a dedicated forum to your course (only shown if the **Forum** feature is enabled in the app's settings);" +msgid "Communication" msgstr "" #: ../../content/applications/websites/elearning.rst:94 -msgid ":guilabel:`New Content Notification`: select an email template sent to your attendees when you upload new content. Click on the internal link button (:guilabel:`➜`) to have access to the email template editor;" +msgid ":guilabel:`Allow Reviews`: Enable this option to allow attendees to like, comment on, and submit reviews for the course content." msgstr "" -#: ../../content/applications/websites/elearning.rst:97 -msgid ":guilabel:`Completion Notification`: select an email template sent to your attendees once they reach the end of your course. Click on the internal link button (:guilabel:`➜`) to access the email template editor;" +#: ../../content/applications/websites/elearning.rst:96 +msgid ":guilabel:`Forum`: Add a dedicated forum to the course (only shown if the :guilabel:`Forum` feature is enabled in the :ref:`eLearning settings `)." msgstr "" -#: ../../content/applications/websites/elearning.rst:104 -msgid "Access rights" +#: ../../content/applications/websites/elearning.rst:98 +msgid ":guilabel:`New Content Notification`: Select an email template to send emails to attendees when you upload new content items. Click on :icon:`oi-arrow-right` :guilabel:`Internal link` to access the email template editor." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:101 +msgid ":guilabel:`Completion Notification`: Select an email template to send emails to attendees once they reach the end of the course. Click on :icon:`oi-arrow-right` :guilabel:`Internal link` to access the email template editor." msgstr "" #: ../../content/applications/websites/elearning.rst:106 -msgid ":guilabel:`Prerequisites`: set one or more courses that users are advised to complete before" -msgstr "" - -#: ../../content/applications/websites/elearning.rst:107 -msgid "accessing your course;" -msgstr "" - -#: ../../content/applications/websites/elearning.rst:108 -msgid ":guilabel:`Show course to`: define who can access your course and their content between :guilabel:`Everyone`, :guilabel:`Signed In` or :guilabel:`Course Attendees`;" -msgstr "" - -#: ../../content/applications/websites/elearning.rst:110 -msgid ":guilabel:`Enroll Policy`: define how people enroll in your course. Select:" -msgstr "" - -#: ../../content/applications/websites/elearning.rst:112 -msgid ":guilabel:`Open`: if you want your course to be available to anyone;" +msgid "If the :guilabel:`Mailing` feature is enabled in the :ref:`eLearning settings `, a :guilabel:`Contact Attendees` button at the top left of the course form allows you to send mass mailings to people enrolled in the course." msgstr "" #: ../../content/applications/websites/elearning.rst:113 -msgid ":guilabel:`On Invitation`: if only people who received an invitation can enroll to your course. If selected, fill in the :guilabel:`Enroll Message` explaining the course's enrollment process. This message appears on your website under the course title;" +msgid "Access rights" msgstr "" -#: ../../content/applications/websites/elearning.rst:116 -msgid ":guilabel:`On Payment`: if only people who bought your course can attend it. The :guilabel:`Paid Courses` feature must be enabled to get this option. If you select :guilabel:`On Payment`, you must add a :guilabel:`Product` for your course." +#: ../../content/applications/websites/elearning.rst:115 +msgid ":guilabel:`Prerequisites`: Set one or more other courses that users are advised to complete before accessing the course." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:117 +msgid ":guilabel:`Prerequisite Of`: If the course has been defined as a prerequisite for one or more courses, this read-only field displays the course name(s)." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:119 +msgid ":guilabel:`Show course to`: Define who can access the course and its content. Select :guilabel:`Everyone`, :guilabel:`Signed In`, or :guilabel:`Course Attendees`." msgstr "" #: ../../content/applications/websites/elearning.rst:121 -msgid "Only products set up with :guilabel:`Course` as their :guilabel:`Product Type` are displayed." +msgid ":guilabel:`Enroll Policy`: Define how people enroll in the course. Select:" msgstr "" -#: ../../content/applications/websites/elearning.rst:127 -msgid "Display" +#: ../../content/applications/websites/elearning.rst:123 +msgid ":guilabel:`Open`: to make the course available to anyone." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:124 +msgid ":guilabel:`On Invitation`: to restrict enrollment to invited attendees only. If enabled, provide an :guilabel:`Enroll Message` explaining the enrollment process. This message is displayed on your website beneath the course title. To send invite to attendees, click :guilabel:`Invite` and either:guilabel:`Copy` the link or toggle :guilabel:`Send by Email` to send the invitation via email." msgstr "" #: ../../content/applications/websites/elearning.rst:129 -msgid ":guilabel:`Training`: the course content appears as a training program, and the courses must be taken in the proposed order." +msgid ":guilabel:`On Payment`: to restrict enrollment to users who purchase the course. If enabled, select the :guilabel:`Product` to be used. This option requires the :guilabel:`Paid Courses` feature to be enabled in the :ref:`eLearning settings `." msgstr "" -#: ../../content/applications/websites/elearning.rst:131 -msgid ":guilabel:`Documentation`: the content is available in any order. If you choose this option, you can choose which page should be promoted on the course homepage by using the :guilabel:`Featured Content` field." -msgstr "" - -#: ../../content/applications/websites/elearning.rst:138 -msgid "Karma tab" +#: ../../content/applications/websites/elearning.rst:134 +msgid "Only products set up with :guilabel:`Course` as their :guilabel:`Product Type` are available for selection." msgstr "" #: ../../content/applications/websites/elearning.rst:140 -msgid "This tab is about gamification to make eLearning fun and interactive." +msgid "Display" msgstr "" #: ../../content/applications/websites/elearning.rst:142 -msgid "In the :guilabel:`Rewards` section, choose how many karma points you want to grant your students when they :guilabel:`Review` or :guilabel:`Finish` a course." +msgid ":guilabel:`Training`: The course content appears as a training program, and the courses must be taken in the proposed order." msgstr "" -#: ../../content/applications/websites/elearning.rst:145 -msgid "In the :guilabel:`Access Rights` section, define the karma needed to :guilabel:`Add Review`, :guilabel:`Add Comment`, or :guilabel:`Vote` on the course." +#: ../../content/applications/websites/elearning.rst:144 +msgid ":guilabel:`Documentation`: The content is available in any order. Use the :guilabel:`Featured Content` field to define which content items are promoted on the course homepage." msgstr "" -#: ../../content/applications/websites/elearning.rst:149 -msgid "From your course, click the :guilabel:`Contact Attendees` button to reach people who are enrolled in the course." +#: ../../content/applications/websites/elearning.rst:150 +msgid "Karma tab" msgstr "" -#: ../../content/applications/websites/elearning.rst:155 -msgid "Course groups" +#: ../../content/applications/websites/elearning.rst:152 +msgid "This tab is about gamification to make eLearning fun and interactive." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:154 +msgid "In the :guilabel:`Rewards` section, choose how many karma points you want to grant attendees when they :guilabel:`Review` or :guilabel:`Finish` a course." msgstr "" #: ../../content/applications/websites/elearning.rst:157 -msgid "Use the **Course Groups** to inform users and allow them to filter the courses from the :guilabel:`All Courses` dashboard." +msgid "In the :guilabel:`Access Rights` section, define the karma points needed to :guilabel:`Add Review`, :guilabel:`Add Comment`, or :guilabel:`Vote` on the course." msgstr "" -#: ../../content/applications/websites/elearning.rst:160 -msgid "You can manage them by going to :menuselection:`Configuration --> Course Groups`. Click :guilabel:`New` to create a new course group. Add the :guilabel:`Course Group Name`, tick the :guilabel:`Menu Entry` box to allow users to search by course group on the website, and add tags in the :guilabel:`Tag Name` column. For each tag, you can select a corresponding color." +#: ../../content/applications/websites/elearning.rst:163 +msgid "Course groups" msgstr "" -#: ../../content/applications/websites/elearning.rst:166 -msgid "Settings" +#: ../../content/applications/websites/elearning.rst:165 +msgid "**Course Groups** allow users to filter the :guilabel:`All Courses` dashboard on your website and find the course that meets their interests, needs, level, etc." msgstr "" #: ../../content/applications/websites/elearning.rst:168 -msgid "You can enable different features to customize your courses by going to :menuselection:`eLearning --> Configuration --> Settings`:" +msgid "To manage them, go to :menuselection:`eLearning --> Configuration --> Course Groups`. Click :guilabel:`New` to create a new course group. Add the :guilabel:`Course Group Name`, enable :guilabel:`Menu Entry` to allow users to search by course group on the website, and add tags in the :guilabel:`Tag Name` column. For each tag, you can select a corresponding color." msgstr "" -#: ../../content/applications/websites/elearning.rst:171 -msgid "**Certifications**: to evaluate the knowledge of your attendees and certify their skills;" +#: ../../content/applications/websites/elearning.rst:176 +msgid "Settings" msgstr "" -#: ../../content/applications/websites/elearning.rst:172 -msgid "**Paid courses**: to sell access to your courses on your website and track revenues;" -msgstr "" - -#: ../../content/applications/websites/elearning.rst:173 -msgid "**Mailing**: to update all your attendees at once through mass mailings;" -msgstr "" - -#: ../../content/applications/websites/elearning.rst:174 -msgid "**Forum**: to create a community and let attendees answer each other's questions." -msgstr "" - -#: ../../content/applications/websites/elearning.rst:179 -msgid "Content" +#: ../../content/applications/websites/elearning.rst:178 +msgid "The following options are available in the eLearning settings. Go to :menuselection:`eLearning --> Configuration --> Settings`, then enable the desired feature:" msgstr "" #: ../../content/applications/websites/elearning.rst:181 -msgid "Manage your content by going to :menuselection:`eLearning --> Courses --> Contents`. Click :guilabel:`New` to create content. Add your :guilabel:`Content Title`, and if you want :ref:`Tags `, then fill in the related information among the different tabs." +msgid ":guilabel:`Certifications`: Assess attendees' knowledge and provide official certification of their skills." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:183 +msgid ":guilabel:`Paid Courses`: Sell course access directly through your website and track revenue." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:184 +msgid ":guilabel:`Mailing`: Send mass mailings to keep all attendees informed and up to date." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:185 +msgid ":guilabel:`Forum`: Build a community space where attendees can ask questions and help each other." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:190 +msgid "Content" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:192 +msgid "To manage course content, go to :menuselection:`eLearning --> Courses --> Contents`. Click :guilabel:`New` to create a content item. Add the :guilabel:`Content Title` and any desired :ref:`Tags `, then fill in the required information in the different tabs." msgstr "" #: ../../content/applications/websites/elearning.rst:-1 msgid "Create your content." msgstr "" -#: ../../content/applications/websites/elearning.rst:190 +#: ../../content/applications/websites/elearning.rst:200 +msgid "You can also create new content from within a course. Go to :menuselection:`eLearning --> Courses --> Courses`, click the relevant course card, then click :guilabel:`Add content` at the bottom of the :guilabel:`Content` tab." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:207 msgid "Document tab" msgstr "" -#: ../../content/applications/websites/elearning.rst:192 -msgid ":guilabel:`Course`: select the course your content belongs to;" +#: ../../content/applications/websites/elearning.rst:209 +msgid "For each content type, provide the following information:" msgstr "" -#: ../../content/applications/websites/elearning.rst:193 -msgid ":guilabel:`Content Type`: select the type of your content;" -msgstr "" - -#: ../../content/applications/websites/elearning.rst:194 -msgid ":guilabel:`Responsible`: add a responsible person for your content;" -msgstr "" - -#: ../../content/applications/websites/elearning.rst:195 -msgid ":guilabel:`Duration`: indicate the time required to complete the course;" -msgstr "" - -#: ../../content/applications/websites/elearning.rst:196 -msgid ":guilabel:`Allow Download`: allow users to download the content of the slide. This option is only visible when the content is a document;" -msgstr "" - -#: ../../content/applications/websites/elearning.rst:198 -msgid ":guilabel:`Allow Preview`: the course is accessible by anyone." -msgstr "" - -#: ../../content/applications/websites/elearning.rst:199 -msgid ":guilabel:`# of Public Views`: displays the number of views from non-enrolled participants;" -msgstr "" - -#: ../../content/applications/websites/elearning.rst:200 -msgid ":guilabel:`# Total Views`: displays the total number of views (non-enrolled and enrolled participants)." -msgstr "" - -#: ../../content/applications/websites/elearning.rst:206 -msgid "You can add a description of your content that appears front end in the :guilabel:`About` section of your course content." -msgstr "" - -#: ../../content/applications/websites/elearning.rst:210 -msgid "Additional Resources tab" +#: ../../content/applications/websites/elearning.rst:211 +msgid ":guilabel:`Course`: Select the course to which the content item belongs." msgstr "" #: ../../content/applications/websites/elearning.rst:212 -msgid "Click :guilabel:`Add a line` to add a link or a file that supports your participants' learning. It appears in the course content on your website." +msgid ":guilabel:`Content Type`: Select the relevant :ref:`content type ` and provide the required information." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:214 +msgid ":guilabel:`Responsible`: Select the user responsible for the content item. By default, this is the user who creates the course, but another user can be selected." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:216 +msgid ":guilabel:`Duration`: Enter the time required to complete the lesson." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:217 +msgid ":guilabel:`Allow Preview`: Enable this if the content should be accessible to anyone." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:220 +msgid "If the :ref:`Content Type ` is :guilabel:`Document`, enabling :guilabel:`Allow Download` allows users to download the content." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:223 +msgid "Two read-only fields provide data about how often the content item is viewed:" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:225 +msgid ":guilabel:`# of Public Views`: displays the number of views from non-enrolled participants." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:226 +msgid ":guilabel:`# Total Views`: displays the total number of views (non-enrolled and enrolled participants)." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:-1 +msgid "Provide information about the content." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:235 +msgid "Content types" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:237 +msgid "You can add the following content types:" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:239 +msgid ":guilabel:`Image`: To upload an image, select :guilabel:`Upload from Device`, click :guilabel:`Upload your file`, then select the relevant file. Supported formats include JPG, JPEG, PNG, SVG, GIF, and WEBP. The maximum file size is 25MB." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:243 +msgid "Alternatively, to add an image saved on Google Drive, select :guilabel:`Retrieve from Google Drive`, then add the Google Drive link to the image." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:246 +msgid ":guilabel:`Article`: Articles are website pages that are customized using the website builder on your website's front end." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:249 +msgid "With the :guilabel:`Course` selected, click the :guilabel:`Go to Website` smart button, then, at the top-right of the screen, click :icon:`fa-pencil` :guilabel:`(Edit)`. Write the article's content and :doc:`customize the page using the website builder `." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:253 +msgid ":guilabel:`Document`: To upload a document, select :guilabel:`Upload from Device`, click :guilabel:`Upload your file`, then select the relevant file. Only PDF documents can be uploaded." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:256 +msgid "Alternatively, to add a Google Slides presentation, Google Doc document, or Google Sheets spreadsheet, click :guilabel:`Retrieve from Google Drive` and add the Google Drive link to the file." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:260 +msgid ":guilabel:`Video`: Add the YouTube, Google Drive, or Vimeo link to the video." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:261 +msgid ":guilabel:`Quiz`: Open the :ref:`Quiz tab ` to create a quiz." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:268 +msgid "Add a description for the content. This text is displayed in the :guilabel:`About` section of the content item on your website." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:274 +msgid "Additional Resources tab" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:276 +msgid "Click :guilabel:`Add a line` to add a link or a file that supports your participants' learning. The resource appears in the course content on your website." msgstr "" #: ../../content/applications/websites/elearning.rst:-1 msgid "Additional ressources" msgstr "" -#: ../../content/applications/websites/elearning.rst:222 +#: ../../content/applications/websites/elearning.rst:285 msgid "Quiz tab" msgstr "" -#: ../../content/applications/websites/elearning.rst:224 -msgid "From this tab you can create a quiz to assess your students at the end of the course." +#: ../../content/applications/websites/elearning.rst:287 +msgid "From this tab, you can create a quiz to assess your students at the end of the course." msgstr "" -#: ../../content/applications/websites/elearning.rst:226 -msgid "The :guilabel:`Points Rewards` section lets you give a specific number of karma points depending on how many tries they need to correctly answer the question. Then, create your questions and the possible answers by clicking on :guilabel:`Add a line`. A new window pops up, add the question by filling in the :guilabel:`Question Name` and add multiple answers by clicking on :guilabel:`Add a line`. Tick the :guilabel:`Is correct answer` to mark one or more answers as correct. You can also fill in the :guilabel:`Comment` field to display additional information when the answer is chosen by the participant." +#: ../../content/applications/websites/elearning.rst:289 +msgid "The :guilabel:`Points Rewards` section allows you to assign karma points based on how many attempts are needed to answer correctly. To create a question, click :guilabel:`Add a line`, enter the :guilabel:`Question Name`, and add possible answers. Mark the correct answer(s) by selecting :guilabel:`Is correct answer`. You can also use the :guilabel:`Comment` field to provide additional information when an answer is selected." msgstr "" -#: ../../content/applications/websites/elearning.rst:237 +#: ../../content/applications/websites/elearning.rst:298 msgid "Content Tags" msgstr "" -#: ../../content/applications/websites/elearning.rst:239 -msgid "The **Content Tags** help users to classify the content from the :guilabel:`Contents` dashboard." +#: ../../content/applications/websites/elearning.rst:300 +msgid "**Content Tags** are visible on the :guilabel:`Contents` dashboard of a course on your website, and can help users identify the kind of content a particular lesson contains, e.g., theory, or exercises." msgstr "" -#: ../../content/applications/websites/elearning.rst:241 -msgid "You can manage them by going to :menuselection:`eLearning --> Configuration --> Content Tags`. Click :guilabel:`New` to create a new tag." +#: ../../content/applications/websites/elearning.rst:303 +msgid "To manage content tags, go to :menuselection:`eLearning --> Configuration --> Content Tags`. Click :guilabel:`New` to create a new tag." msgstr "" -#: ../../content/applications/websites/elearning.rst:245 -msgid "Publish your content" +#: ../../content/applications/websites/elearning.rst:309 +msgid "Publish courses and content" msgstr "" -#: ../../content/applications/websites/elearning.rst:247 -msgid "Everything created on the back end needs to be published from the front end. Unpublished content is always visible from your website but still needs to be published to be available to your audience." +#: ../../content/applications/websites/elearning.rst:311 +msgid "Courses and content items must be published from the front end to be available to your audience. To access the front end, click the :guilabel:`Go to Website` smart button at the top of the course form or an individual content form." msgstr "" -#: ../../content/applications/websites/elearning.rst:250 -msgid "You must be on your website's front end to publish your content. To do so, click on the :guilabel:`Go To Website` smart button, and tick the :guilabel:`Publish` option available in the right-hand corner." +#: ../../content/applications/websites/elearning.rst:315 +msgid "A course and its content items are published separately:" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:317 +msgid "To publish a course, access the main course page, then toggle the switch in the upper-right corner from :guilabel:`Unpublished` to :guilabel:`Published`." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:319 +msgid "To publish individual content items, click on an item to open it, then toggle the switch from :guilabel:`Unpublished` to :guilabel:`Published`." msgstr "" #: ../../content/applications/websites/elearning.rst:-1 msgid "Publish your content." msgstr "" +#: ../../content/applications/websites/elearning.rst:326 +msgid "When publishing a new course, publish the individual content items before publishing the course itself. Published content is only available to your audience once the course it is part of is published." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:330 +msgid "To unpublish a course or an individual content item, open the course or item, then toggle the switch from :guilabel:`Published` to :guilabel:`Unpublished`." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:334 +msgid "Unpublishing a course renders the course *and* its content unavailable to your audience." +msgstr "" + #: ../../content/applications/websites/forum.rst:3 msgid "Forum" msgstr "" @@ -2282,7 +2362,7 @@ msgid "A user's karma points are shared across all forums, courses, etc., of a s msgstr "" #: ../../content/applications/websites/forum.rst:56 -msgid "eLearning users can earn karma points through different :ref:`course interactions ` and by :ref:`completing quizzes `." +msgid "eLearning users can earn karma points through different :ref:`course interactions ` and by :ref:`completing quizzes `." msgstr "" #: ../../content/applications/websites/forum.rst:62