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

[I18N] Update translation terms from Transifex

Browse Source
This commit is contained in:
Odoo Translation Bot 2020-09-27 01:31:33 +02:00
parent e218ae4991
commit 5004122011
216 changed files with 179389 additions and 110130 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13920
locale/da/LC_MESSAGES/accounting.po
View File

File diff suppressed because it is too large Load Diff

12
locale/da/LC_MESSAGES/applications.po
View File

@ -3,17 +3,13 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Hans Henrik Gabelgaard <hhg@gabelgaard.org>, 2019
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: 2018-10-19 08:14+0000\n"
"Last-Translator: Hans Henrik Gabelgaard <hhg@gabelgaard.org>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -23,4 +19,4 @@ msgstr ""
#: ../../applications.rst:3
msgid "Applications"
msgstr "Ansøgninger"
msgstr ""

1735
locale/da/LC_MESSAGES/contributing.po Normal file
View File

File diff suppressed because it is too large Load Diff

527
locale/da/LC_MESSAGES/crm.po
View File

@ -4,17 +4,16 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2019
# JonathanStein <jstein@image.dk>, 2019
# Mads Søndergaard, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 12.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-03 08:44+0200\n"
"PO-Revision-Date: 2018-10-19 08:14+0000\n"
"Last-Translator: JonathanStein <jstein@image.dk>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Last-Translator: Mads Søndergaard, 2020\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -24,7 +23,7 @@ msgstr ""
#: ../../crm.rst:5
msgid "CRM"
msgstr "CRM"
msgstr ""
#: ../../crm/acquire_leads.rst:3
msgid "Acquire leads"
@ -38,42 +37,50 @@ msgstr ""
msgid ""
"The system can generate leads instead of opportunities, in order to add a "
"qualification step before converting a *Lead* into an *Opportunity* and "
"assigning to the right sales people. You can activate this mode from the CRM"
" Settings. It applies to all your sales channels by default. But you can "
"make it specific for specific channels from their configuration form."
"assigning to the right sales people."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:13
#: ../../crm/acquire_leads/convert.rst:9
msgid ""
"You can activate this mode from the CRM Settings. It applies to all your "
"sales channels by default. But you can make it specific for specific "
"channels from their configuration form."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:14
#: ../../crm/acquire_leads/generate_from_website.rst:41
#: ../../crm/optimize/onsip.rst:13 ../../crm/track_leads/lead_scoring.rst:12
#: ../../crm/acquire_leads/lead_mining.rst:8
#: ../../crm/optimize/gamification.rst:11 ../../crm/optimize/onsip.rst:13
#: ../../crm/optimize/partner_autocomplete.rst:9
#: ../../crm/track_leads/lead_scoring.rst:12
#: ../../crm/track_leads/prospect_visits.rst:12
msgid "Configuration"
msgstr "Konfiguration"
msgstr ""
#: ../../crm/acquire_leads/convert.rst:15
#: ../../crm/acquire_leads/convert.rst:16
msgid ""
"For this feature to work, go to :menuselection:`CRM --> Configuration --> "
"Settings` and activate the *Leads* feature."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:21
#: ../../crm/acquire_leads/convert.rst:22
msgid ""
"You will now have a new submenu *Leads* under *Leads* where they will "
"aggregate."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:28
#: ../../crm/acquire_leads/convert.rst:29
msgid "Convert a lead into an opportunity"
msgstr ""
#: ../../crm/acquire_leads/convert.rst:30
#: ../../crm/acquire_leads/convert.rst:31
msgid ""
"When you click on a *Lead* you will have the option to convert it to an "
"opportunity and decide if it should still be assigned to the same "
"channel/person and if you need to create a new customer."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:37
#: ../../crm/acquire_leads/convert.rst:38
msgid ""
"If you already have an opportunity with that customer Odoo will "
"automatically offer you to merge with that opportunity. In the same manner, "
@ -81,6 +88,40 @@ msgid ""
"customer already exists."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:44
msgid "Merge opportunities"
msgstr ""
#: ../../crm/acquire_leads/convert.rst:46
msgid ""
"Odoo will also automatically propose to merge opportunities if they have the"
" same email address. When merging opportunities, Odoo merges the information"
" into the opportunity which was created first, giving priority to the "
"information present on the first opportunity."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:51
msgid ""
"No information is lost: data from the other opportunity is logged in the "
"chatter and the information fields for easy access."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:57
msgid ""
"Would you find a duplicate yourself, ...you can also merge opportunities or "
"leads even if the system doesn't propose it."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:60
msgid ""
"Here’s how, from the list view. Select the opportunities or leads you want "
"to merge and the action button will appear. Then, you can select merge."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:67
msgid "It is also possible to merge more than 2 opportunities or leads."
msgstr ""
#: ../../crm/acquire_leads/generate_from_email.rst:3
msgid "Generate leads/opportunities from emails"
msgstr ""
@ -98,11 +139,11 @@ msgstr ""
#: ../../crm/acquire_leads/generate_from_email.rst:13
msgid ""
"Each sales channel can have its own email alias, to generate "
"Each sales teams can have its own email alias, to generate "
"leads/opportunities automatically assigned to it. It is useful if you manage"
" several sales teams with specific business processes. You will find the "
"configuration of sales channels under :menuselection:`Configuration --> "
"Sales Channels`."
"configuration of sales teams under :menuselection:`Configuration --> Sales "
"Teams`."
msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:3
@ -130,7 +171,7 @@ msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:16
msgid ""
"With the CRM app installed, you benefit from ready-to-use contact form on "
"With the CRM app installed, you benefit from a ready-to-use contact form on "
"your Odoo website that will generate leads/opportunities automatically."
msgstr ""
@ -149,35 +190,34 @@ msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:34
msgid ""
"You may want to know more from your visitor when they use the contact form "
"to contact you. You will then need to build a custom contact form on your "
"website. Those contact forms can generate multiple types of records in the "
"system (emails, leads/opportunities, project tasks, helpdesk tickets, "
"etc...)"
"to you will need to build a custom contact form on your website. These "
"contact forms can generate multiple types of records in the system (emails, "
"leads/opportunities, project tasks, helpdesk tickets, etc.)"
msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:43
msgid ""
"You will need to install the free *Form Builder* module. Only available in "
"You will need to install the free *Form Builder* module, only available in "
"Odoo Enterprise."
msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:52
msgid ""
"From any page you want your contact form to be in, in edit mode, drag the "
"form builder in the page and you will be able to add all the fields you "
"wish."
"First, go to the page where you want to put your contact form. In edit mode,"
" drag the form builder onto the page, and you will be able to add all the "
"fields you wish."
msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:59
msgid ""
"By default any new contact form will send an email, you can switch to "
"By default, any new contact form will send an email. You can switch to "
"lead/opportunity generation in *Change Form Parameters*."
msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:63
msgid ""
"If the same visitor uses the contact form twice, the second information will"
" be added to the first lead/opportunity in the chatter."
"If the same visitor uses the contact form twice, the second entry will be "
"added to the first lead/opportunity in the chatter."
msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:67
@ -186,9 +226,109 @@ msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:69
msgid ""
"When using a contact form, it is advised to use a qualification step before "
"assigning to the right sales people. To do so, activate *Leads* in CRM "
"settings and refer to :doc:`convert`."
"When using a contact form, you should use a qualification step before "
"assigning the form to the right sales people. To do so, activate *Leads* in "
"CRM settings and refer to :doc:`convert`."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:3
msgid "Lead mining"
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:4
msgid ""
"In any business, getting quality leads is essential to keep the business "
"growing. Lead mining allows you to generate leads from scratch directly from"
" your database. Target your leads based on a set of criteria such as the "
"country, the size of the company, the industry your leads are coming from to"
" make them relevant to your business."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:10
msgid ""
"For this feature to work, go to :menuselection:`CRM --> Configuration --> "
"Settings` and activate the **Lead Mining** feature."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:17
msgid "Start generating leads"
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:18
msgid ""
"You will now have a new button **Generate Leads** available in your "
"pipeline. You are also able to create lead mining requests from the "
":menuselection:`Configuration --> Lead Mining Requests` and trough "
":menuselection:`Leads --> Leads` where you have the **Generate Leads** "
"button."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:27
msgid ""
"From there, click on the **Generate Leads** button, a window where you will "
"be able to pick your criteria will pop up."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:34
msgid ""
"When choosing to target Companied and their contacts you can choose the "
"contacts you are getting based on Role or Seniority. When getting contact "
"information make sure to be aware of the latest EU regulation, get more "
"information about General Data Protection Regulation on `Odoo GDPR "
"<http://odoo.com/gdpr>`__,"
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:39
msgid ""
"You can decide to filter the leads you are getting depending on the size "
"(number of employees) of the companies. You can pick the countries your "
"leads are coming from. It is possible to pick multiple countries. You can "
"pick the industries your leads are coming from. It is possible to pick "
"multiple countries."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:43
msgid ""
"You can choose the salesperson and the Salesteam the lead will be assigned "
"to. You can also add tags to track your generated leads."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:47
msgid "The generated leads will have the name of the company."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:50
#: ../../crm/optimize/partner_autocomplete.rst:36
msgid "Pricing"
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:51
msgid ""
"This is an In-App Purchase feature, each generated lead will cost you one "
"credit. If you choose to get contact information each contact will also cost"
" us one additional credit. Here is the pricing for this `feature "
"<https://iap.odoo.com/iap/in-app-services/167?>`__, To buy credits you can "
"either go to :menuselection:`CRM --> Configuration --> Settings --> Buy "
"Credits`; or go to :menuselection: `Settings --> In-App Purchases --> View "
"my Services`."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:65
msgid ""
"The blue box will automatically tell you how many credits are going to be "
"consumed."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:68
msgid ""
"If you are on Odoo Online (SAAS) and have the Enterprise version, you "
"benefit from free trial credits to test the feature."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:71
msgid ""
":doc:`In-App Purchases (IAP) "
"<../../general/in_app_purchase/in_app_purchase>`"
msgstr ""
#: ../../crm/acquire_leads/send_quotes.rst:3
@ -237,6 +377,128 @@ msgstr ""
msgid "Optimize your Day-to-Day work"
msgstr ""
#: ../../crm/optimize/gamification.rst:3
msgid "How to motivate and reward my salespeople?"
msgstr ""
#: ../../crm/optimize/gamification.rst:5
msgid ""
"Challenging your employees to reach specific targets with goals and rewards "
"is an excellent way to reinforce good habits and improve your salespeople "
"productivity. The Gamification module gives you simple and creative ways to "
"motivate and evaluate your employees with real-time recognition and badges "
"inspired by game mechanics."
msgstr ""
#: ../../crm/optimize/gamification.rst:13
msgid ""
"Install the *Gamification* module, or the *CRM gamification* one, which adds"
" some useful data (goals and challenges) that can be used on *CRM/Sale*."
msgstr ""
#: ../../crm/optimize/gamification.rst:21
msgid "Create a challenge"
msgstr ""
#: ../../crm/optimize/gamification.rst:23
msgid ""
"Now, create your first challenge by going to :menuselection:`Settings --> "
"Gamification Tools --> Challenges`."
msgstr ""
#: ../../crm/optimize/gamification.rst:27
msgid ""
"As the gamification tool is a one-time technical setup, you need to activate"
" the technical features in order to access the configuration. To do so, go "
"to *Settings* and *Activate the developer mode*."
msgstr ""
#: ../../crm/optimize/gamification.rst:35
msgid ""
"A challenge is a mission that you send to your sales team. It can include "
"one or several goals, set for a specific period of time. Configure your "
"challenge as follows:"
msgstr ""
#: ../../crm/optimize/gamification.rst:38
msgid "Assign the salespeople to be challenged;"
msgstr ""
#: ../../crm/optimize/gamification.rst:39
msgid "Assign a responsible;"
msgstr ""
#: ../../crm/optimize/gamification.rst:40
msgid "Set up the periodicity along with the start and the end date;"
msgstr ""
#: ../../crm/optimize/gamification.rst:41
msgid "Select your goals;"
msgstr ""
#: ../../crm/optimize/gamification.rst:42
msgid "Set up your rewards (badges)."
msgstr ""
#: ../../crm/optimize/gamification.rst:45
msgid ""
"Badges are granted when a challenge is finished. This is either at the end "
"of a running period (eg: end of the month for a monthly challenge), at the "
"end date of a challenge (if no periodicity is set), or when the challenge is"
" manually closed."
msgstr ""
#: ../../crm/optimize/gamification.rst:49
msgid ""
"In the example below, 2 employees are being challenged with a *Monthly Sales"
" Target*. The challenge is based on 2 goals: the total amount invoiced and "
"number of new leads generated. At the end of the month, the winner will be "
"granted with a badge."
msgstr ""
#: ../../crm/optimize/gamification.rst:58
msgid "Set up goals"
msgstr ""
#: ../../crm/optimize/gamification.rst:60
msgid ""
"The users can be evaluated using goals and numerical objectives to reach."
msgstr ""
#: ../../crm/optimize/gamification.rst:62
msgid ""
"**Goals** are assigned through *challenges* that evaluate (see image above) "
"and compare members of a team throughout time."
msgstr ""
#: ../../crm/optimize/gamification.rst:66
msgid ""
"You can create a new goal on the fly from a *Challenge* by clicking on *Add "
"new item*, under *Goals*. Select the business object according to your "
"company's needs. Examples: number of new leads, time to qualify a lead, "
"total amount invoiced in a specific week, month or any other time frame "
"based on your management preferences, etc."
msgstr ""
#: ../../crm/optimize/gamification.rst:73
msgid ""
"Goals may include your database setup as well (e.g. set your company data "
"and a timezone, create new users, etc.)."
msgstr ""
#: ../../crm/optimize/gamification.rst:77
msgid "Set up rewards"
msgstr ""
#: ../../crm/optimize/gamification.rst:79
msgid ""
"For non-numerical achievements, **Badges** can be granted to users. From a "
"simple thank you to an exceptional achievement, a badge is an easy way to "
"express gratitude to a user for their good work. To create and grant badges "
"to your employees based on their performance, go to :menuselection:`Settings"
" --> Gamification Tools --> Badges`."
msgstr ""
#: ../../crm/optimize/google_calendar_credentials.rst:3
msgid "Synchronize Google Calendar with Odoo"
msgstr ""
@ -268,7 +530,7 @@ msgstr ""
#: ../../crm/optimize/google_calendar_credentials.rst:27
msgid "Enable the API."
msgstr ""
msgstr "Aktiver API'en."
#: ../../crm/optimize/google_calendar_credentials.rst:32
msgid ""
@ -285,6 +547,8 @@ msgid ""
"Select *Web browser (Javascript)* as calling source and *User data* as kind "
"of data."
msgstr ""
"Vælg *Web browser (Javascript)* som kalds kilde, og *Bruger data* som slags "
"på data."
#: ../../crm/optimize/google_calendar_credentials.rst:46
msgid ""
@ -343,7 +607,7 @@ msgstr ""
#: ../../crm/optimize/onsip.rst:6
msgid "Introduction"
msgstr "Introduktion"
msgstr ""
#: ../../crm/optimize/onsip.rst:8
msgid ""
@ -498,6 +762,75 @@ msgid ""
" not be logged in Odoo as the softphone acts as an independent separate app."
msgstr ""
#: ../../crm/optimize/partner_autocomplete.rst:3
msgid "Enrich your contacts base with Partner Autocomplete"
msgstr ""
#: ../../crm/optimize/partner_autocomplete.rst:5
msgid ""
"Parter Autocomplete helps you to enrich your contacts database with "
"corporate data. Select one of the companies suggested in the dropdown, and "
"quickly get all the information you need."
msgstr ""
#: ../../crm/optimize/partner_autocomplete.rst:11
msgid ""
"Go to :menuselection:`Settings --> Contacts` and activate the *Partner "
"Autocomplete* feature."
msgstr ""
#: ../../crm/optimize/partner_autocomplete.rst:18
msgid "Enrich your contacts with corporate data"
msgstr ""
#: ../../crm/optimize/partner_autocomplete.rst:22
msgid ""
"From any module, once you start to create a new contact typing the name of "
"it, the system will suggest a potential match. If you select it, the contact"
" will be populated with corporate data."
msgstr ""
#: ../../crm/optimize/partner_autocomplete.rst:23
msgid ""
"For example, after typing *Odoo*, you will get the following information:"
msgstr ""
#: ../../crm/optimize/partner_autocomplete.rst:33
msgid ""
"Partner Autocomplete also works if you enter a VAT number instead of a "
"company name."
msgstr ""
#: ../../crm/optimize/partner_autocomplete.rst:39
msgid ""
"*Partner Autocomplete* is an *In-App Purchase (IAP)* service, which requires"
" prepaid credits to be used. Each request will consume one credit."
msgstr ""
#: ../../crm/optimize/partner_autocomplete.rst:41
msgid ""
"To buy credits, go to :menuselection:`Settings --> Contacts --> Partner "
"Autocomplete or Odoo IAP --> View My Services` and select a package."
msgstr ""
#: ../../crm/optimize/partner_autocomplete.rst:44
msgid ""
"If you run out of credits, the only information that will be populated when "
"clicking on the suggested company will be the website link and the logo."
msgstr ""
#: ../../crm/optimize/partner_autocomplete.rst:46
msgid ""
"If you are on Odoo Online (SAAS) and you have the Enterprise version, you "
"benefit from free trial credits to test the feature."
msgstr ""
#: ../../crm/optimize/partner_autocomplete.rst:48
msgid ""
"Learn about our *Privacy Policy* `here "
"<https://iap.odoo.com/privacy#header_2>`_."
msgstr ""
#: ../../crm/optimize/setup.rst:3
msgid "Configure your VOIP Asterisk server for Odoo"
msgstr ""
@ -508,7 +841,7 @@ msgstr ""
#: ../../crm/optimize/setup.rst:9
msgid "Dependencies"
msgstr "Afhængigheder"
msgstr ""
#: ../../crm/optimize/setup.rst:11
msgid ""
@ -694,106 +1027,46 @@ msgstr ""
msgid "In Odoo, the configuration should be done in the user's preferences."
msgstr ""
#: ../../crm/optimize/setup.rst:206
#: ../../crm/optimize/setup.rst:210
msgid ""
"The SIP Login/Browser's Extension is the number you configured previously in"
" the sip.conf file. In our example, 1060. The SIP Password is the secret you"
" chose in the sip.conf file. The extension of your office's phone is not a "
"required field but it is used if you want to transfer your call from Odoo to"
" an external phone also configured in the sip.conf file."
" the sip.conf file (in our example: 1060)."
msgstr ""
#: ../../crm/optimize/setup.rst:212
msgid "The SIP Password is the secret you chose in the sip.conf file."
msgstr ""
#: ../../crm/optimize/setup.rst:214
msgid ""
"The configuration should also be done in the sale settings under the title "
"\"PBX Configuration\". You need to put the IP you define in the http.conf "
"file and the WebSocket should be: ws://127.0.0.1:8088/ws. The part "
"\"127.0.0.1\" needs to be the same as the IP defined previously and the "
"\"8088\" is the port you defined in the http.conf file."
"The extension of your office's phone is not a required field but it is used "
"if you want to transfer your call from Odoo to an external phone also "
"configured in the sip.conf file."
msgstr ""
#: ../../crm/optimize/setup.rst:217
msgid ""
"The configuration should also be done in the General Settings under the "
"\"Integrations\" section."
msgstr ""
#: ../../crm/optimize/setup.rst:222
msgid ""
"The PBX Server IP should be the same as the IP you define in the http.conf "
"file."
msgstr ""
#: ../../crm/optimize/setup.rst:224
msgid ""
"The WebSocket should be: ws://localhost:XXXX/ws where \"localhost\" needs to"
" be the same as the IP defined previously and \"XXXX\" needs to be the port "
"defined in the http.conf file."
msgstr ""
#: ../../crm/performance.rst:3
msgid "Analyze performance"
msgstr ""
#: ../../crm/performance/turnover.rst:3
msgid "Get an accurate probable turnover"
msgstr ""
#: ../../crm/performance/turnover.rst:5
msgid ""
"As you progress in your sales cycle, and move from one stage to another, you"
" can expect to have more precise information about a given opportunity "
"giving you an better idea of the probability of closing it, this is "
"important to see your expected turnover in your various reports."
msgstr ""
#: ../../crm/performance/turnover.rst:11
msgid "Configure your kanban stages"
msgstr ""
#: ../../crm/performance/turnover.rst:13
msgid ""
"By default, Odoo Kanban view has four stages: New, Qualified, Proposition, "
"Won. Respectively with a 10, 30, 70 and 100% probability of success. You can"
" add stages as well as edit them. By refining default probability of success"
" for your business on stages, you can make your probable turnover more and "
"more accurate."
msgstr ""
#: ../../crm/performance/turnover.rst:25
msgid ""
"Every one of your opportunities will have the probability set by default but"
" you can modify them manually of course."
msgstr ""
#: ../../crm/performance/turnover.rst:29
msgid "Set your opportunity expected revenue & closing date"
msgstr ""
#: ../../crm/performance/turnover.rst:31
msgid ""
"When you get information on a prospect, it is important to set an expected "
"revenue and expected closing date. This will let you see your total expected"
" revenue by stage as well as give a more accurate probable turnover."
msgstr ""
#: ../../crm/performance/turnover.rst:40
msgid "See the overdue or closing soon opportunities"
msgstr ""
#: ../../crm/performance/turnover.rst:42
msgid ""
"In your pipeline, you can filter opportunities by how soon they will be "
"closing, letting you prioritize."
msgstr ""
#: ../../crm/performance/turnover.rst:48
msgid ""
"As a sales manager, this tool can also help you see potential ways to "
"improve your sale process, for example a lot of opportunities in early "
"stages but with near closing date might indicate an issue."
msgstr ""
#: ../../crm/performance/turnover.rst:53
msgid "View your total expected revenue and probable turnover"
msgstr ""
#: ../../crm/performance/turnover.rst:55
msgid ""
"While in your Kanban view you can see the expected revenue for each of your "
"stages. This is based on each opportunity expected revenue that you set."
msgstr ""
#: ../../crm/performance/turnover.rst:62
msgid ""
"As a manager you can go to :menuselection:`CRM --> Reporting --> Pipeline "
"Analysis` by default *Probable Turnover* is set as a measure. This report "
"will take into account the revenue you set on each opportunity but also the "
"probability they will close. This gives you a much better idea of your "
"expected revenue allowing you to make plans and set targets."
msgstr ""
#: ../../crm/performance/win_loss.rst:3
msgid "Check your Win/Loss Ratio"
msgstr ""

371
locale/da/LC_MESSAGES/db_management.po
View File

@ -3,17 +3,13 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2019
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-27 11:08+0200\n"
"PO-Revision-Date: 2018-10-19 08:15+0000\n"
"Last-Translator: Martin Trigaux, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -110,123 +106,207 @@ msgstr ""
#: ../../db_management/db_online.rst:51
msgid "Upgrade"
msgstr "Opgrader"
msgstr ""
#: ../../db_management/db_online.rst:53
msgid ""
"Make sure to be connected to the database you want to upgrade and access the"
" database management page. On the line of the database you want to upgrade, "
"click on the \"Upgrade\" button."
"Upgrading your database to a newer version of Odoo is a complex operation "
"that require time and caution. It is extremely important that you fully test"
" the process before upgrading your production database."
msgstr ""
#: ../../db_management/db_online.rst:57
msgid ""
"Odoo releases new versions regularly (at least once a year), and upgrading "
"your database to enjoy new Odoo features is part of the Odoo Online "
"experience."
msgstr ""
#: ../../db_management/db_online.rst:60
msgid ""
"You have the possibility to choose the target version of the upgrade. By "
"default, we select the highest available version available for your "
"database; if you were already in the process of testing a migration, we will"
" automatically select the version you were already testing (even if we "
"released a more recent version during your tests)."
"The upgrade process can take some time, especially if you use multiple apps "
"or apps that manage sensitive data (e.g. Accounting, Inventory, etc.). In "
"general, the 'smaller' the database, the quickest the upgrade. A single-user"
" database that uses only CRM will be processed faster than a multi-company, "
"multi-user database that uses Accounting, Sales, Purchase and Manufacturing."
msgstr ""
#: ../../db_management/db_online.rst:66
msgid ""
"By clicking on the \"Test upgrade\" button an upgrade request will be "
"generated. If our automated system does not encounter any problem, you will "
"receive a \"Test\" version of your upgraded database."
"Unfortunately, it is impossible to give time estimates for every upgrade "
"request, since Odoo.com will test manually every database upgrade at least "
"once and will need to correct/adapt changes made to the standard Odoo Apps "
"(e.g. through Studio or through a Success Pack) on a case-by-case basis. "
"This can make the process slower, since requests are treated in the order "
"they arrive. This is especially true in the months following the release of "
"a new major version, which can lengthen the upgrade delay significantly."
msgstr ""
#: ../../db_management/db_online.rst:73
msgid ""
"If our automatic system detect an issue during the creation of your test "
"database, our dedicated team will have to work on it. You will be notified "
"by email and the process will take up to 4 weeks."
#: ../../db_management/db_online.rst:74
msgid "The upgrade process is quite simple from your point of view:"
msgstr ""
#: ../../db_management/db_online.rst:76
msgid "You request a test upgrade"
msgstr ""
#: ../../db_management/db_online.rst:77
msgid ""
"You will have the possibility to test it for 1 month. Inspect your data "
"(e.g. accounting reports, stock valuation, etc.), check that all your usual "
"flows work correctly (CRM flow, Sales flow, etc.)."
"Once all tests have been validated **by you**, you upgrade your actual "
"database"
msgstr ""
#: ../../db_management/db_online.rst:79
msgid ""
"The process to request a test or a production (*actual*) upgrade is the "
"same."
msgstr ""
#: ../../db_management/db_online.rst:81
msgid ""
"Once you are ready and that everything is correct in your test migration, "
"you can click again on the Upgrade button, and confirm by clicking on "
"Upgrade (the button with the little rocket!) to switch your production "
"database to the new version."
"First, make sure to be connected to the database you want to upgrade and "
"access the `database management page <https://www.odoo.com/my/databases>`__."
msgstr ""
#: ../../db_management/db_online.rst:89
#: ../../db_management/db_online.rst:84
msgid ""
"You have to have an active session with access to the Settings app in the "
"database you want to upgrade for the button to be visible."
msgstr ""
#: ../../db_management/db_online.rst:87
msgid ""
"On the line of the database you want to upgrade, click on the \"Cog\" menu. "
"If an newer version of Odoo is available, you will see an 'Upgrade' button."
msgstr ""
#: ../../db_management/db_online.rst:94
msgid ""
"You have the possibility to choose the target version of the upgrade. By "
"default, we select the highest available version available for your "
"database; if you were already in the process of testing an upgrade, we will "
"automatically select the version you were already testing (even if we "
"released a more recent version during your tests)."
msgstr ""
#: ../../db_management/db_online.rst:103
msgid ""
"By clicking on the \"Test upgrade\" button, an upgrade request will be "
"generated. Only one request can be made at time for each database; if a "
"request has already been made, you will see an 'Upgrade Queued' note instead"
" and asking another request will not be possible."
msgstr ""
#: ../../db_management/db_online.rst:108
msgid ""
"A test upgrade will create a copy of your database, upgrade it and make it "
"available to you automatically once successful. If this is the first test "
"you request for this particular database, a manual testing phase will be "
"done by Odoo.com - this could take time (up to several weeks). Subsequent "
"requests will not go through that manual testing step and will usually be "
"made available in a few hours. Once the test database is available, you "
"should receive an e-mail with the URL of the test database."
msgstr ""
#: ../../db_management/db_online.rst:116
msgid ""
"**Testing your database is the most important step of the upgrade process!**"
" Even though we test all upgrades manually, we do not know your work "
"processes. A change in standard worfklows of Odoo in new versions might "
"require you to change internal processes, or some of the customizations you "
"made through Odoo Studio might not work properly. *It is up to you to make "
"sure that everything works as it should!* You can report issues with your "
"test database through our `Support page <https://www.odoo.com/help>`__."
msgstr ""
#: ../../db_management/db_online.rst:124
msgid ""
"Make sure to do one last test of your upgrade right before the final upgrade"
" (e.g. the day before) to ensure everything will run smoothly. Downgrading "
"is not possible and post-poning an upgrade is always easier than being "
"prevented to work by an upgrade issue after the fact!"
msgstr ""
#: ../../db_management/db_online.rst:129
msgid ""
"Once you are ready and you have validated all your tests, you can click "
"again on the Upgrade button and confirm by clicking on Upgrade (the button "
"with the little rocket!) to switch your production database to the new "
"version. Your database will then be taken offline within the next 10 minutes"
" and will be upgraded automatically; you receive a confirmation e-mail once "
"the process is completed."
msgstr ""
#: ../../db_management/db_online.rst:140
msgid ""
"Your database will be taken offline during the upgrade (usually between "
"30min up to several hours for big databases), so make sure to plan your "
"migration during non-business hours."
msgstr ""
#: ../../db_management/db_online.rst:96
#: ../../db_management/db_online.rst:146
msgid "Duplicating a database"
msgstr ""
#: ../../db_management/db_online.rst:98
#: ../../db_management/db_online.rst:148
msgid ""
"Database duplication, renaming, custom DNS, etc. is not available for trial "
"databases on our Online platform. Paid Databases and \"One App Free\" "
"database can duplicate without problem."
msgstr ""
#: ../../db_management/db_online.rst:103
#: ../../db_management/db_online.rst:153
msgid ""
"In the line of the database you want to duplicate, you will have a few "
"buttons. To duplicate your database, just click **Duplicate**. You will have"
" to give a name to your duplicate, then click **Duplicate Database**."
msgstr ""
#: ../../db_management/db_online.rst:110
#: ../../db_management/db_online.rst:160
msgid ""
"If you do not check the \"For testing purposes\" checkbox when duplicating a"
" database, all external communication will remain active:"
msgstr ""
#: ../../db_management/db_online.rst:113
#: ../../db_management/db_online.rst:163
msgid "Emails are sent"
msgstr ""
#: ../../db_management/db_online.rst:115
#: ../../db_management/db_online.rst:165
msgid ""
"Payments are processed (in the e-commerce or Subscriptions apps, for "
"example)"
msgstr ""
#: ../../db_management/db_online.rst:118
#: ../../db_management/db_online.rst:168
msgid "Delivery orders (shipping providers) are sent"
msgstr ""
#: ../../db_management/db_online.rst:120
#: ../../db_management/db_online.rst:170
msgid "Etc."
msgstr ""
#: ../../db_management/db_online.rst:122
#: ../../db_management/db_online.rst:172
msgid ""
"Make sure to check the checkbox \"For testing purposes\" if you want these "
"behaviours to be disabled."
msgstr ""
#: ../../db_management/db_online.rst:125
#: ../../db_management/db_online.rst:175
msgid ""
"After a few seconds, you will be logged in your duplicated database. Notice "
"that the url uses the name you chose for your duplicated database."
msgstr ""
#: ../../db_management/db_online.rst:129
#: ../../db_management/db_online.rst:180
msgid "Duplicate databases expire automatically after 15 days."
msgstr ""
#: ../../db_management/db_online.rst:137
#: ../../db_management/db_online.rst:188
msgid "Rename a Database"
msgstr ""
#: ../../db_management/db_online.rst:139
#: ../../db_management/db_online.rst:190
msgid ""
"To rename your database, make sure you are connected to the database you "
"want to rename, access the `database management page "
@ -234,15 +314,15 @@ msgid ""
"to give a new name to your database, then click **Rename Database**."
msgstr ""
#: ../../db_management/db_online.rst:150
#: ../../db_management/db_online.rst:201
msgid "Deleting a Database"
msgstr ""
#: ../../db_management/db_online.rst:152
#: ../../db_management/db_online.rst:203
msgid "You can only delete databases of which you are the administrator."
msgstr ""
#: ../../db_management/db_online.rst:154
#: ../../db_management/db_online.rst:205
msgid ""
"When you delete your database all the data will be permanently lost. The "
"deletion is instant and for all the Users. We advise you to do an instant "
@ -250,45 +330,45 @@ msgid ""
"backup may be several hours old at that point."
msgstr ""
#: ../../db_management/db_online.rst:160
#: ../../db_management/db_online.rst:211
msgid ""
"From the `database management page <https://www.odoo.com/my/databases>`__, "
"on the line of the database you want to delete, click on the \"Delete\" "
"button."
msgstr ""
#: ../../db_management/db_online.rst:167
#: ../../db_management/db_online.rst:218
msgid ""
"Read carefully the warning message that will appear and proceed only if you "
"fully understand the implications of deleting a database:"
msgstr ""
#: ../../db_management/db_online.rst:173
#: ../../db_management/db_online.rst:224
msgid ""
"After a few seconds, the database will be deleted and the page will reload "
"automatically."
msgstr ""
#: ../../db_management/db_online.rst:177
#: ../../db_management/db_online.rst:228
msgid ""
"If you need to re-use this database name, it will be immediately available."
msgstr ""
#: ../../db_management/db_online.rst:179
#: ../../db_management/db_online.rst:230
msgid ""
"It is not possible to delete a database if it is expired or linked to a "
"Subscription. In these cases contact `Odoo Support "
"<https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_online.rst:183
#: ../../db_management/db_online.rst:234
msgid ""
"If you want to delete your Account, please contact `Odoo Support "
"<https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:7
msgid "On-premise Database management"
msgid "On-premises Database management"
msgstr ""
#: ../../db_management/db_premise.rst:10
@ -315,8 +395,9 @@ msgid ""
"message:"
msgstr ""
#: ../../db_management/db_premise.rst:31 ../../db_management/db_premise.rst:97
#: ../../db_management/db_premise.rst:130
#: ../../db_management/db_premise.rst:31
#: ../../db_management/db_premise.rst:110
#: ../../db_management/db_premise.rst:138
msgid "Solutions"
msgstr ""
@ -359,7 +440,7 @@ msgid "Do you have the updated version of Odoo 9?"
msgstr ""
#: ../../db_management/db_premise.rst:61
#: ../../db_management/db_premise.rst:190
#: ../../db_management/db_premise.rst:171
msgid ""
"From July 2016 onward, Odoo 9 now automatically change the uuid of a "
"duplicated database; a manual operation is no longer required."
@ -387,41 +468,60 @@ msgid ""
"invoicing proceed effortlessly for your and for us."
msgstr ""
#: ../../db_management/db_premise.rst:80
msgid "Check your network and firewall settings"
msgstr ""
#: ../../db_management/db_premise.rst:82
msgid ""
"The Update notification must be able to reach Odoo's subscription validation"
" servers. In other words, make sure that the Odoo server is able to open "
"outgoing connections towards:"
msgstr ""
#: ../../db_management/db_premise.rst:86
msgid "services.odoo.com on port 443 (or 80)"
msgstr ""
#: ../../db_management/db_premise.rst:87
msgid "services.openerp.com on port 443 (or 80) for older deployments"
msgstr ""
#: ../../db_management/db_premise.rst:89
msgid ""
"Once you activated your database, you must keep these ports open, as the "
"Update notification runs once a week."
msgstr ""
#: ../../db_management/db_premise.rst:95
msgid "Error message due to too many users"
msgstr ""
#: ../../db_management/db_premise.rst:84
#: ../../db_management/db_premise.rst:97
msgid ""
"If you have more users in your local database than provisionned in your Odoo"
" Enterprise subscription, you may encounter this message:"
msgstr ""
#: ../../db_management/db_premise.rst:93
#: ../../db_management/db_premise.rst:106
msgid ""
"When the message appears you have 30 days before the expiration. The "
"countdown is updated everyday."
msgstr ""
#: ../../db_management/db_premise.rst:99
#: ../../db_management/db_premise.rst:112
msgid ""
"**Add more users** on your subscription: follow the link and Validate the "
"upsell quotation and pay for the extra users."
msgstr ""
#: ../../db_management/db_premise.rst:102
msgid "or"
msgstr "eller"
#: ../../db_management/db_premise.rst:104
#: ../../db_management/db_premise.rst:114
msgid ""
"**Deactivate users** as explained in this `Documentation "
"<https://www.odoo.com "
"/documentation/user/11.0/db_management/documentation.html#deactivating-"
"users>`__ and **Reject** the upsell quotation."
"**Deactivate users** as explained in this `documentation <documentation.html"
"#deactivating-users>`_ and **Reject** the upsell quotation."
msgstr ""
#: ../../db_management/db_premise.rst:109
#: ../../db_management/db_premise.rst:117
msgid ""
"Once your database has the correct number of users, the expiration message "
"will disappear automatically after a few days, when the next verification "
@ -430,109 +530,58 @@ msgid ""
"message disappear right away."
msgstr ""
#: ../../db_management/db_premise.rst:116
#: ../../db_management/db_premise.rst:124
msgid "Database expired error message"
msgstr ""
#: ../../db_management/db_premise.rst:118
#: ../../db_management/db_premise.rst:126
msgid ""
"If your database reaches its expiration date before your renew your "
"subscription, you will encounter this message:"
msgstr ""
#: ../../db_management/db_premise.rst:126
#: ../../db_management/db_premise.rst:134
msgid ""
"This **blocking** message appears after a non-blocking message that lasts 30"
" days. If you fail to take action before the end of the countdown, the "
"database is expired."
msgstr ""
#: ../../db_management/db_premise.rst:134
#: ../../db_management/db_premise.rst:142
msgid ""
"Renew your subscription: follow the link and renew your subscription - note "
"that"
msgstr ""
#: ../../db_management/db_premise.rst:133
#: ../../db_management/db_premise.rst:141
msgid ""
"if you wish to pay by Wire Transfer, your subscription will effectively be "
"renewed only when the payment arrives, which can take a few days. Credit "
"card payments are processed immediately."
msgstr ""
#: ../../db_management/db_premise.rst:136
#: ../../db_management/db_premise.rst:144
msgid "Contact our `Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:138
#: ../../db_management/db_premise.rst:146
msgid ""
"None of those solutions worked for you? Please contact our `Support "
"<https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:145
msgid "Force an Update Notification"
msgstr ""
#: ../../db_management/db_premise.rst:147
msgid ""
"Update Notifications happen once every 7 days and keep your database up-to-"
"date with your Odoo Enterprise subscription. If you modify your subscription"
" (i.e. add more users, renew it for a year, etc.), your local database will "
"only be made aware of the change once every 7 days - this can cause "
"discrepancies between the state of your subscription and some notifications "
"in your App Switcher. When doing such an operation on your subscription, you"
" can force an Update using the following procedure:"
msgstr ""
#: ../../db_management/db_premise.rst:154
msgid "Connect to the database with the **Administrator** account"
msgstr ""
#: ../../db_management/db_premise.rst:155
msgid ""
"Switch to the Developer mode by using the **About** option in the top-right "
"menu (in V9) / in **Settings** (in V10): click on **Activate the developer"
" mode**"
msgstr ""
#: ../../db_management/db_premise.rst:158
msgid ""
"Navigate to the \"Settings\" menu, then \"Technical\" > \"Automation\" > "
"\"Scheduled Actions\""
msgstr ""
#: ../../db_management/db_premise.rst:160
msgid ""
"Find \"Update Notification\" in the list, click on it, and finally click on "
"the button \"**RUN MANUALLY**\""
msgstr ""
#: ../../db_management/db_premise.rst:162
msgid "Refresh the page, the \"Expiration\" notification should be gone"
msgstr ""
#: ../../db_management/db_premise.rst:165
msgid ""
"You may have kept the same UUID on different databases and we receive "
"information from those databases too. So please read :ref:`this "
"documentation <duplicate_premise>` to know how to change the UUID. After the"
" change you can force a ping to speed up the verification, your production "
"database will then be correctly identified."
msgstr ""
#: ../../db_management/db_premise.rst:174
msgid "Duplicate a database"
msgstr ""
#: ../../db_management/db_premise.rst:176
#: ../../db_management/db_premise.rst:157
msgid ""
"You can duplicate your database by accessing the database manager on your "
"server (<odoo-server>/web/database/manager). In this page, you can easily "
"duplicate your database (among other things)."
msgstr ""
#: ../../db_management/db_premise.rst:184
#: ../../db_management/db_premise.rst:165
msgid ""
"When you duplicate a local database, it is **strongly** advised to change "
"the duplicated database's uuid (Unniversally Unique Identifier), since this "
@ -541,13 +590,13 @@ msgid ""
"registration problems down the line."
msgstr ""
#: ../../db_management/db_premise.rst:193
#: ../../db_management/db_premise.rst:174
msgid ""
"The database uuid is currently accessible from the menu **Settings > "
"Technical > System Parameters**, we advise you to use a `uuid generator "
"<https://www.uuidgenerator.net>`__ or to use the unix command ``uuidgen`` to"
" generate a new uuid. You can then simply replace it like any other record "
"by clicking on it and using the edit button."
"The database uuid is currently accessible from the menu "
":menuselection:`Settings --> Technical --> System Parameters`, we advise you"
" to use a `uuid generator <https://www.uuidtools.com>`_ or to use the unix "
"command ``uuidgen`` to generate a new uuid. You can then simply replace it "
"like any other record by clicking on it and using the edit button."
msgstr ""
#: ../../db_management/documentation.rst:7
@ -605,76 +654,74 @@ msgstr ""
#: ../../db_management/documentation.rst:39
msgid ""
"In your Odoo instance, click on **Settings**. You will have a section "
"showing you the active users on your database. Click on **Manage access "
"rights.**"
"showing you the active users on your database. Click on **Manage Users.**"
msgstr ""
#: ../../db_management/documentation.rst:44
#: ../../db_management/documentation.rst:82
#: ../../db_management/documentation.rst:43
#: ../../db_management/documentation.rst:80
msgid "|settings|"
msgstr ""
#: ../../db_management/documentation.rst:44
#: ../../db_management/documentation.rst:43
msgid "|browse_users|"
msgstr ""
#: ../../db_management/documentation.rst:47
#: ../../db_management/documentation.rst:46
msgid "You'll then see the list of your users."
msgstr ""
#: ../../db_management/documentation.rst:52
#: ../../db_management/documentation.rst:51
msgid ""
"The pre-selected filter *Internal Users* shows your paying users (different "
"from the *Portal Users* which are free). If you remove this filter, you'll "
"get all your users (the ones you pay for and the portal ones)"
msgstr ""
#: ../../db_management/documentation.rst:57
#: ../../db_management/documentation.rst:56
msgid ""
"In your list of users, click on the user you want to deactivate. As soon as "
"you are on the userform, go with your mouse cursor on the status **Active** "
"(top right). Click on Active and you will notice that the status will change"
" to **Inactive** immediately."
"you are on the userform, click on the Action drop down menu, and then click "
"on Archive."
msgstr ""
#: ../../db_management/documentation.rst:66
#: ../../db_management/documentation.rst:64
msgid "The user is now deactivated."
msgstr ""
#: ../../db_management/documentation.rst:68
#: ../../db_management/documentation.rst:66
msgid "**Never** deactivate the main user (*admin*)"
msgstr ""
#: ../../db_management/documentation.rst:71
#: ../../db_management/documentation.rst:69
msgid "Uninstalling Apps"
msgstr ""
#: ../../db_management/documentation.rst:73
#: ../../db_management/documentation.rst:71
msgid ""
"Make sure you first test what you are about to do on a :ref:`duplicate "
"<duplicate_online>` of your database before making any changes (*especially*"
" installing/uninstalling apps)."
msgstr ""
#: ../../db_management/documentation.rst:77
#: ../../db_management/documentation.rst:75
msgid ""
"In your Odoo instance click on **Settings**; in this app, you will be able "
"to see how many applications you have installed. Click on **Browse Apps** to"
" access the list of your installed applications."
msgstr ""
#: ../../db_management/documentation.rst:82
#: ../../db_management/documentation.rst:80
msgid "|browse_apps|"
msgstr ""
#: ../../db_management/documentation.rst:85
#: ../../db_management/documentation.rst:83
msgid ""
"In your applications' dashboard, you will see all the icons of your "
"applications. Click on the application you want to uninstall. Then, on the "
"form of the application, click on **Uninstall**."
msgstr ""
#: ../../db_management/documentation.rst:92
#: ../../db_management/documentation.rst:90
msgid ""
"Some applications have dependencies, like Invoicing, eCommerce, etc. "
"Therefore, the system will give you a warning message to advise you of what "
@ -684,20 +731,20 @@ msgid ""
" click **Confirm**."
msgstr ""
#: ../../db_management/documentation.rst:99
#: ../../db_management/documentation.rst:97
msgid ""
"Last, after having checked the warning message (if any), click **Confirm**."
msgstr ""
#: ../../db_management/documentation.rst:104
#: ../../db_management/documentation.rst:102
msgid "You have finished uninstalling your application."
msgstr ""
#: ../../db_management/documentation.rst:107
#: ../../db_management/documentation.rst:105
msgid "Good to know"
msgstr ""
#: ../../db_management/documentation.rst:109
#: ../../db_management/documentation.rst:107
msgid ""
"**Uninstalling apps, managing users, etc. is up to you**: no one else can "
"know if your business flow is broken better than you. If we were to "
@ -707,7 +754,7 @@ msgid ""
"operations."
msgstr ""
#: ../../db_management/documentation.rst:115
#: ../../db_management/documentation.rst:113
msgid ""
"**Odoo Apps have dependencies**: this means that you may need to install "
"modules that you do not actively use to access some features of Odoo you "
@ -717,7 +764,7 @@ msgid ""
"to work properly."
msgstr ""
#: ../../db_management/documentation.rst:122
#: ../../db_management/documentation.rst:120
msgid ""
"**Always test app installation/removal on a duplicate** (or on a free trial "
"database): that way you can know what other apps may be required, etc. This "

761
locale/da/LC_MESSAGES/discuss.po
View File

File diff suppressed because it is too large Load Diff

582
locale/da/LC_MESSAGES/ecommerce.po
View File

@ -3,20 +3,13 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2019
# Pernille Kristensen <pernillekristensen1994@gmail.com>, 2019
# Sanne Kristensen <sanne@vkdata.dk>, 2019
# lhmflexerp <lhm@flexerp.dk>, 2019
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: 2018-10-19 08:15+0000\n"
"Last-Translator: lhmflexerp <lhm@flexerp.dk>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -26,11 +19,11 @@ msgstr ""
#: ../../ecommerce.rst:5
msgid "eCommerce"
msgstr "Webshop"
msgstr ""
#: ../../ecommerce/getting_started.rst:3
msgid "Get started"
msgstr "Kom igang"
msgstr ""
#: ../../ecommerce/getting_started/catalog.rst:3
msgid "How to customize my catalog page"
@ -38,7 +31,7 @@ msgstr ""
#: ../../ecommerce/getting_started/catalog.rst:6
msgid "Product Catalog"
msgstr "Varekartotek"
msgstr ""
#: ../../ecommerce/getting_started/catalog.rst:8
msgid ""
@ -468,7 +461,7 @@ msgstr ""
#: ../../ecommerce/maximizing_revenue/promo_code.rst:9
#: ../../ecommerce/maximizing_revenue/reviews.rst:13
msgid "Setup"
msgstr "Opsætning"
msgstr ""
#: ../../ecommerce/maximizing_revenue/promo_code.rst:11
msgid ""
@ -581,7 +574,7 @@ msgid ""
msgstr ""
#: ../../ecommerce/maximizing_revenue/upselling.rst:3
msgid "How to sell pricier product alternatives (upselling)"
msgid "How to sell pricier alternative products (upselling)"
msgstr ""
#: ../../ecommerce/maximizing_revenue/upselling.rst:5
@ -610,7 +603,7 @@ msgstr ""
#: ../../ecommerce/overview.rst:3
msgid "Overview"
msgstr "Oversigt"
msgstr ""
#: ../../ecommerce/overview/introduction.rst:3
msgid "Introduction to Odoo eCommerce"
@ -632,11 +625,11 @@ msgstr ""
#: ../../ecommerce/overview/introduction.rst:15
msgid "Pricing"
msgstr "Priser"
msgstr ""
#: ../../ecommerce/overview/introduction.rst:16
msgid "Taxes"
msgstr "Moms"
msgstr ""
#: ../../ecommerce/overview/introduction.rst:17
msgid "Checkout process"
@ -648,7 +641,7 @@ msgstr ""
#: ../../ecommerce/overview/introduction.rst:19
msgid "Payment"
msgstr "Betaling"
msgstr ""
#: ../../ecommerce/overview/introduction.rst:20
msgid "Shipping & Tracking"
@ -666,307 +659,6 @@ msgstr ""
msgid "Get paid"
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:3
msgid "How to get paid with Authorize.Net"
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:5
msgid ""
"Authorize.Net is one of the most popular eCommerce payment platforms in "
"North America. Unlike most of the other payment acquirers compatible with "
"Odoo, Authorize.Net can be used as `payment gateway "
"<https://www.authorize.net/solutions/merchantsolutions/pricing/?p=gwo>`__ "
"only. That way you can use the `payment processor or merchant "
"<https://www.authorize.net/partners/resellerprogram/processorlist/>`__ that "
"you like."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:12
msgid "Create an Authorize.Net account"
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:14
msgid ""
"Create an `Authorize.Net account <https://www.authorize.net>`__ by clicking "
"'Get Started'."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:16
msgid ""
"In the pricing page, press *Sign up now* if you want to use Authorize.net as"
" both payment gateway and merchant. If you want to use your own merchant, "
"press the related option."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:23
msgid "Go through the registration steps."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:24
msgid ""
"The account is set as a test account by default. You can use this test "
"account to process a test transaction from Odoo."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:26
msgid "Once ready, switch to **Production** mode."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:30
#: ../../ecommerce/shopper_experience/paypal.rst:74
msgid "Set up Odoo"
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:31
msgid ""
"Activate Authorize.Net in Odoo from :menuselection:`Website or Sales or "
"Accounting --> Settings --> Payment Acquirers`."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:33
msgid "Enter both your **Login ID** and your **API Transaction Key**."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:39
msgid ""
"To get those credentials in Authorize.Net, you can rely on *API Login ID and"
" Transaction Key* video of `Authorize.Net Video Tutorials "
"<https://www.authorize.net/videos/>`__. Such videos give meaningful insights"
" about how to set up your Authorize.Net account according to your needs."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:47
#: ../../ecommerce/shopper_experience/paypal.rst:102
msgid "Go live"
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:48
msgid ""
"Your configuration is now ready! You can make Authorize.Net visible on your "
"merchant interface and activate the **Production** mode."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:55
msgid ""
"Credentials provided by Authorize.net are different for both test and "
"production mode. Don't forget to update them in Odoo when you turn on the "
"production mode."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:61
msgid "Assess Authorize.Net as payment solution"
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:62
msgid ""
"You can test and assess Authorize.Net for free by creating a `developer "
"account <https://developer.authorize.net>`__."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:64
msgid ""
"Once the account created you receive sandbox credentials. Enter them in Odoo"
" as explained here above and make sure you are still in *Test* mode."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:68
msgid ""
"You can also log in to `Authorize.Net sandbox platform "
"<https://sandbox.authorize.net/>`__ to configure your sandbox account."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:71
msgid ""
"To perform ficticious transactions you can use fake card numbers provided in"
" the `Authorize.Net Testing Guide "
"<https://developer.authorize.net/hello_world/testing_guide/>`__."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:76
#: ../../ecommerce/shopper_experience/paypal.rst:154
msgid ":doc:`payment`"
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:77
#: ../../ecommerce/shopper_experience/payment.rst:111
#: ../../ecommerce/shopper_experience/paypal.rst:155
msgid ":doc:`payment_acquirer`"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:3
msgid "How to get paid with payment acquirers"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:5
msgid ""
"Odoo embeds several payment methods to get paid on eCommerce, Sales and "
"Invoicing apps."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:10
msgid "What are the payment methods available"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:13
msgid "Wire transfer"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:15
msgid ""
"Wire Transfer is the default payment method available. The aim is providing "
"your customers with your bank details so they can pay on their own via their"
" bank. This is very easy to start with but slow and inefficient process-"
"wise. Opt for online acquirers as soon as you can!"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:21
msgid "Payment acquirers"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:23
msgid ""
"Redirect your customers to payment platforms to collect money effortless and"
" track the payment status (call-back). Odoo supports more and more platforms"
" over time:"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:27
msgid "`Paypal <paypal.html>`__"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:28
msgid "Ingenico"
msgstr "Ingenico"
#: ../../ecommerce/shopper_experience/payment.rst:29
msgid "Authorize.net"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:30
msgid "Adyen"
msgstr "Adyen"
#: ../../ecommerce/shopper_experience/payment.rst:31
msgid "Buckaroo"
msgstr "Buckaroo"
#: ../../ecommerce/shopper_experience/payment.rst:32
msgid "PayUmoney"
msgstr "PayUmoney"
#: ../../ecommerce/shopper_experience/payment.rst:33
msgid "Sips"
msgstr "Sips"
#: ../../ecommerce/shopper_experience/payment.rst:34
msgid "Stripe"
msgstr "Stribe"
#: ../../ecommerce/shopper_experience/payment.rst:38
msgid "How to go live"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:40
msgid ""
"Once the payment method ready, make it visible in the payment interface and "
"activate the **Production** mode."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:48
msgid "How to let customers save and reuse credit cards"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:49
msgid ""
"To ease the payment of returning customers, you can let them save and reuse "
"a credit card if they want to. If so, a payment token will be saved in Odoo."
" This option is available with Ingenico and Authorize.net."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:54
#: ../../ecommerce/shopper_experience/payment.rst:68
msgid "You can turn this on from the acquirer configuration form."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:61
msgid "How to debit credit cards to pay subscriptions"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:62
msgid ""
"`Odoo Subscription <https://www.odoo.com/page/subscriptions>`__ allows to "
"bill services automatically on a recurring basis. Along with it, you can "
"have an automatic debit of the customer's credit card."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:66
msgid "This option is available with Ingenico and Authorize.net."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:73
msgid ""
"That way a payment token will be recorded when the customer goes for the "
"subscription and an automatic debit will occur whenever an invoice is issued"
" from the subscription."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:79
msgid "How to use other acquirers (advanced)"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:81
msgid ""
"Odoo can submit single payment requests and redirect to any payment "
"acquirer. But there is no call-back, i.e. Odoo doesn't track the transaction"
" status. So you will confirm orders manually once you get paid."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:85
msgid "How to:"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:87
msgid "Switch to developer mode."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:89
msgid "Take the **Custom** payment method."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:91
msgid ""
"Set up the payment form (S2S Form Template) as instructed by your payment "
"acquirer. You can start from *default_acquirer_button* that you can "
"duplicate."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:96
msgid "Other configurations"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:98
msgid ""
"Odoo can also be used for more advanced payment processes like installment "
"plans (e.g. `Paypal Installment Plans "
"<https://developer.paypal.com/docs/classic/paypal-payments-standard"
"/integration-guide/installment_buttons>`__)."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:102
msgid ""
"Such a customization service is made on-demand by our technical experts "
"based on your own requirements. A business advisor can reach you out for "
"such matter. `Contact us. <https://www.odoo.com/page/contactus>`__"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:109
msgid ":doc:`paypal`"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:110
msgid ":doc:`wire_transfer`"
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:3
msgid "How to manage orders paid with payment acquirers"
msgstr ""
@ -1040,7 +732,7 @@ msgid ""
"orders straight on."
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:53
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:54
msgid ""
"If you choose this mode you are requested to select a payment journal in "
"order to record payments in your books. This payment is automatically "
@ -1048,219 +740,33 @@ msgid ""
"account** if you get paid immediately on your bank account. If you don't you"
" can create a specific journal for the payment acquirer (type = Bank). That "
"way, you can track online payments in an intermediary account of your books "
"until you get paid into your bank account (see `How to register credit card "
"payments "
"<../../accounting/receivables/customer_payments/credit_cards.html>`__)."
"until you get paid into your bank account (see "
":doc:`../../general/payment_acquirers/payment_acquirers`)."
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:64
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:63
msgid "Capture the payment after the delivery"
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:65
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:64
msgid ""
"With this mode, the order is confirmed but the amount is kept on hold. Once "
"the delivery processed, you can capture the payment from Odoo. This mode is "
"only available with Authorize.net."
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:72
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:71
msgid ""
"To capture the payment, open the transaction from the order. Then click "
"*Capture Transaction*."
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:78
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:77
msgid ""
"With other payment acquirers, you can manage the capture in their own "
"interfaces, not from Odoo."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:3
msgid "How to get paid with Paypal"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:5
msgid ""
"Paypal is the easiest online payment acquirer to configure. It is also the "
"only one without any subscription fee. We definitely advise it to any "
"starter."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:11
msgid "Set up your Paypal account"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:13
msgid ""
"Create a `Paypal Business Account <https://www.paypal.com>`__ or upgrade "
"your account to *Business account* if you have a basic account."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:16
msgid ""
"Log in to `Paypal <https://www.paypal.com>`__ and open the settings of your "
"**Profile**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:22
msgid "Now enter the menu **My selling tools**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:27
msgid "Let's start with the **Website Preferences**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:29
msgid ""
"Turn on **Auto Return** and enter the **Return URL**: "
"<odoo_instance_url>/shop/confirmation. Verify that this address uses the "
"correct protocol (HTTP/HTTPS)."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:36
msgid ""
"Turn on **Payment Data Transfer**. When saving, an **Identity Token** is "
"generated. You will be later requested to enter it in Odoo."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:43
msgid ""
"Then, get back to your profile to activate the **Instant Payment "
"Notification (IPN)** in *My selling tools*."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:46
msgid "Enter the **Notification URL**: <odoo_instance_url>/payment/paypal/ipn"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:51
msgid ""
"Now you must change the encoding format of the payment request sent by Odoo "
"to Paypal. To do so, get back to *My selling tools* and click **PayPal "
"button language encoding** in *More Selling Tools* section."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:58
msgid ""
"Then, click *More Options* and set the two default encoding formats as "
"**UTF-8**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:66
msgid ""
"If you want your customers to pay without creating a Paypal account, "
"**Paypal Account Optional** needs to be turned on."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:75
msgid ""
"Open Paypal setup form in :menuselection:`Website or Sales or Accounting -->"
" Settings --> Payment Acquirers+`. Enter both your **Email ID** and your "
"**Merchant ID** and check **Use IPN**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:82
msgid ""
"They are both provided in your Paypal profile, under :menuselection:`My "
"business info`."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:85
msgid ""
"Enter your **Identity Token** in Odoo (from *Auto Return* option). To do so,"
" open the *Settings* and activate the **Developer Mode**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:91
msgid ""
"Then, go to :menuselection:`Settings --> Technical --> Parameters --> System"
" Parameters` and create a parameter with following values:"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:94
msgid "Key: payment_paypal.pdt_token"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:95
msgid "Value: your Paypal *Identity Token*"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:103
msgid ""
"Your configuration is now ready! You can make Paypal visible on your "
"merchant interface and activate the **Production mode**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:112
msgid "Transaction fees"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:114
msgid ""
"You can charge an extra to the customer to cover the transaction fees Paypal"
" charges you. Once redirected to Paypal, your customer sees an extra applied"
" to the order amount."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:117
msgid ""
"To activate this, go to the *Configuration* tab of Paypal config form in "
"Odoo and check *Add Extra Fees*. Default fees for US can be seen here below."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:123
msgid ""
"To apply the right fees for your country, please refer to `Paypal Fees "
"<https://www.paypal.com/webapps/mpp/paypal-fees>`__."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:128
msgid "Test the payment flow"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:130
msgid ""
"You can test the entire payment flow thanks to Paypal Sandbox accounts."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:132
msgid ""
"Log in to `Paypal Developer Site <https://developer.paypal.com>`__ with your"
" Paypal credentials. This will create two sandbox accounts:"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:136
msgid ""
"A business account (to use as merchant, e.g. "
"pp.merch01-facilitator@example.com)."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:137
msgid ""
"A default personal account (to use as shopper, e.g. "
"pp.merch01-buyer@example.com)."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:139
msgid ""
"Log in to `Paypal Sandbox <https://www.sandbox.paypal.com>`__ with the "
"merchant account and follow the same configuration instructions."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:142
msgid ""
"Enter your sandbox credentials in Odoo and make sure Paypal is still set on "
"*Test* mode. Also, make sure the confirmation mode of Paypal is not "
"*Authorize & capture the amount, confirm the SO and auto-validate the "
"invoice on acquirer confirmation*. Otherwise a confirmed invoice will be "
"automatically generated when the transaction is completed."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:150
msgid "Run a test transaction from Odoo using the sandbox personal account."
msgstr ""
#: ../../ecommerce/shopper_experience/portal.rst:3
msgid "How customers can access their customer account"
msgstr ""
@ -1276,7 +782,7 @@ msgstr ""
#: ../../ecommerce/shopper_experience/portal.rst:14
msgid "Sign up"
msgstr "Tilmeld dig"
msgstr ""
#: ../../ecommerce/shopper_experience/portal.rst:16
msgid ""
@ -1306,54 +812,6 @@ msgid ""
"will see all the documents whose the customer belongs to this company."
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:3
msgid "How to get paid with wire transfers"
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:5
msgid ""
"**Wire Transfer** is the default payment method available. The aim is "
"providing your customers with your bank details so they can pay on their "
"own. This is very easy to start with but slow and inefficient process-wise. "
"Opt for payment acquirers as soon as you can!"
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:13
msgid "How to provide customers with payment instructions"
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:14
msgid ""
"Put your payment instructions in the **Thanks Message** of your payment "
"method."
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:19
msgid "They will appear to the customers when they place an order."
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:26
msgid "How to manage an order once you get paid"
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:28
msgid ""
"Whenever a customer pays by wire transfer, the order stays in an "
"intermediary stage **Quotation Sent** (i.e. unpaid order). When you get "
"paid, you confirm the order manually to launch the delivery."
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:35
msgid "How to create other manual payment methods"
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:37
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 ""
#: ../../ecommerce/taxes.rst:3
msgid "Collect taxes"
msgstr ""

284
locale/da/LC_MESSAGES/email_marketing.po Normal file
View File

@ -0,0 +1,284 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: da\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../email_marketing.rst:5
msgid "Email Marketing"
msgstr ""
#: ../../email_marketing/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:3
msgid "Work with Mailing Lists"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:5
msgid ""
"Mailing lists can be a goldmine for your company’s marketing department as "
"they can provide leads for sales, focus groups for testing new products, and"
" consumers to provide feedback on satisfaction, for example."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:10
msgid "Create mailing lists"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:12
msgid ""
"Go to :menuselection:`Mailing lists --> Mailing lists --> Create`. Enable "
"the option *Is Public* to make the list visible for users when "
"unsubscribing."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:19
msgid ""
"Once your mailing list is created, you can manually add contacts clicking on"
" *Create*. *Import* a list of contacts if you have it from a previous tool."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:23
msgid "Linking a mailing list to my website"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:26
msgid ""
"Create a mailing list called Newsletter, as you use this strategy to "
"advertise and communicate new ideas to subscribers interested in listening."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:27
msgid ""
"Go to your *Website*, add a *Newsletter* block and choose the respective "
"mailing list."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:34
msgid "Contacts"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:36
msgid ""
"Under :menuselection:`Mailing Lists --> Mailing List Contacts` see a list of"
" all contacts under all your mailing lists, and the ones you individually "
"created here."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:43
msgid ""
"Open a contact form to see or add different mailing lists to which the "
"contact is or will be part of."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:51
#: ../../email_marketing/overview/manage_unsubscriptions.rst:46
msgid ":doc:`send_emails`"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:3
msgid "Manage Unsubscriptions and Blacklist"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:5
msgid ""
"It is best practice, and legally required, to allow recipients to "
"unsubscribe from mailing lists as you do not want your audience to think "
"that your company is using any tactics that are dishonest or spammy."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:10
msgid "Enable the Blacklist feature"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:12
msgid ""
"Go to :menuselection:`Configuration --> Settings` and enable the option "
"*Blacklist Option when Unsubscribing*."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:19
msgid ""
"Now, once the user clicks on the *Unsubscribe* link on your email, he is "
"redirected to the following page:"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:28
msgid ""
"After clicking on the unsubscribe button when using the test feature, you "
"are sent to an error page (*error 403 - Access Denied*). If you want to be "
"sure the link is working properly, create your mass mail and send it only to"
" a personal email."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:32
msgid ""
"In addition to having the option of unsubscribing from specific mailing "
"lists, the user can also blacklist himself, meaning that he will not receive"
" *any* more emails from you."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:36
msgid ""
"The mailing list has to be configured as *Public* in order to be visible for"
" users."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:38
msgid ""
"Under :menuselection:`Configuration --> Blacklist`, blacklisted email "
"addresses are shown."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:39
msgid ""
"When opening the record, as a *Log note*, a description-history is kept."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:47
msgid ":doc:`mailing_lists`"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:3
msgid "Send Emails Marketing and Manage Campaigns"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:5
msgid ""
"Emails allow you to effectively, and at a low cost, reach a large number of "
"consumers while being able to customize your message in a way that resonates"
" with them. It is measurable, and a call-to-action oriented channel."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:10
msgid "Choose the right target and create the message"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:12
msgid "Go to :menuselection:`Mailings --> Create`."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:14
msgid ""
"Choosing *Contacts* as *Recipients* (for example), allows you to add "
"specifications to match just certain contacts, filtering your target."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:21
msgid ""
"With a trial databases, you have a limit of 50 emails per day; on Odoo SH "
"Cloud Platform the limit is 200. There is a possibility to increase these "
"numbers by contacting Odoo Support. To contact Support, `click here "
"<https://www.odoo.com/help>`_."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:25
msgid ""
"Under *Mail Body*, choose a layout and make the modifications needed by "
"dragging, dropping and double-clicking on content. Note that it is possible "
"to start from scratch selecting the *blank* template option."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:34
msgid ""
"Under *Settings*, you can assign someone else as the responsible sender if "
"you do not want it to be you. To do so, change the email address used as the"
" sender (*Send From*)."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:37
msgid ""
"With the *Reply To* radio button, you can also choose to gather answers "
"either on the respective recipients’ records or on a specific email address."
" Note that this option is not available if you target mailing contacts or "
"contacts as recipients."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:45
msgid "Test, send or schedule a mailing"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:53
msgid ""
"*Save*: the work is allocated in the *draft* column in the Kanban view. "
"Modifications can be made while being in this stage. The option *Discard* "
"deletes the email."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:54
msgid ""
"Click on *Test* and send your message to one, or even multiple, test "
"contacts to avoid errors."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:56
msgid ""
"*Send* triggers the email with the next run and put the work on the *queue* "
"column in the Kanban view."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:58
msgid ""
"*Schedule* allows you to choose a date and time, and puts the email in the "
"*queue* column in the Kanban view."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:61
msgid ""
"The daily limit is applied for **all emails** sent, in other words, "
"throughout all applications. Therefore, if at the end of the day you have "
"remaining ones to be sent, note that they *will not* be sent automatically "
"the next day. You need to force that by opening the email and clicking on "
"*Retry*."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:67
msgid "Manage campaigns"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:69
msgid ""
"Go to :menuselection:`Configuration --> Settings` and enable *Mailing "
"Campaigns*."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:71
msgid ""
"The campaign option is effective as it allows you to organize your marketing"
" efforts and have a centralized view of its metrics."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:72
msgid "Go to *Campaign* and click on *Create* to start one."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:80
msgid ""
"If you use the SMS and Social Marketing applications, as well as the Push "
"Notification feature, you see the option to create content for those "
"channels. You also see the *Campaign* menu within those applications. All of"
" this is possible because the applications work integrated."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:85
msgid ":doc:`../../discuss/advanced/email_servers`"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:86
msgid ":doc:`../../social_marketing/overview/campaigns`"
msgstr ""

429
locale/da/LC_MESSAGES/events.po Normal file
View File

@ -0,0 +1,429 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: da\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../events.rst:5
msgid "Events"
msgstr ""
#: ../../events/integrations.rst:3
msgid "Integrations"
msgstr ""
#: ../../events/integrations/integration_sms.rst:3
msgid "Communicating about my Event using SMS Text Messages"
msgstr ""
#: ../../events/integrations/integration_sms.rst:5
msgid ""
"Using SMS as a communication strategy for your event establishes interaction"
" between organizers, attendees, speakers and further targets. It allows your"
" message to be heard whether the goal is to send out reminders, teasers or "
"to advertise."
msgstr ""
#: ../../events/integrations/integration_sms.rst:10
#: ../../events/overview/tickets.rst:9 ../../events/overview/track_talks.rst:9
msgid "Configuration"
msgstr ""
#: ../../events/integrations/integration_sms.rst:13
msgid ""
"Under *Communication* SMS is a standard feature. That means nothing needs to"
" be enabled or installed."
msgstr ""
#: ../../events/integrations/integration_sms.rst:16
msgid ""
"On the other hand, to contact the speakers of your event, you need the *SMS "
"Marketing* application installed, and to enable *Schedule & Tracks* under "
":menuselection:`Events --> Configuration --> Settings`."
msgstr ""
#: ../../events/integrations/integration_sms.rst:23
msgid ""
"The *Schedule & Tracks* feature allows you to manage the agenda and speakers"
" of your event. For more details watch: `Creating an agenda for your event "
"<https://www.odoo.com/slides/slide/create-an-agenda-for-your-"
"event-717?fullscreen=1>`_."
msgstr ""
#: ../../events/integrations/integration_sms.rst:28
msgid "Send SMSs to attendees"
msgstr ""
#: ../../events/integrations/integration_sms.rst:30
msgid ""
"Under *Communication*, the message’s target is the attendees of your event."
msgstr ""
#: ../../events/integrations/integration_sms.rst:32
msgid ""
"You can choose to confirm each registration with the *Registration* "
"template, and to send a reminder shortly before the event takes place with "
"the *Reminder* template."
msgstr ""
#: ../../events/integrations/integration_sms.rst:38
msgid "To make changes in an existing template, click on the external link."
msgstr ""
#: ../../events/integrations/integration_sms.rst:45
msgid "Send SMSs to speakers and further targets"
msgstr ""
#: ../../events/integrations/integration_sms.rst:47
msgid ""
"The benefit of the integration with the *SMS Marketing* application is that "
"you can choose the target you would like your message to be delivered to. To"
" get started, click on *Contact Track Speakers*."
msgstr ""
#: ../../events/integrations/integration_sms.rst:56
msgid ""
"If *Event Track* is not your target (*Recipient*), choose the right one. "
"*Filters* are eligible here."
msgstr ""
#: ../../events/integrations/integration_sms.rst:58
msgid ""
"In the example below, the SMS would be sent to the speakers who are in the "
"stage *Proposal* on *Event Track*."
msgstr ""
#: ../../events/integrations/integration_sms.rst:65
msgid ""
"Credits are required to be able to send SMSs. For more information about "
"Pricing :doc:`click here <../../sms_marketing/pricing/pricing_and_faq>`, "
"and, about IAP Services :doc:`here "
"<../../general/in_app_purchase/in_app_purchase>`."
msgstr ""
#: ../../events/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../events/overview/create_event.rst:3
msgid "Create your First Event"
msgstr ""
#: ../../events/overview/create_event.rst:5
msgid "Some of the reasons why hosting events is essential are:"
msgstr ""
#: ../../events/overview/create_event.rst:7
msgid "To create an engaging experience with your audience;"
msgstr ""
#: ../../events/overview/create_event.rst:8
msgid "To generate word of mouth about your company;"
msgstr ""
#: ../../events/overview/create_event.rst:9
msgid "To allow networking;"
msgstr ""
#: ../../events/overview/create_event.rst:10
msgid ""
"To provide an opportunity for sales representatives to walk their prospects "
"through the product and even their pipeline."
msgstr ""
#: ../../events/overview/create_event.rst:14
msgid "Get started"
msgstr ""
#: ../../events/overview/create_event.rst:16
msgid ""
"Under the menu *Events*, have a view of all existing events and some key "
"information, such as the number of expected and confirmed attendees."
msgstr ""
#: ../../events/overview/create_event.rst:23
msgid ""
"To start a new one, click on *Create* and fill in the form with all the "
"needed information. Enable *Website Menu* to have the menus *Introduction*, "
"*Location*, and *Register* being shown on your event’s website page."
msgstr ""
#: ../../events/overview/create_event.rst:31
msgid ""
"To personalize these pages, click on *Edit* to open the `website builder "
"<https://www.odoo.com/slides/slide/website-basics-643?fullscreen=1>`_, and "
"edit content by dragging and dropping blocks."
msgstr ""
#: ../../events/overview/create_event.rst:40
msgid "Tab: Tickets"
msgstr ""
#: ../../events/overview/create_event.rst:43
msgid ""
"Go to :menuselection:`Events --> Configuration --> Settings` and enable "
":doc:`Tickets and Online Ticketing <tickets>`."
msgstr ""
#: ../../events/overview/create_event.rst:46
msgid ""
"Now, under the *Tickets* Tab, add lines to include the different ticket "
"types you offer. Include the price, the start and end dates for "
"registrations, and even the maximum number of tickets that can be sold."
msgstr ""
#: ../../events/overview/create_event.rst:48
msgid ""
"The *Reserved Seats* and *Unconfirmed Seat Reservations* are counted as "
"attendees are marked as :doc:`confirmed <track_attendees>` or not."
msgstr ""
#: ../../events/overview/create_event.rst:55
msgid "Tab: Communication"
msgstr ""
#: ../../events/overview/create_event.rst:58
msgid ""
"Choose the email and/or SMS message template, as well as the frequency with "
"which you would like to communicate with your attendees under the tab "
"*Communication*."
msgstr ""
#: ../../events/overview/create_event.rst:61
msgid ""
"Create a template on the fly or choose an existing one. Define the "
"*Interval* (2, 7, 15..) for the *Unit* (days, hours, weeks, etc.), and the "
"*Trigger* action (after registration, after the event, etc.)."
msgstr ""
#: ../../events/overview/create_event.rst:68
msgid "Tab: Questions"
msgstr ""
#: ../../events/overview/create_event.rst:70
msgid ""
"Go to :menuselection:`Configuration --> Settings` and enable *Questions*."
msgstr ""
#: ../../events/overview/create_event.rst:72
msgid ""
"Now, under the tab *Questions*, edit your questions and answers, choosing if"
" you would like your questionnaire to be asked per order or per "
"registration."
msgstr ""
#: ../../events/overview/create_event.rst:75
msgid ""
"Example of a registration for 3 attendees: if enabling the option *Ask each "
"attendee*, the questionnaire is shown 3 times, meaning that answers can vary"
" for each attendee; if *Ask each attendee* is not enabled, the questionnaire"
" is shown once, resulting in a global answer."
msgstr ""
#: ../../events/overview/create_event.rst:81
msgid ""
"Once your event is *Confirmed*, you can manage attendees badges, and mark "
"the event as *Finished*. Events marked as *Finished* can be *Set to draft*, "
"putting the event back to an *Unconfirmed* stage from which it can be edited"
" and used again."
msgstr ""
#: ../../events/overview/create_event.rst:90
msgid "Publish your event"
msgstr ""
#: ../../events/overview/create_event.rst:92
msgid "*Go to Website* and turn *Published* on."
msgstr ""
#: ../../events/overview/create_event.rst:99
msgid ":doc:`track_attendees`"
msgstr ""
#: ../../events/overview/create_event.rst:100
#: ../../events/overview/track_attendees.rst:45
msgid ":doc:`tickets`"
msgstr ""
#: ../../events/overview/create_event.rst:101
#: ../../events/overview/track_attendees.rst:46
msgid ":doc:`track_talks`"
msgstr ""
#: ../../events/overview/tickets.rst:3
msgid "Selling Tickets"
msgstr ""
#: ../../events/overview/tickets.rst:5
msgid ""
"If you automate processes, you save time. If you give attendees multiple "
"payment options to choose from, you allow flexibility and open margins for "
"more registrations to happen."
msgstr ""
#: ../../events/overview/tickets.rst:11
msgid ""
"Go to :menuselection:`Configuration --> Settings` and activate *Tickets* and"
" *Online Ticketing*."
msgstr ""
#: ../../events/overview/tickets.rst:13
msgid ""
"*Tickets* allow tickets to be sold "
":ref:`events/create_event/through_sales_orders`. *Online Ticketing* allows "
"the sale of tickets to happen "
":ref:`events/create_event/through_the_website`."
msgstr ""
#: ../../events/overview/tickets.rst:22
msgid "Through Sales Orders"
msgstr ""
#: ../../events/overview/tickets.rst:24
msgid ""
"On the *Sales* application, choose the event product you created and add it "
"as a product line. A window pops-up, allowing you to choose the event for "
"which you want to create the sales order."
msgstr ""
#: ../../events/overview/tickets.rst:32
msgid ""
"Remember to create a product form for the event registration, under "
"*Product*, in the *Sales* application, and to add that same product under "
"your event’s form."
msgstr ""
#: ../../events/overview/tickets.rst:43
msgid "Through the Website"
msgstr ""
#: ../../events/overview/tickets.rst:45
msgid ""
"On the website, once tickets are added to the cart, the user can continue "
"the transaction choosing among the payment methods you chose to have "
"available."
msgstr ""
#: ../../events/overview/tickets.rst:53
msgid ":doc:`../../general/payment_acquirers/payment_acquirers`"
msgstr ""
#: ../../events/overview/track_attendees.rst:3
msgid "Track your Attendees"
msgstr ""
#: ../../events/overview/track_attendees.rst:5
msgid ""
"Attendees are at the heart of your event. Keeping track of their number and "
"managing their registration and attendance is necessary for planning and "
"analyzing reasons."
msgstr ""
#: ../../events/overview/track_attendees.rst:9
msgid "Attendees list and attendance"
msgstr ""
#: ../../events/overview/track_attendees.rst:11
msgid ""
"Once attendees have registered or bought their tickets, they are added to "
"the *Attendees* list."
msgstr ""
#: ../../events/overview/track_attendees.rst:12
msgid ""
"Tickets sold through sales orders validate attendees as soon as the "
"quotation is confirmed."
msgstr ""
#: ../../events/overview/track_attendees.rst:18
msgid ""
"The check mark button is used to confirm the registration. Once a "
"registration is confirmed, attendance can be marked."
msgstr ""
#: ../../events/overview/track_attendees.rst:26
msgid "Bagdes and cancellations"
msgstr ""
#: ../../events/overview/track_attendees.rst:28
msgid ""
"On the attendees form, choose to send badges manually by clicking on *Send "
"By Email*. *Cancel Registration* to have that attendee being moved to the "
"*Cancelled* stage."
msgstr ""
#: ../../events/overview/track_attendees.rst:36
msgid ""
"To see a list of your canceled attendees, under *Filters*, add a *Custom "
"Filter* choosing *Status > is > Cancelled*."
msgstr ""
#: ../../events/overview/track_attendees.rst:44
#: ../../events/overview/track_talks.rst:49
msgid ":doc:`../integrations/integration_sms`"
msgstr ""
#: ../../events/overview/track_talks.rst:3
msgid "Track and Manage Talks"
msgstr ""
#: ../../events/overview/track_talks.rst:5
msgid ""
"Allow partners to submit talk proposals so they can share their knowledge "
"and expertise. Good speakers and talks are what make your event great."
msgstr ""
#: ../../events/overview/track_talks.rst:11
msgid ""
"Go to :menuselection:`Events --> Configuration --> Settings` and enable "
"*Schedule & Tracks*."
msgstr ""
#: ../../events/overview/track_talks.rst:14
msgid ""
"Now, in your event's form, once *Website menu* is enabled, the options "
"*Tracks on Website* and *Track Proposals on Website* become available. "
"Enabling them adds the menus *Talks*, *Talk Proposals*, and *Agenda* to your"
" website."
msgstr ""
#: ../../events/overview/track_talks.rst:20
msgid ""
"Besides having the ability to suggest their own talks, the website now "
"allows users to see a list of the whole agenda and scheduled talks."
msgstr ""
#: ../../events/overview/track_talks.rst:28
msgid ""
"To handle tracks internally and not have the menus *Talks*, *Talk "
"Proposals*, and *Agenda* online, use the menu *Tracks* individually."
msgstr ""
#: ../../events/overview/track_talks.rst:32
msgid "Publishing speaker proposals"
msgstr ""
#: ../../events/overview/track_talks.rst:34
msgid ""
"Once partners have filled in the appropriate form and submitted their "
"proposals, a new *Proposal* is instantly created under the menu *Track*."
msgstr ""
#: ../../events/overview/track_talks.rst:41
msgid ""
"If the proposal is accepted and can go online, simply open its form and "
"click on *Go to Website*. From the website page, turn *Published* on."
msgstr ""

340
locale/da/LC_MESSAGES/expense.po Normal file
View File

@ -0,0 +1,340 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: da\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../expense/expense.rst:5
msgid "Expenses"
msgstr ""
#: ../../expense/expense.rst:8
msgid "How to set expense types"
msgstr ""
#: ../../expense/expense.rst:9
msgid ""
"The first step to track expenses is to configure the expense types (managed "
"as products in Odoo) that your company allows, from the *Configuration* "
"menu. When a specific expense is reimbursed at a fixed price, set a cost on "
"the product. Otherwise keep the cost at 0.0 and employees will report the "
"real cost per expense."
msgstr ""
#: ../../expense/expense.rst:17
msgid "Here are some examples to configure:"
msgstr ""
#: ../../expense/expense.rst:19
msgid "Restaurant:"
msgstr ""
#: ../../expense/expense.rst:21 ../../expense/expense.rst:27
msgid "Cost: 0.00 (the cost of the ticket will be recorded on every expense)"
msgstr ""
#: ../../expense/expense.rst:22
msgid "Travel with Personal Car:"
msgstr ""
#: ../../expense/expense.rst:24
msgid "Cost: 0.30 (the price per mile reimbursed by the company is fixed)"
msgstr ""
#: ../../expense/expense.rst:25
msgid "Hotel:"
msgstr ""
#: ../../expense/expense.rst:29
msgid "Others:"
msgstr ""
#: ../../expense/expense.rst:31
msgid "Cost: 0.0"
msgstr ""
#: ../../expense/expense.rst:33
msgid ""
"Don't forget to set an expense tax on each expense type (and an account if "
"you use Odoo Accounting). It's usually a good practice to use a tax that is "
"configured with :ref:`Tax Included in Price <taxes/included-in-price>`. That"
" way, employees report expenses with prices including taxes, which is "
"usually the expected behaviour."
msgstr ""
#: ../../expense/expense.rst:41
msgid ""
"The *Sales* app allows you to specify unit of measures for your expense "
"types (units, miles, nights, etc.). Go to :menuselection:`Sales --> "
"Configuration --> Settings` and check *Some products may be sold/purchased "
"in different units of measure (advanced)*."
msgstr ""
#: ../../expense/expense.rst:48
msgid "How to record expenses"
msgstr ""
#: ../../expense/expense.rst:51
msgid "Manually"
msgstr ""
#: ../../expense/expense.rst:53
msgid ""
"As an employee (Employee in user access rights), you can record expenses "
"from :menuselection:`My Expenses --> Expenses to Submit`."
msgstr ""
#: ../../expense/expense.rst:59
msgid ""
"Select the related product and enter either the total amount you paid (with "
"Quantity = 1) or the unit price if Quantity is countable (e.g. number of "
"hotel nights)."
msgstr ""
#: ../../expense/expense.rst:62
msgid "Enter the expense date."
msgstr ""
#: ../../expense/expense.rst:63
msgid ""
"Choose if you paid the bill on your own (and expect to be reimbursed) or if "
"the company paid directly (e.g. if you used a company's credit card)."
msgstr ""
#: ../../expense/expense.rst:65
msgid ""
"Set the bill reference, add some notes if requested and attach a photo/scan "
"of the receipt from the discussion thread. That will help the manager and "
"the accountant validate it."
msgstr ""
#: ../../expense/expense.rst:73
msgid "In one click from emails"
msgstr ""
#: ../../expense/expense.rst:74
msgid ""
"Let your employees record their expenses from a simple email. Make a "
"snapshot of the receipt and send it by email, or simply forward a bill!"
msgstr ""
#: ../../expense/expense.rst:77
msgid ""
"The only thing to do is setting up an email alias in "
":menuselection:`Expenses --> Configuration --> Settings` (e.g. *expenses* "
"@mycompany.odoo.com). For security purposes, only authenticated employee "
"emails (cfr. *Work Email* in employee detail form) are accepted."
msgstr ""
#: ../../expense/expense.rst:83
msgid ""
"The expense product is set automatically if the mail subject contains the "
"product's internal reference in first position. Type the expense amount in "
"the mail subject to set it on the expense too (e.g. Ref001 Food 100€)."
msgstr ""
#: ../../expense/expense.rst:88
msgid "How to submit expenses to managers"
msgstr ""
#: ../../expense/expense.rst:90
msgid ""
"When you are ready to submit your expenses to your manager (e.g. at the end "
"of a business trip, or once a month), go to the menu :menuselection:`My "
"Expenses --> Expenses to Submit`. Select all expenses from the list view and"
" click on :menuselection:`Action --> Submit to Manager`. Save the newly "
"created expense report (i.e. set of expenses), and wait for your manager to "
"approve it."
msgstr ""
#: ../../expense/expense.rst:100
msgid ""
"You can also submit expenses one by one from the *Submit to Manager* button "
"on the form view of an expense."
msgstr ""
#: ../../expense/expense.rst:103
msgid ""
"All your submitted expense reports can be found in :menuselection:`Expenses "
"--> My Expenses --> Expense Reports`."
msgstr ""
#: ../../expense/expense.rst:108
msgid "How to approve expenses"
msgstr ""
#: ../../expense/expense.rst:110
msgid ""
"HR and team managers get an overview of all expense reports to validate from"
" the top menu :menuselection:`To Approve --> Expense Reports to Approve`. "
"Such users must have at least *Officers* access rights for *Expenses*."
msgstr ""
#: ../../expense/expense.rst:117
msgid ""
"They can review expense reports, approve or reject them, as well as "
"providing feedback thanks to the integrated communication tool."
msgstr ""
#: ../../expense/expense.rst:123
msgid ""
"As a team manager you can easily find the expense reports of your team "
"members. You need to be set as manager in the detail form of those "
"employees."
msgstr ""
#: ../../expense/expense.rst:131
msgid "How to post expenses in accounting"
msgstr ""
#: ../../expense/expense.rst:133
msgid ""
"Once expense reports approved by managers, the accounting department goes to"
" :menuselection:`Expenses --> Accountant --> Expense Reports To Post` to "
"check accounts, products and taxes. They can click *Post Journal Entries* to"
" post related journal entries into your books. To do so, the user must have "
"following access rights:"
msgstr ""
#: ../../expense/expense.rst:139
msgid "Accounting: Accountant or Adviser"
msgstr ""
#: ../../expense/expense.rst:140
msgid "Expenses: Manager"
msgstr ""
#: ../../expense/expense.rst:143
msgid ""
"To post an expense, a *Home Address* must be set on the employee. If you get"
" a related blocking message when posting, click the employee, go to "
"*Personal Information* tab and select/create the contact of your employee in"
" the address book. A contact has been automatically created if this person "
"is using Odoo."
msgstr ""
#: ../../expense/expense.rst:150
msgid "How to reimburse employees"
msgstr ""
#: ../../expense/expense.rst:152
msgid ""
"You can now see all the expense reports to reimburse in "
":menuselection:`Expenses --> Accountant --> Expense Reports To Pay`. To "
"record the payment or pay by check, click *Register a Payment*."
msgstr ""
#: ../../expense/expense.rst:156
msgid "See how you can easily manage the payment process in Odoo:"
msgstr ""
#: ../../expense/expense.rst:158
msgid ":doc:`../accounting/payables/pay/check`"
msgstr ""
#: ../../expense/expense.rst:159
msgid ":doc:`../accounting/payables/pay/sepa`"
msgstr ""
#: ../../expense/expense.rst:163
msgid "How to re-invoice expenses to your customers"
msgstr ""
#: ../../expense/expense.rst:165
msgid ""
"If you track expenses on customer projects, you can charge them back to your"
" customers automatically."
msgstr ""
#: ../../expense/expense.rst:169
msgid "Setup"
msgstr ""
#: ../../expense/expense.rst:171
msgid "Enable **Customer Billing** in the Expenses settings"
msgstr ""
#: ../../expense/expense.rst:173
msgid ""
"Go to the product configuration menu and set the invoicing method on all "
"your Expense types:"
msgstr ""
#: ../../expense/expense.rst:176
msgid ""
"Ordered quantities : it will invoice expenses based on the ordered quantity"
msgstr ""
#: ../../expense/expense.rst:179
msgid ""
"Delivered quantities :it will invoice expenses based on the expenses "
"quantity"
msgstr ""
#: ../../expense/expense.rst:182
msgid "At cost: will invoice expenses at their real cost."
msgstr ""
#: ../../expense/expense.rst:184
msgid ""
"At sales price: will invoice based on a fixed sales price set on the sale "
"order."
msgstr ""
#: ../../expense/expense.rst:191
msgid "Create an order"
msgstr ""
#: ../../expense/expense.rst:193
msgid ""
"As a salesman, create and confirm a Sales Order for the services delivered "
"to your customer. If you don't put any expense in the order, it will be "
"added automatically once posted by the accountant."
msgstr ""
#: ../../expense/expense.rst:198
msgid "Link the expense to the Sale Order."
msgstr ""
#: ../../expense/expense.rst:204
msgid "Submit, validate and post expenses"
msgstr ""
#: ../../expense/expense.rst:206
msgid ""
"As a manager, make sure the analytic account is set on every expense line on"
" approving expenses reports. Click the line to add one if missing. Employees"
" are already able to set one when submitting."
msgstr ""
#: ../../expense/expense.rst:213
msgid "As an accountant, post journal entries."
msgstr ""
#: ../../expense/expense.rst:216
msgid "Invoice expenses"
msgstr ""
#: ../../expense/expense.rst:218
msgid ""
"Now you can invoice the order. It shows up in :menuselection:`Sales --> "
"Invoicing --> Sales` to Invoice. The expenses have been added automatically "
"in the order lines. Such items show up in blue (i.e. to invoice)."
msgstr ""
#: ../../expense/expense.rst:226
msgid "e (i.e. to invoice)."
msgstr ""

386
locale/da/LC_MESSAGES/fsm.po Normal file
View File

@ -0,0 +1,386 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: da\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../fsm.rst:5
msgid "Field Service"
msgstr ""
#: ../../fsm/helpdesk.rst:3
msgid "Helpdesk"
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:3
msgid "Plan Onsite Interventions from Helpdesk Tickets"
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:4
msgid ""
"The integration with the Helpdesk application lets your helpdesk team manage"
" interventions requests directly. It speeds up processes as you can plan "
"field services tasks from tickets."
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:8
#: ../../fsm/sales/create_quotations.rst:8
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:9
#: ../../fsm/worksheets/customize_worksheets.rst:9
msgid "Enable the feature"
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:9
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams --> "
"Edit` and enable :menuselection:`Onsite Interventions --> Save`."
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:17
msgid ""
"Now once your helpdesk team needs, they have the option to *Plan "
"Intervention* from tickets."
msgstr ""
#: ../../fsm/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:3
msgid "Invoicing Time and Material to Customers"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:4
msgid ""
"Track the exact time spent on a task and give customers the ability to sign "
"their worksheet report onsite. Invoice customers as soon as the work is "
"complete, leaving you, and the customer, with the confidence that they will "
"be charged for the exact right hours and material used."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:9
msgid "Get the exact time spent on a task"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:10
msgid ""
"Click on *Start* to launch the timer. You can *Pause* at any moment and "
"*Resume* when you would like to continue."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:17
msgid ""
"Click on *Stop* once the work is done to confirm the total time spent and "
"add a description."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:24
msgid "Sign and send reports & validate stock-picking"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:25
msgid ""
"Now, fill your *Worksheet* and add the used products clicking on *Products*."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:31
msgid ""
"Click on *Start* if you need to record additional time for the same "
"activity. The time recorded will be added to the already created and signed "
"worksheet. Then, create a new invoice for the time added."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:34
msgid ""
"*Mark as done* to close the task and to invoice your intervention. It also "
"validates the stock-picking keeping your inventory up-to-date."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:37
msgid ""
"*Sign Report* generates a detailed worksheet report for the customer to "
"sign. Send it through email clicking on *Send Report*."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:41
msgid "Invoice your time and material"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:42
msgid ""
"Under :menuselection:`All Tasks --> To Invoice`, find a list of all tasks "
"marked as done but that have not been invoiced. Convenient feature as it "
"allows accountants to easily access all finished tasks at once."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:52
msgid ""
"Invoice all tasks at once selecting them all and going to "
":menuselection:`Action --> Create Invoice`."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:60
msgid ":doc:`../../project/advanced/feedback`"
msgstr ""
#: ../../fsm/overview/keep_track.rst:3
msgid "Keeping Track of Stock"
msgstr ""
#: ../../fsm/overview/keep_track.rst:4
msgid ""
"The integration with the Inventory application makes possible to track the "
"material used and automatically keep your stock up to date."
msgstr ""
#: ../../fsm/overview/keep_track.rst:8
msgid "Set up your Field Service project"
msgstr ""
#: ../../fsm/overview/keep_track.rst:9
msgid ""
"Go to :menuselection:`Field Service --> Configuration --> Projects` and make"
" sure the option *Products on Tasks* is enabled."
msgstr ""
#: ../../fsm/overview/keep_track.rst:15
msgid ""
"Now, add the materials used in the intervention to the worksheet, and once "
"the task is *Marked as done*, the stock-picking is automatically validated "
"and the inventory evaluation is automatically updated."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:3
msgid "Manage your Employees’ Schedules and Time Off"
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:4
msgid ""
"The integration with the *Time off* application allows you to quickly see "
"your employees’ availabilities. It will avoid conflicts and errors between "
"employees schedules and interventions."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:8
msgid "Effortlessly see employees’ time off"
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:9
msgid ""
"No configuration needs to be done. Once the employees’ time has been "
"validated in the *Time off* application, cells will be grayed for those days"
" in your Gantt view."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:13
msgid ""
"It also adapts to the working calendar of the employee. Example: the "
"employee works part-time (from Monday to Wednesday). So, Thursday and Friday"
" will also be greyed, in addition to the weekends."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:20
msgid "Easily manage employees’ schedules"
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:21
msgid ""
"From the Gantt view (under *Planning by User, Project or Worksheet*), click "
"on the plus sign to add a new task or on the magnifying glass to plan an "
"existing one."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:29
msgid "Unassigned tasks"
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:30
msgid ""
"If you need to plan an intervention but you do not know yet who will take "
"care of it, you can leave the task unassigned. It will still be shown in the"
" Gantt view. Simply drag and drop the responsible person he can be assigned."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:39
msgid ""
"Create projects per team, or per working site, and have a more accurate and "
"dynamic database."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:42
msgid ":doc:`../../project/overview/setup`"
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:3
msgid "Planning an Itinerary"
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:5
msgid ""
"Having an itinerary being shown based on the chronological order of the "
"activities and on the best route to take, makes employees’ life easier and "
"the workload more efficient."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:9
msgid "Have an itinerary displayed directly in Odoo"
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:10
msgid "Go to *Settings* and under *Map view* click on *Get token*."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:15
msgid ""
"Click on :menuselection:`Start mapping for free --> fill the Username, email"
" and password fields --> agree with their Terms of Service and Privacy "
"Policy --> Get started`. You will be redirected to your account. Scrolling "
"the page down you will find *Access tokens*. Copy the *Default public "
"token*."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:24
msgid "Back in Odoo, paste it on :menuselection:`Token --> Save`."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:29
msgid ""
"Now, your maps will show the itinerary based on the scheduled time and best "
"route."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:36
msgid ""
"This is an optional feature, as you can still have access to a map view "
"without a Mapbox account."
msgstr ""
#: ../../fsm/sales.rst:3
msgid "Sales"
msgstr ""
#: ../../fsm/sales/create_quotations.rst:3
msgid "Create Quotations from Tasks"
msgstr ""
#: ../../fsm/sales/create_quotations.rst:4
msgid ""
"Allowing quotations to be created from tasks delivers a more efficient "
"service as it allows space for preventive actions, while making the flow "
"easy for employees."
msgstr ""
#: ../../fsm/sales/create_quotations.rst:9
msgid ""
"First, go to :menuselection:`Field Service --> Configuration --> Settings` "
"and enable the option *Extra Quotations*."
msgstr ""
#: ../../fsm/sales/create_quotations.rst:16
msgid ""
"Second, go to :menuselection:`Configuration --> Projects` and enable *Extra "
"Quotations*."
msgstr ""
#: ../../fsm/sales/create_quotations.rst:23
msgid "You can now create *New Quotations* directly from your tasks."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:3
msgid "Create Onsite Interventions Tasks from Sales Orders"
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:4
msgid ""
"By allowing your sales team to open onsite interventions tasks will create a"
" seamless experience for your customers. It also allows them to first "
"receive a quotation with the materials that will be used plus the service "
"price to be approved before the work even starts."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:10
msgid ""
"Go to :menuselection:`Sales --> Products --> Create` or edit an existing "
"one. Select: under :menuselection:`General Information --> Product Type: "
"Service`; under :menuselection:`Sales --> Service Invoicing Policy: "
"Timesheet on task --> Service Tracking: Create a task in an existing project"
" --> Project --> Worksheet Template --> Save`."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:19
msgid ""
"Now, once you have *Confirmed* a *quotation*, a task will be created in the "
"respective project you have chosen."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:28
msgid ""
"One of the greatest benefits here is that you can have different *Worksheets"
" Templates* under the same project and product, for example."
msgstr ""
#: ../../fsm/worksheets.rst:3
msgid "Worksheets"
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:3
msgid "Customize Worksheet Reports"
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:4
msgid ""
"Personalizing your customer reports, also called *worksheets*, allows you to"
" have different descriptions of the work for each type of intervention. It "
"speeds up the flow for your employees while giving customers a detailed "
"summary, which can be reviewed and signed onsite."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:10
msgid ""
"Go to :menuselection:`Field Service --> Configuration` and enable "
":menuselection:`Worksheet Templates --> Save`."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:18
msgid "Designing worksheets"
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:19
msgid ""
"Under :menuselection:`Configuration --> Worksheet Templates`, click on "
"*Create* and start to *Design Worksheet Template*. You will be redirected to"
" the *Studio* application."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:27
msgid ""
"With the freedom of *Studio*, drag and drop fields to create a report "
"tailored to your needs. Once you are done, click on *Close* and get an "
"overview of the work done."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:30
msgid ""
"*Worksheets* is where you can see how many times the worksheet has been "
"used/completed under a task. *Analysis* examines all the worksheets under "
"that given template and generates a graph."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:38
msgid ""
"`Studio Basics <https://www.odoo.com/slides/slide/studio-"
"basics-710?fullscreen=1>`_"
msgstr ""

2145
locale/da/LC_MESSAGES/general.po
View File

File diff suppressed because it is too large Load Diff

219
locale/da/LC_MESSAGES/getting_started.po
View File

@ -6,10 +6,10 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 12.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-11-07 15:38+0100\n"
"PO-Revision-Date: 2018-10-19 08:15+0000\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -29,7 +29,7 @@ msgid ""
msgstr ""
#: ../../getting_started/documentation.rst:12
msgid "1. The SPoC (*Single Point of Contact*) and the Consultant"
msgid "The SPoC (*Single Point of Contact*) and the Consultant"
msgstr ""
#: ../../getting_started/documentation.rst:14
@ -72,24 +72,22 @@ msgid ""
"training to the SPoC so that he can pass on this knowledge to his "
"collaborators. In order for this approach to be successful, it is necessary "
"that the SPoC is also involved in its own rise in skills through self-"
"learning via the `Odoo documentation "
"<http://www.odoo.com/documentation/user/10.0/index.html>`__, `The elearning "
"platform <https://odoo.thinkific.com/courses/odoo-functional>`__ and the "
"testing of functionalities."
msgstr ""
#: ../../getting_started/documentation.rst:47
msgid "2. Project Scope"
"learning via the :doc:`Odoo documentation <../index>`, `The elearning "
"platform <https://odoo.com/learn>`_ and the testing of functionalities."
msgstr ""
#: ../../getting_started/documentation.rst:49
msgid "Project Scope"
msgstr ""
#: ../../getting_started/documentation.rst:51
msgid ""
"To make sure all the stakeholders involved are always aligned, it is "
"necessary to define and to make the project scope evolve as long as the "
"project implementation is pursuing."
msgstr ""
#: ../../getting_started/documentation.rst:53
#: ../../getting_started/documentation.rst:55
msgid ""
"**A clear definition of the initial project scope**: A clear definition of "
"the initial needs is crucial to ensure the project is running smoothly. "
@ -98,7 +96,7 @@ msgid ""
" clear."
msgstr ""
#: ../../getting_started/documentation.rst:59
#: ../../getting_started/documentation.rst:61
msgid ""
"**Phasing the project**: Favoring an implementation in several coherent "
"phases allowing regular production releases and an evolving takeover of Odoo"
@ -107,7 +105,7 @@ msgid ""
"the implementation."
msgstr ""
#: ../../getting_started/documentation.rst:66
#: ../../getting_started/documentation.rst:68
msgid ""
"**Adopting standard features as a priority**: Odoo offers a great "
"environment to implement slight improvements (customizations) or more "
@ -119,18 +117,18 @@ msgid ""
"experiment of the standard in production."
msgstr ""
#: ../../getting_started/documentation.rst:80
msgid "3. Managing expectations"
#: ../../getting_started/documentation.rst:82
msgid "Managing expectations"
msgstr ""
#: ../../getting_started/documentation.rst:82
#: ../../getting_started/documentation.rst:84
msgid ""
"The gap between the reality of an implementation and the expectations of "
"future users is a crucial factor. Three important aspects must be taken into"
" account from the beginning of the project:"
msgstr ""
#: ../../getting_started/documentation.rst:86
#: ../../getting_started/documentation.rst:88
msgid ""
"**Align with the project approach**: Both a clear division of roles and "
"responsibilities and a clear description of the operating modes (validation,"
@ -140,7 +138,7 @@ msgid ""
"check that this is still the case."
msgstr ""
#: ../../getting_started/documentation.rst:94
#: ../../getting_started/documentation.rst:96
msgid ""
"**Focus on the project success, not on the ideal solution**: The main goal "
"of the SPoC and the Consultant is to carry out the project entrusted to them"
@ -155,7 +153,7 @@ msgid ""
"to pursue this same objective."
msgstr ""
#: ../../getting_started/documentation.rst:108
#: ../../getting_started/documentation.rst:110
msgid ""
"**Specifications are always EXPLICIT**: Gaps between what is expected and "
"what is delivered are often a source of conflict in a project. In order to "
@ -163,35 +161,34 @@ msgid ""
"tools\\* :"
msgstr ""
#: ../../getting_started/documentation.rst:113
#: ../../getting_started/documentation.rst:115
msgid ""
"**The GAP Analysis**: The comparison of the request with the standard "
"features proposed by Odoo will make it possible to identify the gap to be "
"filled by developments/customizations or changes in business processes."
msgstr ""
#: ../../getting_started/documentation.rst:118
#: ../../getting_started/documentation.rst:120
msgid ""
"`The User Story <https://help.rallydev.com/writing-great-user-story>`__: "
"This technique clearly separates the responsibilities between the SPoC, "
"responsible for explaining the WHAT, the WHY and the WHO, and the Consultant"
" who will provide a response to the HOW."
"**The User Story**: This technique clearly separates the responsibilities "
"between the SPoC, responsible for explaining the WHAT, the WHY and the WHO, "
"and the Consultant who will provide a response to the HOW."
msgstr ""
#: ../../getting_started/documentation.rst:126
#: ../../getting_started/documentation.rst:128
msgid ""
"`The Proof of Concept <https://en.wikipedia.org/wiki/Proof_of_concept>`__ A "
"simplified version, a prototype of what is expected to agree on the main "
"lines of expected changes."
msgstr ""
#: ../../getting_started/documentation.rst:130
#: ../../getting_started/documentation.rst:132
msgid ""
"**The Mockup**: In the same idea as the Proof of Concept, it will align with"
" the changes related to the interface."
msgstr ""
#: ../../getting_started/documentation.rst:133
#: ../../getting_started/documentation.rst:135
msgid ""
"To these tools will be added complete transparency on the possibilities and "
"limitations of the software and/or its environment so that all project "
@ -200,17 +197,17 @@ msgid ""
"verifying its veracity beforehand."
msgstr ""
#: ../../getting_started/documentation.rst:139
#: ../../getting_started/documentation.rst:141
msgid ""
"*This list can, of course, be completed by other tools that would more "
"adequately meet the realities and needs of your project*"
msgstr ""
#: ../../getting_started/documentation.rst:143
msgid "4. Communication Strategy"
#: ../../getting_started/documentation.rst:145
msgid "Communication Strategy"
msgstr ""
#: ../../getting_started/documentation.rst:145
#: ../../getting_started/documentation.rst:147
msgid ""
"The purpose of the QuickStart methodology is to ensure quick ownership of "
"the tool for end users. Effective communication is therefore crucial to the "
@ -218,7 +215,7 @@ msgid ""
"follow those principles:"
msgstr ""
#: ../../getting_started/documentation.rst:150
#: ../../getting_started/documentation.rst:152
msgid ""
"**Sharing the project management documentation**: The best way to ensure "
"that all stakeholders in a project have the same level of knowledge is to "
@ -228,45 +225,45 @@ msgid ""
" manager are clearly defined."
msgstr ""
#: ../../getting_started/documentation.rst:158
#: ../../getting_started/documentation.rst:160
msgid ""
"The Project Organizer is a shared project tracking tool that allows both "
"detailed tracking of ongoing tasks and the overall progress of the project."
msgstr ""
#: ../../getting_started/documentation.rst:162
#: ../../getting_started/documentation.rst:164
msgid ""
"**Report essential information**: In order to minimize the documentation "
"time to the essentials, we will follow the following good practices:"
msgstr ""
#: ../../getting_started/documentation.rst:166
#: ../../getting_started/documentation.rst:168
msgid "Meeting minutes will be limited to decisions and validations;"
msgstr ""
#: ../../getting_started/documentation.rst:168
#: ../../getting_started/documentation.rst:170
msgid ""
"Project statuses will only be established when an important milestone is "
"reached;"
msgstr ""
#: ../../getting_started/documentation.rst:171
#: ../../getting_started/documentation.rst:173
msgid ""
"Training sessions on the standard or customized solution will be organized."
msgstr ""
#: ../../getting_started/documentation.rst:175
msgid "5. Customizations and Development"
#: ../../getting_started/documentation.rst:177
msgid "Customizations and Development"
msgstr ""
#: ../../getting_started/documentation.rst:177
#: ../../getting_started/documentation.rst:179
msgid ""
"Odoo is a software known for its flexibility and its important evolution "
"capacity. However, a significant amount of development contradicts a fast "
"and sustainable implementation. This is the reason why it is recommended to:"
msgstr ""
#: ../../getting_started/documentation.rst:182
#: ../../getting_started/documentation.rst:184
msgid ""
"**Develop only for a good reason**: The decision to develop must always be "
"taken when the cost-benefit ratio is positive (saving time on a daily basis,"
@ -280,7 +277,7 @@ msgid ""
"\"Adopting the standard as a priority\")."
msgstr ""
#: ../../getting_started/documentation.rst:194
#: ../../getting_started/documentation.rst:196
msgid ""
"**Replace, without replicate**: There is a good reason for the decision to "
"change the management software has been made. In this context, the moment of"
@ -289,18 +286,18 @@ msgid ""
"business processes of the company."
msgstr ""
#: ../../getting_started/documentation.rst:202
msgid "6. Testing and Validation principles"
#: ../../getting_started/documentation.rst:204
msgid "Testing and Validation principles"
msgstr ""
#: ../../getting_started/documentation.rst:204
#: ../../getting_started/documentation.rst:206
msgid ""
"Whether developments are made or not in the implementation, it is crucial to"
" test and validate the correspondence of the solution with the operational "
"needs of the company."
msgstr ""
#: ../../getting_started/documentation.rst:208
#: ../../getting_started/documentation.rst:210
msgid ""
"**Role distribution**: In this context, the Consultant will be responsible "
"for delivering a solution corresponding to the defined specifications; the "
@ -308,33 +305,33 @@ msgid ""
"requirements of the operational reality."
msgstr ""
#: ../../getting_started/documentation.rst:214
#: ../../getting_started/documentation.rst:216
msgid ""
"**Change management**: When a change needs to be made to the solution, the "
"noted gap is caused by:"
msgstr ""
#: ../../getting_started/documentation.rst:218
#: ../../getting_started/documentation.rst:220
msgid ""
"A difference between the specification and the delivered solution - This is "
"a correction for which the Consultant is responsible"
msgstr ""
#: ../../getting_started/documentation.rst:220
#: ../../getting_started/documentation.rst:223
msgid "**or**"
msgstr ""
#: ../../getting_started/documentation.rst:222
#: ../../getting_started/documentation.rst:225
msgid ""
"A difference between the specification and the imperatives of operational "
"reality - This is a change that is the responsibility of SPoC."
msgstr ""
#: ../../getting_started/documentation.rst:226
msgid "7. Data Imports"
#: ../../getting_started/documentation.rst:229
msgid "Data Imports"
msgstr ""
#: ../../getting_started/documentation.rst:228
#: ../../getting_started/documentation.rst:231
msgid ""
"Importing the history of transactional data is an important issue and must "
"be answered appropriately to allow the project running smoothly. Indeed, "
@ -343,14 +340,14 @@ msgid ""
"it will be decided :"
msgstr ""
#: ../../getting_started/documentation.rst:234
#: ../../getting_started/documentation.rst:237
msgid ""
"**Not to import anything**: It often happens that after reflection, "
"importing data history is not considered necessary, these data being, "
"moreover, kept outside Odoo and consolidated for later reporting."
msgstr ""
#: ../../getting_started/documentation.rst:239
#: ../../getting_started/documentation.rst:242
msgid ""
"**To import a limited amount of data before going into production**: When "
"the data history relates to information being processed (purchase orders, "
@ -359,7 +356,7 @@ msgid ""
" import will be made before the production launch."
msgstr ""
#: ../../getting_started/documentation.rst:246
#: ../../getting_started/documentation.rst:249
msgid ""
"**To import after production launch**: When the data history needs to be "
"integrated with Odoo mainly for reporting purposes, it is clear that these "
@ -367,106 +364,16 @@ msgid ""
"production launch of the solution will precede the required imports."
msgstr ""
#: ../../getting_started/documentation.rst:253
msgid "8. Support"
#: ../../getting_started/documentation.rst:256
msgid "Support"
msgstr ""
#: ../../getting_started/documentation.rst:255
#: ../../getting_started/documentation.rst:258
msgid ""
"Your Odoo Online subscription includes **unlimited 24hr support at no extra "
"cost, Monday to Friday**. Our teams are located around the world to ensure "
"you have support, no matter your location. Your support representative could"
" be communicating to you from San Francisco, Belgium, or India!"
"When your project is put in production, our support teams take care of your "
"questions or technical issues."
msgstr ""
#: ../../getting_started/documentation.rst:260
msgid "What kind of support is included?"
msgstr ""
#: ../../getting_started/documentation.rst:262
msgid ""
"Providing you with relevant material (guidelines, product documentation, "
"etc...)"
msgstr ""
#: ../../getting_started/documentation.rst:264
msgid ""
"Answers to issues that you may encounter in your standard Odoo database (eg."
" “I cannot close my Point of Sale” or “I cannot find my sales KPIs?”)"
msgstr ""
#: ../../getting_started/documentation.rst:266
msgid "Questions related to your account, subscription, or billing"
msgstr ""
#: ../../getting_started/documentation.rst:267
msgid ""
"Bug resolution (blocking issues or unexpected behaviour not due to "
"misconfiguration or customization)"
msgstr ""
#: ../../getting_started/documentation.rst:269
msgid ""
"Issues that might occur in a test database after upgrading to a newer "
"version"
msgstr ""
#: ../../getting_started/documentation.rst:271
msgid ""
"*Odoo Support does not make changes to your production database, but gives "
"you the material and knowledge to do it yourself!*"
msgstr ""
#: ../../getting_started/documentation.rst:274
msgid "What kind of support is not included?"
msgstr ""
#: ../../getting_started/documentation.rst:276
msgid ""
"Questions that require us to understand your business processes in order to "
"help you implement your database"
msgstr ""
#: ../../getting_started/documentation.rst:278
msgid ""
"Training on how to use our software (we will direct you to our many "
"resources)"
msgstr ""
#: ../../getting_started/documentation.rst:279
msgid "Importation of documents into your database"
msgstr ""
#: ../../getting_started/documentation.rst:280
msgid ""
"Guidance on which configurations to apply inside of an application or the "
"database"
msgstr ""
#: ../../getting_started/documentation.rst:281
msgid ""
"How to set up configuration models (Examples include: Inventory Routes, "
"Payment Terms, Warehouses, etc)"
msgstr ""
#: ../../getting_started/documentation.rst:283
msgid ""
"Questions or issues related to specific developments or customizations done "
"either by Odoo or a third party (this is specific only to your database or "
"involving code)"
msgstr ""
#: ../../getting_started/documentation.rst:287
msgid ""
"You can get this type of support with a `Success Pack <https://www.odoo.com"
"/pricing-packs>`__. With a pack, one of our consultants will analyze the way"
" your business runs and tell you how you can get the most out of your Odoo "
"Database. We will handle all configurations and coach you on how to use "
"Odoo."
msgstr ""
#: ../../getting_started/documentation.rst:292
msgid ""
"Our support team can be contacted through our `online support form "
"<https://www.odoo.com/help>`__."
#: ../../getting_started/documentation.rst:261
msgid "See :ref:`support-expectations`."
msgstr ""

962
locale/da/LC_MESSAGES/helpdesk.po
View File

File diff suppressed because it is too large Load Diff

6
locale/da/LC_MESSAGES/index.po
View File

@ -6,10 +6,10 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: 2018-10-19 08:15+0000\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"

8401
locale/da/LC_MESSAGES/inventory.po
View File

File diff suppressed because it is too large Load Diff

610
locale/da/LC_MESSAGES/iot.po
View File

@ -3,13 +3,18 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Mads Søndergaard, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: 2018-10-19 08:15+0000\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Mads Søndergaard, 2020\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -21,66 +26,83 @@ msgstr ""
msgid "Internet of Things (IoT)"
msgstr ""
#: ../../iot/connect.rst:3
#: ../../iot/config.rst:3
msgid "Configuration"
msgstr "Konfiguration"
#: ../../iot/config/connect.rst:3
msgid "Connect an IoT Box to your database"
msgstr ""
#: ../../iot/connect.rst:5
#: ../../iot/config/connect.rst:5
msgid "Install the Internet of Things (IoT) App on your Odoo Database."
msgstr ""
#: ../../iot/connect.rst:10
#: ../../iot/config/connect.rst:10
msgid "Go in the IoT App and click on Connect on the IoT Boxes page."
msgstr ""
#: ../../iot/connect.rst:15
#: ../../iot/config/connect.rst:15
msgid "Follow the steps to connect your IoT Box."
msgstr ""
#: ../../iot/connect.rst:21
#: ../../iot/config/connect.rst:21
msgid "Ethernet Connection"
msgstr ""
#: ../../iot/connect.rst:23
#: ../../iot/config/connect.rst:23
msgid ""
"Connect to the IoT Box all the devices that have to be connected with cables"
" (ethernet, usb devices, etc.)."
msgstr ""
#: ../../iot/connect.rst:26
#: ../../iot/config/connect.rst:26
msgid "Power on the IoT Box."
msgstr ""
#: ../../iot/connect.rst:28
msgid "Then click on the Scan button."
#: ../../iot/config/connect.rst:28
msgid ""
"Read the Pairing Code from a screen or a receipt printer connected to the "
"IoT Box."
msgstr ""
#: ../../iot/connect.rst:34
#: ../../iot/config/connect.rst:32
msgid "Input the Pairing Code and click on the Pair button."
msgstr ""
#: ../../iot/config/connect.rst:35
msgid ""
"Recent changes in modern web browsers forced us to modify the connection "
"wizard. If your screen is different from the screenshots, make sure that the"
" ``iot_pairing`` module is installed."
msgstr ""
#: ../../iot/config/connect.rst:40
msgid "WiFi Connection"
msgstr ""
#: ../../iot/connect.rst:36
#: ../../iot/config/connect.rst:42
msgid "Power on the IoT Box"
msgstr ""
#: ../../iot/connect.rst:38
#: ../../iot/config/connect.rst:44
msgid "Copy the token"
msgstr ""
#: ../../iot/connect.rst:43
#: ../../iot/config/connect.rst:48
msgid ""
"Connect to the IoT Box WiFi Network (make sure there is no ethernet cable "
"plugged in your computer)."
msgstr ""
#: ../../iot/connect.rst:49
#: ../../iot/config/connect.rst:53
msgid ""
"You will be redirected to the IoT Box Homepage (if it doesn't work, connect "
"to the IP address of the box). Give a name to your IoT Box (not required) "
"and paste the token, then click on next."
msgstr ""
#: ../../iot/connect.rst:57
#: ../../iot/config/connect.rst:60
msgid ""
"If you are on Runbot, do not forget to add the -all or -base in the token "
"(e.g. this token **http://375228-saas-11-5-iot-"
@ -88,107 +110,178 @@ msgid ""
"**http://375228-saas-11-5-iot-f3f920-all.runbot16.odoo.com\\|4957098401**)."
msgstr ""
#: ../../iot/connect.rst:63
#: ../../iot/config/connect.rst:66
msgid ""
"Choose the WiFi network you want to connect with (enter the password if "
"there is one) and click on Submit. Wait a few seconds before being "
"redirected to your database."
msgstr ""
#: ../../iot/connect.rst:70
#: ../../iot/config/connect.rst:72
msgid "You should now see the IoT Box."
msgstr ""
#: ../../iot/connect.rst:76
#: ../../iot/config/connect.rst:78
msgid "IoT Box Schema"
msgstr ""
#: ../../iot/pos.rst:3
#: ../../iot/config/flash_sdcard.rst:3
msgid "Flashing your SD Card"
msgstr ""
#: ../../iot/config/flash_sdcard.rst:5
msgid ""
"In some case, you may need to reflash your IoT Box’s SD Card to benefit from"
" our latest updates."
msgstr ""
#: ../../iot/config/flash_sdcard.rst:9
msgid "Updating your SD Card with Etcher"
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."
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*!."
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."
msgstr ""
#: ../../iot/config/iot_notfound.rst:3
msgid "IoT Box not found"
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`"
msgstr ""
#: ../../iot/config/pos.rst:3
msgid "Use the IoT Box for the PoS"
msgstr ""
#: ../../iot/pos.rst:9
#: ../../iot/config/pos.rst:9
msgid "Prerequisites"
msgstr ""
#: ../../iot/pos.rst:11
#: ../../iot/config/pos.rst:11
msgid "Before starting, make sure you have the following:"
msgstr ""
#: ../../iot/pos.rst:13
#: ../../iot/config/pos.rst:13
msgid "An IoT Box"
msgstr ""
#: ../../iot/pos.rst:15
#: ../../iot/config/pos.rst:15
msgid "A 2A Power adapter with pi 3 b+ 2.5 A"
msgstr ""
#: ../../iot/pos.rst:17
#: ../../iot/config/pos.rst:17
msgid "A computer or tablet with an up-to-date web browser"
msgstr ""
#: ../../iot/pos.rst:19
#: ../../iot/config/pos.rst:19
msgid ""
"A running SaaS or Odoo instance with the Point of Sale and IoT apps "
"installed"
msgstr ""
#: ../../iot/pos.rst:22
#: ../../iot/config/pos.rst:22
msgid "A local network setup with DHCP (this is the default setting)"
msgstr ""
#: ../../iot/pos.rst:24
#: ../../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/pos.rst:28
#: ../../iot/config/pos.rst:28
msgid "A Honeywell Eclipse USB Barcode Scanner or another compatible scanner"
msgstr ""
#: ../../iot/pos.rst:30
#: ../../iot/config/pos.rst:30
msgid "An Epson compatible cash drawer"
msgstr ""
#: ../../iot/pos.rst:32
#: ../../iot/config/pos.rst:32
msgid "An RJ45 Ethernet Cable (optional, WiFi is built in)"
msgstr ""
#: ../../iot/pos.rst:35
#: ../../iot/config/pos.rst:35
msgid "Set Up"
msgstr ""
#: ../../iot/pos.rst:37
#: ../../iot/config/pos.rst:37
msgid ""
"To connect hardware to the PoS, the first step is to connect an IoT Box to "
"your database. For this, follow this `documentation "
"<https://docs.google.com/document/d/1vhWrSSlSdJcRYe4tjPpXKYVMTD47lVK3ysyYc7tJDlA/edit#>`__."
"your database. For this, follow this :doc:`documentation <connect>`."
msgstr ""
#: ../../iot/pos.rst:44
#: ../../iot/config/pos.rst:44
msgid "Then, you have to connect the peripheral devices to your IoT Box."
msgstr ""
#: ../../iot/pos.rst:46
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:50
#: ../../iot/config/pos.rst:50
msgid "**Printer**: Connect an ESC/POS printer to a USB port and power it on."
msgstr ""
#: ../../iot/pos.rst:53
#: ../../iot/config/pos.rst:53
msgid ""
"**Cash drawer**: The cash drawer should be connected to the printer with an "
"RJ25 cable."
msgstr ""
#: ../../iot/pos.rst:56
#: ../../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 "
@ -197,18 +290,18 @@ msgid ""
"your barcode scanner."
msgstr ""
#: ../../iot/pos.rst:62
#: ../../iot/config/pos.rst:62
msgid "**Scale**: Connect your scale and power it on."
msgstr ""
#: ../../iot/pos.rst:64
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:68
#: ../../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 "
@ -216,26 +309,26 @@ msgid ""
"on boot."
msgstr ""
#: ../../iot/pos.rst:73
#: ../../iot/config/pos.rst:73
msgid ""
"Once it's done, you can connect the IoT Box to your PoS. For this, go in "
"Point of Sale > Configuration > PoS, tick the box \"IoT Box\" and select the"
" IoT Box you want to connect with. Save the changes."
":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/pos.rst:77
#: ../../iot/config/pos.rst:77
msgid "Set up is done, you can launch a new PoS Session."
msgstr ""
#: ../../iot/pos.rst:80
#: ../../iot/config/pos.rst:80
msgid "Troubleshoot"
msgstr ""
#: ../../iot/pos.rst:83
#: ../../iot/config/pos.rst:83
msgid "The PoS cannot connect to the IoT Box"
msgstr ""
#: ../../iot/pos.rst:85
#: ../../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"
@ -243,90 +336,90 @@ msgid ""
"receipt is printed, check the following steps:"
msgstr ""
#: ../../iot/pos.rst:91
#: ../../iot/config/pos.rst:91
msgid ""
"Make sure the IoT Box is powered on, indicated by a brightly lit red status "
"LED."
msgstr ""
#: ../../iot/pos.rst:94
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:98
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:102
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:106
#: ../../iot/config/pos.rst:106
msgid "Make sure that the POS is not loaded over HTTPS."
msgstr ""
#: ../../iot/pos.rst:108
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:113
#: ../../iot/config/pos.rst:113
msgid "The Barcode Scanner is not working"
msgstr ""
#: ../../iot/pos.rst:115
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:120
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:124
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:129
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:134
#: ../../iot/config/pos.rst:134
msgid "The Barcode Scanner is not working reliably"
msgstr ""
#: ../../iot/pos.rst:136
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:140
#: ../../iot/config/pos.rst:140
msgid "Printing the receipt takes too much time"
msgstr ""
#: ../../iot/pos.rst:142
#: ../../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 "
@ -334,33 +427,404 @@ msgid ""
"and the IoT Box."
msgstr ""
#: ../../iot/pos.rst:148
#: ../../iot/config/pos.rst:148
msgid "Some characters are not correctly printed on the receipt"
msgstr ""
#: ../../iot/pos.rst:150
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:155
#: ../../iot/config/pos.rst:155
msgid "The printer is offline"
msgstr ""
#: ../../iot/pos.rst:157
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:162
#: ../../iot/config/pos.rst:162
msgid "The cashdrawer does not open"
msgstr ""
#: ../../iot/pos.rst:164
#: ../../iot/config/pos.rst:164
msgid ""
"The cashdrawer should be connected to the printer and should be activated in"
" the POS configuration."
msgstr ""
#: ../../iot/devices.rst:3
msgid "Devices"
msgstr "Enheder"
#: ../../iot/devices/camera.rst:3
msgid "Connect a Camera"
msgstr ""
#: ../../iot/devices/camera.rst:5
msgid ""
"When using your *IoT Box* in Odoo, you could need to use a camera. As it can"
" be done in a few steps, this device is really easy to configure. Then, you "
"can use it in your manufacturing process and link it to a control point. "
"Doing so will allow you to take pictures when you reach the chosen quality "
"control point."
msgstr ""
#: ../../iot/devices/camera.rst:12 ../../iot/devices/footswitch.rst:13
#: ../../iot/devices/printer.rst:11
msgid "Connection"
msgstr "Forbindelse"
#: ../../iot/devices/camera.rst:14
msgid ""
"To connect the camera to the *IoT Box*, simply combine 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
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
msgid "Link a Camera to a Quality Control Point"
msgstr ""
#: ../../iot/devices/camera.rst:38 ../../iot/devices/measurement_tool.rst:42
msgid "With the Manufacturing app"
msgstr ""
#: ../../iot/devices/camera.rst:40
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
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
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 ""
#: ../../iot/devices/footswitch.rst:3
msgid "Connect a Footswitch"
msgstr ""
#: ../../iot/devices/footswitch.rst:5
msgid ""
"When working, it is always better to have your two hands available. Using "
"Odoo’s *IoT Box* and a footswitch will allow it."
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."
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."
msgstr ""
#: ../../iot/devices/footswitch.rst:19
msgid "In some cases, a serial to USB adapter may be needed."
msgstr ""
#: ../../iot/devices/footswitch.rst:21
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
msgid "Link a Footswitch to a Workcenter"
msgstr ""
#: ../../iot/devices/footswitch.rst:39
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
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
msgid ""
"When you are on the work order screen, a status button indicates if you are "
"correctly connected to the footswitch."
msgstr ""
#: ../../iot/devices/measurement_tool.rst:3
msgid "Connect a Measurement Tool"
msgstr ""
#: ../../iot/devices/measurement_tool.rst:5
msgid ""
"With Odoo’s *IoT Box*, it is possible to connect measurement tools to your "
"database. Find the list of supported devices here: `Supported devices "
"<https://www.odoo.com/page/iot-hardware>`__,."
msgstr ""
#: ../../iot/devices/measurement_tool.rst:10
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."
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
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
msgid "Here is an example of what it should look like:"
msgstr ""
#: ../../iot/devices/measurement_tool.rst:39
msgid "Link a measurement tool to a quality control point"
msgstr ""
#: ../../iot/devices/measurement_tool.rst:44
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
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
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 ""
#: ../../iot/devices/printer.rst:3
msgid "Connect a Printer"
msgstr ""
#: ../../iot/devices/printer.rst:5
msgid ""
"When using your *IoT Box* in Odoo, you could need to use a printer. Doing so"
" is easy and convenient as it can be done in a few steps. Then, you can use "
"it to print receipts, orders or even reports in different Odoo apps."
msgstr ""
#: ../../iot/devices/printer.rst:13
msgid ""
"To connect the printer to the *IoT Box*, you just have to combine the two by"
" cable."
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
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
msgid "Link the Printer"
msgstr ""
#: ../../iot/devices/printer.rst:40
msgid "To Work Orders"
msgstr ""
#: ../../iot/devices/printer.rst:42
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
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
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
msgid "To Reports"
msgstr ""
#: ../../iot/devices/printer.rst:62
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
msgid "Now, go to the *Printer Reports* tab."
msgstr ""
#: ../../iot/devices/printer.rst:74
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
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
msgid "Print Receipts from the PoS"
msgstr ""
#: ../../iot/devices/printer.rst:88
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*."
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**."
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*."
msgstr ""
#: ../../iot/devices/printer.rst:104
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."
msgstr ""
#: ../../iot/devices/printer.rst:119
msgid "Print Orders in the kitchen"
msgstr ""
#: ../../iot/devices/printer.rst:121
msgid "In restaurant mode, you can send order tickets to the kitchen."
msgstr ""
#: ../../iot/devices/printer.rst:123
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."
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."
msgstr ""

297
locale/da/LC_MESSAGES/livechat.po
View File

@ -4,17 +4,18 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2019
# lhmflexerp <lhm@flexerp.dk>, 2019
# Pernille Kristensen <pernillekristensen1994@gmail.com>, 2020
# Sanne Kristensen <sanne@vkdata.dk>, 2020
# Ejner Sønniksen <ejner@vkdata.dk>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-23 12:10+0200\n"
"PO-Revision-Date: 2018-10-19 08:15+0000\n"
"Last-Translator: lhmflexerp <lhm@flexerp.dk>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Ejner Sønniksen <ejner@vkdata.dk>, 2020\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -22,177 +23,253 @@ msgstr ""
"Language: da\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../livechat/livechat.rst:5
msgid "Live Chat"
msgstr "Live Chat"
#: ../../livechat/overview.rst:3
msgid "Overview"
msgstr "Oversigt"
#: ../../livechat/livechat.rst:8
msgid "Chat in live with website visitors"
#: ../../livechat/overview/get_started.rst:3
msgid "Get Started with Live Chat"
msgstr ""
#: ../../livechat/livechat.rst:10
#: ../../livechat/overview/get_started.rst:5
msgid ""
"With Odoo Live Chat, you can establish a direct contact with your website "
"visitors. A simple dialog box will be available on their screen and will "
"allow them to get in touch with one of your sales representatives. This way,"
" you can easily turn prospects into potential business opportunities. You "
"will also be able to provide assistance to your customers. Overall, this is "
"the perfect tool to improve customer satisfaction."
"Live Chat has the highest satisfaction rating of any communication tool. It "
"allows fast responses and it is accessible and convenient, as your customers"
" can keep doing what they are doing while interacting with you. Remember: "
"your customers want to talk to you, so let's make it easy."
msgstr ""
#: ../../livechat/livechat.rst:19
msgid "Configuration"
msgstr "Konfiguration"
#: ../../livechat/overview/get_started.rst:10
msgid "Set up"
msgstr ""
#: ../../livechat/livechat.rst:21
#: ../../livechat/overview/get_started.rst:12
msgid ""
"To get the Live Chat feature, open the Apps module, search for \"Live Chat\""
" and then click on install."
"Once *Live Chat* is installed on your database, if your website was created "
"with Odoo, the application is automatically added to it. All that is left to"
" do is to go to :menuselection:`Website --> Configuration --> Settings --> "
"Live Chat`."
msgstr ""
#: ../../livechat/livechat.rst:27
#: ../../livechat/overview/get_started.rst:21
msgid ""
"The Live Chat module provides you a direct access to your channels. There, "
"operators can easily join and leave the chat."
"Select the channel to be linked to your website or create one on the fly."
msgstr ""
#: ../../livechat/livechat.rst:34
msgid "Add the live chat to an Odoo website"
#: ../../livechat/overview/get_started.rst:27
msgid "For both scenarios, under:"
msgstr ""
#: ../../livechat/livechat.rst:36
#: ../../livechat/overview/get_started.rst:30
msgid ""
"If your website was created with Odoo, then the live chat is automatically "
"added to it. All that is left to do, is to go to :menuselection:`Website -->"
" Configuration --> Settings` to select the channel to be linked to the "
"website."
"- **Operators**: add agents to respond to the chat requests. Add as many as "
"you like, and keep in mind that operators that do not show any activity in "
"Odoo for more than 30min are considered disconnected."
msgstr ""
#: ../../livechat/livechat.rst:45
msgid "Add the live chat to an external website"
msgstr ""
#: ../../livechat/livechat.rst:47
#: ../../livechat/overview/get_started.rst:33
msgid ""
"If your website was not created with Odoo, go to the Live Chat module and "
"then select the channel to be linked. There, you can simply copy paste the "
"code available into your website. A specific url you can send to customers "
"or suppliers for them to access the live chat is also provided."
"- **Options**: set the default text to be shown on the live chat button; an "
"automated welcome message to be seen by visitors when a conversation is "
"initiated, and the text that prompts the user to initiate a chat."
msgstr ""
#: ../../livechat/livechat.rst:54
msgid "Hide / display the live chat according to rules"
msgstr ""
#: ../../livechat/livechat.rst:56
#: ../../livechat/overview/get_started.rst:36
msgid ""
"Rules for the live chat can be defined on the channel form. For instance, "
"you can choose to display the chat in the countries you speak the language "
"of. On the contrary, you are able to hide the chat in countries your company"
" does not sell in. If you select *Auto popup*, you can also set the length "
"of time it takes for the chat to appear."
"- **Channel Rules**: choose an action for a given URL, and/or per country. "
"In the example below, the chat window automatically pops-up 3 seconds after "
"users (from any country) land on the contact us page."
msgstr ""
#: ../../livechat/livechat.rst:66
msgid "Prepare automatic messages"
msgstr ""
#: ../../livechat/livechat.rst:68
#: ../../livechat/overview/get_started.rst:43
msgid ""
"On the channel form, in the *Options* section, several messages can be typed"
" to appear automatically on the chat. This will entice visitors to reach you"
" through the live chat."
"GeoIP, which refers to the process of finding a computer terminal’s "
"geographical location by its IP address, must be installed on your server. "
"Otherwise, under *Channel Rules*, countries are not taken into account."
msgstr ""
#: ../../livechat/livechat.rst:76
msgid "Start chatting with customers"
#: ../../livechat/overview/get_started.rst:48
msgid "External options"
msgstr ""
#: ../../livechat/livechat.rst:78
#: ../../livechat/overview/get_started.rst:51
msgid ""
"In order to start chatting with customers, first make sure that the channel "
"is published on your website. To do so, select *Unpublished on Website* on "
"the top right corner of the channel form to toggle the *Published* setting. "
"Then, the live chat can begin once an operator has joined the channel."
"If your website was not created with Odoo, you can find the code to be added"
" to your own, under the *Widget* tab."
msgstr ""
#: ../../livechat/livechat.rst:88
#: ../../livechat/overview/get_started.rst:52
msgid ""
"If no operator is available and/or if the channel is unpublished on the "
"website, then the live chat button will not appear to visitors."
"Odoo also offers an URL you can send to users so they can have access to a "
"single live chat page."
msgstr ""
#: ../../livechat/livechat.rst:92
#: ../../livechat/overview/get_started.rst:59
msgid "Managing chat requests"
msgstr ""
#: ../../livechat/overview/get_started.rst:61
msgid ""
"In practice, the conversations initiated by the visitors will appear in the "
"Discuss module and will also pop up as a direct message. Therefore, "
"inquiries can be answered wherever you are in Odoo."
"Conversations initiated by visitors pop up as a direct message, and are "
"shown in *Discuss*. Therefore, inquiries can be answered wherever you are in"
" Odoo."
msgstr ""
#: ../../livechat/livechat.rst:96
#: ../../livechat/overview/get_started.rst:69
msgid ""
"If there several operators in charge of a channel, the system will dispatch "
"sessions randomly between them."
"Conversations are dispatched based on the current workload of the online "
"operators."
msgstr ""
#: ../../livechat/livechat.rst:100
#: ../../livechat/overview/get_started.rst:72
msgid "Leave or join a channel"
msgstr ""
#: ../../livechat/overview/get_started.rst:74
msgid ""
"Go to :menuselection:`Website --> Configuration --> Settings`, access your "
"channel under *Live Chat*, and *Join Channel* or *Leave Channel*."
msgstr ""
#: ../../livechat/overview/get_started.rst:82
#: ../../livechat/overview/responses.rst:48
msgid ":doc:`ratings`"
msgstr ""
#: ../../livechat/overview/get_started.rst:83
#: ../../livechat/overview/ratings.rst:45
msgid ":doc:`responses`"
msgstr ""
#: ../../livechat/overview/ratings.rst:3
msgid "Ratings"
msgstr "Bedømmelser"
#: ../../livechat/overview/ratings.rst:5
msgid ""
"Giving users the opportunity to rate their interactions can help you "
"improving the experience you offer. That means staying on top of your "
"customers' needs, besides keeping track of your operators’ performances."
msgstr ""
#: ../../livechat/overview/ratings.rst:10
msgid "Customer Rating"
msgstr "Kundevurdering"
#: ../../livechat/overview/ratings.rst:12
msgid ""
"Once the user chooses to close the chat window, he can rate his interaction."
msgstr ""
#: ../../livechat/overview/ratings.rst:14
msgid ""
"If the user is *Not satisfied* or *Highly dissatisfied*, a field allowing "
"for an explanation is shown."
msgstr ""
#: ../../livechat/overview/ratings.rst:15
msgid "A copy of the conversation can also be sent by email."
msgstr ""
#: ../../livechat/overview/ratings.rst:22
msgid "The rating is shown on the chat window itself for the operator."
msgstr ""
#: ../../livechat/overview/ratings.rst:28
msgid "And under :menuselection:`Report --> Customer Ratings`."
msgstr ""
#: ../../livechat/overview/ratings.rst:35
msgid "Make the rating public"
msgstr ""
#: ../../livechat/overview/ratings.rst:37
msgid ""
"Go to :menuselection:`Website --> Configuration --> Settings`, access your "
"channel form, click on *Go to Website* and on *Unpublished*, to publish the "
"rating of that channel on your website."
msgstr ""
#: ../../livechat/overview/responses.rst:3
msgid "Commands and Canned Responses"
msgstr ""
#: ../../livechat/overview/responses.rst:5
msgid ""
"Using canned responses can help you save time and have a previous, well-"
"thought response, to some of your most common questions and comments."
msgstr ""
#: ../../livechat/overview/responses.rst:9
msgid "Use commands"
msgstr ""
#: ../../livechat/livechat.rst:102
#: ../../livechat/overview/responses.rst:11
msgid ""
"Commands are useful shortcuts for completing certain actions or to access "
"information you might need. To use this feature, simply type the commands "
"into the chat. The following actions are available :"
"Commands are shortcuts that do specific actions within the chat window:"
msgstr ""
#: ../../livechat/livechat.rst:106
msgid "**/help** : show a helper message."
#: ../../livechat/overview/responses.rst:13
msgid "**/help**: shows a help message."
msgstr ""
#: ../../livechat/livechat.rst:108
msgid "**/helpdesk** : create a helpdesk ticket."
#: ../../livechat/overview/responses.rst:14
msgid "**/helpdesk**: creates a helpdesk ticket."
msgstr ""
#: ../../livechat/livechat.rst:110
msgid "**/helpdesk\\_search** : search for a helpdesk ticket."
#: ../../livechat/overview/responses.rst:15
msgid "**/helpdesk_search**: searches for a helpdesk ticket."
msgstr ""
#: ../../livechat/livechat.rst:112
msgid "**/history** : see 15 last visited pages."
#: ../../livechat/overview/responses.rst:16
msgid "**/history**: shows the last 15 visited pages."
msgstr ""
#: ../../livechat/livechat.rst:114
msgid "**/lead** : create a new lead."
#: ../../livechat/overview/responses.rst:17
msgid "**/lead**: creates a new lead."
msgstr ""
#: ../../livechat/livechat.rst:116
msgid "**/leave** : leave the channel."
#: ../../livechat/overview/responses.rst:18
msgid "**/leave**: leaves the channel."
msgstr ""
#: ../../livechat/livechat.rst:119
#: ../../livechat/overview/responses.rst:0
msgid ""
"If a helpdesk ticket is created from the chat, then the conversation it was "
"generated from will automatically appear as the description of the ticket. "
"The same goes for the creation of a lead."
"- For *helpdesk tickets*: make sure the application is installed on your "
"database and the option *Live Chat* under :menuselection:`Helpdesk --> "
"Configuration --> Helpdesk Teams` is enabled."
msgstr ""
#: ../../livechat/livechat.rst:124
#: ../../livechat/overview/responses.rst:0
msgid ""
"- For *leads*: the *CRM* application must be installed on your database."
msgstr ""
#: ../../livechat/overview/responses.rst:26
msgid ""
"To access the ticket or lead created from the chat, click on the shortcut "
"link."
msgstr ""
#: ../../livechat/overview/responses.rst:33
msgid ""
"Helpdesk tickets created from the chat automatically add the conversation as"
" a description of the ticket. The same goes for the creation of a lead."
msgstr ""
#: ../../livechat/overview/responses.rst:37
msgid "Send canned responses"
msgstr ""
#: ../../livechat/livechat.rst:126
#: ../../livechat/overview/responses.rst:40
msgid ""
"Canned responses allow you to create substitutes to generic sentences you "
"frequently use. Typing a word instead of several will save you a lot of "
"time. To add canned responses, go to :menuselection:`LIVE CHAT --> "
"Configuration --> Canned Responses` and create as many as you need to. Then,"
" to use them during a chat, simply type \":\" followed by the shortcut you "
"assigned."
"Canned responses allow you to have a full piece of text being placed when "
"you type a shortcut word. To create them, go to :menuselection:`Live Chat "
"--> Configuration --> Canned Responses`."
msgstr ""
#: ../../livechat/livechat.rst:136
#: ../../livechat/overview/responses.rst:41
msgid ""
"You now have all of the tools needed to chat in live with your website "
"visitors, enjoy !"
"To use them during a conversation, simply type **:** followed by the "
"shortcut word you created."
msgstr ""

1277
locale/da/LC_MESSAGES/manufacturing.po
View File

File diff suppressed because it is too large Load Diff

381
locale/da/LC_MESSAGES/marketing_automation.po Normal file
View File

@ -0,0 +1,381 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Sanne Kristensen <sanne@vkdata.dk>, 2020
# Mads Søndergaard, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Mads Søndergaard, 2020\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: da\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../marketing_automation.rst:5
msgid "Marketing Automation"
msgstr "Marketing automatisering"
#: ../../marketing_automation/advanced.rst:3
msgid "Advanced"
msgstr "Avanceret"
#: ../../marketing_automation/advanced/understanding_metrics.rst:3
msgid "Understanding Metrics"
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:4
msgid ""
"Metrics are values that help you measure progress and can be a powerful way "
"of linking your employees to goals."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:9
msgid ""
"When you create a workflow in Odoo, its visual content already shows metrics"
" in a graph form and in numbers."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:10
msgid "Let’s consider the example below:"
msgstr ""
#: ../../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."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:20
msgid "A total number of 20 records match the criteria."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:28
msgid ""
"Out of those 20 records, 25 have become participants, in other words, they "
"have matched the criteria."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:36
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."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:41
msgid ""
"The filter here is applied to *all* activities. Leads that lose the tag in "
"the meantime will be excluded from later activities."
msgstr ""
#: ../../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*."
msgstr ""
#: ../../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."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:0
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."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:64
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 ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:65
msgid ""
"If a participant does not match the conditions, it will be added to "
"*Rejected*."
msgstr ""
#: ../../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."
msgstr ""
#: ../../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)."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:79
msgid ":doc:`../overview/automate_actions`"
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:80
msgid ":doc:`../overview/segment`"
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:81
msgid ":doc:`../overview/test`"
msgstr ""
#: ../../marketing_automation/overview.rst:3
msgid "Overview"
msgstr "Oversigt"
#: ../../marketing_automation/overview/automate_actions.rst:3
msgid "Automate Actions and Create a Workflow"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:4
msgid ""
"Automated workflows are a sign that you are building intelligent, data-"
"driven, multifaceted campaigns to enable the delivery of the right message, "
"to the right prospects, at the right time. It also speeds up processes and "
"creates a seamless experience for employees."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:9
msgid "Segment and create a campaign"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:10
msgid "Go to :menuselection:`Campaigns --> Create`."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:12
msgid ""
"In the example below, the *Marketing Automation* application is fully "
"integrated with *Contacts*."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:14
msgid ""
"But it can also be integrated with other apps like CRM, as long as they are "
"installed in your database."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:23
msgid ""
"Depending on the criteria, the *target model updates itself* while the "
"campaign is running. That means that every new record that meets the "
"criteria will be added to the workflow."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:25
msgid ""
"Example: a campaign starts for leads that have no salesman assigned. If at "
"some point, those leads get to have a salesman assigned to it, the campaign "
"will stop running."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:29
msgid "Create a parent activity and start to build a workflow"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:30
msgid "Click on *Add new activity*."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:37
msgid ""
"*Trigger* is the field to set for the activity to start to de deployed."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:39
msgid ""
"Adopt an *Expiry Duration* if you would like to stop actions from being "
"executed after a certain amount of time and in subsequence to the trigger."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:42
msgid ""
"Under *Domain* you can narrow down your target, even more, applying filters "
"for this specific activity."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:47
msgid "Add Child Activities"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:48
msgid ""
"A *child activity* is an action that will take place based on a condition."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:50
msgid ""
"You can either create or add a child activity if on the previous one: the "
"email was opened or not, the email was replied or not, the link was clicked "
"or not, the email bounced back."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:59
#: ../../marketing_automation/overview/test.rst:53
msgid ":doc:`segment`"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:3
msgid "Segment the Database with Filters"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:4
msgid "Filters let you reach a granular level of detail in your records."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:7
msgid "How to work with filters"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:8
msgid ""
"When working with filters, you will see that some of the rules have an arrow"
" button next to it, informing you that the parameter has more variables "
"within it."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:18
msgid ""
"More than one parameter line - *node* (+) - can be added under what is "
"called a *branch* (...)."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:19
msgid "To exclude a *node* or a *branch*, click on *Delete node* (x)."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:27
msgid ""
"Every time a new branch is created, you can choose if you would like the "
"records to match *all* criteria of the upcoming rules, or *any*, meaning one"
" rule or the other."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:32
msgid "Use cases"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:34
msgid ""
"**Scenario**: narrow the target down to new opportunities in the pipeline."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:39
msgid "**Scenario**: narrow the target down to suppliers."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:44
msgid ""
"**Scenario**: narrow the leads down to the ones that contain a certain tag "
"name."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:49
msgid ""
"**Scenario**: narrow the target down to the attendees of a specific event "
"that purchase a specific category of ticket."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:55
msgid "**Scenario**: narrow the target down to the employees who have kids."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:60
msgid ""
"**Scenario**: narrow the target down to records with a helpdesk ticket "
"solved."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:66
#: ../../marketing_automation/overview/test.rst:52
msgid ":doc:`automate_actions`"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:67
msgid ":doc:`../../general/tags/take_tags`"
msgstr ""
#: ../../marketing_automation/overview/test.rst:3
msgid "Launch a Test and Start a Campaign"
msgstr ""
#: ../../marketing_automation/overview/test.rst:4
msgid ""
"Before starting a campaign, launching a test allows you to run the workflow "
"on a test contact and view the sequence of events in action, avoiding "
"mistakes."
msgstr ""
#: ../../marketing_automation/overview/test.rst:8
msgid "Launch a test"
msgstr "Påbegynd en test"
#: ../../marketing_automation/overview/test.rst:9
msgid "Click on *Launch a test*."
msgstr ""
#: ../../marketing_automation/overview/test.rst:12
msgid ""
"Once you have selected the test contact, *Run* the parent activity and the "
"subsequent ones as needed. *Run* and *Stop* activities individually. To stop"
" the whole workflow click on *Stop*."
msgstr ""
#: ../../marketing_automation/overview/test.rst:22
msgid ""
"Launching a test does not add data to your metrics with the purpose of not "
"introducing wrong inputs to reports."
msgstr ""
#: ../../marketing_automation/overview/test.rst:27
msgid "Start and stop a workflow"
msgstr ""
#: ../../marketing_automation/overview/test.rst:28
msgid ""
"Click on *Start* to run the workflow, and on *Stop* to interrupt it. The "
"interruption and new start can happen at any moment. The current status will"
" be shown on the status bar."
msgstr ""
#: ../../marketing_automation/overview/test.rst:38
msgid "Participants and their specific workflow"
msgstr ""
#: ../../marketing_automation/overview/test.rst:39
msgid ""
"*Participants* are all the records that have ever been involved in the "
"campaign."
msgstr ""
#: ../../marketing_automation/overview/test.rst:47
msgid ""
"If you click on *Participants* and open a record, you will find the specific"
" activities the record went/are/will go through, as well as when the "
"workflow was triggered to him. If you wish to cancel an activity click on "
"*Cancel*."
msgstr ""

101
locale/da/LC_MESSAGES/mobile.po
View File

@ -4,16 +4,17 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2019
# Martin Trigaux, 2020
# Mads Søndergaard, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: 2018-10-19 08:15+0000\n"
"Last-Translator: Martin Trigaux, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Mads Søndergaard, 2020\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -26,95 +27,17 @@ msgid "Mobile"
msgstr "Mobil"
#: ../../mobile/firebase.rst:8
msgid "Setup your Firebase Cloud Messaging"
msgstr ""
msgid "Push Notifications"
msgstr "Push notifikationer"
#: ../../mobile/firebase.rst:10
msgid ""
"In order to have mobile notifications in our Android app, you need an API "
"key."
"As of Odoo 12.0, 13.0 or above, there is no more complex configuration to "
"enable push notifications in the mobile app."
msgstr ""
#: ../../mobile/firebase.rst:13
msgid ""
"If it is not automatically configured (for instance for On-premise or "
"Odoo.sh) please follow these steps below to get an API key for the android "
"app."
msgstr ""
#: ../../mobile/firebase.rst:18
msgid ""
"The iOS app doesn't support mobile notifications for Odoo versions < 12."
msgstr ""
#: ../../mobile/firebase.rst:22
msgid "Firebase Settings"
msgstr ""
#: ../../mobile/firebase.rst:25
msgid "Create a new project"
msgstr ""
#: ../../mobile/firebase.rst:27
msgid ""
"First, make sure you to sign in to your Google Account. Then, go to "
"`https://console.firebase.google.com "
"<https://console.firebase.google.com/>`__ and create a new project."
msgstr ""
#: ../../mobile/firebase.rst:34
msgid ""
"Choose a project name, click on **Continue**, then click on **Create "
"project**."
msgstr ""
#: ../../mobile/firebase.rst:37
msgid "When you project is ready, click on **Continue**."
msgstr ""
#: ../../mobile/firebase.rst:39
msgid ""
"You will be redirected to the overview project page (see next screenshot)."
msgstr ""
#: ../../mobile/firebase.rst:43
msgid "Add an app"
msgstr ""
#: ../../mobile/firebase.rst:45
msgid "In the overview page, click on the Android icon."
msgstr ""
#: ../../mobile/firebase.rst:50
msgid ""
"You must use \"com.odoo.com\" as Android package name. Otherwise, it will "
"not work."
msgstr ""
#: ../../mobile/firebase.rst:56
msgid ""
"No need to download the config file, you can click on **Next** twice and "
"skip the fourth step."
msgstr ""
#: ../../mobile/firebase.rst:60
msgid "Get generated API key"
msgstr ""
#: ../../mobile/firebase.rst:62
msgid "On the overview page, go to Project settings:"
msgstr ""
#: ../../mobile/firebase.rst:67
msgid ""
"In **Cloud Messaging**, you will see the **API key** and the **Sender ID** "
"that you need to set in Odoo General Settings."
msgstr ""
#: ../../mobile/firebase.rst:74
msgid "Settings in Odoo"
msgstr ""
#: ../../mobile/firebase.rst:76
msgid "Simply paste the API key and the Sender ID from Cloud Messaging."
"Simply go to :menuselection:`Settings --> General Settings --> Odoo Cloud "
"Notification (OCN)` and make sure that **Push Notifications** is checked."
msgstr ""

158
locale/da/LC_MESSAGES/planning.po Normal file
View File

@ -0,0 +1,158 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Sanne Kristensen <sanne@vkdata.dk>, 2020
# Mads Søndergaard, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Mads Søndergaard, 2020\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: da\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../planning.rst:5
msgid "Planning"
msgstr "Planlægning"
#: ../../planning/overview.rst:3
msgid "Overview"
msgstr "Oversigt"
#: ../../planning/overview/duplicate_a_planning.rst:3
msgid "Create a Schedule and Make Encoding Easier"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:5
msgid ""
"Organize regular schedules or forecast projects in a long term basis. Create"
" shifts to manage your tasks, assign employees, and stay organized at a high"
" level."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:9
msgid "Organize your team by roles"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:11
msgid ""
"Go to :menuselection:`Configuration --> Roles --> Create`. Optionally, go to"
" the *Employees* application, select the respective employee, and under "
"*Work Information* select the *Default Planning Role*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:20
msgid "Make shifts recurrent"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:22
msgid ""
"While creating a shift, select *Repeat* and configure as needed, saving you "
"from the need of re-planning it."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:30
msgid ""
"Repeated shifts are generated for the next six months. A modification is "
"possible in :doc:`Developer mode <../../general/developer_mode/activate>`, "
"from *Settings*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:38
msgid "To duplicate a shift in the Gantt view, press CTRL + drag and drop."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:41
msgid "Save shifts as templates"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:43
msgid ""
"If creating a shift on the fly and know you might use that template in the "
"future, click on *Save as a Template*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:51
msgid ""
"To create a template in advance, go to :menuselection:`Configuration --> "
"Shifts Templates --> Create`."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:55
msgid "Duplicate a planning from the previous week"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:57
msgid ""
"When in the Gantt view, either under *Schedule by Employee, Role or "
"Project*, instead of re-planning shifts that have been planned before, "
"simply click on *Copy Previous Week*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:65
msgid ""
"The integration with the *Time off* and *Employee* applications, show you "
"grayed cells to the days when the employee does not work and is on vacation "
"time, for example."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:3
msgid "Send Planned Shifts and Give Employees Autonomy Over Shifts"
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:5
msgid ""
"If you are not on top of your tasks and shifts you might fall behind, losing"
" productivity. Allowing your employees to have a say over shifts helps you "
"to be on top of your workload, and gives them flexibility."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:10
msgid "Publish and send the planned week by email"
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:12
msgid ""
"Once you have your shifts planned, click on *Send Schedule*. Select *Include"
" Open shift* if you would like the *Unassigned* shifts to be seen."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:19
msgid ""
"Choose if you just want to *Publish* or *Publish and Send*. If you *Publish "
"and Send*, employees get an email that redirects them to their planned "
"tasks:"
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:26
msgid ""
"Employees will not be able to see shifts until they have been published."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:29
msgid "Let employees unassign themselves from shifts"
msgstr "Lad medarbejdere fraskrive dem selv fra vagter"
#: ../../planning/overview/send_planned_shifts.rst:31
msgid ""
"Go to *Configuration* and enable *Allow Unassignment*. From now on, when an "
"employee opens his tasks, he can indicate his unavailability clicking on *I "
"am unavailable*. The shift will be opened again, allowing someone else to "
"take it."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:44
msgid "Employees have portal access; users have access to the database."
msgstr ""

1519
locale/da/LC_MESSAGES/point_of_sale.po
View File

File diff suppressed because it is too large Load Diff

103
locale/da/LC_MESSAGES/portal.po
View File

@ -4,17 +4,18 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Sanne Kristensen <sanne@vkdata.dk>, 2018
# Martin Trigaux, 2019
# Martin Trigaux, 2020
# Kenneth Hansen <kenneth@vkdata.dk>, 2020
# Sanne Kristensen <sanne@vkdata.dk>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-23 12:10+0200\n"
"PO-Revision-Date: 2018-10-19 08:15+0000\n"
"Last-Translator: Martin Trigaux, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Sanne Kristensen <sanne@vkdata.dk>, 2020\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -28,15 +29,15 @@ msgstr ""
#: ../../portal/my_odoo_portal.rst:8
msgid ""
"In this section of the portal you will find all the communications between "
"you and Odoo, documents such Quotations, Sales Orders, Invoices and your "
"Subscriptions."
"In this section of the portal, you will find all the communications between "
"you and Odoo: documents such as quotations, sales orders, invoices and "
"subscriptions."
msgstr ""
#: ../../portal/my_odoo_portal.rst:11
#: ../../portal/my_odoo_portal.rst:12
msgid ""
"To access this section you have to log with your username and password to "
"`Odoo <https://www.odoo.com/my/home>`__ . If you are already logged-in just "
"To access this section, you have to log with your username and password to "
"`Odoo <https://www.odoo.com/my/home>`_. If you are already logged in, just "
"click on your name on the top-right corner and select \"My Account\"."
msgstr ""
@ -47,23 +48,23 @@ msgstr "Tilbud"
#: ../../portal/my_odoo_portal.rst:22
msgid ""
"Here you will find all the quotations sent to you by Odoo. For example, a "
"quotation can be generated for you after adding an Application or a User to "
"quotation can be generated for you after adding an application or a user to "
"your database or if your contract has to be renewed."
msgstr ""
#: ../../portal/my_odoo_portal.rst:29
msgid ""
"The *Valid Until* column shows until when the quotation is valid; after that"
" date the quotation will be \"Expired\". By clicking on the quotation you "
"will see all the details of the offer, the pricing and other useful "
"information."
"The *Valid Until* column shows the date through which the quotation is "
"valid; after that date, the quotation will be \"Expired\". By clicking on "
"the quotation, you will see all the details of the offer, such as the "
"pricing and other useful information."
msgstr ""
#: ../../portal/my_odoo_portal.rst:36
msgid ""
"If you want to accept the quotation just click \"Accept & Pay\" and the "
"If you want to accept the quotation, just click \"Accept & Pay,\" and the "
"quote will get confirmed. If you don't want to accept it, or you need to ask"
" for some modifications, click on \"Ask Changes Reject\"."
" for some modifications, click on \"Ask Changes Reject.\""
msgstr ""
#: ../../portal/my_odoo_portal.rst:41
@ -72,13 +73,13 @@ msgstr "Salgsordre"
#: ../../portal/my_odoo_portal.rst:43
msgid ""
"All your purchases within Odoo such as Upsells, Themes, Applications, etc. "
"will be registered under this section."
"All your purchases within Odoo (Upsells, Themes, Applications, etc.) will be"
" registered under this section."
msgstr ""
#: ../../portal/my_odoo_portal.rst:49
msgid ""
"By clicking on the sale order you can review the details of the products "
"By clicking on the sale order, you can review the details of the products "
"purchased and process the payment."
msgstr ""
@ -88,81 +89,81 @@ msgstr "Fakturaer"
#: ../../portal/my_odoo_portal.rst:55
msgid ""
"All the invoices of your subscription(s), or generated by a sales order, "
"will be shown in this section. The tag before the Amount Due will indicate "
"you if the invoice has been paid."
"All the invoices of your subscriptions and/or sales orders will be shown in "
"this section. The tag before the Amount Due will indicate if the invoice has"
" been paid."
msgstr ""
#: ../../portal/my_odoo_portal.rst:62
msgid ""
"Just click on the Invoice if you wish to see more information, pay the "
"invoice or download a PDF version of the document."
"Just click on the invoice if you wish to see more information, pay the "
"invoice, or download a PDF version of the document."
msgstr ""
#: ../../portal/my_odoo_portal.rst:66
msgid "Tickets"
msgstr "Opgaver"
msgstr "Supportsager"
#: ../../portal/my_odoo_portal.rst:68
msgid ""
"When you submit a ticket through `Odoo Support "
"<https://www.odoo.com/help>`__ a ticket will be created. Here you can find "
"all the tickets that you have opened, the conversation between you and our "
"Agents, the Status of the ticket and the ID (# Ref)."
"When you submit a ticket through `Odoo Support <https://www.odoo.com/help>`,"
" a ticket will be created. Here you can find all the tickets that you have "
"opened, the conversations between you and our Agents, and the statuses and "
"IDs (# Ref) of the tickets."
msgstr ""
#: ../../portal/my_odoo_portal.rst:77
#: ../../portal/my_odoo_portal.rst:76
msgid "Subscriptions"
msgstr "Abonnementer"
#: ../../portal/my_odoo_portal.rst:79
#: ../../portal/my_odoo_portal.rst:78
msgid ""
"You can access to your Subscription with Odoo from this section. The first "
"You can access your subscriptions with Odoo from this section. The first "
"page shows you the subscriptions that you have and their status."
msgstr ""
#: ../../portal/my_odoo_portal.rst:85
#: ../../portal/my_odoo_portal.rst:84
msgid ""
"By clicking on the Subscription you will access to all the details regarding"
" your plan: this includes the number of applications purchased, the billing "
"information and the payment method."
"By clicking on the subscription you will access all the details regarding "
"your plan: the number of applications purchased, the billing information, "
"and the payment method."
msgstr ""
#: ../../portal/my_odoo_portal.rst:89
#: ../../portal/my_odoo_portal.rst:88
msgid ""
"To change the payment method click on \"Change Payment Method\" and enter "
"To change the payment method, click on \"Change Payment Method\" and enter "
"the new credit card details."
msgstr ""
#: ../../portal/my_odoo_portal.rst:95
#: ../../portal/my_odoo_portal.rst:94
msgid ""
"If you want to remove the credit cards saved, you can do it by clicking on "
"\"Manage you payment methods\" at the bottom of the page. Click then on "
"\"Delete\" to delete the payment method."
"If you want to remove the credit cards that are saved, you can do so by "
"clicking on \"Manage your payment methods\" at the bottom of the page. Click"
" \"Delete\" to delete the payment method."
msgstr ""
#: ../../portal/my_odoo_portal.rst:102
msgid ""
"At the date of the next invoice, if there is no payment information provided"
" or if your credit card has expired, the status of your subscription will "
"change to \"To Renew\". You will then have 7 days to provide a valid method"
" of payment. After this delay, the subscription will be closed and you will "
"change to \"To Renew\". You will then have 7 days to provide a valid method "
"of payment. After this delay, the subscription will be closed, and you will "
"no longer be able to access the database."
msgstr ""
#: ../../portal/my_odoo_portal.rst:109
#: ../../portal/my_odoo_portal.rst:108
msgid "Success Packs"
msgstr ""
#: ../../portal/my_odoo_portal.rst:110
#: ../../portal/my_odoo_portal.rst:109
msgid ""
"With a Success Pack/Partner Success Pack, you are assigned an expert to "
"provide unique personalized assistance to help you customize your solution "
"and optimize your workflows as part of your initial implementation. These "
"hours never expire allowing you to utilize them whenever you need support."
"hours never expire, allowing you to utilize them whenever you need support."
msgstr ""
#: ../../portal/my_odoo_portal.rst:116
#: ../../portal/my_odoo_portal.rst:115
msgid ""
"If you need information about how to manage your database see "
":ref:`db_online`"

6
locale/da/LC_MESSAGES/practical.po
View File

@ -6,10 +6,10 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: 2018-10-19 08:15+0000\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"

2162
locale/da/LC_MESSAGES/project.po
View File

File diff suppressed because it is too large Load Diff

449
locale/da/LC_MESSAGES/purchase.po
View File

@ -4,22 +4,20 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Jesper Carstensen <info@danodoo.dk>, 2018
# Ejner Sønniksen <ejner@vkdata.dk>, 2018
# peso <peer.sommerlund@gmail.com>, 2019
# Martin Trigaux, 2019
# Morten Schou <ms@msteknik.dk>, 2019
# Sanne Kristensen <sanne@vkdata.dk>, 2019
# lhmflexerp <lhm@flexerp.dk>, 2019
# peso <peer.sommerlund@gmail.com>, 2020
# Martin Trigaux, 2020
# Morten Schou <ms@msteknik.dk>, 2020
# Sanne Kristensen <sanne@vkdata.dk>, 2020
# lhmflexerp <lhm@flexerp.dk>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 12.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-11-07 15:38+0100\n"
"PO-Revision-Date: 2018-10-19 08:15+0000\n"
"Last-Translator: lhmflexerp <lhm@flexerp.dk>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: lhmflexerp <lhm@flexerp.dk>, 2020\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -54,7 +52,7 @@ msgstr ""
#: ../../purchase/purchases/rfq/3_way_matching.rst:18
#: ../../purchase/purchases/rfq/analyze.rst:24
#: ../../purchase/purchases/rfq/approvals.rst:9
#: ../../purchase/purchases/rfq/bills.rst:31
#: ../../purchase/purchases/rfq/bills.rst:10
#: ../../purchase/purchases/rfq/create.rst:13
#: ../../purchase/purchases/rfq/lock_orders.rst:9
#: ../../purchase/purchases/rfq/reception.rst:14
@ -95,8 +93,8 @@ msgstr ""
#: ../../purchase/purchases/master/import.rst:33
msgid ""
"`Template download "
"<https://docs.google.com/spreadsheets/d/1N8c_eejLV_8NhYMGCfZau_oGCnRkUIT9nwdX7n0shhY/edit#gid=964193981>`__"
":download:`Click here to download the template "
"<../../../_static/example_files/vendor_pricelists_template.csv>`"
msgstr ""
#: ../../purchase/purchases/master/suppliers.rst:3
@ -342,7 +340,7 @@ msgstr ""
#: ../../purchase/purchases/rfq/3_way_matching.rst:9
msgid ""
"To define whether the vendor bill should be paid or not, you can use what we"
" call *3-way matching*. It refers to the comparaison of the information "
" call *3-way matching*. It refers to the comparison of the information "
"appearing on the *Purchase Order*, the *Vendor Bill* and the *Receipt*."
msgstr ""
@ -546,324 +544,54 @@ msgid "Once approved, the purchase order follows the normal process."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:3
msgid "Control supplier bills"
msgstr ""
msgid "Bill Control"
msgstr "Fakturakontrol"
#: ../../purchase/purchases/rfq/bills.rst:5
msgid ""
"The **Purchase** application allows you to manage your purchase orders, "
"incoming products, and vendor bills all seamlessly in one place."
"With Odoo, you can define a setting to help the control of your bills. *Bill"
" Control* lets you choose if the supplier sends you the bill before or after"
" you receive the goods."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:8
#: ../../purchase/purchases/rfq/bills.rst:12
msgid ""
"If you want to set up a vendor bill control process, the first thing you "
"need to do is to have purchase data in Odoo. Knowing what has been purchased"
" and received is the first step towards understanding your purchase "
"management processes."
"For this feature to work, go to :menuselection:`Purchases --> Configuration "
"--> Settings` and select which way you want to control your bills."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:13
msgid "Here is the standard work flow in Odoo:"
#: ../../purchase/purchases/rfq/bills.rst:20
msgid "Change the control policy"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:15
#: ../../purchase/purchases/rfq/bills.rst:22
msgid ""
"You begin with a **Request for Quotation (RFQ)** to send out to your "
"vendor(s)."
"While the setting above will be your default method of bill control, you can"
" always select which way you want to invoice your product on each product "
"page under the *Purchase* tab."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:18
#: ../../purchase/purchases/rfq/bills.rst:26
msgid ""
"Once the vendor has accepted the RFQ, confirm the RFQ into a **Purchase "
"Order (PO)**."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:21
msgid ""
"Confirming the PO generates an **Incoming Shipment** if you purchased any "
"stockable products."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:24
msgid ""
"Upon receiving a **Vendor Bill** from your Vendor, validate the bill with "
"products received in the previous step to ensure accuracy."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:27
msgid ""
"This process may be done by three different people within the company, or "
"only one."
"You might want to use different settings for different types of products."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:34
msgid "Installing the Purchase and Inventory applications"
msgid "Verify your Vendor Bill"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:36
msgid ""
"From the **Apps** application, search for the **Purchase** module and "
"install it. Due to certain dependencies, installing purchase will "
"automatically install the **Inventory** and **Accounting** applications."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:41
msgid "Creating products"
"If you didn’t receive any of your product yet on *Purchase Order* under the "
"*Shipment* tab,"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:43
msgid ""
"Creating products in Odoo is essential for quick and efficient purchasing "
"within Odoo. Simply navigate to the **Products** submenu under **Purchase**,"
" and click **Create**."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:50
msgid ""
"When creating the product, Pay attention to the **Product Type** field, as "
"it is important:"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:53
msgid ""
"Products that are set as **Stockable** or **Consumable** will allow you to "
"keep track of their inventory levels. These options imply stock management "
"and will allow for receiving these kinds of products."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:58
msgid ""
"Conversely, products that are set as a **Service** or **Digital Product** "
"will not imply stock management, simply due to the fact that there is no "
"inventory to manage. You will not be able to receive products under either "
"of these designations."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:64
msgid ""
"It is recommended that you create a **Miscellaneous** product for all "
"purchases that occur infrequently and do not require inventory valuation or "
"management. If you create such a product, it is recommend to set the product"
" type to **Service**."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:70
msgid "Managing your Vendor Bills"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:73
msgid "Purchasing products or services"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:75
msgid ""
"From the purchase application, you can create a purchase order with as many "
"products as you need. If the vendor sends you a confirmation or quotation "
"for an order, you may record the order reference number in the **Vendor "
"Reference** field. This will enable you to easily match the PO with the the "
"vendor bill later (as the vendor bill will probably include the Vendor "
"Reference)"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:85
msgid ""
"Validate the purchase order and receive the products from the **Inventory** "
"application."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:89
msgid "Receiving Products"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:91
msgid ""
"If you purchased any stockable products that you manage the inventory of, "
"you will need to receive the products from the **Inventory** application "
"after you confirm a purchase order. From the **Inventory** dashboard, you "
"should see a button linking you directly to the transfer of products. This "
"button is outlined in red below:"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:100
msgid ""
"Navigating this route will take you to a list of all orders awaiting to be "
"received."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:106
msgid ""
"If you have a lot of awaiting orders, apply a filter using the search bar in"
" the upper right. With this search bar, you may filter based on the "
"**Vendor** (or **Partner**), the product, or the source document, also known"
" as the reference of your purchase order. You also have the capability to "
"group the orders by different criteria under **Group By**. Selecting an item"
" from this list will open the following screen where you then will receive "
"the products."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:117
msgid "Purchasing **Service** products does not trigger a delivery order."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:120
msgid "Managing Vendor Bills"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:122
msgid ""
"When you receive a **Vendor Bill** for a previous purchase, be sure to "
"record it in the **Purchases** application under the **Control Menu**. You "
"need to create a new vendor bill even if you already registered a purchase "
"order."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:130
msgid ""
"The first thing you will need to do upon creating a **Vendor Bill** is to "
"select the appropriate **Vendor** as this will also pull up any associated "
"accounting or pricelist information. From there, you can choose to specify "
"any one or multiple purchase orders to populate the vendor bill with. When "
"you select a purchase order from the list, Odoo will pull any uninvoiced "
"products associated to that purchase order and automatically populate that "
"information below. If you are having a hard time finding the appropriate "
"vendor bill, you may search through the list by inputting the vendor "
"reference number or your internal purchase order number."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:144
msgid ""
"While the invoice is in draft state, you can make any modifications you need"
" (i.e. remove or add product lines, modify quantities, and change prices)."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:149
msgid "Your vendor may send you several bills for the same purchase order if:"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:151
msgid ""
"Your vendor is in back-order and is sending you invoices as they ship the "
"products."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:154
msgid "Your vendor is sending you a partial bill or asking for a deposit."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:156
msgid ""
"Every time you record a new vendor bill, Odoo will automatically populate "
"the product quantities based on what has been received from the vendor. If "
"this value is showing a zero, this means that you have not yet received this"
" product and simply serves as a reminder that the product is not in hand and"
" you may need to inquire further into this. At any point in time, before you"
" validate the vendor bill, you may override this zero quantity."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:165
msgid "Vendor Bill Matching"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:168
msgid "What to do if your vendor bill does not match what you received"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:170
msgid ""
"If the bill you receive from the vendor has different quantities than what "
"Odoo automatically populates as quantities, this could be due to several "
"reasons:"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:174
msgid ""
"The vendor is incorrectly charging you for products and/or services that you"
" have not ordered."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:177
msgid ""
"The vendor is billing you for products that you might not have received yet,"
" as the invoicing control may be based on ordered or received quantities."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:181
msgid "Or the vendor did not bill you for previously purchased products."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:183
msgid ""
"In these instances it is recommended that you verify that the bill, and any "
"associated purchase order to the vendor, are accurate and that you "
"understand what you have ordered and what you have already received."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:187
msgid ""
"If you are unable to find a purchase order related to a vendor bill, this "
"could be due to one of a few reasons:"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:190
msgid ""
"The vendor has already invoiced you for this purchase order, therefore it is"
" not going to appear anywhere in the selection."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:193
msgid ""
"Someone in the company forgot to record a purchase order for this vendor."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:196
msgid "Or the vendor is charging you for something you did not order."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:199
msgid "How product quantities are managed"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:201
msgid ""
"By default, services are managed based on ordered quantities, while "
"stockables and consumables are managed based on received quantities."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:204
msgid ""
"If you need to manage products based on ordered quantities over received "
"quantities, you will need to enable **Debug Mode** from the **About Odoo** "
"information. Once debug mode is activated, select the product(s) you wish to"
" modify, and you should see a new field appear, labeled **Control Purchase "
"Bills**."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:213
msgid ""
"You can then change the default management method for the selected product "
"to be based on either:"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:216
msgid "Ordered quantities"
msgstr "Bestilt antal"
#: ../../purchase/purchases/rfq/bills.rst:218
msgid "Received quantities"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:221
msgid "Batch Billing"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:223
msgid ""
"When creating a vendor bill and selecting the appropriate purchase order, "
"you may continue to select additional purchase orders and Odoo will add the "
"additional line items from that purchase order. If you have not deleted the "
"previous line items from the first purchase order the bill will be linked to"
" all the appropriate purchase orders."
"Depending on the billing policy defined above. If you're supposed to be "
"billed based on ordered quantity, Odoo will suggest a bill for the number of"
" units ordered. If you're supposed to be billed based on the received "
"quantities, Odoo will suggest a bill for 0 as shown above."
msgstr ""
#: ../../purchase/purchases/rfq/cancel.rst:3
@ -1022,100 +750,7 @@ msgid ""
"date to which you wish to proceed to the actual order."
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Receipt"
msgstr "Modtagelse"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Incoming Shipments"
msgstr "Indkommende leverancer"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Vendor"
msgstr "Leverandør"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "You can find a vendor by its Name, TIN, Email or Internal Reference."
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Vendor Reference"
msgstr "Leverandør reference/fakturanr."
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"Reference of the sales order or bid sent by the vendor. It's used to do the "
"matching when you receive the products as this reference is usually written "
"on the delivery order sent by your vendor."
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Order Date"
msgstr "Ordredato"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"Depicts the date where the Quotation should be validated and converted into "
"a purchase order."
msgstr "Datoen hvor tilbuddet skal være konverteret til en indkøbsordre."
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Source Document"
msgstr "Kildedokument"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"Reference of the document that generated this purchase order request (e.g. a"
" sales order)"
msgstr ""
"Reference fra det dokument, som genererede denne indkøbsordreanmodning (fx "
"en salgsordre)"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Deliver To"
msgstr "Levere til"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "This will determine operation type of incoming shipment"
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Drop Ship Address"
msgstr "Dropship adresse"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"Put an address if you want to deliver directly from the vendor to the "
"customer. Otherwise, keep empty to deliver to your own company."
msgstr ""
"Indsæt en adresse hvis du ønsker at levere direkte fra leverandøren til "
"kunden. Hold den ellers tom hvis du ønsker levering til din egen virksomhed."
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Destination Location Type"
msgstr "Lokationstypen for destinationen"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Technical field used to display the Drop Ship Address"
msgstr "Teknisk felt til visning af dropshipping adressen"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Incoterm"
msgstr "Incoterm"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"International Commercial Terms are a series of predefined commercial terms "
"used in international transactions."
msgstr ""
"Internationale leveringsbetingelser er en serie af foruddefinerede "
"kommercielle vilkår, der anvendes i internationale transaktioner."
#: ../../purchase/purchases/rfq/create.rst:32
msgid "View *Request for Quotation* in our Online Demonstration"
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:34
#: ../../purchase/purchases/rfq/create.rst:28
msgid ""
"In **Products**, click on Add an item. Select the product you wish to order "
"in the **Product** menu. Specify the **Quantity** by inserting the number "
@ -1127,26 +762,26 @@ msgid ""
"supplier or enter a new one)."
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:48
#: ../../purchase/purchases/rfq/create.rst:40
msgid ""
"After having clicked on **Send**, you will notice that the RFQ's status will"
" switch from **Draft** to **RFQ Sent**."
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:54
#: ../../purchase/purchases/rfq/create.rst:46
msgid ""
"Once your supplier has replied with an offer, update the RfQ by clicking on "
"**Edit** to fit the quotation (prices, taxes, expected delivery lead time, "
"payment terms, etc.), then click on **Save** to issue a Purchase Order."
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:59
#: ../../purchase/purchases/rfq/create.rst:51
msgid ""
"To proceed with the order, click on **Confirm Order** to send the order to "
"the supplier. The RfQ's status will switch to **Purchase Order**."
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:65
#: ../../purchase/purchases/rfq/create.rst:57
msgid ""
"The status of the RfQ will change to PURCHASE ORDER. Tabs in the upper right"
" corner of the order will show 1 Shipment and 0 Invoice."
@ -1909,7 +1544,7 @@ msgid ""
msgstr ""
#: ../../purchase/replenishment/flows/setup_stock_rule.rst:33
msgid "See also: :doc:`../../../inventory/management/misc/schedulers`"
msgid "See also: :doc:`../../../inventory/management/planning/schedulers`"
msgstr ""
#: ../../purchase/replenishment/flows/setup_stock_rule.rst:35

469
locale/da/LC_MESSAGES/quality.po Normal file
View File

@ -0,0 +1,469 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Pernille Kristensen <pernillekristensen1994@gmail.com>, 2020
# Sanne Kristensen <sanne@vkdata.dk>, 2020
# Ejner Sønniksen <ejner@vkdata.dk>, 2020
# lhmflexerp <lhm@flexerp.dk>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: lhmflexerp <lhm@flexerp.dk>, 2020\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: da\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../quality.rst:5
msgid "Quality"
msgstr "Kvalitet"
#: ../../quality/alert.rst:3
msgid "Alert"
msgstr "Advarsel"
#: ../../quality/alert/alert_mo.rst:3
msgid "Generate a Quality Alert from a Manufacturing Order"
msgstr ""
#: ../../quality/alert/alert_mo.rst:5
msgid ""
"Speaking of manufacturing orders, you have two different situations to "
"consider in Odoo. Those two will result in two different processes:"
msgstr ""
#: ../../quality/alert/alert_mo.rst:8
msgid "You work with a simple manufacturing flow;"
msgstr ""
#: ../../quality/alert/alert_mo.rst:10
msgid "You work with a complex manufacturing flow that includes routings."
msgstr ""
#: ../../quality/alert/alert_mo.rst:13
msgid "Simple manufacturing flow"
msgstr ""
#: ../../quality/alert/alert_mo.rst:15
msgid ""
"If you work with simple manufacturing orders, the *Quality Alerts* will be "
"launched from the manufacturing order itself. When manufacturing a product "
"for which you need to process quality controls, a button *Quality Alert* "
"will appear on the top of your manufacturing order."
msgstr ""
#: ../../quality/alert/alert_mo.rst:23
msgid ""
"By clicking on the button, you can specify the quality problem that arose "
"during the process."
msgstr ""
#: ../../quality/alert/alert_mo.rst:29
msgid ""
"If one of the quality checks failed, the button will be highlighted on the "
"document. If not, the button won’t be highlighted."
msgstr ""
#: ../../quality/alert/alert_mo.rst:36 ../../quality/checks/quality_mo.rst:50
msgid "Manufacturing Flow with Routings"
msgstr ""
#: ../../quality/alert/alert_mo.rst:38
msgid ""
"If you work with routings defined on your manufacturing orders, the quality "
"alerts will be launched directly from the work orders on which the quality "
"checks took place."
msgstr ""
#: ../../quality/alert/alert_mo.rst:48
msgid ""
"Then, a button *Quality Alert* will be available from the work order view. "
"When you click on the button, you can specify the quality problem that "
"appeared during the process."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:3
msgid "Generate a Quality Alert from a Transfer"
msgstr ""
#: ../../quality/alert/alert_transfer.rst:6
msgid "Use the Quality Alert"
msgstr ""
#: ../../quality/alert/alert_transfer.rst:8
msgid ""
"Every time you perform some *Quality Checks* on a transfer, a *Quality "
"Alert* button appears. You can always use it. The button is automatically "
"highlighted once you have a failed quality check for the transfer."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:16
msgid ""
"If you click on that *Quality Alert* button, you can specify what was the "
"problem with the product."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:22
msgid ""
"The *Quality Alert* that is created from the transfer can be found via the "
"button appearing on the top right corner of the transfer."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:28
msgid ""
"You can also access all your *Quality Alerts* via the menu, accessible under"
" *Control*."
msgstr ""
#: ../../quality/checks.rst:3
msgid "Checks"
msgstr "Kontrolpunkter"
#: ../../quality/checks/quality_mo.rst:3
msgid "Perform Quality Checks on Manufacturing Orders"
msgstr ""
#: ../../quality/checks/quality_mo.rst:5
msgid ""
"There are two different situations to consider and that will differ in Odoo "
"processes:"
msgstr ""
#: ../../quality/checks/quality_mo.rst:8
msgid "You work with simple manufacturing flows;"
msgstr ""
#: ../../quality/checks/quality_mo.rst:10
msgid ""
"You work with complex manufacturing flows that are represented by the use of"
" routings in Odoo."
msgstr ""
#: ../../quality/checks/quality_mo.rst:13
msgid "Simple Manufacturing Flow"
msgstr ""
#: ../../quality/checks/quality_mo.rst:16
#: ../../quality/checks/quality_mo.rst:53
#: ../../quality/checks/quality_transfers.rst:6
msgid "Create the Quality Control Point"
msgstr ""
#: ../../quality/checks/quality_mo.rst:18
msgid ""
"To create a quality control point, open the quality app and go to "
":menuselection:`Control --> Control Points`. There, hit create. Make sure to"
" select *Manufacturing* as operation and choose the type of quality check "
"you want to perform."
msgstr ""
#: ../../quality/checks/quality_mo.rst:27
#: ../../quality/checks/quality_mo.rst:69
#: ../../quality/checks/quality_transfers.rst:17
msgid "Process the Quality Check"
msgstr ""
#: ../../quality/checks/quality_mo.rst:29
msgid ""
"Once your *Quality Control Point* has been created, you can create a "
"manufacturing order for your product. Now, and before marking the "
"manufacturing as done, you can register the *Quality Checks*."
msgstr ""
#: ../../quality/checks/quality_mo.rst:39
msgid ""
"Once you have performed your quality checks, you can find them via the "
"*Quality Checks* button available on the manufacturing order form."
msgstr ""
#: ../../quality/checks/quality_mo.rst:46
msgid ""
"If you want to access all your quality checks, you can do this by opening "
"the quality checks menu, under quality control."
msgstr ""
#: ../../quality/checks/quality_mo.rst:55
msgid ""
"If you want to create a *Quality Control Point*, open the *Quality* app and "
"go to :menuselection:`Control --> Control Points`. Then, click on create. "
"Make sure to select *Manufacturing* as operation and select the work order "
"operation on which the quality check should be performed."
msgstr ""
#: ../../quality/checks/quality_mo.rst:64
msgid ""
"Choosing the work order operation is necessary if you want the quality "
"checks to be performed in the work orders. After that, you can choose the "
"type of quality check."
msgstr ""
#: ../../quality/checks/quality_mo.rst:71
msgid ""
"Once your *Quality Control Point* has been configured, create a "
"manufacturing order for your product. You have to plan it if you want to "
"generate the necessary work orders."
msgstr ""
#: ../../quality/checks/quality_mo.rst:78
msgid ""
"Now, process the work order and your quality check will appear. In this "
"example, the quality check requests to enter the serial number of the Table "
"Top component."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:3
msgid "Perform Quality Checks on Transfers"
msgstr ""
#: ../../quality/checks/quality_transfers.rst:8
msgid ""
"To create a *Quality Control Point*, open the *Quality* application. Then, "
"go to :menuselection:`Quality Control --> Control Points --> Create`. Now, "
"you can define the quality control point you want to apply to a specific "
"product. Don’t forget to select a transfer operation type."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:19
msgid ""
"Let’s say that we will receive a laptop. First, create a planned receipt for"
" the product. Then, on the receipt, you will see a *Quality Checks* button "
"that appears to proceed to the quality check you configured before."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:27
msgid ""
"By clicking on it, the instruction set on the quality control point will be "
"displayed and will require the check value."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:33
msgid ""
"Once the quality check is done, you can find it linked to the corresponding "
"transfer and access it by clicking on the button."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:39
msgid ""
"But, if the quality check failed, the stat button will appear in red "
"(instead of green) and Odoo will suggest you to create a *Quality Alert* by "
"highlighting the corresponding button."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:46
msgid ""
"The quality checks can also be found in the *Quality* application by opening"
" the *Quality Checks* menu, under *Quality Control*."
msgstr ""
#: ../../quality/control.rst:3
msgid "Control"
msgstr "Kontrol"
#: ../../quality/control/control_points.rst:3
msgid "Define Quality Control Points"
msgstr ""
#: ../../quality/control/control_points.rst:5
msgid ""
"Quality is an important factor when it comes to products or services. "
"Nowadays, quality has become the differentiating factor for all goods and "
"services. It is vital for businesses to deliver products that meet or exceed"
" expectations. It also helps minimize waste."
msgstr ""
#: ../../quality/control/control_points.rst:10
msgid ""
"That is why most manufacturers would not think of eliminating the quality "
"control from their manufacturing process. After all, removing quality "
"controls would dramatically increase the number of defective products that "
"the company then has to rework or scrap."
msgstr ""
#: ../../quality/control/control_points.rst:15
msgid ""
"Then, using business applications to ensure data quality is important. With "
"Odoo insuring the rear, any major problem can be avoided before occurring!"
msgstr ""
#: ../../quality/control/control_points.rst:20
msgid "Quality Control Points"
msgstr "Kvalitetskontrolpunkter"
#: ../../quality/control/control_points.rst:22
msgid ""
"To create a *Quality Control Point*, go to :menuselection:`Quality --> "
"Quality Control --> Control Points`. Once there, define the product on which"
" the quality control point should take place. The operation at which it "
"takes place also is to be defined here."
msgstr ""
#: ../../quality/control/control_points.rst:27
msgid ""
"The *Quality Control Points* take place during transfers or during the "
"manufacturing process of the products. If working with routings on *Bill of "
"Materials*, you have to precise at which step of the manufacturing process "
"the quality control point needs to be applied."
msgstr ""
#: ../../quality/control/control_points.rst:32
msgid ""
"The *Control Type* defines at which frequency the quality checks should take"
" place:"
msgstr ""
#: ../../quality/control/control_points.rst:35
msgid ""
"**All operations**: all the operations automatically generate quality checks"
" to perform;"
msgstr ""
#: ../../quality/control/control_points.rst:38
msgid ""
"**Randomly**: the quality checks only perform on x% of the operation. The "
"percentage needs to be defined on the control point;"
msgstr ""
#: ../../quality/control/control_points.rst:41
msgid ""
"**Periodically**: the quality checks are performed periodically. The "
"periodicity is based on the defined period (once a day, once a week)."
msgstr ""
#: ../../quality/control/control_points.rst:50
msgid "Quality Control Point Types"
msgstr ""
#: ../../quality/control/control_points.rst:52
msgid ""
"Now, one thing remains to be configured: the type of quality check. There "
"are several types that can be used: text, take a picture, pass-fail, take a "
"measure, register consumed material, register by-product, and print label."
msgstr ""
#: ../../quality/control/control_points.rst:58
msgid ""
"Some types are available only with the manufacturing application installed."
msgstr ""
#: ../../quality/control/control_points.rst:62
msgid "Text"
msgstr "Tekst"
#: ../../quality/control/control_points.rst:64
msgid ""
"This control point type allows giving instructions to workers during the "
"transfer or during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:80
msgid "Take a Picture"
msgstr "Tag et billede"
#: ../../quality/control/control_points.rst:82
msgid ""
"This control point type asks to take a picture of the product applied in a "
"transfer or when manufacturing it."
msgstr ""
#: ../../quality/control/control_points.rst:98
msgid ""
"This process can be simplified by using a connected :doc:`camera "
"<../../iot/devices/measurement_tool>`."
msgstr ""
#: ../../quality/control/control_points.rst:102
msgid "Pass-Fail"
msgstr ""
#: ../../quality/control/control_points.rst:104
msgid ""
"*Pass-Fail* requires to specify if the products pass or fail specific "
"criteria. It can be applied for both transfers or manufacturing orders."
msgstr ""
#: ../../quality/control/control_points.rst:111
msgid ""
"For this kind of type, there is the possibility to define a failure message "
"giving instructions to follow in case of failure."
msgstr ""
#: ../../quality/control/control_points.rst:127
msgid "Take a Measure"
msgstr ""
#: ../../quality/control/control_points.rst:129
msgid ""
"Taking measures requires to enter the product’s measurements during a "
"transfer or during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:132
msgid ""
"To use it, it necessary to specify the norm for your product’s measurements,"
" but also a tolerance threshold. Doing so, all the products with good "
"measures can are automatically accepted."
msgstr ""
#: ../../quality/control/control_points.rst:140
msgid ""
"As for *Pass-Fail*, this type allows defining a failure message that gives "
"instructions to the worker."
msgstr ""
#: ../../quality/control/control_points.rst:156
msgid ""
"This process can be simplified by using connected :doc:`measurement tools "
"<../../iot/devices/camera>`."
msgstr ""
#: ../../quality/control/control_points.rst:159
msgid "Register Consumed Materials"
msgstr ""
#: ../../quality/control/control_points.rst:161
msgid ""
"When using *Register Consumed Materials*, it is required to register the "
"component’s serial/lot numbers during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:165
#: ../../quality/control/control_points.rst:182
msgid "This type is only available when working with routings."
msgstr ""
#: ../../quality/control/control_points.rst:176
msgid "Register By-Products"
msgstr ""
#: ../../quality/control/control_points.rst:178
msgid ""
"With *Register By-Products*, it is required to register the serial/lot "
"number of the by-products that are manufactured."
msgstr ""
#: ../../quality/control/control_points.rst:193
msgid "Print Label"
msgstr ""
#: ../../quality/control/control_points.rst:195
msgid ""
"*Print Label*, as its name points out, allows printing labels to add to the "
"product during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:207
msgid ""
"This process can be simplified by using a connected :doc:`printer "
"<../../iot/devices/printer>`."
msgstr ""

2086
locale/da/LC_MESSAGES/sales.po
View File

File diff suppressed because it is too large Load Diff

558
locale/da/LC_MESSAGES/sms_marketing.po Normal file
View File

@ -0,0 +1,558 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Pernille Kristensen <pernillekristensen1994@gmail.com>, 2020
# Sanne Kristensen <sanne@vkdata.dk>, 2020
# Mads Søndergaard, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Mads Søndergaard, 2020\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: da\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../sms_marketing.rst:5
msgid "SMS Marketing"
msgstr "SMS Marketing"
#: ../../sms_marketing/overview.rst:3
msgid "Overview"
msgstr "Oversigt"
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:3
msgid "Contact Lists and Blacklist"
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:5
msgid ""
"Creating your own list of contacts, or importing it, is useful when you want"
" to create specific groups of people, such as the subscribers of your "
"newsletter. It is also the best way to get started if you are coming from "
"another system and already have built an audience. It makes the SMS "
"distribution easier."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:11
msgid "Contact lists"
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:13
msgid "Go to :menuselection:`Contacts lists --> Contacts lists --> Create`."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:16
msgid ""
"Choose a name for your *Mailing list*, and activate the option *Is Public* "
"if you would like to make the mailing list accessible to your recipients in "
"the unsubscription page (allowing users to update their subscription "
"preferences)."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:22
msgid "History with the Log Notes"
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:25
msgid ""
"A record of the mailings sent is kept on the recipient's chatter (whether it"
" is a contact or an opportunity, for example)."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:28
msgid ""
"This is important as you and team members can easily keep track and see a "
"history of the interactions with your contacts or prospects. Example: your "
"sales representative can easily find out which SMS mailing promotions a "
"customer has received or not."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:35
msgid "Blacklist"
msgstr "Blacklist"
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:38
msgid ""
"If you are coming from another software and have a list of clients who have "
"already asked to be blacklisted, you can import those entries to your "
"database."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:39
msgid ""
"For that, go to :menuselection:`Configuration --> Phone Blacklist --> "
"Import`."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:3
msgid "Integrations and Templates"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:5
msgid ""
"Using SMS to reach people can be a strategy not just used for advertisement "
"purposes, but also as a reminder of events or issued invoices to your "
"costumers, for example."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:9
msgid "Campaigns"
msgstr "Kampagner"
#: ../../sms_marketing/overview/integrations_and_template.rst:11
msgid ""
"First, make sure to have the necessary feature activated. Go to the "
":menuselection:`Email Marketing app --> Configuration --> Settings` and "
"enable *Mailing Campaigns*."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:17
msgid ""
"Now, the menu *Campaigns* is also available on the *SMS Marketing* app, "
"allowing you to manage and have an overview of your SMS mailings under "
"campaigns."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:23
msgid ""
"This feature is especially useful if you have aggregated campaigns, as you "
"have a global reporting view. In addition to that, you can create stages in "
"your Kanban view to better organize the work being done."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:31
msgid "Sending SMSs through the Contacts app"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:34
msgid ""
"Sending SMSs through the contact’s form is available by default in Odoo. It "
"makes your work easier if you need to send an SMS to a specific contact, for"
" example."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:36
msgid ""
"For that, go to the *Contacts* app, select the contact and click on the "
"*SMS* icon next to the phone number."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:41
msgid ""
"If you would like to send a message to multiple contacts at once, choose the"
" *List View*, select all the contacts needed, and under *Action* select "
"*Send SMS*."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:48
msgid "Set up SMS templates"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:50
msgid ""
"To set up *SMS Templates*, activate the :doc:`Developer mode "
"<../../general/developer_mode/activate>`, then go to "
":menuselection:`Technical --> SMS Templates`."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:60
msgid ""
"Use *Dynamic Placeholders* to adapt automatically the content of the SMS to "
"the context."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:63
msgid "SMS Text Messaging is available throughout Odoo:"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:65
msgid "*CRM*: send SMSs to your leads and opportunities."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:66
msgid "*Subscription*: alert customers about their subscription."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:67
msgid "*Accounting*: send payment reminders."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:68
msgid "*Marketing Automation*: automate your SMS marketing campaigns."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:69
msgid ""
"*Inventory*: send an automatic confirmation when a delivery order is done."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:70
msgid ""
"*Sign*: receive a validation code to verify your identity before signing a "
"document online."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:71
msgid ""
"*SEPA debit payment provider*: send a verification code to your customers."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:72
msgid ""
"*Studio*: send an SMS according to your needs by using automated actions."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:75
msgid ""
"For more information about SMS integrations in Odoo and a list of frequently"
" asked questions, go to :doc:`../pricing/pricing_and_faq`."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:79
msgid ":doc:`../../social_marketing/overview/campaigns`"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:80
msgid ":doc:`../../discuss/advanced/email_template`"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:3
msgid "Build, Send and Get Reports from a SMS Mailing"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:5
msgid ""
"Using SMS Marketing as part of your communication strategies can empower you"
" to expand your markets, considering that in some countries emails are not "
"very used or used at all. It also helps to boost conversion rates, as this "
"strategy has a high open-rate percentage among people who use smartphones."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:11
msgid "Get started"
msgstr "Kom igang"
#: ../../sms_marketing/overview/sms_mailing_reports.rst:13
msgid "Go to :menuselection:`SMS Marketing --> Create`."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:18
msgid ""
"Specify a *subject* name to help you remembering what the mailing is about."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:20
msgid ""
"Under *Recipients*, choose to whom you would like the SMS to be sent. If you"
" choose *Contact*, all your Odoo contacts (vendor, customers, etc.) receive "
"your SMS."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:22
msgid ""
"From there, you can refine your recipient list with the *add filter* option."
" In the example below, the message would be sent to the contacts living in "
"Belgium."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:27
msgid ""
"The *Mailing list* option, on the other hand, allows you to choose the "
"specific mailing lists you created to group specific contacts. You are "
"allowed to select multiple ones."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:34
msgid ""
"Under the *SMS Content* tab, links can be included and Odoo automatically "
"generates *link trackers* in order to generate data about these links."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:36
msgid ""
"Under *Settings* you have the option *Include opt-out link*. If activated, "
"the contact is able to unsubscribe from the mailing list."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:43
msgid ""
"In the *Link Tracker* menu under *Configuration*, you can see the history of"
" your sent links, access them and look at statistics."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:50
msgid "Double-check that you have the phone number of your contacts saved."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:53
msgid "Send a mailing"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:57
msgid ""
"Once you have your mailing created, you must choose when you would like it "
"to be delivered:"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:59
msgid ""
"*Put in Queue*: the mailing is triggered with the next automatic run. "
"Interesting option if you do not need the message to be sent at a specific "
"time."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:61
msgid ""
"*Send Now*: sends the message immediately. Use this option if the recipient "
"list is not excessive."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:62
msgid ""
"*Schedule*: allows you to choose a day and time. Best option for mailings "
"that you would like to send during a specific event, to promote an offer "
"while it is active, or to simply plan your content strategy in advance."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:65
msgid ""
"*Test*: allows you to send an SMS to one or multiple numbers for test "
"purposes. Check, for example, if the link provided lands on the right page "
"while making sure they are responsive. If sending it to multiple numbers, "
"you must remember to use a comma between them."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:70
msgid "Visualize reports"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:72
msgid ""
"Under the *Reporting* menu apply filters, measures, and adopt different "
"layouts to do analyses of the performance of your SMS mailings."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:79
msgid ""
"You can also check the price to send an SMS for your country by clicking on "
"the *Information* icon."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:86
msgid ""
"**Buy Credits:** in order to take advantage of the app and its features, "
"make sure you have purchased credits. For more information: "
":doc:`../pricing/pricing_and_faq`."
msgstr ""
#: ../../sms_marketing/pricing.rst:3
msgid "Pricing and FAQ"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:3
msgid "SMS Pricing and FAQ"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:6
msgid "What do I need to send SMSs?"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:7
msgid ""
"SMS Text Messaging is an In-App Purchase (IAP) service that *requires "
"prepaid credits* to work."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:11
msgid "How many types of SMSs are there?"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:12
msgid "There are 2 types: GSM7 and UNICODE."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:14
msgid ""
"**GSM7** is the standard format, with a limit of 160 characters per message,"
" that includes the following characters:"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:23
msgid ""
"**UNICODE** is the format applied if a special character, that *is not* in "
"the GSM7 list, is used. Limit per SMS: 70 characters."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:27
msgid ""
"For GSM7 SMS the size limit is 160 characters, and for Unicode is 70. *Above"
" these limits, the content is divided into a multi-part message* and the "
"limit of characters is lowered to 153 for GSM7 and to 67 for Unicode. The "
"system will inform you in real-time about the number of SMS your message "
"represents."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:34
msgid "How much does it cost to send an SMS?"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:35
msgid ""
"The price of an SMS depends on the destination and the length (number of "
"characters) of the message."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:37
msgid ""
"To see the **price per country, please consult**: `Odoo SMS - FAQ <https"
"://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:39
msgid ""
"The number of SMSs a message represents will be always available to you in "
"your database."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:49
msgid "How do I buy credits?"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:50
msgid "Go to :menuselection:`Settings --> Buy Credits`."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:57
msgid "Or go to :menuselection:`Settings --> View my Services`."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:65
msgid ""
"If you are on Odoo Online (SAAS) and have the Enterprise version, you "
"benefit from free trial credits to test the feature."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:70
msgid "More common questions"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:72
msgid "**Is there an expiration time for my credits?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:74
msgid "No, credits do not expire."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:77
msgid ""
"**Can I send an SMS to a phone number (which is not a mobile phone) because "
"I see the icon in front of the field “phone”?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:80
msgid "Only if that phone number supports SMS (e.g. SIP phones)."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:83
msgid "**Do I receive an invoice to buy my credits?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:85
msgid "Yes."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:88
msgid "**Can the recipient answer to me?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:90
msgid "No, it is not possible to reply to the SMS."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:93
msgid ""
"**What happens if I send multiple SMS but I do not have enough credits to "
"send them all?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:95
msgid ""
"The whole transaction is counted as a single one, so no SMS will be sent "
"until you have enough credits to send them all."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:99
msgid "**Do I have a history of the sent SMSs?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:101
msgid ""
"Yes, the SMS is logged as a note under the chatter of the corresponding "
"record, and a complete history of the SMSs sent is available on "
":doc:`Developer mode <../../general/developer_mode/activate>` under "
":menuselection:`Technical --> SMS`."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:107
msgid "**Can I send as many SMSs I want at once?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:109
msgid "Yes, if you have enough credits."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:112
msgid ""
"**If I have a number that does not exist in the list of recipients, will I "
"lose credits?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:114
msgid ""
"Not if the phone number is in the wrong format (e.g. too many digits). "
"Otherwise, if the SMS is sent to the wrong person or to a fake number, the "
"credit will be lost."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:118
msgid ""
"**What happens if I send my SMS to a paying number (e.g.: a contest to win a"
" ticket for a festival)?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:120
msgid ""
"The SMS will not be delivered to that kind of number, so you won’t be "
"charged."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:123
msgid ""
"**Can I identify the numbers that do not exist when I send several SMSs?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:125
msgid "Only the ones that have an invalid format."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:128
msgid "**How does the GDPR regulation affect this service?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:130
msgid ""
"Please find our `Privacy Policy here <https://iap.odoo.com/privacy#sms>`__."
msgstr ""

362
locale/da/LC_MESSAGES/social_marketing.po Normal file
View File

@ -0,0 +1,362 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Sanne Kristensen <sanne@vkdata.dk>, 2020
# Mads Søndergaard, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:42+0000\n"
"Last-Translator: Mads Søndergaard, 2020\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: da\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../social_marketing.rst:5
msgid "Social Marketing"
msgstr "Social Marketing"
#: ../../social_marketing/overview.rst:3
msgid "Overview"
msgstr "Oversigt"
#: ../../social_marketing/overview/campaigns.rst:3
msgid "Connecting to my Marketplace with Campaigns"
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:5
msgid ""
"Whether your goal is to sell a new product, explain the value of your "
"services or advertise your event, a campaign helps you to connect with your "
"marketplace. They normally involve multiple channels, so it is fundamental "
"to have a solution with which you can plan, execute, track, and analyze your"
" content."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:10
msgid "Go to :menuselection:`Social Marketing --> Campaigns --> Create`."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:16
msgid ""
"As you create content, tabs for that specific channel are shown. The "
"overview of the campaign displays global metrics such as:"
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:19
msgid ""
"*Revenue*: number of users who, from a link in your content, finished a "
"transaction (paid)."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:20
msgid ""
"*Quotations*: number of users who, from a link in your content, have started"
" but not finished a transaction (did not pay)."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:22
msgid ""
"*Leads*: users who have filled out your contact form, from a link in your "
"content."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:25
msgid ""
"To be able to *Send New Mailing*, make sure the feature is enabled in the "
"*Email Marketing* application, under :menuselection:`Email Marketing --> "
"Configuration --> Settings`. To be able to *Send SMS*, the *SMS Marketing* "
"application must be installed on your database."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:30
msgid ""
"*Social Marketing* works integrated with other applications such as *Sales*,"
" *Invoicing*, *CRM* and *Website*."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:34
#: ../../social_marketing/overview/manage_social.rst:77
msgid ":doc:`./push_notifications`"
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:35
#: ../../social_marketing/overview/push_notifications.rst:66
msgid ":doc:`./manage_social`"
msgstr ""
#: ../../social_marketing/overview/livechat.rst:3
msgid "Interact with Customers and Visitors with Live Chat"
msgstr ""
#: ../../social_marketing/overview/livechat.rst:5
msgid ""
"One of the ways you can build stronger relationships with your customers is "
"by making yourself available through live chat. Live chats can have a big "
"impact not just on your customer service, but also on sales performance, as "
"it gives users a chance of having real-time, fast, and effective "
"interaction."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:11
msgid "Configuration"
msgstr "Konfiguration"
#: ../../social_marketing/overview/livechat.rst:13
msgid ""
"Go to :menuselection:`Website --> Configuration --> Settings --> Live Chat` "
"select the appropriate channel, and set it up."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:20
msgid ""
"Under *Channel Rules*, choose when the chat pop-up appears, and an action "
"for a given URL and/or country. Note that to take the country into account, "
"GeoIP must be installed on your server."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:24
msgid "The *Live Chat* application must be installed on your database."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:27
msgid "Monitor your visitors"
msgstr ""
#: ../../social_marketing/overview/livechat.rst:29
msgid ""
"Under the *Visitors* menu, see the visitors that landed on one of your "
":ref:`social_marketing/website_tracked_pages` online or offline."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:34
msgid ""
"You can send emails (if an email address has been saved), send SMSs (if a "
"phone number has been saved), send a push notification (if the user has "
"subscribed to it), and even send a live chat request that will be received "
"by the user once they move to a tracked page."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:36
msgid ""
"Open a record to see details including the visited pages, and the first and "
"last date and time the user was connected."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:43
msgid ""
"Your online visitors will be authenticated if they are linked to a lead or "
"an existing partner."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:44
msgid ""
"If you do not use the *Website* app, you can add a live chat widget to your "
"own website."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:49
msgid "Website’s tracked pages"
msgstr ""
#: ../../social_marketing/overview/livechat.rst:51
msgid ""
"To define which pages are tracked, on the *Website* application, go to "
":menuselection:`Website --> Configuration --> Pages` and enable the option "
"*Track*, on the respective pages."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:60
msgid ":doc:`../../livechat/overview/get_started`"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:3
msgid "Manage Social Media Pages and Create Content"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:5
msgid ""
"Once you are present on social media platforms, it is important to keep them"
" up-to-date. However, that might feel like a full-time job. Having a "
"solution that allows you to create, schedule, keep track, engage with your "
"audience and measure results saves you time and helps you to successfully "
"execute your online strategy, from posts to results."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:12
msgid "Add accounts and create your feed"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:14
msgid ""
"Click on *Add Stream* and grant the required permissions to add your "
"accounts."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:21
msgid "You can link a Facebook page for which you are the admin."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:23
msgid ""
"You are then redirected to your *Feed* and a column with the publications is"
" automatically added."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:25
msgid ""
"You can then add new accounts and/or streams, such as Facebook mentions, and"
" customize your Kanban view."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:31
msgid ""
"Adding social media accounts to your feed will also link KPIs. To get "
"redirected to the statistics page of the social account, click on "
"*Insights*."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:39
msgid "Link a LinkedIn account"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:41
msgid ""
"Go to :menuselection:`Social Marketing --> Configuration --> Social Media`."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:48
msgid ""
"LinkedIn is in Beta Version, therefore, the feed is not available. Only the "
"creation of content."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:51
msgid "Publish content"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:53
msgid ""
"Click on :menuselection:`Social Marketing --> Feed --> New Post`, or go to "
":menuselection:`Social Marketing --> Posts → Create`."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:60
msgid "Choose to upload your post right away or to schedule it."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:61
msgid "Saving your post will apply a draft status to it."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:64
msgid "Overview and plan your posts with a calendar view"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:67
msgid ""
"Through the calendar view, besides having an overview of your planned day, "
"week or month, also see your drafted, scheduled and published posts."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:68
msgid "Drag and drop (scheduled posts) to change their scheduled date."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:70
msgid ""
"Double-click on a date to create a post directly from the *Calendar view*, "
"and click on an existing one to edit it."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:78
#: ../../social_marketing/overview/push_notifications.rst:67
msgid ":doc:`./campaigns`"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:79
msgid ":doc:`./livechat`"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:3
msgid "Use Web Push Notifications"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:5
msgid ""
"Web Push Notifications deliver messages to your user’s device without the "
"need to be on your website, or for them to give personal information. They "
"can be used to inform your users about news, articles and content posted, "
"practical messages like traffic and weather updates, flight information, "
"sales alerts, coupons, and product updates."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:11
msgid "Ask users for permission"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:13
msgid ""
"In the *Website* application go to :menuselection:`Website --> Configuration"
" --> Settings` and enable *Web Push Notifications*."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:20
msgid ""
"Choose your message, icon, and delay time (which is the wait time for the "
"permission request to be shown once the user lands on your page)."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:28
msgid "Send notifications"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:31
msgid "Individually"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:33
msgid "You can send individual messages through the menu *Visitors*."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:40
msgid "To a group"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:42
msgid ""
"Target a bigger segment by selecting multiple visitors in the *View List* "
"(e.g.: all visitors that visited your Homepage)."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:50
msgid ""
"Visitors records are kept under *Visitors* for a week, before getting "
"archived."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:53
msgid "By rules"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:55
msgid ""
"Or go to :menuselection:`Social Marketing --> Posts --> Create`. Under *Web "
"Notification options*, apply filters to send your message to the records "
"that match the rules you set."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:63
msgid "The feature only works with Odoo Website application."
msgstr ""

940
locale/da/LC_MESSAGES/studio.po Normal file
View File

@ -0,0 +1,940 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# lhmflexerp <lhm@flexerp.dk>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:42+0000\n"
"Last-Translator: lhmflexerp <lhm@flexerp.dk>, 2020\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: da\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../studio.rst:5
msgid "Studio"
msgstr "Studio"
#: ../../studio/concepts.rst:3
msgid "Concepts"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:3
msgid "Understanding Automated Actions"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:6
msgid ""
"Automated actions are used to trigger actions. They are based on conditions "
"and happen on top of Odoo’s default business logic."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:9
msgid ""
"Examples of automated actions include: creating a next activity upon a "
"quote's confirmation; adding a user as a follower of a confirmed invoice if "
"its total is higher than a certain amount; or preventing a lead from "
"changing stage if a field is not filled in."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:16
msgid ""
"Let's understand how to properly define *when* an automated action runs and "
"*how* to create one:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:18
msgid ""
"The first step is to choose the :doc:`Model <understanding_general>` on "
"which the action is applied."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:19
msgid ""
"The **Trigger** field defines the event that causes the automated action to "
"happen:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:21
msgid ""
"*On Creation*: when a new record is created. Note that the record is created"
" once saved for the first time."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:23
msgid ""
"*On Update*: when the record is updated. Note that the update happens once "
"the record is saved."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:24
msgid ""
"*On Creation & Update*: on the creation and/or on the update of a record "
"once the form is saved."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:25
msgid "*On Deletion*: on the removal of a record under the condition set."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:26
msgid ""
"*Based on Form Modification*: when the value of the specified *Trigger* "
"field is changed in the interface (user sees the changes before saving the "
"record). Note that this action can only be used with the *Execute Python "
"Code* action type."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:29
msgid ""
"*Based on Timed Condition*: a delay happens after a specific date/time. Set "
"a *Delay after trigger date* if you need a delay to happen before the "
"*Trigger Date*. Example: to send a reminder 15min before a meeting. If the "
"date/time is not set on the form of the model chosen, the date/time "
"considered is the one of the creation/update of the record."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:34
msgid "For every Trigger option, **conditions** can be applied, such as:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:36
msgid ""
"*Before Update Domain*: if designated, this condition must be satisfied "
"before the record is updated."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:38
msgid ""
"*Apply on*: if designated, this condition must be satisfied before executing"
" the action rule (*Action To Do*), and after the update."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:41
msgid ""
"The **Active** option is to be turned off when the rule should be hidden and"
" not executed."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:43
msgid ""
"Under **Action To Do** choose the type of server action that must be "
"executed once records meet the *Trigger* conditions:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:45
msgid ""
"*Execute Python Code*: a block of code is executed. A *Help* tab with the "
"variables that can be used is available."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:47
msgid "*Create New Record*: a new record with new values is created."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:48
msgid "*Update a Record*: updates the record that triggered the action."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:49
msgid ""
"*Execute several actions*: defines an action that triggers other server "
"actions."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:50
msgid ""
"*Send Email*: an automatic :doc:`email "
"<../../discuss/advanced/email_template>` is sent."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:51
msgid ""
"*Add Followers*: :doc:`followers <../../project/tasks/collaborate>` are "
"notified of changes in the task."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:53
msgid ""
"*Create Next Activity*: creates an activity such as: *Call*, *Email*, "
"*Reminder*."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:54
msgid ""
"*Send SMS Text Message*: sends an :doc:`SMS "
"<../../sms_marketing/pricing/pricing_and_faq>`."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:57
msgid "Example"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:59
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
msgid "The user creates the record without an email address set."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:67
msgid "The user updates the record defining an email address."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:68
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
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
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
msgid "If true, the chosen *Action To Do* is performed on the record."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:77
msgid ":doc:`understanding_general`"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:78
msgid ":doc:`../use_cases/automated_actions`"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:3
msgid "Understanding General Concepts"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:7
msgid ""
"Odoo Studio is a toolbox that allows you to add models or adapt "
"functionalities on top of Odoo’s standard behavior without coding knowledge."
" You can also create custom views and modify existing ones without having to"
" get into the XML code."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:11
msgid ""
"Even for experienced developers, typing out code requires time. By using "
"Odoo Studio, you can quickly get your models up and going and focus on the "
"crucial parts of your application. The result is a user-friendly solution "
"that makes customizations and designing new applications easy with or "
"without programming skills."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:15
msgid "Getting started"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:17
msgid ""
"One you start using Odoo Studio, you automatically create a new *module* "
"that contains all your modifications. These modifications can be done on "
"existing screens (*views*), by adding new *fields* in existing applications,"
" or by creating an entirely new *model*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:22
msgid "What is a Module?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:25
msgid ""
"An Odoo **Module** can contain a number of elements, such as: business "
"objects (models), object views, data files, web controllers, and static web "
"data. An application is a collection of modules."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:29
msgid ""
"In object-oriented programming, models usually represent a concept from the "
"real world. Example: Odoo has models for Sales Orders, Users, Countries, "
"etc. If you were to build an application to manage Real Estate sales, a "
"model that represents the Properties for sale would probably be your first "
"step."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:38
msgid "What is a Model (also called Object)?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:40
msgid ""
"A **Model** determines the logical structure of a database and fundamentally"
" determines in which manner data can be stored, organized, and manipulated. "
"In other words, a model is a table of information that can be bridged with "
"other tables."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:45
msgid "What are Fields?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:47
msgid ""
"**Fields** compose models. It is where a record (a piece of data) is "
"registered."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:49
msgid ""
"Example: on the Real Estate application, fields on the Properties model "
"would include the price, address, a picture, a link to the current owner, "
"etc."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:50
msgid ""
"There are 2 main types of fields in Odoo: *basic (or scalar) fields* and "
"*relational fields*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:53
msgid ""
"Basic fields represent simple values, like numbers or text. Relational "
"fields represent relations between models. So, if you have a model for "
"*Customers* and another one for *Properties*, you would use a relational "
"field to link each Property to its Customer."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:56
msgid "Relational Fields in detail"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:59
msgid ""
"**Relational Fields** provide the option to link the data of one model with "
"the data of another model."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:60
msgid ""
"In Odoo, relational field types are: *One2many*, *Many2one*, *Many2many*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:66
msgid ""
"An **One2many** field is a *one-way* direction of selecting *multiple* "
"records from a table."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:68
msgid ""
"Example: a Sales Order can contain multiple Sales Order Lines, which also "
"contain multiple fields of information."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:69
msgid ""
"A **Many2one** field is a *one-way* direction of selecting *one* record from"
" a table."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:70
msgid ""
"Example: you can have many product categories, but each product can only "
"belong to one category."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:71
msgid ""
"A **Many2many** field is a *two-way* direction of selecting records from a "
"table."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:72
msgid "Example: multiple tags can be added to a lead’s form."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:75
msgid "An *One2many* field must have a *Many2one* related to it."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:78
msgid "What are Views?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:80
msgid ""
"**Views** define how records are displayed. They are specified in XML which "
"means that they can be edited independently from the models that they "
"represent. There are various types of views in Odoo, and each of them "
"represents a mode of visualization. Some examples are: *form*, *list*, "
"*kanban*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:85
msgid "What is a Menu?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:87
msgid ""
"A **Menu** is a button that executes and action. In Odoo Studio, to create "
"menus (models) and rearrange their hierarchy, click on *Edit Menu*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:95
msgid "`Studio Basics <https://www.odoo.com/fr_FR/slides/studio-31>`_"
msgstr ""
#: ../../studio/how_to.rst:3
msgid "How To"
msgstr ""
#: ../../studio/how_to/export_import.rst:3
msgid "Export and Import Modules"
msgstr ""
#: ../../studio/how_to/export_import.rst:5
msgid ""
"When you do customizations in Odoo Studio, a new module is created in your "
"database, making it easy to use Studio for prototyping."
msgstr ""
#: ../../studio/how_to/export_import.rst:8
msgid ""
"To export these customizations, activate Studio on the main dashboard and, "
"under the menu *Customizations*, click on *Export*. The default filename is "
"*customizations.zip*."
msgstr ""
#: ../../studio/how_to/export_import.rst:16
msgid ""
"The module created contains the definition of custom models and fields, as "
"well as the UI elements of any customization in an XML format."
msgstr ""
#: ../../studio/how_to/export_import.rst:18
msgid ""
"To import and install the customizations in another instance, connect to the"
" destination database, activate Studio and, under *Customizations*, click on"
" *Import*."
msgstr ""
#: ../../studio/how_to/export_import.rst:25
msgid ""
"Studio does not know which apps are customized (because the same view can be"
" modified on different apps), therefore, it *does not* add the underlying "
"modules as dependencies of the exported module. In other words, the "
"applications installed on the source database should be installed on the "
"destination database."
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:3
msgid "Customizing the Rainbow Man"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:5
msgid ""
"The Rainbow Man in Odoo is an animation shown once the user completes "
"certain tasks and clicks on certain buttons. It is a way to make the "
"software fun to use, and rewarding, for employees."
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:13
msgid ""
"On most buttons in Odoo, such as *Send by Email*, *Confirm* or *Cancel*, "
"once they are selected in Studio, under their *Properties*, the *Rainbow "
"Man* effect can be applied."
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:14
msgid "By default, the feature is active:"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:16
msgid "when opportunities are marked as won;"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:17
msgid "when users empty their inboxes;"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:18
msgid "when the user finishes a tour;"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:19
msgid "when the user finishes doing reconciliations."
msgstr ""
#: ../../studio/how_to/reports.rst:3
msgid "Customizing Reports"
msgstr ""
#: ../../studio/how_to/reports.rst:9
msgid ""
"Odoo uses HTML and CSS technologies to create reports. HTML is a markup "
"language that uses tags, also called elements. It is the core of any webpage"
" because it provides its basic structure. CSS interacts with HTML elements "
"to add style to the page, establishing how the HTML is shown to the user. "
"Odoo’s reports also use Bootstrap’s grid layout, which is the containers, "
"rows, and columns to align content, and support Odoo's website themes."
msgstr ""
#: ../../studio/how_to/reports.rst:11
msgid ""
"When creating a new report, choose the purpose of it and if you would like "
"the report to include header and footer (company logo, name, address, phone,"
" email address, etc.)."
msgstr ""
#: ../../studio/how_to/reports.rst:17
msgid ""
"Under the tab **Add**, you find the fields to be dragged and dropped to the "
"view. *Fields*, *Data tables*, *Subtotal & Total*, and *Address Book* are "
"dynamic elements (meaning that they need a :doc:`one2many or a many2many "
"<../concepts/understanding_general>` related object). *Text*, *Title Block*,"
" *Image*, and *Text in Cell* are static elements."
msgstr ""
#: ../../studio/how_to/reports.rst:26
msgid ""
"Once the element is added to the view, select it to see its **Options**. The"
" first section shows the hierarchy of the selected object and its "
"properties, allowing you to individually edit them. Fields with related "
"objects have their directives shown on *Field Expression*."
msgstr ""
#: ../../studio/how_to/reports.rst:34
msgid ""
"Under **Visible if**, define the rule(s) to set visibility conditions to "
"fields."
msgstr ""
#: ../../studio/how_to/reports.rst:36
msgid ""
"Example: if choosing to display a product image, you could set a visibility "
"rule to only display the ones that are *set* in the product form, avoiding "
"having a plain icon when they are not set."
msgstr ""
#: ../../studio/how_to/reports.rst:40
msgid ""
"**Visible for** is used to set which :doc:`groups "
"<../../general/odoo_basics/add_user>` can have access to specific elements "
"in the report. **Limit visibility to groups**, under *Report*, sets the "
"visibility of the report to specifics groups, meaning that users belonging "
"to other groups do not see the same final document."
msgstr ""
#: ../../studio/how_to/reports.rst:46
msgid ""
"Under the **Report** tab, name your report, choose the paper format, and if "
"the report should be added to the *Print* menu list on its respective "
"document form."
msgstr ""
#: ../../studio/how_to/reports.rst:53
msgid ""
"If activating the :doc:`Developer mode "
"<../../general/developer_mode/activate>`, additional fields such as *Class* "
"under *Options*, and *Reload from attachment* under *Report*, become "
"visible."
msgstr ""
#: ../../studio/how_to/reports.rst:56
msgid ""
"*Class*: add custom CSS classes to the selected element (e.g. Bootstrap "
"classes such as *text-danger*)."
msgstr ""
#: ../../studio/how_to/reports.rst:59
msgid ""
"*Reload from attachment*: saves the report as an attachment of the document "
"when printed. When the report is reprinted, it re-downloads that attachment "
"instead of re-printing it. This means that if the underlying record (e.g. "
"Invoice) changes when compared to the first impression, the report does not "
"reflect the changes because they were done after the attachment was created."
" This is typically useful for reports linked to documents that should not "
"change, such as Invoices."
msgstr ""
#: ../../studio/how_to/reports.rst:67
msgid ""
"Actions in Odoo Studio can be undone until you *Close* the toolbox. Once you"
" have closed Studio, changes can not be undone anymore."
msgstr ""
#: ../../studio/use_cases.rst:3
msgid "Use Cases"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:3
msgid "Advanced Use Cases: Automated Actions"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:5
msgid ""
"**Case scenario 1: when a Belgian lead is created, a 3-stars priority should"
" be automatically applied.**"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:8
msgid "Under *Automations*, click on *Create* and set the following rules:"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:10
msgid "*Model*: Lead/Opportunity"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:11
msgid "*Active*: On"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:12
msgid "*Trigger*: On Creation & Update"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:13
msgid "*Apply on*: Country > Country Name = Belgium"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:14
#: ../../studio/use_cases/filters_status_bar.rst:53
msgid "*Action To Do*: Update the Record"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:15
msgid "*Data to Write*: Lead/Opportunity > Value > 3"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:22
msgid ""
"Check :doc:`this doc <filters_status_bar>` in order to have another "
"automated action example."
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:25
msgid ":doc:`../concepts/understanding_automated_actions`"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:26
#: ../../studio/use_cases/filters_status_bar.rst:61
#: ../../studio/use_cases/models_fields.rst:138
#: ../../studio/use_cases/views.rst:28
msgid ":doc:`../concepts/understanding_general`"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:3
msgid "Advanced Use Cases: Filters and Status Bar"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:5
msgid ""
"**Case scenario 1: on Sales, set a filter on Belgian customers and define it"
" as the default one (the user should still be able to unset the filter).**"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:8
msgid ""
"On your customer’s page, use *Filters* > *Add Custom Filter* to group "
"customers by country. Now, under *Favorites*, *Save Current Search* enabling"
" *Use by default* and *Save*."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:15
msgid ""
"On *Filter Rules* in Studio mode, select the respective filter and enable "
"*Default Filter*."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:21
msgid ""
"**Case scenario 2: add a status bar on the product form to manage its life "
"cycle. Set the values: ‘Prototype’, ‘In use’ and ‘Deprecated’. By default, "
"the Kanban view must be grouped by status.**"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:26
msgid ""
"On your product form, *Add a pipeline status bar* and name its values. "
"Status bars are *selection* fields that give you the ability to follow a "
"specific flow. They are useful to show you the progress that has been made."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:28
msgid ""
"On the *Views* menu, access *Kanban* and, under its *View* options, set the "
"*Default Group by* as *Pipeline status bar*."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:34
msgid ""
"Now, open your product form and set the right status for that product. As "
"you move products throughout stages (also through the product’s form), "
"stages are shown in the Kanban view."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:38
msgid ""
"To make modifications in the pipeline status bar, for example, remember to "
"go back to *Form View*."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:44
msgid ""
"**Case scenario 2.a: when a product goes from ‘In use’ to ‘Deprecate’, set "
"its cost to 0€.**"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:46
msgid ""
"Create an :doc:`automated action "
"<../concepts/understanding_automated_actions>` with the selected values:"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:49
msgid "*Model*: Product Template"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:50
msgid "*Trigger*: On Update"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:51
msgid "*First Domain*: Pipeline status bar = In use"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:52
msgid "*Second Domain*: Pipeline status bar = Deprecated"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:54
msgid "*Data to Write*: Cost (Product Template) > Value > 0"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:3
msgid "Advanced Use Cases: Creating Models and Adding Fields"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:5
msgid ""
"**Case scenario 1: on the leads’ form, if the chosen country is France, show"
" a field 'Pay by check?'**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:8
msgid ""
"On your leads’ form, add a *Related Field* to *Country > Country Name*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:10
msgid ""
"Now, add a *Checkbox* field and define its invisibility options as *Country*"
" (carefully select the one just created) *> is not = > France.*"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:11
msgid "You can now hide the related field created (*Country*) if you wish."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:19
msgid ""
"Another approach is to use the country’s ID. To do so, go to "
":menuselection:`Contacts --> Configuration --> Countries`, select France "
"(for example), and on the URL check its *ID*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:21
msgid ""
"The related field invisibility path should now be *Country* (carefully "
"select the one just created) *> is not = > 75*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:22
msgid "Again, hide the related field with the country’s ID if you prefer."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:28
msgid ""
"**Case scenario 2: create a model called 'Properties' and add fields called:"
" company, value, name, address, active, image.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:31
msgid ""
"From the dashboard, (optionally) start a new module. Then, click on *Edit "
"Menu* and start a *New Menu* (model). Set your menu name and *Confirm*. Now,"
" on its form, drag & drop the necessary fields."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:39
msgid ""
"**Case scenario 2.a: now, you would like to have a model called 'Regions' to"
" which each property must be linked. And, on 'Regions', you would like to "
"see the properties for each region.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:43
msgid ""
"Go to *Edit Menu > New Menu* and create your menu, calling it *Regions*. Add"
" the necessary fields on its form by dragging & dropping them."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:45
msgid ""
"Now, in the form view of *Properties*, add a *Many2one* field with a "
"relation to your model *Region*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:48
msgid ""
"The *Existing Fields* are the ones that are on the current model but not yet"
" in the view."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:60
msgid ""
"Now, go to the model *Regions*, select the form view, and add a status "
"button selecting *Regions (Properties)* as your relational field."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:62
msgid ""
"*Status buttons* are computed fields, meaning that they count the numbers of"
" records on the related model, and allow you to access them."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:69
msgid ""
"When searching for relations, click on *Search more* and filter it by "
"*Custom*. This way you avoid creating duplicates."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:76
msgid ""
"**Case scenario 2.b: in the model 'Properties', show all the tags as "
"checkboxes instead of tags.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:78
msgid ""
"Once the field *Tags* is added to the form, select it and, under its "
"*Properties > Widgets*, choose *Checkboxes*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:85
msgid ""
"**Case scenario 3: on the leads’ form, add a selection field with the "
"values:'Tags' & 'List' & 'Checkboxes'. According to the value of the field, "
"show tags as many2many_tags, many2many_radio, or many2many(_list).**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:89
msgid ""
"In your form view, add a *Tags* field and relate it to *Partners Tag*. Under"
" *Properties*, define its *Widget* as *Many2many*. Do the same process "
"another 2 times for *Checkboxes* and *Tags*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:96
msgid "Now, add a *Selection* field and the necessary values."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:99
msgid ""
"Continue by selecting your *Tags* fields, one by one, to set their "
"*Invisible* options according to their *Widget*. In the example below, the "
"invisibility rule for the *Partner Tags* is set as: *Select Tag type > is "
"not = > Tags.*"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:105
msgid ""
"**Case scenario 4: on a quotation’s form, add a selection field called "
"'Manager Validation' with the values: ‘Accepted’ and ‘Refused’. Only a sales"
" manager can see it, and the field should be set as mandatory if the untaxed"
" amount is higher than 500€.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:109
msgid ""
"On your quotation form, add a *Selection* field with the values *Accepted* "
"and *Refused*. Set its *Required* condition as *Untaxed Amount > 500* and "
"the *Limit visibility to groups* as *Sales / Administrator* or managers."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:117
msgid "**Case scenario 5: change the tooltip of a field for all views.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:119
msgid ""
"Activate the :doc:`Developer mode <../../general/developer_mode/activate>` "
"and open Studio."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:122
msgid ""
"Select the necessary field and, under *Properties*, click on *More* to write"
" your tooltip message on *Field Help*. The tooltip message is the "
"explanatory message shown when the user hovers the field. The message here "
"written is displayed on all views forms where the field is added."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:129
msgid ""
"The *Field Help* message can only be applied to *new* fields. If you would "
"like to change/apply a tooltip for a specific field, use the *Help Tooltip* "
"option under *Properties*."
msgstr ""
#: ../../studio/use_cases/views.rst:3
msgid "Advanced Use Cases: Views"
msgstr ""
#: ../../studio/use_cases/views.rst:5
msgid ""
"**Case scenario 1: in Sales, show orders in a Kanban View instead of a List "
"View.**"
msgstr ""
#: ../../studio/use_cases/views.rst:7
msgid ""
"From the Sales page, access Studio and, under *Views*, set the *Kanban* "
"option as the default one."
msgstr ""
#: ../../studio/use_cases/views.rst:14
msgid ""
"**Case scenario 2: allow for the list of leads to be edited inline without "
"having to switch to the form view.**"
msgstr ""
#: ../../studio/use_cases/views.rst:19
msgid ""
"On the *List View*, under *View* > *Editable*, choose between *New record on"
" top* or *New record at the bottom*. This way, besides defining the order in"
" which new records are displayed in the view, you are able to edit them."
msgstr ""
#: ../../studio/use_cases/views.rst:21
msgid ""
"If the field is left blank, no editing is possible and records are shown "
"based on your column preferences on the lead's page (front-end)."
msgstr ""

458
locale/da/LC_MESSAGES/support.po Normal file
View File

@ -0,0 +1,458 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Morten Schou <ms@msteknik.dk>, 2020
# JonathanStein <jstein@image.dk>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:42+0000\n"
"Last-Translator: JonathanStein <jstein@image.dk>, 2020\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: da\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../support.rst:5
msgid "Support"
msgstr "Support"
#: ../../support/supported_versions.rst:6
msgid "Supported versions"
msgstr ""
#: ../../support/supported_versions.rst:9
msgid ""
"Odoo provides support and bug fixing **for the 3 last major versions** of "
"Odoo."
msgstr ""
#: ../../support/supported_versions.rst:11
msgid ""
"Users hosted on **Odoo Online** may use intermediary versions (sometimes "
"called *SaaS versions*) that are supported as well. These versions are not "
"published for Odoo.sh or On-Premise installations."
msgstr ""
#: ../../support/supported_versions.rst:17
msgid "What's the support status of my Odoo?"
msgstr ""
#: ../../support/supported_versions.rst:19
msgid "This matrix shows the support status of every version."
msgstr ""
#: ../../support/supported_versions.rst:21
msgid "**Major releases are in bold type.**"
msgstr ""
#: ../../support/supported_versions.rst:24
msgid "Odoo Online"
msgstr ""
#: ../../support/supported_versions.rst:24
msgid "Odoo.sh"
msgstr ""
#: ../../support/supported_versions.rst:24
msgid "On-Premise"
msgstr ""
#: ../../support/supported_versions.rst:24
msgid "Release date"
msgstr ""
#: ../../support/supported_versions.rst:26
msgid "**Odoo 14.0**"
msgstr ""
#: ../../support/supported_versions.rst:26
#: ../../support/supported_versions.rst:26
#: ../../support/supported_versions.rst:26
msgid "🏁"
msgstr ""
#: ../../support/supported_versions.rst:26
msgid "October 2020"
msgstr ""
#: ../../support/supported_versions.rst:28
msgid "**Odoo 13.0**"
msgstr ""
#: ../../support/supported_versions.rst:28
#: ../../support/supported_versions.rst:28
#: ../../support/supported_versions.rst:28
#: ../../support/supported_versions.rst:30
#: ../../support/supported_versions.rst:32
#: ../../support/supported_versions.rst:32
#: ../../support/supported_versions.rst:32
#: ../../support/supported_versions.rst:34
#: ../../support/supported_versions.rst:36
#: ../../support/supported_versions.rst:36
#: ../../support/supported_versions.rst:36
msgid "|green|"
msgstr ""
#: ../../support/supported_versions.rst:28
msgid "October 2019"
msgstr ""
#: ../../support/supported_versions.rst:30
msgid "Odoo 12.saas~3"
msgstr ""
#: ../../support/supported_versions.rst:30
#: ../../support/supported_versions.rst:30
#: ../../support/supported_versions.rst:34
#: ../../support/supported_versions.rst:34
#: ../../support/supported_versions.rst:38
#: ../../support/supported_versions.rst:38
#: ../../support/supported_versions.rst:40
#: ../../support/supported_versions.rst:40
#: ../../support/supported_versions.rst:44
#: ../../support/supported_versions.rst:44
#: ../../support/supported_versions.rst:46
#: ../../support/supported_versions.rst:48
#: ../../support/supported_versions.rst:48
#: ../../support/supported_versions.rst:50
msgid "N/A"
msgstr "- Ikke angivet -"
#: ../../support/supported_versions.rst:30
msgid "August 2019"
msgstr ""
#: ../../support/supported_versions.rst:32
msgid "**Odoo 12.0**"
msgstr ""
#: ../../support/supported_versions.rst:32
msgid "October 2018"
msgstr ""
#: ../../support/supported_versions.rst:34
msgid "Odoo 11.saas~3"
msgstr ""
#: ../../support/supported_versions.rst:34
msgid "April 2018"
msgstr ""
#: ../../support/supported_versions.rst:36
msgid "**Odoo 11.0**"
msgstr ""
#: ../../support/supported_versions.rst:36
msgid "October 2017"
msgstr ""
#: ../../support/supported_versions.rst:36
msgid "*End-of-support is planned for October 2020*"
msgstr ""
#: ../../support/supported_versions.rst:38
msgid "Odoo 10.saas~15"
msgstr ""
#: ../../support/supported_versions.rst:38
#: ../../support/supported_versions.rst:40
#: ../../support/supported_versions.rst:42
#: ../../support/supported_versions.rst:42
#: ../../support/supported_versions.rst:44
#: ../../support/supported_versions.rst:46
#: ../../support/supported_versions.rst:48
#: ../../support/supported_versions.rst:50
msgid "|orange|"
msgstr ""
#: ../../support/supported_versions.rst:38
msgid "March 2017"
msgstr ""
#: ../../support/supported_versions.rst:40
msgid "Odoo 10.saas~14"
msgstr ""
#: ../../support/supported_versions.rst:40
msgid "January 2017"
msgstr ""
#: ../../support/supported_versions.rst:42
msgid "**Odoo 10.0**"
msgstr ""
#: ../../support/supported_versions.rst:42
#: ../../support/supported_versions.rst:46
#: ../../support/supported_versions.rst:50
msgid "|red|"
msgstr ""
#: ../../support/supported_versions.rst:42
msgid "October 2016"
msgstr ""
#: ../../support/supported_versions.rst:44
msgid "Odoo 9.saas~11"
msgstr ""
#: ../../support/supported_versions.rst:44
msgid "May 2016"
msgstr ""
#: ../../support/supported_versions.rst:46
msgid "**Odoo 9.0**"
msgstr ""
#: ../../support/supported_versions.rst:46
msgid "October 2015"
msgstr ""
#: ../../support/supported_versions.rst:48
msgid "Odoo 8.saas~6"
msgstr ""
#: ../../support/supported_versions.rst:48
msgid "February 2015"
msgstr ""
#: ../../support/supported_versions.rst:50
msgid "**Odoo 8.0**"
msgstr ""
#: ../../support/supported_versions.rst:50
msgid "September 2014"
msgstr ""
#: ../../support/supported_versions.rst:56
msgid "|green| Supported version"
msgstr ""
#: ../../support/supported_versions.rst:58
msgid "|red| End-of-support"
msgstr ""
#: ../../support/supported_versions.rst:60
msgid "N/A Never released for this platform"
msgstr ""
#: ../../support/supported_versions.rst:62
msgid ""
"|orange| Some of our older customers may still run this version on our Odoo "
"Online servers, we provide help only on blocking issues and advise you to "
"upgrade."
msgstr ""
#: ../../support/supported_versions.rst:64
msgid "🏁 Future version, not released yet"
msgstr ""
#: ../../support/supported_versions.rst:77
msgid "I run an older version of Odoo/OpenERP/TinyERP"
msgstr ""
#: ../../support/supported_versions.rst:79
msgid ""
"OpenERP 7.0, 6.1, 6.0 and 5.0 is not supported anymore, on any platform."
msgstr ""
#: ../../support/supported_versions.rst:81
msgid ""
"TinyERP 4.0, 3.0, 2.0 and 1.0 is not supported anymore, on any platform."
msgstr ""
#: ../../support/supported_versions.rst:83
msgid ""
"You should consider `upgrading <https://upgrade.odoo.com/>`_ your database."
msgstr ""
#: ../../support/what_can_i_expect.rst:8
msgid "What can I expect from the support service?"
msgstr ""
#: ../../support/what_can_i_expect.rst:12
msgid "5 days a week"
msgstr ""
#: ../../support/what_can_i_expect.rst:14
msgid ""
"Your Odoo Online subscription includes **unlimited 24hr support at no extra "
"cost, Monday to Friday**. Our teams are located around the world to ensure "
"you have support, no matter your location. Your support representative could"
" be communicating to you from San Francisco, Belgium, or India!"
msgstr ""
#: ../../support/what_can_i_expect.rst:19
msgid ""
"Our support team can be contacted through our `online support form "
"<https://www.odoo.com/help>`__."
msgstr ""
#: ../../support/what_can_i_expect.rst:23
msgid "What kind of support is included?"
msgstr ""
#: ../../support/what_can_i_expect.rst:25
msgid ""
"Providing you with relevant material (guidelines, product documentation, "
"etc...)"
msgstr ""
#: ../../support/what_can_i_expect.rst:27
msgid ""
"Answers to issues that you may encounter in your standard Odoo database (eg."
" “I cannot close my Point of Sale” or “I cannot find my sales KPIs?”)"
msgstr ""
#: ../../support/what_can_i_expect.rst:29
msgid "Questions related to your account, subscription, or billing"
msgstr ""
#: ../../support/what_can_i_expect.rst:30
msgid ""
"Bug resolution (blocking issues or unexpected behaviour not due to "
"misconfiguration or customization)"
msgstr ""
#: ../../support/what_can_i_expect.rst:32
msgid ""
"Issues that might occur in a test database after upgrading to a newer "
"version"
msgstr ""
#: ../../support/what_can_i_expect.rst:34
msgid ""
"*Odoo Support does not make changes to your production database without your"
" agreement and gives you the material and knowledge to do it yourself!*"
msgstr ""
#: ../../support/what_can_i_expect.rst:39
msgid "What kind of support is not included?"
msgstr ""
#: ../../support/what_can_i_expect.rst:41
msgid ""
"Questions that require us to understand your business processes in order to "
"help you implement your database"
msgstr ""
#: ../../support/what_can_i_expect.rst:43
msgid ""
"Training on how to use our software (we will direct you to our many "
"resources)"
msgstr ""
#: ../../support/what_can_i_expect.rst:44
msgid "Import of documents into your database"
msgstr ""
#: ../../support/what_can_i_expect.rst:45
msgid ""
"Guidance on which configurations to apply inside of an application or the "
"database"
msgstr ""
#: ../../support/what_can_i_expect.rst:46
msgid ""
"How to set up configuration models (Examples include: Inventory Routes, "
"Payment Terms, Warehouses, etc)"
msgstr ""
#: ../../support/what_can_i_expect.rst:48
msgid "Any intervention on your own servers/deployments of Odoo"
msgstr ""
#: ../../support/what_can_i_expect.rst:49
msgid ""
"Any intervention on your own third party account (Ingenico, Authorize, UPS, "
"etc)"
msgstr ""
#: ../../support/what_can_i_expect.rst:50
msgid ""
"Questions or issues related to specific developments or customizations done "
"either by Odoo or a third party (this is specific only to your database or "
"involving code)"
msgstr ""
#: ../../support/what_can_i_expect.rst:54
msgid ""
"You can get this type of support with a `Success Pack <https://www.odoo.com"
"/pricing-packs>`__. With a pack, one of our consultants will analyze the way"
" your business runs and tell you how you can get the most out of your Odoo "
"Database. We will handle all configurations and coach you on how to use "
"Odoo."
msgstr ""
#: ../../support/where_can_i_get_support.rst:6
msgid "Where to find help?"
msgstr ""
#: ../../support/where_can_i_get_support.rst:10
msgid "Odoo Enterprise"
msgstr "Odoo Enterprise"
#: ../../support/where_can_i_get_support.rst:12
msgid ""
"Users who have a valid Odoo Enterprise subscription may always contact our "
"support teams through our `support form <https://www.odoo.com/help>`_, no "
"matter the hosting type you chose (Odoo Online, Odoo.sh or on your own "
"server)."
msgstr ""
#: ../../support/where_can_i_get_support.rst:16
msgid "Please include in your request:"
msgstr ""
#: ../../support/where_can_i_get_support.rst:18
msgid "your subscription number"
msgstr ""
#: ../../support/where_can_i_get_support.rst:19
msgid ""
"the URL of your database if your database is hosted by Odoo (Odoo Online or "
"Odoo.sh)"
msgstr ""
#: ../../support/where_can_i_get_support.rst:21
msgid "Our agents will get back to you as soon as possible."
msgstr ""
#: ../../support/where_can_i_get_support.rst:25
msgid "Odoo Community"
msgstr ""
#: ../../support/where_can_i_get_support.rst:27
msgid "*Odoo Community users don't get access to the support service.*"
msgstr ""
#: ../../support/where_can_i_get_support.rst:29
msgid "Here are some resources that might help you:"
msgstr ""
#: ../../support/where_can_i_get_support.rst:31
msgid "Our `documentation pages <https://www.odoo.com/page/docs>`_."
msgstr ""
#: ../../support/where_can_i_get_support.rst:32
msgid ""
"Ask your question on the `community forum "
"<https://www.odoo.com/forum/help-1>`_."
msgstr ""
#: ../../support/where_can_i_get_support.rst:33
msgid ""
"`Buy Odoo Enterprise "
"<https://www.odoo.com/documentation/13.0/setup/enterprise.html>`_ to get the"
" support and bugfix services."
msgstr ""

242
locale/da/LC_MESSAGES/survey.po Normal file
View File

@ -0,0 +1,242 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Pernille Kristensen <pernillekristensen1994@gmail.com>, 2020
# Sanne Kristensen <sanne@vkdata.dk>, 2020
# Mads Søndergaard, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:42+0000\n"
"Last-Translator: Mads Søndergaard, 2020\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: da\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../survey.rst:5
msgid "Survey"
msgstr "Undersøgelse"
#: ../../survey/overview.rst:3
msgid "Overview"
msgstr "Oversigt"
#: ../../survey/overview/create.rst:3
msgid "Get Started with Surveys"
msgstr ""
#: ../../survey/overview/create.rst:5
msgid ""
"Surveys can be used for a range of purposes that can go from collecting "
"customer feedback, evaluate the success of an event, measure how pleased "
"customers are with your products/services, gauge whether employees are happy"
" and satisfied with their work environment, and even to find out what your "
"market is thinking."
msgstr ""
#: ../../survey/overview/create.rst:11
msgid "Get started"
msgstr "Kom igang"
#: ../../survey/overview/create.rst:13
msgid ""
"When creating your survey, choose a *Title* and *Category*. The *Category* "
"field is used to know in which context the survey is being conducted, as "
"different applications might use it for different purposes such as "
"recruitment, certification, or employee appraisal."
msgstr ""
#: ../../survey/overview/create.rst:22
msgid "Tab: Questions"
msgstr ""
#: ../../survey/overview/create.rst:24
msgid "Add sections and questions by clicking on the respective links."
msgstr ""
#: ../../survey/overview/create.rst:27
msgid ""
"On the *Sections and Questions* form, once the question type is chosen and "
"the answer added, under the tab *Options*, enable *Mandatory Answer*, and "
"set an *Error message* to be shown when the user tries to submit the survey "
"without answering the respective question."
msgstr ""
#: ../../survey/overview/create.rst:29
msgid ""
"Depending on the *Question Type*, the tab *Options* aggregates extra and "
"different possibilities. Examples:"
msgstr ""
#: ../../survey/overview/create.rst:31
msgid ""
"*Single Line Text Box* - can choose a minimum and maximum text length "
"(number of characters - spaces do not count), and its error message."
msgstr ""
#: ../../survey/overview/create.rst:33
msgid ""
"*Multiple choice: multiple answers allowed*: choose between radio buttons or"
" a dropdown menu list, and if you would like to have a comment field. If the"
" user select an answer and type a comment, the values are separately "
"recorded. Or, enable the comment field to be displayed as an answer choice, "
"with which a text type field is displayed."
msgstr ""
#: ../../survey/overview/create.rst:37
msgid ""
"*Matrix Type*: choose if you would like to have one or multiple choices per "
"row."
msgstr ""
#: ../../survey/overview/create.rst:44
msgid "Tab: Description"
msgstr ""
#: ../../survey/overview/create.rst:46
msgid ""
"Write a *Description* to be displayed under the title of the survey's "
"homepage."
msgstr ""
#: ../../survey/overview/create.rst:53
msgid "Click on *Edit* to personalize your pages with the website builder."
msgstr ""
#: ../../survey/overview/create.rst:56
msgid "Tab: Options"
msgstr ""
#: ../../survey/overview/create.rst:58
msgid ""
"Under the tab *Options*, choose the *Layout* of your questions. If choosing "
"*One page per section* or *One page per question*, an option *Back Button* "
"becomes available, which allows the user to go back pages."
msgstr ""
#: ../../survey/overview/create.rst:67
msgid "Test and share the survey"
msgstr ""
#: ../../survey/overview/create.rst:70
msgid ""
"Once your Survey is ready, *Test* it to avoid *Sharing* it with potential "
"errors. As answers get collected, click on *Answers* to access all the "
"details of the respondent and his answers."
msgstr ""
#: ../../survey/overview/create.rst:72
msgid ""
"By default, a filter *Except Test Entries* is applied to keep the list of "
"entries clean with only real participants."
msgstr ""
#: ../../survey/overview/create.rst:79
msgid ""
"Another way to access detailed answers is by going to "
":menuselection:`Participations --> Participations`."
msgstr ""
#: ../../survey/overview/create.rst:80
msgid "Click on *See results* to be redirected to an analytical page."
msgstr ""
#: ../../survey/overview/create.rst:87
#: ../../survey/overview/time_random.rst:34
msgid ":doc:`scoring`"
msgstr ""
#: ../../survey/overview/create.rst:88 ../../survey/overview/scoring.rst:35
msgid ":doc:`time_random`"
msgstr ""
#: ../../survey/overview/scoring.rst:3
msgid "Scoring Surveys"
msgstr ""
#: ../../survey/overview/scoring.rst:5
msgid ""
"To measure your respondent’s performance, knowledge of a subject, or overall"
" satisfaction, attach points to the answers of specific questions. The "
"points are summed up to give your respondent a final score."
msgstr ""
#: ../../survey/overview/scoring.rst:9
msgid ""
"On your survey’s form, click on *Add a question* and, under the tab "
"*Options*, choose between *Scoring with answers at the end* or *Scoring "
"without answers at the end*. Now, on your question’s form, set the right "
"answer and score."
msgstr ""
#: ../../survey/overview/scoring.rst:17
msgid ""
"Set the percentage score the user needs to achieve to have successfully "
"taken the survey. If enabling *Certificate*, choose its template. The "
"certification is automatically sent by email to the users who successfully "
"finish it."
msgstr ""
#: ../../survey/overview/scoring.rst:25
msgid ""
"Enable *Login required* to be able to *Give Badges*. Badges are related to "
"the eLearning section of your website. Besides the logged-in user, visitors "
"of the website that access the page *Courses* can also see the granted "
"badges."
msgstr ""
#: ../../survey/overview/time_random.rst:3
msgid "Time and Randomize Questions"
msgstr ""
#: ../../survey/overview/time_random.rst:6
msgid "Time Limit"
msgstr "Tidsbegrænsning"
#: ../../survey/overview/time_random.rst:10
msgid ""
"On timed surveys, respondents need to complete the survey within a certain "
"period of time. It can be used to ensure that all respondents get the same "
"amount of time to find the answers, or to decrease the chance of having them"
" looking at external resources."
msgstr ""
#: ../../survey/overview/time_random.rst:11
msgid "Set the *Time limit* under the tab *Options*."
msgstr ""
#: ../../survey/overview/time_random.rst:17
msgid ""
"A timer is shown on the pages so the user can keep track of the remaining "
"time. Surveys not \\ submitted by the *Time limit* do not have their answers"
" saved."
msgstr ""
#: ../../survey/overview/time_random.rst:21
msgid "Selection"
msgstr "Udvælgelse"
#: ../../survey/overview/time_random.rst:25
msgid ""
"When you randomize a survey, you allow for the questions to be shuffled in a"
" random order every time someone opens the questionnaire. This can be useful"
" to avoid having respondents looking at each others' answers."
msgstr ""
#: ../../survey/overview/time_random.rst:27
msgid ""
"To do so, under the tab *Options*, enable *Randomized per section*. Now, "
"under the tab *Questions*, set how many of the questions in that section "
"should be taken into account during the shuffling."
msgstr ""

224
locale/da/LC_MESSAGES/timesheets.po Normal file
View File

@ -0,0 +1,224 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Sanne Kristensen <sanne@vkdata.dk>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 15:13+0000\n"
"Last-Translator: Sanne Kristensen <sanne@vkdata.dk>, 2020\n"
"Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: da\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../timesheets.rst:5
msgid "Timesheets"
msgstr "Timesedler"
#: ../../timesheets/overview.rst:3
msgid "Overview"
msgstr "Oversigt"
#: ../../timesheets/overview/compare.rst:3
msgid "Compare Hours and do Analyses"
msgstr ""
#: ../../timesheets/overview/compare.rst:5
msgid ""
"Make sure your employees’ workload is being fairly distributed and control "
"your tasks to get powerful insights when comparing planned versus effective "
"hours."
msgstr ""
#: ../../timesheets/overview/compare.rst:9
msgid "Compare the planned and effective hours of your tasks"
msgstr ""
#: ../../timesheets/overview/compare.rst:11
msgid ""
"Go to :menuselection:`Project --> Reporting --> Tasks Analysis`, select the "
"*Pivot* view and refine your *Measures* to *Effective Hours* and *Planned "
"Hours*."
msgstr ""
#: ../../timesheets/overview/compare.rst:18
msgid ""
"Still on *Project*, under :menuselection:`Reporting --> Planning Analysis` "
"find a pivot view with an analysis of allocated and effective hours of your "
"tasks by user and start date, or by any of the other available filters."
msgstr ""
#: ../../timesheets/overview/compare.rst:27
msgid "HR analysis"
msgstr ""
#: ../../timesheets/overview/compare.rst:29
msgid ""
"Under :menuselection:`Timesheets --> Reporting --> Timesheet/Attendance` "
"have an overview of the worked hours and allocated time of your employees."
msgstr ""
#: ../../timesheets/overview/get_started.rst:3
msgid "Get Started with Timesheets"
msgstr ""
#: ../../timesheets/overview/get_started.rst:5
msgid ""
"When you use timesheets (from any device, anywhere) to track the time spent "
"on tasks, you are able to bill customers for the exact right amount they "
"should be billed. In addition to it, add a description of the work done to "
"have a reliable tracking and history, and compare the forecasted times, all "
"in favor of becoming a more proactive company."
msgstr ""
#: ../../timesheets/overview/get_started.rst:11
msgid "Choose an encoding unit"
msgstr ""
#: ../../timesheets/overview/get_started.rst:14
msgid ""
"Under :menuselection:`Timesheets --> Configuration --> Settings`, choose the"
" unit of measure to register your timesheet. This provides tools and widgets"
" to help you encoding."
msgstr ""
#: ../../timesheets/overview/get_started.rst:15
msgid "*Minimal duration* is the minimum time at which a task is recorded."
msgstr ""
#: ../../timesheets/overview/get_started.rst:18
msgid ""
"*Rounding up* allows you to time up or down to the nearest minutes or hours."
" For example: if the interval is set to 30min, a 14min entry will show up in"
" reports as 0min, and a 29min entry as 30min."
msgstr ""
#: ../../timesheets/overview/get_started.rst:25
msgid "Reportings are expressed in hours, the default value."
msgstr ""
#: ../../timesheets/overview/get_started.rst:28
msgid "Create a task from a SO & timesheet on it"
msgstr ""
#: ../../timesheets/overview/get_started.rst:30
msgid ""
"Under the *General Settings* of your product, categorize it as a service."
msgstr ""
#: ../../timesheets/overview/get_started.rst:34
msgid ""
"On the *Sales* tab, (section *Sales Invoicing Policy*) choose if you want to"
" invoice customers based on the quantity previous ordered (the one sent on a"
" quotation, for instance), on the time recorded (while the service was being"
" executed), or by manually adding the time spent when creating the invoice."
msgstr ""
#: ../../timesheets/overview/get_started.rst:37
msgid ""
"Chose the right *Service Tracking* for you and, from now on, when a sales "
"order is confirmed, Odoo automatically creates a task/project (if that was "
"the chosen option) and allows you to timesheet on it."
msgstr ""
#: ../../timesheets/overview/get_started.rst:44
msgid "Choose an Invoicing Policy"
msgstr ""
#: ../../timesheets/overview/get_started.rst:46
msgid ""
"Go to :menuselection:`Timesheets --> Configuration --> Settings` and choose "
"if you want the recorded time to be directly invoiced, or if it should be "
"approved first."
msgstr ""
#: ../../timesheets/overview/get_started.rst:54
msgid "Send reminders"
msgstr ""
#: ../../timesheets/overview/get_started.rst:57
msgid ""
"Choose to have an automatic email being sent to all users and managers who "
"have not recorded their times."
msgstr ""
#: ../../timesheets/overview/get_started.rst:59
msgid ""
"Go to :menuselection:`Timesheets --> Configuration --> Settings` and enable "
"the *Employee Reminder* and *Manager Reminder* features."
msgstr ""
#: ../../timesheets/overview/get_started.rst:66
msgid ""
"Odoo Timesheets continues to run even if there is no internet connection. "
"The data syncs once you are back online."
msgstr ""
#: ../../timesheets/overview/time_off.rst:3
msgid "Create Timesheets upon Time Off Validation"
msgstr ""
#: ../../timesheets/overview/time_off.rst:5
msgid ""
"Odoo automatically timesheets on project/tasks upon time off requests. This "
"allows for better overall control over the validation of timesheets, as it "
"does not leave place for forgetfulness and questions after hours that have "
"not been timesheeted by the employee."
msgstr ""
#: ../../timesheets/overview/time_off.rst:9
msgid ""
"Activate the :doc:`Developer mode <../../general/developer_mode/activate>`, "
"go to *Timesheets*, and change the *Project* and *Task* set by default, if "
"you like."
msgstr ""
#: ../../timesheets/overview/time_off.rst:16
msgid ""
"Go to :menuselection:`Time Off --> Configuration --> Time Off Types`. Select"
" or create the needed type, and decide if you would like the requests to be "
"validated or not."
msgstr ""
#: ../../timesheets/overview/time_off.rst:26
msgid ""
"Now, once the employee has requested his time off and the request has been "
"validated (or not, depending on the setting chosen), the time is "
"automatically allocated on *Timesheets*, under the respective project and "
"task."
msgstr ""
#: ../../timesheets/overview/time_off.rst:27
msgid ""
"On the example below, the user requested *Paid Time off* from July 13th to "
"15th."
msgstr ""
#: ../../timesheets/overview/time_off.rst:33
msgid ""
"Considering that validation is not required, the requested time off is "
"automatically displayed in *Timesheets*. If validation is necessary, the "
"time is automatically allocated after the responsible person for validating "
"does it so."
msgstr ""
#: ../../timesheets/overview/time_off.rst:41
msgid ""
"Click on the magnifying glass, hovering over the concerned cell, to access "
"all the aggregated data on that cell (day), and see details regarding the "
"project/task."
msgstr ""
#: ../../timesheets/overview/time_off.rst:49
msgid ":doc:`compare`"
msgstr ""

2585
locale/da/LC_MESSAGES/website.po
View File

File diff suppressed because it is too large Load Diff

16635
locale/es/LC_MESSAGES/accounting.po
View File

File diff suppressed because it is too large Load Diff

9
locale/es/LC_MESSAGES/applications.po
View File

@ -6,11 +6,10 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Martin Trigaux, 2018\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -20,4 +19,4 @@ msgstr ""
#: ../../applications.rst:3
msgid "Applications"
msgstr "Solicitudes"
msgstr ""

1737
locale/es/LC_MESSAGES/contributing.po Normal file
View File

File diff suppressed because it is too large Load Diff

747
locale/es/LC_MESSAGES/crm.po
View File

File diff suppressed because it is too large Load Diff

478
locale/es/LC_MESSAGES/db_management.po
View File

@ -6,11 +6,10 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-27 11:08+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Antonio Trueba, 2018\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -107,130 +106,207 @@ msgstr ""
#: ../../db_management/db_online.rst:51
msgid "Upgrade"
msgstr "Actualizar"
msgstr ""
#: ../../db_management/db_online.rst:53
msgid ""
"Make sure to be connected to the database you want to upgrade and access the"
" database management page. On the line of the database you want to upgrade, "
"click on the \"Upgrade\" button."
"Upgrading your database to a newer version of Odoo is a complex operation "
"that require time and caution. It is extremely important that you fully test"
" the process before upgrading your production database."
msgstr ""
#: ../../db_management/db_online.rst:57
msgid ""
"Odoo releases new versions regularly (at least once a year), and upgrading "
"your database to enjoy new Odoo features is part of the Odoo Online "
"experience."
msgstr ""
#: ../../db_management/db_online.rst:60
msgid ""
"You have the possibility to choose the target version of the upgrade. By "
"default, we select the highest available version available for your "
"database; if you were already in the process of testing a migration, we will"
" automatically select the version you were already testing (even if we "
"released a more recent version during your tests)."
"The upgrade process can take some time, especially if you use multiple apps "
"or apps that manage sensitive data (e.g. Accounting, Inventory, etc.). In "
"general, the 'smaller' the database, the quickest the upgrade. A single-user"
" database that uses only CRM will be processed faster than a multi-company, "
"multi-user database that uses Accounting, Sales, Purchase and Manufacturing."
msgstr ""
#: ../../db_management/db_online.rst:66
msgid ""
"By clicking on the \"Test upgrade\" button an upgrade request will be "
"generated. If our automated system does not encounter any problem, you will "
"receive a \"Test\" version of your upgraded database."
"Unfortunately, it is impossible to give time estimates for every upgrade "
"request, since Odoo.com will test manually every database upgrade at least "
"once and will need to correct/adapt changes made to the standard Odoo Apps "
"(e.g. through Studio or through a Success Pack) on a case-by-case basis. "
"This can make the process slower, since requests are treated in the order "
"they arrive. This is especially true in the months following the release of "
"a new major version, which can lengthen the upgrade delay significantly."
msgstr ""
#: ../../db_management/db_online.rst:73
msgid ""
"If our automatic system detect an issue during the creation of your test "
"database, our dedicated team will have to work on it. You will be notified "
"by email and the process will take up to 4 weeks."
#: ../../db_management/db_online.rst:74
msgid "The upgrade process is quite simple from your point of view:"
msgstr ""
#: ../../db_management/db_online.rst:76
msgid "You request a test upgrade"
msgstr ""
#: ../../db_management/db_online.rst:77
msgid ""
"You will have the possibility to test it for 1 month. Inspect your data "
"(e.g. accounting reports, stock valuation, etc.), check that all your usual "
"flows work correctly (CRM flow, Sales flow, etc.)."
"Once all tests have been validated **by you**, you upgrade your actual "
"database"
msgstr ""
#: ../../db_management/db_online.rst:79
msgid ""
"The process to request a test or a production (*actual*) upgrade is the "
"same."
msgstr ""
#: ../../db_management/db_online.rst:81
msgid ""
"Once you are ready and that everything is correct in your test migration, "
"you can click again on the Upgrade button, and confirm by clicking on "
"Upgrade (the button with the little rocket!) to switch your production "
"database to the new version."
"First, make sure to be connected to the database you want to upgrade and "
"access the `database management page <https://www.odoo.com/my/databases>`__."
msgstr ""
#: ../../db_management/db_online.rst:89
#: ../../db_management/db_online.rst:84
msgid ""
"You have to have an active session with access to the Settings app in the "
"database you want to upgrade for the button to be visible."
msgstr ""
#: ../../db_management/db_online.rst:87
msgid ""
"On the line of the database you want to upgrade, click on the \"Cog\" menu. "
"If an newer version of Odoo is available, you will see an 'Upgrade' button."
msgstr ""
#: ../../db_management/db_online.rst:94
msgid ""
"You have the possibility to choose the target version of the upgrade. By "
"default, we select the highest available version available for your "
"database; if you were already in the process of testing an upgrade, we will "
"automatically select the version you were already testing (even if we "
"released a more recent version during your tests)."
msgstr ""
#: ../../db_management/db_online.rst:103
msgid ""
"By clicking on the \"Test upgrade\" button, an upgrade request will be "
"generated. Only one request can be made at time for each database; if a "
"request has already been made, you will see an 'Upgrade Queued' note instead"
" and asking another request will not be possible."
msgstr ""
#: ../../db_management/db_online.rst:108
msgid ""
"A test upgrade will create a copy of your database, upgrade it and make it "
"available to you automatically once successful. If this is the first test "
"you request for this particular database, a manual testing phase will be "
"done by Odoo.com - this could take time (up to several weeks). Subsequent "
"requests will not go through that manual testing step and will usually be "
"made available in a few hours. Once the test database is available, you "
"should receive an e-mail with the URL of the test database."
msgstr ""
#: ../../db_management/db_online.rst:116
msgid ""
"**Testing your database is the most important step of the upgrade process!**"
" Even though we test all upgrades manually, we do not know your work "
"processes. A change in standard worfklows of Odoo in new versions might "
"require you to change internal processes, or some of the customizations you "
"made through Odoo Studio might not work properly. *It is up to you to make "
"sure that everything works as it should!* You can report issues with your "
"test database through our `Support page <https://www.odoo.com/help>`__."
msgstr ""
#: ../../db_management/db_online.rst:124
msgid ""
"Make sure to do one last test of your upgrade right before the final upgrade"
" (e.g. the day before) to ensure everything will run smoothly. Downgrading "
"is not possible and post-poning an upgrade is always easier than being "
"prevented to work by an upgrade issue after the fact!"
msgstr ""
#: ../../db_management/db_online.rst:129
msgid ""
"Once you are ready and you have validated all your tests, you can click "
"again on the Upgrade button and confirm by clicking on Upgrade (the button "
"with the little rocket!) to switch your production database to the new "
"version. Your database will then be taken offline within the next 10 minutes"
" and will be upgraded automatically; you receive a confirmation e-mail once "
"the process is completed."
msgstr ""
#: ../../db_management/db_online.rst:140
msgid ""
"Your database will be taken offline during the upgrade (usually between "
"30min up to several hours for big databases), so make sure to plan your "
"migration during non-business hours."
msgstr ""
#: ../../db_management/db_online.rst:96
#: ../../db_management/db_online.rst:146
msgid "Duplicating a database"
msgstr ""
#: ../../db_management/db_online.rst:98
#: ../../db_management/db_online.rst:148
msgid ""
"Database duplication, renaming, custom DNS, etc. is not available for trial "
"databases on our Online platform. Paid Databases and \"One App Free\" "
"database can duplicate without problem."
msgstr ""
#: ../../db_management/db_online.rst:103
#: ../../db_management/db_online.rst:153
msgid ""
"In the line of the database you want to duplicate, you will have a few "
"buttons. To duplicate your database, just click **Duplicate**. You will have"
" to give a name to your duplicate, then click **Duplicate Database**."
msgstr ""
"Si quiere duplicar en la línea de la base de datos, tendrá algunos botones. "
"Para duplicar su base de datos, solo de clic en **Duplicar**. Tendrá que "
"darle un nombre a su duplicado, luego de clic en **Duplicar Base de Datos**."
#: ../../db_management/db_online.rst:110
#: ../../db_management/db_online.rst:160
msgid ""
"If you do not check the \"For testing purposes\" checkbox when duplicating a"
" database, all external communication will remain active:"
msgstr ""
#: ../../db_management/db_online.rst:113
#: ../../db_management/db_online.rst:163
msgid "Emails are sent"
msgstr "Los correos electrónicos fueron enviados"
msgstr ""
#: ../../db_management/db_online.rst:115
#: ../../db_management/db_online.rst:165
msgid ""
"Payments are processed (in the e-commerce or Subscriptions apps, for "
"example)"
msgstr ""
#: ../../db_management/db_online.rst:118
#: ../../db_management/db_online.rst:168
msgid "Delivery orders (shipping providers) are sent"
msgstr "Órdenes de envio (proveedores de envio) fueron enviadas"
msgstr ""
#: ../../db_management/db_online.rst:120
#: ../../db_management/db_online.rst:170
msgid "Etc."
msgstr "Etc."
msgstr ""
#: ../../db_management/db_online.rst:122
#: ../../db_management/db_online.rst:172
msgid ""
"Make sure to check the checkbox \"For testing purposes\" if you want these "
"behaviours to be disabled."
msgstr ""
#: ../../db_management/db_online.rst:125
#: ../../db_management/db_online.rst:175
msgid ""
"After a few seconds, you will be logged in your duplicated database. Notice "
"that the url uses the name you chose for your duplicated database."
msgstr ""
"Después de unos segundos, podrás iniciar sesión en tu base de datos "
"duplicada. Observe que la dirección URL utiliza el nombre que elijo para su "
"base de datos duplicada."
#: ../../db_management/db_online.rst:129
#: ../../db_management/db_online.rst:180
msgid "Duplicate databases expire automatically after 15 days."
msgstr ""
"Las bases de datos duplicadas expiran automaticamente después de 15 días."
#: ../../db_management/db_online.rst:137
#: ../../db_management/db_online.rst:188
msgid "Rename a Database"
msgstr ""
#: ../../db_management/db_online.rst:139
#: ../../db_management/db_online.rst:190
msgid ""
"To rename your database, make sure you are connected to the database you "
"want to rename, access the `database management page "
@ -238,15 +314,15 @@ msgid ""
"to give a new name to your database, then click **Rename Database**."
msgstr ""
#: ../../db_management/db_online.rst:150
#: ../../db_management/db_online.rst:201
msgid "Deleting a Database"
msgstr ""
#: ../../db_management/db_online.rst:152
#: ../../db_management/db_online.rst:203
msgid "You can only delete databases of which you are the administrator."
msgstr ""
#: ../../db_management/db_online.rst:154
#: ../../db_management/db_online.rst:205
msgid ""
"When you delete your database all the data will be permanently lost. The "
"deletion is instant and for all the Users. We advise you to do an instant "
@ -254,45 +330,45 @@ msgid ""
"backup may be several hours old at that point."
msgstr ""
#: ../../db_management/db_online.rst:160
#: ../../db_management/db_online.rst:211
msgid ""
"From the `database management page <https://www.odoo.com/my/databases>`__, "
"on the line of the database you want to delete, click on the \"Delete\" "
"button."
msgstr ""
#: ../../db_management/db_online.rst:167
#: ../../db_management/db_online.rst:218
msgid ""
"Read carefully the warning message that will appear and proceed only if you "
"fully understand the implications of deleting a database:"
msgstr ""
#: ../../db_management/db_online.rst:173
#: ../../db_management/db_online.rst:224
msgid ""
"After a few seconds, the database will be deleted and the page will reload "
"automatically."
msgstr ""
#: ../../db_management/db_online.rst:177
#: ../../db_management/db_online.rst:228
msgid ""
"If you need to re-use this database name, it will be immediately available."
msgstr ""
#: ../../db_management/db_online.rst:179
#: ../../db_management/db_online.rst:230
msgid ""
"It is not possible to delete a database if it is expired or linked to a "
"Subscription. In these cases contact `Odoo Support "
"<https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_online.rst:183
#: ../../db_management/db_online.rst:234
msgid ""
"If you want to delete your Account, please contact `Odoo Support "
"<https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:7
msgid "On-premise Database management"
msgid "On-premises Database management"
msgstr ""
#: ../../db_management/db_premise.rst:10
@ -319,8 +395,9 @@ msgid ""
"message:"
msgstr ""
#: ../../db_management/db_premise.rst:31 ../../db_management/db_premise.rst:97
#: ../../db_management/db_premise.rst:130
#: ../../db_management/db_premise.rst:31
#: ../../db_management/db_premise.rst:110
#: ../../db_management/db_premise.rst:138
msgid "Solutions"
msgstr ""
@ -363,13 +440,11 @@ msgid "Do you have the updated version of Odoo 9?"
msgstr ""
#: ../../db_management/db_premise.rst:61
#: ../../db_management/db_premise.rst:190
#: ../../db_management/db_premise.rst:171
msgid ""
"From July 2016 onward, Odoo 9 now automatically change the uuid of a "
"duplicated database; a manual operation is no longer required."
msgstr ""
"A partír de Julio de 2016 en adelante, Odoo 0 cambiara el uuid de una base "
"dedatos duplicada automaticamente; una operación manual ya no es necesaria."
#: ../../db_management/db_premise.rst:64
msgid ""
@ -393,41 +468,60 @@ msgid ""
"invoicing proceed effortlessly for your and for us."
msgstr ""
#: ../../db_management/db_premise.rst:80
msgid "Check your network and firewall settings"
msgstr ""
#: ../../db_management/db_premise.rst:82
msgid ""
"The Update notification must be able to reach Odoo's subscription validation"
" servers. In other words, make sure that the Odoo server is able to open "
"outgoing connections towards:"
msgstr ""
#: ../../db_management/db_premise.rst:86
msgid "services.odoo.com on port 443 (or 80)"
msgstr ""
#: ../../db_management/db_premise.rst:87
msgid "services.openerp.com on port 443 (or 80) for older deployments"
msgstr ""
#: ../../db_management/db_premise.rst:89
msgid ""
"Once you activated your database, you must keep these ports open, as the "
"Update notification runs once a week."
msgstr ""
#: ../../db_management/db_premise.rst:95
msgid "Error message due to too many users"
msgstr ""
#: ../../db_management/db_premise.rst:84
#: ../../db_management/db_premise.rst:97
msgid ""
"If you have more users in your local database than provisionned in your Odoo"
" Enterprise subscription, you may encounter this message:"
msgstr ""
#: ../../db_management/db_premise.rst:93
#: ../../db_management/db_premise.rst:106
msgid ""
"When the message appears you have 30 days before the expiration. The "
"countdown is updated everyday."
msgstr ""
#: ../../db_management/db_premise.rst:99
#: ../../db_management/db_premise.rst:112
msgid ""
"**Add more users** on your subscription: follow the link and Validate the "
"upsell quotation and pay for the extra users."
msgstr ""
#: ../../db_management/db_premise.rst:102
msgid "or"
msgstr "o"
#: ../../db_management/db_premise.rst:104
#: ../../db_management/db_premise.rst:114
msgid ""
"**Deactivate users** as explained in this `Documentation "
"<https://www.odoo.com "
"/documentation/user/11.0/db_management/documentation.html#deactivating-"
"users>`__ and **Reject** the upsell quotation."
"**Deactivate users** as explained in this `documentation <documentation.html"
"#deactivating-users>`_ and **Reject** the upsell quotation."
msgstr ""
#: ../../db_management/db_premise.rst:109
#: ../../db_management/db_premise.rst:117
msgid ""
"Once your database has the correct number of users, the expiration message "
"will disappear automatically after a few days, when the next verification "
@ -436,112 +530,58 @@ msgid ""
"message disappear right away."
msgstr ""
#: ../../db_management/db_premise.rst:116
#: ../../db_management/db_premise.rst:124
msgid "Database expired error message"
msgstr ""
#: ../../db_management/db_premise.rst:118
#: ../../db_management/db_premise.rst:126
msgid ""
"If your database reaches its expiration date before your renew your "
"subscription, you will encounter this message:"
msgstr ""
#: ../../db_management/db_premise.rst:126
#: ../../db_management/db_premise.rst:134
msgid ""
"This **blocking** message appears after a non-blocking message that lasts 30"
" days. If you fail to take action before the end of the countdown, the "
"database is expired."
msgstr ""
#: ../../db_management/db_premise.rst:134
#: ../../db_management/db_premise.rst:142
msgid ""
"Renew your subscription: follow the link and renew your subscription - note "
"that"
msgstr ""
#: ../../db_management/db_premise.rst:133
#: ../../db_management/db_premise.rst:141
msgid ""
"if you wish to pay by Wire Transfer, your subscription will effectively be "
"renewed only when the payment arrives, which can take a few days. Credit "
"card payments are processed immediately."
msgstr ""
#: ../../db_management/db_premise.rst:136
#: ../../db_management/db_premise.rst:144
msgid "Contact our `Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:138
#: ../../db_management/db_premise.rst:146
msgid ""
"None of those solutions worked for you? Please contact our `Support "
"<https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:145
msgid "Force an Update Notification"
msgstr ""
#: ../../db_management/db_premise.rst:147
msgid ""
"Update Notifications happen once every 7 days and keep your database up-to-"
"date with your Odoo Enterprise subscription. If you modify your subscription"
" (i.e. add more users, renew it for a year, etc.), your local database will "
"only be made aware of the change once every 7 days - this can cause "
"discrepancies between the state of your subscription and some notifications "
"in your App Switcher. When doing such an operation on your subscription, you"
" can force an Update using the following procedure:"
msgstr ""
#: ../../db_management/db_premise.rst:154
msgid "Connect to the database with the **Administrator** account"
msgstr ""
#: ../../db_management/db_premise.rst:155
msgid ""
"Switch to the Developer mode by using the **About** option in the top-right "
"menu (in V9) / in **Settings** (in V10): click on **Activate the developer"
" mode**"
msgstr ""
#: ../../db_management/db_premise.rst:158
msgid ""
"Navigate to the \"Settings\" menu, then \"Technical\" > \"Automation\" > "
"\"Scheduled Actions\""
msgstr ""
#: ../../db_management/db_premise.rst:160
msgid ""
"Find \"Update Notification\" in the list, click on it, and finally click on "
"the button \"**RUN MANUALLY**\""
msgstr ""
#: ../../db_management/db_premise.rst:162
msgid "Refresh the page, the \"Expiration\" notification should be gone"
msgstr ""
#: ../../db_management/db_premise.rst:165
msgid ""
"You may have kept the same UUID on different databases and we receive "
"information from those databases too. So please read :ref:`this "
"documentation <duplicate_premise>` to know how to change the UUID. After the"
" change you can force a ping to speed up the verification, your production "
"database will then be correctly identified."
msgstr ""
#: ../../db_management/db_premise.rst:174
msgid "Duplicate a database"
msgstr ""
#: ../../db_management/db_premise.rst:176
#: ../../db_management/db_premise.rst:157
msgid ""
"You can duplicate your database by accessing the database manager on your "
"server (<odoo-server>/web/database/manager). In this page, you can easily "
"duplicate your database (among other things)."
msgstr ""
"Puede duplicar su base de datos ingresando a la base de datos del "
"administrador en su servidor (<odoo-server>/web/database/manager). En esta "
"página, puede fácilmente duplicar su base de datos (entre otras cosas)."
#: ../../db_management/db_premise.rst:184
#: ../../db_management/db_premise.rst:165
msgid ""
"When you duplicate a local database, it is **strongly** advised to change "
"the duplicated database's uuid (Unniversally Unique Identifier), since this "
@ -549,26 +589,15 @@ msgid ""
"databases with the same uuid could result in invoicing problems or "
"registration problems down the line."
msgstr ""
"Cuando duplique una base de datos local, se recomienda **fuertemente** "
"cambiar los uuid (Unniversally Unique Identifier) de las bases de datos "
"duplicadas, desde que el uuid es como su base de datos se identifica a si "
"misma con otros servidores. Teniendo dos bases de datos con el mismo uuid "
"podría resultar en problemas de facturación o problemas de registro bajo la "
"línea."
#: ../../db_management/db_premise.rst:193
#: ../../db_management/db_premise.rst:174
msgid ""
"The database uuid is currently accessible from the menu **Settings > "
"Technical > System Parameters**, we advise you to use a `uuid generator "
"<https://www.uuidgenerator.net>`__ or to use the unix command ``uuidgen`` to"
" generate a new uuid. You can then simply replace it like any other record "
"by clicking on it and using the edit button."
"The database uuid is currently accessible from the menu "
":menuselection:`Settings --> Technical --> System Parameters`, we advise you"
" to use a `uuid generator <https://www.uuidtools.com>`_ or to use the unix "
"command ``uuidgen`` to generate a new uuid. You can then simply replace it "
"like any other record by clicking on it and using the edit button."
msgstr ""
"El uuid de la base de datos es actualmente accesible desde el menú **Ajustes"
" > Técnicos > Parámetros del Sistema**, recomendamos usar un `generador uuid"
" <https://www.uuidgenerator.net>`__ or usar el comando unix ``uuidgen`` para"
" generar un nuevo uuid. Puede luego simplemente reemplazarlo como cualquier "
"otro registro dando clic en el y usando el botón editar."
#: ../../db_management/documentation.rst:7
msgid "Users and Features"
@ -580,9 +609,6 @@ msgid ""
"This includes the Apps you install as well as the number of users currently "
"in use."
msgstr ""
"Como administrador de tu base de datos, tu eres el responsable de su uso. "
"Esto incluye las Aplicaciones que instalas así como el número de usuarios "
"que se utilizan."
#: ../../db_management/documentation.rst:13
msgid ""
@ -592,11 +618,6 @@ msgid ""
"subscription amount significantly (or switch you from a free account to a "
"paying one on our online platform)."
msgstr ""
"Odoo son muchas cosas (ERP, CMS, aplicación CRM, comercio electrónico, etc.)"
" pero *no* un smartphone. Debe tomar precauciones al añadir/eliminar "
"características (especialmente Aplicaciones) en tu base de datos debido a "
"que esto puede impactar en el monto de la suscripción siginficativamente (o "
"cambiarte de una cuenta gratuita a una de paga en plataforma en línea)."
#: ../../db_management/documentation.rst:19
msgid ""
@ -619,112 +640,88 @@ msgid ""
"issue while carrying out these procedures, please contact us through our "
"`support form <https://www.odoo.com/help>`__."
msgstr ""
"Si tienes preguntas sobre el contenido de esta página o si encuentras un "
"problema al realizar estos procesos, por favor contactanos por el "
"`formulario de soporte <https://www.odoo.com/help>`__."
#: ../../db_management/documentation.rst:34
msgid "Deactivating Users"
msgstr "Desactivar Usuarios"
msgstr ""
#: ../../db_management/documentation.rst:36
msgid ""
"Make sure you have sufficient **administrative rights** if you want to "
"change the status of any of your users."
msgstr ""
"Asegúrese que tiene los suficientes **permisos administrativos** si quieres "
"cambiar el estatus de cualquiera de tus usuarios."
#: ../../db_management/documentation.rst:39
msgid ""
"In your Odoo instance, click on **Settings**. You will have a section "
"showing you the active users on your database. Click on **Manage access "
"rights.**"
"showing you the active users on your database. Click on **Manage Users.**"
msgstr ""
"En tu instancia de Odoo, da click en **Configuración**.Tendrás una sección "
"mostrando los usuarios activos en la base de datos. Da click en "
"**Administrar permisos de acceso.**"
#: ../../db_management/documentation.rst:44
#: ../../db_management/documentation.rst:82
#: ../../db_management/documentation.rst:43
#: ../../db_management/documentation.rst:80
msgid "|settings|"
msgstr "|ajustes|"
msgstr ""
#: ../../db_management/documentation.rst:44
#: ../../db_management/documentation.rst:43
msgid "|browse_users|"
msgstr "|buscar_usuarios|"
msgstr ""
#: ../../db_management/documentation.rst:47
#: ../../db_management/documentation.rst:46
msgid "You'll then see the list of your users."
msgstr "Luego verá la lista de sus usuarios."
msgstr ""
#: ../../db_management/documentation.rst:52
#: ../../db_management/documentation.rst:51
msgid ""
"The pre-selected filter *Internal Users* shows your paying users (different "
"from the *Portal Users* which are free). If you remove this filter, you'll "
"get all your users (the ones you pay for and the portal ones)"
msgstr ""
"El filtro pre-seleccionado *Usuarios Internos* muestra sus usuarios "
"pagadores (diferentes del *Portal de Usuarios* los cuales son gratis). Si "
"remueve este filtro, obtendrá todos sus usuarios (de los que paga y los del "
"portal)"
#: ../../db_management/documentation.rst:57
#: ../../db_management/documentation.rst:56
msgid ""
"In your list of users, click on the user you want to deactivate. As soon as "
"you are on the userform, go with your mouse cursor on the status **Active** "
"(top right). Click on Active and you will notice that the status will change"
" to **Inactive** immediately."
"you are on the userform, click on the Action drop down menu, and then click "
"on Archive."
msgstr ""
#: ../../db_management/documentation.rst:64
msgid "The user is now deactivated."
msgstr ""
"En su lista de usuarios, de clic en el usuario que quiere desactivar. Tan "
"pronto como este en el formulario del usuario, vaya con el cursor del ratón "
"al estado **Activar** (parte superior). De clic en Activar y notará que el "
"estado cambiará a **Inactivo** inmediatamente."
#: ../../db_management/documentation.rst:66
msgid "The user is now deactivated."
msgstr "El usuario ahora esta desactivado."
#: ../../db_management/documentation.rst:68
msgid "**Never** deactivate the main user (*admin*)"
msgstr "**Nunca** desactive al usuario principal (*admin*)"
msgstr ""
#: ../../db_management/documentation.rst:69
msgid "Uninstalling Apps"
msgstr ""
#: ../../db_management/documentation.rst:71
msgid "Uninstalling Apps"
msgstr "Desinstalar Aplicaciones"
#: ../../db_management/documentation.rst:73
msgid ""
"Make sure you first test what you are about to do on a :ref:`duplicate "
"<duplicate_online>` of your database before making any changes (*especially*"
" installing/uninstalling apps)."
msgstr ""
#: ../../db_management/documentation.rst:77
#: ../../db_management/documentation.rst:75
msgid ""
"In your Odoo instance click on **Settings**; in this app, you will be able "
"to see how many applications you have installed. Click on **Browse Apps** to"
" access the list of your installed applications."
msgstr ""
"En su instancia de Odoo de clic en **Ajustes**; en esta aplicación, podrá "
"ver cuántas aplicaciones ha instalado. De clic en **Buscar Aplicaciones** "
"para acceder a la lista de sus aplicaciones instaladas."
#: ../../db_management/documentation.rst:82
#: ../../db_management/documentation.rst:80
msgid "|browse_apps|"
msgstr "|buscar_aplicaciones|"
msgstr ""
#: ../../db_management/documentation.rst:85
#: ../../db_management/documentation.rst:83
msgid ""
"In your applications' dashboard, you will see all the icons of your "
"applications. Click on the application you want to uninstall. Then, on the "
"form of the application, click on **Uninstall**."
msgstr ""
"En su tablero de aplicaciones, verá todos los ícones de sus aplicaciones. De"
" clic en la aplicación que quiere desinstalar. Luego, en el formulario de la"
" aplicación, de clic en **Desinstalar**."
#: ../../db_management/documentation.rst:92
#: ../../db_management/documentation.rst:90
msgid ""
"Some applications have dependencies, like Invoicing, eCommerce, etc. "
"Therefore, the system will give you a warning message to advise you of what "
@ -733,29 +730,21 @@ msgid ""
"permanently disappear). If you are sure you still want to uninstall it, then"
" click **Confirm**."
msgstr ""
"Algunas aplicaciones tienen dependencias, como facturación, comercio "
"electrónico, etc. Por lo tanto, el sistema le dará un mensaje de alerta para"
" advertirle de lo que esta a punto de ser removido. Si desinstala su "
"aplicación, todas sus dependencias también serán desinstaladas (y la "
"información en ellas desaparecerá permanentemente). Si esta seguro que igual"
" quiere desinstalarla, de clic en **Confirmar**."
#: ../../db_management/documentation.rst:99
#: ../../db_management/documentation.rst:97
msgid ""
"Last, after having checked the warning message (if any), click **Confirm**."
msgstr ""
"Por último, después de haber revisado el mensaje de alerta (si hay), de clic"
" en **Confirmar**"
#: ../../db_management/documentation.rst:104
#: ../../db_management/documentation.rst:102
msgid "You have finished uninstalling your application."
msgstr "Ha terminado de desinstalar su aplicación."
msgstr ""
#: ../../db_management/documentation.rst:105
msgid "Good to know"
msgstr ""
#: ../../db_management/documentation.rst:107
msgid "Good to know"
msgstr "Bueno saber"
#: ../../db_management/documentation.rst:109
msgid ""
"**Uninstalling apps, managing users, etc. is up to you**: no one else can "
"know if your business flow is broken better than you. If we were to "
@ -764,14 +753,8 @@ msgid ""
"*do not know how you work* and therefore cannot validate these kinds of "
"operations."
msgstr ""
"**Desinstalar aplicaciones, administrar usuarios, etc. es su decisión**: "
"nadie mejor que Ud. puede saber si el flujo de su negocio esta roto. Si "
"nosotros desinstalaramos aplicaciones por Ud, nunca podríamos decir si "
"información importante ha sido removida o si uno de los flujos de su negocio"
" se rompió porque nosotros *no sabemos como Ud. trabaja* y por lo tanto, no "
"podemos validar estos tipos de operaciones."
#: ../../db_management/documentation.rst:115
#: ../../db_management/documentation.rst:113
msgid ""
"**Odoo Apps have dependencies**: this means that you may need to install "
"modules that you do not actively use to access some features of Odoo you "
@ -780,21 +763,10 @@ msgid ""
"need or use the Website itself, it is needed for the Online Quotes feature "
"to work properly."
msgstr ""
"**Las aplicaciones de Odoo tienen dependencias**: esto significa que puede "
"necesitar instalar módulos que no usa activamente para acceder a algunas "
"funciones de Odoo que podría necesitar. Por ejemplo, se requiere de la "
"aplicación Constructor de Página Web para poder mostrar a su cliente sus "
"Cotizaciones en una página web. Aún así podría no necesitar o usar la Página"
" Web en si misma, si es necesaria para la función de Cotizaciones En Línea "
"para trabajar apropiadamente."
#: ../../db_management/documentation.rst:122
#: ../../db_management/documentation.rst:120
msgid ""
"**Always test app installation/removal on a duplicate** (or on a free trial "
"database): that way you can know what other apps may be required, etc. This "
"will avoid surprises when uninstalling or when receiving your invoices."
msgstr ""
"**Siempre pruebe la instalación/eliminación de aplicaciones en un "
"duplicado** (o en una base de datos de prueba gratis): de esta forma puede "
"saber que otras aplicaciones pueden ser requeridas, etc. Esto evitará "
"sorpresas cuando desinstale o cuando reciba sus facturas."

889
locale/es/LC_MESSAGES/discuss.po
View File

File diff suppressed because it is too large Load Diff

860
locale/es/LC_MESSAGES/ecommerce.po
View File

File diff suppressed because it is too large Load Diff

284
locale/es/LC_MESSAGES/email_marketing.po Normal file
View File

@ -0,0 +1,284 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: es\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../email_marketing.rst:5
msgid "Email Marketing"
msgstr ""
#: ../../email_marketing/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:3
msgid "Work with Mailing Lists"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:5
msgid ""
"Mailing lists can be a goldmine for your company’s marketing department as "
"they can provide leads for sales, focus groups for testing new products, and"
" consumers to provide feedback on satisfaction, for example."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:10
msgid "Create mailing lists"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:12
msgid ""
"Go to :menuselection:`Mailing lists --> Mailing lists --> Create`. Enable "
"the option *Is Public* to make the list visible for users when "
"unsubscribing."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:19
msgid ""
"Once your mailing list is created, you can manually add contacts clicking on"
" *Create*. *Import* a list of contacts if you have it from a previous tool."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:23
msgid "Linking a mailing list to my website"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:26
msgid ""
"Create a mailing list called Newsletter, as you use this strategy to "
"advertise and communicate new ideas to subscribers interested in listening."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:27
msgid ""
"Go to your *Website*, add a *Newsletter* block and choose the respective "
"mailing list."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:34
msgid "Contacts"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:36
msgid ""
"Under :menuselection:`Mailing Lists --> Mailing List Contacts` see a list of"
" all contacts under all your mailing lists, and the ones you individually "
"created here."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:43
msgid ""
"Open a contact form to see or add different mailing lists to which the "
"contact is or will be part of."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:51
#: ../../email_marketing/overview/manage_unsubscriptions.rst:46
msgid ":doc:`send_emails`"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:3
msgid "Manage Unsubscriptions and Blacklist"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:5
msgid ""
"It is best practice, and legally required, to allow recipients to "
"unsubscribe from mailing lists as you do not want your audience to think "
"that your company is using any tactics that are dishonest or spammy."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:10
msgid "Enable the Blacklist feature"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:12
msgid ""
"Go to :menuselection:`Configuration --> Settings` and enable the option "
"*Blacklist Option when Unsubscribing*."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:19
msgid ""
"Now, once the user clicks on the *Unsubscribe* link on your email, he is "
"redirected to the following page:"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:28
msgid ""
"After clicking on the unsubscribe button when using the test feature, you "
"are sent to an error page (*error 403 - Access Denied*). If you want to be "
"sure the link is working properly, create your mass mail and send it only to"
" a personal email."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:32
msgid ""
"In addition to having the option of unsubscribing from specific mailing "
"lists, the user can also blacklist himself, meaning that he will not receive"
" *any* more emails from you."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:36
msgid ""
"The mailing list has to be configured as *Public* in order to be visible for"
" users."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:38
msgid ""
"Under :menuselection:`Configuration --> Blacklist`, blacklisted email "
"addresses are shown."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:39
msgid ""
"When opening the record, as a *Log note*, a description-history is kept."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:47
msgid ":doc:`mailing_lists`"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:3
msgid "Send Emails Marketing and Manage Campaigns"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:5
msgid ""
"Emails allow you to effectively, and at a low cost, reach a large number of "
"consumers while being able to customize your message in a way that resonates"
" with them. It is measurable, and a call-to-action oriented channel."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:10
msgid "Choose the right target and create the message"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:12
msgid "Go to :menuselection:`Mailings --> Create`."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:14
msgid ""
"Choosing *Contacts* as *Recipients* (for example), allows you to add "
"specifications to match just certain contacts, filtering your target."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:21
msgid ""
"With a trial databases, you have a limit of 50 emails per day; on Odoo SH "
"Cloud Platform the limit is 200. There is a possibility to increase these "
"numbers by contacting Odoo Support. To contact Support, `click here "
"<https://www.odoo.com/help>`_."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:25
msgid ""
"Under *Mail Body*, choose a layout and make the modifications needed by "
"dragging, dropping and double-clicking on content. Note that it is possible "
"to start from scratch selecting the *blank* template option."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:34
msgid ""
"Under *Settings*, you can assign someone else as the responsible sender if "
"you do not want it to be you. To do so, change the email address used as the"
" sender (*Send From*)."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:37
msgid ""
"With the *Reply To* radio button, you can also choose to gather answers "
"either on the respective recipients’ records or on a specific email address."
" Note that this option is not available if you target mailing contacts or "
"contacts as recipients."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:45
msgid "Test, send or schedule a mailing"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:53
msgid ""
"*Save*: the work is allocated in the *draft* column in the Kanban view. "
"Modifications can be made while being in this stage. The option *Discard* "
"deletes the email."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:54
msgid ""
"Click on *Test* and send your message to one, or even multiple, test "
"contacts to avoid errors."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:56
msgid ""
"*Send* triggers the email with the next run and put the work on the *queue* "
"column in the Kanban view."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:58
msgid ""
"*Schedule* allows you to choose a date and time, and puts the email in the "
"*queue* column in the Kanban view."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:61
msgid ""
"The daily limit is applied for **all emails** sent, in other words, "
"throughout all applications. Therefore, if at the end of the day you have "
"remaining ones to be sent, note that they *will not* be sent automatically "
"the next day. You need to force that by opening the email and clicking on "
"*Retry*."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:67
msgid "Manage campaigns"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:69
msgid ""
"Go to :menuselection:`Configuration --> Settings` and enable *Mailing "
"Campaigns*."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:71
msgid ""
"The campaign option is effective as it allows you to organize your marketing"
" efforts and have a centralized view of its metrics."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:72
msgid "Go to *Campaign* and click on *Create* to start one."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:80
msgid ""
"If you use the SMS and Social Marketing applications, as well as the Push "
"Notification feature, you see the option to create content for those "
"channels. You also see the *Campaign* menu within those applications. All of"
" this is possible because the applications work integrated."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:85
msgid ":doc:`../../discuss/advanced/email_servers`"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:86
msgid ":doc:`../../social_marketing/overview/campaigns`"
msgstr ""

433
locale/es/LC_MESSAGES/events.po Normal file
View File

@ -0,0 +1,433 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Althay Ramallo Fuentes <arf@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Last-Translator: Althay Ramallo Fuentes <arf@odoo.com>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: es\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../events.rst:5
msgid "Events"
msgstr "Eventos"
#: ../../events/integrations.rst:3
msgid "Integrations"
msgstr "Integraciones"
#: ../../events/integrations/integration_sms.rst:3
msgid "Communicating about my Event using SMS Text Messages"
msgstr ""
#: ../../events/integrations/integration_sms.rst:5
msgid ""
"Using SMS as a communication strategy for your event establishes interaction"
" between organizers, attendees, speakers and further targets. It allows your"
" message to be heard whether the goal is to send out reminders, teasers or "
"to advertise."
msgstr ""
#: ../../events/integrations/integration_sms.rst:10
#: ../../events/overview/tickets.rst:9 ../../events/overview/track_talks.rst:9
msgid "Configuration"
msgstr "Configuración"
#: ../../events/integrations/integration_sms.rst:13
msgid ""
"Under *Communication* SMS is a standard feature. That means nothing needs to"
" be enabled or installed."
msgstr ""
#: ../../events/integrations/integration_sms.rst:16
msgid ""
"On the other hand, to contact the speakers of your event, you need the *SMS "
"Marketing* application installed, and to enable *Schedule & Tracks* under "
":menuselection:`Events --> Configuration --> Settings`."
msgstr ""
#: ../../events/integrations/integration_sms.rst:23
msgid ""
"The *Schedule & Tracks* feature allows you to manage the agenda and speakers"
" of your event. For more details watch: `Creating an agenda for your event "
"<https://www.odoo.com/slides/slide/create-an-agenda-for-your-"
"event-717?fullscreen=1>`_."
msgstr ""
#: ../../events/integrations/integration_sms.rst:28
msgid "Send SMSs to attendees"
msgstr "Enviar SMS a asistentes"
#: ../../events/integrations/integration_sms.rst:30
msgid ""
"Under *Communication*, the message’s target is the attendees of your event."
msgstr ""
#: ../../events/integrations/integration_sms.rst:32
msgid ""
"You can choose to confirm each registration with the *Registration* "
"template, and to send a reminder shortly before the event takes place with "
"the *Reminder* template."
msgstr ""
#: ../../events/integrations/integration_sms.rst:38
msgid "To make changes in an existing template, click on the external link."
msgstr ""
#: ../../events/integrations/integration_sms.rst:45
msgid "Send SMSs to speakers and further targets"
msgstr ""
#: ../../events/integrations/integration_sms.rst:47
msgid ""
"The benefit of the integration with the *SMS Marketing* application is that "
"you can choose the target you would like your message to be delivered to. To"
" get started, click on *Contact Track Speakers*."
msgstr ""
#: ../../events/integrations/integration_sms.rst:56
msgid ""
"If *Event Track* is not your target (*Recipient*), choose the right one. "
"*Filters* are eligible here."
msgstr ""
#: ../../events/integrations/integration_sms.rst:58
msgid ""
"In the example below, the SMS would be sent to the speakers who are in the "
"stage *Proposal* on *Event Track*."
msgstr ""
#: ../../events/integrations/integration_sms.rst:65
msgid ""
"Credits are required to be able to send SMSs. For more information about "
"Pricing :doc:`click here <../../sms_marketing/pricing/pricing_and_faq>`, "
"and, about IAP Services :doc:`here "
"<../../general/in_app_purchase/in_app_purchase>`."
msgstr ""
#: ../../events/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../events/overview/create_event.rst:3
msgid "Create your First Event"
msgstr "Crea tu primer evento"
#: ../../events/overview/create_event.rst:5
msgid "Some of the reasons why hosting events is essential are:"
msgstr ""
#: ../../events/overview/create_event.rst:7
msgid "To create an engaging experience with your audience;"
msgstr ""
#: ../../events/overview/create_event.rst:8
msgid "To generate word of mouth about your company;"
msgstr ""
#: ../../events/overview/create_event.rst:9
msgid "To allow networking;"
msgstr ""
#: ../../events/overview/create_event.rst:10
msgid ""
"To provide an opportunity for sales representatives to walk their prospects "
"through the product and even their pipeline."
msgstr ""
#: ../../events/overview/create_event.rst:14
msgid "Get started"
msgstr "Empezar"
#: ../../events/overview/create_event.rst:16
msgid ""
"Under the menu *Events*, have a view of all existing events and some key "
"information, such as the number of expected and confirmed attendees."
msgstr ""
#: ../../events/overview/create_event.rst:23
msgid ""
"To start a new one, click on *Create* and fill in the form with all the "
"needed information. Enable *Website Menu* to have the menus *Introduction*, "
"*Location*, and *Register* being shown on your event’s website page."
msgstr ""
#: ../../events/overview/create_event.rst:31
msgid ""
"To personalize these pages, click on *Edit* to open the `website builder "
"<https://www.odoo.com/slides/slide/website-basics-643?fullscreen=1>`_, and "
"edit content by dragging and dropping blocks."
msgstr ""
#: ../../events/overview/create_event.rst:40
msgid "Tab: Tickets"
msgstr ""
#: ../../events/overview/create_event.rst:43
msgid ""
"Go to :menuselection:`Events --> Configuration --> Settings` and enable "
":doc:`Tickets and Online Ticketing <tickets>`."
msgstr ""
#: ../../events/overview/create_event.rst:46
msgid ""
"Now, under the *Tickets* Tab, add lines to include the different ticket "
"types you offer. Include the price, the start and end dates for "
"registrations, and even the maximum number of tickets that can be sold."
msgstr ""
#: ../../events/overview/create_event.rst:48
msgid ""
"The *Reserved Seats* and *Unconfirmed Seat Reservations* are counted as "
"attendees are marked as :doc:`confirmed <track_attendees>` or not."
msgstr ""
#: ../../events/overview/create_event.rst:55
msgid "Tab: Communication"
msgstr ""
#: ../../events/overview/create_event.rst:58
msgid ""
"Choose the email and/or SMS message template, as well as the frequency with "
"which you would like to communicate with your attendees under the tab "
"*Communication*."
msgstr ""
#: ../../events/overview/create_event.rst:61
msgid ""
"Create a template on the fly or choose an existing one. Define the "
"*Interval* (2, 7, 15..) for the *Unit* (days, hours, weeks, etc.), and the "
"*Trigger* action (after registration, after the event, etc.)."
msgstr ""
#: ../../events/overview/create_event.rst:68
msgid "Tab: Questions"
msgstr ""
#: ../../events/overview/create_event.rst:70
msgid ""
"Go to :menuselection:`Configuration --> Settings` and enable *Questions*."
msgstr ""
#: ../../events/overview/create_event.rst:72
msgid ""
"Now, under the tab *Questions*, edit your questions and answers, choosing if"
" you would like your questionnaire to be asked per order or per "
"registration."
msgstr ""
#: ../../events/overview/create_event.rst:75
msgid ""
"Example of a registration for 3 attendees: if enabling the option *Ask each "
"attendee*, the questionnaire is shown 3 times, meaning that answers can vary"
" for each attendee; if *Ask each attendee* is not enabled, the questionnaire"
" is shown once, resulting in a global answer."
msgstr ""
#: ../../events/overview/create_event.rst:81
msgid ""
"Once your event is *Confirmed*, you can manage attendees badges, and mark "
"the event as *Finished*. Events marked as *Finished* can be *Set to draft*, "
"putting the event back to an *Unconfirmed* stage from which it can be edited"
" and used again."
msgstr ""
#: ../../events/overview/create_event.rst:90
msgid "Publish your event"
msgstr ""
#: ../../events/overview/create_event.rst:92
msgid "*Go to Website* and turn *Published* on."
msgstr ""
#: ../../events/overview/create_event.rst:99
msgid ":doc:`track_attendees`"
msgstr ""
#: ../../events/overview/create_event.rst:100
#: ../../events/overview/track_attendees.rst:45
msgid ":doc:`tickets`"
msgstr ""
#: ../../events/overview/create_event.rst:101
#: ../../events/overview/track_attendees.rst:46
msgid ":doc:`track_talks`"
msgstr ""
#: ../../events/overview/tickets.rst:3
msgid "Selling Tickets"
msgstr ""
#: ../../events/overview/tickets.rst:5
msgid ""
"If you automate processes, you save time. If you give attendees multiple "
"payment options to choose from, you allow flexibility and open margins for "
"more registrations to happen."
msgstr ""
#: ../../events/overview/tickets.rst:11
msgid ""
"Go to :menuselection:`Configuration --> Settings` and activate *Tickets* and"
" *Online Ticketing*."
msgstr ""
#: ../../events/overview/tickets.rst:13
msgid ""
"*Tickets* allow tickets to be sold "
":ref:`events/create_event/through_sales_orders`. *Online Ticketing* allows "
"the sale of tickets to happen "
":ref:`events/create_event/through_the_website`."
msgstr ""
#: ../../events/overview/tickets.rst:22
msgid "Through Sales Orders"
msgstr ""
#: ../../events/overview/tickets.rst:24
msgid ""
"On the *Sales* application, choose the event product you created and add it "
"as a product line. A window pops-up, allowing you to choose the event for "
"which you want to create the sales order."
msgstr ""
#: ../../events/overview/tickets.rst:32
msgid ""
"Remember to create a product form for the event registration, under "
"*Product*, in the *Sales* application, and to add that same product under "
"your event’s form."
msgstr ""
#: ../../events/overview/tickets.rst:43
msgid "Through the Website"
msgstr ""
#: ../../events/overview/tickets.rst:45
msgid ""
"On the website, once tickets are added to the cart, the user can continue "
"the transaction choosing among the payment methods you chose to have "
"available."
msgstr ""
#: ../../events/overview/tickets.rst:53
msgid ":doc:`../../general/payment_acquirers/payment_acquirers`"
msgstr ""
#: ../../events/overview/track_attendees.rst:3
msgid "Track your Attendees"
msgstr ""
#: ../../events/overview/track_attendees.rst:5
msgid ""
"Attendees are at the heart of your event. Keeping track of their number and "
"managing their registration and attendance is necessary for planning and "
"analyzing reasons."
msgstr ""
#: ../../events/overview/track_attendees.rst:9
msgid "Attendees list and attendance"
msgstr ""
#: ../../events/overview/track_attendees.rst:11
msgid ""
"Once attendees have registered or bought their tickets, they are added to "
"the *Attendees* list."
msgstr ""
#: ../../events/overview/track_attendees.rst:12
msgid ""
"Tickets sold through sales orders validate attendees as soon as the "
"quotation is confirmed."
msgstr ""
#: ../../events/overview/track_attendees.rst:18
msgid ""
"The check mark button is used to confirm the registration. Once a "
"registration is confirmed, attendance can be marked."
msgstr ""
#: ../../events/overview/track_attendees.rst:26
msgid "Bagdes and cancellations"
msgstr ""
#: ../../events/overview/track_attendees.rst:28
msgid ""
"On the attendees form, choose to send badges manually by clicking on *Send "
"By Email*. *Cancel Registration* to have that attendee being moved to the "
"*Cancelled* stage."
msgstr ""
#: ../../events/overview/track_attendees.rst:36
msgid ""
"To see a list of your canceled attendees, under *Filters*, add a *Custom "
"Filter* choosing *Status > is > Cancelled*."
msgstr ""
#: ../../events/overview/track_attendees.rst:44
#: ../../events/overview/track_talks.rst:49
msgid ":doc:`../integrations/integration_sms`"
msgstr ""
#: ../../events/overview/track_talks.rst:3
msgid "Track and Manage Talks"
msgstr ""
#: ../../events/overview/track_talks.rst:5
msgid ""
"Allow partners to submit talk proposals so they can share their knowledge "
"and expertise. Good speakers and talks are what make your event great."
msgstr ""
#: ../../events/overview/track_talks.rst:11
msgid ""
"Go to :menuselection:`Events --> Configuration --> Settings` and enable "
"*Schedule & Tracks*."
msgstr ""
#: ../../events/overview/track_talks.rst:14
msgid ""
"Now, in your event's form, once *Website menu* is enabled, the options "
"*Tracks on Website* and *Track Proposals on Website* become available. "
"Enabling them adds the menus *Talks*, *Talk Proposals*, and *Agenda* to your"
" website."
msgstr ""
#: ../../events/overview/track_talks.rst:20
msgid ""
"Besides having the ability to suggest their own talks, the website now "
"allows users to see a list of the whole agenda and scheduled talks."
msgstr ""
#: ../../events/overview/track_talks.rst:28
msgid ""
"To handle tracks internally and not have the menus *Talks*, *Talk "
"Proposals*, and *Agenda* online, use the menu *Tracks* individually."
msgstr ""
#: ../../events/overview/track_talks.rst:32
msgid "Publishing speaker proposals"
msgstr ""
#: ../../events/overview/track_talks.rst:34
msgid ""
"Once partners have filled in the appropriate form and submitted their "
"proposals, a new *Proposal* is instantly created under the menu *Track*."
msgstr ""
#: ../../events/overview/track_talks.rst:41
msgid ""
"If the proposal is accepted and can go online, simply open its form and "
"click on *Go to Website*. From the website page, turn *Published* on."
msgstr ""

350
locale/es/LC_MESSAGES/expense.po Normal file
View File

@ -0,0 +1,350 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Althay Ramallo Fuentes <arf@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Last-Translator: Althay Ramallo Fuentes <arf@odoo.com>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: es\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../expense/expense.rst:5
msgid "Expenses"
msgstr "Gastos"
#: ../../expense/expense.rst:8
msgid "How to set expense types"
msgstr ""
"Como configurar tipos de gasto\n"
" "
#: ../../expense/expense.rst:9
msgid ""
"The first step to track expenses is to configure the expense types (managed "
"as products in Odoo) that your company allows, from the *Configuration* "
"menu. When a specific expense is reimbursed at a fixed price, set a cost on "
"the product. Otherwise keep the cost at 0.0 and employees will report the "
"real cost per expense."
msgstr ""
#: ../../expense/expense.rst:17
msgid "Here are some examples to configure:"
msgstr "Estos son algunos de los ejemplos para configurar:"
#: ../../expense/expense.rst:19
msgid "Restaurant:"
msgstr ""
"Restaurante\n"
" "
#: ../../expense/expense.rst:21 ../../expense/expense.rst:27
msgid "Cost: 0.00 (the cost of the ticket will be recorded on every expense)"
msgstr ""
#: ../../expense/expense.rst:22
msgid "Travel with Personal Car:"
msgstr ""
#: ../../expense/expense.rst:24
msgid "Cost: 0.30 (the price per mile reimbursed by the company is fixed)"
msgstr ""
#: ../../expense/expense.rst:25
msgid "Hotel:"
msgstr "Hotel:"
#: ../../expense/expense.rst:29
msgid "Others:"
msgstr ""
#: ../../expense/expense.rst:31
msgid "Cost: 0.0"
msgstr "Coste: 0.0"
#: ../../expense/expense.rst:33
msgid ""
"Don't forget to set an expense tax on each expense type (and an account if "
"you use Odoo Accounting). It's usually a good practice to use a tax that is "
"configured with :ref:`Tax Included in Price <taxes/included-in-price>`. That"
" way, employees report expenses with prices including taxes, which is "
"usually the expected behaviour."
msgstr ""
#: ../../expense/expense.rst:41
msgid ""
"The *Sales* app allows you to specify unit of measures for your expense "
"types (units, miles, nights, etc.). Go to :menuselection:`Sales --> "
"Configuration --> Settings` and check *Some products may be sold/purchased "
"in different units of measure (advanced)*."
msgstr ""
#: ../../expense/expense.rst:48
msgid "How to record expenses"
msgstr "Cómo registrar gastos"
#: ../../expense/expense.rst:51
msgid "Manually"
msgstr ""
"Manualmente\n"
" "
#: ../../expense/expense.rst:53
msgid ""
"As an employee (Employee in user access rights), you can record expenses "
"from :menuselection:`My Expenses --> Expenses to Submit`."
msgstr ""
#: ../../expense/expense.rst:59
msgid ""
"Select the related product and enter either the total amount you paid (with "
"Quantity = 1) or the unit price if Quantity is countable (e.g. number of "
"hotel nights)."
msgstr ""
#: ../../expense/expense.rst:62
msgid "Enter the expense date."
msgstr "Introduce la fecha del gasto"
#: ../../expense/expense.rst:63
msgid ""
"Choose if you paid the bill on your own (and expect to be reimbursed) or if "
"the company paid directly (e.g. if you used a company's credit card)."
msgstr ""
#: ../../expense/expense.rst:65
msgid ""
"Set the bill reference, add some notes if requested and attach a photo/scan "
"of the receipt from the discussion thread. That will help the manager and "
"the accountant validate it."
msgstr ""
#: ../../expense/expense.rst:73
msgid "In one click from emails"
msgstr "Correos en un solo clic"
#: ../../expense/expense.rst:74
msgid ""
"Let your employees record their expenses from a simple email. Make a "
"snapshot of the receipt and send it by email, or simply forward a bill!"
msgstr ""
#: ../../expense/expense.rst:77
msgid ""
"The only thing to do is setting up an email alias in "
":menuselection:`Expenses --> Configuration --> Settings` (e.g. *expenses* "
"@mycompany.odoo.com). For security purposes, only authenticated employee "
"emails (cfr. *Work Email* in employee detail form) are accepted."
msgstr ""
#: ../../expense/expense.rst:83
msgid ""
"The expense product is set automatically if the mail subject contains the "
"product's internal reference in first position. Type the expense amount in "
"the mail subject to set it on the expense too (e.g. Ref001 Food 100€)."
msgstr ""
#: ../../expense/expense.rst:88
msgid "How to submit expenses to managers"
msgstr "Cómo enviar gastos a los responsables"
#: ../../expense/expense.rst:90
msgid ""
"When you are ready to submit your expenses to your manager (e.g. at the end "
"of a business trip, or once a month), go to the menu :menuselection:`My "
"Expenses --> Expenses to Submit`. Select all expenses from the list view and"
" click on :menuselection:`Action --> Submit to Manager`. Save the newly "
"created expense report (i.e. set of expenses), and wait for your manager to "
"approve it."
msgstr ""
#: ../../expense/expense.rst:100
msgid ""
"You can also submit expenses one by one from the *Submit to Manager* button "
"on the form view of an expense."
msgstr ""
#: ../../expense/expense.rst:103
msgid ""
"All your submitted expense reports can be found in :menuselection:`Expenses "
"--> My Expenses --> Expense Reports`."
msgstr ""
#: ../../expense/expense.rst:108
msgid "How to approve expenses"
msgstr "Cómo aprobar gastos"
#: ../../expense/expense.rst:110
msgid ""
"HR and team managers get an overview of all expense reports to validate from"
" the top menu :menuselection:`To Approve --> Expense Reports to Approve`. "
"Such users must have at least *Officers* access rights for *Expenses*."
msgstr ""
#: ../../expense/expense.rst:117
msgid ""
"They can review expense reports, approve or reject them, as well as "
"providing feedback thanks to the integrated communication tool."
msgstr ""
#: ../../expense/expense.rst:123
msgid ""
"As a team manager you can easily find the expense reports of your team "
"members. You need to be set as manager in the detail form of those "
"employees."
msgstr ""
#: ../../expense/expense.rst:131
msgid "How to post expenses in accounting"
msgstr ""
#: ../../expense/expense.rst:133
msgid ""
"Once expense reports approved by managers, the accounting department goes to"
" :menuselection:`Expenses --> Accountant --> Expense Reports To Post` to "
"check accounts, products and taxes. They can click *Post Journal Entries* to"
" post related journal entries into your books. To do so, the user must have "
"following access rights:"
msgstr ""
#: ../../expense/expense.rst:139
msgid "Accounting: Accountant or Adviser"
msgstr ""
#: ../../expense/expense.rst:140
msgid "Expenses: Manager"
msgstr "Gastos: Responsable"
#: ../../expense/expense.rst:143
msgid ""
"To post an expense, a *Home Address* must be set on the employee. If you get"
" a related blocking message when posting, click the employee, go to "
"*Personal Information* tab and select/create the contact of your employee in"
" the address book. A contact has been automatically created if this person "
"is using Odoo."
msgstr ""
#: ../../expense/expense.rst:150
msgid "How to reimburse employees"
msgstr "Cómo reembolsar a los empleados"
#: ../../expense/expense.rst:152
msgid ""
"You can now see all the expense reports to reimburse in "
":menuselection:`Expenses --> Accountant --> Expense Reports To Pay`. To "
"record the payment or pay by check, click *Register a Payment*."
msgstr ""
#: ../../expense/expense.rst:156
msgid "See how you can easily manage the payment process in Odoo:"
msgstr ""
#: ../../expense/expense.rst:158
msgid ":doc:`../accounting/payables/pay/check`"
msgstr ""
#: ../../expense/expense.rst:159
msgid ":doc:`../accounting/payables/pay/sepa`"
msgstr ""
#: ../../expense/expense.rst:163
msgid "How to re-invoice expenses to your customers"
msgstr "¿Cómo volver a facturar gastos a sus clientes?"
#: ../../expense/expense.rst:165
msgid ""
"If you track expenses on customer projects, you can charge them back to your"
" customers automatically."
msgstr ""
#: ../../expense/expense.rst:169
msgid "Setup"
msgstr "Configurar"
#: ../../expense/expense.rst:171
msgid "Enable **Customer Billing** in the Expenses settings"
msgstr ""
#: ../../expense/expense.rst:173
msgid ""
"Go to the product configuration menu and set the invoicing method on all "
"your Expense types:"
msgstr ""
#: ../../expense/expense.rst:176
msgid ""
"Ordered quantities : it will invoice expenses based on the ordered quantity"
msgstr ""
#: ../../expense/expense.rst:179
msgid ""
"Delivered quantities :it will invoice expenses based on the expenses "
"quantity"
msgstr ""
#: ../../expense/expense.rst:182
msgid "At cost: will invoice expenses at their real cost."
msgstr ""
#: ../../expense/expense.rst:184
msgid ""
"At sales price: will invoice based on a fixed sales price set on the sale "
"order."
msgstr ""
#: ../../expense/expense.rst:191
msgid "Create an order"
msgstr ""
#: ../../expense/expense.rst:193
msgid ""
"As a salesman, create and confirm a Sales Order for the services delivered "
"to your customer. If you don't put any expense in the order, it will be "
"added automatically once posted by the accountant."
msgstr ""
#: ../../expense/expense.rst:198
msgid "Link the expense to the Sale Order."
msgstr ""
#: ../../expense/expense.rst:204
msgid "Submit, validate and post expenses"
msgstr ""
#: ../../expense/expense.rst:206
msgid ""
"As a manager, make sure the analytic account is set on every expense line on"
" approving expenses reports. Click the line to add one if missing. Employees"
" are already able to set one when submitting."
msgstr ""
#: ../../expense/expense.rst:213
msgid "As an accountant, post journal entries."
msgstr ""
#: ../../expense/expense.rst:216
msgid "Invoice expenses"
msgstr ""
#: ../../expense/expense.rst:218
msgid ""
"Now you can invoice the order. It shows up in :menuselection:`Sales --> "
"Invoicing --> Sales` to Invoice. The expenses have been added automatically "
"in the order lines. Such items show up in blue (i.e. to invoice)."
msgstr ""
#: ../../expense/expense.rst:226
msgid "e (i.e. to invoice)."
msgstr ""

386
locale/es/LC_MESSAGES/fsm.po Normal file
View File

@ -0,0 +1,386 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: es\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../fsm.rst:5
msgid "Field Service"
msgstr ""
#: ../../fsm/helpdesk.rst:3
msgid "Helpdesk"
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:3
msgid "Plan Onsite Interventions from Helpdesk Tickets"
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:4
msgid ""
"The integration with the Helpdesk application lets your helpdesk team manage"
" interventions requests directly. It speeds up processes as you can plan "
"field services tasks from tickets."
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:8
#: ../../fsm/sales/create_quotations.rst:8
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:9
#: ../../fsm/worksheets/customize_worksheets.rst:9
msgid "Enable the feature"
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:9
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams --> "
"Edit` and enable :menuselection:`Onsite Interventions --> Save`."
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:17
msgid ""
"Now once your helpdesk team needs, they have the option to *Plan "
"Intervention* from tickets."
msgstr ""
#: ../../fsm/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:3
msgid "Invoicing Time and Material to Customers"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:4
msgid ""
"Track the exact time spent on a task and give customers the ability to sign "
"their worksheet report onsite. Invoice customers as soon as the work is "
"complete, leaving you, and the customer, with the confidence that they will "
"be charged for the exact right hours and material used."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:9
msgid "Get the exact time spent on a task"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:10
msgid ""
"Click on *Start* to launch the timer. You can *Pause* at any moment and "
"*Resume* when you would like to continue."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:17
msgid ""
"Click on *Stop* once the work is done to confirm the total time spent and "
"add a description."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:24
msgid "Sign and send reports & validate stock-picking"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:25
msgid ""
"Now, fill your *Worksheet* and add the used products clicking on *Products*."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:31
msgid ""
"Click on *Start* if you need to record additional time for the same "
"activity. The time recorded will be added to the already created and signed "
"worksheet. Then, create a new invoice for the time added."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:34
msgid ""
"*Mark as done* to close the task and to invoice your intervention. It also "
"validates the stock-picking keeping your inventory up-to-date."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:37
msgid ""
"*Sign Report* generates a detailed worksheet report for the customer to "
"sign. Send it through email clicking on *Send Report*."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:41
msgid "Invoice your time and material"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:42
msgid ""
"Under :menuselection:`All Tasks --> To Invoice`, find a list of all tasks "
"marked as done but that have not been invoiced. Convenient feature as it "
"allows accountants to easily access all finished tasks at once."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:52
msgid ""
"Invoice all tasks at once selecting them all and going to "
":menuselection:`Action --> Create Invoice`."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:60
msgid ":doc:`../../project/advanced/feedback`"
msgstr ""
#: ../../fsm/overview/keep_track.rst:3
msgid "Keeping Track of Stock"
msgstr ""
#: ../../fsm/overview/keep_track.rst:4
msgid ""
"The integration with the Inventory application makes possible to track the "
"material used and automatically keep your stock up to date."
msgstr ""
#: ../../fsm/overview/keep_track.rst:8
msgid "Set up your Field Service project"
msgstr ""
#: ../../fsm/overview/keep_track.rst:9
msgid ""
"Go to :menuselection:`Field Service --> Configuration --> Projects` and make"
" sure the option *Products on Tasks* is enabled."
msgstr ""
#: ../../fsm/overview/keep_track.rst:15
msgid ""
"Now, add the materials used in the intervention to the worksheet, and once "
"the task is *Marked as done*, the stock-picking is automatically validated "
"and the inventory evaluation is automatically updated."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:3
msgid "Manage your Employees’ Schedules and Time Off"
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:4
msgid ""
"The integration with the *Time off* application allows you to quickly see "
"your employees’ availabilities. It will avoid conflicts and errors between "
"employees schedules and interventions."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:8
msgid "Effortlessly see employees’ time off"
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:9
msgid ""
"No configuration needs to be done. Once the employees’ time has been "
"validated in the *Time off* application, cells will be grayed for those days"
" in your Gantt view."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:13
msgid ""
"It also adapts to the working calendar of the employee. Example: the "
"employee works part-time (from Monday to Wednesday). So, Thursday and Friday"
" will also be greyed, in addition to the weekends."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:20
msgid "Easily manage employees’ schedules"
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:21
msgid ""
"From the Gantt view (under *Planning by User, Project or Worksheet*), click "
"on the plus sign to add a new task or on the magnifying glass to plan an "
"existing one."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:29
msgid "Unassigned tasks"
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:30
msgid ""
"If you need to plan an intervention but you do not know yet who will take "
"care of it, you can leave the task unassigned. It will still be shown in the"
" Gantt view. Simply drag and drop the responsible person he can be assigned."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:39
msgid ""
"Create projects per team, or per working site, and have a more accurate and "
"dynamic database."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:42
msgid ":doc:`../../project/overview/setup`"
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:3
msgid "Planning an Itinerary"
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:5
msgid ""
"Having an itinerary being shown based on the chronological order of the "
"activities and on the best route to take, makes employees’ life easier and "
"the workload more efficient."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:9
msgid "Have an itinerary displayed directly in Odoo"
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:10
msgid "Go to *Settings* and under *Map view* click on *Get token*."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:15
msgid ""
"Click on :menuselection:`Start mapping for free --> fill the Username, email"
" and password fields --> agree with their Terms of Service and Privacy "
"Policy --> Get started`. You will be redirected to your account. Scrolling "
"the page down you will find *Access tokens*. Copy the *Default public "
"token*."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:24
msgid "Back in Odoo, paste it on :menuselection:`Token --> Save`."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:29
msgid ""
"Now, your maps will show the itinerary based on the scheduled time and best "
"route."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:36
msgid ""
"This is an optional feature, as you can still have access to a map view "
"without a Mapbox account."
msgstr ""
#: ../../fsm/sales.rst:3
msgid "Sales"
msgstr ""
#: ../../fsm/sales/create_quotations.rst:3
msgid "Create Quotations from Tasks"
msgstr ""
#: ../../fsm/sales/create_quotations.rst:4
msgid ""
"Allowing quotations to be created from tasks delivers a more efficient "
"service as it allows space for preventive actions, while making the flow "
"easy for employees."
msgstr ""
#: ../../fsm/sales/create_quotations.rst:9
msgid ""
"First, go to :menuselection:`Field Service --> Configuration --> Settings` "
"and enable the option *Extra Quotations*."
msgstr ""
#: ../../fsm/sales/create_quotations.rst:16
msgid ""
"Second, go to :menuselection:`Configuration --> Projects` and enable *Extra "
"Quotations*."
msgstr ""
#: ../../fsm/sales/create_quotations.rst:23
msgid "You can now create *New Quotations* directly from your tasks."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:3
msgid "Create Onsite Interventions Tasks from Sales Orders"
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:4
msgid ""
"By allowing your sales team to open onsite interventions tasks will create a"
" seamless experience for your customers. It also allows them to first "
"receive a quotation with the materials that will be used plus the service "
"price to be approved before the work even starts."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:10
msgid ""
"Go to :menuselection:`Sales --> Products --> Create` or edit an existing "
"one. Select: under :menuselection:`General Information --> Product Type: "
"Service`; under :menuselection:`Sales --> Service Invoicing Policy: "
"Timesheet on task --> Service Tracking: Create a task in an existing project"
" --> Project --> Worksheet Template --> Save`."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:19
msgid ""
"Now, once you have *Confirmed* a *quotation*, a task will be created in the "
"respective project you have chosen."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:28
msgid ""
"One of the greatest benefits here is that you can have different *Worksheets"
" Templates* under the same project and product, for example."
msgstr ""
#: ../../fsm/worksheets.rst:3
msgid "Worksheets"
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:3
msgid "Customize Worksheet Reports"
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:4
msgid ""
"Personalizing your customer reports, also called *worksheets*, allows you to"
" have different descriptions of the work for each type of intervention. It "
"speeds up the flow for your employees while giving customers a detailed "
"summary, which can be reviewed and signed onsite."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:10
msgid ""
"Go to :menuselection:`Field Service --> Configuration` and enable "
":menuselection:`Worksheet Templates --> Save`."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:18
msgid "Designing worksheets"
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:19
msgid ""
"Under :menuselection:`Configuration --> Worksheet Templates`, click on "
"*Create* and start to *Design Worksheet Template*. You will be redirected to"
" the *Studio* application."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:27
msgid ""
"With the freedom of *Studio*, drag and drop fields to create a report "
"tailored to your needs. Once you are done, click on *Close* and get an "
"overview of the work done."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:30
msgid ""
"*Worksheets* is where you can see how many times the worksheet has been "
"used/completed under a task. *Analysis* examines all the worksheets under "
"that given template and generates a graph."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:38
msgid ""
"`Studio Basics <https://www.odoo.com/slides/slide/studio-"
"basics-710?fullscreen=1>`_"
msgstr ""

2380
locale/es/LC_MESSAGES/general.po
View File

File diff suppressed because it is too large Load Diff

256
locale/es/LC_MESSAGES/getting_started.po
View File

@ -3,17 +3,13 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Alejandro Kutulas <alk@odoo.com>, 2018
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 12.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-11-07 15:38+0100\n"
"PO-Revision-Date: 2018-10-19 08:15+0000\n"
"Last-Translator: Alejandro Kutulas <alk@odoo.com>, 2018\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -33,7 +29,7 @@ msgid ""
msgstr ""
#: ../../getting_started/documentation.rst:12
msgid "1. The SPoC (*Single Point of Contact*) and the Consultant"
msgid "The SPoC (*Single Point of Contact*) and the Consultant"
msgstr ""
#: ../../getting_started/documentation.rst:14
@ -76,24 +72,22 @@ msgid ""
"training to the SPoC so that he can pass on this knowledge to his "
"collaborators. In order for this approach to be successful, it is necessary "
"that the SPoC is also involved in its own rise in skills through self-"
"learning via the `Odoo documentation "
"<http://www.odoo.com/documentation/user/10.0/index.html>`__, `The elearning "
"platform <https://odoo.thinkific.com/courses/odoo-functional>`__ and the "
"testing of functionalities."
msgstr ""
#: ../../getting_started/documentation.rst:47
msgid "2. Project Scope"
"learning via the :doc:`Odoo documentation <../index>`, `The elearning "
"platform <https://odoo.com/learn>`_ and the testing of functionalities."
msgstr ""
#: ../../getting_started/documentation.rst:49
msgid "Project Scope"
msgstr ""
#: ../../getting_started/documentation.rst:51
msgid ""
"To make sure all the stakeholders involved are always aligned, it is "
"necessary to define and to make the project scope evolve as long as the "
"project implementation is pursuing."
msgstr ""
#: ../../getting_started/documentation.rst:53
#: ../../getting_started/documentation.rst:55
msgid ""
"**A clear definition of the initial project scope**: A clear definition of "
"the initial needs is crucial to ensure the project is running smoothly. "
@ -102,7 +96,7 @@ msgid ""
" clear."
msgstr ""
#: ../../getting_started/documentation.rst:59
#: ../../getting_started/documentation.rst:61
msgid ""
"**Phasing the project**: Favoring an implementation in several coherent "
"phases allowing regular production releases and an evolving takeover of Odoo"
@ -111,7 +105,7 @@ msgid ""
"the implementation."
msgstr ""
#: ../../getting_started/documentation.rst:66
#: ../../getting_started/documentation.rst:68
msgid ""
"**Adopting standard features as a priority**: Odoo offers a great "
"environment to implement slight improvements (customizations) or more "
@ -123,18 +117,18 @@ msgid ""
"experiment of the standard in production."
msgstr ""
#: ../../getting_started/documentation.rst:80
msgid "3. Managing expectations"
#: ../../getting_started/documentation.rst:82
msgid "Managing expectations"
msgstr ""
#: ../../getting_started/documentation.rst:82
#: ../../getting_started/documentation.rst:84
msgid ""
"The gap between the reality of an implementation and the expectations of "
"future users is a crucial factor. Three important aspects must be taken into"
" account from the beginning of the project:"
msgstr ""
#: ../../getting_started/documentation.rst:86
#: ../../getting_started/documentation.rst:88
msgid ""
"**Align with the project approach**: Both a clear division of roles and "
"responsibilities and a clear description of the operating modes (validation,"
@ -144,7 +138,7 @@ msgid ""
"check that this is still the case."
msgstr ""
#: ../../getting_started/documentation.rst:94
#: ../../getting_started/documentation.rst:96
msgid ""
"**Focus on the project success, not on the ideal solution**: The main goal "
"of the SPoC and the Consultant is to carry out the project entrusted to them"
@ -159,7 +153,7 @@ msgid ""
"to pursue this same objective."
msgstr ""
#: ../../getting_started/documentation.rst:108
#: ../../getting_started/documentation.rst:110
msgid ""
"**Specifications are always EXPLICIT**: Gaps between what is expected and "
"what is delivered are often a source of conflict in a project. In order to "
@ -167,35 +161,34 @@ msgid ""
"tools\\* :"
msgstr ""
#: ../../getting_started/documentation.rst:113
#: ../../getting_started/documentation.rst:115
msgid ""
"**The GAP Analysis**: The comparison of the request with the standard "
"features proposed by Odoo will make it possible to identify the gap to be "
"filled by developments/customizations or changes in business processes."
msgstr ""
#: ../../getting_started/documentation.rst:118
#: ../../getting_started/documentation.rst:120
msgid ""
"`The User Story <https://help.rallydev.com/writing-great-user-story>`__: "
"This technique clearly separates the responsibilities between the SPoC, "
"responsible for explaining the WHAT, the WHY and the WHO, and the Consultant"
" who will provide a response to the HOW."
"**The User Story**: This technique clearly separates the responsibilities "
"between the SPoC, responsible for explaining the WHAT, the WHY and the WHO, "
"and the Consultant who will provide a response to the HOW."
msgstr ""
#: ../../getting_started/documentation.rst:126
#: ../../getting_started/documentation.rst:128
msgid ""
"`The Proof of Concept <https://en.wikipedia.org/wiki/Proof_of_concept>`__ A "
"simplified version, a prototype of what is expected to agree on the main "
"lines of expected changes."
msgstr ""
#: ../../getting_started/documentation.rst:130
#: ../../getting_started/documentation.rst:132
msgid ""
"**The Mockup**: In the same idea as the Proof of Concept, it will align with"
" the changes related to the interface."
msgstr ""
#: ../../getting_started/documentation.rst:133
#: ../../getting_started/documentation.rst:135
msgid ""
"To these tools will be added complete transparency on the possibilities and "
"limitations of the software and/or its environment so that all project "
@ -204,17 +197,17 @@ msgid ""
"verifying its veracity beforehand."
msgstr ""
#: ../../getting_started/documentation.rst:139
#: ../../getting_started/documentation.rst:141
msgid ""
"*This list can, of course, be completed by other tools that would more "
"adequately meet the realities and needs of your project*"
msgstr ""
#: ../../getting_started/documentation.rst:143
msgid "4. Communication Strategy"
#: ../../getting_started/documentation.rst:145
msgid "Communication Strategy"
msgstr ""
#: ../../getting_started/documentation.rst:145
#: ../../getting_started/documentation.rst:147
msgid ""
"The purpose of the QuickStart methodology is to ensure quick ownership of "
"the tool for end users. Effective communication is therefore crucial to the "
@ -222,7 +215,7 @@ msgid ""
"follow those principles:"
msgstr ""
#: ../../getting_started/documentation.rst:150
#: ../../getting_started/documentation.rst:152
msgid ""
"**Sharing the project management documentation**: The best way to ensure "
"that all stakeholders in a project have the same level of knowledge is to "
@ -232,45 +225,45 @@ msgid ""
" manager are clearly defined."
msgstr ""
#: ../../getting_started/documentation.rst:158
#: ../../getting_started/documentation.rst:160
msgid ""
"The Project Organizer is a shared project tracking tool that allows both "
"detailed tracking of ongoing tasks and the overall progress of the project."
msgstr ""
#: ../../getting_started/documentation.rst:162
#: ../../getting_started/documentation.rst:164
msgid ""
"**Report essential information**: In order to minimize the documentation "
"time to the essentials, we will follow the following good practices:"
msgstr ""
#: ../../getting_started/documentation.rst:166
#: ../../getting_started/documentation.rst:168
msgid "Meeting minutes will be limited to decisions and validations;"
msgstr ""
#: ../../getting_started/documentation.rst:168
#: ../../getting_started/documentation.rst:170
msgid ""
"Project statuses will only be established when an important milestone is "
"reached;"
msgstr ""
#: ../../getting_started/documentation.rst:171
#: ../../getting_started/documentation.rst:173
msgid ""
"Training sessions on the standard or customized solution will be organized."
msgstr ""
#: ../../getting_started/documentation.rst:175
msgid "5. Customizations and Development"
#: ../../getting_started/documentation.rst:177
msgid "Customizations and Development"
msgstr ""
#: ../../getting_started/documentation.rst:177
#: ../../getting_started/documentation.rst:179
msgid ""
"Odoo is a software known for its flexibility and its important evolution "
"capacity. However, a significant amount of development contradicts a fast "
"and sustainable implementation. This is the reason why it is recommended to:"
msgstr ""
#: ../../getting_started/documentation.rst:182
#: ../../getting_started/documentation.rst:184
msgid ""
"**Develop only for a good reason**: The decision to develop must always be "
"taken when the cost-benefit ratio is positive (saving time on a daily basis,"
@ -284,7 +277,7 @@ msgid ""
"\"Adopting the standard as a priority\")."
msgstr ""
#: ../../getting_started/documentation.rst:194
#: ../../getting_started/documentation.rst:196
msgid ""
"**Replace, without replicate**: There is a good reason for the decision to "
"change the management software has been made. In this context, the moment of"
@ -293,18 +286,18 @@ msgid ""
"business processes of the company."
msgstr ""
#: ../../getting_started/documentation.rst:202
msgid "6. Testing and Validation principles"
#: ../../getting_started/documentation.rst:204
msgid "Testing and Validation principles"
msgstr ""
#: ../../getting_started/documentation.rst:204
#: ../../getting_started/documentation.rst:206
msgid ""
"Whether developments are made or not in the implementation, it is crucial to"
" test and validate the correspondence of the solution with the operational "
"needs of the company."
msgstr ""
#: ../../getting_started/documentation.rst:208
#: ../../getting_started/documentation.rst:210
msgid ""
"**Role distribution**: In this context, the Consultant will be responsible "
"for delivering a solution corresponding to the defined specifications; the "
@ -312,33 +305,33 @@ msgid ""
"requirements of the operational reality."
msgstr ""
#: ../../getting_started/documentation.rst:214
#: ../../getting_started/documentation.rst:216
msgid ""
"**Change management**: When a change needs to be made to the solution, the "
"noted gap is caused by:"
msgstr ""
#: ../../getting_started/documentation.rst:218
#: ../../getting_started/documentation.rst:220
msgid ""
"A difference between the specification and the delivered solution - This is "
"a correction for which the Consultant is responsible"
msgstr ""
#: ../../getting_started/documentation.rst:220
#: ../../getting_started/documentation.rst:223
msgid "**or**"
msgstr ""
#: ../../getting_started/documentation.rst:222
#: ../../getting_started/documentation.rst:225
msgid ""
"A difference between the specification and the imperatives of operational "
"reality - This is a change that is the responsibility of SPoC."
msgstr ""
#: ../../getting_started/documentation.rst:226
msgid "7. Data Imports"
#: ../../getting_started/documentation.rst:229
msgid "Data Imports"
msgstr ""
#: ../../getting_started/documentation.rst:228
#: ../../getting_started/documentation.rst:231
msgid ""
"Importing the history of transactional data is an important issue and must "
"be answered appropriately to allow the project running smoothly. Indeed, "
@ -347,14 +340,14 @@ msgid ""
"it will be decided :"
msgstr ""
#: ../../getting_started/documentation.rst:234
#: ../../getting_started/documentation.rst:237
msgid ""
"**Not to import anything**: It often happens that after reflection, "
"importing data history is not considered necessary, these data being, "
"moreover, kept outside Odoo and consolidated for later reporting."
msgstr ""
#: ../../getting_started/documentation.rst:239
#: ../../getting_started/documentation.rst:242
msgid ""
"**To import a limited amount of data before going into production**: When "
"the data history relates to information being processed (purchase orders, "
@ -363,7 +356,7 @@ msgid ""
" import will be made before the production launch."
msgstr ""
#: ../../getting_started/documentation.rst:246
#: ../../getting_started/documentation.rst:249
msgid ""
"**To import after production launch**: When the data history needs to be "
"integrated with Odoo mainly for reporting purposes, it is clear that these "
@ -371,139 +364,16 @@ msgid ""
"production launch of the solution will precede the required imports."
msgstr ""
#: ../../getting_started/documentation.rst:253
msgid "8. Support"
#: ../../getting_started/documentation.rst:256
msgid "Support"
msgstr ""
#: ../../getting_started/documentation.rst:255
#: ../../getting_started/documentation.rst:258
msgid ""
"Your Odoo Online subscription includes **unlimited 24hr support at no extra "
"cost, Monday to Friday**. Our teams are located around the world to ensure "
"you have support, no matter your location. Your support representative could"
" be communicating to you from San Francisco, Belgium, or India!"
"When your project is put in production, our support teams take care of your "
"questions or technical issues."
msgstr ""
"Tu subscripción online incluye **soporte ilimitado 24 horas sin costo extra,"
" Lunes a Viernes**. Nuestros equipos estan localizados alrededor del mundo "
"para asegurar que tengas soporte, sin importar tu localización. Tu "
"representativo de soporte puede comunicarse contigo desde San Francisco, "
"Bélgica, o India!"
#: ../../getting_started/documentation.rst:260
msgid "What kind of support is included?"
msgstr "¿Qué tipo de soporte está incluido?"
#: ../../getting_started/documentation.rst:262
msgid ""
"Providing you with relevant material (guidelines, product documentation, "
"etc...)"
#: ../../getting_started/documentation.rst:261
msgid "See :ref:`support-expectations`."
msgstr ""
"Proveerte con material relevante (guías, documentación de producto, etc...)"
#: ../../getting_started/documentation.rst:264
msgid ""
"Answers to issues that you may encounter in your standard Odoo database (eg."
" “I cannot close my Point of Sale” or “I cannot find my sales KPIs?”)"
msgstr ""
"Respuestas para asegurar que puedes encontrarte en tu database de Odoo "
"stándar (ej. \"No puedo cerrar my Punto de Venta\" o \"¿No puedo encontrar "
"los KPI's de ventas?)"
#: ../../getting_started/documentation.rst:266
msgid "Questions related to your account, subscription, or billing"
msgstr "Preguntas relacionadas con tu cuenta, subscripción, o facturación."
#: ../../getting_started/documentation.rst:267
msgid ""
"Bug resolution (blocking issues or unexpected behaviour not due to "
"misconfiguration or customization)"
msgstr ""
"Resolución de problemas (bloquear problemas o comportamientos inesperados no"
" por desconfiguración o customización)"
#: ../../getting_started/documentation.rst:269
msgid ""
"Issues that might occur in a test database after upgrading to a newer "
"version"
msgstr ""
"Situaciones que pueden ocurrir en una base de datos de prueba despues de "
"actualizar a la nueva versión "
#: ../../getting_started/documentation.rst:271
msgid ""
"*Odoo Support does not make changes to your production database, but gives "
"you the material and knowledge to do it yourself!*"
msgstr ""
"*Soporte de Odoo no hace cambios a tu base de datos de producción, pero te "
"entrega material y conocimiento para que lo hagas tu mismo!*"
#: ../../getting_started/documentation.rst:274
msgid "What kind of support is not included?"
msgstr "¿Qué tipo de soporte no está incluido?"
#: ../../getting_started/documentation.rst:276
msgid ""
"Questions that require us to understand your business processes in order to "
"help you implement your database"
msgstr ""
"Preguntas que requieren que entendamos tu proceso de negocio para así "
"ayudarte a implementar tu base de datos"
#: ../../getting_started/documentation.rst:278
msgid ""
"Training on how to use our software (we will direct you to our many "
"resources)"
msgstr ""
"Entrenamiento en cómo usar tu Software (te direccionaremos a nuestros "
"variados recursos)"
#: ../../getting_started/documentation.rst:279
msgid "Importation of documents into your database"
msgstr "Importación de documentos en tu base de datos"
#: ../../getting_started/documentation.rst:280
msgid ""
"Guidance on which configurations to apply inside of an application or the "
"database"
msgstr ""
"Guía en qué configuraciones aplicar dentro de una aplicación o la base de "
"datos"
#: ../../getting_started/documentation.rst:281
msgid ""
"How to set up configuration models (Examples include: Inventory Routes, "
"Payment Terms, Warehouses, etc)"
msgstr ""
"Como fijar modelos de configuración (Ejemplos incluyen: Rutas de Inventario,"
" Términos de Pagos, Bodegas, etc)"
#: ../../getting_started/documentation.rst:283
msgid ""
"Questions or issues related to specific developments or customizations done "
"either by Odoo or a third party (this is specific only to your database or "
"involving code)"
msgstr ""
"Preguntas o situaciones relacionadas a desarrollos específicos o "
"customizaciones hechas por Odoo o un tercero (esto es específico sólo para "
"tu base de datos o código involvente)"
#: ../../getting_started/documentation.rst:287
msgid ""
"You can get this type of support with a `Success Pack <https://www.odoo.com"
"/pricing-packs>`__. With a pack, one of our consultants will analyze the way"
" your business runs and tell you how you can get the most out of your Odoo "
"Database. We will handle all configurations and coach you on how to use "
"Odoo."
msgstr ""
"Puedes tener este tipo de soporte con un `Success Pack <https://www.odoo.com"
"/pricing-packs>`__. Con un pack, uno de nuestros consultantes analizará la "
"manera que manejas tu negocio y decirte cómo puedes obtener lo mejor de tu "
"base de datos de Odoo. Manejaremos todas las configuraciones y te "
"entrenaremos en cómo usar Odoo."
#: ../../getting_started/documentation.rst:292
msgid ""
"Our support team can be contacted through our `online support form "
"<https://www.odoo.com/help>`__."
msgstr ""
"Nuestro equipo de soporte puede ser contactado a través de nuestra `forma de"
" soporte online <https://www.odoo.com/help>`__."

980
locale/es/LC_MESSAGES/helpdesk.po
View File

File diff suppressed because it is too large Load Diff

11
locale/es/LC_MESSAGES/index.po
View File

@ -3,14 +3,17 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Pedro M. Baeza <pedro.baeza@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Pedro M. Baeza <pedro.baeza@gmail.com>, 2018\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Last-Translator: Pedro M. Baeza <pedro.baeza@gmail.com>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"

10533
locale/es/LC_MESSAGES/inventory.po
View File

File diff suppressed because it is too large Load Diff

614
locale/es/LC_MESSAGES/iot.po
View File

@ -3,14 +3,21 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Luis M. Ontalba <luis.martinez@tecnativa.com>, 2020
# Pablo Rojas <rojaspablo88@gmail.com>, 2020
# AleEscandon <alejandra.escandon@jarsa.com.mx>, 2020
# Vivian Montana <vmo@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: AleEscandon <alejandra.escandon@jarsa.com.mx>, 2018\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Vivian Montana <vmo@odoo.com>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -22,66 +29,83 @@ msgstr ""
msgid "Internet of Things (IoT)"
msgstr ""
#: ../../iot/connect.rst:3
#: ../../iot/config.rst:3
msgid "Configuration"
msgstr "Configuración"
#: ../../iot/config/connect.rst:3
msgid "Connect an IoT Box to your database"
msgstr ""
#: ../../iot/connect.rst:5
#: ../../iot/config/connect.rst:5
msgid "Install the Internet of Things (IoT) App on your Odoo Database."
msgstr ""
#: ../../iot/connect.rst:10
#: ../../iot/config/connect.rst:10
msgid "Go in the IoT App and click on Connect on the IoT Boxes page."
msgstr ""
#: ../../iot/connect.rst:15
#: ../../iot/config/connect.rst:15
msgid "Follow the steps to connect your IoT Box."
msgstr ""
#: ../../iot/connect.rst:21
#: ../../iot/config/connect.rst:21
msgid "Ethernet Connection"
msgstr ""
#: ../../iot/connect.rst:23
#: ../../iot/config/connect.rst:23
msgid ""
"Connect to the IoT Box all the devices that have to be connected with cables"
" (ethernet, usb devices, etc.)."
msgstr ""
#: ../../iot/connect.rst:26
#: ../../iot/config/connect.rst:26
msgid "Power on the IoT Box."
msgstr ""
#: ../../iot/connect.rst:28
msgid "Then click on the Scan button."
#: ../../iot/config/connect.rst:28
msgid ""
"Read the Pairing Code from a screen or a receipt printer connected to the "
"IoT Box."
msgstr ""
#: ../../iot/connect.rst:34
#: ../../iot/config/connect.rst:32
msgid "Input the Pairing Code and click on the Pair button."
msgstr ""
#: ../../iot/config/connect.rst:35
msgid ""
"Recent changes in modern web browsers forced us to modify the connection "
"wizard. If your screen is different from the screenshots, make sure that the"
" ``iot_pairing`` module is installed."
msgstr ""
#: ../../iot/config/connect.rst:40
msgid "WiFi Connection"
msgstr ""
#: ../../iot/connect.rst:36
#: ../../iot/config/connect.rst:42
msgid "Power on the IoT Box"
msgstr ""
#: ../../iot/connect.rst:38
#: ../../iot/config/connect.rst:44
msgid "Copy the token"
msgstr ""
#: ../../iot/connect.rst:43
#: ../../iot/config/connect.rst:48
msgid ""
"Connect to the IoT Box WiFi Network (make sure there is no ethernet cable "
"plugged in your computer)."
msgstr ""
#: ../../iot/connect.rst:49
#: ../../iot/config/connect.rst:53
msgid ""
"You will be redirected to the IoT Box Homepage (if it doesn't work, connect "
"to the IP address of the box). Give a name to your IoT Box (not required) "
"and paste the token, then click on next."
msgstr ""
#: ../../iot/connect.rst:57
#: ../../iot/config/connect.rst:60
msgid ""
"If you are on Runbot, do not forget to add the -all or -base in the token "
"(e.g. this token **http://375228-saas-11-5-iot-"
@ -89,104 +113,175 @@ msgid ""
"**http://375228-saas-11-5-iot-f3f920-all.runbot16.odoo.com\\|4957098401**)."
msgstr ""
#: ../../iot/connect.rst:63
#: ../../iot/config/connect.rst:66
msgid ""
"Choose the WiFi network you want to connect with (enter the password if "
"there is one) and click on Submit. Wait a few seconds before being "
"redirected to your database."
msgstr ""
#: ../../iot/connect.rst:70
#: ../../iot/config/connect.rst:72
msgid "You should now see the IoT Box."
msgstr ""
#: ../../iot/connect.rst:76
#: ../../iot/config/connect.rst:78
msgid "IoT Box Schema"
msgstr ""
#: ../../iot/pos.rst:3
#: ../../iot/config/flash_sdcard.rst:3
msgid "Flashing your SD Card"
msgstr ""
#: ../../iot/config/flash_sdcard.rst:5
msgid ""
"In some case, you may need to reflash your IoT Box’s SD Card to benefit from"
" our latest updates."
msgstr ""
#: ../../iot/config/flash_sdcard.rst:9
msgid "Updating your SD Card with Etcher"
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."
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*!."
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."
msgstr ""
#: ../../iot/config/iot_notfound.rst:3
msgid "IoT Box not found"
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`"
msgstr ""
#: ../../iot/config/pos.rst:3
msgid "Use the IoT Box for the PoS"
msgstr ""
#: ../../iot/pos.rst:9
#: ../../iot/config/pos.rst:9
msgid "Prerequisites"
msgstr "Pre-requisitos"
#: ../../iot/pos.rst:11
#: ../../iot/config/pos.rst:11
msgid "Before starting, make sure you have the following:"
msgstr ""
#: ../../iot/pos.rst:13
#: ../../iot/config/pos.rst:13
msgid "An IoT Box"
msgstr ""
#: ../../iot/pos.rst:15
#: ../../iot/config/pos.rst:15
msgid "A 2A Power adapter with pi 3 b+ 2.5 A"
msgstr ""
#: ../../iot/pos.rst:17
#: ../../iot/config/pos.rst:17
msgid "A computer or tablet with an up-to-date web browser"
msgstr "Una computadora o tableta con un navegador web actualizado a la fecha"
#: ../../iot/pos.rst:19
#: ../../iot/config/pos.rst:19
msgid ""
"A running SaaS or Odoo instance with the Point of Sale and IoT apps "
"installed"
msgstr ""
#: ../../iot/pos.rst:22
#: ../../iot/config/pos.rst:22
msgid "A local network setup with DHCP (this is the default setting)"
msgstr ""
#: ../../iot/pos.rst:24
#: ../../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/pos.rst:28
#: ../../iot/config/pos.rst:28
msgid "A Honeywell Eclipse USB Barcode Scanner or another compatible scanner"
msgstr ""
"Un Escáner de código de barras USB Honeywell Eclipse u otro escáner "
"compatible"
#: ../../iot/pos.rst:30
#: ../../iot/config/pos.rst:30
msgid "An Epson compatible cash drawer"
msgstr "Un cajón de dinero Epson compatible"
#: ../../iot/pos.rst:32
#: ../../iot/config/pos.rst:32
msgid "An RJ45 Ethernet Cable (optional, WiFi is built in)"
msgstr ""
#: ../../iot/pos.rst:35
#: ../../iot/config/pos.rst:35
msgid "Set Up"
msgstr "Configurar"
#: ../../iot/pos.rst:37
#: ../../iot/config/pos.rst:37
msgid ""
"To connect hardware to the PoS, the first step is to connect an IoT Box to "
"your database. For this, follow this `documentation "
"<https://docs.google.com/document/d/1vhWrSSlSdJcRYe4tjPpXKYVMTD47lVK3ysyYc7tJDlA/edit#>`__."
"your database. For this, follow this :doc:`documentation <connect>`."
msgstr ""
#: ../../iot/pos.rst:44
#: ../../iot/config/pos.rst:44
msgid "Then, you have to connect the peripheral devices to your IoT Box."
msgstr ""
#: ../../iot/pos.rst:46
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:50
#: ../../iot/config/pos.rst:50
msgid "**Printer**: Connect an ESC/POS printer to a USB port and power it on."
msgstr ""
"**Impresora**: Conectar una impresora ESC/POS a un puerto USB y encenderla."
#: ../../iot/pos.rst:53
#: ../../iot/config/pos.rst:53
msgid ""
"**Cash drawer**: The cash drawer should be connected to the printer with an "
"RJ25 cable."
@ -194,7 +289,7 @@ msgstr ""
"**Cajón de dinero**: El cajón de dinero debe conectarse a la impresora con "
"un cable RJ25."
#: ../../iot/pos.rst:56
#: ../../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 "
@ -208,18 +303,18 @@ msgstr ""
"barras con una tecla ENTER (código clave 28). Esto es más probable en la "
"configuración por defecto de su escáner."
#: ../../iot/pos.rst:62
#: ../../iot/config/pos.rst:62
msgid "**Scale**: Connect your scale and power it on."
msgstr "**Escala**: Conecte su escala y enciéndala. "
#: ../../iot/pos.rst:64
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:68
#: ../../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 "
@ -227,26 +322,26 @@ msgid ""
"on boot."
msgstr ""
#: ../../iot/pos.rst:73
#: ../../iot/config/pos.rst:73
msgid ""
"Once it's done, you can connect the IoT Box to your PoS. For this, go in "
"Point of Sale > Configuration > PoS, tick the box \"IoT Box\" and select the"
" IoT Box you want to connect with. Save the changes."
":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/pos.rst:77
#: ../../iot/config/pos.rst:77
msgid "Set up is done, you can launch a new PoS Session."
msgstr ""
#: ../../iot/pos.rst:80
#: ../../iot/config/pos.rst:80
msgid "Troubleshoot"
msgstr "Solución de problemas"
#: ../../iot/pos.rst:83
#: ../../iot/config/pos.rst:83
msgid "The PoS cannot connect to the IoT Box"
msgstr ""
#: ../../iot/pos.rst:85
#: ../../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"
@ -254,48 +349,48 @@ msgid ""
"receipt is printed, check the following steps:"
msgstr ""
#: ../../iot/pos.rst:91
#: ../../iot/config/pos.rst:91
msgid ""
"Make sure the IoT Box is powered on, indicated by a brightly lit red status "
"LED."
msgstr ""
#: ../../iot/pos.rst:94
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:98
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:102
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:106
#: ../../iot/config/pos.rst:106
msgid "Make sure that the POS is not loaded over HTTPS."
msgstr "Asegúrese que el PdV no está cargado sobre HTTPS."
#: ../../iot/pos.rst:108
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:113
#: ../../iot/config/pos.rst:113
msgid "The Barcode Scanner is not working"
msgstr "El escáner de código de barra no está funcionando"
#: ../../iot/pos.rst:115
#: ../../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. "
@ -307,14 +402,14 @@ msgstr ""
"barras. Consulte la documentación del lector de código de barras para "
"obtener más información."
#: ../../iot/pos.rst:120
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:124
#: ../../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"
@ -325,28 +420,28 @@ msgstr ""
"proporcionada. En estos casos usted puede conectar el escáner de código de "
"barras en un concentrador USB con alimentación propia."
#: ../../iot/pos.rst:129
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:134
#: ../../iot/config/pos.rst:134
msgid "The Barcode Scanner is not working reliably"
msgstr "El escáner de código de barra no está funcionando de manera segura"
#: ../../iot/pos.rst:136
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:140
#: ../../iot/config/pos.rst:140
msgid "Printing the receipt takes too much time"
msgstr "Impresión del recibo tarda demasiado tiempo"
#: ../../iot/pos.rst:142
#: ../../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 "
@ -354,21 +449,21 @@ msgid ""
"and the IoT Box."
msgstr ""
#: ../../iot/pos.rst:148
#: ../../iot/config/pos.rst:148
msgid "Some characters are not correctly printed on the receipt"
msgstr "Algunos caracteres no se imprimen correctamente en el recibo"
#: ../../iot/pos.rst:150
#: ../../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."
msgstr ""
#: ../../iot/pos.rst:155
#: ../../iot/config/pos.rst:155
msgid "The printer is offline"
msgstr "La impresora está fuera de línea"
#: ../../iot/pos.rst:157
#: ../../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 "
@ -378,14 +473,385 @@ msgstr ""
"suficiente papel y tener su tapa cerrada, y que no informe error. Si el "
"error persiste, póngase en contacto con soporte."
#: ../../iot/pos.rst:162
#: ../../iot/config/pos.rst:162
msgid "The cashdrawer does not open"
msgstr "El cajón de dinero no abre"
#: ../../iot/pos.rst:164
#: ../../iot/config/pos.rst:164
msgid ""
"The cashdrawer should be connected to the printer and should be activated in"
" the POS configuration."
msgstr ""
"El cajón de dinero debe estar conectado a la impresora y se debe activar en "
"la configuración de la terminal."
#: ../../iot/devices.rst:3
msgid "Devices"
msgstr "Dispositivos"
#: ../../iot/devices/camera.rst:3
msgid "Connect a Camera"
msgstr ""
#: ../../iot/devices/camera.rst:5
msgid ""
"When using your *IoT Box* in Odoo, you could need to use a camera. As it can"
" be done in a few steps, this device is really easy to configure. Then, you "
"can use it in your manufacturing process and link it to a control point. "
"Doing so will allow you to take pictures when you reach the chosen quality "
"control point."
msgstr ""
#: ../../iot/devices/camera.rst:12 ../../iot/devices/footswitch.rst:13
#: ../../iot/devices/printer.rst:11
msgid "Connection"
msgstr "Conexión"
#: ../../iot/devices/camera.rst:14
msgid ""
"To connect the camera to the *IoT Box*, simply combine 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
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
msgid "Link a Camera to a Quality Control Point"
msgstr ""
#: ../../iot/devices/camera.rst:38 ../../iot/devices/measurement_tool.rst:42
msgid "With the Manufacturing app"
msgstr ""
#: ../../iot/devices/camera.rst:40
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
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
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 ""
#: ../../iot/devices/footswitch.rst:3
msgid "Connect a Footswitch"
msgstr ""
#: ../../iot/devices/footswitch.rst:5
msgid ""
"When working, it is always better to have your two hands available. Using "
"Odoo’s *IoT Box* and a footswitch will allow it."
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."
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."
msgstr ""
#: ../../iot/devices/footswitch.rst:19
msgid "In some cases, a serial to USB adapter may be needed."
msgstr ""
#: ../../iot/devices/footswitch.rst:21
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
msgid "Link a Footswitch to a Workcenter"
msgstr ""
#: ../../iot/devices/footswitch.rst:39
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
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
msgid ""
"When you are on the work order screen, a status button indicates if you are "
"correctly connected to the footswitch."
msgstr ""
#: ../../iot/devices/measurement_tool.rst:3
msgid "Connect a Measurement Tool"
msgstr ""
#: ../../iot/devices/measurement_tool.rst:5
msgid ""
"With Odoo’s *IoT Box*, it is possible to connect measurement tools to your "
"database. Find the list of supported devices here: `Supported devices "
"<https://www.odoo.com/page/iot-hardware>`__,."
msgstr ""
#: ../../iot/devices/measurement_tool.rst:10
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."
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
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
msgid "Here is an example of what it should look like:"
msgstr ""
#: ../../iot/devices/measurement_tool.rst:39
msgid "Link a measurement tool to a quality control point"
msgstr ""
#: ../../iot/devices/measurement_tool.rst:44
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
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
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 ""
#: ../../iot/devices/printer.rst:3
msgid "Connect a Printer"
msgstr ""
#: ../../iot/devices/printer.rst:5
msgid ""
"When using your *IoT Box* in Odoo, you could need to use a printer. Doing so"
" is easy and convenient as it can be done in a few steps. Then, you can use "
"it to print receipts, orders or even reports in different Odoo apps."
msgstr ""
#: ../../iot/devices/printer.rst:13
msgid ""
"To connect the printer to the *IoT Box*, you just have to combine the two by"
" cable."
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
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
msgid "Link the Printer"
msgstr ""
#: ../../iot/devices/printer.rst:40
msgid "To Work Orders"
msgstr ""
#: ../../iot/devices/printer.rst:42
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
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
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
msgid "To Reports"
msgstr ""
#: ../../iot/devices/printer.rst:62
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
msgid "Now, go to the *Printer Reports* tab."
msgstr ""
#: ../../iot/devices/printer.rst:74
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
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
msgid "Print Receipts from the PoS"
msgstr ""
#: ../../iot/devices/printer.rst:88
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*."
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**."
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*."
msgstr ""
#: ../../iot/devices/printer.rst:104
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."
msgstr ""
#: ../../iot/devices/printer.rst:119
msgid "Print Orders in the kitchen"
msgstr ""
#: ../../iot/devices/printer.rst:121
msgid "In restaurant mode, you can send order tickets to the kitchen."
msgstr ""
#: ../../iot/devices/printer.rst:123
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."
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."
msgstr ""

378
locale/es/LC_MESSAGES/livechat.po
View File

@ -3,14 +3,19 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Lina Maria Avendaño Carvajal <lina8823@gmail.com>, 2020
# Nicolás Broggi <rnbroggi@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-23 12:10+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Nicolás Broggi <rnbroggi@gmail.com>, 2018\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Nicolás Broggi <rnbroggi@gmail.com>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -18,232 +23,253 @@ msgstr ""
"Language: es\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../livechat/livechat.rst:5
msgid "Live Chat"
msgstr "Charla en vivo"
#: ../../livechat/overview.rst:3
msgid "Overview"
msgstr "Información general"
#: ../../livechat/livechat.rst:8
msgid "Chat in live with website visitors"
msgstr "Chatee en vivo con los visitantes del sitio web"
#: ../../livechat/livechat.rst:10
msgid ""
"With Odoo Live Chat, you can establish a direct contact with your website "
"visitors. A simple dialog box will be available on their screen and will "
"allow them to get in touch with one of your sales representatives. This way,"
" you can easily turn prospects into potential business opportunities. You "
"will also be able to provide assistance to your customers. Overall, this is "
"the perfect tool to improve customer satisfaction."
#: ../../livechat/overview/get_started.rst:3
msgid "Get Started with Live Chat"
msgstr ""
"Con Odoo Live Chat, puede establecer un contacto directo con los visitantes "
"de su sitio web. Un cuadro de diálogo simple estará disponible en su "
"pantalla y les permitirá ponerse en contacto con uno de sus representantes "
"de ventas. De esta manera, puede convertir fácilmente a los prospectos en "
"posibles oportunidades comerciales. También podrá brindar asistencia a sus "
"clientes. En general, esta es la herramienta perfecta para mejorar la "
"satisfacción del cliente."
#: ../../livechat/livechat.rst:19
msgid "Configuration"
msgstr "Configuración"
#: ../../livechat/livechat.rst:21
#: ../../livechat/overview/get_started.rst:5
msgid ""
"To get the Live Chat feature, open the Apps module, search for \"Live Chat\""
" and then click on install."
"Live Chat has the highest satisfaction rating of any communication tool. It "
"allows fast responses and it is accessible and convenient, as your customers"
" can keep doing what they are doing while interacting with you. Remember: "
"your customers want to talk to you, so let's make it easy."
msgstr ""
"Para obtener la función de chat en vivo, abra el módulo Aplicaciones, busque"
" \"Chat en vivo\" y luego haga clic en instalar."
#: ../../livechat/livechat.rst:27
#: ../../livechat/overview/get_started.rst:10
msgid "Set up"
msgstr ""
#: ../../livechat/overview/get_started.rst:12
msgid ""
"The Live Chat module provides you a direct access to your channels. There, "
"operators can easily join and leave the chat."
"Once *Live Chat* is installed on your database, if your website was created "
"with Odoo, the application is automatically added to it. All that is left to"
" do is to go to :menuselection:`Website --> Configuration --> Settings --> "
"Live Chat`."
msgstr ""
"El módulo Live Chat le proporciona acceso directo a sus canales. Allí, los "
"operadores pueden unirse fácilmente y abandonar el chat."
#: ../../livechat/livechat.rst:34
msgid "Add the live chat to an Odoo website"
msgstr "Agregue el chat en vivo a un sitio web de Odoo"
#: ../../livechat/livechat.rst:36
#: ../../livechat/overview/get_started.rst:21
msgid ""
"If your website was created with Odoo, then the live chat is automatically "
"added to it. All that is left to do, is to go to :menuselection:`Website -->"
" Configuration --> Settings` to select the channel to be linked to the "
"website."
"Select the channel to be linked to your website or create one on the fly."
msgstr ""
"Si su sitio web fue creado con Odoo, entonces el chat en vivo se agrega "
"automáticamente. Todo lo que queda por hacer es ir a: menu selection: `Sitio"
" web -> Configuración -> Configuración` para seleccionar el canal que se va "
"a vincular al sitio web."
#: ../../livechat/livechat.rst:45
msgid "Add the live chat to an external website"
msgstr "Agregue el chat en vivo a un sitio web externo"
#: ../../livechat/overview/get_started.rst:27
msgid "For both scenarios, under:"
msgstr ""
#: ../../livechat/livechat.rst:47
#: ../../livechat/overview/get_started.rst:30
msgid ""
"If your website was not created with Odoo, go to the Live Chat module and "
"then select the channel to be linked. There, you can simply copy paste the "
"code available into your website. A specific url you can send to customers "
"or suppliers for them to access the live chat is also provided."
"- **Operators**: add agents to respond to the chat requests. Add as many as "
"you like, and keep in mind that operators that do not show any activity in "
"Odoo for more than 30min are considered disconnected."
msgstr ""
"Si su sitio web no se creó con Odoo, vaya al módulo Chat en vivo y luego "
"seleccione el canal que se va a vincular. Allí, simplemente copie y pegue el"
" código disponible en su sitio web. También se proporciona una URL "
"específica que puede enviar a clientes o proveedores para que accedan al "
"chat en vivo."
#: ../../livechat/livechat.rst:54
msgid "Hide / display the live chat according to rules"
msgstr "Ocultar / mostrar el chat en vivo de acuerdo a las reglas"
#: ../../livechat/livechat.rst:56
#: ../../livechat/overview/get_started.rst:33
msgid ""
"Rules for the live chat can be defined on the channel form. For instance, "
"you can choose to display the chat in the countries you speak the language "
"of. On the contrary, you are able to hide the chat in countries your company"
" does not sell in. If you select *Auto popup*, you can also set the length "
"of time it takes for the chat to appear."
"- **Options**: set the default text to be shown on the live chat button; an "
"automated welcome message to be seen by visitors when a conversation is "
"initiated, and the text that prompts the user to initiate a chat."
msgstr ""
"Las reglas para el chat en vivo se pueden definir en el formulario del "
"canal. Por ejemplo, puede elegir mostrar el chat en los países en los que "
"habla el idioma. Por el contrario, puede ocultar el chat en países en los "
"que su empresa no vende. Si selecciona *Auto popup*, también puede "
"establecer el tiempo que tarda el chat en aparecer."
#: ../../livechat/livechat.rst:66
msgid "Prepare automatic messages"
msgstr "Preparar mensajes automáticos"
#: ../../livechat/livechat.rst:68
#: ../../livechat/overview/get_started.rst:36
msgid ""
"On the channel form, in the *Options* section, several messages can be typed"
" to appear automatically on the chat. This will entice visitors to reach you"
" through the live chat."
"- **Channel Rules**: choose an action for a given URL, and/or per country. "
"In the example below, the chat window automatically pops-up 3 seconds after "
"users (from any country) land on the contact us page."
msgstr ""
"En el formulario del canal, en la sección *Opciones*, se pueden escribir "
"varios mensajes para que aparezcan automáticamente en el chat. Esto atraerá "
"a los visitantes a contactarlo a través del chat en vivo."
#: ../../livechat/livechat.rst:76
msgid "Start chatting with customers"
msgstr "Comience a chatear con los clientes"
#: ../../livechat/livechat.rst:78
#: ../../livechat/overview/get_started.rst:43
msgid ""
"In order to start chatting with customers, first make sure that the channel "
"is published on your website. To do so, select *Unpublished on Website* on "
"the top right corner of the channel form to toggle the *Published* setting. "
"Then, the live chat can begin once an operator has joined the channel."
"GeoIP, which refers to the process of finding a computer terminal’s "
"geographical location by its IP address, must be installed on your server. "
"Otherwise, under *Channel Rules*, countries are not taken into account."
msgstr ""
"Para comenzar a chatear con los clientes, primero asegúrese de que el canal "
"esté publicado en su sitio web. Para hacerlo, seleccione *No publicado en el"
" sitio web* en la esquina superior derecha del formulario del canal para "
"alternar la configuración *Publicado*. Luego, el chat en vivo puede comenzar"
" una vez que un operador se haya unido al canal."
#: ../../livechat/livechat.rst:88
#: ../../livechat/overview/get_started.rst:48
msgid "External options"
msgstr ""
#: ../../livechat/overview/get_started.rst:51
msgid ""
"If no operator is available and/or if the channel is unpublished on the "
"website, then the live chat button will not appear to visitors."
"If your website was not created with Odoo, you can find the code to be added"
" to your own, under the *Widget* tab."
msgstr ""
"Si no hay un operador disponible y/o si el canal no está publicado en el "
"sitio web, el botón de chat en vivo no aparecerá para los visitantes."
#: ../../livechat/livechat.rst:92
#: ../../livechat/overview/get_started.rst:52
msgid ""
"In practice, the conversations initiated by the visitors will appear in the "
"Discuss module and will also pop up as a direct message. Therefore, "
"inquiries can be answered wherever you are in Odoo."
"Odoo also offers an URL you can send to users so they can have access to a "
"single live chat page."
msgstr ""
"En la práctica, las conversaciones iniciadas por los visitantes aparecerán "
"en el módulo Discusión y también aparecerán como un mensaje directo. Por lo "
"tanto, las consultas pueden responderse donde sea que se encuentre en Odoo."
#: ../../livechat/livechat.rst:96
#: ../../livechat/overview/get_started.rst:59
msgid "Managing chat requests"
msgstr ""
#: ../../livechat/overview/get_started.rst:61
msgid ""
"If there several operators in charge of a channel, the system will dispatch "
"sessions randomly between them."
"Conversations initiated by visitors pop up as a direct message, and are "
"shown in *Discuss*. Therefore, inquiries can be answered wherever you are in"
" Odoo."
msgstr ""
"Si hay varios operadores a cargo de un canal, el sistema enviará sesiones al"
" azar entre ellos."
#: ../../livechat/livechat.rst:100
#: ../../livechat/overview/get_started.rst:69
msgid ""
"Conversations are dispatched based on the current workload of the online "
"operators."
msgstr ""
#: ../../livechat/overview/get_started.rst:72
msgid "Leave or join a channel"
msgstr ""
#: ../../livechat/overview/get_started.rst:74
msgid ""
"Go to :menuselection:`Website --> Configuration --> Settings`, access your "
"channel under *Live Chat*, and *Join Channel* or *Leave Channel*."
msgstr ""
#: ../../livechat/overview/get_started.rst:82
#: ../../livechat/overview/responses.rst:48
msgid ":doc:`ratings`"
msgstr ""
#: ../../livechat/overview/get_started.rst:83
#: ../../livechat/overview/ratings.rst:45
msgid ":doc:`responses`"
msgstr ""
#: ../../livechat/overview/ratings.rst:3
msgid "Ratings"
msgstr "Valoraciones"
#: ../../livechat/overview/ratings.rst:5
msgid ""
"Giving users the opportunity to rate their interactions can help you "
"improving the experience you offer. That means staying on top of your "
"customers' needs, besides keeping track of your operators’ performances."
msgstr ""
#: ../../livechat/overview/ratings.rst:10
msgid "Customer Rating"
msgstr "Valoración del cliente"
#: ../../livechat/overview/ratings.rst:12
msgid ""
"Once the user chooses to close the chat window, he can rate his interaction."
msgstr ""
#: ../../livechat/overview/ratings.rst:14
msgid ""
"If the user is *Not satisfied* or *Highly dissatisfied*, a field allowing "
"for an explanation is shown."
msgstr ""
#: ../../livechat/overview/ratings.rst:15
msgid "A copy of the conversation can also be sent by email."
msgstr ""
#: ../../livechat/overview/ratings.rst:22
msgid "The rating is shown on the chat window itself for the operator."
msgstr ""
#: ../../livechat/overview/ratings.rst:28
msgid "And under :menuselection:`Report --> Customer Ratings`."
msgstr ""
#: ../../livechat/overview/ratings.rst:35
msgid "Make the rating public"
msgstr ""
#: ../../livechat/overview/ratings.rst:37
msgid ""
"Go to :menuselection:`Website --> Configuration --> Settings`, access your "
"channel form, click on *Go to Website* and on *Unpublished*, to publish the "
"rating of that channel on your website."
msgstr ""
#: ../../livechat/overview/responses.rst:3
msgid "Commands and Canned Responses"
msgstr ""
#: ../../livechat/overview/responses.rst:5
msgid ""
"Using canned responses can help you save time and have a previous, well-"
"thought response, to some of your most common questions and comments."
msgstr ""
#: ../../livechat/overview/responses.rst:9
msgid "Use commands"
msgstr "Usar comandos"
#: ../../livechat/livechat.rst:102
#: ../../livechat/overview/responses.rst:11
msgid ""
"Commands are useful shortcuts for completing certain actions or to access "
"information you might need. To use this feature, simply type the commands "
"into the chat. The following actions are available :"
"Commands are shortcuts that do specific actions within the chat window:"
msgstr ""
"Los comandos son atajos útiles para completar ciertas acciones o para "
"acceder a la información que pueda necesitar. Para usar esta función, "
"simplemente escriba los comandos en el chat. Las siguientes acciones están "
"disponibles:"
#: ../../livechat/livechat.rst:106
msgid "**/help** : show a helper message."
msgstr "**/help**: muestra un mensaje de ayuda."
#: ../../livechat/overview/responses.rst:13
msgid "**/help**: shows a help message."
msgstr ""
#: ../../livechat/livechat.rst:108
msgid "**/helpdesk** : create a helpdesk ticket."
msgstr "**/helpdesk** : crea un ticket de servicio de asistencia."
#: ../../livechat/overview/responses.rst:14
msgid "**/helpdesk**: creates a helpdesk ticket."
msgstr ""
#: ../../livechat/livechat.rst:110
msgid "**/helpdesk\\_search** : search for a helpdesk ticket."
msgstr "**/helpdesk\\_search** : busca un ticket de servicio de asistencia."
#: ../../livechat/overview/responses.rst:15
msgid "**/helpdesk_search**: searches for a helpdesk ticket."
msgstr ""
#: ../../livechat/livechat.rst:112
msgid "**/history** : see 15 last visited pages."
msgstr "**/history** : ver 15 últimas páginas visitadas."
#: ../../livechat/overview/responses.rst:16
msgid "**/history**: shows the last 15 visited pages."
msgstr ""
#: ../../livechat/livechat.rst:114
msgid "**/lead** : create a new lead."
msgstr "**/lead** : crea una nueva iniciativa."
#: ../../livechat/overview/responses.rst:17
msgid "**/lead**: creates a new lead."
msgstr ""
#: ../../livechat/livechat.rst:116
msgid "**/leave** : leave the channel."
msgstr "**/leave** : dejar el canal."
#: ../../livechat/overview/responses.rst:18
msgid "**/leave**: leaves the channel."
msgstr ""
#: ../../livechat/livechat.rst:119
#: ../../livechat/overview/responses.rst:0
msgid ""
"If a helpdesk ticket is created from the chat, then the conversation it was "
"generated from will automatically appear as the description of the ticket. "
"The same goes for the creation of a lead."
"- For *helpdesk tickets*: make sure the application is installed on your "
"database and the option *Live Chat* under :menuselection:`Helpdesk --> "
"Configuration --> Helpdesk Teams` is enabled."
msgstr ""
"Si se crea un ticket de servicio de asistencia desde el chat, la "
"conversación de la que se generó aparecerá automáticamente como la "
"descripción del ticket. Lo mismo ocurre con la creación de una iniciativa."
#: ../../livechat/livechat.rst:124
#: ../../livechat/overview/responses.rst:0
msgid ""
"- For *leads*: the *CRM* application must be installed on your database."
msgstr ""
#: ../../livechat/overview/responses.rst:26
msgid ""
"To access the ticket or lead created from the chat, click on the shortcut "
"link."
msgstr ""
#: ../../livechat/overview/responses.rst:33
msgid ""
"Helpdesk tickets created from the chat automatically add the conversation as"
" a description of the ticket. The same goes for the creation of a lead."
msgstr ""
#: ../../livechat/overview/responses.rst:37
msgid "Send canned responses"
msgstr "Enviar respuestas guardadas"
#: ../../livechat/livechat.rst:126
#: ../../livechat/overview/responses.rst:40
msgid ""
"Canned responses allow you to create substitutes to generic sentences you "
"frequently use. Typing a word instead of several will save you a lot of "
"time. To add canned responses, go to :menuselection:`LIVE CHAT --> "
"Configuration --> Canned Responses` and create as many as you need to. Then,"
" to use them during a chat, simply type \":\" followed by the shortcut you "
"assigned."
"Canned responses allow you to have a full piece of text being placed when "
"you type a shortcut word. To create them, go to :menuselection:`Live Chat "
"--> Configuration --> Canned Responses`."
msgstr ""
"Las respuestas guardadas le permiten crear sustitutos a oraciones genéricas "
"que usa con frecuencia. Escribir una palabra en vez de varias le ahorrará "
"mucho tiempo. Para agregar respuestas guardadas, vaya a: menuselection: "
"`CHAT EN VIVO -> Configuración -> Respuestas guardadas` y cree todas las que"
" necesite. Luego, para usarlos durante un chat, simplemente escriba \":\" "
"seguido del atajo que asignó."
#: ../../livechat/livechat.rst:136
#: ../../livechat/overview/responses.rst:41
msgid ""
"You now have all of the tools needed to chat in live with your website "
"visitors, enjoy !"
"To use them during a conversation, simply type **:** followed by the "
"shortcut word you created."
msgstr ""
"Ahora tiene todas las herramientas necesarias para chatear en vivo con los "
"visitantes de su sitio web, ¡disfrútelo!"

1348
locale/es/LC_MESSAGES/manufacturing.po
View File

File diff suppressed because it is too large Load Diff

382
locale/es/LC_MESSAGES/marketing_automation.po Normal file
View File

@ -0,0 +1,382 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Lina Maria Avendaño Carvajal <lina8823@gmail.com>, 2020
# Raquel Iciarte <ric@odoo.com>, 2020
# Fabian <fabiananguiano@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Fabian <fabiananguiano@gmail.com>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: es\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../marketing_automation.rst:5
msgid "Marketing Automation"
msgstr "Automatización de marketing"
#: ../../marketing_automation/advanced.rst:3
msgid "Advanced"
msgstr "Avanzado"
#: ../../marketing_automation/advanced/understanding_metrics.rst:3
msgid "Understanding Metrics"
msgstr "Comprendiendo las métricas"
#: ../../marketing_automation/advanced/understanding_metrics.rst:4
msgid ""
"Metrics are values that help you measure progress and can be a powerful way "
"of linking your employees to goals."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:9
msgid ""
"When you create a workflow in Odoo, its visual content already shows metrics"
" in a graph form and in numbers."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:10
msgid "Let’s consider the example below:"
msgstr "Consideremos el ejemplo abajo:"
#: ../../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."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:20
msgid "A total number of 20 records match the criteria."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:28
msgid ""
"Out of those 20 records, 25 have become participants, in other words, they "
"have matched the criteria."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:36
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."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:41
msgid ""
"The filter here is applied to *all* activities. Leads that lose the tag in "
"the meantime will be excluded from later activities."
msgstr ""
#: ../../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*."
msgstr ""
#: ../../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."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:0
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."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:64
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 ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:65
msgid ""
"If a participant does not match the conditions, it will be added to "
"*Rejected*."
msgstr ""
#: ../../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."
msgstr ""
#: ../../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)."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:79
msgid ":doc:`../overview/automate_actions`"
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:80
msgid ":doc:`../overview/segment`"
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:81
msgid ":doc:`../overview/test`"
msgstr ""
#: ../../marketing_automation/overview.rst:3
msgid "Overview"
msgstr "Información general"
#: ../../marketing_automation/overview/automate_actions.rst:3
msgid "Automate Actions and Create a Workflow"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:4
msgid ""
"Automated workflows are a sign that you are building intelligent, data-"
"driven, multifaceted campaigns to enable the delivery of the right message, "
"to the right prospects, at the right time. It also speeds up processes and "
"creates a seamless experience for employees."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:9
msgid "Segment and create a campaign"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:10
msgid "Go to :menuselection:`Campaigns --> Create`."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:12
msgid ""
"In the example below, the *Marketing Automation* application is fully "
"integrated with *Contacts*."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:14
msgid ""
"But it can also be integrated with other apps like CRM, as long as they are "
"installed in your database."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:23
msgid ""
"Depending on the criteria, the *target model updates itself* while the "
"campaign is running. That means that every new record that meets the "
"criteria will be added to the workflow."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:25
msgid ""
"Example: a campaign starts for leads that have no salesman assigned. If at "
"some point, those leads get to have a salesman assigned to it, the campaign "
"will stop running."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:29
msgid "Create a parent activity and start to build a workflow"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:30
msgid "Click on *Add new activity*."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:37
msgid ""
"*Trigger* is the field to set for the activity to start to de deployed."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:39
msgid ""
"Adopt an *Expiry Duration* if you would like to stop actions from being "
"executed after a certain amount of time and in subsequence to the trigger."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:42
msgid ""
"Under *Domain* you can narrow down your target, even more, applying filters "
"for this specific activity."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:47
msgid "Add Child Activities"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:48
msgid ""
"A *child activity* is an action that will take place based on a condition."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:50
msgid ""
"You can either create or add a child activity if on the previous one: the "
"email was opened or not, the email was replied or not, the link was clicked "
"or not, the email bounced back."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:59
#: ../../marketing_automation/overview/test.rst:53
msgid ":doc:`segment`"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:3
msgid "Segment the Database with Filters"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:4
msgid "Filters let you reach a granular level of detail in your records."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:7
msgid "How to work with filters"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:8
msgid ""
"When working with filters, you will see that some of the rules have an arrow"
" button next to it, informing you that the parameter has more variables "
"within it."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:18
msgid ""
"More than one parameter line - *node* (+) - can be added under what is "
"called a *branch* (...)."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:19
msgid "To exclude a *node* or a *branch*, click on *Delete node* (x)."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:27
msgid ""
"Every time a new branch is created, you can choose if you would like the "
"records to match *all* criteria of the upcoming rules, or *any*, meaning one"
" rule or the other."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:32
msgid "Use cases"
msgstr "Casos de uso"
#: ../../marketing_automation/overview/segment.rst:34
msgid ""
"**Scenario**: narrow the target down to new opportunities in the pipeline."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:39
msgid "**Scenario**: narrow the target down to suppliers."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:44
msgid ""
"**Scenario**: narrow the leads down to the ones that contain a certain tag "
"name."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:49
msgid ""
"**Scenario**: narrow the target down to the attendees of a specific event "
"that purchase a specific category of ticket."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:55
msgid "**Scenario**: narrow the target down to the employees who have kids."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:60
msgid ""
"**Scenario**: narrow the target down to records with a helpdesk ticket "
"solved."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:66
#: ../../marketing_automation/overview/test.rst:52
msgid ":doc:`automate_actions`"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:67
msgid ":doc:`../../general/tags/take_tags`"
msgstr ""
#: ../../marketing_automation/overview/test.rst:3
msgid "Launch a Test and Start a Campaign"
msgstr ""
#: ../../marketing_automation/overview/test.rst:4
msgid ""
"Before starting a campaign, launching a test allows you to run the workflow "
"on a test contact and view the sequence of events in action, avoiding "
"mistakes."
msgstr ""
#: ../../marketing_automation/overview/test.rst:8
msgid "Launch a test"
msgstr "Lanzar un test"
#: ../../marketing_automation/overview/test.rst:9
msgid "Click on *Launch a test*."
msgstr ""
#: ../../marketing_automation/overview/test.rst:12
msgid ""
"Once you have selected the test contact, *Run* the parent activity and the "
"subsequent ones as needed. *Run* and *Stop* activities individually. To stop"
" the whole workflow click on *Stop*."
msgstr ""
#: ../../marketing_automation/overview/test.rst:22
msgid ""
"Launching a test does not add data to your metrics with the purpose of not "
"introducing wrong inputs to reports."
msgstr ""
#: ../../marketing_automation/overview/test.rst:27
msgid "Start and stop a workflow"
msgstr ""
#: ../../marketing_automation/overview/test.rst:28
msgid ""
"Click on *Start* to run the workflow, and on *Stop* to interrupt it. The "
"interruption and new start can happen at any moment. The current status will"
" be shown on the status bar."
msgstr ""
#: ../../marketing_automation/overview/test.rst:38
msgid "Participants and their specific workflow"
msgstr ""
#: ../../marketing_automation/overview/test.rst:39
msgid ""
"*Participants* are all the records that have ever been involved in the "
"campaign."
msgstr ""
#: ../../marketing_automation/overview/test.rst:47
msgid ""
"If you click on *Participants* and open a record, you will find the specific"
" activities the record went/are/will go through, as well as when the "
"workflow was triggered to him. If you wish to cancel an activity click on "
"*Cancel*."
msgstr ""

117
locale/es/LC_MESSAGES/mobile.po
View File

@ -3,14 +3,18 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Victoria Quesada <victoria.quesada@nybblegroup.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Diego de cos <diegodecos@hotmail.com>, 2018\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Victoria Quesada <victoria.quesada@nybblegroup.com>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -23,105 +27,22 @@ msgid "Mobile"
msgstr "Móvil"
#: ../../mobile/firebase.rst:8
msgid "Setup your Firebase Cloud Messaging"
msgstr ""
msgid "Push Notifications"
msgstr "Notificaciones automáticas"
#: ../../mobile/firebase.rst:10
msgid ""
"In order to have mobile notifications in our Android app, you need an API "
"key."
"As of Odoo 12.0, 13.0 or above, there is no more complex configuration to "
"enable push notifications in the mobile app."
msgstr ""
"Para tener notificaciones móviles en nuestra aplicación Android, necesita "
"una clave API "
"Para Odoo 12.0, 13.0 o superior, no hay configuración más compleja que "
"configurar las notificaciones automáticas en la app móvil. "
#: ../../mobile/firebase.rst:13
msgid ""
"If it is not automatically configured (for instance for On-premise or "
"Odoo.sh) please follow these steps below to get an API key for the android "
"app."
msgstr ""
#: ../../mobile/firebase.rst:18
msgid ""
"The iOS app doesn't support mobile notifications for Odoo versions < 12."
msgstr ""
"La aplicación iOS no soporta notificaciones móviles en Oddo para versiones "
">12"
#: ../../mobile/firebase.rst:22
msgid "Firebase Settings"
msgstr ""
#: ../../mobile/firebase.rst:25
msgid "Create a new project"
msgstr "Crear un nuevo proyecto"
#: ../../mobile/firebase.rst:27
msgid ""
"First, make sure you to sign in to your Google Account. Then, go to "
"`https://console.firebase.google.com "
"<https://console.firebase.google.com/>`__ and create a new project."
msgstr ""
#: ../../mobile/firebase.rst:34
msgid ""
"Choose a project name, click on **Continue**, then click on **Create "
"project**."
msgstr ""
"Elija un nombre de proyecto, seleccione **Continuar**, entonces selecciones "
"**Crear Proyecto**."
#: ../../mobile/firebase.rst:37
msgid "When you project is ready, click on **Continue**."
msgstr "Cuando su proyecto esté listo, seleccione **Continuar**."
#: ../../mobile/firebase.rst:39
msgid ""
"You will be redirected to the overview project page (see next screenshot)."
msgstr ""
#: ../../mobile/firebase.rst:43
msgid "Add an app"
msgstr "Agregar una aplicación"
#: ../../mobile/firebase.rst:45
msgid "In the overview page, click on the Android icon."
msgstr ""
#: ../../mobile/firebase.rst:50
msgid ""
"You must use \"com.odoo.com\" as Android package name. Otherwise, it will "
"not work."
msgstr ""
"Debe usar \"com.odoo.com\" como nombre de paquete Android. DE otro modo, no "
"funcionará."
#: ../../mobile/firebase.rst:56
msgid ""
"No need to download the config file, you can click on **Next** twice and "
"skip the fourth step."
msgstr ""
"No necesita descargar el archivo de configuración, puede seleccionar "
"*Siguiente** 2 veces y saltar al cuarto paso."
#: ../../mobile/firebase.rst:60
msgid "Get generated API key"
msgstr "Obtenga la API key generada"
#: ../../mobile/firebase.rst:62
msgid "On the overview page, go to Project settings:"
msgstr ""
#: ../../mobile/firebase.rst:67
msgid ""
"In **Cloud Messaging**, you will see the **API key** and the **Sender ID** "
"that you need to set in Odoo General Settings."
msgstr ""
#: ../../mobile/firebase.rst:74
msgid "Settings in Odoo"
msgstr "Configuraciones en Odoo"
#: ../../mobile/firebase.rst:76
msgid "Simply paste the API key and the Sender ID from Cloud Messaging."
"Simply go to :menuselection:`Settings --> General Settings --> Odoo Cloud "
"Notification (OCN)` and make sure that **Push Notifications** is checked."
msgstr ""
"Simplemente tiene que ir a :menuselection`Settings--> General Settings -- > "
"Odoo Notificaciones en la nube (OCN)` y asegúrese que esté tildada la opción"
" de notificaciones automáticas."

158
locale/es/LC_MESSAGES/planning.po Normal file
View File

@ -0,0 +1,158 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Lina Maria Avendaño Carvajal <lina8823@gmail.com>, 2020
# Jon Perez <jop@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Jon Perez <jop@odoo.com>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: es\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../planning.rst:5
msgid "Planning"
msgstr "Planificación"
#: ../../planning/overview.rst:3
msgid "Overview"
msgstr "Información general"
#: ../../planning/overview/duplicate_a_planning.rst:3
msgid "Create a Schedule and Make Encoding Easier"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:5
msgid ""
"Organize regular schedules or forecast projects in a long term basis. Create"
" shifts to manage your tasks, assign employees, and stay organized at a high"
" level."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:9
msgid "Organize your team by roles"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:11
msgid ""
"Go to :menuselection:`Configuration --> Roles --> Create`. Optionally, go to"
" the *Employees* application, select the respective employee, and under "
"*Work Information* select the *Default Planning Role*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:20
msgid "Make shifts recurrent"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:22
msgid ""
"While creating a shift, select *Repeat* and configure as needed, saving you "
"from the need of re-planning it."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:30
msgid ""
"Repeated shifts are generated for the next six months. A modification is "
"possible in :doc:`Developer mode <../../general/developer_mode/activate>`, "
"from *Settings*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:38
msgid "To duplicate a shift in the Gantt view, press CTRL + drag and drop."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:41
msgid "Save shifts as templates"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:43
msgid ""
"If creating a shift on the fly and know you might use that template in the "
"future, click on *Save as a Template*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:51
msgid ""
"To create a template in advance, go to :menuselection:`Configuration --> "
"Shifts Templates --> Create`."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:55
msgid "Duplicate a planning from the previous week"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:57
msgid ""
"When in the Gantt view, either under *Schedule by Employee, Role or "
"Project*, instead of re-planning shifts that have been planned before, "
"simply click on *Copy Previous Week*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:65
msgid ""
"The integration with the *Time off* and *Employee* applications, show you "
"grayed cells to the days when the employee does not work and is on vacation "
"time, for example."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:3
msgid "Send Planned Shifts and Give Employees Autonomy Over Shifts"
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:5
msgid ""
"If you are not on top of your tasks and shifts you might fall behind, losing"
" productivity. Allowing your employees to have a say over shifts helps you "
"to be on top of your workload, and gives them flexibility."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:10
msgid "Publish and send the planned week by email"
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:12
msgid ""
"Once you have your shifts planned, click on *Send Schedule*. Select *Include"
" Open shift* if you would like the *Unassigned* shifts to be seen."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:19
msgid ""
"Choose if you just want to *Publish* or *Publish and Send*. If you *Publish "
"and Send*, employees get an email that redirects them to their planned "
"tasks:"
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:26
msgid ""
"Employees will not be able to see shifts until they have been published."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:29
msgid "Let employees unassign themselves from shifts"
msgstr "Deje que los empleados se desasignen de turnos"
#: ../../planning/overview/send_planned_shifts.rst:31
msgid ""
"Go to *Configuration* and enable *Allow Unassignment*. From now on, when an "
"employee opens his tasks, he can indicate his unavailability clicking on *I "
"am unavailable*. The shift will be opened again, allowing someone else to "
"take it."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:44
msgid "Employees have portal access; users have access to the database."
msgstr ""

1603
locale/es/LC_MESSAGES/point_of_sale.po
View File

File diff suppressed because it is too large Load Diff

152
locale/es/LC_MESSAGES/portal.po
View File

@ -3,14 +3,19 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Pedro M. Baeza <pedro.baeza@gmail.com>, 2020
# Alejandro Kutulas <alk@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-23 12:10+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Alejandro Kutulas <alk@odoo.com>, 2018\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Alejandro Kutulas <alk@odoo.com>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -24,24 +29,17 @@ msgstr "Mi portal de Odoo"
#: ../../portal/my_odoo_portal.rst:8
msgid ""
"In this section of the portal you will find all the communications between "
"you and Odoo, documents such Quotations, Sales Orders, Invoices and your "
"Subscriptions."
"In this section of the portal, you will find all the communications between "
"you and Odoo: documents such as quotations, sales orders, invoices and "
"subscriptions."
msgstr ""
"En esta sección del portal encontrarás toda la comunicación entre tu y Odoo."
" Documentos tales como presupuestos, ordenes de venta, facturas y tus "
"subscripciones."
#: ../../portal/my_odoo_portal.rst:11
#: ../../portal/my_odoo_portal.rst:12
msgid ""
"To access this section you have to log with your username and password to "
"`Odoo <https://www.odoo.com/my/home>`__ . If you are already logged-in just "
"To access this section, you have to log with your username and password to "
"`Odoo <https://www.odoo.com/my/home>`_. If you are already logged in, just "
"click on your name on the top-right corner and select \"My Account\"."
msgstr ""
"Para acceder a esta sección tienes que iniciar sesión con tu nombre de "
"usuario y contraseña de `Odoo <https://www.odoo.com/my/home>`__ . Si es que "
"ya iniciaste sesión sólo haz clic en tu nombre en la esquina derecha arriba "
"y selecciona \"Mi Cuenta\"."
#: ../../portal/my_odoo_portal.rst:20
msgid "Quotations"
@ -50,34 +48,24 @@ msgstr "Presupuestos"
#: ../../portal/my_odoo_portal.rst:22
msgid ""
"Here you will find all the quotations sent to you by Odoo. For example, a "
"quotation can be generated for you after adding an Application or a User to "
"quotation can be generated for you after adding an application or a user to "
"your database or if your contract has to be renewed."
msgstr ""
"Aquí encontrarás todos los presupuestos enviados a tí por Odoo. Por ejemplo,"
" un presupuesto puede ser generado para tí después de añadir una aplicación "
"o un usuario a tu base de datos o si tu contrato tiene que ser renovado."
#: ../../portal/my_odoo_portal.rst:29
msgid ""
"The *Valid Until* column shows until when the quotation is valid; after that"
" date the quotation will be \"Expired\". By clicking on the quotation you "
"will see all the details of the offer, the pricing and other useful "
"information."
"The *Valid Until* column shows the date through which the quotation is "
"valid; after that date, the quotation will be \"Expired\". By clicking on "
"the quotation, you will see all the details of the offer, such as the "
"pricing and other useful information."
msgstr ""
"La columna *Valido Hasta* muestra hasta cuándo el presupuesto es válido; "
"después de esa fecha, el presupuesto será \"Expirado\". Al cliquear en el "
"presupuesto, verás todos los detalles de la oferta, el precio y otra "
"información valiosa."
#: ../../portal/my_odoo_portal.rst:36
msgid ""
"If you want to accept the quotation just click \"Accept & Pay\" and the "
"If you want to accept the quotation, just click \"Accept & Pay,\" and the "
"quote will get confirmed. If you don't want to accept it, or you need to ask"
" for some modifications, click on \"Ask Changes Reject\"."
" for some modifications, click on \"Ask Changes Reject.\""
msgstr ""
"Si quieres aceptar el presupuesto solo cliquea \"Acepta y Paga\" y el "
"presupuesto será confirmado. Si no quieres aceptarlo, o necesitas preguntar "
"por algunas modificaciones, cliquea en \"Pregunta Cambios Rechazar\"."
#: ../../portal/my_odoo_portal.rst:41
msgid "Sales Orders"
@ -85,19 +73,15 @@ msgstr "Pedidos de ventas"
#: ../../portal/my_odoo_portal.rst:43
msgid ""
"All your purchases within Odoo such as Upsells, Themes, Applications, etc. "
"will be registered under this section."
"All your purchases within Odoo (Upsells, Themes, Applications, etc.) will be"
" registered under this section."
msgstr ""
"Todas tus compras en Odoo tales como ventas adicionales, temas, "
"aplicaciones, etc. serán registradas bajo esta sección."
#: ../../portal/my_odoo_portal.rst:49
msgid ""
"By clicking on the sale order you can review the details of the products "
"By clicking on the sale order, you can review the details of the products "
"purchased and process the payment."
msgstr ""
"Al cliquear en la orden de venta puedes revisar el detalle de los productos "
"comprados y procesar el pago."
#: ../../portal/my_odoo_portal.rst:53
msgid "Invoices"
@ -105,109 +89,81 @@ msgstr "Facturas"
#: ../../portal/my_odoo_portal.rst:55
msgid ""
"All the invoices of your subscription(s), or generated by a sales order, "
"will be shown in this section. The tag before the Amount Due will indicate "
"you if the invoice has been paid."
"All the invoices of your subscriptions and/or sales orders will be shown in "
"this section. The tag before the Amount Due will indicate if the invoice has"
" been paid."
msgstr ""
"Todas las facturas de tu subscripciones, o generadas por una orden de venta,"
" serán mostradas en esta sección. La etiqueta antes del monto a pagar te "
"indicará si la factura ha sido pagada."
#: ../../portal/my_odoo_portal.rst:62
msgid ""
"Just click on the Invoice if you wish to see more information, pay the "
"invoice or download a PDF version of the document."
"Just click on the invoice if you wish to see more information, pay the "
"invoice, or download a PDF version of the document."
msgstr ""
"Solo haz clic en la factura si deseas ver más información, pagar la factura "
"o descargar una versión PDF del documento."
#: ../../portal/my_odoo_portal.rst:66
msgid "Tickets"
msgstr "Tickets"
msgstr "Entradas"
#: ../../portal/my_odoo_portal.rst:68
msgid ""
"When you submit a ticket through `Odoo Support "
"<https://www.odoo.com/help>`__ a ticket will be created. Here you can find "
"all the tickets that you have opened, the conversation between you and our "
"Agents, the Status of the ticket and the ID (# Ref)."
"When you submit a ticket through `Odoo Support <https://www.odoo.com/help>`,"
" a ticket will be created. Here you can find all the tickets that you have "
"opened, the conversations between you and our Agents, and the statuses and "
"IDs (# Ref) of the tickets."
msgstr ""
"Cuando envías un ticket a través `Odoo Support "
"<https://www.odoo.com/help>`__ un ticket será creado. Aquí puedes encontrar "
"todos los tickets que haz abierto, la conversación entre tu y tus Agentes, "
"Status del ticket y la ID (# Ref)."
#: ../../portal/my_odoo_portal.rst:77
#: ../../portal/my_odoo_portal.rst:76
msgid "Subscriptions"
msgstr "Suscripciones"
#: ../../portal/my_odoo_portal.rst:79
#: ../../portal/my_odoo_portal.rst:78
msgid ""
"You can access to your Subscription with Odoo from this section. The first "
"You can access your subscriptions with Odoo from this section. The first "
"page shows you the subscriptions that you have and their status."
msgstr ""
"Puedes acceder a tu Subcripción con Odoo desde esta sección. La primera "
"página te muestra las subscripciones que tienes y su status."
#: ../../portal/my_odoo_portal.rst:85
#: ../../portal/my_odoo_portal.rst:84
msgid ""
"By clicking on the Subscription you will access to all the details regarding"
" your plan: this includes the number of applications purchased, the billing "
"information and the payment method."
"By clicking on the subscription you will access all the details regarding "
"your plan: the number of applications purchased, the billing information, "
"and the payment method."
msgstr ""
"Al cliquear en la Subscripción tendrás acceso a todos los detalles respecto "
"a tu plan: esto incluye el número de aplicaciones compradas, la información "
"de factura y el método de pago."
#: ../../portal/my_odoo_portal.rst:89
#: ../../portal/my_odoo_portal.rst:88
msgid ""
"To change the payment method click on \"Change Payment Method\" and enter "
"To change the payment method, click on \"Change Payment Method\" and enter "
"the new credit card details."
msgstr ""
"Para cambiar el método de pago haz clic en \"Cambiar Método de Pago\" y "
"entra los detalles de la nueva tarjeta de crédito."
#: ../../portal/my_odoo_portal.rst:95
#: ../../portal/my_odoo_portal.rst:94
msgid ""
"If you want to remove the credit cards saved, you can do it by clicking on "
"\"Manage you payment methods\" at the bottom of the page. Click then on "
"\"Delete\" to delete the payment method."
"If you want to remove the credit cards that are saved, you can do so by "
"clicking on \"Manage your payment methods\" at the bottom of the page. Click"
" \"Delete\" to delete the payment method."
msgstr ""
"Si quieres remover las tarjetas de crédito grabadas, lo puedes hacer al "
"cliquear en \"Administra tus métodos de pago\" al fondo de la página. Haz "
"clic en \"Borrar\" para borrar este método de pago."
#: ../../portal/my_odoo_portal.rst:102
msgid ""
"At the date of the next invoice, if there is no payment information provided"
" or if your credit card has expired, the status of your subscription will "
"change to \"To Renew\". You will then have 7 days to provide a valid method"
" of payment. After this delay, the subscription will be closed and you will "
"change to \"To Renew\". You will then have 7 days to provide a valid method "
"of payment. After this delay, the subscription will be closed, and you will "
"no longer be able to access the database."
msgstr ""
"A la fecha de la próxima factura, si es que no hay información del pago "
"disponible, o si tu tarjeta de crédito ha expirado, el status de tu "
"subscripción cambiará a \"Para renovar\". Luego tendrás 7 días para proveer "
"un método de pago válido. Después de esto, la subscripción será cerrada y no"
" tendrás más acceso a la base de datos."
#: ../../portal/my_odoo_portal.rst:109
#: ../../portal/my_odoo_portal.rst:108
msgid "Success Packs"
msgstr "Success Packs"
#: ../../portal/my_odoo_portal.rst:110
#: ../../portal/my_odoo_portal.rst:109
msgid ""
"With a Success Pack/Partner Success Pack, you are assigned an expert to "
"provide unique personalized assistance to help you customize your solution "
"and optimize your workflows as part of your initial implementation. These "
"hours never expire allowing you to utilize them whenever you need support."
"hours never expire, allowing you to utilize them whenever you need support."
msgstr ""
"Con un Success Pack/Socio Success Pack, se te asigna un experto que provee "
"asistencia única y personalizada para ayudarte a customizar tu solución y "
"optimizar tus flow de trabajo como parte de tu implementación inicial. Estas"
" horas nunca expiran, permitiéndote utilizarlas cuando necesites soporte."
#: ../../portal/my_odoo_portal.rst:116
#: ../../portal/my_odoo_portal.rst:115
msgid ""
"If you need information about how to manage your database see "
":ref:`db_online`"

11
locale/es/LC_MESSAGES/practical.po
View File

@ -3,14 +3,17 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Pablo Rojas <rojaspablo88@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Pablo Rojas <rojaspablo88@gmail.com>, 2018\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Pablo Rojas <rojaspablo88@gmail.com>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"

2796
locale/es/LC_MESSAGES/project.po
View File

File diff suppressed because it is too large Load Diff

589
locale/es/LC_MESSAGES/purchase.po
View File

@ -4,24 +4,23 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Lina Maria Avendaño Carvajal <lina8823@gmail.com>, 2018
# Jesús Alan Ramos Rodríguez <alan.ramos@jarsa.com.mx>, 2018
# Jose Manuel <admin@jaboweb.com>, 2018
# Pablo Rojas <rojaspablo88@gmail.com>, 2018
# AleEscandon <alejandra.escandon@jarsa.com.mx>, 2018
# Fairuoz Hussein Naranjo <l92hunaf@gmail.com>, 2018
# Martin Trigaux, 2018
# Carlos Lopez <celm1990@hotmail.com>, 2018
# Jon Perez <jop@odoo.com>, 2019
# Lina Maria Avendaño Carvajal <lina8823@gmail.com>, 2020
# Fairuoz Hussein Naranjo <l92hunaf@gmail.com>, 2020
# Jon Perez <jop@odoo.com>, 2020
# Martin Trigaux, 2020
# Jesús Alan Ramos Rodríguez <alan.ramos@jarsa.com.mx>, 2020
# Jose Manuel <admin@jaboweb.com>, 2020
# Pablo Rojas <rojaspablo88@gmail.com>, 2020
# AleEscandon <alejandra.escandon@jarsa.com.mx>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 12.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-11-07 15:38+0100\n"
"PO-Revision-Date: 2018-10-19 08:15+0000\n"
"Last-Translator: Jon Perez <jop@odoo.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: AleEscandon <alejandra.escandon@jarsa.com.mx>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -56,7 +55,7 @@ msgstr ""
#: ../../purchase/purchases/rfq/3_way_matching.rst:18
#: ../../purchase/purchases/rfq/analyze.rst:24
#: ../../purchase/purchases/rfq/approvals.rst:9
#: ../../purchase/purchases/rfq/bills.rst:31
#: ../../purchase/purchases/rfq/bills.rst:10
#: ../../purchase/purchases/rfq/create.rst:13
#: ../../purchase/purchases/rfq/lock_orders.rst:9
#: ../../purchase/purchases/rfq/reception.rst:14
@ -97,8 +96,8 @@ msgstr ""
#: ../../purchase/purchases/master/import.rst:33
msgid ""
"`Template download "
"<https://docs.google.com/spreadsheets/d/1N8c_eejLV_8NhYMGCfZau_oGCnRkUIT9nwdX7n0shhY/edit#gid=964193981>`__"
":download:`Click here to download the template "
"<../../../_static/example_files/vendor_pricelists_template.csv>`"
msgstr ""
#: ../../purchase/purchases/master/suppliers.rst:3
@ -415,7 +414,7 @@ msgstr ""
#: ../../purchase/purchases/rfq/3_way_matching.rst:9
msgid ""
"To define whether the vendor bill should be paid or not, you can use what we"
" call *3-way matching*. It refers to the comparaison of the information "
" call *3-way matching*. It refers to the comparison of the information "
"appearing on the *Purchase Order*, the *Vendor Bill* and the *Receipt*."
msgstr ""
@ -662,450 +661,55 @@ msgid "Once approved, the purchase order follows the normal process."
msgstr "Una vez aprobada, la orden de compra sigue el proceso normal."
#: ../../purchase/purchases/rfq/bills.rst:3
msgid "Control supplier bills"
msgstr ""
msgid "Bill Control"
msgstr "Control de Factura"
#: ../../purchase/purchases/rfq/bills.rst:5
msgid ""
"The **Purchase** application allows you to manage your purchase orders, "
"incoming products, and vendor bills all seamlessly in one place."
"With Odoo, you can define a setting to help the control of your bills. *Bill"
" Control* lets you choose if the supplier sends you the bill before or after"
" you receive the goods."
msgstr ""
"El módulo de **Compras** permite que usted maneje las órdenes de compras, "
"los productos entrantes y las facturas de los proveedores, todo a la "
"perfección en un mismo lugar. "
#: ../../purchase/purchases/rfq/bills.rst:8
#: ../../purchase/purchases/rfq/bills.rst:12
msgid ""
"If you want to set up a vendor bill control process, the first thing you "
"need to do is to have purchase data in Odoo. Knowing what has been purchased"
" and received is the first step towards understanding your purchase "
"management processes."
"For this feature to work, go to :menuselection:`Purchases --> Configuration "
"--> Settings` and select which way you want to control your bills."
msgstr ""
"Si desea establecer un proceso de control de factura de proveedor, lo "
"primero que hay que hacer es tener datos de la compra en Odoo. Saber lo que "
"se ha comprado y recibido es el primer paso hacia la comprensión de sus "
"procesos de gestión de compras."
#: ../../purchase/purchases/rfq/bills.rst:13
msgid "Here is the standard work flow in Odoo:"
msgstr "Aquí está un flujo de trabajo estándar de Odoo:"
#: ../../purchase/purchases/rfq/bills.rst:20
msgid "Change the control policy"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:15
#: ../../purchase/purchases/rfq/bills.rst:22
msgid ""
"You begin with a **Request for Quotation (RFQ)** to send out to your "
"vendor(s)."
"While the setting above will be your default method of bill control, you can"
" always select which way you want to invoice your product on each product "
"page under the *Purchase* tab."
msgstr ""
"Usted empezará con las **Solicitudes de Presupuesto (RfQ)** que se enviarán "
"a sus proveedor(es)."
#: ../../purchase/purchases/rfq/bills.rst:18
#: ../../purchase/purchases/rfq/bills.rst:26
msgid ""
"Once the vendor has accepted the RFQ, confirm the RFQ into a **Purchase "
"Order (PO)**."
"You might want to use different settings for different types of products."
msgstr ""
"Una vez que el proveedor haya aceptado la RfQ, es necesario confirmar la "
"entrada de RfQ en las **Órdenes de Compra (PO)**."
#: ../../purchase/purchases/rfq/bills.rst:21
msgid ""
"Confirming the PO generates an **Incoming Shipment** if you purchased any "
"stockable products."
msgstr ""
"Confirmando la PO se generará un **Envío entrante**, en caso de adquirir "
"cualquiera de los productos almacenables."
#: ../../purchase/purchases/rfq/bills.rst:24
msgid ""
"Upon receiving a **Vendor Bill** from your Vendor, validate the bill with "
"products received in the previous step to ensure accuracy."
msgstr ""
"Al recibir una **Factura de proveedor** de su proveedor, hay que validar la "
"cuenta con productos recibidos en el paso anterior para asegurar la "
"precisión."
#: ../../purchase/purchases/rfq/bills.rst:27
msgid ""
"This process may be done by three different people within the company, or "
"only one."
msgstr ""
"Este proceso puede estar hecho por tres diferentes personas de la compañía o"
" por una sola. "
#: ../../purchase/purchases/rfq/bills.rst:34
msgid "Installing the Purchase and Inventory applications"
msgstr "Instalación de Solicitudes de Compra e Inventarios"
msgid "Verify your Vendor Bill"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:36
msgid ""
"From the **Apps** application, search for the **Purchase** module and "
"install it. Due to certain dependencies, installing purchase will "
"automatically install the **Inventory** and **Accounting** applications."
"If you didn’t receive any of your product yet on *Purchase Order* under the "
"*Shipment* tab,"
msgstr ""
"Desde el módulo de **Aplicaciones**, busque el módulo de **Compras** e "
"instálelo. Debido a ciertas dependencias, la instalación del módulo de "
"compras instalará el módulo de **Almacén** y el de **Contabilidad**."
#: ../../purchase/purchases/rfq/bills.rst:41
msgid "Creating products"
msgstr "Creando productos"
#: ../../purchase/purchases/rfq/bills.rst:43
msgid ""
"Creating products in Odoo is essential for quick and efficient purchasing "
"within Odoo. Simply navigate to the **Products** submenu under **Purchase**,"
" and click **Create**."
"Depending on the billing policy defined above. If you're supposed to be "
"billed based on ordered quantity, Odoo will suggest a bill for the number of"
" units ordered. If you're supposed to be billed based on the received "
"quantities, Odoo will suggest a bill for 0 as shown above."
msgstr ""
"La creación de productos en Odoo es esencial para la compra rápida y "
"eficiente dentro Odoo. Simplemente navegar en el submenú de los "
"**Productos** bajo **Compra** y haga clic en **Crear**."
#: ../../purchase/purchases/rfq/bills.rst:50
msgid ""
"When creating the product, Pay attention to the **Product Type** field, as "
"it is important:"
msgstr ""
"Cuando se crea un producto, es necesario poner atención al campo del **Tipo "
"de Producto**, ya que es importante: "
#: ../../purchase/purchases/rfq/bills.rst:53
msgid ""
"Products that are set as **Stockable** or **Consumable** will allow you to "
"keep track of their inventory levels. These options imply stock management "
"and will allow for receiving these kinds of products."
msgstr ""
"Los productos que se configuran como **Almacenable** o **Consumible** le "
"permitirá realizar un seguimiento de sus niveles de almacén. Estas opciones "
"implican la gestión de almacenes y permitirán la recepción de este tipo de "
"productos."
#: ../../purchase/purchases/rfq/bills.rst:58
msgid ""
"Conversely, products that are set as a **Service** or **Digital Product** "
"will not imply stock management, simply due to the fact that there is no "
"inventory to manage. You will not be able to receive products under either "
"of these designations."
msgstr ""
"Por el contrario, los productos que se configuran como un **Servicio** o un "
"**Producto Digital** no aplican en la gestión de almacén, simplemente por el"
" hecho de que no existe un inventario de manejar. Usted no será capaz de "
"recibir los productos en cualquiera de estas designaciones."
#: ../../purchase/purchases/rfq/bills.rst:64
msgid ""
"It is recommended that you create a **Miscellaneous** product for all "
"purchases that occur infrequently and do not require inventory valuation or "
"management. If you create such a product, it is recommend to set the product"
" type to **Service**."
msgstr ""
"Se recomienda crear un **Diverso Producto** para todas las compras que se "
"producen con poca frecuencia y no requieren de valoración o la gestión de "
"inventarios. Si crea un producto de este tipo, se recomienda establecer el "
"tipo de producto en **Servicio**."
#: ../../purchase/purchases/rfq/bills.rst:70
msgid "Managing your Vendor Bills"
msgstr "Gestionando las cuentas de sus vendedores"
#: ../../purchase/purchases/rfq/bills.rst:73
msgid "Purchasing products or services"
msgstr "Comprando productos o servicios"
#: ../../purchase/purchases/rfq/bills.rst:75
msgid ""
"From the purchase application, you can create a purchase order with as many "
"products as you need. If the vendor sends you a confirmation or quotation "
"for an order, you may record the order reference number in the **Vendor "
"Reference** field. This will enable you to easily match the PO with the the "
"vendor bill later (as the vendor bill will probably include the Vendor "
"Reference)"
msgstr ""
"A partir de la solicitud de compra, se puede crear una orden de compra con "
"tantos productos como sea necesario. Si el proveedor le envía una "
"confirmación o una cita para un pedido, puede registrar el número de "
"referencia del pedido en el campo de **Referencia del Proveedor**. Esto le "
"permitirá hacer coincidir fácilmente el PO con la factura del proveedor "
"después (como la factura de proveedor probablemente incluirá la Referencia "
"del Proveedor)"
#: ../../purchase/purchases/rfq/bills.rst:85
msgid ""
"Validate the purchase order and receive the products from the **Inventory** "
"application."
msgstr ""
"Validar el pedido y recibir los productos desde el módulo de **Almacenes**. "
#: ../../purchase/purchases/rfq/bills.rst:89
msgid "Receiving Products"
msgstr "Recibiendo productos"
#: ../../purchase/purchases/rfq/bills.rst:91
msgid ""
"If you purchased any stockable products that you manage the inventory of, "
"you will need to receive the products from the **Inventory** application "
"after you confirm a purchase order. From the **Inventory** dashboard, you "
"should see a button linking you directly to the transfer of products. This "
"button is outlined in red below:"
msgstr ""
"Si ha adquirido cualquier producto almacenable que administra el inventario,"
" tendrá que recibir los productos desde el módulo de **Almacén** después de "
"que usted confirme una orden de compra. Desde el tablero de **Almacén**, "
"debería ver un botón que une directamente a la transferencia de productos. "
"Este botón se indica en rojo a continuación:"
#: ../../purchase/purchases/rfq/bills.rst:100
msgid ""
"Navigating this route will take you to a list of all orders awaiting to be "
"received."
msgstr ""
"Navegando por esta ruta le llevará una lista de todos los pedidos en espera "
"de ser recibidos."
#: ../../purchase/purchases/rfq/bills.rst:106
msgid ""
"If you have a lot of awaiting orders, apply a filter using the search bar in"
" the upper right. With this search bar, you may filter based on the "
"**Vendor** (or **Partner**), the product, or the source document, also known"
" as the reference of your purchase order. You also have the capability to "
"group the orders by different criteria under **Group By**. Selecting an item"
" from this list will open the following screen where you then will receive "
"the products."
msgstr ""
"Si usted tiene varias órdenes en espera, debe de aplicar un filtro "
"utilizando la barra de búsqueda en la parte superior derecha. Con esta barra"
" de búsqueda, es posible acceder a un filtro basado en el **Proveedor** (o "
"**Socio**), el producto o el documento de origen, también conocido como la "
"referencia de la orden de compra. Usted también tiene la capacidad de "
"agrupar los pedidos por diferentes criterios bajo el nombre de **Grupo "
"Por**. Al seleccionar un elemento de esta lista se abrirá la siguiente "
"pantalla en la que a continuación, recibirá los productos. "
#: ../../purchase/purchases/rfq/bills.rst:117
msgid "Purchasing **Service** products does not trigger a delivery order."
msgstr ""
"La compra del **Servicio** de productos no desencadena una orden de entrega."
#: ../../purchase/purchases/rfq/bills.rst:120
msgid "Managing Vendor Bills"
msgstr "Gestionando las cuentas de sus vendedores"
#: ../../purchase/purchases/rfq/bills.rst:122
msgid ""
"When you receive a **Vendor Bill** for a previous purchase, be sure to "
"record it in the **Purchases** application under the **Control Menu**. You "
"need to create a new vendor bill even if you already registered a purchase "
"order."
msgstr ""
"Cuando reciba una **Factura de Proveedor** para una compra anterior, "
"asegúrese de anotar en el módulo de **Compras** bajo el **Menú de Control**."
" Es necesario crear una nueva factura de proveedor, incluso si ya está "
"registrada una orden de compra."
#: ../../purchase/purchases/rfq/bills.rst:130
msgid ""
"The first thing you will need to do upon creating a **Vendor Bill** is to "
"select the appropriate **Vendor** as this will also pull up any associated "
"accounting or pricelist information. From there, you can choose to specify "
"any one or multiple purchase orders to populate the vendor bill with. When "
"you select a purchase order from the list, Odoo will pull any uninvoiced "
"products associated to that purchase order and automatically populate that "
"information below. If you are having a hard time finding the appropriate "
"vendor bill, you may search through the list by inputting the vendor "
"reference number or your internal purchase order number."
msgstr ""
"Lo primero que tendrá que hacer al crear una **Factura de Proveedor**, es "
"seleccionar al **Proveedor** adecuado ya que esto también se asocia a "
"cualquier asociado contable o a la información de lista de precios. A partir"
" de ahí, se puede optar por especificar cualquiera o varias órdenes de "
"compra para llenar la factura del proveedor con. Al seleccionar una orden de"
" compra de la lista, Odoo empujará cualquier producto no facturado ni "
"asociado a la orden de compra y rellenará automáticamente la información a "
"continuación. Si usted está teniendo dificultades para encontrar la factura "
"del proveedor correspondiente, puede buscar a través de la lista "
"introduciendo el número de referencia del proveedor o su número de orden de "
"compra interna."
#: ../../purchase/purchases/rfq/bills.rst:144
msgid ""
"While the invoice is in draft state, you can make any modifications you need"
" (i.e. remove or add product lines, modify quantities, and change prices)."
msgstr ""
"Mientras que la factura está en estado de borrador, puede hacer las "
"modificaciones necesarias (es decir, quitar o añadir líneas de productos, "
"modificar cantidades, y cambiar los precios)."
#: ../../purchase/purchases/rfq/bills.rst:149
msgid "Your vendor may send you several bills for the same purchase order if:"
msgstr ""
"Su proveedor puede enviarle varias facturas para la misma orden de compra "
"sí:"
#: ../../purchase/purchases/rfq/bills.rst:151
msgid ""
"Your vendor is in back-order and is sending you invoices as they ship the "
"products."
msgstr ""
"Su proveedor está en la parte trasera de la orden y usted está el envío de "
"facturas, ya que se envían los productos."
#: ../../purchase/purchases/rfq/bills.rst:154
msgid "Your vendor is sending you a partial bill or asking for a deposit."
msgstr "Su proveedor le envía una factura parcial o pregunta por un depósito."
#: ../../purchase/purchases/rfq/bills.rst:156
msgid ""
"Every time you record a new vendor bill, Odoo will automatically populate "
"the product quantities based on what has been received from the vendor. If "
"this value is showing a zero, this means that you have not yet received this"
" product and simply serves as a reminder that the product is not in hand and"
" you may need to inquire further into this. At any point in time, before you"
" validate the vendor bill, you may override this zero quantity."
msgstr ""
"Cada vez que se graba una nueva factura de proveedor, Odoo rellenará "
"automáticamente las cantidades de productos en base a lo que se ha recibido "
"del proveedor. Si este valor está mostrando un cero, esto significa que "
"usted todavía no ha recibido este producto y simplemente sirve como un "
"recordatorio de que el producto no está en la mano y es posible que tenga "
"que investigar más a fondo de esto. En cualquier punto en el tiempo, antes "
"de validar la factura de proveedor, puede anular esta cantidad cero."
#: ../../purchase/purchases/rfq/bills.rst:165
msgid "Vendor Bill Matching"
msgstr "Facturas de Proveedor Acompañadas"
#: ../../purchase/purchases/rfq/bills.rst:168
msgid "What to do if your vendor bill does not match what you received"
msgstr ""
"¿Qué hacer si su factura de proveedor no coincide con lo que ha recibido?"
#: ../../purchase/purchases/rfq/bills.rst:170
msgid ""
"If the bill you receive from the vendor has different quantities than what "
"Odoo automatically populates as quantities, this could be due to several "
"reasons:"
msgstr ""
"Si la factura que reciba del proveedor tiene diferentes cantidades que las "
"cantidades puestas automáticamente por Odoo, esto podría ser debido a varias"
" razones:"
#: ../../purchase/purchases/rfq/bills.rst:174
msgid ""
"The vendor is incorrectly charging you for products and/or services that you"
" have not ordered."
msgstr ""
"El proveedor le está cobrando de forma incorrecta los productos y/o "
"servicios que usted no haya solicitado."
#: ../../purchase/purchases/rfq/bills.rst:177
msgid ""
"The vendor is billing you for products that you might not have received yet,"
" as the invoicing control may be based on ordered or received quantities."
msgstr ""
"El proveedor le está facturando para los productos que es posible que no "
"haya recibido todavía, como el control de la facturación puede basarse en "
"cantidades solicitadas o recibidas."
#: ../../purchase/purchases/rfq/bills.rst:181
msgid "Or the vendor did not bill you for previously purchased products."
msgstr "O el proveedor no le facturará los productos previamente adquiridos."
#: ../../purchase/purchases/rfq/bills.rst:183
msgid ""
"In these instances it is recommended that you verify that the bill, and any "
"associated purchase order to the vendor, are accurate and that you "
"understand what you have ordered and what you have already received."
msgstr ""
"En estos casos se recomienda que compruebe que la factura, y cualquier orden"
" de compra asociada al proveedor, sea precisa y que entienda lo que usted ha"
" pedido y lo que haya recibido."
#: ../../purchase/purchases/rfq/bills.rst:187
msgid ""
"If you are unable to find a purchase order related to a vendor bill, this "
"could be due to one of a few reasons:"
msgstr ""
"Si no puede encontrar una orden de compra relacionada con la factura de "
"proveedor, esto podría deberse a una de varias razones:"
#: ../../purchase/purchases/rfq/bills.rst:190
msgid ""
"The vendor has already invoiced you for this purchase order, therefore it is"
" not going to appear anywhere in the selection."
msgstr ""
"El proveedor ya le ha facturado por esta orden de compra, por lo que no va a"
" aparecer en cualquier parte de la selección."
#: ../../purchase/purchases/rfq/bills.rst:193
msgid ""
"Someone in the company forgot to record a purchase order for this vendor."
msgstr ""
"Alguien en la empresa se olvidó de registrar una orden de compra para este "
"proveedor."
#: ../../purchase/purchases/rfq/bills.rst:196
msgid "Or the vendor is charging you for something you did not order."
msgstr "O el proveedor le está cobrando algo que usted no pidió. "
#: ../../purchase/purchases/rfq/bills.rst:199
msgid "How product quantities are managed"
msgstr "¿Cómo se manejan las cantidades de productos?"
#: ../../purchase/purchases/rfq/bills.rst:201
msgid ""
"By default, services are managed based on ordered quantities, while "
"stockables and consumables are managed based on received quantities."
msgstr ""
"Por defecto, los servicios se gestionan en base a cantidades pedidas, "
"mientras los almacenables y consumibles se gestionan sobre la base de las "
"cantidades recibidas."
#: ../../purchase/purchases/rfq/bills.rst:204
msgid ""
"If you need to manage products based on ordered quantities over received "
"quantities, you will need to enable **Debug Mode** from the **About Odoo** "
"information. Once debug mode is activated, select the product(s) you wish to"
" modify, and you should see a new field appear, labeled **Control Purchase "
"Bills**."
msgstr ""
"Si usted necesita para administrar los productos basados en cantidades "
"pedidas más de las cantidades recibidas, necesitará habilitar el **Modo de "
"depuración** de la información **Sobre Odoo**. Una vez que se activa el modo"
" de depuración, seleccione el producto(s) que desea modificar, y usted "
"debería ver aparecer un nuevo campo, con la etiqueta **Factura de control de"
" compra**."
#: ../../purchase/purchases/rfq/bills.rst:213
msgid ""
"You can then change the default management method for the selected product "
"to be based on either:"
msgstr ""
"A continuación, puede cambiar el método de gestión predeterminada para el "
"producto seleccionado a basarse en cualquiera:"
#: ../../purchase/purchases/rfq/bills.rst:216
msgid "Ordered quantities"
msgstr "Cantidades pedidas"
#: ../../purchase/purchases/rfq/bills.rst:218
msgid "Received quantities"
msgstr "Cantidades recibidas"
#: ../../purchase/purchases/rfq/bills.rst:221
msgid "Batch Billing"
msgstr "Facturación por lotes"
#: ../../purchase/purchases/rfq/bills.rst:223
msgid ""
"When creating a vendor bill and selecting the appropriate purchase order, "
"you may continue to select additional purchase orders and Odoo will add the "
"additional line items from that purchase order. If you have not deleted the "
"previous line items from the first purchase order the bill will be linked to"
" all the appropriate purchase orders."
msgstr ""
"Al crear una factura de proveedor y la selección de la orden de compra "
"apropiada, puede continuar para seleccionar las órdenes de compra "
"adicionales y Odoo agregará las partidas adicionales de esa orden de compra."
" Si no ha eliminado las partidas anteriores de la primera orden de compra la"
" factura se vinculará a todas las órdenes de compra correspondientes."
#: ../../purchase/purchases/rfq/cancel.rst:3
msgid "Cancel a purchase order"
@ -1317,106 +921,7 @@ msgstr ""
" marcha, haga clic en **Crear y Editar**. En el campo **Fecha de pedido**, "
"seleccione la fecha en la que desea continuar con el orden real."
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Receipt"
msgstr "Recepción"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Incoming Shipments"
msgstr "Envíos a recibir"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Vendor"
msgstr "Proveedor"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "You can find a vendor by its Name, TIN, Email or Internal Reference."
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Vendor Reference"
msgstr "Referencia de proveedor"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"Reference of the sales order or bid sent by the vendor. It's used to do the "
"matching when you receive the products as this reference is usually written "
"on the delivery order sent by your vendor."
msgstr ""
"Referencia del pedido de venta o la oferta enviada por el proveedor. Se "
"utiliza para hacer la correspondencia cuando usted recibe los productos, "
"esta referencia se suele escribir en la orden de entrega enviado por el "
"proveedor."
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Order Date"
msgstr "Fecha de pedido"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"Depicts the date where the Quotation should be validated and converted into "
"a purchase order."
msgstr ""
"Representa la fecha en que el presupuesto debe ser validado y se convierte "
"en una orden de compra."
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Source Document"
msgstr "Documento origen"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"Reference of the document that generated this purchase order request (e.g. a"
" sales order)"
msgstr ""
"Referencia del documento que generó esta solicitud de pedido de compra (por "
"ejemplo, un pedido de cliente)"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Deliver To"
msgstr "Entregar a"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "This will determine operation type of incoming shipment"
msgstr "Esto determinará el tipo de operación del envío entrante"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Drop Ship Address"
msgstr "Dirección Drop Ship"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"Put an address if you want to deliver directly from the vendor to the "
"customer. Otherwise, keep empty to deliver to your own company."
msgstr ""
"Ponga una dirección si desea entregar directamente desde el proveedor al "
"cliente. De lo contrario, mantenga vacía para entregar a su propia compañía."
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Destination Location Type"
msgstr "Tipo de ubicación de destino"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Technical field used to display the Drop Ship Address"
msgstr "Campo técnico utilizado para mostrar la dirección de envió directo"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Incoterm"
msgstr "Incoterm"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"International Commercial Terms are a series of predefined commercial terms "
"used in international transactions."
msgstr ""
"Los términos de comercio internacional son una serie de condiciones "
"comerciales usadas en las transacciones internacionales."
#: ../../purchase/purchases/rfq/create.rst:32
msgid "View *Request for Quotation* in our Online Demonstration"
msgstr "Vista de la *Solicitud de Cotización* en la demostración en línea"
#: ../../purchase/purchases/rfq/create.rst:34
#: ../../purchase/purchases/rfq/create.rst:28
msgid ""
"In **Products**, click on Add an item. Select the product you wish to order "
"in the **Product** menu. Specify the **Quantity** by inserting the number "
@ -1438,7 +943,7 @@ msgstr ""
"correo electrónico sea especifica para este proveedor o introduzca uno "
"nuevo)."
#: ../../purchase/purchases/rfq/create.rst:48
#: ../../purchase/purchases/rfq/create.rst:40
msgid ""
"After having clicked on **Send**, you will notice that the RFQ's status will"
" switch from **Draft** to **RFQ Sent**."
@ -1446,7 +951,7 @@ msgstr ""
"Después de haber hecho clic en **Enviar**, usted se dará cuenta de que el "
"estado de la petición de oferta pasará de **Borrador** a **RFQ enviados**."
#: ../../purchase/purchases/rfq/create.rst:54
#: ../../purchase/purchases/rfq/create.rst:46
msgid ""
"Once your supplier has replied with an offer, update the RfQ by clicking on "
"**Edit** to fit the quotation (prices, taxes, expected delivery lead time, "
@ -1457,7 +962,7 @@ msgstr ""
" impuestos, plazo de entrega previsto, condiciones de pago, etc.), a "
"continuación, haga clic en **Guardar** para emitir una Orden de Compra."
#: ../../purchase/purchases/rfq/create.rst:59
#: ../../purchase/purchases/rfq/create.rst:51
msgid ""
"To proceed with the order, click on **Confirm Order** to send the order to "
"the supplier. The RfQ's status will switch to **Purchase Order**."
@ -1465,7 +970,7 @@ msgstr ""
"Para continuar con la orden, haga clic en **Confirmar Orden** para enviar el"
" pedido al proveedor. El estado del RfQ cambiará a **Orden de Compra**."
#: ../../purchase/purchases/rfq/create.rst:65
#: ../../purchase/purchases/rfq/create.rst:57
msgid ""
"The status of the RfQ will change to PURCHASE ORDER. Tabs in the upper right"
" corner of the order will show 1 Shipment and 0 Invoice."
@ -2302,7 +1807,7 @@ msgid ""
msgstr ""
#: ../../purchase/replenishment/flows/setup_stock_rule.rst:33
msgid "See also: :doc:`../../../inventory/management/misc/schedulers`"
msgid "See also: :doc:`../../../inventory/management/planning/schedulers`"
msgstr ""
#: ../../purchase/replenishment/flows/setup_stock_rule.rst:35

466
locale/es/LC_MESSAGES/quality.po Normal file
View File

@ -0,0 +1,466 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Jesús Alan Ramos Rodríguez <alan.ramos@jarsa.com.mx>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Jesús Alan Ramos Rodríguez <alan.ramos@jarsa.com.mx>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: es\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../quality.rst:5
msgid "Quality"
msgstr "Calidad"
#: ../../quality/alert.rst:3
msgid "Alert"
msgstr "Alerta"
#: ../../quality/alert/alert_mo.rst:3
msgid "Generate a Quality Alert from a Manufacturing Order"
msgstr ""
#: ../../quality/alert/alert_mo.rst:5
msgid ""
"Speaking of manufacturing orders, you have two different situations to "
"consider in Odoo. Those two will result in two different processes:"
msgstr ""
#: ../../quality/alert/alert_mo.rst:8
msgid "You work with a simple manufacturing flow;"
msgstr ""
#: ../../quality/alert/alert_mo.rst:10
msgid "You work with a complex manufacturing flow that includes routings."
msgstr ""
#: ../../quality/alert/alert_mo.rst:13
msgid "Simple manufacturing flow"
msgstr ""
#: ../../quality/alert/alert_mo.rst:15
msgid ""
"If you work with simple manufacturing orders, the *Quality Alerts* will be "
"launched from the manufacturing order itself. When manufacturing a product "
"for which you need to process quality controls, a button *Quality Alert* "
"will appear on the top of your manufacturing order."
msgstr ""
#: ../../quality/alert/alert_mo.rst:23
msgid ""
"By clicking on the button, you can specify the quality problem that arose "
"during the process."
msgstr ""
#: ../../quality/alert/alert_mo.rst:29
msgid ""
"If one of the quality checks failed, the button will be highlighted on the "
"document. If not, the button won’t be highlighted."
msgstr ""
#: ../../quality/alert/alert_mo.rst:36 ../../quality/checks/quality_mo.rst:50
msgid "Manufacturing Flow with Routings"
msgstr ""
#: ../../quality/alert/alert_mo.rst:38
msgid ""
"If you work with routings defined on your manufacturing orders, the quality "
"alerts will be launched directly from the work orders on which the quality "
"checks took place."
msgstr ""
#: ../../quality/alert/alert_mo.rst:48
msgid ""
"Then, a button *Quality Alert* will be available from the work order view. "
"When you click on the button, you can specify the quality problem that "
"appeared during the process."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:3
msgid "Generate a Quality Alert from a Transfer"
msgstr ""
#: ../../quality/alert/alert_transfer.rst:6
msgid "Use the Quality Alert"
msgstr ""
#: ../../quality/alert/alert_transfer.rst:8
msgid ""
"Every time you perform some *Quality Checks* on a transfer, a *Quality "
"Alert* button appears. You can always use it. The button is automatically "
"highlighted once you have a failed quality check for the transfer."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:16
msgid ""
"If you click on that *Quality Alert* button, you can specify what was the "
"problem with the product."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:22
msgid ""
"The *Quality Alert* that is created from the transfer can be found via the "
"button appearing on the top right corner of the transfer."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:28
msgid ""
"You can also access all your *Quality Alerts* via the menu, accessible under"
" *Control*."
msgstr ""
#: ../../quality/checks.rst:3
msgid "Checks"
msgstr "Cheques"
#: ../../quality/checks/quality_mo.rst:3
msgid "Perform Quality Checks on Manufacturing Orders"
msgstr ""
#: ../../quality/checks/quality_mo.rst:5
msgid ""
"There are two different situations to consider and that will differ in Odoo "
"processes:"
msgstr ""
#: ../../quality/checks/quality_mo.rst:8
msgid "You work with simple manufacturing flows;"
msgstr ""
#: ../../quality/checks/quality_mo.rst:10
msgid ""
"You work with complex manufacturing flows that are represented by the use of"
" routings in Odoo."
msgstr ""
#: ../../quality/checks/quality_mo.rst:13
msgid "Simple Manufacturing Flow"
msgstr ""
#: ../../quality/checks/quality_mo.rst:16
#: ../../quality/checks/quality_mo.rst:53
#: ../../quality/checks/quality_transfers.rst:6
msgid "Create the Quality Control Point"
msgstr ""
#: ../../quality/checks/quality_mo.rst:18
msgid ""
"To create a quality control point, open the quality app and go to "
":menuselection:`Control --> Control Points`. There, hit create. Make sure to"
" select *Manufacturing* as operation and choose the type of quality check "
"you want to perform."
msgstr ""
#: ../../quality/checks/quality_mo.rst:27
#: ../../quality/checks/quality_mo.rst:69
#: ../../quality/checks/quality_transfers.rst:17
msgid "Process the Quality Check"
msgstr ""
#: ../../quality/checks/quality_mo.rst:29
msgid ""
"Once your *Quality Control Point* has been created, you can create a "
"manufacturing order for your product. Now, and before marking the "
"manufacturing as done, you can register the *Quality Checks*."
msgstr ""
#: ../../quality/checks/quality_mo.rst:39
msgid ""
"Once you have performed your quality checks, you can find them via the "
"*Quality Checks* button available on the manufacturing order form."
msgstr ""
#: ../../quality/checks/quality_mo.rst:46
msgid ""
"If you want to access all your quality checks, you can do this by opening "
"the quality checks menu, under quality control."
msgstr ""
#: ../../quality/checks/quality_mo.rst:55
msgid ""
"If you want to create a *Quality Control Point*, open the *Quality* app and "
"go to :menuselection:`Control --> Control Points`. Then, click on create. "
"Make sure to select *Manufacturing* as operation and select the work order "
"operation on which the quality check should be performed."
msgstr ""
#: ../../quality/checks/quality_mo.rst:64
msgid ""
"Choosing the work order operation is necessary if you want the quality "
"checks to be performed in the work orders. After that, you can choose the "
"type of quality check."
msgstr ""
#: ../../quality/checks/quality_mo.rst:71
msgid ""
"Once your *Quality Control Point* has been configured, create a "
"manufacturing order for your product. You have to plan it if you want to "
"generate the necessary work orders."
msgstr ""
#: ../../quality/checks/quality_mo.rst:78
msgid ""
"Now, process the work order and your quality check will appear. In this "
"example, the quality check requests to enter the serial number of the Table "
"Top component."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:3
msgid "Perform Quality Checks on Transfers"
msgstr ""
#: ../../quality/checks/quality_transfers.rst:8
msgid ""
"To create a *Quality Control Point*, open the *Quality* application. Then, "
"go to :menuselection:`Quality Control --> Control Points --> Create`. Now, "
"you can define the quality control point you want to apply to a specific "
"product. Don’t forget to select a transfer operation type."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:19
msgid ""
"Let’s say that we will receive a laptop. First, create a planned receipt for"
" the product. Then, on the receipt, you will see a *Quality Checks* button "
"that appears to proceed to the quality check you configured before."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:27
msgid ""
"By clicking on it, the instruction set on the quality control point will be "
"displayed and will require the check value."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:33
msgid ""
"Once the quality check is done, you can find it linked to the corresponding "
"transfer and access it by clicking on the button."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:39
msgid ""
"But, if the quality check failed, the stat button will appear in red "
"(instead of green) and Odoo will suggest you to create a *Quality Alert* by "
"highlighting the corresponding button."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:46
msgid ""
"The quality checks can also be found in the *Quality* application by opening"
" the *Quality Checks* menu, under *Quality Control*."
msgstr ""
#: ../../quality/control.rst:3
msgid "Control"
msgstr "Control"
#: ../../quality/control/control_points.rst:3
msgid "Define Quality Control Points"
msgstr ""
#: ../../quality/control/control_points.rst:5
msgid ""
"Quality is an important factor when it comes to products or services. "
"Nowadays, quality has become the differentiating factor for all goods and "
"services. It is vital for businesses to deliver products that meet or exceed"
" expectations. It also helps minimize waste."
msgstr ""
#: ../../quality/control/control_points.rst:10
msgid ""
"That is why most manufacturers would not think of eliminating the quality "
"control from their manufacturing process. After all, removing quality "
"controls would dramatically increase the number of defective products that "
"the company then has to rework or scrap."
msgstr ""
#: ../../quality/control/control_points.rst:15
msgid ""
"Then, using business applications to ensure data quality is important. With "
"Odoo insuring the rear, any major problem can be avoided before occurring!"
msgstr ""
#: ../../quality/control/control_points.rst:20
msgid "Quality Control Points"
msgstr "Puntos del control de calidad"
#: ../../quality/control/control_points.rst:22
msgid ""
"To create a *Quality Control Point*, go to :menuselection:`Quality --> "
"Quality Control --> Control Points`. Once there, define the product on which"
" the quality control point should take place. The operation at which it "
"takes place also is to be defined here."
msgstr ""
#: ../../quality/control/control_points.rst:27
msgid ""
"The *Quality Control Points* take place during transfers or during the "
"manufacturing process of the products. If working with routings on *Bill of "
"Materials*, you have to precise at which step of the manufacturing process "
"the quality control point needs to be applied."
msgstr ""
#: ../../quality/control/control_points.rst:32
msgid ""
"The *Control Type* defines at which frequency the quality checks should take"
" place:"
msgstr ""
#: ../../quality/control/control_points.rst:35
msgid ""
"**All operations**: all the operations automatically generate quality checks"
" to perform;"
msgstr ""
#: ../../quality/control/control_points.rst:38
msgid ""
"**Randomly**: the quality checks only perform on x% of the operation. The "
"percentage needs to be defined on the control point;"
msgstr ""
#: ../../quality/control/control_points.rst:41
msgid ""
"**Periodically**: the quality checks are performed periodically. The "
"periodicity is based on the defined period (once a day, once a week)."
msgstr ""
#: ../../quality/control/control_points.rst:50
msgid "Quality Control Point Types"
msgstr ""
#: ../../quality/control/control_points.rst:52
msgid ""
"Now, one thing remains to be configured: the type of quality check. There "
"are several types that can be used: text, take a picture, pass-fail, take a "
"measure, register consumed material, register by-product, and print label."
msgstr ""
#: ../../quality/control/control_points.rst:58
msgid ""
"Some types are available only with the manufacturing application installed."
msgstr ""
#: ../../quality/control/control_points.rst:62
msgid "Text"
msgstr "Texto"
#: ../../quality/control/control_points.rst:64
msgid ""
"This control point type allows giving instructions to workers during the "
"transfer or during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:80
msgid "Take a Picture"
msgstr "Hacer foto"
#: ../../quality/control/control_points.rst:82
msgid ""
"This control point type asks to take a picture of the product applied in a "
"transfer or when manufacturing it."
msgstr ""
#: ../../quality/control/control_points.rst:98
msgid ""
"This process can be simplified by using a connected :doc:`camera "
"<../../iot/devices/measurement_tool>`."
msgstr ""
#: ../../quality/control/control_points.rst:102
msgid "Pass-Fail"
msgstr ""
#: ../../quality/control/control_points.rst:104
msgid ""
"*Pass-Fail* requires to specify if the products pass or fail specific "
"criteria. It can be applied for both transfers or manufacturing orders."
msgstr ""
#: ../../quality/control/control_points.rst:111
msgid ""
"For this kind of type, there is the possibility to define a failure message "
"giving instructions to follow in case of failure."
msgstr ""
#: ../../quality/control/control_points.rst:127
msgid "Take a Measure"
msgstr ""
#: ../../quality/control/control_points.rst:129
msgid ""
"Taking measures requires to enter the product’s measurements during a "
"transfer or during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:132
msgid ""
"To use it, it necessary to specify the norm for your product’s measurements,"
" but also a tolerance threshold. Doing so, all the products with good "
"measures can are automatically accepted."
msgstr ""
#: ../../quality/control/control_points.rst:140
msgid ""
"As for *Pass-Fail*, this type allows defining a failure message that gives "
"instructions to the worker."
msgstr ""
#: ../../quality/control/control_points.rst:156
msgid ""
"This process can be simplified by using connected :doc:`measurement tools "
"<../../iot/devices/camera>`."
msgstr ""
#: ../../quality/control/control_points.rst:159
msgid "Register Consumed Materials"
msgstr ""
#: ../../quality/control/control_points.rst:161
msgid ""
"When using *Register Consumed Materials*, it is required to register the "
"component’s serial/lot numbers during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:165
#: ../../quality/control/control_points.rst:182
msgid "This type is only available when working with routings."
msgstr ""
#: ../../quality/control/control_points.rst:176
msgid "Register By-Products"
msgstr ""
#: ../../quality/control/control_points.rst:178
msgid ""
"With *Register By-Products*, it is required to register the serial/lot "
"number of the by-products that are manufactured."
msgstr ""
#: ../../quality/control/control_points.rst:193
msgid "Print Label"
msgstr ""
#: ../../quality/control/control_points.rst:195
msgid ""
"*Print Label*, as its name points out, allows printing labels to add to the "
"product during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:207
msgid ""
"This process can be simplified by using a connected :doc:`printer "
"<../../iot/devices/printer>`."
msgstr ""

2392
locale/es/LC_MESSAGES/sales.po
View File

File diff suppressed because it is too large Load Diff

559
locale/es/LC_MESSAGES/sms_marketing.po Normal file
View File

@ -0,0 +1,559 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Lina Maria Avendaño Carvajal <lina8823@gmail.com>, 2020
# José Vicente <txusev@gmail.com>, 2020
# Cristopher Cravioto <ccr@odoo.com>, 2020
# Jon Perez <jop@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Jon Perez <jop@odoo.com>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: es\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../sms_marketing.rst:5
msgid "SMS Marketing"
msgstr "Marketing por SMS"
#: ../../sms_marketing/overview.rst:3
msgid "Overview"
msgstr "Información general"
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:3
msgid "Contact Lists and Blacklist"
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:5
msgid ""
"Creating your own list of contacts, or importing it, is useful when you want"
" to create specific groups of people, such as the subscribers of your "
"newsletter. It is also the best way to get started if you are coming from "
"another system and already have built an audience. It makes the SMS "
"distribution easier."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:11
msgid "Contact lists"
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:13
msgid "Go to :menuselection:`Contacts lists --> Contacts lists --> Create`."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:16
msgid ""
"Choose a name for your *Mailing list*, and activate the option *Is Public* "
"if you would like to make the mailing list accessible to your recipients in "
"the unsubscription page (allowing users to update their subscription "
"preferences)."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:22
msgid "History with the Log Notes"
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:25
msgid ""
"A record of the mailings sent is kept on the recipient's chatter (whether it"
" is a contact or an opportunity, for example)."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:28
msgid ""
"This is important as you and team members can easily keep track and see a "
"history of the interactions with your contacts or prospects. Example: your "
"sales representative can easily find out which SMS mailing promotions a "
"customer has received or not."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:35
msgid "Blacklist"
msgstr "Lista negra"
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:38
msgid ""
"If you are coming from another software and have a list of clients who have "
"already asked to be blacklisted, you can import those entries to your "
"database."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:39
msgid ""
"For that, go to :menuselection:`Configuration --> Phone Blacklist --> "
"Import`."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:3
msgid "Integrations and Templates"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:5
msgid ""
"Using SMS to reach people can be a strategy not just used for advertisement "
"purposes, but also as a reminder of events or issued invoices to your "
"costumers, for example."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:9
msgid "Campaigns"
msgstr "Campañas"
#: ../../sms_marketing/overview/integrations_and_template.rst:11
msgid ""
"First, make sure to have the necessary feature activated. Go to the "
":menuselection:`Email Marketing app --> Configuration --> Settings` and "
"enable *Mailing Campaigns*."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:17
msgid ""
"Now, the menu *Campaigns* is also available on the *SMS Marketing* app, "
"allowing you to manage and have an overview of your SMS mailings under "
"campaigns."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:23
msgid ""
"This feature is especially useful if you have aggregated campaigns, as you "
"have a global reporting view. In addition to that, you can create stages in "
"your Kanban view to better organize the work being done."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:31
msgid "Sending SMSs through the Contacts app"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:34
msgid ""
"Sending SMSs through the contact’s form is available by default in Odoo. It "
"makes your work easier if you need to send an SMS to a specific contact, for"
" example."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:36
msgid ""
"For that, go to the *Contacts* app, select the contact and click on the "
"*SMS* icon next to the phone number."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:41
msgid ""
"If you would like to send a message to multiple contacts at once, choose the"
" *List View*, select all the contacts needed, and under *Action* select "
"*Send SMS*."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:48
msgid "Set up SMS templates"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:50
msgid ""
"To set up *SMS Templates*, activate the :doc:`Developer mode "
"<../../general/developer_mode/activate>`, then go to "
":menuselection:`Technical --> SMS Templates`."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:60
msgid ""
"Use *Dynamic Placeholders* to adapt automatically the content of the SMS to "
"the context."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:63
msgid "SMS Text Messaging is available throughout Odoo:"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:65
msgid "*CRM*: send SMSs to your leads and opportunities."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:66
msgid "*Subscription*: alert customers about their subscription."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:67
msgid "*Accounting*: send payment reminders."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:68
msgid "*Marketing Automation*: automate your SMS marketing campaigns."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:69
msgid ""
"*Inventory*: send an automatic confirmation when a delivery order is done."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:70
msgid ""
"*Sign*: receive a validation code to verify your identity before signing a "
"document online."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:71
msgid ""
"*SEPA debit payment provider*: send a verification code to your customers."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:72
msgid ""
"*Studio*: send an SMS according to your needs by using automated actions."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:75
msgid ""
"For more information about SMS integrations in Odoo and a list of frequently"
" asked questions, go to :doc:`../pricing/pricing_and_faq`."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:79
msgid ":doc:`../../social_marketing/overview/campaigns`"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:80
msgid ":doc:`../../discuss/advanced/email_template`"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:3
msgid "Build, Send and Get Reports from a SMS Mailing"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:5
msgid ""
"Using SMS Marketing as part of your communication strategies can empower you"
" to expand your markets, considering that in some countries emails are not "
"very used or used at all. It also helps to boost conversion rates, as this "
"strategy has a high open-rate percentage among people who use smartphones."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:11
msgid "Get started"
msgstr "Empezar"
#: ../../sms_marketing/overview/sms_mailing_reports.rst:13
msgid "Go to :menuselection:`SMS Marketing --> Create`."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:18
msgid ""
"Specify a *subject* name to help you remembering what the mailing is about."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:20
msgid ""
"Under *Recipients*, choose to whom you would like the SMS to be sent. If you"
" choose *Contact*, all your Odoo contacts (vendor, customers, etc.) receive "
"your SMS."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:22
msgid ""
"From there, you can refine your recipient list with the *add filter* option."
" In the example below, the message would be sent to the contacts living in "
"Belgium."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:27
msgid ""
"The *Mailing list* option, on the other hand, allows you to choose the "
"specific mailing lists you created to group specific contacts. You are "
"allowed to select multiple ones."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:34
msgid ""
"Under the *SMS Content* tab, links can be included and Odoo automatically "
"generates *link trackers* in order to generate data about these links."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:36
msgid ""
"Under *Settings* you have the option *Include opt-out link*. If activated, "
"the contact is able to unsubscribe from the mailing list."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:43
msgid ""
"In the *Link Tracker* menu under *Configuration*, you can see the history of"
" your sent links, access them and look at statistics."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:50
msgid "Double-check that you have the phone number of your contacts saved."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:53
msgid "Send a mailing"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:57
msgid ""
"Once you have your mailing created, you must choose when you would like it "
"to be delivered:"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:59
msgid ""
"*Put in Queue*: the mailing is triggered with the next automatic run. "
"Interesting option if you do not need the message to be sent at a specific "
"time."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:61
msgid ""
"*Send Now*: sends the message immediately. Use this option if the recipient "
"list is not excessive."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:62
msgid ""
"*Schedule*: allows you to choose a day and time. Best option for mailings "
"that you would like to send during a specific event, to promote an offer "
"while it is active, or to simply plan your content strategy in advance."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:65
msgid ""
"*Test*: allows you to send an SMS to one or multiple numbers for test "
"purposes. Check, for example, if the link provided lands on the right page "
"while making sure they are responsive. If sending it to multiple numbers, "
"you must remember to use a comma between them."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:70
msgid "Visualize reports"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:72
msgid ""
"Under the *Reporting* menu apply filters, measures, and adopt different "
"layouts to do analyses of the performance of your SMS mailings."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:79
msgid ""
"You can also check the price to send an SMS for your country by clicking on "
"the *Information* icon."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:86
msgid ""
"**Buy Credits:** in order to take advantage of the app and its features, "
"make sure you have purchased credits. For more information: "
":doc:`../pricing/pricing_and_faq`."
msgstr ""
#: ../../sms_marketing/pricing.rst:3
msgid "Pricing and FAQ"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:3
msgid "SMS Pricing and FAQ"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:6
msgid "What do I need to send SMSs?"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:7
msgid ""
"SMS Text Messaging is an In-App Purchase (IAP) service that *requires "
"prepaid credits* to work."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:11
msgid "How many types of SMSs are there?"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:12
msgid "There are 2 types: GSM7 and UNICODE."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:14
msgid ""
"**GSM7** is the standard format, with a limit of 160 characters per message,"
" that includes the following characters:"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:23
msgid ""
"**UNICODE** is the format applied if a special character, that *is not* in "
"the GSM7 list, is used. Limit per SMS: 70 characters."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:27
msgid ""
"For GSM7 SMS the size limit is 160 characters, and for Unicode is 70. *Above"
" these limits, the content is divided into a multi-part message* and the "
"limit of characters is lowered to 153 for GSM7 and to 67 for Unicode. The "
"system will inform you in real-time about the number of SMS your message "
"represents."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:34
msgid "How much does it cost to send an SMS?"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:35
msgid ""
"The price of an SMS depends on the destination and the length (number of "
"characters) of the message."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:37
msgid ""
"To see the **price per country, please consult**: `Odoo SMS - FAQ <https"
"://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:39
msgid ""
"The number of SMSs a message represents will be always available to you in "
"your database."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:49
msgid "How do I buy credits?"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:50
msgid "Go to :menuselection:`Settings --> Buy Credits`."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:57
msgid "Or go to :menuselection:`Settings --> View my Services`."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:65
msgid ""
"If you are on Odoo Online (SAAS) and have the Enterprise version, you "
"benefit from free trial credits to test the feature."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:70
msgid "More common questions"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:72
msgid "**Is there an expiration time for my credits?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:74
msgid "No, credits do not expire."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:77
msgid ""
"**Can I send an SMS to a phone number (which is not a mobile phone) because "
"I see the icon in front of the field “phone”?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:80
msgid "Only if that phone number supports SMS (e.g. SIP phones)."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:83
msgid "**Do I receive an invoice to buy my credits?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:85
msgid "Yes."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:88
msgid "**Can the recipient answer to me?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:90
msgid "No, it is not possible to reply to the SMS."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:93
msgid ""
"**What happens if I send multiple SMS but I do not have enough credits to "
"send them all?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:95
msgid ""
"The whole transaction is counted as a single one, so no SMS will be sent "
"until you have enough credits to send them all."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:99
msgid "**Do I have a history of the sent SMSs?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:101
msgid ""
"Yes, the SMS is logged as a note under the chatter of the corresponding "
"record, and a complete history of the SMSs sent is available on "
":doc:`Developer mode <../../general/developer_mode/activate>` under "
":menuselection:`Technical --> SMS`."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:107
msgid "**Can I send as many SMSs I want at once?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:109
msgid "Yes, if you have enough credits."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:112
msgid ""
"**If I have a number that does not exist in the list of recipients, will I "
"lose credits?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:114
msgid ""
"Not if the phone number is in the wrong format (e.g. too many digits). "
"Otherwise, if the SMS is sent to the wrong person or to a fake number, the "
"credit will be lost."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:118
msgid ""
"**What happens if I send my SMS to a paying number (e.g.: a contest to win a"
" ticket for a festival)?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:120
msgid ""
"The SMS will not be delivered to that kind of number, so you won’t be "
"charged."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:123
msgid ""
"**Can I identify the numbers that do not exist when I send several SMSs?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:125
msgid "Only the ones that have an invalid format."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:128
msgid "**How does the GDPR regulation affect this service?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:130
msgid ""
"Please find our `Privacy Policy here <https://iap.odoo.com/privacy#sms>`__."
msgstr ""

361
locale/es/LC_MESSAGES/social_marketing.po Normal file
View File

@ -0,0 +1,361 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Lina Maria Avendaño Carvajal <lina8823@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:42+0000\n"
"Last-Translator: Lina Maria Avendaño Carvajal <lina8823@gmail.com>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: es\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../social_marketing.rst:5
msgid "Social Marketing"
msgstr ""
#: ../../social_marketing/overview.rst:3
msgid "Overview"
msgstr "Información general"
#: ../../social_marketing/overview/campaigns.rst:3
msgid "Connecting to my Marketplace with Campaigns"
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:5
msgid ""
"Whether your goal is to sell a new product, explain the value of your "
"services or advertise your event, a campaign helps you to connect with your "
"marketplace. They normally involve multiple channels, so it is fundamental "
"to have a solution with which you can plan, execute, track, and analyze your"
" content."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:10
msgid "Go to :menuselection:`Social Marketing --> Campaigns --> Create`."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:16
msgid ""
"As you create content, tabs for that specific channel are shown. The "
"overview of the campaign displays global metrics such as:"
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:19
msgid ""
"*Revenue*: number of users who, from a link in your content, finished a "
"transaction (paid)."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:20
msgid ""
"*Quotations*: number of users who, from a link in your content, have started"
" but not finished a transaction (did not pay)."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:22
msgid ""
"*Leads*: users who have filled out your contact form, from a link in your "
"content."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:25
msgid ""
"To be able to *Send New Mailing*, make sure the feature is enabled in the "
"*Email Marketing* application, under :menuselection:`Email Marketing --> "
"Configuration --> Settings`. To be able to *Send SMS*, the *SMS Marketing* "
"application must be installed on your database."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:30
msgid ""
"*Social Marketing* works integrated with other applications such as *Sales*,"
" *Invoicing*, *CRM* and *Website*."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:34
#: ../../social_marketing/overview/manage_social.rst:77
msgid ":doc:`./push_notifications`"
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:35
#: ../../social_marketing/overview/push_notifications.rst:66
msgid ":doc:`./manage_social`"
msgstr ""
#: ../../social_marketing/overview/livechat.rst:3
msgid "Interact with Customers and Visitors with Live Chat"
msgstr ""
#: ../../social_marketing/overview/livechat.rst:5
msgid ""
"One of the ways you can build stronger relationships with your customers is "
"by making yourself available through live chat. Live chats can have a big "
"impact not just on your customer service, but also on sales performance, as "
"it gives users a chance of having real-time, fast, and effective "
"interaction."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:11
msgid "Configuration"
msgstr "Configuración"
#: ../../social_marketing/overview/livechat.rst:13
msgid ""
"Go to :menuselection:`Website --> Configuration --> Settings --> Live Chat` "
"select the appropriate channel, and set it up."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:20
msgid ""
"Under *Channel Rules*, choose when the chat pop-up appears, and an action "
"for a given URL and/or country. Note that to take the country into account, "
"GeoIP must be installed on your server."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:24
msgid "The *Live Chat* application must be installed on your database."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:27
msgid "Monitor your visitors"
msgstr ""
#: ../../social_marketing/overview/livechat.rst:29
msgid ""
"Under the *Visitors* menu, see the visitors that landed on one of your "
":ref:`social_marketing/website_tracked_pages` online or offline."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:34
msgid ""
"You can send emails (if an email address has been saved), send SMSs (if a "
"phone number has been saved), send a push notification (if the user has "
"subscribed to it), and even send a live chat request that will be received "
"by the user once they move to a tracked page."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:36
msgid ""
"Open a record to see details including the visited pages, and the first and "
"last date and time the user was connected."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:43
msgid ""
"Your online visitors will be authenticated if they are linked to a lead or "
"an existing partner."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:44
msgid ""
"If you do not use the *Website* app, you can add a live chat widget to your "
"own website."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:49
msgid "Website’s tracked pages"
msgstr ""
#: ../../social_marketing/overview/livechat.rst:51
msgid ""
"To define which pages are tracked, on the *Website* application, go to "
":menuselection:`Website --> Configuration --> Pages` and enable the option "
"*Track*, on the respective pages."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:60
msgid ":doc:`../../livechat/overview/get_started`"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:3
msgid "Manage Social Media Pages and Create Content"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:5
msgid ""
"Once you are present on social media platforms, it is important to keep them"
" up-to-date. However, that might feel like a full-time job. Having a "
"solution that allows you to create, schedule, keep track, engage with your "
"audience and measure results saves you time and helps you to successfully "
"execute your online strategy, from posts to results."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:12
msgid "Add accounts and create your feed"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:14
msgid ""
"Click on *Add Stream* and grant the required permissions to add your "
"accounts."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:21
msgid "You can link a Facebook page for which you are the admin."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:23
msgid ""
"You are then redirected to your *Feed* and a column with the publications is"
" automatically added."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:25
msgid ""
"You can then add new accounts and/or streams, such as Facebook mentions, and"
" customize your Kanban view."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:31
msgid ""
"Adding social media accounts to your feed will also link KPIs. To get "
"redirected to the statistics page of the social account, click on "
"*Insights*."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:39
msgid "Link a LinkedIn account"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:41
msgid ""
"Go to :menuselection:`Social Marketing --> Configuration --> Social Media`."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:48
msgid ""
"LinkedIn is in Beta Version, therefore, the feed is not available. Only the "
"creation of content."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:51
msgid "Publish content"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:53
msgid ""
"Click on :menuselection:`Social Marketing --> Feed --> New Post`, or go to "
":menuselection:`Social Marketing --> Posts → Create`."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:60
msgid "Choose to upload your post right away or to schedule it."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:61
msgid "Saving your post will apply a draft status to it."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:64
msgid "Overview and plan your posts with a calendar view"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:67
msgid ""
"Through the calendar view, besides having an overview of your planned day, "
"week or month, also see your drafted, scheduled and published posts."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:68
msgid "Drag and drop (scheduled posts) to change their scheduled date."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:70
msgid ""
"Double-click on a date to create a post directly from the *Calendar view*, "
"and click on an existing one to edit it."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:78
#: ../../social_marketing/overview/push_notifications.rst:67
msgid ":doc:`./campaigns`"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:79
msgid ":doc:`./livechat`"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:3
msgid "Use Web Push Notifications"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:5
msgid ""
"Web Push Notifications deliver messages to your user’s device without the "
"need to be on your website, or for them to give personal information. They "
"can be used to inform your users about news, articles and content posted, "
"practical messages like traffic and weather updates, flight information, "
"sales alerts, coupons, and product updates."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:11
msgid "Ask users for permission"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:13
msgid ""
"In the *Website* application go to :menuselection:`Website --> Configuration"
" --> Settings` and enable *Web Push Notifications*."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:20
msgid ""
"Choose your message, icon, and delay time (which is the wait time for the "
"permission request to be shown once the user lands on your page)."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:28
msgid "Send notifications"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:31
msgid "Individually"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:33
msgid "You can send individual messages through the menu *Visitors*."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:40
msgid "To a group"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:42
msgid ""
"Target a bigger segment by selecting multiple visitors in the *View List* "
"(e.g.: all visitors that visited your Homepage)."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:50
msgid ""
"Visitors records are kept under *Visitors* for a week, before getting "
"archived."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:53
msgid "By rules"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:55
msgid ""
"Or go to :menuselection:`Social Marketing --> Posts --> Create`. Under *Web "
"Notification options*, apply filters to send your message to the records "
"that match the rules you set."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:63
msgid "The feature only works with Odoo Website application."
msgstr ""

943
locale/es/LC_MESSAGES/studio.po Normal file
View File

@ -0,0 +1,943 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Pablo Rojas <rojaspablo88@gmail.com>, 2020
# AleEscandon <alejandra.escandon@jarsa.com.mx>, 2020
# Nicolás Broggi <rnbroggi@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:42+0000\n"
"Last-Translator: Nicolás Broggi <rnbroggi@gmail.com>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: es\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../studio.rst:5
msgid "Studio"
msgstr "Studio"
#: ../../studio/concepts.rst:3
msgid "Concepts"
msgstr "Conceptos"
#: ../../studio/concepts/understanding_automated_actions.rst:3
msgid "Understanding Automated Actions"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:6
msgid ""
"Automated actions are used to trigger actions. They are based on conditions "
"and happen on top of Odoo’s default business logic."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:9
msgid ""
"Examples of automated actions include: creating a next activity upon a "
"quote's confirmation; adding a user as a follower of a confirmed invoice if "
"its total is higher than a certain amount; or preventing a lead from "
"changing stage if a field is not filled in."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:16
msgid ""
"Let's understand how to properly define *when* an automated action runs and "
"*how* to create one:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:18
msgid ""
"The first step is to choose the :doc:`Model <understanding_general>` on "
"which the action is applied."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:19
msgid ""
"The **Trigger** field defines the event that causes the automated action to "
"happen:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:21
msgid ""
"*On Creation*: when a new record is created. Note that the record is created"
" once saved for the first time."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:23
msgid ""
"*On Update*: when the record is updated. Note that the update happens once "
"the record is saved."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:24
msgid ""
"*On Creation & Update*: on the creation and/or on the update of a record "
"once the form is saved."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:25
msgid "*On Deletion*: on the removal of a record under the condition set."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:26
msgid ""
"*Based on Form Modification*: when the value of the specified *Trigger* "
"field is changed in the interface (user sees the changes before saving the "
"record). Note that this action can only be used with the *Execute Python "
"Code* action type."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:29
msgid ""
"*Based on Timed Condition*: a delay happens after a specific date/time. Set "
"a *Delay after trigger date* if you need a delay to happen before the "
"*Trigger Date*. Example: to send a reminder 15min before a meeting. If the "
"date/time is not set on the form of the model chosen, the date/time "
"considered is the one of the creation/update of the record."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:34
msgid "For every Trigger option, **conditions** can be applied, such as:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:36
msgid ""
"*Before Update Domain*: if designated, this condition must be satisfied "
"before the record is updated."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:38
msgid ""
"*Apply on*: if designated, this condition must be satisfied before executing"
" the action rule (*Action To Do*), and after the update."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:41
msgid ""
"The **Active** option is to be turned off when the rule should be hidden and"
" not executed."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:43
msgid ""
"Under **Action To Do** choose the type of server action that must be "
"executed once records meet the *Trigger* conditions:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:45
msgid ""
"*Execute Python Code*: a block of code is executed. A *Help* tab with the "
"variables that can be used is available."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:47
msgid "*Create New Record*: a new record with new values is created."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:48
msgid "*Update a Record*: updates the record that triggered the action."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:49
msgid ""
"*Execute several actions*: defines an action that triggers other server "
"actions."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:50
msgid ""
"*Send Email*: an automatic :doc:`email "
"<../../discuss/advanced/email_template>` is sent."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:51
msgid ""
"*Add Followers*: :doc:`followers <../../project/tasks/collaborate>` are "
"notified of changes in the task."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:53
msgid ""
"*Create Next Activity*: creates an activity such as: *Call*, *Email*, "
"*Reminder*."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:54
msgid ""
"*Send SMS Text Message*: sends an :doc:`SMS "
"<../../sms_marketing/pricing/pricing_and_faq>`."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:57
msgid "Example"
msgstr "Ejemplo"
#: ../../studio/concepts/understanding_automated_actions.rst:59
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
msgid "The user creates the record without an email address set."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:67
msgid "The user updates the record defining an email address."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:68
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
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
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
msgid "If true, the chosen *Action To Do* is performed on the record."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:77
msgid ":doc:`understanding_general`"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:78
msgid ":doc:`../use_cases/automated_actions`"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:3
msgid "Understanding General Concepts"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:7
msgid ""
"Odoo Studio is a toolbox that allows you to add models or adapt "
"functionalities on top of Odoo’s standard behavior without coding knowledge."
" You can also create custom views and modify existing ones without having to"
" get into the XML code."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:11
msgid ""
"Even for experienced developers, typing out code requires time. By using "
"Odoo Studio, you can quickly get your models up and going and focus on the "
"crucial parts of your application. The result is a user-friendly solution "
"that makes customizations and designing new applications easy with or "
"without programming skills."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:15
msgid "Getting started"
msgstr "Primeros pasos"
#: ../../studio/concepts/understanding_general.rst:17
msgid ""
"One you start using Odoo Studio, you automatically create a new *module* "
"that contains all your modifications. These modifications can be done on "
"existing screens (*views*), by adding new *fields* in existing applications,"
" or by creating an entirely new *model*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:22
msgid "What is a Module?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:25
msgid ""
"An Odoo **Module** can contain a number of elements, such as: business "
"objects (models), object views, data files, web controllers, and static web "
"data. An application is a collection of modules."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:29
msgid ""
"In object-oriented programming, models usually represent a concept from the "
"real world. Example: Odoo has models for Sales Orders, Users, Countries, "
"etc. If you were to build an application to manage Real Estate sales, a "
"model that represents the Properties for sale would probably be your first "
"step."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:38
msgid "What is a Model (also called Object)?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:40
msgid ""
"A **Model** determines the logical structure of a database and fundamentally"
" determines in which manner data can be stored, organized, and manipulated. "
"In other words, a model is a table of information that can be bridged with "
"other tables."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:45
msgid "What are Fields?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:47
msgid ""
"**Fields** compose models. It is where a record (a piece of data) is "
"registered."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:49
msgid ""
"Example: on the Real Estate application, fields on the Properties model "
"would include the price, address, a picture, a link to the current owner, "
"etc."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:50
msgid ""
"There are 2 main types of fields in Odoo: *basic (or scalar) fields* and "
"*relational fields*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:53
msgid ""
"Basic fields represent simple values, like numbers or text. Relational "
"fields represent relations between models. So, if you have a model for "
"*Customers* and another one for *Properties*, you would use a relational "
"field to link each Property to its Customer."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:56
msgid "Relational Fields in detail"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:59
msgid ""
"**Relational Fields** provide the option to link the data of one model with "
"the data of another model."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:60
msgid ""
"In Odoo, relational field types are: *One2many*, *Many2one*, *Many2many*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:66
msgid ""
"An **One2many** field is a *one-way* direction of selecting *multiple* "
"records from a table."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:68
msgid ""
"Example: a Sales Order can contain multiple Sales Order Lines, which also "
"contain multiple fields of information."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:69
msgid ""
"A **Many2one** field is a *one-way* direction of selecting *one* record from"
" a table."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:70
msgid ""
"Example: you can have many product categories, but each product can only "
"belong to one category."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:71
msgid ""
"A **Many2many** field is a *two-way* direction of selecting records from a "
"table."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:72
msgid "Example: multiple tags can be added to a lead’s form."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:75
msgid "An *One2many* field must have a *Many2one* related to it."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:78
msgid "What are Views?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:80
msgid ""
"**Views** define how records are displayed. They are specified in XML which "
"means that they can be edited independently from the models that they "
"represent. There are various types of views in Odoo, and each of them "
"represents a mode of visualization. Some examples are: *form*, *list*, "
"*kanban*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:85
msgid "What is a Menu?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:87
msgid ""
"A **Menu** is a button that executes and action. In Odoo Studio, to create "
"menus (models) and rearrange their hierarchy, click on *Edit Menu*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:95
msgid "`Studio Basics <https://www.odoo.com/fr_FR/slides/studio-31>`_"
msgstr ""
#: ../../studio/how_to.rst:3
msgid "How To"
msgstr ""
#: ../../studio/how_to/export_import.rst:3
msgid "Export and Import Modules"
msgstr ""
#: ../../studio/how_to/export_import.rst:5
msgid ""
"When you do customizations in Odoo Studio, a new module is created in your "
"database, making it easy to use Studio for prototyping."
msgstr ""
#: ../../studio/how_to/export_import.rst:8
msgid ""
"To export these customizations, activate Studio on the main dashboard and, "
"under the menu *Customizations*, click on *Export*. The default filename is "
"*customizations.zip*."
msgstr ""
#: ../../studio/how_to/export_import.rst:16
msgid ""
"The module created contains the definition of custom models and fields, as "
"well as the UI elements of any customization in an XML format."
msgstr ""
#: ../../studio/how_to/export_import.rst:18
msgid ""
"To import and install the customizations in another instance, connect to the"
" destination database, activate Studio and, under *Customizations*, click on"
" *Import*."
msgstr ""
#: ../../studio/how_to/export_import.rst:25
msgid ""
"Studio does not know which apps are customized (because the same view can be"
" modified on different apps), therefore, it *does not* add the underlying "
"modules as dependencies of the exported module. In other words, the "
"applications installed on the source database should be installed on the "
"destination database."
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:3
msgid "Customizing the Rainbow Man"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:5
msgid ""
"The Rainbow Man in Odoo is an animation shown once the user completes "
"certain tasks and clicks on certain buttons. It is a way to make the "
"software fun to use, and rewarding, for employees."
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:13
msgid ""
"On most buttons in Odoo, such as *Send by Email*, *Confirm* or *Cancel*, "
"once they are selected in Studio, under their *Properties*, the *Rainbow "
"Man* effect can be applied."
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:14
msgid "By default, the feature is active:"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:16
msgid "when opportunities are marked as won;"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:17
msgid "when users empty their inboxes;"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:18
msgid "when the user finishes a tour;"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:19
msgid "when the user finishes doing reconciliations."
msgstr ""
#: ../../studio/how_to/reports.rst:3
msgid "Customizing Reports"
msgstr ""
#: ../../studio/how_to/reports.rst:9
msgid ""
"Odoo uses HTML and CSS technologies to create reports. HTML is a markup "
"language that uses tags, also called elements. It is the core of any webpage"
" because it provides its basic structure. CSS interacts with HTML elements "
"to add style to the page, establishing how the HTML is shown to the user. "
"Odoo’s reports also use Bootstrap’s grid layout, which is the containers, "
"rows, and columns to align content, and support Odoo's website themes."
msgstr ""
#: ../../studio/how_to/reports.rst:11
msgid ""
"When creating a new report, choose the purpose of it and if you would like "
"the report to include header and footer (company logo, name, address, phone,"
" email address, etc.)."
msgstr ""
#: ../../studio/how_to/reports.rst:17
msgid ""
"Under the tab **Add**, you find the fields to be dragged and dropped to the "
"view. *Fields*, *Data tables*, *Subtotal & Total*, and *Address Book* are "
"dynamic elements (meaning that they need a :doc:`one2many or a many2many "
"<../concepts/understanding_general>` related object). *Text*, *Title Block*,"
" *Image*, and *Text in Cell* are static elements."
msgstr ""
#: ../../studio/how_to/reports.rst:26
msgid ""
"Once the element is added to the view, select it to see its **Options**. The"
" first section shows the hierarchy of the selected object and its "
"properties, allowing you to individually edit them. Fields with related "
"objects have their directives shown on *Field Expression*."
msgstr ""
#: ../../studio/how_to/reports.rst:34
msgid ""
"Under **Visible if**, define the rule(s) to set visibility conditions to "
"fields."
msgstr ""
#: ../../studio/how_to/reports.rst:36
msgid ""
"Example: if choosing to display a product image, you could set a visibility "
"rule to only display the ones that are *set* in the product form, avoiding "
"having a plain icon when they are not set."
msgstr ""
#: ../../studio/how_to/reports.rst:40
msgid ""
"**Visible for** is used to set which :doc:`groups "
"<../../general/odoo_basics/add_user>` can have access to specific elements "
"in the report. **Limit visibility to groups**, under *Report*, sets the "
"visibility of the report to specifics groups, meaning that users belonging "
"to other groups do not see the same final document."
msgstr ""
#: ../../studio/how_to/reports.rst:46
msgid ""
"Under the **Report** tab, name your report, choose the paper format, and if "
"the report should be added to the *Print* menu list on its respective "
"document form."
msgstr ""
#: ../../studio/how_to/reports.rst:53
msgid ""
"If activating the :doc:`Developer mode "
"<../../general/developer_mode/activate>`, additional fields such as *Class* "
"under *Options*, and *Reload from attachment* under *Report*, become "
"visible."
msgstr ""
#: ../../studio/how_to/reports.rst:56
msgid ""
"*Class*: add custom CSS classes to the selected element (e.g. Bootstrap "
"classes such as *text-danger*)."
msgstr ""
#: ../../studio/how_to/reports.rst:59
msgid ""
"*Reload from attachment*: saves the report as an attachment of the document "
"when printed. When the report is reprinted, it re-downloads that attachment "
"instead of re-printing it. This means that if the underlying record (e.g. "
"Invoice) changes when compared to the first impression, the report does not "
"reflect the changes because they were done after the attachment was created."
" This is typically useful for reports linked to documents that should not "
"change, such as Invoices."
msgstr ""
#: ../../studio/how_to/reports.rst:67
msgid ""
"Actions in Odoo Studio can be undone until you *Close* the toolbox. Once you"
" have closed Studio, changes can not be undone anymore."
msgstr ""
#: ../../studio/use_cases.rst:3
msgid "Use Cases"
msgstr "Casos de uso"
#: ../../studio/use_cases/automated_actions.rst:3
msgid "Advanced Use Cases: Automated Actions"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:5
msgid ""
"**Case scenario 1: when a Belgian lead is created, a 3-stars priority should"
" be automatically applied.**"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:8
msgid "Under *Automations*, click on *Create* and set the following rules:"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:10
msgid "*Model*: Lead/Opportunity"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:11
msgid "*Active*: On"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:12
msgid "*Trigger*: On Creation & Update"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:13
msgid "*Apply on*: Country > Country Name = Belgium"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:14
#: ../../studio/use_cases/filters_status_bar.rst:53
msgid "*Action To Do*: Update the Record"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:15
msgid "*Data to Write*: Lead/Opportunity > Value > 3"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:22
msgid ""
"Check :doc:`this doc <filters_status_bar>` in order to have another "
"automated action example."
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:25
msgid ":doc:`../concepts/understanding_automated_actions`"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:26
#: ../../studio/use_cases/filters_status_bar.rst:61
#: ../../studio/use_cases/models_fields.rst:138
#: ../../studio/use_cases/views.rst:28
msgid ":doc:`../concepts/understanding_general`"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:3
msgid "Advanced Use Cases: Filters and Status Bar"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:5
msgid ""
"**Case scenario 1: on Sales, set a filter on Belgian customers and define it"
" as the default one (the user should still be able to unset the filter).**"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:8
msgid ""
"On your customer’s page, use *Filters* > *Add Custom Filter* to group "
"customers by country. Now, under *Favorites*, *Save Current Search* enabling"
" *Use by default* and *Save*."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:15
msgid ""
"On *Filter Rules* in Studio mode, select the respective filter and enable "
"*Default Filter*."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:21
msgid ""
"**Case scenario 2: add a status bar on the product form to manage its life "
"cycle. Set the values: ‘Prototype’, ‘In use’ and ‘Deprecated’. By default, "
"the Kanban view must be grouped by status.**"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:26
msgid ""
"On your product form, *Add a pipeline status bar* and name its values. "
"Status bars are *selection* fields that give you the ability to follow a "
"specific flow. They are useful to show you the progress that has been made."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:28
msgid ""
"On the *Views* menu, access *Kanban* and, under its *View* options, set the "
"*Default Group by* as *Pipeline status bar*."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:34
msgid ""
"Now, open your product form and set the right status for that product. As "
"you move products throughout stages (also through the product’s form), "
"stages are shown in the Kanban view."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:38
msgid ""
"To make modifications in the pipeline status bar, for example, remember to "
"go back to *Form View*."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:44
msgid ""
"**Case scenario 2.a: when a product goes from ‘In use’ to ‘Deprecate’, set "
"its cost to 0€.**"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:46
msgid ""
"Create an :doc:`automated action "
"<../concepts/understanding_automated_actions>` with the selected values:"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:49
msgid "*Model*: Product Template"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:50
msgid "*Trigger*: On Update"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:51
msgid "*First Domain*: Pipeline status bar = In use"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:52
msgid "*Second Domain*: Pipeline status bar = Deprecated"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:54
msgid "*Data to Write*: Cost (Product Template) > Value > 0"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:3
msgid "Advanced Use Cases: Creating Models and Adding Fields"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:5
msgid ""
"**Case scenario 1: on the leads’ form, if the chosen country is France, show"
" a field 'Pay by check?'**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:8
msgid ""
"On your leads’ form, add a *Related Field* to *Country > Country Name*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:10
msgid ""
"Now, add a *Checkbox* field and define its invisibility options as *Country*"
" (carefully select the one just created) *> is not = > France.*"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:11
msgid "You can now hide the related field created (*Country*) if you wish."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:19
msgid ""
"Another approach is to use the country’s ID. To do so, go to "
":menuselection:`Contacts --> Configuration --> Countries`, select France "
"(for example), and on the URL check its *ID*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:21
msgid ""
"The related field invisibility path should now be *Country* (carefully "
"select the one just created) *> is not = > 75*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:22
msgid "Again, hide the related field with the country’s ID if you prefer."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:28
msgid ""
"**Case scenario 2: create a model called 'Properties' and add fields called:"
" company, value, name, address, active, image.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:31
msgid ""
"From the dashboard, (optionally) start a new module. Then, click on *Edit "
"Menu* and start a *New Menu* (model). Set your menu name and *Confirm*. Now,"
" on its form, drag & drop the necessary fields."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:39
msgid ""
"**Case scenario 2.a: now, you would like to have a model called 'Regions' to"
" which each property must be linked. And, on 'Regions', you would like to "
"see the properties for each region.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:43
msgid ""
"Go to *Edit Menu > New Menu* and create your menu, calling it *Regions*. Add"
" the necessary fields on its form by dragging & dropping them."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:45
msgid ""
"Now, in the form view of *Properties*, add a *Many2one* field with a "
"relation to your model *Region*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:48
msgid ""
"The *Existing Fields* are the ones that are on the current model but not yet"
" in the view."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:60
msgid ""
"Now, go to the model *Regions*, select the form view, and add a status "
"button selecting *Regions (Properties)* as your relational field."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:62
msgid ""
"*Status buttons* are computed fields, meaning that they count the numbers of"
" records on the related model, and allow you to access them."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:69
msgid ""
"When searching for relations, click on *Search more* and filter it by "
"*Custom*. This way you avoid creating duplicates."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:76
msgid ""
"**Case scenario 2.b: in the model 'Properties', show all the tags as "
"checkboxes instead of tags.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:78
msgid ""
"Once the field *Tags* is added to the form, select it and, under its "
"*Properties > Widgets*, choose *Checkboxes*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:85
msgid ""
"**Case scenario 3: on the leads’ form, add a selection field with the "
"values:'Tags' & 'List' & 'Checkboxes'. According to the value of the field, "
"show tags as many2many_tags, many2many_radio, or many2many(_list).**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:89
msgid ""
"In your form view, add a *Tags* field and relate it to *Partners Tag*. Under"
" *Properties*, define its *Widget* as *Many2many*. Do the same process "
"another 2 times for *Checkboxes* and *Tags*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:96
msgid "Now, add a *Selection* field and the necessary values."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:99
msgid ""
"Continue by selecting your *Tags* fields, one by one, to set their "
"*Invisible* options according to their *Widget*. In the example below, the "
"invisibility rule for the *Partner Tags* is set as: *Select Tag type > is "
"not = > Tags.*"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:105
msgid ""
"**Case scenario 4: on a quotation’s form, add a selection field called "
"'Manager Validation' with the values: ‘Accepted’ and ‘Refused’. Only a sales"
" manager can see it, and the field should be set as mandatory if the untaxed"
" amount is higher than 500€.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:109
msgid ""
"On your quotation form, add a *Selection* field with the values *Accepted* "
"and *Refused*. Set its *Required* condition as *Untaxed Amount > 500* and "
"the *Limit visibility to groups* as *Sales / Administrator* or managers."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:117
msgid "**Case scenario 5: change the tooltip of a field for all views.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:119
msgid ""
"Activate the :doc:`Developer mode <../../general/developer_mode/activate>` "
"and open Studio."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:122
msgid ""
"Select the necessary field and, under *Properties*, click on *More* to write"
" your tooltip message on *Field Help*. The tooltip message is the "
"explanatory message shown when the user hovers the field. The message here "
"written is displayed on all views forms where the field is added."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:129
msgid ""
"The *Field Help* message can only be applied to *new* fields. If you would "
"like to change/apply a tooltip for a specific field, use the *Help Tooltip* "
"option under *Properties*."
msgstr ""
#: ../../studio/use_cases/views.rst:3
msgid "Advanced Use Cases: Views"
msgstr ""
#: ../../studio/use_cases/views.rst:5
msgid ""
"**Case scenario 1: in Sales, show orders in a Kanban View instead of a List "
"View.**"
msgstr ""
#: ../../studio/use_cases/views.rst:7
msgid ""
"From the Sales page, access Studio and, under *Views*, set the *Kanban* "
"option as the default one."
msgstr ""
#: ../../studio/use_cases/views.rst:14
msgid ""
"**Case scenario 2: allow for the list of leads to be edited inline without "
"having to switch to the form view.**"
msgstr ""
#: ../../studio/use_cases/views.rst:19
msgid ""
"On the *List View*, under *View* > *Editable*, choose between *New record on"
" top* or *New record at the bottom*. This way, besides defining the order in"
" which new records are displayed in the view, you are able to edit them."
msgstr ""
#: ../../studio/use_cases/views.rst:21
msgid ""
"If the field is left blank, no editing is possible and records are shown "
"based on your column preferences on the lead's page (front-end)."
msgstr ""

516
locale/es/LC_MESSAGES/support.po Normal file
View File

@ -0,0 +1,516 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# David Arnold <blaggacao@users.noreply.github.com>, 2020
# Noemi Nahomy <noemi.t.angles@gmail.com>, 2020
# Alejandro Kutulas <alk@odoo.com>, 2020
# Jesse Garza <jga@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:42+0000\n"
"Last-Translator: Jesse Garza <jga@odoo.com>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: es\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../support.rst:5
msgid "Support"
msgstr "Soporte"
#: ../../support/supported_versions.rst:6
msgid "Supported versions"
msgstr "Versiones con soporte"
#: ../../support/supported_versions.rst:9
msgid ""
"Odoo provides support and bug fixing **for the 3 last major versions** of "
"Odoo."
msgstr ""
"Odoo provee soporte y corrección de \"bugs\" **a las últimas 3 versiones "
"mayores** de Odoo."
#: ../../support/supported_versions.rst:11
msgid ""
"Users hosted on **Odoo Online** may use intermediary versions (sometimes "
"called *SaaS versions*) that are supported as well. These versions are not "
"published for Odoo.sh or On-Premise installations."
msgstr ""
"Usuarios hospedados en **Odoo Online** pueden usar versiones intermedias (a "
"veces llamadas *versiones SaaS*) que también reciben soporte. Estas "
"versiones no se publican para Odoo.sh o para instalaciones \"On-Premise\"."
#: ../../support/supported_versions.rst:17
msgid "What's the support status of my Odoo?"
msgstr "¿Cuál es el estatus de soporte para mi versión de Odoo?"
#: ../../support/supported_versions.rst:19
msgid "This matrix shows the support status of every version."
msgstr "Esta tabla muestra el estatus de soporte para todas las versiones."
#: ../../support/supported_versions.rst:21
msgid "**Major releases are in bold type.**"
msgstr "**Versiones mayores en negrita.**"
#: ../../support/supported_versions.rst:24
msgid "Odoo Online"
msgstr "Odoo en línea"
#: ../../support/supported_versions.rst:24
msgid "Odoo.sh"
msgstr "Odoo.sh"
#: ../../support/supported_versions.rst:24
msgid "On-Premise"
msgstr "On-Premise"
#: ../../support/supported_versions.rst:24
msgid "Release date"
msgstr "Fecha de lanzamiento"
#: ../../support/supported_versions.rst:26
msgid "**Odoo 14.0**"
msgstr ""
#: ../../support/supported_versions.rst:26
#: ../../support/supported_versions.rst:26
#: ../../support/supported_versions.rst:26
msgid "🏁"
msgstr ""
#: ../../support/supported_versions.rst:26
msgid "October 2020"
msgstr ""
#: ../../support/supported_versions.rst:28
msgid "**Odoo 13.0**"
msgstr "**Odoo 13.0**"
#: ../../support/supported_versions.rst:28
#: ../../support/supported_versions.rst:28
#: ../../support/supported_versions.rst:28
#: ../../support/supported_versions.rst:30
#: ../../support/supported_versions.rst:32
#: ../../support/supported_versions.rst:32
#: ../../support/supported_versions.rst:32
#: ../../support/supported_versions.rst:34
#: ../../support/supported_versions.rst:36
#: ../../support/supported_versions.rst:36
#: ../../support/supported_versions.rst:36
msgid "|green|"
msgstr ""
#: ../../support/supported_versions.rst:28
msgid "October 2019"
msgstr "Octubre 2019"
#: ../../support/supported_versions.rst:30
msgid "Odoo 12.saas~3"
msgstr ""
#: ../../support/supported_versions.rst:30
#: ../../support/supported_versions.rst:30
#: ../../support/supported_versions.rst:34
#: ../../support/supported_versions.rst:34
#: ../../support/supported_versions.rst:38
#: ../../support/supported_versions.rst:38
#: ../../support/supported_versions.rst:40
#: ../../support/supported_versions.rst:40
#: ../../support/supported_versions.rst:44
#: ../../support/supported_versions.rst:44
#: ../../support/supported_versions.rst:46
#: ../../support/supported_versions.rst:48
#: ../../support/supported_versions.rst:48
#: ../../support/supported_versions.rst:50
msgid "N/A"
msgstr "N/A"
#: ../../support/supported_versions.rst:30
msgid "August 2019"
msgstr "Agosto 2019"
#: ../../support/supported_versions.rst:32
msgid "**Odoo 12.0**"
msgstr ""
#: ../../support/supported_versions.rst:32
msgid "October 2018"
msgstr "Octubre 2018"
#: ../../support/supported_versions.rst:34
msgid "Odoo 11.saas~3"
msgstr ""
#: ../../support/supported_versions.rst:34
msgid "April 2018"
msgstr "Abril 2018"
#: ../../support/supported_versions.rst:36
msgid "**Odoo 11.0**"
msgstr ""
#: ../../support/supported_versions.rst:36
msgid "October 2017"
msgstr "Octubre 2017"
#: ../../support/supported_versions.rst:36
msgid "*End-of-support is planned for October 2020*"
msgstr "*Fin de soporte planificado para octubre 2020*"
#: ../../support/supported_versions.rst:38
msgid "Odoo 10.saas~15"
msgstr ""
#: ../../support/supported_versions.rst:38
#: ../../support/supported_versions.rst:40
#: ../../support/supported_versions.rst:42
#: ../../support/supported_versions.rst:42
#: ../../support/supported_versions.rst:44
#: ../../support/supported_versions.rst:46
#: ../../support/supported_versions.rst:48
#: ../../support/supported_versions.rst:50
msgid "|orange|"
msgstr ""
#: ../../support/supported_versions.rst:38
msgid "March 2017"
msgstr "Marzo 2017"
#: ../../support/supported_versions.rst:40
msgid "Odoo 10.saas~14"
msgstr ""
#: ../../support/supported_versions.rst:40
msgid "January 2017"
msgstr "Enero 2017"
#: ../../support/supported_versions.rst:42
msgid "**Odoo 10.0**"
msgstr ""
#: ../../support/supported_versions.rst:42
#: ../../support/supported_versions.rst:46
#: ../../support/supported_versions.rst:50
msgid "|red|"
msgstr ""
#: ../../support/supported_versions.rst:42
msgid "October 2016"
msgstr "Octubre 2016"
#: ../../support/supported_versions.rst:44
msgid "Odoo 9.saas~11"
msgstr ""
#: ../../support/supported_versions.rst:44
msgid "May 2016"
msgstr "Mayo 2016"
#: ../../support/supported_versions.rst:46
msgid "**Odoo 9.0**"
msgstr ""
#: ../../support/supported_versions.rst:46
msgid "October 2015"
msgstr "Octubre 2015"
#: ../../support/supported_versions.rst:48
msgid "Odoo 8.saas~6"
msgstr ""
#: ../../support/supported_versions.rst:48
msgid "February 2015"
msgstr "Febrero 2015"
#: ../../support/supported_versions.rst:50
msgid "**Odoo 8.0**"
msgstr ""
#: ../../support/supported_versions.rst:50
msgid "September 2014"
msgstr "Septiembre 2014"
#: ../../support/supported_versions.rst:56
msgid "|green| Supported version"
msgstr "|green| Versión con soporte"
#: ../../support/supported_versions.rst:58
msgid "|red| End-of-support"
msgstr "|red| Fin de soporte"
#: ../../support/supported_versions.rst:60
msgid "N/A Never released for this platform"
msgstr "N/A Nunca hubo par esta plataforma"
#: ../../support/supported_versions.rst:62
msgid ""
"|orange| Some of our older customers may still run this version on our Odoo "
"Online servers, we provide help only on blocking issues and advise you to "
"upgrade."
msgstr ""
"|orange| Algunos de nuestros clientes más antiguos quizás aún usen esta "
"versión en nuestros servidores de Odoo Online, para ellos únicamente "
"apoyamos con asuntos que estén bloqueando su operación y recomendamos que se"
" actualicen a una versión posterior."
#: ../../support/supported_versions.rst:64
msgid "🏁 Future version, not released yet"
msgstr "🏁 Versión futura, aún no disponibe"
#: ../../support/supported_versions.rst:77
msgid "I run an older version of Odoo/OpenERP/TinyERP"
msgstr "Uso una versión más antigua de Odoo/OpenERP/TinyERP"
#: ../../support/supported_versions.rst:79
msgid ""
"OpenERP 7.0, 6.1, 6.0 and 5.0 is not supported anymore, on any platform."
msgstr ""
"OpenERP 7.0, 6.1, 6.0 y 5.0 ya no reciben soporte, en ninguna plataforma."
#: ../../support/supported_versions.rst:81
msgid ""
"TinyERP 4.0, 3.0, 2.0 and 1.0 is not supported anymore, on any platform."
msgstr ""
"TinyERP 4.0, 3.0, 2.0 y 1.0 ya no reciben soporte, en ninguna plataforma."
#: ../../support/supported_versions.rst:83
msgid ""
"You should consider `upgrading <https://upgrade.odoo.com/>`_ your database."
msgstr "Considera `actualizar <https://upgrade.odoo.com/>`_ tu base de datos."
#: ../../support/what_can_i_expect.rst:8
msgid "What can I expect from the support service?"
msgstr "¿Qué puedo esperar del equipo de soporte?"
#: ../../support/what_can_i_expect.rst:12
msgid "5 days a week"
msgstr "5 días a la semana"
#: ../../support/what_can_i_expect.rst:14
msgid ""
"Your Odoo Online subscription includes **unlimited 24hr support at no extra "
"cost, Monday to Friday**. Our teams are located around the world to ensure "
"you have support, no matter your location. Your support representative could"
" be communicating to you from San Francisco, Belgium, or India!"
msgstr ""
"Tu suscripción online incluye **soporte ilimitado 24 horas sin costo extra, "
"lunes a viernes**. Nuestros equipos están localizados alrededor del mundo "
"para asegurar que tengas soporte, sin importar tu ubicación. ¡Tu asesor de "
"soporte puede estar en San Francisco, Bélgica, o India!"
#: ../../support/what_can_i_expect.rst:19
msgid ""
"Our support team can be contacted through our `online support form "
"<https://www.odoo.com/help>`__."
msgstr ""
"Nuestro equipo de soporte puede ser contactado a través de nuestro "
"`formulario de soporte online <https://www.odoo.com/help>`__."
#: ../../support/what_can_i_expect.rst:23
msgid "What kind of support is included?"
msgstr "¿Qué tipo de soporte está incluido?"
#: ../../support/what_can_i_expect.rst:25
msgid ""
"Providing you with relevant material (guidelines, product documentation, "
"etc...)"
msgstr ""
"Proveerte con material relevante (guías, documentación de producto, etc...)"
#: ../../support/what_can_i_expect.rst:27
msgid ""
"Answers to issues that you may encounter in your standard Odoo database (eg."
" “I cannot close my Point of Sale” or “I cannot find my sales KPIs?”)"
msgstr ""
"Respuestas a preguntas o problemas relacionados con tu base de datos de Odoo"
" estándar (por ej., “No puedo cerrar mi Punto de Venta” o “¿Dónde puedo "
"encontrar los KPI's de ventas?”)"
#: ../../support/what_can_i_expect.rst:29
msgid "Questions related to your account, subscription, or billing"
msgstr "Preguntas relacionadas con tu cuenta, suscripción, o facturación."
#: ../../support/what_can_i_expect.rst:30
msgid ""
"Bug resolution (blocking issues or unexpected behaviour not due to "
"misconfiguration or customization)"
msgstr ""
"Resolución de \"bugs\" (problemas que estén bloqueando el servicio o "
"comportamientos inesperados que no se deban a configuraciones erróneas o "
"personalizaciones)"
#: ../../support/what_can_i_expect.rst:32
msgid ""
"Issues that might occur in a test database after upgrading to a newer "
"version"
msgstr ""
"Situaciones que pueden ocurrir en una base de datos de prueba después de "
"actualizar a una nueva versión"
#: ../../support/what_can_i_expect.rst:34
msgid ""
"*Odoo Support does not make changes to your production database without your"
" agreement and gives you the material and knowledge to do it yourself!*"
msgstr ""
#: ../../support/what_can_i_expect.rst:39
msgid "What kind of support is not included?"
msgstr "¿Qué tipo de soporte no está incluido?"
#: ../../support/what_can_i_expect.rst:41
msgid ""
"Questions that require us to understand your business processes in order to "
"help you implement your database"
msgstr ""
"Preguntas relacionadas a la implementación de tu base de datos que requieran"
" que entendamos tus procesos de negocio específicos"
#: ../../support/what_can_i_expect.rst:43
msgid ""
"Training on how to use our software (we will direct you to our many "
"resources)"
msgstr ""
"Entrenamiento en cómo usar el software (te dirigiremos\n"
" a nuestros variados recursos)"
#: ../../support/what_can_i_expect.rst:44
msgid "Import of documents into your database"
msgstr "Cómo importar información o documentos a tu base de datos"
#: ../../support/what_can_i_expect.rst:45
msgid ""
"Guidance on which configurations to apply inside of an application or the "
"database"
msgstr ""
"Orientación respecto a cómo configurar las aplicaciones o la base de datos"
#: ../../support/what_can_i_expect.rst:46
msgid ""
"How to set up configuration models (Examples include: Inventory Routes, "
"Payment Terms, Warehouses, etc)"
msgstr ""
"Cómo fijar modelos de configuración (tales como rutas de inventario, "
"términos de pago, bodegas, etc.)"
#: ../../support/what_can_i_expect.rst:48
msgid "Any intervention on your own servers/deployments of Odoo"
msgstr ""
"Cualquier intervención en tus propios servidores o instalaciones de Odoo"
#: ../../support/what_can_i_expect.rst:49
msgid ""
"Any intervention on your own third party account (Ingenico, Authorize, UPS, "
"etc)"
msgstr ""
"Cualquier intervención en las cuentas que tengas en otras compañías "
"(Ingenico, Authorize, UPS, etc.)"
#: ../../support/what_can_i_expect.rst:50
msgid ""
"Questions or issues related to specific developments or customizations done "
"either by Odoo or a third party (this is specific only to your database or "
"involving code)"
msgstr ""
"Preguntas o asuntos relacionados a desarrollos o personalizaciones hechas "
"específicamente para tu base de datos, ya sea por Odoo o un tercero (así "
"como cualquier asunto relacionado con programación)"
#: ../../support/what_can_i_expect.rst:54
msgid ""
"You can get this type of support with a `Success Pack <https://www.odoo.com"
"/pricing-packs>`__. With a pack, one of our consultants will analyze the way"
" your business runs and tell you how you can get the most out of your Odoo "
"Database. We will handle all configurations and coach you on how to use "
"Odoo."
msgstr ""
"Puedes tener este tipo de soporte con un `Success Pack <https://www.odoo.com"
"/pricing-packs>`__. Con un pack, uno de nuestros consultores analizará la "
"manera que manejas tu negocio y te dirá cómo puedes optimizar el uso de tu "
"base de datos de Odoo. Haremos todas las configuraciones y te entrenaremos "
"en cómo usar Odoo."
#: ../../support/where_can_i_get_support.rst:6
msgid "Where to find help?"
msgstr "¿Dónde encuentro ayuda?"
#: ../../support/where_can_i_get_support.rst:10
msgid "Odoo Enterprise"
msgstr "Odoo Enterprise"
#: ../../support/where_can_i_get_support.rst:12
msgid ""
"Users who have a valid Odoo Enterprise subscription may always contact our "
"support teams through our `support form <https://www.odoo.com/help>`_, no "
"matter the hosting type you chose (Odoo Online, Odoo.sh or on your own "
"server)."
msgstr ""
"Usuarios con una suscripción activa de Odoo Enterprise pueden contactar al "
"equipo de soporte a través de nuestro `formulario de soporte "
"<https://www.odoo.com/help>`_, sin importar el tipo de hospedaje (Odoo "
"Online, Odoo.sh, o tu propio servidor)."
#: ../../support/where_can_i_get_support.rst:16
msgid "Please include in your request:"
msgstr "Por favor incluye en tu solicitud de apoyo:"
#: ../../support/where_can_i_get_support.rst:18
msgid "your subscription number"
msgstr "tu número de suscripción"
#: ../../support/where_can_i_get_support.rst:19
msgid ""
"the URL of your database if your database is hosted by Odoo (Odoo Online or "
"Odoo.sh)"
msgstr ""
"el URL de la base de datos si está hospedada en los servidores de Odoo (Odoo"
" Online u Odoo.sh)"
#: ../../support/where_can_i_get_support.rst:21
msgid "Our agents will get back to you as soon as possible."
msgstr "Nuestros agentes se pondrán en contacto contigo lo antes posible."
#: ../../support/where_can_i_get_support.rst:25
msgid "Odoo Community"
msgstr "Odoo Community"
#: ../../support/where_can_i_get_support.rst:27
msgid "*Odoo Community users don't get access to the support service.*"
msgstr ""
"*Los usuarios de Odoo Community no tienen acceso al servicio de soporte.*"
#: ../../support/where_can_i_get_support.rst:29
msgid "Here are some resources that might help you:"
msgstr "Estos son algunos de los recursos con los que te puedes apoyar:"
#: ../../support/where_can_i_get_support.rst:31
msgid "Our `documentation pages <https://www.odoo.com/page/docs>`_."
msgstr "Nuestro `sitio de documentación <https://www.odoo.com/page/docs>`_."
#: ../../support/where_can_i_get_support.rst:32
msgid ""
"Ask your question on the `community forum "
"<https://www.odoo.com/forum/help-1>`_."
msgstr ""
"Haz tu pregunta en el `foro comunitario "
"<https://www.odoo.com/forum/help-1>`_."
#: ../../support/where_can_i_get_support.rst:33
msgid ""
"`Buy Odoo Enterprise "
"<https://www.odoo.com/documentation/13.0/setup/enterprise.html>`_ to get the"
" support and bugfix services."
msgstr ""
"`Adquiere Odoo Enterprise "
"<https://www.odoo.com/documentation/13.0/setup/enterprise.html>`_ para "
"obtener soporte y servicios de corrección de \"bugs\"."

242
locale/es/LC_MESSAGES/survey.po Normal file
View File

@ -0,0 +1,242 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Lina Maria Avendaño Carvajal <lina8823@gmail.com>, 2020
# José Vicente <txusev@gmail.com>, 2020
# Jesse Garza <jga@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:42+0000\n"
"Last-Translator: Jesse Garza <jga@odoo.com>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: es\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../survey.rst:5
msgid "Survey"
msgstr "Encuesta"
#: ../../survey/overview.rst:3
msgid "Overview"
msgstr "Información general"
#: ../../survey/overview/create.rst:3
msgid "Get Started with Surveys"
msgstr ""
#: ../../survey/overview/create.rst:5
msgid ""
"Surveys can be used for a range of purposes that can go from collecting "
"customer feedback, evaluate the success of an event, measure how pleased "
"customers are with your products/services, gauge whether employees are happy"
" and satisfied with their work environment, and even to find out what your "
"market is thinking."
msgstr ""
#: ../../survey/overview/create.rst:11
msgid "Get started"
msgstr "Empezar"
#: ../../survey/overview/create.rst:13
msgid ""
"When creating your survey, choose a *Title* and *Category*. The *Category* "
"field is used to know in which context the survey is being conducted, as "
"different applications might use it for different purposes such as "
"recruitment, certification, or employee appraisal."
msgstr ""
#: ../../survey/overview/create.rst:22
msgid "Tab: Questions"
msgstr ""
#: ../../survey/overview/create.rst:24
msgid "Add sections and questions by clicking on the respective links."
msgstr ""
#: ../../survey/overview/create.rst:27
msgid ""
"On the *Sections and Questions* form, once the question type is chosen and "
"the answer added, under the tab *Options*, enable *Mandatory Answer*, and "
"set an *Error message* to be shown when the user tries to submit the survey "
"without answering the respective question."
msgstr ""
#: ../../survey/overview/create.rst:29
msgid ""
"Depending on the *Question Type*, the tab *Options* aggregates extra and "
"different possibilities. Examples:"
msgstr ""
#: ../../survey/overview/create.rst:31
msgid ""
"*Single Line Text Box* - can choose a minimum and maximum text length "
"(number of characters - spaces do not count), and its error message."
msgstr ""
#: ../../survey/overview/create.rst:33
msgid ""
"*Multiple choice: multiple answers allowed*: choose between radio buttons or"
" a dropdown menu list, and if you would like to have a comment field. If the"
" user select an answer and type a comment, the values are separately "
"recorded. Or, enable the comment field to be displayed as an answer choice, "
"with which a text type field is displayed."
msgstr ""
#: ../../survey/overview/create.rst:37
msgid ""
"*Matrix Type*: choose if you would like to have one or multiple choices per "
"row."
msgstr ""
#: ../../survey/overview/create.rst:44
msgid "Tab: Description"
msgstr ""
#: ../../survey/overview/create.rst:46
msgid ""
"Write a *Description* to be displayed under the title of the survey's "
"homepage."
msgstr ""
#: ../../survey/overview/create.rst:53
msgid "Click on *Edit* to personalize your pages with the website builder."
msgstr ""
#: ../../survey/overview/create.rst:56
msgid "Tab: Options"
msgstr ""
#: ../../survey/overview/create.rst:58
msgid ""
"Under the tab *Options*, choose the *Layout* of your questions. If choosing "
"*One page per section* or *One page per question*, an option *Back Button* "
"becomes available, which allows the user to go back pages."
msgstr ""
#: ../../survey/overview/create.rst:67
msgid "Test and share the survey"
msgstr ""
#: ../../survey/overview/create.rst:70
msgid ""
"Once your Survey is ready, *Test* it to avoid *Sharing* it with potential "
"errors. As answers get collected, click on *Answers* to access all the "
"details of the respondent and his answers."
msgstr ""
#: ../../survey/overview/create.rst:72
msgid ""
"By default, a filter *Except Test Entries* is applied to keep the list of "
"entries clean with only real participants."
msgstr ""
#: ../../survey/overview/create.rst:79
msgid ""
"Another way to access detailed answers is by going to "
":menuselection:`Participations --> Participations`."
msgstr ""
#: ../../survey/overview/create.rst:80
msgid "Click on *See results* to be redirected to an analytical page."
msgstr ""
#: ../../survey/overview/create.rst:87
#: ../../survey/overview/time_random.rst:34
msgid ":doc:`scoring`"
msgstr ""
#: ../../survey/overview/create.rst:88 ../../survey/overview/scoring.rst:35
msgid ":doc:`time_random`"
msgstr ""
#: ../../survey/overview/scoring.rst:3
msgid "Scoring Surveys"
msgstr ""
#: ../../survey/overview/scoring.rst:5
msgid ""
"To measure your respondent’s performance, knowledge of a subject, or overall"
" satisfaction, attach points to the answers of specific questions. The "
"points are summed up to give your respondent a final score."
msgstr ""
#: ../../survey/overview/scoring.rst:9
msgid ""
"On your survey’s form, click on *Add a question* and, under the tab "
"*Options*, choose between *Scoring with answers at the end* or *Scoring "
"without answers at the end*. Now, on your question’s form, set the right "
"answer and score."
msgstr ""
#: ../../survey/overview/scoring.rst:17
msgid ""
"Set the percentage score the user needs to achieve to have successfully "
"taken the survey. If enabling *Certificate*, choose its template. The "
"certification is automatically sent by email to the users who successfully "
"finish it."
msgstr ""
#: ../../survey/overview/scoring.rst:25
msgid ""
"Enable *Login required* to be able to *Give Badges*. Badges are related to "
"the eLearning section of your website. Besides the logged-in user, visitors "
"of the website that access the page *Courses* can also see the granted "
"badges."
msgstr ""
#: ../../survey/overview/time_random.rst:3
msgid "Time and Randomize Questions"
msgstr ""
#: ../../survey/overview/time_random.rst:6
msgid "Time Limit"
msgstr ""
#: ../../survey/overview/time_random.rst:10
msgid ""
"On timed surveys, respondents need to complete the survey within a certain "
"period of time. It can be used to ensure that all respondents get the same "
"amount of time to find the answers, or to decrease the chance of having them"
" looking at external resources."
msgstr ""
#: ../../survey/overview/time_random.rst:11
msgid "Set the *Time limit* under the tab *Options*."
msgstr ""
#: ../../survey/overview/time_random.rst:17
msgid ""
"A timer is shown on the pages so the user can keep track of the remaining "
"time. Surveys not \\ submitted by the *Time limit* do not have their answers"
" saved."
msgstr ""
#: ../../survey/overview/time_random.rst:21
msgid "Selection"
msgstr "Selección"
#: ../../survey/overview/time_random.rst:25
msgid ""
"When you randomize a survey, you allow for the questions to be shuffled in a"
" random order every time someone opens the questionnaire. This can be useful"
" to avoid having respondents looking at each others' answers."
msgstr ""
#: ../../survey/overview/time_random.rst:27
msgid ""
"To do so, under the tab *Options*, enable *Randomized per section*. Now, "
"under the tab *Questions*, set how many of the questions in that section "
"should be taken into account during the shuffling."
msgstr ""

225
locale/es/LC_MESSAGES/timesheets.po Normal file
View File

@ -0,0 +1,225 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Lina Maria Avendaño Carvajal <lina8823@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 15:13+0000\n"
"Last-Translator: Lina Maria Avendaño Carvajal <lina8823@gmail.com>, 2020\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: es\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../timesheets.rst:5
msgid "Timesheets"
msgstr "Partes de horas"
#: ../../timesheets/overview.rst:3
msgid "Overview"
msgstr "Información general"
#: ../../timesheets/overview/compare.rst:3
msgid "Compare Hours and do Analyses"
msgstr ""
#: ../../timesheets/overview/compare.rst:5
msgid ""
"Make sure your employees’ workload is being fairly distributed and control "
"your tasks to get powerful insights when comparing planned versus effective "
"hours."
msgstr ""
#: ../../timesheets/overview/compare.rst:9
msgid "Compare the planned and effective hours of your tasks"
msgstr ""
#: ../../timesheets/overview/compare.rst:11
msgid ""
"Go to :menuselection:`Project --> Reporting --> Tasks Analysis`, select the "
"*Pivot* view and refine your *Measures* to *Effective Hours* and *Planned "
"Hours*."
msgstr ""
#: ../../timesheets/overview/compare.rst:18
msgid ""
"Still on *Project*, under :menuselection:`Reporting --> Planning Analysis` "
"find a pivot view with an analysis of allocated and effective hours of your "
"tasks by user and start date, or by any of the other available filters."
msgstr ""
#: ../../timesheets/overview/compare.rst:27
msgid "HR analysis"
msgstr ""
#: ../../timesheets/overview/compare.rst:29
msgid ""
"Under :menuselection:`Timesheets --> Reporting --> Timesheet/Attendance` "
"have an overview of the worked hours and allocated time of your employees."
msgstr ""
#: ../../timesheets/overview/get_started.rst:3
msgid "Get Started with Timesheets"
msgstr ""
#: ../../timesheets/overview/get_started.rst:5
msgid ""
"When you use timesheets (from any device, anywhere) to track the time spent "
"on tasks, you are able to bill customers for the exact right amount they "
"should be billed. In addition to it, add a description of the work done to "
"have a reliable tracking and history, and compare the forecasted times, all "
"in favor of becoming a more proactive company."
msgstr ""
#: ../../timesheets/overview/get_started.rst:11
msgid "Choose an encoding unit"
msgstr ""
#: ../../timesheets/overview/get_started.rst:14
msgid ""
"Under :menuselection:`Timesheets --> Configuration --> Settings`, choose the"
" unit of measure to register your timesheet. This provides tools and widgets"
" to help you encoding."
msgstr ""
#: ../../timesheets/overview/get_started.rst:15
msgid "*Minimal duration* is the minimum time at which a task is recorded."
msgstr ""
#: ../../timesheets/overview/get_started.rst:18
msgid ""
"*Rounding up* allows you to time up or down to the nearest minutes or hours."
" For example: if the interval is set to 30min, a 14min entry will show up in"
" reports as 0min, and a 29min entry as 30min."
msgstr ""
#: ../../timesheets/overview/get_started.rst:25
msgid "Reportings are expressed in hours, the default value."
msgstr ""
#: ../../timesheets/overview/get_started.rst:28
msgid "Create a task from a SO & timesheet on it"
msgstr ""
#: ../../timesheets/overview/get_started.rst:30
msgid ""
"Under the *General Settings* of your product, categorize it as a service."
msgstr ""
#: ../../timesheets/overview/get_started.rst:34
msgid ""
"On the *Sales* tab, (section *Sales Invoicing Policy*) choose if you want to"
" invoice customers based on the quantity previous ordered (the one sent on a"
" quotation, for instance), on the time recorded (while the service was being"
" executed), or by manually adding the time spent when creating the invoice."
msgstr ""
#: ../../timesheets/overview/get_started.rst:37
msgid ""
"Chose the right *Service Tracking* for you and, from now on, when a sales "
"order is confirmed, Odoo automatically creates a task/project (if that was "
"the chosen option) and allows you to timesheet on it."
msgstr ""
#: ../../timesheets/overview/get_started.rst:44
msgid "Choose an Invoicing Policy"
msgstr ""
#: ../../timesheets/overview/get_started.rst:46
msgid ""
"Go to :menuselection:`Timesheets --> Configuration --> Settings` and choose "
"if you want the recorded time to be directly invoiced, or if it should be "
"approved first."
msgstr ""
#: ../../timesheets/overview/get_started.rst:54
msgid "Send reminders"
msgstr ""
#: ../../timesheets/overview/get_started.rst:57
msgid ""
"Choose to have an automatic email being sent to all users and managers who "
"have not recorded their times."
msgstr ""
#: ../../timesheets/overview/get_started.rst:59
msgid ""
"Go to :menuselection:`Timesheets --> Configuration --> Settings` and enable "
"the *Employee Reminder* and *Manager Reminder* features."
msgstr ""
#: ../../timesheets/overview/get_started.rst:66
msgid ""
"Odoo Timesheets continues to run even if there is no internet connection. "
"The data syncs once you are back online."
msgstr ""
#: ../../timesheets/overview/time_off.rst:3
msgid "Create Timesheets upon Time Off Validation"
msgstr ""
#: ../../timesheets/overview/time_off.rst:5
msgid ""
"Odoo automatically timesheets on project/tasks upon time off requests. This "
"allows for better overall control over the validation of timesheets, as it "
"does not leave place for forgetfulness and questions after hours that have "
"not been timesheeted by the employee."
msgstr ""
#: ../../timesheets/overview/time_off.rst:9
msgid ""
"Activate the :doc:`Developer mode <../../general/developer_mode/activate>`, "
"go to *Timesheets*, and change the *Project* and *Task* set by default, if "
"you like."
msgstr ""
#: ../../timesheets/overview/time_off.rst:16
msgid ""
"Go to :menuselection:`Time Off --> Configuration --> Time Off Types`. Select"
" or create the needed type, and decide if you would like the requests to be "
"validated or not."
msgstr ""
#: ../../timesheets/overview/time_off.rst:26
msgid ""
"Now, once the employee has requested his time off and the request has been "
"validated (or not, depending on the setting chosen), the time is "
"automatically allocated on *Timesheets*, under the respective project and "
"task."
msgstr ""
#: ../../timesheets/overview/time_off.rst:27
msgid ""
"On the example below, the user requested *Paid Time off* from July 13th to "
"15th."
msgstr ""
#: ../../timesheets/overview/time_off.rst:33
msgid ""
"Considering that validation is not required, the requested time off is "
"automatically displayed in *Timesheets*. If validation is necessary, the "
"time is automatically allocated after the responsible person for validating "
"does it so."
msgstr ""
#: ../../timesheets/overview/time_off.rst:41
msgid ""
"Click on the magnifying glass, hovering over the concerned cell, to access "
"all the aggregated data on that cell (day), and see details regarding the "
"project/task."
msgstr ""
#: ../../timesheets/overview/time_off.rst:49
msgid ":doc:`compare`"
msgstr ""

2454
locale/es/LC_MESSAGES/website.po
View File

File diff suppressed because it is too large Load Diff

15589
locale/fr/LC_MESSAGES/accounting.po
View File

File diff suppressed because it is too large Load Diff

12
locale/fr/LC_MESSAGES/applications.po
View File

@ -3,17 +3,13 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Richard Mathot <rim@odoo.com>, 2019
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Last-Translator: Richard Mathot <rim@odoo.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -23,4 +19,4 @@ msgstr ""
#: ../../applications.rst:3
msgid "Applications"
msgstr "Applications"
msgstr ""

1739
locale/fr/LC_MESSAGES/contributing.po Normal file
View File

File diff suppressed because it is too large Load Diff

795
locale/fr/LC_MESSAGES/crm.po
View File

File diff suppressed because it is too large Load Diff

201
locale/fr/LC_MESSAGES/db_management.po
View File

@ -3,20 +3,13 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2019
# Lucas Deliege <lud@odoo.com>, 2019
# Rémi FRANÇOIS <remi@sudokeys.com>, 2019
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2019
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Last-Translator: Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -113,7 +106,7 @@ msgstr ""
#: ../../db_management/db_online.rst:51
msgid "Upgrade"
msgstr "Mettre à jour"
msgstr ""
#: ../../db_management/db_online.rst:53
msgid ""
@ -221,7 +214,7 @@ msgid ""
" Even though we test all upgrades manually, we do not know your work "
"processes. A change in standard worfklows of Odoo in new versions might "
"require you to change internal processes, or some of the customizations you "
"made through Odoo Studio might now work properly. *It is up to you to make "
"made through Odoo Studio might not work properly. *It is up to you to make "
"sure that everything works as it should!* You can report issues with your "
"test database through our `Support page <https://www.odoo.com/help>`__."
msgstr ""
@ -244,7 +237,7 @@ msgid ""
"the process is completed."
msgstr ""
#: ../../db_management/db_online.rst:139
#: ../../db_management/db_online.rst:140
msgid ""
"Your database will be taken offline during the upgrade (usually between "
"30min up to several hours for big databases), so make sure to plan your "
@ -268,10 +261,6 @@ msgid ""
"buttons. To duplicate your database, just click **Duplicate**. You will have"
" to give a name to your duplicate, then click **Duplicate Database**."
msgstr ""
"Sur la ligne de la base de données que vous souhaitez dupliquer, vous verrez"
" quelques boutons. Pour dupliquer votre base de données, il suffit de "
"cliquer sur **Dupliquer**. Vous devrez donner un nom à votre copie, puis "
"cliquez sur **Dupliquer la base de données**."
#: ../../db_management/db_online.rst:160
msgid ""
@ -281,7 +270,7 @@ msgstr ""
#: ../../db_management/db_online.rst:163
msgid "Emails are sent"
msgstr "Les courriels sont envoyés"
msgstr ""
#: ../../db_management/db_online.rst:165
msgid ""
@ -291,11 +280,11 @@ msgstr ""
#: ../../db_management/db_online.rst:168
msgid "Delivery orders (shipping providers) are sent"
msgstr "Les bons de livraison (fournisseurs d'expédition) sont envoyés"
msgstr ""
#: ../../db_management/db_online.rst:170
msgid "Etc."
msgstr "Etc."
msgstr ""
#: ../../db_management/db_online.rst:172
msgid ""
@ -308,20 +297,16 @@ msgid ""
"After a few seconds, you will be logged in your duplicated database. Notice "
"that the url uses the name you chose for your duplicated database."
msgstr ""
"Après quelques secondes, vous serez connecté à votre copie de base de "
"données. Notez que l'URL utilise le nom que vous avez choisi lors de la "
"duplication."
#: ../../db_management/db_online.rst:179
#: ../../db_management/db_online.rst:180
msgid "Duplicate databases expire automatically after 15 days."
msgstr ""
"Les copies de bases de données expirent automatiquement après 15 jours."
#: ../../db_management/db_online.rst:187
#: ../../db_management/db_online.rst:188
msgid "Rename a Database"
msgstr ""
#: ../../db_management/db_online.rst:189
#: ../../db_management/db_online.rst:190
msgid ""
"To rename your database, make sure you are connected to the database you "
"want to rename, access the `database management page "
@ -329,15 +314,15 @@ msgid ""
"to give a new name to your database, then click **Rename Database**."
msgstr ""
#: ../../db_management/db_online.rst:200
#: ../../db_management/db_online.rst:201
msgid "Deleting a Database"
msgstr ""
#: ../../db_management/db_online.rst:202
#: ../../db_management/db_online.rst:203
msgid "You can only delete databases of which you are the administrator."
msgstr ""
#: ../../db_management/db_online.rst:204
#: ../../db_management/db_online.rst:205
msgid ""
"When you delete your database all the data will be permanently lost. The "
"deletion is instant and for all the Users. We advise you to do an instant "
@ -345,38 +330,38 @@ msgid ""
"backup may be several hours old at that point."
msgstr ""
#: ../../db_management/db_online.rst:210
#: ../../db_management/db_online.rst:211
msgid ""
"From the `database management page <https://www.odoo.com/my/databases>`__, "
"on the line of the database you want to delete, click on the \"Delete\" "
"button."
msgstr ""
#: ../../db_management/db_online.rst:217
#: ../../db_management/db_online.rst:218
msgid ""
"Read carefully the warning message that will appear and proceed only if you "
"fully understand the implications of deleting a database:"
msgstr ""
#: ../../db_management/db_online.rst:223
#: ../../db_management/db_online.rst:224
msgid ""
"After a few seconds, the database will be deleted and the page will reload "
"automatically."
msgstr ""
#: ../../db_management/db_online.rst:227
#: ../../db_management/db_online.rst:228
msgid ""
"If you need to re-use this database name, it will be immediately available."
msgstr ""
#: ../../db_management/db_online.rst:229
#: ../../db_management/db_online.rst:230
msgid ""
"It is not possible to delete a database if it is expired or linked to a "
"Subscription. In these cases contact `Odoo Support "
"<https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_online.rst:233
#: ../../db_management/db_online.rst:234
msgid ""
"If you want to delete your Account, please contact `Odoo Support "
"<https://www.odoo.com/help>`__"
@ -412,13 +397,13 @@ msgstr ""
#: ../../db_management/db_premise.rst:31
#: ../../db_management/db_premise.rst:110
#: ../../db_management/db_premise.rst:143
#: ../../db_management/db_premise.rst:138
msgid "Solutions"
msgstr ""
#: ../../db_management/db_premise.rst:33
msgid "Do you have a valid Enterprise subscription?"
msgstr "Avez-vous un abonnement Entreprise valide ?"
msgstr ""
#: ../../db_management/db_premise.rst:35
msgid ""
@ -430,7 +415,6 @@ msgstr ""
#: ../../db_management/db_premise.rst:39
msgid "Have you already linked a database with your subscription reference?"
msgstr ""
"Avez-vous déjà associé un base de données à votre référence d'abonnement ?"
#: ../../db_management/db_premise.rst:41
msgid ""
@ -456,13 +440,11 @@ msgid "Do you have the updated version of Odoo 9?"
msgstr ""
#: ../../db_management/db_premise.rst:61
#: ../../db_management/db_premise.rst:176
#: ../../db_management/db_premise.rst:171
msgid ""
"From July 2016 onward, Odoo 9 now automatically change the uuid of a "
"duplicated database; a manual operation is no longer required."
msgstr ""
"Depuis Juillet 2016, Odoo 9 modifie maintenant automatiquement l'UUID d'une "
"base de données dupliquée; une opération manuelle n'est plus nécessaire."
#: ../../db_management/db_premise.rst:64
msgid ""
@ -533,19 +515,13 @@ msgid ""
"upsell quotation and pay for the extra users."
msgstr ""
#: ../../db_management/db_premise.rst:115
msgid "or"
msgstr "ou"
#: ../../db_management/db_premise.rst:117
#: ../../db_management/db_premise.rst:114
msgid ""
"**Deactivate users** as explained in this `Documentation "
"<https://www.odoo.com "
"/documentation/user/13.0/db_management/documentation.html#deactivating-"
"users>`__ and **Reject** the upsell quotation."
"**Deactivate users** as explained in this `documentation <documentation.html"
"#deactivating-users>`_ and **Reject** the upsell quotation."
msgstr ""
#: ../../db_management/db_premise.rst:122
#: ../../db_management/db_premise.rst:117
msgid ""
"Once your database has the correct number of users, the expiration message "
"will disappear automatically after a few days, when the next verification "
@ -554,62 +530,58 @@ msgid ""
"message disappear right away."
msgstr ""
#: ../../db_management/db_premise.rst:129
#: ../../db_management/db_premise.rst:124
msgid "Database expired error message"
msgstr ""
#: ../../db_management/db_premise.rst:131
#: ../../db_management/db_premise.rst:126
msgid ""
"If your database reaches its expiration date before your renew your "
"subscription, you will encounter this message:"
msgstr ""
#: ../../db_management/db_premise.rst:139
#: ../../db_management/db_premise.rst:134
msgid ""
"This **blocking** message appears after a non-blocking message that lasts 30"
" days. If you fail to take action before the end of the countdown, the "
"database is expired."
msgstr ""
#: ../../db_management/db_premise.rst:147
#: ../../db_management/db_premise.rst:142
msgid ""
"Renew your subscription: follow the link and renew your subscription - note "
"that"
msgstr ""
#: ../../db_management/db_premise.rst:146
#: ../../db_management/db_premise.rst:141
msgid ""
"if you wish to pay by Wire Transfer, your subscription will effectively be "
"renewed only when the payment arrives, which can take a few days. Credit "
"card payments are processed immediately."
msgstr ""
#: ../../db_management/db_premise.rst:149
#: ../../db_management/db_premise.rst:144
msgid "Contact our `Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:151
#: ../../db_management/db_premise.rst:146
msgid ""
"None of those solutions worked for you? Please contact our `Support "
"<https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:160
#: ../../db_management/db_premise.rst:155
msgid "Duplicate a database"
msgstr ""
#: ../../db_management/db_premise.rst:162
#: ../../db_management/db_premise.rst:157
msgid ""
"You can duplicate your database by accessing the database manager on your "
"server (<odoo-server>/web/database/manager). In this page, you can easily "
"duplicate your database (among other things)."
msgstr ""
"Vous pouvez dupliquer votre base de données en accédant au gestionnaire de "
"base de données sur votre serveur (<odoo-server>/web/database/manager). Dans"
" cette page, vous pouvez facilement dupliquer votre base de données (entre "
"autres choses)."
#: ../../db_management/db_premise.rst:170
#: ../../db_management/db_premise.rst:165
msgid ""
"When you duplicate a local database, it is **strongly** advised to change "
"the duplicated database's uuid (Unniversally Unique Identifier), since this "
@ -617,28 +589,15 @@ msgid ""
"databases with the same uuid could result in invoicing problems or "
"registration problems down the line."
msgstr ""
"Lorsque vous dupliquez une base de données locale, il est **fortement** "
"conseillé de changer l'UUID (Universally Unique Identifier) de la base de "
"données dupliquée, puisque cet UUID est utilisé par votre base de données "
"pour s'identifier avec nos serveurs. Avoir deux bases de données avec le "
"même UUID pourrait entraîner des problèmes de facturation ou des problèmes "
"d'iidentification à tous les niveaux."
#: ../../db_management/db_premise.rst:179
#: ../../db_management/db_premise.rst:174
msgid ""
"The database uuid is currently accessible from the menu **Settings > "
"Technical > System Parameters**, we advise you to use a `uuid generator "
"<https://www.uuidgenerator.net>`__ or to use the unix command ``uuidgen`` to"
" generate a new uuid. You can then simply replace it like any other record "
"by clicking on it and using the edit button."
"The database uuid is currently accessible from the menu "
":menuselection:`Settings --> Technical --> System Parameters`, we advise you"
" to use a `uuid generator <https://www.uuidtools.com>`_ or to use the unix "
"command ``uuidgen`` to generate a new uuid. You can then simply replace it "
"like any other record by clicking on it and using the edit button."
msgstr ""
"L'UUID d'une base de données est actuellement accessible à partir du menu "
":menuselection:`Configuration --> Technique --> Paramètres --> Paramètres "
"systèmes`. Nous vous conseillons d'utiliser un générateur `UUID "
"<https://www.uuidgenerator.net>`__ ou d'utiliser la commande unix "
"``uuidgen`` pour générer un nouveau UUID. Vous pouvez alors simplement le "
"remplacer comme tout autre enregistrement en cliquant dessus et en utilisant"
" le bouton Modifier."
#: ../../db_management/documentation.rst:7
msgid "Users and Features"
@ -650,9 +609,6 @@ msgid ""
"This includes the Apps you install as well as the number of users currently "
"in use."
msgstr ""
"En tant qu'administrateur de votre base de données, vous êtes responsable de"
" son utilisation. Cela inclut les Applications que vous installez, ainsi que"
" le nombre d'utilisateurs qui les utilisent."
#: ../../db_management/documentation.rst:13
msgid ""
@ -662,13 +618,6 @@ msgid ""
"subscription amount significantly (or switch you from a free account to a "
"paying one on our online platform)."
msgstr ""
"Odoo est beaucoup de choses (ERP, CMS, CRM application, site de "
"eCommerce,etc...) mais ce n'est *pas* un smartphone. Vous devez faire preuve"
" de prudence lorsque vous ajouter/supprimez des fonctionnalités (en "
"particulier les applications) à votre base de données, car cela pourrait "
"influer sur le montant de votre abonnement de manière significative (ou vous"
" faire passer d'un compte gratuit à un payant sur notre plate-forme en "
"ligne)."
#: ../../db_management/documentation.rst:19
msgid ""
@ -691,21 +640,16 @@ msgid ""
"issue while carrying out these procedures, please contact us through our "
"`support form <https://www.odoo.com/help>`__."
msgstr ""
"Si vous avez des questions sur le contenu de cette page ou si vous "
"rencontrez un problème lors de l'exécution de ces procédures, contactez-nous"
" via notre `formulaire d'assistance <https://www.odoo.com/help>`__."
#: ../../db_management/documentation.rst:34
msgid "Deactivating Users"
msgstr "Désactivation d'Utilisateurs"
msgstr ""
#: ../../db_management/documentation.rst:36
msgid ""
"Make sure you have sufficient **administrative rights** if you want to "
"change the status of any of your users."
msgstr ""
"Assurez-vous que vous disposez des **permissions** suffisantes si vous "
"voulez changer le statut de l'un de vos utilisateurs."
#: ../../db_management/documentation.rst:39
msgid ""
@ -716,15 +660,15 @@ msgstr ""
#: ../../db_management/documentation.rst:43
#: ../../db_management/documentation.rst:80
msgid "|settings|"
msgstr "|settings|"
msgstr ""
#: ../../db_management/documentation.rst:43
msgid "|browse_users|"
msgstr "|browse_users|"
msgstr ""
#: ../../db_management/documentation.rst:46
msgid "You'll then see the list of your users."
msgstr "Vous verrez alors la liste de vos utilisateurs."
msgstr ""
#: ../../db_management/documentation.rst:51
msgid ""
@ -732,10 +676,6 @@ msgid ""
"from the *Portal Users* which are free). If you remove this filter, you'll "
"get all your users (the ones you pay for and the portal ones)"
msgstr ""
"Le filtre pré-sélectionné *Utilisateurs Internes* montre vos utilisateurs "
"payants (pas les *Utilisateurs du Portail* qui sont gratuits). Si vous "
"supprimez ce filtre, vous obtiendrez tous les utilisateurs (les payants et "
"ceux du portail)"
#: ../../db_management/documentation.rst:56
msgid ""
@ -746,15 +686,15 @@ msgstr ""
#: ../../db_management/documentation.rst:64
msgid "The user is now deactivated."
msgstr "L'utilisateur est maintenant désactivé."
msgstr ""
#: ../../db_management/documentation.rst:66
msgid "**Never** deactivate the main user (*admin*)"
msgstr "Ne désactivez **jamais** l'utilisateur principal (*admin*)"
msgstr ""
#: ../../db_management/documentation.rst:69
msgid "Uninstalling Apps"
msgstr "Désinstallation d'Applications"
msgstr ""
#: ../../db_management/documentation.rst:71
msgid ""
@ -769,13 +709,10 @@ msgid ""
"to see how many applications you have installed. Click on **Browse Apps** to"
" access the list of your installed applications."
msgstr ""
"Dans votre instance Odoo cliquez sur **Configuration**; dans ce module, vous"
" verrez le nombre d'applications que vous avez installées. Cliquez sur "
"**Parcourir les applications** pour accéder à la liste des applications."
#: ../../db_management/documentation.rst:80
msgid "|browse_apps|"
msgstr "|browse_apps|"
msgstr ""
#: ../../db_management/documentation.rst:83
msgid ""
@ -783,10 +720,6 @@ msgid ""
"applications. Click on the application you want to uninstall. Then, on the "
"form of the application, click on **Uninstall**."
msgstr ""
"Dans le tableau de bord de vos applications, vous verrez toutes les icônes "
"de vos applications. Cliquez sur l'application que vous souhaitez "
"désinstaller. Puis, sur la fiche de l'application, cliquez sur "
"**Désinstaller**."
#: ../../db_management/documentation.rst:90
msgid ""
@ -797,28 +730,19 @@ msgid ""
"permanently disappear). If you are sure you still want to uninstall it, then"
" click **Confirm**."
msgstr ""
"Certaines applications ont des dépendances, comme Facturation, eCommerce, "
"etc... Par conséquent, le système vous avertira pour vous informer de ce qui"
" est sur le point d'être retiré. Si vous désinstallez votre application, "
"toutes ses dépendances seront également désinstallées (et les données "
"qu'elles contiennent vont disparaître également de façon irréversible). Si "
"vous êtes sûr que vous voulez toujours la désinstaller, alors cliquez sur "
"**Confirmer**."
#: ../../db_management/documentation.rst:97
msgid ""
"Last, after having checked the warning message (if any), click **Confirm**."
msgstr ""
"Enfin, après avoir vérifié le message d'avertissement (le cas échéant), "
"cliquez sur **Confirmer**."
#: ../../db_management/documentation.rst:102
msgid "You have finished uninstalling your application."
msgstr "Vous avez terminé la désinstallation de votre application."
msgstr ""
#: ../../db_management/documentation.rst:105
msgid "Good to know"
msgstr "Bon à savoir"
msgstr ""
#: ../../db_management/documentation.rst:107
msgid ""
@ -829,13 +753,6 @@ msgid ""
"*do not know how you work* and therefore cannot validate these kinds of "
"operations."
msgstr ""
"**Désinstaller des applications, gérer les utilisateurs, etc... c'est à vous"
" de le faire**: personne mieux que vous ne peut savoir si les activités de "
"votre entreprise sont interrompues. Si nous devions désinstaller des "
"applications pour vous, nous ne serions jamais en mesure de dire si des "
"données pertinentes ont été supprimées ou si l'une de vos activités a été "
"interrompue, parce que nous *ne savons pas comment vous travaillez* et ne "
"pouvons donc pas valider ce types d'opérations."
#: ../../db_management/documentation.rst:113
msgid ""
@ -846,13 +763,6 @@ msgid ""
"need or use the Website itself, it is needed for the Online Quotes feature "
"to work properly."
msgstr ""
"**Les Applications Odoo ont des dépendances** : cela signifie que vous "
"pouvez avoir besoin d'installer des modules que vous n'utilisez pas "
"activement, pour accéder à certaines fonctionnalités de Odoo dont vous avez "
"besoin. Par exemple, l'application Construction de site web est nécessaire "
"pour pouvoir montrer des devis dans une page web à vos clients. Même si vous"
" n'avez pas besoin du site web lui-même, il est requis pour que la "
"fonctionnalité Offres en ligne fonctionne correctement."
#: ../../db_management/documentation.rst:120
msgid ""
@ -860,8 +770,3 @@ msgid ""
"database): that way you can know what other apps may be required, etc. This "
"will avoid surprises when uninstalling or when receiving your invoices."
msgstr ""
"**Tester toujours l'installation/la suppression d'application sur une "
"copie** (ou sur une base de données d'essai gratuit) : de cette façon, vous "
"pouvez savoir quelles autres applications peuvent être nécessaires, etc... "
"Cela évitera des surprises lors de la désinstallation ou lors de la "
"réception de vos factures d'abonnement."

877
locale/fr/LC_MESSAGES/discuss.po
View File

File diff suppressed because it is too large Load Diff

1172
locale/fr/LC_MESSAGES/ecommerce.po
View File

File diff suppressed because it is too large Load Diff

284
locale/fr/LC_MESSAGES/email_marketing.po Normal file
View File

@ -0,0 +1,284 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../email_marketing.rst:5
msgid "Email Marketing"
msgstr ""
#: ../../email_marketing/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:3
msgid "Work with Mailing Lists"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:5
msgid ""
"Mailing lists can be a goldmine for your company’s marketing department as "
"they can provide leads for sales, focus groups for testing new products, and"
" consumers to provide feedback on satisfaction, for example."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:10
msgid "Create mailing lists"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:12
msgid ""
"Go to :menuselection:`Mailing lists --> Mailing lists --> Create`. Enable "
"the option *Is Public* to make the list visible for users when "
"unsubscribing."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:19
msgid ""
"Once your mailing list is created, you can manually add contacts clicking on"
" *Create*. *Import* a list of contacts if you have it from a previous tool."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:23
msgid "Linking a mailing list to my website"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:26
msgid ""
"Create a mailing list called Newsletter, as you use this strategy to "
"advertise and communicate new ideas to subscribers interested in listening."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:27
msgid ""
"Go to your *Website*, add a *Newsletter* block and choose the respective "
"mailing list."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:34
msgid "Contacts"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:36
msgid ""
"Under :menuselection:`Mailing Lists --> Mailing List Contacts` see a list of"
" all contacts under all your mailing lists, and the ones you individually "
"created here."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:43
msgid ""
"Open a contact form to see or add different mailing lists to which the "
"contact is or will be part of."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:51
#: ../../email_marketing/overview/manage_unsubscriptions.rst:46
msgid ":doc:`send_emails`"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:3
msgid "Manage Unsubscriptions and Blacklist"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:5
msgid ""
"It is best practice, and legally required, to allow recipients to "
"unsubscribe from mailing lists as you do not want your audience to think "
"that your company is using any tactics that are dishonest or spammy."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:10
msgid "Enable the Blacklist feature"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:12
msgid ""
"Go to :menuselection:`Configuration --> Settings` and enable the option "
"*Blacklist Option when Unsubscribing*."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:19
msgid ""
"Now, once the user clicks on the *Unsubscribe* link on your email, he is "
"redirected to the following page:"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:28
msgid ""
"After clicking on the unsubscribe button when using the test feature, you "
"are sent to an error page (*error 403 - Access Denied*). If you want to be "
"sure the link is working properly, create your mass mail and send it only to"
" a personal email."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:32
msgid ""
"In addition to having the option of unsubscribing from specific mailing "
"lists, the user can also blacklist himself, meaning that he will not receive"
" *any* more emails from you."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:36
msgid ""
"The mailing list has to be configured as *Public* in order to be visible for"
" users."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:38
msgid ""
"Under :menuselection:`Configuration --> Blacklist`, blacklisted email "
"addresses are shown."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:39
msgid ""
"When opening the record, as a *Log note*, a description-history is kept."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:47
msgid ":doc:`mailing_lists`"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:3
msgid "Send Emails Marketing and Manage Campaigns"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:5
msgid ""
"Emails allow you to effectively, and at a low cost, reach a large number of "
"consumers while being able to customize your message in a way that resonates"
" with them. It is measurable, and a call-to-action oriented channel."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:10
msgid "Choose the right target and create the message"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:12
msgid "Go to :menuselection:`Mailings --> Create`."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:14
msgid ""
"Choosing *Contacts* as *Recipients* (for example), allows you to add "
"specifications to match just certain contacts, filtering your target."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:21
msgid ""
"With a trial databases, you have a limit of 50 emails per day; on Odoo SH "
"Cloud Platform the limit is 200. There is a possibility to increase these "
"numbers by contacting Odoo Support. To contact Support, `click here "
"<https://www.odoo.com/help>`_."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:25
msgid ""
"Under *Mail Body*, choose a layout and make the modifications needed by "
"dragging, dropping and double-clicking on content. Note that it is possible "
"to start from scratch selecting the *blank* template option."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:34
msgid ""
"Under *Settings*, you can assign someone else as the responsible sender if "
"you do not want it to be you. To do so, change the email address used as the"
" sender (*Send From*)."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:37
msgid ""
"With the *Reply To* radio button, you can also choose to gather answers "
"either on the respective recipients’ records or on a specific email address."
" Note that this option is not available if you target mailing contacts or "
"contacts as recipients."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:45
msgid "Test, send or schedule a mailing"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:53
msgid ""
"*Save*: the work is allocated in the *draft* column in the Kanban view. "
"Modifications can be made while being in this stage. The option *Discard* "
"deletes the email."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:54
msgid ""
"Click on *Test* and send your message to one, or even multiple, test "
"contacts to avoid errors."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:56
msgid ""
"*Send* triggers the email with the next run and put the work on the *queue* "
"column in the Kanban view."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:58
msgid ""
"*Schedule* allows you to choose a date and time, and puts the email in the "
"*queue* column in the Kanban view."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:61
msgid ""
"The daily limit is applied for **all emails** sent, in other words, "
"throughout all applications. Therefore, if at the end of the day you have "
"remaining ones to be sent, note that they *will not* be sent automatically "
"the next day. You need to force that by opening the email and clicking on "
"*Retry*."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:67
msgid "Manage campaigns"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:69
msgid ""
"Go to :menuselection:`Configuration --> Settings` and enable *Mailing "
"Campaigns*."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:71
msgid ""
"The campaign option is effective as it allows you to organize your marketing"
" efforts and have a centralized view of its metrics."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:72
msgid "Go to *Campaign* and click on *Create* to start one."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:80
msgid ""
"If you use the SMS and Social Marketing applications, as well as the Push "
"Notification feature, you see the option to create content for those "
"channels. You also see the *Campaign* menu within those applications. All of"
" this is possible because the applications work integrated."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:85
msgid ":doc:`../../discuss/advanced/email_servers`"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:86
msgid ":doc:`../../social_marketing/overview/campaigns`"
msgstr ""

429
locale/fr/LC_MESSAGES/events.po Normal file
View File

@ -0,0 +1,429 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../events.rst:5
msgid "Events"
msgstr ""
#: ../../events/integrations.rst:3
msgid "Integrations"
msgstr ""
#: ../../events/integrations/integration_sms.rst:3
msgid "Communicating about my Event using SMS Text Messages"
msgstr ""
#: ../../events/integrations/integration_sms.rst:5
msgid ""
"Using SMS as a communication strategy for your event establishes interaction"
" between organizers, attendees, speakers and further targets. It allows your"
" message to be heard whether the goal is to send out reminders, teasers or "
"to advertise."
msgstr ""
#: ../../events/integrations/integration_sms.rst:10
#: ../../events/overview/tickets.rst:9 ../../events/overview/track_talks.rst:9
msgid "Configuration"
msgstr ""
#: ../../events/integrations/integration_sms.rst:13
msgid ""
"Under *Communication* SMS is a standard feature. That means nothing needs to"
" be enabled or installed."
msgstr ""
#: ../../events/integrations/integration_sms.rst:16
msgid ""
"On the other hand, to contact the speakers of your event, you need the *SMS "
"Marketing* application installed, and to enable *Schedule & Tracks* under "
":menuselection:`Events --> Configuration --> Settings`."
msgstr ""
#: ../../events/integrations/integration_sms.rst:23
msgid ""
"The *Schedule & Tracks* feature allows you to manage the agenda and speakers"
" of your event. For more details watch: `Creating an agenda for your event "
"<https://www.odoo.com/slides/slide/create-an-agenda-for-your-"
"event-717?fullscreen=1>`_."
msgstr ""
#: ../../events/integrations/integration_sms.rst:28
msgid "Send SMSs to attendees"
msgstr ""
#: ../../events/integrations/integration_sms.rst:30
msgid ""
"Under *Communication*, the message’s target is the attendees of your event."
msgstr ""
#: ../../events/integrations/integration_sms.rst:32
msgid ""
"You can choose to confirm each registration with the *Registration* "
"template, and to send a reminder shortly before the event takes place with "
"the *Reminder* template."
msgstr ""
#: ../../events/integrations/integration_sms.rst:38
msgid "To make changes in an existing template, click on the external link."
msgstr ""
#: ../../events/integrations/integration_sms.rst:45
msgid "Send SMSs to speakers and further targets"
msgstr ""
#: ../../events/integrations/integration_sms.rst:47
msgid ""
"The benefit of the integration with the *SMS Marketing* application is that "
"you can choose the target you would like your message to be delivered to. To"
" get started, click on *Contact Track Speakers*."
msgstr ""
#: ../../events/integrations/integration_sms.rst:56
msgid ""
"If *Event Track* is not your target (*Recipient*), choose the right one. "
"*Filters* are eligible here."
msgstr ""
#: ../../events/integrations/integration_sms.rst:58
msgid ""
"In the example below, the SMS would be sent to the speakers who are in the "
"stage *Proposal* on *Event Track*."
msgstr ""
#: ../../events/integrations/integration_sms.rst:65
msgid ""
"Credits are required to be able to send SMSs. For more information about "
"Pricing :doc:`click here <../../sms_marketing/pricing/pricing_and_faq>`, "
"and, about IAP Services :doc:`here "
"<../../general/in_app_purchase/in_app_purchase>`."
msgstr ""
#: ../../events/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../events/overview/create_event.rst:3
msgid "Create your First Event"
msgstr ""
#: ../../events/overview/create_event.rst:5
msgid "Some of the reasons why hosting events is essential are:"
msgstr ""
#: ../../events/overview/create_event.rst:7
msgid "To create an engaging experience with your audience;"
msgstr ""
#: ../../events/overview/create_event.rst:8
msgid "To generate word of mouth about your company;"
msgstr ""
#: ../../events/overview/create_event.rst:9
msgid "To allow networking;"
msgstr ""
#: ../../events/overview/create_event.rst:10
msgid ""
"To provide an opportunity for sales representatives to walk their prospects "
"through the product and even their pipeline."
msgstr ""
#: ../../events/overview/create_event.rst:14
msgid "Get started"
msgstr ""
#: ../../events/overview/create_event.rst:16
msgid ""
"Under the menu *Events*, have a view of all existing events and some key "
"information, such as the number of expected and confirmed attendees."
msgstr ""
#: ../../events/overview/create_event.rst:23
msgid ""
"To start a new one, click on *Create* and fill in the form with all the "
"needed information. Enable *Website Menu* to have the menus *Introduction*, "
"*Location*, and *Register* being shown on your event’s website page."
msgstr ""
#: ../../events/overview/create_event.rst:31
msgid ""
"To personalize these pages, click on *Edit* to open the `website builder "
"<https://www.odoo.com/slides/slide/website-basics-643?fullscreen=1>`_, and "
"edit content by dragging and dropping blocks."
msgstr ""
#: ../../events/overview/create_event.rst:40
msgid "Tab: Tickets"
msgstr ""
#: ../../events/overview/create_event.rst:43
msgid ""
"Go to :menuselection:`Events --> Configuration --> Settings` and enable "
":doc:`Tickets and Online Ticketing <tickets>`."
msgstr ""
#: ../../events/overview/create_event.rst:46
msgid ""
"Now, under the *Tickets* Tab, add lines to include the different ticket "
"types you offer. Include the price, the start and end dates for "
"registrations, and even the maximum number of tickets that can be sold."
msgstr ""
#: ../../events/overview/create_event.rst:48
msgid ""
"The *Reserved Seats* and *Unconfirmed Seat Reservations* are counted as "
"attendees are marked as :doc:`confirmed <track_attendees>` or not."
msgstr ""
#: ../../events/overview/create_event.rst:55
msgid "Tab: Communication"
msgstr ""
#: ../../events/overview/create_event.rst:58
msgid ""
"Choose the email and/or SMS message template, as well as the frequency with "
"which you would like to communicate with your attendees under the tab "
"*Communication*."
msgstr ""
#: ../../events/overview/create_event.rst:61
msgid ""
"Create a template on the fly or choose an existing one. Define the "
"*Interval* (2, 7, 15..) for the *Unit* (days, hours, weeks, etc.), and the "
"*Trigger* action (after registration, after the event, etc.)."
msgstr ""
#: ../../events/overview/create_event.rst:68
msgid "Tab: Questions"
msgstr ""
#: ../../events/overview/create_event.rst:70
msgid ""
"Go to :menuselection:`Configuration --> Settings` and enable *Questions*."
msgstr ""
#: ../../events/overview/create_event.rst:72
msgid ""
"Now, under the tab *Questions*, edit your questions and answers, choosing if"
" you would like your questionnaire to be asked per order or per "
"registration."
msgstr ""
#: ../../events/overview/create_event.rst:75
msgid ""
"Example of a registration for 3 attendees: if enabling the option *Ask each "
"attendee*, the questionnaire is shown 3 times, meaning that answers can vary"
" for each attendee; if *Ask each attendee* is not enabled, the questionnaire"
" is shown once, resulting in a global answer."
msgstr ""
#: ../../events/overview/create_event.rst:81
msgid ""
"Once your event is *Confirmed*, you can manage attendees badges, and mark "
"the event as *Finished*. Events marked as *Finished* can be *Set to draft*, "
"putting the event back to an *Unconfirmed* stage from which it can be edited"
" and used again."
msgstr ""
#: ../../events/overview/create_event.rst:90
msgid "Publish your event"
msgstr ""
#: ../../events/overview/create_event.rst:92
msgid "*Go to Website* and turn *Published* on."
msgstr ""
#: ../../events/overview/create_event.rst:99
msgid ":doc:`track_attendees`"
msgstr ""
#: ../../events/overview/create_event.rst:100
#: ../../events/overview/track_attendees.rst:45
msgid ":doc:`tickets`"
msgstr ""
#: ../../events/overview/create_event.rst:101
#: ../../events/overview/track_attendees.rst:46
msgid ":doc:`track_talks`"
msgstr ""
#: ../../events/overview/tickets.rst:3
msgid "Selling Tickets"
msgstr ""
#: ../../events/overview/tickets.rst:5
msgid ""
"If you automate processes, you save time. If you give attendees multiple "
"payment options to choose from, you allow flexibility and open margins for "
"more registrations to happen."
msgstr ""
#: ../../events/overview/tickets.rst:11
msgid ""
"Go to :menuselection:`Configuration --> Settings` and activate *Tickets* and"
" *Online Ticketing*."
msgstr ""
#: ../../events/overview/tickets.rst:13
msgid ""
"*Tickets* allow tickets to be sold "
":ref:`events/create_event/through_sales_orders`. *Online Ticketing* allows "
"the sale of tickets to happen "
":ref:`events/create_event/through_the_website`."
msgstr ""
#: ../../events/overview/tickets.rst:22
msgid "Through Sales Orders"
msgstr ""
#: ../../events/overview/tickets.rst:24
msgid ""
"On the *Sales* application, choose the event product you created and add it "
"as a product line. A window pops-up, allowing you to choose the event for "
"which you want to create the sales order."
msgstr ""
#: ../../events/overview/tickets.rst:32
msgid ""
"Remember to create a product form for the event registration, under "
"*Product*, in the *Sales* application, and to add that same product under "
"your event’s form."
msgstr ""
#: ../../events/overview/tickets.rst:43
msgid "Through the Website"
msgstr ""
#: ../../events/overview/tickets.rst:45
msgid ""
"On the website, once tickets are added to the cart, the user can continue "
"the transaction choosing among the payment methods you chose to have "
"available."
msgstr ""
#: ../../events/overview/tickets.rst:53
msgid ":doc:`../../general/payment_acquirers/payment_acquirers`"
msgstr ""
#: ../../events/overview/track_attendees.rst:3
msgid "Track your Attendees"
msgstr ""
#: ../../events/overview/track_attendees.rst:5
msgid ""
"Attendees are at the heart of your event. Keeping track of their number and "
"managing their registration and attendance is necessary for planning and "
"analyzing reasons."
msgstr ""
#: ../../events/overview/track_attendees.rst:9
msgid "Attendees list and attendance"
msgstr ""
#: ../../events/overview/track_attendees.rst:11
msgid ""
"Once attendees have registered or bought their tickets, they are added to "
"the *Attendees* list."
msgstr ""
#: ../../events/overview/track_attendees.rst:12
msgid ""
"Tickets sold through sales orders validate attendees as soon as the "
"quotation is confirmed."
msgstr ""
#: ../../events/overview/track_attendees.rst:18
msgid ""
"The check mark button is used to confirm the registration. Once a "
"registration is confirmed, attendance can be marked."
msgstr ""
#: ../../events/overview/track_attendees.rst:26
msgid "Bagdes and cancellations"
msgstr ""
#: ../../events/overview/track_attendees.rst:28
msgid ""
"On the attendees form, choose to send badges manually by clicking on *Send "
"By Email*. *Cancel Registration* to have that attendee being moved to the "
"*Cancelled* stage."
msgstr ""
#: ../../events/overview/track_attendees.rst:36
msgid ""
"To see a list of your canceled attendees, under *Filters*, add a *Custom "
"Filter* choosing *Status > is > Cancelled*."
msgstr ""
#: ../../events/overview/track_attendees.rst:44
#: ../../events/overview/track_talks.rst:49
msgid ":doc:`../integrations/integration_sms`"
msgstr ""
#: ../../events/overview/track_talks.rst:3
msgid "Track and Manage Talks"
msgstr ""
#: ../../events/overview/track_talks.rst:5
msgid ""
"Allow partners to submit talk proposals so they can share their knowledge "
"and expertise. Good speakers and talks are what make your event great."
msgstr ""
#: ../../events/overview/track_talks.rst:11
msgid ""
"Go to :menuselection:`Events --> Configuration --> Settings` and enable "
"*Schedule & Tracks*."
msgstr ""
#: ../../events/overview/track_talks.rst:14
msgid ""
"Now, in your event's form, once *Website menu* is enabled, the options "
"*Tracks on Website* and *Track Proposals on Website* become available. "
"Enabling them adds the menus *Talks*, *Talk Proposals*, and *Agenda* to your"
" website."
msgstr ""
#: ../../events/overview/track_talks.rst:20
msgid ""
"Besides having the ability to suggest their own talks, the website now "
"allows users to see a list of the whole agenda and scheduled talks."
msgstr ""
#: ../../events/overview/track_talks.rst:28
msgid ""
"To handle tracks internally and not have the menus *Talks*, *Talk "
"Proposals*, and *Agenda* online, use the menu *Tracks* individually."
msgstr ""
#: ../../events/overview/track_talks.rst:32
msgid "Publishing speaker proposals"
msgstr ""
#: ../../events/overview/track_talks.rst:34
msgid ""
"Once partners have filled in the appropriate form and submitted their "
"proposals, a new *Proposal* is instantly created under the menu *Track*."
msgstr ""
#: ../../events/overview/track_talks.rst:41
msgid ""
"If the proposal is accepted and can go online, simply open its form and "
"click on *Go to Website*. From the website page, turn *Published* on."
msgstr ""

340
locale/fr/LC_MESSAGES/expense.po Normal file
View File

@ -0,0 +1,340 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../expense/expense.rst:5
msgid "Expenses"
msgstr ""
#: ../../expense/expense.rst:8
msgid "How to set expense types"
msgstr ""
#: ../../expense/expense.rst:9
msgid ""
"The first step to track expenses is to configure the expense types (managed "
"as products in Odoo) that your company allows, from the *Configuration* "
"menu. When a specific expense is reimbursed at a fixed price, set a cost on "
"the product. Otherwise keep the cost at 0.0 and employees will report the "
"real cost per expense."
msgstr ""
#: ../../expense/expense.rst:17
msgid "Here are some examples to configure:"
msgstr ""
#: ../../expense/expense.rst:19
msgid "Restaurant:"
msgstr ""
#: ../../expense/expense.rst:21 ../../expense/expense.rst:27
msgid "Cost: 0.00 (the cost of the ticket will be recorded on every expense)"
msgstr ""
#: ../../expense/expense.rst:22
msgid "Travel with Personal Car:"
msgstr ""
#: ../../expense/expense.rst:24
msgid "Cost: 0.30 (the price per mile reimbursed by the company is fixed)"
msgstr ""
#: ../../expense/expense.rst:25
msgid "Hotel:"
msgstr ""
#: ../../expense/expense.rst:29
msgid "Others:"
msgstr ""
#: ../../expense/expense.rst:31
msgid "Cost: 0.0"
msgstr ""
#: ../../expense/expense.rst:33
msgid ""
"Don't forget to set an expense tax on each expense type (and an account if "
"you use Odoo Accounting). It's usually a good practice to use a tax that is "
"configured with :ref:`Tax Included in Price <taxes/included-in-price>`. That"
" way, employees report expenses with prices including taxes, which is "
"usually the expected behaviour."
msgstr ""
#: ../../expense/expense.rst:41
msgid ""
"The *Sales* app allows you to specify unit of measures for your expense "
"types (units, miles, nights, etc.). Go to :menuselection:`Sales --> "
"Configuration --> Settings` and check *Some products may be sold/purchased "
"in different units of measure (advanced)*."
msgstr ""
#: ../../expense/expense.rst:48
msgid "How to record expenses"
msgstr ""
#: ../../expense/expense.rst:51
msgid "Manually"
msgstr ""
#: ../../expense/expense.rst:53
msgid ""
"As an employee (Employee in user access rights), you can record expenses "
"from :menuselection:`My Expenses --> Expenses to Submit`."
msgstr ""
#: ../../expense/expense.rst:59
msgid ""
"Select the related product and enter either the total amount you paid (with "
"Quantity = 1) or the unit price if Quantity is countable (e.g. number of "
"hotel nights)."
msgstr ""
#: ../../expense/expense.rst:62
msgid "Enter the expense date."
msgstr ""
#: ../../expense/expense.rst:63
msgid ""
"Choose if you paid the bill on your own (and expect to be reimbursed) or if "
"the company paid directly (e.g. if you used a company's credit card)."
msgstr ""
#: ../../expense/expense.rst:65
msgid ""
"Set the bill reference, add some notes if requested and attach a photo/scan "
"of the receipt from the discussion thread. That will help the manager and "
"the accountant validate it."
msgstr ""
#: ../../expense/expense.rst:73
msgid "In one click from emails"
msgstr ""
#: ../../expense/expense.rst:74
msgid ""
"Let your employees record their expenses from a simple email. Make a "
"snapshot of the receipt and send it by email, or simply forward a bill!"
msgstr ""
#: ../../expense/expense.rst:77
msgid ""
"The only thing to do is setting up an email alias in "
":menuselection:`Expenses --> Configuration --> Settings` (e.g. *expenses* "
"@mycompany.odoo.com). For security purposes, only authenticated employee "
"emails (cfr. *Work Email* in employee detail form) are accepted."
msgstr ""
#: ../../expense/expense.rst:83
msgid ""
"The expense product is set automatically if the mail subject contains the "
"product's internal reference in first position. Type the expense amount in "
"the mail subject to set it on the expense too (e.g. Ref001 Food 100€)."
msgstr ""
#: ../../expense/expense.rst:88
msgid "How to submit expenses to managers"
msgstr ""
#: ../../expense/expense.rst:90
msgid ""
"When you are ready to submit your expenses to your manager (e.g. at the end "
"of a business trip, or once a month), go to the menu :menuselection:`My "
"Expenses --> Expenses to Submit`. Select all expenses from the list view and"
" click on :menuselection:`Action --> Submit to Manager`. Save the newly "
"created expense report (i.e. set of expenses), and wait for your manager to "
"approve it."
msgstr ""
#: ../../expense/expense.rst:100
msgid ""
"You can also submit expenses one by one from the *Submit to Manager* button "
"on the form view of an expense."
msgstr ""
#: ../../expense/expense.rst:103
msgid ""
"All your submitted expense reports can be found in :menuselection:`Expenses "
"--> My Expenses --> Expense Reports`."
msgstr ""
#: ../../expense/expense.rst:108
msgid "How to approve expenses"
msgstr ""
#: ../../expense/expense.rst:110
msgid ""
"HR and team managers get an overview of all expense reports to validate from"
" the top menu :menuselection:`To Approve --> Expense Reports to Approve`. "
"Such users must have at least *Officers* access rights for *Expenses*."
msgstr ""
#: ../../expense/expense.rst:117
msgid ""
"They can review expense reports, approve or reject them, as well as "
"providing feedback thanks to the integrated communication tool."
msgstr ""
#: ../../expense/expense.rst:123
msgid ""
"As a team manager you can easily find the expense reports of your team "
"members. You need to be set as manager in the detail form of those "
"employees."
msgstr ""
#: ../../expense/expense.rst:131
msgid "How to post expenses in accounting"
msgstr ""
#: ../../expense/expense.rst:133
msgid ""
"Once expense reports approved by managers, the accounting department goes to"
" :menuselection:`Expenses --> Accountant --> Expense Reports To Post` to "
"check accounts, products and taxes. They can click *Post Journal Entries* to"
" post related journal entries into your books. To do so, the user must have "
"following access rights:"
msgstr ""
#: ../../expense/expense.rst:139
msgid "Accounting: Accountant or Adviser"
msgstr ""
#: ../../expense/expense.rst:140
msgid "Expenses: Manager"
msgstr ""
#: ../../expense/expense.rst:143
msgid ""
"To post an expense, a *Home Address* must be set on the employee. If you get"
" a related blocking message when posting, click the employee, go to "
"*Personal Information* tab and select/create the contact of your employee in"
" the address book. A contact has been automatically created if this person "
"is using Odoo."
msgstr ""
#: ../../expense/expense.rst:150
msgid "How to reimburse employees"
msgstr ""
#: ../../expense/expense.rst:152
msgid ""
"You can now see all the expense reports to reimburse in "
":menuselection:`Expenses --> Accountant --> Expense Reports To Pay`. To "
"record the payment or pay by check, click *Register a Payment*."
msgstr ""
#: ../../expense/expense.rst:156
msgid "See how you can easily manage the payment process in Odoo:"
msgstr ""
#: ../../expense/expense.rst:158
msgid ":doc:`../accounting/payables/pay/check`"
msgstr ""
#: ../../expense/expense.rst:159
msgid ":doc:`../accounting/payables/pay/sepa`"
msgstr ""
#: ../../expense/expense.rst:163
msgid "How to re-invoice expenses to your customers"
msgstr ""
#: ../../expense/expense.rst:165
msgid ""
"If you track expenses on customer projects, you can charge them back to your"
" customers automatically."
msgstr ""
#: ../../expense/expense.rst:169
msgid "Setup"
msgstr ""
#: ../../expense/expense.rst:171
msgid "Enable **Customer Billing** in the Expenses settings"
msgstr ""
#: ../../expense/expense.rst:173
msgid ""
"Go to the product configuration menu and set the invoicing method on all "
"your Expense types:"
msgstr ""
#: ../../expense/expense.rst:176
msgid ""
"Ordered quantities : it will invoice expenses based on the ordered quantity"
msgstr ""
#: ../../expense/expense.rst:179
msgid ""
"Delivered quantities :it will invoice expenses based on the expenses "
"quantity"
msgstr ""
#: ../../expense/expense.rst:182
msgid "At cost: will invoice expenses at their real cost."
msgstr ""
#: ../../expense/expense.rst:184
msgid ""
"At sales price: will invoice based on a fixed sales price set on the sale "
"order."
msgstr ""
#: ../../expense/expense.rst:191
msgid "Create an order"
msgstr ""
#: ../../expense/expense.rst:193
msgid ""
"As a salesman, create and confirm a Sales Order for the services delivered "
"to your customer. If you don't put any expense in the order, it will be "
"added automatically once posted by the accountant."
msgstr ""
#: ../../expense/expense.rst:198
msgid "Link the expense to the Sale Order."
msgstr ""
#: ../../expense/expense.rst:204
msgid "Submit, validate and post expenses"
msgstr ""
#: ../../expense/expense.rst:206
msgid ""
"As a manager, make sure the analytic account is set on every expense line on"
" approving expenses reports. Click the line to add one if missing. Employees"
" are already able to set one when submitting."
msgstr ""
#: ../../expense/expense.rst:213
msgid "As an accountant, post journal entries."
msgstr ""
#: ../../expense/expense.rst:216
msgid "Invoice expenses"
msgstr ""
#: ../../expense/expense.rst:218
msgid ""
"Now you can invoice the order. It shows up in :menuselection:`Sales --> "
"Invoicing --> Sales` to Invoice. The expenses have been added automatically "
"in the order lines. Such items show up in blue (i.e. to invoice)."
msgstr ""
#: ../../expense/expense.rst:226
msgid "e (i.e. to invoice)."
msgstr ""

386
locale/fr/LC_MESSAGES/fsm.po Normal file
View File

@ -0,0 +1,386 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../fsm.rst:5
msgid "Field Service"
msgstr ""
#: ../../fsm/helpdesk.rst:3
msgid "Helpdesk"
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:3
msgid "Plan Onsite Interventions from Helpdesk Tickets"
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:4
msgid ""
"The integration with the Helpdesk application lets your helpdesk team manage"
" interventions requests directly. It speeds up processes as you can plan "
"field services tasks from tickets."
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:8
#: ../../fsm/sales/create_quotations.rst:8
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:9
#: ../../fsm/worksheets/customize_worksheets.rst:9
msgid "Enable the feature"
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:9
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams --> "
"Edit` and enable :menuselection:`Onsite Interventions --> Save`."
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:17
msgid ""
"Now once your helpdesk team needs, they have the option to *Plan "
"Intervention* from tickets."
msgstr ""
#: ../../fsm/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:3
msgid "Invoicing Time and Material to Customers"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:4
msgid ""
"Track the exact time spent on a task and give customers the ability to sign "
"their worksheet report onsite. Invoice customers as soon as the work is "
"complete, leaving you, and the customer, with the confidence that they will "
"be charged for the exact right hours and material used."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:9
msgid "Get the exact time spent on a task"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:10
msgid ""
"Click on *Start* to launch the timer. You can *Pause* at any moment and "
"*Resume* when you would like to continue."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:17
msgid ""
"Click on *Stop* once the work is done to confirm the total time spent and "
"add a description."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:24
msgid "Sign and send reports & validate stock-picking"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:25
msgid ""
"Now, fill your *Worksheet* and add the used products clicking on *Products*."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:31
msgid ""
"Click on *Start* if you need to record additional time for the same "
"activity. The time recorded will be added to the already created and signed "
"worksheet. Then, create a new invoice for the time added."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:34
msgid ""
"*Mark as done* to close the task and to invoice your intervention. It also "
"validates the stock-picking keeping your inventory up-to-date."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:37
msgid ""
"*Sign Report* generates a detailed worksheet report for the customer to "
"sign. Send it through email clicking on *Send Report*."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:41
msgid "Invoice your time and material"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:42
msgid ""
"Under :menuselection:`All Tasks --> To Invoice`, find a list of all tasks "
"marked as done but that have not been invoiced. Convenient feature as it "
"allows accountants to easily access all finished tasks at once."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:52
msgid ""
"Invoice all tasks at once selecting them all and going to "
":menuselection:`Action --> Create Invoice`."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:60
msgid ":doc:`../../project/advanced/feedback`"
msgstr ""
#: ../../fsm/overview/keep_track.rst:3
msgid "Keeping Track of Stock"
msgstr ""
#: ../../fsm/overview/keep_track.rst:4
msgid ""
"The integration with the Inventory application makes possible to track the "
"material used and automatically keep your stock up to date."
msgstr ""
#: ../../fsm/overview/keep_track.rst:8
msgid "Set up your Field Service project"
msgstr ""
#: ../../fsm/overview/keep_track.rst:9
msgid ""
"Go to :menuselection:`Field Service --> Configuration --> Projects` and make"
" sure the option *Products on Tasks* is enabled."
msgstr ""
#: ../../fsm/overview/keep_track.rst:15
msgid ""
"Now, add the materials used in the intervention to the worksheet, and once "
"the task is *Marked as done*, the stock-picking is automatically validated "
"and the inventory evaluation is automatically updated."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:3
msgid "Manage your Employees’ Schedules and Time Off"
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:4
msgid ""
"The integration with the *Time off* application allows you to quickly see "
"your employees’ availabilities. It will avoid conflicts and errors between "
"employees schedules and interventions."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:8
msgid "Effortlessly see employees’ time off"
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:9
msgid ""
"No configuration needs to be done. Once the employees’ time has been "
"validated in the *Time off* application, cells will be grayed for those days"
" in your Gantt view."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:13
msgid ""
"It also adapts to the working calendar of the employee. Example: the "
"employee works part-time (from Monday to Wednesday). So, Thursday and Friday"
" will also be greyed, in addition to the weekends."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:20
msgid "Easily manage employees’ schedules"
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:21
msgid ""
"From the Gantt view (under *Planning by User, Project or Worksheet*), click "
"on the plus sign to add a new task or on the magnifying glass to plan an "
"existing one."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:29
msgid "Unassigned tasks"
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:30
msgid ""
"If you need to plan an intervention but you do not know yet who will take "
"care of it, you can leave the task unassigned. It will still be shown in the"
" Gantt view. Simply drag and drop the responsible person he can be assigned."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:39
msgid ""
"Create projects per team, or per working site, and have a more accurate and "
"dynamic database."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:42
msgid ":doc:`../../project/overview/setup`"
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:3
msgid "Planning an Itinerary"
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:5
msgid ""
"Having an itinerary being shown based on the chronological order of the "
"activities and on the best route to take, makes employees’ life easier and "
"the workload more efficient."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:9
msgid "Have an itinerary displayed directly in Odoo"
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:10
msgid "Go to *Settings* and under *Map view* click on *Get token*."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:15
msgid ""
"Click on :menuselection:`Start mapping for free --> fill the Username, email"
" and password fields --> agree with their Terms of Service and Privacy "
"Policy --> Get started`. You will be redirected to your account. Scrolling "
"the page down you will find *Access tokens*. Copy the *Default public "
"token*."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:24
msgid "Back in Odoo, paste it on :menuselection:`Token --> Save`."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:29
msgid ""
"Now, your maps will show the itinerary based on the scheduled time and best "
"route."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:36
msgid ""
"This is an optional feature, as you can still have access to a map view "
"without a Mapbox account."
msgstr ""
#: ../../fsm/sales.rst:3
msgid "Sales"
msgstr ""
#: ../../fsm/sales/create_quotations.rst:3
msgid "Create Quotations from Tasks"
msgstr ""
#: ../../fsm/sales/create_quotations.rst:4
msgid ""
"Allowing quotations to be created from tasks delivers a more efficient "
"service as it allows space for preventive actions, while making the flow "
"easy for employees."
msgstr ""
#: ../../fsm/sales/create_quotations.rst:9
msgid ""
"First, go to :menuselection:`Field Service --> Configuration --> Settings` "
"and enable the option *Extra Quotations*."
msgstr ""
#: ../../fsm/sales/create_quotations.rst:16
msgid ""
"Second, go to :menuselection:`Configuration --> Projects` and enable *Extra "
"Quotations*."
msgstr ""
#: ../../fsm/sales/create_quotations.rst:23
msgid "You can now create *New Quotations* directly from your tasks."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:3
msgid "Create Onsite Interventions Tasks from Sales Orders"
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:4
msgid ""
"By allowing your sales team to open onsite interventions tasks will create a"
" seamless experience for your customers. It also allows them to first "
"receive a quotation with the materials that will be used plus the service "
"price to be approved before the work even starts."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:10
msgid ""
"Go to :menuselection:`Sales --> Products --> Create` or edit an existing "
"one. Select: under :menuselection:`General Information --> Product Type: "
"Service`; under :menuselection:`Sales --> Service Invoicing Policy: "
"Timesheet on task --> Service Tracking: Create a task in an existing project"
" --> Project --> Worksheet Template --> Save`."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:19
msgid ""
"Now, once you have *Confirmed* a *quotation*, a task will be created in the "
"respective project you have chosen."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:28
msgid ""
"One of the greatest benefits here is that you can have different *Worksheets"
" Templates* under the same project and product, for example."
msgstr ""
#: ../../fsm/worksheets.rst:3
msgid "Worksheets"
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:3
msgid "Customize Worksheet Reports"
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:4
msgid ""
"Personalizing your customer reports, also called *worksheets*, allows you to"
" have different descriptions of the work for each type of intervention. It "
"speeds up the flow for your employees while giving customers a detailed "
"summary, which can be reviewed and signed onsite."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:10
msgid ""
"Go to :menuselection:`Field Service --> Configuration` and enable "
":menuselection:`Worksheet Templates --> Save`."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:18
msgid "Designing worksheets"
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:19
msgid ""
"Under :menuselection:`Configuration --> Worksheet Templates`, click on "
"*Create* and start to *Design Worksheet Template*. You will be redirected to"
" the *Studio* application."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:27
msgid ""
"With the freedom of *Studio*, drag and drop fields to create a report "
"tailored to your needs. Once you are done, click on *Close* and get an "
"overview of the work done."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:30
msgid ""
"*Worksheets* is where you can see how many times the worksheet has been "
"used/completed under a task. *Analysis* examines all the worksheets under "
"that given template and generates a graph."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:38
msgid ""
"`Studio Basics <https://www.odoo.com/slides/slide/studio-"
"basics-710?fullscreen=1>`_"
msgstr ""

2283
locale/fr/LC_MESSAGES/general.po
View File

File diff suppressed because it is too large Load Diff

114
locale/fr/LC_MESSAGES/getting_started.po
View File

@ -8,8 +8,8 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -29,7 +29,7 @@ msgid ""
msgstr ""
#: ../../getting_started/documentation.rst:12
msgid "1. The SPoC (*Single Point of Contact*) and the Consultant"
msgid "The SPoC (*Single Point of Contact*) and the Consultant"
msgstr ""
#: ../../getting_started/documentation.rst:14
@ -72,24 +72,22 @@ msgid ""
"training to the SPoC so that he can pass on this knowledge to his "
"collaborators. In order for this approach to be successful, it is necessary "
"that the SPoC is also involved in its own rise in skills through self-"
"learning via the `Odoo documentation "
"<http://www.odoo.com/documentation/user/10.0/index.html>`__, `The elearning "
"platform <https://odoo.thinkific.com/courses/odoo-functional>`__ and the "
"testing of functionalities."
msgstr ""
#: ../../getting_started/documentation.rst:47
msgid "2. Project Scope"
"learning via the :doc:`Odoo documentation <../index>`, `The elearning "
"platform <https://odoo.com/learn>`_ and the testing of functionalities."
msgstr ""
#: ../../getting_started/documentation.rst:49
msgid "Project Scope"
msgstr ""
#: ../../getting_started/documentation.rst:51
msgid ""
"To make sure all the stakeholders involved are always aligned, it is "
"necessary to define and to make the project scope evolve as long as the "
"project implementation is pursuing."
msgstr ""
#: ../../getting_started/documentation.rst:53
#: ../../getting_started/documentation.rst:55
msgid ""
"**A clear definition of the initial project scope**: A clear definition of "
"the initial needs is crucial to ensure the project is running smoothly. "
@ -98,7 +96,7 @@ msgid ""
" clear."
msgstr ""
#: ../../getting_started/documentation.rst:59
#: ../../getting_started/documentation.rst:61
msgid ""
"**Phasing the project**: Favoring an implementation in several coherent "
"phases allowing regular production releases and an evolving takeover of Odoo"
@ -107,7 +105,7 @@ msgid ""
"the implementation."
msgstr ""
#: ../../getting_started/documentation.rst:66
#: ../../getting_started/documentation.rst:68
msgid ""
"**Adopting standard features as a priority**: Odoo offers a great "
"environment to implement slight improvements (customizations) or more "
@ -119,18 +117,18 @@ msgid ""
"experiment of the standard in production."
msgstr ""
#: ../../getting_started/documentation.rst:80
msgid "3. Managing expectations"
#: ../../getting_started/documentation.rst:82
msgid "Managing expectations"
msgstr ""
#: ../../getting_started/documentation.rst:82
#: ../../getting_started/documentation.rst:84
msgid ""
"The gap between the reality of an implementation and the expectations of "
"future users is a crucial factor. Three important aspects must be taken into"
" account from the beginning of the project:"
msgstr ""
#: ../../getting_started/documentation.rst:86
#: ../../getting_started/documentation.rst:88
msgid ""
"**Align with the project approach**: Both a clear division of roles and "
"responsibilities and a clear description of the operating modes (validation,"
@ -140,7 +138,7 @@ msgid ""
"check that this is still the case."
msgstr ""
#: ../../getting_started/documentation.rst:94
#: ../../getting_started/documentation.rst:96
msgid ""
"**Focus on the project success, not on the ideal solution**: The main goal "
"of the SPoC and the Consultant is to carry out the project entrusted to them"
@ -155,7 +153,7 @@ msgid ""
"to pursue this same objective."
msgstr ""
#: ../../getting_started/documentation.rst:108
#: ../../getting_started/documentation.rst:110
msgid ""
"**Specifications are always EXPLICIT**: Gaps between what is expected and "
"what is delivered are often a source of conflict in a project. In order to "
@ -163,34 +161,34 @@ msgid ""
"tools\\* :"
msgstr ""
#: ../../getting_started/documentation.rst:113
#: ../../getting_started/documentation.rst:115
msgid ""
"**The GAP Analysis**: The comparison of the request with the standard "
"features proposed by Odoo will make it possible to identify the gap to be "
"filled by developments/customizations or changes in business processes."
msgstr ""
#: ../../getting_started/documentation.rst:118
#: ../../getting_started/documentation.rst:120
msgid ""
"**The User Story**: This technique clearly separates the responsibilities "
"between the SPoC, responsible for explaining the WHAT, the WHY and the WHO, "
"and the Consultant who will provide a response to the HOW."
msgstr ""
#: ../../getting_started/documentation.rst:126
#: ../../getting_started/documentation.rst:128
msgid ""
"`The Proof of Concept <https://en.wikipedia.org/wiki/Proof_of_concept>`__ A "
"simplified version, a prototype of what is expected to agree on the main "
"lines of expected changes."
msgstr ""
#: ../../getting_started/documentation.rst:130
#: ../../getting_started/documentation.rst:132
msgid ""
"**The Mockup**: In the same idea as the Proof of Concept, it will align with"
" the changes related to the interface."
msgstr ""
#: ../../getting_started/documentation.rst:133
#: ../../getting_started/documentation.rst:135
msgid ""
"To these tools will be added complete transparency on the possibilities and "
"limitations of the software and/or its environment so that all project "
@ -199,17 +197,17 @@ msgid ""
"verifying its veracity beforehand."
msgstr ""
#: ../../getting_started/documentation.rst:139
#: ../../getting_started/documentation.rst:141
msgid ""
"*This list can, of course, be completed by other tools that would more "
"adequately meet the realities and needs of your project*"
msgstr ""
#: ../../getting_started/documentation.rst:143
msgid "4. Communication Strategy"
#: ../../getting_started/documentation.rst:145
msgid "Communication Strategy"
msgstr ""
#: ../../getting_started/documentation.rst:145
#: ../../getting_started/documentation.rst:147
msgid ""
"The purpose of the QuickStart methodology is to ensure quick ownership of "
"the tool for end users. Effective communication is therefore crucial to the "
@ -217,7 +215,7 @@ msgid ""
"follow those principles:"
msgstr ""
#: ../../getting_started/documentation.rst:150
#: ../../getting_started/documentation.rst:152
msgid ""
"**Sharing the project management documentation**: The best way to ensure "
"that all stakeholders in a project have the same level of knowledge is to "
@ -227,45 +225,45 @@ msgid ""
" manager are clearly defined."
msgstr ""
#: ../../getting_started/documentation.rst:158
#: ../../getting_started/documentation.rst:160
msgid ""
"The Project Organizer is a shared project tracking tool that allows both "
"detailed tracking of ongoing tasks and the overall progress of the project."
msgstr ""
#: ../../getting_started/documentation.rst:162
#: ../../getting_started/documentation.rst:164
msgid ""
"**Report essential information**: In order to minimize the documentation "
"time to the essentials, we will follow the following good practices:"
msgstr ""
#: ../../getting_started/documentation.rst:166
#: ../../getting_started/documentation.rst:168
msgid "Meeting minutes will be limited to decisions and validations;"
msgstr ""
#: ../../getting_started/documentation.rst:168
#: ../../getting_started/documentation.rst:170
msgid ""
"Project statuses will only be established when an important milestone is "
"reached;"
msgstr ""
#: ../../getting_started/documentation.rst:171
#: ../../getting_started/documentation.rst:173
msgid ""
"Training sessions on the standard or customized solution will be organized."
msgstr ""
#: ../../getting_started/documentation.rst:175
msgid "5. Customizations and Development"
#: ../../getting_started/documentation.rst:177
msgid "Customizations and Development"
msgstr ""
#: ../../getting_started/documentation.rst:177
#: ../../getting_started/documentation.rst:179
msgid ""
"Odoo is a software known for its flexibility and its important evolution "
"capacity. However, a significant amount of development contradicts a fast "
"and sustainable implementation. This is the reason why it is recommended to:"
msgstr ""
#: ../../getting_started/documentation.rst:182
#: ../../getting_started/documentation.rst:184
msgid ""
"**Develop only for a good reason**: The decision to develop must always be "
"taken when the cost-benefit ratio is positive (saving time on a daily basis,"
@ -279,7 +277,7 @@ msgid ""
"\"Adopting the standard as a priority\")."
msgstr ""
#: ../../getting_started/documentation.rst:194
#: ../../getting_started/documentation.rst:196
msgid ""
"**Replace, without replicate**: There is a good reason for the decision to "
"change the management software has been made. In this context, the moment of"
@ -288,18 +286,18 @@ msgid ""
"business processes of the company."
msgstr ""
#: ../../getting_started/documentation.rst:202
msgid "6. Testing and Validation principles"
#: ../../getting_started/documentation.rst:204
msgid "Testing and Validation principles"
msgstr ""
#: ../../getting_started/documentation.rst:204
#: ../../getting_started/documentation.rst:206
msgid ""
"Whether developments are made or not in the implementation, it is crucial to"
" test and validate the correspondence of the solution with the operational "
"needs of the company."
msgstr ""
#: ../../getting_started/documentation.rst:208
#: ../../getting_started/documentation.rst:210
msgid ""
"**Role distribution**: In this context, the Consultant will be responsible "
"for delivering a solution corresponding to the defined specifications; the "
@ -307,33 +305,33 @@ msgid ""
"requirements of the operational reality."
msgstr ""
#: ../../getting_started/documentation.rst:214
#: ../../getting_started/documentation.rst:216
msgid ""
"**Change management**: When a change needs to be made to the solution, the "
"noted gap is caused by:"
msgstr ""
#: ../../getting_started/documentation.rst:218
#: ../../getting_started/documentation.rst:220
msgid ""
"A difference between the specification and the delivered solution - This is "
"a correction for which the Consultant is responsible"
msgstr ""
#: ../../getting_started/documentation.rst:220
#: ../../getting_started/documentation.rst:223
msgid "**or**"
msgstr ""
#: ../../getting_started/documentation.rst:222
#: ../../getting_started/documentation.rst:225
msgid ""
"A difference between the specification and the imperatives of operational "
"reality - This is a change that is the responsibility of SPoC."
msgstr ""
#: ../../getting_started/documentation.rst:226
msgid "7. Data Imports"
#: ../../getting_started/documentation.rst:229
msgid "Data Imports"
msgstr ""
#: ../../getting_started/documentation.rst:228
#: ../../getting_started/documentation.rst:231
msgid ""
"Importing the history of transactional data is an important issue and must "
"be answered appropriately to allow the project running smoothly. Indeed, "
@ -342,14 +340,14 @@ msgid ""
"it will be decided :"
msgstr ""
#: ../../getting_started/documentation.rst:234
#: ../../getting_started/documentation.rst:237
msgid ""
"**Not to import anything**: It often happens that after reflection, "
"importing data history is not considered necessary, these data being, "
"moreover, kept outside Odoo and consolidated for later reporting."
msgstr ""
#: ../../getting_started/documentation.rst:239
#: ../../getting_started/documentation.rst:242
msgid ""
"**To import a limited amount of data before going into production**: When "
"the data history relates to information being processed (purchase orders, "
@ -358,7 +356,7 @@ msgid ""
" import will be made before the production launch."
msgstr ""
#: ../../getting_started/documentation.rst:246
#: ../../getting_started/documentation.rst:249
msgid ""
"**To import after production launch**: When the data history needs to be "
"integrated with Odoo mainly for reporting purposes, it is clear that these "
@ -366,16 +364,16 @@ msgid ""
"production launch of the solution will precede the required imports."
msgstr ""
#: ../../getting_started/documentation.rst:253
msgid "8. Support"
#: ../../getting_started/documentation.rst:256
msgid "Support"
msgstr ""
#: ../../getting_started/documentation.rst:255
#: ../../getting_started/documentation.rst:258
msgid ""
"When your project is put in production, our support teams take care of your "
"questions or technical issues."
msgstr ""
#: ../../getting_started/documentation.rst:258
#: ../../getting_started/documentation.rst:261
msgid "See :ref:`support-expectations`."
msgstr ""

969
locale/fr/LC_MESSAGES/helpdesk.po
View File

File diff suppressed because it is too large Load Diff

10
locale/fr/LC_MESSAGES/index.po
View File

@ -4,16 +4,16 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Richard Mathot <rim@odoo.com>, 2019
# Richard Mathot <rim@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Last-Translator: Richard Mathot <rim@odoo.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Last-Translator: Richard Mathot <rim@odoo.com>, 2020\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"

4411
locale/fr/LC_MESSAGES/inventory.po
View File

File diff suppressed because it is too large Load Diff

421
locale/fr/LC_MESSAGES/iot.po
View File

File diff suppressed because it is too large Load Diff

319
locale/fr/LC_MESSAGES/livechat.po
View File

@ -4,18 +4,19 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2019
# Eloïse Stilmant <est@odoo.com>, 2019
# William Henrotin <whe@odoo.com>, 2019
# Martin Trigaux, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
# Aurélien Pillevesse <aurelienpillevesse@hotmail.fr>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Last-Translator: William Henrotin <whe@odoo.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Fernanda Marques <fem@odoo.com>, 2020\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -23,189 +24,253 @@ msgstr ""
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../livechat/livechat.rst:5
msgid "Live Chat"
msgstr "Live Chat"
#: ../../livechat/overview.rst:3
msgid "Overview"
msgstr "Vue d'ensemble"
#: ../../livechat/livechat.rst:8
msgid "Chat in real time with website visitors"
#: ../../livechat/overview/get_started.rst:3
msgid "Get Started with Live Chat"
msgstr ""
#: ../../livechat/livechat.rst:10
#: ../../livechat/overview/get_started.rst:5
msgid ""
"With Odoo Live Chat, you can establish a direct contact with your website "
"visitors. A simple dialog box will be available on their screen and will "
"allow them to get in touch with one of your sales representatives. This way,"
" you can easily turn prospects into potential business opportunities. You "
"will also be able to provide assistance to your customers. Overall, this is "
"the perfect tool to improve customer satisfaction."
"Live Chat has the highest satisfaction rating of any communication tool. It "
"allows fast responses and it is accessible and convenient, as your customers"
" can keep doing what they are doing while interacting with you. Remember: "
"your customers want to talk to you, so let's make it easy."
msgstr ""
"Avec Odoo Discussion instantanée, vous pouvez établir un contact direct avec"
" les visiteur de votre site web. Une simple boite de dialogue sera "
"disponible sur leur écran et leur permettra de discuter av,ec un de vos "
"représentant commercial. de cette manière, vous pouvez facilement "
"transformer un intérêt en une potentielle opportunité. Vous serez aussi "
"capable d'apporter une aide à vos clients. En résumé, il s'agit du parfait "
"outil pour améliorer la satisfaction de votre clientèle"
#: ../../livechat/livechat.rst:19
msgid "Configuration"
msgstr "Configuration"
#: ../../livechat/overview/get_started.rst:10
msgid "Set up"
msgstr ""
#: ../../livechat/livechat.rst:21
#: ../../livechat/overview/get_started.rst:12
msgid ""
"To get the Live Chat feature, open the Apps module, search for \"Live Chat\""
" and then click on install."
"Once *Live Chat* is installed on your database, if your website was created "
"with Odoo, the application is automatically added to it. All that is left to"
" do is to go to :menuselection:`Website --> Configuration --> Settings --> "
"Live Chat`."
msgstr ""
"Pour avoir la fonctionnalité Discussion Instantanée, ouvrez le module "
"Applications, cherchez \"Discussion Instantanée\" et cliquer sur installer."
#: ../../livechat/livechat.rst:27
#: ../../livechat/overview/get_started.rst:21
msgid ""
"The Live Chat module provides you a direct access to your channels. There, "
"operators can easily join and leave the chat."
"Select the channel to be linked to your website or create one on the fly."
msgstr ""
"Le module Discussion Instantanée vous donne un accès direct au canaux de "
"discussion, Là, les opérateurs peuvent facilement rejoindre et quitter les "
"discussions."
#: ../../livechat/livechat.rst:34
msgid "Add the live chat to an Odoo website"
msgstr "Ajouter les discussions instantanées au site web Odoo"
#: ../../livechat/overview/get_started.rst:27
msgid "For both scenarios, under:"
msgstr ""
#: ../../livechat/livechat.rst:36
#: ../../livechat/overview/get_started.rst:30
msgid ""
"If your website was created with Odoo, then the live chat is automatically "
"added to it. All that is left to do, is to go to :menuselection:`Website -->"
" Configuration --> Settings` to select the channel to be linked to the "
"website."
"- **Operators**: add agents to respond to the chat requests. Add as many as "
"you like, and keep in mind that operators that do not show any activity in "
"Odoo for more than 30min are considered disconnected."
msgstr ""
#: ../../livechat/livechat.rst:45
msgid "Add the live chat to an external website"
msgstr ""
#: ../../livechat/livechat.rst:47
#: ../../livechat/overview/get_started.rst:33
msgid ""
"If your website was not created with Odoo, go to the Live Chat module and "
"then select the channel to be linked. There, you can simply copy paste the "
"code available into your website. A specific url you can send to customers "
"or suppliers for them to access the live chat is also provided."
"- **Options**: set the default text to be shown on the live chat button; an "
"automated welcome message to be seen by visitors when a conversation is "
"initiated, and the text that prompts the user to initiate a chat."
msgstr ""
#: ../../livechat/livechat.rst:54
msgid "Hide / display the live chat according to rules"
msgstr ""
#: ../../livechat/livechat.rst:56
#: ../../livechat/overview/get_started.rst:36
msgid ""
"Rules for the live chat can be defined on the channel form. For instance, "
"you can choose to display the chat in the countries you speak the language "
"of. On the contrary, you are able to hide the chat in countries your company"
" does not sell in. If you select *Auto popup*, you can also set the length "
"of time it takes for the chat to appear."
"- **Channel Rules**: choose an action for a given URL, and/or per country. "
"In the example below, the chat window automatically pops-up 3 seconds after "
"users (from any country) land on the contact us page."
msgstr ""
#: ../../livechat/livechat.rst:66
msgid "Prepare automatic messages"
msgstr ""
#: ../../livechat/livechat.rst:68
#: ../../livechat/overview/get_started.rst:43
msgid ""
"On the channel form, in the *Options* section, several messages can be typed"
" to appear automatically on the chat. This will entice visitors to reach you"
" through the live chat."
"GeoIP, which refers to the process of finding a computer terminal’s "
"geographical location by its IP address, must be installed on your server. "
"Otherwise, under *Channel Rules*, countries are not taken into account."
msgstr ""
#: ../../livechat/livechat.rst:76
msgid "Start chatting with customers"
#: ../../livechat/overview/get_started.rst:48
msgid "External options"
msgstr ""
#: ../../livechat/livechat.rst:78
#: ../../livechat/overview/get_started.rst:51
msgid ""
"In order to start chatting with customers, first make sure that the channel "
"is published on your website. To do so, select *Unpublished on Website* on "
"the top right corner of the channel form to toggle the *Published* setting. "
"Then, the live chat can begin once an operator has joined the channel."
"If your website was not created with Odoo, you can find the code to be added"
" to your own, under the *Widget* tab."
msgstr ""
#: ../../livechat/livechat.rst:88
#: ../../livechat/overview/get_started.rst:52
msgid ""
"If no operator is available and/or if the channel is unpublished on the "
"website, then the live chat button will not appear to visitors."
"Odoo also offers an URL you can send to users so they can have access to a "
"single live chat page."
msgstr ""
#: ../../livechat/livechat.rst:92
#: ../../livechat/overview/get_started.rst:59
msgid "Managing chat requests"
msgstr ""
#: ../../livechat/overview/get_started.rst:61
msgid ""
"Conversations initiated by visitors also appear in the Discuss module in "
"addition to popping up as a direct message. Therefore, inquiries can be "
"answered wherever you are in Odoo."
"Conversations initiated by visitors pop up as a direct message, and are "
"shown in *Discuss*. Therefore, inquiries can be answered wherever you are in"
" Odoo."
msgstr ""
#: ../../livechat/livechat.rst:96
#: ../../livechat/overview/get_started.rst:69
msgid ""
"If there are several operators who have all joined a channel, the system "
"will dispatch visitor sessions randomly between them."
"Conversations are dispatched based on the current workload of the online "
"operators."
msgstr ""
#: ../../livechat/livechat.rst:100
#: ../../livechat/overview/get_started.rst:72
msgid "Leave or join a channel"
msgstr ""
#: ../../livechat/overview/get_started.rst:74
msgid ""
"Go to :menuselection:`Website --> Configuration --> Settings`, access your "
"channel under *Live Chat*, and *Join Channel* or *Leave Channel*."
msgstr ""
#: ../../livechat/overview/get_started.rst:82
#: ../../livechat/overview/responses.rst:48
msgid ":doc:`ratings`"
msgstr ""
#: ../../livechat/overview/get_started.rst:83
#: ../../livechat/overview/ratings.rst:45
msgid ":doc:`responses`"
msgstr ""
#: ../../livechat/overview/ratings.rst:3
msgid "Ratings"
msgstr "Évaluations"
#: ../../livechat/overview/ratings.rst:5
msgid ""
"Giving users the opportunity to rate their interactions can help you "
"improving the experience you offer. That means staying on top of your "
"customers' needs, besides keeping track of your operators’ performances."
msgstr ""
#: ../../livechat/overview/ratings.rst:10
msgid "Customer Rating"
msgstr "Évaluation de la clientèle"
#: ../../livechat/overview/ratings.rst:12
msgid ""
"Once the user chooses to close the chat window, he can rate his interaction."
msgstr ""
#: ../../livechat/overview/ratings.rst:14
msgid ""
"If the user is *Not satisfied* or *Highly dissatisfied*, a field allowing "
"for an explanation is shown."
msgstr ""
#: ../../livechat/overview/ratings.rst:15
msgid "A copy of the conversation can also be sent by email."
msgstr ""
#: ../../livechat/overview/ratings.rst:22
msgid "The rating is shown on the chat window itself for the operator."
msgstr ""
#: ../../livechat/overview/ratings.rst:28
msgid "And under :menuselection:`Report --> Customer Ratings`."
msgstr ""
#: ../../livechat/overview/ratings.rst:35
msgid "Make the rating public"
msgstr ""
#: ../../livechat/overview/ratings.rst:37
msgid ""
"Go to :menuselection:`Website --> Configuration --> Settings`, access your "
"channel form, click on *Go to Website* and on *Unpublished*, to publish the "
"rating of that channel on your website."
msgstr ""
#: ../../livechat/overview/responses.rst:3
msgid "Commands and Canned Responses"
msgstr ""
#: ../../livechat/overview/responses.rst:5
msgid ""
"Using canned responses can help you save time and have a previous, well-"
"thought response, to some of your most common questions and comments."
msgstr ""
#: ../../livechat/overview/responses.rst:9
msgid "Use commands"
msgstr ""
msgstr "Utilisez des commandes"
#: ../../livechat/livechat.rst:102
#: ../../livechat/overview/responses.rst:11
msgid ""
"Commands are useful shortcuts for completing certain actions or to access "
"information you might need. To use this feature, simply type the commands "
"into the chat. The following actions are available :"
"Commands are shortcuts that do specific actions within the chat window:"
msgstr ""
#: ../../livechat/livechat.rst:106
msgid "**/help** : show a helper message."
#: ../../livechat/overview/responses.rst:13
msgid "**/help**: shows a help message."
msgstr ""
#: ../../livechat/livechat.rst:108
msgid "**/helpdesk** : create a helpdesk ticket."
#: ../../livechat/overview/responses.rst:14
msgid "**/helpdesk**: creates a helpdesk ticket."
msgstr ""
#: ../../livechat/livechat.rst:110
msgid "**/helpdesk\\_search** : search for a helpdesk ticket."
#: ../../livechat/overview/responses.rst:15
msgid "**/helpdesk_search**: searches for a helpdesk ticket."
msgstr ""
#: ../../livechat/livechat.rst:112
msgid "**/history** : see 15 last visited pages."
#: ../../livechat/overview/responses.rst:16
msgid "**/history**: shows the last 15 visited pages."
msgstr ""
#: ../../livechat/livechat.rst:114
msgid "**/lead** : create a new lead."
#: ../../livechat/overview/responses.rst:17
msgid "**/lead**: creates a new lead."
msgstr ""
#: ../../livechat/livechat.rst:116
msgid "**/leave** : leave the channel."
#: ../../livechat/overview/responses.rst:18
msgid "**/leave**: leaves the channel."
msgstr ""
#: ../../livechat/livechat.rst:119
#: ../../livechat/overview/responses.rst:0
msgid ""
"If a helpdesk ticket is created from the chat, then the conversation it was "
"generated from will automatically appear as the description of the ticket. "
"The same goes for the creation of a lead."
"- For *helpdesk tickets*: make sure the application is installed on your "
"database and the option *Live Chat* under :menuselection:`Helpdesk --> "
"Configuration --> Helpdesk Teams` is enabled."
msgstr ""
#: ../../livechat/livechat.rst:124
#: ../../livechat/overview/responses.rst:0
msgid ""
"- For *leads*: the *CRM* application must be installed on your database."
msgstr ""
#: ../../livechat/overview/responses.rst:26
msgid ""
"To access the ticket or lead created from the chat, click on the shortcut "
"link."
msgstr ""
#: ../../livechat/overview/responses.rst:33
msgid ""
"Helpdesk tickets created from the chat automatically add the conversation as"
" a description of the ticket. The same goes for the creation of a lead."
msgstr ""
#: ../../livechat/overview/responses.rst:37
msgid "Send canned responses"
msgstr "Envoyez des réponses toutes prêtes"
#: ../../livechat/overview/responses.rst:40
msgid ""
"Canned responses allow you to have a full piece of text being placed when "
"you type a shortcut word. To create them, go to :menuselection:`Live Chat "
"--> Configuration --> Canned Responses`."
msgstr ""
#: ../../livechat/livechat.rst:126
#: ../../livechat/overview/responses.rst:41
msgid ""
"Canned responses allow you to create substitutes to generic sentences you "
"frequently use. Typing a word instead of several will save you a lot of "
"time. To add canned responses, go to :menuselection:`LIVE CHAT --> "
"Configuration --> Canned Responses` and create as many as you need to. Then,"
" to use them during a chat, simply type \":\" followed by the shortcut you "
"assigned."
msgstr ""
#: ../../livechat/livechat.rst:136
msgid ""
"You now have all of the tools needed to chat in live with your website "
"visitors, enjoy !"
"To use them during a conversation, simply type **:** followed by the "
"shortcut word you created."
msgstr ""

471
locale/fr/LC_MESSAGES/manufacturing.po
View File

@ -4,18 +4,19 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2019
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2019
# thomas quertinmont <tqu@odoo.com>, 2019
# Martin Trigaux, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
# thomas quertinmont <tqu@odoo.com>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Last-Translator: thomas quertinmont <tqu@odoo.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Fernanda Marques <fem@odoo.com>, 2020\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -25,15 +26,15 @@ msgstr ""
#: ../../manufacturing.rst:5
msgid "Manufacturing"
msgstr "Fabrication"
msgstr "Production"
#: ../../manufacturing/management.rst:5
msgid "Manufacturing Management"
msgstr ""
msgstr "Gestion de la production"
#: ../../manufacturing/management/alternative_wc.rst:3
msgid "Using an alternative Work Center"
msgstr ""
msgstr "Utilisation d'un poste de travail"
#: ../../manufacturing/management/alternative_wc.rst:5
msgid ""
@ -42,6 +43,10 @@ msgid ""
" If in practice, employees can manufacture the goods at another work center,"
" it is not that simple."
msgstr ""
"Pour de nombreuses entreprises manufacturières, un problème commun est de "
"devoir fabriquer, en même temps, plusieurs produits habituellement fabriqués"
" au même poste de travail. Si, dans la pratique, les employés peuvent le "
"faire sur un autre poste de travail, en réalité ce n'est pas si simple."
#: ../../manufacturing/management/alternative_wc.rst:10
msgid ""
@ -59,13 +64,15 @@ msgstr ""
#: ../../manufacturing/management/alternative_wc.rst:20
msgid "Configure your Work Centers"
msgstr ""
msgstr "Configurez vos postes de travail"
#: ../../manufacturing/management/alternative_wc.rst:22
msgid ""
"The first thing to do is to go to the *Manufacturing* app settings. Then, "
"enable the *Work Orders* feature and hit save."
msgstr ""
"La première chose à faire est aller dans l'application *Production*, puis "
"activer la fonctionnalité *Ordres de travail* et enregistrer."
#: ../../manufacturing/management/alternative_wc.rst:30
msgid ""
@ -88,7 +95,7 @@ msgstr ""
#: ../../manufacturing/management/alternative_wc.rst:56
msgid "Create your Work Orders"
msgstr ""
msgstr "Créez vos ordres de travail"
#: ../../manufacturing/management/alternative_wc.rst:58
msgid ""
@ -150,11 +157,11 @@ msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:24
msgid ""
"Before creating your *BoM*, you have to create the product using the *BoM* "
"and, at least, one of the components. Go to the *Master Data* menu > "
"*Products* and create both the finished product and the component."
"and, at least, one of the components. Go to the :menuselection:`Master Data "
"menu --> Products` and create both the finished product and the component."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:29
#: ../../manufacturing/management/bill_configuration.rst:28
msgid ""
"Once done, go to the *Bills of Materials* menu under *Master Data*. Now, "
"create it. Choose the product from the dropdown menu and add your components"
@ -162,64 +169,64 @@ msgid ""
"*Manufacture this Product*."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:38
#: ../../manufacturing/management/bill_configuration.rst:37
msgid "Using the same BoM to describe Variants"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:40
#: ../../manufacturing/management/bill_configuration.rst:39
msgid ""
"As said above, you can use *BoM* for *Product Variants*. It is basically the"
" same as for the standard product."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:43
#: ../../manufacturing/management/bill_configuration.rst:42
msgid ""
"If your *BoM* is for one variant only, then specify which one in the "
"*Product Variant* field. If not, specify the variant it is consumed for on "
"each component line. You can add several variants for each component."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:52
#: ../../manufacturing/management/bill_configuration.rst:51
msgid "Adding a routing"
msgstr ""
msgstr "Ajouter un routage"
#: ../../manufacturing/management/bill_configuration.rst:54
#: ../../manufacturing/management/bill_configuration.rst:53
msgid ""
"You can add routing to your *BoM*. You will do this if you need to define a "
"series of operations required by your manufacturing process. To use it, "
"enable the *Work Orders* feature in the *Manufacturing* app settings."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:63
#: ../../manufacturing/management/bill_configuration.rst:62
msgid ""
"Each *BoM* can have only one routing while each routing can be used multiple"
" times."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:66
#: ../../manufacturing/management/bill_configuration.rst:65
msgid ""
"Now that you have created your routing, add it to your *BoM*. You can select"
" when, in the work operations, your components are consumed with the "
"dropdown menu."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:74
#: ../../manufacturing/management/bill_configuration.rst:73
msgid "Adding By-Products"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:76
#: ../../manufacturing/management/bill_configuration.rst:75
msgid ""
"In Odoo, a *by-product* is any product produced by a *BoM* in addition to "
"the primary product."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:79
#: ../../manufacturing/management/bill_configuration.rst:78
msgid ""
"To add *by-products* to a *BoM*, you will first need to enable them from the"
" *Manufacturing* app settings."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:85
#: ../../manufacturing/management/bill_configuration.rst:84
msgid ""
"Once the feature is enabled, you can add your *By-Products* to your *BoMs*. "
"You can add as many *By-Products* as you want. Just keep in mind that you "
@ -249,7 +256,7 @@ msgstr ""
#: ../../manufacturing/management/flexible_components_consumption.rst:16
#: ../../manufacturing/management/kit_shipping.rst:31
#: ../../manufacturing/management/kit_shipping.rst:66
#: ../../manufacturing/management/subcontracting.rst:9
#: ../../manufacturing/management/subcontracting.rst:26
#: ../../manufacturing/management/use_mps.rst:9
msgid "Configuration"
msgstr "Configuration"
@ -431,7 +438,7 @@ msgstr ""
#: ../../manufacturing/management/manufacturing_order.rst:32
msgid "Create a manufacturing order"
msgstr ""
msgstr "Créez un ordre de production"
#: ../../manufacturing/management/manufacturing_order.rst:34
msgid "Record the production"
@ -467,11 +474,11 @@ msgstr ""
#: ../../manufacturing/management/manufacturing_order.rst:62
msgid "Create the manufacturing order"
msgstr ""
msgstr "Créez l'ordre de production"
#: ../../manufacturing/management/manufacturing_order.rst:67
msgid "Schedule the associated work orders"
msgstr ""
msgstr "Programmer des ordres de travail associées"
#: ../../manufacturing/management/manufacturing_order.rst:72
msgid "Perform the scheduled work and record production"
@ -479,7 +486,7 @@ msgstr ""
#: ../../manufacturing/management/plan_work_orders.rst:3
msgid "Plan Work Orders"
msgstr ""
msgstr "Planifier des ordres de travail"
#: ../../manufacturing/management/plan_work_orders.rst:5
msgid ""
@ -500,13 +507,16 @@ msgstr ""
#: ../../manufacturing/management/plan_work_orders.rst:17
msgid "Create the Work Orders"
msgstr ""
msgstr "Créez des ordres de travail"
#: ../../manufacturing/management/plan_work_orders.rst:19
msgid ""
"The first thing you need to do is to open the *Manufacturing* app. Then, Go "
"to the settings and enable the *Work Orders* feature."
msgstr ""
"La première chose à faire est ouvrir l'application *Production*. Ensuite, il"
" faut aller dans les paramètres et activer la fonctionnalité *Ordres de "
"travail*."
#: ../../manufacturing/management/plan_work_orders.rst:25
msgid ""
@ -624,7 +634,7 @@ msgstr ""
#: ../../manufacturing/management/routing_kit_bom.rst:84
#: ../../manufacturing/management/routing_kit_bom.rst:127
msgid "Manufacturing Order"
msgstr "Ordre de fabrication"
msgstr "Ordre de production"
#: ../../manufacturing/management/routing_kit_bom.rst:42
msgid ""
@ -746,153 +756,320 @@ msgid ""
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:3
msgid "Subcontract the manufacturing"
msgid "Subcontract your Manufacturing"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:5
msgid ""
"Some businesses subcontract the production of some finished products through"
" subcontractors. This can be easily managed through Odoo."
"Outsourcing a portion of some or all your company’s manufacturing needs is "
"not easy. To make it work right, you have to:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:8
msgid "Manage the inventory of raw materials at your subcontractor;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:9
msgid ""
"Ship new materials to your subcontractors based on your forecasted demand;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:11
msgid ""
"Go to the *Manufacturing app > Configuration > Settings* and tick the box "
"*Subcontracting*."
"Keep track of manufacturing operations done at the subcontractor location;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:17
#: ../../manufacturing/management/subcontracting.rst:13
msgid "Control incoming goods quality;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:14
msgid "Control subcontractors bills."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:16
msgid ""
"You can now define subcontracted *Bill of Materials*. Therefore, you need to"
" go to *Manufacturing > Master Data > Bill of Materials* and hit *Create*. "
"In this *BoM*, list the components which will be used by the subcontractor "
"to manufacture the subcontracted finished product. Specify that the *BoM* "
"type is *Subcontracting*."
"Here is an example of subcontracting the manufacturing of “C”, which is "
"produced out of raw materials “A” and “B”."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:22
msgid "You can also define subcontractors on the BoM."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:24
msgid "If no subcontractor is set, the BoM can be used by any subcontractor"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:26
msgid "If some are set, the BoM can only be used for those subcontractors"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:32
msgid "Receive or buy a subcontracted product"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:34
msgid "You have two options to trigger the subcontracting of a product:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:36
#: ../../manufacturing/management/subcontracting.rst:23
msgid ""
"**Option A**: You can buy the subcontracted product from your subcontractor"
"With its subcontracting feature, Odoo helps you handle this flow easily."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:28
msgid ""
"To use the subcontracting feature, go to :menuselection:`Manufacturing --> "
"Configuration --> Settings` and tick the box *Subcontracting*."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:35
msgid ""
"To define if a product must be subcontracted, use a *Bill of Materials "
"(BoM)* of type *Subcontracting*."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:38
msgid "**Option B**: You can directly receive the subcontracted product"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:40
msgid "Let’s start with option A (option B is just a simpler version of it)."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:42
msgid ""
"Create a new purchase order. The vendor must be a subcontractor. The unit "
"price should be the cost you are paying to the subcontractor for the "
"subcontracting (thus, it’s not necessarily the total cost of the "
"subcontracted product)."
"To create a new *BoM*, go to :menuselection:`Manufacturing --> Master Data "
"--> Bill of Materials` and hit create. Then, list the components your "
"subcontractor needs to manufacture the product. For costing purposes, you "
"might want to register all the components, even the ones that are sourced "
"directly from the subcontractor."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:50
#: ../../manufacturing/management/subcontracting.rst:44
msgid ""
"The validation of the purchase order automatically creates the receipt. "
"Whenever you receive the product, you can validate the receipt. The "
"following stock moves are created:"
"Once you have set the *BoM Type* to *Subcontracting*, specify one or several"
" subcontractors."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:52
msgid "Basic Subcontracting Flow"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:54
msgid "For the components"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:56
msgid "From Subcontracting To Production"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:58
msgid "For the subcontracted product"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:60
msgid "From Production to Subcontracting"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:62
msgid "From Subcontracting to Stock"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:64
msgid ""
"The *Subcontracting Location* represents the place where the products are at"
" your subcontractor’s warehouse. It is configured as an internal location, "
"the components that are sent to the subcontractor are still valued in your "
"stock."
"To let your subcontractor know how many products you need, create and send "
"them purchase orders (PO). To do so, open the *Purchase* app and create a "
"new one. Be sure to send the PO to a vendor that is defined as a "
"subcontractor on the *BoM*."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:69
#: ../../manufacturing/management/subcontracting.rst:63
msgid ""
"For option B, you can simply create the receipt manually with a partner of "
"type subcontractor defined on it."
"Once the *PO* is validated (1), a pending receipt is created. When the "
"products are received, validate the receipt (2), with the actual quantity "
"received. Then Odoo automatically created several inventory moves:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:73
msgid "Resupply the subcontractor with the components"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:75
#: ../../manufacturing/management/subcontracting.rst:68
msgid ""
"There are 3 ways to manage the resupply of your subcontractor with the "
"components:"
"Consume the components at the subcontractor’s location, based on the *BoM* "
"(3);"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:80
msgid "**Manually**: You create a delivery order in which you set the"
#: ../../manufacturing/management/subcontracting.rst:70
msgid "Produce finished goods at the subcontractor’s location (4);"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:71
msgid ""
"Move products from the subcontractor’s location to YourCompany through the "
"validated receipt (5)."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:74
msgid ""
"Of course, Odoo does all the transactions for you, automatically. Simply "
"control the vendor bill with the usual matching process with the purchase "
"order."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:79
msgid "subcontractor as a partner and you choose the components to deliver."
msgid ""
"The *PO* is optional. If you create a receipt manually, with the right "
"subcontractor, Odoo still performs all the moves. Useful if the "
"subcontractor does not bill a fixed price per item, but rather the time and "
"materials used."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:85
msgid "Inventory Valuation"
msgstr "Valorisation de l'inventaire"
#: ../../manufacturing/management/subcontracting.rst:87
msgid "The cost of the manufactured product “C” is defined as:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:89
msgid "**With reordering rules**: You can define a *reordering rule*"
msgid "**C = A + B + s**"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:86
#: ../../manufacturing/management/subcontracting.rst:91
msgid "With:"
msgstr "Avec :"
#: ../../manufacturing/management/subcontracting.rst:93
msgid "**A**: Cost of raw materials coming from YourCompany;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:96
msgid "**B**: Cost of raw materials sourced directly from the"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:96
msgid "subcontractor;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:98
msgid "**s**: Cost of the subcontracted service."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:100
msgid ""
"on the *Subcontracting location* to ensure that they are always enough "
"components sent to your subcontractors. When the reordering rule is "
"triggered, a delivery order is created for the product is automatically "
"created."
"Sending raw materials to your subcontractors (**A**) does not impact the "
"inventory valuation, the components still belonging to your company. To "
"manage this, the *Subcontracting Location* is configured as an *Internal "
"Location* so that the components are still valued in the inventory."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:97
msgid "**On order**: You can also deliver the components to your"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:95
#: ../../manufacturing/management/subcontracting.rst:106
msgid ""
"subcontractors each time you order a subcontracted product. For this, you "
"need to tick the route *Resupply Subcontractor on Order* on the wanted "
"Then, the vendor price set on the product C form has to be what has to be "
"paid to the subcontractor for his parts and service time: **B + s**. The "
"product cost has to be: **A + B + s**, how much the product is valued in the"
" accounting."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:111
msgid ""
"Finally, the subcontractor bill matches the purchase order, with the "
"proposed price coming from the finished products C."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:115
msgid ""
"If managing the replenishment of raw materials **B** at your subcontractor’s"
" location is not needed, simply include the cost of **B** in the "
"subcontractor’s price **s** and remove the products *B* from the *BoM*."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:121
msgid "Traceability"
msgstr "Traçabilité"
#: ../../manufacturing/management/subcontracting.rst:123
msgid ""
"In case the products received from the subcontractor contain tracked "
"components, their serial or lot numbers need to be specified during the "
"receipt."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:127
msgid ""
"On the receipt of the subcontracted product, a *Record Components* button "
"appears when necessary. Click on it to open a dialog and record the "
"serial/lot numbers of the components. If the finished product is also "
"tracked, its serial/lot number can be registered here too."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:136
msgid ""
"For audit purposes, it is possible to check the lot numbers recorded on a "
"receipt by using the icon on the right of the finished products:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:144
msgid "Automate Replenishment of Subcontractors"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:146
msgid ""
"To manage the resupply of your subcontractor, activate *Multi-locations* in "
":menuselection:`Inventory --> Configuration --> Configuration`. Then, the "
"inventory at the subcontractor location can be tracked."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:151
msgid ""
"It is possible to resupply subcontractors by sending products from the "
"company locations, or by sending products from another supplier to the "
"subcontractors."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:156
msgid "Replenishment from the warehouse"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:158
msgid ""
"Resupplying subcontractors manually is the simplest approach. To do so, "
"create delivery orders in which the subcontractor is set as a delivery "
"address and fill the components to deliver."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:162
msgid ""
"To automate the subcontractors’ replenishment propositions, there are two "
"approaches:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:165
msgid "Reordering rules;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:166
msgid "Replenish on order flow."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:168
msgid ""
"For the first one, just define a reordering rule on the subcontracting "
"location, with a minimum and maximum inventory level. When the reordering "
"rule is triggered, a delivery order is created to ship the components to the"
" subcontractor."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:177
msgid ""
"The second approach is to use a “pull” flow. Here, the demand in the "
"finished product (real demand or forecasted one through the Master "
"Production Schedule) triggers the replenishment of the subcontractor. To do "
"so, select the route *Resupply Subcontractor on Order* on the wanted "
"components."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:188
msgid "Replenishment from another supplier"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:190
msgid ""
"When purchasing items to another supplier, it is possible to ask him to "
"deliver the subcontractor directly. To do so, activate the *Drop Shipping* "
"feature in :menuselection:`Purchase --> Configuration --> Configuration`."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:195
msgid ""
"Now, set the *Dropship* option in the *Deliver To* field of the *Other "
"Information* tab. Then, provide the address of the subcontractor for the "
"shipping."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:203
msgid ""
"That way, the supplier can ship items directly and you simply receive and "
"pay the bill. However, it is still required to validate receipts for the "
"subcontractor."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:212
msgid "Quality Control"
msgstr "Contrôle qualité"
#: ../../manufacturing/management/subcontracting.rst:214
msgid ""
"Controlling the quality of the products manufactured by subcontractors is "
"possible thanks to the Odoo Quality app. Quality checks can be made on a "
"manufacturing step but, because the manufacturing process is handled by an "
"external party, it can be defined on the product reception."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:224
msgid ""
"To create a quality check at the receipt, open the *Quality* app and create "
"a new *Control Point* on the reception."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:231
msgid ""
"By doing so, a quality check is automatically created each time a finished "
"product is received."
msgstr ""
#: ../../manufacturing/management/unbuild.rst:3
msgid "Unbuild a product"
msgstr ""
@ -963,8 +1140,8 @@ msgstr ""
#: ../../manufacturing/management/use_mps.rst:11
msgid ""
"Go to the *Manufacturing app > Configuration > Settings* and activate the "
"Master Production Schedule feature before hitting save."
"Go to the :menuselection:`Manufacturing app --> Configuration --> Settings` "
"and activate the Master Production Schedule feature before hitting save."
msgstr ""
#: ../../manufacturing/management/use_mps.rst:18
@ -975,10 +1152,10 @@ msgstr ""
#: ../../manufacturing/management/use_mps.rst:20
msgid ""
"Now, go in *Planning > Master Production Schedule* and click on add a "
"product. You can now define your safety stock target (= the stock you want "
"to have on hand at the end of the period) and the minimum and maximum "
"quantities to replenish."
"Now, go in :menuselection:`Planning --> Master Production Schedule` and "
"click on add a product. You can now define your safety stock target (= the "
"stock you want to have on hand at the end of the period) and the minimum and"
" maximum quantities to replenish."
msgstr ""
#: ../../manufacturing/management/use_mps.rst:29
@ -1116,32 +1293,32 @@ msgstr "Vue d'ensemble"
msgid "Repair Management"
msgstr ""
#: ../../manufacturing/repair/repair.rst:3
#: ../../manufacturing/repair/repair.rst:5
msgid "Repair products"
msgstr ""
#: ../../manufacturing/repair/repair.rst:5
#: ../../manufacturing/repair/repair.rst:7
msgid ""
"The Odoo *Repair* app allows you to manage a complete after sales process "
"but also to simply repair products you have manufactured, if they present a "
"defect."
msgstr ""
#: ../../manufacturing/repair/repair.rst:10
#: ../../manufacturing/repair/repair.rst:12
msgid "Create a Repair Order"
msgstr "Créer un Ordre de Réparation"
#: ../../manufacturing/repair/repair.rst:12
#: ../../manufacturing/repair/repair.rst:14
msgid ""
"Once in the app, you can access your existing *Repair Orders* and create a "
"new one."
msgstr ""
#: ../../manufacturing/repair/repair.rst:19
#: ../../manufacturing/repair/repair.rst:21
msgid "Manage a repair"
msgstr ""
#: ../../manufacturing/repair/repair.rst:21
#: ../../manufacturing/repair/repair.rst:23
msgid ""
"When a customer sends you a product for repair, create a new *Repair Order*."
" Fill it in with all the information you may need such as the product, the "
@ -1149,13 +1326,13 @@ msgid ""
" might need, etc."
msgstr ""
#: ../../manufacturing/repair/repair.rst:29
#: ../../manufacturing/repair/repair.rst:31
msgid ""
"Once everything is done, you can then send the repair quotation to your "
"customer. If it is approved, you can confirm the repair. You will then be "
"able to start & end the repair when it is completed."
msgstr ""
#: ../../manufacturing/repair/repair.rst:36
#: ../../manufacturing/repair/repair.rst:38
msgid "You can now invoice the repair."
msgstr ""
msgstr "Vous pouvez désormais facturer la facturation."

382
locale/fr/LC_MESSAGES/marketing_automation.po Normal file
View File

@ -0,0 +1,382 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
# Florent de Labarre <florent@iguanayachts.com>, 2020
# Cécile Collart <cco@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Cécile Collart <cco@odoo.com>, 2020\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../marketing_automation.rst:5
msgid "Marketing Automation"
msgstr "Automatisation du Marketing"
#: ../../marketing_automation/advanced.rst:3
msgid "Advanced"
msgstr "Avancé"
#: ../../marketing_automation/advanced/understanding_metrics.rst:3
msgid "Understanding Metrics"
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:4
msgid ""
"Metrics are values that help you measure progress and can be a powerful way "
"of linking your employees to goals."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:9
msgid ""
"When you create a workflow in Odoo, its visual content already shows metrics"
" in a graph form and in numbers."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:10
msgid "Let’s consider the example below:"
msgstr ""
#: ../../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."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:20
msgid "A total number of 20 records match the criteria."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:28
msgid ""
"Out of those 20 records, 25 have become participants, in other words, they "
"have matched the criteria."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:36
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."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:41
msgid ""
"The filter here is applied to *all* activities. Leads that lose the tag in "
"the meantime will be excluded from later activities."
msgstr ""
#: ../../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*."
msgstr ""
#: ../../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."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:0
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."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:64
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 ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:65
msgid ""
"If a participant does not match the conditions, it will be added to "
"*Rejected*."
msgstr ""
#: ../../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."
msgstr ""
#: ../../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)."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:79
msgid ":doc:`../overview/automate_actions`"
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:80
msgid ":doc:`../overview/segment`"
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:81
msgid ":doc:`../overview/test`"
msgstr ""
#: ../../marketing_automation/overview.rst:3
msgid "Overview"
msgstr "Vue d'ensemble"
#: ../../marketing_automation/overview/automate_actions.rst:3
msgid "Automate Actions and Create a Workflow"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:4
msgid ""
"Automated workflows are a sign that you are building intelligent, data-"
"driven, multifaceted campaigns to enable the delivery of the right message, "
"to the right prospects, at the right time. It also speeds up processes and "
"creates a seamless experience for employees."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:9
msgid "Segment and create a campaign"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:10
msgid "Go to :menuselection:`Campaigns --> Create`."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:12
msgid ""
"In the example below, the *Marketing Automation* application is fully "
"integrated with *Contacts*."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:14
msgid ""
"But it can also be integrated with other apps like CRM, as long as they are "
"installed in your database."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:23
msgid ""
"Depending on the criteria, the *target model updates itself* while the "
"campaign is running. That means that every new record that meets the "
"criteria will be added to the workflow."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:25
msgid ""
"Example: a campaign starts for leads that have no salesman assigned. If at "
"some point, those leads get to have a salesman assigned to it, the campaign "
"will stop running."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:29
msgid "Create a parent activity and start to build a workflow"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:30
msgid "Click on *Add new activity*."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:37
msgid ""
"*Trigger* is the field to set for the activity to start to de deployed."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:39
msgid ""
"Adopt an *Expiry Duration* if you would like to stop actions from being "
"executed after a certain amount of time and in subsequence to the trigger."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:42
msgid ""
"Under *Domain* you can narrow down your target, even more, applying filters "
"for this specific activity."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:47
msgid "Add Child Activities"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:48
msgid ""
"A *child activity* is an action that will take place based on a condition."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:50
msgid ""
"You can either create or add a child activity if on the previous one: the "
"email was opened or not, the email was replied or not, the link was clicked "
"or not, the email bounced back."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:59
#: ../../marketing_automation/overview/test.rst:53
msgid ":doc:`segment`"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:3
msgid "Segment the Database with Filters"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:4
msgid "Filters let you reach a granular level of detail in your records."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:7
msgid "How to work with filters"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:8
msgid ""
"When working with filters, you will see that some of the rules have an arrow"
" button next to it, informing you that the parameter has more variables "
"within it."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:18
msgid ""
"More than one parameter line - *node* (+) - can be added under what is "
"called a *branch* (...)."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:19
msgid "To exclude a *node* or a *branch*, click on *Delete node* (x)."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:27
msgid ""
"Every time a new branch is created, you can choose if you would like the "
"records to match *all* criteria of the upcoming rules, or *any*, meaning one"
" rule or the other."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:32
msgid "Use cases"
msgstr "Cas d'utilisation"
#: ../../marketing_automation/overview/segment.rst:34
msgid ""
"**Scenario**: narrow the target down to new opportunities in the pipeline."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:39
msgid "**Scenario**: narrow the target down to suppliers."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:44
msgid ""
"**Scenario**: narrow the leads down to the ones that contain a certain tag "
"name."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:49
msgid ""
"**Scenario**: narrow the target down to the attendees of a specific event "
"that purchase a specific category of ticket."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:55
msgid "**Scenario**: narrow the target down to the employees who have kids."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:60
msgid ""
"**Scenario**: narrow the target down to records with a helpdesk ticket "
"solved."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:66
#: ../../marketing_automation/overview/test.rst:52
msgid ":doc:`automate_actions`"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:67
msgid ":doc:`../../general/tags/take_tags`"
msgstr ""
#: ../../marketing_automation/overview/test.rst:3
msgid "Launch a Test and Start a Campaign"
msgstr ""
#: ../../marketing_automation/overview/test.rst:4
msgid ""
"Before starting a campaign, launching a test allows you to run the workflow "
"on a test contact and view the sequence of events in action, avoiding "
"mistakes."
msgstr ""
#: ../../marketing_automation/overview/test.rst:8
msgid "Launch a test"
msgstr "Lancer un test"
#: ../../marketing_automation/overview/test.rst:9
msgid "Click on *Launch a test*."
msgstr ""
#: ../../marketing_automation/overview/test.rst:12
msgid ""
"Once you have selected the test contact, *Run* the parent activity and the "
"subsequent ones as needed. *Run* and *Stop* activities individually. To stop"
" the whole workflow click on *Stop*."
msgstr ""
#: ../../marketing_automation/overview/test.rst:22
msgid ""
"Launching a test does not add data to your metrics with the purpose of not "
"introducing wrong inputs to reports."
msgstr ""
#: ../../marketing_automation/overview/test.rst:27
msgid "Start and stop a workflow"
msgstr ""
#: ../../marketing_automation/overview/test.rst:28
msgid ""
"Click on *Start* to run the workflow, and on *Stop* to interrupt it. The "
"interruption and new start can happen at any moment. The current status will"
" be shown on the status bar."
msgstr ""
#: ../../marketing_automation/overview/test.rst:38
msgid "Participants and their specific workflow"
msgstr ""
#: ../../marketing_automation/overview/test.rst:39
msgid ""
"*Participants* are all the records that have ever been involved in the "
"campaign."
msgstr ""
#: ../../marketing_automation/overview/test.rst:47
msgid ""
"If you click on *Participants* and open a record, you will find the specific"
" activities the record went/are/will go through, as well as when the "
"workflow was triggered to him. If you wish to cancel an activity click on "
"*Cancel*."
msgstr ""

19
locale/fr/LC_MESSAGES/mobile.po
View File

@ -4,16 +4,17 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Richard Mathot <rim@odoo.com>, 2019
# Richard Mathot <rim@odoo.com>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Last-Translator: Richard Mathot <rim@odoo.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Fernanda Marques <fem@odoo.com>, 2020\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -39,9 +40,9 @@ msgstr ""
#: ../../mobile/firebase.rst:13
msgid ""
"Simply go to *Settings* > *General Settings* > *Odoo Cloud Notification "
"(OCN)* and make sure that **Push Notifications** is checked."
"Simply go to :menuselection:`Settings --> General Settings --> Odoo Cloud "
"Notification (OCN)` and make sure that **Push Notifications** is checked."
msgstr ""
"Rendez vous dans *Configuration* > *Paramètres généraux* > *Odoo Cloud "
"Notification (OCN)* et assurez vous que la case **Push Notifications** est "
"cochée."
"Allez simplement à :menuselection:`Paramètres --> Paramètres généraux --> "
"Odoo Cloud Notification (OCN)` et assurez-vous que les **Notifications "
"push** sont activées."

159
locale/fr/LC_MESSAGES/planning.po Normal file
View File

@ -0,0 +1,159 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
# Alexandra Jubert <aju@odoo.com>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Fernanda Marques <fem@odoo.com>, 2020\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../planning.rst:5
msgid "Planning"
msgstr "Planification"
#: ../../planning/overview.rst:3
msgid "Overview"
msgstr "Vue d'ensemble"
#: ../../planning/overview/duplicate_a_planning.rst:3
msgid "Create a Schedule and Make Encoding Easier"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:5
msgid ""
"Organize regular schedules or forecast projects in a long term basis. Create"
" shifts to manage your tasks, assign employees, and stay organized at a high"
" level."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:9
msgid "Organize your team by roles"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:11
msgid ""
"Go to :menuselection:`Configuration --> Roles --> Create`. Optionally, go to"
" the *Employees* application, select the respective employee, and under "
"*Work Information* select the *Default Planning Role*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:20
msgid "Make shifts recurrent"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:22
msgid ""
"While creating a shift, select *Repeat* and configure as needed, saving you "
"from the need of re-planning it."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:30
msgid ""
"Repeated shifts are generated for the next six months. A modification is "
"possible in :doc:`Developer mode <../../general/developer_mode/activate>`, "
"from *Settings*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:38
msgid "To duplicate a shift in the Gantt view, press CTRL + drag and drop."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:41
msgid "Save shifts as templates"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:43
msgid ""
"If creating a shift on the fly and know you might use that template in the "
"future, click on *Save as a Template*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:51
msgid ""
"To create a template in advance, go to :menuselection:`Configuration --> "
"Shifts Templates --> Create`."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:55
msgid "Duplicate a planning from the previous week"
msgstr "Dupliquez un planning de la semaine précédente"
#: ../../planning/overview/duplicate_a_planning.rst:57
msgid ""
"When in the Gantt view, either under *Schedule by Employee, Role or "
"Project*, instead of re-planning shifts that have been planned before, "
"simply click on *Copy Previous Week*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:65
msgid ""
"The integration with the *Time off* and *Employee* applications, show you "
"grayed cells to the days when the employee does not work and is on vacation "
"time, for example."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:3
msgid "Send Planned Shifts and Give Employees Autonomy Over Shifts"
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:5
msgid ""
"If you are not on top of your tasks and shifts you might fall behind, losing"
" productivity. Allowing your employees to have a say over shifts helps you "
"to be on top of your workload, and gives them flexibility."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:10
msgid "Publish and send the planned week by email"
msgstr "Publiez et envoyez le planning par email"
#: ../../planning/overview/send_planned_shifts.rst:12
msgid ""
"Once you have your shifts planned, click on *Send Schedule*. Select *Include"
" Open shift* if you would like the *Unassigned* shifts to be seen."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:19
msgid ""
"Choose if you just want to *Publish* or *Publish and Send*. If you *Publish "
"and Send*, employees get an email that redirects them to their planned "
"tasks:"
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:26
msgid ""
"Employees will not be able to see shifts until they have been published."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:29
msgid "Let employees unassign themselves from shifts"
msgstr "Laissez vos employés se désassigner eux-mêmes des postes"
#: ../../planning/overview/send_planned_shifts.rst:31
msgid ""
"Go to *Configuration* and enable *Allow Unassignment*. From now on, when an "
"employee opens his tasks, he can indicate his unavailability clicking on *I "
"am unavailable*. The shift will be opened again, allowing someone else to "
"take it."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:44
msgid "Employees have portal access; users have access to the database."
msgstr ""

2072
locale/fr/LC_MESSAGES/point_of_sale.po
View File

File diff suppressed because it is too large Load Diff

28
locale/fr/LC_MESSAGES/portal.po
View File

@ -4,17 +4,17 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Richard Mathot <rim@odoo.com>, 2019
# Martin Trigaux, 2019
# Martin Trigaux, 2020
# Richard Mathot <rim@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Last-Translator: Martin Trigaux, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Richard Mathot <rim@odoo.com>, 2020\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -36,16 +36,12 @@ msgstr ""
"entre vous et Odoo : les documents comme les devis, bons de commande, "
"factures et abonnements."
#: ../../portal/my_odoo_portal.rst:11
#: ../../portal/my_odoo_portal.rst:12
msgid ""
"To access this section, you have to log with your username and password to "
"`Odoo <https://www.odoo.com/my/home>`__ . If you are already logged in, just"
" click on your name on the top-right corner and select \"My Account\"."
"`Odoo <https://www.odoo.com/my/home>`_. If you are already logged in, just "
"click on your name on the top-right corner and select \"My Account\"."
msgstr ""
"Pour accéder à cette section, vous devez vous identifier avec votre nom "
"d'utilisateur et mot de passe `Odoo <https://www.odoo.com/my/home>`__ . Si "
"vous êtes déjà identifié, cliquez simplement sur votre nom en haut à droite "
"et choisissez \"Mon compte\"."
#: ../../portal/my_odoo_portal.rst:20
msgid "Quotations"
@ -148,13 +144,13 @@ msgid ""
" \"Delete\" to delete the payment method."
msgstr ""
#: ../../portal/my_odoo_portal.rst:101
#: ../../portal/my_odoo_portal.rst:102
msgid ""
"At the date of the next invoice, if there is no payment information provided"
" or if your credit card has expired, the status of your subscription will "
"change to \"To Renew\". You will then have 7 days to provide a valid method"
" of payment. After this delay, the subscription will be closed, and you will"
" no longer be able to access the database."
"change to \"To Renew\". You will then have 7 days to provide a valid method "
"of payment. After this delay, the subscription will be closed, and you will "
"no longer be able to access the database."
msgstr ""
#: ../../portal/my_odoo_portal.rst:108

10
locale/fr/LC_MESSAGES/practical.po
View File

@ -4,16 +4,16 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Richard Mathot <rim@odoo.com>, 2019
# Richard Mathot <rim@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: 2019-10-03 09:47+0000\n"
"Last-Translator: Richard Mathot <rim@odoo.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Richard Mathot <rim@odoo.com>, 2020\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"

2236
locale/fr/LC_MESSAGES/project.po
View File

File diff suppressed because it is too large Load Diff

160
locale/fr/LC_MESSAGES/purchase.po
View File

@ -4,19 +4,20 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2019
# Benjamin Frantzen, 2019
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2019
# Oriane Malburny <oma@odoo.com>, 2019
# Martin Trigaux, 2020
# 5cad1b0f1319985f8413d48b70c3c192_b038c35, 2020
# Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2020
# Cécile Collart <cco@odoo.com>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-10-03 09:47+0000\n"
"Last-Translator: Oriane Malburny <oma@odoo.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Fernanda Marques <fem@odoo.com>, 2020\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -92,9 +93,11 @@ msgstr ""
#: ../../purchase/purchases/master/import.rst:33
msgid ""
"`Template download "
"<https://docs.google.com/spreadsheets/d/1N8c_eejLV_8NhYMGCfZau_oGCnRkUIT9nwdX7n0shhY/edit#gid=964193981>`__"
":download:`Click here to download the template "
"<../../../_static/example_files/vendor_pricelists_template.csv>`"
msgstr ""
":download:`Cliquez ici pour télécharger le template "
"<../../../_static/example_files/vendor_pricelists_template.csv>`"
#: ../../purchase/purchases/master/suppliers.rst:3
msgid "Set multiple vendors on a product"
@ -404,7 +407,7 @@ msgstr ""
#: ../../purchase/purchases/rfq/3_way_matching.rst:9
msgid ""
"To define whether the vendor bill should be paid or not, you can use what we"
" call *3-way matching*. It refers to the comparaison of the information "
" call *3-way matching*. It refers to the comparison of the information "
"appearing on the *Purchase Order*, the *Vendor Bill* and the *Receipt*."
msgstr ""
@ -911,108 +914,7 @@ msgstr ""
"commande**, sélectionnez la date à laquelle vous souhaitez passer la "
"commande."
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Receipt"
msgstr "Reçu"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Incoming Shipments"
msgstr "Réceptions"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Vendor"
msgstr "Fournisseur"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "You can find a vendor by its Name, TIN, Email or Internal Reference."
msgstr ""
"Vous pouvez trouver un fournisseur par son nom, numéro de TVA, courriel ou "
"sa référence interne."
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Vendor Reference"
msgstr "Référence fournisseur"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"Reference of the sales order or bid sent by the vendor. It's used to do the "
"matching when you receive the products as this reference is usually written "
"on the delivery order sent by your vendor."
msgstr ""
"Référence du bon de commande ou offre envoyée par le fournisseur. Utilisé "
"principalement pour faire la correspondance lors de la réception des "
"articles, puisque cette référence est généralement écrite sur le bon de "
"livraison envoyé par votre fournisseur."
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Order Date"
msgstr "Date de la commande"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"Depicts the date where the Quotation should be validated and converted into "
"a purchase order."
msgstr ""
"Représente la date où le devis devrait être validé et le converti en bon "
"d'achat."
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Source Document"
msgstr "Document d'origine"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"Reference of the document that generated this purchase order request (e.g. a"
" sales order)"
msgstr ""
"Référence du document qui a généré cette demande de bon de commande (p. ex. "
"un ordre de vente)"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Deliver To"
msgstr "Livrer à"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "This will determine operation type of incoming shipment"
msgstr "Cela déterminera le type d'opération des réceptions"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Drop Ship Address"
msgstr "Adresse de livraison directe"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"Put an address if you want to deliver directly from the vendor to the "
"customer. Otherwise, keep empty to deliver to your own company."
msgstr ""
"Ajoutez une adresse si vous voulez livrer directement du fournisseur au "
"client. Sinon, laissez vide pour vous faire livrer à votre société."
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Destination Location Type"
msgstr "Type d'emplacement de destination"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Technical field used to display the Drop Ship Address"
msgstr "Champ technique utilisé pour afficher l'adresse de livraison directe."
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Incoterm"
msgstr "Incoterm"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"International Commercial Terms are a series of predefined commercial terms "
"used in international transactions."
msgstr ""
"Les Incoterms sont une série de termes commerciaux prédéfinie utilisés dans "
"les transactions internationales."
#: ../../purchase/purchases/rfq/create.rst:32
msgid "View *Request for Quotation* in our Online Demonstration"
msgstr "Voir *Demande de Prix* dans notre Démonstration en Ligne"
#: ../../purchase/purchases/rfq/create.rst:34
#: ../../purchase/purchases/rfq/create.rst:28
msgid ""
"In **Products**, click on Add an item. Select the product you wish to order "
"in the **Product** menu. Specify the **Quantity** by inserting the number "
@ -1030,10 +932,10 @@ msgstr ""
"vous propose (vous pouvez également laisser le champ vide si vous ne savez "
"pas quel est le prix), et ajouter la date de livraison prévue dans le champ "
"Date prévue. Cliquez sur **Sauvegarder**, puis sur **Imprimer Demande de "
"Prix** ou ** Envoyer la Demande de Prix par Courriel** (assurez-vous qu'une "
"Prix** ou ** Envoyer la Demande de Prix par Email** (assurez-vous qu'une "
"adresse email est définie pour ce fournisseur ou entrez-en une nouvelle)."
#: ../../purchase/purchases/rfq/create.rst:48
#: ../../purchase/purchases/rfq/create.rst:40
msgid ""
"After having clicked on **Send**, you will notice that the RFQ's status will"
" switch from **Draft** to **RFQ Sent**."
@ -1041,7 +943,7 @@ msgstr ""
"Après avoir cliqué sur **Envoyer...**, vous constaterez que le statut de la "
"Demande de Prix est passé de **Brouillon** à **Demande de Prix Envoyée**."
#: ../../purchase/purchases/rfq/create.rst:54
#: ../../purchase/purchases/rfq/create.rst:46
msgid ""
"Once your supplier has replied with an offer, update the RfQ by clicking on "
"**Edit** to fit the quotation (prices, taxes, expected delivery lead time, "
@ -1052,7 +954,7 @@ msgstr ""
"l'offre (prix, taxes, délai de livraison prévu, conditions de paiement, "
"etc.), puis cliquez sur **Enregistrer** pour émettre un Bon de Commande."
#: ../../purchase/purchases/rfq/create.rst:59
#: ../../purchase/purchases/rfq/create.rst:51
msgid ""
"To proceed with the order, click on **Confirm Order** to send the order to "
"the supplier. The RfQ's status will switch to **Purchase Order**."
@ -1061,7 +963,7 @@ msgstr ""
"la commande au fournisseur. Le statut de la Demande de Prix passera à "
"**Commande Fournisseur**."
#: ../../purchase/purchases/rfq/create.rst:65
#: ../../purchase/purchases/rfq/create.rst:57
msgid ""
"The status of the RfQ will change to PURCHASE ORDER. Tabs in the upper right"
" corner of the order will show 1 Shipment and 0 Invoice."
@ -1086,6 +988,8 @@ msgid ""
"You need the *Sales*, *Inventory* and *Purchases* modules for this feature "
"to work."
msgstr ""
"Pour que cette fonctionnalité fonctionne vous avez besoin des modules "
"*Ventes*, *Inventaire* et *Achats*."
#: ../../purchase/purchases/rfq/dropshipping.rst:14
msgid "Activate the dropshipping feature"
@ -1180,10 +1084,10 @@ msgid ""
" thing to do is to deploy the Odoo purchase process. Knowing what have been "
"purchased is the basis of forecasting and controlling receptions."
msgstr ""
"Si vous souhaitez obtenir des prévisions et des réceptions de produits sous "
"contrôle, la première chose à faire est de déployer le processus d'achat de "
"Odoo. Savoir ce qui a été acheté est la base des prévisions et du contrôle "
"de réceptions."
"Si vous souhaitez garder les prévisions et les réceptions de produits sous "
"contrôle, la première chose à faire est de déployer le processus d'achat "
"d'Odoo. Savoir ce qui a été acheté est à la base des prévisions et du "
"contrôle des réceptions."
#: ../../purchase/purchases/rfq/reception.rst:17
msgid "Install the Purchase and Inventory applications"
@ -1265,10 +1169,10 @@ msgid ""
msgstr ""
"Depuis l'application Achats, créez un bon de commande avec quelques "
"articles. Si le fournisseur vous envoie une confirmation ou un devis, "
"enregistrez le numéro de commande dans le champ **Référence Fournisseur**. "
"Cela vous permettra de faciliter le rapprochement ultérieur avec le "
"bordereau de livraison (car le bordereau de livraison contiendra "
"probablement la référence fournisseur)"
"enregistrez le numéro de la commande dans le champ **Référence "
"fournisseur**. Cela vous permettra de faire facilement la correspondance "
"avec le bon de livraison par la suite (car le bordereau de livraison "
"comprendra probablement la **Référence du vendeur** de son bon de commande)."
#: ../../purchase/purchases/rfq/reception.rst:67
msgid "Receive Products"
@ -1812,6 +1716,8 @@ msgid ""
"Open a product form and, under the inventory tab, tick the routes *Buy* and "
"*Make To Order*."
msgstr ""
"Ouvrez une fiche produit et cochez les routes *Acheter* et *Passer une "
"commande* dans l'onglet **Inventaire**. "
#: ../../purchase/replenishment/flows/purchase_triggering.rst:20
msgid "Don't forget to also set a vendor under the *Purchase* tab."
@ -1861,7 +1767,7 @@ msgstr ""
#: ../../purchase/replenishment/flows/purchase_triggering.rst:57
msgid ":doc:`../../../purchase/replenishment/flows/setup_stock_rule`"
msgstr ""
msgstr ":doc:`../../../purchase/replenishment/flows/setup_stock_rule`"
#: ../../purchase/replenishment/flows/setup_stock_rule.rst:3
msgid "Don’t run out of stock thanks to Reordering Rules"
@ -1905,6 +1811,8 @@ msgstr ""
#: ../../purchase/replenishment/flows/setup_stock_rule.rst:33
msgid "See also: :doc:`../../../inventory/management/planning/schedulers`"
msgstr ""
"Consultez également: "
":doc:`../../../inventory/management/planning/schedulers`"
#: ../../purchase/replenishment/flows/setup_stock_rule.rst:35
msgid ""

252
locale/fr/LC_MESSAGES/quality.po
View File

@ -4,17 +4,18 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2019
# Cécile Collart <cco@odoo.com>, 2019
# Martin Trigaux, 2020
# Cécile Collart <cco@odoo.com>, 2020
# Fernanda Marques <fem@odoo.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-11-20 09:24+0000\n"
"Last-Translator: Cécile Collart <cco@odoo.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Fernanda Marques <fem@odoo.com>, 2020\n"
"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@ -96,7 +97,7 @@ msgstr ""
#: ../../quality/alert/alert_transfer.rst:6
msgid "Use the Quality Alert"
msgstr ""
msgstr "Utilisez l'alerte qualité"
#: ../../quality/alert/alert_transfer.rst:8
msgid ""
@ -155,13 +156,14 @@ msgstr ""
#: ../../quality/checks/quality_mo.rst:53
#: ../../quality/checks/quality_transfers.rst:6
msgid "Create the Quality Control Point"
msgstr ""
msgstr "Créez le point de contrôle qualité"
#: ../../quality/checks/quality_mo.rst:18
msgid ""
"To create a quality control point, open the quality app and go to *Control >"
" Control Points*. There, hit create. Make sure to select *Manufacturing* as "
"operation and choose the type of quality check you want to perform."
"To create a quality control point, open the quality app and go to "
":menuselection:`Control --> Control Points`. There, hit create. Make sure to"
" select *Manufacturing* as operation and choose the type of quality check "
"you want to perform."
msgstr ""
#: ../../quality/checks/quality_mo.rst:27
@ -192,9 +194,9 @@ msgstr ""
#: ../../quality/checks/quality_mo.rst:55
msgid ""
"If you want to create a *Quality Control Point*, open the *Quality* app and "
"go to *Control > Control Points*. Then, click on create. Make sure to select"
" *Manufacturing* as operation and select the work order operation on which "
"the quality check should be performed."
"go to :menuselection:`Control --> Control Points`. Then, click on create. "
"Make sure to select *Manufacturing* as operation and select the work order "
"operation on which the quality check should be performed."
msgstr ""
#: ../../quality/checks/quality_mo.rst:64
@ -225,9 +227,9 @@ msgstr ""
#: ../../quality/checks/quality_transfers.rst:8
msgid ""
"To create a *Quality Control Point*, open the *Quality* application. Then, "
"go to *Quality Control > Control Points > Create*. Now, you can define the "
"quality control point you want to apply to a specific product. Don’t forget "
"to select a transfer operation type."
"go to :menuselection:`Quality Control --> Control Points --> Create`. Now, "
"you can define the quality control point you want to apply to a specific "
"product. Don’t forget to select a transfer operation type."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:19
@ -268,148 +270,198 @@ msgstr "Contrôle"
#: ../../quality/control/control_points.rst:3
msgid "Define Quality Control Points"
msgstr "Définissez des points de contrôle qualité"
#: ../../quality/control/control_points.rst:5
msgid ""
"Quality is an important factor when it comes to products or services. "
"Nowadays, quality has become the differentiating factor for all goods and "
"services. It is vital for businesses to deliver products that meet or exceed"
" expectations. It also helps minimize waste."
msgstr ""
#: ../../quality/control/control_points.rst:6
#: ../../quality/control/control_points.rst:10
msgid ""
"That is why most manufacturers would not think of eliminating the quality "
"control from their manufacturing process. After all, removing quality "
"controls would dramatically increase the number of defective products that "
"the company then has to rework or scrap."
msgstr ""
#: ../../quality/control/control_points.rst:15
msgid ""
"Then, using business applications to ensure data quality is important. With "
"Odoo insuring the rear, any major problem can be avoided before occurring!"
msgstr ""
#: ../../quality/control/control_points.rst:20
msgid "Quality Control Points"
msgstr "Points de contrôle qualité"
#: ../../quality/control/control_points.rst:8
msgid ""
"If it is the first *Quality Control Point* that you create, know that you "
"need to open the *Quality* app. Then, go to *Quality Control > Control "
"Points*. Once there, you have to define the product on which the quality "
"control will take place, as well as the operation at which it should take "
"place."
msgstr ""
#: ../../quality/control/control_points.rst:14
msgid ""
"The *Quality Control Points* can take place during transfers or during the "
"manufacturing process of the products. If you work with routings on your "
"*Bill of Materials*, you have to precise at which step of the manufacturing "
"process the quality control point should be applied."
msgstr ""
#: ../../quality/control/control_points.rst:19
msgid ""
"The control type defines at which frequency the quality checks should take "
"place:"
msgstr ""
msgstr "Points de contrôle de la qualité"
#: ../../quality/control/control_points.rst:22
msgid ""
"All Operations: all the operations will generate quality checks to perform;"
"To create a *Quality Control Point*, go to :menuselection:`Quality --> "
"Quality Control --> Control Points`. Once there, define the product on which"
" the quality control point should take place. The operation at which it "
"takes place also is to be defined here."
msgstr ""
#: ../../quality/control/control_points.rst:24
#: ../../quality/control/control_points.rst:27
msgid ""
"Randomly: the quality checks will only be performed on x% of the operation. "
"You must define the percentage yourself, on the control point;"
msgstr ""
#: ../../quality/control/control_points.rst:26
msgid ""
"Periodically: the quality checks will be performed periodically. The "
"periodicity is based on the period you define (once a day, once a week)."
"The *Quality Control Points* take place during transfers or during the "
"manufacturing process of the products. If working with routings on *Bill of "
"Materials*, you have to precise at which step of the manufacturing process "
"the quality control point needs to be applied."
msgstr ""
#: ../../quality/control/control_points.rst:32
msgid "Quality Control Point Types"
msgid ""
"The *Control Type* defines at which frequency the quality checks should take"
" place:"
msgstr ""
#: ../../quality/control/control_points.rst:34
#: ../../quality/control/control_points.rst:35
msgid ""
"Now that the rest is configured, you need to define the type of quality "
"check."
"**All operations**: all the operations automatically generate quality checks"
" to perform;"
msgstr ""
#: ../../quality/control/control_points.rst:38
msgid ""
"Some of the types are only available with the manufacturing application."
"**Randomly**: the quality checks only perform on x% of the operation. The "
"percentage needs to be defined on the control point;"
msgstr ""
#: ../../quality/control/control_points.rst:41
msgid "Text"
msgstr "Texte"
#: ../../quality/control/control_points.rst:43
msgid ""
"This control point type allows you to give instructions to your workers "
"during the transfer, or the manufacturing process."
"**Periodically**: the quality checks are performed periodically. The "
"periodicity is based on the defined period (once a day, once a week)."
msgstr ""
#: ../../quality/control/control_points.rst:56
msgid "Take a Picture"
msgstr "Prendre une photo"
#: ../../quality/control/control_points.rst:50
msgid "Quality Control Point Types"
msgstr "Types de point de contrôle de la qualité"
#: ../../quality/control/control_points.rst:52
msgid ""
"Now, one thing remains to be configured: the type of quality check. There "
"are several types that can be used: text, take a picture, pass-fail, take a "
"measure, register consumed material, register by-product, and print label."
msgstr ""
#: ../../quality/control/control_points.rst:58
msgid ""
"This control point type asks you to take a picture of the product in a "
"transfer, or when manufacturing it."
"Some types are available only with the manufacturing application installed."
msgstr ""
#: ../../quality/control/control_points.rst:71
msgid "Pass-Fail"
msgstr ""
#: ../../quality/control/control_points.rst:62
msgid "Text"
msgstr "Texte"
#: ../../quality/control/control_points.rst:73
#: ../../quality/control/control_points.rst:64
msgid ""
"This type of control point requires that you specify if the products pass or"
" fail a specific text. It can be applied for both transfers or manufacturing"
" orders."
"This control point type allows giving instructions to workers during the "
"transfer or during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:80
msgid "Take a Picture"
msgstr "Prendre une photo"
#: ../../quality/control/control_points.rst:82
msgid ""
"For this kind of control point type, you have the possibility to define a "
"failure message that will give instructions to follow in case of quality "
"check failure."
"This control point type asks to take a picture of the product applied in a "
"transfer or when manufacturing it."
msgstr ""
#: ../../quality/control/control_points.rst:94
msgid "Take a Measure"
msgstr ""
#: ../../quality/control/control_points.rst:96
#: ../../quality/control/control_points.rst:98
msgid ""
"This control point type requires you to enter the product’s measurements "
"during a transfer, or during the manufacturing process."
"This process can be simplified by using a connected :doc:`camera "
"<../../iot/devices/measurement_tool>`."
msgstr ""
#: ../../quality/control/control_points.rst:102
msgid ""
"For this kind of control point type, you also have the possibility to define"
" a failure message that will give instructions to the worker."
msgid "Pass-Fail"
msgstr ""
#: ../../quality/control/control_points.rst:115
#: ../../quality/control/control_points.rst:104
msgid ""
"*Pass-Fail* requires to specify if the products pass or fail specific "
"criteria. It can be applied for both transfers or manufacturing orders."
msgstr ""
#: ../../quality/control/control_points.rst:111
msgid ""
"For this kind of type, there is the possibility to define a failure message "
"giving instructions to follow in case of failure."
msgstr ""
#: ../../quality/control/control_points.rst:127
msgid "Take a Measure"
msgstr ""
#: ../../quality/control/control_points.rst:129
msgid ""
"Taking measures requires to enter the product’s measurements during a "
"transfer or during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:132
msgid ""
"To use it, it necessary to specify the norm for your product’s measurements,"
" but also a tolerance threshold. Doing so, all the products with good "
"measures can are automatically accepted."
msgstr ""
#: ../../quality/control/control_points.rst:140
msgid ""
"As for *Pass-Fail*, this type allows defining a failure message that gives "
"instructions to the worker."
msgstr ""
#: ../../quality/control/control_points.rst:156
msgid ""
"This process can be simplified by using connected :doc:`measurement tools "
"<../../iot/devices/camera>`."
msgstr ""
#: ../../quality/control/control_points.rst:159
msgid "Register Consumed Materials"
msgstr ""
#: ../../quality/control/control_points.rst:117
#: ../../quality/control/control_points.rst:161
msgid ""
"This control point type requires you register the component serial/lot "
"numbers during the manufacturing process. It is only available if you work "
"with routings."
"When using *Register Consumed Materials*, it is required to register the "
"component’s serial/lot numbers during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:128
#: ../../quality/control/control_points.rst:165
#: ../../quality/control/control_points.rst:182
msgid "This type is only available when working with routings."
msgstr ""
#: ../../quality/control/control_points.rst:176
msgid "Register By-Products"
msgstr ""
#: ../../quality/control/control_points.rst:130
#: ../../quality/control/control_points.rst:178
msgid ""
"With this control point type, you must register the serial/lot number of the"
" by-products that are manufactured. It is also only available with routings."
"With *Register By-Products*, it is required to register the serial/lot "
"number of the by-products that are manufactured."
msgstr ""
#: ../../quality/control/control_points.rst:141
#: ../../quality/control/control_points.rst:193
msgid "Print Label"
msgstr ""
#: ../../quality/control/control_points.rst:143
#: ../../quality/control/control_points.rst:195
msgid ""
"This control point type allows you to print labels to add to the product "
"during the manufacturing process."
"*Print Label*, as its name points out, allows printing labels to add to the "
"product during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:207
msgid ""
"This process can be simplified by using a connected :doc:`printer "
"<../../iot/devices/printer>`."
msgstr ""

Some files were not shown because too many files have changed in this diff Show More