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

[I18N] Export 14.0 source terms

Browse Source
This commit is contained in:
Martin Trigaux 2020-11-02 12:07:59 +01:00
parent 27175c3685
commit 97ece83b34
9 changed files with 453 additions and 828 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

284
locale/sources/accounting.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-10-09 11:26+0200\n"
"POT-Creation-Date: 2020-11-02 12:05+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -173,7 +173,7 @@ msgstr ""
#: ../../accounting/fiscal_localizations/localizations/argentina.rst:24
#: ../../accounting/fiscal_localizations/localizations/chile.rst:21
#: ../../accounting/fiscal_localizations/localizations/chile.rst:277
#: ../../accounting/fiscal_localizations/localizations/chile.rst:329
#: ../../accounting/fiscal_localizations/localizations/chile.rst:314
#: ../../accounting/fiscal_localizations/localizations/colombia.rst:27
#: ../../accounting/fiscal_localizations/localizations/mexico.rst:35
#: ../../accounting/fiscal_localizations/overview/fiscal_localization_packages.rst:14
@ -1531,7 +1531,6 @@ msgid "Debit Note: ND-A 0001-00000004."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/argentina.rst:268
#: ../../accounting/fiscal_localizations/localizations/chile.rst:295
msgid "Sequences"
msgstr ""
@ -1837,7 +1836,7 @@ msgid "You can also get the last number used in AFIP for a specific Document Typ
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/argentina.rst:507
#: ../../accounting/fiscal_localizations/localizations/chile.rst:639
#: ../../accounting/fiscal_localizations/localizations/chile.rst:614
#: ../../accounting/others/multicurrencies/invoices_payments.rst:64
#: ../../accounting/payables/supplier_bills.rst:3
msgid "Vendor Bills"
@ -2037,7 +2036,7 @@ msgid "A certificate can be shared between several users. If this is the case le
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:101
#: ../../accounting/fiscal_localizations/localizations/chile.rst:690
#: ../../accounting/fiscal_localizations/localizations/chile.rst:665
msgid "Financial Reports"
msgstr ""
@ -2135,7 +2134,7 @@ msgid "The document type is essential information that needs to be displayed in
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:220
msgid "Each document type can have a unique sequence per journal where it is assigned. As part of the localization, the Document Type includes the country on which the document is applicable and the data is created automatically when the localization module is installed."
msgid "Each document type can have a unique sequence per company. As part of the localization, the Document Type includes the country on which the document is applicable and the data is created automatically when the localization module is installed."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:240
@ -2216,386 +2215,366 @@ msgstr ""
msgid "**Use Documents**: This field is used to define if the journal will use Document Types. It is only applicable to Purchase and Sales journals that can be related to the different sets of document types available in Chile. By default, all the sales journals created will use documents."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:297
msgid "When a Journal is created we have two options with document types sequences."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:299
msgid "Create new sequences: In this case, Odoo will create new sequences for the most common document types."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:301
msgid "Use existent sequence: If the sequence should be shared between several journals, the user can add manually sequences previously created."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:309
#: ../../accounting/fiscal_localizations/localizations/chile.rst:295
msgid "For the Chilean localization it’s important to define the default Debt and Credit accounts as they are required for one of the debit notes use cases."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:313
#: ../../accounting/fiscal_localizations/localizations/chile.rst:299
msgid "CAF"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:315
msgid "For each sequence related to the documents type, a CAF (Folio Authorization Code) is required, the CAF is a file the SII provides to the Emisor with the folio/sequence authorized for the electronic invoice documents."
#: ../../accounting/fiscal_localizations/localizations/chile.rst:301
msgid "A CAF (Folio Authorization Code) is required, for each document type that is issued to your customers, the CAF is a file the SII provides to the Emisor with the folio/sequence authorized for the electronic invoice documents."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:319
msgid "Your company can make several requests for folios and obtain several CAFs, each one associated with different ranges of folios. In this way, you could order folios per the different segmentations you have in your journals (example per office) thus avoiding distributing a range of folios. In this way, each branch would have its private key of the respective CAF."
#: ../../accounting/fiscal_localizations/localizations/chile.rst:305
msgid "Your company can make several requests for folios and obtain several CAFs, each one associated with different ranges of folios. The CAFs are shared within all the journals, this means that you only need one active CAF per document type and it will be applied on all journals."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:324
#: ../../accounting/fiscal_localizations/localizations/chile.rst:309
msgid "Please refer to the SII documentation to check the detail on how to acquire the CAF: `SII Timbraje <https://palena.sii.cl/dte/mn_timbraje.html>`_."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:331
msgid "Once you have the CAF files you need to associate them with journal sequence in Odoo, after you create the sequence for the first time the will be in red, which indicates that no CAF has been configured for that particular sequence:"
#: ../../accounting/fiscal_localizations/localizations/chile.rst:316
msgid "Once you have the CAF files you need to associate them with a document type in Odoo, in order to add a CAF, just follow these steps:"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:339
msgid "In order to add a CAF, just follow these steps:"
#: ../../accounting/fiscal_localizations/localizations/chile.rst:319
msgid "Access to :menuselection:`Accounting --> Settings --> CAF`"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:341
msgid "Open the sequence."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:342
msgid "Go the the Tab “CAF”."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:343
#: ../../accounting/fiscal_localizations/localizations/chile.rst:320
msgid "Upload the file."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:344
#: ../../accounting/fiscal_localizations/localizations/chile.rst:321
msgid "Save the CAF."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:345
msgid "Save the sequence."
#: ../../accounting/fiscal_localizations/localizations/chile.rst:327
msgid "Once loaded, the status changes to *In Use*. At this moment, when a transaction is used for this document type, the invoice number takes the first folio in the sequence."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:352
msgid "As a result, the sequence color changes to black and the column Next number and quantity available are updated:"
#: ../../accounting/fiscal_localizations/localizations/chile.rst:331
msgid "In case you have used some folios in your previous system, make sure you set the next valid folio when the first transation is created."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:361
#: ../../accounting/fiscal_localizations/localizations/chile.rst:337
msgid "Usage and Testing"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:364
#: ../../accounting/fiscal_localizations/localizations/chile.rst:340
msgid "Electronic Invoice Workflow"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:366
#: ../../accounting/fiscal_localizations/localizations/chile.rst:342
msgid "In the Chilean localization the electronic Invoice workflow covers the Emission of Customer Invoices and the reception of Vendor Bills, in the next diagram we explain how the information transmitted to the SII and between the customers and Vendors."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:376
#: ../../accounting/fiscal_localizations/localizations/chile.rst:352
msgid "Customer invoice Emission"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:378
#: ../../accounting/fiscal_localizations/localizations/chile.rst:354
msgid "After the partners and journals are created and configured, the invoices are created in the standard way, for Chile one of the differentiators is the document type which is selected automatically based on the Taxpayer."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:382
#: ../../accounting/fiscal_localizations/localizations/chile.rst:358
msgid "You can manually change the document type if needed."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:390
#: ../../accounting/fiscal_localizations/localizations/chile.rst:366
msgid "Validation and DTE Status"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:392
#: ../../accounting/fiscal_localizations/localizations/chile.rst:368
msgid "When all the invoice information is filled, either manually or automatically when it’s created from a sales order, proceed to validate the invoice. After the invoice is posted:"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:395
#: ../../accounting/fiscal_localizations/localizations/chile.rst:371
msgid "The DTE File (Electronic Tax Document) is created automatically and added in the chatter."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:396
#: ../../accounting/fiscal_localizations/localizations/chile.rst:372
msgid "The DTE SII status is set as: Pending to be sent."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:402
#: ../../accounting/fiscal_localizations/localizations/chile.rst:378
msgid "The DTE Status is updated automatically by Odoo with a scheduled action that runs every day at night, if you need to get the response from the SII immediately you can do it manually as well. The DTE status workflow is as follows:"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:411
#: ../../accounting/fiscal_localizations/localizations/chile.rst:387
msgid "In the first step the DTE is sent to the SII, you can manually send it using the button: Enviar Ahora, a SII Tack number is generated and assigned to the invoice, you can use this number to check the details the SII sent back by email. The DTE status is updated to Ask for Status."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:416
#: ../../accounting/fiscal_localizations/localizations/chile.rst:392
msgid "Once the SII response is received Odoo updates the DTE Status, in case you want to do it manually just click on the button: Verify on SII. The result can either be Accepted, Accepted With Objection or Rejected."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:425
#: ../../accounting/fiscal_localizations/localizations/chile.rst:401
msgid "There are several internal status in the SII before you get Acceptance or Rejection, in case you click continuously the Button Verify in SII, you will receive in the chatter the detail of those intermediate statuses:"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:433
#: ../../accounting/fiscal_localizations/localizations/chile.rst:409
msgid "The final response from the SII, can take on of these values:"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:436
#: ../../accounting/fiscal_localizations/localizations/chile.rst:412
msgid "**Accepted:** Indicates the invoice information is correct, our document is now fiscally valid and it’s automatically sent to the customer."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:439
#: ../../accounting/fiscal_localizations/localizations/chile.rst:415
msgid "**Accepted with objections:** Indicates the invoice information is correct but a minor issue was identified, nevertheless our document is now fiscally valid and it’s automatically sent to the customer."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:447
#: ../../accounting/fiscal_localizations/localizations/chile.rst:423
msgid "**Rejected:** Indicates the information in the invoice is incorrect and needs to be corrected, the detail of the issue is received in the emails you registered in the SII, if it is properly configured in Odoo, the details are also retrieved in the chatter once the email server is processed."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:452
#: ../../accounting/fiscal_localizations/localizations/chile.rst:428
msgid "If the invoice is Rejected please follow this steps:"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:454
#: ../../accounting/fiscal_localizations/localizations/chile.rst:430
msgid "Change the document to draft."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:455
#: ../../accounting/fiscal_localizations/localizations/chile.rst:431
msgid "Make the required corrections based on the message received from the SII."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:456
#: ../../accounting/fiscal_localizations/localizations/chile.rst:432
msgid "Post the invoice again."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:464
#: ../../accounting/fiscal_localizations/localizations/chile.rst:440
msgid "Crossed references"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:466
#: ../../accounting/fiscal_localizations/localizations/chile.rst:442
msgid "When the Invoice is created as a result of another fiscal document, the information related to the originator document must be registered in the Tab Cross Reference, which is commonly used for credit or debit notes, but in some cases can be used on Customer Invoices as well. In the case of the credit and debit notes, they are set automatically by Odoo:"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:476
#: ../../accounting/fiscal_localizations/localizations/chile.rst:452
msgid "Invoice PDF Report"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:478
#: ../../accounting/fiscal_localizations/localizations/chile.rst:454
msgid "After the invoice is Accepted and valdiated by the SII and the PDF is printed it includes the fiscal elements that indicates out document is fiscally valid:"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:487
#: ../../accounting/fiscal_localizations/localizations/chile.rst:463
msgid "Commercial Validation"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:489
#: ../../accounting/fiscal_localizations/localizations/chile.rst:465
msgid "Once the invoice has been sent to the customer:"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:491
#: ../../accounting/fiscal_localizations/localizations/chile.rst:467
msgid "DTE partner status changes to “Sent”."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:492
#: ../../accounting/fiscal_localizations/localizations/chile.rst:468
msgid "The customer must send a reception confirmation email."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:493
#: ../../accounting/fiscal_localizations/localizations/chile.rst:469
msgid "Subsequently, if all the commercial terms and invoice data are correct, they will send the Acceptance confirmation, otherwise they send a Claim."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:495
#: ../../accounting/fiscal_localizations/localizations/chile.rst:471
msgid "The field DTE acceptation status is updated automatically."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:503
#: ../../accounting/fiscal_localizations/localizations/chile.rst:479
msgid "Processed for Claimed invoices"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:505
#: ../../accounting/fiscal_localizations/localizations/chile.rst:481
msgid "Once the invoice has been Accepted by the SII **it can not be cancelled in Odoo**. In case you get a Claim for your customer the correct way to proceed is with a Credit Note to either cancel the Invoice or correct it. Please refer to the Credit Notes section for more details."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:514
#: ../../accounting/fiscal_localizations/localizations/chile.rst:490
msgid "Common Errors"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:516
#: ../../accounting/fiscal_localizations/localizations/chile.rst:492
msgid "There are multiple reasons behind a rejection from the SII, but these are some of the common errors you might have and which is the related solution."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:519
#: ../../accounting/fiscal_localizations/localizations/chile.rst:495
msgid "Error: RECHAZO- DTE Sin Comuna Origen."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:521
#: ../../accounting/fiscal_localizations/localizations/chile.rst:497
msgid "*Hint:* Make sure the Company Address is properly filled including the State and City."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:523
#: ../../accounting/fiscal_localizations/localizations/chile.rst:499
msgid "Error en Monto : - IVA debe declararse."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:525
#: ../../accounting/fiscal_localizations/localizations/chile.rst:529
#: ../../accounting/fiscal_localizations/localizations/chile.rst:501
#: ../../accounting/fiscal_localizations/localizations/chile.rst:505
msgid "*Hint:* The invoice lines should include one VAT tax, make sure you add one on each invoice line."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:527
#: ../../accounting/fiscal_localizations/localizations/chile.rst:503
msgid "Error: Rut No Autorizado a Firmar."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:531
#: ../../accounting/fiscal_localizations/localizations/chile.rst:507
msgid "Error: Fecha/Número Resolucion Invalido RECHAZO- CAF Vencido : (Firma_DTE[AAAA-MM-DD] - CAF[AAAA-MM-DD]) &gt; 6 meses."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:534
msgid "*Hint:* Try to add a new CAF in the journal sequence related to this document as the one you’re using is expired."
#: ../../accounting/fiscal_localizations/localizations/chile.rst:510
msgid "*Hint:* Try to add a new CAF related to this document as the one you’re using is expired."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:540
#: ../../accounting/fiscal_localizations/localizations/chile.rst:515
msgid "Credit Notes"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:542
msgid "When a cancellation or correction is needed over a validated invoice, a credit note must be generated. It is important to consider that a CAF file is required for the Credit Note sequence, which is identified as document 64 in the SII."
#: ../../accounting/fiscal_localizations/localizations/chile.rst:517
msgid "When a cancellation or correction is needed over a validated invoice, a credit note must be generated. It is important to consider that a CAF file is required for the Credit Note, which is identified as document 64 in the SII."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:551
msgid "Refer to the journal section where we described the process to load the CAF on each sequence."
#: ../../accounting/fiscal_localizations/localizations/chile.rst:526
msgid "Refer to the CAF section where we described the process to load the CAF on each document type."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:555
#: ../../accounting/fiscal_localizations/localizations/chile.rst:607
#: ../../accounting/fiscal_localizations/localizations/chile.rst:530
#: ../../accounting/fiscal_localizations/localizations/chile.rst:582
msgid "Use Cases"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:558
#: ../../accounting/fiscal_localizations/localizations/chile.rst:533
msgid "Cancel Referenced document"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:560
#: ../../accounting/fiscal_localizations/localizations/chile.rst:535
msgid "In case you need to cancel or invalid an Invoice, use the button Add Credit note and select Full Refund, in this case the SII reference Code is automatically set to: Anula Documento de referencia."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:568
#: ../../accounting/fiscal_localizations/localizations/chile.rst:543
msgid "Corrects Referenced Document Text"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:570
#: ../../accounting/fiscal_localizations/localizations/chile.rst:545
msgid "If a correction in the invoice information is required, for example the Street Name, use the button Add Credit note,select Partial Refund and select the option “Solo corregir Texto”. In this case the SII reference Code is automatically set to: Corrige el monto del Documento de Referencia."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:578
#: ../../accounting/fiscal_localizations/localizations/chile.rst:553
msgid "Odoo creates a Credit Note with the corrected text in an invoice and price 0."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:585
#: ../../accounting/fiscal_localizations/localizations/chile.rst:560
msgid "It’s important to define the default credit account in the Sales journal as it is taken for this use case in specific."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:589
#: ../../accounting/fiscal_localizations/localizations/chile.rst:564
msgid "Corrects Referenced Document Amount"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:591
#: ../../accounting/fiscal_localizations/localizations/chile.rst:566
msgid "When a correction on the amounts is required, use the button Add Credit note and select Partial Refund. In this case the SII reference Code is automatically set to: Corrige el monto del Documento de Referencia."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:600
#: ../../accounting/fiscal_localizations/localizations/chile.rst:575
msgid "Debit Notes"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:602
#: ../../accounting/fiscal_localizations/localizations/chile.rst:577
msgid "As part of the Chilean localization, besides creating credit notes from an existing document you can also create debit Notes. For this just use the button “Add Debit Note”. The two main use cases for debit notes are detailed below."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:610
#: ../../accounting/fiscal_localizations/localizations/chile.rst:585
msgid "Add debt on Invoices"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:612
#: ../../accounting/fiscal_localizations/localizations/chile.rst:587
msgid "The most common use case for debit notes is to increase the value of an existing invoice, you need to select option 3 in the field Reference code SII:"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:620
#: ../../accounting/fiscal_localizations/localizations/chile.rst:595
msgid "In this case Odoo automatically includes the source invoice in the cross reference section:"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:627
#: ../../accounting/fiscal_localizations/localizations/chile.rst:602
msgid "Cancel Credit Notes"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:629
#: ../../accounting/fiscal_localizations/localizations/chile.rst:604
msgid "In Chile the debits notes are used to cancel a validated Credit Note, in this case just select the button Add debit note and select the first option in the wizard: *1: Anula Documentos de referencia.*"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:641
#: ../../accounting/fiscal_localizations/localizations/chile.rst:616
msgid "As part of the Chilean localization, you can configure your Incoming email server as the same you have register in the SII in order to:"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:644
#: ../../accounting/fiscal_localizations/localizations/chile.rst:619
msgid "Automatically receive the vendor bills DTE and create the vendor bill based on this information."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:645
#: ../../accounting/fiscal_localizations/localizations/chile.rst:620
msgid "Automatically Send the reception acknowledgement to your vendor."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:646
#: ../../accounting/fiscal_localizations/localizations/chile.rst:621
msgid "Accept or Claim the document and send this status to your vendor."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:650
#: ../../accounting/fiscal_localizations/localizations/chile.rst:625
msgid "Reception"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:652
#: ../../accounting/fiscal_localizations/localizations/chile.rst:627
msgid "As soon as the vendor email with the attached DTE is received: 1. The vendor Bill mapping all the information included in the xml. 2. An email is sent to the vendor with the Reception acknowledgement. 3. The DTE status is set as: Acuse de Recibido Enviado"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:662
#: ../../accounting/fiscal_localizations/localizations/chile.rst:637
msgid "Acceptation"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:664
#: ../../accounting/fiscal_localizations/localizations/chile.rst:639
msgid "If all the commercial information is correct on your vendor bill, you can accept the document using the button: Aceptar Documento, once this is done the DTE Acceptation Status changes to: Accepted and an email of acceptance is sent to the vendor."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:674
#: ../../accounting/fiscal_localizations/localizations/chile.rst:649
msgid "Claim"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:676
#: ../../accounting/fiscal_localizations/localizations/chile.rst:651
msgid "In case there is a commercial issue or the information is not correct on your vendor bill, you can Claim the document before validating it, using the button: Claim, once this is done the DTE Acceptation Status change to: Claim and an email of acceptance is sent to the vendor."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:684
#: ../../accounting/fiscal_localizations/localizations/chile.rst:659
msgid "If you claim a vendor bill, the status changes from draft to cancel automatically. Considering this as best practice, all the Claim documents should be canceled as they won’t be valid for your accounting records."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:693
#: ../../accounting/fiscal_localizations/localizations/chile.rst:668
msgid "Balance Tributario de 8 Columnas"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:695
#: ../../accounting/fiscal_localizations/localizations/chile.rst:670
msgid "This report presents the accounts in detail (with their respective balances), classifying them according to their origin and determining the level of profit or loss that the business had within the evaluated period of time, so that a real and complete knowledge of the status of a company."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:699
#: ../../accounting/fiscal_localizations/localizations/chile.rst:715
#: ../../accounting/fiscal_localizations/localizations/chile.rst:674
#: ../../accounting/fiscal_localizations/localizations/chile.rst:690
msgid "You can find this report in :menuselection:`Accounting --> Accounting --> Reports`"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:706
#: ../../accounting/fiscal_localizations/localizations/chile.rst:681
msgid "Propuesta F29"
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:708
#: ../../accounting/fiscal_localizations/localizations/chile.rst:683
msgid "The form F29 is a new system that the SII enabled to taxpayers, and that replaces the Purchase and Sales Books. This report is integrated by Purchase Register (CR) and the Sales Register (RV). Its purpose is to support the transactions related to VAT, improving its control and declaration."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/chile.rst:712
#: ../../accounting/fiscal_localizations/localizations/chile.rst:687
msgid "This record is supplied by the electronic tax documents (DTE’s) that have been received by the SII."
msgstr ""
@ -4074,7 +4053,7 @@ msgid "First, make sure that your company is configured with the correct data. G
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/mexico.rst:82
msgid "If you want use the Mexican localization on test mode, you can put any known address inside Mexico with all fields for the company address and set the vat to **TCM970625MB1**."
msgid "If you want use the Mexican localization on test mode, you can put any known address inside Mexico with all fields for the company address and set the vat to **EKU9003173C9**."
msgstr ""
#: ../../accounting/fiscal_localizations/localizations/mexico.rst:91
@ -6303,7 +6282,7 @@ msgid "Via the analytical account, Odoo can account the invoice lines and purcha
msgstr ""
#: ../../accounting/others/adviser/budget.rst:153
msgid "The theoretical amount represents the amount of money you theoretically could have spend / should have received in function of the date. When your budget is 1200 for 12 months (january to december), and today is 31 of january, the theoretical amount will be 1000, since this is the actual amount that could have been realised."
msgid "The theoretical amount represents the amount of money you theoretically could have spend / should have received in function of the date. When your budget is 1200 for 12 months (january to december), and today is 31 of january, the theoretical amount will be 100, since this is the actual amount that could have been realised."
msgstr ""
#: ../../accounting/others/analytic.rst:3
@ -7435,13 +7414,20 @@ msgstr ""
msgid "The Exchange difference journal can be changed in your accounting settings."
msgstr ""
#: ../../accounting/others/multicurrencies/exchange.rst:109
#: ../../accounting/others/multicurrencies/full_reconcile_warning.rst:2
#: ../../accounting/others/multicurrencies/full_reconcile_warning.rst:2
#: ../../accounting/others/multicurrencies/full_reconcile_warning.rst:2
#: ../../accounting/others/multicurrencies/full_reconcile_warning.rst:2
msgid "In order for an exchange difference entry to be created automatically, the corresponding invoices and payments need to be fully reconciled. This means the invoices are fully paid and the payments are fully spent on invoices. If you partially pay 3 invoices from 2 payments, and the last invoice still has an amount due, there will be no exchange difference entry for any of them until that final amount is paid."
msgstr ""
#: ../../accounting/others/multicurrencies/exchange.rst:111
#: ../../accounting/payables/pay/multiple.rst:147
#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:68
msgid ":doc:`../../bank/reconciliation/reconciliation_models`"
msgstr ""
#: ../../accounting/others/multicurrencies/exchange.rst:110
#: ../../accounting/others/multicurrencies/exchange.rst:112
#: ../../accounting/payables/pay/multiple.rst:100
#: ../../accounting/payables/pay/sepa.rst:131
msgid ":doc:`../../bank/reconciliation/use_cases`"
@ -7582,12 +7568,12 @@ msgstr ""
msgid "Go to :menuselection:`Adviser --> Journal Entries` and look for the Exchange difference journal entries. All the exchange rates differences are recorded in it."
msgstr ""
#: ../../accounting/others/multicurrencies/how_it_works.rst:168
#: ../../accounting/others/multicurrencies/how_it_works.rst:170
msgid ":doc:`invoices_payments`"
msgstr ""
#: ../../accounting/others/multicurrencies/how_it_works.rst:169
#: ../../accounting/others/multicurrencies/invoices_payments.rst:119
#: ../../accounting/others/multicurrencies/how_it_works.rst:171
#: ../../accounting/others/multicurrencies/invoices_payments.rst:121
msgid ":doc:`exchange`"
msgstr ""
@ -7647,7 +7633,7 @@ msgstr ""
msgid "Go to :menuselection:`Adviser --> Journal Entries` and look for the **Exchange Difference** journal entries. All the exchange rates differences are recorded in it."
msgstr ""
#: ../../accounting/others/multicurrencies/invoices_payments.rst:118
#: ../../accounting/others/multicurrencies/invoices_payments.rst:120
msgid ":doc:`how_it_works`"
msgstr ""
@ -8113,7 +8099,7 @@ msgstr ""
#: ../../accounting/overview/getting_started/setup.rst:190
#: ../../accounting/payables/pay/sepa.rst:130
#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:64
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:151
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:146
msgid ":doc:`../../bank/setup/bank_accounts`"
msgstr ""
@ -11224,50 +11210,46 @@ msgid "To do so, open the invoice, click on *Register Payment*, and choose *SEPA
msgstr ""
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:107
msgid "In previous versions, Odoo used SDD payment as the default payment for all customers with an active mandate. Your customers can still activate automatic SDD for their subscriptions with a recurring payment."
msgstr ""
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:112
msgid "Generate SEPA Direct Debit XML files to submit payments"
msgstr ""
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:114
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:109
msgid "**XML files** with all SDD payment instructions can be uploaded to your online banking interface to process all payments at once."
msgstr ""
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:118
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:113
msgid "The files generated by Odoo follow the SEPA Direct Debit **PAIN.008.001.02** specifications, as required by the SEPA customer-to-bank Implementation Guidelines, which ensures compatibility with the banks."
msgstr ""
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:122
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:117
msgid "To generate your XML file for the pending SDD payments, go to the related *bank journal* on your *Accounting dashboard*, then click on *Direct Debit Payments to Collect*."
msgstr ""
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:129
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:124
msgid "Select all the payments you want to include in your SDD XML file, then click on *Action* and select *Create Batch Payment*."
msgstr ""
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:136
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:131
msgid "Odoo then takes you to your *Batch Payment*’s form. Click on *Validate* and download the SDD XML file."
msgstr ""
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:143
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:138
msgid "Finally, upload this file to your online banking interface to process the payments."
msgstr ""
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:146
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:141
msgid "You can retrieve all the generated SDD XML files by going to :menuselection:`Accounting --> Configuration --> Customers --> Batch Payments`."
msgstr ""
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:150
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:145
msgid ":doc:`batch`"
msgstr ""
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:152
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:147
msgid "`Odoo Academy: SEPA Direct Debit Mandates (SDD) <https://www.odoo.com/r/Zxs>`_"
msgstr ""
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:153
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:148
msgid "`List of all SEPA countries <https://www.europeanpaymentscouncil.eu/document-library/other/epc-list-sepa-scheme-countries>`_"
msgstr ""

