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

ADD italian

Browse Source
This commit is contained in:
eLBati 2018-05-03 21:29:24 +02:00
parent 2744fd9298
commit ee3fb8cfb7
21 changed files with 34457 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8018
locale/it/LC_MESSAGES/accounting.po Normal file
View File

File diff suppressed because it is too large Load Diff

24
locale/it/LC_MESSAGES/applications.po Normal file
View File

@ -0,0 +1,24 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2018.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-06-07 09:30+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.5.3\n"
#: ../../applications.rst:3
msgid "Applications"
msgstr ""

24
locale/it/LC_MESSAGES/business.po Normal file
View File

@ -0,0 +1,24 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2018.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-10-10 09:08+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.5.3\n"
#: ../../business.rst:3
msgid "Business Mementoes"
msgstr ""

2557
locale/it/LC_MESSAGES/crm.po Normal file
View File

File diff suppressed because it is too large Load Diff

525
locale/it/LC_MESSAGES/db_management.po Normal file
View File

@ -0,0 +1,525 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2018.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-12-13 13:35+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.5.3\n"
#: ../../db_management/db_online.rst:8
msgid "Online Database management"
msgstr ""
#: ../../db_management/db_online.rst:13
msgid "Duplicating a database"
msgstr ""
#: ../../db_management/db_online.rst:15
msgid ""
"Database duplication, renaming, custom DNS, etc. is not available to free"
" customers of our Online platform."
msgstr ""
#: ../../db_management/db_online.rst:18
msgid ""
"Access the `database management page "
"<https://www.odoo.com/my/databases>`__ (you will have to sign in). Next, "
"make sure you are connected as the administrator of the database you want"
" to duplicate. After that, click on the **Manage Your Databases** button."
msgstr ""
#: ../../db_management/db_online.rst:26
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:36
msgid "A duplicated database has the same behaviour as a real one:"
msgstr ""
#: ../../db_management/db_online.rst:38
msgid "Emails are sent"
msgstr ""
#: ../../db_management/db_online.rst:40
msgid "Payments are processed (in the e-commerce, for example)"
msgstr ""
#: ../../db_management/db_online.rst:42
msgid "Delivery orders (shipping providers) are sent"
msgstr ""
#: ../../db_management/db_online.rst:44
msgid "Etc."
msgstr ""
#: ../../db_management/db_online.rst:46
msgid ""
"It is **strongly** advised to test behaviour using sample "
"customers/products (with a `disposable e-mail "
"<http://www.mailinator.com>`__ address, for example)"
msgstr ""
#: ../../db_management/db_online.rst:50
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:54
msgid "Duplicate databases expire automatically after 15 days."
msgstr ""
#: ../../db_management/db_premise.rst:7
msgid "On-premise Database management"
msgstr ""
#: ../../db_management/db_premise.rst:10
msgid "Register a database"
msgstr ""
#: ../../db_management/db_premise.rst:12
msgid ""
"To register your database, you just need to enter your Subscription Code "
"in the banner in the App Switcher. Make sure you do not add extra spaces "
"before or after your subscription code. If the registration is "
"successful, it will turn green and will provide you with the Expiration "
"Date of your freshly-registered database. You can check this Epiration "
"Date in the About menu (Odoo 9) or in the Settings Dashboard (Odoo 10)."
msgstr ""
#: ../../db_management/db_premise.rst:20
msgid "Registration Error Message"
msgstr ""
#: ../../db_management/db_premise.rst:22
msgid ""
"If you are unable to register your database, you will likely encounter "
"this message:"
msgstr ""
#: ../../db_management/db_premise.rst:31 ../../db_management/db_premise.rst:97
#: ../../db_management/db_premise.rst:130
msgid "Solutions"
msgstr ""
#: ../../db_management/db_premise.rst:33
msgid "Do you have a valid Enterprise subscription?"
msgstr ""
#: ../../db_management/db_premise.rst:35
msgid ""
"Check if your subscription details get the tag \"In Progress\" on your "
"`Odoo Account <https://accounts.odoo.com/my/contract>`__ or with your "
"Account Manager"
msgstr ""
#: ../../db_management/db_premise.rst:39
msgid "Have you already linked a database with your subscription reference?"
msgstr ""
#: ../../db_management/db_premise.rst:41
msgid ""
"You can link only one database per subscription. (Need a test or a "
"development database? `Find a partner <https://www.odoo.com/partners>`__)"
msgstr ""
#: ../../db_management/db_premise.rst:45
msgid ""
"You can unlink the old database yourself on your `Odoo Contract "
"<https://accounts.odoo.com/my/contract>`__ with the button \"Unlink "
"database\""
msgstr ""
#: ../../db_management/db_premise.rst:52
msgid ""
"A confirmation message will appear; make sure this is the correct "
"database as it will be deactivated shortly:"
msgstr ""
#: ../../db_management/db_premise.rst:59
msgid "Do you have the updated version of Odoo 9?"
msgstr ""
#: ../../db_management/db_premise.rst:61 ../../db_management/db_premise.rst:190
msgid ""
"From July 2016 onward, Odoo 9 now automatically change the uuid of a "
"duplicated database; a manual operation is no longer required."
msgstr ""
#: ../../db_management/db_premise.rst:64
msgid ""
"If it's not the case, you may have multiple databases sharing the same "
"UUID. Please check on your `Odoo Contract "
"<https://accounts.odoo.com/my/contract>`__, a short message will appear "
"specifying which database is problematic:"
msgstr ""
#: ../../db_management/db_premise.rst:73
msgid ""
"In this case, you need to change the UUID on your test databases to solve"
" this issue. You will find more information about this in :ref:`this "
"section <duplicate_premise>`."
msgstr ""
#: ../../db_management/db_premise.rst:76
msgid ""
"For your information, we identify database with UUID. Therefore, each "
"database should have a distinct UUID to ensure that registration and "
"invoicing proceed effortlessly for your and for us."
msgstr ""
#: ../../db_management/db_premise.rst:82
msgid "Error message due to too many users"
msgstr ""
#: ../../db_management/db_premise.rst:84
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
msgid ""
"When the message appears you have 30 days before the expiration. The "
"countdown is updated everyday."
msgstr ""
#: ../../db_management/db_premise.rst:99
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 ""
#: ../../db_management/db_premise.rst:104
msgid ""
"**Deactivate users** as explained in this `Documentation "
"<https://www.odoo.com "
"/documentation/user/10.0/db_management/documentation.html#deactivating-"
"users>`__ and **Reject** the upsell quotation."
msgstr ""
#: ../../db_management/db_premise.rst:109
msgid ""
"Once your database has the correct number of users, the expiration "
"message will disappear automatically after a few days, when the next "
"verification occurs. We understand that it can be a bit frightening to "
"see the countdown, so you can :ref:`force an Update Notification "
"<force_ping>` to make the message disappear right away."
msgstr ""
#: ../../db_management/db_premise.rst:116
msgid "Database expired error message"
msgstr ""
#: ../../db_management/db_premise.rst:118
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
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
msgid ""
"Renew your subscription: follow the link and renew your subscription - "
"note that"
msgstr ""
#: ../../db_management/db_premise.rst:133
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
msgid "Contact our `Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:138
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
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
msgid ""
"When you duplicate a local database, it is **strongly** advised to change"
" the duplicated database's uuid (Unniversally Unique Identifier), since "
"this uuid is how your database identifies itself with our servers. Having"
" two databases with the same uuid could result in invoicing problems or "
"registration problems down the line."
msgstr ""
#: ../../db_management/db_premise.rst:193
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."
msgstr ""
#: ../../db_management/documentation.rst:7
msgid "Users and Features"
msgstr ""
#: ../../db_management/documentation.rst:9
msgid ""
"As the administrator of your database, you are responsible for its usage."
" This includes the Apps you install as well as the number of users "
"currently in use."
msgstr ""
#: ../../db_management/documentation.rst:13
msgid ""
"Odoo is many things (ERP, CMS, CRM application, e-Commerce backend, etc.)"
" but it is *not* a smartphone. You should apply caution when "
"adding/removing features (especially Apps) on your database since this "
"may impact your subscription amount significantly (or switch you from a "
"free account to a paying one on our online platform)."
msgstr ""
#: ../../db_management/documentation.rst:19
msgid ""
"This page contains some information as to how you can manage your Odoo "
"instances. Before carrying any of these procedures, we **strongly** "
"advise to test them on a duplicate of your database first. That way, if "
"something goes wrong, your day-to-day business is not impacted."
msgstr ""
#: ../../db_management/documentation.rst:24
msgid ""
"You can find guides on how to duplicate your databases both for "
":ref:`online <duplicate_online>` and :ref:`on premise "
"<duplicate_premise>` installations."
msgstr ""
#: ../../db_management/documentation.rst:28
msgid ""
"If you have questions about the content of this page or if you encounter "
"an issue while carrying out these procedures, please contact us through "
"our `support form <https://www.odoo.com/help>`__."
msgstr ""
#: ../../db_management/documentation.rst:34
msgid "Deactivating Users"
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 ""
#: ../../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.**"
msgstr ""
#: ../../db_management/documentation.rst:44
#: ../../db_management/documentation.rst:82
msgid "|settings|"
msgstr ""
#: ../../db_management/documentation.rst:44
msgid "|browse_users|"
msgstr ""
#: ../../db_management/documentation.rst:47
msgid "You'll then see the list of your users."
msgstr ""
#: ../../db_management/documentation.rst:52
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
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."
msgstr ""
#: ../../db_management/documentation.rst:66
msgid "The user is now deactivated."
msgstr ""
#: ../../db_management/documentation.rst:68
msgid "**Never** deactivate the main user (*admin*)"
msgstr ""
#: ../../db_management/documentation.rst:71
msgid "Uninstalling Apps"
msgstr ""
#: ../../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
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
msgid "|browse_apps|"
msgstr ""
#: ../../db_management/documentation.rst:85
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
msgid ""
"Some applications have dependencies, like Invoicing, eCommerce, etc. "
"Therefore, the system will give you a warning message to advise you of "
"what is about to be removed. If you uninstall your application, all its "
"dependencies will be uninstalled as well (and the data in them will "
"permanently disappear). If you are sure you still want to uninstall it, "
"then click **Confirm**."
msgstr ""
#: ../../db_management/documentation.rst:99
msgid ""
"Last, after having checked the warning message (if any), click "
"**Confirm**."
msgstr ""
#: ../../db_management/documentation.rst:104
msgid "You have finished uninstalling your application."
msgstr ""
#: ../../db_management/documentation.rst:107
msgid "Good to know"
msgstr ""
#: ../../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 "
"uninstall applications for you, we would never be able to tell if "
"relevant data had been removed or if one of your business flow was broken"
" because we *do not know how you work* and therefore cannot validate "
"these kinds of operations."
msgstr ""
#: ../../db_management/documentation.rst:115
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 "
"might need. For example, the Website Builder app is needed to be able to "
"show your customer their Quotes in a web page. Even though you might not "
"need or use the Website itself, it is needed for the Online Quotes "
"feature to work properly."
msgstr ""
#: ../../db_management/documentation.rst:122
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 ""

573
locale/it/LC_MESSAGES/discuss.po Normal file
View File

