bzr revid: vra@tinyerp.com-20090612051222-f1e7agh9hgkiiqk8
This commit is contained in:
vra (Tiny)
2009-06-12 10:42:22 +05:30
73 changed files with 776 additions and 1252 deletions
+1 -1
View File
@@ -652,7 +652,7 @@ class account_journal_period(osv.osv):
'name': fields.char('Journal-Period Name', size=64, required=True),
'journal_id': fields.many2one('account.journal', 'Journal', required=True, ondelete="cascade"),
'period_id': fields.many2one('account.period', 'Period', required=True, ondelete="cascade"),
'icon': fields.function(_icon_get, method=True, string='Icon', type='string'),
'icon': fields.function(_icon_get, method=True, string='Icon', type='char', size=32),
'active': fields.boolean('Active', required=True),
'state': fields.selection([('draft','Draft'), ('printed','Printed'), ('done','Done')], 'Status', required=True, readonly=True),
'fiscalyear_id': fields.related('period_id', 'fiscalyear_id', string='Fiscal Year', type='many2one', relation='account.fiscalyear'),
+1 -1
View File
@@ -18,5 +18,5 @@ msgstr ""
#. module: account_chart
#: model:ir.module.module,description:account_chart.module_meta_information
msgid "Remove minimal account chart"
msgstr ""
msgstr "Supprime le plan comptable minimum"
File diff suppressed because it is too large Load Diff
+2 -2
View File
@@ -34,9 +34,9 @@
Note that:
- You can define new types of events in
Events \ Configuration \ Types of Events
Events / Configuration / Types of Events
- You can access predefined reports about number of registration per event or per event category in :
Events \ Reporting
Events / Reporting
""",
'author': 'Tiny',
'depends': ['crm', 'base_contact', 'account'],
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+7 -613
View File
@@ -4,620 +4,14 @@
#
msgid ""
msgstr ""
"Project-Id-Version: OpenERP Server 5.0.1\n"
"Project-Id-Version: OpenERP Server 5.0.0\n"
"Report-Msgid-Bugs-To: support@openerp.com\n"
"POT-Creation-Date: 2009-05-19 14:22:20+0000\n"
"PO-Revision-Date: 2009-05-20 10:22:20+0000\n"
"Last-Translator: <>\n"
"POT-Creation-Date: 2009-04-10 12:38+0000\n"
"PO-Revision-Date: 2009-04-20 06:41+0000\n"
"Last-Translator: Olivier (OpenERP) <Unknown>\n"
"Language-Team: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: \n"
"Plural-Forms: \n"
#. module: event
#: field:event.event,date_end:0
#: field:report.event.registration,date_end:0
msgid "Ending date"
msgstr ""
#. module: event
#: field:event.event,register_min:0
msgid "Minimum Registrations"
msgstr ""
#. module: event
#: constraint:ir.actions.act_window:0
msgid "Invalid model name in the action definition."
msgstr ""
#. module: event
#: field:event.event,mail_registr:0
msgid "Registration Email"
msgstr ""
#. module: event
#: model:crm.case.section,name:event.event_0_crm_case_section
msgid "Concert of Bon Jovi"
msgstr ""
#. module: event
#: field:event.event,mail_confirm:0
msgid "Confirmation Email"
msgstr ""
#. module: event
#: constraint:crm.case.section:0
msgid "Error ! You cannot create recursive sections."
msgstr ""
#. module: event
#: model:ir.model,name:event.model_event_registration
msgid "Event Registration"
msgstr ""
#. module: event
#: model:ir.actions.wizard,name:event.event_reg_invoice
msgid "Make Invoice"
msgstr ""
#. module: event
#: field:report.event.type.registration,draft_state:0
msgid "Draft Registrations"
msgstr ""
#. module: event
#: view:report.event.registration:0
msgid "Event on Registration"
msgstr ""
#. module: event
#: wizard_button:event.reg_make_invoice,init,end:0
msgid "Ok"
msgstr ""
#. module: event
#: field:event.event,mail_auto_confirm:0
msgid "Mail Auto Confirm"
msgstr ""
#. module: event
#: model:product.template,name:event.event_product_1_product_template
msgid "Ticket for Opera"
msgstr ""
#. module: event
#: code:addons/event/event.py:0
#, python-format
msgid "Error!"
msgstr ""
#. module: event
#: view:event.event:0
msgid "Confirm Event"
msgstr ""
#. module: event
#: model:crm.case.section,name:event.event_1_crm_case_section
msgid "Opera of Verdi"
msgstr ""
#. module: event
#: field:report.event.registration,draft_state:0
msgid "Draft Registration"
msgstr ""
#. module: event
#: wizard_view:event.reg_make_invoice,init:0
msgid "Create Invoices"
msgstr ""
#. module: event
#: view:event.registration:0
msgid "Extra Info"
msgstr ""
#. module: event
#: view:event.registration:0
msgid "Registration"
msgstr ""
#. module: event
#: field:event.type,name:0
#: model:ir.model,name:event.model_event_type
msgid "Event type"
msgstr ""
#. module: event
#: view:event.event:0
#: model:ir.model,name:event.model_event_event
#: model:ir.module.module,shortdesc:event.module_meta_information
#: field:report.event.registration,name:0
msgid "Event"
msgstr ""
#. module: event
#: selection:event.event,state:0
msgid "Confirmed"
msgstr ""
#. module: event
#: wizard_view:event.confirm_registration,split:0
msgid "Registration Confirmation"
msgstr ""
#. module: event
#: view:event.registration:0
msgid "Dates"
msgstr ""
#. module: event
#: field:event.event,register_current:0
#: model:ir.actions.act_window,name:event.action_registration_confirm
#: model:ir.ui.menu,name:event.menu_action_registration_confirm
msgid "Confirmed Registrations"
msgstr ""
#. module: event
#: field:event.event,mail_auto_registr:0
msgid "Mail Auto Register"
msgstr ""
#. module: event
#: view:event.registration:0
msgid "Badge"
msgstr ""
#. module: event
#: field:event.event,section_id:0
msgid "Case section"
msgstr ""
#. module: event
#: field:event.registration,tobe_invoiced:0
msgid "To be Invoiced"
msgstr ""
#. module: event
#: model:ir.ui.menu,name:event.menu_event_event
msgid "All Events"
msgstr ""
#. module: event
#: model:ir.ui.menu,name:event.menu_report_event
msgid "Reporting"
msgstr "Reporting"
#. module: event
#: view:event.registration:0
msgid "Cancel Registration"
msgstr ""
#. module: event
#: model:ir.ui.menu,name:event.menu_action_event_categories
msgid "Events by Categories"
msgstr ""
#. module: event
#: wizard_view:event.confirm_registration,split:0
msgid "The event limit is reached. What do you want to do?"
msgstr ""
#. module: event
#: field:report.event.type.registration,confirm_state:0
msgid "Confirm Registrations"
msgstr ""
#. module: event
#: view:event.registration:0
msgid "References"
msgstr ""
#. module: event
#: model:ir.actions.act_window,name:event.action_event_type_registration
#: model:ir.ui.menu,name:event.menu_report_event_type_registration
#: view:report.event.type.registration:0
msgid "Registration By Event Types"
msgstr ""
#. module: event
#: model:ir.ui.menu,name:event.menu_event_config
msgid "Configuration"
msgstr "Configuration"
#. module: event
#: code:addons/event/event.py:0
#, python-format
msgid "You must define a reply-to address in order to mail the participant. You can do this in the Mailing tab of your event. Note that this is also the place where you can configure your event to not send emails automaticly while registering"
msgstr ""
#. module: event
#: constraint:ir.ui.view:0
msgid "Invalid XML for View Architecture!"
msgstr "XML non valide pour l'architecture de la vue"
#. module: event
#: wizard_button:event.confirm_registration,split,confirm:0
msgid "Confirm Anyway"
msgstr ""
#. module: event
#: constraint:product.template:0
msgid "Error: UOS must be in a different category than the UOM"
msgstr "Erreur: l'unité de vente doit appartenir à une catégorie différente que l'unité de mesure"
#. module: event
#: view:event.event:0
msgid "Parent Category"
msgstr ""
#. module: event
#: view:event.registration:0
msgid "Registration Invoiced"
msgstr ""
#. module: event
#: field:report.event.type.registration,nbevent:0
msgid "Number Of Events"
msgstr ""
#. module: event
#: view:event.event:0
msgid "Cancel Event"
msgstr ""
#. module: event
#: wizard_field:event.reg_make_invoice,init,inv_rej_reason:0
msgid "Error Messages"
msgstr ""
#. module: event
#: view:event.event:0
msgid "Mailing"
msgstr ""
#. module: event
#: model:product.template,name:event.event_product_0_product_template
msgid "Ticket for Concert"
msgstr ""
#. module: event
#: field:event.event,register_prospect:0
#: model:ir.actions.act_window,name:event.action_registration_draft
#: model:ir.ui.menu,name:event.menu_action_registration_draft
msgid "Unconfirmed Registrations"
msgstr ""
#. module: event
#: field:event.registration,partner_invoice_id:0
msgid "Partner Invoiced"
msgstr ""
#. module: event
#: view:event.registration:0
msgid "Communication history"
msgstr ""
#. module: event
#: selection:event.event,state:0
msgid "Canceled"
msgstr ""
#. module: event
#: view:event.event:0
msgid "Event Done"
msgstr ""
#. module: event
#: field:event.registration,badge_name:0
msgid "Badge Name"
msgstr ""
#. module: event
#: model:ir.actions.act_window,name:event.action_event_registration
#: model:ir.ui.menu,name:event.menu_report_event_registration
msgid "Events On Registrations"
msgstr ""
#. module: event
#: constraint:product.template:0
msgid "Error: The default UOM and the purchase UOM must be in the same category."
msgstr "Erreur: l'unité de mesure par défaut et l'unité de mesure d'achat doivent faire partie de la même catégorie"
#. module: event
#: wizard_field:event.reg_make_invoice,init,inv_created:0
msgid "Invoice Created"
msgstr ""
#. module: event
#: view:event.event:0
msgid "Statistics"
msgstr ""
#. module: event
#: selection:event.event,state:0
msgid "Draft"
msgstr ""
#. module: event
#: view:event.event:0
msgid "Event description"
msgstr ""
#. module: event
#: model:ir.model,name:event.model_report_event_type_registration
msgid "Event type on registration"
msgstr ""
#. module: event
#: model:ir.module.module,description:event.module_meta_information
msgid "Organization and management of events.\n"
"\n"
" This module allow you\n"
" * to manage your events and their registrations\n"
" * to use emails to automatically confirm and send acknowledgements for any registration to an event\n"
" * ...\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
""
msgstr ""
#. module: event
#: field:event.registration,event_id:0
msgid "Event Related"
msgstr ""
#. module: event
#: model:crm.case.section,name:event.case_section_event
#: view:event.event:0
#: model:ir.actions.act_window,name:event.action_event_view
msgid "Events"
msgstr "Évènements"
#. module: event
#: field:event.registration,nb_register:0
msgid "Number of Registration"
msgstr ""
#. module: event
#: view:event.event:0
#: field:event.event,state:0
#: view:event.registration:0
msgid "Status"
msgstr ""
#. module: event
#: model:ir.actions.act_window,name:event.action_event_categories
msgid "Events by section"
msgstr ""
#. module: event
#: constraint:ir.model:0
msgid "The Object name must start with x_ and not contain any special character !"
msgstr "Le nom de l'objet doit commencer avec x_ et ne pas contenir de charactères spéciaux !"
#. module: event
#: model:ir.ui.menu,name:event.menu_action_registration
msgid "All Registrations"
msgstr ""
#. module: event
#: help:event.event,mail_auto_registr:0
msgid "Check this box if you want to use the automatic mailing for new registration"
msgstr ""
#. module: event
#: view:event.event:0
msgid "Set To Draft"
msgstr ""
#. module: event
#: view:event.registration:0
#: model:ir.actions.wizard,name:event.event_confirm_registration
#: field:report.event.registration,confirm_state:0
msgid "Confirm Registration"
msgstr ""
#. module: event
#: view:event.registration:0
msgid "History"
msgstr ""
#. module: event
#: model:ir.ui.menu,name:event.menu_event_type
msgid "Types of Events"
msgstr ""
#. module: event
#: field:event.registration,contact_id:0
msgid "Partner Contact"
msgstr ""
#. module: event
#: view:event.event:0
msgid "Auto Confirmation Email"
msgstr ""
#. module: event
#: view:event.event:0
#: view:event.registration:0
msgid "General"
msgstr ""
#. module: event
#: view:event.registration:0
msgid "Send Reminder"
msgstr ""
#. module: event
#: selection:event.event,state:0
msgid "Done"
msgstr ""
#. module: event
#: field:event.event,date_begin:0
#: field:report.event.registration,date_begin:0
msgid "Beginning date"
msgstr ""
#. module: event
#: field:event.registration,invoice_id:0
msgid "Invoice"
msgstr ""
#. module: event
#: model:ir.model,name:event.model_report_event_registration
msgid "Events on registrations"
msgstr ""
#. module: event
#: wizard_button:event.confirm_registration,split,end:0
msgid "Cancel"
msgstr ""
#. module: event
#: wizard_button:event.reg_make_invoice,init,open:0
msgid "Open"
msgstr ""
#. module: event
#: field:event.registration,badge_title:0
msgid "Badge Title"
msgstr ""
#. module: event
#: model:ir.actions.act_window,name:event.action_new_event_form
#: model:ir.ui.menu,name:event.menu_event_new_event
msgid "New event"
msgstr ""
#. module: event
#: field:event.registration,unit_price:0
msgid "Unit Price"
msgstr ""
#. module: event
#: model:crm.case.section,name:event.event_2_crm_case_section
msgid "Conference on ERP Buisness"
msgstr ""
#. module: event
#: field:event.registration,badge_partner:0
msgid "Badge Partner"
msgstr ""
#. module: event
#: model:ir.actions.act_window,name:event.action_event_view_confirm
#: model:ir.ui.menu,name:event.menu_event_event_confirm
msgid "Confirmed Events"
msgstr ""
#. module: event
#: field:event.event,register_max:0
#: field:report.event.registration,register_max:0
msgid "Maximum Registrations"
msgstr ""
#. module: event
#: field:event.event,type:0
msgid "Type"
msgstr ""
#. module: event
#: help:event.event,mail_registr:0
msgid "This email will be sent when someone subscribes to the event."
msgstr ""
#. module: event
#: model:product.template,name:event.event_product_2_product_template
msgid "Ticket for Conference"
msgstr ""
#. module: event
#: field:event.registration,case_id:0
msgid "Case"
msgstr ""
#. module: event
#: view:event.event:0
msgid "Name"
msgstr ""
#. module: event
#: help:event.event,mail_auto_confirm:0
msgid "Check this box if you want ot use the automatic confirmation emailing or the reminder"
msgstr ""
#. module: event
#: help:event.event,mail_confirm:0
msgid "This email will be sent when the event gets confimed or when someone subscribes to a confirmed event. This is also the email sent to remind someone about the event."
msgstr ""
#. module: event
#: field:event.event,product_id:0
msgid "Product"
msgstr ""
#. module: event
#: field:event.registration,invoice_label:0
msgid "Label Invoice"
msgstr ""
#. module: event
#: view:event.registration:0
msgid "Payments"
msgstr ""
#. module: event
#: view:event.type:0
#: field:report.event.type.registration,name:0
msgid "Event Type"
msgstr ""
#. module: event
#: view:event.event:0
#: model:ir.actions.act_window,name:event.action_registration
#: model:ir.actions.wizard,name:event.wizard_event_registration
msgid "Registrations"
msgstr ""
#. module: event
#: model:ir.actions.act_window,name:event.action_event_view_draft
#: model:ir.ui.menu,name:event.menu_event_event_draft
msgid "Draft Events"
msgstr ""
#. module: event
#: wizard_field:event.reg_make_invoice,init,inv_rejected:0
msgid "Invoice Rejected"
msgstr ""
#. module: event
#: model:ir.ui.menu,name:event.menu_event_main
msgid "Events Organisation"
msgstr ""
#. module: event
#: view:event.registration:0
msgid "Actions"
msgstr ""
#. module: event
#: model:ir.actions.wizard,name:event.wizard_event_reg_partners
msgid "List Register Partners"
msgstr ""
#. module: event
#: constraint:product.product:0
msgid "Error: Invalid ean code"
msgstr "Erreur: code EAN invalide"
#. module: event
#: view:event.event:0
msgid "Auto Registration Email"
msgstr ""
"Content-Transfer-Encoding: 8bit\n"
"X-Launchpad-Export-Date: 2009-06-11 08:08+0000\n"
"X-Generator: Launchpad (build Unknown)\n"
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+2 -2
View File
@@ -360,9 +360,9 @@ msgid "Organization and management of events.\n"
"\n"
" Note that:\n"
" - You can define new types of events in\n"
" Events \ Configuration \ Types of Events\n"
" Events / Configuration / Types of Events\n"
" - You can access predefined reports about number of registration per event or per event category in :\n"
" Events \ Reporting\n"
" Events / Reporting\n"
""
msgstr ""
+21 -17
View File
@@ -4,16 +4,17 @@
#
msgid ""
msgstr ""
"Project-Id-Version: OpenERP Server 5.0.1\n"
"Project-Id-Version: OpenERP Server 5.0.0\n"
"Report-Msgid-Bugs-To: support@openerp.com\n"
"POT-Creation-Date: 2009-05-19 14:22:20+0000\n"
"PO-Revision-Date: 2009-05-20 10:22:20+0000\n"
"Last-Translator: <>\n"
"POT-Creation-Date: 2009-05-19 14:36+0000\n"
"PO-Revision-Date: 2009-06-11 13:40+0000\n"
"Last-Translator: Olivier (OpenERP) <Unknown>\n"
"Language-Team: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: \n"
"Plural-Forms: \n"
"Content-Transfer-Encoding: 8bit\n"
"X-Launchpad-Export-Date: 2009-06-11 13:44+0000\n"
"X-Generator: Launchpad (build Unknown)\n"
#. module: hr
#: model:process.node,name:hr.process_node_openerpuser0
@@ -51,12 +52,12 @@ msgstr "Dimanche"
#. module: hr
#: view:res.users:0
msgid "Parents"
msgstr ""
msgstr "Parents"
#. module: hr
#: constraint:ir.actions.act_window:0
msgid "Invalid model name in the action definition."
msgstr ""
msgstr "Nom de Modèle non valide pour la définition de l'action."
#. module: hr
#: view:hr.department:0
@@ -150,7 +151,7 @@ msgstr "Téléphone professionnel"
#. module: hr
#: field:hr.employee.category,child_ids:0
msgid "Child Categories"
msgstr ""
msgstr "Catégories filles"
#. module: hr
#: field:hr.employee,work_location:0
@@ -208,7 +209,7 @@ msgstr "Divorcé(e)"
#. module: hr
#: field:hr.employee.category,parent_id:0
msgid "Parent Category"
msgstr ""
msgstr "Catégorie Parente"
#. module: hr
#: model:ir.actions.act_window,name:hr.open_module_tree_department
@@ -314,7 +315,8 @@ msgstr "Actif"
#. module: hr
#: constraint:hr.employee:0
msgid "Error ! You cannot create recursive Hierarchy of Employees."
msgstr "Erreur ! Vous ne pouvez pas créer de hiérarchie d'employés récursives."
msgstr ""
"Erreur ! Vous ne pouvez pas créer de hiérarchie d'employés récursives."
#. module: hr
#: model:process.process,name:hr.process_process_employeecontractprocess0
@@ -355,7 +357,7 @@ msgstr "Date début"
#. module: hr
#: field:res.users,parent_id:0
msgid "Parent Users"
msgstr ""
msgstr "Utilisateurs Parents"
#. module: hr
#: field:hr.employee,address_id:0
@@ -379,8 +381,11 @@ msgstr "Informations personnelles"
#. module: hr
#: constraint:ir.model:0
msgid "The Object name must start with x_ and not contain any special character !"
msgstr "Le nom de l'objet doit commencer avec x_ et ne pas contenir de charactères spéciaux !"
msgid ""
"The Object name must start with x_ and not contain any special character !"
msgstr ""
"Le nom de l'objet doit commencer avec x_ et ne pas contenir de charactères "
"spéciaux !"
#. module: hr
#: view:hr.timesheet:0
@@ -412,7 +417,7 @@ msgstr "Catégories des employés"
#. module: hr
#: field:hr.employee,address_home_id:0
msgid "Home Address"
msgstr ""
msgstr "Adresse Personnelle"
#. module: hr
#: view:hr.department:0
@@ -454,7 +459,7 @@ msgstr "Nom du département"
#. module: hr
#: field:hr.department,child_ids:0
msgid "Child Departments"
msgstr ""
msgstr "Départements fils"
#. module: hr
#: view:hr.employee:0
@@ -488,4 +493,3 @@ msgstr "Samedi"
#: model:ir.ui.menu,name:hr.menu_open_view_employee_new
msgid "New Employee"
msgstr "Nouvel employé"
+4 -4
View File
@@ -13,17 +13,17 @@
Note that:
- A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in
HR \ Configuration \ Holidays Status
HR / Configuration / Holidays Status
- An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).
- There are two ways to print the employee's holidays:
* The first will allow to choose employees by department and is used by clicking the menu item located in
HR \ Holidays Request \ Print Summary of Holidays
HR / Holidays Request / Print Summary of Holidays
* The second will allow you to choose the holidays report for specific employees. Go on the list
HR \ Employees \ Employees
HR / Employees / Employees
then select the ones you want to choose, click on the print icon and select the option
'Print Summary of Employee's Holidays'
- The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in
Administration \ Users \ Users
Administration / Users / Users
for example, you maybe will do it for the user 'admin'.
""",
'author': 'Tiny & Axelor',
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+4 -4
View File
@@ -469,17 +469,17 @@ msgid "Human Ressources: Holidays tracking and workflow\n"
"\n"
" Note that:\n"
" - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in\n"
" HR \ Configuration \ Holidays Status\n"
" HR / Configuration / Holidays Status\n"
" - An employee can make a negative holiday request (holiday request of -2 days for example), this is considered by the system as an ask for more off-days. It will increase his total of that holiday status available (if the request is accepted).\n"
" - There are two ways to print the employee's holidays:\n"
" * The first will allow to choose employees by department and is used by clicking the menu item located in\n"
" HR \ Holidays Request \ Print Summary of Holidays\n"
" HR / Holidays Request / Print Summary of Holidays\n"
" * The second will allow you to choose the holidays report for specific employees. Go on the list\n"
" HR \ Employees \ Employees\n"
" HR / Employees / Employees\n"
" then select the ones you want to choose, click on the print icon and select the option\n"
" 'Print Summary of Employee's Holidays'\n"
" - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR' and with the role 'holidays'. You can define these features in the security tab from the user data in\n"
" Administration \ Users \ Users\n"
" Administration / Users / Users\n"
" for example, you maybe will do it for the user 'admin'.\n"
""
msgstr ""
+75 -56
View File
@@ -4,137 +4,139 @@
#
msgid ""
msgstr ""
"Project-Id-Version: OpenERP Server 5.0.1\n"
"Project-Id-Version: OpenERP Server 5.0.0\n"
"Report-Msgid-Bugs-To: support@openerp.com\n"
"POT-Creation-Date: 2009-05-19 14:22:20+0000\n"
"PO-Revision-Date: 2009-05-20 10:22:20+0000\n"
"Last-Translator: <>\n"
"POT-Creation-Date: 2009-05-19 14:36+0000\n"
"PO-Revision-Date: 2009-06-11 09:26+0000\n"
"Last-Translator: Olivier (OpenERP) <Unknown>\n"
"Language-Team: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: \n"
"Plural-Forms: \n"
"Content-Transfer-Encoding: 8bit\n"
"X-Launchpad-Export-Date: 2009-06-11 09:28+0000\n"
"X-Generator: Launchpad (build Unknown)\n"
#. module: l10n_be
#: selection:vat.intra.xml,init,trimester:0
msgid "Oct/Nov/Dec"
msgstr ""
msgstr "Oct/Nov/Déc"
#. module: l10n_be
#: model:account.account.type,name:l10n_be.user_type_tiers_receiv
msgid "Tiers - Recevable"
msgstr ""
msgstr "Tiers - Recevable"
#. module: l10n_be
#: wizard_view:list.vat.detail,go:0
#: wizard_view:vat.intra.xml,go:0
#: wizard_view:wizard.account.xml.vat.declaration,go:0
msgid "Notification"
msgstr ""
msgstr "Notification"
#. module: l10n_be
#: code:addons/l10n_be/wizard/partner_vat_listing.py:0
#, python-format
msgid "No partner has a VAT Number asociated with him."
msgstr ""
msgstr "Aucun Partenaire n'a de numéro de TVA associé."
#. module: l10n_be
#: wizard_field:vat.intra.xml,init,trimester:0
msgid "Trimester Number"
msgstr ""
msgstr "Numéro de Trimestre"
#. module: l10n_be
#: model:account.account.type,name:l10n_be.user_type_tiers
msgid "Tiers"
msgstr ""
msgstr "Tiers"
#. module: l10n_be
#: wizard_field:wizard.account.xml.vat.declaration,init,period:0
msgid "Period"
msgstr ""
msgstr "Période"
#. module: l10n_be
#: model:account.account.type,name:l10n_be.user_type_charge
msgid "Charge"
msgstr ""
msgstr "Charge"
#. module: l10n_be
#: code:addons/l10n_be/wizard/partner_vat_listing.py:0
#, python-format
msgid "Data Insufficient!"
msgstr ""
msgstr "Données insuffisantes"
#. module: l10n_be
#: wizard_button:list.vat.detail,init,go:0
#: wizard_button:vat.intra.xml,init,go:0
#: wizard_button:wizard.account.xml.vat.declaration,init,go:0
msgid "Create XML"
msgstr ""
msgstr "Créer le fichier XML"
#. module: l10n_be
#: model:account.account.type,name:l10n_be.user_type_capitaux
msgid "Capital"
msgstr ""
msgstr "Capital"
#. module: l10n_be
#: wizard_field:list.vat.detail,go,msg:0
#: wizard_field:vat.intra.xml,go,msg:0
#: wizard_field:wizard.account.xml.vat.declaration,go,msg:0
msgid "File created"
msgstr ""
msgstr "Fichier crée"
#. module: l10n_be
#: selection:vat.intra.xml,init,trimester:0
msgid "Apr/May/Jun"
msgstr ""
msgstr "Avr/Mai/Jun"
#. module: l10n_be
#: constraint:account.account.template:0
msgid "Error ! You can not create recursive account templates."
msgstr ""
"Erreur ! Vous ne pouvez pas créer de modèles de compte de manière récursive."
#. module: l10n_be
#: selection:vat.intra.xml,init,trimester:0
msgid "Jul/Aug/Sep"
msgstr ""
msgstr "Jui/Aoû/Sep"
#. module: l10n_be
#: model:account.account.type,name:l10n_be.user_type_immo
msgid "Immobilisation"
msgstr ""
msgstr "Immobilisation"
#. module: l10n_be
#: wizard_field:list.vat.detail,go,file_save:0
#: wizard_field:vat.intra.xml,go,file_save:0
#: wizard_field:wizard.account.xml.vat.declaration,go,file_save:0
msgid "Save File"
msgstr ""
msgstr "Sauvegarder le Fichier"
#. module: l10n_be
#: wizard_view:vat.intra.xml,init:0
msgid "This wizard will create an XML file for Vat Intra"
msgstr ""
msgstr "Cet Assistant créera un fichier XML pour la TVA Intra"
#. module: l10n_be
#: model:ir.module.module,shortdesc:l10n_be.module_meta_information
msgid "Belgium - Plan Comptable Minimum Normalise"
msgstr ""
msgstr "Belgique - Plan Comptable Minimum Normalise"
#. module: l10n_be
#: wizard_view:list.vat.detail,init:0
msgid "Select Fiscal Year"
msgstr ""
msgstr "Sélectionnez l'Année Fiscale"
#. module: l10n_be
#: wizard_view:vat.intra.xml,init:0
msgid "Partner VAT Intra"
msgstr ""
msgstr "Numéro de TVA Intra du Partenaire"
#. module: l10n_be
#: model:ir.actions.wizard,name:l10n_be.wizard_xml_vat_declaration
#: model:ir.ui.menu,name:l10n_be.account_wizard_vat_declaration
msgid "Periodical VAT Declaration"
msgstr ""
msgstr "Déclaration de TVA Périodique"
#. module: l10n_be
#: constraint:account.tax.code.template:0
@@ -144,101 +146,119 @@ msgstr "Erreur ! Vous ne pouvez pas créer de codes de taxe récursifs"
#. module: l10n_be
#: model:account.account.type,name:l10n_be.user_type_tiers_payable
msgid "Tiers - Payable"
msgstr ""
msgstr "Tiers - Payable"
#. module: l10n_be
#: model:account.fiscal.position.template,name:l10n_be.fiscal_position_template_1
msgid "Régime National"
msgstr ""
msgstr "Régime National"
#. module: l10n_be
#: wizard_view:wizard.account.xml.vat.declaration,init:0
msgid "Select Period"
msgstr ""
msgstr "Sélectionnez la Période"
#. module: l10n_be
#: model:account.account.type,name:l10n_be.user_type_produit
msgid "Produit"
msgstr ""
msgstr "Produit"
#. module: l10n_be
#: model:account.fiscal.position.template,name:l10n_be.fiscal_position_template_2
msgid "Régime Extra-Communautaire"
msgstr ""
msgstr "Régime Extra-Communautaire"
#. module: l10n_be
#: model:account.account.type,name:l10n_be.user_type_view
msgid "Vue"
msgstr ""
msgstr "Vue"
#. module: l10n_be
#: wizard_button:list.vat.detail,go,end:0
#: wizard_button:vat.intra.xml,go,end:0
#: wizard_button:wizard.account.xml.vat.declaration,go,end:0
msgid "Ok"
msgstr ""
msgstr "Ok"
#. module: l10n_be
#: wizard_view:list.vat.detail,init:0
msgid "This wizard will create an XML file for Vat details and total invoiced amounts per partner."
msgid ""
"This wizard will create an XML file for Vat details and total invoiced "
"amounts per partner."
msgstr ""
"Cet Assistant créera un fichier XML pour le détail de la TVA et les montants "
"totaux facturés par Partenaire."
#. module: l10n_be
#: wizard_field:list.vat.detail,init,limit_amount:0
msgid "Limit Amount"
msgstr ""
msgstr "Montant Limite"
#. module: l10n_be
#: model:ir.actions.wizard,name:l10n_be.partner_wizard_vat
#: model:ir.ui.menu,name:l10n_be.partner_wizard_vat_menu
msgid "Annual Listing of VAT-Subjected Customers"
msgstr ""
msgstr "Liste Annuelle des clients assujettis à la TVA"
#. module: l10n_be
#: wizard_field:list.vat.detail,init,fyear:0
#: wizard_field:vat.intra.xml,init,fyear:0
msgid "Fiscal Year"
msgstr ""
msgstr "Année Fiscale"
#. module: l10n_be
#: wizard_view:wizard.account.xml.vat.declaration,go:0
msgid "XML Flie has been Created."
msgstr ""
msgstr "Fichier XML Crée"
#. module: l10n_be
#: model:account.account.type,name:l10n_be.user_type_stock
msgid "Stock et Encours"
msgstr ""
msgstr "Stock et Encours"
#. module: l10n_be
#: code:addons/l10n_be/wizard/account_vat_declaration.py:0
#: code:addons/l10n_be/wizard/partner_vat_listing.py:0
#, python-format
msgid "Data Insufficient"
msgstr ""
msgstr "Données Insuffisantes"
#. module: l10n_be
#: model:ir.ui.menu,name:l10n_be.menu_finance_belgian_statement
msgid "Belgium Statements"
msgstr ""
msgstr "Déclarations Belges"
#. module: l10n_be
#: wizard_field:list.vat.detail,init,test_xml:0
#: wizard_field:vat.intra.xml,init,test_xml:0
msgid "Test XML file"
msgstr ""
msgstr "Tester le Fichier XML"
#. module: l10n_be
#: model:ir.actions.todo,note:l10n_be.config_call_account_template
msgid "Generate Chart of Accounts from a Chart Template. You will be asked to pass the name of the company, the chart template to follow, the no. of digits to generate the code for your accounts and Bank account, currency to create Journals. Thus,the pure copy of chart Template is generated.\n"
"This is the same wizard that runs from Financial Management/Configuration/Financial Accounting/Financial Accounts/Generate Chart of Accounts from a Chart Template."
msgid ""
"Generate Chart of Accounts from a Chart Template. You will be asked to pass "
"the name of the company, the chart template to follow, the no. of digits to "
"generate the code for your accounts and Bank account, currency to create "
"Journals. Thus,the pure copy of chart Template is generated.\n"
"This is the same wizard that runs from Financial "
"Management/Configuration/Financial Accounting/Financial Accounts/Generate "
"Chart of Accounts from a Chart Template."
msgstr ""
"Génère un Plan Comptable à partir d'un Modèle de Plan. Vous devrez indiquer "
"le nom de la Société, le modèle de plan à suivre,le nombre de chiffres pour "
"générer les codes pour vos comptes, le compte bancaire, et la devise pour "
"créer les Jouranux. Ainsi, une copie parfaite du Modèle de Plan sera "
"générée.\n"
"C'est le même Assistant qui est lancé à partir du menu \"Finance & "
"Comptabilité/Configuration/Comptabilité financière/Modèles/Générer le plan "
"de comptes à partir d'un modèle\""
#. module: l10n_be
#: wizard_field:list.vat.detail,init,mand_id:0
#: wizard_field:vat.intra.xml,init,mand_id:0
msgid "MandataireId"
msgstr ""
msgstr "Id du Mandataire"
#. module: l10n_be
#: model:account.account.type,name:l10n_be.user_type_tax
@@ -250,50 +270,49 @@ msgstr "Taxe"
#: code:addons/l10n_be/wizard/partner_vat_listing.py:0
#, python-format
msgid "No VAT Number Associated with Main Company!"
msgstr ""
msgstr "Aucun Numéro de TVA Associé avec la Société Principale !"
#. module: l10n_be
#: wizard_view:vat.intra.xml,init:0
#: wizard_field:vat.intra.xml,init,country_ids:0
msgid "European Countries"
msgstr ""
msgstr "Pays Européens"
#. module: l10n_be
#: wizard_view:vat.intra.xml,init:0
msgid "General Information"
msgstr ""
msgstr "Information Générale"
#. module: l10n_be
#: wizard_view:list.vat.detail,go:0
#: wizard_view:vat.intra.xml,go:0
msgid "XML File has been Created."
msgstr ""
msgstr "Le Fichier XML a été créé."
#. module: l10n_be
#: model:account.account.type,name:l10n_be.user_type_financiers
msgid "Financier"
msgstr ""
msgstr "Financier"
#. module: l10n_be
#: wizard_button:list.vat.detail,init,end:0
#: wizard_button:vat.intra.xml,init,end:0
#: wizard_button:wizard.account.xml.vat.declaration,init,end:0
msgid "Cancel"
msgstr ""
msgstr "Annuler"
#. module: l10n_be
#: model:account.fiscal.position.template,name:l10n_be.fiscal_position_template_3
msgid "Régime Intra-Communautaire"
msgstr ""
msgstr "Régime Intra-Communautaire"
#. module: l10n_be
#: model:ir.actions.wizard,name:l10n_be.partner_vat_intra
#: model:ir.ui.menu,name:l10n_be.partner_intra_vat_menu
msgid "Partner VAT intra"
msgstr ""
msgstr "Numéro de TVA Intra du Partenaire"
#. module: l10n_be
#: selection:vat.intra.xml,init,trimester:0
msgid "Jan/Feb/Mar"
msgstr ""
msgstr "Jan/Fév/Mar"
+64 -52
View File
@@ -4,43 +4,47 @@
#
msgid ""
msgstr ""
"Project-Id-Version: OpenERP Server 5.0.1\n"
"Project-Id-Version: OpenERP Server 5.0.0\n"
"Report-Msgid-Bugs-To: support@openerp.com\n"
"POT-Creation-Date: 2009-05-19 14:22:20+0000\n"
"PO-Revision-Date: 2009-05-20 10:22:20+0000\n"
"Last-Translator: <>\n"
"POT-Creation-Date: 2009-05-19 14:36+0000\n"
"PO-Revision-Date: 2009-06-11 08:50+0000\n"
"Last-Translator: Olivier (OpenERP) <Unknown>\n"
"Language-Team: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: \n"
"Plural-Forms: \n"
"Content-Transfer-Encoding: 8bit\n"
"X-Launchpad-Export-Date: 2009-06-11 08:52+0000\n"
"X-Generator: Launchpad (build Unknown)\n"
#. module: mrp_operations
#: model:process.node,name:mrp_operations.process_node_startoperation0
msgid "Start Operation"
msgstr ""
msgstr "Opération de Départ"
#. module: mrp_operations
#: selection:mrp.production.workcenter.line,state:0
msgid "In Progress"
msgstr ""
msgstr "En progress"
#. module: mrp_operations
#: view:mrp.production.workcenter.line:0
#: selection:mrp.production.workcenter.line,state:0
#: selection:mrp_operations.operation.code,start_stop:0
msgid "Pause"
msgstr ""
msgstr "en Pause"
#. module: mrp_operations
#: constraint:ir.model:0
msgid "The Object name must start with x_ and not contain any special character !"
msgstr "Le nom de l'objet doit commencer avec x_ et ne pas contenir de charactères spéciaux !"
msgid ""
"The Object name must start with x_ and not contain any special character !"
msgstr ""
"Le nom de l'objet doit commencer avec x_ et ne pas contenir de charactères "
"spéciaux !"
#. module: mrp_operations
#: model:process.node,note:mrp_operations.process_node_startoperation0
msgid "Operation is started"
msgstr ""
msgstr "Opération commencée"
#. module: mrp_operations
#: model:process.node,name:mrp_operations.process_node_productionorder0
@@ -50,23 +54,23 @@ msgstr "Ordre de Production"
#. module: mrp_operations
#: view:mrp.production.workcenter.line:0
msgid "Start working"
msgstr ""
msgstr "Commencer à Travailler"
#. module: mrp_operations
#: model:ir.actions.act_window,name:mrp_operations.mrp_production_code_action
msgid "Operations Code"
msgstr ""
msgstr "Code des Opérations"
#. module: mrp_operations
#: code:addons/mrp_operations/mrp_operations.py:0
#, python-format
msgid "Production Order Cannot start in [%s] state"
msgstr ""
msgstr "Un ordre de Production ne peux pas commencer dans l'état [%s]"
#. module: mrp_operations
#: model:process.process,name:mrp_operations.process_process_mrpoperationprocess0
msgid "Mrp Operation Process"
msgstr ""
msgstr "Processus des Opérations de Production"
#. module: mrp_operations
#: field:mrp.production.workcenter.line,state:0
@@ -77,7 +81,7 @@ msgstr "État"
#. module: mrp_operations
#: field:mrp.production.workcenter.line,delay:0
msgid "Delay"
msgstr ""
msgstr "Délai"
#. module: mrp_operations
#: selection:mrp_operations.operation.code,start_stop:0
@@ -92,17 +96,17 @@ msgstr "Production"
#. module: mrp_operations
#: view:mrp_operations.operation:0
msgid "Calendar View"
msgstr ""
msgstr "Vue Calendrier"
#. module: mrp_operations
#: model:process.node,name:mrp_operations.process_node_workorder0
msgid "Work Center"
msgstr ""
msgstr "Centre de Travail"
#. module: mrp_operations
#: constraint:ir.actions.act_window:0
msgid "Invalid model name in the action definition."
msgstr ""
msgstr "Nom du Modèle non valide dans la définition de l'action"
#. module: mrp_operations
#: model:ir.ui.menu,name:mrp_operations.menu_mrp_production_operation_action
@@ -117,7 +121,7 @@ msgstr "Mettre en brouillon"
#. module: mrp_operations
#: field:mrp.production.workcenter.line,date_planned:0
msgid "Date Planned"
msgstr ""
msgstr "Date Planifiée"
#. module: mrp_operations
#: model:ir.ui.menu,name:mrp_operations.menu_mrp_production_code_action
@@ -127,7 +131,7 @@ msgstr ""
#. module: mrp_operations
#: field:mrp.production.workcenter.line,uom:0
msgid "UOM"
msgstr ""
msgstr "UdM"
#. module: mrp_operations
#: view:mrp_operations.operation.code:0
@@ -139,6 +143,8 @@ msgstr "Code d'Opération de Production"
#, python-format
msgid " You cannot Resume the operation other then Pause state !"
msgstr ""
" Vous ne pouvez pas Résumer une Opération qui se trouve dans un état autre "
"que 'en Pause' !"
#. module: mrp_operations
#: model:process.transition,note:mrp_operations.process_transition_productionstart0
@@ -180,13 +186,13 @@ msgstr "Code-barre des Centres de Travail"
#: model:process.node,note:mrp_operations.process_node_doneoperation0
#: model:process.transition,note:mrp_operations.process_transition_startdoneoperation0
msgid "Operation is done"
msgstr ""
msgstr "Opération terminée"
#. module: mrp_operations
#: code:addons/mrp_operations/mrp_operations.py:0
#, python-format
msgid "Operation is already finished !"
msgstr ""
msgstr "Opération déjà terminée !"
#. module: mrp_operations
#: model:process.transition,name:mrp_operations.process_transition_startdoneoperation0
@@ -197,41 +203,42 @@ msgstr ""
#: code:addons/mrp_operations/mrp_operations.py:0
#, python-format
msgid "There is no Operation to be cancelled !"
msgstr ""
msgstr "Il n'y a aucune Opération à annuler !"
#. module: mrp_operations
#: view:mrp.production.workcenter.line:0
#: selection:mrp.production.workcenter.line,state:0
msgid "Finished"
msgstr ""
msgstr "Terminé"
#. module: mrp_operations
#: model:ir.actions.act_window,name:mrp_operations.mrp_production_wc_action_form
#: view:mrp.production.workcenter.line:0
msgid "Work Orders"
msgstr ""
msgstr "Ordres de Travail"
#. module: mrp_operations
#: field:mrp.production.workcenter.line,date_start:0
#: field:mrp_operations.operation,date_start:0
msgid "Start Date"
msgstr ""
msgstr "Date de Début"
#. module: mrp_operations
#: code:addons/mrp_operations/mrp_operations.py:0
#, python-format
msgid "Sorry!"
msgstr ""
msgstr "Désolé !"
#. module: mrp_operations
#: model:process.node,note:mrp_operations.process_node_productionorder0
msgid "Production order for any products"
msgstr ""
msgstr "Ordres de Production pour n'importe quel produit"
#. module: mrp_operations
#: model:ir.module.module,shortdesc:mrp_operations.module_meta_information
msgid "Workcenter Production start end workflow"
msgstr ""
"Flux de Travail de Début et de Fin pour la Production des Centres de Travail"
#. module: mrp_operations
#: field:mrp_operations.operation.code,name:0
@@ -242,7 +249,7 @@ msgstr "Nom de l'Opération"
#: field:mrp.production.workcenter.line,date_finnished:0
#: field:mrp_operations.operation,date_finished:0
msgid "End Date"
msgstr ""
msgstr "Date de Fin"
#. module: mrp_operations
#: constraint:ir.ui.view:0
@@ -252,13 +259,13 @@ msgstr "XML non valide pour l'architecture de la vue"
#. module: mrp_operations
#: model:ir.model,name:mrp_operations.model_mrp_operations_operation_code
msgid "mrp_operations.operation.code"
msgstr ""
msgstr "mrp_operations.operation.code"
#. module: mrp_operations
#: code:addons/mrp_operations/mrp_operations.py:0
#, python-format
msgid "You cannot finish the operation without Starting/Resuming it !"
msgstr ""
msgstr "Vous ne pouvez pas terminer l'opération sans la Commencer/Résumer !"
#. module: mrp_operations
#: help:mrp.production.workcenter.line,delay:0
@@ -268,7 +275,7 @@ msgstr ""
#. module: mrp_operations
#: field:mrp.production.workcenter.line,product:0
msgid "Product"
msgstr ""
msgstr "Produit"
#. module: mrp_operations
#: model:process.transition,note:mrp_operations.process_transition_workstartoperation0
@@ -279,13 +286,13 @@ msgstr ""
#: code:addons/mrp_operations/mrp_operations.py:0
#, python-format
msgid "Operation is not started yet !"
msgstr ""
msgstr "L'Opération n'est pas encore commencée !"
#. module: mrp_operations
#: code:addons/mrp_operations/mrp_operations.py:0
#, python-format
msgid "Error!"
msgstr ""
msgstr "Erreur !"
#. module: mrp_operations
#: field:mrp.production.workcenter.line,production_state:0
@@ -295,23 +302,23 @@ msgstr ""
#. module: mrp_operations
#: field:mrp_operations.operation,order_date:0
msgid "Order Date"
msgstr ""
msgstr "Date de la Commande"
#. module: mrp_operations
#: model:process.node,note:mrp_operations.process_node_workorder0
msgid "Production Work Center"
msgstr ""
msgstr "Centre de Travail de Production"
#. module: mrp_operations
#: code:addons/mrp_operations/mrp_operations.py:0
#, python-format
msgid "Operation is Already Cancelled !"
msgstr ""
msgstr "L'Opération est déjà annulée !"
#. module: mrp_operations
#: model:process.transition,name:mrp_operations.process_transition_productionstart0
msgid "Production start Operation"
msgstr ""
msgstr "Opération de Début de Production"
#. module: mrp_operations
#: field:mrp_operations.operation,workcenter_id:0
@@ -321,7 +328,7 @@ msgstr "Centre de Travail"
#. module: mrp_operations
#: view:mrp.production.workcenter.line:0
msgid "Graph view in hours by workcenter"
msgstr ""
msgstr "Vue Graphe en heures par centre de travail"
#. module: mrp_operations
#: model:ir.actions.act_window,name:mrp_operations.mrp_production_operation_action
@@ -334,6 +341,8 @@ msgstr "Opérations"
#, python-format
msgid "You cannot Pause the Operation other then Start/Resume state !"
msgstr ""
"Vous ne pouvez pas mettre en pause une Opération qui se trouve dans un autre "
"état que Commencée/Résumée !"
#. module: mrp_operations
#: field:mrp_operations.operation,code_id:0
@@ -344,17 +353,17 @@ msgstr "Code"
#. module: mrp_operations
#: model:ir.actions.act_window,name:mrp_operations.mrp_production_wc_confirm_action
msgid "Confirmed Work Orders"
msgstr ""
msgstr "Commandes de Travail Confirmées"
#. module: mrp_operations
#: model:ir.ui.menu,name:mrp_operations.menu_mrp_production_wc_confirm_action
msgid "Work Orders to Do"
msgstr ""
msgstr "Commandes de Travail à faire"
#. module: mrp_operations
#: model:process.node,name:mrp_operations.process_node_canceloperation0
msgid "Cancel Operation"
msgstr ""
msgstr "Opération d'annulation"
#. module: mrp_operations
#: model:process.transition,name:mrp_operations.process_transition_workstartoperation0
@@ -370,23 +379,23 @@ msgstr ""
#: view:mrp.production.workcenter.line:0
#: selection:mrp_operations.operation.code,start_stop:0
msgid "Resume"
msgstr ""
msgstr "Résumer"
#. module: mrp_operations
#: model:process.node,name:mrp_operations.process_node_doneoperation0
msgid "Done Operation"
msgstr ""
msgstr "Opération effectuée"
#. module: mrp_operations
#: field:mrp.production.workcenter.line,qty:0
msgid "Qty"
msgstr ""
msgstr "Qté"
#. module: mrp_operations
#: model:ir.actions.act_window,name:mrp_operations.mrp_production_wc_action
#: model:ir.ui.menu,name:mrp_operations.menu_mrp_production_wc_action
msgid "All Work Orders"
msgstr ""
msgstr "Toutes les Commandes de Travail"
#. module: mrp_operations
#: view:mrp_operations.operation:0
@@ -401,7 +410,7 @@ msgstr "Terminé"
#. module: mrp_operations
#: model:ir.model,name:mrp_operations.model_mrp_operations_operation
msgid "mrp_operations.operation"
msgstr ""
msgstr "mrp_operations.operation"
#. module: mrp_operations
#: view:mrp.production.workcenter.line:0
@@ -418,11 +427,14 @@ msgstr "Brouillon"
#: model:process.node,note:mrp_operations.process_node_canceloperation0
#: model:process.transition,note:mrp_operations.process_transition_startcanceloperation0
msgid "Operation is cancelled"
msgstr ""
msgstr "L'Opération est annulée"
#. module: mrp_operations
#: code:addons/mrp_operations/mrp_operations.py:0
#, python-format
msgid "Operation has already started !' 'You can either Pause /Finish/Cancel the operation"
msgid ""
"Operation has already started !' 'You can either Pause /Finish/Cancel the "
"operation"
msgstr ""
"L'Opération a déjà commencé ! Vous pouvez Mettre en Pause/Terminer/Annuler "
"l'Opération"
+1
View File
@@ -68,6 +68,7 @@ class mrp_production_workcenter_line(osv.osv):
res[op.id] = op.date_planned
return res
_inherit = 'mrp.production.workcenter.line'
_order = "sequence, date_planned"
_columns = {
'state': fields.selection([('draft','Draft'),('startworking', 'In Progress'),('pause','Pause'),('cancel','Canceled'),('done','Finished')],'Status', readonly=True),
'date_start_date': fields.function(_get_date_date, method=True, string='Start Date', type='date'),
+40 -37
View File
@@ -4,16 +4,17 @@
#
msgid ""
msgstr ""
"Project-Id-Version: OpenERP Server 5.0.1\n"
"Project-Id-Version: OpenERP Server 5.0.0\n"
"Report-Msgid-Bugs-To: support@openerp.com\n"
"POT-Creation-Date: 2009-05-19 14:22:20+0000\n"
"PO-Revision-Date: 2009-05-20 10:22:20+0000\n"
"Last-Translator: <>\n"
"POT-Creation-Date: 2009-05-19 14:36+0000\n"
"PO-Revision-Date: 2009-06-11 07:58+0000\n"
"Last-Translator: Olivier (OpenERP) <Unknown>\n"
"Language-Team: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: \n"
"Plural-Forms: \n"
"Content-Transfer-Encoding: 8bit\n"
"X-Launchpad-Export-Date: 2009-06-11 08:04+0000\n"
"X-Generator: Launchpad (build Unknown)\n"
#. module: point_of_sale
#: rml:pos.details:0
@@ -50,7 +51,7 @@ msgstr "Numéro de pièce"
#. module: point_of_sale
#: constraint:ir.actions.act_window:0
msgid "Invalid model name in the action definition."
msgstr ""
msgstr "Nom du Modèle non valide dans la définition de l'action."
#. module: point_of_sale
#: field:pos.order,name:0
@@ -75,7 +76,7 @@ msgstr "Ajouter Produit :"
#. module: point_of_sale
#: rml:pos.lines:0
msgid "Net Total"
msgstr ""
msgstr "Total Net"
#. module: point_of_sale
#: model:ir.ui.menu,name:point_of_sale.menu_action_pos_order_tree2
@@ -86,7 +87,7 @@ msgstr "Commandes du jour"
#: code:addons/point_of_sale/pos.py:0
#, python-format
msgid "No Pricelist !"
msgstr ""
msgstr "Pas de Liste de Prix !"
#. module: point_of_sale
#: wizard_view:pos.sale.get,init:0
@@ -96,7 +97,7 @@ msgstr "Sélectionnez une Commande Ouverte"
#. module: point_of_sale
#: rml:pos.lines:0
msgid "Company"
msgstr ""
msgstr "Société"
#. module: point_of_sale
#: rml:pos.invoice:0
@@ -107,7 +108,7 @@ msgstr "Date de Facture"
#: code:addons/point_of_sale/pos.py:0
#, python-format
msgid "Cannot create invoice without a partner."
msgstr ""
msgstr "Impossible de créer une facture sans partenaire."
#. module: point_of_sale
#: model:ir.actions.report.xml,name:point_of_sale.pos_lines_detail
@@ -182,13 +183,13 @@ msgstr "Ligne de Vente"
#. module: point_of_sale
#: rml:pos.lines:0
msgid "No. Of Articles"
msgstr ""
msgstr "Nombre d'Articles"
#. module: point_of_sale
#: code:addons/point_of_sale/report/pos_invoice.py:0
#, python-format
msgid "Please create an invoice for this sale."
msgstr ""
msgstr "Veuillez créer une facture pour cette vente."
#. module: point_of_sale
#: field:pos.order,date_validity:0
@@ -215,7 +216,7 @@ msgstr "Remboursement"
#. module: point_of_sale
#: field:pos.order,last_out_picking:0
msgid "Last Output Picking"
msgstr ""
msgstr "Dernier Colisage Sortant"
#. module: point_of_sale
#: wizard_view:pos.config.journal,init:0
@@ -250,7 +251,7 @@ msgstr "Fax :"
#. module: point_of_sale
#: wizard_view:pos.scan_product,init:0
msgid "Scan Barcode"
msgstr ""
msgstr "Scanner le code barre"
#. module: point_of_sale
#: field:pos.order,partner_id:0
@@ -335,14 +336,14 @@ msgstr "Qté"
#. module: point_of_sale
#: model:ir.module.module,shortdesc:point_of_sale.module_meta_information
msgid "Point Of Sale"
msgstr ""
msgstr "Point de Vente"
#. module: point_of_sale
#: code:addons/point_of_sale/pos.py:0
#: code:addons/point_of_sale/report/pos_invoice.py:0
#, python-format
msgid "Error !"
msgstr ""
msgstr "Erreur !"
#. module: point_of_sale
#: rml:pos.receipt:0
@@ -352,7 +353,7 @@ msgstr "Utilisateur :"
#. module: point_of_sale
#: field:pos.order.line,create_date:0
msgid "Creation Date"
msgstr ""
msgstr "Date de Création"
#. module: point_of_sale
#: rml:pos.invoice:0
@@ -431,7 +432,7 @@ msgstr "Lignes du Point de Vente du Jour"
#. module: point_of_sale
#: field:pos.order,nb_print:0
msgid "Number of Print"
msgstr ""
msgstr "Nombre d'Impression"
#. module: point_of_sale
#: model:ir.ui.menu,name:point_of_sale.menu_wizard_default_journal
@@ -442,12 +443,12 @@ msgstr "Journaux par défaut"
#: code:addons/point_of_sale/pos.py:0
#, python-format
msgid "No valid pricelist line found !"
msgstr ""
msgstr "Aucune ligne de Liste de Prix valide trouvée !"
#. module: point_of_sale
#: rml:pos.invoice:0
msgid "Draft Invoice"
msgstr ""
msgstr "Facture Brouillon"
#. module: point_of_sale
#: field:pos.order.line,discount:0
@@ -472,7 +473,7 @@ msgstr "Lignes de ticket"
#. module: point_of_sale
#: view:pos.order:0
msgid "Sales Order POS"
msgstr ""
msgstr "Commandes de Vente Point de Vente"
#. module: point_of_sale
#: wizard_button:pos.config.journal,init,set_default_journal:0
@@ -530,12 +531,12 @@ msgstr "Effectuer le paiement"
#: code:addons/point_of_sale/pos.py:0
#, python-format
msgid "No order lines defined for this sale."
msgstr ""
msgstr "Aucune lignes de commande pour cette vente."
#. module: point_of_sale
#: rml:pos.receipt:0
msgid ","
msgstr ""
msgstr ","
#. module: point_of_sale
#: wizard_button:pos.scan_product,init,add:0
@@ -582,7 +583,7 @@ msgstr "Ventes du jour"
#: code:addons/point_of_sale/pos.py:0
#, python-format
msgid "Please provide a partner for the sale."
msgstr ""
msgstr "Veuillez fournir un partenaire pour cette vente."
#. module: point_of_sale
#: view:pos.order.line:0
@@ -607,12 +608,12 @@ msgstr "Utilisateur"
#. module: point_of_sale
#: field:pos.payment,payment_date:0
msgid "Payment Date"
msgstr ""
msgstr "Date de Paiement"
#. module: point_of_sale
#: field:pos.payment,payment_name:0
msgid "Payment Name"
msgstr ""
msgstr "Nom du Paiement"
#. module: point_of_sale
#: rml:pos.details:0
@@ -669,7 +670,7 @@ msgstr "Colisage"
#: code:addons/point_of_sale/wizard/wizard_get_sale.py:0
#, python-format
msgid "You can't modify this order. It has already been paid"
msgstr ""
msgstr "Vous ne pouvez pas modifier cetee commande. Elle a déjà été payée"
#. module: point_of_sale
#: code:addons/point_of_sale/pos.py:0
@@ -740,7 +741,7 @@ msgstr "Rembourser la commande :"
#. module: point_of_sale
#: field:report.transaction.pos,no_trans:0
msgid "Number of Transaction"
msgstr ""
msgstr "Nombre de Transactions"
#. module: point_of_sale
#: rml:pos.invoice:0
@@ -808,8 +809,11 @@ msgstr "Ajouter un paiement :"
#. module: point_of_sale
#: constraint:ir.model:0
msgid "The Object name must start with x_ and not contain any special character !"
msgstr "Le nom de l'objet doit commencer avec x_ et ne pas contenir de charactères spéciaux !"
msgid ""
"The Object name must start with x_ and not contain any special character !"
msgstr ""
"Le nom de l'objet doit commencer avec x_ et ne pas contenir de charactères "
"spéciaux !"
#. module: point_of_sale
#: rml:pos.details:0
@@ -831,7 +835,7 @@ msgstr "Remise totale"
#. module: point_of_sale
#: field:pos.order,invoice_wanted:0
msgid "Create Invoice"
msgstr ""
msgstr "Créer une Facture"
#. module: point_of_sale
#: wizard_view:pos.refund_order,init:0
@@ -883,7 +887,7 @@ msgstr "Journal"
#. module: point_of_sale
#: wizard_field:pos.scan_product,init,gencod:0
msgid "Barcode"
msgstr ""
msgstr "Code Barre"
#. module: point_of_sale
#: rml:pos.invoice:0
@@ -908,7 +912,7 @@ msgstr "Tél. :"
#. module: point_of_sale
#: field:pos.payment,payment_nb:0
msgid "Piece Number"
msgstr ""
msgstr "Numéro de Pièce"
#. module: point_of_sale
#: wizard_field:pos.config.journal,init,default_journal_gift:0
@@ -965,7 +969,7 @@ msgstr "Note de Crédit Fournisseur"
#: code:addons/point_of_sale/wizard/wizard_get_sale.py:0
#, python-format
msgid "UserError"
msgstr ""
msgstr "Error Utilisateur"
#. module: point_of_sale
#: rml:pos.details:0
@@ -1032,7 +1036,7 @@ msgstr "Société :"
#. module: point_of_sale
#: rml:pos.lines:0
msgid "Print Date"
msgstr ""
msgstr "Date d'Impression"
#. module: point_of_sale
#: rml:pos.lines:0
@@ -1047,4 +1051,3 @@ msgstr "Total"
#: rml:pos.receipt:0
msgid "Price"
msgstr "Prix"
+176 -96
View File
@@ -4,16 +4,17 @@
#
msgid ""
msgstr ""
"Project-Id-Version: OpenERP Server 5.0.1\n"
"Project-Id-Version: OpenERP Server 5.0.0\n"
"Report-Msgid-Bugs-To: support@openerp.com\n"
"POT-Creation-Date: 2009-05-19 14:22:21+0000\n"
"PO-Revision-Date: 2009-05-20 10:22:21+0000\n"
"Last-Translator: <>\n"
"POT-Creation-Date: 2009-05-19 14:36+0000\n"
"PO-Revision-Date: 2009-06-11 06:45+0000\n"
"Last-Translator: Olivier (OpenERP) <Unknown>\n"
"Language-Team: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: \n"
"Plural-Forms: \n"
"Content-Transfer-Encoding: 8bit\n"
"X-Launchpad-Export-Date: 2009-06-11 06:48+0000\n"
"X-Generator: Launchpad (build Unknown)\n"
#. module: purchase
#: field:purchase.order,invoiced:0
@@ -23,27 +24,27 @@ msgstr "Facturé & payé"
#. module: purchase
#: model:process.node,note:purchase.process_node_invoiceafterpacking0
msgid "Supplier Invoice pre-generated on receptions for control"
msgstr ""
msgstr "Facture Fournisseur pré-générée à la réception pour contrôle"
#. module: purchase
#: field:purchase.order,location_id:0
msgid "Destination"
msgstr ""
msgstr "Destination"
#. module: purchase
#: selection:purchase.order,invoice_method:0
msgid "From Picking"
msgstr ""
msgstr "Du Colisage"
#. module: purchase
#: rml:purchase.order:0
msgid "Validated By"
msgstr ""
msgstr "Validée par"
#. module: purchase
#: constraint:ir.actions.act_window:0
msgid "Invalid model name in the action definition."
msgstr ""
msgstr "Nom de Modèle non valide dans la définition de l'action"
#. module: purchase
#: field:purchase.order,partner_id:0
@@ -57,24 +58,31 @@ msgstr "Livraison"
#. module: purchase
#: wizard_view:purchase.order.merge,init:0
msgid "Please note that orders will only be merged if they are to the same partner and going to the same location, and lines will only be merged if they are exactly the same except for the quantity and unit."
msgstr "Veuillez noter que les commandes ne seront fusionnées que si elles sont destinées au même partenaire et vont à la même zone de stockage, et que les lignes ne seront fusionnées que si elles sont exactement les mêmes, sauf pour la quantité et l'unité"
msgid ""
"Please note that orders will only be merged if they are to the same partner "
"and going to the same location, and lines will only be merged if they are "
"exactly the same except for the quantity and unit."
msgstr ""
"Veuillez noter que les commandes ne seront fusionnées que si elles sont "
"destinées au même partenaire et vont à la même zone de stockage, et que les "
"lignes ne seront fusionnées que si elles sont exactement les mêmes, sauf "
"pour la quantité et l'unité"
#. module: purchase
#: code:addons/purchase/purchase.py:0
#, python-format
msgid "No Pricelist !"
msgstr ""
msgstr "Pas de Liste de Prix !"
#. module: purchase
#: model:ir.actions.act_window,name:purchase.act_purchase_order_2_stock_picking
msgid "Packing"
msgstr ""
msgstr "Emballage"
#. module: purchase
#: model:process.node,name:purchase.process_node_confirmpurchaseorder0
msgid "Confirmed Purchase"
msgstr ""
msgstr "Achat Comfirmé"
#. module: purchase
#: selection:purchase.order,state:0
@@ -89,12 +97,16 @@ msgstr "Liste de prix d'achat par défaut"
#. module: purchase
#: model:process.transition.action,name:purchase.process_transition_action_invoicefrompurchaseorder0
msgid "Create invoice"
msgstr ""
msgstr "Créer une Facture"
#. module: purchase
#: help:res.partner,property_product_pricelist_purchase:0
msgid "This pricelist will be used, instead of the default one, for purchases from the current partner"
msgstr "Cette liste de prix sera utilisée, au lieu de celle par défaut, pour les achats du partenaire courant"
msgid ""
"This pricelist will be used, instead of the default one, for purchases from "
"the current partner"
msgstr ""
"Cette liste de prix sera utilisée, au lieu de celle par défaut, pour les "
"achats du partenaire courant"
#. module: purchase
#: rml:purchase.order:0
@@ -104,17 +116,22 @@ msgstr "Fax :"
#. module: purchase
#: model:process.transition,note:purchase.process_transition_productrecept0
msgid "Create invoice from product recept"
msgstr ""
msgstr "Créer une Facture à partir du reçu du produit"
#. module: purchase
#: help:purchase.order,pricelist_id:0
msgid "The pricelist sets the currency used for this purchase order. It also computes the supplier price for the selected products/quantities."
msgstr "La liste de prix fixe la devise utilisée pour la commande d'achat. Elle calcule également le prix fournisseur pour les quantités de produits sélectionnées."
msgid ""
"The pricelist sets the currency used for this purchase order. It also "
"computes the supplier price for the selected products/quantities."
msgstr ""
"La liste de prix fixe la devise utilisée pour la commande d'achat. Elle "
"calcule également le prix fournisseur pour les quantités de produits "
"sélectionnées."
#. module: purchase
#: model:process.process,name:purchase.process_process_purchaseprocess0
msgid "Purchase Process"
msgstr ""
msgstr "Processus d'Achat"
#. module: purchase
#: field:purchase.order.line,product_qty:0
@@ -153,7 +170,7 @@ msgstr "Notes"
#. module: purchase
#: rml:purchase.order:0
msgid "N°"
msgstr ""
msgstr "N°"
#. module: purchase
#: rml:purchase.order:0
@@ -179,7 +196,7 @@ msgstr "Référence commande"
#. module: purchase
#: rml:purchase.order:0
msgid "Net Total :"
msgstr ""
msgstr "Total Net :"
#. module: purchase
#: selection:purchase.order,state:0
@@ -188,8 +205,21 @@ msgstr "Annulé"
#. module: purchase
#: help:purchase.order,state:0
msgid "The state of the purchase order or the quotation request. A quotation is a purchase order in a 'Draft' state. Then the order has to be confirmed by the user, the state switch to 'Confirmed'. Then the supplier must confirm the order to change the state to 'Approved'. When the purchase order is paid and received, the state becomes 'Done'. If a cancel action occurs in the invoice or in the reception of goods, the state becomes in exception."
msgstr "État de la commande d'achat ou du devis. Un devis est une commande d'achat à l'état 'Brouillon'. La commande doit alors être confirmée par l'utilisateur, l'état deviendra 'Confirmée'. Le fournisseur devra alors confirmer la commande pour changer l'état à 'Appouvée'. Lorsque la commande d'achat est payée et reçue, l'état devient 'Terminé'. Si une action 'Annuler' est déclenchée dans la facturation ou dans la réception de marchandises, l'état de la commande se met en exception."
msgid ""
"The state of the purchase order or the quotation request. A quotation is a "
"purchase order in a 'Draft' state. Then the order has to be confirmed by the "
"user, the state switch to 'Confirmed'. Then the supplier must confirm the "
"order to change the state to 'Approved'. When the purchase order is paid and "
"received, the state becomes 'Done'. If a cancel action occurs in the invoice "
"or in the reception of goods, the state becomes in exception."
msgstr ""
"État de la commande d'achat ou du devis. Un devis est une commande d'achat à "
"l'état 'Brouillon'. La commande doit alors être confirmée par l'utilisateur, "
"l'état deviendra 'Confirmée'. Le fournisseur devra alors confirmer la "
"commande pour changer l'état à 'Appouvée'. Lorsque la commande d'achat est "
"payée et reçue, l'état devient 'Terminé'. Si une action 'Annuler' est "
"déclenchée dans la facturation ou dans la réception de marchandises, l'état "
"de la commande se met en exception."
#. module: purchase
#: field:purchase.order,origin:0
@@ -199,28 +229,30 @@ msgstr "Origine"
#. module: purchase
#: model:process.node,name:purchase.process_node_packinglist0
msgid "Incoming Products"
msgstr ""
msgstr "Produits Entrants"
#. module: purchase
#: model:process.node,note:purchase.process_node_confirmpurchaseorder0
msgid "Purchase order is confirmed by the user."
msgstr ""
msgstr "La commande d'achat est confirmée par l'utilisateur."
#. module: purchase
#: view:purchase.order:0
msgid "Manually Corrected"
msgstr ""
msgstr "Corrigé manuellement"
#. module: purchase
#: code:addons/purchase/purchase.py:0
#, python-format
msgid "You must first cancel all invoices attached to this purchase order."
msgstr ""
"Vous devez avant tout annuler les factures attachées à cette commande "
"d'achat."
#. module: purchase
#: view:purchase.order:0
msgid "Reference"
msgstr ""
msgstr "Référence"
#. module: purchase
#: rml:purchase.order:0
@@ -230,7 +262,7 @@ msgstr "TVA :"
#. module: purchase
#: rml:purchase.quotation:0
msgid "Tel.:"
msgstr ""
msgstr "Tél. :"
#. module: purchase
#: field:purchase.order.line,account_analytic_id:0
@@ -249,15 +281,26 @@ msgstr "Validé par"
#. module: purchase
#: help:purchase.order,invoice_method:0
msgid "From Order: a draft invoice will be pre-generated based on the purchase order. The accountant will just have to validate this invoice for control.\n"
"From Picking: a draft invoice will be pre-genearted based on validated receptions.\n"
"Manual: no invoice will be pre-generated. The accountant will have to encode manually."
msgid ""
"From Order: a draft invoice will be pre-generated based on the purchase "
"order. The accountant will just have to validate this invoice for control.\n"
"From Picking: a draft invoice will be pre-genearted based on validated "
"receptions.\n"
"Manual: no invoice will be pre-generated. The accountant will have to encode "
"manually."
msgstr ""
"À partir de la Commande: une facture brouillon sera pré-générée basée sur "
"les commandes d'achat. Le comptable devra simplement valider cette facture "
"pour contrôle.\n"
"À partir du Colisage: une facture brouillon sera pré-générée basée sur les "
"réceptions de marchandises validées.\n"
"Manuelle: aucune facture ne sera pré-générée. Le comptable devra les encoder "
"manuellement."
#. module: purchase
#: model:process.node,note:purchase.process_node_packinginvoice0
msgid "Invoice based on deliveries"
msgstr ""
msgstr "Facture basée sur les livraisons"
#. module: purchase
#: rml:purchase.order:0
@@ -272,14 +315,18 @@ msgstr "Ligne de commande"
#. module: purchase
#: code:addons/purchase/purchase.py:0
#, python-format
msgid "You have to select a pricelist in the purchase form !\nPlease set one before choosing a product."
msgid ""
"You have to select a pricelist in the purchase form !\n"
"Please set one before choosing a product."
msgstr ""
"Vous devez sélectionner une liste de prix dans le formulaire d'achat !\n"
"Veuillez en sélectionner une avant d'acheter un produit."
#. module: purchase
#: code:addons/purchase/purchase.py:0
#, python-format
msgid "Wrong Product UOM !"
msgstr ""
msgstr "Unité de Mesure du Produit incorrecte !"
#. module: purchase
#: selection:purchase.order,state:0
@@ -289,7 +336,7 @@ msgstr "Visé par acheteur"
#. module: purchase
#: model:process.node,name:purchase.process_node_productrecept0
msgid "Product Receipt"
msgstr ""
msgstr "Reçu du Produit"
#. module: purchase
#: model:process.transition.action,name:purchase.process_transition_action_confirmpurchaseorder0
@@ -305,7 +352,7 @@ msgstr "Contrôle facture"
#: model:process.node,name:purchase.process_node_draftpurchaseorder0
#: model:process.node,name:purchase.process_node_draftpurchaseorder1
msgid "RFQ"
msgstr ""
msgstr "Demande de Devis"
#. module: purchase
#: selection:purchase.order,state:0
@@ -331,11 +378,12 @@ msgstr "Lignes de la commande"
#: model:process.transition,note:purchase.process_transition_confirmingpurchaseorder1
msgid "Confirm Purchase order from Request for quotation without origin"
msgstr ""
"Confirmer la commande d'achat à partir de la demande de devis sans origine"
#. module: purchase
#: rml:purchase.quotation:0
msgid "Fax:"
msgstr ""
msgstr "Fax :"
#. module: purchase
#: view:purchase.order:0
@@ -345,7 +393,7 @@ msgstr "Montant détaxé"
#. module: purchase
#: rml:purchase.quotation:0
msgid "Expected Date"
msgstr ""
msgstr "Date d'échéance"
#. module: purchase
#: rml:purchase.order:0
@@ -356,12 +404,12 @@ msgstr "Adresse de livraison :"
#: code:addons/purchase/purchase.py:0
#, python-format
msgid "Error !"
msgstr ""
msgstr "Erreur !"
#. module: purchase
#: field:purchase.order,minimum_planned_date:0
msgid "Planned Date"
msgstr ""
msgstr "Date Planifiée"
#. module: purchase
#: view:purchase.order:0
@@ -371,7 +419,7 @@ msgstr "Approuvé par le fournisseur"
#. module: purchase
#: selection:purchase.order,invoice_method:0
msgid "From Order"
msgstr ""
msgstr "De la Commande"
#. module: purchase
#: model:ir.actions.wizard,name:purchase.purchase_order_merge
@@ -387,7 +435,7 @@ msgstr "Destination de la réservation"
#: code:addons/purchase/purchase.py:0
#, python-format
msgid "Invalid action !"
msgstr ""
msgstr "Action non valide !"
#. module: purchase
#: selection:purchase.order,state:0
@@ -402,7 +450,7 @@ msgstr "Liste de prix"
#. module: purchase
#: model:process.node,note:purchase.process_node_purchaseorder0
msgid "When controlling invoice from orders"
msgstr ""
msgstr "En contrôlant la facture à partir des commandes"
#. module: purchase
#: constraint:ir.ui.view:0
@@ -412,17 +460,17 @@ msgstr "XML non valide pour l'architecture de la vue"
#. module: purchase
#: model:process.node,note:purchase.process_node_invoicecontrol0
msgid "Pre-generated supplier invoice to control based on order"
msgstr ""
msgstr "Facture fournisseur pré-générée basée sur la commande"
#. module: purchase
#: model:process.transition,name:purchase.process_transition_invoicefrompurchase0
msgid "Invoice from Purchase"
msgstr ""
msgstr "Facture à partir de l'achat"
#. module: purchase
#: model:process.node,note:purchase.process_node_packinglist0
msgid "Packing is created for the products reception control."
msgstr ""
msgstr "Colis crée pour le contrôle de réception des produits"
#. module: purchase
#: selection:purchase.order,invoice_method:0
@@ -432,12 +480,12 @@ msgstr "Manuel"
#. module: purchase
#: model:process.transition,name:purchase.process_transition_confirmingpurchaseorder1
msgid "Confirming Purchase"
msgstr ""
msgstr "Confirmer l'achat"
#. module: purchase
#: model:process.transition,note:purchase.process_transition_approvingpurchaseorder0
msgid "Approve Purchase order after Confirming"
msgstr ""
msgstr "Approuver la commande d'achat après confirmation"
#. module: purchase
#: selection:purchase.order,state:0
@@ -447,7 +495,7 @@ msgstr "Exception livraison"
#. module: purchase
#: model:process.node,note:purchase.process_node_draftpurchaseorder1
msgid "Encoded manually by the user."
msgstr ""
msgstr "Encodée manuellement par l'utilisateur."
#. module: purchase
#: rml:purchase.order:0
@@ -457,8 +505,12 @@ msgstr "Qté"
#. module: purchase
#: help:purchase.order,minimum_planned_date:0
msgid "This is computed as the minimum scheduled date of all purchase order lines' products."
msgid ""
"This is computed as the minimum scheduled date of all purchase order lines' "
"products."
msgstr ""
"Elle est calculée comme la date planifiée minimum de tous les lignes de "
"produit de la commande d'achat."
#. module: purchase
#: model:ir.actions.act_window,name:purchase.act_res_partner_2_purchase_order
@@ -467,18 +519,24 @@ msgstr "Ordres d'achat"
#. module: purchase
#: help:purchase.order,dest_address_id:0
msgid "Put an address if you want to deliver directly from the supplier to the customer.In this case, it will remove the warehouse link and set the customer location."
msgid ""
"Put an address if you want to deliver directly from the supplier to the "
"customer.In this case, it will remove the warehouse link and set the "
"customer location."
msgstr ""
"Encodez une adresse si vous voulez livrer directement du fournisseur au "
"client. Dans ce cas, le lien vers l'entrepôt sera supprimé et l'emplacement "
"client sera utilisé."
#. module: purchase
#: rml:purchase.quotation:0
msgid "Request for Quotation :"
msgstr ""
msgstr "Demande de Devis"
#. module: purchase
#: model:process.transition,note:purchase.process_transition_confirmingpurchaseorder0
msgid "Confirm Purchase order from Request for quotation"
msgstr ""
msgstr "Confirmer la commande d'achat à partir de la demande de devis"
#. module: purchase
#: view:purchase.order:0
@@ -487,8 +545,10 @@ msgstr "Confirmer cde fourn."
#. module: purchase
#: help:purchase.order,picking_ids:0
msgid "This is the list of picking list that have been generated for this purchase"
msgstr "Ceci est la liste de la liste de picking ayant été généré pour cet achat"
msgid ""
"This is the list of picking list that have been generated for this purchase"
msgstr ""
"Ceci est la liste de la liste de picking ayant été généré pour cet achat"
#. module: purchase
#: model:ir.module.module,shortdesc:purchase.module_meta_information
@@ -504,7 +564,7 @@ msgstr "Réf. Partenaire"
#. module: purchase
#: rml:purchase.order:0
msgid "Taxes :"
msgstr ""
msgstr "Taxes :"
#. module: purchase
#: field:purchase.order,invoiced_rate:0
@@ -514,8 +574,12 @@ msgstr "Facturée"
#. module: purchase
#: code:addons/purchase/purchase.py:0
#, python-format
msgid "You have to select a product UOM in the same category than the purchase UOM of the product"
msgid ""
"You have to select a product UOM in the same category than the purchase UOM "
"of the product"
msgstr ""
"Vous devez sélectionner une Unité de Mesure de la même catégorie que l'Unité "
"de Mesure du Produit"
#. module: purchase
#: field:purchase.order,dest_address_id:0
@@ -531,8 +595,12 @@ msgstr "Ligne de commande"
#. module: purchase
#: code:addons/purchase/purchase.py:0
#, python-format
msgid "You have to select a partner in the purchase form !\nPlease set one partner before choosing a product."
msgid ""
"You have to select a partner in the purchase form !\n"
"Please set one partner before choosing a product."
msgstr ""
"Vous devez sélectionner un partenaire dans le formulaire d'achat !\n"
"Veuillez sélectionner un partenaire avant de choisir un produit."
#. module: purchase
#: view:purchase.order:0
@@ -542,12 +610,12 @@ msgstr "Vue calendrier"
#. module: purchase
#: view:purchase.order:0
msgid "Set to Draft"
msgstr ""
msgstr "Mettre en Brouillon"
#. module: purchase
#: model:process.node,note:purchase.process_node_approvepurchaseorder0
msgid "Purchase order is approved by supplier."
msgstr ""
msgstr "La commande d'achat est approuvée par le fournisseur"
#. module: purchase
#: model:process.node,name:purchase.process_node_invoiceafterpacking0
@@ -563,17 +631,17 @@ msgstr "Commande fournisseur"
#. module: purchase
#: model:process.node,note:purchase.process_node_draftpurchaseorder0
msgid "Request for quotation is proposed by the system."
msgstr ""
msgstr "Une demande de devis est proposée par le système."
#. module: purchase
#: model:process.transition,name:purchase.process_transition_packinginvoice0
msgid "Packing Invoice"
msgstr ""
msgstr "Facture de Colisage"
#. module: purchase
#: model:process.transition,note:purchase.process_transition_invoicefrompackinglist0
msgid "Creates invoice from packin list"
msgstr ""
msgstr "Créer la facture à partir de la liste de colisage"
#. module: purchase
#: view:purchase.order:0
@@ -583,13 +651,14 @@ msgstr "Livraisons & Factures"
#. module: purchase
#: help:purchase.order,origin:0
msgid "Reference of the document that generated this purchase order request."
msgstr ""
msgstr "Référence du document qui a généré la demande de commande d'achat."
#. module: purchase
#: code:addons/purchase/purchase.py:0
#, python-format
msgid "There is no expense account defined for this product: \"%s\" (id:%d)"
msgstr ""
"Il n'y a pas de compte de dépense défini pour ce produit: \"%s\" (id: %d)"
#. module: purchase
#: rml:purchase.order:0
@@ -599,7 +668,7 @@ msgstr "Tél. :"
#. module: purchase
#: model:process.transition,note:purchase.process_transition_purchaseinvoice0
msgid "After Purchase order , Create invoice."
msgstr ""
msgstr "Après la commande d'achat, créer la facture"
#. module: purchase
#: field:purchase.order.line,date_planned:0
@@ -609,12 +678,12 @@ msgstr "Date prévue"
#. module: purchase
#: rml:purchase.order:0
msgid "Our Order Reference"
msgstr ""
msgstr "Notre Référence de Commande"
#. module: purchase
#: rml:purchase.quotation:0
msgid "TVA:"
msgstr ""
msgstr "TVA :"
#. module: purchase
#: view:purchase.order:0
@@ -625,6 +694,7 @@ msgstr "Calculer"
#: constraint:product.pricelist.version:0
msgid "You cannot have 2 pricelist versions that overlap!"
msgstr ""
"Vous ne pouvez pas avoir 2 versions de liste de prix qui se chevauchent !"
#. module: purchase
#: view:purchase.order:0
@@ -634,22 +704,23 @@ msgstr "Annuler cde fourn."
#. module: purchase
#: model:process.transition,name:purchase.process_transition_createpackinglist0
msgid "Create Packing list"
msgstr ""
msgstr "Créer la liste de colisage"
#. module: purchase
#: rml:purchase.order:0
msgid "Total :"
msgstr ""
msgstr "Total :"
#. module: purchase
#: model:process.transition,note:purchase.process_transition_createpackinglist0
msgid "When purchase order is approved , it creates its packing list."
msgstr ""
"Lorsque la commande d'achat est approuvée, la liste de colisage est créée."
#. module: purchase
#: model:process.transition,name:purchase.process_transition_invoicefrompackinglist0
msgid "Invoice from Packing list"
msgstr ""
msgstr "Facture à partir de la liste de colisage"
#. module: purchase
#: field:purchase.order,state:0
@@ -664,7 +735,7 @@ msgstr "Sous-total"
#. module: purchase
#: model:product.pricelist.version,name:purchase.ver0
msgid "Default Purchase Pricelist Version"
msgstr ""
msgstr "Version par Défaut de la liste de Prix d'Achat"
#. module: purchase
#: rml:purchase.order:0
@@ -675,7 +746,7 @@ msgstr "Prix"
#. module: purchase
#: field:purchase.order,fiscal_position:0
msgid "Fiscal Position"
msgstr ""
msgstr "Position Fiscale"
#. module: purchase
#: field:purchase.order,invoice_id:0
@@ -692,7 +763,7 @@ msgstr "Annuler"
#. module: purchase
#: view:res.partner:0
msgid "Purchases Properties"
msgstr ""
msgstr "Propriétés d'Achat"
#. module: purchase
#: field:purchase.order.line,order_id:0
@@ -713,8 +784,11 @@ msgstr "Fusionner les commandes"
#. module: purchase
#: constraint:ir.model:0
msgid "The Object name must start with x_ and not contain any special character !"
msgstr "Le nom de l'objet doit commencer avec x_ et ne pas contenir de charactères spéciaux !"
msgid ""
"The Object name must start with x_ and not contain any special character !"
msgstr ""
"Le nom de l'objet doit commencer avec x_ et ne pas contenir de charactères "
"spéciaux !"
#. module: purchase
#: model:ir.actions.act_window,name:purchase.purchase_form_action_new
@@ -737,12 +811,12 @@ msgstr "Demande de devis"
#. module: purchase
#: model:process.node,name:purchase.process_node_packinginvoice0
msgid "Out Packing"
msgstr ""
msgstr "Colisage Sortant"
#. module: purchase
#: model:process.node,note:purchase.process_node_productrecept0
msgid "Control invoices on receptions"
msgstr ""
msgstr "Contrôle des factures à la réception"
#. module: purchase
#: rml:purchase.order:0
@@ -758,13 +832,16 @@ msgstr "Date approbation"
#: code:addons/purchase/purchase.py:0
#, python-format
msgid "Could not cancel this purchase order !"
msgstr ""
msgstr "Impossible d'annuler cette commande d'achat !"
#. module: purchase
#: model:ir.module.module,description:purchase.module_meta_information
msgid "Module for purchase management\n"
msgid ""
"Module for purchase management\n"
" Request for quotation, Create Supplier Invoice, Print Order..."
msgstr ""
"Module de gestion des achat\n"
" Demande de Devis, Factures Fournisseurs, Impression des Commandes, ..."
#. module: purchase
#: field:purchase.order.line,product_id:0
@@ -775,7 +852,7 @@ msgstr "Produit"
#: code:addons/purchase/purchase.py:0
#, python-format
msgid "No Partner!"
msgstr ""
msgstr "Pas de Partenaire !"
#. module: purchase
#: rml:purchase.order:0
@@ -787,12 +864,12 @@ msgstr "Description"
#. module: purchase
#: model:process.transition,name:purchase.process_transition_productrecept0
msgid "Product recept invoice"
msgstr ""
msgstr "Facture de Réception du Produit"
#. module: purchase
#: rml:purchase.quotation:0
msgid "Expected Delivery address:"
msgstr ""
msgstr "Adresse de Livraison Attendue :"
#. module: purchase
#: model:ir.actions.act_window,name:purchase.purchase_form_action3
@@ -803,7 +880,7 @@ msgstr "Commande d'achat en attente d'approbation"
#. module: purchase
#: model:process.transition,name:purchase.process_transition_confirmingpurchaseorder0
msgid "Confirming Purchase Order"
msgstr ""
msgstr "Confirmer la Commande d'Achat"
#. module: purchase
#: field:purchase.order.line,product_uom:0
@@ -813,7 +890,7 @@ msgstr "UDM produit"
#. module: purchase
#: rml:purchase.quotation:0
msgid "Regards,"
msgstr ""
msgstr "Bien à vous,"
#. module: purchase
#: field:purchase.order.line,move_id:0
@@ -824,23 +901,25 @@ msgstr "Réservation"
#: code:addons/purchase/purchase.py:0
#, python-format
msgid "Could not cancel purchase order !"
msgstr ""
msgstr "Impossible d'annuler la commande d'achat !"
#. module: purchase
#: model:process.transition,name:purchase.process_transition_purchaseinvoice0
msgid "Purchase Invoice"
msgstr ""
msgstr "Facture d'Achat"
#. module: purchase
#: code:addons/purchase/purchase.py:0
#, python-format
msgid "You must first cancel all packing attached to this purchase order."
msgstr ""
"Vous devez, avant tout, annuler tous les colisages attachés à cette commande "
"d'achat."
#. module: purchase
#: rml:purchase.order:0
msgid "Your Order Reference"
msgstr ""
msgstr "Votre Référence Commande"
#. module: purchase
#: view:purchase.order:0
@@ -878,17 +957,17 @@ msgstr "Méthode de facturation"
#. module: purchase
#: model:process.transition.action,name:purchase.process_transition_action_approvingpurchaseorder0
msgid "Approve"
msgstr ""
msgstr "Approuver"
#. module: purchase
#: model:process.node,name:purchase.process_node_approvepurchaseorder0
msgid "Approved Purchase"
msgstr ""
msgstr "Achat approuvé"
#. module: purchase
#: model:process.transition,note:purchase.process_transition_packinginvoice0
msgid "From Packing list, Create invoice."
msgstr ""
msgstr "De la liste de colisage, créer la facture."
#. module: purchase
#: wizard_view:purchase.order.merge,init:0
@@ -898,15 +977,16 @@ msgstr "Êtes-vous sûr de vouloir fusionner ces commandes ?"
#. module: purchase
#: model:process.transition,name:purchase.process_transition_approvingpurchaseorder0
msgid "Approving Purchase Order"
msgstr ""
msgstr "Approuver la Commande d'Achat"
#. module: purchase
#: model:process.transition,note:purchase.process_transition_invoicefrompurchase0
msgid "After approved purchase order , it comes into the supplier invoice"
msgstr ""
"Après que la commande d'achat ait été approuvée, elle se retrouve dans la "
"facture fournisseur"
#. module: purchase
#: field:purchase.order,amount_total:0
msgid "Total"
msgstr "Total"
+7 -3
View File
@@ -21,8 +21,7 @@
##############################################################################
from osv import fields,osv
import tools.sql
from tools.sql import drop_view_if_exists
class report_timesheet_user(osv.osv):
_name = "report_timesheet.user"
@@ -36,7 +35,7 @@ class report_timesheet_user(osv.osv):
}
_order = 'name desc,user_id desc'
def init(self, cr):
tools.sql.drop_view_if_exists(cr, 'report_timesheet_user')
drop_view_if_exists(cr, 'report_timesheet_user')
cr.execute("""
create or replace view report_timesheet_user as (
select
@@ -66,6 +65,7 @@ class report_timesheet_account(osv.osv):
}
_order = 'name desc,account_id desc,user_id desc'
def init(self, cr):
drop_view_if_exists(cr, 'report_timesheet_account')
cr.execute("""
create or replace view report_timesheet_account as (
select
@@ -96,6 +96,7 @@ class report_timesheet_account_date(osv.osv):
_order = 'name desc,account_id desc,user_id desc'
def init(self, cr):
drop_view_if_exists(cr, 'report_timesheet_account_date')
cr.execute("""
create or replace view report_timesheet_account_date as (
select
@@ -127,6 +128,7 @@ class report_timesheet_invoice(osv.osv):
_rec_name = 'user_id'
_order = 'user_id desc'
def init(self, cr):
drop_view_if_exists(cr, 'report_timesheet_invoice')
cr.execute("""
create or replace view report_timesheet_invoice as (
select
@@ -181,6 +183,7 @@ class report_random_timsheet(osv.osv):
return res
def init(self, cr, uid=1):
drop_view_if_exists(cr, 'report_random_timesheet')
cr.execute("""create or replace view report_random_timesheet as (
@@ -220,6 +223,7 @@ class random_timesheet_lines(osv.osv):
_order = "date desc"
def init(self, cr):
drop_view_if_exists(cr, 'random_timesheet_lines')
cr.execute("""create or replace view random_timesheet_lines as (
select
@@ -72,6 +72,7 @@ def _createInvoices(self, cr, uid, data, context={}):
'uos_id': val['value']['uos_id'],
'product_id':data['form']['product_id'],
'invoice_line_tax_id': [(6,0,val['value']['invoice_line_tax_id'])],
'account_analytic_id': sale.project_id and sale.project_id.id or False,
'note':'',
})
create_ids.append(line_id)
+5 -3
View File
@@ -86,18 +86,20 @@ class stock_location(osv.osv):
return res
def product_detail(self, cr, uid, id, field):
def product_detail(self, cr, uid, id, field, context={}):
res = {}
res[id] = {}
final_value = 0.0
field_to_read = 'virtual_available'
if field == 'stock_real_value':
field_to_read = 'qty_available'
cr.execute('select distinct product_id from stock_move where location_id=%s',(id,))
cr.execute('select distinct product_id from stock_move where (location_id=%s) or (location_dest_id=%s)',(id,id))
result = cr.dictfetchall()
if result:
for r in result:
product = self.pool.get('product.product').read(cr, uid, r['product_id'], [field_to_read,'standard_price','name'])
c = (context or {}).copy()
c['location'] = id
product = self.pool.get('product.product').read(cr, uid, r['product_id'], [field_to_read,'standard_price'], context=c)
final_value += (product[field_to_read] * product['standard_price'])
return final_value
+10 -6
View File
@@ -188,12 +188,16 @@
<field name="type">form</field>
<field name="arch" type="xml">
<form string="Production Lot">
<field name="name" select="1"/>
<field name="ref" select="2"/>
<field name="product_id" select="1"/>
<field name="stock_available"/>
<field name="date" select="2"/>
<field colspan="4" name="revisions" nolabel="1"/>
<notebook colspan="4">
<page string="Production Lot">
<field name="name" select="1"/>
<field name="ref" select="2"/>
<field name="product_id" select="1"/>
<field name="stock_available"/>
<field name="date" select="2"/>
<field colspan="4" name="revisions" nolabel="1"/>
</page>
</notebook>
</form>
</field>
</record>