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

[I18N] Update translation terms from Transifex

Browse Source
This commit is contained in:
Odoo Translation Bot
2022-12-25 00:40:38 +01:00
parent 6a56842e1f
commit abe3f8f3d6
47 changed files with 34169 additions and 20064 deletions
Download Patch File Download Diff File Expand all files Collapse all files
locale/pt_BR/LC_MESSAGES/finance.po
+2660 -1729
View File
File diff suppressed because it is too large Load Diff
locale/pt_BR/LC_MESSAGES/inventory_and_mrp.po
+225 -165
View File
@@ -6,15 +6,16 @@
# Translators:
# grazziano <gra.negocia@gmail.com>, 2022
# Martin Trigaux, 2022
# Marcel Savegnago <marcel.savegnago@gmail.com>, 2022
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-11-17 09:28+0000\n"
"POT-Creation-Date: 2022-12-23 09:13+0000\n"
"PO-Revision-Date: 2022-10-04 12:53+0000\n"
"Last-Translator: Martin Trigaux, 2022\n"
"Last-Translator: Marcel Savegnago <marcel.savegnago@gmail.com>, 2022\n"
"Language-Team: Portuguese (Brazil) (https://www.transifex.com/odoo/teams/41243/pt_BR/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -534,7 +535,6 @@ msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:13
#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:17
#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:14
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:27
#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:23
#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:9
msgid "Configuration"
@@ -7231,67 +7231,84 @@ msgid ""
"on which work center is busy and plan resources accordingly in real-time."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:11
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:10
msgid ""
"With Odoo, you can configure alternative work centers to solve this issue. "
"This automatically checks which work center is busy and which equivalent "
"ones are free, and schedules orders and maintenance accordingly."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:15
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:14
msgid ""
"This way, your process becomes more efficient, as work center utilisation is"
" optimised."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:19
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:17
msgid "Configure your Work Centers"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:21
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:19
msgid ""
"First, go to the :menuselection:`Manufacturing app --> Configuration --> "
"Settings`. Then, enable the Work Orders feature and hit save."
"Settings`. Then, enable the :guilabel:`Work Orders` feature and hit "
":guilabel:`Save`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rstNone
msgid "work order settings ticked"
msgid "Work order settings ticked in Odoo Manufacturing."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:29
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:26
msgid ""
"Now, go to :menuselection:`Configuration --> Work Centers` and create two "
"new work centers. Add the second work center as an alternative to the first "
"one and vice versa."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:38
msgid ""
"Next, go to :menuselection:`Products --> Bills of Materials`, choose your "
"product, and add these work centers to the operations of your BOM."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rstNone
msgid "Create a secondary work center as an alternate to the first."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:48
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:33
msgid ""
"Next, go to :menuselection:`Products --> Bills of Materials`, choose your "
"product, and add these work centers to the operations of your :abbr:`BoM "
"(Bill of Materials)`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rstNone
msgid "Add work centers to Bill of Materials operations."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:41
msgid "Create your Work Orders"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:50
msgid ""
"Now that everything is configured, you can create your *Work Orders*. Go to "
":menuselection:`Operations --> Manufacturing Orders`, and hit **Create**. "
"There, add your product to your manufacturing order and plan it. You can "
"then retrieve them from the Work Orders list view, under Operations > Work "
"Orders."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:43
msgid "Now that everything is configured, you can create your *Work Orders*."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:55
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:45
msgid ""
"Go to :menuselection:`Operations --> Manufacturing Orders`, and hit "
":guilabel:`Create`. There, add your product to your manufacturing order and "
"plan it. You can then retrieve them from the :guilabel:`Work Orders` list "
"view, under :menuselection:`Operations > Work Orders`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:49
msgid ""
"Each new *Work Order*, which will be created before the end of the first "
"one, will be scheduled at the alternative work center you configured, as "
"shown below."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:64
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rstNone
msgid "Work order creation and scheduling."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:57
msgid ""
"Keep in mind that, if you add time after production to your work center, you"
" may have work orders scheduled for your alternative work center even if the"
@@ -7299,246 +7316,289 @@ msgid ""
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:3
msgid "Create Bills of Materials"
msgstr ""
msgid "Create a bill of materials"
msgstr "Crie uma lista de materiais"
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:5
msgid ""
"A *Bill of Materials* is a document defining the quantity of each component "
"required to make or deliver a finished product. Additionally, it can also "
"include various operations and individual step guidelines needed to complete"
" a production process."
"A *Bill of Materials* (or *BoM* for short) is a document that defines the "
"quantity of each component required to make or deliver a finished product. "
"It can also include various operations and the individual step guidelines "
"needed to complete a production process."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:10
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:9
msgid ""
"With Odoo's MRP solution, multiple BOMs can also be linked to each product, "
"so that even product variants can have their *own* tailored BOM."
"In Odoo Manufacturing, multiple :abbr:`BoMs (Bills of Materials)` can be "
"linked to each product, so that even product variants can have their own "
"tailored :abbr:`BoMs (Bills of Materials)`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:13
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:12
msgid ""
"This will help you to optimize your manufacturing process and save time as a"
" result."
"Correctly setting up a :abbr:`BoM (Bill of Materials)` helps optimize the "
"manufacturing process and save time."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:17
msgid "Setting up a BoM"
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:16
msgid "Set up a bill of baterials (BoM)"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:18
msgid ""
"The simplest BoM set up is one without operations or instructions. In this "
"case, you will manage your production using Manufacturing Orders only."
"The simplest :abbr:`BoM (Bill of Materials)` setup is one without operations"
" or instructions, only components. In this case, the production is solely "
"managed using *Manufacturing Orders*."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:22
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:21
msgid ""
"To create a BoM from the Manufacturing module, go to "
":menuselection:`Products --> Bills of Materials`. If you click **Create**, "
"the first thing you'll have to do is to specify the final product. For an "
"existing product, simply select it from the list, or create a new one on the"
" spot. Note that if you go through the product form to create your BOM, the "
"product will already be set for you."
"To create a :abbr:`BoM (Bill of Materials)` from the "
":guilabel:`Manufacturing` module, go to :menuselection:`Products --> Bills "
"of Materials`. Then, click :guilabel:`Create`. Next, specify the "
":guilabel:`Product`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:27
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:26
msgid ""
"For a standard Bill of Material, keep the default *BoM* type, which is "
"*Manufacture this Product*. Now specify the various components that make up "
"the production of your final product and their respective quantities. You "
"can create components as you go, on the BOM, or create products beforehand, "
"by going to the :menuselection:`Top Menu --> Products --> Create`, and add "
"them later on."
"A :abbr:`BoM (Bill of Materials)` can also be created directly from the "
"product form, in which case the :guilabel:`Product` field is pre-filled."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:37
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:29
msgid ""
"The destination location should **not** be a scrap location. A scrap "
"location is where you put products that you don't need."
"For a standard :abbr:`BoM (Bill of Materials)`, set the :guilabel:`BoM Type`"
" to :guilabel:`Manufacture this Product`. Then, click :guilabel:`Add a Line`"
" to specify the various components that make up the production of the final "
"product and their respective quantities. New components can be created "
"quickly through the :abbr:`BoM (Bill of Materials)`, or can be created "
"beforehand in :menuselection:`Manufacturing --> Products --> Products --> "
"Create`. Finally, click :guilabel:`Save` to finish creating the :abbr:`BoM "
"(Bill of Materials)`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rstNone
msgid "Set up a Bill of Materials."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:41
msgid "Using the same BoM to describe Variants"
msgid "Specify a bill of materials (BoM) for a product variant"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:43
msgid ""
"As suggested above, you can use *BOMs* for specific *Product Variants*. Once"
" the various attributes have been configured on the product form, there are "
"two ways to configure the appropriate BoM for the respective product "
"combination."
":abbr:`BoMs (Bills of Materials)` can also be assigned to specific *Product "
"Variants*, with two setup options available to choose from."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:47
msgid ""
"Either create one BoM per variant, by specifying the Product Variant in the "
"dedicated field below the product name. Or use one BOM, that contains all of"
" the components and for each component, indicate which variant it applies "
"to, using the *Apply on Variants* column, as shown below."
"In order to assign :abbr:`BoMs (Bills of Materials)` to product variants, "
"the product's variant attributes must already be configured on the product "
"form."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:57
msgid "Adding Operations"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:59
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:50
msgid ""
"You can also add operations to your *BoM*, if you want workers to follow "
"instructions or register time spent. To use this feature, enable the *Work "
"Orders* feature in the *Manufacturing* app settings, as shown below."
"The first method is to create one :abbr:`BoM (Bill of Materials)` per "
"variant by creating a new :abbr:`BoM (Bill of Materials)` and specifying the"
" :guilabel:`Product Variant`. The second method is to create one master "
":abbr:`BoM (Bill of Materials)` that contains all of the components, and "
"specify which variant each component applies to using the :guilabel:`Apply "
"on Variants` column."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rstNone
msgid "Product Variants in the Bill of Materials."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:60
msgid "Set up operations"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:62
msgid ""
"Add an :guilabel:`Operation` to a :abbr:`BoM (Bill of Materials)` to specify"
" instructions for production and register time spent on an operation. To use"
" this feature, first enable the :guilabel:`Work Orders` feature in "
":menuselection:`Manufacturing --> Configuration --> Settings --> "
"Operations`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:67
msgid ""
"Each operation is unique as it is always linked to only one BOM. This being "
"said, Operations Operations can be re-used when configuring a new BOM, with "
"the *Copy Existing Operations* feature."
"Then, when creating a new :abbr:`BoM (Bill of Materials)`, click on the "
":guilabel:`Operations` tab and click :guilabel:`Add a line` to add a new "
"operation. In the :guilabel:`Create Operations` box, give the operation a "
"name, specify the :guilabel:`Work Center` and duration settings. Like "
"components, Odoo gives the option to specify a product variant in the "
":guilabel:`Apply on Variants` field so the operation only applies to that "
"variant. Finally, click :guilabel:`Save & Close`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:74
msgid ""
"Finally, just like for components, operations can also be variant specific "
"only, as shown below."
"Each operation is unique, as it is always exclusively linked to one "
":abbr:`BoM (Bill of Materials)`. Operations can be reused when configuring a"
" new :abbr:`BoM (Bill of Materials)`, with the :guilabel:`Copy Existing "
"Operations` feature."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:82
msgid "Adding By-Products"
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rstNone
msgid "Copy Existing Operations feature."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:84
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:83
msgid "Add by-products to a bill of materials (BoM)"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:85
msgid ""
"A *by-product* is a product that is produced on top of the main product of a"
" *BoM*. As opposed to the primary product, there can be more than one on a "
"BOM."
"A *By-Product* is a residual product that is created during production in "
"addition to the main product of a :abbr:`BoM (Bill of Materials)`. Unlike "
"the primary product, there can be more than one by-product on a :abbr:`BoM "
"(Bill of Materials)`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:87
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:89
msgid ""
"To add *by-products* to a *BoM*, you will first need to enable the by-"
"product feature from the *Manufacturing* app settings."
"To add by-products to a :abbr:`BoM (Bill of Materials)`, first enable the "
":guilabel:`By-Products` feature in :menuselection:`Manufacturing --> "
"Configuration --> Settings --> Operations`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:93
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:92
msgid ""
"Once the feature is enabled, you can add *by-products* to your *BoMs*. Note "
"that if you have Operations, you'll need to specify in which operation the "
"by-product is produced."
"Once the feature is enabled, you can add by-products to a :abbr:`BoM (Bill "
"of Materials)` by clicking on the :guilabel:`Operations` tab and clicking "
":guilabel:`Add a line`. Then, name the by-product and indicate the "
":guilabel:`Quantity` and the :guilabel:`Unit of Measure`. If the :abbr:`BoM "
"(Bill of Materials)` has configured operations, specify exactly which "
"operation the by-product is produced from in the :guilabel:`Produced in "
"Operation` field. Finally, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:3
msgid "Kits"
msgid "Use kits"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:5
msgid ""
"A *kit* is a set of components that are not pre-assembled or mixed. This is "
"useful for selling but also for creating cleaner and more effective *BOMs*. "
"To use kits, you need both the Manufacturing and Inventory apps to be "
"installed."
"A *kit* is a set of unassembled components. Kits may be sold as products, "
"but are also useful tools for managing more complex bills of materials "
"(BoMs). To use kits, the :guilabel:`Manufacturing` and :guilabel:`Inventory`"
" applications need to be installed."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:10
msgid "Manage Stock of Component Products"
msgid "Create the kit as a product"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:12
msgid ""
"If you want to assemble kits as they are ordered, managing stock of the kit "
"components only, you will use a *Kit BoM* Type without any manufacturing "
"operations."
"To use a kit as a sellable product or simply as a component organization "
"tool, the kit should first be created as a product. To create a kit product,"
" go to :menuselection:`Manufacturing or Inventory --> Products --> "
"Products`, and then click :guilabel:`Create`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:15
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:16
msgid ""
"A product using a *Kit BoM* will appear as a single line item on a quotation"
" and a sales order, but will generate a delivery order with one line item "
"for each of the components of the kit. In the examples below, the first "
"image shows a sales order for the kit *Custom Computer Kit*, while the "
"second image shows the corresponding delivery order."
"Next, set the :guilabel:`Product Type` to :guilabel:`Storable Product`: this"
" allows for management of kit inventory. The :guilabel:`Route` designation "
"under the :guilabel:`Inventory` tab does not matter, since Odoo uses the "
"routes of the kit's components for replenishment purposes. All other "
"parameters for the kit product may be modified according to preference. "
"Finally, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:29
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:22
msgid ""
"From the *Products menu* in either the *Inventory* or *Manufacturing* app, "
"create each component product (as you would with any other product), then "
"create the top-level, or kit product. Because you cannot track the stock of "
"kit products, the *Product Type* should be set to *Consumable*. However, if "
"you are using Anglo-Saxon accounting, and you would like COGS to be posted "
"when invoicing your kits (and only for this reason), the storable product "
"type should selected instead. Because a kit product cannot be purchased, "
"*Can be Purchased* should be unchecked. The route of the kit product in the "
"*Inventory* Tab does not really matter, as, for replenishment, only the "
"route of the components that will be taken into account only."
"The kit's components must also be configured as products via "
":menuselection:`Manufacturing or Inventory --> Products --> Products`. These"
" components require no specific configuration."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:26
msgid "Set up the kit BoM"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:28
msgid ""
"After fully configuring the kit product and its components, create a "
":abbr:`BoM (Bill of Materials)` for the kit product. Go to "
":menuselection:`Manufacturing --> Products --> Bills of Materials`, and then"
" click :guilabel:`Create`. Next, set the :guilabel:`Product` field to the "
"previously configured kit product. Then, set the :guilabel:`BoM Type` to "
":guilabel:`Kit`. Finally, add each component and specify its quantity. Make "
"sure to :guilabel:`Save` the changes."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rstNone
msgid "Kit selection on the bill of materials."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:38
msgid ""
"All other parameters on the kit product may be modified according to your "
"preference. The component products require no particular configuration."
"If the kit is solely being used as a sellable product, then only components "
"need to be added under the :guilabel:`Components` tab, and configuring "
"manufacturing operations is not necessary."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:41
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:42
msgid ""
"Once the products are configured, create a *bill of materials* for the kit "
"product. Add each component and its quantity. Select the *BoM Type* Kit. All"
" other options may be left with their default values."
"When a kit is sold as a product, it appears as a single line item on the "
"quotation and sales order. However, on delivery orders, each component of "
"the kit is listed."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:46
msgid "Use kits to manage complex BoMs"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:48
msgid "Manage Stock of Kit Product and Component Products"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:50
msgid ""
"If you want to manage the stock of the *top-level kit product*, you will use"
" a standard *BoM Type* manufacture or subcontracting instead. In this case "
"you will either buy the final product from your subcontractor, or make it "
"yourself through a manufacturing order."
"Kits are also used to manage *multilevel* :abbr:`BoMs (Bills of Materials)`."
" These are products that contain other products as components and therefore "
"require nested :abbr:`BoMs (Bills of Materials)`. Incorporating pre-"
"configured kits into multilevel :abbr:`BoMs (Bills of Materials)` allows for"
" cleaner organization of bundled products. Under :guilabel:`Components`, "
"list a kit as a component in a higher-level product's :abbr:`BoM (Bills of "
"Material)` to eliminate the need to add the kit's parts individually. Any "
":guilabel:`BoM Type` can be used for the higher-level product's :abbr:`BoM "
"(Bill of Materials)`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:54
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rstNone
msgid "Kit as a component in a multilevel bill of materials."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:60
msgid ""
"In that case the product type will be storable, and the BOM type either "
"'Manufacture this product' or 'Subcontracting' as shown below."
"To access a comprehensive overview of the multilevel :abbr:`BoM's (Bill of "
"Material's)` components, click on the :guilabel:`Structure & Cost` smart "
"button. Sublevel :abbr:`BoMs (Bills of Materials)` can be expanded and "
"viewed from this report."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:62
msgid "Build a cleaner BOM"
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rstNone
msgid "Expanded kit in the Structure and Cost report."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:64
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:68
msgid ""
"As suggested above, a kit BOM can also simply be used to manage a more "
"complex BOM."
"When creating a manufacturing order for a product with a multilevel "
":abbr:`BoM (Bill of Materials)`, the kit product automatically expands to "
"show all components. Any operations in the kit's :abbr:`BoM (Bill of "
"Materials)` are also added to the list of work orders on the manufacturing "
"order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:66
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:74
msgid ""
"Imagine the Custom Computer parts above were part of another final product. "
"It would be much clearer and simpler if the BOMs were added together (as "
"shown below) instead of adding all the individual parts one by one."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:73
msgid ""
"This is even better illustrated when looking at the BOM Structure Report, "
"where it is easy to expand and hide specific kit level or sub-assembly type "
"BOMs."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:79
msgid ""
"On the creation of the manufacturing order, the BOM will automatically "
"expand to show all top level and kit level components. You can go back to "
"the BOM at any point though as it remains available on the form view of "
"your manufacturing order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:86
msgid ""
"Finally, note that if there were any Operations in the Kit BOM, these would "
"also simply be added in to the work order list of the main component."
"Kits are primarily used to bundle components together for organization or "
"sale. To manage multilevel products that require manufactured subcomponents,"
" refer to :doc:`this documentation <sub_assemblies>` on sub-assemblies."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:3
locale/pt_BR/LC_MESSAGES/marketing.po
+662 -70
View File
@@ -3,13 +3,18 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Luis Felipe Miléo <mileo@kmee.com.br>, 2022
# Martin Trigaux, 2022
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-10-04 12:47+0000\n"
"POT-Creation-Date: 2022-12-23 09:13+0000\n"
"PO-Revision-Date: 2022-10-04 12:54+0000\n"
"Last-Translator: Martin Trigaux, 2022\n"
"Language-Team: Portuguese (Brazil) (https://www.transifex.com/odoo/teams/41243/pt_BR/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -22,6 +27,7 @@ msgid "Marketing"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:8
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:3
msgid "Marketing Automation"
msgstr ""
@@ -36,111 +42,697 @@ msgid "Advanced"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:3
msgid "Understanding Metrics"
msgid "Understanding metrics"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:4
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:5
msgid ""
"Metrics are values that help you measure progress and can be a powerful way "
"of linking your employees to goals."
"Metrics are detailed statistics that measure the progress (and success) of "
"marketing campaigns. When creating marketing activities in a workflow, Odoo "
"will visually display various metrics related to the campaign with graphs "
"and data."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:9
msgid "Consider the following example:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone
msgid "An example of a marketing automation campaign in Odoo."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:15
msgid ""
"When you create a workflow in Odoo, its visual content already shows metrics"
" in a graph form and in numbers."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:10
msgid "Let’s consider the example below:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone
msgid "Metrics in Odoo Marketing Automation"
"In this case, the :guilabel:`Target` of this campaign is set to "
":guilabel:`Lead/Opportunity` and was narrowed down to only focus on the "
"Leads (or Opportunities) whose :guilabel:`Tag Name` contain a value of "
"`product` and they *also* have an email address set up in the database."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:19
msgid ""
"The *Target* - business object - is *Lead/Opportunity* and was narrowed down"
" to the ones whose *Tag Name* contain the description “Product”, and have an"
" email address set."
"Beneath the filter nodes, Odoo will display how many records in the database"
" fall into the previously-specified criteria filter. In this example, there "
"are 18 records in the database that match the criteria."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:20
msgid "A total number of 20 records match the criteria."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:28
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone
msgid ""
"Out of those 20 records, 25 have become participants, in other words, they "
"have matched the criteria."
"Lead generation filters used to refine records on marketing automation "
"campaigns in Odoo."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:36
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:27
msgid ""
"Every time the system runs, updating numbers and triggering actions, it will"
" look at the *Target* model and check if new records have been added or "
"modified, keeping the flow up-to-date."
"At the top of the marketing automation form, there are a series of smart "
"buttons. The :guilabel:`Participations` smart button in this example "
"indicates that, out of those 18 records, 25 have become participants. In "
"other words, they have matched the criteria, and have already interacted "
"with the campaign in one way or another."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:41
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:33
msgid ""
"The filter here is applied to *all* activities. Leads that lose the tag in "
"the meantime will be excluded from later activities."
":guilabel:`Records` represent a real-time number. Therefore, while the "
"workflow is running, changes in opportunity records (deletions, additions, "
"adjustments) may occur. This means there will be real-time updates to the "
"number of :guilabel:`Records`, but such updates do *not* change the number "
"of :guilabel:`Participants`, as the metric *will not* exclude opportunities "
"that have already been set as :guilabel:`Participants` before - Odoo will "
"just add new ones. That's why the number of :guilabel:`Records` can be "
"different from the number of :guilabel:`Participants` from time to time."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone
msgid ""
"Difference between real-time record count and total participants on a "
"markeing campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:45
msgid ""
"*Records* is a real-time number, therefore while the workflow is running, "
"changes in opportunity records can be made - delete, add, adjustment - "
"updating the number of records, but not changing the number of participants,"
" as the metric *will not* exclude opportunities that have been set as "
"participants before. It will just add new ones. For this reason, the number "
"of *Records* can be different from the number of *Participants*."
"Whenever the system runs, updating numbers and triggering actions, it will "
"look at the :guilabel:`Target` model, and check if new :guilabel:`Records` "
"have been added (or modified), which always keeps the flow up-to-date."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:50
msgid ""
"The filter here is applied to *all* activities. Leads that lose that "
"specific :guilabel:`Tag` in the meantime will be excluded from later "
"activities."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:54
msgid ""
"Filters can also be applied to individual activities, in the "
":guilabel:`Domain` section of the activity pop-up form. Use this feature to "
"specify an individual filter that will only be performed if the records "
"satisfy *both* filter criteria - the activity filter and its specific domain"
" filter."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:59
msgid ""
"(*Example*: when configuring an SMS activity, make sure a certain phone "
"number is set, in order to avoid triggering a SMS that would never be sent.)"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0
msgid ""
"You can also have filters applied to activities individually, under "
"*Domain*. A useful feature to specify an individual filter that will only be"
" performed if the records satisfied both filters, the activity and its "
"domain one."
"A relevant targeting filter that applies to a type of individual activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:66
msgid ""
"Example: for an activity sending an SMS, you could make sure a phone number "
"is set to avoid triggering a SMS that would never be sent and crash."
":guilabel:`Success` represents the number of times the searching for "
"participants - who match the criteria filter(s) of that activity - was "
"performed successfully, in relation to the total number of participants. If "
"a participant does *not* match the conditions, it will be added to "
":guilabel:`Rejected`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:64
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone
msgid ""
"*Success* is the number of times the searching for participants - that match"
" the filter(s) of that activity - was performed successfully in relation to "
"the total number of participants."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:65
msgid ""
"If a participant does not match the conditions, it will be added to "
"*Rejected*."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:71
msgid ""
"Hovering over the graph, you can see the number of successful and rejected "
"participants, per day, for the last 15 days."
"Overview showing participants who do or do not match filtering criteria on "
"an activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:75
msgid ""
"Every time a new record is added to the *Target* model, it will be "
"automatically added to the workflow, and, it will start the workflow from "
"the beginning (parent action)."
"Hovering over the graph, Odoo displays the number of successful and rejected"
" participants, per day, over the last 15 days."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:79
msgid ""
"Whenever a new record is added to the :guilabel:`Target` model, it will "
"automatically be added to the workflow, and it will start the workflow from "
"the beginning (:guilabel:`Parent Action`)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started.rst:5
msgid "Getting Started"
msgstr "Começando"
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:5
msgid ""
"The Odoo Marketing Automation app automates a variety of marketing tasks by "
"combining specific rules and filters to generate timed actions. Instead of "
"manually having to build each stage of a campaign (such as a series of timed"
" massmails), the Marketing Automation app allows marketers to build the "
"entire campaign, and all of its stages, in one place on one dashboard."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:11
msgid "Create a campaign"
msgstr "Crie uma campanha"
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:13
msgid ""
"To create a new automated marketing campaign, open the :guilabel:`Marketing "
"Automation` app and click :guilabel:`Create`. On the :guilabel:`Campaign` "
"page, there are the following smart buttons and fields:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rstNone
msgid ""
"A dashboard showing the creation of a new marketing automation campaign in "
"Odoo."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:21
msgid ""
":guilabel:`Templates`: represents the number of pre-configured mail "
"templates being used in this particular campaign. (Templates can always be "
"created on-the-fly as well)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:23
msgid ""
":guilabel:`SMS`: represents the number of personalized SMS messages "
"connected to this campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:24
msgid ""
":guilabel:`Clicks`: represents the number of times attached links have been "
"clicked by recipients of this campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:26
msgid ""
":guilabel:`Participants`: represents the number of contacts that have "
"directly participated in this campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:28
msgid ""
":guilabel:`Target`: this field is a drop-down menu to choose which model is "
"targeted by this campaign (i.e., by Contacts, Sales Order, Lead/Opportunity,"
" etc.)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:32
msgid "Campaign filters"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:34
msgid ""
"To add a filter to the target audience, click :guilabel:`Add Filter`, and a "
"node field will appear. In the node field, a custom equation can be "
"configured for Odoo to use when filtering who to include (and exclude) in "
"this specific marketing campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rstNone
msgid "A filter node in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:42
msgid ""
"When the first field of the node is clicked, a nested drop-down menu of "
"options appears on the screen where specific criteria is chosen based on "
"needs of the campaign. The remaining fields on the node further define the "
"criteria which determines which records to include (or exclude) in the "
"execution of the campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:47
msgid ""
"To add another node, simply click the :guilabel:`+ (plus sign)` icon to the "
"right of the filtering rule. To add a branch of multiple nodes at the same "
"time, click the :guilabel:`... (ellipses)` icon."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:51
msgid ""
"For further information on filters, refer to :doc:`this documentation page "
"<target_audience>`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:54
msgid ""
":guilabel:`Records` represent the number of contacts in the system that fit "
"the specified criteria for a campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:58
msgid ":doc:`testing_running`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:59
msgid ":doc:`workflow_activities`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:3
msgid "Target an audience"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:5
msgid ""
"Delivering marketing campaigns to the *right* audience is paramount when "
"trying to grow a business. The :guilabel:`Odoo Marketing Automation` "
"application helps marketers to do just that by providing filtering tools, "
"that can be as simple or as complex as necessary, to reach the right "
"customers at the right time."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:11
msgid "Work with target filters"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:13
msgid ""
"When configuring the filters on a marketing campaign, there are some options"
" that have an arrow icon beside them. The arrow signifies that the filter "
"has more refined parameters within it."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rstNone
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rstNone
msgid "The drop-down filter menu in the Marketing Automation application."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:20
msgid ""
"Filters can be extended by adding *branches* and *nodes*. A *node* adds "
"another filtering parameter to a group of targeting conditions (e.g. a new "
"line), and a *branch* creates a narrowly refined cluster of parameters, "
"allowing filters to be grouped with *Any* or *All* statements."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:24
msgid "Every time a new branch is created, there are two options:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:26
msgid ""
"Either the records can match :guilabel:`ALL` criteria for the upcoming rules"
" (an AND statement where all criteria must match)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:29
msgid ""
"Or, the records can match :guilabel:`ANY` criteria for the upcoming rules "
"(an OR statement where only one of the criteria must match)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:32
msgid ""
"To change between these two options, simply click the drop-down arrow icon "
"in the green box and select :guilabel:`Any` or :guilabel:`All`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:35
msgid ""
"To add a node, click on the :guilabel:`+ (plus sign icon)` and to add "
"another branch click on the :guilabel:`... (ellipses icon)`. To exclude a "
":guilabel:`node` (or a :guilabel:`branch`), click on :guilabel:`x (delete)`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:44
msgid "Use cases"
msgstr "Casos de uso"
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:46
msgid ""
"The following scenarios below outline different combinations of filters a "
"marketing campaign might commonly use."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:50
msgid ""
"Scenario #1: Narrow the target down to new opportunities in the pipeline"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:52
msgid ""
"While in Edit mode on a campaign template form, select the "
":guilabel:`Target` field, and click :guilabel:`Search More` from the drop-"
"down menu. Then, search for :guilabel:`Lead/Opportunity` and select it."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:56
msgid ""
"Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Click on"
" the default :guilabel:`ID` filter option in the first portion of the filter"
" equation. Doing so reveals a drop-down menu full of filter options. From "
"this drop-down, scroll down (or search for) :guilabel:`Type`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:61
msgid ""
"Keep the second portion of the filter equation on the default :guilabel:`= "
"(equal sign)`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:63
msgid ""
"Then, change the third (and final) portion of the filter equation from "
":guilabel:`Lead` to :guilabel:`Opportunity`. The number of "
":guilabel:`Records` that fit this specific filter equation will change as "
"the equation is customized."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:67
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:103
msgid ""
"Add another node to this filter by clicking the :guilabel:`+ (plus sign)` to"
" the right of the equation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:70
msgid ""
"With \"new\" opportunities being the target of this filter, the second node "
"will focus on only locating opportunities that are in the :guilabel:`New` "
"stage of the pipeline. To do that, select the default :guilabel:`ID` from "
"the first portion of the second filter equation, and scroll down (or search "
"for) :guilabel:`Stage` from the field drop-down menu."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:75
msgid ""
"Once again, leave the second portion of the filter equation on :guilabel:`= "
"(equal sign)`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:77
msgid ""
"Lastly, highlight the default value in the third (and final) portion of the "
"second filter equation and type in :guilabel:`New`. With that completed, "
"Odoo will only target opportunities that are in the \"New\" stage of the "
"pipeline."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rstNone
msgid ""
"A standard scenario using filters in the Odoo Marketing Automation app."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:86
msgid ""
"Scenario #2: Narrow the target down to the event attendees that purchased a "
"specific ticket"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:88
msgid ""
"While in Edit mode on a campaign template form, select the "
":guilabel:`Target` field, and click :guilabel:`Search More` from the drop-"
"down menu. Then, scroll down (or search for) :guilabel:`Event` and select "
"it."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:92
msgid ""
"Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Click on"
" the default :guilabel:`ID` filter option in the first portion of the filter"
" equation. Doing so reveals a drop-down menu full of filter options. From "
"this drop-down, scroll down (or search for) :guilabel:`Event`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:97
msgid ""
"Click the the default :guilabel:`= (equal sign)` in the second portion of "
"the filter equation. This reveals a drop-down menu. On this menu, select "
":guilabel:`contains`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:100
msgid ""
"In the third (and final) empty portion of the filter equation, type in the "
"name of the event(s) that you would like Odoo to consider for this campaign "
"filter."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:106
msgid ""
"The second node will focus on targeting this campaign to attendees who "
"purchase a specific type of ticket to the aforementioned event(s) in the "
"first filter equation. To do that, select the default :guilabel:`ID` from "
"the first portion of the second filter equation, and scroll down (or search "
"for) :guilabel:`Event Ticket` from the field drop-down menu. Then, in that "
"same drop-down menu, select :guilabel:`Name`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:112
msgid ""
"Once again, click the the default :guilabel:`= (equal sign)` in the second "
"portion of the filter equation, and select :guilabel:`contains`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:115
msgid ""
"Lastly, in the third (and final) portion of the second filter equation, "
"which will be blank, type in the name of the ticket type that should be used"
" for the filter. In this case, :guilabel:`Standard` is the name of the event"
" ticket type for this sample filter."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rstNone
msgid "An event ticket filter in the Odoo Marketing Automation application."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:3
msgid "Testing and running a campaign"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:5
msgid ""
"Odoo gives users the ability to test marketing campaigns (and mailings) "
"before officially running them."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:8
msgid ""
"First, open the :guilabel:`Marketing Automation` application and click on a "
"campaign. Make sure the campaign already has activities configured on it (or"
" build a campaign by following the directions here on :doc:`this "
"documentation <workflow_activities>`). To start a test, click the "
":guilabel:`Launch a Test` button at the top of the template form."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rstNone
msgid "Launch a test button in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:17
msgid ""
"When clicked, a pop-up window appears. In the dropdown field choose a "
"specific record to run the test on, or create a brand new record by clicking"
" the :guilabel:`Search More...` link at the bottom of the dropdown menu, and"
" then click the :guilabel:`Create` button."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:21
msgid ""
"Once the record is selected, click :guilabel:`Continue`, and Odoo will "
"redirect to the campaign test page."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rstNone
msgid "Test screen in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:28
msgid ""
"Here, the name of the :guilabel:`Record` being tested is visible, along with"
" the precise time this test workflow was started. Beneath that is the first "
"activity (or activities) in the workflow."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:31
msgid ""
"To start a test, click the :guilabel:`Run` icon beside the first activity in"
" the workflow. When clicked, the page will reload, and Odoo will show the "
"various results (and analytics) connected to that specific activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rstNone
msgid "Workflow test progress in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:39
msgid ""
"Once all the workflow activities are completed, the test will end and be "
"moved to the :guilabel:`Completed` stage. To stop a test before all the "
"workflow activities are completed, click the :guilabel:`Stop` button."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:3
msgid "Marketing activities"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:5
msgid ""
"When creating a campaign in the :guilabel:`Marketing Automation` app, users "
"can plan marketing activities such as email or SMS campaigns. To get "
"started, navigate to the :guilabel:`Workflow` area, and click :guilabel:`Add"
" New Activity`. A blank activity template will appear where parameters can "
"be set for that specific activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:10
msgid ""
"When :guilabel:`Add New Activity` is selected, a blank activity template "
"will appear with the following customizable fields:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rstNone
msgid "An activity template in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:17
msgid ":guilabel:`Activity Name`: the title of the activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:18
msgid ""
":guilabel:`Activity Type`: choose between Email, Server Action (internal "
"Odoo operation), or SMS."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:19
msgid ""
":guilabel:`Mail Template`: choose from pre-configured templates (or create a"
" new one on-the-fly)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:20
msgid ":guilabel:`Trigger`: choose when this activity should be triggered."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:21
msgid ""
":guilabel:`Expiry Duration`: configure to stop the actions after a specific "
"amount of time (after the scheduled date). When selected, a "
":guilabel:`Cancel after` field appears, in which the user can choose how "
"many :guilabel:`Hours, Days, Weeks, or Months` they want the actions to "
"cease after the initial date."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:25
msgid ""
":guilabel:`Activity Filter`: domain related to this activity (and all "
"subsequent Child Activities)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:27
msgid ""
":guilabel:`Applied Filter`: activity will *only* be performed if it "
"satisfies the specified domain (filter)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:30
msgid ""
"After the activity's settings are fully configured, click :guilabel:`Save & "
"Close` to finish creating the activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:34
msgid "Workflow activity"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:36
msgid ""
"Once saved, the :guilabel:`Workflow Activity` will appear in Odoo, where "
"each activity will be shown as a graph by default. The configured trigger "
"time for that activity can be found to the left of the :guilabel:`Workflow "
"Activity` card."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:40
msgid ""
"In the :guilabel:`Workflow Activity` section, there is also the number of "
"activities that are successful or rejected. The :guilabel:`Success` and "
":guilabel:`Rejected` numbers are color-coded in the graph for easy reference"
" (in green and red, respectively)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rstNone
msgid "Typical workflow activity in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:49
msgid ""
"If the :guilabel:`Activity Type` of the activity is set to "
":guilabel:`Email`, there are more in-depth analytics beneath the "
":guilabel:`Workflow Activity` data detailing how many emails have been "
":guilabel:`Sent`, and what percentage of those have been "
":guilabel:`Clicked`, :guilabel:`Replied` to, or :guilabel:`Bounced`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:55
msgid "Child activities"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:57
msgid ""
"Odoo also has the option to :guilabel:`Add Child Activity`. *Child "
"Activities* are sub-activities that are connected to (and triggered by) the "
"activity above it, which is also known as its *Parent Activity*."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:61
msgid ""
"Odoo provides a number of triggering options to launch a :guilabel:`Child "
"Activity` - all of which depend on the trigger configurations related to the"
" parent activity. Under the desired parent activity, hover over "
":guilabel:`Add child activity`, and select the trigger:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:65
msgid ":guilabel:`Add Another Activity`: instantly add another activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:66
msgid ""
":guilabel:`Opened`: the next activity will be triggered if the (email) "
"recipient opens the mailing."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:68
msgid ""
":guilabel:`Not Opened`: the next activity will be triggered if the recipient"
" does not open the mailing."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:70
msgid ""
":guilabel:`Replied`: the next activity will be triggered if the recipient "
"replies to the mailing."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:71
msgid ""
":guilabel:`Not Replied`: the next activity will be triggered if the "
"recipient does not reply to the mailing."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:73
msgid ""
":guilabel:`Clicked`: the next activity will be triggered if the recipient "
"clicks on a link included in the mailing."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:75
msgid ""
":guilabel:`Not Clicked`: the next activity will be triggered if the "
"recipient does not click on a link included in the mailing."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:77
msgid ""
":guilabel:`Bounced`: the next activity will be triggered if the mailing is "
"bounced (not sent)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:79
msgid ""
"Once a trigger is selected, the user can configure the child activity (it "
"has the same configuration options as a regular activity) and click "
":guilabel:`Save & Close`` to finish creating the child activity."
msgstr ""
#: ../../content/applications/marketing/sms_marketing.rst:8
@@ -240,8 +832,8 @@ msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:67
msgid ""
"If you are on Odoo Online (SAAS) and have the Enterprise version, you "
"benefit from free trial credits to test the feature."
"If you are on Odoo Online and have the Enterprise version, you benefit from "
"free trial credits to test the feature."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:72
locale/pt_BR/LC_MESSAGES/sales.po
+853 -354
View File
File diff suppressed because it is too large Load Diff
locale/pt_BR/LC_MESSAGES/sphinx.po
+84 -2
View File
@@ -5,15 +5,17 @@
#
# Translators:
# Luis Gustavo Almeida <luis.gustavo@kmee.com.br>, 2022
# Silmar <pinheirosilmar@gmail.com>, 2022
# Martin Trigaux, 2022
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-10-04 12:47+0000\n"
"POT-Creation-Date: 2022-12-23 09:13+0000\n"
"PO-Revision-Date: 2022-10-04 12:54+0000\n"
"Last-Translator: Luis Gustavo Almeida <luis.gustavo@kmee.com.br>, 2022\n"
"Last-Translator: Martin Trigaux, 2022\n"
"Language-Team: Portuguese (Brazil) (https://www.transifex.com/odoo/teams/41243/pt_BR/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -154,6 +156,86 @@ msgstr ""
msgid "Content guidelines"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/legal.html:4
msgid "Legal"
msgstr "Legal"
#: ../../extensions/odoo_theme/layout_templates/legal.html:10
#: ../../extensions/odoo_theme/layout_templates/legal.html:17
msgid "Licenses"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/legal.html:25
msgid "Terms and Conditions"
msgstr "Termos e Condições"
#: ../../extensions/odoo_theme/layout_templates/legal.html:34
msgid "Odoo Enterprise Agreement"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/legal.html:36
msgid "Applies to self-hosting, Odoo.SH and Odoo Cloud."
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/legal.html:40
#: ../../extensions/odoo_theme/layout_templates/legal.html:42
#: ../../extensions/odoo_theme/layout_templates/legal.html:59
#: ../../extensions/odoo_theme/layout_templates/legal.html:61
#: ../../extensions/odoo_theme/layout_templates/legal.html:78
#: ../../extensions/odoo_theme/layout_templates/legal.html:80
msgid "Read"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/legal.html:43
#: ../../extensions/odoo_theme/layout_templates/legal.html:62
#: ../../extensions/odoo_theme/layout_templates/legal.html:81
msgid "English"
msgstr "Inglês"
#: ../../extensions/odoo_theme/layout_templates/legal.html:54
msgid "Odoo Partnership Agreement"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/legal.html:73
msgid "Terms Of Sale"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/legal.html:90
msgid "See also"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/legal.html:93
msgid "Archive of older agreements"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/legal.html:99
msgid "Other legal references"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/legal.html:105
msgid "Odoo Cloud Service Level Agreement (SLA)"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/legal.html:110
msgid "Odoo Cloud Acceptable Use Policy"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/legal.html:115
msgid "Odoo SA’s Privacy Policy"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/legal.html:120
msgid "Odoo SA’s GDPR Compliance Guide"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/legal.html:126
msgid "Contributor License Agreement"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/legal.html:133
msgid "German Tax Accounting Standards: Odoo’s guide to GoBD Compliance"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/page_toc.html:2
msgid "On this page"
msgstr ""