[FIX] l10n_multilang: remove force_write attribute in process_translations


When processing a translation, the module used to replace the original term by the translated value for accounts (only object with force_write=True).
This lead to only having the translated version for every user, independent of user's language.
On new chart of accounts, will have different account names according to the user preference.
Keep argument force_write in API for stability reason (will be removed in trunk)
[FIX] stock: use eventual serial number attribute into account while doing product reservation
[FIX] account: generate the accounts based on templates with untranslated terms (so benefit from translation)
[IMP] l10n_multilang: revert previous change and move it to l10n_multilang, the accounts are now translatable and with the correct source value
[IMP] l10n_multilang: remove force_write from function call, mark parameter as deprecated
Launchpad automatic translations update.
Launchpad automatic translations update.
Launchpad automatic translations update.
Launchpad automatic translations update.
[FIX] stock: include enventual serial number in product reservation procedure
done using context for stability reason
wont be needed in new wms
opw 600078
[FIX] hr_recruitment: avoid overriding email_from and email_cc in
message_update. This behavior makes sens only in message_new when
setting initial parameter of the applicant, not when somebody sends
an email on the record.
Removed priority change when there is  a 'priority' key in msg; but
this key is not likely to be present in a parsed email.
Removed updated values change due to a mapping of values present in
the email. This code was a copy-and-paste from crm and did not have
any meaning in hr_recruitment.

Also removed unnecessary code in project, project_issue, crm_helpdesk
and crm_claim for the same reasons as for hr_recruitment.
[FIX] l10n_multilang: remove force_write attribute in process_translations
When processing a translation, the module used to replace the original term by the translated value for accounts (only object with force_write=True). Now getting real multilang feature.
Generates the accounts with no language to get the untranslated value
[FIX] document: correct numbering of attachments with the same name
Launchpad automatic translations update.
[FIX] purchase: Purchase Analysis view was using incorrect JOIN order

The starting table for Purchase Analysis is purchase_order_line
not purchase_order. The previous code was using a wrong JOIN
combination starting from purchase_order, which resulted in
a crash if an empty PO was created.
In order to prevent this an extra  WHERE clause on product_id
being NOT NULL was added, but this was incorrect too as it
prevented PO lines with no product_id value from appearing
in the Purchase Analysis results, while being perfectly valid.
[FIX] stock: `product cost` field in partial picking wizard must respect decimal precision

Without the right precision the default rounding is
applied and causes a possible loss of precision when
the `Product Price` precision is increased.
This can in turn lead to incorrect average price
computations.
[FIX] stock: programming error in average price computation for multiple lines of the same product

While processing a picking we must keep track of
previously processed lines as they modify the
stock on hand but are not yet included in the
`qty_available` function.
Negative stock on hand is handled as if
the stock was zero as far as the average
price computation is concerned.
[FIX] stock: no early currency rounding when computing average price

It is a common need to set a higher decimal precision
for `Product Price` (i.e. the product cost field) for
high volume / low value items. This may typically
require up to 4-6 decimals for e.g. EUR/USD-based
companies where the currency has 2 decimals.
In that case the product cost should be stored with
full precision without applying the currency rounding.
The appropriate currency rounding will be applied
anyway as soon as a transaction actually uses that
product cost (typically in a SO/PO)
[FIX] purchase: analysis view must not group by quantity, otherwise identical PO lines are counted only once

The product quantity is one of the columns that must be
aggregated, not used to fold PO lines into the same
result row.
This, combined with missing aggregation operators
was causing multiple identical PO lines from the
same PO to be merged together and only counted once
in some aggregations.
[FIX] sale,sale_stock: sales analysis view using incorrect JOIN and group by clause

Similarly to the recent fixes in Purchase Analysis,
the Sales Analysis view must not group on the quantity
field. It is one of the columns that must be aggregated,
not used to fold PO lines into the same
result row.
The line count was also incorrect because of this, and
had to be corrected to actually count() the underlying
SO lines.

In addition, the JOINs were done in the wrong order,
which could cause problems (e.g. if an empty SO ever
landed in the database, all the SO line columns
would be empty in the JOIN, and cause errors)