@ -0,0 +1,573 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2018.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-10-10 09:08+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.5.3\n"
#: ../../discuss.rst:5
msgid "Discuss"
msgstr ""
#: ../../discuss/email_servers.rst:3
msgid "How to use my own email servers to send and receive email in Odoo"
msgstr ""
#: ../../discuss/email_servers.rst:6
msgid "When is it needed"
msgstr ""
#: ../../discuss/email_servers.rst:7
msgid ""
"Using your own email servers is required to send and receive messages in "
"Odoo Community or Enterprise. Odoo Online embeds an out-of-box email "
"solution that works straight away. However you can still use your own "
"email servers with the online edition. Some insights are provided here "
"below."
msgstr ""
#: ../../discuss/email_servers.rst:14
msgid "How to set it up"
msgstr ""
#: ../../discuss/email_servers.rst:15
msgid ""
"As a system admin, go to :menuselection:`Settings --> General Settings` "
"and check *External Email Servers* (watch out: this checkbox only shows "
"up after Odoo 10). Then, go through the following steps."
msgstr ""
#: ../../discuss/email_servers.rst:21
msgid ""
"Office 365 email servers don't allow to send external emails from hosts "
"like Odoo. Consequently you can only use such email servers for incoming "
"messages."
msgstr ""
#: ../../discuss/email_servers.rst:26
msgid "Set an outgoing email server for outbound messages"
msgstr ""
#: ../../discuss/email_servers.rst:27
msgid ""
"You need the SMTP data of your email provider (Gmail, Outlook, Yahoo, "
"AOL, etc.) as well as your admin credentials. Once all the information "
"has been filled out, click on *Test Connection*."
msgstr ""
#: ../../discuss/email_servers.rst:35
msgid "Set an incoming email server for inbound messages"
msgstr ""
#: ../../discuss/email_servers.rst:36
msgid ""
"Fill out the form according to your email provider’s settings. Leave the "
"*Actions to Perform on Incoming Mails* blank. Once all the information "
"has been filled out, click on *TEST & CONFIRM*."
msgstr ""
#: ../../discuss/email_servers.rst:43
msgid ""
"By default inbound messages are fetched every 5 minutes. You can change "
"this value in developer mode. Go to :menuselection:`Settings --> "
"Technical --> Automation --> Scheduled Actions` and look for *Mail: "
"Fetchmail Service*."
msgstr ""
#: ../../discuss/email_servers.rst:49
msgid "Set the domain name"
msgstr ""
#: ../../discuss/email_servers.rst:50
msgid ""
"Enter the domain name of your email servers (e.g. mycompany.com) in "
"General Settings."
msgstr ""
#: ../../discuss/email_servers.rst:57
msgid "Create a catchall address"
msgstr ""
#: ../../discuss/email_servers.rst:58
msgid ""
"When a contact replies to an email sent from Odoo, the *reply-to* address"
" is a generic address used to route the reply to the right discussion "
"thread in Odoo (opportunity, order, task, etc.) and to the inbox of all "
"its followers. By default this address is \"catchall@\" but it can be "
"changed."
msgstr ""
#: ../../discuss/email_servers.rst:63
msgid ""
"Create a catchall address in your email server settings. We advise you to"
" use \"catchall@\" so that everything works out straight away. If you "
"want to use another alias, you have extra steps in Odoo:"
msgstr ""
#: ../../discuss/email_servers.rst:67
msgid "Activate the developer mode from your Settings Dashboard."
msgstr ""
#: ../../discuss/email_servers.rst:72
msgid ""
"Refresh your screen. Then go to :menuselection:`Settings --> Technical "
"--> Parameters --> System Parameters` and enter your custom catchall "
"alias in *mail.catchall.alias*."
msgstr ""
#: ../../discuss/email_servers.rst:79
msgid "You can edit the email alias used for bounced messages the same way."
msgstr ""
#: ../../discuss/email_servers.rst:82
msgid "How to use my own email servers with Odoo Online"
msgstr ""
#: ../../discuss/email_servers.rst:83
msgid ""
"Odoo Online comes up with an embedded and ready-to-use email solution "
"with *@yourcompany.odoo.com* as domain. We recommend to keep this default"
" setup as it is really convenient."
msgstr ""
#: ../../discuss/email_servers.rst:87
msgid ""
"Nevertheless you can still use your own email servers if you want to "
"manage your email server's reputation (blacklisting, etc). The "
"configuration for both incoming and outgoing mail servers is given here "
"above."
msgstr ""
#: ../../discuss/email_servers.rst:92
msgid ""
"However when it comes to incoming messages, we don't recommend to "
"exclusively use your own email server. Indeed, Odoo Online is fetching "
"incoming messages from the email server once every hour only. To receive "
"emails in real time, you should rather use a **catchall redirection** "
"(your server -> Odoo server). To do so:"
msgstr ""
#: ../../discuss/email_servers.rst:98
msgid "Create a catchall address in your email server settings (e.g. catchall)."
msgstr ""
#: ../../discuss/email_servers.rst:99
msgid ""
"Still from such settings, set a redirection from this catchall address to"
" Odoo's one: catchall@yourdomain.ext -> catchall@yourcompany.odoo.com."
msgstr ""
#: ../../discuss/email_servers.rst:102
msgid ""
"In Odoo check *External Email Servers* in :menuselection:`Settings --> "
"General Settings` and enter your email domain name (i.e. yourdomain.ext)."
msgstr ""
#: ../../discuss/email_servers.rst:104
msgid "No need to set up an incoming email server in such a case."
msgstr ""
#: ../../discuss/email_servers.rst:108
msgid "How to be SPF-compliant when using external email servers in Odoo"
msgstr ""
#: ../../discuss/email_servers.rst:109
msgid ""
"Sender Policy Framework (SPF) is an email-validation system that checks "
"that incoming mail from a domain comes from a host authorized by that "
"domain's administrator. Such a security system is used in most email "
"servers. If you don't comply with it, your emails sent from Odoo will be "
"likely flagged as spam."
msgstr ""
#: ../../discuss/email_servers.rst:115
msgid ""
"To be SPF-compliant, you need to authorize Odoo as a sending host in your"
" domain name settings:"
msgstr ""
#: ../../discuss/email_servers.rst:118
msgid "Sign in to your domain’s account at your domain host."
msgstr ""
#: ../../discuss/email_servers.rst:119
msgid "Locate the page for updating your domain’s DNS records."
msgstr ""
#: ../../discuss/email_servers.rst:120
msgid ""
"If no TXT record is set, create one with following definition: v=spf1 "
"include:_spf.odoo.com ~all"
msgstr ""
#: ../../discuss/email_servers.rst:122
msgid "In case a TXT record is already set, add \"include:_spf.odoo.com\"."
msgstr ""
#: ../../discuss/email_servers.rst:124
msgid "e.g. for a Gmail server it should be:"
msgstr ""
#: ../../discuss/email_servers.rst:126
msgid "v=spf1 include:_spf.odoo.com include:_spf.google.com ~all"
msgstr ""
#: ../../discuss/email_servers.rst:128
msgid ""
"Find `here <https://www.mail-tester.com/spf/>`__ the exact procedure to "
"create or modify TXT records in your own domain registrar."
msgstr ""
#: ../../discuss/email_servers.rst:131
msgid ""
"Your new SPF record can take up to 48 hours to go into effect, but this "
"usually happens more quickly."
msgstr ""
#: ../../discuss/email_servers.rst:134
msgid ""
"Adding more than one SPF record for a domain can cause problems with mail"
" delivery and spam classification. Instead, we recommend using only one "
"SPF record by modifying it to authorize Odoo."
msgstr ""
#: ../../discuss/email_servers.rst:139
msgid "How to choose between Odoo and my traditional email box"
msgstr ""
#: ../../discuss/email_servers.rst:140
msgid ""
"Odoo Discuss is a perfect tool to send and read messages related to "
"business documents. However it doesn't aim to replace a full-featured "
"email solution (Gmail, Outlook, Yahoo, AOL, etc.). We recommend to take "
"the most out of both systems without mingling them: What is related to "
"Odoo business objects or applications goes into Odoo; What is not can be "
"managed into your external email box."
msgstr ""
#: ../../discuss/email_servers.rst:147
msgid ""
"To do so, create specific email aliases to use in Odoo (to generate leads"
" or opportunities, helpdesk tickets, etc.). If you take an email alias "
"already used for messaging outside of Odoo, incoming messages will land "
"into both systems. This will negatively impact your productivity."
msgstr ""
#: ../../discuss/mail_twitter.rst:3
msgid "How to follow Twitter feed from Odoo"
msgstr ""
#: ../../discuss/mail_twitter.rst:8
msgid ""
"You can follow specific hashtags on Twitter and see the tweets within the"
" Odoo Discuss channels of your choice. The tweets are retrieved "
"periodically from Twitter. An authenticated user can retweet the "
"messages."
msgstr ""
#: ../../discuss/mail_twitter.rst:13
msgid "Setting up the App on Twitter's side"
msgstr ""
#: ../../discuss/mail_twitter.rst:15
msgid ""
"Twitter uses an \"App\" on its side which is opens a gate to which Odoo "
"asks for tweets, and through which a user can retweet. To set up this "
"app, go to http://apps.twitter.com/app/new and put in the values:"
msgstr ""
#: ../../discuss/mail_twitter.rst:19
msgid "Name: this is the name of the application on Twitter"
msgstr ""
#: ../../discuss/mail_twitter.rst:21
msgid ""
"Website: this is the external url of your Odoo database, with \"/web\" "
"added. For example, if your Odoo instance is hosted at "
"\"http://www.example.com\", you should put \"http://www.example.com/web\""
" in this field."
msgstr ""
#: ../../discuss/mail_twitter.rst:25
msgid ""
"Callback URL: this is the address on which Twitter will respond. "
"Following the previous example you should write "
"\"http://www.example.com/web/twitter/callback\"."
msgstr ""
#: ../../discuss/mail_twitter.rst:28
msgid ""
"Do not forget to accept the terms **Developer agreement** of use and "
"click on **Create your Twitter application** at the bottom of the page."
msgstr ""
#: ../../discuss/mail_twitter.rst:33
msgid "Getting the API key and secret"
msgstr ""
#: ../../discuss/mail_twitter.rst:35
msgid "When on the App dashboard, switch to the **Keys and Access Tokens** tab."
msgstr ""
#: ../../discuss/mail_twitter.rst:40
msgid ""
"And copy those values in Odoo in :menuselection:`Settings--> General "
"Settings--> Twitter discuss integration` and click on **Save** to save "
"the settings."
msgstr ""
#: ../../discuss/mentions.rst:3
msgid "How to grab attention of other users in my messages"
msgstr ""
#: ../../discuss/mentions.rst:5
msgid ""
"You can **mention** a user in a channel or chatter by typing **@user-"
"name**. Mentioning a user in the chatter will set them as a follower of "
"the item (if they are not already) and send a message to their inbox. The"
" item containing the mention will also be bolded in the list view. "
"Mentioning a user in a channel will send a message to their inbox. You "
"cannot mention a user in a channel who is not subscribed to the channel. "
"Typing **#channel-name** will provide a link to the mentioned channel in "
"either a chatter or another channel."
msgstr ""
#: ../../discuss/mentions.rst:15
msgid "Direct messaging a user"
msgstr ""
#: ../../discuss/mentions.rst:17
msgid ""
"**Direct messages** are private messages viewable only by the sender and "
"recipient. You can send direct messages to other users from within the "
"Discuss module by creating a new conversation or selecting an existing "
"one from the sidebar. Direct messages can be sent from anywhere in Odoo "
"using the speech bubble icon in the top bar. The online status of other "
"users is displayed to the left of their name. A **green dot** indicates "
"that a user is Online, an **orange dot** that they are Idle, and a **grey"
" dot** that they are offline."
msgstr ""
#: ../../discuss/mentions.rst:28
msgid "Desktop notifications from Discuss"
msgstr ""
#: ../../discuss/mentions.rst:30
msgid ""
"You can choose to see **desktop notifications** when you receive a new "
"direct message. The notification shows you the sender and a brief preview"
" of the message contents. These can be configured or disabled by clicking"
" on the gear icon in the corner of the notification.."
msgstr ""
#: ../../discuss/monitoring.rst:3
msgid "How to be responsive at work thanks to my Odoo inbox"
msgstr ""
#: ../../discuss/monitoring.rst:5
msgid ""
"Use the **Inbox** in Discuss app to monitor updates and progress on "
"everything you do in Odoo. Notifications and messages from everything you"
" follow or in which you are mentioned appear in your inbox."
msgstr ""
#: ../../discuss/monitoring.rst:13
msgid "You can keep an eye on your **Inbox** from any screen."
msgstr ""
#: ../../discuss/monitoring.rst:18
msgid ""
"Marking an item with a check marks the message as **read** and removes it"
" from your inbox. If you would like to save an item for future reference "
"or action, mark it with a star to add it to the **Starred** box. You can "
"star any message or notification in Discuss or any of the item-specific "
"chatters throughout Odoo to keep tabs on it here."
msgstr ""
#: ../../discuss/overview.rst:3
msgid "Why to use Odoo Discuss"
msgstr ""
#: ../../discuss/overview.rst:5
msgid ""
"Odoo Discuss is an easy to use messaging app for teams that brings all "
"your organization's communication into one place and seamlessly "
"integrates with the Odoo platform. Discuss lets you send and receive "
"messages from wherever you are in Odoo as well as manage your messages "
"and notifications easily from within the app. Discuss allows you to "
"create **channels** for team chats, conversations about projects, meeting"
" coordination, and more in one simple and searchable interface."
msgstr ""
#: ../../discuss/team_communication.rst:3
msgid "How to efficiently communicate in team using channels"
msgstr ""
#: ../../discuss/team_communication.rst:5
msgid ""
"You can use **channels** to organize discussions between individual "
"teams, departments, projects, or any other group that requires regular "
"communication. By having conversations that everyone in the channel can "
"see, it's easy to keep the whole team in the loop with the latest "
"developments."
msgstr ""
#: ../../discuss/team_communication.rst:12
msgid "Creating a channel"
msgstr ""
#: ../../discuss/team_communication.rst:14
msgid "In Discuss there are two types of channels - **public** and **private**."
msgstr ""
#: ../../discuss/team_communication.rst:17
msgid ""
"A **public channel** can only be created by an administrator with write "
"privileges and can be seen by everyone in the organization. By contrast, "
"a **private channel** can be created by any user and by default is only "
"visible to users who have been invited to this channel."
msgstr ""
#: ../../discuss/team_communication.rst:24
msgid ""
"A public channel is best used when many employees need to access "
"information (such as interdepartmental communication or company "
"announcements), whereas a private channel should be used whenever "
"information should be limited to specific users/employees (such as "
"department specific or sensitive information)."
msgstr ""
#: ../../discuss/team_communication.rst:31
msgid "Configuring a channel"
msgstr ""
#: ../../discuss/team_communication.rst:33
msgid ""
"You can configure a channel's name, description, access rights, automatic"
" subscription, and emailing from :menuselection:`#channel-name --> "
"Settings`. Changing channel access rights allows you to control which "
"groups can view each channel. You can make a channel visible by all "
"users, invited users, or users within a selected user group. Note that "
"allowing \"Everyone\" to follow a private channel will let other users "
"view and join it as they would a public channel."
msgstr ""
#: ../../discuss/team_communication.rst:47
msgid "How to set up a mailing list"
msgstr ""
#: ../../discuss/team_communication.rst:49
msgid ""
"A channel can be configured to behave as a mailing list. From within "
":menuselection:`#channel-name --> Settings`, define the email you would "
"like to use. Users can then post to the channel and choose to receive "
"notifications using the defined email address. An envelope icon will "
"appear next to the channel name in the list to indicate that a channel "
"will send messages by email."
msgstr ""
#: ../../discuss/team_communication.rst:57
msgid "Locating a channel"
msgstr ""
#: ../../discuss/team_communication.rst:59
msgid ""
"If you do not see a channel on your dashboard, you can search the list of"
" **public channels** to locate the correct channel or create a new "
"channel by clicking the plus icon."
msgstr ""
#: ../../discuss/team_communication.rst:66
msgid ""
"You can also click the **CHANNELS** heading to browse a list of all "
"public channels. This allows the user to manually **join** and **leave** "
"public channels from a single screen."
msgstr ""
#: ../../discuss/team_communication.rst:71
msgid ""
"It is always wise to search for a channel before creating a new one to "
"ensure that duplicate entries are not created for the same topic."
msgstr ""
#: ../../discuss/team_communication.rst:76
msgid "Using filters to navigate within Discuss"
msgstr ""
#: ../../discuss/team_communication.rst:78
msgid ""
"The topbar search provides access to the same comprehensive search "
"function present in the rest of Odoo. You can apply multiple **filter "
"criteria** and **save filters** for later use. The search function "
"accepts wildcards by using the underscore character \"\\ **\\_**\\ \" to "
"represent a **single character wildcard.**"
msgstr ""
#: ../../discuss/tracking.rst:3
msgid "How to follow a discussion thread and define what I want to hear about"
msgstr ""
#: ../../discuss/tracking.rst:6
msgid "How to follow a discussion thread"
msgstr ""
#: ../../discuss/tracking.rst:7
msgid ""
"You can keep track of virtually any business object in Odoo (an "
"opportunity, a quotation, a task, etc.), by **following** it."
msgstr ""
#: ../../discuss/tracking.rst:14
msgid "How to choose the events to follow"
msgstr ""
#: ../../discuss/tracking.rst:15
msgid ""
"You can choose which types of events you want to be notified about. The "
"example below shows the options available when following a **task** in "
"the **Project** app."
msgstr ""
#: ../../discuss/tracking.rst:23
msgid "How to add other followers"
msgstr ""
#: ../../discuss/tracking.rst:24
msgid ""
"You can invite other users and add channels as followers. Adding a "
"channel as a follower will send messages posted in the chatter to the "
"channel with a link back to the original document."
msgstr ""
#: ../../discuss/tracking.rst:34
msgid "How to be a default follower"
msgstr ""
#: ../../discuss/tracking.rst:35
msgid ""
"You are automatically set as a default follower of any item you create. "
"In some applications like CRM and Project, you can be a default follower "
"of any new record created to get notified of specific events (e.g. a new "
"task created, an opportunity won)."
msgstr ""
#: ../../discuss/tracking.rst:40
msgid ""
"To do so, start following the parent business object (e.g. the sales "
"channel in CRM, the project in Project). Then, choose the events you want"
" to hear about."
msgstr ""