4
locale/sources/crm.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-10-09 11:26+0200\n"
"POT-Creation-Date: 2020-11-02 12:05+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -618,7 +618,7 @@ msgid "Outlook warns you that Microsoft hasn’t verified the add-in. Click on *
msgstr ""
#: ../../crm/optimize/outlook_extension.rst:84
msgid "The *Odoo for Outlook* add-in is not listed in Outlook yet on Outlook's add-ins list. This is why it is currently necessary to install it as a *custom add-in*."
msgid "The *Odoo for Outlook* add-in is not listed yet on Outlook's add-ins list. This is why it is currently necessary to install it as a *custom add-in*."
msgstr ""
#: ../../crm/optimize/outlook_extension.rst:90

138
locale/sources/discuss.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-10-09 11:26+0200\n"
"POT-Creation-Date: 2020-11-02 12:05+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -57,170 +57,170 @@ msgid "You will find here below some useful information on how to integrate your
msgstr ""
#: ../../discuss/advanced/email_servers.rst:34
msgid "Office 365 email servers don't allow easily to send external emails from hosts like Odoo. Refer to the `Microsoft's documentation <https://support.office.com/en-us/article/How-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`__ to make it work."
msgid "Office 365 email servers don't easily allow to send external emails from hosts like Odoo. Refer to `Microsoft's documentation <https://support.office.com/en-us/article/How-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`__ to make it work."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:40
#: ../../discuss/advanced/email_servers.rst:39
msgid "How to manage outbound messages"
msgstr ""
#: ../../discuss/advanced/email_servers.rst:41
#: ../../discuss/advanced/email_servers.rst:40
msgid "As a system admin, go to :menuselection:`Settings --> General Settings` and check *External Email Servers*. Then, click *Outgoing Mail Servers* to create one and reference the SMTP data of your email server. Once all the information has been filled out, click on *Test Connection*."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:46
#: ../../discuss/advanced/email_servers.rst:45
msgid "Here is a typical configuration for a G Suite server."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:51
#: ../../discuss/advanced/email_servers.rst:50
msgid "Then set your email domain name in the General Settings."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:54
#: ../../discuss/advanced/email_servers.rst:53
msgid "If you get a ``[AUTHENTICATIONFAILED] Invalid credentials (Failure)`` warning when you *Test Connection* on a Gmail address, activate the *Less secure app access* option. A direct link can be `accessed here <https://myaccount.google.com/lesssecureapps?pli=1>`_."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:58
#: ../../discuss/advanced/email_servers.rst:57
msgid "In addition to that, enable the IMAP setting on your Gmail account."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:62
#: ../../discuss/advanced/email_servers.rst:61
msgid "Can I use an Office 365 server"
msgstr ""
#: ../../discuss/advanced/email_servers.rst:63
#: ../../discuss/advanced/email_servers.rst:62
msgid "You can use an Office 365 server if you run Odoo on-premise. Office 365 SMTP relays are not compatible with Odoo Online."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:66
#: ../../discuss/advanced/email_servers.rst:65
msgid "Please refer to `Microsoft's documentation <https://support.office.com/en-us/article/How-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`__ to configure a SMTP relay for your Odoo's IP address."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:70
#: ../../discuss/advanced/email_servers.rst:69
msgid "How to use a G Suite server"
msgstr ""
#: ../../discuss/advanced/email_servers.rst:71
#: ../../discuss/advanced/email_servers.rst:70
msgid "You can use an G Suite server for any Odoo hosting type. To do so you need to setup the SMTP relay service. The configuration steps are explained in `Google documentation <https://support.google.com/a/answer/2956491?hl=en>`__."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:78
#: ../../discuss/advanced/email_servers.rst:77
msgid "Be SPF-compliant"
msgstr ""
#: ../../discuss/advanced/email_servers.rst:79
#: ../../discuss/advanced/email_servers.rst:78
msgid "In case you use SPF (Sender Policy Framework) to increase the deliverability of your outgoing emails, don't forget to authorize Odoo as a sending host in your domain name settings. Here is the configuration for Odoo Online:"
msgstr ""
#: ../../discuss/advanced/email_servers.rst:83
#: ../../discuss/advanced/email_servers.rst:82
msgid "If no TXT record is set for SPF, create one with following definition: v=spf1 include:_spf.odoo.com ~all"
msgstr ""
#: ../../discuss/advanced/email_servers.rst:85
#: ../../discuss/advanced/email_servers.rst:84
msgid "In case a SPF TXT record is already set, add \"include:_spf.odoo.com\". e.g. for a domain name that sends emails via Odoo Online and via G Suite it could be: v=spf1 include:_spf.odoo.com include:_spf.google.com ~all"
msgstr ""
#: ../../discuss/advanced/email_servers.rst:89
#: ../../discuss/advanced/email_servers.rst:88
msgid "Find `here <https://www.mail-tester.com/spf/>`__ the exact procedure to create or modify TXT records in your own domain registrar."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:92
#: ../../discuss/advanced/email_servers.rst:91
msgid "Your new SPF record can take up to 48 hours to go into effect, but this usually happens more quickly."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:95
#: ../../discuss/advanced/email_servers.rst:94
msgid "Adding more than one SPF record for a domain can cause problems with mail delivery and spam classification. Instead, we recommend using only one SPF record by modifying it to authorize Odoo."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:100
#: ../../discuss/advanced/email_servers.rst:99
msgid "Allow DKIM"
msgstr ""
#: ../../discuss/advanced/email_servers.rst:101
#: ../../discuss/advanced/email_servers.rst:100
msgid "You should do the same thing if DKIM (Domain Keys Identified Mail) is enabled on your email server. In the case of Odoo Online & Odoo.sh, you should add a DNS \"odoo._domainkey\" CNAME record to \"odoo._domainkey.odoo.com\". For example, for \"foo.com\" they should have a record \"odoo._domainkey.foo.com\" that is a CNAME with the value \"odoo._domainkey.odoo.com\"."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:109
#: ../../discuss/advanced/email_servers.rst:108
msgid "Restriction"
msgstr ""
#: ../../discuss/advanced/email_servers.rst:110
#: ../../discuss/advanced/email_servers.rst:109
msgid "Please note that the port 25 is blocked for security reasons. Try using 587, 465 or 2525."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:113
#: ../../discuss/advanced/email_servers.rst:112
msgid "How to manage inbound messages"
msgstr ""
#: ../../discuss/advanced/email_servers.rst:115
#: ../../discuss/advanced/email_servers.rst:114
msgid "Odoo relies on generic email aliases to fetch incoming messages."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:117
#: ../../discuss/advanced/email_servers.rst:116
msgid "**Reply messages** of messages sent from Odoo are routed to their original discussion thread (and to the inbox of all its followers) by the catchall alias (**catchall@**)."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:121
#: ../../discuss/advanced/email_servers.rst:120
msgid "**Bounced messages** are routed to **bounce@** in order to track them in Odoo. This is especially used in `Odoo Email Marketing <https://www.odoo.com/page/email-marketing>`__ to opt-out invalid recipients."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:125
#: ../../discuss/advanced/email_servers.rst:124
msgid "**Original messages**: Several business objects have their own alias to create new records in Odoo from incoming emails:"
msgstr ""
#: ../../discuss/advanced/email_servers.rst:128
#: ../../discuss/advanced/email_servers.rst:127
msgid "Sales Channel (to create Leads or Opportunities in `Odoo CRM <https://www.odoo.com/page/crm>`__),"
msgstr ""
#: ../../discuss/advanced/email_servers.rst:130
#: ../../discuss/advanced/email_servers.rst:129
msgid "Support Channel (to create Tickets in `Odoo Helpdesk <https://www.odoo.com/page/helpdesk>`__),"
msgstr ""
#: ../../discuss/advanced/email_servers.rst:132
#: ../../discuss/advanced/email_servers.rst:131
msgid "Projects (to create new Tasks in `Odoo Project <https://www.odoo.com/page/project-management>`__),"
msgstr ""
#: ../../discuss/advanced/email_servers.rst:134
#: ../../discuss/advanced/email_servers.rst:133
msgid "Job Positions (to create Applicants in `Odoo Recruitment <https://www.odoo.com/page/recruitment>`__),"
msgstr ""
#: ../../discuss/advanced/email_servers.rst:136
#: ../../discuss/advanced/email_servers.rst:135
msgid "etc."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:138
#: ../../discuss/advanced/email_servers.rst:137
msgid "Depending on your mail server, there might be several methods to fetch emails. The easiest and most recommended method is to manage one email address per Odoo alias in your mail server."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:142
#: ../../discuss/advanced/email_servers.rst:141
msgid "Create the corresponding email addresses in your mail server (catchall@, bounce@, sales@, etc.)."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:144
#: ../../discuss/advanced/email_servers.rst:143
msgid "Set your domain name in the General Settings."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:149
#: ../../discuss/advanced/email_servers.rst:148
msgid "If you use Odoo on-premise, create an *Incoming Mail Server* in Odoo for each alias. You can do it from the General Settings as well. Fill out the form according to your email provider’s settings. Leave the *Actions to Perform on Incoming Mails* blank. Once all the information has been filled out, click on *TEST & CONFIRM*."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:158
#: ../../discuss/advanced/email_servers.rst:157
msgid "If you use Odoo Online or Odoo.sh, We do recommend to redirect incoming messages to Odoo's domain name rather than exclusively use your own email server. That way you will receive incoming messages without delay. Indeed, Odoo Online is fetching incoming messages of external servers once per hour only. You should set redirections for all the email addresses to Odoo's domain name in your email server (e.g. *catchall@mydomain.ext* to *catchall@mycompany.odoo.com*)."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:168
#: ../../discuss/advanced/email_servers.rst:167
msgid "All the aliases are customizable in Odoo."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:166
#: ../../discuss/advanced/email_servers.rst:165
msgid "Object aliases can be edited from their respective configuration view. To edit catchall and bounce aliases, you first need to activate the :doc:`Developer mode <../../general/developer_mode/activate>`."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:170
#: ../../discuss/advanced/email_servers.rst:169
msgid "Then go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` to customize the aliases (*mail.catchall.alias* & * mail.bounce.alias*)."
msgstr ""
#: ../../discuss/advanced/email_servers.rst:176
#: ../../discuss/advanced/email_servers.rst:175
msgid "By default inbound messages are fetched every 5 minutes in Odoo on-premise. You can change this value in :doc:`Developer mode <../../general/developer_mode/activate>`. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for *Mail: Fetchmail Service*."
msgstr ""
@ -293,91 +293,87 @@ msgid "Choose your notifications preference"
msgstr ""
#: ../../discuss/overview/get_started.rst:13
msgid "Access your *Preferences* and choose how you would like your :doc:`Chatter <../../project/tasks/collaborate>` notifications to be handled."
msgid "Access your *Preferences* and choose how you would like your notifications to be handled."
msgstr ""
#: ../../discuss/overview/get_started.rst:22
#: ../../discuss/overview/get_started.rst:21
msgid "By default, the field is set as *Handle by Emails* making messages, notes, and notifications where you were mentioned or that you follow, to be sent through email. By choosing *Handle in Odoo*, they are shown in the *Inbox*."
msgstr ""
#: ../../discuss/overview/get_started.rst:23
#: ../../discuss/overview/get_started.rst:22
msgid "Messages can then be *Marked as Todo*, *Replied*, or *Marked as Read*."
msgstr ""
#: ../../discuss/overview/get_started.rst:29
#: ../../discuss/overview/get_started.rst:28
msgid "The messages tagged as *Mark as Todo* are also shown in *Starred*, while the ones *Marked as Read* are moved to *History*."
msgstr ""
#: ../../discuss/overview/get_started.rst:37
#: ../../discuss/overview/get_started.rst:36
msgid "Start Chatting"
msgstr ""
#: ../../discuss/overview/get_started.rst:39
#: ../../discuss/overview/get_started.rst:38
msgid "The first time you log in to your account, OdooBot sends you a message asking for permission to receive desktop notifications to chats. If accepted, you receive push notifications to the messages sent to you despite of where you are in Odoo."
msgstr ""
#: ../../discuss/overview/get_started.rst:49
#: ../../discuss/overview/get_started.rst:48
msgid "To stop receiving desktop notifications, reset the notifications settings of your browser."
msgstr ""
#: ../../discuss/overview/get_started.rst:51
#: ../../discuss/overview/get_started.rst:50
msgid "To start a chat, click on *New Message* on the *Messaging Menu*, or go to *Discuss* and send a *Direct Message*."
msgstr ""
#: ../../discuss/overview/get_started.rst:59
#: ../../discuss/overview/get_started.rst:58
msgid "You can also create :doc:`public and private channels <team_communication>`."
msgstr ""
#: ../../discuss/overview/get_started.rst:62
#: ../../discuss/overview/get_started.rst:61
msgid "Mentions in the chat and on the Chatter"
msgstr ""
#: ../../discuss/overview/get_started.rst:65
msgid "To mention a user within a chat or the :doc:`chatter <../../project/tasks/collaborate>` type *@user-name*; to refer to a channel, type *#channel-name*."
#: ../../discuss/overview/get_started.rst:64
msgid "To mention a user within a chat or the chatter type *@user-name*; to refer to a channel, type *#channel-name*."
msgstr ""
#: ../../discuss/overview/get_started.rst:67
#: ../../discuss/overview/get_started.rst:66
msgid "A notification is sent to the user mentioned either to his *Inbox* or through email, depending on his settings."
msgstr ""
#: ../../discuss/overview/get_started.rst:74
msgid "When a user is mentioned, the search list (list of names) suggests values first based on the task’s :doc:`followers <../../project/tasks/collaborate>`, and secondly on *Employees*. If the record being searched does not match with either a follower or employee, the scope of the search becomes all partners."
#: ../../discuss/overview/get_started.rst:73
msgid "When a user is mentioned, the search list (list of names) suggests values first based on the task’s followers, and secondly on *Employees*. If the record being searched does not match with either a follower or employee, the scope of the search becomes all partners."
msgstr ""
#: ../../discuss/overview/get_started.rst:80
#: ../../discuss/overview/get_started.rst:78
msgid "Chat status"
msgstr ""
#: ../../discuss/overview/get_started.rst:82
#: ../../discuss/overview/get_started.rst:80
msgid "It is helpful to see what colleagues are up to and how quickly they can respond to messages by checking their *Status*. The status is shown on the left side of a contact’s names on Discuss’ sidebar and on the *Messaging menu*."
msgstr ""
#: ../../discuss/overview/get_started.rst:86
#: ../../discuss/overview/get_started.rst:84
msgid "Green = online"
msgstr ""
#: ../../discuss/overview/get_started.rst:87
#: ../../discuss/overview/get_started.rst:85
msgid "Orange = away"
msgstr ""
#: ../../discuss/overview/get_started.rst:88
#: ../../discuss/overview/get_started.rst:86
msgid "White = offline"
msgstr ""
#: ../../discuss/overview/get_started.rst:89
#: ../../discuss/overview/get_started.rst:87
msgid "Airplane = out of the office"
msgstr ""
#: ../../discuss/overview/get_started.rst:97
msgid ":doc:`../../project/tasks/collaborate`"
msgstr ""
#: ../../discuss/overview/get_started.rst:98
#: ../../discuss/overview/get_started.rst:95
#: ../../discuss/overview/plan_activities.rst:65
msgid ":doc:`team_communication`"
msgstr ""
#: ../../discuss/overview/get_started.rst:99
#: ../../discuss/overview/get_started.rst:96
msgid ":doc:`../advanced/email_servers`"
msgstr ""
@ -402,7 +398,7 @@ msgid "Plan activities"
msgstr ""
#: ../../discuss/overview/plan_activities.rst:22
msgid "Activities can be planned and managed from the :doc:`Chatter <../../project/tasks/collaborate>` by clicking on *Schedule activity*, or through Kanban views."
msgid "Activities can be planned and managed from the chatter by clicking on *Schedule activity*, or through Kanban views."
msgstr ""
#: ../../discuss/overview/plan_activities.rst:31

