[FIX] res.config.installer: correct module installing
[FIX] res.config.installer: correct module installing
[FIX] Passed context in write(...)(Courtesy: Humberto Arocha(hbto)). (Maintenance Case: 586824)
Launchpad automatic translations update.
[I18N] base: update translation templates for latest term changes due to bug fixes
[FIX] timezone: under windows os.environ["TZ"] was not affecting the server,

now it does (probably because we make sure to first set the environment
*then* import the time module. Works fine under Windows XP.
[FIX] module loading: allow addons path entries to have substring of others.
i.e. having ./addons/ and ./addons2/ is now possible
[REVERT] tools.translate: undo rev 4874 refactoring and renaming `trans_parse_view`, was meant for trunk

rev 4874 = rev-id xmo@openerp.com-20130306095720-3277aw0rq9pzpsw4
Launchpad automatic translations update.
[FIX] base: invalid address in demo data causes failure in Google Maps lookup

Apprently on 2013-03-08 Google Maps stopped
returning a location in Belgium for this invalid
street name.

We consider Google Maps as a commodity so it
is ok to have the crm_partner_assign tests
fail in case our lookup mechanism does
not work anymore.
[FIX]tools/mail: fix regex when sanitizing html containing mail address
[FIX] py2exe: keep the code unoptimized (i.e. no -Ox).

This is necessary to keep assert statements throwing AssertException,
which are tested by our test suite, which is integrated to the server.
Launchpad automatic translations update.
Launchpad automatic translations update.
Launchpad automatic translations update.
[FIX] report: fallback on default font when a specified font does not exist.
Launchpad automatic translations update.
[IMP] res_partner: use tools.email_split instead of custom regex when parsing partner_name to find an email.
[FIX] res_partner: parse_partner_name now uses standard tools method to parse the name and find the email, instead of a custom regex.
[FIX] web_services: fix db dump/restore when authentication requires a password on non-win32 systems

The various pg_* utilities require the password
via a special environment variable or a special
`pgpass` file in the user home, even on Unix,
namely when the PostgreSQL connection is done
via TCP and not via a unix socket.

Setting the environment variable is relatively
safe if it is removed from the environment
immediately after the operation, and saves user
the trouble of managing the pgpass file themselves.

This had been fixed at revision 3992 but was
incorrectly removed for non win32 platforms
at revision 4424 (rev-id stw@openerp.com-20120912114651-8hcliparft1ep9tc)