1360
locale/it/LC_MESSAGES/ecommerce.po Normal file
View File

File diff suppressed because it is too large Load Diff

347
locale/it/LC_MESSAGES/expense.po Normal file
View File

@ -0,0 +1,347 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2018.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-06-07 09:30+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.5.3\n"
#: ../../expense.rst:5 ../../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 *Tax Included in Price* (see: "
":doc:`../accounting/others/taxes/tax_included`). 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 between brackets (e.g. [Food]). Type the "
"expense amount in the mail subject to set it on the expense too."
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 reinvoice 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 "Install *Sales* app if not yet done."
msgstr ""
#: ../../expense/expense.rst:172
msgid ""
"Go to :menuselection:`Accounting --> Configuration --> Settings` and "
"install Analytic Accounting* (in Recommended Features)."
msgstr ""
#: ../../expense/expense.rst:175
msgid ""
"Go to :menuselection:`Sales --> Sales --> Products` and set the invoicing"
" method on all your Expense types:"
msgstr ""
#: ../../expense/expense.rst:178
msgid "At cost: will invoice expenses at their real cost."
msgstr ""
#: ../../expense/expense.rst:179
msgid ""
"At sales price: will invoice based on a fixed sales price defined in the "
"product form."
msgstr ""
#: ../../expense/expense.rst:186
msgid "Create an order"
msgstr ""
#: ../../expense/expense.rst:187
msgid ""
"As a salesman, create and confirm a Sales Order for the services "
"delivered to your customer. Don’t put any expense in the order. They will"
" be added automatically once posted by the accountant."
msgstr ""
#: ../../expense/expense.rst:191
msgid ""
"Link this order to an analytic account dedicated to the customer project."
" You can create it on the fly."
msgstr ""
#: ../../expense/expense.rst:198
msgid ""
"If you track *Timesheets* on customer projects, Odoo can create an "
"analytic account automatically once the order confirmed. It's useful if "
"your employees must record timesheets on customer-specific projects. To "
"do so, open your order product (service item) and make sure *Track "
"Service* is set on *Timesheets on project*."
msgstr ""
#: ../../expense/expense.rst:205
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:217
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 ""

24
locale/it/LC_MESSAGES/expenses.po Normal file
View File

@ -0,0 +1,24 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2018.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-11-22 13:16+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.5.3\n"
#: ../../expenses.rst:5
msgid "Expenses"
msgstr ""

833
locale/it/LC_MESSAGES/general.po Normal file
View File