103
locale/sources/general.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-10-09 11:26+0200\n"
"POT-Creation-Date: 2020-11-02 12:05+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1382,6 +1382,7 @@ msgid "SIPS"
msgstr ""
#: ../../general/payment_acquirers/payment_acquirers.rst:71
#: ../../general/payment_acquirers/stripe.rst:3
msgid "Stripe"
msgstr ""
@ -1749,6 +1750,50 @@ msgstr ""
msgid "Run a test transaction from Odoo using the sandbox personal account."
msgstr ""
#: ../../general/payment_acquirers/stripe.rst:5
msgid "`Stripe <https://stripe.com/>`_ is a United States-based online payment solution provider, allowing businesses to accept **credit cards** and other payment methods."
msgstr ""
#: ../../general/payment_acquirers/stripe.rst:9
msgid "Enable Local Payment Methods"
msgstr ""
#: ../../general/payment_acquirers/stripe.rst:11
msgid "Local payment methods are payment methods that are only available for certain merchants and customers countries and currencies."
msgstr ""
#: ../../general/payment_acquirers/stripe.rst:14
msgid "The Stripe connector in Odoo supports the following local payment methods:"
msgstr ""
#: ../../general/payment_acquirers/stripe.rst:16
msgid "Bancontact"
msgstr ""
#: ../../general/payment_acquirers/stripe.rst:17
msgid "EPS"
msgstr ""
#: ../../general/payment_acquirers/stripe.rst:18
msgid "Giropay"
msgstr ""
#: ../../general/payment_acquirers/stripe.rst:19
msgid "iDeal:"
msgstr ""
#: ../../general/payment_acquirers/stripe.rst:20
msgid "Przelewy24 (P24)"
msgstr ""
#: ../../general/payment_acquirers/stripe.rst:22
msgid "To enable specific Local Payment Methods with Stripe, list them as supported payment icons. To do so, go to :menuselection:`Payment Acquirers --> Stripe --> Configuration` and add the desired payment methods in the **Supported Payment Icons** field. If the desired payment method is already listed, you don't have anything to do."
msgstr ""
#: ../../general/payment_acquirers/stripe.rst:31
msgid "If a payment method icon doesn't exist at all in the database, the corresponding local payment method is always offered to customers."
msgstr ""
#: ../../general/payment_acquirers/wire_transfer.rst:3
msgid "How to get paid with wire transfers"
msgstr ""
@ -1785,62 +1830,6 @@ msgstr ""
msgid "If you manage a B2B business, you can create other manually-processed payment methods like paying by check. To do so, just rename *Wire Transfer* or duplicate it."
msgstr ""
#: ../../general/tags.rst:3
msgid "Tags"
msgstr ""
#: ../../general/tags/take_tags.rst:3
msgid "Take Advantage of Tags"
msgstr ""
#: ../../general/tags/take_tags.rst:5
msgid "Tags work like keywords or labels that will help you to categorize your work, as well as make objectives and goals clearer and available for everyone instantly. They are also a useful source of filtering, helping you to boost productivity."
msgstr ""
#: ../../general/tags/take_tags.rst:11
msgid "Where can I use and how do I create tags?"
msgstr ""
#: ../../general/tags/take_tags.rst:14
msgid "Tags can be used in numerous applications going from *CRM*, *Project*, *Contacts*, *Marketing Automation*, etc."
msgstr ""
#: ../../general/tags/take_tags.rst:16
msgid "On *CRM* for instance, under :menuselection:`CRM --> Configuration --> Tags` you can create new or edit existing ones."
msgstr ""
#: ../../general/tags/take_tags.rst:23
msgid "You can also create them on the fly."
msgstr ""
#: ../../general/tags/take_tags.rst:29
msgid "Choose specific colors for each tag to help identify them, or *Hide in Kanban*, simply by clicking on the tag once it is created."
msgstr ""
#: ../../general/tags/take_tags.rst:38
msgid "Remove tags from a task or from the database"
msgstr ""
#: ../../general/tags/take_tags.rst:40
msgid "Click on the *x* to delete a tag from a specific task or contact. To delete it from your database, go to :menuselection:`CRM --> Configuration --> Tags --> Action --> Delete`."
msgstr ""
#: ../../general/tags/take_tags.rst:48
msgid "Use tags as a parameter"
msgstr ""
#: ../../general/tags/take_tags.rst:50
msgid "On the *Marketing Automation* application, for example, you can re-use tags as a parameter to specify a niche of records for your campaign."
msgstr ""
#: ../../general/tags/take_tags.rst:59
msgid "Use tags for reporting"
msgstr ""
#: ../../general/tags/take_tags.rst:61
msgid "To get the information you need in an organized format and for a specific purpose, you can also add tags."
msgstr ""
#: ../../general/unsplash.rst:3
msgid "Unsplash"
msgstr ""

