[FIX]:pass the correct context value for the account move
[FIX] account_voucher : Wrong payment date when invoice is paid from bank statement (Ref : Case 592393)
[FIX] account_voucher: when importing invoices the payment date should be set to the statement date instead of being set to the original invoice date
[FIX] account_voucher : Wrong payment date when invoice is paid from bank statement, code forward-port from 6.1 revision 6966 (Ref : Case 592393)
[FIX] account_voucher: implemented on_change to set voucher date based on statement line
[MERGE] Merged in the fix from 6.0 which overwrites the voucher date and period in case the on_change was not executed
[IMP] Display account field in purchase reciept when no supplier define
[MERGE] with 7.0
[MERGE] with 7.0
[MERGE] with 7.0
[IMP] improve domain
[MERGE] [FIX] account_voucher: forward port of fixes from 6.1 (rev 6966)
When importing invoices to a bank statement the bank statement lines are created with statement date instead of today
Set the date on the created voucher in the same wizard to the statement date instead of invoice date (problematic if different period)
When creating the account moves (at bank statement confirmation), make sur the date and period of the vouncher are synchronised
[FIX] mail: for mass mailing, replies in document False by default

Post a copy in the document is False by default, and it does not make sense to replies in the document if the copy is not itself in the document.
Therefore, if post a copy in the document is false by default, replies in the document should be false too.

Moreover, reply_to is required in the form view if mass mailing mode and post a copy is false OR replies in the document is false
But, to avoid updating the view, in the send_mail python function, if no reply to is set and post a copy or replies is false, we set the from email as the reply_to email
[FIX] mail: same_thread back to True by default, otherwise this is not anymore possible to send email in non mass mailing. Same thread should be changed to False in trunk release
Launchpad automatic translations update.
[FIX] stock: when creating manufacturing order from procurement workflow, do not write location on state (already set previously). (opw 603600)

This avoids having an access rights error when trying to write on a move in done state (eg: in case of force availibility)
[MERGE] Forward-port of latest 7.0 bugfixes, up to rev. 9801 revid:mat@openerp.com-20140131160304-22mokur2uuo1cw4r
Launchpad automatic translations update.
Launchpad automatic translations update.
Launchpad automatic translations update.