@ -0,0 +1,833 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2018.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-10-10 09:08+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.5.3\n"
#: ../../general.rst:5
msgid "General"
msgstr ""
#: ../../general/auth.rst:3
msgid "Authentication"
msgstr ""
#: ../../general/auth/google.rst:3
msgid "How to allow users to sign in with their Google account"
msgstr ""
#: ../../general/auth/google.rst:5
msgid ""
"Connect to your Google account and go to "
"`https://console.developers.google.com/ "
"<https://console.developers.google.com/>`_."
msgstr ""
#: ../../general/auth/google.rst:7
msgid "Click on **Create Project** and enter the project name and other details."
msgstr ""
#: ../../general/auth/google.rst:15
msgid "Click on **Use Google APIs**"
msgstr ""
#: ../../general/auth/google.rst:20
msgid ""
"On the left side menu, select the sub menu **Credentials** (from **API "
"Manager**) then select **OAuth consent screen**."
msgstr ""
#: ../../general/auth/google.rst:25
msgid ""
"Fill in your address, email and the product name (for example odoo) and "
"then save."
msgstr ""
#: ../../general/auth/google.rst:30
msgid ""
"Then click on **Add Credentials** and select the second option (OAuth 2.0"
" Client ID)."
msgstr ""
#: ../../general/auth/google.rst:38
msgid ""
"Check that the application type is set on **Web Application**. Now "
"configure the allowed pages on which you will be redirected."
msgstr ""
#: ../../general/auth/google.rst:40
msgid ""
"To achieve this, complete the field **Authorized redirect URIs**. Copy "
"paste the following link in the box: "
"http://mydomain.odoo.com/auth_oauth/signin. Then click on **Create**"
msgstr ""
#: ../../general/auth/google.rst:48
msgid ""
"Once done, you receive two information (your Client ID and Client "
"Secret). You have to insert your Client ID in the **General Settings**."
msgstr ""
#: ../../general/base_import.rst:3
msgid "Data Import"
msgstr ""
#: ../../general/base_import/adapt_template.rst:3
msgid "How to adapt an import template"
msgstr ""
#: ../../general/base_import/adapt_template.rst:5
msgid ""
"Import templates are provided in the import tool of the most common data "
"to import (contacts, products, bank statements, etc.). You can open them "
"with any spreadsheets software (Microsoft Office, OpenOffice, Google "
"Drive, etc.)."
msgstr ""
#: ../../general/base_import/adapt_template.rst:11
msgid "How to customize the file"
msgstr ""
#: ../../general/base_import/adapt_template.rst:13
msgid ""
"Remove columns you don't need. We advise to not remove the *ID* one (see "
"why here below)."
msgstr ""
#: ../../general/base_import/adapt_template.rst:15
#: ../../general/base_import/import_faq.rst:26
msgid "Set a unique ID to every single record by dragging down the ID sequencing."
msgstr ""
#: ../../general/base_import/adapt_template.rst:20
msgid ""
"When you add a new column, Odoo might not be able to map it automatically"
" if its label doesn't fit any field of the system. If so, find the "
"corresponding field using the search."
msgstr ""
#: ../../general/base_import/adapt_template.rst:27
msgid ""
"Then, use the label you found in your import template in order to make it"
" work straight away the very next time you try to import."
msgstr ""
#: ../../general/base_import/adapt_template.rst:31
msgid "Why an “ID” column"
msgstr ""
#: ../../general/base_import/adapt_template.rst:33
msgid ""
"The **ID** (External ID) is an unique identifier for the line item. Feel "
"free to use the one of your previous software to ease the transition to "
"Odoo."
msgstr ""
#: ../../general/base_import/adapt_template.rst:36
msgid "Setting an ID is not mandatory when importing but it helps in many cases:"
msgstr ""
#: ../../general/base_import/adapt_template.rst:38
msgid ""
"Update imports: you can import the same file several times without "
"creating duplicates;"
msgstr ""
#: ../../general/base_import/adapt_template.rst:39
msgid "Import relation fields (see here below)."
msgstr ""
#: ../../general/base_import/adapt_template.rst:42
msgid "How to import relation fields"
msgstr ""
#: ../../general/base_import/adapt_template.rst:44
msgid ""
"An Odoo object is always related to many other objects (e.g. a product is"
" linked to product categories, attributes, vendors, etc.). To import "
"those relations you need to import the records of the related object "
"first from their own list menu."
msgstr ""
#: ../../general/base_import/adapt_template.rst:48
msgid ""
"You can do it using either the name of the related record or its ID. The "
"ID is expected when two records have the same name. In such a case add \""
" / ID\" at the end of the column title (e.g. for product attributes: "
"Product Attributes / Attribute / ID)."
msgstr ""
#: ../../general/base_import/import_faq.rst:3
msgid "How to import data into Odoo"
msgstr ""
#: ../../general/base_import/import_faq.rst:6
msgid "How to start"
msgstr ""
#: ../../general/base_import/import_faq.rst:7
msgid ""
"You can import data on any Odoo's business object using either Excel "
"(.xlsx) or CSV (.csv) formats: contacts, products, bank statements, "
"journal entries and even orders!"
msgstr ""
#: ../../general/base_import/import_faq.rst:11
msgid "Open the view of the object you want to populate and click *Import*."
msgstr ""
#: ../../general/base_import/import_faq.rst:16
msgid ""
"There you are provided with templates you can easily populate with your "
"own data. Such templates can be imported in one click; The data mapping "
"is already done."
msgstr ""
#: ../../general/base_import/import_faq.rst:22
msgid "How to adapt the template"
msgstr ""
#: ../../general/base_import/import_faq.rst:24
msgid "Add, remove and sort columns to fit at best your data structure."
msgstr ""
#: ../../general/base_import/import_faq.rst:25
msgid "We advise to not remove the **ID** one (see why in the next section)."
msgstr ""
#: ../../general/base_import/import_faq.rst:31
msgid ""
"When you add a new column, Odoo might not be able to map it automatically"
" if its label doesn't fit any field in Odoo. Don't worry! You can map new"
" columns manually when you test the import. Search the list for the "
"corresponding field."
msgstr ""
#: ../../general/base_import/import_faq.rst:39
msgid ""
"Then, use this field's label in your file in order to make it work "
"straight on the very next time."
msgstr ""
#: ../../general/base_import/import_faq.rst:44
msgid "How to import from another application"
msgstr ""
#: ../../general/base_import/import_faq.rst:46
msgid ""
"In order to re-create relationships between different records, you should"
" use the unique identifier from the original application and map it to "
"the **ID** (External ID) column in Odoo. When you import another record "
"that links to the first one, use **XXX/ID** (XXX/External ID) to the "
"original unique identifier. You can also find this record using its name "
"but you will be stuck if at least 2 records have the same name."
msgstr ""
#: ../../general/base_import/import_faq.rst:54
msgid ""
"The **ID** will also be used to update the original import if you need to"
" re-import modified data later, it's thus good practice to specify it "
"whenever possible."
msgstr ""
#: ../../general/base_import/import_faq.rst:60
msgid "I cannot find the field I want to map my column to"
msgstr ""
#: ../../general/base_import/import_faq.rst:62
msgid ""
"Odoo tries to find with some heuristic, based on the first ten lines of "
"the files, the type of field for each column inside your file. For "
"example if you have a column only containing numbers, only the fields "
"that are of type *Integer* will be displayed for you to choose from. "
"While this behavior might be good and easy for most cases, it is also "
"possible that it goes wrong or that you want to map your column to a "
"field that is not proposed by default."
msgstr ""
#: ../../general/base_import/import_faq.rst:71
msgid ""
"If that happens, you just have to check the ** Show fields of relation "
"fields (advanced)** option, you will then be able to choose from the "
"complete list of fields for each column."
msgstr ""
#: ../../general/base_import/import_faq.rst:79
msgid "Where can I change the date import format?"
msgstr ""
#: ../../general/base_import/import_faq.rst:81
msgid ""
"Odoo can automatically detect if a column is a date and it will try to "
"guess the date format from a set of most used date format. While this "
"process can work for a lot of simple date format, some exotic date format"
" will not be recognize and it is also possible to have some confusion "
"(day and month inverted as example) as it is difficult to guess correctly"
" which part is the day and which one is the month in a date like "
"'01-03-2016'."
msgstr ""
#: ../../general/base_import/import_faq.rst:83
msgid ""
"To view which date format Odoo has found from your file you can check the"
" **Date Format** that is shown when clicking on **Options** under the "
"file selector. If this format is incorrect you can change it to your "
"liking using the *ISO 8601* to define the format."
msgstr ""
#: ../../general/base_import/import_faq.rst:86
msgid ""
"If you are importing an excel (.xls, .xlsx) file, you can use date cells "
"to store dates as the display of dates in excel is different from the way"
" it is stored. That way you will be sure that the date format is correct "
"in Odoo whatever your locale date format is."
msgstr ""
#: ../../general/base_import/import_faq.rst:91
msgid "Can I import numbers with currency sign (e.g.: $32.00)?"
msgstr ""
#: ../../general/base_import/import_faq.rst:93
msgid ""
"Yes, we fully support numbers with parenthesis to represent negative sign"
" as well as numbers with currency sign attached to them. Odoo also "
"automatically detect which thousand/decimal separator you use (you can "
"change those under **options**). If you use a currency symbol that is not"
" known to Odoo, it might not be recognized as a number though and it will"
" crash."
msgstr ""
#: ../../general/base_import/import_faq.rst:95
msgid "Examples of supported numbers (using thirty-two thousands as an example):"
msgstr ""
#: ../../general/base_import/import_faq.rst:97
msgid "32.000,00"
msgstr ""
#: ../../general/base_import/import_faq.rst:98
msgid "32000,00"
msgstr ""
#: ../../general/base_import/import_faq.rst:99
msgid "32,000.00"
msgstr ""
#: ../../general/base_import/import_faq.rst:100
msgid "-32000.00"
msgstr ""
#: ../../general/base_import/import_faq.rst:101
msgid "(32000.00)"
msgstr ""
#: ../../general/base_import/import_faq.rst:102
msgid "$ 32.000,00"
msgstr ""
#: ../../general/base_import/import_faq.rst:103
msgid "(32000.00 €)"
msgstr ""
#: ../../general/base_import/import_faq.rst:105
msgid "Example that will not work:"
msgstr ""
#: ../../general/base_import/import_faq.rst:107
msgid "ABC 32.000,00"
msgstr ""
#: ../../general/base_import/import_faq.rst:108
msgid "$ (32.000,00)"
msgstr ""
#: ../../general/base_import/import_faq.rst:113
msgid "What can I do when the Import preview table isn't displayed correctly?"
msgstr ""
#: ../../general/base_import/import_faq.rst:115
msgid ""
"By default the Import preview is set on commas as field separators and "
"quotation marks as text delimiters. If your csv file does not have these "
"settings, you can modify the File Format Options (displayed under the "
"Browse CSV file bar after you select your file)."
msgstr ""
#: ../../general/base_import/import_faq.rst:117
msgid ""
"Note that if your CSV file has a tabulation as separator, Odoo will not "
"detect the separations. You will need to change the file format options "
"in your spreadsheet application. See the following question."
msgstr ""
#: ../../general/base_import/import_faq.rst:122
msgid ""
"How can I change the CSV file format options when saving in my "
"spreadsheet application?"
msgstr ""
#: ../../general/base_import/import_faq.rst:124
msgid ""
"If you edit and save CSV files in speadsheet applications, your "
"computer's regional settings will be applied for the separator and "
"delimiter. We suggest you use OpenOffice or LibreOffice Calc as they will"
" allow you to modify all three options (in 'Save As' dialog box > Check "
"the box 'Edit filter settings' > Save)."
msgstr ""
#: ../../general/base_import/import_faq.rst:126
msgid ""
"Microsoft Excel will allow you to modify only the encoding when saving "
"(in 'Save As' dialog box > click 'Tools' dropdown list > Encoding tab)."
msgstr ""
#: ../../general/base_import/import_faq.rst:131
msgid "What's the difference between Database ID and External ID?"
msgstr ""
#: ../../general/base_import/import_faq.rst:133
msgid ""
"Some fields define a relationship with another object. For example, the "
"country of a contact is a link to a record of the 'Country' object. When "
"you want to import such fields, Odoo will have to recreate links between "
"the different records. To help you import such fields, Odoo provides 3 "
"mechanisms. You must use one and only one mechanism per field you want to"
" import."
msgstr ""
#: ../../general/base_import/import_faq.rst:135
msgid ""
"For example, to reference the country of a contact, Odoo proposes you 3 "
"different fields to import:"
msgstr ""
#: ../../general/base_import/import_faq.rst:137
msgid "Country: the name or code of the country"
msgstr ""
#: ../../general/base_import/import_faq.rst:138
msgid ""
"Country/Database ID: the unique Odoo ID for a record, defined by the ID "
"postgresql column"
msgstr ""
#: ../../general/base_import/import_faq.rst:139
msgid ""
"Country/External ID: the ID of this record referenced in another "
"application (or the .XML file that imported it)"
msgstr ""
#: ../../general/base_import/import_faq.rst:141
msgid "For the country Belgium, you can use one of these 3 ways to import:"
msgstr ""
#: ../../general/base_import/import_faq.rst:143
msgid "Country: Belgium"
msgstr ""
#: ../../general/base_import/import_faq.rst:144
msgid "Country/Database ID: 21"
msgstr ""
#: ../../general/base_import/import_faq.rst:145
msgid "Country/External ID: base.be"
msgstr ""
#: ../../general/base_import/import_faq.rst:147
msgid ""
"According to your need, you should use one of these 3 ways to reference "
"records in relations. Here is when you should use one or the other, "
"according to your need:"
msgstr ""
#: ../../general/base_import/import_faq.rst:149
msgid ""
"Use Country: This is the easiest way when your data come from CSV files "
"that have been created manually."
msgstr ""
#: ../../general/base_import/import_faq.rst:150
msgid ""
"Use Country/Database ID: You should rarely use this notation. It's mostly"
" used by developers as it's main advantage is to never have conflicts "
"(you may have several records with the same name, but they always have a "
"unique Database ID)"
msgstr ""
#: ../../general/base_import/import_faq.rst:151
msgid ""
"Use Country/External ID: Use External ID when you import data from a "
"third party application."
msgstr ""
#: ../../general/base_import/import_faq.rst:153
msgid ""
"When you use External IDs, you can import CSV files with the \"External "
"ID\" column to define the External ID of each record you import. Then, "
"you will be able to make a reference to that record with columns like "
"\"Field/External ID\". The following two CSV files give you an example "
"for Products and their Categories."
msgstr ""
#: ../../general/base_import/import_faq.rst:155
msgid ""
"`CSV file for categories "
"<../../_static/example_files/External_id_3rd_party_application_product_categories.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:157
msgid ""
"`CSV file for Products "
"<../../_static/example_files/External_id_3rd_party_application_products.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:161
msgid "What can I do if I have multiple matches for a field?"
msgstr ""
#: ../../general/base_import/import_faq.rst:163
msgid ""
"If for example you have two product categories with the child name "
"\"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other "
"Products/Sellable\"), your validation is halted but you may still import "
"your data. However, we recommend you do not import the data because they "
"will all be linked to the first 'Sellable' category found in the Product "
"Category list (\"Misc. Products/Sellable\"). We recommend you modify one "
"of the duplicates' values or your product category hierarchy."
msgstr ""
#: ../../general/base_import/import_faq.rst:165
msgid ""
"However if you do not wish to change your configuration of product "
"categories, we recommend you use make use of the external ID for this "
"field 'Category'."
msgstr ""
#: ../../general/base_import/import_faq.rst:170
msgid ""
"How can I import a many2many relationship field (e.g. a customer that has"
" multiple tags)?"
msgstr ""
#: ../../general/base_import/import_faq.rst:172
msgid ""
"The tags should be separated by a comma without any spacing. For example,"
" if you want your customer to be linked to both tags 'Manufacturer' and "
"'Retailer' then you will encode \"Manufacturer,Retailer\" in the same "
"column of your CSV file."
msgstr ""
#: ../../general/base_import/import_faq.rst:174
msgid ""
"`CSV file for Manufacturer, Retailer "
"<../../_static/example_files/m2m_customers_tags.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:179
msgid ""
"How can I import a one2many relationship (e.g. several Order Lines of a "
"Sales Order)?"
msgstr ""
#: ../../general/base_import/import_faq.rst:181
msgid ""
"If you want to import sales order having several order lines; for each "
"order line, you need to reserve a specific row in the CSV file. The first"
" order line will be imported on the same row as the information relative "
"to order. Any additional lines will need an addtional row that does not "
"have any information in the fields relative to the order. As an example, "
"here is purchase.order_functional_error_line_cant_adpat.CSV file of some "
"quotations you can import, based on demo data."
msgstr ""
#: ../../general/base_import/import_faq.rst:184
msgid ""
"`File for some Quotations "
"<../../_static/example_files/purchase.order_functional_error_line_cant_adpat.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:186
msgid ""
"The following CSV file shows how to import purchase orders with their "
"respective purchase order lines:"
msgstr ""
#: ../../general/base_import/import_faq.rst:188
msgid ""
"`Purchase orders with their respective purchase order lines "
"<../../_static/example_files/o2m_purchase_order_lines.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:190
msgid ""
"The following CSV file shows how to import customers and their respective"
" contacts:"
msgstr ""
#: ../../general/base_import/import_faq.rst:192
msgid ""
"`Customers and their respective contacts "
"<../../_static/example_files/o2m_customers_contacts.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:197
msgid "Can I import several times the same record?"
msgstr ""
#: ../../general/base_import/import_faq.rst:199
msgid ""
"If you import a file that contains one of the column \"External ID\" or "
"\"Database ID\", records that have already been imported will be modified"
" instead of being created. This is very usefull as it allows you to "
"import several times the same CSV file while having made some changes in "
"between two imports. Odoo will take care of creating or modifying each "
"record depending if it's new or not."
msgstr ""
#: ../../general/base_import/import_faq.rst:201
msgid ""
"This feature allows you to use the Import/Export tool of Odoo to modify a"
" batch of records in your favorite spreadsheet application."
msgstr ""
#: ../../general/base_import/import_faq.rst:206
msgid "What happens if I do not provide a value for a specific field?"
msgstr ""
#: ../../general/base_import/import_faq.rst:208
msgid ""
"If you do not set all fields in your CSV file, Odoo will assign the "
"default value for every non defined fields. But if you set fields with "
"empty values in your CSV file, Odoo will set the EMPTY value in the "
"field, instead of assigning the default value."
msgstr ""
#: ../../general/base_import/import_faq.rst:213
msgid "How to export/import different tables from an SQL application to Odoo?"
msgstr ""
#: ../../general/base_import/import_faq.rst:215
msgid ""
"If you need to import data from different tables, you will have to "
"recreate relations between records belonging to different tables. (e.g. "
"if you import companies and persons, you will have to recreate the link "
"between each person and the company they work for)."
msgstr ""
#: ../../general/base_import/import_faq.rst:217
msgid ""
"To manage relations between tables, you can use the \"External ID\" "
"facilities of Odoo. The \"External ID\" of a record is the unique "
"identifier of this record in another application. This \"External ID\" "
"must be unique accoss all the records of all objects, so it's a good "
"practice to prefix this \"External ID\" with the name of the application "
"or table. (like 'company_1', 'person_1' instead of '1')"
msgstr ""
#: ../../general/base_import/import_faq.rst:219
msgid ""
"As an example, suppose you have a SQL database with two tables you want "
"to import: companies and persons. Each person belong to one company, so "
"you will have to recreate the link between a person and the company he "
"work for. (If you want to test this example, here is a <a "
"href=\"/base_import/static/csv/database_import_test.sql\">dump of such a "
"PostgreSQL database</a>)"
msgstr ""
#: ../../general/base_import/import_faq.rst:221
msgid ""
"We will first export all companies and their \"External ID\". In PSQL, "
"write the following command:"
msgstr ""
#: ../../general/base_import/import_faq.rst:227
msgid "This SQL command will create the following CSV file::"
msgstr ""
#: ../../general/base_import/import_faq.rst:234
msgid ""
"To create the CSV file for persons, linked to companies, we will use the "
"following SQL command in PSQL:"
msgstr ""
#: ../../general/base_import/import_faq.rst:240
msgid "It will produce the following CSV file::"
msgstr ""
#: ../../general/base_import/import_faq.rst:248
msgid ""
"As you can see in this file, Fabien and Laurence are working for the "
"Bigees company (company_1) and Eric is working for the Organi company. "
"The relation between persons and companies is done using the External ID "
"of the companies. We had to prefix the \"External ID\" by the name of the"
" table to avoid a conflict of ID between persons and companies (person_1 "
"and company_1 who shared the same ID 1 in the orignial database)."
msgstr ""
#: ../../general/base_import/import_faq.rst:250
msgid ""
"The two files produced are ready to be imported in Odoo without any "
"modifications. After having imported these two CSV files, you will have 4"
" contacts and 3 companies. (the firsts two contacts are linked to the "
"first company). You must first import the companies and then the persons."
msgstr ""
#: ../../general/odoo_basics.rst:3
msgid "Basics"
msgstr ""
#: ../../general/odoo_basics/add_user.rst:3
msgid "How to add a user"
msgstr ""
#: ../../general/odoo_basics/add_user.rst:5
msgid ""
"Odoo provides you with the option to add additional users at any given "
"point."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:9
msgid "Add individual users"
msgstr ""
#: ../../general/odoo_basics/add_user.rst:11
msgid ""
"From the Settings module, go to the submenu :menuselection:`Users --> "
"Users` and click on **CREATE.** First add the name of your new user and "
"the professional email address - the one he will use to log into Odoo "
"instance - and a picture."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:19
msgid ""
"Under Access Rights, you can choose which applications your user can "
"access and use. Different levels of rights are available depending on the"
" app."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:23
msgid ""
"When you’re done editing the page and have clicked on **SAVE**, an "
"invitation email will automatically be sent to the user. The user must "
"click on it to accept the invitation to your instance and create a log-"
"in."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:32
msgid ""
"Remember that each additional user will increase your subscription fees. "
"Refer to our `*Pricing page* <https://www.odoo.com/pricing>`__ for more "
"information."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:39
msgid ""
"You can also add a new user on the fly from your dashboard. From the "
"above screenshot, enter the email address of the user you would like to "
"add and click on **INVITE**. The user will receive an email invite "
"containing a link to set his password. You will then be able to define "
"his accesses rights under the :menuselection:`Settings --> Users menu`."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:45
msgid ""
"`Deactivating Users <../../db_management/documentation.html#deactivating-"
"users>`_"
msgstr ""
#: ../../general/odoo_basics/add_user.rst:46
msgid ":doc:`../../crm/salesteam/setup/create_team`"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:3
msgid "Manage Odoo in your own language"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:5
msgid ""
"Odoo provides you with the option to manage Odoo in different languages, "
"and each user can use Odoo in his own language ."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:9
msgid "Load your desired language"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:11
msgid ""
"The first thing to do is to load your desired language on your Odoo "
"instance."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:14
msgid ""
"From the general dashboard click on the **Settings** app; on the top left"
" of the page select :menuselection:`Translations --> Load a Translation`,"
" select a language to install and click on **LOAD.**"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:23
msgid ""
"If you check the \"Websites to translate\" checkbox you will have the "
"option to change the navigation language on your website."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:27
msgid "Change your language"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:29
msgid ""
"You can change the language to the installed language by going to the "
"drop-down menu at the top right side of the screen, choose "
"**Preferences**."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:36
msgid ""
"Then change the Language setting to your installed language and click "
"**SAVE.**"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:42
msgid "Open a new menu to view the changes."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:45
msgid "Change another user's language"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:47
msgid ""
"Odoo also gives you the possibility for each user to choose his preferred"
" language."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:50
msgid ""
"To change the language for a different user, choose :menuselection:`Users"
" --> Users` from the Settings app. Here you have a list of all users and "
"you can choose the user who you'd like to change the language for. Select"
" the user and click on **Edit** in the top left corner. Under Preferences"
" you can change the Language to any previously installed language and "
"click **SAVE.**"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:61
msgid ":doc:`../../website/publish/translate`"
msgstr ""