6
locale/sources/helpdesk.pot
View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"POT-Creation-Date: 2020-11-02 12:05+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -280,7 +280,7 @@ msgid "Now, once a ticket reaches the stage(s) designated as the *Closing Stage*
msgstr ""
#: ../../helpdesk/overview/ratings.rst:35
msgid "Ratings can be seen on the :doc:`chatter <../../project/tasks/collaborate>` of each ticket, under the *See Customer Satisfaction* link on the main dashboard, and through *Reporting*."
msgid "Ratings can be seen on the chatter of each ticket, under the *See Customer Satisfaction* link on the main dashboard, and through *Reporting*."
msgstr ""
#: ../../helpdesk/overview/ratings.rst:39

388
locale/sources/iot.pot
View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"POT-Creation-Date: 2020-11-02 12:05+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -109,47 +109,27 @@ msgid "In some case, you may need to reflash your IoT Box’s SD Card to benefit
msgstr ""
#: ../../iot/config/flash_sdcard.rst:9
msgid "Updating your SD Card with Etcher"
msgid "Upgrade from the IoT Box homepage"
msgstr ""
#: ../../iot/config/flash_sdcard.rst:11
msgid "Go to Balena’s website and download `Etcher <https://www.balena.io/>`__, It’s a free and open-source utility used for burning image files. Install and launch it."
msgid "Go to the IoT Box homepage, click on *Update*, next to the version number. If a new version of the IoT Box image is available, you will see a *Upgrade to ___* button a the bottom of the page, the IoT Box will then flash itself to the new version of the IoT Box. All of your configurations will be saved."
msgstr ""
#: ../../iot/config/flash_sdcard.rst:15
msgid "Now, download the latest image `here <http://nightly.odoo.com/master/posbox/iotbox/>`__, and extract it from the zip file. Then, open *Etcher* and select the image. Select the drive to flash (where your SD Card is) and click on *Flash*!."
#: ../../iot/config/flash_sdcard.rst:18
msgid "This process can take more than 30 minutes. Do not turn off or unplug the IoT Box as it would leave it in an inconsistent state."
msgstr ""
#: ../../iot/config/flash_sdcard.rst:19
msgid "Now, your image will be automatically updated. You just have to wait 5 minutes for it to finish."
#: ../../iot/config/flash_sdcard.rst:25
msgid "Upgrade with Etcher"
msgstr ""
#: ../../iot/config/iot_notfound.rst:3
msgid "IoT Box not found"
#: ../../iot/config/flash_sdcard.rst:27
msgid "Go to Balena’s website and download `Etcher <https://www.balena.io/>`__. It’s a free and open-source utility used for burning image files. Install and launch it. Download the latest image from `nightly <http://nightly.odoo.com/master/iotbox/>`__."
msgstr ""
#: ../../iot/config/iot_notfound.rst:5
msgid "When using your IoT Box, a common issue you might encounter is that your box is not found on your database. Fortunately, there are a few easy steps you can follow to find your IoT box."
msgstr ""
#: ../../iot/config/iot_notfound.rst:10
msgid "HTTPS Issues"
msgstr ""
#: ../../iot/config/iot_notfound.rst:12
msgid "Your IoT Box is not found? You probably have https issues!"
msgstr ""
#: ../../iot/config/iot_notfound.rst:14
msgid "To check it, go to your database and verify if your database address starts with an https (like https://www.odoo.com). If this is the case, then you may have problems with your IoT Box image. It should be version 18.12 or later."
msgstr ""
#: ../../iot/config/iot_notfound.rst:19
msgid "If your IoT Box image is from an earlier version, then you will have to reflash the SD card of your IoT Box to update the image (the latest image can be found `here <http://nightly.odoo.com/master/posbox/iotbox/>`__)."
msgstr ""
#: ../../iot/config/iot_notfound.rst:24
msgid ":doc:`flash_sdcard`"
#: ../../iot/config/flash_sdcard.rst:32
msgid "Then, open *Etcher* and select *Flash from file*, find the image you just downloaded. Insert the IoT Box SD card into your computer and select it. Click on *Flash* and wait for the process to finish."
msgstr ""
#: ../../iot/config/pos.rst:3
@ -165,183 +145,211 @@ msgid "Before starting, make sure you have the following:"
msgstr ""
#: ../../iot/config/pos.rst:13
msgid "An IoT Box"
msgid "An IoT Box, with its power adapter."
msgstr ""
#: ../../iot/config/pos.rst:15
msgid "A 2A Power adapter with pi 3 b+ 2.5 A"
msgstr ""
#: ../../iot/config/pos.rst:17
msgid "A computer or tablet with an up-to-date web browser"
msgstr ""
#: ../../iot/config/pos.rst:19
#: ../../iot/config/pos.rst:17
msgid "A running SaaS or Odoo instance with the Point of Sale and IoT apps installed"
msgstr ""
#: ../../iot/config/pos.rst:22
#: ../../iot/config/pos.rst:20
msgid "A local network setup with DHCP (this is the default setting)"
msgstr ""
#: ../../iot/config/pos.rst:24
msgid "An Epson USB TM-T20 Printer or another ESC/POS compatible printer (officially supported printers are listed at the `POS Hardware page <https://www.odoo.com/page/pos-ipad-android-hardware>`__)"
msgstr ""
#: ../../iot/config/pos.rst:28
msgid "A Honeywell Eclipse USB Barcode Scanner or another compatible scanner"
msgstr ""
#: ../../iot/config/pos.rst:30
msgid "An Epson compatible cash drawer"
msgstr ""
#: ../../iot/config/pos.rst:32
#: ../../iot/config/pos.rst:22
msgid "An RJ45 Ethernet Cable (optional, WiFi is built in)"
msgstr ""
#: ../../iot/config/pos.rst:35
#: ../../iot/config/pos.rst:24
msgid "Any of the supported hardware (receipt printer, barcode scanner, cash drawer, payment terminal, scale, customer display, etc.). The list of supported hardware can be found on the `POS Hardware page <https://www.odoo.com/page/point-of-sale-hardware>`__"
msgstr ""
#: ../../iot/config/pos.rst:30
msgid "Set Up"
msgstr ""
#: ../../iot/config/pos.rst:37
#: ../../iot/config/pos.rst:32
msgid "To connect hardware to the PoS, the first step is to connect an IoT Box to your database. For this, follow this :doc:`documentation <connect>`."
msgstr ""
#: ../../iot/config/pos.rst:44
#: ../../iot/config/pos.rst:36
msgid "Then, you have to connect the peripheral devices to your IoT Box."
msgstr ""
#: ../../iot/config/pos.rst:46
msgid "Officially supported hardware is listed on `the POS Hardware page <https://www.odoo.com/page/pos-ipad-android-hardware>`__, but other hardware might work as well."
#: ../../iot/config/pos.rst:38
msgid "**Printer**: Connect a supported receipt printer to a USB port or to the network and power it on."
msgstr ""
#: ../../iot/config/pos.rst:50
msgid "**Printer**: Connect an ESC/POS printer to a USB port and power it on."
msgstr ""
#: ../../iot/config/pos.rst:53
#: ../../iot/config/pos.rst:41
msgid "**Cash drawer**: The cash drawer should be connected to the printer with an RJ25 cable."
msgstr ""
#: ../../iot/config/pos.rst:56
msgid "**Barcode scanner**: Connect your barcode scanner. In order for your barcode scanner to be compatible it must behave as a keyboard and must be configured in **US QWERTY**. It also must end barcodes with an Enter character (keycode 28). This is most likely the default configuration of your barcode scanner."
#: ../../iot/config/pos.rst:44
msgid "**Barcode scanner**: Connect your barcode scanner. In order for your barcode scanner to be compatible it must end barcodes with an Enter character (keycode 28). This is most likely the default configuration of your barcode scanner."
msgstr ""
#: ../../iot/config/pos.rst:62
#: ../../iot/config/pos.rst:49
msgid "**Scale**: Connect your scale and power it on."
msgstr ""
#: ../../iot/config/pos.rst:64
msgid "**Ethernet**: If you do not wish to use Wi-Fi, plug in the Ethernet cable. Make sure this will connect the IoT Box to the same network as your POS device."
#: ../../iot/config/pos.rst:51
msgid "**Customer Display**: Connect a monitor to the IoT Box using an HDMI cable. You can also access the Customer Display from any other computer by accessing the IoT Box homepage and clicking on the *POS Display* button."
msgstr ""
#: ../../iot/config/pos.rst:56
msgid "**Payment terminal**: The connection process depends on the terminal, please refer to the :doc:`payment terminals documentation <../../point_of_sale/payment>`."
msgstr ""
#: ../../iot/config/pos.rst:60
msgid "Once it's done, you can connect the IoT Box to your PoS. For this, go in :menuselection:`Point of Sale --> Configuration --> PoS`, tick *IoT Box* and select the devices you want to use in this Point of Sale. Save the changes."
msgstr ""
#: ../../iot/config/pos.rst:68
msgid "**Wi-Fi**: The current version of the IoT Box has Wi-Fi built in. Make sure not to plug in an Ethernet cable when booting, because all Wi-Fi functionality will be bypassed when a wired network connection is available on boot."
msgstr ""
#: ../../iot/config/pos.rst:73
msgid "Once it's done, you can connect the IoT Box to your PoS. For this, go in :menuselection:`Point of Sale --> Configuration --> PoS`, tick the box \"IoT Box\" and select the IoT Box you want to connect with. Save the changes."
msgstr ""
#: ../../iot/config/pos.rst:77
msgid "Set up is done, you can launch a new PoS Session."
msgstr ""
#: ../../iot/config/pos.rst:80
msgid "Troubleshoot"
#: ../../iot/config/troubleshooting.rst:3
msgid "Troubleshooting"
msgstr ""
#: ../../iot/config/pos.rst:83
msgid "The PoS cannot connect to the IoT Box"
#: ../../iot/config/troubleshooting.rst:6
msgid "IoT Box Connection"
msgstr ""
#: ../../iot/config/pos.rst:85
msgid "The easiest way to make sure the IoT Box is properly set-up is to turn it on with the printer plugged in as it will print a receipt indicating any error if encountered or the IoT Box's IP address in case of success. If no receipt is printed, check the following steps:"
#: ../../iot/config/troubleshooting.rst:9
msgid "I can't find the pairing code to connect my IoT Box"
msgstr ""
#: ../../iot/config/pos.rst:91
msgid "Make sure the IoT Box is powered on, indicated by a brightly lit red status LED."
#: ../../iot/config/troubleshooting.rst:11
msgid "The pairing code should be printed on receipt printers connected to the IoT Box and should also be displayed on connected monitors."
msgstr ""
#: ../../iot/config/pos.rst:94
msgid "Make sure the IoT Box is ready, this is indicated by a brightly lit green status LED just next to the red power status LED. The IoT Box should be ready ~2 minutes after it is started."
#: ../../iot/config/troubleshooting.rst:14
msgid "The pairing code doesn't show under the following circumstances:"
msgstr ""
#: ../../iot/config/pos.rst:98
msgid "Make sure the IoT Box is connected to the same network as your POS device. Both the device and the IoT Box should be visible in the list of connected devices on your network router."
#: ../../iot/config/troubleshooting.rst:16
msgid "The IoT Box is already connected to an Odoo database;"
msgstr ""
#: ../../iot/config/pos.rst:102
msgid "If you specified the IoT Box's IP address in the configuration, make sure it corresponds to the ip address printed on the IoT Box's status receipt."
#: ../../iot/config/troubleshooting.rst:18
msgid "The IoT Box is not connected to the Internet;"
msgstr ""
#: ../../iot/config/pos.rst:106
msgid "Make sure that the POS is not loaded over HTTPS."
#: ../../iot/config/troubleshooting.rst:20
msgid "The code is only valid for 5 minutes after the IoT Box has started. It's automatically removed from connected displays when this delay has expired;"
msgstr ""
#: ../../iot/config/pos.rst:108
msgid "A bug in Firefox's HTTP implementation might prevent the autodiscovery from working reliably. You could also manually set up the IoT Box's IP address in the POS configuration."
#: ../../iot/config/troubleshooting.rst:23
msgid "The version of the IoT Box image is too old. It should use version 20.06 or more recent. If your IoT Box image is from an earlier version, then you will have to reflash the SD card of your IoT Box to update the image (see :doc:`Flashing your SD Card <flash_sdcard>`)"
msgstr ""
#: ../../iot/config/pos.rst:113
msgid "The Barcode Scanner is not working"
#: ../../iot/config/troubleshooting.rst:28
msgid "If you are not in any of the cases listed above, make sure that the IoT Box has correctly started, by checking that a fixed green LED is showing next to the micro-USB port."
msgstr ""
#: ../../iot/config/pos.rst:115
msgid "The barcode scanner must be configured in US QWERTY and emit an Enter after each barcode. This is the default configuration of most barcode readers. Refer to the barcode reader documentation for more information."
#: ../../iot/config/troubleshooting.rst:33
msgid "I've connected my IoT Box but it's not showing in my database"
msgstr ""
#: ../../iot/config/pos.rst:120
msgid "The IoT Box needs a 2A power supply to work with some barcode scanners. If you are not using the provided power supply, make sure the one you use has enough power."
#: ../../iot/config/troubleshooting.rst:35
msgid "When you connect an IoT Box to a database, the IoT Box might restart, if that is the case, it might take up to one minute before appearing in your database. If after some time the IoT is still not showing, make sure that your database can be reached from the IoT Box and that your server doesn't use a multi-database environment."
msgstr ""
#: ../../iot/config/pos.rst:124
msgid "Some barcode scanners will need more than 2A and will not work, or will work unreliably, even with the provided power supply. In those case you can plug the barcode scanner in a self-powered USB hub."
#: ../../iot/config/troubleshooting.rst:42
msgid "My IoT Box is connected to my database, but cannot be reached"
msgstr ""
#: ../../iot/config/pos.rst:129
msgid "Some poorly built barcode scanners do not advertise themselves as barcode scanners but as a usb keyboard instead, and will not be recognized by the IoT Box."
#: ../../iot/config/troubleshooting.rst:44
msgid "Make sure that the IoT Box and the device running the browser are located on the same network as the IoT Box cannot be reached from outside the local network."
msgstr ""
#: ../../iot/config/pos.rst:134
msgid "The Barcode Scanner is not working reliably"
#: ../../iot/config/troubleshooting.rst:49
msgid "Printer"
msgstr ""
#: ../../iot/config/pos.rst:136
msgid "Make sure that no more than one device with 'Scan via Proxy'/'Barcode Scanner' enabled are connected to the IoT Box at the same time."
#: ../../iot/config/troubleshooting.rst:52
msgid "My printer is not detected"
msgstr ""
#: ../../iot/config/pos.rst:140
msgid "Printing the receipt takes too much time"
#: ../../iot/config/troubleshooting.rst:54
msgid "If one of your printers doesn't show up in your devices list, go to the IoT Box homepage and make sure that it is listed under *Printers*."
msgstr ""
#: ../../iot/config/pos.rst:142
msgid "A small delay before the first print is expected, as the IoT Box will do some preprocessing to speed up the next printings. If you suffer delays afterwards it is most likely due to poor network connection between the POS and the IoT Box."
#: ../../iot/config/troubleshooting.rst:60
msgid "If your printer is not present on the IoT Box homepage, hit *Printers Server*, go to the *Administration* tab and click on *Add Printer*. If you can't find your printer in the list, it's probably not connected properly."
msgstr ""
#: ../../iot/config/pos.rst:148
msgid "Some characters are not correctly printed on the receipt"
#: ../../iot/config/troubleshooting.rst:66
msgid "My printer outputs random text"
msgstr ""
#: ../../iot/config/pos.rst:150
msgid "The IoT Box does not support all languages and characters. It currently supports Latin and Cyrillic based scripts, with basic Japanese support."
#: ../../iot/config/troubleshooting.rst:68
msgid "For most printers, the correct driver should be automatically detected and selected. However, in some cases, the automatic detection mechanism might not be enough, and if no driver is found the printer might print random characters."
msgstr ""
#: ../../iot/config/pos.rst:155
msgid "The printer is offline"
#: ../../iot/config/troubleshooting.rst:73
msgid "The solution is to manually select the corresponding driver. On the IoT Box homepage, click on *Printers Server*, go to the *Printers* tab and select the printer in the list. In the Administration dropdown, click on *Modify Printer*. Follow the steps and select the Make and Model corresponding to your printer."
msgstr ""
#: ../../iot/config/pos.rst:157
msgid "Make sure the printer is connected, powered, has enough paper and has its lid closed, and is not reporting an error. If the error persists, please contact support."
#: ../../iot/config/troubleshooting.rst:83
msgid "Epson and Star receipt printers and Zebra label printers do not need a driver to work. Make sure that no driver is selected for those printers."
msgstr ""
#: ../../iot/config/pos.rst:162
#: ../../iot/config/troubleshooting.rst:88
msgid "My Zebra Printer doesn't print anything"
msgstr ""
#: ../../iot/config/troubleshooting.rst:90
msgid "Zebra printers are quite sensitive to the format of the ZPL code that is printed. If nothing comes out of the printer or blank labels are printed, try changing the format of the report that is sent to the printer by accessing :menuselection:`Settings ~~> Technical ~~> Views` in developer mode and look for the corresponding template."
msgstr ""
#: ../../iot/config/troubleshooting.rst:97
msgid "Barcode Scanner"
msgstr ""
#: ../../iot/config/troubleshooting.rst:100
msgid "The characters read by the barcode scanner don't match the barcode"
msgstr ""
#: ../../iot/config/troubleshooting.rst:102
msgid "By default, we assume that your barcode scanner is configured in US QWERTY. This is the default configuration of most barcode readers. If your barcode scanner uses a different layout, please go to the form view of your device and select the correct one."
msgstr ""
#: ../../iot/config/troubleshooting.rst:108
msgid "Nothing happens when a barcode is scanned"
msgstr ""
#: ../../iot/config/troubleshooting.rst:110
msgid "Make sure that the correct device is selected in your Point of Sale configuration and that your barcode is configured to send an ENTER character (keycode 28) at the end of every barcode."
msgstr ""
#: ../../iot/config/troubleshooting.rst:115
msgid "The barcode scanner is detected as a keyboard"
msgstr ""
#: ../../iot/config/troubleshooting.rst:117
msgid "Some poorly built barcode scanners do not advertise themselves as barcode scanners but as a USB keyboard instead, and will not be recognized by the IoT Box."
msgstr ""
#: ../../iot/config/troubleshooting.rst:121
msgid "You can manually change the device type by going to its form view and activating the *Is scanner* option."
msgstr ""
#: ../../iot/config/troubleshooting.rst:128
msgid "Cashdrawer"
msgstr ""
#: ../../iot/config/troubleshooting.rst:131
msgid "The cashdrawer does not open"
msgstr ""
#: ../../iot/config/pos.rst:164
msgid "The cashdrawer should be connected to the printer and should be activated in the POS configuration."
#: ../../iot/config/troubleshooting.rst:133
msgid "The cashdrawer should be connected to the printer and the *Cashdrawer* checkbox should be ticked in the POS configuration."
msgstr ""
#: ../../iot/devices.rst:3
@ -363,39 +371,31 @@ msgid "Connection"
msgstr ""
#: ../../iot/devices/camera.rst:14
msgid "To connect the camera to the *IoT Box*, simply combine the two by cable."
msgid "To connect the camera to the *IoT Box*, simply connect the two by cable."
msgstr ""
#: ../../iot/devices/camera.rst:18
msgid "In some cases, a serial to USB adapter could be needed."
msgstr ""
#: ../../iot/devices/camera.rst:20
#: ../../iot/devices/camera.rst:17
msgid "If your camera is a `*supported one* <https://www.odoo.com/page/iot-hardware>`__, there is no need to set up anything as it will be detected as soon as it is connected."
msgstr ""
#: ../../iot/devices/camera.rst:27
msgid "In some cases, you could need to restart the box and download your camera’s drivers from the box. To do so, go to your *IoT Box Home Page* and click on *drivers list*. Then, click on load drivers."
msgstr ""
#: ../../iot/devices/camera.rst:35
#: ../../iot/devices/camera.rst:25
msgid "Link a Camera to a Quality Control Point"
msgstr ""
#: ../../iot/devices/camera.rst:38
#: ../../iot/devices/measurement_tool.rst:42
#: ../../iot/devices/camera.rst:28
#: ../../iot/devices/measurement_tool.rst:34
msgid "With the Manufacturing app"
msgstr ""
#: ../../iot/devices/camera.rst:40
#: ../../iot/devices/camera.rst:30
msgid "In your *Quality app*, you can setup the device on a *Quality Control Point*. Go to the *Control Points* menu, under *Quality Control* and open the control point you want to link with the camera."
msgstr ""
#: ../../iot/devices/camera.rst:44
#: ../../iot/devices/camera.rst:34
msgid "Now, you can edit the control point and select the device from the dropdown list. Now, hit save."
msgstr ""
#: ../../iot/devices/camera.rst:50
#: ../../iot/devices/camera.rst:40
msgid "Then, your camera can be used with the picked *Control Point*. During the manufacturing process, reaching the *Quality Control Point* you chose before will allow you to take a picture."
msgstr ""
@ -408,38 +408,30 @@ msgid "When working, it is always better to have your two hands available. Using
msgstr ""
#: ../../iot/devices/footswitch.rst:8
msgid "In fact, you will be able to go from one screen to another by using your foot and the footswitch. Really convenient, it can be configured in a few steps."
msgid "In fact, you will be able to go from one screen to another and perform actions by using your foot and the footswitch. Really convenient, it can be configured in a few steps."
msgstr ""
#: ../../iot/devices/footswitch.rst:15
msgid "Connecting the footswitch to the *IoT Box* is easy, you just have to combine the two by cable."
msgid "Connecting the footswitch to the *IoT Box* is easy, you just have to connect the two by cable."
msgstr ""
#: ../../iot/devices/footswitch.rst:19
msgid "In some cases, a serial to USB adapter may be needed."
msgstr ""
#: ../../iot/devices/footswitch.rst:21
#: ../../iot/devices/footswitch.rst:18
msgid "If your footswitch is a `supported one <https://www.odoo.com/page/iot-hardware>`__, there is no need to set up anything since it will be automatically detected when connected."
msgstr ""
#: ../../iot/devices/footswitch.rst:28
msgid "If it is not a supported one, you may need to restart the box and download your footswitch’s drivers from the box. To do so, go to the *IoT Box Home Page* and click on *drivers list*. Then, click on load drivers."
msgstr ""
#: ../../iot/devices/footswitch.rst:37
#: ../../iot/devices/footswitch.rst:26
msgid "Link a Footswitch to a Workcenter"
msgstr ""
#: ../../iot/devices/footswitch.rst:39
#: ../../iot/devices/footswitch.rst:28
msgid "To link the footswitch to an action, it needs to be configured on a workcenter. Go to the workcenter you want to use the footswitch in and add the device in the *IoT Triggers* tab. Then, you can link it to an action and also add a key to trigger it."
msgstr ""
#: ../../iot/devices/footswitch.rst:47
#: ../../iot/devices/footswitch.rst:36
msgid "Note that the one that is first in the list will be chosen. So, the order matters! In the picture above, using the footswitch will, for example, automatically skip the current part of the process you work on."
msgstr ""
#: ../../iot/devices/footswitch.rst:52
#: ../../iot/devices/footswitch.rst:41
msgid "When you are on the work order screen, a status button indicates if you are correctly connected to the footswitch."
msgstr ""
@ -456,38 +448,34 @@ msgid "Connect in USB"
msgstr ""
#: ../../iot/devices/measurement_tool.rst:12
msgid "To add a device connected by USB, just plug the USB cable in the *IoT Box*, restart the Box and the device should appear in your Odoo database."
msgid "To add a device connected by USB, just plug the USB cable in the *IoT Box*, and the device should appear in your Odoo database."
msgstr ""
#: ../../iot/devices/measurement_tool.rst:19
msgid "If the device is not found, make sure the drivers have well been loaded on your IoT Box. For this, connect to the *IoT Box Homepage* and click on load drivers."
msgstr ""
#: ../../iot/devices/measurement_tool.rst:27
msgid "Connect in Bluetooth"
msgstr ""
#: ../../iot/devices/measurement_tool.rst:29
#: ../../iot/devices/measurement_tool.rst:21
msgid "Activate the Bluetooth on your device (see your device manual for further explanation) and the IoT Box will automatically try to connect to the device."
msgstr ""
#: ../../iot/devices/measurement_tool.rst:33
#: ../../iot/devices/measurement_tool.rst:25
msgid "Here is an example of what it should look like:"
msgstr ""
#: ../../iot/devices/measurement_tool.rst:39
#: ../../iot/devices/measurement_tool.rst:31
msgid "Link a measurement tool to a quality control point"
msgstr ""
#: ../../iot/devices/measurement_tool.rst:44
#: ../../iot/devices/measurement_tool.rst:36
msgid "In your *Quality app*, you can setup a device on your *Quality Control Points*. To do so, go to the *Control Points* menu, under *Quality Control* and open the control point to which you want to assign a measurement tool."
msgstr ""
#: ../../iot/devices/measurement_tool.rst:49
#: ../../iot/devices/measurement_tool.rst:41
msgid "Now, you can edit the control point and choose the device from the dropdown list. Then, hit save."
msgstr ""
#: ../../iot/devices/measurement_tool.rst:55
#: ../../iot/devices/measurement_tool.rst:47
msgid "Now, your measurement tool is linked to the chosen *Control Point*. The value, which needs to be changed manually, will be automatically updated while the tool is being used."
msgstr ""
@ -500,110 +488,98 @@ msgid "When using your *IoT Box* in Odoo, you could need to use a printer. Doing
msgstr ""
#: ../../iot/devices/printer.rst:13
msgid "To connect the printer to the *IoT Box*, you just have to combine the two by cable."
msgid "The IoT Box supports printers connected through USB, network or Bluetooth. `Supported printers <https://www.odoo.com/page/iot-hardware>`__ will be detected automatically and will appear in the *Devices* list of your IoT app."
msgstr ""
#: ../../iot/devices/printer.rst:17
msgid "Sometimes, a serial to USB adapter may be needed."
msgstr ""
#: ../../iot/devices/printer.rst:19
msgid "If your printer is a `supported one <https://www.odoo.com/page/iot-hardware>`__, there is no need to set up anything because it will be automatically detected as soon as it is connected."
msgstr ""
#: ../../iot/devices/printer.rst:24
#: ../../iot/devices/printer.rst:18
msgid "The printer can take up to two minutes to appear in your devices list."
msgstr ""
#: ../../iot/devices/printer.rst:29
msgid "In some cases, you may need to restart the box and download your printer’s drivers from the box. To do so, go to the *IoT Box Home Page* and click on *drivers list*. Then, click on load drivers."
msgstr ""
#: ../../iot/devices/printer.rst:37
#: ../../iot/devices/printer.rst:24
msgid "Link the Printer"
msgstr ""
#: ../../iot/devices/printer.rst:40
#: ../../iot/devices/printer.rst:27
msgid "To Work Orders"
msgstr ""
#: ../../iot/devices/printer.rst:42
#: ../../iot/devices/printer.rst:29
msgid "You can link *Work Orders* to printers via a *Quality Control Point* to print labels for manufactured products."
msgstr ""
#: ../../iot/devices/printer.rst:45
#: ../../iot/devices/printer.rst:32
msgid "To do so, you need to create a *Quality Control Point* from the *Quality* app. Then, you can select the correct manufacturing operation and the work order operation. In type, choose *Print Label* and hit save."
msgstr ""
#: ../../iot/devices/printer.rst:53
#: ../../iot/devices/printer.rst:40
msgid "Now, each time you reach the quality control point for the chosen product, a *Print Label* button will appear."
msgstr ""
#: ../../iot/devices/printer.rst:60
#: ../../iot/devices/printer.rst:47
msgid "To Reports"
msgstr ""
#: ../../iot/devices/printer.rst:62
#: ../../iot/devices/printer.rst:49
msgid "You can also link a type of report to a certain printer. In the *IoT* app, go to the *Devices* menu and select the printer you want to set up."
msgstr ""
#: ../../iot/devices/printer.rst:69
#: ../../iot/devices/printer.rst:56
msgid "Now, go to the *Printer Reports* tab."
msgstr ""
#: ../../iot/devices/printer.rst:74
#: ../../iot/devices/printer.rst:61
msgid "Hit edit and then, click on *Add a line*. In the window that shows up, check all the types of reports that should be linked to this printer. Click on select and save."
msgstr ""
#: ../../iot/devices/printer.rst:81
#: ../../iot/devices/printer.rst:68
msgid "Now, each time you click on *Print* in the control panel, instead of downloading a PDF, it will send it to the selected printer and automatically print it."
msgstr ""
#: ../../iot/devices/printer.rst:86
#: ../../iot/devices/printer.rst:73
msgid "Print Receipts from the PoS"
msgstr ""
#: ../../iot/devices/printer.rst:88
#: ../../iot/devices/printer.rst:75
msgid "You can link a printer to your *Point of Sale* app so you can print receipts directly from your *PoS*."
msgstr ""
#: ../../iot/devices/printer.rst:91
msgid "Doing so is really easy. Go to your *Point of Sale* app and open your *PoS* settings, under *Configuration*. There, click on *Edit* and check the *IoT Box* feature. Then, enable the *Receipt Printer*."
#: ../../iot/devices/printer.rst:78
msgid "Doing so is really easy. Go to your *Point of Sale* app and open your *Point of Sale* settings, under *Configuration*. There, click on *Edit* and check the *IoT Box* feature. Then, choose your *Receipt Printer* from the dropdown."
msgstr ""
#: ../../iot/devices/printer.rst:98
msgid "Now, on your *PoS* view, you will be able to print different kinds of tickets: **receipts**, **sale details** and **bills**."
#: ../../iot/devices/printer.rst:86
msgid "Now, you will be able to print different kinds of tickets from your *POS*: **receipts**, **sale details** and **bills**."
msgstr ""
#: ../../iot/devices/printer.rst:101
msgid "For the receipt, it will be printed once the order is validated. The process is automated when you enable the feature in your *PoS*."
#: ../../iot/devices/printer.rst:89
msgid "Receipts are printed once the order is validated. The process is automated when you enable the feature in your *PoS* configuration."
msgstr ""
#: ../../iot/devices/printer.rst:104
#: ../../iot/devices/printer.rst:92
msgid "Sales details can be printed by clicking on the printer icon on the navbar at the top of the *PoS*. It will print the details of the sales of the current day."
msgstr ""
#: ../../iot/devices/printer.rst:111
msgid "As for the bill, it is only available in restaurant mode. In your restaurant settings, activate bills and a *Bill* button will appear in the left panel. Click on it and it will print the bill."
#: ../../iot/devices/printer.rst:99
msgid "As for the bill, it is only available in restaurant mode. In your restaurant settings, activate *Print Bills* and a *Bill* button will appear in the left panel of the *PoS*."
msgstr ""
#: ../../iot/devices/printer.rst:119
#: ../../iot/devices/printer.rst:107
msgid "Print Orders in the kitchen"
msgstr ""
#: ../../iot/devices/printer.rst:121
#: ../../iot/devices/printer.rst:109
msgid "In restaurant mode, you can send order tickets to the kitchen."
msgstr ""
#: ../../iot/devices/printer.rst:123
#: ../../iot/devices/printer.rst:111
msgid "To do so, go to the *PoS* app and open your *PoS* settings. Then, tick *Order Printer*."
msgstr ""
#: ../../iot/devices/printer.rst:129
msgid "Now, go to the *Printers* menu. Hit create and select the *IoT Box* with all the categories of product that should be printed in the *Printer Product Categories* field."
#: ../../iot/devices/printer.rst:117
msgid "Now, go to the *Printers* menu. Hit create, select the printer from the dropdown and, in the *Printer Product Categories* field, choose all the categories of products that should be printed on this printer."
msgstr ""
#: ../../iot/devices/printer.rst:136
msgid "In the *PoS*, when you add or remove a product from one of the selected categories, the button *Order* will be green. If you click on it, a ticket will be printed."
#: ../../iot/devices/printer.rst:124
msgid "In the *PoS*, when you add or remove a product from one of the selected categories, the button *Order* will be green. If you click on it, the IoT Box will print a receipt on the corresponding printer."
msgstr ""

4
locale/sources/portal.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-10-09 11:26+0200\n"
"POT-Creation-Date: 2020-11-02 12:05+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -122,7 +122,7 @@ msgid "In order to delete your Odoo.com account, you have to reach out to our `S
msgstr ""
#: ../../portal/my_odoo_portal.rst:126
msgid "If you want to delete one of your databases, see:ref:`db_online`"
msgid "If you want to delete one of your databases, see :ref:`db_online`"
msgstr ""
#: ../../portal/my_odoo_portal.rst:129

324
locale/sources/project.pot
View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"POT-Creation-Date: 2020-11-02 12:05+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -53,7 +53,7 @@ msgid "To create a project for specific teams, under *Visibility*, choose who ca
msgstr ""
#: ../../project/advanced/advanced_projects.rst:25
msgid "*Invited employees*: the ones who are followers (see :doc:`../tasks/collaborate`)"
msgid "*Invited employees*: the ones who are followers."
msgstr ""
#: ../../project/advanced/advanced_projects.rst:26
@ -305,102 +305,9 @@ msgid "To only invoice approved timesheets, go to :menuselection:`Timesheets -->
msgstr ""
#: ../../project/advanced/so_to_task.rst:70
msgid ":doc:`../overview/setup`"
msgstr ""
#: ../../project/advanced/so_to_task.rst:71
msgid ":doc:`../../sales/invoicing/subscriptions`"
msgstr ""
#: ../../project/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../project/overview/setup.rst:3
msgid "Get Started with Project"
msgstr ""
#: ../../project/overview/setup.rst:5
msgid "Managing projects means managing people, tasks, due dates, budgets and predicted return on investments. For all of it, you need a solution that allows you to reduce risks, get information at a glance, have an overview of your progress and stay organized. And, from start to finish, to be able to run multiple projects in parallel easily. Odoo Project application is the solution you need."
msgstr ""
#: ../../project/overview/setup.rst:11
msgid "Creating a new project"
msgstr ""
#: ../../project/overview/setup.rst:13
msgid "Click on *Create*. Specify the name of the project and choose which features you would like to integrate. Note that they can be enabled afterward through *Settings*."
msgstr ""
#: ../../project/overview/setup.rst:21
msgid "Manage your project’s stages"
msgstr ""
#: ../../project/overview/setup.rst:23
msgid "Open your project and add as many columns as there are stages in your project."
msgstr ""
#: ../../project/overview/setup.rst:27
msgid "Each project stage can be characterized by a distinct set of activities, or your stages can guide you to the different steps a project has to go through. It is important to set them right as they lead you from the first idea or step to its conclusion, contributing to the overall success of your project."
msgstr ""
#: ../../project/overview/setup.rst:33
msgid "For each stage, there are markers for the status of tasks that you can personalize."
msgstr ""
#: ../../project/overview/setup.rst:34
msgid "Drag your mouse over a stage name, and click on :menuselection:`Settings --> Edit`."
msgstr ""
#: ../../project/overview/setup.rst:41
msgid "The dots correspond to customizable markers applied on tasks, making it easier to know which tasks require attention. You can give them any signification you like."
msgstr ""
#: ../../project/overview/setup.rst:50
msgid "Rearrange stages"
msgstr ""
#: ../../project/overview/setup.rst:52
msgid "From the Kanban view of your project, you can add stages by clicking on *Add a column*."
msgstr ""
#: ../../project/overview/setup.rst:54
msgid "To rearrange the order of your stages easily do so by dragging and dropping columns. You can also fold or unfold them on *Settings*."
msgstr ""
#: ../../project/overview/setup.rst:62
msgid ":doc:`../tasks/collaborate`"
msgstr ""
#: ../../project/overview/setup.rst:63
#: ../../project/tasks/sub_tasks.rst:66
msgid ":doc:`../record_and_invoice/time_record`"
msgstr ""
#: ../../project/overview/share.rst:3
msgid "Share Projects and Tasks"
msgstr ""
#: ../../project/overview/share.rst:5
msgid "When you share your projects/tasks, you allow external users to be on the same page as you. It avoids misunderstandings, simplifies communication, and allows you to become a more coordinated company as you get the right information to the right people."
msgstr ""
#: ../../project/overview/share.rst:10
msgid "Share projects and tasks"
msgstr ""
#: ../../project/overview/share.rst:12
msgid "To share a project, go to :menuselection:`Manage --> Share`."
msgstr ""
#: ../../project/overview/share.rst:19
msgid "To share a task, open it and click on :menuselection:`Action --> Share`. Choose an existing *Recipient(s)* or create it on the fly."
msgstr ""
#: ../../project/overview/share.rst:27
msgid "The recipient receives an email saying that he has been invited to access a document. In the example below, a project was shared. When the user opens it, he sees the settings of that project and can access its tasks, for example."
msgstr ""
#: ../../project/planning.rst:3
msgid "Planning"
msgstr ""
@ -561,94 +468,6 @@ msgstr ""
msgid "Tasks"
msgstr ""
#: ../../project/tasks/collaborate.rst:3
msgid "Collaborate on Tasks"
msgstr ""
#: ../../project/tasks/collaborate.rst:5
msgid "Being able to collaborate virtually but with the same effect as if people were in the same room increases your productivity. It results in faster execution of processes, brainstorming and decision made easier while also allowing the support of outside contributions."
msgstr ""
#: ../../project/tasks/collaborate.rst:10
msgid "Add followers to a project"
msgstr ""
#: ../../project/tasks/collaborate.rst:12
msgid "*Edit* the project to add followers."
msgstr ""
#: ../../project/tasks/collaborate.rst:14
msgid "Followers are notified of any changes: tasks sliding from one stage to another, conversations taking place, etc."
msgstr ""
#: ../../project/tasks/collaborate.rst:21
msgid "Following a project automatically makes you a follower of all its tasks."
msgstr ""
#: ../../project/tasks/collaborate.rst:24
msgid "Add followers to a task"
msgstr ""
#: ../../project/tasks/collaborate.rst:26
msgid "Within a task, click on the *Followers* icon. Followers get notified of any changes in the task and can see the task like you do, with the description and the chatter."
msgstr ""
#: ../../project/tasks/collaborate.rst:34
msgid "Select which notifications to get"
msgstr ""
#: ../../project/tasks/collaborate.rst:36
msgid "For a project or task, select what you would like to be notified about. For that, *Edit subscription*."
msgstr ""
#: ../../project/tasks/collaborate.rst:44
msgid "Use the pad like a collaborative note"
msgstr ""
#: ../../project/tasks/collaborate.rst:48
msgid "Go to :menuselection:`Project --> Configuration --> Settings --> Collaborative Pads`, then edit the *Settings* of the project you would like the feature to work and enable *Use Collaborative Pads*."
msgstr ""
#: ../../project/tasks/collaborate.rst:51
msgid "Now, you are able to contribute to tasks in real-time, with several users, with an Etherpad collaborative note. Every user has his own color and you can replay the whole creation of the content."
msgstr ""
#: ../../project/tasks/collaborate.rst:58
msgid "Click on the *</>* icon to get the direct URL of the task description: useful if you want to share it without adding this person as a follower, or to someone outside of the company."
msgstr ""
#: ../../project/tasks/collaborate.rst:62
msgid "The Chatter"
msgstr ""
#: ../../project/tasks/collaborate.rst:65
msgid "*Chatter* is a communication tool that shows the history of a task, including changes and the interactions between you and your customers or colleagues."
msgstr ""
#: ../../project/tasks/collaborate.rst:68
msgid "To interact with followers, whether there are internal or external, click on *Log a note* and ping them using the at symbol (*@*). If you want to send a message/email to all the followers in the task, use *Send a message*."
msgstr ""
#: ../../project/tasks/collaborate.rst:70
msgid "You can also ping a channel using the hashtag sign (*#*). This way, users can have a channel per project team, for example."
msgstr ""
#: ../../project/tasks/collaborate.rst:77
msgid "Schedule activities"
msgstr ""
#: ../../project/tasks/collaborate.rst:79
msgid "Do not forget promises made and stay organized by conveniently *Scheduling activities* from the chatter."
msgstr ""
#: ../../project/tasks/collaborate.rst:87
msgid "Edit or create new activities types"
msgstr ""
#: ../../project/tasks/collaborate.rst:89
msgid "Go to :menuselection:`Project --> Configuration --> Activity Types`."
msgstr ""
#: ../../project/tasks/email_alias.rst:3
msgid "Create Project's Tasks from an Email Alias"
msgstr ""
@ -689,140 +508,3 @@ msgstr ""
msgid "The email can be seen under the name of your project on the dashboard."
msgstr ""
#: ../../project/tasks/email_alias.rst:40
msgid ":doc:`./get_started`"
msgstr ""
#: ../../project/tasks/email_alias.rst:41
msgid ":doc:`./collaborate`"
msgstr ""
#: ../../project/tasks/get_started.rst:3
msgid "Get Started with Tasks"
msgstr ""
#: ../../project/tasks/get_started.rst:5
msgid "Break down a project by creating, assigning and organizing tasks. Set priorities to help you determine where you want to invest your time first, manage files within it and keep everything you need to complete your work in one place. Ensure that your strategies are turned into actionable plans and, as a result, have a successful project."
msgstr ""
#: ../../project/tasks/get_started.rst:11
msgid "Create a task"
msgstr ""
#: ../../project/tasks/get_started.rst:13
msgid "Click on *Create*. Once created, add more details opening it and clicking on *Edit*."
msgstr ""
#: ../../project/tasks/get_started.rst:21
msgid "Assignation"
msgstr ""
#: ../../project/tasks/get_started.rst:23
msgid "Choose the responsible person for a task under *Assigned to*."
msgstr ""
#: ../../project/tasks/get_started.rst:30
msgid "Sort tasks by priority"
msgstr ""
#: ../../project/tasks/get_started.rst:34
msgid "Mark the star on your task to set it as a high priority one. That automatically moves the task to the top of the column. Tasks that are not starred are classified according to their deadlines."
msgstr ""
#: ../../project/tasks/get_started.rst:36
msgid "Note that tasks with dates passed their deadlines are shown in red; tasks with a deadline for the current date are orange."
msgstr ""
#: ../../project/tasks/get_started.rst:43
msgid "Manage files in tasks"
msgstr ""
#: ../../project/tasks/get_started.rst:45
msgid "Add images/documents to your task by clicking on the *Attachment icon*."
msgstr ""
#: ../../project/tasks/get_started.rst:52
msgid "Files from emails are automatically saved."
msgstr ""
#: ../../project/tasks/get_started.rst:55
msgid "Set cover images in tasks"
msgstr ""
#: ../../project/tasks/get_started.rst:57
msgid "Use *Set Cover Image* to your task and quickly get to comprehend what the task is about. The image is directly shown in the Kanban view."
msgstr ""
#: ../../project/tasks/get_started.rst:66
msgid "Choose how to visualize tasks"
msgstr ""
#: ../../project/tasks/get_started.rst:68
msgid "Tasks can be managed and followed up in the Kanban view, which is a post-it kind of view divided into different stages. More options are otherwise available."
msgstr ""
#: ../../project/tasks/get_started.rst:75
msgid "Drag and drop tasks to change their stage and define colors to help you identify them."
msgstr ""
#: ../../project/tasks/get_started.rst:83
msgid ":doc:`../../general/tags/take_tags`"
msgstr ""
#: ../../project/tasks/sub_tasks.rst:3
msgid "Work with Sub-tasks"
msgstr ""
#: ../../project/tasks/sub_tasks.rst:5
msgid "Being a dynamic and organized company is important as it also helps you to not overload your employees. For that, split large tasks into smaller ones by creating subs-tasks, timesheet on them, and have an overview of all hours recorded."
msgstr ""
#: ../../project/tasks/sub_tasks.rst:10
msgid "Configuration"
msgstr ""
#: ../../project/tasks/sub_tasks.rst:12
msgid "Go to :menuselection:`Project --> Configuration --> Settings --> Sub-tasks`."
msgstr ""
#: ../../project/tasks/sub_tasks.rst:18
msgid "From now on, a *Sub-tasks* menu is available within your task."
msgstr ""
#: ../../project/tasks/sub_tasks.rst:25
msgid "Select a specific project in which sub-tasks will be created by default"
msgstr ""
#: ../../project/tasks/sub_tasks.rst:27
msgid "By default, sub-tasks are created under the same project. However, you can select another one by going to :menuselection:`Project --> Configuration --> Projects --> Sub-task Project`."
msgstr ""
#: ../../project/tasks/sub_tasks.rst:35
msgid "Timesheet on sub-tasks"
msgstr ""
#: ../../project/tasks/sub_tasks.rst:37
msgid "Make sure the feature *Timesheets* is enabled under :menuselection:`Project --> Configuration --> Settings` and under the settings of the needed *Project*. Now you are able to timesheet on your tasks and sub-tasks. The time recorded on a sub-task is counted on the parent task."
msgstr ""
#: ../../project/tasks/sub_tasks.rst:46
msgid "Transform an existing task into a sub-task"
msgstr ""
#: ../../project/tasks/sub_tasks.rst:48
#: ../../project/tasks/sub_tasks.rst:58
msgid "Go to :menuselection:`Settings --> Activate the developer mode`."
msgstr ""
#: ../../project/tasks/sub_tasks.rst:49
msgid "Now access your task, *Edit*, and add a *Parent Task*."
msgstr ""
#: ../../project/tasks/sub_tasks.rst:56
msgid "Unlink a sub-task from a parent task"
msgstr ""
#: ../../project/tasks/sub_tasks.rst:59
msgid "Open and *Edit* the respective sub-task to remove the *Parent Task*."
msgstr ""