695
locale/it/LC_MESSAGES/getting_started.po Normal file
View File

@ -0,0 +1,695 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2018.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-12-13 13:35+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.5.3\n"
#: ../../getting_started/documentation.rst:5
msgid "Odoo Online Implementation"
msgstr ""
#: ../../getting_started/documentation.rst:7
msgid ""
"This document summarizes **Odoo's Online services**, our Success Pack "
"**implementation methodology**, and *best practices* to **get started** "
"with our product."
msgstr ""
#: ../../getting_started/documentation.rst:11
msgid ""
"*We recommend that new Odoo Online customers read this document before "
"the kick-off call with our project manager. This way, we save time and "
"don't have to use your hours from the success pack discussing the "
"basics.*"
msgstr ""
#: ../../getting_started/documentation.rst:16
msgid ""
"*If you have not read this document, our project manager will review this"
" with you at the time of the kick-off call.*"
msgstr ""
#: ../../getting_started/documentation.rst:20
msgid "Getting Started"
msgstr ""
#: ../../getting_started/documentation.rst:22
msgid ""
"Do not wait for the kick-off meeting to begin playing with the software. "
"The more exposure you have with Odoo, the more time you will save later "
"during the implementation."
msgstr ""
#: ../../getting_started/documentation.rst:26
msgid ""
"Once you purchase an Odoo Online subscription, you will receive "
"instructions by e-mail on how to activate or create your database. From "
"this email, you can activate your existing Odoo database or create a new "
"one from scratch."
msgstr ""
#: ../../getting_started/documentation.rst:31
msgid ""
"If you did not receive this email, e.g. because the payment was made by "
"someone else in your company, contact our support using our `online "
"support form <https://www.odoo.com/help>`__."
msgstr ""
#: ../../getting_started/documentation.rst:38
msgid ""
"Fill in the sign-in or sign-up screens and you will get your first Odoo "
"database ready to be used."
msgstr ""
#: ../../getting_started/documentation.rst:41
msgid ""
"In order to familiarize yourself with the user interface, take a few "
"minutes to create records: *products, customers, opportunities or "
"projects / tasks*. Follow the blinking dots, they give you tips about the"
" user interface as shown in the picture below."
msgstr ""
#: ../../getting_started/documentation.rst:47
msgid "|left_pic|"
msgstr ""
#: ../../getting_started/documentation.rst:47
msgid "|right_pic|"
msgstr ""
#: ../../getting_started/documentation.rst:50
msgid ""
"Once you get used to the user interface, have a look at the "
"implementation planners. These are accessible from the Settings app, or "
"from the top progress bar on the right hand side of the main "
"applications."
msgstr ""
#: ../../getting_started/documentation.rst:58
msgid "These implementation planners will:"
msgstr ""
#: ../../getting_started/documentation.rst:60
msgid "help you define your goals and KPIs for each application,"
msgstr ""
#: ../../getting_started/documentation.rst:62
msgid "guide you through the different configuration steps,"
msgstr ""
#: ../../getting_started/documentation.rst:64
msgid "and provide you with tips and tricks to getting the most out of Odoo."
msgstr ""
#: ../../getting_started/documentation.rst:66
msgid ""
"Fill in the first steps of the implementation planner (goals, "
"expectations and KPIs). Our project manager will review them with you "
"during the implementation process."
msgstr ""
#: ../../getting_started/documentation.rst:73
msgid ""
"If you have questions or need support, our project manager will guide you"
" through all the steps. But you can also:"
msgstr ""
#: ../../getting_started/documentation.rst:76
msgid ""
"Read the documentation on our website: "
"`https://www.odoo.com/documentation/user "
"<https://www.odoo.com/documentation/user>`__"
msgstr ""
#: ../../getting_started/documentation.rst:79
msgid ""
"Watch the videos on our eLearning platform (Free with your first Success "
"Pack): `https://odoo.thinkific.com/courses/odoo-functional "
"<https://odoo.thinkific.com/courses/odoo-functional>`__"
msgstr ""
#: ../../getting_started/documentation.rst:82
msgid ""
"Watch the webinars on our `Youtube channel "
"<https://www.youtube.com/user/OpenERPonline>`__"
msgstr ""
#: ../../getting_started/documentation.rst:85
msgid ""
"Or send your questions to our online support through our `online support "
"form <https://www.odoo.com/help>`__."
msgstr ""
#: ../../getting_started/documentation.rst:89
msgid "What do we expect from you?"
msgstr ""
#: ../../getting_started/documentation.rst:91
msgid ""
"We are used to deploying fully featured projects within 25 to 250 hours "
"of services, which is much faster than any other ERP vendor on the "
"market. Most projects are completed between 1 to 9 calendar months."
msgstr ""
#: ../../getting_started/documentation.rst:95
msgid ""
"But what really **differentiates between a successful implementation and "
"a slow one, is you, the customer!** From our experience, when our "
"customer is engaged and proactive the implementation is smooth."
msgstr ""
#: ../../getting_started/documentation.rst:100
msgid "Your internal implementation manager"
msgstr ""
#: ../../getting_started/documentation.rst:102
msgid ""
"We ask that you maintain a single point of contact within your company to"
" work with our project manager on your Odoo Implementation. This is to "
"ensure efficiency and a single knowledge base in your company. "
"Additionally, this person must:"
msgstr ""
#: ../../getting_started/documentation.rst:107
msgid ""
"**be available at least 2 full days a week** for the project, otherwise "
"you risk slowing down your implementation. More is better with the "
"fastest implementations having a full time project manager."
msgstr ""
#: ../../getting_started/documentation.rst:111
msgid ""
"**have authority to take decisions** on their own. Odoo usually "
"transforms all departments within a company for the better. There can be "
"many small details that need quick turn arounds for answers and if there "
"is too much back and forth between several internal decision makers "
"within your company it could potentially seriously slow everything down."
msgstr ""
#: ../../getting_started/documentation.rst:117
msgid ""
"**have the leadership** to train and enforce policies internally with "
"full support from all departments and top management, or be part of top "
"management."
msgstr ""
#: ../../getting_started/documentation.rst:121
#, python-format
msgid "Integrate 90% of your business, not 100%"
msgstr ""
#: ../../getting_started/documentation.rst:123
msgid ""
"You probably chose Odoo because no other software allows for such a high "
"level of automation, feature coverage, and integration. But **don't be an"
" extremist.**"
msgstr ""
#: ../../getting_started/documentation.rst:127
msgid ""
"Customizations cost you time, money, are more complex to maintain, add "
"risks to the implementation, and can cause issues with upgrades."
msgstr ""
#: ../../getting_started/documentation.rst:130
#, python-format
msgid ""
"Standard Odoo can probably cover 90% of your business processes and "
"requirements. Be flexible on the remaining 10%, otherwise that 10% will "
"cost you twice the original project price. One always underestimates the "
"hidden costs of customization."
msgstr ""
#: ../../getting_started/documentation.rst:134
msgid ""
"**Do it the Odoo way, not yours.** Be flexible, use Odoo the way it was "
"designed. Learn how it works and don't try to replicate the way your old "
"system(s) works."
msgstr ""
#: ../../getting_started/documentation.rst:138
#, python-format
msgid ""
"**The project first, customizations second.** If you really want to "
"customize Odoo, phase it towards the end of the project, ideally after "
"having been in production for several months. Once a customer starts "
"using Odoo, they usually drop about 60% of their customization requests "
"as they learn to perform their work flows out of the box, or the Odoo "
"way. It is more important to have all your business processes working "
"than customizing a screen to add a few fields here and there or "
"automating a few e-mails."
msgstr ""
#: ../../getting_started/documentation.rst:147
msgid ""
"Our project managers are trained to help you make the right decisions and"
" measure the tradeoffs involved but it is much easier if you are aligned "
"with them on the objectives. Some processes may take more time than your "
"previous system(s), however you need to weigh that increase in time with "
"other decreases in time for other processes. If the net time spent is "
"decreased with your move to Odoo than you are already ahead."
msgstr ""
#: ../../getting_started/documentation.rst:155
msgid "Invest time in learning Odoo"
msgstr ""
#: ../../getting_started/documentation.rst:157
msgid ""
"Start your free trial and play with the system. The more comfortable you "
"are with navigating Odoo, the better your decisions will be and the "
"quicker and easier your training phases will be."
msgstr ""
#: ../../getting_started/documentation.rst:161
msgid ""
"Nothing replaces playing with the software, but here are some extra "
"resources:"
msgstr ""
#: ../../getting_started/documentation.rst:164
msgid ""
"Documentation: `https://www.odoo.com/documentation/user "
"<https://www.odoo.com/documentation/user>`__"
msgstr ""
#: ../../getting_started/documentation.rst:167
msgid ""
"Introduction Videos: `https://www.odoo.com/r/videos "
"<https://www.odoo.com/r/videos>`__"
msgstr ""
#: ../../getting_started/documentation.rst:170
msgid ""
"Customer Reviews: `https://www.odoo.com/blog/customer-reviews-6 "
"<https://www.odoo.com/blog/customer-reviews-6>`__"
msgstr ""
#: ../../getting_started/documentation.rst:174
msgid "Get things done"
msgstr ""
#: ../../getting_started/documentation.rst:176
msgid ""
"Want an easy way to start using Odoo? Install Odoo Notes to manage your "
"to-do list for the implementation: `https://www.odoo.com/page/notes "
"<https://www.odoo.com/page/notes>`__. From your Odoo home, go to Apps and"
" install the Notes application."
msgstr ""
#: ../../getting_started/documentation.rst:184
msgid "This module allows you to:"
msgstr ""
#: ../../getting_started/documentation.rst:186
msgid "Manage to-do lists for better interactions with your consultant;"
msgstr ""
#: ../../getting_started/documentation.rst:188
msgid "Share Odoo knowledge & good practices with your employees;"
msgstr ""
#: ../../getting_started/documentation.rst:190
msgid ""
"Get acquainted with all the generic tools of Odoo: Messaging, Discussion "
"Groups, Kanban Dashboard, etc."
msgstr ""
#: ../../getting_started/documentation.rst:197
msgid ""
"This application is even compatible with the Etherpad platform "
"(http://etherpad.org). To use these collaborative pads rather than "
"standard Odoo Notes, install the following add-on: Memos Pad."
msgstr ""
#: ../../getting_started/documentation.rst:202
msgid "What should you expect from us?"
msgstr ""
#: ../../getting_started/documentation.rst:205
msgid "Subscription Services"
msgstr ""
#: ../../getting_started/documentation.rst:208
msgid "Cloud Hosting"
msgstr ""
#: ../../getting_started/documentation.rst:210
msgid ""
"Odoo provides a top notch cloud infrastructure including backups in three"
" different data centers, database replication, the ability to duplicate "
"your instance in 10 minutes, and more!"
msgstr ""
#: ../../getting_started/documentation.rst:214
msgid ""
"Odoo Online SLA: `https://www.odoo.com/page/odoo-online-sla "
"<https://www.odoo.com/page/odoo-online-sla>`__\\"
msgstr ""
#: ../../getting_started/documentation.rst:217
msgid ""
"Odoo Online Security: `https://www.odoo.com/page/security "
"<https://www.odoo.com/fr_FR/page/security>`__"
msgstr ""
#: ../../getting_started/documentation.rst:220
msgid ""
"Privacy Policies: `https://www.odoo.com/page/odoo-privacy-policy "
"<https://www.odoo.com/page/odoo-privacy-policy>`__"
msgstr ""
#: ../../getting_started/documentation.rst:224
msgid "Support"
msgstr ""
#: ../../getting_started/documentation.rst:226
msgid ""
"Your Odoo Online subscription includes an **unlimited support service at "
"no extra cost, 24/5, Monday to Friday**. To cover 24 hours, our teams are"
" in San Francisco, Belgium and India. Questions could be about anything "
"and everything from: specific questions on current Odoo features and "
"where to configure them, bugfix requests, payments or subscription "
"issues."
msgstr ""
#: ../../getting_started/documentation.rst:232
msgid ""
"Our support can be contacted through our `online support form "
"<https://www.odoo.com/help>`__."
msgstr ""
#: ../../getting_started/documentation.rst:235
msgid ""
"Note: The support team cannot develop new features, customize, import "
"data or train your users. These services are provided by your dedicated "
"project manager, as part of the Success Pack."
msgstr ""
#: ../../getting_started/documentation.rst:240
msgid "Upgrades"
msgstr ""
#: ../../getting_started/documentation.rst:242
msgid ""
"Once every two months, Odoo releases a new version. You will get an "
"upgrade button within the **Manage Your Databases** screen. Upgrading "
"your database is at your own discretion, but allows you to benefit from "
"new features."
msgstr ""
#: ../../getting_started/documentation.rst:247
msgid ""
"We provide the option to upgrade in a test environment so that you can "
"evaluate a new version or train your team before the roll out. Simply "
"fill our `online support form <https://www.odoo.com/help>`__ to make this"
" request."
msgstr ""
#: ../../getting_started/documentation.rst:252
msgid "Success Pack Services"
msgstr ""
#: ../../getting_started/documentation.rst:254
msgid ""
"The Success Pack is a package of premium hour-based services performed by"
" a dedicated project manager and business analyst. The initial alloted "
"hours you purchased is purely an estimate and we do not guarantee "
"completion of your project within the first pack. We always strive to "
"complete projects within the initial allotement however any number of "
"factors can contribute to us not being able to do so, for example a scope"
" expansion or \"Scope Creep\" in the middle of your implementation, new "
"detail descoveries, or an increase in complexity that was not apparent "
"from the beginning."
msgstr ""
#: ../../getting_started/documentation.rst:263
msgid ""
"The list of services according to your success pack is detailed online: "
"`https://www.odoo.com/pricing-packs <https://www.odoo.com/pricing-"
"packs>`__"
msgstr ""
#: ../../getting_started/documentation.rst:266
msgid ""
"The goal of the project manager is to help you get to production within "
"the defined time frame and budget, i.e. the initial number of hours "
"defined in your success pack."
msgstr ""
#: ../../getting_started/documentation.rst:270
msgid "His/her role includes:"
msgstr ""
#: ../../getting_started/documentation.rst:272
msgid ""
"**Project Management:** review of your objectives & expectations, phasing"
" of the implementation (road map), mapping of your business needs and the"
" Odoo features."
msgstr ""
#: ../../getting_started/documentation.rst:276
msgid "**Customized Support:** by phone, e-mail or webinar."
msgstr ""
#: ../../getting_started/documentation.rst:278
msgid ""
"**Training, Coaching, and Onsite Consulting:** remote trainings via "
"screen sharing or training on premises. For on premise training sessions,"
" you will be expected to pay extra for travel expenses and accommodations"
" for your consultant."
msgstr ""
#: ../../getting_started/documentation.rst:283
msgid ""
"**Configuration:** decisions about how to implement specific needs in "
"Odoo and advanced configuration. (e.g. logistic routes, advanced pricing "
"structures, etc.)"
msgstr ""
#: ../../getting_started/documentation.rst:287
msgid ""
"**Data Import**: we can do it or assist you on how to do it with a "
"template prepared by the project manager."
msgstr ""
#: ../../getting_started/documentation.rst:290
msgid ""
"If you have subscribed to **Studio**, you benefit from following extra "
"services:"
msgstr ""
#: ../../getting_started/documentation.rst:293
msgid ""
"**Customization of screens:** Studio takes the Drag and Drop approach to "
"customize most screens in any way you see fit."
msgstr ""
#: ../../getting_started/documentation.rst:296
msgid ""
"**Customization of reports (PDF):** Studio itself will not allow you to "
"customize the reports yourself, however our project managers have access "
"to developers for advanced customizations."
msgstr ""
#: ../../getting_started/documentation.rst:300
msgid ""
"**Website Design:** standard themes are provided to get started at no "
"extra cost. However, our project manager can coach you on how to utilize "
"the building blocks of the website designer. The time spent will consume "
"hours of your success pack."
msgstr ""
#: ../../getting_started/documentation.rst:305
msgid ""
"**Workflow automations:** e.g. setting values in fields based on "
"triggers, sending reminders by emails, automating actions, etc. For very "
"advanced automations, our project managers have access to Odoo "
"developers."
msgstr ""
#: ../../getting_started/documentation.rst:310
msgid ""
"If any customization is needed, Odoo Studio App will be required. "
"Customizations made through Odoo Studio App will be maintained and "
"upgraded at each Odoo upgrade, at no extra cost."
msgstr ""
#: ../../getting_started/documentation.rst:314
msgid ""
"All time spent to perform these customizations by our Business Analysts "
"will be deducted from your Success Pack."
msgstr ""
#: ../../getting_started/documentation.rst:317
msgid ""
"In case of customizations that cannot be done via Studio and would "
"require a developer’s intervention, this will require Odoo.sh, please "
"speak to your Account Manager for more information. Additionally, any "
"work performed by a developer will add a recurring maintenance fee to "
"your subscription to cover maintenance and upgrade services. This cost "
"will be based on hours spent by the developer: 4€ or $5/month, per hour "
"of development will be added to the subscription fee."
msgstr ""
#: ../../getting_started/documentation.rst:325
msgid ""
"**Example:** a customization that took 2 hours of development will cost: "
"2 hours deducted from the Success Pack for the customization development "
"2 * $5 = $10/month as recurring fee for the maintenance of this "
"customization"
msgstr ""
#: ../../getting_started/documentation.rst:330
msgid "Implementation Methodology"
msgstr ""
#: ../../getting_started/documentation.rst:332
msgid ""
"We follow a **lean and hands-on methodology**, that is used to put "
"customers in production in a short period of time and at a low cost."
msgstr ""
#: ../../getting_started/documentation.rst:335
msgid ""
"After the kick-off meeting, we define a phasing plan to deploy Odoo "
"progressively, by groups of apps."
msgstr ""
#: ../../getting_started/documentation.rst:341
msgid ""
"The goal of the **Kick-off call** is for our project manager to come to "
"an understanding of your business in order to propose an implementation "
"plan (phasing). Each phase is the deployment of a set applications that "
"you will fully use in production at the end of the phase."
msgstr ""
#: ../../getting_started/documentation.rst:347
msgid "For every phase, the steps are the following:"
msgstr ""
#: ../../getting_started/documentation.rst:349
msgid ""
"**On Boarding:** Odoo's project manager will review Odoo's business flows"
" with you, according to your business. The goal is to train you, validate"
" the business process and configure according to your specific needs."
msgstr ""
#: ../../getting_started/documentation.rst:354
msgid ""
"**Data:** created manually or imported from your existing system. You are"
" responsible to export the data from your existing system and Odoo's "
"project manager will import them in Odoo."
msgstr ""
#: ../../getting_started/documentation.rst:358
msgid ""
"**Training:** once your applications are set up, your data imported, and "
"the system is working smoothly, you will train your users. There will be "
"some back and forth with your Odoo project manager to answer questions "
"and process your feedback."
msgstr ""
#: ../../getting_started/documentation.rst:363
msgid "**Production**: Once everyone is trained, your users start using Odoo."
msgstr ""
#: ../../getting_started/documentation.rst:366
msgid ""
"Once you are comfortable using Odoo, we will fine-tune the process and "
"**automate** some tasks and do the remaining customizations (**extra "
"screens and reports**)."
msgstr ""
#: ../../getting_started/documentation.rst:370
msgid ""
"Once all applications are deployed and users are comfortable on Odoo, our"
" project manager will not work on your project anymore (unless you have "
"new needs) and you will use the support service if you have further "
"questions."
msgstr ""
#: ../../getting_started/documentation.rst:376
msgid "Managing your databases"
msgstr ""
#: ../../getting_started/documentation.rst:378
msgid ""
"To access your databases, go to Odoo.com, sign in and click **My "
"Databases** in the drop-down menu at the top right corner."
msgstr ""
#: ../../getting_started/documentation.rst:384
msgid ""
"Odoo gives you the opportunity to test the system before going live or "
"before upgrading to a newer version. Do not mess up your working "
"environment with test data!"
msgstr ""
#: ../../getting_started/documentation.rst:388
msgid ""
"In that purpose, you can create as many free trials as you want "
"(available for 15 days). Those instances can be instant copies of your "
"working environment. To do so, go to the Odoo.com account in **My "
"Organizations** page and click **Duplicate**."
msgstr ""
#: ../../getting_started/documentation.rst:399
msgid ""
"You can find more information on how to manage your databases :ref:`here "
"<db_management/documentation>`."
msgstr ""
#: ../../getting_started/documentation.rst:403
msgid "Customer Success"
msgstr ""
#: ../../getting_started/documentation.rst:405
msgid ""
"Odoo is passionate about delighting our customers and ensuring that they "
"have all the resources needed to complete their project."
msgstr ""
#: ../../getting_started/documentation.rst:408
msgid ""
"During the implementation phase, your point of contact is the project "
"manager and eventually the support team."
msgstr ""
#: ../../getting_started/documentation.rst:411
msgid ""
"Once you are in production, you will probably have less interaction with "
"your project manager. At that time, we will assign a member of our Client"
" Success Team to you. They are specialized in the long-term relationship "
"with our customers. They will contact you to showcase new versions, "
"improve the way you work with Odoo, assess your new needs, etc..."
msgstr ""
#: ../../getting_started/documentation.rst:418
msgid ""
"Our internal goal is to keep customers for at least 10 years and offer "
"them a solution that grows with their needs!"
msgstr ""
#: ../../getting_started/documentation.rst:421
msgid "Welcome aboard and enjoy your Odoo experience!"
msgstr ""
#: ../../getting_started/documentation.rst:424
msgid ":doc:`../../db_management/documentation`"
msgstr ""

24
locale/it/LC_MESSAGES/index.po Normal file
View File

@ -0,0 +1,24 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2018.
#
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-06-07 09:30+0200\n"
"PO-Revision-Date: 2018-05-03 21:21+0200\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.5.3\n"
"Last-Translator: \n"
"Language-Team: \n"
"Language: it\n"
"X-Generator: Poedit 1.8.7.1\n"
#: ../../index.rst:3
msgid "Odoo User Documentation"
msgstr "Odoo documentazione utente"

7710
locale/it/LC_MESSAGES/inventory.po Normal file
View File

File diff suppressed because it is too large Load Diff

734
locale/it/LC_MESSAGES/manufacturing.po Normal file
View File

@ -0,0 +1,734 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2018.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-06-07 09:30+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.5.3\n"
#: ../../manufacturing.rst:5
msgid "Manufacturing"
msgstr ""
#: ../../manufacturing/operations.rst:3
msgid "Manufacturing Operations"
msgstr ""
#: ../../manufacturing/operations/replenishment.rst:3
msgid "Replenishment Strategies"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:3
msgid "How to select the right replenishment strategy"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:5
msgid ""
"Minimum Stock rules and Make to Order have similar consequences but "
"different rules. They should be used depending on your manufacturing and "
"delivery strategies."
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:10
msgid "Terminology"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:13
msgid "Minimum stock rule"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:15
msgid ""
"Minimum Stock rules are used to ensure that you always have the minimum "
"amount of a product in stock in order to manufacture your products and/or"
" answer to your customer needs. When the stock level of a product reaches"
" its minimum the system will automatically generate a procurement order "
"with the quantity needed to reach the maximum stock level."
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:22
#: ../../manufacturing/operations/replenishment/strategies.rst:58
msgid "Make to Order"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:24
msgid ""
"The Make to Order function will trigger a Purchase Order of the amount of"
" the Sales Order related to the product. The system will **not** check "
"the current stock. This means that a draft purchase order will be "
"generated regardless of the quantity on hand of the product."
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:30
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:27
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:62
msgid "Configuration"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:33
msgid "Minimum stock rules"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:35
msgid ""
"The Minimum Stock Rules configuration is available through your Inventory"
" module. In the Inventory Control menu select \"Reordering Rule\" in the "
"drop down menu. There, click on \"Create\" to set minimum and maximum "
"stock values for a given product."
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:44
msgid ""
"Show tooltips for \"minimum quantity\", \"maximum quantity\" and "
"\"quantity multiple\" fields"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:47
msgid ""
"Then, click on your product to access the related product form and, on "
"the \"Inventory submenu\", do not forget to select a supplier."
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:54
msgid ""
"Don't forget to select the right product type. A consumable can not be "
"stocked and will thus not be accounted for in the stock valuation."
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:60
msgid ""
"The Make to Order configuration is available on your product form through"
" your :menuselection:`Inventory --> Inventory control --> Products` (or "
"any other module where products are available)."
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:64
msgid "On the product form, under Inventory, click on \"Make To Order\"."
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:70
msgid "Choice between the two options"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:72
msgid ""
"The choice between the two options is thus dependent of your inventory "
"strategy. If you prefer to have a buffer and always have at least a "
"minimum amount, the minimum stock rule should be used. If you want to "
"reorder your stocks only if your sale is confirmed it is better to use "
"the Make to Order."
msgstr ""
#: ../../manufacturing/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials.rst:3
#: ../../manufacturing/overview/main_concepts/terminologies.rst:6
msgid "Bill of Materials"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:3
msgid "How to Sell a Set of Products as a Kit"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:5
msgid ""
"A *kit* is a set of components that are delivered without first being "
"assembled or mixed. Kits are described in Odoo using *bills of "
"materials*. There are two basic ways to configure kits, depending on how "
"stock of the kit product is to be managed. In either case, both the "
"Inventory and Manufacturing apps must be installed."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:12
msgid "Manage Stock of Component Products"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:14
msgid ""
"If you would like to assemble kits as they are ordered, managing stock of"
" the kit *components* only, you will use a Kit BoM without a "
"manufacturing step."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:18
msgid ""
"A product using a Kit BoM will appear as a single line item on a "
"quotation and sales order, but will generate a delivery order with one "
"line item for each of the components of the kit. In the examples below, "
"the image at left shows a sales order for the kit \"Custom Computer "
"Kit\", while the image at right shows the corresponding delivery order."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:24
msgid "|image0|\\ |image1|"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:29
msgid ""
"From the **Products** menu in either the Inventory or Manufacturing app, "
"create each component product as you would any other product, then create"
" the top-level, or kit product. The kit product should have only the "
"route **Manufacture** set. Because you cannot track the stock of kit "
"products, the Product Type should be set to **Consumable**. Because a kit"
" product cannot be purchased, **Can be Purchased** should be unchecked."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:37
msgid ""
"All other parameters on the kit product may be modified according to your"
" preference. The component products require no special configuration."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:44
msgid ""
"Once the products are configured, create a bill of materials for the kit "
"product. Add each component and its quantity. Select the BoM Type **Ship "
"this product as a set of components**. All other options may be left with"
" their default values."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:53
msgid "Manage Stock of Kit Product and Component Products"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:55
msgid ""
"If you would like to manage stock of the top-level kit product, you will "
"use a standard BoM with a manufacturing step instead of a Kit BoM. When "
"using a standard BoM to assemble kits, a manufacturing order will be "
"created. The manufacturing order must be registered as completed before "
"the kit product will appear in your stock."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:64
msgid ""
"On the kit product, select the route **Manufacture**. You may also select"
" **Make to Order**, which will create a manufacturing order whenever a "
"sales order is confirmed. Select the product type **Stockable Product** "
"to enable stock management."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:72
msgid ""
"When you create the bill of materials, select the BoM Type **Manufacture "
"this product**. The assembly of the kit will be described by a "
"manufacturing order rather than a packing operation."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/product_variants.rst:3
msgid "How to manage BoMs for product variants"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/product_variants.rst:5
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:125
msgid ""
"Odoo allows you to use one bill of materials for multiple variants of the"
" same product. Simply enable variants from :menuselection:`Configuration "
"--> Settings`."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/product_variants.rst:12
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:132
msgid ""
"You will then be able to specify which component lines are to be used in "
"the manufacture of each product variant. You may specify multiple "
"variants for each line. If no variant is specified, the line will be used"
" for all variants."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/product_variants.rst:17
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:137
msgid ""
"When defining variant BoMs on a line-item-basis, the **Product Variant** "
"field in the main section of the BoM should be left blank. This field is "
"used when creating a BoM for one variant of a product only."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:3
msgid "How to manage semi-finished products"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:5
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:83
msgid ""
"A subassembly is a manufactured product which is intended to be used as a"
" component of another manufactured product. You may wish to employ sub-"
"assemblies to simplify a complex BoM, to more accurately represent your "
"manufacturing flow, or to use the same subassembly in multiple BoMs. A "
"BoM that employs subassemblies is often referred to as a multi-level BoM."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:12
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:90
msgid ""
"Multi-level bills of materials in Odoo are accomplished by creating a "
"top-level BoM and subassembly BoMs. Next, the procurement route of the "
"subassembly product is defined. This ensures that every time a "
"manufacturing order for the top-level product is created, a manufacturing"
" order for each subassembly is created as well."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:19
msgid "Configure the Top -Level Product BoM"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:21
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:99
msgid ""
"To configure a multi-level BoM, create the top-level product and its BoM."
" Include any subassemblies in the list of components. Create a BoM for "
"each subassembly as you would for any product."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:29
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:107
msgid "Configure the Subassembly Product Data"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:31
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:109
msgid ""
"On the product form of the subassembly, you must select the routes "
"**Manufacture** and **Make To Order**. The **Manufacture** route takes "
"precedence over the **Buy** route, so selecting the latter will have no "
"effect."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:39
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:117
msgid ""
"If you would like to be able to purchase the subassembly in addition to "
"manufacturing it, select **Can be Purchased**. All other fields on the "
"subassembly product form may be configured according to your preference."
msgstr ""
#: ../../manufacturing/overview/getting_started.rst:3
msgid "Getting Started"
msgstr ""
#: ../../manufacturing/overview/getting_started.rst:5
msgid "How to consume composents to make a finished product"
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:3
msgid "How to create a Bill of Materials"
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:5
msgid ""
"A bill of materials (BoM) is a document that describes the component "
"products, the quantity of each component, and the process required to "
"manufacture a product, including a routing and individual steps."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:9
msgid ""
"In Odoo, each product may have multiple BoMs associated with it, but a "
"BoM can only be associated with a single product. A single BoM can, "
"however, describe multiple variants of the same product."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:14
msgid "Setting up a Basic BoM"
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:16
msgid ""
"If you choose to manage your manufacturing operations using manufacturing"
" orders only, you will define basic bills of materials without routings. "
"For more information about which method of management to use, review the "
"**Getting Started** section of the *Manufacturing* chapter of the "
"documentation."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:22
msgid ""
"Before creating your first bill of materials, you will need to create a "
"product and at least one component (components are considered products in"
" Odoo). You can do so from :menuselection:`Master Data --> Products`, or "
"on the fly from the relevant fields on the BoM form. Review the Inventory"
" chapter for more information about configuring products. Once you have "
"created a product and at least one component, select them from the "
"relevant dropdown menus to add them to your bill of materials. A new bill"
" of materials can be created from :menuselection:`Master Data --> Bills "
"of Materials`, or using the button on the top of the product form."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:32
msgid ""
"Under the **Miscellaneous** tab, you can fill additional fields. "
"**Sequence** defines the order in which your BoMs will be selected for "
"production orders, with lower numbers having higher priority. **Version**"
" allows you to track changes to your BoM over time."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:38
msgid "Adding a Routing to a BoM"
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:40
msgid ""
"A routing defines a series of operations required to manufacture a "
"product and the work center at which each operation is performed. A "
"routing may be added to multiple BoMs, though a BoM may only have one "
"routing. For more information about configuring routings, review the "
"chapter on routings."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:46
msgid ""
"After enabling routings from :menuselection:`Configuration --> Settings`,"
" you will be able to add a routing to a bill of materials by selecting a "
"routing from the dropdown list or creating one on the fly."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:50
msgid ""
"You may define the work operation or step in which each component is "
"consumed using the field, **Consumed in Operation** under the "
"**Components** tab. Similarly, you can define the operation at which the "
"product will be produced under the **Miscellaneous** tab using the field "
"**Produced at Operation**. If this field is left blank, the products will"
" be consumed/produced at the final operation in the routing."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:61
msgid "Adding Byproducts to a BoM"
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:63
msgid ""
"In Odoo, a byproduct is any product produced by a BoM in addition to the "
"primary product."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:66
msgid ""
"To add byproducts to a BoM, you will first need to enable them from "
":menuselection:`Configuration --> Settings`."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:72
msgid ""
"Once byproducts are enabled, you can add them to your bills of materials "
"under the **Byproducts** tab of the bill of materials. You can add any "
"product or products as byproducts. Byproducts are produced in the same "
"step of the routing as the primary product of the BoM."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:81
msgid "Setting up a BoM for a Product With Sub-Assemblies"
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:97
msgid "Configure the Top-Level Product BoM"
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:123
msgid "Using a Single BoM to Describe Several Variants of a Single Product"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:3
msgid "How to process a manufacturing order"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:6
msgid "Introduction"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:8
msgid ""
"There are two basic ways to manage manufacturing in Odoo. The first way "
"manages work with one document only. This document is the **manufacturing"
" order**. The second way uses additional documents to give you more "
"precise control over the manufacturing process. In this way, "
"**Manufacturing orders** are divided into one or more steps defined by "
"**work orders**, performed in an order defined by **routings**."
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:17
msgid "How to manage manufacturing without routings"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:19
msgid ""
"You will most likely use manufacturing orders without routings if all the"
" work to produce your product is performed in one place, by one person, "
"in one step, and/or you do not need the level of granular control "
"afforded by work orders and routings."
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:24
msgid ""
"Managing your operations in this way is the default behavior in Odoo. "
"There are two basic phases from planning to production:"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:27
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:52
msgid "Create manufacturing orders"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:29
msgid "Record Production"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:32
msgid "How to manage manufacturing with routings and work orders"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:34
msgid ""
"To use work orders and routings, you will need to enable the option "
"**Manage production by work orders** From :menuselection:`Configuration "
"--> Settings`. You will then be able to add routings to bills of "
"materials, and configure some additional related fields. You will also be"
" able to create **work centers**, the locations at which work orders are "
"performed."
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:41
msgid ""
"When manufacturing with routings and work orders, each work order is "
"scheduled individually. You will also have access to time and capacity "
"planning, and reports on costing and efficiency on a work center level."
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:45
msgid ""
"Manufacturing using routings can be broken down into several steps. When "
"configuring your BoM, you will need to add a routing defining the "
"component work orders. After planning the manufacturing order, you will "
"have the added step of scheduling work orders."
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:50
msgid "The workflow is thus divided into three basic phases, as follows:"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:54
msgid "Schedule the associated work orders."
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:56
msgid "Perform the scheduled work and record production."
msgstr ""
#: ../../manufacturing/overview/main_concepts.rst:3
msgid "Main Concepts"
msgstr ""
#: ../../manufacturing/overview/main_concepts/intro.rst:3
msgid "Introduction to Odoo Manufacturing"
msgstr ""
#: ../../manufacturing/overview/main_concepts/intro.rst:11
msgid "Transcript"
msgstr ""
#: ../../manufacturing/overview/main_concepts/intro.rst:13
msgid "Work in progress."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:3
msgid "Manufacturing Terminologies"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:9
msgid ""
"A bill of materials (BoM) is a document that describes the materials, the"
" quantity of each material, and the steps required to manufacture a "
"product. Depending on the industry and the nature of the finished "
"product, a different name may be used to describe the same document. For "
"example, in the pharmaceutical industry, the term “recipe” may be used."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:14
msgid "Cycle"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:17
msgid ""
"A production cycle is a frame of time during which an entire "
"manufacturing process can be fulfilled."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:19
msgid "Downtime or Leave"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:22
msgid ""
"Time during which a resource is unavailable. If the resource is a "
"machine, the unavailability is downtime, while if the resource is human, "
"unavailable time is called a Leave."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:25
msgid "Finished products"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:28
msgid ""
"Finished products are the final output of a manufacturing process. They "
"are normally not intended to be used as input into another manufacturing "
"order of the company."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:31
msgid "Kit"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:34
msgid ""
"A kit is a set of components that are described by a bill of materials, "
"but which are delivered separately rather than assembled or mixed."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:36
msgid "Multi-level Bill of Materials"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:39
msgid ""
"A bill of material can quickly grow very complex. To keep it manageable, "
"it can be broken down into several smaller manufactured parts, each "
"having its own BOM. These parts are typically referred to as sub-assembly"
" of intermediate products."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:44
msgid ""
"Defining a BOM in multiple levels reduces the complexity of the top-level"
" document and allows components to be reused in other BoMs."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:46
msgid "Phantom Bill of Material"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:49
msgid ""
"A phantom bill of material is always used in the context of multi-level "
"BOMs. It allows to add a sub-assembly as part of a bigger end-product "
"while avoiding to trigger a separate manufacturing order for the sub-"
"assembly."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:54
msgid ""
"As such, when a manufacturing order for the final product is launched, "
"the components of the sub-assembly are reflected in the parent BOM as if "
"they were direct components of the parent BOM."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:58
msgid ""
"Phantom BOM are thus used for grouping a set of components with the aim "
"of reusing them in many other BOM without the need to launch separate "
"manufacturing orders for the sub-assemblies."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:61
msgid "Raw Materials"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:64
msgid ""
"Raw materials and components constitute the input that are transformed to"
" produce semi-finished or finished goods."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:67
msgid ""
"The transformation here can take many aspects according to the industry. "
"It can be simple assembly, welding, mixing, etc."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:69
msgid "Routing"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:72
msgid ""
"A routing is a document that describes a series of Work Orders and the "
"Work Centers at which they will be carried out"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:74
msgid "Semi-finished products and sub-assemblies"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:77
msgid ""
"These are products which are manufactured with the purpose to be consumed"
" in another manufacturing order."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:79
msgid "Work Order Operations"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:82
msgid ""
"Work Order Operations specify the set of activities necessary to fully "
"process a manufacturing order. Each activity or operation takes some time"
" to be completed and is performed into a determined production unit (also"
" called work center)."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:86
msgid "Work Order"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:89
msgid ""
"A work order is a single manufacturing operation that is scheduled for "
"execution on a given date and a given duration."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:91
msgid "Work Center"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:94
msgid ""
"Work centers identify production units and their resources. They are used"
" to represent the plant capacity as well as costing information. The "
"capacity is a combination of resources and their availability time."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:97
msgid "Resources"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:100
msgid ""
"In manufacturing a resource can be a human being (employee) or machine "
"available in a work center."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:102
msgid "Working Time"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:105
msgid ""
"Each resource has its normal working time. For instance, machines can be "
"set up to operate 7 days a week 20 hours out of 24."
msgstr ""

3003
locale/it/LC_MESSAGES/point_of_sale.po Normal file
View File

File diff suppressed because it is too large Load Diff

24
locale/it/LC_MESSAGES/practical.po Normal file
View File

@ -0,0 +1,24 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2018.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-06-07 09:30+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.5.3\n"
#: ../../practical.rst:3
msgid "Practical Information"
msgstr ""

1715
locale/it/LC_MESSAGES/project.po Normal file
View File

File diff suppressed because it is too large Load Diff

2945
locale/it/LC_MESSAGES/purchase.po Normal file
View File

File diff suppressed because it is too large Load Diff

24
locale/it/LC_MESSAGES/recruitment.po Normal file
View File

@ -0,0 +1,24 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2018.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-11-22 13:16+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.5.3\n"
#: ../../recruitment.rst:5
msgid "Recruitment"
msgstr ""

1888
locale/it/LC_MESSAGES/sales.po Normal file
View File

File diff suppressed because it is too large Load Diff

1410
locale/it/LC_MESSAGES/website.po Normal file
View File

File diff suppressed because it is too large Load Diff