30
locale/sources/studio.pot
View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"POT-Creation-Date: 2020-11-02 12:05+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -113,54 +113,54 @@ msgid "*Send Email*: an automatic :doc:`email <../../discuss/advanced/email_temp
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:51
msgid "*Add Followers*: :doc:`followers <../../project/tasks/collaborate>` are notified of changes in the task."
msgid "*Add Followers*: followers are notified of changes in the task."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:53
#: ../../studio/concepts/understanding_automated_actions.rst:52
msgid "*Create Next Activity*: creates an activity such as: *Call*, *Email*, *Reminder*."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:54
#: ../../studio/concepts/understanding_automated_actions.rst:53
msgid "*Send SMS Text Message*: sends an :doc:`SMS <../../sms_marketing/pricing/pricing_and_faq>`."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:57
#: ../../studio/concepts/understanding_automated_actions.rst:56
msgid "Example"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:59
#: ../../studio/concepts/understanding_automated_actions.rst:58
msgid "This is the process of which the update of the *Email* field on the Lead/Opportunity *Model*, with a *Trigger Condition* set to *On Update*, goes through:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:66
#: ../../studio/concepts/understanding_automated_actions.rst:65
msgid "The user creates the record without an email address set."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:67
#: ../../studio/concepts/understanding_automated_actions.rst:66
msgid "The user updates the record defining an email address."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:68
#: ../../studio/concepts/understanding_automated_actions.rst:67
msgid "Once the change is saved, the automation checks if any of the *Watched Fields* are being updated (for the example: field name *email_from* (Email)."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:70
#: ../../studio/concepts/understanding_automated_actions.rst:69
msgid "If true, it checks if the record matches the *Before Update Domain* (for the example: *email is not set*)."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:72
#: ../../studio/concepts/understanding_automated_actions.rst:71
msgid "If true, it checks (*after the update*) whether the record matches the *Apply on* domain (for the example: *email is set*)."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:74
#: ../../studio/concepts/understanding_automated_actions.rst:73
msgid "If true, the chosen *Action To Do* is performed on the record."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:77
#: ../../studio/concepts/understanding_automated_actions.rst:76
msgid ":doc:`understanding_general`"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:78
#: ../../studio/concepts/understanding_automated_actions.rst:77
msgid ":doc:`../use_cases/automated_actions`"
msgstr ""